Users Guide

Module Standard
SFLOW-MIB RFC 3176
SNMP-FRAMEWORK-MIB RFC 3411
SNMP-MPD-MIB RFC 3412
SNMP-NOTIFICATION-MIB RFC 3413
SNMP-TARGET-MIB RFC 3413
SNMP-USER-BASED-SM-MIB RFC 3414
SNMP-VIEW-BASED-ACM-MIB RFC 3415
SNMPv2-MIB RFC 3418
TCP-MIB RFC 4022
UDP-MIB RFC 4113
Table 4. Dell EMC Enterprise MIBs
Module Description
DELLEMC-OS10-BGP4V2-MIB OS10 BGPv2 implementations
DELLEMC-OS10-CHASSIS-MIB OS10 chassis implementations
DELLEMC-OS10-PRODUCTS-MIB OS10 platform product denitions
DELLEMC-OS10-SMI-MIB OS10 SMI implementations
DELLEMC-OS10-TC-MIB OS10 networking equipment textual convention
NOTE: To monitor BGP, OS10 supports the Dell EMC proprietary MIB, DELLEMC-OS10-BGP4V2-MIB.mib. OS10 returns a No
such object message when you use the standard BGP4-MIB with OID 1.3.6.1.2.1.15. Use OID 1.3.6.1.4.1.674.11000.5000.200.1.1
for BGP-related MIB objects.
SNMPv3
SNMP version 3 (SNMPv3) provides an enhanced security model for user authentication and SNMP message encryption. User
authentication requires that SNMP packets come from an authorized source. Message encryption ensures that packet contents cannot be
viewed by an unauthorized source.
To congure SNMPv3-specic security settings — user authentication and message encryption — use the snmp-server user
command. You can generate localized keys with enhanced security for authentication and privacy (encryption) passwords.
SNMP engine ID
An engine ID identies the SNMP entity that serves as the local agent on the switch. The engine ID is an octet colon-separated number; for
example, 00:00:17:8B:02:00:00:01.
When you congure an SNMPv3 user, you can specify that a localized authentication and/or privacy key be generated. The localized
password keys are generated using the engine ID of the switch. A localized key is more complex and provides greater privacy protection.
The engine ID used to generate the password keys is unique to the switch. For this reason, you cannot copy and use localized SNMP
security passwords on another switch.
System management
117