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: HI3641__
********************** 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:
7025 f50 421
problems regarding armon trap alert configuration
=-=-=> 08/27/98 <=-=> 07:31:21 CDT <=-=-=> Nancy Tapia <=-=-=-=-=
A:
Customer Rep: Ernie Obrist at 215-574-3841
Problem: Unable to set-up an RMON trap
Software: AIX v4.2.1
NetView, v4.0
NWays Manager for AIX, v1.2.1
Action Taken: I searched the Networking Web page with no help.
Moving this to AXLAN,12U for assistance.
Thanks, Harry
A:
We have set up the Rules Set Editor in Netview and it is working for
traps we have identified. We have also set up Alarms in Remote Monitor
and it is working for entries we have identified. We are ow trying to g
et the Alarms in Remote Monitor or the RMON Agent (8260 HTMAC) to send a
n SNMP trap to Netview so we can configure it into out Ruleset Editor.
Please help, we are struggling, thanks-EO
A:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-98/05/15-14:40--FI
Support Line: _20__ mins.
CUstomer trying to get RMON traps after having setup the RMON alarm
through the LanReMon application.
The trap never is presented in event desk. There is a trap reflecting
an authentication trap from the RMON in 8260 HTMAC.
The communities seem to be incorrect.
WOrking to get communities set properly in HTMAC.
Q:
A:
This may or may not be related information:
The HTMAC that we are using in this scenario is the only one in the 8260
and is therefore the ADMM administator with an ip/hostname=hubclf/172.1
8.241.130. There also is a RMON probe address assigned to this HTMAC in
it's configuration ip/hostname=hubclf_tr1/172.18.244.200. Nways Remon
discovered a probe at hubclf/172.18.241.130 and we get a "No response fr
om device" at the probe address of hubclf_tr1/172.18.244.200. (We "creat
ed" this probe and added it ourselves earlier, the hubclf/172.18.241.130
was discovered by ReMon.
Therefore, all of our efforts thus far have been working with the 172.18
.241.130 address.
FURTHERMORE; When we select 172.18.241.130 and bring up the Device Admin
box (aka-Probe Admin in Remon Users Guide, ref pg3-6) the only tab that
is NOT greyed out, IOW the only tab we can work with, is Routing. Under
Routing, all we can work with is Echo Interval. The other tabs appear t
o be where we need to further configure for Traps and Community Access a
s references in the Nways Remon Users Guide.
All this leads us to believe we may not have the probe identified prope
rly in the HTMAC/8260 or we have a potential defect with the Nways ReMon
Device Configuration screen access.
We will try changing the RMON probes address to match the HTMAC's ip add
ress, IOW make them both 172.18.241.130, and see if we can get access to
the other screens.
IBM Feedback:
-HAYS, DO -FORMAT 0973-L10R/-------P3S3-98/05/15-14:40--FI
Support Line: _60_ mins.
Customer problem seems to be surrounding contact to IP for ADMM
rather than IP for RMON probe(different for HTMAC) and through the
RMON application an attempt to configure the probe using the IP
of the ADMM rather than the HTMAC.
Customer worked to get IP contact with HTMAC and the RMON application
then allows probe administration panels to communicate with the RMON
probe. The documented communities for access to the HTMAC were used
as per HTMAC Users Guide chap 8.
Once customer used community "admin" set by default for full probe
access, the RMON application allowed the panels for setting trap
community to the value used by the NV4AIX machine...traps were then
received in to the event desk.
CUstomer is now pleased to have RMON trap operation working.
PMR closed.
S e a r c h - k e y w o r d s:
RMON community htmac
WWQA: ITEM: RTA000152165 ITEM: RTA000152165
Dated: 08/1998 Category: NWAYSAIX
This HTML file was generated 99/06/24~12:43:40
Comments or suggestions?
Contact us