The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS system management commands that begin with the letter R.
To configure the source rate limit for Ethernet Switched Port Analyzer (SPAN) packets in the specified SPAN session, use the rate-limit command. To remove the rate limit configuration, use the no form of this command.
Monitor configuration (config-monitor)
|
|
Make sure that you are in the correct virtual device context (VDC). To change the VDC, use the switchto vdc command.
MTU truncation and the SPAN rate limit cannot be enabled for the same SPAN session. If you configure both for one session, only the rate limit is allowed on F1 Series modules, and MTU truncation is disabled until you disable the rate limit configuration.
Note SPAN rate limit is supported only on F1 Series modules and F2 Series modules.
This example shows how to configure the rate limit for SPAN packets in the specified SPAN session:
This example shows how to remove the rate limit configuration for SPAN packets in the specified SPAN session:
|
|
---|---|
Places you in the monitor configuration mode for configuring a SPAN session. |
|
To specify a flow record to be used by a NetFlow monitor, use the record command. To remove the record, use the no form of this command.
NetFlow monitor configuration (config-flow-record)
|
|
Make sure that you are in the correct virtual device context (VDC). To change the VDC, use the switchto vdc command.
This example shows how to specify a NetFlow record to use for a NetFlow monitor:
This example shows how to remove a record from a NetFlow monitor:
switch(
config-flow-record)#
no record netflow ipv4 original-input
switch(
config-flow-record)#
|
|
---|---|
To select a traditional Layer 2 record for the NetFlow monitor, use the record netflow command. To remove the record selection, use the no form of this command.
record netflow layer2-switched input
no record netflow layer2-switched input
Specifies the traditional Layer 2 NetFlow collection scheme. |
|
|
|
This example shows how to select a traditional Layer 2 record for the NetFlow monitor:
This example shows how to remove the traditional Layer 2 NetFlow record selection:
|
|
---|---|
To select an IPv4 record for the NetFlow monitor, use the record netflow ipv4 command. To remove the record selection, use the no form of this command.
record netflow ipv4 { original-input | original-output | protocol-port }
no record netflow ipv4 { original-input | original-output | protocol-port }
NetFlow monitor configuration (config-flow-monitor)
|
|
This example shows how to select a NetFlow IPv4 record for the NetFlow monitor:
This example shows how to remove the NetFlow IPv4 record selection:
|
|
---|---|
To select a NetFlow IPv6 record for the NetFlow monitor, use the record netflow ipv6 command. To remove the record selection, use the no form of this command.
record netflow ipv6 { original-input | original-output | protocol-port }
no record netflow ipv6 { original-input | original-output | protocol-port }
NetFlow monitor configuration (config-flow-monitor)
|
|
This example shows how to select a NetFlow IPv6 record for the NetFlow monitor:
This example shows how to remove the NetFlow IPv6 record selection:
switch(config-flow-monitor)#
no record netflow ipv6 original-input
switch(config-flow-monitor)#
|
|
---|---|
To select an input IPv4 record, use the record netflow-original command. To remove the record selection, use the no form of this command.
NetFlow monitor configuration (config-flow-monitor)
|
|
This example shows how to select an IPv4 input record:
This example shows how to remove the record selection:
switch(
config-flow-monitor)#
no record netflow-original
switch(
config-flow-monitor)#
|
|
---|---|
To specify a remote Ethernet Switched Port Analyzer (RSPAN) VLAN as a SPAN session source, use the remote-span command. To remove an RSPAN VLAN as a SPAN session source, use the no form of this command.
Vlan configuration (config-vlan)
|
|
This example shows how to configure an RSPAN VLAN as a SPAN session source:
switch(
config)#
vlan 100
This example shows how to remove an RSPAN VLAN configuration:
|
|
---|---|
To configure a 32-bit remote monitoring RMON alarm, use the rmon alarm command. To delete RMON alarms, use the no form of this command.
rmon alarm alarm number mib-object sample-interval {absolute | delta} rising-threshold value [ rising-event ] falling-threshold value [falling-event] [owner alarm-owner]
|
|
This example shows how to configure the 32-bit alarm number 20 for OID (1.3.6.1.2.1.2.2.1.14). The sample interval is 30 seconds and delta samples are tested. The rising threshold is 15 errors per sample window; reaching this level triggers event 1. The falling threshold is 0 errors in the sample window; reaching this level triggers event 0 (no action).
|
|
---|---|
To configure an RMON event, use the rmon event command. To delete an RMON event, use the no form of this command.
rmon event event-number [description text] [log] [trap community-string] [owner owner-name]
|
|
You can trigger an events created by this command with an alarm that you configured by using the rmon alarm or rmon hcalarm commands.
Events can be used by both rmon alarm (32-bit) and hcalarm (64-bit) commands.
Note You may chose to load the default RMON events template configuration or you can delete these entries and create new RMON events. Until you create RMON alarm configurations, however, no alarms will be triggered by these configurations.
This example shows how to configure RMON event 2 to log the onboard RMON log and send an SNMP trap to public community trap destinations:
|
|
---|---|
To configure a 64-bit RMON high-capacity alarm (hcalarm), use the rmon hcalarm command. To delete an rmon hcalarm, use the no form of this command.
rmon hcalarm alarm-number mib-object sample-interval {absolute | delta} {rising-threshold- high value rising-threshold-low value [rising-event] [falling-threshold-high value falling-threshold-low value [falling-event]]} [owner alarm-owner]
|
|
Event number 0 is a predefined null (or no operation) event. When no event is specified by the user in an alarm, this event is automatically used by the system. The event causes no action to be taken when triggered; however, the alarm is still reset. The event cannot be redefined by the user. It is a predefined event.
This example shows how to configure a RMON high-capacity alarm:
|
|
---|---|
To enable Cisco Fabric Services (CFS) to distribute role configurations, use the role distribute command.
|
|
This example shows how to enable CFS to distribute role configurations and then display the status:
|
|
---|---|
Displays the status of the specified application, including whether CFS distribution is enabled for the application. |
To implement a rollback for the configured checkpoint file, use the rollback running-config checkpoint command.
rollback running-config {checkpoint cp-name | file cp-file} [atomic | best-effort | stop-at-first-failure]
|
|
The rollback running-config checkpoint command creates a rollback to the specified checkpoint name or file. The default rollback type is atomic.
Note The running configuration may be disrupted before the rollback operation finally fails if you mistakenly roll back with the file option using a file from a different device but with the same VDC ID as the local VDC.
This example shows how to implement a rollback for the configured checkpoint file:
|
|
---|---|
Displays the differences between the source and the destination file. |