To create a
RADIUS server group and enter RADIUS server group configuration mode, use the
aaa group server
radius command in global configuration mode. To delete a RADIUS
server group, use the
no form of
this command.
aaa group server radiusgroup-name
no aaa
group server radiusgroup-name
Syntax Description
group-name
RADIUS
server group name.
The name is alphanumeric and case-sensitive. The maximum length is
64 characters.
Command Default
A RADIUS server
group is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to create a RADIUS server group and enter RADIUS server
configuration mode:
Device# configure terminal
Device(config)# aaa group server radius RadServer
Device(config-radius)#
The following
example shows how to delete a RADIUS server group:
Device# configure terminal
Device(config)# no aaa group server radius RadServer
address-family
To configure
multicast VPN (MVPN) for IPv4 or IPv6, use the
address-family command in router configuration mode or neighbor configuration
mode. To disable MVPN configuration, use the
no form of this command.
address-family
{ ipv4
| ipv6 }
mvpn
noaddress-family
{ ipv4
| ipv6 }
mvpn
Syntax Description
ipv4
Configures the IPv4 address-family.
ipv6
Configures the IPv6 address-family.
mvpn
Configures Multicast VPN .
Command Default
No MVPN
provisioning support is enabled.
Command Modes
Router configuration (config-router)
Neighbor configuration (config-router-neighbor)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
This command
places the router in address family configuration mode (prompt:
config-router-af), from which you can configure routing sessions that support
Multicast VPN provisioning for IPv4 or IPv6.
Examples
The following
example shows how to configure multicast VPN for IPv4:
To create a
summary address in a Border Gateway Protocol (BGP) routing table, use the
aggregate-address command. To remove the summary
address, use the
no form of
this command.
no
aggregate-addressaddress/length [ advertise-map
map-name][as-set][ attribute-map
map-name][summary-only][ suppress-map
map-name]
Syntax Description
address/length
Specifies
aggregate IP address and mask length. Valid values for length are as follows:
IPv4 addresses from1 to 32
IPv6 addresses from 1 to
128
advertise-map
map-name
(Optional)
Specifies the name of the route map used to select attribute information from
specific routes.
as-set
(Optional)
Generates the autonomous system set path information and community information
from the contributing paths.
attribute-map
map-name
(Optional)
Specifies the name of the route map used to set the attribute information for
specific routes. The map-name is an alphanumeric string up to 63 characters.
summary-only
(Optional)
Filters all more-specific routes from updates.
suppress-map
map-name
(Optional) Specifies the name of the route map used to
conditionally filter more specific routes. The map-name is an alphanumeric
string up to 63 characters.
Command Default
The atomic
aggregate attribute is set automatically when an aggregate route is created
with this command unless the
as-set
keyword is specified.
Command Modes
Address-family configuration mode
Neighbor address-family configuration mode
Router BGP configuration mode
Command History
Release
Modification
- -
This
command was introduced in an earlier Cisco NX-OS release.
Usage Guidelines
You can implement
aggregate routing in BGP and mBGP either by redistributing an aggregate route
into BGP or mBGP, or by using the conditional aggregate routing feature.
Using the
aggregate-address command with no keywords will
create an aggregate entry in the BGP or mBGP routing table if any more-specific
BGP or mBGP routes are available that fall within the specified range. (A
longer prefix which matches the aggregate must exist in the RIB.) The aggregate
route will be advertised as coming from your autonomous system and will have
the atomic aggregate attribute set to show that information might be missing.
(By default, the atomic aggregate attribute is set unless you specify the
as-set
keyword.)
Using the
as-set
keyword creates an aggregate entry using the same rules that the command
follows without this keyword, but the path advertised for this route will be an
AS_SET consisting of all elements contained in all paths that are being
summarized. Do not use this form of the
aggregate-address command when aggregating many
paths, because this route must be continually withdrawn and updated as
autonomous system path reachability information for the summarized routes
changes.
Using thesummary-onlykeyword not only creates the aggregate route (for example,
192.*.*.*) but also suppresses advertisements of more-specific routes to all
neighbors. If you want to suppress only advertisements to certain neighbors,
you may use the neighbor distribute-list
command, with caution. If a more-specific route leaks
out, all BGP or mBGP routers will prefer that route over the less-specific
aggregate you are generating (using longest-match routing).
Using the
suppress-map keyword creates the aggregate route
but suppresses advertisement of specified routes. You can use the match clauses
of route maps to selectively suppress some more-specific routes of the
aggregate and leave others unsuppressed. IP access lists and autonomous system
path access lists match clauses are supported.
Using the
advertise-map keyword selects specific routes that
will be used to build different components of the aggregate route, such as
AS_SET or community. This form of the aggregate-address
command is useful when the components of an aggregate are
in separate autonomous systems and you want to create an aggregate with AS_SET,
and advertise it back to some of the same autonomous systems. You must remember
to omit the specific autonomous system numbers from the AS_SET to prevent the
aggregate from being dropped by the BGP loop detection mechanism at the
receiving router. IP access lists and autonomous system path access lists match
clauses are supported.
Using the
attribute-map keyword allows attributes of the
aggregate route to be changed. This form of the
aggregate-address
command is useful when one of the routes forming the
AS_SET is configured with an attribute such as the community no-export
attribute, which would prevent the aggregate route from being exported. An
attribute map route map can be created to change the aggregate attributes.
This command
requires the Enterprise Services license.
Examples
AS-Set Example
In This example,
an aggregate BGP address is created in router configuration mode. The path
advertised for this route will be an AS_SET consisting of all elements
contained in all paths that are being summarized.
In This example,
an aggregate BGP address is created in address family configuration mode and
applied to the multicast database (SAFI) under the IP Version 4 address family.
Because the
summary-only keyword is configured, more-specific
routes are filtered from updates.
In This example,
a route map called MAP-ONE is created to match on an as-path access list. The
path advertised for this route will be an AS_SET consisting of elements
contained in paths that are matched in the route map.
Device(config)# ip as-path access-list 1 deny ^1234_
Device(config)# ip as-path access-list 1 permit .*
Device(config)# !
Device(config)# route-map MAP-ONE
Device(config-route-map)# match ip as-path 1
Device(config-route-map)# exit
Device(config)# router bgp 64496
Device(config-router)# address-family ipv4
Device(config-router-af)# aggregate-address 10.0.0.0 255.0.0.0 as-set advertise-map MAP-ONE
Device(config-router-af)# end
apply
profile
To apply a
configuration profile to configure hosts, use the
apply
profile command in global configuration mode. To remove the
configuration profile use the
no form of
this command.
Name of
the profile that is created using the
configure
profile command.
include-instanceinclude-instance
(Optional)
Specifies the include instance name.
param-instanceinstance-name
(Optional)
Specifies the parameter instance name.
Command Default
The port profile
is not applied.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Configuration
profiles provide an infrastructure to configure hosts based on a set of
user-defined templates. You can define different templates for different types
of hosts and enable them appropriately based on an event, such as host
discovery. You can apply different profiles to different hosts and apply
different values for the configuration for different hosts.
Use the
apply
profile command to apply a configuration profile on a host.
Use the
configure
profile command to create a configuration profile and add a
parameter list and a parameter-list instance. You can either create one
parameterized profile for each host or create one profile with parameterized
argument and apply it with host-specific arguments. The parameter-list instance
provides the actual values that are added in the configuration profile before
the profile is applied. The parameter name in the instance must match the
parameter name in the profile.
Examples
The following
example shows how to create a configuration profile and apply it to a host
instance, named HOST-1, to expand the profile and configure a new host:
Device(config)# configure profile sample
Device(conf-profile)# vlan $vlanId
Device(conf-profile-vlan)# vn-segment $segmentId
Device(conf-profile-vlan)# interface vlan $vlanId
Device(conf-profile-if-verify)# ip address $ipv4addr/$netmask1
Device(conf-profile-if-verify)# ipv6 address $ipv6addr/$netmask2
Device(conf-profile-if-verify)# ip access-group $aclnum out
Device(conf-profile-if-verify)# configure terminal
Device(config)# apply profile sample param-instance HOST-1
Device(config)# end
To enable autodiscovery
using Label Distribution Protocol (LDP) in a Layer 2 virtual forwarding
interface (VFI), use the
autodiscovery bgp signaling
ldp command in L2 VFI configuration mode. To disable
autodiscovery, use the
no form of
this command.
autodiscovery bgp signaling ldp
no autodiscovery bgp signaling ldp
This command has no arguments or keywords.
Command Default
Layer 2 VFI
autodiscovery is disabled.
Command Modes
L2 VFI configuration (config-vfi)
Command History
Release
Modification
- -
This
command was introduced in an earlier Cisco NX-OS release.
Examples
The following
example shows how to enable Layer 2 VFI as having BGP autodiscovered pseudowire
members and specify that LDP signaling should be used for autodiscovery:
To reboot a device
and apply the changes after you configure the device or install a new image,
use the
bootpoap command in global configuration mode. To
avoid rebooting the device, use the
no form of
this command.
boot poap
[ enable ]
no boot poap
Syntax Description
enable
(Optional) Enables the boot POAP (Power On Auto Provisioning)
functionality.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Rebooting the
device is required in the following situations:
If the configuration is
supported only on the new image.
If you configure the device
after rebooting it.
You can avoid
rebooting the device in the following situations:
If there is no change in
the image or in the configuration of device.
If you want to apply only
specific configuration updates on the device.
Examples
This example
shows how to reboot a device after configuring the device or installing a new
image:
Configures a file that contains CLI commands and applies on the next reboot of the device.
bridge-domain
To enter bridge-domain
configuration mode and configure a bridge domain, use the
bridge-domain
command. To remove the bridge-domain configurations, use the
no form of
this command.
bridge-domain
domain-id
no bridge-domain
domain-id
Syntax Description
domain-id
Specifies
the Bridge-domain ID. The range is defined by the system-bridge-domain
configuration.
Command Default
None
Command Modes
Global configuration mode
Command History
Release
Modification
- -
This
command was introduced in an earlier Cisco NX-OS release.
Usage Guidelines
Removing the
bridge-domain configuration does not remove the underlying VLAN. If a VLAN is
associated with a bridge domain, you cannot remove the VLAN without first
removing the bridge domain. To remove the underlying VLAN, use the no vlan
command after you remove the bridge domain. This command requires the MPLS
Services license.
Examples
This example shows
how to enter bridge-domain configuration mode and configure a bridge domain:
To configure the
rollback checkpoint, use the
checkpoint
command. To delete the checkpoint, use the
no form of
this command.
checkpoint {
name |
descriptiondescription |
filename}
no checkpoint
Syntax Description
name
Specifies the checkpoint name that is used in the
checkpoint database. The name can contain any alphanumeric string up to 80
characters, without any spaces.
descriptiondescription
Specifies the checkpoint description. The description can
contain up to 80 alphanumeric characters, including space.
filename
Specifies the filename that is used to
save the checkpoint.
Command Modes
Any command mode
Supported User
Roles
network-admin
network-operator
vdc-admin
vdc-operator
Command History
Release
Modification
--
This
command was introduced in an earlier Cisco NX-OS release.
Usage Guidelines
If you use the
checkpoint
command without a name, Cisco NX-OS software creates the file with the name
auto-x, where x is a decimal number that increments each time you create an
unnamed checkpoint file.
This command does
not require a license.
Examples
This example
shows how to configure the rollback checkpoint:
Device# checkpoint stable
This example
shows how to delete the checkpoint file:
Device# no checkpoint
clear evb
To clear
information associated with Edge Virtual Bridging (EVB), use the
clearevb command in global configuration mode.
To clear specific
user sessions and disconnect specific user from the Extensible Messaging and
Presence Protocol (XMPP) server, or to clear fabric access statistics, use the
clear fabric
access command in privileged EXEC mode.
clearfabricaccess{statistics |
userusername}
Syntax Description
statistics
Clears
user statistics such as ping parameters.
userusername
Clears
the specified user connection.
Command Default
No statistics are
cleared, and no session is cleared.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example show how to clear access statistics of the XMPP server:
Device# clear fabric access statistics
The following
example show how to clear specific user sessions and disconnect a user
specified as "spines":
Creates one or more groups of devices on the fabric access network using the XMPP server.
clear fabric
connectivity cable-plan
To clear the
current cable plan, use the
clearfabricconnectivitycable-plan command in privileged EXEC mode.
clearfabricconnectivitycable-plan
Syntax Description
This command has
no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)N3(1)
This
command was introduced.
Usage Guidelines
Before you import
a new cable plan, use this command to clear the existing one.
To clear a cable
plan that is already saved to the startup configuration, specify this command
and then configure the
copy running-config
startup-config command.
Examples
The following
example shows how to clear an existing cable plan:
To clear all
information about neighbors or subset of neighbors from the neighbor cache, use
the
clear fabric connectivity
neighbors command in privileged EXEC mode.
(Optional)
Clears cache of neighbors connected to an interface.
ethernet
(Optional)
Specifies the Ethernet interface.
slot-number/port-number
(Optional)
Slot number and port number.
mgmtinterface-number
(Optional)
Specifies the management interface and the interface number.
stale
(Optional)
Clears neighbor cache information for stale or purged neighbors.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use this command
to delete a single entry, all entries, or all error entries from the network
neighbor cache. You should manually clear an already secured port in the
neighbor cache if recabling is desired to immediately remove old or stale
entries. If you have a switch that was previously in the network but has since
gone stale (because it was removed or taken down), the only way to completely
remove it from the neighbor cache is by using this command. You have to enable
the cable management feature using the
feature cable-management
command to be able to use the
clear fabric connectivity
neighbors command.
Examples
The following
example shows how to clear neighbor cache from the Ethernet interface:
To clear the
external database statistics such as number of messages sent or received,
pending requests, access errors, and access timeouts, use the
clear fabric database
statistics command in privileged EXEC mode.
(Optional) Specifies a port or switch profile database.
server-proto
(Optional) Specifies a database protocol.
ldap
(Optional) Specifies the use of Lightweight Directory Access
Protocol (LDAP).
radius
(Optional) Specifies the use of RADIUS.
xmpp
(Optional) Specifies the use of Extensible Messaging and
Presence Protocol (XMPP).
hosthostname
(Optional) Specifies the hostname of the server.
ipip-address
(Optional) Specifies the IP address of the server.
portport-number
(Optional) Specifies the port number of the server.
db-jidjid
(Optional) Specifies the Jabber ID of the database.
Command Default
None
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
The
clear fabric database
statistics command is used to reset the database statistics
counters to zero. But this command does not delete existing statistics memory.
You can use the
show fabric database
statistics command to display per-server statistics including
number of messages sent or received, pending requests, access errors, and
timeouts.
Examples
The following
example shows how to clear the database statistics of Jabber ID db@domain.com
from the XMPP server:
To clear
information about FabricPath Operation, Administration, and Maintenance (OAM)
loopback, use the
clear
fabricpathOAM
loopback command in privileged EXEC mode.
Clears
information about FabricPath OAM loopback database.
sessionsession-handle
Clears
information about the FabricPath OAM loopback for a specific session.
statistics
Clears
information about FabricPath OAM loopback statistics.
summary
Clears
summary information about fabricpath OAM loopback statistics.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
To clear
statistics for all sessions, use the
clear fabricpath oam
loopback statistics command. To clear statistics for a particular
session, use the
clear fabricpath oam
loopback statistics session command. To clear summary statistics,
use the clear fabricpath oam
loopback statistics summary command.
Examples
The following
example shows how to clear the FabricPath OAM loopback statistics.
To clear
information about FabricPath Operation, Administration, and Maintenance (OAM)
mtrace, use the
clear
fabricpathoammtrace command in privileged EXEC mode.
To clear
information about FabricPath Operation, Administration, and Maintenance (OAM)
notification, use the
clear
fabricpathoamnotification command in privileged EXEC mode.
Shows information about for FabricPath OAM notification.
clear fabricpath
oam traceroute
To clear
information about FabricPath Operation, Administration, and Maintenance (OAM)
traceroute, use the
clear
fabricpathoamtraceroute command in privileged EXEC mode.
To configure a
profile, use the
configure profile
command in privileged EXEC mode. To remove a configured
profile, use the
no
form of this command.
configureprofileprofile-name
noconfigureprofileprofile-name
Syntax Description
profile-name
Name of
the profile to be configured.
Command Default
A profile is not
configured.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)N3(1)
This
command was introduced.
Usage Guidelines
You can specify a
maximum of 80 characters for the
profile-name
argument. Once you configure a profile name, this
profile is available in the list of profiles that can be used to configure
profile parameters. Use the
show
running-config command to display all configured profiles and
their parameters.
When you configure
a profile, the command mode changes to configuration profile mode. You can
configure profile parameters into a template in the configuration profile mode.
Use the
show config-profile
command to view the list of configured profiles.
Examples
The following
example shows how to configure a profile named pname:
The following
example shows how to configure profile parameters in the configuration profile
mode:
Device# configure profile sample
Device(config-profile)# vrf context sample-vrf
Device(config-profile-vrf)# end
copy
scheduled-config
To configure a
file containing CLI commands that you want to apply on the next reboot of the
device, use the
copyscheduled-config command in any command mode.
copyfilenamescheduled-config
Syntax Description
filename
Name of
the configuration file .
scheduled-config
Specifies the schedule of the configuration at the specified source to apply on
the next reboot of the device.
Command Default
None
Command Modes
Any command mode
Supported User
Roles
network-admin
vdc-admin
Command History
Release
Modification
--
This
command was introduced in an earlier Cisco NX-OS release.
Usage Guidelines
The
copy scheduled-config
command specifies the schedule of the configuration at
the specified source to apply on the next reboot of the device. This command
must be called explicitly within the POAP (Power On Auto Provisioning) script
to allow the POAP boot process to continue at the next reboot. When PowerOn
Auto Provisioning (POAP) is in progress, any important information or errors
are displayed over the serial console, aiding the administrator to troubleshoot
in case of problems.
This command does
not require a license.
Note
This command
is used in POAP script.
Examples
This example
shows how to specify that the abc file to be applied to the running
configuration when the device next reloads:
To configure the
Jabber ID of the database using Extensible Messaging and Presence Protocol
(XMPP), use the
db-jid
command in fabric database server configuration mode. To remove the Jabber ID
of the database, use the
no form of
this command.
db-jidjid
[ key-typekey-type-value ]
nodb-jidjid
[ key-typekey-type-value ]
Syntax Description
jid
Jabber
ID of the database.
key-typekey-type-value
(Optional)
Specifies the key type for the database queries. The valid value is 1.
Command Default
Jabber ID of the
database is not configured.
Command Modes
Fabric database server configuration (config-fabric-db-server)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You can specify
the Jabber ID to which the database manager sends search queries by using the
db-jid
command.
Examples
The following example shows how to configure the Jabber ID db@domain.com using XMPP:
Device# configure
Device(config)# fabric database type asset
Device(config-fabric-db)# server protocol xmpp host host1
Device(config-fabric-db-server)# db-jid db@domain.com key-type 1
To configure a
database table using Lightweight Directory Access Protocol (LDAP), use the
db-table
command in fabric database server configuration mode. To remove the database
table, use the
no form of
this command.
db-tabletable-name
[ key-typekey-type-value ]
nodb-tabletable-name
[ key-typekey-type-value ]
Syntax Description
table-name
Name of
the database table.
key-typekey-type-value
(Optional)
Specifies the key type for the database queries. The valid value is 1.
Command Default
The database table
is not configured.
Command Modes
Fabric database server configuration (config-fabric-db-server)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You can specify
the database table name to which the database manager sends search queries by
using the
db-table
command.
Examples
The following example shows how to configure a database table using LDAP:
Device# configure terminal
Device(config)# fabric database type network
Device(config-fabric-db)# server protocol ldap host host1
Device(config-fabric-db-server)# db-table ou=networks,dc=host,dc=com key-type 1
Configures the Jabber ID of the database using XMPP.
debug evb
To enable
debugging of events associated with an Edge Virtual Bridging (EVB) session, use
the
debugevb command in privileged EXEC mode. To disable
debugging, use the
no form of
this command.
debugevb
{ all
| cli
| errors
| events
| ha
| periodic
| pss
| trace
| verbose }
no debugevb
{ all
| cli
| errors
| events
| ha
| periodic
| pss
| trace
| verbose }
Syntax Description
all
Enables
debugging of all events in an EVB session.
cli
Enables
debugging of CLI command processing events only.
errors
Enables
debugging of only errors in an EVB session.
events
Enables
debugging of only general events in an EVB session.
ha
Enables
debugging of only High Availability (HA) related events in an EVB session.
periodic
Enables
debugging of only periodic events in an EVB session.
pss
Enables
debugging of only persistent storage service (PSS) related events in an EVB
session.
trace
Enables
debugging of detailed processing traces in an EVB session.
verbose
Enables
debugging of verbose mode in an EVB session.
Command Default
Debugging of
events in an EVB session is disabled.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
featureevb command to enable the EVB session. This, in
turn, enables the
debug evb
command on the device.
Examples
The following
example shows how to enable debugging of detail processing traces in an EVB
session:
The following is
sample output from the
show debug
evb command in an EVB session:
Device# show debug evb
Debugs Enabled: errors events
default-information originate
To configure a
Border Gateway Protocol (BGP) routing process to distribute a default route
(network 0.0.0.0), use the
default-information
originate command in address family configuration mode. To
disable the advertisement of a default route, use the
no form of
this command.
default-information originate
no default-information originate
Syntax Description
This command has no arguments or keywords.
Command Modes
Address family configuration (config-router-af)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
The
default-information originate command is used
to configure a BGP routing process to advertise a default route (network
0.0.0.0). A redistribution statement must also be configured to complete this
configuration or the default route will not be advertised.
Examples
The following
example configuration shows how to originate and redistribute a default route
(0.0.0.0/0) in BGP:
To create user-defined parameters for a parameter list, use the
define command in parameter list configuration mode. To remove user-defined parameters from a parameter list, use the
no form of
this command.
(Optional). Specifies the data type as an integer.
ipaddr
(Optional). Specifies the address as an IPv4 address.
ipv6addr
(Optional). Specifies the address as an IPv6 address.
mac-addr
(Optional). Specifies the address as a MAC address.
string
(Optional). Specifies the data type as a string.
value
(Optional). Parameter data type or address type value or parameter description.
Use the value argument with the parameter name to describe the parameter.
Use the value argument with a data type or address type to assign a value.
Command Default
User-defined parameters are not created.
Command Modes
Parameter list configuration (config-param-list)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
User-defined parameters that you create using the define command are associated with a parameter list.
A parameter list can be created using the param-list command.
You can use existing user-defined parameters and associate values (such as integer, IP address, and MAC address) to them.
Examples
The following example shows how to create a user-defined parameter param1 within the specified parameter list List1:
To configure a
description for a FabricPath Operation, Administration, and Maintenance (OAM)
profile, use the
description
command in FabricPath OAM profile configuration mode. To remove the FabricPath
OAM profile description, use the
no form of
this command.
descriptiondescription
nodescription
Syntax Description
description
The
description for the FabricPath OAM profile. The range is 1 to 64 characters.
Command Default
A description for
the FabricPath OAM profile is not configured.
To specify that a
FabricPath Operation, Administration, and Maintenance (OAM) flow profile must
include a dot1q tag, use the
dot1q command
in FabricPath oam flow profile configuration mode. To remove the dot1q tag, use
the
no form of
this command.
dot1qvlan-id
[ cosservice-value ]
nodot1q
Syntax Description
vlan-id
Specifies
the flow profile VLAN ID.
cosservice-value
(Optional)
Specifies the class of service (CoS). The range is from 0 to 7.
Command Default
Dot1q tag is not
included in the FabricPath OAM flow profile.
802.1Q tunneling
enables service providers to use a single VLAN to support customers who have
multiple VLANs, while preserving customer VLAN IDs and keeping traffic in
different customer VLANs segregated. Use this command to enter 802.1Q or
802.1ad configuration with CoS value.
Examples
The following
example shows how to configure a FabricPath OAM flow profile and specify a
802.1Q tag.
Configures the direction FabricPath OAM flow entropy.
encapsulation
dot1Q
To enable IEEE 802.1Q
encapsulation of traffic on a specified subinterface in a virtual LAN (VLAN),
use the
encapsulation
dot1q command. To disable encapsulation, use the
no form of
this command.
encapsulation dot1Q
vlan-id
no encapsulation dot1Q
vlan-id
Syntax Description
vlan-id
Specifies
the VLAN to set when the interface is in access mode. The range is from 1 to
4094 except for the VLANs reserved for internal switch use.
Command Default
No encapsulation
Command Modes
Subinterface configuration mode
Command History
Release
Modification
- -
This
command was introduced in an earlier Cisco NX-OS release.
Usage Guidelines
IEEE 802.1Q
encapsulation is configurable on Ethernet interfaces. IEEE 802.1Q is a standard
protocol for interconnecting multiple switches and routers and for defining
VLAN topologies.
Use the
encapsulation
dot1q command in subinterface range configuration mode to apply a
VLAN ID to the subinterface.
This command does
not require a license.
Examples
This example shows
how to enable dot1Q encapsulation on a subinterface for VLAN 30:
To enable error-disable
(errdisable) detection for an application, use the
errdisable detect
cause command in global configuration mode. To disable
error-disable detection, use the
no form of
this command.
errdisable detect cause
{ acl-exception
| all
| link-flap
| loopback
| miscabling }
no errdisable detect cause
{ acl-exception
| all
| link-flap
| loopback
| miscabling }
Syntax Description
acl-exception
Enables
error-disabled detection for access-list installation failures.
all
Enables
error-disabled detection for all causes.
link-flap
Enables
error-disabled detection on link-state flapping.
loopback
Enables
error-disabled detection on loopback detected by unidirectional link detection
(UDLD).
miscabling
Enables
error-disabled detection on a miscabled port.
Command Default
Error-disable
detection is enabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
—
This command was introduced in a release
earlier than Cisco NX-OS Release 7.0(0)N1(1).
7.0(0)N1(1)
This
command was modified. The
miscabling
keyword was added.
Examples
The following
example shows how to disable error-disabled detection on a miscabled port:
Device# configure terminal
Device(config)# no errdisable detect cause miscabling
Displays information about interfaces that are in error-disabled state.
errdisable
recovery cause
To enable
automatic recovery of an application from an error-disabled (errdisable) state,
use the
errdisable recovery
cause command in global configuration mode. To return to the
default setting, use the
no form of
this command.
Enables
the timer to recover from the bridge protocol data unit (BPDU) guard error
disable state.
failed-port-state
Enables
the timer to recover from the Spanning Tree Protocol (STP) set port state
failure.
link-flap
Enables
the timer to recover from link-state flapping.
loopback
Enables
timer to recover from the loopback error disabled state detected by
Unidirectional Link Detection (UDLD).
miscabling
Enables
the timer to automatically recover miscabled ports from an error-disabled
state.
psecure-violation
Enables
the timer to recover from the psecure-violation disable state.
security-violation
Enables
the timer to recover from the 802.1x violation disable state.
storm-control
Enables
the timer to recover from the storm control error-disabled state.
udld
Enables
the timer to recover from the UDLD error-disabled state.
vpc-peerlink
Enables
the timer to recover from an inconsistent virtual port channel (vPC) peer-link
error-disabled state.
Command Default
Automatic recovery
of any application from an error-disabled state is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
—
This command was introduced in a release
earlier than Cisco NX-OS Release 7.0(0)N1(1).
7.0(0)N1(1)
This
command was modified. The
miscabling
keyword was added.
Usage Guidelines
Use the
errdisable
recovery cause command to enable an automatic recovery of an application on
the interface from an error-disabled state. This command tries to bring the
interface out of the error-disabled state once all the causes have timed out.
The interface automatically tries to come up again after 300 seconds. To change
this interval, use the
errdisable
recovery interval command.
This command
does not require a license.
Examples
This example shows
how to automatically recover miscabled ports from an error-disabled state:
Device# configure terminal
Device(config)# errdisable recovery cause miscabling
Displays information about interfaces that are in error-disabled state.
errdisable
recovery interval
To configure the
error disable recovery timer, use the
errdisable recovery
interval in global configuration mode. To remove this
configuration, use the no form of
this command.
errdisable recovery intervalinterval
no errdisable recovery interval
Syntax Description
interval
Timer
interval in seconds. The range is from 30 to 65535.
Command Default
The default is 300
seconds.
Command Modes
Global configuration (config)
Command History
Release
Modification
—
This command was introduced in a release earlier than Cisco
NX-OS Release 7.0(0)N1(1).
Usage Guidelines
Use the errdisable recovery interval command to configure
the recovery timer. This command does not require a license.
Examples
This example shows
how to configure the recovery timer:
Displays information about interfaces that are in error-disabled state.
ether-type
(fabricpath-oam)
To configure the
FabricPath Operation, Administration, and Maintenance (OAM) flow profile
ether-type, use the
ether-type
command in FabricPath OAM flow profile configuration
mode. To remove the ether-type, use the
no
form of this command.
ether-type
ether-type
noether-type
Syntax Description
ether-type
The flow
profile ether-type. The range is from 0x0 to 0xffff.
To configure the
Virtual Station Interface (VSI) Discovery and Configuration Protocol (VDP)
multicast MAC address for the Edge Virtual Bridge (EVB) feature on a device,
use the
evb mac
command in global configuration mode. To return to the default, use the
no form of
this command.
evb macmac-address
noevb
macmac-address
Syntax Description
mac-address
VDP
multicast MAC address.
Command Default
The VDP multicast
MAC address for EVB is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
To configure the
device to use a VDP multicast MAC address, the EVB feature needs to be enabled
globally on the device using the
feature evb
command.
Examples
This example shows
how to configure a VDP multicast MAC address:
Device(config)# feature evb
Device(config)# evb mac 01-23-45-67-89-ab
To configure the Virtual Station Interface
(VSI) Discovery and Configuration protocol (VDP) keepalive parameter for the Edge
Virtual Bridging (EVB) feature on a device, use the
evbreinit-keep-alive command in global configuration
mode. To return to the default, use the
no form of
this command.
evbreinit-keep-alivetimer
noevbreinit-keep-alivetimer
Syntax Description
timer
Timer
exponent to calculate the keepalive time in seconds. The range is from 20 to
31.
Command Default
The default
reinit-keep-alive timer exponent is 22.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
feature evb
command to enable the EVB feature globally on the device before configuring the
keepalive parameter. After a VDP request is successful, a refresh request is
expected within the keep-alive time. If the refresh request is not received
within the keepalive time, device revokes the configuration changes. You must
configure the correct reinit-keepalive EVB parameter to align with the network
scale as each virtual machine contributes a refresh message as per the
keepalive time.
Examples
The following examples shows how to configure the keepalive parameter for EVB:
To configure the Virtual Station Interface
(VSI) Discovery and Configuration protocol (VDP) resource wait delay parameter
for the Edge Virtual Bridge (EVB) feature on a device, use the
evbresource-wait-delay command in global
configuration mode. To return to the default, use the
no form of
this command.
evbresource-wait-delaytimer
noevbresource-wait-delaytimer
Syntax Description
timer
Timer
exponent to calculate the actual delay in seconds. The range is from 20 to 31.
Command Default
The default
resource wait delay timer exponent is 20.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
feature evb
command to enable the EVB feature globally on the device before configuring the
resource wait delay parameter.
When a VDP request
is received, a series of configuration changes are triggered on the device. The
resource-wait-delay parameter indicates the maximum waiting time for a device
to complete the configuration change. If the change is not completed within the
wait delay parameter, then the VDP request fails. You can configure the
resource-wait-delay EVB parameter to align with specific configuration scale
and requirement.
Examples
The following example shows how to configure the VDP resource wait delay parameter:
To attach a remote
device in the fabric network to an Extensible Messaging and Presence Protocol
(XMPP) server, use the
fabric access attach
device command in privileged EXEC mode.
fabricaccessattachdevicedevice-name
Syntax Description
device-name
Name of
the remote device in the fabric network.
Command Default
The remote device
is not attached.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to attach a remote device to the XMPP server:
Creates one or more groups of devices on the fabric access network using the XMPP server.
fabric access
attach group
To attach a group
of devices in the fabric network to an Extensible Messaging and Presence
Protocol (XMPP) server, use the
fabric access attach
group command in privileged EXEC mode.
fabricaccessattachgroup
group-name
Syntax Description
group-name
Name of
the group of devices.
Command Default
The group of
devices in the fabric network is not attached to the XMPP server.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
A group may
consist of only one device.
Examples
The following
example shows how to attach a group of devices to the fabric network though the
XMPP server:
Creates one or more groups of devices on the fabric access network using the XMPP server.
fabric access
create group
To create one or
more groups of devices on the fabric access network using the Extensible
Messaging and Presence Protocol (XMPP) server, use the
fabric access create
group command in privileged EXEC mode. To remove one or more
groups of devices from the fabric access network, use the
no form of this command.
Attaches a remote device in the fabric network to an XMPP server.
fabric access
group
To configure a
group to which the switch needs to join or subscribe to in a fabric access
network, use the
fabric access
group command in global configuration mode. To remove the switch
from a group, use the
no form of this command.
Name of
the group to which the switch needs to join or subscribe to.
[group-name-2, group-name-3, ...]
(Optional) Name of
the additional groups.
Command Default
A switch in a
fabric access network is not joined to any group.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Switches do not
join all the groups in a fabric access network by default. The
fabric access group command should be
configured on all or required switches across the network in order to enable
the switches to join the specified group(s) in a network.
Examples
The following
example shows how to configure a switch to subscribe to group “spines” and
group “rr”:
To get the online
command syntax help using the currently logged-in local switch instead of remote
switches accessed via the fabric access group chat, use the fabric access local-help command in privileged
EXEC mode. To disable the online help on the currently logged-in local switch,
use the
no form of
this command.
fabric access local-help
no fabric access local-help
Syntax Description
This command has no arguments or keywords.
Command Default
Online help is
not enabled for the currently logged-in local switch in the fabric access group
chat mode.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Online help can
be used to find the available options after typing in a keyword. By default,
online help is executed on the remote devices that generate several keyword
options for each device in a network. To retrieve only those keywords related
to the currently logged in device, the
fabric access
local-help command is used.
Examples
The following
example shows how to enable the online-help option only for the currently
logged-in local device in the fabric access group chat mode:
Device(config)# fabric access local-help
fabric access
login
To log in to the
fabric access server, use the
fabric access
login command in privileged EXEC mode. To log out of the server,
use the
no form of
this command.
fabric access loginpassword
no fabric access login
Syntax Description
password
Password
for users to log in to the fabric access server. A password can contain any
combination of alphanumeric characters.
Command Default
Users are not
logged in to the fabric access server.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to log in to the fabric access server:
Configures a group to which the switch needs to join or subscribe to in a fabric access network.
fabric access
ping
To check the
network reachability of the switch to the fabric access server and to enable
the Extensible Messaging and Presence Protocol (XMPP) ping, use the
fabric access
ping command in global configuration mode. To disable the ping,
use the
no form of
this command.
(Optional) Specifies
the frequency of XMPP ping messages that are sent out. The default interval is
60 seconds. The range is from 30 to 180.
response seconds
(Optional) Specifies
the expected time to receive a ping response from the fabric access server. The
default response value is 10 seconds. The range is from 3 to 30.
retry
time
(Optional) Specifies
the number of ping messages that are sent without receiving a successful
response from the fabric access server. The default retry value is 5. The range
is from 1 to 5.
Command Default
The network
connectivity of the fabric access server is not verified.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to configure the switch to send XMPP ping message to the
fabric access server at a 120-second interval, with a 20-second response time
expectancy and with and three retries:
Configures a group to which the switch needs to join or subscribe to in a fabric access network.
fabric access
prepend-id
To enable the
display of the device ID in the response message of a remote device in the fabric
access group chat, use thefabric access
prepend-id command in global configuration mode. To remove the
device ID in the response message, use the
no form of
this command.
fabric access prepend-id
no fabric access prepend-id
Syntax Description
This command has no arguments or keywords.
Command Default
The device ID of
a remote device is not displayed in the response message.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
The
fabric access
prepend-id command enables the user to identify the device ID of
a remote device from where the response was generated. This identification
enables the local grep to find information about a specific device in a network
using the device ID.
Examples
The following
example shows how to enable the device ID being displayed in the response
message of a remote device:
Configures a group to which the switch needs to join or subscribe to in a fabric access network.
fabric access send
device
To send a command
to a host device or a list of host devices without entering the fabric access
group chat mode, use the
fabric access send
device command in privileged EXEC mode.
The
Jabber ID (JID) of the single peer device to be addressed. Multiple device JIDs
(device-jid2...device-jidn ) can also be specified.
“cli-command”
The
command to be executed at the device(s) whose JID(s) are listed as the
recipient(s) of this command.
The CLI command must be within quotation marks.
Command Default
A command is
not sent to the host device.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
To ensure the
remote device is in the correct mode to accept the command(s), start the
message to be sent with an
“end” keyword
followed by a space, semicolon, and the command. If there are multiple
commands to be sent, each command should be separated by a space and semicolon.
Examples
The following
example shows how to send a command to a host device with the JID p3-ac13-64t
to enable
“feature
lldp” on that device:
Sends a CLI command to a group of devices without entering fabric access group chat mode.
fabric access send
group
To send a CLI
command to a group of devices without entering fabric access group chat mode,
use the
fabric access send
group command in EXEC mode.
fabric access send groupgroup-name"cli-command"
Syntax Description
group-name
Name of
the group in the fabric access network to which messages are sent.
"cli-command"
CLI
command to be executed for a group of devices in a fabric access network.
Note
The
CLI command must be within quotation marks.
Command Default
No command is
sent.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
fabric access send
group command to send CLI commands to a group in a fabric access
network without entering fabric access group chat mode.
Note
You need to
enable the fabric access feature to use the
fabric access send
group command. Use the
feature fabric
access command to enable fabric access on a device.
Examples
This example shows
how to send CLI commands to a group with the group name “spines” in a fabric
access network:
Sends a command to a host device or a list of host devices without entering the fabric access group chat mode.
fabric access
server
To configure the
fabric access server to be connected to from a device, use the
fabric access
server command in global configuration mode. To disconnect the
device from the fabric access server, use the
no form of
this command.
(Optional)
Configures virtual routing and forwarding (VRF) information for a fabric access
server.
vrf-name
(Optional)
Name of the VRF.
default
(Optional)
Configures the default VRF name.
management
(Optional)
Configures the management VRF name.
device
(Optional)
Configures the device in the fabric network.
device-name
(Optional)
Name of the device to be configured in the fabric network.
password
(Optional)
Configures the password for a device in the fabric network.
password-name
(Optional) Password for the device.
Command Default
A fabric access
server is not configured in a fabric network.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
fabric access
server command to configure the fabric access server to be
connected from the device that needs to be added to the fabric network. You
need to configure the device name and password for the device in the fabric
access server. The device name has to be a unique name in the network on a
fabric access server.
Note
You need to
enable the fabric access feature to access and view the
fabric access
server command. Use the
feature fabric
access command to enable the fabric access feature on a device.
Examples
This example shows
how to configure a fabric access server in a fabric network:
Device(config)# feature fabric access
Device(config)# fabric access server host1.cisco.com management password test
Displays the connection status of a device or a user that is connected in the fabric access network.
fabric
connectivity cable-plan enforce
To enforce an
imported cable plan, use the
fabricconnectivitycable-planenforce command in global configuration mode. To
stop enforcing a cable plan, use the
no
form of this command.
fabricconnectivitycable-planenforce
nofabricconnectivitycable-planenforce
Syntax Description
This command has
no arguments or keywords.
Command Default
A cable plan is
not enforced.
Command Modes
Global configuration (config)
Command History
Release
Modification
6.0(2)N3(1)
This
command was introduced.
Usage Guidelines
When the
fabricconnectivitycable-planenforce command is configured, all type, length,
value (TLV) fields received on a device are checked against the enforced cable
plan. If no cable plan is enforced, checks are ignored.
After importing a
cable plan if the cable plan is not enforced or if the
no
fabricconnectivitycable-planenforce command is configured, all cable plan
checks are disabled. However, the imported cable plan will remain in the
device.
Use the
showfabricconnectivitycable-plancommand to view the currently enforced cable plan.
Examples
The following
example shows how to enforce an already imported cable plan:
Enables the cable management feature for a network
fabric
connectivity cable-plan generate
To automatically
generate a cable plan based on the topology of the data center neighbors, use
the
fabricconnectivitycable-plangenerate command in privileged EXEC mode.
(Optional)
Filename of the newly generated cable plan.
Command Default
A cable plan is
not automatically generated.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)N3(1)
This
command was introduced.
Usage Guidelines
The
fabricconnectivitycable-plangenerate command creates a valid cable plan from
the output of the
show
fabric
connectivity
neighbors command. You can modify the
autogenerated cable plan to suit the link or connectivity endpoints within your
data center.
If you do not
specify a
plan-name,
then the filename is a generic time-stamped name.
Note
Before
configuring this command you must enable the
featurelldp command and then the
featurecable-management command in global configuration
mode.
Examples
The following
example shows how to autogenerate a cable plan named cplan1:
(Optional)
Imports a cable plan from a remote FTP location.
scp:
(Optional)
Imports a cable plan from a remote Secure Copy Protocol location.
sftp:
(Optional)
Imports a cable plan from a remote Secure FTP location.
tftp:
(Optional)
Imports a cable plan from a remote TFTP location.
bootflash:
Imports a
cable plan from the local location.
vrf
vrf-name
(Optional)
Displays information about the specified virtual routing and forwarding
instance.
update
(Optional) Updates the existing cable plan with a newly imported
cable plan.
verbose
(Optional) Prints all errors regarding the cable plan file
import to the console.
Command Default
Cable plans are
not imported.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
6.0(2)N3(1)
This
command was introduced.
Usage Guidelines
When you copy a
cable plan from a remote location, you must specify the local location to save
the file. If a remote import fails, the downloaded file is deleted
automatically.
Once you
configure the command, you have to enter the name of the source cable plan file
and the destination cable plan file.
When you specify
the
fabricconnectivitycable-planimportbootflash: command, the local cable plan file that
exists in the bootflash is imported. Imported cable plans are stored in the
device memory. Once imported, cable plans are persistent across reboots if you
configure the
copy running-config
startup-config command.
Examples
The following
example shows how the cp.xml file is imported from the local location:
The following
sample output from the
fabricconnectivitycable-planimportbootflash:verbose command displays cable plan import
failures:
Device# fabric connectivity cable-plan import bootflash:cp_failure.xml verbose
/bootflash/cp_failure.xml:6: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': [facet 'pattern'] The value 'Eth11' is not accepted by the pattern 'Eth[0-9]{1,3}/[0-9]{1,3}'.
/bootflash/cp_failure.xml:6: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': 'Eth11' is not a valid value of the atomic type '{http://www.cisco.com/cableplan/Schema2}portType'.
/bootflash/cp_failure.xml:7: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': [facet 'pattern'] The value 'Et1/1' is not accepted by the pattern 'Eth[0-9]{1,3}/[0-9]{1,3}'.
/bootflash/cp_failure.xml:7: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': 'Et1/1' is not a valid value of the atomic type '{http://www.cisco.com/cableplan/Schema2}portType'.
/bootflash/cp_failure.xml:11: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': [facet 'pattern'] The value 'Eth18881/2' is not accepted by the pattern 'Eth[0-9]{1,3}/[0-9]{1,3}'.
/bootflash/cp_failure.xml:11: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': 'Eth18881/2' is not a valid value of the atomic type '{http://www.cisco.com/cableplan/Schema2}portType'.
/bootflash/cp_failure.xml:13: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': [facet 'pattern'] The value 'th1/2' is not accepted by the pattern 'Eth[0-9]{1,3}/[0-9]{1,3}'.
/bootflash/cp_failure.xml:13: element LINK_INFO: Schemas validity error : Element '{http://www.cisco.com/cableplan/Schema2}LINK_INFO',
attribute 'destPort': 'th1/2' is not a valid value of the atomic type '{http://www.cisco.com/cableplan/Schema2}portType'.
Error: Failed to import cable-plan: Invalid cable-plan
Device#
The following is
a sample cable plan for a data center with two spine devices and three leaf
devices. This cable plan describes a data center that contains the following
switches: spine1, spine2, leaf1, leaf2, and leaf3. The sourceChassis, spine2 is
connected to destChassis, leaf1 through Ethernet 1/1. If your data center
network has more interfaces than the ones described in the cable plan, a
warning about the absence is logged.
The following
paragraphs describe the lines and the XML tags and attributes associated with
each line in the cable plan. These lines are required headings for XML
processing and Cisco-specific headers that denote that this is a Cisco cable
plan. The format must be exactly the same as shown in the following example for
all cable plans. Failure to adhere to the format results in a rejected cable
plan.
The
CISCO_NETWORK_TYPES tag is required and it is the parent tag for the entire XML
cable plan. The entire cable plan must be within this tag.
The DATA_CENTER
tag is required and it houses all information about each chassis in the plan.
The networkLocation tag is required and it specifies the location of the data
center. The idFormat tag is required and it specifies the format in which IDs
are present in subsequent entries. In the Cisco NX-OS Release 6.0(2)N3(1), the
only supported format is "hostname". Cable plans that do not use "hostname" as
the format are rejected.
The CHASSIS_INFO
tag is required and it describes one single chassis. All interfaces that belong
to the sourceChassis that administrators want to include in the cable plan must
be within this tag. The sourceChassis tag is required and it describes the
chassis that all subsequent interfaces (described below by LINK_INFO tags)
belong to.
Include all
details about the interfaces on a device inside the CHASSIS_INFO tag. If you
need to check interfaces on another device, include them inside another
CHASSIS_INFO tag. There is no limit to the number of unique CHASSIS_INFO tags
in a cable plan.
In the following
example, all interfaces within the CHASSIS_INFO tag belong to spine1 chassis.
The specified chassis name must be the fully qualified domain name of the
device. If a domain name is configured for the hostname, the hostname must be
followed by the domain name. For example, spine1.cisco.com if spine1 is
configured with the domain name, cisco.com.
The type tag is
required and it specifies the type of chassis. In the Cisco NX-OS Release
6.0(2)N3(1), only Cisco Nexus switches are supported. This tag is not case
sensitive. Cable plans that do not adhere to the "n#k" format are rejected.
<CHASSIS_INFO sourceChassis="spine1" type="n7k">
The LINK_INFO
tag is required and it describes an interface connection from the sourceChassis
to the destChassis. In the following example, the spine1 source port on
Ethernet 2/1 is connected to the leaf1 destination port on Ethernet2/1, spine1
source port on Ethernet 2/2 is connected to leaf2 destination port on Ethernet
2/1, and so on.
The sourcePort
tag is required and it denotes the port on the sourceChassis. Source ports must
be unique per chassis. For example, spine1 must not specify multiple
connections that come from port Ethernet 2/1. The cable plan import will not
fail if you do not specify unique ports. However, a warning is displayed on the
console and only the first entry is read and checked by the cable plan.
The destChassis
tag is required and it denotes the destination chassis that the sourceChassis
is connected to. The destChassis name must be the fully qualified domain name.
The destPort tag
is required and it denotes the port on the destination chassis. Like the
sourcePort, the destPort must be unique to the destChassis.
Displays the cable plan available in the system memory.
fabric
connectivity mismatch action delay
To delay the port
error-disable action on detecting cabling errors for a specified time, use the
fabric connectivity
mismatch action delay command in global configuration mode. To
remove this configuration, use the
no form of
this command
fabric connectivity mismatch action delaytime
no fabric connectivity mismatch action delaytime
Syntax Description
time
Time in
seconds to delay action. The range is from 30 to 3600.
Command Default
Delayed action on
mismatched errors is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use this command
to delay, by seconds, any action caused by mismatched errors. For example, if
you set the action delay to 30 seconds and have errors configured to
error-disable ports, then in case an error is detected at a network port, the
port is error-disabled after a period of 30 seconds. If a valid entry is
received within the wait period of 30 seconds, the port will remain open and
not be error-disabled. You have to enable the cable management feature using
the
feature cable-management
command to be able to configure the
fabric connectivity
mismatch action delay command.
Examples
The following
example shows how to configure a time period to delay action caused by mismatch
errors. Here the time to delay action is set to 35 seconds.
To configure the
tier level of a device in the Dynamic Fabric Automation (DFA) fabric, use the
fabric connectivity
tier command in global configuration mode. To remove this
configuration, use the no form of
this command.
fabric connectivity tiertier-level
no fabric connectivity tiertier-level
Syntax Description
tier-level
Tier level
of the device. The range is from 1 to 16, where 1 indicates a leaf, 2 indicates
a level 1 spine, 3 indicates a level 2 spine, and so on.
Command Default
Tier level of the
device is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced
Usage Guidelines
To detect and
resolve miscabling issues in a Clos network, DFA provides the user the
functionality to assign a sequential number (called the tier number) at each
stage of the network topology. Every device in a stage can be associated with
the corresponding tier level number assigned to the stage the device is in. All
leaf switches (in the lowest level of the Clos stage) are provisioned with a
tier level of 1, the next higher-level stage devices (1st stage of spine
switches) are provisioned with a tier level value of 2, and the next
higher-level stage devices (2nd stage of spine switches) are provisioned with a
tier level of 3, and so on. Use the
fabric connectivity
tier command to assign the tier-level number for a specific
device in the fabric. You have to enable the cable management feature using the
feature cable-management
command to be able to configure the
fabric connectivity
tier command.
Examples
The following
example shows how you can assign a tier number to a specific device in the
topology:
Delays the port error-disable action on detecting cabling errors for a specified time.
fabric database mobility-domain
To configure the mobility domain name, use the fabric database mobility-domain command in global configuration mode. To remove the mobility domain name, use the no form of this command.
fabric database mobility-domain domain-name
no fabric database mobility-domain domain-name
Syntax Description
domain-name
Mobility domain name up to 128 characters.
Command Default
The mobility domain name is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
Use the fabric database mobility-domain command to configure the mobility domain name that is used to get the profile name if the profiles are stored remotely.
Examples
The following example shows how to configure the mobility domain name:
To configure
the external database, use
the fabric database
type command in global configuration mode. To remove this
configuration, use the
no form of
this command
fabric database type
{ network | profile }
no fabric database type
{ network | profile }
Syntax Description
network
Configures
the network database.
profile
Configures
the config-profile database.
Command Default
The external database
is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to configure a database type:
Device# configure terminal
Device(config)# fabric database type network
Device(config)# fabric database type profile
To specify the MAC address of the server facing ports across all leaf nodes, use the fabric forwarding anycast-gateway-mac command in global configuration mode. To disable the anycast gateway MAC address, use the no form of this command.
fabric forwarding anycast-gateway-mac mac-address
no fabric forwarding anycast-gateway-mac mac-address
Syntax Description
mac-address
Anycast gateway MAC address of the switch.
Command Default
The anycast gateway MAC address is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
The anycast gateway MAC address is used per interface; hence, it is replicated across all the switch virtual interfaces (SVI) that are supporting proxy gateway or anycast gateway.
Examples
The following example shows how to configure the anycast gateway MAC address:
To configure a control segment under a switched virtual interface (SVI) in a default virtual routing and forwarding (VRF) instance, use the fabric forwarding control-segment command in interface configuration mode.
fabric forwarding control-segment
Syntax Description
This command has no arguments or keywords.
Command Default
A control segment is not configured.
Command Modes
Interface configuration (config-if)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the fabric forwarding control-segment command to specify an SVI interface to be a fabric control VLAN interface on which adjacencies are established in the default VRF. You can configure only one SVI interface in the default VRF as a fabric control VLAN interface.
Note
You can also configure a control segment under a bridge domain.
Examples
The following example shows how to specify an SVI interface to be a fabric control VLAN interface:
To configure the conversational aging timeout value, use the fabric forwarding conversational-aging command in global configuration mode. To remove the aging timeout value, use the no form of this command.
fabric forwarding conversational-aging timeout
no fabric forwarding conversational-aging timeout
Syntax Description
timeout
Conversational aging timeout value in minutes. The range is from 15 to 1800. The default is 30.
Command Default
The timeout value is set to 30 minutes.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
Use the fabric forwarding conversational-aging command to configure the aging timeout value that determines if a conditional route must be aged or not.
Examples
The following example shows how to set the conversational learning aging timeout value to 50 minutes:
To enable Layer 3 conversational learning-based route download into the forwarding information base (FIB), use the fabric forwarding conversational-learning command in global configuration mode. To disable the conversational learning-based FIB route download, use the no form of this command.
fabric forwarding conversational-learning [all]
no fabric forwarding conversational-learning
Syntax Description
all
(Optional) Enables conversational learning for all virtual routing and forwarding (VRF) instances.
Command Default
Conversational learning is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
Use the fabric forwarding conversational-learning command to enable Layer 3 conversational learning. After conversational learning is enabled, the host routes are downloaded into the FIB when a conversation is detected.
Note
If you use this command without the all keyword, it specifies that conversational learning is used for the default VRF.
Examples
The following example shows how to enable Layer 3 conversational learning for all VRFs:
To specify a
fabric forwarding identifier, use the
fabric forwarding
identifier command in global configuration mode. To remove this
configuration, use the
no form of
this command.
fabric forwardingidentifierid
nofabric forwardingidentifierid
Syntax Description
identifierid
Specifies
a fabric forwarding identifier number. The range is from 1 to 65535.
Command Default
A fabric
forwarding identifier is not specified.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use this command
to configure a fabric forwarding identifier.
Examples
The following
example shows how to configure a fabric forwarding identifier:
To specify the role of a device in the network, use the fabric forwarding switch-role command in global configuration mode. To disable the role specified for a device, use the no form of the command.
Use the fabric forwarding switch-role command to specify the role of a device. You can configure a device to act like a border, a spine or a leaf. A device sends notifications to registered components whenever there is a change in the role of a device. You can specify a combination of a border and a leaf or a spine on a device. Both Border Gateway Protocol (BGP) and Intermediate System-to-Intermediate System (ISIS) protocol restart when the role of a device changes.
Examples
The following example shows how to specify the role of a device to be a border and a spine:
To enable the FabricPath Bidirectional Forwarding (BFD) feature on an Intermediate System-to-Intermediate System (IS-IS) interface, use the fabricpath isis bfd command in interface configuration mode. To disable the FabricPath BFD feature on the IS-IS interface, use the no form of this command.
fabricpathisisbfd [disable]
no fabricpathisisbfd [disable]
Syntax Description
disable
(Optional) Disables the FabricPath feature on the IS-IS interface.
Command Default
The FabricPath feature is not enabled on the IS-IS interface.
Command Modes
Interface configuration (config-if)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
The no fabricpath isis bfd
command disables the BFD on the interface, but if global BFD is configured, the interface inherits the global BFD and BFD is remains enabled on that interface.
The no fabricpath isis bfd disable
command disables the BFD on the interface even if global BFD is configured. This command overrides the global BFD configuration. No BFD is configured on that interface .
Examples
This example shows how to enable the FabricPath feature on an IS-IS interface:
Displays information about the FabricPath Intermediate System-to-Intermediate System (IS-IS) interface.
fabricpath oam
profile
To configure a
FabricPath Operation, Administration, and Maintenance (OAM) profile and enter
FabricPath OAM profile configuration mode, use the
fabricpath oam
profile command in global configuration mode. To remove the
FabricPath OAM profile, use the
no form of
this command.
fabricpathoamprofileprofile-id
nofabricpathoamprofileprofile-id
Syntax Description
profile-id
Profile
ID. The range is from 1 to 1023.
Command Default
A FabricPath OAM
profile is not configured.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
All FabricPath
OAM profiles have default values. To display the FabricPath OAM profiles, use
the
show run all
command. A FabricPath OAM profile with a profile ID of 1 is created by default,
when the FabricPath feature is enabled.
Examples
The following
example shows how to configure a FabricPath OAM profile with a profile ID of
100.
To enable the
cable management feature for a network, use the
feature
cable-management command in global configuration mode. To disable
the feature, use the
no form of
this command.
featurecable-management
nofeaturecable-management
Syntax Description
This command has
no arguments or keywords.
Command Default
Disabled
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
feature
cable-management command to enable the cable management feature.
This command does not require a license.
Note
Enable the
Link Layer Discovery Protocol (LLDP) by using the
feature lldp
command prior to enabling the cable management feature.
Examples
This example shows
how to enable the cable management feature:
This example shows
how to disable the cable management feature:
Device(config)# no feature cable-management
feature
evb
To enable the Edge
Virtual Bridging (EVB) feature on a device, use the
feature evb
command in global configuration mode. To disable EVB feature, use the
no form of
this command.
featureevb
nofeatureevb
Syntax Description
This command has
no arguments or keywords.
Command Default
EVB is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You can enable or
disable EVB globally on a device. You must use the
feature evb
command to enable and configure the EVB parameters.
Examples
This example shows
how to enable the EVB feature on a device:
Displays information associated with Edge Virtual Bridging (EVB).
feature
fabric
To enable fabric
network services on a device, use the
featurefabric command in global configuration mode. To
disable the fabric network services, use the
no form of
this command.
To enable the
fabric access feature for a fabric network, use the
feature fabric
access command in global configuration mode. To disable the
fabric access feature, use the
no form of
this command.
feature fabric
access
nofeature fabric access
Syntax Description
This command
has no arguments or keywords.
Command Default
Disabled
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You must use the
feature fabric
access command to enable the fabric access feature. This command
does not require a license.
Examples
This example shows
how to enable the fabric access feature on a device:
Device(config)# feature fabric access
This example shows
how to disable the fabric access feature on a device:
Displays the connection status of a device or a user that is connected in the fabric access network.
feature fabric multicast
To enable the Next-Generation Multicast VPN (NG-MVPN) features on a device, use the feature fabric multicast command in global configuration mode. To disable the NG-MVPN features on a device, use the no form of this command.
feature fabric multicast
no feature fabric multicast
This command
has no arguments or keywords.
Command Default
The NG-MVPN features are disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following example shows how to enable NG-MVPN features on a device:
Device(config)# feature fabric multicast
The following example shows how to disable NG-MVPN features on a device:
To enable the (VLAN)-based virtual network (VN) segment feature on a device, use the
feature
vn-segment-vlan-based command in global configuration mode. To
disable VLAN-based VN segment feature, use the
no form of
this command.
feature vn-segment-vlan-based
nofeature vn-segment-vlan-based
Syntax Description
This command has
no arguments or keywords.
Command Default
The VLAN-based virtual network segment is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You can enable or
disable the VLAN-based VN segment feature globally on a device. The VLAN-based VN segment feature
is enabled only if the feature-set fabricpath is
enabled on the device.
Examples
This example shows
how to enable the VLAN-based VN segment feature on a device:
To configure the
direction of FabricPath Operation, Administration, and Maintenance (OAM) packet
flow and enter FabricPath OAM profile flow configuration mode, use the
flow command
in FabricPath OAM profile configuration mode. To remove the flow configuration,
use the
no form of
this command.
flow
{ forward
|
reverse }
noflow
{ forward
|
reverse }
Syntax Description
forward
Configures
the FabricPath OAM forward flow.
reverse
Configures
the FabricPath OAM reverse flow.
Command Default
The direction of
FabricPath OAM packet flow is not configured.
Use the
flow command
to configure the direction of flow entropy, forward or reverse, and enter
FabricPath OAM profile flow configuration mode. You can configure specific
information for forward or reverse flow entropy from FabricPath OAM profile
flow configuration mode.
Examples
The following
example shows how to configure the forward flow entropy for FabricPath OAM.
Configures the FabricPath OAM flow protocol number.
hop
(fabricpath-oam)
To configure the
hop limit for a FabricPath OAM service packet protocol header, use the
hop command
in FabricPath OAM profile configuration mode. To restore the hop limit to the
default value, use the
no form of
this command.
hophop-limit
nohop
Syntax Description
hop-limit
Hop limit.
Range is from 1 to 255. Default is 64.
Command Default
The hop limit for
FabricPath OAM service packets is 64 hops.
Configures the FabricPath OAM flow protocol number.
include profile
To configure a set of VLAN profile instances to refer to a common virtual routing and forwarding (VRF) instance, use the include profile command in profile configuration mode. To remove the reference to a common VRF instance, use the no form of this command.
include profileprofile-name
no include profileprofile-name
Syntax Description
profile-name
Name of the profile. The maximum number of characters allowed is 80.
Command Default
VLAN profile instances do not refer to a common VRF instance.
Command Modes
Profile configuration (config-profile)
Command History
Release
Modification
7.0(0)N1(1)
This command was introduced.
Usage Guidelines
Use the include profile command to configure a set of VRF profile instances to refer to a common VRF instance. For example, a set of VLANs can refer to the same VLAN VRF instance. Any configuration after you configure the first VLAN VRF instance will increment the reference count of the include instance. The configuration related to the VRF stays until the last instance referring to the VRF is present.
Examples
The following example shows how to configure a set of VLAN profile instances to refer to a common VRF instance:
To create an instance of a user-defined parameter list, use the
instance command in parameter list configuration mode. To remove an instance of a user-defined parameter list, use the
no form of
this command.
instanceinstance-name
noinstanceinstance-name
Syntax Description
instance-name
Parameter-list instance name.
Command Default
A user-defined parameter-list instance is not created.
Command Modes
Parameter list configuration (config-param-list)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
You can create instances of a parameter list for different hosts with various values. When you create an instance of a parameter list using the instance command, the device enters parameter instance configuration (config-param-inst) mode. The following options are available in this mode:
set - Sets the parameter value.
this - Displays information about the instance.
verify - Verifies the instance with the specified device-profile.
end - Exits parameter instance configuration mode and returns to EXEC mode.
exit - Exits parameter instance configuration mode and returns to parameter list configuration mode.
pop - Pops the mode from the stack or restores it from the specified name.
push - Pushes the current mode to the stack or saves it with the specified name.
where - Displays instance-related details (such as parameter-list name, instance name, and so on).
Examples
The following example shows to create an instance inst1 under the user-defined parameter list List1:
Creates user-defined parameters for the specified parameter list.
interface
(fabricpath-oam)
To configure a
FabricPath Operation, Administration, and Maintenance (OAM) egress interface,
use the
interface
command in FabricPath OAM profile configuration mode. To remove the egress
interface configuration, use the
no form of
this command.
You can configure
multiple egress interfaces to create an interface list in the fabric OAM
profile. You can also enter a range of interface addresses of the same
interface type. You can configure Ethernet or PortChannel interfaces.
Examples
The following
example shows how to configure an egress ethernet interface.
To configure a
Layer 3 flow destination or source IPv4 address, use the
ip command in
FabricPath OAM profile flow configuration mode. To remove the IPv4 flow
address, use the
no form of
this command.
ip
{ destination
|
source }
ip-address
noip
{ destination
|
source }
Syntax Description
destination
Specifies
the FabricPath OAM profile flow destination address.
source
Specifies
the FabricPath OAM profile flow source address.
Configures the direction FabricPath OAM flow entropy.
ip arp rarp fabric-forwarding
To enable forwarding of Reverse Address Resolution Protocol (RARP) messages from a host to the fabric, and to set a rate-limit for the messages being forwarded, use the
ip arp rarp fabric-forwarding command in global configuration mode. To disable forwarding of RARP messages from a host to the fabric, use the
no form of
this command.
ip arp rarp fabric-forwarding
[
rate-limitrate-limit]
(Optional) Specifies the forwarding rate of the RARP frames.
Note
The default forwarding rate is 200 RARP frames per second. You can specify a forwarding rate in the range of 200 to 400 RARP frames per second.
Command Default
Forwarding of RARP messages from a host to the fabric is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
If you want to enable forwarding of RARP messages and set the rate to the default value of 200 RARP frames per second, then use the ip arp rarp fabric-forwarding command.
If you want to enable forwarding of RARP messages and set the rate to a specific value, then include the use the rate-limit keyword and the rate-limit value.
Examples
The following example shows how to enable forwarding of RARP messages from a host to the fabric:
To enable
multicast enhanced fabric forwarding for a particular Virtual Routing and
Forwarding (VRF), use the
ip multicastfabric-forwarding command in global configuration
mode. To disable fabric forwarding for the VRF, use the
no form of
this command.
{ ip
| ipv6 } multicastfabric-forwarding
no
{ ip
| ipv6 } multicastfabric-forwarding
Syntax Description
ip
Enables
IPv4 multicast fabric forwarding.
ipv6
Enables
IPv6 multicast fabric forwarding.
Command Default
Multicast
forwarding is disabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Examples
The following
example shows how to enable the fabric forwarding feature:
Displays the global state associated with the fabric multicast process.
ipv6
(fabricpath-oam)
To configure a
Layer 3 flow destination or source IPv6 address, use the
ipv6 command
in FabricPath OAM profile flow configuration mode. To remove the IPv6 flow
address, use the
no form of
this command.
ipv6
{ destination
|
source }
ip-address
noipv6
{ destination
|
source }
Syntax Description
destination
Specifies
the FabricPath OAM profile flow destination address.
source
Specifies
the FabricPath OAM profile flow source address.
Configures the direction FabricPath OAM flow entropy.
logging level
evb
To enable the
system log (syslog) filter level for an Edge Virtual Bridging (EVB) session,
use the
logginglevelevb command in global configuration mode. To
disable the syslog filter level for EVB, use the
no form of
this command.
logginglevelevblog-level
no logginglevelevblog-level
Syntax Description
log-level
Sets the
severity for the syslog filter level. The level values ranges from 0 to 7. The
severity associated with the values are:
0-emerg—Sets severity
levels for emergencies.
1-alert—Sets severity
levels for alerts.
2-crit—Sets severity levels
for critical issues.
3-err—Sets severity levels
for errors.
4-warn—Sets severity levels
for warnings.
5-notif—Sets severity
levels for notifications.
6-inform—Sets severity
levels for session information.
7-debug—Sets severity
levels for debugs.
Command Default
Syslog filter
level with severity value 5 is enabled.
Command Modes
Global configuration (config)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
Use the
featureevb command to enable the EVB session. This, in
turn, enables the
evb keyword
in the
logging level
command on the device.
Examples
The following
example shows how to set a syslog filter level of 4 for an EVB session:
To specify a
FabricPath OAM flow destination or source MAC address, use the
mac-address
command in FabricPath OAM profile flow configuration mode. To remove the MAC
address, use the
no form of
this command.
mac-address
{ destination
|
source }
mac-address
nomac-address
{ destination
|
source }
Syntax Description
destination
Specifies
the FabricPath OAM profile flow destination MAC address.
source
Specifies
the FabricPath OAM profile flow source MAC address.
Configures the direction FabricPath OAM flow entropy.
match (VLAN access-map)
To specify an access control list (ACL) for traffic filtering in a VLAN access map, use the match command in VLAN access-map configuration mode. To remove a
match
command from a VLAN access map, use
the no form of
this command.
match {ip | ipv6 | mac} addressaccess-list-name
no
match {ip | ipv6 | mac} addressaccess-list-name
Syntax Description
ip
Specifies that the ACL is an IPv4 ACL.
ipv6
Specifies that the ACL is an IPv6 ACL.
mac
Specifies that the ACL is a MAC ACL.
access-list-name
Specifies the ACL by name, which can be up to 64 alphanumeric, case-sensitive characters.
Command Default
None
Command Modes
VLAN access-map configuration
Command History
Release
Modification
—
This
command was introduced in a release earlier than Cisco NX-OS Release 7.0(0)N1(1).
Usage Guidelines
You can specify one or more
match
commands per entry in a VLAN access
map.
By default, the device classifies traffic and applies IPv4 ACLs to IPv4 traffic, IPv6 ACLs to IPv6 traffic, and MAC ACLs to all other traffic.
This command does not require a license.
Examples
This example shows how to create a VLAN access
map named vlan-map-01 and add two entries that each have
two
match
commands and one action command:
Device(config-access-map)# vlan access-map vlan-map-01
Device(config-access-map)# match ip address ip-acl-01
switch(config-access-map)# action forward
switch(config-access-map)# match mac address mac-acl-00f
switch(config-access-map)# vlan access-map vlan-map-01
switch(config-access-map)# match ip address ip-acl-320
switch(config-access-map)# match mac address mac-acl-00e
switch(config-access-map)# action drop
switch(config-access-map)# show vlan access-map
Vlan access-map vlan-map-01 10
match ip: ip-acl-01
match mac: mac-acl-00f
action: forward
Vlan access-map vlan-map-01 20
match ip: ip-acl-320
match mac: mac-acl-00e
action: drop
mtrace
fabricpath
To trace the path
from a source to a destination branch for FabricPath OAM, use the
mtrace
fabricpath command in privileged EXEC mode.
(Optional) Specifies the ID of the multicast tree to be verified.
ftagftag-id
(Optional) Specifies the multicast Forwarding Tag (FTag) ID.
profileprofile-id
Specifies
the profile ID.
macdstdst-mac
Specifies the destination MAC address.
etypeetype
Specifies the ether type.
ipdstdst-ip
Specifies the destination IP address.
srcsrc-ip
Specifies the source IP address.
forwardflowflow-ent
Specifies the input flow entropy (128 bytes) from actual user data traffic so
that FabricPath OAM packet takes the same path as user traffic.
l2
Specifies that the input flow entropy must be terminated until
only Layer 2 entries are used. For example, MAC address, VLAN, and e-type. We
recommend that you use only one string option.
l3
Specifies that the input flow entropy must be terminated until only Layer 3
entries are used.
Note
Only IPv4 and IPv6 entries can be processed
ingressif-id
(Optional) Specifies the ingress interface ID.
vlanvlan-id
Specifies the VLAN ID for the multicast tree to be verified.
tagtag-id
Specifies the tag ID.
Note
The VLAN ID and tag ID are mutually exclusive.
dot1qdot1q-idintf-id
Specifies the 802.1Q tag ID.
Note
The
dot1q option is not available on
Cisco Nexus 5000 series and 6000 series switches; it is available only on the
Cisco Nexus 7000 series switches.
use-host-vlan
(Optional) Specifies that only VLAN input should be used. Use
this keyword when enhanced forwarding is applied and you do not want to use
translated VLAN. Use this option when you specify the ingress interface ID or
when you specify the flow entropy through the
profile
keyword or through forward flow with IP address of customer traffic.
topologyt-id
(Optional) Specifies the topology ID. Range is from 0 to 63.
Default is 0.
replymodeout-of-band
(Optional) Specifies that the FabricPath OAM reply mode is out
of band. By default, FabricPath OAM is replied in band (on the FabricPath
network). Use the
replymodeout-of-band keyword to change the mode of reply to
out of band for input IPv4 or IPv6 addresses. For routing, only the default VRF
is used.
ipv4ip-addr
(Optional) Specifies the input IPv4 address for out-of-band
reply.
ipv6ipv6-addr
(Optional) Specifies the input IPv6 address for out-of-band
reply.
datapatterndata
(Optional) Specifies the data pattern.
sizesize
(Optional) Specifies the padding size of data TLV or test TLV.
The total size must not be greater than the MTU of the egress interface.
validate
(Optional) Validates the
ping command.
repeatrepeat-count
(Optional) Specifies the repeat value.
intervalinterval-value
(Optional) Specifies the minimum send delay between requests, in
milliseconds. The range is from 100 to 3600000. Default is 0 for synchronous
ping, 1000 for asynchronous ping.
timeouttimeout-value
(Optional) Specifies the timeout values in seconds. Range is
from 1 to 36000.
hophop-count
(Optional) Specifies the FabricPath OAM ping hop count. Range is
from 1 to 64. Default is 63.
switch-idsw-id
(Optional) Sends an mtrace request to the specified switch ID.
verbose
(Optional) Displays additional information.
Command Modes
Privileged EXEC (#)
Command History
Release
Modification
7.0(0)N1(1)
This
command was introduced.
Usage Guidelines
For a
synchronous ping, traceroute, or mtrace, if the profile has multiple
interfaces, only the first interface is selected. Use the
interface
keyword to overwrite the selected interface. Only one session is created.
The following
rules are apply:
If a tree ID is
specified, an ether type cannot be specified.
If a Layer 2 tree is
specified, a source MAC cannot be specified.
If a Layer 3 tree is
specified, a source and destination MAC addresses cannot be specified.
If flow entropy is
specified, type of flow, either Layer 2 or Layer 3, must be specified. If the
flow is Layer 2, the source MAC address is overwritten. If the flow is Layer 3,
the source and destination MAC addresses are overwritten.
Examples
The following
example shows how to specify a FabricPath mtrace for all trees.
Device# mtrace fabricpath vlan 10
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'D' - Destination Unreachable, 'X' - unknown return code,
'V' - VLAN nonexistent, 'v' - VLAN in suspended state,
'm' - malformed request, 'C' - Cross Connect Error,
'U' - Unknown RBridge nickname, 'n' - Not AF,
'*' - Success, Optional Tlv incomplete,
'I' - Interface not in forwarding state,
'S' - Service Tag nonexistent, 's' - Service Tag in suspended state,
'c' - Corrupted Data/Test
Sender handle: 3
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms
! 3498 Rcvd on Eth1/47 fwd 2ms
FabricPath mtrace for multicast ftag 2, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms
! 3498 Rcvd on Eth1/47 fwd 2ms
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms
! 3498 Rcvd on Eth1/47 fwd 2ms
FabricPath mtrace for multicast ftag 2, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms
! 3498 Rcvd on Eth1/47 fwd 3ms
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms
! 3498 Rcvd on Eth1/47 fwd 3ms
The following
example shows how to specify FabricPath mtrace for a specific tree.
Device(#) mtrace fabricpath tree 1 vlan 10 repeat 1
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'D' - Destination Unreachable, 'X' - unknown return code,
'V' - VLAN nonexistent, 'v' - VLAN in suspended state,
'm' - malformed request, 'C' - Cross Connect Error,
'U' - Unknown RBridge nickname, 'n' - Not AF,
'*' - Success, Optional Tlv incomplete,
'I' - Interface not in forwarding state,
'S' - Service Tag nonexistent, 's' - Service Tag in suspended state,
'c' - Corrupted Data/Test
Sender handle: 4
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 3498 Rcvd on Eth1/47 fwd 2ms
! 320 Rcvd on Eth1/48 fwd 3ms
The following example shows how to specify FTag instead of tree.
Device(#) mtrace fabricpath ftag 1 vlan 10 repeat 1 verbose
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'D' - Destination Unreachable, 'X' - unknown return code,
'V' - VLAN nonexistent, 'v' - VLAN in suspended state,
'm' - malformed request, 'C' - Cross Connect Error,
'U' - Unknown RBridge nickname, 'n' - Not AF,
'*' - Success, Optional Tlv incomplete,
'I' - Interface not in forwarding state,
'S' - Service Tag nonexistent, 's' - Service Tag in suspended state,
'c' - Corrupted Data/Test
Sender handle: 6
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime DownSwitchId Intf State
============================================================================
! 3498 Rcvd on Eth1/47 fwd 2ms
! 320 Rcvd on Eth1/48 fwd 3ms
The following example shows how to specify a pair of trees.
Device(#) mtrace fabricpath ip dst 224.1.1.1 src 10.1.1.1 vlan 10 repeat 1
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'D' - Destination Unreachable, 'X' - unknown return code,
'V' - VLAN nonexistent, 'v' - VLAN in suspended state,
'm' - malformed request, 'C' - Cross Connect Error,
'U' - Unknown RBridge nickname, 'n' - Not AF,
'*' - Success, Optional Tlv incomplete,
'I' - Interface not in forwarding state,
'S' - Service Tag nonexistent, 's' - Service Tag in suspended state,
'c' - Corrupted Data/Test
Sender handle: 7
FabricPath mtrace for multicast ftag 1, vlan 10
Code SwitchId Interface State TotalTime
==================================================
! 320 Rcvd on Eth1/48 fwd 2ms