Nways manager for aix LNM problem
ITEM: RTA000153790
A:
IF THIS PMR HAS BEEN QUEUED TO AN INCORRECT SUPPORT CENTER, PLEASE
ENTER PROBLEM DESCRIPTION AND QUEUE TO ZAIXV3 L165
SELECT ALL APPLICABLE SUPPORTLINE SERVICES:
HOURLY: N MONTHLY: Y
24 X 7: Y COMPLIMENTARY: N
PREMIUM: Y PROGRAM SERVICES: N
CONSULTLINE ELIGIBLE: YES: - NO: X
XMENU ITEM REFERENCE: JD6211__
********************** ATTENTION ***************************
Time associated with work on this PMR must be recorded using
FI 973. Both DEFECT and USAGE time must be documented in this FI.
Question:
7013 j50 415
problem with nways for campus manager for aix
=-=-=> 11/16/98 <=-=> 12:04:56 CST <=-=-=> Nancy Tapia <=-=-=-=-=
A:
problem with demon - lnmbrmgr shows 100% utilization
customer running Nways 1.1 code I sent him a ptf to upgrade him ti 1.2.
2 code but he wants to fix this problem first. I do not understand his
problem.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-98/05/15-14:40--FI
Support Line: _30__ mins.
Customer running AIX4.2 and NV412+PTFs and NWAYS v1.1 which is no longer
in support.
CUstomer was running OK on platform until installing another 3rd party
mgmt extension for managing Olicom TR switches.(Switch Manager for
Tivoli TME10 NV4AIX).
The F50(4 processors, 1.5-2.0GB memory) was CPU bound by lnmbrmgr,
iubsearchx, and possibly other lnm processes.
Instructed customer to kill lnmbrmon and lnmtrmon and stop NV EUI.
Customer never uses the LAN mgmt so recommended preventing the startup
of LNM processes.
Recommended customer clear LAN DB and ovstop cmld.
Customer will callback after processes complete(system CPU bound).
Research basis for LNM lockup.
Waiting for customer callback.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-98/05/15-14:40--FI
Support Line: _30__ mins.
Customer running AIX4.2 and NV412+PTFs and NWAYS v1.1 which is no longer
in support.
CUstomer was running OK on platform until installing another 3rd party
mgmt extension for managing Olicom TR switches.(Switch Manager for
Tivoli TME10 NV4AIX).
The F50(4 processors, 1.5-2.0GB memory) was CPU bound by lnmbrmgr,
iubsearchx, and possibly other lnm processes.
Instructed customer to kill lnmbrmon and lnmtrmon and stop NV EUI.
Customer never uses the LAN mgmt so recommended preventing the startup
of LNM processes.
Recommended customer clear LAN DB and ovstop cmld.
Customer will callback after processes complete(system CPU bound).
Research basis for LNM lockup.
Waiting for customer callback.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-98/05/15-14:40--FI
Support Line: _30__ mins.
CUstomer cleared LAN DB(in progress) and updated cmld.conf to "0"
the 2nd entry for lnmhubint...prevents lnmhubint and lnmtopod from
running.
Customer will callback with status update.
Q:
A:
Called and left message to callback with status update or for further
assistance. Indicated that problem resolution would be assumed if
no callback.
Q:
A:
No response from customer following recommendations given to eliminate
LNM processes. Per message left with customer and presumption that
problem is resolved, PMR is closed.
S e a r c h - k e y w o r d s:
lnmhubint cmld.conf
WWQA: ITEM: RTA000153790 ITEM: RTA000153790
Dated: 12/1998 Category: NWAYSAIX
This HTML file was generated 99/06/24~12:43:41
Comments or suggestions?
Contact us