| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 287.1 | | MIPSBX::thomas | The Code Warrior | Fri Jun 21 1991 10:54 | 218 |
| The 700 doesn;t really have anything to manage. Using either netstat -s -i
or if you have DECnet/OSI for ULTRIX installed, you ncl to show the device.
fza0 FDDI counters at Fri Jun 21 09:51:04 1991
63655 seconds since last zeroed
1064855366 ANSI MAC frames count
0 ANSI MAC frame errors
0 ANSI MAC frames lost
208443298 bytes received
12703150 bytes sent
1388059 data blocks received
147811 data blocks sent
100915359 multicast bytes received
1035446 multicast blocks received
604532 multicast bytes sent
7428 multicast blocks sent
0 transmit underrun errors
0 send failures
0 FCS check failures
0 frame status errors
0 frame alignment errors
0 frame length errors
207 unrecognized frames
0 unrecognized multicast frames
0 receive data overruns
0 system buffers unavailable
0 user buffers unavailable
0 ring reinitialization received
0 ring reinitialization initiated
0 ring beacon process initiated
0 duplicate tokens detected
0 duplicate address test failures
0 ring purge errors
0 bridge strip errors
0 traces initiated
0 traces received
0 LEM reject count
0 LEM events count
0 LCT reject count
0 TNE expired reject count
1 Completed Connection count
0 Elasticity Buffer Errors
fza0 FDDI status
Adapter State: Running State
LED State: Green
Link State: On Ring Running
Duplicate Address Condition: Absent
Ring Purger: Non Purger
Negotiated TRT: 7.987 ms
Upstream Neighbor Address: 08-00-2B-1D-64-C2
UNA Timed Out: False
Claim Token Yield: False
Frame Strip Mode: Source Address Match
Ring Error Reason: No Reason
Last Direct Beacon SA: 00-00-00-00-00-00
Physical Port State: In Use
Neighbor Physical Port Type: Master
Reject Reason: No Reason
Physical Link Error Estimate: 15
fza0 FDDI characteristics
Link Address: 08-00-2B-19-D2-69
Firmware Revision: 1.0B
ROM Revision: 1.0
SMT Version ID: 1
Requested TRT: 8.000 ms
Maximum TRT: 173.015 ms
Valid Transmission Time: 2.621 ms
LEM Threshold: 8
PMD Type Multimode
ncl> show fddi station fddi-1 all
Node 0 FDDI Station fddi-1
AT 1991-06-21-09:48:47.561-04:00I0.093
Identifiers
Name = fddi-1
Status
UID = 08E99504-2F2E-11CA-8A95-08002B1C8F30
State = On
Last Set Station ID = 00-00-00-00-00-00-00-00
Characteristics
Station ID = 08-00-2b-19-d2-69-00-00
Type = SAS
SMT Version ID = 1
SMT Maximum Version ID = 1
SMT Minimum Version ID = 1
Communication Port = fza0
Counters
Creation Time = 1991-06-20-15:10:09.801-05:00Iinf
Selftest Failures = 0
Traces Received = 0
Configuration Changes = 0
ncl> show fddi station fddi-1 link 1 all
Node 0 FDDI Station fddi-1 Link 1
AT 1991-06-21-09:49:05.342-04:00I0.094
Identifiers
Index = 1
Status
State = On-Ring Run
UID = 08E99505-2F2E-11CA-8A95-08002B1C8F30
Negotiated TRT = 7.987 ms
Duplicate Address Flag = Success
Upstream Neighbor = 08-00-2b-1d-64-c2
Old Upstream Neighbor = 00-00-00-00-00-00
Upstream Neighbor Duplicate Address Flag = False
Downstream Neighbor = 00-00-00-00-00-00
Old Downstream Neighbor = 00-00-00-00-00-00
Ring Purger State = Non-purger
Frame Strip Mode = SA Match
Ring Error Reason = No Error
Loopback = False
Ring Latency = 0.000 ms
Characteristics
Link Address = 08-00-2b-19-d2-69
Requested TRT = 8.000 ms
Valid Transmission Time = 2.621 ms
Restricted Token Timeout = 0.000 ms
Ring Purger Enable = False
Counters
Creation Time = 1991-06-20-15:10:09.801-05:00Iinf
Frame Count = 1062716301
Error Count = 0
Lost Count = 0
Octets Received = 208184504
Octets Sent = 12693530
PDUs Received = 1385978
PDUs Sent = 147679
Multicast Octets Received = 100731398
Multicast Octets Sent = 603479
Multicast PDUs Received = 1033567
Multicast PDUs Sent = 7415
Transmit Underruns = 0
Transmit Failures = 0
Block Check Errors = 0
Frame Status Errors = 0
PDU Length Errors = 0
Unrecognized Individual Destination PDUs = 207
Unrecognized Multicast Destination PDUs = 6351
Receive Data Overruns = 0
Unavailable Link Buffers = 0
Unavailable User Buffers = 0
Ring Initializations Initiated = 0
Ring Initializations Received = 0
Ring Beacons Initiated = 0
Duplicate Address Test Failures = 0
Duplicate Tokens Detected = 0
Ring Purge Errors = 0
FCI Strip Errors = 0
Traces Initiated = 0
Directed Beacons Received = 0
Token Count = 0
ncl> show fddi station fddi-1 phy port 1 all
Node 0 FDDI Station fddi-1 PHY Port 1
AT 1991-06-21-09:49:12.698-04:00I0.094
Identifiers
Index = 1
Status
State = In Use
UID = 08E99506-2F2E-11CA-8A95-08002B1C8F30
Neighbor PHY Type = M
Link Error Estimate = 15
Broken Reason = None
Reject Reason = None
Characteristics
PHY Type = S
PMD Type = ANSI Multi-Mode
LEM Treshold = 8
Counters
Creation Time = 1991-06-20-15:10:09.801-05:00Iinf
Elasticity Buffer Errors = 0
LCT Rejects = 0
LEM Rejects = 0
Link Errors = 0
Connections Completed = 1
|
| 287.2 | Unfortunate , but true... | STAR::SALKEWICZ | It missed... therefore, I am | Fri Jun 21 1991 17:33 | 13 |
| UIltrix has not provided any way to adjust the FDDI ring parameters?
Like TReq for example?
This is also true for VMS, but we plan to update DECnet-VAX ASAP
with some additional management functions for FDDI. It is unfortunate
that these products are not more manageable right now. Popular
belief is that there should be little or no need to catually manage
the FDDI ring parameters,.. but I guess nobody really has enough
experience yet to know what the field will trun up.
/Bill
|
| 287.3 | | MIPSBX::thomas | The Code Warrior | Fri Jun 21 1991 18:06 | 1 |
| Nope. it's something that's supposed be added but ...
|
| 287.4 | MSU 1.1 can manage DECbridge 500 | MIGHTY::LEVY | | Thu Jun 27 1991 11:02 | 8 |
| re: <<< Note 287.0 by TRHLE1::INGVARD "You ask why I say Ultrix" >>>
>He has no VAX/VMS only ULTRIX systems. I know that MSU 1.1 wil manage
>DECbridge 6xx. I have not any info about managing DEC FDDIcontroller 700 or
>DECbridge 500.
MSU 1.1 speaks RBMS-protocol, and can therefore manage ALL Digital
bridges (except DECbridge 90).
|
| 287.5 | | TRHLE1::INGVARD | You ask why I say Ultrix | Fri Jun 28 1991 07:10 | 6 |
| re .4
Thank you very mutch
Ole
|