|
|
This appendix deals with the management elements offered by the SNMP agent.
Configuration using the SNMP agent enabling these elements to be obtained is described in the section on implementing the SNMP agent in the Configuration Manual.
The trap is one of the five PDUs (Protocol Data Units) of the SNMP protocol.
It is sent at the initiative of the SNMP agent to one or more managers upon the detection of a special event.
This appendix describes the circumstances under which each of the standard or private traps is transmitted.
The "Cold Start" trap (generic-trap = 0) is generated with each start-up following a hardware reset or a power-up. It is not generated in the case of software tests.
The "Warm Start" trap (generic-trap = 1) is not available in V12.2.
The "Link Down" trap (generic-trap = 2) is generated when the physical line level is out of service (see event 00 of family 04 in Appendix A, Description of Outstanding Events).
The "Link up" trap (generic-trap = 3) is generated when the physical line level is established (see event 01 of family 04 in Appendix A, Description of Outstanding Events).
The "Authentication Failure" trap (generic-trap = 4), if it is configured for transmission, is generated when the SNMP agent receives a request from an unauthorized manager or a request containing an incorrect community string.
The "Egp. Neighbor Loss" trap (generic-trap = 5) is not available in V12.2.
To the extent that an event has been selected in class 5, the corresponding private trap is transmitted as soon as the equipment generates this event.
A private trap transports four variables defined in the private MIB in the trap group. These variables specify the line number, the family, the event and additional information..
The following table describes the association of the events with the six private traps (refer to Appendix A, Description of Outstanding Events, for details on each event).
In this table, the columns have the following meanings:
| Trap | Name of trap |
| N° | Value of the specific trap variable contained in the trap |
| Code | Hexadecimal code of the event family |
| Family | Designation of event family |
| Events | List of events of the family associated with the trap |
| Trap | No. | Code | Family | Events |
|---|---|---|---|---|
| General | Families/Events not mentioned in traps 6 to 10 | |||
| Node status | 6 | 00 | Trouble report | 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0D, 0E, 0F, 10, 11, 12, 13 |
| Line status | 7 | 02 | Synchronous-signalling | 30, 50, 51 |
| 03 | Synchronous- X.25 procedure | 08, 09 | ||
| 04 | Link | 00, 01 | ||
| 0D | MLP | 0E, 0F | ||
| 0E | PSTN procedure | 0A, 0C | ||
| 12 | ISDN procedure on D-channel, line level | 00, 01, B0, B1, B2 | ||
| 14 | Ethernet Bridge function and IP Router Function | 0B, 0C, 10, 11 | ||
| 15 | DLC/MTR procedure of FRAD and RAD | 00, 01 | ||
| Charge | 8 | 00 | Trouble report | 20, 21, 22, 23 |
| 01 | Management | D1, D2 | ||
| 12 | ISDN procedure on D-channel, line level | A1, A3 | ||
| 15 | DLC/MTR procedure of FRAD and RAD | 05, 06, 07, 08 | ||
| Management-Security | 9 | 00 | Trouble report | 0C |
| 01 | Management | 16, 17, 30, 37, E3 | ||
| 18 | Configuration function | 00, 03, 04, 05, 06, 07, 08, 16, 17, 18, 19, 1E, 1F, 20 | ||
| Services | 10 | 0F | CVF/ESV procedure | 43 |
| 10 | CVF/N4 procedure | 51, 52, 5A | ||
| 11 | CVF/IR procedure | 00, 02 | ||
| 15 | DLC/MTR procedure of FRAD and RAD | 03, 04 | ||
| 16 | Compression procedures | 00, 01, 02, 03 |
This section deals briefly with the features of the SNMP agent as regards the groups defined in RFC 1213. Refer to the contents of the MIB for details on the variables and their meanings.
The size of "sysContact" and "sysLocation" objects is limited to 34 characters.
The size of the "sysName" object is limited to 14 characters.
An interface represents a physical line.
For the physical lines, the "ifIndex" of the table corresponds to the line number plus 1 (for example, ifIndex = 2 corresponds to line 1).
The SNMP agent of a module proposes only the lines located on this module.
SET requests on the "ifAdminStatus" object are accepted except on the LAN line.
Obsolete group, not available.
SET requests on the "ipForwarding" and "ipDefaultTTL" objects are not available.
As per RFC 1213.
Not applicable
As per RFC 1213.
As per RFC 1213.
Not applicable.
The "snmpEnableAuthenTraps" object is initialised by the value read in configuration. The SETs are authorized on this object to modify the behavior of the agent with regard to the transmission of "Authentication-Failure" traps.
However, the value placed by a set on this object is not stored in the configuration and is thus valid only until the next initialization of the equipment.
Part of the groups defined in the Cisco private MIB is proposed by the SNMP agent in V12.2. This appendix deals briefly with the available groups. Refer to the contents of the MIB for details on the variables and their meanings.
These groups concern the outstanding events and statistics.
The SNMP agent provides access to information also available through the "Outstanding Events" management function.
This group specifies the type of the last equipment reset (deliberate, involuntary or hardware reset) as well as the information relative to this reset.
This table indicates, by family, the number of events stored and also allows the elimination of all the events stored in this family.
The maximum number of outstanding events stored per family is six. However, the total number of events stored, for all the families, is limited to three times the number of families.
In each family, when the maximum number of storable events has been reached, the most recent events overwrite the earlier ones with the exception of the first event generated since the last deletion.
For each event, the family, the type of event, the time of appearance, the associated line number as well as additional information are entered.
If no line is associated with the event, the line number is 255.
This group defines the variables transported by the private traps. It allows no direct read access.
The SNMP agent proposes access to information also available through the "Statistics Distribution" management function (statistics type 1 and 2).
This group includes information and actions on the general status of the statistics function of the equipment and on the statistics at the level of the management MIB:
This group includes the various information specific to the equipment and not affected by a reset of the Stat group counters (number of buffers, CPU load, etc.).
It comes from the "Equipment activity zone" (see Statistics Distribution management function).
This group includes the counters specific to the traffic switched at the equipment level.
It comes from the "Switched traffic zone" (See Statistics Distribution management function).
This table includes, for each configured line of the equipment, the counters specific to the traffic on that line.
It comes from the "Line zone" (see Statistics Distribution management function).
This table contains, in 80 bytes, a summary of the line status.
This table specifies for each line of an MLP trunk, the trunk number, the line type (main or secondary) and the status of the trunk.
It is derived from the type 6 buffer (see statistics distribution operation function).
The statistics on an Ethernet line, derived from a type 3 buffer (see statistics distribution operation function) break down into 4 tables indexed by the Ethernet line number:
This table is indexed by the X121 address of the remote end, the encapsulation type on the connection and the identifier of the connection used for characterizing the status of the connection and containing a number of counters (transmitted/received frames, transmitted/received bytes).
This table contains the state of the Off function or the Transparent Bridge (from the type 4 buffer).
This table only contains at V12.2 the status of the router Off or On function (derived from the type 4 buffer).
These statistics are obtained from the type 7 buffer (see statistics distribution operation function) and contains two tables:
The PPP group gives the status of the LCP and NCP protocols, the cause of their disconnection and the result of the negotiation of options.
|
|