snmp
config>system
This command enables the context to configure SNMP parameters.
[no] engineID engine-id
config>system>snmp
This command sets the SNMP engine ID to uniquely identify the SNMPv3 node. By default, the engine ID is generated using information from the system backplane.
If the SNMP engine ID is changed in the config>system>snmp>engineID engine-id context, the current configuration must be saved and a reboot must be executed. If the configuration is not saved and the system is not rebooted, the previously configured SNMP communities and logger trap-destination notify communities will not be valid for the new engine ID.
In conformance with IETF standard RFC 3414, User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3), hashing algorithms that generate SNMPv3 MD5 or SHA security digest keys use the engine ID. Changing the SNMP engine ID invalidates all SNMPv3 MD5 and SHA security digest keys and may render the node unmanageable. If the SNMP engine ID is changed, the SNMP hash keys must be reconfigured.
This command could be used, for example, when a chassis is replaced. Use the engine ID of the first system and configure it in the new system to preserve SNMPv3 security keys. This allows management stations to use their existing authentication keys for the new system.
Ensure that the engine IDs are not used on multiple systems. A management domain can only have one instance of each engine ID.
The no form of the command reverts to the default setting.
the engine ID is system-generated
an identifier from 10 to 64 hexadecimal digits (5 to 32 octet number), uniquely identifying this SNMPv3 node. This string is used to access this node from a remote host with SNMPv3.
general-port port-number
no general-port
config>system>snmp
This command configures the port number used by this node to receive SNMP request messages and to send replies. SNMP notifications generated by the agent are sent from the port specified in the config>log>snmp-trap-group>trap-target command.
The no form of the command reverts to the default value.
161
the port number used to send SNMP traffic other than traps
packet-size bytes
no packet-size
config>system>snmp
This command configures the maximum SNMP packet size generated by this node. If the packet size exceeds the MTU size of the egress interface, the packet will be fragmented.
The no form of the command reverts to the default value.
1500 bytes
the SNMP packet size in bytes
[no] shutdown
config>system>snmp
This command administratively disables SNMP agent operations. System management can then only be performed using the CLI. Shutting down SNMP does not remove or change configuration parameters other than the administrative state. This command does not prevent the agent from sending SNMP notifications to any configured SNMP trap destinations. SNMP trap destinations are configured under the config>log>snmp-trap-group context.
This command is automatically invoked in the event of a reboot when the processing of the configuration file fails to complete or when an SNMP persistent index file fails while the bof persist on command is enabled.
The no form of the command administratively enables SNMP.
no shutdown
streaming
config>system>snmp
This command enables the proprietary SNMP request/response bundling and TCP-based transport mechanism for optimizing network management of the router nodes. In higher-latency networks, synchronizing router MIBs from network management via streaming takes less time than synchronizing via classic SNMP UDP requests. Streaming operates on TCP port 1491 and runs over IPv4 or IPv6.
[no] shutdown
config>system>snmp>streaming
This command administratively disables the proprietary SNMP request/response bundling and TCP-based transport mechanism for optimizing network management of the router nodes.
The no form of the command administratively re-enables SNMP request/response bundling and the TCP-based transport mechanism.
shutdown