Specifications

ENT_MLE_015989 - Ed 02_2014-10-13
Chapter 13: Topology – Network Services
26/64
Alcatel-Lucent Enterprise Communication Solutions
April 2014 Offer
– Topology views may cover every network element and application. Alarm status is
indicated by a change in the color of the associated icon. In depth analysis of the alarm
status may be conducted, either by using the hypervisor event manager, or by using the
proprietary tools designed by the network item provider. Hypervisors do not provide
configuration capabilities because this is specifically linked to each network item.
– Specific Alarm Handling: This is a customized solution specifically defined by the customer.
The customer will handle all the global network alarms with specific tools created for their
help desk organization. This usually requires in-house development by the customer.
Functional options and how they work on the Alcatel-Lucent OmniPCX Enterprise
Communication Server
Functionalities vary for each hypervisor. They depend on the generic capabilities of the hypervisor
and on the capabilities of the hypervisor agent that are developed by Alcatel-Lucent, partners, or the
customer.
Auto-discovery and Topology
The hypervisor uses ping and SNMP Get commands to discover IP components. The hypervisor
replies to SNMP Get commands with Alcatel-Lucent-specific object IDs or specific extended attributes
allowing for the discovery of Alcatel-Lucent IP components and represented by Alcatel-Lucent specific
icons on the topology map.
Hypervisors may poll IP components to get their status and display the related icons with their
related colors.
The status of IP components may be obtained by the hypervisor based on answer (green)/no answer
(red) or more precisely by using the Alcatel-Lucent-proprietary status attribute (there is no standard
status attribute defined in MIB II) or status trap. MIB extensions and hypervisor agent development
are required to handle the extended status attribute or status trap functions.
Alarm Handling
Alarms are sent by IP components using SNMP traps. Alcatel-Lucent uses a specific SNMP trap
(defined in the SNMP standard) that allows equipment providers to create proprietary alarm traps to
notify the hypervisor of alarms.
Security
The customer can define communities. SNMP requests can be done only between hypervisor and
OmniPCXs belonging to the same community. The members of one community share the same
community name. The community name is sent with each SNMP message and acts as a clear text
password. SNMP requests with an unknown community name are rejected. The new SNMPv3:
– Restricts access of MIB information to authenticated hypervisors only. A hypervisor
requires a SNMPv3 account (login name and password) declared in the Communication
Server configuration. The hypervisor agent, which carries out specific functions (e.g.
security), must also be declared. A maximum of 10 SNMPv3 user accounts can be
configured on the hypervisor agent
– Provides an encryption process for SNMP Protocol Data Units (PDUs). PDUs can contain
address and control information. To cipher the PDUs, a hypervisor must declare a SNMPv3
passphrase in the CS configuration and in the hypervisor agent configuration.
3.2.11 Business continuity in case of Communication Server switch-over
Network established ongoing communications are maintained, even if an IP/ABC Link or hybrid TDM
Link is involved in the communication. Thus, business continuity is offered between endpoints (IP
Touch, legacy devices/ trunks, SIP devices/trunks, MyIC clients for OpenTouch users, equipment