Enabling Snmp And Polling Support; Enabling Snmp Trap Sending - Avaya IP500 V2 Installation Manual

8.12.2 Enabling SNMP and Polling Support

In order for the IP Office control unit to be discovered and polled by an SNMP manager, its SNMP agent must be enabled
and placed in the same read community as the SNMP manager.
1. In IP Office Manager, receive the control unit's configuration.
2. Double-click System from the Configuration Tree panel and select the SNMP tab.
3. Tick SNMP Enabled.
4. In SNMP Port, enter the UDP port number used by the IP Office SNMP agent to listen for and respond to SNMP
traffic. The normal default is 161.
5. In Community (Read-only), enter the community to which the device belongs for read access. This community
name must match that used by the SNMP manager application when sending requests to the device. The
community public is frequently used to establish communication and then changed (at both the SNMP agent and
manager ends) for security.
6. Click OK.
7. Send the configuration back to the IP Office and select reboot.
8. Following the IP Office reboot, the SNMP manager should be able to discover the control unit.
9. The control unit's response will include details of the control unit type and the current level of core software.

8.12.3 Enabling SNMP Trap Sending

In IP Office Manager, receive the control unit's configuration.
1. Double-click System from the Configuration Tree panel and select the SNMP tab.
2. Ensure that SNMP Enabled is ticked.
3. Using either Trap Destination 1 or Trap Destination 2, enter the following information:
· Enter the IP Address of the PC running the SNMP manager application.
· Enter the Port on which the traps messages should be sent. This is the UDP port on which the IP Office sends
SNMP trap messages. The default is 162.
· Set the Community that will be used by the agent and the SNMP manager. The community public is frequently
used to establish communication and then changed (at both the SNMP agent and manager ends) for security.
4. Select the Events which should be sent:
· Generic:
Events such as soft reboot (warm start), hard reboot (cold start), links up/down (transition in the status of a
PPP or frame relay interface) or SNMP community mismatch.
· Entity:
Failures, errors and changes of state in IP Office modules and trunk interfaces. Note: Does not include ATM4.
· Licence:
Changes of state in the communication with the Feature Key Server.
· Phone Change:
Changes to the type of DS or IP phone connected to a port.
· Click on OK.
5. Send the configuration back to the IP Office and select reboot.
Installing IP500/IP500 V2
IP Office 9.0 15-601042 Issue 28c (19 August 2013)
Page 180