| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 710.1 | Me too | WOTVAX::HATTOS | I think, Therefore I'm paid less | Wed Feb 09 1994 10:21 | 9 |
| TIM,
I have a similar problem for a DS900TM.
I can see it in the hub but not manage it. If I give the 90oTM an IP
address and set it up for SNMP, I can then manage it as a standalone
agent but still not from the HUB view.
Stuart
|
| 710.2 | A couple of possibilities | QUIVER::HAROKOPUS | | Wed Feb 09 1994 10:37 | 12 |
| Did you add an entry for the Brouter to the HUBwatch agents file
and include the MAC address in the entry?
I'm not sure why the DS900TM isn't working. It's not necessary
to have an agent file entry for that module. The only problem
I know of with this module is if you change the community name
string to anything but public then it doesn't report it corectly
to the MAM.
Regards,
Bob
|
| 710.3 | But it is public...8*( | WOTVAX::HATTOS | I think, Therefore I'm paid less | Wed Feb 09 1994 10:43 | 15 |
| >>I'm not sure why the DS900TM isn't working. It's not necessary
>>to have an agent file entry for that module. The only problem
>>I know of with this module is if you change the community name
>>string to anything but public then it doesn't report it corectly
>>to the MAM.
Are you referring to the community name in the DS900?
I have just checked on my DS900 and the read only community is public,
the r/w is something else unique. I still cannot manage the DS from the
hub view using 900T repeater for IP services.
If you want a look... 16.182.224.175
Stuart
|
| 710.4 | illegal sysObjectID ? | SLINK::HOOD | I'd rather be surfing | Wed Feb 09 1994 11:42 | 6 |
| 16.182.224.175 returns an illegal sysObjectID to HUBwatch
1.3.6.1.4.1.36.2.15.5.1
The DECserver 90TL/900TM should return:
1.3.6.1.4.1.36.2.15.5.1.3
What rev is that?
|
| 710.5 | Known DS900 bug | QUIVER::HAROKOPUS | | Wed Feb 09 1994 15:28 | 14 |
| re .3
The read-write community of the DS900TM module needs to be public in
order to manage that module in a DEChub 900 with HUBwatch. When the
servers' read-write community is not public it passes a bogus community name
string to the DEChub 900 hub manager and thus HUBwatch does not
know the correct community. This is a known bug in the DS900 firmware.
The only workarounds are either to change the read-write community
to public or manage the DS900 stand-alone.
Regards,
Bob
|
| 710.6 | Got it now.. but here are the revs | WOTVAX::STUS::Stuart Hatto | ACB actually means A Cold Beer | Thu Feb 10 1994 05:45 | 14 |
| Hi,
DS900TM revisions are...
Access Software V1.3
DS900TM BL80-27
ROM V5.0-0
LAT V5.1
I have managed to manage the DS900 now from both VMS and Windows,
by doing what was suggested by the .2 note for the Brouter.
Thanks,
Stuart
|
| 710.7 | | QUIVER::SLAWRENCE | | Mon Feb 14 1994 14:13 | 3 |
| More specifically, the string must be 'PUBLIC', not the more usual
'public'.
|