04-06-2009 04:49 AM
I am getting SNMP traps from our Cisco Cerent ONS 15454 . See below
Generic: 6; Specific: 5120; Enterprise: .1.3.6.1.4.1.3607.6.10.30;
Variables:
[1] private.enterprises.cerent.cerentProducts.cerent454Mib.cerentCommonObjects.cerent454CommonObjectsGroup.cerent454NodeTime.0 (OctetString): 20090404035108D
[2] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmState.1.5120 (Integer): notAlarmedNonServiceAffecting
[3] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmObjectType.1.5120 (Integer): ne
[4] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmObjectIndex.1.5120 (Integer): 1
[5] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmSlotNumber.1.5120 (Integer): 0
[6] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmPortNumber.1.5120 (Integer): unknown
[7] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmLineNumber.1.5120 (Integer): 0
[8] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmObjectName.1.5120 (OctetString): SYSTEM
[9] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmSeverity.1.5120 (Integer): notAlarmed
[10] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmStatus.1.5120 (Integer): transient
[11] private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Objects.cerent454AlarmGroup.cerent454AlarmTable.cerent454AlarmEntry.cerent454AlarmServiceAffecting.1.5120 (Integer): nonServiceAffecting
[12] snmpV2.snmpModules.18.1.3.0 (IpAddress): 192.168.*.*
Any idea why we are getting the alarms??
Francisco
04-06-2009 05:06 AM
also
Long Descr.:
"Logout of User"
Variables:
1: cerent454NodeTime
Syntax="Display String"
Descr="Indicates current local time as reflected by
the Cisco OTBU equipment. The format this scalar is
YYYYMMDDhhmmss{S/D}. E.g.,
20011103133453D means 1:34:53 PM PDT on 03/Nov/2001
19990614095436S means 9:54:36 AM PST on 14/Jun/1999.
If the last octet is S then the time is standard time.
Otherwise it is D to indicate it is daylight saving
time, if applicable"
2: cerent454AlarmState
Syntax="CerentNotificationClass"
Descr="Specifies alarm severity and service
affecting status ( SA/NSA ). Only
{minor|major|critical}+{NA|NSA} alarms and
standing conditions will be represented here."
3: cerent454AlarmObjectType
Syntax="Cerent454EntityClass (Integer) "
Descr="This will indicate what is the type
of the entity which raised this alarm.
( E.g., DS3, etherBridge, VT-TERM, etc )
The NMS is expected to use this value
to decide which table to poll for
further info about the alarm"
4: cerent454AlarmObjectIndex
Syntax="Integer"
Descr="Every alarm is raised by an object and
this object is an entry in a specific
table. This is the index of the object
in that table E.g., if the alarm is interface
related, this index is the index of the
interface in the interface table."
5: cerent454AlarmSlotNumber
Syntax="Integer"
Descr="This will indicate what is the slot
of the object which raised this alarm.
If not relevant to the alarm, will be
zero."
6: cerent454AlarmPortNumber
Syntax="CerentPortNumber"
Descr="This will indicate what is the port
of the object which raised this alarm."
7: cerent454AlarmLineNumber
Syntax="Integer"
Descr="This will indicate what is the port
of the object which raised this alarm.
If not relevant to the alarm, will be
zero."
8: cerent454AlarmObjectName
Syntax="Display String"
Descr="TL1-style user-visible name which uniquely
identifies an object in the system"
9: cerent454AlarmSeverity
Syntax="CerentAlarmSeverity"
Descr="Specifies severity of the alarm
being sent out."
10: cerent454AlarmStatus
Syntax="CerentAlarmStatus"
Descr="Represents if the alarm is currently raised
or cleared."
11: cerent454AlarmServiceAffecting
Syntax="CerentAlarmServiceAffecting"
Descr="Specifies whether the alarm that is being
sent out is Service Affecting (SA) or Non-
Service Affecting (NSA)."
04-06-2009 06:34 AM
Your second posting notes the condition that is being reported as "logout of User". according to the Cisco ONS 15454 DWDM Reference Manual, Release 9.0
Appendix B, Administrative and Service States (see http://www.cisco.com/en/US/partner/docs/optical/15000r9_0/dwdm/reference/guide/454d90_adminstates.html), that condition is noted as follows:
3.3.5 ADMIN-LOGOUT
The Admin Logout of User (ADMIN-LOGOUT) condition occurs when the administrator logs off a user session.
This transient condition does not result in a standing condition.
So, that's what's being reported to your network management station. It is a transient condition and not generally useful except in auditing situations. You should be able to suppress or filter it from being displayed without affecting operations or management of your system.
Hope this helps. Please rate this post if it does.
04-06-2009 06:59 AM
Marvin,
thanks from your reply. I am more interested in the first posting. I need to work out what the sting MIB sting "Enterprise: .1.3.6.1.4.1.3607.6.10.30" means. so far i have worked out, the traps above is relating to a port number on one of the slot on the ONS but the traps doesnt provide enough information as to what the problem is with the port..
I have looked at the CERENT-454-MIB, but dont have enough information to know the root of the problem.
Please help.
Francisco.
04-08-2009 10:14 AM
Francisco,
I hope this helps youâ¦
I think your first reply and mklemovitch's reply describe the trap.
I believe the root cause is a user has logged off the chassis. That happens every time someone disconnects CTC (Cisco Transport Controller) and possibly other management tools you may be using. I see these daily and analyzed it a long time ago. :-)
Also, Object ID .1.3.6.1.4.1.3607.6.10.30 is type âObject Identityâ with nameâ¦
â.iso.org.dod.internet.private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Eventsâ
And the description is âPlace holder for all notifications of Cisco ONS 15454â. It is a partial object.
I believe the full object is .1.3.6.1.4.1.3607.6.10.30.0.5120 â.iso.org.dod.internet.private.enterprises.cerent.cerentProducts.cerent454Mib.cerent454Events.cerent454V2Events.logoutOfUserâ.
It is just indicating that a user has logged out. It looks to me like most Cerent traps include a number of variable bindings whether they are useful to you or not. The following 3 variables show that it is not an issue with a port but relates to the âSYSTEMâ.
[5]⦠cerent454AlarmSlotNumber.1.5120 (Integer): 0
[6]⦠cerent454AlarmPortNumber.1.5120 (Integer): unknown
[8]⦠cerent454AlarmObjectName.1.5120 (OctetString): SYSTEM
⦠with .0.5120 appended to likely reference the parent trap ID but I'm assuming that.
04-13-2009 01:35 AM
thanks guys...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide