Conference netcad::hub_mgnt

I am getting a similar effect to your problem #1 when using HUBwatch for ULTRIX.

See 245

Any ideas??

Paul.

    First of all, DECbridge 90 and DENMA should be upgraded to most
    up-to-date firmware with the HUBwatch as follows:
    
    DECbridge 90 - V3.1 (V3.0 is also acceptable)
    DECagent     - V1.1 
    HUBwatch for VMS or Ultrix (V1.1)
    
    As far as Problem 1, the HUBwatch failed to get the IFindex information
    for a bridge port from the DECagent.   In other word the DECagent
    failed to poll the bridge in a hub.  The HUBwatch needs a port IfIndex
    information to get other attributes.   The DECagent firmware folks will
    look into this problem.
    
    This is not a good solution but it is worth to try.  Reset the bridge
    first to see the problem disappears.  Communication will be disrupted
    for 30 - 50 seconds until the bridge goes into forwarding state. 
    Notice that the HUBwatch will fail to talk to the HUB until the bridge
    is up (30 - 50 seconds).   You should not use the FACTORY RESET which
    causes the bridge reset to factory settings.
    
    If the problem still exists, try to reset the DECagent.  Once again, no
    FACTORY RESET which causes the DECagent loose all information such as
    community table.   This process normally fixes the problem.
    
    
    
    
    the bridge is up the HUBwatch will fail to talk to the HUB.  If
    the problem still exists, reset the DECagent.

.2
>>    DECbridge 90 - V3.1 (V3.0 is also acceptable)
>>    DECagent     - V1.1 
>>    HUBwatch for VMS or Ultrix (V1.1)

I've been using DECagent X1.77. Is V1.1 different and is it available on the net?

DIRT::DENMA$SSB does not have the kit.

regards,

	Paul.

    I have tried T1.1-2 DECagent and it still doesn't work.
    I also can't find V1.1 DECagent...
    Mike

    I have now tried this with the V1.1 DECagent code and the behaviour is
    still the same.
    You get the Failed to get bridge management information box pop up when
    you double click on the DECbridge and a message
    (E) Failed to get IF interface.
    This is a HUB90 with a DECagent in slot 8 a DECbridge90 in slot 7
    (V3.1) and a DECrepeater 90C in slot 1.
    
    I have tried powering off the bridge and agent and resetting them.
    I can't find any way to make this stuff work.....
    Any clues???
    thanks,
    Mike

    I had the same problem, then my agent died. I got a new one, with T1.1
    and now it all works fine. My DECbridge 90FL's are at V3.1, I don't
    know if this is coincedence or not.
    
    Brad
    

    re: .6
    Ok, I reset the agent to factory defaults and now it works ok.
    
    I have tried with both a DECbridge90 (V3.1) and a DECbridge90FL (V3.0)
    in the HUB with the DECagent(v1.1) and a DECrepeater 90C and it all
    pretty much seems to work.
    
    I had actually tried to reset to factory defaults from HUBwatch, but
    that must not have worked...
    Mike

    new (V1.1) agnet code can be found by reading
    NAC::MANAGMENT:AGENT_LOAD.TXT.  No longer on DIRT!
    

	re .7
	I also tried an Agent factory reset and it now works. Now I need to 
	upgrade and reset all the remote Agents :^)

	re .8
	that should read -

	NAC::MANAGEMENT:AGENT_LOAD.TXT
		  ^
		  

    Hello,
    
    Can anyone clarify the upgrade proceedure for the Decagent and Decbridge
    90.
    
    I would like a customer to upgrade to V1.1 of the Decagent and 3.1 for
    the Decbridge but am unsure of how the customer gets the kits.
    
    Do we provide them free from the CSC?
    
    Is there an upgrade kit (Part numbers?) that the customer buys?. 
    Does it contain NDU?
    
    Is there anyone who can clarify the proceedure we should follow to get
    these devices upgraded for customers?
    
    Thanks and Regards,
    
    Jon
    
    

    Hello,
    
       RE 0
    
    A customer has two dechub 90's, each with a 90FL bridge in slot 7 (V3.0)
    and 3 90T repeaters in slots 1 to 3 and a 90F Fibre repeater in slot 6.
    
    The first hub has an Agent 90 (V1.1) in slot 8.
    
    The customer found that with Hubwatch (V1.1) he could access all devices
    except the 90FL bridge in the same hub as the agent, and when he tried to
    access this bridge he got the message "Failed to get IF Interface, Failed
    to get Bridge Management information". The other bridge in the other Hub
    was OK
    
    A factory reset of the agent had no effect (This was done from a terminal
    connected to console).
    
    The customer removed all the modules from the first hub and slotted
    them in in the following order and the problem went away:-
    
       1 - insert agent and factory reset
       2 - insert Bridge
       3 - Set agent IP address
       4 - insert other modules
    
       Is the order of inserting Modules significant?
    
    I have seen several situations similar to this but have been unable
    to get to the cause of the problem - it usually results in the agent being
    swapped out.
    
    Can anyone offer an explanation?
    
    
    Thanks for any help,
    
       Regards,
    
       Jon