SNMP Introduction
©2008 Allied Telesis Inc. All rights reserved.
Software Version 5.2.1
AlliedWare Plus
TM
Operating System Software Reference C613-50003-00 REV E
54.15
b.If the community called “admin” already exists, allocate a three binary digit block of addresses
to an existing community called “admin” with the address subnet 146.15.1.X.
For security reasons, the common management prefix should be larger than the IP subnet. This
prevents stations on one subnet from being considered valid management stations on a
different subnet.
Configuration Example (SNMPv1 and v2)
This example shows how to configure the switch’s SNMP agent. Two network management
stations have been set up on a large network. The central NMS (IP address 192.168.11.5)
monitors devices on the network and uses SNMP set messages to manage devices on the
network. Trap messages are sent to this management station. The regional network
management station (IP addresses 192.168.16.1) is used just to monitor devices on the
network by using SNMP get messages. Link traps are enabled for all interfaces on this particular
switch.
The IP module must be enabled and correctly configured in order to access the SNMP agent in
the switch. This is because the IP module handles both the TCP transport functions, and the
UDP functions that enable datagrams to transport SNMP messages. See Chapter 13, Internet
Protocol (IP) for commands that enable and configure IP.
To configure SNMP
1. Enable the SNMP agent.
Enable the SNMP agent and enable the generation of authenticate failure traps to monitor
unauthorised SNMP access. SNMP is enabled by default in AlliedWare Plus.
2. Create a community with write access for the central NMS.
Create a community called “private”, with write access for use only by the central network
management station at 192.168.11.5. All traps are sent to this NMS.
awplus(config)#snmp-server community private rw
Care must be taken with the security of community names. Do not use the name “private” in
your network because it is too obvious. Community names act as passwords and provide only
trivial authentication. Any SNMP application entity that knows a community name can read the
value of any instance of any object in the MIB implemented in the switch. Any SNMP
application entity that knows the name of a community with write access can change the value
of any instance of any object in the MIB implemented in the switch, possibly affecting the
operation of the switch.
3. Create a community with read-only access for the regional NMS.
Create a community called “public”, with read-only access for use by the regional network
management station at 192.168.16.1.
awplus(config)#snmp-server community public ro
4. Enable link traps.
Enable link traps for the switch’s VLAN interfaces.
5. Check the configuration.
Check that the current configuration of the SNMP communities matches the desired
configuration:
awplus#show snmp-server