IP Office
SNMP (Simple Network Management Protocol)
SNMP allows network devices (SNMP
clients and servers) to exchange information. SNMP clients are built into devices
such as network routers, server PC, etc. SNMP servers are typically PC application
which receive and/or request SNMP information. AlarmTraq is an SNMP server.
The IP Office SNMP client allows
the IP Office control unit to respond to SNMP polling and to send information about
error conditions to AlarmTraq.
Due to the many improvements in
SNMP signaling with the latest release of IP Office 3.2 (July 2006) such as the
new 'Device-ID' (ipoGTEventDevID) that AlarmTraq uses to track the Product-ID of the IP Office.
Viewing: If you do not already
have Adobe Acrobat, you can download Acrobat Reader for free.
SNMP Setup
IP Office 3.2 SNMP Setup
IP Office 3.2 Alarms
IP Office 3.1 Alarms
MIB Files
SNMP Traps
Note: In order for
AlarmTraq to interact with an IP Office, the IP Office MIB files, provided on the
IP Office Admin CD, must be compiled into AlarmTraq. Refer to the IP Office Installation
Manual.
To setup SNMP click
on Edit>System-Wide Options>SNMP tab.
System-Wide Option
- SNMP
Enable SNMP Manager on Port 162:
Select this option to automatically load the SNMP manager application to receive
traps from systems such as S8700, S8300, S8500, and IP Office. SNMP Manager will
run in the background and can be monitored with the SNMP Viewer. To open the SNMP
Viewer, click View>SNMP Trap Viewer.
Track Product ID by:
If you wish to track the
WAN IP address for use when assigning a Product ID select WAN IP. To track
by Agent IP select Agent IP.
Generic Traps:
Select the trap types you want to be processed. If not checked these trap types
will be ignored by AlarmTraq.
Send SNMP trap to NMS (HP OpenView) on port 161:
Select this option to automatically send an SNMP trap message to a 3rd party Network
Management System (NMS) when an alarm is received via modem or SNMP.
This option allows AlarmTraq to act
as a proxy SNMP server to integrate legacy Definity systems such as System-75, G1,
G2 and G3 to be monitored by HP OpenView or any 3rd party SNMP manager application.
Destination 1-4:
Enter the IP address of
the SNMP Manager application you would like to send traps to. This is the IP address
of the HP OpenView server or other 3rd party SNMP Manager.
Make sure you DO NOT enter the
IP address of the AlarmTraq server in this field, as this will create an endless
loop the next time an alarm is received.
AlarmTraq SNMP Viewer:
To open the SNMP
Viewer, click View>SNMP Trap Viewer
Open IP Office Manager 5.2 and click
on the ‘System Alarms’ tab.
IP Office Manager
5.2 – System Alarms - Configuration
SNMP Enabled: Default = Off
Enables support for SNMP by the IP Office control unit.
Community (Read-only):
Default = Blank
The SNMP community, eg. public.
SNMP Port:
Default = 161
The port on which the control listens and responds to SNMP polling traffic.
Device ID: Default = blank
Enter the 10-digit Product ID of this system to be used by AlarmTraq. This number
must be in the format 6XXXXXXXXX and be unique in order for AlarmTraq to recognize
this system
Contact:
Enter the name of the contact for this system (reference only, not used by AlarmTraq).
Location:
Enter the name of the location of this system (reference only, not used by AlarmTraq).
Click on the ‘Alarms’ tab.
IP Office Manager
5.2 – System Alarms - Configuration
IP Address: Default = Blank
The public IP address of the AlarmTraq server to which trap information is sent.
Port:
Default = 162
The SNMP transmit port
Community:
Default = Blank
The SNMP community for the transmitted traps. Must be matched by the receiving SNMP
server.
Events:
Default =
None
Sets which types of IP Office events should be collected and sent by the trap:
Entity:
Report on
link up/down changes between IP Office modules (except WAN3), trunks and VCM.
Generic:
Report on
cold starts, warm starts and SNMP authentication failure.
Licence:
Report failure
to connect with the Licence Key Server.
CSU Loop-Back: Only displays when the system locale
is set to enu. Ticking this field enables the sending of CSU loop-back events,
which may then be monitored by an SNMP manager application.
Phone Change: Send a trap whenever a phone is removed or moved.
IP Office 3.2 supports
the addition of Device-ID (ipoGTEventDevID) that AlarmTraq uses
to establish the Product ID of the system sending the trap.
|
7/27/2006 12:45:06
PM SYS Trap received from host 63.168.24.67
Site based
on WAN IP 63.168.24.67
Community: public
WAN IP: 63.168.24.67
Agent IP: 192.168.1.50
EnterpriseOid:
1.3.6.1.4.1.6889.2.2.1.2 [ipoGenTraps]
Description: 1.3.6.1.4.1.6889.2.2.1.2
VariableCount:
4
Generic
Trap: 6 [EnterpriseSpecific]
SNMP Type: 36
Uptime: 2186
Specific
Trap: 16 [ipoGenWarmStartSvcEvent]
[1.3.6.1.4.1.6889.2.2.1.2.1.9.0]
[ipoGTEventStdSeverity] 4
[1.3.6.1.4.1.6889.2.2.1.2.1.2.0]
[ipoGTEventDateTime] 07/27/2006
12:45:06
[1.3.6.1.4.1.6889.2.2.1.2.1.10.0]
[ipoGTEventDevID]
6203234911
[1.3.6.1.2.1.1.1.0]
[sysDescr] IP 406 DS 3.2(17)
Definition:
Enterprise version of standard warmstart trap featuring device identification information
Proccessing
alarm as:
620323491127/12:45,EOF,ACT|0,ipoGenWarmStartSvcEvent,n,MAJ
|
|
7/27/2006 12:35:25
PM SYS Trap received from host 63.168.24.67
Site based
on WAN IP 63.168.24.67
Community: public
WAN IP: 63.168.24.67
Agent IP: 192.168.1.50
EnterpriseOid:
1.3.6.1.4.1.6889.2.2.1.1.1 [ipoPhonesMIB]
Description: 1.3.6.1.4.1.6889.2.2.1.1.1
VariableCount:
8
Generic
Trap: 6 [EnterpriseSpecific]
SNMP Type: 36
Uptime: 363752
Specific
Trap: 2 [ipoPhonesChangeSvcEvent]
[1.3.6.1.4.1.6889.2.2.1.2.1.9.0]
[ipoGTEventStdSeverity] 5
[1.3.6.1.4.1.6889.2.2.1.2.1.2.0]
[ipoGTEventDateTime] 07/27/2006
12:35:25
[1.3.6.1.4.1.6889.2.2.1.2.1.10.0]
[ipoGTEventDevID]
6203234911
[1.3.6.1.2.1.1.1.0]
[sysDescr] IP 406 DS 3.2(17)
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.2.2]
[ipoPhonesExtID] 35
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.6.2]
[ipoPhonesType] 26
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.7.2]
[ipoPhonesPort] 29
[1.3.6.1.4.1.6889.2.2.1.2.1.11.0]
[ipoGTEventEntityName] Controller, DS 1
Definition:
This notification is generated whenever the type of phone connected to a logical
extension entity is detected as having changed after completion of normal start
up of the Agent entity
Proccessing
alarm as: 620323491127/12:35,EOF,ACT|M:"ipoPhonesExtID 35 changed
to 5420 on ipoPhonesPort 29",,n,MIN
|
When a trap is received
by an IP Office system, the Product ID is derived from the first nine digits of
the WAN IP Address plus as many zeros as needed to become a nine-digit number, with
the addition of a "6" inserted at the
beginning in order to identify itself as an IP Office. See the above example:
IP Office Identifier
= 6
WAN IP Address =
63.168.24.67
Product ID will
be 6631682467
|
3/15/2005
12:30:28 PM Trap received from host 63.168.24.67
Community: public
WAN IP: 63.168.24.67
Agent IP: 10.10.100.50
EnterpriseOid: 1.3.6.1.4.1.6889.1.2.1.2.2 [ipoProd403DS]
Description: 1.3.6.1.4.1.6889.1.2.1.2.2
VariableCount: 0
Generic Trap: 1 [WarmStart]
SNMP Type: 36
Uptime: 1500
Specific Trap: 0
Definition: A warmStart trap signifies that the sending protocol entity is reinitializing
itself such that neither the agent configuration nor the protocol entity implementation
is altered.
663168246715/12:30,EOF,ACT|0,WarmStart-ipoProd403DS,n,WAR
***************** End Trap 3/15/2005 12:30:31 PM **************************************
|
|
3/15/2005
11:18:51 AM Trap received from host 63.168.24.67
Community: public
WAN IP: 63.168.24.67
Agent IP: 10.10.100.50
EnterpriseOid: 1.3.6.1.4.1.6889.2.2.1.1.1 [ipoPhonesMIB]
Description: 1.3.6.1.4.1.6889.2.2.1.1.1
VariableCount: 5
Generic Trap: 6 [EnterpriseSpecific]
SNMP Type: 36
Uptime: 8929612
Specific Trap: 1
[1.3.6.1.4.1.6889.2.2.1.2.1.1.0] [ipoGTEventSeverity] 3
[1.3.6.1.4.1.6889.2.2.1.2.1.2.0] [ipoGTEventDateTime] 03/15/2005 11:18:51
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.2.3] [ipoPhonesExtID] 67
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.6.3] [ipoPhonesType] 1
[1.3.6.1.4.1.6889.2.2.1.1.1.1.1.2.1.7.3] [ipoPhonesPort] 20
Definition: This notification is generated whenever the type of phone connected
to a logical extension entity is detected as having changed after completion of
normal start up of the Agent entity.
663168246715/11:18,EOF,ACT|20,ipoPhonesChangeEvent-EXT67_noPhone,n,MIN
***************** End Trap 3/15/2005 11:18:54 AM **************************************
|
Although MIB (Management
Information Base) files are not required for AlarmTraq to operate, MIBs allow AlarmTraq
to access management data from supported systems using SNMP.
All MIB files that
need to be loaded at startup should reside in the "AlarmTraq\MIB\" directory, and
the "MIB_Order.txt" file should contain the file names in the order
they should be loaded.
Sample MIB_Order.txt
file
To Verify the proper
operation and loading of the MIBs, a separate program names MIBListView.exe located
in the \AlarmTraq directory will show all the variables assigned by the MIBs.
Run "C:\Program
Files\AlarmTraq\MIBListView.exe"
Sample MIBListView
The left column shows the list of variables
loaded by the MIBs. The main window shows the Oid (Object Identifier) and description
of the variable.
To find the variable
name from an Oid, click "Action>Convert Oid To Name" (see below).
To find the OID
from a variable name, click "Action>Convert Name To Oid" (see below).
IPO-MIB Traps 3.1
ipoGenEntityFailureEvent NOTIFICATION-TYPE
OBJECTS {
ipoGTEventSeverity,
ipoGTEventDateTime,
ipoGTEventEntity
}
STATUS current
DESCRIPTION
"A ipoGenEntityFailureEvent notification is generated whenever a
physical entity on the IP Office fails in its operation. It
signifies that the SNMP entity, acting in an agent role, has
detected that the state of a physical entity of the system has
transitioned from the operational to the failed state"
::= { ipoGTEvents 1
}
ipoGenEntityOperationalEvent
NOTIFICATION-TYPE
OBJECTS {
ipoGTEventSeverity,
ipoGTEventDateTime,
ipoGTEventEntity
}
STATUS current
DESCRIPTION
"A ipoGenEntityOperationalEvent notification is generated whenever
a physical entity on the IP Office becomes operational again
after having failed. It signifies that the SNMP entity, acting
in an agent role, has detected that the state of a physical
entity of the system has transitioned from the failed to the
operational state"
::= { ipoGTEvents 2
}
ipoGenEntityErrorEvent
NOTIFICATION-TYPE
OBJECTS {
ipoGTEventSeverity,
ipoGTEventDateTime,
ipoGTEventEntity
}
STATUS current
DESCRIPTION
"A ipoGenEntityErrorEvent notification is generated whenever a
physical entity on the IP Office experiences a temporary
error. It signifies that the SNMP entity, acting in an agent
role, has detected a transitory error on a physical entity of
the system."
::= { ipoGTEvents 3
}
ipoGenEntityChangeEvent NOTIFICATION-TYPE
OBJECTS {
ipoGTEventSeverity,
ipoGTEventDateTime,
ipoGTEventEntity
}
STATUS current
DESCRIPTION
"A ipoGenEntityChangeEvent notification is generated whenever
a physical entity on the IP Office experiences a change itself
or with other entities associated with it. It signifies that
the SNMP entity, acting in an agent role, has detected a non
error/failure change for a physical entity on the system."
::= { ipoGTEvents 4
}
ipoGenLKSCommsFailureEvent
NOTIFICATION-TYPE
OBJECTS {
ipoGTEventSeverity,
ipoGTEventDateTime
}
STATUS current
DESCRIPTION
"A ipoGenLKSCommsFailureEvent notification is generated