Q:
AIX Support Family
O/S Level: hpux
Type/Model: k360
Description:nways for hpux : realtime pollar numbers are different than
what he gets in graphing the nib browser
java based element manager..the cursor changes and doesn't change back
atm campus view mode: only 1 cluster shows..(the default) and in it,
only a couple of atm devices show up
A:
customer requested nways group...he said that he has spoken to them for
hpux before.
customer rep: Phone mail.
problem: need to call customer back to determin problem.
action plan: at alarm contact customer to get software version of
operating system and nways manager. get a discription of
problem.
A:
CUST CALLED REQ A CALLBACK FOR IMMEDIATE ASSIST¢
A:
customer rep: ron fox at 630-725-3469
product: nways manager for hp/ux, v2.0
problem: 1. when using the performance management function, the
number of atm branches in use number approx 6-12
branches, while the mib browser shows approx 600.
2. java element manager, while using the cursor to size
the window, the cursor doesn't revert back to it's
normal shape after releasing the mouse button.
3. his atm cluster display doesn't show the correct
number of devices.
action taken: no hits on the networking pages.
moving this to UXLAN,12U for assist.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _30__ mins.
Received more detail info via email from customer. Reviewing and
researching.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _150_ mins.
Received email with details on problems noted herein.
Duplicated problem 1 on test machine using RealTime Poller and SNMP
Collection. Observed same results as documented by customer.
Consulted development who explained that even though the name of the
object in the Poller Tree matches the name in the ATM MIB, it is not
the same representation by poller(or JPM) since the actual presentation
is the definition of the object according to the JPM configuration.
In this case, the Poller was showing a PERCENTAGE of Actual to Maximum
branches used rather than the raw number for actual used.
I created the object in JPM configuration to match the MIB object of the
SNMP collection and the same value was presented by Poller and SNMP
Collect.
I emailed this finding to customer.
Problem 2 has been noted previously and will be fixed in a future releas
e of the product. I emailed this to customer.
Problem 3 seems to have been a corruption either created by the Nways
upgrade to V2 or an existing corruption in the ATM DB/NV DB.
I sent email recommending these steps.
Waiting for customer response.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _20__ mins.
Customer responded by email. He acknowledges that he realized the
percent measurement was what he was seeing. He did appreciate an
explanantion of how to get the actual value that SNMP Collect was
monitoring.
In response to my recommendation for clearing the ATM Topology DB,
customer has completed (noting some significant documentation problems)
and is now at least starting to get a good beginning to the ATM
Topology map. Customer will report back tomorrow on status.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _15__ mins.
Called customer to get status update on ATM map problems.
Asked customer to call back with possibility for my logging in to
check the system out.
Waiting for customer callback.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _60__ mins.
Dialed into customer machine to fix ATM map problems with HPUX NNM5
and Nways V2. Customer has 3 maps and apparently has caused some DB
consistency problems...found ahmledisplay and ahmeui orphaned.
Called customer to indicate this finding and indicated that I would
work on recommending a plan to resolve as well as a recommendation for
working with multiple maps and preventing these DB consistency
problems.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _100_ mins.
After dialin to customer machine, discovered multiple maps as well as
many REMOVED objects in NNM DB that will prevent Nways discovery from
proceding properly.
Customer replied in email that he had taken several steps to fix DBs
by removing extra maps, ovtopofix, etc.
Sent several emails, on indicating the need to perform "ovmapcount -R"
followed by ovtopofix to get REMOVED objects out of DB.
Waiting for customer call back.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _45__ mins.
Customer sent email with update on ATM map status....still not perfect
yet.
I dialed-in to customer machine and noticed still the REMOVED objects
in the NNM ovwdb DB. Directed customer to HP support for final word on
fixing this but indicated that the "ovmapcount -R" and "ovtopofix -a"
seems to remove these objects from the DB.
Waiting to hear back from customer.
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _45__ mins.
Customer sent email with update on ATM map status....still not perfect
yet.
I dialed-in to customer machine and noticed still the REMOVED objects
in the NNM ovwdb DB. Directed customer to HP support for final word on
fixing this but indicated that the "ovmapcount -R" and "ovtopofix -a"
seems to remove these objects from the DB.
Waiting to hear back from customer.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _12__ mins.
Customer called and left message indicating that the ATM map on his
HPUX system is now working in some fashion although some instability
might remain on PNNI links(still working with it).
Customer asked that I page him at 888-269-1732.
I paged customer.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _20__ mins.
Customer responded to second page. Customer now getting 8265s in ATM
view after deleting them from the map separately from Nways Device
submap and IP submap. The 8210s do not seem to respond to the same
treatment.
The NNM database still contains the REMOVED objects and customer is in
a quandary about what to do....HP gives a procedure to rid the DB of
these type problems(but seemingly does not) and I have indicated a
procedure that did remove such entries on my machine. Customer will
call HP support for further understanding of problem. I indicated that
I would also pursue to better understand problem.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _30__ mins.
Talked further with customer who indicated that he was going to
pursue with HP support the difference between my recommendation for
cleaning up his NNM db and the HP recommendation.
(Many objects are marked as REMOVED in db and seem to be preventing
the Nways daemons from discovering Nways devices properly).
Customer called again and indciated that he had now deleted an 8265
from the Nways Device submap and the IP submap and the rediscovery
seemed to work OK. Customer will very further correction for MSSs
and call back.
I received message to callback customer(or page).
I paged customer 2 times during the day today(8/13) with no response.
Page again later.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _15__ mins.
Customer called to update status on HPUX platform with NWays V2.
The customer is following recommendations given to eliminate unnecessary
NNM maps, down to default now(1), and also performing cleanup operations
on the NNM DB. THe Nways devices that were manually deleted previous to
this activity are now rediscovered and showing up in the Nways device
submap as well as ATM submap.
THe customer is pleased that good progress is being made to resolve the
map problems. CUstomer will check out system and maps further and
call back with update on status.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _25__ mins.
Customer questions in email how to determine the physical location of
a device with a certain MAC and IP. I responded to the customer via
email with a recommended procedure for isolating to the actual port
for a given MAC and IP of a device. I covered the basic procedure as
well as actual operations in Nways and NV for obtaining the port
location.
Q:
A:
No further update on ATM map progress...assume still evaluating or no
longer a problem. Check back with customer for status update.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _06__ mins.
Sent email checking on status. Waiting for customer response.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _40__ mins.
Customer has performed HPUX maintenance on platform and and is now
having NNM and Nways map problems. Customer tried clearing the ATM
Topology DB but it stopped before completion with an error message:
"No Handler for Exception: no database is assigned to this location..."
(customer used /usr/CML/bin/ahmclearatm script)
This kind of error occured last occasion for cleaning up the Nways maps
and we were successful in this task by ignoring the error message and
running NNM ovmapcount and ovtopofix -R on the database(removes
REMOVED objects).
I recommended customer proceed as before and report back status.
Addionally, customer was having problem running "ossvrping" for
OBjectstore server due to a missing library. On checking the SHLIB_PATH,
it was discovered that this path was incorrect in /etc/profile....was
missing the trailing "lib" in the SHLIB_PATH. Customer corrected and
now the ossvrping works OK....server running OK.
Customer will report back on status or for help cleaning up NNM DB.
Q:
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-99/01/01-01:01--FI
Support Line: _20__ mins.
Following recommending action for customer to take, customer has
responded with email indicating that the maps are starting to look much
better especially in the ATM submap. THe customer procedure involved
cleaning up the NNM DB which actually reduced its size dramatically
so that his system should be perfoming much better as well.
Customer indicated that he would update status further as appropriate.
Waiting for customer response.
Q:
IBM Feedback:
Database problems resolved.
PMR closed.
S e a r c h - k e y w o r d s:
nnm ovtopofix REMOVED ahmclearatm
WWQA: ITEM: RTA000159451 ITEM: RTA000159451
Dated: 10/1999 Category: NWAYSAIX
This HTML file was generated 2000/11/30~13:34:12
Comments or suggestions?
Contact us