SNMP in AlphaCom XE

The AlphaCom XE and some of its stations runs a SNMP service.

Stentofon MIB OID numbers

Zenitel Norway AS have 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 about AlphaCom OID

The AlphaCom OID has of historical reasons not followed the enterpise numbering defined above. The current AlphaCom OID is:

enterprises.26122

AlphaCom MIB

Revision 1

OID: enterprises.9362
Included in RootFS versions: 01-0x and 10-1x (to be updated revision 2 released)
MIB text: AlphaCom MIB Revision 1

Revision 2

OID enterprises.26122: 
Included in RootFS versions: 0x-0xx and 1x-1xx (to be updated revision 2 released)
MIB text: AlphaCom MIB Revision 2

Revision 3

OID enterprises.26122: 
MIB text: AlphaCom MIB Revision 3

Frequently asked questions on SNMP

Which functions of SNMP are implemented?

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:

AMC-IP status (Enabled/Disabled) (Same as AlphaWeb Node State/Operational)
RTP statistics (Audio Statistics)

All MIBS variables are accessed through SNMP v2 protocol with community public. All variables are read only. Example of reading the AlphaCom MIB with NET-SNMP:

> snmpwalk –v 2c –c public localhost enterprises.26122

Where to get the MIB configuration file?

The active MIB file for a ACE board can be found in the folder :

/usr/local/share/snmp/mibs/ALPHACOM-MIB.txt

MIB text: AlphaCom MIB Revision 3

How to activate SNMP in AlphaCom XE?

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

How to change the SNMP UDP port number?

Connect to the linux console through the ssh port using a terminal program like Putty.
log in as normal with alpha/com
In the linux bash write these commands:
- su [enter]
- root password [enter]
- nano /usr/local/share/snmp/snmpd.conf

Add the line agentaddress 165 somewhere. Here 165 is the new portnumber used as an example:

Use ctrl+X followed by Y to save and exit.

For more information see:
http://stackoverflow.com/questions/16205453/how-to-change-the-net-snmp-default-port-to-one-less-than-1024-in-linux
http://www.net-snmp.org/docs/man/snmpd.conf.html

How to change the SNMP trap UDP port number?

Connect to the linux console through the ssh port using a terminal program like Putty.
log in as normal with alpha/com
In the linux bash write these commands:
- su [enter]
- root password [enter]
- nano /var/opt/www/amc_ip_config.xml [enter]

Step a couple of pages down and you should find:

<destination>
        <type>snmptrap</type>
        10.5.101.112

Add the new port number to the IP address like this: 10.5.101.112:165

Use ctrl+X followed by Y to save and exit.
Finally write:
- /etc/init.d/syslog-ng restart

For more information see:
http://www.net-snmp.org/docs/man/snmpcmd.html