T.R | Title | User | Personal Name | Date | Lines |
---|
3302.1 | Nope. | NETCAD::GALLAGHER | | Thu Feb 22 1996 09:17 | 20 |
| > Can anyone tell me whether HubWatch for VMS will regularly poll hubs on
> a network? And, if so, what would it be doing?
HUBwatch doesn't poll hubs.
> I am currently working an
> issue where we are getting regular "authentication failures" from IP
> services modules in a DECHUB900 & modules w/IP addr's in DECHUB one's.
> However, HubWatch can bring up DECHUB's configurations w/o a hitch.
What's the community string of the modules? Are there other NMS-like tools
in this environment?
(I ask because we have a lot of auto-discovery/network topology tools
which discover IP addresses, and send SNMP read requests to those devices
to find out more about them. The SNMP messages use community string "public".
If the device's don't have this read-only community, they will generate
authenticationFailure traps when queried. It's just a theory.)
-Shawn
|
3302.2 | Okay, it kinda does poll one hub... | NETCAD::GALLAGHER | | Thu Feb 22 1996 09:47 | 7 |
| Okay, I tried to be brief, now I'll try to be accurate.
HUBwatch is used to manage one hub at a time. So a HUBwatch session will
only poll the hub your currently watching. (There's a pull-down to enable
polling the hub.) When you exit HUBwatch, polling stops.
-Shawn
|
3302.3 | Have a Theory | OHFS02::MALOTT | | Fri Feb 23 1996 08:53 | 20 |
| Thank you, Shawn for your quick replies. I have a theory on the
problem that I think may have resolved it;
Each module (900 class modules, in this case) within the hub can be
assigned an IP address. However, the Hub only had IP Servicesaddresses
assigned to slots within the Hub. Hubwatch was running and polling the
IP Services addresses used by the MAM in the Hub. The MAM in the Hub
was (I think) in turn polling its individual modules. .: Since these
modules were not set up with an IP Address, Community String, etc...
we rev'd "authentication failures" from the polledd IP Services Address
of the Hub.
We are going to re-check this today, but I believe giving each module
an IP address (in addition to the IP Services Address(s)), R/W
community string etc... resolved the issue.
thx,
jcm
|
3302.4 | hmmmm | NETCAD::MILLBRANDT | answer mam | Fri Feb 23 1996 10:48 | 14 |
| Hi -
Assigning an IP address to each module in a hub should not be
necessary, though Hubwatch will discover the addresses and
use them, thus getting around your problem.
Did you change the Hub's read/write community string? If so,
have you reset the Hub since then? If you have not, then
polls to the hub will work but polls that pass through the
Hub to the modules will not. This confusing behavior has
been deemed "okay" by powers that be and is presumably
buried somewhere in the documentation.
Dotsie
|