Difference between revisions of "SNMP in AlphaCom XE"

Latest revision as of 06:43, 13 September 2022

The AlphaCom XE runs a SNMP service, and supports SNMP polling and SNMP traps.

The main difference between a SNMP poll and a SNMP trap is which device initiates the communication. An SNMP poll is initiated by the SNMP server and the AlphaCom responds to the server. An SNMP trap is initiated by the AlphaCom when it has information to send (usually some event happened) and does not want to wait for the server to ask for information.

Stentofon MIB OID numbers

Zenitel Norway AS has assigned a Private Enterprise Number OID 26122.

The Zenitel Norway AS enterprise number is labeled enterprises.stentofon
Allocated Sub OIDs:

1 - enterprises.stentofon.alphacom
2 - enterprises.stentofon.ipstation

Note that the AlphaCom OID has of historical reasons not always followed the enterprise numbering defined above, see AlphaCom_MIB_revisions

SNMP poll

In addition to the AlphaCom MIB, the standard MIBs mibII, ucd-snmp and snmpv2 are implemented. These Mibs only implements polled information.

The AlphaCom MIB implements two main statuses:

Variable	Object ID	Comment
Nodestate	1.3.6.1.4.1.26122.1.1.1	AMC-IP status enabled/disabled. Shows if the AlphaCom is operational. Same info as in AlphaWeb, Node State - Operational
RTP Statistics	1.3.6.1.4.1.26122.1.2.1	RTP audio statistics

All MIBs variables are accessed through SNMP v2 protocol with community = public. All variables are read only.

The default MIBs are always active, but in order to receive polling requests from an SNMP server you need to open the firewall (Filters) in AlphaWeb (UDP port 161).

Define and enable UDP port 161 in Filters settings in AlphaWeb

SNMP Traps

The AlphaCom log events can be sent as SNMP traps.

The alert types that support SNMP traps have a number assigned to them, for example, 1001 is the number assigned to System Log events. The following table lists the number sent in the SNMP trap for each alert type.

Alert number	Object ID	Alert type	Alert criteria
1001	1.3.6.1.4.1.26122.1.11.1001	Debug log events	Software debug information
1002	1.3.6.1.4.1.26122.1.11.1002	System log events	Station Line error Board down Device/MultiModule (card cage) error AGA/AE1 audio line error Software error Remote Control Input on/off Customized event logging (LOG command)
1003	1.3.6.1.4.1.26122.1.11.1003	Call Statistics log events	Point to point calls Group Calls Call Request Ringing Group

SNMP trap is configured in AlphaWeb, System Configuration > Logging. Select destination ‘SNMP Trap’ and configure which logs you want to send.

Configuration of SNMP Traps in AlphaWeb

SNMP traps are using UDP port 162. As this is outbound data, there is no need to define this port in the Filters settings in AlphaWeb.

AlphaCom MIB file

Link to download AlphaCom MIB file

Revision 3:

OID enterprises.26122
Added missing imports giving MIB validation errors.
Removed some unused import definitions

Revision 2:

OID enterprises.26122
Updated with Zenitel enterprise OID and snmptrap definition for AlphaCom syslog to snmptraps log facilities

Revision 1:

OID: enterprises.9362

@@ Line 1: / Line 1: @@
+{{A}}
+The AlphaCom XE runs a [[Wikipedia:SNMP|SNMP]] service, and supports SNMP polling and SNMP traps.
-== Witch functions of SNMP are implemented? ==
+The main difference between a SNMP poll and a SNMP trap is which device initiates the communication. An SNMP poll is initiated by the SNMP server and the AlphaCom responds to the server. An SNMP trap is initiated by the AlphaCom when it has information to send (usually some event happened) and does not want to wait for the server to ask for information.
-In addition to the AlphaCom MIB, the standard MIBs mibII, ucd-snmp and snmpv2 are implemented.
+==Stentofon MIB OID numbers==
+Zenitel Norway AS has assigned a Private Enterprise Number [http://oid-info.com/get/1.3.6.1.4.1.26122 OID 26122].
+The Zenitel Norway AS enterprise number is labeled '''enterprises.stentofon'''<br />
+Allocated Sub OIDs:
+*1 - enterprises.stentofon.alphacom
+*2 - enterprises.stentofon.ipstation
+Note that the AlphaCom OID has of historical reasons not always followed the enterprise numbering defined above, see [[SNMP_in_AlphaCom_XE#AlphaCom_MIB_revisions|AlphaCom_MIB_revisions]]
+==SNMP poll==
+In addition to the [[Downloads#SNMP_MIB_files|AlphaCom MIB]], the standard MIBs [http://tools.ietf.org/html/rfc1213 mibII], [http://net-snmp.sourceforge.net/docs/mibs/ucdavis.html ucd-snmp] and [http://tools.ietf.org/html/rfc3418 snmpv2] are implemented.
 These Mibs only implements polled information.
 The AlphaCom MIB implements two main statuses:
-* amc status (Enabled/Disabled)   (Same as AlphaWeb Node State/Operational)
+{| border="1"
-* rtp statistics (Audio Statistics)
+! style="background:#ffdead;" width="200" |Variable
+! style="background:#ffdead;" width="200" |Object ID
+! style="background:#ffdead;" width="600" |Comment
+|-
+|Nodestate|| align="center" |1.3.6.1.4.1.26122.1.1.1||AMC-IP status enabled/disabled. Shows if the AlphaCom is operational. Same info as in AlphaWeb, Node State - Operational
+|-
+|RTP Statistics|| align="center" |1.3.6.1.4.1.26122.1.2.1||RTP audio statistics
+|-
+|}
+All MIBs variables are accessed through [[WikiPedia:SNMP#SNMPv2_and_Structure_of_Management_Information|SNMP v2]] protocol with '''community''' = '''public'''. All variables are read only.
+The default MIBs are always active, but in order to receive polling requests from an SNMP server you need to open the firewall (Filters) in AlphaWeb (UDP port 161).
+[[File:SNMP Filters 161.PNG|thumb|left|500px|Define and enable UDP port 161 in '''Filters''' settings in AlphaWeb]]
+<br style="clear:both;" />
+==SNMP Traps==
+The AlphaCom log events can be sent as SNMP traps.
+The alert types that support SNMP traps have a number assigned to them, for example, 1001 is the number assigned to System Log events. The following table lists the number sent in the SNMP trap for each alert type.
-All MIBS variables are accessed through SNMP v2c protocol with community public. All variables are read only.
-Example of reading the AlphaCom MIB with NET-SNMP:
+{| border="1"
+! style="background:#ffdead;" width="120" |Alert number
+! style="background:#ffdead;" width="200" |Object ID
+! style="background:#ffdead;" width="250" |Alert type
+! style="background:#ffdead;" width="350" |Alert criteria
+|-
+| align="center" |1001|| align="center" |1.3.6.1.4.1.26122.1.11.1001||[[AlphaCom debug log|Debug log]] events||
+*Software debug information
+|-
+| align="center" |1002|| align="center" |1.3.6.1.4.1.26122.1.11.1002||[[System log]] events||
+*Station Line error
+*Board down
+*Device/MultiModule (card cage) error
+*AGA/AE1 audio line error
+*Software error
+*[[RCI|Remote Control Input]] on/off
+*Customized event logging ([[LOG|LOG command]])
+|-
+| align="center" |1003|| align="center" |1.3.6.1.4.1.26122.1.11.1003||[[Call Statistics Log|Call Statistics log]] events||
+*Point to point calls
+*Group Calls
+*Call Request
+*Ringing Group
+|-
+|}
+<br>
-> snmpwalk –v 2c –c public localhost enterprises.9362
+SNMP trap is configured in AlphaWeb, '''System Configuration''' > '''Logging'''. Select destination ‘SNMP Trap’ and configure which logs you want to send.
-== Where to get the MIB configuration file? ==
+[[File:SNMP trap.PNG|thumb|left|500px|Configuration of SNMP Traps in AlphaWeb]]
+<br style="clear:both;" />
-See attached file
+SNMP traps are using UDP port 162. As this is outbound data, there is no need to define this port in the Filters settings in AlphaWeb.
+==AlphaCom MIB file==
+*Link to [[Downloads#SNMP_MIB_files|download AlphaCom MIB file]]
+'''Revision 3:'''
+*OID enterprises.26122
+*Added missing imports giving MIB validation errors.
+*Removed some unused import definitions
-== How to activate SNMP in AC? (AlphaWeb – Logging ?) ==
+'''Revision 2:'''
-The default MIBS are always active, but you need to open the firewall in AlphaWeb (UDP port 161)
-If you need to log to snmp (snmp traps) it is possible to configure this in AlphaWeb ‘System Configuration’ / ‘Logging’
-Select destination ‘SNMP Trap’ and configure which logs you want to send.
-The SNMP traps will be sent with the OID: enterprises.1000.1 (This may be subject to change since it is not using our own Zenitel SNMP OID)
-As a general rule I think it is better to use syslog directly for these kinds of log events and not SNMP. Most  Building Management Systems handles both syslog and SNMP. The SNMP log options is implemented to serve systems that do not handle syslog..
+*OID enterprises.26122
+*Updated with Zenitel enterprise OID and snmptrap definition for AlphaCom syslog to snmptraps log facilities
-How to get more information about AC SNMP; I’ve read there is a “Stentofon AC MIB Documentaion”.
+'''Revision 1:'''
-I think the documentation is the MIB file itself (Asle is there written anything else?)
+*OID: enterprises.9362
+<br />
-== Witch function of SNMP in AC will be implemented in near future? ==
+==Related articles==
-There is at this moment not any plans for more snmp implementation.
+*Link to [[Downloads#SNMP_MIB_files|download MIB files]]
+*[[SNMP in IP Stations]]
+*Link to a [https://www.manageengine.com/products/mibbrowser-free-tool free MIB Browser], useful for testing
-I personally have not got any reports on anybody using snmp actively, but it will be nice if you let me now how it works for your customer, and if they miss some functionality.
+[[Category:Logging]]

Difference between revisions of "SNMP in AlphaCom XE"

From Zenitel Wiki

Latest revision as of 06:43, 13 September 2022

Contents

Stentofon MIB OID numbers

SNMP poll

SNMP Traps

AlphaCom MIB file

Related articles