R6 SNMP Version 1.0 Table of Contents Overview .................................................................................................................... 3 SV8100 Programming ................................................................................................ 4 MIB File ...................................................................................................................... 5 Example Operation Using the MIB File ...................................................................... 8 Example Operation Using SNMP Traps ..................................................................... 9 Overview R6 system software contains Simple Network Management Protocol (SNMP) support that works with a Private MIB file and SNMP traps. Typically an administrator will use an SNMP application to centrally manage network devices, using SNMP on the SV8100 allows it to be managed alongside these other network devices. The SV8100 is considered as an SNMP Agent that can talk to an SNMP application. The Private MIB file allows an SNMP application to make very specific requests to the SV8100 to obtain useful information from the PBX. Below are examples of the different types of information that is available: Hardware Key Code Installed Hardware System Software System Date and Time Installed licenses VOIP Information SNMP traps can be used for the purpose of monitoring SV8100 alarms via SNMP. When any of the alarms are triggered on the SV, they can be reported in the SNMP application. Details of the available alarms reports are available in the SV8100 Features Manual. A ‘MIB’ (Management Information Base) file has been created that can be loaded into an SNMP application. An ‘OID’ (Object ID) of 14399 has been registered for use by NEC Infrontia for its PBX’s, this pre-configured in the MIB file. The SNMP feature available in system software version 6 requires 2 licenses to be installed on the SV8100 in order to function. The licenses are as follows: BE111389 – R6 Enhanced Feature Pack BE111390 – Maintenance Feature Pack Where Netlink is used, it is only possible to see SNMP information relating to the Primary system. SV8100 Programming The following commands are required to enable SNMP. All of the easy edit commands are located in programming level 3 in Advanced Items / SNMP. PRG Command Name Data Default Description 90-64-01 SNMP 0 – Disable 1 – Enable 0 Set to enable the SNMP feature 90-64-02 Community Name 12 Characters Max Public Enter the SNMP community name 90-64-03 Target Host 1 IP Address ***.***.***.*** None 90-64-04 Target Host 2 IP Address ***.***.***.*** None 90-64-05 Target Host 3 IP Address ***.***.***.*** None 90-64-06 Target Host 4 IP Address ***.***.***.*** None 90-64-07 Target Host 5 IP Address ***.***.***.*** None 90-64-08 Domain name 255 Characters Max None 90-64-09 Trap Set Message 0 – Disable 1 – Enable Enter the IP Address of the PC running the SNMP application. Enter the domain name When Disabled, only alarms that are set as major or minor will be output as an SNMP trap message. 0 When Enabled all system alarms will be output as an SNMP trap message regardless of whether they are set to major or minor. Alarms can be configured in Easy Edit / Advanced Items / Maintenance / Alarms / System Alarm Setup or PRG command 90-10. MIB File The MIB file is structured according to the following tables, only data listed here is available via SNMP. The data for each of the items can be read or write, read is data that can be requested from the system. Write requires that a value has to be entered in the SNMP application, when querying a card for example the slot number would need to be entered. 10. Position can be used to obtain information about a card in a specific slot in the system. The R6 release does not have ability to see remote Netlink systems, only the Primary system is available. Type Description Read or Write 1.System ID Netlink Link System ID. W 2.System Card position Card Slot Number W 10.Position 20. Common can be used to determine hardware versions and system port numbers. Type 20.Common 1. Card Info Description Read or Write 1. Version 1. Hardware Version Write 2. Hardware 1. Port Number Read 30.CPU contains serveral items relating to the CPU, the following tables show a break down of the data available. Type 1.System Description 1.Hardware 30.CPU 2.Main Read or Write 1.Hardware Key code Read 1.CPU Version Read 2.CPU Main Software Build Version Read 3.System Date and Time Read 4.DSP Version Read 1.Version 30. CPU can also be used to see installed licenses on the CPU, licenses are split by feature licenses or port licenses. Available feature licenses are as follows. Type 30.CPU 2.Main 2. License Description 1. Feature License Read or Write 0002.Cygnus-Link Read 0003. Aspire Net Read 0007. Hotel/Motel(PMS) Read 0008. SMDR Read 0009. Remote upgrade Read 0013. Q-sig Read 0016. K-CCIS Read 0018. SIP T.38 FAX Relay Read 0030. Encryption Read 0031. /NAT Traversal Read 0032. IPv6 Read 0033.V4000 Enhancements (BSSD) Read 0034.V5000 Enhancements Read 0040.SIP Video Read 0041.XML Pro Read 0123.OAI Activation Read 2001.ACD Activation Read 2101.ACD P-event Read Description Read or Write 0111.1st Party CTI(Ethernet) Read 0112.3rd Party CTI Client Read 2001.ACD client Read 5001.IP Trunk (SIP/H323) Read 5012.K-CCIS over IP Read 5091.Aspire Net over IP Read 5101.IP Terminal(SIP-MLT/SP) Read 5102.IP Terminal(SP only) Read 5111.IP Terminal(SIP-SLT/3rd Pty) Read Available port licenses are as follows. Type 30.CPU 2.Main 2. License 2.Port License. The following information is also available for Network, Interface, Trapset and Trap Type 2.Main Read or Write 1.CPU Card Address Read 2.CPU Subnet Mask Read 3.CPU Default Gateway Read 4.CPU MAC Address Read 4. Interface 1-24. Type of card inserted in Slot Read 5. Trapset 1-100 Alarm Report Write 6. Trap 1- 100 Alarm Report Read 3. Network 30.CPU Description 40. VOIP can be used to determine information about the IPL card. Type 1. Hardware 2. Status 40.VOIPDB 3. Gateway Description Read or Write 1. VOIP type Read 1. VOIP Card IP Address Read 2. VOIP Card Subnet Mask Read 3. VOIP Card MAC Address Read 1. Gateway 1 IP Address. Read 2. Gateway 2 IP Address. Read 3. Gateway 3 IP Address. Read 4. Gateway 4 IP Address. Read 5. Gateway 5 IP Address. Read 6. Gateway 6 IP Address. Read 7. Gateway 7 IP Address. Read 8. Gateway 8 IP Address. Read Example Operation Using the MIB File When the MIB file has been loaded into an SNMP application, it can send requests to the SV8100 and the SV8100 will send a response back. The request is made up from information available in the MIB file. Below are two example of how these requests and respsonses would be processed in regards to the hardware key code and CPU IP address. PC Running an SNMP Application with the SV8100 MIB file loaded SV8100 Acting as an SNMP Agent Get Hardware Key Code Receive request 191000001813 Send response First of all the SNMP user will make a request in the application to get the hardware key code, this is received by the SV8100 and in turn sends back the hardware key code via SNMP. In a similar fashion, the SNMP user can make a request for the CPU IP Address, this is received the send back via SNMP. PC Running an SNMP Application with the SV8100 MIB file loaded SV8100 Acting as an SNMP Agent Get CPU IP Address Receive request 192.168.0.10 Send response Example Operation Using SNMP Traps SNMP Traps can be used to provide notifications to an SNMP application when an SV8100 alarm has been triggered on the SV8100. The trap message will be sent in accordance with the configuration of the SNMP settings. When the alarm happens on the SV8100, the trap message is sent to the SNMP application. The SNMP application can then pickup and display the alarm. The diagram below shows an SNMP trap message being sent for Alarm 64. PC Running an SNMP Application SV8100 Acting as an SNMP Agent Notification Alarm 64 has occurred Alarm 64 occurs The detail of the alarm is sent in the trap message that will be displayed in the SNMP application, information in the alarm is made up as follows. MAJ 050 WAR Sep 21, 2010 14:50:19 +09:00 System Start Up -none- 00 00 00 MAJ 010 ERR Sep 21, 2010 14:50:19 +09:00 ISDN Link PRT 01 02 12 ① ② ③ ④ ⑤ ⑥ ⑦ ⑧⑨ 1. AlarmLevel：MAJ : Major Alarm / MIN: Minor Alarm 2. Alarm No 3. Alarm Status：ERR: Error REC: Recover WAR: Warning INF: Information 4. Date 5. Alarm Name 6. Unit Name 7. System ID 8. Slot No：1-24 9. Port No：1-30 10. Additional information ⑩ Document History 2011 Initial Release
© Copyright 2024 Paperzz
