[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

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

4190.0. "Portswitch 900CP, FATAL ERROR & IP Service problem" by KERNEL::CHOPRAA () Tue Jan 28 1997 16:14

        Hi,
    
        I have a customer with a DEChub 900 configured with the following
        modules
            Slot 1  90 Series module ?
            Slot 2  90 Series Module ?
            Slot 6  Portswitch 900CP        V2.1.1
            Slot 7  Portswitch 900CP        V2.1.1
            Slot 8  DECSwitch 900EF         V1.6.1
            MAM Module is running           V4.2.0
    
        The PC running MCM is on a LAN segment connected to a port on the
        portswitch in slot 7.  This particular port is in group 1.
    
        The Portswitch in slot 7 has always been the IP services module.
    
        The customer has two problems.
    
        1. The customer could not fire up MCM to the hub using the portswitch
        in slot 7 as the IP services module.  If the IP services module was
        changed to the portswitch in slot 6, all worked o.k.
    
        2.  The portswitch in slot 7 has apparently reset itself with a fatal
        error.  The error log is as follows.
    
                                                                       
    PORTswitch 900CP - slot 7
    =====================================================================
                                    DUMP ERROR LOG
                                Current Reset Count: 24
    =====================================================================
    
            Entry        = 4
            Time Stamp   = 0 326501808
            Reset Count  = 23
            Fatal error: Line 888, File enet.c
    
    Dump another entry [Y]/N?
    
            Entry        = 3
            Time Stamp   = 0 0
            Reset Count  = 19
            FW upgraded: V2.1.0->V2.1.1
    
    Dump another entry [Y]/N?
    
            Entry        = 2
            Time Stamp   = 0 0
            Reset Count  = 5
            FW upgraded: V2.0.2->V2.1.0
    
    Dump another entry [Y]/N?
    
            Entry        = 1
            Time Stamp   = 0 0
            Reset Count  = 0
            FW upgraded to V2.0.2
    
    Dump another entry [Y]/N?
    =======================================================================
    
    No more Error Log entries.
    
    
    QUESTIONS.
    Are there any known problems with the portswitch 900CP and IP Services?
    How can I get the portswitch working as an IP services module again?
    A power reset would probably achieve this but will the problem reoccur!
    Are there any fixes for the FATAL ERROR and reset problems?
    
    Any info would be appreciated.
    
    Regards
    
    Anil Chopra                         Tel:  01256-373746 (Direct line)
    UK Comms Support                          01256-57122  (central call desk)
    Digital Customer Support Centre     Fax:  01256-841494
    Multivendor Customer Services       Internet:  [email protected]

T.R	Title	User	Personal Name	Date	Lines
4190.1	900CP IP failure	NPSS::KILSDONK		`Wed Mar 12 1997 09:27`	5
	In the code base for the portswitch, we are currently working a problem similar to your own in which the box does not answer a ping after a tremendous busy second in which network utilization is quite high. We are currently finishing an engineering build that would will attempt to fix this problem and then move it into the portswitch product space. The box continues to work except without IP because its local LANCE chip is disabled and re-enabled. Unfortunately, while disabled it has gotten itself into a bad state.
4190.2	reformated to 80 col.	KERNEL::FREKES	Like a thief in the night	`Wed Mar 12 1997 09:47`	9
	In the code base for the portswitch, we are currently working a problem similar to your own in which the box does not answer a ping after a tremendous busy second in which network utilization is quite high. We are currently finishing an engineering build that would will attempt to fix this problem and then move it into the portswitch product space. The box continues to work except without IP because its local LANCE chip is disabled and re-enabled. Unfortunately, while disabled it has gotten itself into a bad state.