| First of all, YOUR CUSTOMER HAS FIELD-TEST SOFTWARE! If it were my customer,
I would change it into real software.
As for the DECservers, ...
Read the HUBwatch Installation and Configuration manual. There you will
find, in convenient table format, how to manage DECserver 900TM's.
But, sure, I'll be happy to type it here. Again. and Again. and Again.
- Assign the DECserver an IP address.
"def inter subnet mask nn.nn.nn.nn"
"change inter address nn.nn.nn.nn"
- Community in the DECserver must be PUBLIC (this requirement will change
in a future version of NAS)
- Enable SNMP in the DECserver
"change snmp state enabled"
"change snmp comm PUBLIC getnext enable"
"change snmp comm PUBLIC set enable"
"change snmp comm PUBLIC address <ANY or adr-of-pc>"
"init delay 0"
It can then be managed either as a standalone module or as a module within a
hub.
Tom Hood
HUBwatch
|
|
Tom,
Sorry to be so thick, but I think my problem may have been the community name.
I did read the previous entries on that subject after my attemp, but wasn't
sure if the restriction still existed. We did manage to manage DECserver90-TL's
as part of a hub by specifying their agent info, and then adding them to a
DEChub-90 graphic.
I'm going to get the customer a proper copy of HUBwatch, and try again.
Many thanks,
Meic.
|