Q:
************************** For IBM Use Only ****************************
* In RETAIN use CR CA to complete the call. *
* The use of CC will not notify the originator of a response¢ *
************************************************************************
RESPOND ELECTRONICALLY.
Route = 5697C3000.
Abstract: 8260 & 8265 devices do not display in ATM Campus group
After doing a discovery, 8260, 8265 and 8210 devices are not showing in
ATM Campus and IP Internet groups. SNMP community strings have been
verified using SNMPWALK. Is it possible that the modules for these
devices have not been properly installed? How can I check?
If you cannot reach me at my phone, please page me at 800-533-5645.
Thanks,
MRD
Requeue to NWAYS for diagnose. dlw0727
A:
Attempted to call Maria, no contact. Requeue to attempt contact later.
NSSST - 07/27/98 - 15:56 - RD
NSSST - 07/27/98 - 15:56 - RD
NSSST - 07/27/98 - 15:57 - RD
Q:
RESPOND ELECTRONICALLY.
I found a voice mail with an attempt from IBM to contact me. No phone
number for callback was left. If you do not find me at my desk
(305-348-2703), please page me at 800-533-5645.
Update by customer to NWAYSW,172 dlw0728
A:
CUSTOMER REP: Maria Drake
PROBLEM: Auto-discovery not working properly.
ACTION TAKEN: I contacted Maria, had her verify that she had physical
connectivity to the affected machines (via PING and DEMAND POLLS).
After this verification, the objects still did not show on the mao.
ACTION PLAN: Requeue for level 2.
Q:
RESPOND ELECTRONICALLY.
I have created a seed file hoping that it would help the discovery
process; however, devices added to the seed file list are not displaying
in IP Internet and ATM Campus groups.
Q:
RESPOND ELECTRONICALLY.
Please note that I will be out of the office July 30 through August 2.
MRD
A:
The problem on the machine is that ipmap was failing. Discovery was
finding the objects and putting them into the object database, but with
ipmap failing, there was no ip map in Netview. Had to start ovwdb,
ovtopmd, and netmon separately, they all strated. I had obdelobj'd
all of the Nways daemons and moved the Nways registration files so that
they wouldn't chew it up. Then discovered ovtopmd was failing, so
netmon fell over. Could not do ovstart, so to find the breakage,
started first 'ovstart ovwdb', then ovtopmd, then netmon. Left that to
stabilize for a few minutes, then ran ovstart alone for the rest. After
that, added the Nways lrf's back in, then moved the Nways registration
files back in place, and fired him up. All was VERY slow (45 minutes
to get the gui all the way up, but it cam up, 8260's and 65's were there
the ATM topology correctly contained 7 PNNI peer groups and no default
cluster. So, we're on the way. Letting it run a while to be sure,
then will wait to talk to Maria on Monday.
Q:
A:
Called customer to check on status. System is working OK now.
Customer says that she hopes to get a "bigger" AIX box wit more memory
soon to help the NWAYS load.
Customer says that PMR can be closed.
Q:
RESPOND ELECTRONICALLY.
This problem may be closed
IBM Feedback:
Per customer recommendtaion, PMR is closed.
S e a r c h - k e y w o r d s:
AIX resources nways
WWQA: ITEM: RTA000152319 ITEM: RTA000152319
Dated: 09/1998 Category: NWAYSAIX
This HTML file was generated 99/06/24~12:43:40
Comments or suggestions?
Contact us