Feedback
Table Of Contents
F Commands
This chapter describes the Cisco NX-OS system management commands that begin with the letter F.
feature lldp
To enable the Link Layer Discovery Protocol (LLDP) feature globally, use the feature lldp command. To disable the LLDP feature, use the no form of this command.
feature lldp
no feature lldp
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration (config)
Supported User Rolesnetwork-admin
network-operator
vdc-admin
vdc-operatorCommand History
Usage Guidelines
In order for LLDP to discover servers, the servers must be running openLLDP software.
LLDP must be enabled on the device before you can enable or disable it on any interfaces.
LLDP is supported only on physical interfaces. LLDP can discover up to one device per port. LLDP can discover Linux servers, if they are not using a converged network adapter (CNA); however, LLDP cannot discover other types of servers.
Make sure that you are in the correct virtual device context (VDC). To switch VDCs, use the switchto vdc command.
This command does not require a license.
Examples
This example shows how to enable the LLDP feature globally:
switch(config)#feature lldpswitch(config)This example shows how to disable the LLDP feature:
switch(config)#no feature lldpswitch(config)#2010 Jan 11 01:50:33 switch %FEATURE-MGR-2-FM_AUTOCKPT_IN_PROGRESS: AutoCheckpoint system-fm-lldp's creation in progress...2010 Jan 21 01:50:34 switch %FEATURE-MGR-2-FM_AUTOCKPT_SUCCEEDED: AutoCheckpointcreated successfullyswitch(config)#Related Commands
feature netflow
To globally enable the NetFlow feature, use the feature netflow command. To disable NetfFow, use the no form of this command.
feature netflow
no feature netflow
Syntax Description
This command does not have any arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enable NetFlow on a Cisco NX-OS device:
switch(config)# configure terminalswitch(config)# feature netflowswitch(config)#This example shows how to disable NetFlow on a Cisco NX-OS device:
switch(config)# no feature netflowswitch(config)#Related Commands
flow record
Creates a flow record and enters flow record configuration mode.
show flow record
Displays information about NetFlow flow records.
feature ntp
To enable the Network Time Protocol (NTP) on a virtual device context (VDC), use the feature ntp command. To disable NTP on a VDC, use the no form of this command.
feature ntp
no feature ntp
Syntax Description
This command does not have any arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Make sure that you are in the correct virtual device context (VDC). To change the VDC, use the switchto vdc command.
This command does not require a license.
Examples
This example shows how to enable NTP on a VDC:
switch# configure terminalswitch(config)# feature ntpThis example shows how to disable NTP on a VDC:
switch# configure terminalswitch(config)# no feature ntpRelated Commands
ntp master
Configures the device to act as an authoritative NTP server.
ntp enable
Enables the NTP feature on a VDC.
feature ptp
To enable the Precision Time Protocol (PTP) feature on the current virtual device context (VDC), use the feature ptp command. To disable the PTP feature, use the no form of this command.
feature ptp
no feature ptp
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enable the PTP feature on the current VDC:
switch# configure terminalswitch(config)# feature ptpswitch(config)#This example shows how to disable the PTP feature on the current VDC:
switch(config)# no feature ptp 2011 Jul 5 06:11:07 switch %FEATURE-MGR-2-FM_AUTOCKPT_IN_PROGRESS: AutoCheckpoint system-fm-ptp's creation in progress...2011 Jul 5 06:11:07 switch %FEATURE-MGR-2-FM_AUTOCKPT_SUCCEEDED: AutoCheckpointcreated successfullyswitch(config)#Related Commands
feature scheduler
To enable the scheduling of maintenance jobs, use the feature scheduler command. To disable the scheduler, use the no form of this command.
feature scheduler
no feature scheduler
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You must enable the scheduler feature before you can configure a maintenance job.
Maintenance jobs can be scheduled for one-time-only or at periodic intervals. Maintenance jobs include quality of service policy changes, data and configuration backup, and so on.
This command does not require a license.
Examples
This example shows how to enable the scheduler:
switch# config tswitch(config)# feature schedulerswitch(config)#This example shows how to disable the scheduler:
switch# config tswitch(config)# no feature schedulerswitch(config)#Related Commands
scheduler
Creates and schedules maintenance jobs.
show scheduler
Displays scheduler information.
filter access-group
To apply an access group to an Encapsulated Remote Switched Port Analyzer (ERSPAN) source session, use the filter access-group command. To remove an access group, use the no form of this command.
filter access-group acl_filter
no filter access-group acl_filter
Syntax Description
Defaults
None
Command Modes
config-monitor-erspan-src
Supported User Rolesnetwork-admin
VDC-adminCommand History
Usage Guidelines
Only the permit to deny actions are allowed for Encapsulated Remote Switched Port Analyzer (ERSPAN) access control list (ACL) filters.
For information about ACL-related commands, see the Cisco Nexus 7000 Series NX-OS Security Command Reference.
This command does not require a license.
Examples
This example shows how to apply an access group to an ERSPAN session:
switch# configure terminalswitch(config)# monitor session 3 type erspan-sourceswitch(config-monitor-erspan-src)# filter vlan 3-5, 7switch(config-monitor-erspan-src)# filter access-group ACL1This example shows how to disassociate an access group to an ERSPAN session:
switch# configure terminalswitch(config)# monitor session 3 type erspan-sourceswitch(config-monitor-erspan-src)# filter vlan 3-5, 7switch(config-monitor-erspan-src)# no filter access-group ACL1Related Commands
filter vlan
To apply a VLAN access map to one or more VLANs, use the filter vlan command. To remove a VLAN access map, use the no form of this command.
filter vlan vlan_mrange [include-untagged]
no filter vlan vlan_mrange [include-untagged]
Syntax Description
Defaults
None
Command Modes
Config-monitor configuration (config-monitor)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to apply a VLAN access map to one or more VLANs:
switch(config)# monitor session 1switch(config-monitor)# filter vlan 5-10 include-untaggedswitch(config-monitor)#This example shows how to remove the VLAN access map:
switch(config-monitor)# no filter vlan 5-10 include-untaggedswitch(config-monitor)#Related Commands
filter vlan include-untagged
Applies a VLAN access map to one or more VLANs and includes untagged frames on a port with Layer 3 subinterfaces.
filter vlan include-untagged
To apply a VLAN access map to one or more VLANs and include untagged frames on a port with Layer 3 subinterfaces, use the filter vlan include-untagged command. To remove a VLAN access map to one or more VLANs with untagged frames on a port with Layer 3 subinterfaces, use the no form of this command.
filter vlan include-untagged
no filter vlan include-untagged
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Config-monitor configuration (config-monitor)
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to apply a VLAN access map to one or more VLANs and include untagged frames on a port with Layer 3 subinterfaces:
switch(config)# monitor session 1switch(config-monitor)# filter vlan 1-20 include-untaggedswitch(config-monitor)#This example shows how to remove a VLAN access map to one or more VLANs with untagged frames on a port with Layer 3 subinterfaces:
switch(config-monitor)# no filter vlan 1-20 include-untaggedswitch(config-monitor)#Related Commands
flow exporter
To create a Flexible NetFlow flow exporter or to modify an existing Flexible NetFlow flow exporter, use the flow exporter command. To remove a Flexible NetFlow flow exporter, use the no form of this command.
flow exporter exporter-name
no flow exporter exporter-name
Syntax Description
Defaults
Flow exporters are not present in the configuration until you create them.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Flow exporters export the data in the flow monitor cache to a remote system, such as a server running NetFlow collector, for analysis and storage. Flow exporters are created as separate entities in the configuration. Flow exporters are assigned to flow monitors to provide data export capability for the flow monitors. You can create several flow exporters and assign them to one or more flow monitors to provide several export destinations. You can create one flow exporter and apply it to several flow monitors.
Once you enter the flow export configuration mode, the prompt changes to the following:
switch(config-flow-exporter)#Within the flow export configuration mode, the following keywords and arguments are available to configure the flow exporters:
•
description description—Provides a description for this flow exporter; you can use a maximum of 63 characters.
•
–
–
•
•
•
•
–
–
–
•
•
This command does not require a license.
Examples
This example shows how to create a flow exporter named FLOW-EXPORTER-1, enter flow exporter configuration mode, and configure the flow exporter:
switch(config)# flow exporter FLOW-EXPORTER-1switch(config-flow-exporter)# description located in Pahrump, NVswitch(config-flow-exporter)# destination A.B.C.Dswitch(config-flow-monitor)# dscp 32switch(config-flow-monitor)# source ethernet 3/2switch(config-flow-monitor)# transport udp 59switch(config-flow-monitor)# version 5Related Commands
clear flow exporter
Clears the flow monitor.
show flow exporter
Displays flow monitor status and statistics.
flow monitor
To create a Flexible NetFlow flow monitor or to modify an existing Flexible NetFlow flow monitor and enter flow monitor configuration mode, use the flow monitor command. To remove a Flexible NetFlow flow monitor, use the no form of this command.
flow monitor monitor-name
no flow monitor monitor-name
Syntax Description
Defaults
Flow monitors are not present in the configuration until you create them.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Flow monitors are the Flexible NetFlow component that is applied to interfaces to perform network traffic monitoring. Flow monitors consist of a record that you add to the flow monitor after you create the flow monitor and a cache that is automatically created at the time that the flow monitor is applied to the first interface. Flow data is collected from the network traffic during the monitoring process based on the key and nonkey fields in record that is configured for the flow monitor and stored in the flow monitor cache.
Once you enter the flow monitor configuration mode, the prompt changes to the following:
switch(config-flow-monitor)#Within the flow monitor configuration mode, the following keywords and arguments are available to configure the flow monitor:
•
•
•
•
•
–
–
original-input—Specifies the traditional IPv4 input NetFlow.
original-output—Specifies the traditional IPv4 output NetFlow.
protocol-port—Specifies the protocol and ports aggregation scheme.
–
The netflow-original and original-input keywords are the same and are equivalent to the following commands:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The original-output keywords are the same as the original-input keywords except for the following:
•
•
This command does not require a license.
Examples
This example shows how to create and configure a flow monitor named FLOW-MONITOR-1:
switch(config)# flow monitor FLOW-MONITOR-1switch(config-flow-monitor)# description monitor location las vegas, NVswitch(config-flow-monitor)# exporter exporter-name1switch(config-flow-monitor)# record test-recordswitch(config-flow-monitor)# netflow ipv4 original-inputRelated Commands
clear flow monitor
Clears the flow monitor.
show flow sw-monitor
Displays flow monitor status and statistics.
flow record
To create a Flexible NetFlow flow record or to modify an existing Flexible NetFlow flow record and enter flow record configuration mode, use the flow record command. To remove a Flexible NetFlow flow record, use the no form of this command.
flow record record-name
no flow record record-name
Syntax Description
Defaults
Flow records are not present in the configuration until you create them.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Flexible NetFlow uses key and nonkey fields just as original NetFlow does to create and populate flows in a cache. In Flexible NetFlow, a combination of key and nonkey fields is called a record. Original NetFlow and Flexible NetFlow both use the values in key fields in IP datagrams, such as the IP source or destination address and the source or destination transport protocol port, as the criteria for determining when a new flow must be created in the cache while network traffic is being monitored. A flow is defined as a stream of packets between a given source and a given destination. New flows are created whenever NetFlow analyzes a packet that has a unique value in one of the key fields.
Once you enter the flow record configuration mode, the prompt changes to the following:
switch(config-flow-record)#Within the flow record configuration mode, the following keywords and arguments are available to configure the flow record:
•
•
•
•
•
Cisco NX-OS enables the following match fields by default when you create a flow record:
•
•
•
This command does not require a license.
Examples
This example shows how to create a flow record and enter flow record configuration mode:
switch(config)# flow record FLOW-RECORD-1switch(config-flow-record)#Related Commands
clear flow monitor
Clears the flow monitor.
flow monitor
Creates a flow monitor.
show flow sw-monitor
Displays flow monitor status and statistics.
flow timeout
To create a Flexible NetFlow flow timeout or to modify an existing Flexible NetFlow flow timeout, use the flow timeout command. To remove a Flexible NetFlow flow timeout, use the no form of this command.
flow timeout {active seconds | aggressive threshold percentage | fast seconds threshold packets | inactive seconds | session | seconds}
no flow timeout {active seconds | aggressive threshold percentage | fast seconds threshold packets | inactive seconds | session | seconds}
Syntax Description
Defaults
The default settings are as follows:
•
•
•
•
•
•
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
6.1(2)
Added the seconds argument for the syntax description and also the note.
4.0(1)
This command was introduced.
Usage Guidelines
The active timeout is the amount of time to wait before sending flow information about an active session. The flow is not removed from the cache after this timeout; however, the packet count, byte count, and timestamps are reset.
The aggressive timeout only affects hardware caches and is used when flows are being received faster than expected. If flows are being received faster than the threshold, they are aged out of the cache.
The fast timeout specifies when an inactive flow should be aged out.
The inactive timeout is used for Transmission Control Protocol (TCP) sessions that receive no more data from the sender (FIN) followed by an acknowledgment field is significant (ACK) or a reset (RST) packet being received. The inactive timeout indicates the session is over and the flow can be aged out.
Note
This command does not require a license.
Examples
This example shows how to specify the active or long timeout value in seconds for the F1 and M1 Series modules:
switch(config)# flow timeout active 45switch(config)#This example shows how to specify the percentage of the NetFlow table content:
switch(config)# flow timeout aggressive threshold 45switch(config)#This example shows how to specify the fast aging timeout in seconds:
switch(config)# flow timeout fast 30 threshold 20switch(config)#This example shows how to specify the inactive or normal timeout in seconds:
switch(config)# flow timeout inactive 45switch(config)#This example shows how to specify the flush cache timeout in seconds for F2 Series module:
switch(config)# flow timeout 45switch(config)#Related Commands
