SNMP management - Detailed description

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Version 02, October 2008

SNMP management Detailed description Table of contents Com Server SNMP Implementation SNMP Processes Com Server SNMP Agent TRAP Processing SNMP Event Trap SNMP Status Trap TSC-IP & e-Reflexes SNMP Implementation SNMP Versions Alcatel-Lucent Proprietary MIB Properties SNMP Agents and SNMP Versions Compatibilities

Com Server SNMP Implementation SNMP Processes On the Com Server, the SNMP agent and TRAP generation are achieved distinctly by two different processes: snmpd corresponds to the SNMP agent. It answers to the supervisor SNMP requests. Data in the Com Server MIB is readable but not writable incid2trap generates the SNMP TRAP according to the management of the incidents configured in MAO Com Server SNMP Agent Communities A community name is a character string used to identify exchanges between the SNMP supervisor and the SNMP agent. The default string community is “public”. As of R6.2, the community name is checked. When the check fails, the request is not answered.

1 of 8

26/11/2013 08:05

SNMP management - Detailed description

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Notes: As of R7.1, the community names "public" and "private" are forbidden when the SNMP version of the PCX SNMP agent is SNMPv2c (see: SNMP management / Configuration procedure / Declaring SNMP Agent Running on the Com Server). The community name is not used when the SNMP version of the PCX SNMP agent is SNMPv3. Access Only read accesses are allowed (Get and Get-next requests). No write access can be performed (Set request). 802.1 p/q VLAN tagging is enabled on Com Server SNMP requests may be tagged or not. Current VLAN value is used. Null priority (low priority) is always used in 802.1 tags for outgoing SNMP packets.

TRAP Processing SNMP Event Trap On each network node, the incid2trap process converts CMIP alarms into SNMP traps and transmits them to the SNMP supervisor according to incident filters configuration. All CMIP alarms can be converted into a single SNMP trap (called an “event trap”). CMIP alarm attributes are converted into event trap parameters. SNMP event traps can be sent in two different formats: Compact format: this format is for information only. It can be used to display alarms in an event window on the SNMP supervisor Extended format: this format is used to process alarms for dedicated applications. This is the case, for example, of clients with specific management Note: The format choice is configured in the Alcatel-Lucent OmniPCX Enterprise Communication Server. See: SNMP management / Configuration procedure / Declaring Supervisors SNMP Status Trap The SNMP agent also calculates the status of each network node and generates an SNMP trap containing the node status parameter (these traps are called “status traps”). Note: Event traps are always sent to the SNMP supervisor when trap processing is activated but It is possible to select whether status traps are sent or not. This is specified in the Alcatel-Lucent OmniPCX Enterprise CS configuration. See: SNMP management / Configuration procedure / Declaring Supervisors

2 of 8

26/11/2013 08:05

SNMP management - Detailed description

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

TSC-IP & e-Reflexes SNMP Implementation SNMP Set requests Although write requests are allowed for specific variables in MIB, these values are volatile inasmuch as they are not stored locally in the piece of equipment. For security reasons and for administration convenience, the PCX system is in charge of setup at device initialization with a UA specific message SET-PARAM. This contains user name, contact and location information. 802.1 p/q VLAN tagging is enabled on IP-Phone devices SNMP requests may be tagged or not. The current VLAN value is used. Null priority (low priority) is always used in 802.1 tags for outgoing SNMP packets.

SNMP Versions Three versions of SNMP can be used: SNMPv1, SNMPv2c and SNMPv3 (as of R7.1). The first two versions offer common features, but SNMPv2c includes additional features for more security. SNMPv1 is defined in the standard RFC 1157. SNMPv2c is defined in the standard RFC 1442. When SNMPv1 is used, an SNMP agent allows any SNMP supervisor to read MIB information coming from the SNMP agent. When SNMPv2c is used, an SNMP agent allows only SNMP supervisors using the same community name to read MIB information. SNMPv3 differs from SNMPv2c in its ability to: Restrict MIB information access to authenticated SNMP supervisors only (see RFC 3414). For authentication, SNMP supervisors must have an SNMPv3 account (login name and password) declared in Alcatel-Lucent OmniPCX Enterprise CS configuration (see: SNMP management / Configuration procedure / Declaring Supervisors), and the SNMP agent must also be declared (see: SNMP management / Configuration procedure / Declaring SNMP Agent Running on the Com Server). For the SNMP agent, a maximum of 10 SNMPv3 user accounts can be configured Provide an encryption process for SNMP PDUs (Protocol Data Unit) (see RFC 3412). To cipher the SNMP PDUs, SNMP supervisors must have a SNMPv3 passphrase declared in Alcatel-Lucent OmniPCX Enterprise CS configuration (see: SNMP management / Configuration procedure / Declaring Supervisors) as well as the SNMP agent (see: SNMP management / Configuration procedure / Declaring SNMP Agent Running on the Com Server) Within the Alcatel-Lucent OmniPCX Enterprise CS, the SNMPv3 use is incompatible with versions SNMPv1 and SNMPv2c. The Alcatel-Lucent OmniPCX Enterprise CS cannot restrict access to a range of specific MIB information. This implies that all MIB information must be restricted in the AlcatelLucent OmniPCX Enterprise CS environment. Only one SNMP version is available on the AlcatelLucent OmniPCX Enterprise CS at the same time (for SNMP agents and SNMP traps sending).

3 of 8

26/11/2013 08:05

SNMP management - Detailed description

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Note: The MIB information which can be queried and set by SNMP supervisors are described in MIB-II (Management Information Base Version 2) defined in RFC 1213. There is no additional MIB information available (neither VoIP specific nor proprietary variables) in SNMP agents running in TSC-IP or e-Reflexes sets.

Alcatel-Lucent Proprietary MIB Properties The Management Information Base (MIB) is a collection of data (also called objects) defined for an IP device. MIB values can be monitored by an external application, using the SNMP protocol and Object Identifiers (OID). An OID identifies each object of the MIB and defines their access path. The Alcatel-Lucent OmniPCX Enterprise Communication Server includes an MIB description file named A4400-RTM-MIB.txt, registered in the directory /etc/snmp/mibs/export. Available as of R9.0, this file defines objects whose values can be monitored by an external application. Note 1: The directory /etc/snmp/mibs/export also contains two other MIB description files: HPOV-NNM.txt and TRAP-MIB.txt. An external application (SNMP supervisor) can send requests to the Com Server SNMP agent to obtain the value of objects defined in the Alcatel-Lucent OmniPCX Enterprise Communication Server MIB. The Com Server SNMP agent, in turn, sends an answer with the requested values, to the external application The Alcatel-Lucent OmniPCX Enterprise Communication Server MIB is a structured tree including: Standardized branches with the objects typically supported by IP devices. The list of objects is provided: SNMP management / SNMP: Supported entries An Alcatel-Lucent proprietary branch which provides specific information on Alcatel-Lucent OmniPCX Enterprise Communication Server operation. MIB Tree Structure Example

4 of 8

26/11/2013 08:05

SNMP management - Detailed description

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Before R9.0, objects available in the Alcatel-Lucent proprietary branch are: Object Name

Definition

pbxMibVersion

Indicates the MIB version used

pbxState

Indicates the highest severity level of the incidents registered in the Alcatel-Lucent OmniPCX Enterprise Communication Server. Available values are: INDETERMINATE, CRITICAL, MAJOR, MINOR, WARNING or NORMAL Note 2: The SNMP Trap licensing lock is required to retrieve values from an external application.

As of R9.0, additional objects are available in the Alcatel-Lucent proprietary branch. These objects provide real time information either for the whole system or per IP domain: For the whole system:

5 of 8

Object Name

Definition

pbxRole

Indicates the PCX role. Available values are: INDETERMINATE,

26/11/2013 08:05

SNMP management - Detailed description

Object Name

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Definition MAIN, STAND-BY, ACTIVE_PCS or INACTIVE_PCS where: MAIN and STAND-BY values are used to indicate the Com Server role ACTIVE_PCS and INACTIVE_PCS values are used to indicate the Passive Communication Server (PCS) status Note 3: The INDETERMINATE value is not sent in response to an SNMP request when the corresponding SNMP agent is not started

sipRegSets

Indicates the number of SIP terminals registered in the PCX, as well as SIP terminals not defined in PCX configuration (provided that authentication is not required for SIP terminal registration)

sipUnregSets

Indicates the number of SIP terminals not registered in the PCX. This counter is equal to the number of SIP terminals configured in the PCX minus the number of SIP terminals registered in the PCX. If authentication is not required for SIP terminal registration, this counter may be negative (when there are more self registered SIP terminals than SIP terminals configured in the PCX).

setsInService

Indicates the number of sets in service. This counter includes all types of set but not SIP sets.

setsOutOfServices

Indicates the number of sets out of service. This counter includes all types of set but not SIP sets.

Per IP domain:

6 of 8

Object Name

Definition

confAvailable (1)

Indicates the number of available conference circuits (in service and not busy)

confBusy (1)

Indicates the number of busy conference circuits

confOutOfOrder (1)

Indicates the number of conference circuits out of service

dspRessAvailable (2)

Indicates the number of available DSP resources (i.e. compressors)

dspRessBusy (2)

Indicates the number of busy compressors

dspRessOutOfOrder (2)

Indicates the number of compressors out of service

dspRessOverrun (2)

Indicates the number of unsuccessful requests for free compressors due to insufficient PCX resources. Every time a compressor cannot be provided by the PCX (for lack of resource), this counter increases by 1. On Com Server start-up or when a Com Server switchover occurs, this counter is reset to 0.

CacAllowed (2)

Indicates the number of allowed external communications

26/11/2013 08:05

SNMP management - Detailed description

7 of 8

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

Object Name

Definition

CacUsed (2)

Indicates the current number of external communications This counter is only used if the number of allowed external communications is limited, if not its value is 0

CacOverrun (2)

Indicates the number of Call Admission Control (CAC) overrun: every time a communication is not allowed by CAC counters, this counter increases by 1. On Com Server start-up or when a Com Server switchover occurs, this counter is reset to 0. This counter is not configured if the number of allowed external communications is unlimited (no control, value: -1)

(1): These parameters take into account all conferences (regardless of their type and size) but not three-party conferences (2): These parameters can also be checked from the cnx dom command used to display information on IP telephony domains, with the following correspondences: Object Name

Corresponding Parameter (cnx Command)

dspRessAvailable

comp alw

dspRessBusy

comp use

dspRessOutOfOrder

comp out

dspRessOverrun

comp ovr

CacAllowed

allowed

CacUsed

used

CacOverrun

cac over

These additional objects are only available when the Com Server takes the Main role. When a Stand-by Com Server or Passive Communication Server (PCS) take over, the only available object (as soon as the SNMP agent is started) is: pbxRole When a Com Server receives a request from an external application for one of these additional objects: If the request applies to the pbxRole object, the Com Server answers the request If the request applies to another additional objects, the Com Server only answers when it takes the Main role. A Com Server being started (telephone feature not started), or Stand-by Com Server and PCS (in active or inactive mode) cannot provide information on these objects

SNMP Agents and SNMP Versions Compatibilities The table below indicates which SNMP versions are supported by SNMP agents according to their

26/11/2013 08:05

SNMP management - Detailed description

8 of 8

https://www.technical-knowledge-base.com/kmdoc/upload/km_dmodule...

location (Com Server, TSC-IP and/or e-Reflexes set). This table presents SNMP agent location in lines and SNMP version in columns. Com Server

TSC-IP

e-Reflexes

SNMPv1

Yes

Yes

Yes

SNMPv2c

Yes

No

No

SNMPv3

Yes

No

No

26/11/2013 08:05