Conference netcad::hub_mgnt

2489.0. "Clarify for me 90L+ mgmt in 900MS, please" by DECPRG::PAVLUP () Fri Jul 07 1995 14:33

Can anyone clearly clarify for me one point around DS90L+s in DEChub 900
chassis?

Assume a configuration with a DEChub 900, several 900 modules (repeaters,
switches, etc.), and couple of DS90L+. The hub MAM an IP address to manage
normally the modules through hub view from HUBwatch.

In the network somewhere is an Agent 90 that is configured to have a
community defined for the DS90L+s in the hub - say public_1. All agent
table entries are defined according to the manuals, etc. I can easily manage
the DS90L+s by going to agent, selecting a proper community and making
it current... Everything's fine.

The DS90L+s are also added into the DEChub900 view (manually), including all
required characteristics. However, double-clicking on these DS90L+s in the
DEChub 900 front view generates "No response from agent" message, and it
is not possible to manage them in this way.

Just for my understanding: 

I assume that because the MAM is used in the hub 900 management (IP 
address is set), this double clicking cannot work. Is that correct? 

It should work in case the MAM was not used, and all the management was 
through agent90. Correct?

In case the MAM was not used - i.e. no IP address set - would it be possible
to manage also 900 modules from the hub view (double-click) - and how? 
This means whether the agent90 management is an option for such situation.

I'd appreciate answers from those who know...!

Thanks and regards Petr.

You do not have things configured.  See any of the notes in this conference
which reference the 90L+, or look at the HUBwatch installation manual.
Because the weekend's almost here, I won't repeat that info.

But, once you've got this all set up correctly, here's what should happen:

Startup HUBwatch with the 900 hub's front panel.  Double-click on the 
DECserver 90L+.  HUBwatch gets the 90L+'s MAC address from the MAM.  It
then attempts to look up the IP address and community of the DECagent 90
from the agents file.  If it finds it, it sends the SNMP request to the
DECagent 90 community.  The DECagent 90 translates the SNMP to whatever
the 90L+ uses as a protocol (MOP?).

Once you correctly install everything, you never need to know the DECagent 90
even exists.

Tom Hood
HUBwatch

    Hi Tom,
    
    thanks for quick reply just before the weekend... I've read a number of
    relevant topics in the conference regarding the 90L+ management. I
    mostly wanted to know what is supposed to work, and what is not (it was
    not always clear to me). I can
    now try to fix the configuration to make it work as you've described.
    
    Regards Petr.