T.R | Title | User | Personal Name | Date | Lines |
---|
3292.1 | Bulk changes R us | SLINK::HOOD | They call me MISTER Dilbert. | Mon Feb 19 1996 10:30 | 4 |
| clearVISN Resilience will do bulk changes!
Tom Hood
clearVISN apps
|
3292.2 | NetView? | GIDDAY::MUNN | Slothy Dogs Rule the Earth | Wed Feb 21 1996 05:58 | 6 |
| Well, I don;t really want to buy another product to do this job.
I've got NetView which has the snmpset ultility. So the questions is,
can I use that to set the attributes I want ??
/richard
|
3292.3 | | NETCAD::DOODY | Michael Doody | Wed Feb 21 1996 09:31 | 9 |
| But would Resilience really only be doing that one job? You'll also
want it for backing up all those hub & repeater configurations. No more
drudgery of making all those LANs and port groupings just because
you add a hub or repeaters.
But anyway, to answer your question, all the management of hub products
is done via SNMP. So yes, you can do it if you read the MIBs.
-Mike
|
3292.4 | Can't find it ! | GIDDAY::MUNN | Slothy Dogs Rule the Earth | Wed Feb 21 1996 14:29 | 20 |
| Ok, now I'm really confused!!!
I dragged the MIB defn from gatekeeper, had a scan through it and found
the eavesdropping stuff.
I then went over to Netview, loaded the MIB definition OK the used the
MIB brower to go down the MIB.
All seemed to go well, I got down to
...dechub900.repeater.rptrVersion.... so the browser was following the
MIB OK, but when told to query, it found nothing at .repeater. In fact
a walk of the MIB stops at dechub.3 (the repeater is at 5).
By the way, the repeater in question is a 90FS. I know it can be got at
since HUBwatch can set the eavesdropping stuff OK.
Does this mean I'm using the wrong MIB ?
(dec-hub900-erptr-mib-v2-0.txt)
/richard
|
3292.5 | | NETCAD::DOODY | Michael Doody | Wed Feb 21 1996 14:47 | 6 |
| It may mean you're using the wrong community string. If you are using
the MAM's IP address to query the repeater, you need to use the SNMP
gateway by specifying the slot number. Like "public-3" to access the
module in slot 3.
-Mike
|
3292.6 | direct snmp to repeater | NETCAD::CURRIER | | Wed Feb 21 1996 15:54 | 15 |
| ...dechub900.3.... is the ptrm mib which resides only on the management
agent in the hub. As Mike said, you must directly query the repeater
to access repeater mib objects.
This can be done by using the ip address of the repeater with community
string public
or by using the ip address of the hub management agent (mam) with
community string public-# where # is slot number
The repeaters do support these mib objects
-sheila
|
3292.7 | it works now | GIDDAY::MUNN | Slothy Dogs Rule the Earth | Wed Feb 21 1996 17:15 | 10 |
| Yes, it's all my fault.
I had assigned a R/W community string of netman then failed to to use
netman-3 to access port 3.
Since correcting this it all works fine.
Thanks you all!
/richard
|