Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
You can configure the SNMP User string using the below command:
Command
[no] snmp-server user <user_name> priv_type [AuthNoPriv/Priv/noAuthNoPriv] access [RO/RW] auth [HMAC-SHA-2/MD5/SHA] auth-password <auth_password>
Description
SNMP user configuration
Parameters
user value, privilege type, access type, encryption type, password value
Mode
CONFIG
You can verify the configuration by using the command(s) below:
Simple Network Management Protocol (SNMP) is an Internet Standard protocol for collecting and organizing information about managed devices on IP networks and for modifying that information to change device behaviour.
SNMP is widely used in network management for network monitoring. SNMP exposes management data in the form of variables on the managed systems organized in a Management Information Base (MIB) which describes the system status and configuration. These variables can then be remotely queried (and, in some circumstances, manipulated) by managing applications.
Traps are used when the Device needs to alert the Network Management software of an event without being polled. Traps ensure that the NMS gets information if a certain event occurs on the device that needs to be recorded without being polled by the NMS first. Managed network devices will have Trap MIBs with predefined conditions built into them. It’s crucial that the Network management system has these MIBs compiled into them to receive any traps sent by the given device/s. The primary focus of this feature is to support SNMP Trap notifications and in particular, linkUp, linkDown and config change trap notifications.
With these MIBs, you can trigger sending an SNMP trap to a configured SNMP-server host based on certain events. Also, GET/GETNext/WALK operations can be supported on these mibs. The linkUp and linkDown traps are sent to the configured host in the event that an interface Admin or Oper status changes from up to down or vice-versa. The configChange trap monitors NPB (MAP, rule, port-npb config) and port (Speed, MTU, FEC, Autoneg) configuration changes. A configChangeTrap PDU is sent to the host when any value in these tables are modified, added or removed.
It's recommended not to set up more than 4 SNMP-Trap servers.
You can verify the configuration by using the command(s) below:
Traps are only supported on SNMPv2c
Below commands can be used to disable FAN/PSU traps temporarily,
By default, traps are generated every 60 seconds, which may cause unnecessary stress on memory and CPU. To mitigate this, disabling the default behaviour using the above command is recommended for disabling PSU and FAN traps.
This will result in traps being generated only when the PSU/FAN state changes, reducing the load on memory and CPU.
Command
[no] snmp-server location <location_name>
Description
SNMP location configuration
Parameters
SNMP location
Mode
CONFIG
Command
[no] snmp-server trap <cpu-util/mem-util> threshold <%>
Description
SNMP trap threshold configuration
Parameters
SNMP threshold
Mode
CONFIG
Command
[no] snmp-server community <string>
Description
SNMP community configuration
Parameters
SNMP community string
Mode
CONFIG
Command
[no] snmp-server trap modify <version><ip4addr|ip6addr> [port <value>] [community
<value>]
Description
SNMP trap configuration
Parameters
Version, IPv4 or v6 Address , port, community values
Mode
CONFIG
Command
snmp-server trap (psu-util/fan-util) disable
Description
disable PSU/FAN traps temperoraly
Parameters
FAN/PSU
Mode
EXEC
You can configure the SNMP Contact string using the below command:
Command
[no] snmp-server contact contact-name <contact_name> contact-mail <Contact_mail>
Description
SNMP contact configuration
Parameters
SNMP contact
Mode
CONFIG
You can verify the configuration by using the command(s) below: