Command Modessnmp-server community
form of this command.
Syntax Description
Command Modes
Usage GuidelinesYou can assign an access list (ACL) to a community to filter incoming SNMP requests. If the assigned ACL allows the incoming request packet, SNMP processes the request. If the ACL denies the request, SNMP drops the request and sends a system message.
for more information on creating ACLs. The ACL applies to both IPv4 and IPv6 over UDP and TCP. After creating the ACL, assign the ACL to the SNMP community.
snmp-server context
form of this command.
Syntax Description
Command Modes
Usage Guidelinescommand to map between SNMP contexts and logical network entities, such as protocol instances or VRFs.
snmp-server enable traps
form of this command.
Syntax Description
Command Modes
Usage Guidelinescommand enables both traps and informs, depending on the configured notification host receivers.
snmp-server enable traps link
form of this command.
Syntax Description
Command Modes
Usage GuidelinesThis command is disabled by default. Most notification types are disabled.
arguments, the default is to enable all notification types controlled by this command
Command Modessnmp-server host
form of this command.
Syntax Description
Command Modes
Usage GuidelinesSNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver does not send acknowledgments when it receives traps. The sender cannot determine if the traps were received. However, an SNMP entity that receives an inform request acknowledges the message with an SNMP response PDU. If the sender never receives the response, the inform request can be sent again. Therefore, informs are more likely to reach their intended destination.
Command Modes
Command Modes
Command Modessnmp-server user
form of this command.
Syntax Description
Command Modes
Command ModesVirtual Ethernet interface configuration mode
Usage GuidelinesBy default, SNMP link traps are sent when a Layer 2 interface goes up or down. You can disable SNMP link trap notifications on an individual interface. You can use these limit notifications on a flapping interface (an interface that transitions between up and down repeatedly).
You can use this command on the following interfaces:
![]()
Note Use the no switchport command to configure an interface as a Layer 3 interface.
ExamplesThis example shows how to disable SNMP link-state traps for a specific Layer 2 interface:
This example shows how to enable SNMP link-state traps for a specific Layer 3 interface:
This example shows how to enable SNMP link-state traps for a specific Layer 2 interface:
This example shows how to enable SNMP link-state traps for a specific virtual Ethernet interface:
source (SPAN, ERSPAN)
form of this command.
}
}
Syntax Description
Command ModesERSPAN session configuration mode
Command History
Usage Guidelines) is a switched port that you monitor for network traffic analysis. In a single local SPAN session, you can monitor source port traffic such as received (Rx), transmitted (Tx), or bidirectional (both).
A source port can be an Ethernet port, port channel, SAN port channel, VLAN, or a VSAN port. It cannot be a destination port.
![]()
Note For Cisco NX-OS Release 4.2(1)N2(1) and earlier, the Cisco Nexus 5010 Switch and the Cisco Nexus 5020 Switch supports a maximum of two egress SPAN source ports.
Beginning with Cisco NX-OS Release 5.0(2)N2(1):
- There is no limit to the number of egress SPAN source ports.
- SAN Port Channel interfaces can be configured as ingress or egress source ports.
- The limit on the number of egress (TX) sources in a monitor session has been lifted.
- Port-channel interfaces can be configured as egress sources.
, the source traffic is analyzed for both directions.
Command Modesswitch-profile
form of this command.
Syntax Description
Command ModesConfiguration synchronization mode
Usage GuidelinesUse this command to create a switch profile on each of the peer switches. You must use the same profile name on both the switches in the Cisco Fabric Services (CFS) peer configuration.
![]()
Note In this release of Cisco NX-OS, only a pair of switches can be configured as a peer.
You can configure only one active switch profile on each peer switch. If you create or configure a second switch profile, you see the following error message:
The configuration that is made locally on the switch is synchronized and made available on the peer switch only after the connectivity is established between the peer switches and the configuration is verified and committed on the local switch.
You can configure a switch profile to include the interface configuration, quality of service (QoS), and virtual port channel (vPC) commands. FCoE commands are not supported on a switch profile.
When you delete a switch profile, you can choose to delete the local switch profile with the local configurations on the switch, delete the switch profile with the local configurations and configuration information in the peer, or delete the switch profile only while saving all other configuraiton information. The peer becomes unreachable.