| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 536.1 | Thinwire FDDI? | STAR::SALKEWICZ | It missed... therefore, I am | Fri Apr 10 1992 08:18 | 9 |
| Correct me if I'm wrong, but the term "thinwire FDDI" has
no meaning to me. Thinwire is a Ethernet thing,.. copper wire
and electrons.
If we have a product or set of products that actually refer to
themselves as Thinwire FDDI, we're all going to be lost.
/Bill
|
| 536.2 | | MIPSBX::thomas | The Code Warrior | Fri Apr 10 1992 08:41 | 2 |
| We have a copper FDDI board which runs over sheilded
twisted pair or thinwire cable.
|
| 536.3 | Did we really name it "Thinwire FDDI"? | STAR::SALKEWICZ | It missed... therefore, I am | Fri Apr 10 1992 13:21 | 6 |
| OK,.. that was another term I didn't like... "copper FDDI",..
I guess we're going to live with the confusion.
/Bill
|
| 536.4 | | STAR::GILLUM | Kirt Gillum | Fri Apr 10 1992 13:25 | 15 |
|
We, in VMS, haven't tested with copper FDDI yet. The Red light is
definitely a sign of something bad. Nothing struck me out of the
parameters that were in the log file that you included.
Excuse me if you included this in your original note, but if you reboot
the DECstation, does the connection come back up (i.e., both DEFZA and
concentrator lights turn green)?
On naming, I agree with Bill. 'Thinwire' is a name that is more closely
associated with Ethernet. Perhaps we should call this copper FDDI
stuff 'twisted pair', 'STP', or something else...
Paul, Is there an official name for this medium?
|
| 536.5 | | KYOA::KOCH | It never hurts to ask... | Fri Apr 10 1992 17:51 | 3 |
| In the field, ThinWire FDDI is already being used. We were thinking the
meaning of the acronym be changed to Fast Distributed Data Interface.
If they ever decide on UTP FDDI, what will Bill do?
|
| 536.6 | Re. .4 | UTRTSC::DENIJS | | Mon Apr 13 1992 07:38 | 10 |
| Re. 4
Kirt, After boot of the DECstation the connection comes up ok and works
ok. Only after a while the problems begin .
If you look at the counters you see that we gone over the LEM error
rate. I wonder,is there anybody who has seen this kind of connection
work?
Peter.
|
| 536.7 | DEFZA Status | QUIVER::P_SHORT | | Mon Apr 13 1992 10:55 | 8 |
|
RE: .0
Is the information you gave on the status and counters of the DEFZA
talem after the link has "broken"? We are curious because it looks as
if it was taken while everything is up and running.
Pam
|
| 536.8 | Re .7 | UTRTSC::DENIJS | | Tue Apr 14 1992 09:40 | 11 |
| Pam,
In this case the link went up and down while the customer had a command
file to take the counters every minute.If the problems affect the
station to much they reboot via ethernet.The counter info is a snapshot
from the link going up and down.
The link state is off fault recovery while during normal operation the
state is On Ring running. I have more info available if you want.
Cheers, Peter.
|
| 536.9 | FDDI on Thinwire | LEVERS::J_FITZGERALD | | Tue Apr 14 1992 11:50 | 34 |
|
Hi Peter,
First to answer your question of "has anyone ever tested an FDDI
over thinwire setup" Let me sate that numerous tests have been
run. We currently are using a network consisting of 6 DECstation
5000's connected via a concentrator and bridge to an Ethernet
backbone. This setup has been running now for about 6 months.
The setup consists of two 100 meter lengths of thinwire, a 10meter
length and one link of approx. 5 meters. We also have two 100 meter
lengths of STP. As far as seeing the problem you describe, we have
not. From a hardware standpoint I do however, have some
suggestions/comments.
Recently, a problem was found with the mounting of the DEFZA-CA
into the workstation. The metal screws and spacers used to secure the
module can possibly short to vias on the board. This hardware
should be replaced with nylon screws and spacers.
I assume from your note that only approx. 10 meters of untapped
thinwire cable is being used and indeed it is thinwire and not some
RG58 variant. To state the obvious, you did remove the 50 ohm
Ethernet terminators right? Sorry, but I had to ask.....
Just to insure that the modules you are using are
completely up to date. The 6 port thinwire module and
the DEFZA-CA module should both have visible ECO's
(wire adds).
Thats, about all I can think of right now. If you would prefer
give me a call @ DTN 227-3646.
John Fitzgerald
|
| 536.10 | could be cabling? | QUIVER::WEEKS | | Tue Apr 14 1992 12:24 | 9 |
| What happens to the link if you remove the cable from the defza while you're
experiencing the error? Does the LED blink green?
Phil
|
| 536.11 | | STAR::GILLUM | Kirt Gillum | Wed Apr 15 1992 14:50 | 17 |
|
Re; "Thinwire" Naming. I guess it's a done deal. No big deal.
Re; Rebooting the system after the failure clears the problem
(temporarily). This means to me that a selftest operation probably
clears the fault on the board.
If .9's suggestions don't clear up the problem, there's probably a
driver problem in fault recovery. Upon a hard fault, the driver should
re-init the device and attempt to bring it back on ring (PC tests cause
a hard fault on the DEFZA). This is not to say that whatever's causing
the hard faults shouldn't be fixed...
Phil asks a good question too.
Kirt
|
| 536.12 | RE .9/.10/.11 | UTRTSC::DENIJS | | Thu Apr 16 1992 15:22 | 17 |
| Re .9
John,the thinwire connection is point to point (no terminator), i will
check your suggestions about the metal screws and if needed give you a
call. Thanx
Re .10/.11
Kirt/Phil, i think i have seen last time after the link failed some
time later the leds were blinking green again but the problem is it can
take several hours before failing. the customer has most of the time
switched to ethernet.I will check for this again.
Thanx for the replies so far,i will keep you posted.
Peter
|
| 536.13 | | QUIVER::WEEKS | | Thu Apr 16 1992 16:39 | 10 |
| Peter,
It would help a great deal to know if the leds blink green immediately after
removing the cable, sometime later could mean that the Decstation was rebooted.
This information would help to isolate whether it is a cable problem, internal
firmware/driver problem.
Phil
|
| 536.14 | Re .13 | UTRTSC::DENIJS | | Tue Apr 21 1992 11:53 | 11 |
|
Phil,
Let me get this clear,after the problem has occurred you want me to
remove the cable and see if the leds blink green before rebooting the
station? If so,i can instruct the customer to have a look at this since
it can take several hours before the problem occurs.
Cheers, Peter
|
| 536.15 | Re .13 / mote info about the leds | UTRTSC::DENIJS | | Wed Apr 22 1992 15:14 | 54 |
| Phil,
Re-reading my original note i found that i did not include the
interresting part of the NETSTAT counters , so here are two other
samples. Note the led state and fDDI status at 8:45 and 8:46,the
system is definitely not booted inbetween. 8:45 shows led state
green and blinking and link state "off fault recovery".
I think this will answer your question about the link.
If you still want me to remove the cable after the fault pls
let me know.
===================================================================
fza0 FDDI counters at Thu Mar 19 08:45:01 1992
fza0 FDDI status
Adapter State: Running State
LED State: Green and Blinking
Link State: Off Fault Recovery
Duplicate Address Condition: Absent
Ring Purger: Purger off
Negotiated TRT: 7.987 ms
Upstream Neighbor Address: 08-00-2B-27-4B-4B
UNA Timed Out: False
Claim Token Yield: False
Frame Strip Mode: Bridge Strip
Ring Error Reason: Ring Init Received
Last Direct Beacon SA: 00-00-00-00-00-00
Physical Port State: Starting
Neighbor Physical Port Type: Master
Reject Reason: Remote Reject
Physical Link Error Estimate: 15
===================================================================
fza0 FDDI counters at Thu Mar 19 08:46:01 1992
fza0 FDDI status
Adapter State: Running State
LED State: Green
Link State: On Ring Running
Duplicate Address Condition: Absent
Ring Purger: Purger off
Negotiated TRT: 7.987 ms
Upstream Neighbor Address: 08-00-2B-27-4B-4B
UNA Timed Out: False
Claim Token Yield: False
Frame Strip Mode: Bridge Strip
Ring Error Reason: Ring Init Received
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
Peter.
|
| 536.16 | Is this resolved? | LEVERS::J_FITZGERALD | | Wed Apr 29 1992 10:21 | 2 |
| Hi Peter, Has this issue been solved? If not I think we need to
understand it..Where is the link setup? Thanks, John F.
|
| 536.17 | Re .16 | UTRTSC::DENIJS | | Fri May 01 1992 03:26 | 10 |
| John,
This is not resolved yet but the problem is that the customer only lets
us work on the concentrator first mondaymorning of the month because
this concentrator is in his central computerroom. We have ordered a new
concentrator to connect to a SAS port to the concentrator in the
computerroom so we can start troubleshooting this problem.
What link setup are you referring to?
Cheers, Peter.
|
| 536.18 | Bad port on the Concentrator? | STAR::GILLUM | Kirt Gillum | Tue Jun 30 1992 15:16 | 27 |
|
I realize it has been while since there's been activity on this
subject, but I just got off of the phone with a customer who is also
having problems with his "thinwire" FDDI.
This customer runs the LAVC protocol over the DEFZA-CA. He was
noticing that the device was timing out alot (over 32000 times in a
weekend). The driver was indicating transmit timeouts (if a transmit
takes more than 3 seconds to generate an interrupt, we declare it a
transmit lockup situation, and recycle the device). The driver and
cluster protocol recovered everytime, but this error rate was
unacceptable.
I suggested he try a new port on the concentrator, and everything has
been working fine.
From tracing the timeouts, it appears that it takes anywhere from 5 to
30 seconds for the DEFZA to rejoin the ring after this transmit lockup
situation occured.
Does anyone know why a Concentrator port that passes self test would
flake out like this? Does anyone know what group is responsible for
this concentrator?
Kirt
|
| 536.19 | DEFZA on VAXstation 4000 model 90 | VICKI::DODIER | Food for thought makes me hungry | Mon Oct 26 1992 12:14 | 38 |
| I am currently trying to get the DEFZA-CA to run on a VAXstation
4000 model 90. Supposedly, it is supported (or will be soon). I have
VMS 5.5-2HW.
I actually got it to work by accident. Before I knew about the
point to point connection, I connected it with a T-connector on the
workstation end but not one on the concentrator. This would allow the
green LED of the DEFZA to come on solid. The one on the concentrator.
would blink green.
Once the DEFZA LED was on, I shut off the network and re-started it
and FZA-0-0's line and circuit would come up in an "on" state. I then
removed the T-connector and connected it up the right way. The circuit
would then see the various adjacent nodes. The concentrator LED would
also go to a solid green state.
If I shut the system down and connect the DEFZA in a point to point
manner, and then boot the system, the FZA-0-0 line and circuit will not
come up. Both the DEFZA and concentrator LED would be solid green
before I booted the system. If I shut the network off and then do an
@STARTNET, I get the following error -
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available
, unit is active
%NCP-W-INVIDE, Invalid identification format , Line
Line = FZA-0-1
%SYSTEM-F-IVDEVNAM, invalid device name
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = FZA-0-0
%NCP-W-INVIDE, Invalid identification format , Circuit
Circuit = FZA-0-1
%SYSTEM-F-IVDEVNAM, invalid device name
Do I need something greater than VMS 5.5-2HW or is this another
problem ?
Any help appreciated.........Ray
|
| 536.20 | bug in V5.5-2HW | STAR::GAGNE | David Gagne - VMS/LAN Development | Mon Oct 26 1992 14:00 | 6 |
| The line and circuit names are incorrect - I believe that has been
fixed in V5.5-2 (normal release).
You need to set those line and circuits OFF, CLEAR them, and PURGE
them. Then you have to DEFINE and SET LINE/CIRCUIT FZA-0 STATE ON.
This should fix your problems.
|
| 536.21 | Still getting errors | VICKI::DODIER | Food for thought makes me hungry | Mon Oct 26 1992 15:12 | 26 |
| re:-1
I did as you suggested and at the point where STARTNET.COM does the
SET KNOWN LINES ALL, I get an "IVADDR - invalid media address" fatal error.
Consequently, the SET KNOWN CIRCUITS ALL gave an "unrecognized component,
circuit" warning.
I did a list/show known line/circuit to make sure I got rid of all
the old ones and didn't see any. A reboot produced the same results
(i.e. error and no FZA-0-0 or 1 lines/circuits).
The weird part about the whole thing is that when I did the work
around I mentioned earlier (with the T-connector), it works as is. I
also changed the line/circuit name and brought up the newly named one
(FZA-0) and it worked at that point. The reboot is where I have
problems.
As I mentioned, I checked the line/circuit for the proper name after
the reboot and all looked OK. I'm not sure what difference the T-connector
makes, but that's the only way I can get this thing to work with VMS
5.5-2HW.
Do I need to wait for the released version of 5.5-2 or is there an
acceptable work around ?
Ray
|
| 536.22 | USER ERROR | STAR::GAGNE | David Gagne - VMS/LAN Development | Tue Oct 27 1992 10:45 | 14 |
| The Invalid media address error occurs when there is another node on
your LAN with the same address.
The solution is to determine which of the two nodes is supposed be
using that address and take a sledge hammer to the other machine.
Note that (in general) large machines are still using the network (and
their address) even though they may be halted. The large machines
should be INITIALIZED after being halted so that the network adapter
stops using the LAN.
You may want to have your local network people work on locating the
other node - only after you verify that you are using the correct
address and that you aren't the person with the "other" node.
|
| 536.23 | Could it be something else ??? | VICKI::DODIER | Food for thought makes me hungry | Tue Oct 27 1992 12:22 | 5 |
| The system that I'm using has two ethernet devices (ISA-0 and
FZA-0). The ISA-0 line and circuit come up fine on this system. Could it
be that one is somehow interfering with the other ?
Ray
|
| 536.24 | | STAR::GAGNE | David Gagne - VMS/LAN Development | Tue Oct 27 1992 15:03 | 8 |
| The two lines WILL interfere with each other if they are on the same
extended LAN and if they are both trying to use the same address. They
will both try to use the same address if you are trying to run DECnet
Phase IV (and usually Phase V) on both.
A "system" with two LAN connections is two "nodes" in the eyes of the
LAN. Each LAN connection is a different node and MUST have a unique
address on that extended LAN.
|
| 536.25 | Still broke | VICKI::DODIER | Food for thought makes me hungry | Tue Oct 27 1992 15:42 | 10 |
| I have other Phase 4 nodes that have multiple ethernet devices and
do not have this problem. I gave it a try anyway, by setting the line
and circuit for ISA-0 off and trying to turn the FZA-0 line on, only to
get the same failure.
When I use the work around mentioned earlier, I can get both lines
up at the same time. I also checked to make sure the the cost of each
of the lines was different, and it was.
Ray
|
| 536.26 | | CSC32::B_GOODWIN | Time is an illusion... | Tue Oct 27 1992 16:06 | 11 |
| > I have other Phase 4 nodes that have multiple ethernet devices and
> do not have this problem.
What version of VMS, pre VMS 5-4.3 did not have the DAT test.
> I gave it a try anyway, by setting the line
> and circuit for ISA-0 off and trying to turn the FZA-0 line on, only to
> get the same failure.
You may have to "CLEAR" the line and circuit also. The controllers will still
answer up with the address even though they have been turned off.
|
| 536.27 | Why this system and not others ??? | VICKI::DODIER | Food for thought makes me hungry | Tue Oct 27 1992 17:21 | 15 |
| The version of VMS is 5.5-2HW. I will try this again and
clear/purge the other line, and try to set FZA-0's line and circuit to
an on state.
What, if anything, is unique about this system (other than maybe
the DEFZA-CA). The system is configured as a router. Shouldn't a system
configured as a router be able to set-up and use two ethernet devices
in the same system ?
I just looked through about 2 dozen seemingly related notes in the
DECNETVAX notes file and it seemed that two ethernet devices should work
on a system configured as a router. I saw nothing indicating that this
problem has occured on other systems. Why this one ?
Ray
|
| 536.28 | Another work around ??? | VICKI::DODIER | Food for thought makes me hungry | Tue Oct 27 1992 18:11 | 20 |
| Here's more weirdness. I set the circuit and line for ISA-0 off and
then cleared/purged the line and circuit. I then tried to set the FZA-0
line to an "on" state and got the same error.
I rebooted the system and it came up with FZA-0's line and circuit
in an on state and a NCP> show known circuit showed it had connections
to the various systems that it could see.
I then set ISA-0's line and circuit on and it came up and also
established a connection to the same systems seen by FZA-0. It did this
without any sort of error.
It's almost beginning to sound like the DEFZA-CA has some problems
operating under VMS 5.5-2HW. Anyone have another answer ? Should I QAR
this at this point ? I don't have an SPD for 5.5-2HW so I can't verify
if this is supposed to work. The release notes talk about the
turbochannel, but not the DEFZA-CA specifically.
Ray
|
| 536.29 | | STAR::GAGNE | David Gagne - VMS/LAN Development | Wed Oct 28 1992 10:02 | 8 |
| Can you post the output from SDA>SHO LAN/FULL before and after you have
the problem? This will provide more information.
As a router, multiple LAN connections are allowed - BUT they MUST be on
different extended LANs.
If you have a network person there, can you ask for their assistance so
that this may be solved quicker?
|
| 536.30 | SDA> SHOW LAN/FULL info (working) | VICKI::DODIER | Food for thought makes me hungry | Wed Oct 28 1992 11:14 | 572 |
| David,
I don't have anyone available to me that can help me at this level.
I myself have gone beyond my very limited understanding of network
management and there doesn't appear to be anything in the VMS Network
Management guide that packages the info I need to be able to help
myself in the area of setting up multiple ethernet devices on a single
system.
Currently, the system has both circuits and lines up simultaneously.
I cleared and purged the info for ISA-0 and booted the system. FZA-0 came
up fine. I then set ISA-0's line and circuit to an on state. I captured
the SDA> SHOW LAN/FULL info for this state and put it below. I will define
ISA-0's line/circuit to "on" and do a reboot and give you the SDA> SHOW
LAN/FULL info for that in the next note.
Thanks for everything so far.........Ray
LAN Data Structures
-------------------
-- LAN Information Summary 28-OCT-1992 10:09:27 --
LAN flags: 0002 LAN_init
LAN module version 1 First SVAPTE 84C4E234
LAN address 80AAE490 Number of PTEs 4
Number of stations 2 SVA of pages 804C1A00
First LSB address 80AAE810
-- LAN CSMACD Network Management 28-OCT-1992 10:09:27 --
Creation time None Times created 0
Deletion time None Times deleted 0
Module EAB 00000000 Latest EIB 00000000
Port EAB 00000000
Station EAB 00000000
-- LAN FDDI Network Management 28-OCT-1992 10:09:27 --
Creation time None Times created 0
Deletion time None Times deleted 0
Module EAB 00000000 Latest EIB 00000000
Port EAB 00000000
Station EAB 00000000
Link EAB 00000000
PHY port EAB 00000000
-- EZA Device Information 28-OCT-1992 10:37:48 --
LSB address 80AAE810 Active unit count 4
LAN version A4000001 05052025 Driver version 00000001 05052012
LAN code address 80B4AF21 Driver code address 80B491C0
Device name EZ_SGEC Device type 35
Device version 00000000 00000000 DLL type CSMACD
Data chaining ON All multicast state OFF
Controller mode NORMAL Promiscuous mode OFF
CRC generation mode ON Hardware mode 0000
Physical address AA-00-04-00-40-9D Hardware address 08-00-2B-2A-DB-7F
Flags: 0000 Characteristics: 0000
Status: 0013 Inited,Run,Timer
DAT stage 00000000 DAT xmt status 0000001A 001A0001
DAT number started 2 DAT xmt complete 27-OCT 17:53:11
DAT number failed 0 DAT rcv found None
-- EZA Device Information (cont) 28-OCT-1992 10:37:48 --
Creation time None Create count 0
Deletion time None Enable count 0
Enabled time None Fatal error count 0
Disabled time None Excessive collisons 0
Last receive 28-OCT 10:37:48 Last fatal error None
Last transmit 28-OCT 10:37:48 Prev fatal error None
Last fork sched 28-OCT 10:37:48 Last exc collision None
Last fork time 28-OCT 10:37:48
Rcv buffers owned by device 16 System buffer quota 0
Xmt entries owned by device 0 Device dependent longword 00000000
Xmt entries owned by host 0 # restarts pending 0
NMgmt advised buffer count 0 Events logged 0
EIB address 00000000 NMgmt assigned adr 00-00-00-00-00-00
LPB address 00000000
-- EZA Queue Information 28-OCT-1992 10:37:48 --
Control hold queue 80AAE920 Status: Valid, empty
Control request queue 80AAE928 Status: Valid, empty
Control pending queue 80AAE930 Status: Valid, empty
Transmit request queue 80AAE918 Status: Valid, empty
Transmit pending queue 80AAE938 Status: Valid, empty
Receive buffer queue 80AAE940 Status: Valid, empty
Receive pending queue 80AAE948 Status: Valid, 16 elements
Post process queue 80AAE950 Status: Valid, empty
Delay queue 80AAE958 Status: Valid, empty
Auto restart queue 80AAE960 Status: Valid, empty
Netwrk mgmt hold queue 80AAE968 Status: Valid, empty
-- EZA Multicast Address Information 28-OCT-1992 10:37:48 --
AB-00-04-01-31-F8
09-00-2B-00-00-0F
09-00-2B-02-01-04
09-00-2B-02-01-07
AB-00-00-03-00-00
09-00-2B-04-00-00
-- EZA Unit Summary 28-OCT-1992 10:39:31 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EZA0 80AAD7B0
EZA1 80AB2700 Eth 60-07 SCA 0017 Strtn,Len,Uniq,Strtd
EZA4 80B04A80 Eth 60-04 LAT 0015 Strtn,Uniq,Strtd
EZA5 80AF7910 Eth 60-03 DECNET 0017 Strtn,Len,Uniq,Strtd
EZA7 80AFD6C0 Eth 80-41 LAST 0015 Strtn,Uniq,Strtd
-- EZA Counters Information 28-OCT-1992 10:39:31 --
Seconds since zeroed 60893 Station failures 0
Octets received 78712679 Octets sent 11946643
PDUs received 454039 PDUs sent 85509
Mcast octets received 69579205 Mcast octets sent 3740071
Mcast PDUs received 418806 Mcast PDUs sent 26340
Unrec indiv dest PDUs 3 PDUs sent, deferred 1509
Unrec mcast dest PDUs 1 PDUs sent, one coll 490
Data overruns 0 PDUs sent, mul coll 857
Unavail station buffs 0 Excessive collisions 0
Unavail user buffers 0 Carrier check failure 0
Frame check errors 0 Short circuit failure 0
Alignment errors 0 Open circuit failure 0
Frames too long 0 Transmits too long 0
Rcv data length error 0 Late collisions 0
802E PDUs received 0 Coll detect chk fail 0
802 PDUs received 0 Send data length err 0
Eth PDUs received 454039 Frame size errors 0
-- EZA Internal Counters Information 28-OCT-1992 10:39:31 --
Internal counters address 80AAF5EB Internal counters size 28
Number of ports 0 Global page transmits 0
No work transmits 1719 SVAPTE/BOFF transmits 0
Bad PTE transmits 0 Buffer_Adr transmits 0
Fatal error count 0 RDL errors 0
Transmit timeouts 0 Last fatal error None
Restart failures 0 Prev fatal error None
Power failures 0 Last error CSR 00000000
Hardware errors 0 Fatal error code None
Control timeouts 0 Prev fatal error None
Loopback sent 0 Loopback failures 0
System ID sent 99 System ID failures 0
ReqCounters sent 0 ReqCounters failures 0
-- EZA0 Template Unit Information 28-OCT-1992 10:40:34 --
LSB address 80AAE810 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1500 Eth protocol type 00-00
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 0
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address FF-FF-FF-FF-FF-FF
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 00000000 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA1 60-07 (SCA) Unit Information 28-OCT-1992 10:40:58 --
LSB address 80AAE810 VCIB address 80E77500
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1498 Eth protocol type 60-07
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 16
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode ON Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 007341B3 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA1 60-07 (SCA) Counters & Misc Info 28-OCT-1992 10:40:58 --
Last receive 28-OCT 10:40:58 Last transmit 28-OCT 10:40:57
Octets received 17735289 Octets sent 11331568
PDUs received 112825 PDUs sent 75609
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 17:42:56 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AB28C4 Status: Valid, empty
Shared users queue 80AB28B4 Status: Valid, empty
Receive pending queue 80AB28BC Status: Valid, empty
-- EZA1 60-07 (SCA) Multicast Address Info 28-OCT-1992 10:40:58 --
Multicast address table, embedded:
AB-00-04-01-31-F8
-- EZA4 60-04 (LAT) Unit Information 28-OCT-1992 10:41:47 --
LSB address 80AAE810 VCIB address 80EB7700
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1500 Eth protocol type 60-04
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 14
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode OFF Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 007341B1 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA4 60-04 (LAT) Counters & Misc Info 28-OCT-1992 10:41:47 --
Last receive 28-OCT 10:41:47 Last transmit 28-OCT 10:41:47
Octets received 9348100 Octets sent 193646
PDUs received 87073 PDUs sent 2388
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 17:44:07 Last start failed None
Share UCB total quota 0
Receive IRP queue 80B04C44 Status: Valid, empty
Shared users queue 80B04C34 Status: Valid, empty
Receive pending queue 80B04C3C Status: Valid, empty
-- EZA4 60-04 (LAT) Multicast Address Info 28-OCT-1992 10:41:47 --
Multicast address table, embedded:
09-00-2B-00-00-0F
09-00-2B-02-01-04
09-00-2B-02-01-07
-- EZA5 60-03 (DECNET) Unit Information 28-OCT-1992 10:43:07 --
LSB address 80AAE810 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1498 Eth protocol type 60-03
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 14992 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 16
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 10
P2 parameters 00374395 Starter's PID 00010011
All multicast mode OFF Creator's PID 00010011
Rcv buffer quota 14992 LSB size 5449
-- EZA5 60-03 (DECNET) Counters & Misc Info 28-OCT-1992 10:43:07 --
Last receive None Last transmit 28-OCT 10:43:06
Octets received 49382707 Octets sent 1385673
PDUs received 253331 PDUs sent 4905
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 17:53:12 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AF7AD4 Status: Valid, 1 element
Shared users queue 80AF7AC4 Status: Valid, empty
Receive pending queue 80AF7ACC Status: Valid, empty
-- EZA5 60-03 (DECNET) Multicast Address Info 28-OCT-1992 10:43:07 --
Multicast address table, embedded:
AB-00-00-03-00-00
-- EZA7 80-41 (LAST) Unit Information 28-OCT-1992 10:46:18 --
LSB address 80AAE810 VCIB address 80AF7763
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1500 Eth protocol type 80-41
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 14
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode OFF Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 007243B0 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA7 80-41 (LAST) Counters & Misc Info 28-OCT-1992 10:46:18 --
Last receive 28-OCT 10:46:06 Last transmit 28-OCT 10:46:06
Octets received 330738 Octets sent 283766
PDUs received 3291 PDUs sent 2932
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 18:06:41 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AFD884 Status: Valid, empty
Shared users queue 80AFD874 Status: Valid, empty
Receive pending queue 80AFD87C Status: Valid, empty
-- EZA7 80-41 (LAST) Multicast Address Info 28-OCT-1992 10:46:18 --
Multicast address table, embedded:
09-00-2B-04-00-00
-- FCA Device Information 28-OCT-1992 10:47:04 --
LSB address 80AD5130 Active unit count 2
LAN version A4000001 05052025 Driver version 00000001 05052007
LAN code address 80ACF1D7 Driver code address 80ACCEA8
Device name FC_DEFZA Device type 48
Device version 00000000 00000000 DLL type FDDI
Data chaining ON All multicast state OFF
Controller mode NORMAL Promiscuous mode OFF
CRC generation mode ON Hardware mode 0000
Physical address 08-00-2B-27-E2-E0 Hardware address 08-00-2B-27-E2-E0
Flags: 0000 Characteristics: 0001 Devctr
Status: 4013 Inited,Run,Timer
DAT stage 00000000 DAT xmt status 00000024 00240001
DAT number started 2 DAT xmt complete 27-OCT 17:43:57
DAT number failed 0 DAT rcv found None
-- FCA Device Information (cont) 28-OCT-1992 10:47:04 --
Creation time None Create count 0
Deletion time None Enable count 0
Enabled time None Fatal error count 0
Disabled time None Excessive collisons 0
Last receive 28-OCT 10:47:04 Last fatal error None
Last transmit 28-OCT 10:47:02 Prev fatal error None
Last fork sched 28-OCT 10:47:04 Last exc collision None
Last fork time 28-OCT 10:47:04
Rcv buffers owned by device 32 System buffer quota 0
Xmt entries owned by device 0 Device dependent longword 00000000
Xmt entries owned by host 0 # restarts pending 0
NMgmt advised buffer count 0 Events logged 0
EIB address 00000000 NMgmt assigned adr 00-00-00-00-00-00
LPB address 00000000
-- FCA Queue Information 28-OCT-1992 10:47:04 --
Control hold queue 80AD5240 Status: Valid, empty
Control request queue 80AD5248 Status: Valid, empty
Control pending queue 80AD5250 Status: Valid, empty
Transmit request queue 80AD5238 Status: Valid, empty
Transmit pending queue 80AD5258 Status: Valid, empty
Receive buffer queue 80AD5260 Status: Valid, 1 element
Receive pending queue 80AD5268 Status: Valid, 32 elements
Post process queue 80AD5270 Status: Valid, empty
Delay queue 80AD5278 Status: Valid, empty
Auto restart queue 80AD5280 Status: Valid, empty
Netwrk mgmt hold queue 80AD5288 Status: Valid, empty
-- FCA Multicast Address Information 28-OCT-1992 10:47:04 --
AB-00-04-01-31-F8
AB-00-00-03-00-00
-- FCA FDDI Information 28-OCT-1992 10:47:04 --
Data link arch version 00000000 Module serial num 00000000
Max token rotation time 2162688 Module serial num 00000000
Negotiated TRT 0 Module serial num 00000000
Valid transmission time 32762 Upstream neighbor 00-00-00-00-00-00
LEM threshold 8 Phy state 0
Port type 0 Link state 0
DAT results 0 Ring purger state 0
FDDI flags: 0000
-- FCA Unit Summary 28-OCT-1992 10:48:32 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
FCA0 80AD4E70
FCA1 80AD7330 Eth 60-07 SCA 0017 Strtn,Len,Uniq,Strtd
FCA2 80B31880 Eth 60-03 DECNET 0017 Strtn,Len,Uniq,Strtd
-- FCA Counters Information 28-OCT-1992 10:48:50 --
Seconds since zeroed 61430 Station failures 0
Octets received 83012503 Octets sent 8030605
PDUs received 365223 PDUs sent 58623
Mcast octets received 66853875 Mcast octets sent 4177569
Mcast PDUs received 331594 Mcast PDUs sent 25450
Unrec indiv dest PDUs 178 PDUs sent, deferred 0
Unrec mcast dest PDUs 3 PDUs sent, one coll 0
Data overruns 0 PDUs sent, mul coll 0
Unavail station buffs 0 Excessive collisions 0
Unavail user buffers 0 Carrier check failure 0
Frame check errors 0 Short circuit failure 0
Alignment errors 0 Open circuit failure 0
Frames too long 0 Transmits too long 0
Rcv data length error 0 Late collisions 0
802E PDUs received 0 Coll detect chk fail 0
802 PDUs received 0 Send data length err 0
Eth PDUs received 334716 Frame size errors 0
-- FCA FDDI Counters Information 28-OCT-1992 10:48:50 --
Transmit underrun 0 Dup tokens detected 0
Transmit failure 0 Ring purge errors 0
Frame status error 0 FCI strip errors 0
Frame length error 0 Traces initiated 0
MAC frame count 0 Traces received 0
MAC error count 0 Directed beacons rcvd 0
MAC lost count 0 Elasticity buffer err 0
Ring inits initiated 0 LCT rejects 0
Ring inits received 0 LEM rejects 0
Ring beacon initiated 0 Link errors 0
Dup add test failures 0 Connections completed 0
-- FCA Internal Counters Information 28-OCT-1992 10:48:50 --
Internal counters address 80AD5974 Internal counters size 36
Number of ports 0 Global page transmits 0
No work transmits 466 SVAPTE/BOFF transmits 880
Bad PTE transmits 0 Buffer_Adr transmits 0
Fatal error count 0 RDL errors 0
Transmit timeouts 0 Last fatal error None
Restart failures 0 Prev fatal error None
Power failures 0 Last error CSR 00000000
Hardware errors 0 Fatal error code None
Control timeouts 0 Prev fatal error None
Loopback sent 2 Loopback failures 0
System ID sent 0 System ID failures 0
ReqCounters sent 0 ReqCounters failures 0
-- FCA0 Template Unit Information 28-OCT-1992 10:49:47 --
LSB address 80AD5130 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium FDDI
Maximum buffer size 1500 Eth protocol type 00-00
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 0
802.2 service OFF Hardware address 08-00-2B-27-E2-E0
Data chaining OFF Physical address 08-00-2B-27-E2-E0
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 00000000 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 3222
-- FCA1 60-07 (SCA) Unit Information 28-OCT-1992 10:50:07 --
LSB address 80AD5130 VCIB address 80E6E400
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium FDDI
Maximum buffer size 4468 Eth protocol type 60-07
Hardware buffer quota 16 802E protocol ID 00-00-00-60-07
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 26
802.2 service OFF Hardware address 08-00-2B-27-E2-E0
Data chaining OFF Physical address 08-00-2B-27-E2-E0
Padding mode ON Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 0C7341B3 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 3222
-- FCA1 60-07 (SCA) Counters & Misc Info 28-OCT-1992 10:50:07 --
Last receive 28-OCT 10:50:07 Last transmit 28-OCT 10:50:05
Octets received 21510062 Octets sent 5346583
PDUs received 82961 PDUs sent 35481
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 17:43:27 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AD74F4 Status: Valid, empty
Shared users queue 80AD74E4 Status: Valid, empty
Receive pending queue 80AD74EC Status: Valid, empty
-- FCA1 60-07 (SCA) Multicast Address Info 28-OCT-1992 10:50:07 --
Multicast address table, embedded:
AB-00-04-01-31-F8
-- FCA2 60-03 (DECNET) Unit Information 28-OCT-1992 10:51:04 --
LSB address 80AD5130 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium FDDI
Maximum buffer size 4468 Eth protocol type 60-03
Hardware buffer quota 16 802E protocol ID 00-00-00-60-03
Receive buffer quota 14992 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 26
802.2 service OFF Hardware address 08-00-2B-27-E2-E0
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 10
P2 parameters 00374395 Starter's PID 00010011
All multicast mode OFF Creator's PID 00010011
Rcv buffer quota 14992 LSB size 3222
-- FCA2 60-03 (DECNET) Counters & Misc Info 28-OCT-1992 10:51:04 --
Last receive None Last transmit 28-OCT 10:51:01
Octets received 48964183 Octets sent 1433301
PDUs received 252714 PDUs sent 4995
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 27-OCT 17:43:59 Last start failed None
Share UCB total quota 0
Receive IRP queue 80B31A44 Status: Valid, 1 element
Shared users queue 80B31A34 Status: Valid, empty
Receive pending queue 80B31A3C Status: Valid, empty
-- FCA2 60-03 (DECNET) Multicast Address Info 28-OCT-1992 10:51:04 --
Multicast address table, embedded:
AB-00-00-03-00-00
|
| 536.31 | SDA> SHOW LAN/FULL info (not working) | VICKI::DODIER | Food for thought makes me hungry | Wed Oct 28 1992 12:13 | 483 |
| I made a couple observations that may help. When I did a SHOW KNOWN
CIRCUIT in the previous working state, both circuits had a cost of 10.
By default, NETCONFIG wants to set ISA-0 to a cost of 4 and FZA-0 to a
cost of 5. When setting a circuit on without specifying the cost,
evidently 10 is the default.
Because of the known 5.5-2HW bug (i.e. line/circuit have incorrect
mnemonic - FZA-0-0 vs FZA-0), I had to purge the FZA line/circuit info
and then manually DEFINE the circuit and line to an on state. The
following SDA> SHOW LAN/FULL info is from after rebooting the system
with FZA-0's line/circuit defined to an "on" state.
LAN Data Structures
-------------------
-- LAN Information Summary 28-OCT-1992 11:44:31 --
LAN flags: 0002 LAN_init
LAN module version 1 First SVAPTE 84C4E234
LAN address 80AAE490 Number of PTEs 4
Number of stations 2 SVA of pages 804C1A00
First LSB address 80AAE810
-- LAN CSMACD Network Management 28-OCT-1992 11:44:31 --
Creation time None Times created 0
Deletion time None Times deleted 0
Module EAB 00000000 Latest EIB 00000000
Port EAB 00000000
Station EAB 00000000
-- LAN FDDI Network Management 28-OCT-1992 11:44:31 --
Creation time None Times created 0
Deletion time None Times deleted 0
Module EAB 00000000 Latest EIB 00000000
Port EAB 00000000
Station EAB 00000000
Link EAB 00000000
PHY port EAB 00000000
-- EZA Device Information 28-OCT-1992 11:54:24 --
LSB address 80AAE810 Active unit count 3
LAN version A4000001 05052025 Driver version 00000001 05052012
LAN code address 80B4AF21 Driver code address 80B491C0
Device name EZ_SGEC Device type 35
Device version 00000000 00000000 DLL type CSMACD
Data chaining ON All multicast state OFF
Controller mode NORMAL Promiscuous mode OFF
CRC generation mode ON Hardware mode 0000
Physical address AA-00-04-00-40-9D Hardware address 08-00-2B-2A-DB-7F
Flags: 0000 Characteristics: 0000
Status: 0013 Inited,Run,Timer
DAT stage 00000000 DAT xmt status 0000001A 001A0001
DAT number started 2 DAT xmt complete 28-OCT 11:38:25
DAT number failed 0 DAT rcv found None
-- EZA Device Information (cont) 28-OCT-1992 11:54:24 --
Creation time None Create count 0
Deletion time None Enable count 0
Enabled time None Fatal error count 0
Disabled time None Excessive collisons 0
Last receive 28-OCT 11:54:24 Last fatal error None
Last transmit 28-OCT 11:54:24 Prev fatal error None
Last fork sched 28-OCT 11:54:24 Last exc collision None
Last fork time 28-OCT 11:54:24
Rcv buffers owned by device 16 System buffer quota 0
Xmt entries owned by device 0 Device dependent longword 00000000
Xmt entries owned by host 0 # restarts pending 0
NMgmt advised buffer count 0 Events logged 0
EIB address 00000000 NMgmt assigned adr 00-00-00-00-00-00
LPB address 00000000
-- EZA Queue Information 28-OCT-1992 11:54:24 --
Control hold queue 80AAE920 Status: Valid, empty
Control request queue 80AAE928 Status: Valid, empty
Control pending queue 80AAE930 Status: Valid, empty
Transmit request queue 80AAE918 Status: Valid, empty
Transmit pending queue 80AAE938 Status: Valid, empty
Receive buffer queue 80AAE940 Status: Valid, empty
Receive pending queue 80AAE948 Status: Valid, 16 elements
Post process queue 80AAE950 Status: Valid, empty
Delay queue 80AAE958 Status: Valid, empty
Auto restart queue 80AAE960 Status: Valid, empty
Netwrk mgmt hold queue 80AAE968 Status: Valid, empty
-- EZA Multicast Address Information 28-OCT-1992 11:54:24 --
AB-00-04-01-31-F8
AB-00-00-03-00-00
09-00-2B-00-00-0F
09-00-2B-02-01-04
09-00-2B-02-01-07
-- EZA Unit Summary 28-OCT-1992 11:55:51 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
EZA0 80AAD7B0
EZA1 80AB2700 Eth 60-07 SCA 0017 Strtn,Len,Uniq,Strtd
EZA4 80B31C60 Eth 60-03 DECNET 0017 Strtn,Len,Uniq,Strtd
EZA5 80B44950 Eth 60-04 LAT 0015 Strtn,Uniq,Strtd
-- EZA Counters Information 28-OCT-1992 11:55:51 --
Seconds since zeroed 1020 Station failures 0
Octets received 8606382 Octets sent 767161
PDUs received 16265 PDUs sent 6432
Mcast octets received 1091808 Mcast octets sent 66371
Mcast PDUs received 6458 Mcast PDUs sent 440
Unrec indiv dest PDUs 3 PDUs sent, deferred 83
Unrec mcast dest PDUs 3 PDUs sent, one coll 73
Data overruns 0 PDUs sent, mul coll 98
Unavail station buffs 0 Excessive collisions 0
Unavail user buffers 0 Carrier check failure 0
Frame check errors 0 Short circuit failure 0
Alignment errors 0 Open circuit failure 0
Frames too long 0 Transmits too long 0
Rcv data length error 0 Late collisions 0
802E PDUs received 0 Coll detect chk fail 0
802 PDUs received 0 Send data length err 0
Eth PDUs received 16264 Frame size errors 0
-- EZA Internal Counters Information 28-OCT-1992 11:55:51 --
Internal counters address 80AAF5EB Internal counters size 28
Number of ports 0 Global page transmits 0
No work transmits 48 SVAPTE/BOFF transmits 0
Bad PTE transmits 0 Buffer_Adr transmits 0
Fatal error count 0 RDL errors 0
Transmit timeouts 0 Last fatal error None
Restart failures 0 Prev fatal error None
Power failures 0 Last error CSR 00000000
Hardware errors 0 Fatal error code None
Control timeouts 0 Prev fatal error None
Loopback sent 1 Loopback failures 0
System ID sent 2 System ID failures 0
ReqCounters sent 0 ReqCounters failures 0
-- EZA0 Template Unit Information 28-OCT-1992 11:56:32 --
LSB address 80AAE810 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1500 Eth protocol type 00-00
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 0
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address FF-FF-FF-FF-FF-FF
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 00000000 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA1 60-07 (SCA) Unit Information 28-OCT-1992 11:56:50 --
LSB address 80AAE810 VCIB address 80E77500
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1498 Eth protocol type 60-07
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 16
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode ON Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 007341B3 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-------------------
-- EZA1 60-07 (SCA) Counters & Misc Info 28-OCT-1992 11:56:50 --
Last receive 28-OCT 11:56:50 Last transmit 28-OCT 11:56:49
Octets received 7659493 Octets sent 841258
PDUs received 11225 PDUs sent 6304
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 28-OCT 11:37:24 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AB28C4 Status: Valid, empty
Shared users queue 80AB28B4 Status: Valid, empty
Receive pending queue 80AB28BC Status: Valid, empty
-- EZA1 60-07 (SCA) Multicast Address Info 28-OCT-1992 11:56:50 --
Multicast address table, embedded:
AB-00-04-01-31-F8
-- EZA4 60-03 (DECNET) Unit Information 28-OCT-1992 11:57:38 --
LSB address 80AAE810 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1498 Eth protocol type 60-03
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 14992 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 16
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 10
P2 parameters 00374395 Starter's PID 00010011
All multicast mode OFF Creator's PID 00010011
Rcv buffer quota 14992 LSB size 5449
-- EZA4 60-03 (DECNET) Counters & Misc Info 28-OCT-1992 11:57:38 --
Last receive None Last transmit 28-OCT 11:57:29
Octets received 924884 Octets sent 30880
PDUs received 4667 PDUs sent 96
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 28-OCT 11:38:26 Last start failed None
Share UCB total quota 0
Receive IRP queue 80B31E24 Status: Valid, 1 element
Shared users queue 80B31E14 Status: Valid, empty
Receive pending queue 80B31E1C Status: Valid, empty
-- EZA4 60-03 (DECNET) Multicast Address Info 28-OCT-1992 11:57:38 --
Multicast address table, embedded:
AB-00-00-03-00-00
-- EZA5 60-04 (LAT) Unit Information 28-OCT-1992 11:58:24 --
LSB address 80AAE810 VCIB address 80ED0930
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium CSMACD
Maximum buffer size 1500 Eth protocol type 60-04
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 14
802.2 service OFF Hardware address 08-00-2B-2A-DB-7F
Data chaining OFF Physical address AA-00-04-00-40-9D
Padding mode OFF Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 007341B1 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 5449
-- EZA5 60-04 (LAT) Counters & Misc Info 28-OCT-1992 11:58:24 --
Last receive 28-OCT 11:58:24 Last transmit 28-OCT 11:58:24
Octets received 176713 Octets sent 26660
PDUs received 1813 PDUs sent 377
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 28-OCT 11:38:35 Last start failed None
Share UCB total quota 0
Receive IRP queue 80B44B14 Status: Valid, empty
Shared users queue 80B44B04 Status: Valid, empty
Receive pending queue 80B44B0C Status: Valid, empty
-- EZA5 60-04 (LAT) Multicast Address Info 28-OCT-1992 11:58:24 --
Multicast address table, embedded:
09-00-2B-00-00-0F
09-00-2B-02-01-04
09-00-2B-02-01-07
-- FCA Device Information 28-OCT-1992 11:59:32 --
LSB address 80AD4EE0 Active unit count 1
LAN version A4000001 05052025 Driver version 00000001 05052007
LAN code address 80ACEF87 Driver code address 80ACCC58
Device name FC_DEFZA Device type 48
Device version 00000000 00000000 DLL type FDDI
Data chaining ON All multicast state OFF
Controller mode NORMAL Promiscuous mode OFF
CRC generation mode ON Hardware mode 0000
Physical address 08-00-2B-27-E2-E0 Hardware address 08-00-2B-27-E2-E0
Flags: 0000 Characteristics: 0001 Devctr
Status: 4013 Inited,Run,Timer
DAT stage 00000000 DAT xmt status 00000024 00240001
DAT number started 2 DAT xmt complete 28-OCT 11:38:26
DAT number failed 0 DAT rcv found 28-OCT 11:38:26
-- FCA Device Information (cont) 28-OCT-1992 11:59:32 --
Creation time None Create count 0
Deletion time None Enable count 0
Enabled time None Fatal error count 0
Disabled time None Excessive collisons 0
Last receive 28-OCT 11:59:31 Last fatal error None
Last transmit 28-OCT 11:59:30 Prev fatal error None
Last fork sched 28-OCT 11:59:31 Last exc collision None
Last fork time 28-OCT 11:59:31
Rcv buffers owned by device 32 System buffer quota 0
Xmt entries owned by device 0 Device dependent longword 00000000
Xmt entries owned by host 0 # restarts pending 0
NMgmt advised buffer count 0 Events logged 0
EIB address 00000000 NMgmt assigned adr 00-00-00-00-00-00
LPB address 00000000
-- FCA Queue Information 28-OCT-1992 11:59:32 --
Control hold queue 80AD4FF0 Status: Valid, empty
Control request queue 80AD4FF8 Status: Valid, empty
Control pending queue 80AD5000 Status: Valid, empty
Transmit request queue 80AD4FE8 Status: Valid, empty
Transmit pending queue 80AD5008 Status: Valid, empty
Receive buffer queue 80AD5010 Status: Valid, empty
Receive pending queue 80AD5018 Status: Valid, 32 elements
Post process queue 80AD5020 Status: Valid, empty
Delay queue 80AD5028 Status: Valid, empty
Auto restart queue 80AD5030 Status: Valid, empty
Netwrk mgmt hold queue 80AD5038 Status: Valid, empty
-- FCA Multicast Address Information 28-OCT-1992 11:59:32 --
AB-00-04-01-31-F8
-- FCA FDDI Information 28-OCT-1992 11:59:32 --
Data link arch version 00000000 Module serial num 00000000
Max token rotation time 2162688 Module serial num 00000000
Negotiated TRT 0 Module serial num 00000000
Valid transmission time 32768 Upstream neighbor 00-00-00-00-00-00
LEM threshold 8 Phy state 0
Port type 0 Link state 0
DAT results 0 Ring purger state 0
FDDI flags: 0000
-- FCA Unit Summary 28-OCT-1992 12:00:51 --
UCB UCB Addr Fmt Value Client State
--- -------- --- ----- ------ -----------
FCA0 80AD4C20
FCA1 80AD70E0 Eth 60-07 SCA 0017 Strtn,Len,Uniq,Strtd
-- FCA Counters Information 28-OCT-1992 12:01:09 --
Seconds since zeroed 1310 Station failures 0
Octets received 5359791 Octets sent 1900603
PDUs received 8742 PDUs sent 13865
Mcast octets received 264992 Mcast octets sent 58455
Mcast PDUs received 2116 Mcast PDUs sent 433
Unrec indiv dest PDUs 0 PDUs sent, deferred 0
Unrec mcast dest PDUs 1 PDUs sent, one coll 0
Data overruns 0 PDUs sent, mul coll 0
Unavail station buffs 0 Excessive collisions 0
Unavail user buffers 0 Carrier check failure 0
Frame check errors 0 Short circuit failure 0
Alignment errors 0 Open circuit failure 0
Frames too long 0 Transmits too long 0
Rcv data length error 0 Late collisions 0
802E PDUs received 0 Coll detect chk fail 0
802 PDUs received 0 Send data length err 0
Eth PDUs received 8093 Frame size errors 0
-- FCA FDDI Counters Information 28-OCT-1992 12:01:09 --
Transmit underrun 0 Dup tokens detected 0
Transmit failure 0 Ring purge errors 0
Frame status error 0 FCI strip errors 0
Frame length error 0 Traces initiated 0
MAC frame count 0 Traces received 0
MAC error count 0 Directed beacons rcvd 0
MAC lost count 0 Elasticity buffer err 0
Ring inits initiated 0 LCT rejects 0
Ring inits received 0 LEM rejects 0
Ring beacon initiated 0 Link errors 0
Dup add test failures 0 Connections completed 0
-- FCA Internal Counters Information 28-OCT-1992 12:01:09 --
Internal counters address 80AD5724 Internal counters size 36
Number of ports 0 Global page transmits 0
No work transmits 204 SVAPTE/BOFF transmits 294
Bad PTE transmits 0 Buffer_Adr transmits 0
Fatal error count 0 RDL errors 0
Transmit timeouts 0 Last fatal error None
Restart failures 0 Prev fatal error None
Power failures 0 Last error CSR 00000000
Hardware errors 0 Fatal error code None
Control timeouts 0 Prev fatal error None
Loopback sent 0 Loopback failures 0
System ID sent 0 System ID failures 0
ReqCounters sent 0 ReqCounters failures 0
-- FCA0 Template Unit Information 28-OCT-1992 12:02:06 --
LSB address 80AD4EE0 VCIB address 00000000
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium FDDI
Maximum buffer size 1500 Eth protocol type 00-00
Hardware buffer quota 16 802E protocol ID 00-00-00-00-00
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 0
802.2 service OFF Hardware address 08-00-2B-27-E2-E0
Data chaining OFF Physical address 08-00-2B-27-E2-E0
Padding mode ON Can change address OFF
Automatic restart OFF Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 00000000 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 3222
-- FCA1 60-07 (SCA) Unit Information 28-OCT-1992 12:02:24 --
LSB address 80AD4EE0 VCIB address 80E6E400
Packet format Ethernet Error count 0
Device buffer size 1500 LAN medium FDDI
Maximum buffer size 4468 Eth protocol type 60-07
Hardware buffer quota 16 802E protocol ID 00-00-00-60-07
Receive buffer quota 0 802.2 SAP 00
Allow prom client ON 802.2 Group SAPs 00,00,00,00
Promiscuous mode OFF Maximum header size 26
802.2 service OFF Hardware address 08-00-2B-27-E2-E0
Data chaining OFF Physical address 08-00-2B-27-E2-E0
Padding mode ON Can change address ON
Automatic restart ON Access mode EXCLUSIVE
CRC generation mode ON Controller mode NORMAL
Maintenance state ON Rcv buffs to queue 1
P2 parameters 0C7341B3 Starter's PID 00000000
All multicast mode OFF Creator's PID 00000000
Rcv buffer quota 0 LSB size 3222
-- FCA1 60-07 (SCA) Counters & Misc Info 28-OCT-1992 12:02:24 --
Last receive 28-OCT 12:02:23 Last transmit 28-OCT 12:02:21
Octets received 5179440 Octets sent 1919304
PDUs received 8473 PDUs sent 13531
Mcast octets received 0 Mcast octets sent 0
Mcast PDUs received 0 Mcast PDUs sent 0
Unavail user buffer 0 Last start attempt None
Last start done 28-OCT 11:37:55 Last start failed None
Share UCB total quota 0
Receive IRP queue 80AD72A4 Status: Valid, empty
Shared users queue 80AD7294 Status: Valid, empty
Receive pending queue 80AD729C Status: Valid, empty
-- FCA1 60-07 (SCA) Multicast Address Info 28-OCT-1992 12:02:24 --
Multicast address table, embedded:
AB-00-04-01-31-F8
|
| 536.32 | The learn as you burn method | VICKI::DODIER | Food for thought makes me hungry | Wed Nov 04 1992 17:41 | 22 |
| After doing some investigating, I found that two ethernet
controllers running DECnet, on one system, and connected to the same
segment is an illegal configuration.
The actual configuration rule is -
When two or more Ethernet, FDDI, or 802.5/Token Ring controllers are
used on a single CPU, each controller must be connected to a different
Ethernet, FDDI, or 802.5/Token Ring cable. These cables must not be
joined by a bridge or a repeater, though they may be joined by another
DECnet router.
This info came from the DECnet 5.5 SPD. I'm sort of surprised that
this info wasn't in the VMS Networking Guide. I guess that explains
some of the dozen or so entries in the DECNETVAX notes file asking the
same basic question.
Trying to find out why it works one way and not the other is a moot
point now. Thanks to those that tried to help, and hopefully someone
else may see this note and learn from my mistakes. I certainly did.
Ray
|
| 536.33 | | KONING::KONING | Paul Koning, A-13683 | Thu Nov 05 1992 12:14 | 18 |
| That's almost right, but the actual rule is somewhat less restrictive:
"When two or more Ethernet or FDDI controllers are
used on a single CPU, AND PHASE IV DECNET IS ENABLED ON ALL OF THEM,
each controller must ..."
Adapters not running DECnet are exempt. I believe the rule doesn't apply
to token ring adapters, since those don't use the Phase IV HiOrd prefix.
And finally, the rule does not apply when you're running Phase V AND you
have the "Enable PhaseIV Address" attribute set to "disabled" on the
circuit.
The reason for all of these is the same: what gets you in trouble is the
DECnet Phase IV style datalink address (AA-00-04-00...); there are various
reasons why that address might NOT be enabled on a controller, and if it
isn't, then that controller will not give you any trouble.
paul
|
| 536.34 | Latent frustration | VICKI::DODIER | Food for thought makes me hungry | Fri Nov 06 1992 11:09 | 21 |
| re: restrictions
>"When two or more Ethernet or FDDI controllers are used on a single CPU,
>AND PHASE IV DECNET IS ENABLED ON ALL OF THEM, each controller must ..."
This is one of the places I guess people just have to watch out.
The configuration rule that I entered was as written in the "DECnet" SPD.
Anyone looking at this MUST keep in mind that this rule is only valid
as it applies to "Phase IV DECnet".
One of the problems that results in confusion is that there doesn't
seem to be much readily available documentation that talks about "general
ethernet" configuration guidelines/rules. This is the type of information
that really should appear in the VMS Networking Guide.
We may be the "world's leader" in what we can do in the area of
networks, but we're certainly not a world leader in packaging the
documentation in a way that your average computer literate can understand
how to use all this wonderful technology.
Ray
|