Foundry NetIron M2404C and M2404F Metro Access Switches
Configuring SNMP (Rev. 03)
Simple Network Management Protocol
© 2008 Foundry Networks, Inc.
Page 12 of 48
Argument Description
ENGINE-ID
A string of 10 to 64 characters (represented internally by 5 to 32 bytes) that
represents the agent’s Engine ID as a hexadecimal number. Use an even
number of characters in the range <0 – 9> and <a – f> (case-insensitive).
Example
The following example shows how to set the agent local
engineID
to 1234567890ABCD:
device-name
(config)#
snmp-server engineID 1234567890ABCD
Enabling the SNMP Server
The
snmp-server enable
command, in Global Configuration mode, enables the SNMP server. The
no
form of this command disables the SNMP server.
If the UDP port number is specified in the command, the agent will listen for incoming SNMP
messages on this port.
By default, the SNMP server is disabled and the SNMP UDP port is 161.
NOTE
If the SNMP server is disabled it can still be configured from the CLI (Command
Line Interface), but it cannot respond to SNMP PDUs and cannot send traps.
Command Syntax
device-name
(config)
#snmp-server enable
[<
udp-port
>]
device-name
(config)
#no snmp-server enable
Argument Description
udp-port
(Optional). The number of the UDP port on which the SNMP server listens for
messages. If the UDP port is not specified, the SNMP server listens for incoming
messages on its default UDP port – 161. The range is <1-65535>.
Example
The following example shows how to enable the SNMP server on port 1021:
device-name
(config)#
snmp-server enable 1021
Defining SNMPv3 Views
The
snmp-server view
command, in Global Configuration mode, defines the subset of all MIB
objects accessible to the given view. The
no
form of the command removes the defined view.
This command includes or excludes a branch of the MIB tree in a view.
The MIB definition represents a tree architecture where each node in the tree is identified by a
number. To identify a branch in the tree, the usual convention is to use a series of numbers
separated by dots, where each number represents a node in the tree.
The view name is created if it does not exist. If the view definition exists, the defined subtree is
added to the list of view families. If the Object ID already exists, it is replaced by the new data