| 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 |
Question concerning integration of HP OpenView and MultiChassis Manager
V6.0. Per customer:
"Before the upgrade when I opened a hub by clicking on it, hubwatch would
look it up in the data file and use the community string defined there.
Now with the new version it always uses public. I have verified that
hubwatch_library is defined correctly. If I start hubwatch itself all
the hubs show up and work right when I select one.
Any idea what is wrong."
I have responded to the customer that the change in how community
information is stored is probably why it does not work the same.
Pointed out section 4.3.3 in the README.TXT as a possible fix.
Since I have no access to a system running HP OpenView, could anyone
confirm that MultiChassis Manager should work just fine with it? Any
other confiruration changes needed??
Thank You
Randall Buck
MCS - Network Support
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4354.1 | Community string missing | CSC32::R_BUCK | Authenticated and assimilated | Tue Apr 15 1997 10:16 | 18 |
A further update and refinement to the problem statement. Per
customer:
"When I select a hub in HP OV hubwatch starts fine and I can see the hub
and modules. The problem I am having is that I can not make any changes
since it is opened with public. If I select "File" and then "Open" I
do see all my hubs and devices. If I select the hub from there it
comes up with the proper community string."
So it would appear that with a prior version of MultiChassis Manager,
the community string stored in HW_AGENT.DAT was used. Current version
is not picking up the community string from the database when invoked
from HP OpenView and possibly other products, (ManageWorks?).
Any ideas? Fixes??
Randall Buck
MCS - Network Support
| |||||
| 4354.2 | NETCAD::RUSSO | Wed Apr 23 1997 12:07 | 10 | ||
There is no special code that I know of in clearVISN V1.0 that would perform the agent file lookup functionality you described. The clearVISN V1.1 code still uses the HW_AGENT.DAT file so if it did work in V1.0 it should still work in V1.1. Our group has some very tight deadlines for clearVISN V2.0. If the customer has a work around (i.e low priority) I would like to defer this problem. For clearVISN V2.0 I will send system test a note to try to test this. Joseph Russo | |||||