Actions

Difference between revisions of "SNMP in AlphaCom XE"

From Zenitel Wiki

Line 1: Line 1:
{{A}}
+
{{AI}}
The AlphaCom XE runs a [[Wikipedia:SNMP|SNMP]] service, and supports SNMP polling and SNMP traps.
+
The ICX-AlphaCom and AlphaCom XE run a [[Wikipedia:SNMP|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.
+
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 ICX-AlphaCom responds to the server. An SNMP trap is initiated by the ICX-AlphaCom when it has information to send (usually some event happened) and does not want to wait for the server to ask for information.
  
  
Line 15: Line 15:
  
  
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]]
+
Note that the ICX-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==
 
==SNMP poll==
Line 23: Line 23:
 
These Mibs only implements polled information.  
 
These Mibs only implements polled information.  
  
The AlphaCom MIB implements two main statuses:
+
The ICX-AlphaCom MIB implements two main statuses:
  
 
{| border="1"
 
{| border="1"
Line 30: Line 30:
 
! style="background:#ffdead;" width="600" |Comment
 
! 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
+
|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 ICX-Web, Node State - Operational
 
|-
 
|-
 
|RTP Statistics|| align="center" |1.3.6.1.4.1.26122.1.2.1||RTP audio statistics
 
|RTP Statistics|| align="center" |1.3.6.1.4.1.26122.1.2.1||RTP audio statistics
Line 39: Line 39:
 
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.  
 
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).
+
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 ICX-Web (UDP port 161).
  
[[File:SNMP Filters 161.PNG|thumb|left|500px|Define and enable UDP port 161 in '''Filters''' settings in AlphaWeb]]
+
[[File:SNMP Filters 161.PNG|thumb|left|500px|Define and enable UDP port 161 in '''Filters''' settings in ICX-Web]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
 
==SNMP Traps==
 
==SNMP Traps==
  
The AlphaCom log events can be sent as SNMP traps.
+
The ICX-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.
 
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.
Line 57: Line 57:
 
! style="background:#ffdead;" width="350" |Alert criteria
 
! 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||
+
| align="center" |1001|| align="center" |1.3.6.1.4.1.26122.1.11.1001||[[ICX-AlphaCom debug log|Debug log]] events||
 
*Software debug information
 
*Software debug information
 
|-
 
|-
Line 79: Line 79:
  
  
SNMP trap is configured in AlphaWeb, '''System Configuration''' > '''Logging'''. Select destination ‘SNMP Trap’ and configure which logs you want to send.  
+
SNMP trap is configured in ICX-Web, '''System Configuration''' > '''Logging'''. Select destination ‘SNMP Trap’ and configure which logs you want to send.  
  
[[File:SNMP trap.PNG|thumb|left|500px|Configuration of SNMP Traps in AlphaWeb]]
+
[[File:SNMP trap.PNG|thumb|left|500px|Configuration of SNMP Traps in ICX-Web]]
 
<br style="clear:both;" />
 
<br style="clear:both;" />
  
  
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.
+
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 ICX-Web.
  
==AlphaCom MIB file==
+
==ICX-AlphaCom MIB file==
  
 
*Link to [[Downloads#SNMP_MIB_files|download AlphaCom MIB file]]
 
*Link to [[Downloads#SNMP_MIB_files|download AlphaCom MIB file]]

Revision as of 06:01, 7 November 2024

AI.png

The ICX-AlphaCom and AlphaCom XE run 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 ICX-AlphaCom responds to the server. An SNMP trap is initiated by the ICX-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 ICX-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 ICX-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 ICX-Web, 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 ICX-Web (UDP port 161).

Define and enable UDP port 161 in Filters settings in ICX-Web


SNMP Traps

The ICX-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 ICX-Web, System Configuration > Logging. Select destination ‘SNMP Trap’ and configure which logs you want to send.

Configuration of SNMP Traps in ICX-Web



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 ICX-Web.

ICX-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


Related articles