Dell Command Line Reference Guide for the S4048–ON System 9.14.2.5

PDF

snmp-server host

Configure the recipient of an SNMP trap operation.

Syntax
snmp-server host ip-address | ipv6-address [vrf vrf-name] traps | informs [version 1 | 2c | 3] [auth | no auth | priv] [community-string] [udp-port port-number] [notification-type]

To remove the SNMP host, use the no snmp-server host ip-address [vrf vrf-name] traps | informs [version 1 | 2c | 3] [auth | noauth | priv] [community-string] [udp-port number] [notification-type] command.

Parameters
ip-address
Enter the keyword host then the IP address of the host (configurable hosts is limited to 16).
ipv6-address
Enter the keyword host then the IPv6 address of the host in the x:x:x:x::x format.
NOTE: The :: notation specifies successive hexadecimal fields of zero.
vrf vrf-name
Enter the keyword vrf and then the name of the VRF that the SNMP server uses to connect to the host.
NOTE: You can use this attribute to inform the SNMP engine about the vrf instance to be used to reach the corresponding remote host to send Trap or Inform message. If no VRF is specified, then the default VRF is used.
traps
(OPTIONAL) Enter the keyword traps to send trap notifications to the specified host. The default is traps.
informs
(OPTIONAL) Enter the keyword informs to send inform notifications to the specified host. The default is traps.
version 1 | 2c | 3
(OPTIONAL) Enter the keyword version to specify the security model then the security model version number 1, 2c, or 3:
  • Version 1 is the least secure version.
  • Version 3 is the most secure of the security modes.
  • Version 2c allows transmission of informs and counter 64, which allows for integers twice the width of what is normally allowed.

The default is version 1.

auth
(OPTIONAL) Enter the keyword auth to specify authentication of a packet without encryption.
noauth
(OPTIONAL) Enter the keyword noauth to specify no authentication of a packet.
priv
(OPTIONAL) Enter the keyword priv to specify both authentication and then scrambling of the packet.
community-string
Enter a text string (up to 20 characters long) as the name of the SNMP community.
NOTE: For version 1 and version 2c security models, this string represents the name of the SNMP community. The string can be set using this command; however, Dell EMC Networking OS recommends setting the community string using the snmp-server community command before executing this command. For version 3 security model, this string is the USM user security name.
udp-port port-number
(OPTIONAL) Enter the keywords udp-port followed by the port number of the remote host to use. The range is from 0 to 65535. The default is 162.
notification-type
(OPTIONAL) Enter one of the following keywords for the type of trap to be sent to the host:
  • bgp — Enable BGP state change traps.
  • ecfm — Enable ECFM state change traps.
  • entity — Enable entity change traps.
  • envmon — Enable SNMP environmental monitor traps.
  • eoam — Enable EOAM state change traps
  • ets — Enable ets traps
  • fips — Enable FIP Snooping state change traps
  • lacp — Enable LACP state change traps.
  • mac — Enable MAC address notification traps.
  • isis — Enable ISIS adjacency change traps.
  • pfc — Enable pfc traps.
  • snmp — Enable SNMP trap.
  • stp — Enable 802.1d state change traps.
  • vlt — Enable VLT traps.
  • vrrp — Enable VRRP state change traps.
  • xstp — Enable 802.1s, 802.1w, and PVST+ state change traps.

The default is all trap types are sent to host.

Defaults
As above.
Command Modes
CONFIGURATION
Command History

This guide is platform-specific. For command information about other platforms, see the relevant Dell EMC Networking OS Command Line Reference Guide.

Version
Description
9.12(0.0)
Introduced MAC address notification traps on all the Dell EMC Networking OS platforms.
9.10(0.1)
Introduced on the S6010-ON and S4048T-ON.
9.10(0.0)
Introduced on the S3148 and S6100–ON.
9.8(2.0)
Introduced on the S3100 series.
9.8(1.0)
Introduced on the Z9100–ON.
9.8(0.0P5)
Introduced on the S4048-ON.
9.8(0.0P2)
Introduced on the S3048-ON.
9.7(0.0)
Introduced on the S6000-ON.
9.4.(0.0)
Added support for VRF.
9.2(1.0)
Introduced on the Z9500.
9.0.2.0
Introduced on the S6000.
9.1(0.0)
Added support for config and ecmp traps.
8.3.19.0
Introduced on the S4820T.
8.3.11.1
Introduced on the Z9000.
8.3.7.0
Introduced on the S4810.
8.4.1.0
Added support for VRRP traps.
7.6.1.0
Added support for STP and xSTP notification types. Introduced on the S-Series.
7.5.1.0
Introduced on the C-Series.
E-Series legacy command
Usage Information

To configure the router to send SNMP notifications, enter at least one snmp-server host command. If you enter the command with no keywords, all trap types are enabled for the host. If you do not enter an snmp-server host command, no notifications are sent.

In order to enable multiple hosts, issue a separate snmp-server host command for each host. You can specify multiple notification types in the command for each host.

When multiple snmp-server host commands are given for the same host and type of notification (trap or inform), each succeeding command overwrites the previous command. Only the last snmp-server host command will be in effect. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command replaces the first command.

The snmp-server host command is used with the snmp-server enable command. Use the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to receive most notifications, at least one snmp-server enable command and the snmp-server host command for that host must be enabled.

NOTE: For v1 / v2c trap configuration, if the community-string is not defined using the snmp-server community command prior to using this command, the default form of the snmp-server community command automatically is configured with the community-name the same as specified in the snmp-server host command.
NOTE: You must configure notify option for the SNMPv3 traps to work.

Configuring Informs

To send an inform, use the following steps:
  1. Configure a remote engine ID.
  2. Configure a remote user.
  3. Configure a group for this user with access rights.
  4. Enable traps.
  5. Configure a host to receive informs.
Related Commands

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\