Protocol Overview
Network management stations use SNMP to retrieve or alter management data from network elements.
A datum of management information is called a
managed object
; the value of a managed object can be static
or variable. Network elements store managed objects in a database called a
management information base
(MIB).
MIBs are hierarchically structured and use object identifiers to address managed objects, but managed
objects also have a textual name called an
object descriptor
.
You can download the latest MIB files from the following path:
•
https://www.force10networks.com/CSPortal20/Main/SupportMain.aspx
.
Implementation Information
The following describes SNMP implementation information.
• Dell Networking OS supports SNMP version 1 as defined by RFC 1155, 1157, and 1212, SNMP version 2c
as defined by RFC 1901, and SNMP version 3 as defined by RFC 2571.
• Dell Networking OS supports up to 16 trap receivers.
• Dell Networking OS implementation of the sFlow MIB supports sFlow configuration via SNMP sets.
• SNMP traps for the spanning tree protocol (STP) and multiple spanning tree protocol (MSTP) state
changes are based on BRIDGE MIB (RFC 1483) for STP and IEEE 802.1
draft ruzin-mstp-mib-02
for
MSTP.
SNMPv3 Compliance With FIPS
SNMPv3 is compliant with the Federal information processing standard (FIPS) cryptography standard. The
Advanced Encryption Standard (AES) Cipher Feedback (CFB) 128-bit encryption algorithm is in compliance
with RFC 3826. SNMPv3 provides multiple authentication and privacy options for user configuration. A subset
of these options are the FIPS-approved algorithms: HMAC-SHA1-96 for authentication and AES128-CFB for
privacy. The other options are not FIPS-approved algorithms because of known security weaknesses. The
AES128-CFB privacy option is supported and is compliant with RFC 3826.
The SNMPv3 feature also uses a FIPS-validated cryptographic module for all of its cryptographic operations
when the system is configured with the
fips mode enable
command in Global Configuration mode. When
the FIPS mode is enabled on the system, SNMPv3 operates in a FIPS-compliant manner, and only the FIPS-
approved algorithm options are available for SNMPv3 user configuration. When the FIPS mode is disabled on
the system, all options are available for SNMPv3 user configuration.
The following table describes the authentication and privacy options that can be configured when the FIPS
mode is enabled or disabled:
Simple Network Management Protocol (SNMP)
980
Содержание S4048T
Страница 1: ...Dell Configuration Guide for the S4048T ON System 9 10 0 1 ...
Страница 98: ... saveenv 7 Reload the system uBoot mode reset Management 98 ...
Страница 113: ...Total CFM Pkts 10303 CCM Pkts 0 LBM Pkts 0 LTM Pkts 3 LBR Pkts 0 LTR Pkts 0 802 1ag 113 ...
Страница 411: ...mode transit no disable Force10 Resilient Ring Protocol FRRP 411 ...
Страница 590: ...Figure 67 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 590 ...
Страница 591: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 591 ...
Страница 594: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command Link Aggregation Control Protocol LACP 594 ...
Страница 595: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 595 ...
Страница 646: ...Figure 87 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 646 ...
Страница 647: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 647 ...
Страница 648: ...Figure 89 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 648 ...
Страница 653: ...Figure 91 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 653 ...
Страница 654: ...Figure 92 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 654 ...
Страница 955: ...Figure 119 Single and Double Tag First byte TPID Match Service Provider Bridging 955 ...
Страница 1179: ...Figure 147 Create Hypervisor Figure 148 Edit Hypervisor Figure 149 Create Transport Connector Virtual Extensible LAN VXLAN 1179 ...