Reset Search
 

 

Article

Add traps to Extreme Management Center

« Go Back

Information

 
TitleAdd traps to Extreme Management Center
Objective
How to add third party trap to Extreme Management Center.
Environment
  • Extreme Management Center
  • NetSight Console
Procedure
***Import the MIBs in NetSight:***
1. Place the MIBs into the following directory on the NetSight Server:
Windows:  C:\Program Files\Extreme Networks\NetSight\appdata\System\mibs\MyMibs
Linux:  /usr/local/Extreme_Networks/NetSight/appdata/System/mibs/MyMibs

2. Restart the NetSight server services.
3. Enable Use MyMibs directory on server if using Extreme Management Center.  Administration > Options > SNMP.

***Defining the trap in NetSight***
1. Extract the trap definition from the MIB or trap definition file provided by the third party company.  You can do that using MIB Tools from within NetSight Console.
a)  Start NetSight Console.
b)  Select Tool -> MIB Tools.
c)  In the Find What field to the middle left enter the value you are looking for.
d)  Click the Find button to the right of that field.  The Current Object will display what is needed.

2. Make an entry in the C:\Program Files\Extreme Networks\NetSight\services\trapd.conf file for the Enterprise and also the trap definition itself.


Example:

For Step 1:
I will use ctEntStateOperDisabled from the MIB ctron-entity-state-mib. The following is the MIB entry for the notifications (Traps):
-- Notifications
ctEntStateNotifications OBJECT IDENTIFIER ::= { ctEntityStateMIB 0 }
ctEntStateOperEnabled NOTIFICATION-TYPE
OBJECTS { ctEntStateAdmin,
ctEntStateAlarm
}
STATUS current
DESCRIPTION
"An ctEntStateOperEnabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the ctEntStateOper object for one of its entities has
transitioned into the 'enabled' state.
?
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The ctEntStateAdmin and ctEntStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well to find out whether
there were any known alarms against the entity at that
time that may explain why the physical entity has become
operationally disabled."
::= { ctEntStateNotifications 1 }
ctEntStateOperDisabled NOTIFICATION-TYPE
OBJECTS { ctEntStateAdmin,
ctEntStateAlarm }
STATUS current
DESCRIPTION
"An ctEntStateOperDisabled notification signifies that the
SNMP entity, acting in an agent role, has detected that
the ctEntStateOper object for one of its entities has
transitioned into the 'disabled' state.
The entity this notification refers can be identified by
extracting the entPhysicalIndex from one of the
variable bindings. The ctEntStateAdmin and ctEntStateAlarm
varbinds may be examined to find out additional
information on the administrative state at the time of
the operation state change as well to find out whether
there were any known alarms against the entity at that
time that may have affect on the physical entity's
ability to stay operationally enabled."
::= { ctEntStateNotifications 2 }
?


For Step 2:
The easiest thing in this case is to use MIB Tools to find the definition in the database. In this case I will do a find on ctEntStateOperDisabled. This will take me to ctEntStateOperDisabled=1.3.6.1.4.1.52.4.2.31.1.0.2. From here I know the Enterprise is 1.3.6.1.4.1.(enterprise) -- 1.3.6.1.4.1.52
Edit the trapd.conf file. At the top you will see a section for Enterprise Definitions. In this case Cabletron is already defined so I did not need to make one. If the trap belongs to a different enterprise then I would just make a new OID_Alias Entry: 
?
#####################################################################
# Enterprise Definitions
#####################################################################
OID_ALIAS Cabletron .1.3.6.1.4.1.52
OID_ALIAS ctronTrapeze .1.3.6.1.4.1.52.4.15 
OID_ALIAS Enterasys .1.3.6.1.4.1.5624 
OID_ALIAS snmpTraps .1.3.6.1.6.3.1.1.5 
OID_ALIAS rmonEventsV2 .1.3.6.1.2.1.16 
OID_ALIAS dot1dBridge .1.3.6.1.2.1.17 
OID_ALIAS entityMIBTraps .1.3.6.1.2.1.47.2

The next step is to add the trap definition to the end of the file. Each trap definition entry will contain the following information:
EVENT -- Uniquely defines the trap.
FORMAT -- How is the trap viewed and how are the trap variables (varbinds) displayed 
SDEC and EDESC -- description of the trap.
For our trap I will define the following entry:
#
#
EVENT ctEntStateOperDisabled .1.3.6.1.4.1.52.4.2.31.1.0.2 "LOGONLY" Normal 
FORMAT The SNMP agent is now disabled: State Admin $1, State Alarm $2.
SDESC 
An ctEntStateOperDisabled notification signifies that the SNMP entity, acting in an agent role, has detected that the ctEntStateOper object for one of its entities has transitioned into the 'disabled' state.
EDESC
#
#
There are different status entries that you can pull from other trap entries if you do not want "LOGONLY" Normal.
Note for the Format line I entered a value for each entry listed in the OBJECTS section. This will be the information that is returned by the trap.

Once this is completed you will need to restart the NetSight server service as well as the nssnmptrapd service.

How to restart Netsight / Extreme Management Center services on linux or Windows Server Platforms

When you now receive a trap that is defined you will get more useful information in the log.
 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255