Title: | Notes Conference for TME 10 NetView for NT NT |
Moderator: | TUXEDO::BAKER |
Created: | Mon Apr 03 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 540 |
Total number of notes: | 1903 |
I am working on a project in which we have proposed Polycenter Manager on NetView for Windows NT and ClearVISN Multi-Chassis Manager (HUBWatch) as the management tools for a customer network. Due to confusion over where to buy the Polycenter Manager on NetView, we ended up installing the kit (from BIKINI::) on to the demonstration system to show the customer how PNV and MCM would display their system. PNV started up fine and immediately did an autodetect of the various components. However, when we tried to get snmp data from one any remote node, the request timed out and a message was displayed indicating a problem with the community name. We had not changed the community name on any of the devices and all seemed to be using public. We noted that we could get the snmp data from the local machine running PNV. We had MCM running in background. It seemed that either the snmp servers were not running on the remote machines or somehow the snmp requests from the PNV PC were not getting out on to the wire. I saw the note 349 but this seems specific to Router Manager and a conflict on who owns the snmp ports (161/162 ?). But Iassuem this wouldn't be a problem with our own products. Therefore I was wondering if anybody has any idea as to what the problem might be ? The PCs were all running NT V3.51 (plus latest service pack), NT reported that the snmp services were running on all the other PCs in the network. I believe the PNV was V3.1. I apologise if this is a known problem but a quick scan of this conference didn't seem to flag anything and I didn't see anything in the documentation Thanks John
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
510.1 | TUXEDO::ROMBERG | So many log files, so little documentation..... | Wed Jan 29 1997 15:53 | 17 | |
PNVNT and Router Manager do both want port 162. At the current time, the two products cannot run simultaneously on the same machine. Whoever starts first will get the port, and the other will report the error. > It seemed that either the snmp servers were not running on the remote > machines or somehow the snmp requests from the PNV PC were not getting > out on to the wire. Are there any messages in the \usr\ov\log\pnvmsg_stderr.log? Can you turn on netmon logging [netmon -M 15 to see snmp requests and pings] and see if the requests are being sent? Do you know what community name is being used? NetView wants public. Kathy |