Administering The Snmp Module - Avaya S8500 Installing And Configuring

!
!
SECURITY ALERT:
The Get and Set community name strings are initially configured with the default
SECURITY ALERT:
values of Public and Private, respectively. These community name strings
function as passwords for their respective SNMP operation. Avaya recommends
that you change these community name strings to something other than the
default values. If you leave the defaults in place, a serious security issue can
result.
For information about which traps to set, see
If the control network is nondedicated, ensure that the 162/udp port for input to server is
●
enabled and the default is disabled. If you do not enable the 162/udp port and disable the
default, the media server cannot receive the traps from either UPS. See
settings

Administering the SNMP module

Note:
Use the default IP addresses.
Note:
1. to the DB-9 connector on the back of the SNMP module for UPS1. Use the DB-9 to DB-9
serial cable that is supplied with the SNMP module.
2. Open a VT-100 terminal emulation session on your computer.
3. Set the IP address for the UPS.
4. Set the subnetwork mask for the UPS.
5. Set the gateway address for the UPS.
6. Set the IP address of the trap receiver for the UPS.
7. Set the SNMP community name string for Get, Set, and Trap. For information on which
traps to set, see
8. When you finish, disconnect your computer from the UPS.
9. Connect one end of a CAT5 straight-through cable to the RJ45 connector on the UPS
SNMP module and the other end of the cable to the next available port on the Ethernet
switch for Control Network A (CNA).
For a connectivity guide, see the Quick Start for Hardware Installation: Avaya S8500
Media Server (555-245-701).
After you configure the SNMP module in the UPS, you must configure the SNMP subagent on
the Avaya Ethernet switch.
Installing and Configuring the Avaya S8500 Media Server
on page 51.
Setting selected traps (alarming)
Configuring the SNMP modules in the UPS
Setting selected traps (alarming)
on page 38.
on page 38.
Enabling firewall
37
June 2006