- sampler
- sampling
- save
- scheduler
- shut
- sleep instance
- snapshot create
- snapshot delete
- snapshot section
- snmp-server aaa-user cache-timeout
- snmp-server community
- snmp-server contact
- snmp-server context
- snmp-server enable traps
- snmp-server globalEnforcePriv
- snmp-server host
- snmp-server host filter-vrf
- snmp-server host use-vrf
- snmp-server location
- snmp-server mib community-map
- snmp-server p acketsize
- snmp-server protocol enable
- snmp-server source-interface
- snmp-server tcp-session
- snmp-server user
- snmp-server user enforcePriv
- snmp-trap
- source
- source
- source exception
- switchport monitor
- switchport monitor exclude header
- system cores
- system default switchport monitor exclude header
- system hap-reset
- system heartbeat
- system mode maintenance
- system mode maintenance always-use-custom-profile
- system mode maintenance dont-generate-profile
- system mode maintenance non-interactive
- system mode maintenance on-reload reset-reason
- system mode maintenance shutdown
- system mode maintenance snapshot-delay
- system mode maintenance timeout
- system no hap-reset
- system no heartbeat
- system no standby manual-boot
- system no watchdog
- system no watchdog kgdb
- system pss shrink
- system scale-limit monitor
- system standby manual-boot
- system startup-config init
- system startup-config unlock
- system test-preupgrade running-ver
- system switchover
- system trace
- system watchdog
- system watchdog kgdb
S Commands
This chapter describes the Cisco NX-OS system management commands that begin with the letter S, excluding the show commands.
sampler
To define a sampler and enter the sampler configuration mode, use the sampler command. To remove the sampler definition, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
NetFlow sampling means that M out of N packets are sampled. When a packet is sampled and there is a NetFlow cache miss, a NetFlow cache entry is created for this flow. The first packet timestamp is updated and the statistics for the first packet are initialized (for example, the bytes are set to the number of bytes in the packet and the packet count is set to one). If there is a NetFlow cache hit when the packet is sampled, the cache for this flow is updated, which includes adding the number of bytes in the packet to the byte counter and incrementing the packet count by one.
Once you enter the sampler name command, you enter the sampler configuration mode, and the prompt changes to the following:
Within the sampler configuration mode, the following keywords and arguments are available to configure the flow monitor:
- description description —Provides a description for this sampler; you can add a maximum of 63 characters.
- exit —Exits from the current configuration mode.
- mode sample-num out-of packets —Configures the sampler mode. The valid values are as follows:
– sample-num —Number of samples per sampling. The range is from 1 to 64.
– out-of —Specifies the samples per packet ratio.
– packets —Number of packets in each sampling. The range is from 1 to 8192.
Examples
This example shows how to define a sampler and enter the sampler configuration mode:
This example shows how to configure the sampler mode:
This example shows how to remove a sampler definition:
Related Commands
|
|
---|---|
sampling
To set the sampling range for Switched Port Analyzer (SPAN) packets, use the sampling command. To revert to the default settings, use the no form of this command.
Syntax Description
Sampling range. Every nth packet will be spanned. The range is from 2 to 1023. |
Defaults
Command Modes
Sampling only applies to local SPAN (config-monitor) and ERSPAN source session (config-monitor-erspan-src) configuration.
Command History
|
|
---|---|
Usage Guidelines
Examples
This example shows how to set the sampling range for the SPAN packets:
Related Commands
|
|
---|---|
save
To save the current configuration session to a file, use the save command.
Syntax Description
Location of the file. The location can be in bootflash:, slot0:, or volatile: The filename can be any alphanumeric string up to 63 characters. |
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to save a configuration session to a file in bootflash:
switch# configure session myACLs
Related Commands
|
|
---|---|
scheduler
To create or schedule a scheduler job, use the scheduler command. To remove a job or scheduled job, use the no form of this command.
scheduler {aaa-authentication [username username] password [0 | 7] password |
job name job-name | logfile size filesize | schedule name schedule-name }
no scheduler {aaa-authentication [username username] password [0 | 7] password |
job name job-name | logfile size filesize | schedule name schedule-name }
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
To use this command, the scheduler must already be enabled.
To enable the scheduler, use the feature scheduler command.
Remote users must authenticate with the device using the scheduler aaa-authentication command before using this command to configure a maintenance job.
Note The commands within a scheduler job must be entered in a single line separated by semicolon (;).
Examples
This example shows how to create a scheduler job that saves the running configuration to a file in bootflash and then copies the file from bootflash to a TFTP server. The filename is created using the current timestamp and switch name.
switch(config)# scheduler job name backup-cfg
switch(config-job)#
cli var name timestamp $(TIMESTAMP);copy running-config bootflash:/$(SWITCHNAME)-cfg.$(timestamp);copy bootflash:/$(SWITCHNAME)-cfg.$(timestamp) tftp://1.2.3.4/ vrf management
switch(config-job)# end
switch(config)#
This example shows how to schedule a scheduler job to run daily at 1:00 a.m:
switch(config)#
scheduler schedule name daily
switch(config-schedule)#
job name backup-cfg
switch(config-schedule)# end
switch(config)#
This example shows how to remove a scheduler job:
This example shows how to remove a scheduler job schedule:
This example shows how to specify the password for a remote user:
This example shows how to specify a clear text password for a remote user:
This example shows how to specify an encrypted password for a remote user:
This example shows how to specify a name and authentication password for a remote user:
Related Commands
|
|
---|---|
shut
To shut down an Ethernet Switched Port Analyzer (SPAN) session, use the shut command. To enable a SPAN session, use the no form of this command.
Syntax Description
Defaults
Command Modes
Monitor-common configuration (config-monitor)
Command History
|
|
Usage Guidelines
Examples
This example shows how to shut down a SPAN session:
switch(
config)#
monitor session 1
switch(
config-monitor)#
shut
This example shows how to enable a SPAN session:
switch(
config-monitor)#
no shut
switch(
config-monitor)#
Related Commands
|
|
---|---|
sleep instance
To delay the execution of a command by a specified number of seconds in the maintenance profile, use the sleep instance command. You can delay multiple instances of a command. To remove the delay, use the no form of this command.
sleep instance instance-number seconds
no sleep instance instance-number seconds
Syntax Description
Defaults
Command Modes
maintenance profile configuration (config-mm-profile)
Command History
|
|
Usage Guidelines
Examples
This example shows how to delay the execution of one command by 20 seconds and another command by 10 seconds:
switch#
configure maintenance profile normal-mode
Please configure 'system mode maintenance always-use-custom-profile' if you want to use custom profile always for maintenance mode.
Enter configuration commands, one per line. End with CNTL/Z.
switch(config-mm-profile)#
interface ethernet 1/1
switch(config-mm-profile-if-verify)#
no shutdown
switch(config-mm-profile-if-verify)#
exit
switch(config-mm-profile)#
sleep instance 1 20
switch(config-mm-profile)#
router bgp 200
switch(config-mm-profile-router)#
address-family ipv4 unicast
switch(config-mm-profile-router-af)#
redistribute direct route-map my-rmap-deny
switch(config-mm-profile-router-af)#
exit
switch(config-mm-profile-router)#
exit
switch(config-mm-profile)#
sleep instance 1 10
Related Commands
snapshot create
To create a snapshot, use the snapshot create command.
snapshot create name description
Syntax Description
Defaults
Command History
|
|
Examples
This example shows how to create a snapshot:
Related Commands
|
|
---|---|
Compares snapshots and showing the summary and details of each feature. |
snapshot delete
To delete a single snapshot or to delete all the snapshots in a system, use the snapshot delete command.
snapshot delete { all | snapshot-name }
Syntax Description
Defaults
Command History
|
|
Usage Guidelines
Examples
This example shows how to delete all the snapshots in a system:
This example shows how to delete a specific snapshot:
Related Commands
|
|
---|---|
snapshot section
To add or delete a snapshot section, use the snapshot section command.
snapshot section { add section “show-command” row-id element-key1 [ element-key2 ] | delete section }
Syntax Description
Defaults
Command History
|
|
Usage Guidelines
Examples
This example shows how to add a snapshot section that displays the output of the show ip route detail vrf all command to the snapshot:
This example shows how to delete a snapshot section from the snapshot:
Related Commands
|
|
---|---|
snmp-server aaa-user cache-timeout
To configure the Simple Network Management Protocol (SNMP) time-out value for synchronized AAA users, use the snmp-server aaa-user cache-timeout command. To revert to the default settings, use the no form of this command.
snmp-server aaa-user cache-timeout seconds
no snmp-server aaa-user cache-timeout seconds
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure the AAA user synchronization timeout value:
Related Commands
|
|
---|---|
snmp-server community
To configure the Simple Network Management Protocol (SNMP) community string, use the snmp-server community command. To remove the community string, use the no form of this command.
snmp-server community name [group name | ro | rw]
no snmp-server community name [group name | ro | rw]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server community command to configure read-only or read-write access to the SNMP agent on the device. You can optionally configure the community for an access group or user role. For more information on user roles, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x.
Examples
This example shows how to configure a read-only SNMP community:
Related Commands
|
|
---|---|
snmp-server contact
To configure the Simple Network Management Protocol (SNMP) contact information, use the snmp-server contact command. To remove the contact information, use the no form of this command.
snmp-server contact [ contact-info ]
no snmp-server contact [ contact-info ]
Syntax Description
(Optional) SNMP contact information (sysContact). The name can be any alphanumeric string up to 255 characters. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server contact command to configure the SNMP sysContact variable.
Examples
This example shows how to configure the SNMP contact:
Related Commands
|
|
---|---|
snmp-server context
To configure the Simple Network Management Protocol (SNMP) context to logical network entity mapping, use the snmp-server context command. To remove the context, use the no form of this command.
snmp-server context context-name [ instance instance-name ] [ vrf vrf-name ] [ topology topology-name ]
no snmp-server context context-name [ instance instance-name ] [ vrf vrf-name ] [ topology topology-name ]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server context command to map between SNMP contexts and logical network entities, such as protocol instances or VRFs.
Do not use the instance, vrf, or topology keywords to delete a context. If you use these keywords, you map the context to a zero-length string.
If you are using SNMPv2c, use the snmp-server mib community-map command to map an SNMPv2c community to an SNMP context and use the snmp-server context command to map this context to a logical network entity.
For more information on context mapping, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x.
Examples
This example shows how to map the public1 context to VRF red:
Related Commands
|
|
---|---|
snmp-server enable traps
To enable the Simple Network Management Protocol (SNMP) notifications, use the snmp-server enable traps command. To disable SNMP notifications, use the no form of this command.
snmp-server enable traps [ aaa [ server-state-change ] | bgp [ cbgp2 ] | bridge [ newroot ] [ topologychange ] | callhome [ event-notify ] [ smtp-send-fail ] | cfs [ merge-failure ] [ state-change-notif ] | config [ ccmCLIRunningConfigChanged ] | eigrp | entity [ entity_fan_status_change ] [ entity_mib_change ] [ entity_module_inserted ] [ entity_module_removed ] [ entity_module_status_change ] [ entity_power_out_change ] [ entity_power_status_change ] [ entity_unrecognised_module ] | feature-control [ FeatureOpStatusChange ] | hsrp [ state-change ] | license [ notify-license-expiry ] [ notify-license-expiry-warning ] [ notify-licensefile-missing ] [ notify-no-license-for-feature ] | link [ IETF-extended-linkDown ] [ IETF-extended-linkUp ] [ cisco-extended-linkDown ] [ cisco-extended-linkUp ] [ linkDown ] [ linkUp ] | ospf instance-tag [ lsa | rate-limit rate ] | port-security [ access-secure-mac-violation ] [ trunk-secure-mac-violation ] | rf [ redundancy_framework ] | rmon [ fallingAlarm | hcFallingAlarm | hcRisingAlarm | risingAlarm ] | snmp [ authentication ] | stpx [ inconsistency ] [ loop-consistency ] [ root-inconsistency ] | sysmgr [ cseFailSwCoreNotifyExtended ] | upgrade [UpgradeJobStatusNotify] [ UpgradeOpNotifyOnCompletion ] | zone [ default-zone-behavior-change ] [ merge-failure ] [ merge-success ] [ request-reject1 ] [ unsupp-mem ] | vtp [ notifs | vlancreate | vlandelete ]]
no snmp-server enable traps [ aaa [ server-state-change ] | bgp [ cbgp2 ] | bridge [ newroot ] [ topologychange ] | callhome [ event-notify ] [ smtp-send-fail ] | cfs [ merge-failure ] [ state-change-notif ] | config [ ccmCLIRunningConfigChanged ] | eigrp | entity [ entity_fan_status_change ] [ entity_mib_change ] [ entity_module_inserted ] [ entity_module_removed ] [ entity_module_status_change ] [ entity_power_out_change ] [ entity_power_status_change ] [ entity_unrecognised_module ] | feature-control [ FeatureOpStatusChange ] | hsrp [ state-change ] | license [ notify-license-expiry ] [ notify-license-expiry-warning ] [ notify-licensefile-missing ] [ notify-no-license-for-feature ] | link [ IETF-extended-linkDown ] [ IETF-extended-linkUp ] [ cisco-extended-linkDown ] [ cisco-extended-linkUp ] [ linkDown ] [ linkUp ] | ospf instance-tag [ lsa | rate-limit rate ] | port-security [ access-secure-mac-violation ] [ trunk-secure-mac-violation ] | rf [ redundancy_framework ] | rmon [ fallingAlarm | hcFallingAlarm | hcRisingAlarm | risingAlarm ] | snmp [ authentication ] | stpx [ inconsistency ] [ loop-consistency ] [ root-inconsistency ] | sysmgr [ cseFailSwCoreNotifyExtended ] | upgrade [UpgradeJobStatusNotify] [ UpgradeOpNotifyOnCompletion ] | zone [ default-zone-behavior-change ] [ merge-failure ] [ merge-success ] [ request-reject1 ] [ unsupp-mem ] | vtp [ notifs | vlancreate | vlandelete ]]
Syntax Description
Defaults
Command Modes
Command History
|
|
Added the cfs, config, feature-control, rmon, and zone keywords. |
|
Usage Guidelines
Examples
This example shows how to enable BGP notifications:
This example shows how to enable VTP notifications:
Related Commands
|
|
---|---|
Displays the enable or disable state of all SNMP notifications. |
snmp-server globalEnforcePriv
To globally enforce privacy for all Simple Network Management Protocol (SNMP) users, use the snmp-server globalEnforcePriv command. To disable global privacy, use the no form of this command.
no snmp-server globalEnforcePriv
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server globalEnforcePriv command to enforce privacy on all SNMP users.
Examples
This example shows how to globally enforce privacy for all SNMP contacts:
Related Commands
|
|
---|---|
snmp-server host
To specify the server host to receive Simple Network Management Protocol (SNMP) notifications, use the snmp-server ho st command. To remove the SNMP server configuration, use the no form of this command.
snmp-server host host-name { snmp-name | filter-vrf {vrf-name | default | management}} | informs { snmp-name | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}}} | source-interface {ethernet number | loopback number | mgmt number | port-channel number | vlan number} | traps { snmp-name | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}} | use-vrf {vrf-name | default | management} | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}} udp-port port
no snmp-server host host-name { snmp-name | filter-vrf {vrf-name | default | management}} | informs { snmp-name | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}}} | source-interface {ethernet number | loopback number | mgmt number | port-channel number | vlan number} | traps { snmp-name | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}} | use-vrf {vrf-name | default | management} | version {1 snmp-name | 2c snmp-name | 3 {auth snmp-name | noauth snmp-name | priv snmp-name}} udp-port port
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
The source-interface configuration overrides the global source-interface configuration.
Examples
This example shows how to configure an SNMP server host:
This example shows how to remove an SNMP server host:
Related Commands
|
|
---|---|
snmp-server host filter-vrf
To configure a Simple Network Management Protocol (SNMP) host receiver to gather notifications that occur on a specific virtual routing and forwarding (VRF) instance, use the snmp-server host filter-vrf command. To remove the VRF filter, use the no form of this command.
snmp-server host host-address filter-vrf vrf-name [ udp-port port ]
no snmp-server host host-address filter-vrf vrf-name [ udp-port port ]
Syntax Description
Name of the VRF. The name can be any alphanumeric string up to 63 characters. |
|
(Optional) Specifies the port UDP port of the host to use. The range is from 0 to 65535. The default is 162. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
This example shows how to configure the host receiver to receive notifications from the red VRF.
Related Commands
|
|
---|---|
Configures Cisco NX-OS to send notifications on the specified VRF to communicate with an SNMP host receiver. |
snmp-server host use-vrf
To configure the device to communicate with a Simple Network Management Protocol (SNMP) host receiver on a specific virtual routing and forwarding (VRF) instance, use the snmp-server host use-vrf command. To return to the default, use the no form of this command.
snmp-server host host-address use-vrf vrf-name [ udp-port port ]
no snmp-server host host-address use-vrf vrf-name [ udp-port port ]
Syntax Description
Name of the VRF. The name can be any alphanumeric string up to 63 characters. |
|
(Optional) Specifies the port UDP port of the host to use. The range is from 0 to 65535. The default is 162. |
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
This example shows how to configure Cisco NX-OS to communicate with the host receiver on the blue VRF.
Related Commands
|
|
---|---|
Sends only notifications on the specified VRF to the host receiver. |
snmp-server location
To configure the device location used by the Simple Network Management Protocol (SNMP), use the snmp-server location command. To remove the location, use the no form of this command.
snmp-server location [ location ]
no snmp-server location [ location ]
Syntax Description
(Optional) System location. The location can be any alphanumeric string up to 255 characters. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to set the SNMP location:
Related Commands
|
|
---|---|
snmp-server mib community-map
To configure the Simple Network Management Protocol (SNMP) version 2c community to context mapping, use the snmp-server mib community-map command. To remove the community to context mapping, use the no form of this command.
snmp-server mib community-map community-string context context-name
no snmp-server mib community-map community-string context context-name
Syntax Description
SNMP community string. The string can be any alphanumeric string up to 32 characters. |
|
Specifies the SNMP context. The name can be any alphanumeric string up to 32 characters. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server mib community-map command to map between SNMPv2c communities and SNMP contexts. Use the snmp-server context command to map this context to a logical network entity.
For more information on context mapping, see the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 6.x.
Examples
This example shows how to map the public community to the public1 context:
Related Commands
|
|
---|---|
snmp-server packetsize
To establish control over the largest Simple Network Management Protocol (SNMP) packet size permitted when the SNMP server is receiving a request or generating a reply, use the snmp-server packetsize command. To restore the default, use the no form of this command.
snmp-server packetsize byte-count
no snmp-server packetsize byte-count
Syntax Description
Command Default
Command Modes
Command History
|
|
Usage Guidelines
Examples
The following example establishes a packet filtering of a maximum size of 1024 bytes:
snmp-server protocol enable
To enable the Simple Network Management Protocol (SNMP), use the snmp-server protocol enable command. To disable SNMP, use the no form of this command.
no snmp-server protocol enable
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the no snmp protocol enable command to disable SNMP and close any TCP or UDP ports associated with the protocol.
Examples
This example shows how to disable SNMP:
snmp-server source-interface
To configure a Simple Network Management Protocol (SNMP) source interface through which notifications are sent, use the snmp-server source-interface command. To remove the SNMP source interface configuration, use the no form of this command.
snmp-server source-interface { traps | informs } { ethernet number | loopback number | mgmt number | port-channel number | vlan number }
no snmp-server source-interface { traps | informs } { ethernet number | loopback number | mgmt number | port-channel number | vlan number }
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure an SNMP source interface:
This example shows how to remove the SNMP source interface:
Related Commands
|
|
---|---|
snmp-server tcp-session
To enable one-time authentication for Simple Network Management Protocol (SNMP) over a TCP session, use the snmp-server tcp-session command. To disable one-time authentication for SNMP over a TCP session, use the no form of this command.
snmp-server tcp-session [ auth ]
no snmp-server tcp-session [ auth ]
Syntax Description
(Optional) Enables one-time authentication for SNMP over a TCP session. |
Defaults
One-time authentication for SNMP over a TCP session is enabled.
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to enable one-time authentication for SNMP over a TCP session.
Related Commands
|
|
---|---|
snmp-server user
To configure the Simple Network Management Protocol (SNMP) user information, use the snmp-server user command. To disable the configuration or to revert to factory defaults, use the no form of this command.
snmp-server user username [ group-name ] [ auth { md5 | sha } password [ priv [ aes-128] password ] [localizedkey] [engineID id ]
no snmp-server user username [ group-name ] [ auth { md5 | sha } password [ priv [ aes-128] password ] [localizedkey] [engineID id ]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Use the snmp-server use r command to configure user authentication and privacy settings for SNMP. If you use the localizedkey keyword, you cannot port the SNMP user configuration across devices because the user password contains information on the engine ID of the device. If you copy a configuration file into the device, the passwords may not be set correctly if the configuration file was generated at a different device. We recommend that you explicitly configure passwords after copying the configuration into the device.
SNMP Version 3 is the most secure model, because it allows packet encryption with the priv keyword.
To assign multiple roles to a user, configure multiple snmp-server user username group-name commands. The group-name argument is defined by the role name command.
If you are configuring an SNMP notification target user, use the engineID keyword to configure the SNMP engine ID for this user.
To delete the user or the role associated with that user, use the no form of this command.
Note You cannot delete the last role for a user.
Examples
This example shows how to set the user authentication information for user jane:
This example shows how to multiple roles for user sam:
This example shows how to set user authentication and privacy information for user Juan:
This example shows how to set user authentication and SNMP engine ID for a notification target user:
Related Commands
|
|
---|---|
snmp-server user enforcePriv
To enforce privacy for a Simple Network Management Protocol (SNMP) user, use the snmp-server user enforcePriv command. To revert to factory defaults, use the no form of this command.
snmp-server user username enforcePriv
no snmp-server user username enforcePriv
Syntax Description
Name of the user. The name can be any case-sensitive, alphanumeric string up to 32 characters. |
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to enforce privacy for the user joe:
Related Commands
|
|
---|---|
snmp-trap
To generate a Simple Network Management Protocol (SNMP) trap when an Embedded Event Manager (EEM) applet is triggered, use the snmp-trap command.
snmp-trap [ intdata1 integer-data1 ] [ intdata2 integer-data2 ] [ strdata string-data ] event-type ev_type policy-name name
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to generate an SNMP trap when an EEM applet is triggered:
Related Commands
|
|
---|---|
Configures a syslog message to generate when an Embedded Event Manager (EEM) applet is triggered. |
source
To configure the NetFlow exporter interface to use to reach the NetFlow collector for the configured destination, use the source command. To remove the source, use the no form of this command.
no source [ if-type if-number ]
Syntax Description
Defaults
Command Modes
NetFlow exporter configuration (config-flow-exporter)
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure the NetFlow exporter source interface:
switch(config)#
flow exporter Netflow-Exporter-1
This example shows how to remove the Netflow exporter source interface configuration:
Related Commands
|
|
---|---|
source
To configure sources and the traffic direction in which to copy packets, use the source command. To remove sources, use the no form of this command.
source { exception {all | fabricpath | layer3 | other} | interface { all | ethernet { slot-number / port-number | range }| port-channel { port-channel-number | range } | sup-eth inband-interface-number } | vlan { number | range } [ both | rx | tx]}
no source { exception {all | fabricpath | layer3 | other} | interface { all | ethernet { slot-number / port-number | range }| port-channel { port-channel-number | range } | sup-eth inband-interface-number } | vlan { number | range } [ both | rx | tx]}
Syntax Description
Defaults
Command Modes
Monitor configuration (config- monitor)
Command History
|
|
You can use the all keyword to enable the monitor session to monitor all VLANs and ports in the VDC such as physical ports, Port Channels, FEX ports and FEX Port Channels. |
|
Usage Guidelines
You can configure one or more sources, as either a series of comma-separated entries, or a range of numbers. You can specify up to 128 interfaces.
Examples
This example shows how to configure sources and the traffic direction in which to copy packets:
This example shows how to remove a source configuration:
no source vlan 3, 6-10 tx
This example shows how to enable the monitor session to monitor all VDC ports:
Related Commands
|
|
---|---|
Copies the running configuration to the startup configuration. |
source exception
To configure the source as an exception Ethernet Switched Port Analyzer (SPAN) or Encapsulated Remote Switched Port Analyzer (ERSPAN) session, use the source exception command. To remove the source as an exception SPAN or ERSPAN session, use the no form of this command.
source exception {layer3 | fabricpath | other | all}
no source exception {layer3 | fabricpath | other | all}
Syntax Description
Defaults
Command Modes
config-monitor mode (for a SPAN session)
config-erspan-src mode (for an ERSPAN session)
Command History
|
|
Usage Guidelines
M1 and M2 Series modules support exception SPAN only in the nonadministration virtual device context (VDC), and at least one interface of the module must be present for the VDC.
Examples
This example shows how to configure the source as an exception SPAN session:
switch(
config)#
monitor session 1
switch(
config-monitor)#
source exception all
This example shows how to configure the source as an exception ERSPAN session:
switch(config-erspan-src)# source exception all
Related Commands
|
|
---|---|
switchport monitor
To configure the switchport interface as a Switched Port Analyzer (SPAN) destination, use the switchport monitor command. To disable the configuration, use the no form of this command.
switchport monitor [ingress [learning]]
no switchport monitor [ingress [learning]]
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure the Ethernet interface 7/2 as a SPAN destination:
This example shows how to configure the Ethernet interface 7/2 as a SPAN destination and allow it to inject packets and learn MAC addresses:
This example shows how to disable the SPAN destination on Ethernet interface 7/2:
Related Commands
|
|
---|---|
Enters the monitor configuration mode for configuring a SPAN session. |
|
switchport monitor exclude header
To remove the FabricPath and VLAN tag headers for the specified SPAN destination ports in the VDC, use the switchport monitor exclude header command. To disable the configuration, use the no form of this command.
switchport monitor exclude header
no switchport monitor exclude header
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
This command does not require a license.
When you enter both the global and port-level configurations for this feature, the port-level overrides the global configuration.
Examples
This example shows how to configure the Ethernet interface 7/2 to remove the FabricPath and VLAN tag headers to SPAN destination ports:
Related Commands
|
|
---|---|
Displays the configuration for removing the FabricPath and VLAN tag headers from specified SPAN destination ports. |
system cores
To configure the destination for the system core, use the system cores command. To revert to the default, use the no form of this command.
system cores { slot0: [ path ] | tftp:/ server // [ path / ]} filename
Syntax Description
Defaults
Command Modes
Command History
|
|
---|---|
Usage Guidelines
Examples
This example shows how to configure a core file:
This example shows how to disable system core logging:
Related Commands
|
|
---|---|
system default switchport monitor exclude header
To remove the FabricPath and VLAN tag headers for all SPAN destination ports in the VDC, use the system default switchport monitor exclude header command. To disable the configuration, use the no form of this command.
system default switchport monitor exclude header
no system default switchport monitor exclude header
Syntax Description
Defaults
Command Modes
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure all SPAN destination ports to remove the FabricPath and VLAN tag headers:
Related Commands
|
|
---|---|
Displays the configuration for removing the FabricPath and VLAN tag headers from all SPAN destination ports. |
system hap-reset
To enable the Supervisor Reset high availability (HA) policy, use the system hap-reset command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to enable the Supervisor Reset HA policy:
switch(config)#
system hap-reset
switch(config)#
Related Commands
|
|
---|---|
Displays the status of the system standby manual boot option. |
system heartbeat
To enable heartbeat checks (default) and revert to the factory default, use the system heartbeat command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to enable the heartbeat checks (default) and revert to the factory default:
Related Commands
|
|
---|---|
Disables the heartbeat checks (default) and reverts to the factory default. |
system mode maintenance
To put the switch in maintenance mode, use the system mode maintenance command. To exit the maintenance mode and return to normal mode, use the no form of the command.
Syntax Description
Defaults
Command Modes
vdc-admin
network-operator
vdc-operator
Command History
Usage Guidelines
In Cisco NX-OS Release 7.2(0)D1(1), the default mode for Graceful Insertion and Removal (GIR) is "shutdown". The switch will use the shutdown command to bring down the protocols and shut down the physical ports.
Starting with Cisco NX-OS Release 7.3(0)D1(1),the default mode for GIR is ïsolate". The switch will use the isolate command to isolate the protocols from the network. The switch will then be isolated from the network but is not shut down.
Starting with Cisco NX-OS release 8.0(1), the [no] system mode maintenance command has been enhanced to execute a normal mode profile and activate a timer ensuring that sufficient time is provided for the switch to complete any hardware programming that may be going on before the after_maintenance snapshot is taken. Once the timer expires, the after_maintenance snapshot is taken in the background and a new warning syslog message, MODE_SNAPSHOT_DONE, is sent after the snapshot is complete. The default delay timer value is 120 seconds. The output of the [no] system
mode maintenance command displays the delay timer value, in seconds, after which the
after_maintenance snapshot is generated:
Starting with Cisco NX-OS Release 8.0(1), a visible CLI indicator has been added to show that the system is in maintenance mode. For example, switch(config)# will appear as switch(maint-mode)(config)#.
Examples
This example shows how to put the switch in maintenance mode:
This example shows how to put a switch, running the Cisco NX-OS Release 8.0(1), in maintenance mode:
This example shows how to exit the maintenance mode and return to normal mode:
This example shows how to exit the maintenance mode and return to normal mode on a switch running the Cisco NX-OS Release 8.0(1):
Related Commands
system mode maintenance always-use-custom-profile
To apply the existing custom maintenance-mode profile and prevent creation of auto-generated maintenance-mode profile, use the system mode maintenance always-use-custom-profile command.
system mode maintenance always-use-custom-profile
Syntax Description
Defaults
Command Modes
Global configuration mode (config)
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
The always-use-custom-profile option forces the dont-generate-profile option to be used even if it has not been specified using the system mode maintenance command. You cannot use the "shutdown" option when the always-use-custom-profile option is being used.
Examples
This example shows how to always apply the existing custom maintenance mode profile and prevent creation of auto-generated maintenance mode profile:
Related Commands
system mode maintenance dont-generate-profile
To prevent the dynamic searching of enabled protocols and put the switch in maintenance mode by executing commands configured in a custom maintenance mode profile, use the system mode maintenance dont-generate-profile command. To exit maintenance mode and return to normal mode, use the no form of this command.
system mode maintenance dont-generate-profile
no system mode maintenance dont-generate-profile
Syntax Description
Defaults
Command Modes
vdc-admin
network-operator
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to prevent the dynamic searching of enabled protocols and put the switch in maintenance mode by executing commands configured in a custom maintenance mode profile:
Related Commands
system mode maintenance non-interactive
To put the switch in maintenance mode without presenting any switch prompts, use the system mode maintenance non-interactive command. To return to normal mode from maintenance mode without presenting any switch prompts, use the no form of this command.
system mode maintenance non-interactive
no system mode maintenance non-interactive
Syntax Description
Defaults
Command Modes
network-admin
vdc-admin
network-operator
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to put the switch in maintenance mode without presenting any switch prompts:
This example shows how to put the switch in normal mode from maintenance mode without presenting any switch prompts:
Related Commands
system mode maintenance on-reload reset-reason
To boot the switch into maintenance-mode automatically in the event of a specified system crash, use the system mode maintenance on-reload reset-reason command. To prevent the switch from being brought up in maintenance mode in the event of a system crash, use the no form of this command.
system mode maintenance on-reload reset-reason reason
no system mode maintenance on-reload reset-reason reason
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
We recommend configuring the reset reason and saving it to the startup configuration. This enables the switch to go into the maintenance mode after a switch reloads due to any reason.
Examples
This example shows how to automatically boot the switch into maintenance mode if a fatal error or a hardware error occurs
Related Commands
system mode maintenance shutdown
To shut down all protocols and interfaces except the management interface (by using the shutdown command and not the default isolate command), use the system mode maintenance shutdown command.
system mode maintenance shutdown
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to shut down all protocol and interfaces on the switch except the management interface:
Related Commands
system mode maintenance snapshot-delay
To change the snapshot-delay timer value, use the system mode maintenance snapshot-delay command. To remove the configured timer value, use the no form of this command.
system mode maintenance snapshot-delay delay-in-seconds
no system mode maintenance snapshot-delay delay-in-seconds
Syntax Description
Snapshot-delay timer value, in seconds. The range is from 0 to 65535. |
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
The [no] system mode maintenance command has been enhanced from the previous release to execute a normal mode profile and activate a timer ensuring that sufficient time is provided for the switch to complete any hardware programming that may be going on before the after_maintenance snapshot is taken. Once the timer expires, the after_maintenance snapshot is taken in the background and a new warning syslog message, MODE_SNAPSHOT_DONE, is sent after the snapshot is complete.
Use the system mode maintenance snapshot-delay delay-in-seconds command to change the snapshot-delay timer value.
Examples
This example shows how to change the snapshot-delay timer value:
This example shows how to remove the configured snapshot-delay timer value:
Related Commands
system mode maintenance timeout
To configure the maintenance window timer to keep the switch in maintenance mode for a specified number of minutes, use the system mode maintenance timeout command. To remove the configured timer, use the no form of this command.
system mode maintenance timeout value
no system mode maintenance timeout value
Syntax Description
Specifies the number of minutes for which the switch will be in maintenance mode. Range is from 5 to 65535 minutes. |
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
We recommend setting the timeout value to at least 30 minutes. Once the configured time elapses, the switch returns to normal mode automatically.
Examples
This example shows how to keep the switch in maintenance mode for a specific number of minutes:
Related Commands
system no hap-reset
To disable the Supervisor Reset high availability (HA) policy, use the system no hap-reset command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to disable the Supervisor Reset HA policy:
Related Commands
|
|
---|---|
system no heartbeat
To disable the heartbeat checking (default) and revert to the factory default, use the system no heartbeat command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to disable the heartbeat checks (default) and revert to the factory default:
Related Commands
|
|
---|---|
Enables the heartbeat checks (default) and reverts to the factory default. |
system no standby manual-boot
To disable the system standby manual boot option, use the system no standby manual-boot command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to disable the system standby manual boot option:
Related Commands
|
|
---|---|
Displays the status of the system standby manual boot option. |
system no watchdog
To disable the watchdog feature, use the system no watchdog command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to disable the watchdog feature:
Related Commands
|
|
---|---|
Prevents the system from entering the Linux KGDB debugger on a watchdog failure. |
system no watchdog kgdb
To prevent the system from entering the Linux KGDB debugger on a watchdog failure, use the system no watchdog kgdb command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to prevent the system from entering the Linux KGDB debugger on a watchdog failure:
Related Commands
|
|
---|---|
system pss shrink
To shrink Persistent Storage Service (PSS) files on the system, use the system pss shrink command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to shrink PSS files on the system:
switch(
config)
Related Commands
|
|
---|---|
system scale-limit monitor
To enable scale limit monitoring on a switch, use the system scale-limit monitor command. To disable scale limit monitoring, use the no form of this command
system scale-limit monitor time-in-minutes
Syntax Description
Specifies the interval (in minutes) at which the scale limits are monitored. The range is from 5 minutes to 43200 minutes (30 days). |
Defaults
Command Modes
network-admin
vdc-admin
network-operator
vdc-operator
Command History
|
|
Usage Guidelines
You can use the system scale-limit monitor command to monitor the following 16 scale parameters:
- FEX server interfaces
- F1 HW entries
- Virtual Port Channels (vPCs)
- Fabric Extenders (FEXs)
- Edge ports
- Port channels
- Intermediate System-to-Intermediate System (IS-IS) adjacencies
- Bidirectional Forwarding Detection (BFD) sessions
- L2-mroutes
- M2 HW entries
- Core ports
- M1 HW entries
- FabricPath Switch IDs
- VLANs
- FabricPath Topologies
- F2/F2e HW entries
Examples
This example shows how to enable scale limit monitoring on a switch:
Related Commands
|
|
---|---|
system standby manual-boot
To display the standby manual-boot status, use the system standby manual-boot command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to display the standby manual-boot status:
Related Commands
|
|
---|---|
system startup-config init
To initialize the startup configuration, use the system startup-config init command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to initialize the startup configuration:
Related Commands
|
|
---|---|
system startup-config unlock
To release a system startup-configuration lock, use the system startup-config unlock command.
system startup-config unlock luck-id
Syntax Description
Startup-configuration lock ID. The range is from 0 to 65536. |
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to release a system startup-configuration lock:
switch(
config)#
system startup-config unlock
switch(
config)#
Related Commands
|
|
---|---|
system test-preupgrade running-ver
To test the running software version before an upgrade, use the system test-preupgrade running-ver command.
system test-preupgrade running-ver version-number target-ver target-number swid id impact impact-number
Syntax Description
Specifies the software ID of the image running on a module: system or kickstart. |
|
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to test the running software version before an upgrade:
Related Commands
|
|
---|---|
system switchover
To switch over to the standby supervisor, use the system switchover command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
---|---|
Usage Guidelines
Examples
This example shows how to switch over to the standby supervisor:
Related Commands
|
|
---|---|
system trace
To configure a system trace level, use the system trace command. To remove the system trace level configuration, use the no form of this command.
Syntax Description
Defaults
Command Modes
Global configuration mode (config)
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure a system trace level:
switch(
config)#
system trace
switch(
config)#
This example shows how to remove the system trace level configuration:
switch(
config)#
system no trace
switch(
config)#
Related Commands
|
|
---|---|
system watchdog
To enable watchdog checks, use the system watchdog command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to enable watchdog checks:
Related Commands
|
|
---|---|
Prevents the system from entering the Linux KGDB debugger on a watchdog failure. |
system watchdog kgdb
To configure the system to enter the Linux KGDB debugger on a watchdog failure, use the system watchdog kgdb command.
Syntax Description
Defaults
Command Modes
network-admin
network-operator
vdc-admin
vdc-operator
Command History
|
|
Usage Guidelines
Examples
This example shows how to configure the system to enter the Linux KGDB debugger on a watchdog failure:
switch(
config)#
system watchdog kgdb
switch(
config)#
Related Commands
|
|
---|---|