OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)
OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)
OXO - Connect - Evolution - 3.1 - SD - MaintenanceServices - 8AL91229USAB - 1 - en - (Glossario de Erros Dos Alarmes Do OXO)
Disclaimer
While efforts were made to verify the completeness and accuracy of the information contained in this
documentation, this document is provided “as is”. To get more accurate content concerning Cross
Compatibilities, Product Limits, Software Policy and Feature Lists, please refer to the accurate
documents published on the Business Partner Web Site.
In the interest of continued product development, ALE International reserves the right to make
improvements to this documentation and the products it describes at any time, without notice or
obligation.
The CE mark indicates that this product conforms to the following Council Directives:
• 2014/53/EU for radio equipment
• 2014/35/EU and 2014/30/EU for non radio equipment (including wired Telecom Terminal
Equipment)
• 2014/34/EU for ATEX equipment
• 2011/65/EU (RoHS)
• 2012/19/EU (WEEE)
Table of
contents Expert Documentation:
Maintenance Services
Chapter 1
Expert Documentation structure
Chapter 2
PBX diagnostic tool
2.1 Overview.............................................................................................................................................10
2.2 Connecting a management computer to the PBX and powering
the PBX................................................................................................................................................ 10
2.3 Accessing the diagnostic mode..................................................................................10
2.3.1 Accessing the diagnostic mode from the web-based tool...............................................10
2.3.2 Accessing the diagnostic mode from the PBX management console.......................11
2.4 Launching the diagnostic test...................................................................................... 12
2.5 Downloading the diagnostic test results........................................................... 12
2.6 Exiting the diagnostic mode...........................................................................................13
Chapter 3
Replacing/Relocating Sets
3.4 IP Phones.......................................................................................................................................... 15
3.4.1 Automatic Set Relocation Retrieve............................................................................................ 16
3.4.2 Automatic Set Relocation Replace.............................................................................................16
Chapter 4
Backup/restore
Chapter 5
System Messages
Chapter 6
PBX start and stop
6.1 Overview.............................................................................................................................................72
6.2 PBX start process..................................................................................................................... 72
6.2.1 Starting a PBX in On state............................................................................................................... 72
6.2.2 Starting a PBX in LoLa boot state.............................................................................................. 72
6.3 PBX stop process......................................................................................................................72
6.4 PBX restart process................................................................................................................ 73
Chapter 7
System Reset
Chapter 8
SNMP
8.1 Overview.............................................................................................................................................78
8.2 Protocol...............................................................................................................................................78
8.2.1 Topology.................................................................................................................................................. 78
8.2.2 Security.................................................................................................................................................... 78
8.2.3 SNMP Trap.............................................................................................................................................79
8.2.4 MIB............................................................................................................................................................. 81
8.3 Configuration.................................................................................................................................82
8.3.1 Configuring the SNMP Service.................................................................................................... 82
8.3.2 Notification Filtering........................................................................................................................... 83
8.4 Supervision..................................................................................................................................... 83
The OXO Connect Evolution Expert Documentation is split into fifteen separated documents. In
addition, the Cross Compatibility document is the reference for detailed status about supported and
unsupported devices and applications.
These documents are:
[2] OXO Connect Evolution Expert Documentation: Hardware: Platform, in- 8AL91219xxxx
terfaces and devices
Summary: this document covers all hardware aspects related to OXO
Connect Evolution. This document also contains commissioning proce-
dures for sets.
[10] OXO Connect Evolution Expert Documentation: OmniTouch Call Center 8AL91227xxxx
Office
Summary: this document provides the description and installation pro-
cedure of OmniTouch Call Center Office. The document also includes
presentation and operation of Announcement, Traceability, and a short
description of Agent, Statistics and Supervisor applications.
[16] Server deployment guide for remote workers using deskphones 8AL90345xxxx
In the present document, cross-references are identified by the number in the first column of the above
table.
Part numbers are given in the last column, where xx corresponds to the language code of the
document.
Outlook is either a registered trademark, or a trademark of Microsoft Corporation in the United States
and/or other countries.
The diagnostic tool is used to verify that OXO Connect Evolution components run correctly. The
diagnostic tool can be launched before installing a software version on the (OXO Connect Evolution.
For readability purposes, OXO Connect Evolution is called PBX in the rest of the section.
2.1 Overview
The PBX supports the following boot modes:
• Application mode: this is the default boot mode
In this mode, all the PBX functionalities are supported and all external applications (OMC, web-
based tool) can connect to the PBX.
• Diagnostic mode: the diagnostic tool is launched to perform the diagnostic test of the PBX hardware
components
In this mode, the PBX does not support its functional operations and external applications (OMC,
web-based tool) cannot be accessed.
5. Click OK
The system reboots and starts the diagnostic tool.
6. Go to the PBX management console to continue the operation.
2.3.2 Accessing the diagnostic mode from the PBX management console
On the PBX management console:
1. During startup, press ctrl^b + ^I to enter the PBX main menu
The main menu is displayed:
3 Replacing/Relocating Sets
Unplug Plug in
"Terminal replacement"
code + password
Defective Replacement
terminal terminal
Unplug Plug in
Plug in
The set is recognized as soon as it has been plugged into the socket.
3.4 IP Phones
When an IP phone is connected to the network, default parameters are configured on the phone set on
connection.
To keep individual user parameters, configuration is required on the phone.
OMC configuration is recommended for large networks to activate the Automatic Set Relocation
Replace service.
Phone 150 is reset and has the same configuration as set 50.
This means that for each IP Phone in the network there is another Phone defined in the system with
the IP Phone’s previous default configuration.
For each IP Phone connected there are two Phones defined in the system. A license is required to
create an IP Phone whether it is connected or not. In this situation, for a system with N users, 2xN
subscribers are defined in the system and 2xN IP Phone licenses are required. If N > 100, the number
of subscribers and licenses would exceed the limits of the system (200).
From the OMC -> System Miscellaneous -> Memory Read/Write -> Other Labels
Enable Noteworthy addressASRRep_IP
Set to TRUE (01)
Note:
By default the Noteworthy address ASRRep_IP is set to FALSE (00)
After a Cold reset default parameters (00) are restored.
When the OMC is configured in this way, more than 100 sets can be configured
Example:
Replace
Phone 50 has been configured earlier. And now a new IP Phone is connected to the LAN. This Phone
is automatically taken into account by the system with a default configuration and is operational.
The phone number 150 is automatically allocated to this phone. The Automatic Set Relocation
Replace service is invoked from the newly connected IP Phone 150 (target) to retrieve the
configuration of phone 50 (source):
Phone 150 is reset and has the same configuration as set 50 and the previous set is deleted.
Note:
Under normal conditions default passwords are not allowed for set relocation services. If the Noteworthy
addressASRRep_IP service is enabled, a default password can be used.
4 Backup/restore
4.1.2 Configuration
• Manual backup:
• In the OMC (Expert View): select Data Saving & Swapping -> Commands -> validate the
backup option
• Automatic backup:
• In the OMC (Expert View): select Data Saving & Swapping -> Data Saving -> enter date, time
and periodicity for backups
• Restore:
• In the OMC (Expert View): select Data Saving & Swapping -> Commands -> validate the
Immediate Restore option
Configuration and user data is restored from the selected recovery point(s).
The recovery point configured from a specific software version can be restored in the system running
on the same major software version (this is the limitation from the internal data saving process). The
restore operation is not supported from the system running on a major software version, which is
different from the software version where the backed up recovery point was configured.
5 System Messages
38 Power CPU EE does not sup- MAIN_CP INFO 0 = High byte of detected Replace the
port RAM less than 512 MB U_SLOT RAM size RAM
INFO 1= Low byte of detected
RAM size
Example:
comp_info: 01 00 FF FF
The detected RAM size is 256 MB.
51 CLOCK PROBLEM Board lo- INFO 0 = type of interface: T0, T2, Check there
cation. DASS2, etc. is no syn-
Clock synchronization problem
chronizing
detected on an add-on module Access
access in the
interface marker
add-on mod-
ules
52 SPECIFIC ACCESS PROB- Board lo- INFO 0 =1: FCS (Frame Check Se- If the fault re-
LEM DETECTED BY AN ISDN cation. quence) 2: CRC (Cyclic Redundan- curs fre-
BOARD LEVEL 2 cy Check) quently,
Access
check the
marker
connection to
the public
network.
58 ISDN BOARD FAULT Board lo- INFO 0 = type of error (not signifi- If the fault
cation. cant) keeps recur-
A level 1 error was detected by
ring, check
the board's OBC Access
the bus wir-
marker
ing.
242 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
243 ERROR ON CLOSING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
244 ERROR ON READING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
245 ERROR ON WRITING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
246 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
247 ERROR ON OPENING VOICE CPU (80) INFO 0 to 3 = type and value of
PROMPT FILE voice prompt
11 END OF START-UP
The system is operational
21 FULL BUFFER MESSAGE CPU (80) INFO 0 = type of pool (see the
FLOW CONTROL ON MEMORY
POOLS event)
34 SOFTWARE KEY CHANGE CPU (80) INFO 0 = type of key (0= main key;
1 = CTI key)
INFO 1 = type of event (see: Soft-
ware key states (INFO 1 of mes-
sage 34) on page 69)
INFO 2 and 3 = Bytes correspond-
ing to the acknowledgement code
(respectively High and Low)
40 R_ANO_EMERGENCY_CON-
FIG
No device has been configured
to receive emergency call notifi-
cation
100 BOARD BACK IN SERVICE Board lo- INFO 0 = type of board (see:
cation #unique_9/
(Following a system stoppage
unique_9_Connect_42_s8)
or after being unplugged)
101 BOARD UNPLUGGED Board lo- INFO 0 = type of board (if known)
cation (see: #unique_9/
unique_9_Connect_42_s8)
INFO 1 = cause of rejection
104 TEMPORARY BOARD RESET Board lo- INFO 0 =1: hardware fault; 2: no
cation response from board (board main-
tenance); 3: fan fault; 4: running on
battery; 5: license problem; 6:
maintenance problem; 7: reason
unknown
If INFO 0 = 1: hardware fault
• INFO 1 = root problem high
order byte
• INFO 2 = root problem low
order byte
If INFO 0 = 3: fan fault, 4: running
on battery, 5: license problem, 6:
maintenance problem, or 7: reason
• INFO 1 = cause of reset
• INFO 2 = Shutdown Status
105 PERMANENT BOARD RESET Board lo- INFO 0 =1: hardware fault; 2: no Disconnect
cation. response from board; 3: fan failure; and recon-
4: running on battery; 5: license nect the
problem; 6: maintenance problem; board. If the
7: reason unknown; 8: power sup- fault persists,
ply problem replace the
board
If INFO 0 = 1: hardware fault
• INFO 1 = root problem high
order byte
• INFO 2 = root problem low
order byte
If INFO 0 = 3: fan fault, 4: running
on battery, 5: license problem, 6:
maintenance problem, 7: reason,
or 8: power supply problem
• INFO 1 = cause of reset
• INFO 2 = Shutdown Status
106 BOARD REFUSED Board lo- INFO 0 = type of board Check the
cation hardware
The board has been refused INFO 1 = cause of refusal: (See
configuration
and, in the case of an intelligent #s10)
(the system
board, a permanent reset is
1: REJ_MAX_BRD_POW: Too limits may
performed on it
much power consumed have been
exceeded).
4: REJ_UNKOWN_BOARD_TYPE:
Board unknown by system
5: REJ_BOARD_FORBIDDEN:
Board known, but not allowed at
that location
6: REJ_PRA_IN_MASTER_NEE-
DED: No PRA access in Master
cabinet
7: REJ_NO_LICENSE: Not Accep-
ted according rights given by the
License
8: REJ_TOO_MANY_CPUS: Max
of Applicative boards is reached
9: REJ_BOARD_INIT_FAILED:
Board could not be initialized
13: REJ_TOO_MANY_RAS: Max
of coCPU RAS boards is reached
15:
REJ_NO_MORE_MIXED_BOARD
_LICENSE: Number of trunks on
Mixed board reaches maximum
given by the license
111 DEVICE REFUSED Board lo- INFO 0 = type of device (see: Check the
cation. Types of terminal (INFO 0 of mes- hardware
Configuration limit attained
sages 110, 111 and 112) on page configuration
Interface
64) (the system
marker
limits may
INFO 1 = cause of refusal (see:
have been
Reasons for terminal refusal (INFO
exceeded).
1 of message 111) on page 67)
INFO 2 = 1: software license prob-
lem (in this case, INFO 1 = 255
(terminal is not totally refused, be-
cause recognized by MMC))
112 FAULT ON A DEVICE Board lo- INFO 0 = type of device (see: If the fault re-
cation. Types of terminal (INFO 0 of mes- curs fre-
sages 110, 111 and 112) on page quently,
Interface
64) check the ter-
marker
minal and its
INFO 1 = type of error (only rele-
connections.
vant for UA sets)
113 INTERFACE REFUSED Board lo- INFO 0 = type of interface (see: Check the
cation. Types of interface (INFO 0 of mes- hardware
An interface was refused be-
sage 113) on page 67) configuration
cause the system limits were Interface
(the system
exceeded marker INFO 1 = cause of refusal (see: Ad-
limits may
ditional information contained in
have been
message 113 (INFO 1: cause of re-
exceeded).
fusal) on page 68)
123 MAIN FAILURE CPU (80) INFO 0 = Main power supply state
(0 = Electrical power supply KO -
battery activated; 1 = Electrical
power supply OK; 2 = System on
battery, only with 2G power supply)
149 SIP Registration rejected CPU (80) INFO 0 = reason for the rejection
• 0: Undefined error
• 1: Unknown user
• 2: No request or Registrar call
• 3: Bad login or username
• 4: Bad password
• 5: Bad domain name
• 6: Error processing of register
request
• 7: Only one contact allowed.
• 8: Database full
• 9: Too many contacts for one
single address
10: Wrong terminal type for IP-
DECT handset
INFO 1 = First byte of edn
INFO 2 = Second byte of edn.
INFO 3 = Count of occurrence of
the event with same reason of re-
ject
166 METERING TABLE FULL CPU (80) INFO 0 = Origin (1 byte); 0 = Ac-
count ticket table; 1 = VoIP RTP
The metering table is full
ticket table
181 CLOUD CONNECT FAILURE MAIN CPU INFO 0 = Cloud Connect event
type:
Event generated after a con-
nection failure with the Rain- • 0x00: No type
bow Cloud infrastructure, or a • 0x0A: Cloud Connect
problem with the Cloud Con- connection failed
nect Control Agent (CCCtrlA) • 0x0B: Internal Cloud Connect
embedded on OXO Connect agent error
Evolution, or a Rainbow service • 0x0C: Cloud Connect
which is no more reachable connection lost
• 0x0D: Bad credential (THIS
CASE IS URGENT BY
DEFAULT)
• 0x0E: Service unreachable
• 0x0F: Final account getting
• 0x10: Final account
acknowledgement
• 0x11: Inconsistent received data
• 0x12: Event node error
• 0x13: Get File error
• 0x14: License error
• 0x15: Software download error
INFO 1 = Cause:
• 0x00: No cause
• 0x09: Stream version error
• 0x0A: Stream Close
• 0x0B: Proxy authentication
required
• 0x0C: Proxy authentication
failed
• 0x0D: Proxy no supported
authentication
• 0x0E: Connection refused
• 0x0F: DNS error
• 0x10: No supported
authentication
• 0x11: TLS failed
• 0x12: TLS not available
• 0x13: Connection compression
failed
• 0x14: Input/Output error
• 0x15: Parse error
• 0x16: Out of memory
• 0x17: Authentication failed
• 0x18: Service unreachable
• 0x19: Service non responding
• 0x1A: Invalid input
223 REMOTE GATEWAY DOWN INFO 0 to INFO 3: bytes corre- Check the IP
sponding to the IP address Net- connectivity
Remote gateway is out of serv-
work format to the remote
ice.
gateway
(LAN, inter-
mediate IP
router) and
the remote
gateway sta-
tus.
225 GATEWAY TRAFFIC CPU (80) INFO 0 to INFO 3: bytes corre- If this alarm
sponding to the IP address Net- keeps recur-
Too much traffic to the remote
work format ring, increase
gateway xxxxx
the band-
width associ-
ated with the
gateway in
the ARS ta-
ble, and the
number of
DSPs as-
signed to
VoIP access.
228 NOT ENOUGH DSP CPU (80) INFO 0 = Type of DSP allocation If this alarm
failure keeps recur-
VoIP telephony failure: no DSP
ring, increase
channel available.
the number
of DSPs as-
signed to the
IP user pool
(decrease the
number of
VoIP-access
DSPs or add
hardware re-
sources).
241 VMU MEMORY THRESHOLD CPU (80) INFO 0 = 1 (ON) if there are just a
few minutes of recording time left;
The voice message recording
0 (OFF) end of the anomaly.
memory area is nearly full.
5: REJ_MAX_DEV_POW
7: REJ_MAX_DEV
15: REJ_MEM_FULL
16: REJ_MAX_S0
22: REJ_MAX_S_ISDN_SUBS
23: REJ_MAX_S_ISDN_T2
14 : serial number problem with the system key; a new key with a valid serial number but with a version
which does not correspond to system software version has been entered: the services are open for a
limited time.
16 : serial number problem with the system key; a new key with a correct serial number but too old has
been entered: the services are open for a limited time.
21 : the key entered does not correspond to the system: the services are open for a limited time.
24 : the software key entered does not correspond to system software version (invalid serial number):
the services are open for a limited time.
26 : a software key with too old an edition has been entered: the services are open for a limited time.
32 : the services were closed; entering a valid key causes the services to open.
35 : the services were closed; the new key entered has a valid serial number but a version which does
not correspond to the system: the services remain closed.
37 : the services were closed; the new key entered has a valid serial number but too old: the services
remain closed.
41 : the key version does not correspond to the system; the new key entered does not correspond to
the system (invalid serial number): the services are open for a limited time.
42 : the key version does not correspond to the system; a valid key was entered: the services are
open.
45 : the key version does not correspond to the system; the end of the limited time causes the services
to close.
46 : the key version does not correspond to the system; a new key with a valid serial number but too
old an edition has been entered: the services are open for a limited time.
52 : the services were closed; a valid key was entered: the services are open.
53 : the services were closed; the key entered does not correspond to the system: the services remain
closed.
57 : the services were closed; the key entered has a valid version but does not correspond to the
system (invalid serial number): the services remain closed.
61 : the system's edition is too old; the new key entered does not correspond to the system: the
services are open for a limited time.
62 : the system's edition is too old; a valid key was entered: the services are open.
64 : the edition of the system's key is too old; a new key with a valid edition, but an old version, was
entered: the services are open for a limited time.
67 : the system’s key is too old; the end of limited time causes the services to close.
72 : the system’s key is too old; the services were closed; the new key entered is valid: the services are
open.
73 : the system's edition is too old; the services were closed; the new key entered has a problem with
the serial number: the services remain closed.
75 : the system's key is too old; the services were closed; the new key entered has a valid serial
number, but a version which does not correspond to the system: the services remain closed.
6.1 Overview
The PBX power button allows to either start, restart or stop the PBX. A power LED is associated to the
power button giving information on PBX status and activity.
Power button actions differ according to the initial state of the PBX. The PBX can be in any of the
following states:
Note:
When the PBX is stopped without using any standard stop process (for example: the PoE cable is unplugged), and
restarted after approximatively two minutes, the watchdog defense mechanism is launched after some time, and
the PBX restarts a second time.
To stop the PBX (Standby state), press the power button and keep your finger on the button for at
least five seconds.
The PBX shuts down with the power LED flashing red. When the PBX is in Standby state, the power
LED switches to steady red.
To set the PBX from Standby state to Off state, unplug the POE cable from the PBX (power LED is
off).
7 System Reset
From OXO Connect Evolution, system reset can be done in the following ways:
• Warm Reset
• Cold Reset
• Factory Reset
• Administrator
• Installer
• Download
• NMC
• Management services access flag
• Allow Management services from WAN
When cold reset is selected with Network and Management data sub option, network configuration,
management passwords and management service access flags change to their default configuration.
table 7.1: Data removed/not removed in factory reset and LoLa installation
2 IM User data
4 License
5 System logs
14 Server Certificate
15 Certificate Authority
: Data removed
8 SNMP
8.1 Overview
The OXO Connect Evolution includes an SNMP service enabling network supervision (remotely or
locally) of the system from an SNMP supervisor. The number of OXO Connect Evolution nodes
supervised by OmniVista 8770 is limited. SNMP is a protocol commonly used for data network
supervision.
Historic, hardware anomalies and urgent alarms of the OXO Connect Evolution are got via the SNMP
service. Through the SNMP, an alarm report mechanism with traps (SNMP Trap V2C mechanism)
allows to report the urgent alarms of the system on the fly.
Configuration and actions on the system are provided by the OMC tool.
SNMP allows to provide a physical view of system information and equipment status, via:
• MIB-II, which describes all the IP network side and the corresponding generic alarms
• The host resources MIB which describes a “host” system (with all resources)
• Some private MIBs which describe:
• The OXO Connect Evolution Hardware
• The telephony service: historic, hardware anomalies and urgent alarms tables
All these data (information and status), read from the OXO Connect Evolution, cannot be modified.
For more information, see: TC2093en ed.02, available from the Business Portal.
8.2 Protocol
8.2.1 Topology
The SNMP service is a mechanism to supervise remotely the system. Three SNMP protocol versions
are normalized differing from each other mainly on security aspects.
The SNMPv2c protocol is implemented on OXO Connect Evolution. Security is based on a community
identifier, which is sent transparently over the network for trap sent from the OXO Connect Evolution
and status got from the supervisor
VPN is recommended for the exchanges between the OXO Connect Evolution SNMP agent and the
remote supervisor. It can be offered with an network operator.
The OXO Connect Evolution sends its own specific traps, easily integrated with supervisors
The service is available on LAN and WAN with low security level. When enabled, a supervisor can:
• Receive, on the fly, the urgent alarms of the system
• View the system’s life (some supervisors ping their agent), its configuration (hardware description)
and status at any time
8.2.2 Security
When the supervisor is the network operator, it can supervise several OXO Connect Evolution located
in different enterprises. If all the OXO Connect Evolution supervised belong to one enterprise through
an Intranet, the supervisor can be either the operator or the enterprise itself.
When the supervisor is not the operator network, the security must be provided with a VPN which
ensures integrity, confidentiality and authentication if necessary.
On the supervisor side, a gateway VPN must be used, and:
• The supervisor must have a public IP address
• The supervisor must be accessible from the OXO Connect Evolution, and vice versa
Only UDP protocol is used for SNMP.
Ports used by SNMP are the default ones:
• Port 161 (GET mode): used by the OXO Connect Evolution, open only when the SNMP is activated
in the OXO Connect Evolution
• Port 162 (TRAP mode): used by the supervisor to receive the traps
The OXO Connect Evolution uses only SNMP V2c security. The "community identifier" must be known
by all entities and the authentication of clients is performed only by a "community string", as a
password, which is transmitted in clear text. Packets are not encrypted.
ochmTermRebootOrResetOfUserData
ochmBoardTempReset
ochmThresholdHardwareTBL
ochmThresholdHistoryTBL
ochmThresholdMeteringTBL
ochmThresholdUrgentTBL
ochmNmcMeteringTblFull
ochmAnoNoeDLDFail
No trap is sent when the network connection is down, and they are definitely lost. In this case, the
supervisor will retrieve the eventsthe next time it gets the MIBs.
There is no acknowledgment that a trap is correctly received by the SNMP supervisor.
8.2.4 MIB
The MIB files can be collected in two categories:
• Standard MIBs: MIB-II is enabled for the following elements:
• System: global information (Linux version / OID enterprises…)
• Interfaces: network interfaces statistics
• AT: Address Translation (deprecated)
• ICMP: ICMP statistics
• Transmission: SNMP global statistics
• SNMP: SNMP detail statistics
• Proprietary MIBs, containing:
• A hardware MIB available to give a view of what OXO Connect Evolution system is made of
• A specific MIB dedicated to the call handling
Alarm
Alarm description
Start End
8.3 Configuration
8.3.1 Configuring the SNMP Service
The SNMP configuration is performed using the OMC tool. The SNMP service can be activated or
deactivated via the OMC tool (deactivated by default).
Note:
In case of default, the access to the SNMP service is not enabled for the supervisor and all parameter fields are
empty.
To declare the SNMP Service to Supervisors:
1. From the OMC tool, navigate to the menu
Enable Flag Select the check box to activate the SNMP service
System Contact Enter contact information of the person responsible for this man-
aged system
8.4 Supervision
A zip file containing the MIBs description can be downloaded through Web dialog window, see [9]. It is
a free downloadable access, even when SNMP is not activated.
The alarm supervision is done exclusively either through the SNMP supervisor or the NMC. The two
services are exclusive, but neither the OMC nor the OXO Connect Evolution check it. The installer
must insure that both are not configured.
The NMC can be used for taxation purpose in parallel of the SNMP supervision.