Conference netcad::hub_mgnt

2052.0. "Agent failure in HUB900 ?" by RDGENG::GREID (Hook.....in....mouth!) Mon Feb 27 1995 10:10

    Just recently I have benn having trouble talking to the Agent in our
    DEChub 900 backplane even though the IP address, community name and IP
    services slot have not changed. The hub is connected to the LAN by a
    DECBridge 90FL or by FDDI into the DECBridge 900mx in the Hub.
    
    I cannot ping the agent in the Hub but can talk to the console port
    via a reverse lat port.
    
    When trying to fire up Hubwatch from OpenVMS I get :-
    
    HUBwatch for OpenVMS, Revision V3.0.0
    (I*) HUBWATCH$LIBRARY = SYS$LOGIN
    (E*) snmp: failed qid 1 initialization
    (W*) snmp: using sync mode for poll qid 1
    (E*) snmp: failed qid 3 initialization
    (W*) snmp: using sync mode for poll qid 3
    (W*) Current agent not in the agent table
    HUBwatch initialization failure
    
    Is this a failure in the agent ?
    
    There are two DECservers on the backplane which have loaded
    successfully from the LAN and there is traffic on the hub, as all
    the devices indicate traffic and I can PING all devices that have IP
    addresses set.
    
    Giles.
    REO Networks Support.
    

    Actually I can Ping the agent, and the agent is visible via Netview.
    
    However I still cannot get Hubwatch to talk to it.
    
    The IP services module in slot 3 is a DR900tm, which is also setup
    correctly.
    
    Giles.

    Giles,
    
    
    I Have also seen the above problem when corruption appears in the NVRAM
    of the Repeater itself. try replacing the repeater and re enablinf the
    inbound ip setup bits from the console port of the repeater.
    
    Bernie.