Conference netcad::hub_mgnt

    For the crash please read notes 1871.3 and 1871.5 about how to get 
    crash information and core dumps to us.
    
    For the power supply the HUB will still detect that the power supply is
    in the slot even if you turn the switch off.  If you look at the help
    for the Environmental View, Table 5-1 explains the LED states for the
    power supply.  I believe that the LED state should go from green to 
    yellow when you set the switch off.  However, you should refresh the
    screen to see the state update.
    
    							John

    Hello,
    
    I have a customer with the same problem. The only difference is that
    my customer say that HUBwatch crashed 1 sec. after HUBwatch polled
    the HUB900 and see the concentrator loss. The software they used is
    OSF/1 3.0, HUBwatch 3.1, HUB900 NAM 3.1. and concentrator SW 2.8.
    Polling is also set to 10sec (min. value) I have also the crash
    info and core dump.
    
    dbx version 3.11.6
    Type 'help' for help.
    Core file created by program "hubwatch"

    signal Segmentation fault at   [strcat:136 ,0x3ff800d4b24]       
    Source not available
    (dbx) where
    >  0 strcat(0x11fffeea8, 0x140084af8, 0xfffa5a5afffa5a5a, 0x11fffeeae, 
    0x11fffeba0) ["../../../../
    ../src/usr/ccs/lib/libc/alpha/strcat.s":136, 0x3ff800d4b24]
    1 hub_snmp_oid2str(0x1402132a0, 0x11fffef18, 0xfffa5a5afffa5a5a, 
    0xfffa5a5afffa5a5a, 0xfffa5a5a
    fffa5a5a) ["hub_snmp_ifc.c":3596, 0x120445438]
    2 hub_snmp_build_get(0x303037332d2e3638, 0x303037332d2e3638, 
    0x303037332d2e3638, 0x303037332d2e
    3638, 0x303037332d2e3638) ["hub_snmp_ifc.c":2698, 0x1204436e4]
    3 hub_req_send(0x303037332d2e3638, 0x303037332d2e3638, 0x303037332d2e3638, 
    0x303037332d2e3638, 0x303037332d2e3638) ["hub_mgmt_ifc.c":2879, 0x12043c1a8]
    (dbx)

    Is this a known problem / bug?
    
    Ronald de Groot 
      

    This was not a known problem until now.
    
    					John

    John,
    
    Must I open a IPMT case for this problem?
    
    Ronald 

    Not really - we can track it through here if you want.
    
    						John

    John,
    
    >Not really - we can track it through here if you want.
    
    Yes,
    
    Ronald
        

    Any status?

Do not expect a patch as a result of a bug report in this conference.  The
best that will happen here is that the next version of HUBwatch may contain
the fix.  If you have an immediate need, you need to follow the usual
channels.


Tom Hood
HUBwatch

    Tom,
    
    >If you have an immediate need, you need to follow the usual
    >channels.
    
    Thats what I asked in .3
    
    Ronald

    Ron - You'd be best to open an IPMT case, just so there is a
    formal history of the problem in case it is seen by other sites. 
    It also provides a mechanism for closure on problems. IE: It
    is documented as having occured and you have a way of tracking
    it too. It keeps the system honest, and provides means to measure
    product quality and customer satisfaction criteria.
    
    Bob