| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hi,
I got a customer using a few DECHub 900 MS. 1 of the DECHub 900 MS
reset a few times recently. This is their configuration in that
particular DECHub.
Repeater Repeater Repeater Repeater DECSwitch
900TM 900TM 900TM 900TM 900EF
(slot 4) (slot 5) (slot 6) (slot 7) (slot 8)
| | | | |
Thinwire -------------------------------------x---------x----
| | | |
Flex Channel ---------------------------x-------------------x----
| | |
Flex Channel -----------------x-----------------------------x----
| |
Flex Channel -------x---------------------------------------x----
f f f ---- faulty
What I've found out is the Repeaters in slot 4, 5 & 6 on the flex
channels are not working. But the repeaters on slot 7 is still working
& the users still able to login & connect to the backbone(thru
DECSwitch 900 TM). When I go to the workstation which is connected to
repeaters which are facing problem(e.g. slot 4), I can't ping other
workstation in slot 5, 6 or 7. It seems that all the repeater connected
to the flex channels is disconnected. I couldn't startup hubwatch because
the agent was located in a faulty repeater channel.
I've copy the dump files, hope that someone can help me on this matter.
Thanks,
SMF
DECSwitch 900 EF (Slot 8)
Entry # = 0
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 11
Firmware Rev = 1.7
Reset Count = 20
Timestamp = 0 78 EF39
Write Count = 5
FRU Mask = 0
Test ID = 3D7
Error Data = SR=00002000 PC=000937B8 ErrorCode=00000003
Registers = Phy1Csr =000003D7 ElmBase =00000000 MacBase =00001830
CamCsr =0000823F CamData15_00=00000000 PmCsr =00001405
CamData31_16=00004300 CamData47_32=00008001 PortDataA =04000000
RtosTimer =00000030 RtosTimerVal=00000003 PortDataB =00000000
i68k68kInt =00000000 i68k68kMask =000001FF DmaInt =0000003F
i68kForceInt=00000000 DmaMask =00000000 HostData =00000000
HostInt0Mask=00000000 HostInt0 =000000D0 PortStatus =00000500
PortCtrlMask=00007FFF HostDmaMask =00005000 PortCtrlInt=00000000
FmcControl =0000C032 FmcStatus =0000A600 FmcInt =00000000
Dump another entry [Y]/N?
========================================================================================
DECRepeater 900TM (Slot 7)
-----(Still Working)
Entry = 9809
Time Stamp = 0 279395270
Reset Count = 13
Pool:Enet;Hog=233ACC,8;NoPC=16;Free=1
Dump another entry [Y]/N?
=================================================================================
DECRepeater 900TM (Slot 6 & 5)
-----(Connection Lost)
Entry = 9809
Time Stamp = 0 279395270
Reset Count = 13 Pool:Enet;Hog=233ACC,8;NoPC=16;Free=1
DECrepeater 900TM , 32 Port TP Ethernet Rptr SNMP, HW=v3,RO=v01.04,SW=V2.0.0
SysUpTime : 10 days 20:59:32 20 resets
SNMP Read/Write Community : public
SNMP Trap Addresses : Not Configured
Status of Last Downline Upgrade : No Status
BootP : Disabled
Interface IP Address Subnet Mask Def. Gateway Other Info
--------- ---------- ----------- ------------ ----------
Ethernet Port 129.253.145.185 255.255.0.0 129.253.144.254 00-00-F8-41-1C-84
==============================================================================
DECRepeater 900TM (Slot 4)
(Connection Lost)
Entry = 1
Time Stamp = 0 0 Reset Count = 0
Fatal error: Line 310, File pcomErrLog.c
Dump another entry y/[n]?
DECrepeater 900TM
==============================================================================
DECrepeater 900TM 32 Port TP Ethernet Rptr SNMP, HW=v3,RO=v1,SW=v1.0G
Ethernet Address : 08-00-2B-A6-24-1C
In Band interface IP Address : 129.253.145.184
In Band interface Default Gateway Address : 129.253.144.254
SNMP Read/Write Community : public
SNMP Trap Addresses : Not Available
==============================================================================
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4263.1 | Code. | KERNEL::FREKES | Like a thief in the night | Tue Mar 11 1997 11:57 | 9 |
I have noticed that the repeater in slot 4 is running an outdated
version of code. This sould cause serious problems. You should always
try to run with level versions of code on the entire hub. What version
of code are you running on the MAM?
Are the repeater port counters reporting anything other broken?
Steven F
UK CSC.
| |||||
| 4263.2 | Additional Info on DECHub 900MS | MSAM00::FOOSZEMUN | Wed Mar 12 1997 01:51 | 21 | |
Hi,
Thank for the fast reply. The DECHub 900 MS is using firmware
version 4.2.
FYI, the customer used a tool to check the LAN activity through
the DECRepeater 900TM in slot 4 which is cannot be connected to the
backbone(After the incident). She found out that there are a lot of
collisions in that DECRepeater 900TM. She didn't check other
DECRepeater in the DECHub 900MS. She used a tester
called "1 touch" from Fluke.
During that incident, all the modules in the 900MS is shown as up.
But I didn't check the repeater port counters because I can't get into
Multichasis Manager because the agent is in slot 4.
Thanks,
SMF
| |||||
| 4263.3 | Did you upgrade. Time to start moving modules!! | KERNEL::FREKES | Like a thief in the night | Wed Mar 12 1997 09:26 | 21 |
If you assign a secondary inbound IP address and assign that to the
DECswitch900EF. You will need to do this using the setup port. Once you
have made the EF an IP services module, you should be able to
connect.
What happens if the customer removes an EF connection to one of the
flex-channels, can the repeater connect then. Can they connect to ANY
of the flex-channels?
WHat happens if you remove all the repeaters, and then add them to the
hub, and connect them one at a time? ie Process of elimination.
Did you upgrade the repeater in slot 4 from
>.......HW=v3,RO=v1,SW=v1.0G
to V2.0?
I don't know what the error logs are telling us, perhaps someone else
would like to add some value here.
They may be indicating a hardware problem of some description.
Regards
Steven
| |||||
| 4263.4 | Any Tools for Error Log? | MSAM03::FOOSZEMUN | Wed Mar 12 1997 19:45 | 16 | |
Hi,
The repeater in slot 4, 5 & 6 just lost its connection to the EF. I'm
sure they didn't take out the DECRepeater because they are on production
24 hours a day for 7 days a week. Neither did a power failer occur!
Is it alright to give IP to all the modules? They are doing so.
The customer is pressing for an explanation because this is not the
first time this thing happened. Is there a way to translate the error log
or is there any tools like Canasta, the tools we used to analyze dump
file for OpenVMS & Unix?
Thanks,
SMF
| |||||
| 4263.5 | KERNEL::FREKES | Like a thief in the night | Thu Mar 13 1997 09:25 | 11 | |
>Is it alright to give IP to all the modules?
Well, yes, but what purpose is that going to serve apart from making
the other modules capable of being IP services modules.
Again, I do not know what the error logs are telling you, and I do not
know any tools to aid the decoding of the log.
Have you tried removing the EF's connection to the lans, and putting
all the repeaters on the thinwire channel? Does this make anything
better.
| |||||
| 4263.6 | Error log analysis of DECswitch 900EF.... | NETCAD::BATTERSBY | Fri Mar 14 1997 09:55 | 24 | |
I had a suspicion that the DECswitch error log was FDDI related,
and ran it by someone here at LKG who is intimately familiar
with the FDDI corner adapter firmware and got the following analysis.
-----------------------------------------
The data in this dump is consistent with an FDDI crash of:
Error Data = SR=00002000 PC=000937B8 ErrorCode=00000003
SR=00002000 IPL0 (normal)
PC=000937B8 lmgr_event_msg_task + 0x206
Cd=00000003 CNS_K_SW_FAULT
So, CNS decided to crash and sent a message and a code to the
dispatcher.
The dispatcher wrote the error log entry and crashed the corner.
Unfortunately, the "Registers" dump doesn't have the CNS error code!
-----------------------------------------
It's curious that there is no mention in the base note of any FDDI
connections nor are there any shown in the diagram in the base note.
So this error log may be a latent log un-related to the customers
current problem.
Bob
| |||||
| 4263.7 | FDDI Configuration | MSAM00::FOOSZEMUN | Fri Mar 14 1997 19:29 | 10 | |
Hi Bob,
Thank for you note. Yes, DECSwitch 900EF is connected to a FDDI
ring thru a Giga Switch. Actually, they have 2 Giga switch, 1 is for
backup.
Regards,
SMF
| |||||