Q:
7025 f50 432
NWAYS CAMPUS MANAGER ISSUE/UNABLE TO GET HUFFS TO EXCUTE BY ANY USER
OTHER THAN ROOT USER
A:
customer rep: no contact made (answering machine). left a message.
problem: non-root user cannot display hubs (?)
product: nways campus manager lan, v3 (?)
action taken: possible fix by entering the following statement, then
re-trying the step: chmod 777 /usr/CML/conf
action plan: make another attempt to contact the customer and suggest
trying the above fix.
A:
customer rep: no contact made (left another message).
action taken: this time i left a message that he try the statement
chmod 777 /usr/CML/conf then have the non-root user
make another attempt to display the hubs.
> the above may not necessarily be a fix, but it's
a good possibility.
action plan: try to reach the customer tomorrow, 07/14.
A:
Contact Failed - Rang, no answer...
customer still not available.
requeue for later call back
still not available
CUSTOMER (RICK) IS REQUESTING CALL BACK @T/L 347-3228). STATING
SUGGESTIONS DID NOT WORK. REQUESTING AN EMAIL ADDRESS OR PHONE NUMBER
TO GIVE A RETURN CALL. CUSTOMERS EMAIL ADDRESS VALHALLA@US.IBM.COM..
customer rep: Phone Mail
problem: non root user unable to display hubs.
action taken: unable to contact customer by phone. send Email to
VALHALLA@US.IBM.COM
was not able to find a solution in networking.ibm.com
action plan: sending call to L2 for support.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _60__ mins.
Called and left message for customer to callback directly to me and
also left email indicating same.
Researching problem on test machine.
Q:
A:
I received email from customer with more detail of problem.
I called and left message to call back at my number with login info
to facilitate quick resolution of problem.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _45__ mins.
CUstomer running AIX432, NV511, NWays123.
Also, no root user operation...more secure server(I don't think TCB
level but some other permission differences.)
The customer cannot(as normal user) get the Nways maps to bring up
PSMs. The nv6000.log file indicates a OStore cache mgr failure.
The /tmp is drwxrwxrwt bin bin(sticky bit).
There were 2 files in /tmp that indicated attempted start of OStore DB.
I removed the sticky bit from /tmp and also updated ed.conf to proper
ordering of PSMs.
Had customer try EUI again...message left indicates still failing.
Customer will call again after clearing MAT DB.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _15__ mins.
Checking customer system using login.
The PSMs seem to be running with no further messages in nv6000.log.
I called and left message to call back with status.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _30__ mins.
Continuing to monitor system as MAT DB rebuilds. Paged customer who
called back. Customer started nv6000 EUI and waiting for syncing to
finish to know if MAT operation is fixed.
The /usr/lpp/ODI/OS5.0/cset/bin/oscmstat command lists 1 client as
being active....good news. It seems to be operating properly now.
Customer will call back before end of day.
We discussed the fact that the users run with umask 077 and wondered
if that might cause a problem in NWays operation....to be researched.
Q:
A:
Paged customer and left message on phonemail to get back with status
update on Nways operation. Waiting for response.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _90__ mins.
Researching security-based failures on PSMs. On our test system, the
non-root user can bring up a PSM if the previously running root NV
session had started before it which started OStore cache manager
process.
Sent email to customer with update.
Asked customer to call back with any status update.
Logged into customer machine.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _150_ mins.
Continuing to work with customer to isolate/resolve the non-root user
MAT bringup problem. The nv6000.log file indicates an ipmapBailout
error as well as PSM errors (DB_VISTA DB errors).
The ROOT user works OK including PSMs.(Nways123)
Customer does now have the JMAs working with non-root but had to change
the application association with the device to Java thtough manual
change.
--->Customer wants raise priority to 1 to get a resolution.
---> The system uses more than usual security measures.
The NV ovwperms are set to 775 bin bin on the default map.
AIX is 432. Other system running Nways123 is AIX421 and does not
seem to have this problem.
We have been through MAT DB clears, Reorgs, etc. with no success.
The system takes a long time to rebuild the MAT DB so don't do this
unless it seems the thing to do again.
---> CUstomer wants to raise to sev 1.
Customer pager is 888-641-9279.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _40__ mins.
Contacted Defect Support(Jason) to work on a plan to proceed toward
resolution. Discussed failure and messages. Defect support machine
with same code levels will be built to emulate failure.
Discussed ipmapBailout message with NetView support(John) and got
some insight into environment setup problems that could be involved
although no strong reason to think NetView is the root cause at this
point.
Called customer and left message regarding our efforts to resolve
problem.
Research further and call customer again.
--> Customer pager number: 888-641-9279 (Rick Key, Boulder)
Q:
A:
ACTION TAKEN: Discussed with Dan (sent note w/ login info)
ACTION PLAN: Build machine in our lab w/ AIX 4.3.2, NV 5.1.1, and
Nways 1.2.3. Follow up with L3 Bill R.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _200_ mins.
Logged into customer machine checking files, permissions, logs, etc.
Noted several permission differences between this machine and another
customer machine that seems to work. The differences were in MAT
(/usr/CML/PSM....). This did not seem to change the results.
I suggested to customer a removal of MAT and PSMs and a reinstall.
Customer agreed so I performed the removal and reinstall of mgtapptran,
psms6000.lan and jma.image filesets.
The system seemed to come up OK and the NV EUI came up again OK for the
root user. Customer will get MAT DB resync'd and try the non-root user
again with a status call back asap.
Waiting for customer callback.
Q:
A:
ACTION TAKEN: Installed lab machine with same versions of code as
customer. Installed logged in as root. May be useful in comparison to
customer machine.
ACTION TAKEN: Requeued to AXLAN pending reinstall of Nways.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _120_ mins.
Duplicated customer platform environment with Defect support assistance
(Jason).
On the test machine, cleared all DBs in Nways and NV. We did see at
least 2 times the failure of the MAT to stop processes when the NV EUI
was stopped in a proper way.(mgtapptrannv, Red, etc.).
The test environment otherwise seemed to work to allow the non-root
user to bring up PSM views.
The customer environment did continue to allow the root user to bring
up PSMs but not the non-root user.
I suggested that the customer remove the Nways product completely and
reinstall to eliminate any of the install problems that may have
occurred. The customer will remove the product and other remaining
components(MAT, etc.) and then reinstall. Customer will consult with
me before installing anew.
Waiting for customer callback.
Q:
A:
I called and left message with customer to try to change the application
for the PSM-type devices to Application Transporter instead of JMA and
see if they would come up.
Waiting for callback from customer.
Q:
A:
Received message from customer on Friday indicating that the final
recommendation to clear MAT DB and re-sync seemed to clear up the
basic problem of PSM apps starting the JMA instead of the PSM view.
Customer not yet completed with MAT discovery so he will call and
give status update.
Waiting for customer callback.
Q:
A:
Called and left message to callback with status update or for further
assistance.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _15__ mins.
Customer replied that the problem is resolved following the clear of
the MAT DB and removal of the JMA config directory. The rediscovery
completed with the PSMs now working as well as JMAs.
Customer is satisfied and appreciative of our support and indicates that
PMR can be closed.
(second install was with NV security OFF).
S e a r c h - k e y w o r d s:
nways 8224 JMA security
WWQA: ITEM: RTA000157877 ITEM: RTA000157877
Dated: 07/1999 Category: NWAYSAIX
This HTML file was generated 2000/11/30~13:34:11
Comments or suggestions?
Contact us