| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hello,
Since upgradeing to V1.1 a customer has found that when he tries to
fire up a remote community from MSU window he either gets the local
community to the agent or the message "current agent community name
not in agent table".
This used to work ok on V1.0 - Anyone any ideas why this happens?
If customer goes into local community and looks at manage table, the
remote communities are there and he can make them current for
management.
Am I correct in assuming that when activating a remote community icon
in MSU the ip addess (agent address) and community name should be passed to
open up the correct community?
Any help appreciated,
Jon
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 330.1 | What rev MSU? | SLINK::HOOD | I'd rather be surfing | Fri Aug 06 1993 17:20 | 3 |
What version of MSU? Tom | |||||
| 330.2 | MSU V1.2 | KERNEL::WARDJO | Mon Aug 09 1993 13:19 | 7 | |
Tom,
MSU is V1.2.
Regards,
Jon
| |||||
| 330.3 | There is a fix. | QUIVER::WILSON | Tue Aug 10 1993 20:30 | 42 | |
Well, I tried what you described and got the same results that your
customer got.
The Problem:
When you add an item to the MSU map you must fill in the interface
information for that item. Therefore, you must goto the Configuration
pulldown and from there select Interface Database. This brings up
another window in which you specify the IP address, community string, etc.
In this window there is only one field to enter a community string for the
item, but internally to MSU, there are two types of communities, a read-only
and a read-write community.
I assumed that when I was filling in the community string it would be
filling in the read-write community. But apparently the string the user
provides is written into the SQL database as the read-only community.
When HUBwatch is launched it asks for the SNMPwrCommunity (read-write
community). The fix is to modify a line in the file:
/usr/kits/msu/app-default/nms_map_menu.def
The change must be made to the section which launches HUBwatch. Which
currently appears as follows:
# %HUBWATCH_EXTENSION_BEGIN%
MENU: HUBwatch
BUTTON: Manage
ENV_TYPE: WINDOW
BINARY: hubwatch
COMMAND: *-x <InternetAddress>* *-a <InternetName>* *-c <SNMPwrCommunity>*
ENDMENU
# %HUBWATCH_EXTENTSION_END%
change the COMMAND: line to read:
COMMAND: *-x <InternetAddress>* *-a <InternetName>* *-c <SNMPrdCommunity>*
This should fix it. If you have any questions just send me mail.
Karen
| |||||