T.R | Title | User | Personal Name | Date | Lines |
---|
2620.1 | | TOOK::MILLBRANDT | answer mam | Wed Aug 09 1995 12:23 | 1 |
| What management agents are you losing links to?
|
2620.2 | DH900 & Gigaswitch/fddi | PHXSS1::POWERS_BR | | Thu Aug 10 1995 01:12 | 5 |
|
sorry if I was not clear in my note, we are losing links to the
DH900's (two different backplanes), and also the Gigaswitch.
|
2620.3 | Losing IP stack as well as Gigaswitch connectivity | SLOSS1::BREINHOLT_RO | Reb Breinholt | Thu Aug 10 1995 01:33 | 9 |
| I just talked to the customer as he was having the problem. It appears
that there may be two problems. He may be losing his IP socket and he
may also have the Gigaswitch stop responding to IP/SNMP requests.
I call just as he had lost connectivity to the Gigaswitch, so I had him try pinging -
He got the error message that the Winsock was un-available. I had him
reboot so that he could ping to other devices, but the Gigaswtich was
still unavailable.
|
2620.4 | A possibly related problem in SCHOOL::GIGASWITCH | NPSS::MDLYONS | Michael D. Lyons DTN 226-6943 | Thu Aug 10 1995 11:07 | 15 |
| Check to see if your customer is doing something out of the
ordinary with IP addresses which would affect the ARP cache. For
example, check out note 544.* in the GIGAswitch notes conference, in
which a customer is using a cisco router which supports multiple IP
addresses on the same interface. This appears to be causing problems
with the ARP cache entry for the cisco router on the GIGAswitch/FDDI
system. When this system (cisco with multiple IP addresses) is used as
the default gateway on the GIGAswitch/FDDI system, communication
problems result.
For the standard list of things to check when you can't ping a
GIGAswitch/FDDI system, check out note 265.1 in the same notes
conference.
MDL
|