[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
Moderator: | NETCAD::COLELLA DT |
|
Created: | Wed Nov 13 1991 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4455 |
Total number of notes: | 16761 |
2957.0. "DECrepeater 900tm traps since upgrading" by CSC32::MAULUCCI () Mon Nov 06 1995 10:56
A customer that I am assisting has a DECrepeater 900TM in a DEChub 900.
The customer pulls up hubwatch through Polycenter netview, his
DECrepeater was previously at v1.1.0 firmware. Since upgrading the
firmware to V2.0.0 he has been seeing the traps attached below, the
information was handwritten by the customer and fax'd to me so there
may be some inaccuracies with the information because of that:
A RMON falling alarm repeater mau repeater information
repeater mau total media unavailable 0
fell below threshold 1; value = 21: (sample type = 2)
specific = 2
enterprise= rmon 1.3.6.1.2.1.16
A RMON rising alarm: repeater repeater information repeater health text
changes 0
exceeded threshold 1; value 40 (sample type =2; alarm index =4)
specific: 1
generic : 6
catagory: threshold events
enterprise: rmon 1.3.6.1.2.1.16
source: agent (A)
hostname: rep2.shost.ksc.com
severity: critical
RMON rising alarm
repeater extensions, repeater basic package, repeater repeater
information 5.0
exceeded threshold 1; value 83 (sample type =2; alarm index = 5)
specific: 1
generic : 6
catagory: threshold events
enterprise: rmon 1.3.6.1.2.1.16
source: agent (A)
hostname: rep2.elrio.ksc.com
severity: critical
MTI.fddi.ksc.co N elrio2.elrio.ksc.com
reported different link address than obtained from mti.fddi.ksc.com by
snmp
specific: 58982401 (hex: 3840001)
generic : 6
catagory: mode configuration events
enterprise: netview 1.3.6.1.4.1.2.6.3.1
source: network (N)
hostname: net1.fddi.ksc.com
severity: indeterminate
I have some questions regarding this,
1. is this a repeater or polycenter issue
2. it appears that a device reported a different link address than
another device. Is this what is causing the alrams ?
Any suggestions clarifications (not sure what all of the fields mean)
are welcomed.
Thanks,
Gene
T.R | Title | User | Personal Name | Date | Lines
|
---|