Advanced Features - Extreme Networks

Advanced Features
ExtremeXOS 15.5 User Guide
120936-00 Rev. 2
Published June 2014
Copyright © 2011–2014 All rights reserved.
Legal Notice
Extreme Networks, Inc., on behalf of or through its wholly-owned subsidiary, Enterasys Networks,
Inc., reserves the right to make changes in specifications and other information contained in this
document and its website without prior notice. The reader should in all cases consult
representatives of Extreme Networks to determine whether any such changes have been made.
The hardware, firmware, software or any specifications described or referred to in this document
are subject to change without notice.
Trademarks
Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of
Extreme Networks, Inc. in the United States and/or other countries.
All other names (including any product names) mentioned in this document are the property of
their respective owners and may be trademarks or registered trademarks of their respective
companies/owners.
For additional information on Extreme Networks trademarks, please see:
www.extremenetworks.com/company/legal/trademarks/
Support
For product support, including documentation, visit: www.extremenetworks.com/support/
For information, contact:
Extreme Networks, Inc.
145 Rio Robles
San Jose, California 95134
USA
Table of Contents
Preface.........................................................................................................................................9
Conventions.............................................................................................................................................................................9
Related Publications.......................................................................................................................................................... 10
Providing Feedback to Us................................................................................................................................................ 11
Navigating the ExtremeXOS User Guide..........................................................................................................................12
Chapter 1: TRILL........................................................................................................................13
Overview..................................................................................................................................................................................13
TRILL Capabilities................................................................................................................................................................14
TRILL Data Center Solution............................................................................................................................................16
Data Path Packet Forwarding......................................................................................................................................23
TRILL Control Plane Protocol.......................................................................................................................................27
TRILL Network Configuration Example.................................................................................................................. 36
Restrictions and Limitations......................................................................................................................................... 39
Configuring TRILL............................................................................................................................................................. 40
Chapter 2: OpenFlow.............................................................................................................. 43
OpenFlow Overview.........................................................................................................................................................43
Provisioning Flows with FDB Entries....................................................................................................................... 50
Chapter 3: AVB.........................................................................................................................58
Overview.................................................................................................................................................................................58
AVB Feature Pack License............................................................................................................................................ 59
Configuring and Managing AVB................................................................................................................................. 59
Displaying AVB Information...........................................................................................................................................61
Chapter 4: OAM........................................................................................................................67
CFM........................................................................................................................................................................................... 67
Y.1731--Compliant Performance Monitoring..........................................................................................................79
Y.1731 MIB Support.............................................................................................................................................................88
EFM OAM--Unidirectional Link Fault Management.......................................................................................... 89
Bidirectional Forwarding Detection (BFD).............................................................................................................91
Chapter 5: Data Center Solutions..........................................................................................96
Data Center Overview..................................................................................................................................................... 96
Managing the DCBX Feature...................................................................................................................................... 105
Managing the XNV Feature, VM Tracking............................................................................................................107
Managing Direct Attach to Support VEPA.......................................................................................................... 127
Managing the FIP Snooping Feature.......................................................................................................................127
Chapter 6: Advanced Feature Commands......................................................................... 130
clear counters bfd............................................................................................................................................................ 136
clear counters cfm segment all frame-delay.......................................................................................................136
clear counters cfm segment all frame-loss..........................................................................................................139
clear counters cfm segment all..................................................................................................................................142
clear counters cfm segment frame-delay............................................................................................................ 145
clear counters cfm segment frame-loss mep.....................................................................................................146
clear counters cfm segment frame-loss................................................................................................................148
clear counters cfm segment <segment_name>................................................................................................150
clear ethernet oam counters....................................................................................................................................... 152
Advanced Features
3
Table of Contents
show vm-tracking repository......................................................................................................................................152
clear msrp counters......................................................................................................................................................... 153
clear mvrp counters........................................................................................................................................................ 154
clear network-clock gptp counters..........................................................................................................................155
clear openflow counters................................................................................................................................................156
clear trill counters............................................................................................................................................................. 157
configure bfd vlan authentication............................................................................................................................ 158
configure bfd vlan............................................................................................................................................................ 159
configure cfm domain add association integer.................................................................................................160
configure cfm domain add association string..................................................................................................... 161
configure cfm domain add association vlan-id..................................................................................................162
configure cfm domain add association vpn-id oui index..............................................................................163
configure cfm domain association add remote-mep..................................................................................... 164
configure cfm domain association add..................................................................................................................165
configure cfm domain association delete remote-mep................................................................................ 166
configure cfm domain association delete.............................................................................................................167
configure cfm domain association destination-mac-type........................................................................... 168
configure cfm domain association end-point add group.............................................................................169
configure cfm domain association end-point delete group........................................................................170
configure cfm domain association end-point transmit-interval................................................................. 171
configure cfm domain association ports end-point ccm.............................................................................. 172
configure cfm domain association ports end-point mepid..........................................................................173
configure cfm domain association ports end-point sender-id-ipaddress............................................ 174
configure cfm domain association ports end-point........................................................................................ 176
configure cfm domain association remote-mep mac-address.................................................................. 176
configure cfm domain delete association.............................................................................................................177
configure cfm domain md-level.................................................................................................................................178
configure cfm group add rmep................................................................................................................................. 179
configure cfm group delete rmep............................................................................................................................180
configure cfm segment add domain association............................................................................................. 180
configure cfm segment delete domain association..........................................................................................181
configure cfm segment dot1p.....................................................................................................................................182
configure cfm segment frame-delay dot1p..........................................................................................................183
configure cfm segment frame-delay window.................................................................................................... 184
configure cfm segment frame-delay/frame-loss transmit interval..........................................................185
configure cfm segment frame-loss consecutive...............................................................................................186
configure cfm segment frame-loss dot1p.............................................................................................................186
configure cfm segment frame-loss mep............................................................................................................... 187
configure cfm segment frame-loss ses-threshold............................................................................................188
configure cfm segment frame-loss window........................................................................................................189
configure cfm segment threshold............................................................................................................................190
configure cfm segment timeout.................................................................................................................................191
configure cfm segment transmit-interval............................................................................................................. 192
configure cfm segment window............................................................................................................................... 193
configure fip snooping add fcf.................................................................................................................................. 194
configure fip snooping add vlan............................................................................................................................... 195
configure fip snooping delete fcf............................................................................................................................. 196
configure fip snooping delete vlan.......................................................................................................................... 197
configure fip snooping fcf-update........................................................................................................................... 199
Advanced Features
4
Table of Contents
configure fip snooping fcmap.................................................................................................................................. 200
configure fip snooping port location...................................................................................................................... 201
configure lldp ports dcbx add application......................................................................................................... 203
configure lldp ports dcbx delete application.................................................................................................... 204
configure lldp ports vendor-specific dcbx......................................................................................................... 205
configure mrp ports timers........................................................................................................................................ 206
configure msrp latency-max-frame-size............................................................................................................. 208
configure msrp ports sr-pvid.................................................................................................................................... 209
configure msrp ports traffic-class delta-bandwidth....................................................................................... 210
configure msrp timers first-value-change-recovery.........................................................................................211
configure mvrp stpd........................................................................................................................................................212
configure mvrp tag ports registration .................................................................................................................. 213
configure mvrp tag ports transmit.......................................................................................................................... 214
configure mvrp vlan auto-creation.......................................................................................................................... 215
configure mvrp vlan registration ............................................................................................................................. 216
configure network-clock gptp default-set........................................................................................................... 217
configure network-clock gptp ports announce.................................................................................................218
configure network-clock gptp ports peer-delay...............................................................................................219
configure network-clock gptp ports sync ...........................................................................................................221
configure openflow controller ..................................................................................................................................222
configure port reflective-relay.................................................................................................................................. 224
configure snmp traps batch-delay bfd................................................................................................................. 224
configure trill add access tag.....................................................................................................................................225
configure trill add network vlan................................................................................................................................227
configure trill appointed-forwarder........................................................................................................................228
configure trill delete access tag............................................................................................................................... 230
configure trill delete network vlan............................................................................................................................231
configure trill designated-vlan...................................................................................................................................232
configure trill inhibit-time............................................................................................................................................ 233
configure trill mtu probe fail-count........................................................................................................................ 234
configure trill mtu probe.............................................................................................................................................. 235
configure trill mtu size...................................................................................................................................................236
configure trill nickname................................................................................................................................................ 237
configure trill ports protocol......................................................................................................................................238
configure trill ports......................................................................................................................................................... 239
configure trill pseudonode......................................................................................................................................... 240
configure trill system-id.................................................................................................................................................241
configure trill timers csnp............................................................................................................................................243
configure trill timers hello........................................................................................................................................... 244
configure trill timers lsp................................................................................................................................................245
configure trill timers spf backoff-delay................................................................................................................ 246
configure trill timers spf............................................................................................................................................... 247
configure trill tree prune vlan.................................................................................................................................... 248
configure vlan dynamic-vlan uplink-ports.......................................................................................................... 249
configure vm-tracking authentication database-order................................................................................250
configure vm-tracking blackhole.............................................................................................................................. 251
configure vm-tracking local-vm............................................................................................................................... 252
configure vm-tracking nms timeout.......................................................................................................................253
configure vm-tracking nms........................................................................................................................................ 254
Advanced Features
5
Table of Contents
configure vm-tracking repository............................................................................................................................255
configure vm-tracking timers.................................................................................................................................... 256
configure vm-tracking vpp add................................................................................................................................257
configure vm-tracking vpp counters..................................................................................................................... 258
configure vm-tracking vpp delete...........................................................................................................................259
configure vm-tracking vpp vlan-tag......................................................................................................................260
create cfm domain dns md-level.............................................................................................................................. 261
create cfm domain mac md-level............................................................................................................................262
create cfm domain string md-level.........................................................................................................................263
create cfm segment destination.............................................................................................................................. 264
create trill nickname....................................................................................................................................................... 265
create vm-tracking local-vm...................................................................................................................................... 267
create vm-tracking vpp................................................................................................................................................ 268
debug openflow show flows......................................................................................................................................269
debug openflow............................................................................................................................................................... 270
delete cfm domain............................................................................................................................................................271
delete cfm segment........................................................................................................................................................ 272
delete trill nickname........................................................................................................................................................272
delete vm-tracking local-vm...................................................................................................................................... 273
delete vm-tracking vpp................................................................................................................................................ 274
disable avb ports..............................................................................................................................................................275
disable avb.......................................................................................................................................................................... 276
disable cfm segment frame-delay measurement............................................................................................ 277
disable cfm segment frame-loss measurement mep.....................................................................................278
disable ethernet oam ports link-fault-management.......................................................................................279
disable fip snooping....................................................................................................................................................... 279
disable msrp........................................................................................................................................................................ 281
disable mvrp ports........................................................................................................................................................... 281
disable mvrp.......................................................................................................................................................................282
disable network-clock gptp ports........................................................................................................................... 283
disable network-clock gptp....................................................................................................................................... 284
disable openflow vlan....................................................................................................................................................284
disable openflow.............................................................................................................................................................. 285
disable snmp traps bfd................................................................................................................................................. 286
disable trill........................................................................................................................................................................... 287
disable vm-tracking dynamic-vlan ports............................................................................................................. 288
disable vm-tracking ports........................................................................................................................................... 289
disable vm-tracking........................................................................................................................................................ 289
disable msrp ports.......................................................................................................................................................... 290
enable avb ports................................................................................................................................................................291
enable avb........................................................................................................................................................................... 292
enable cfm segment frame-delay measurement............................................................................................. 293
enable cfm segment frame-loss measurement mep..................................................................................... 294
enable ethernet oam ports link-fault-management....................................................................................... 295
enable fip snooping........................................................................................................................................................ 296
enable msrp ports........................................................................................................................................................... 297
enable msrp........................................................................................................................................................................298
enable mvrp ports...........................................................................................................................................................299
enable mvrp.......................................................................................................................................................................300
Advanced Features
6
Table of Contents
enable network-clock gptp ports.............................................................................................................................301
enable network-clock gptp......................................................................................................................................... 301
enable openflow vlan.................................................................................................................................................... 302
enable openflow.............................................................................................................................................................. 303
enable snmp traps bfd..................................................................................................................................................304
enable trill............................................................................................................................................................................305
enable vm-tracking dynamic-vlan ports..............................................................................................................306
enable vm-tracking ports............................................................................................................................................306
enable vm-tracking.........................................................................................................................................................307
enable/disable bfd vlan................................................................................................................................................308
ping mac port....................................................................................................................................................................309
ping trill..................................................................................................................................................................................310
run vm-tracking repository........................................................................................................................................... 311
show avb............................................................................................................................................................................... 312
show bfd counters............................................................................................................................................................313
show bfd session client..................................................................................................................................................314
show bfd session counters vr all............................................................................................................................... 315
show bfd session detail vr all...................................................................................................................................... 316
show bfd session vr all................................................................................................................................................... 318
show bfd vlan counters................................................................................................................................................. 319
show bfd vlan.................................................................................................................................................................... 320
show bfd................................................................................................................................................................................321
show cfm detail.................................................................................................................................................................322
show cfm groups............................................................................................................................................................. 324
show cfm segment frame-delay statistics.......................................................................................................... 328
show cfm segment frame-delay.............................................................................................................................. 330
show cfm segment frame-delay/frame-loss mep id..................................................................................... 330
show cfm segment frame-loss statistics..............................................................................................................333
show cfm segment frame-loss..................................................................................................................................334
show cfm segment mep...............................................................................................................................................336
show cfm segment..........................................................................................................................................................338
show cfm.............................................................................................................................................................................340
show ethernet oam.........................................................................................................................................................343
show fip snooping access-list................................................................................................................................... 345
show fip snooping counters.......................................................................................................................................347
show fip snooping enode............................................................................................................................................ 349
show fip snooping fcf....................................................................................................................................................350
show fip snooping virtual-link.....................................................................................................................................351
show fip snooping vlan................................................................................................................................................. 353
show lldp dcbx..................................................................................................................................................................354
show mrp ports................................................................................................................................................................360
show msrp listeners........................................................................................................................................................362
show msrp ports bandwidth......................................................................................................................................363
show msrp ports counters..........................................................................................................................................364
show msrp ports.............................................................................................................................................................. 366
show msrp streams........................................................................................................................................................ 368
show msrp talkers.............................................................................................................................................................371
show msrp........................................................................................................................................................................... 372
show mvrp ports counters.......................................................................................................................................... 373
Advanced Features
7
Table of Contents
show mvrp tag.................................................................................................................................................................. 375
show mvrp.......................................................................................................................................................................... 376
show network-clock gptp ports............................................................................................................................... 377
show network-clock gptp...........................................................................................................................................380
show openflow controller............................................................................................................................................382
show openflow flows..................................................................................................................................................... 383
show openflow vlan....................................................................................................................................................... 384
show openflow..................................................................................................................................................................385
show snmp traps bfd.....................................................................................................................................................386
show trill distribution-tree........................................................................................................................................... 387
show trill lsdb.....................................................................................................................................................................388
show trill neighbor.......................................................................................................................................................... 389
show trill ports....................................................................................................................................................................391
show trill rbridges............................................................................................................................................................392
show trill...............................................................................................................................................................................393
show vlan dynamic-vlan...............................................................................................................................................395
show vm-tracking local-vm........................................................................................................................................396
show vm-tracking network-vm................................................................................................................................ 397
show vm-tracking nms................................................................................................................................................. 398
show vm-tracking port................................................................................................................................................. 399
show vm-tracking repository................................................................................................................................... 400
show vm-tracking vpp...................................................................................................................................................401
show vm-tracking........................................................................................................................................................... 403
traceroute mac port...................................................................................................................................................... 404
traceroute trill................................................................................................................................................................... 406
unconfigure avb............................................................................................................................................................... 407
unconfigure bfd vlan..................................................................................................................................................... 408
unconfigure cfm domain association end-point transmit-interval.........................................................409
unconfigure mrp ports timers....................................................................................................................................410
unconfigure msrp...............................................................................................................................................................411
unconfigure mvrp stpd.................................................................................................................................................. 412
unconfigure mvrp tag.....................................................................................................................................................413
unconfigure mvrp.............................................................................................................................................................414
unconfigure network-clock gptp ports................................................................................................................. 415
unconfigure openflow controller ............................................................................................................................. 416
unconfigure vm-tracking local-vm...........................................................................................................................416
unconfigure vm-tracking nms.................................................................................................................................... 417
unconfigure vm-tracking repository....................................................................................................................... 418
unconfigure vm-tracking vpp vlan-tag..................................................................................................................419
unconfigure vm-tracking vpp................................................................................................................................... 420
Advanced Features
8
Preface
Conventions
This section discusses the conventions used in this guide.
Text Conventions
The following tables list text conventions that are used throughout this guide.
Table 1: Notice Icons
Icon
Notice Type
Alerts you to...
Note
Important features or instructions.
Caution
Risk of personal injury, system damage, or loss of data.
Warning
Risk of severe personal injury.
New
This command or section is new for this release.
Table 2: Text Conventions
Convention
Screen displays
Description
This typeface indicates command syntax, or represents information as it appears on
the screen.
The words enter and
type
When you see the word “enter” in this guide, you must type something, and then press
the Return or Enter key. Do not press the Return or Enter key when an instruction
simply says “type.”
[Key] names
Key names are written with brackets, such as [Return] or [Esc]. If you must press two
or more keys simultaneously, the key names are linked with a plus sign (+). Example:
Press [Ctrl]+[Alt]+[Del]
Words in italicized type
Italics emphasize a point or denote new terms at the place where they are defined in
the text. Italics are also used when referring to publication titles.
Advanced Features
9
Preface
Platform-Dependent Conventions
Unless otherwise noted, all information applies to all platforms supported by ExtremeXOS software,
which are the following:
•
•
•
•
•
BlackDiamond® X8 series switch
BlackDiamond 8800 series switches
Cell Site Routers (E4G-200 and E4G-400)
Summit® family switches
SummitStack™
When a feature or feature implementation applies to specific platforms, the specific platform is noted in
the heading for the section describing that implementation in the ExtremeXOS command
documentation. In many cases, although the command is available on all platforms, each platform uses
specific keywords. These keywords specific to each platform are shown in the Syntax Description and
discussed in the Usage Guidelines.
Terminology
When features, functionality, or operation is specific to a switch family, the family name is used.
Explanations about features and operations that are the same across all product families simply refer to
the product as the “switch.”
Related Publications
Documentation for Extreme Networks products is available at: www.extremenetworks.com. The
following is a list of related publications currently available:
•
•
•
•
•
ExtremeXOS User Guide
ExtremeXOS Hardware and Software Compatibility Matrix
ExtremeXOS Legacy CLI Quick Reference Guide
ExtremeXOS ScreenPlay User Guide
Using AVB with Extreme Switches
•
•
•
•
BlackDiamond 8800 Series Switches Hardware Installation Guide
BlackDiamond X8 Switch Hardware Installation Guide
Extreme Networks Pluggable Interface Installation Guide
Summit Family Switches Hardware Installation Guide
•
•
Ridgeline Installation and Upgrade Guide
Ridgeline Reference Guide
•
•
SDN OpenFlow Implementation Guide
SDN OpenStack Install Guide
Some ExtremeXOS software files have been licensed under certain open source licenses. Information is
available at: www.extremenetworks.com/services/osl-exos.aspx
Advanced Features
10
Preface
Providing Feedback to Us
We are always striving to improve our documentation and help you work better, so we want to hear
from you! We welcome all feedback but especially want to know about:
• Content errors or confusing or conflicting information.
• Ideas for improvements to our documentation so you can find the information you need faster.
• Broken links or usability issues.
If you would like to provide feedback to the Extreme Networks Information Development team about
this document, please contact us using our short online feedback form. You can also email us directly at
[email protected].
Advanced Features
11
Navigating the ExtremeXOS User Guide
This guide consists of the following eight volumes that contain feature descriptions, conceptual
material, configuration details, command references and examples:
• Basic Switch Operation
• Policies and Security
• Layer 2 Basics
• Layer 2 Protocols
• Layer 3 Basics
• Layer 3 Unicast Protocols
• Multicast
• Advanced Features
Advanced Features
12
1 TRILL
Overview
TRILL Capabilities
TRILL Data Center Solution
Data Path Packet Forwarding
TRILL Control Plane Protocol
TRILL Network Configuration Example
Restrictions and Limitations
Configuring TRILL
This chapter provides information about TRILL functionality for ExtremeXOS. TRILL allows for
improved scaling of data center servers and virtual machine interconnections by combining bridged
networks with network topology control and routing management. Information regarding TRILL
capabilities, protocols, limitations, and solution implementation is included in this chapter.
Overview
TRILL is a packet encapsulation standard specifically designed to meet the requirements of the data
center (DC). It is similar to Service Provider Bridging (SPB) and Virtual Private LAN Service (VPLS), but
is different in few key areas. Like MPLS, TRILL is considered a Layer 2½ protocol. From the end station
device perspective, the network looks like a large, flat Layer 2 network. Within the network, bridge
traffic is transported across the network using Layer 3 route forwarding techniques. Similar to SPB and
VPLS, the TRILL packet payload includes the entire Ethernet packet starting with the destination MAC
address (DA) field in the Ethernet header, through the Ethernet PDU (but does not include the FCS).
TRILL also requires edge TRILL networking devices, hereto referred to as RBridges, to learn both local
MAC address port/VLAN bindings, and remote network MAC address TRILL link/VLAN bindings
associated with egress RBridges.
Note
Availability of TRILL is controlled through the purchase of the TRILL Feature Pack License.
Supported Platforms
TRILL is supported on the Extreme Networks BlackDiamond-X series, Summit X670 and X770 series
switches. In a Summit Stack, all the switches must be Summit X670s or X770s. If one of the stack
members is not a Summit X670 or X770, TRILL is not supported on the stack.
Support Interfaces
TRILL is supported on all Ethernet interfaces for the supported platforms. TRILL can be enabled on any
VLAN and Access VLANs may be configured for all or a portion of the 4K VLAN ID space from 1
Advanced Features
13
TRILL
through 4094 (0xFFE). Network TRILL interfaces are sometimes referred to as tunnel interfaces,
though TRILL does not create tunnels based on the accepted networking definition of a tunnel.
TRILL does not provide point-to-point connections; traffic is free to take multiple paths based on the
calculated path cost. For known unicast traffic, TRILL does provide a single ingress and single egress
interface into and out of a non-native 802.3 Ethernet network. For this reason, you may see references
to TRILL tunnels. In this context, the meaning only implies that a TRILL packet is carrying a native
Ethernet packet from an ingress point to an egress point in the TRILL network. The path the packet
takes is based on traditional routing topology algorithms.
The TRILL protocol treats each port in a VLAN as a distinctly separate interface (except when the ports
are aggregated as an aggregation group). Thus, there could be multiple RBridges connected via pointto-point links to a single RBridge on VLAN 1. Each port to which another RBridge is connected is
considered an adjacency on a non-shared link. This is an important distinction between TRILL and other
routing protocols that use the IP interface to differentiate interfaces. An IP interface may have multiple
ports that are members of a VLAN, and thus an IP interface. Since TRILL does not use IP addresses, the
TRILL topology is port based and the VLAN tag is merely used to provide backwards compatibility so
that standard 802.1Q bridges can co-exist with RBridges.
TRILL Capabilities
TRILL provides a flat core network that is easily scalable, manageable, configurable, and auto
discoverable, that is resilient and provides efficient link usage. TRILL borrows from Layer 2 switching
and Layer 3 routing, and concepts from MAC-in-MAC Bridging and MPLS-VPLS tunneling. TRILL uses
the link state path computation to calculate the best path route based on link cost to every node in the
network. TRILL functionality consists of the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Perform RBridge TRILL packet forwarding function.
Support TRILL and native Ethernet forwarding simultaneously on the same port.
Provide 4K VLAN connectivity across backbone.
Support up to eight ECMP next hop RBridge load share entries
TTL hop-count validation.
Ability to verify link MTU size using MTU probes.
Auto creation of RBridge and Distribution Tree nicknames.
Auto discovery of RBridges in the TRILL network.
Use of pseudonodes to simplify TRILL topologies on shared links.
Control plane support for broadcast and multicast traffic.
Support for one distribution tree.
Capability to prune VLANs nodes from distribution trees.
Ability to assign appointed forwarders for VLANs in a load sharing configuration.
Configurable TRILL protocol timers.
The following features are not supported in the initial ExtremeXOS TRILL release:
•
•
•
•
EASDI protocol
Fine Grain Labeling (FGL)
Active-Active AF status
MAC learn limiting of RBridge FDB entries
Advanced Features
14
TRILL
•
•
•
•
VLAN mapping a TRILL Access VLANs
Use of CFM and or BFD to protect TRILL links
L3 interfaces defined on Access VLANs
Multicast Prunning support is not available.
TRILL Interoperability with Layer 2 Protocols
TRILL Access VLANs are compatible with L2 switching protocols such as STP, EAPS, and ERPS for
some topologies. The CLI does prevent incompatible features from being configured on a TRILL
interface or VLAN, but does not prevent all unsupported networking configurations from being
configured. If a range of VLAN tags is specified and an incompatible feature is detected on a VLAN, the
command does not abort and continues onto the next sequential VLAN tag. Reference verified
solutions are also available from Extreme. Please contact your Extreme Sales Representative for
additional information.
The following protocol features cannot be configured on a TRILL Network VLAN.
• IP Forwarding
• IP Routing Protocols
• IP Multicast Protocols
• MPLS
• ESRP
• Ring Protocols (i.e., EAPS, ERPS)
• MLAG
• Private VLANs
• VLAN Translation
• VLAN Aggregation
• VMANs
• VPLS
• VRRP
• STP
• Customer Edge Ports (CEP)
• Multicast Snooping
• Any type of tunnel (e.g, GRE, IPv6-to-IPv4, IPv6-in-IPv4)
In general, if an L2 protocol (STP, EAPS, ERPS, etc.) is enabled on the TRILL access port, then the L2
protocol PDUs will not be tunneled through the TRILL network, but instead processed locally at the
ingress Rbridge. If a PDU is received for a protocol that is not enabled then it will be treated like data
and therefore tunneled through the TRILL network. STP is an exception as the TRILL protocol requires
the STP BPDU to always be processed at the access regardless of the STP admin state.
Enabling TRILL and MLAG on the same switch may cause temporary flooding. This limitation is present
even if MLAG VLANs and TRILL access/network VLANs are different.
LACP is another example that will always be processed and never tunneled as it has local(LAG)
significance only.
Advanced Features
15
TRILL
Protocols not supported by ExtremeXOS will be tunneled (just like a supported, but disabled protocol).
Examples: VTP is a protocol that ExtremeXOS does not support in 15.4.1.
Protocols such as STP, EAPS, ERPS, and ELRP can be configured on TRILL Access VLANs and will
function correctly in some network configurations. Although not specifically designed to support them,
VMAN packets can be carried over a TRILL network provided they are treated as basic Ethernet tagged
packets (packets use an ethertype of 0x8100 instead of 0x88a8).
TRILL Data Center Solution
Data center networks have a number of unique requirements, such as:
• High total network bandwidth capacity.
• Hyper-fast point-to-point link speeds with low latency.
• High number of high-speed access device (e.g., servers) network connections.
• Multiple paths to reach every access device.
• Flexibility to connect any device with any other set of devices.
• Broadcast domain control to minimize network storms.
TRILL running on the BlackDiamond X8 core switch and the Summit X670, or X770, top-of-rack switch
can solve these requirements. The following reference network diagram has been simplified. Typically
the top-of-rack Summit X670 switches have four or eight up-links into multiple core switches
(highlighted in magnified view at the bottom-right of the diagram). This reduces the number of hops
and end-to-end latency and also offers increased resiliency.
Advanced Features
16
TRILL
Figure 1: Quad-core Data Center Reference Network
The first three challenges are met by deploying the BlackDiamond X8 and Summit X670 with 10G, 40G,
and, in the future,100G Ethernet links in the DC. Multiple 40G links can be trunked together to form
160G or 320G core links. Each Summit X670 supports 48 front-panel 10G Ethernet links. Given the
typical dual Ethernet connected server configuration, each Summit X670 provides core network access
for 24 servers. Each BlackDiamond X8 supports 192 40G and 768 10G Ethernet ports. Scaling a fully
meshed network core is limited by the (Node)2 link requirement. This introduces topology challenges
that TRILL addresses.
Advanced Features
17
TRILL
A large flat Layer 2 network that allows any-to-any connectivity with lots of devices and high
interconnect speeds may be implemented with a single VLAN domain. To prevent loops, Layer 2
protocols must be introduced that limit network link usability. TRILL retains the benefits of Layer 2
networks and adds the capabilities of IP Routing. This includes maintaining and building a complete link
state network topology. TRILL also supports ECMP next-hop routing look up and packet forwarding
operation. Similar to ISIS and OSPF, TRILL uses a modified Hello Protocol to discover neighbors and
exchange capabilities information.
By combining the useful attributes of Layer 3 to the simplicity of Layer 2, TRILL addresses the Data
Center core requirements better than either Layer 2-only or Layer 3-only designed networks.
Figure 2: Shortest Path Forwarding Example
TRILL uses the link state path computation, known as the Dijkstra Algorithm, to calculate the best path
route based on link cost to every node in the network. Each node makes an independent decision on
where to send a packet based on the packet’s destination egress node. Given the quad-core network
layout shown above, interconnect links have been added and associated link costs are shown in the
figure above.
If a packet enters the network at node F and egresses the network at node H, the best path is F > G > H
with a cost of 16. If the packet enters the network at node F and egresses at node N, the best path is F >
I > K > N with a cost of 28. This means that multiple paths through the network are utilized.
Another advantage of using a link state algorithm to forward traffic is that multipath forwarding is also
possible. Multipath forwarding allows the ingress node to forward packets along multiple paths to
reach the destination as long as they are all considered to be the best path. Using the following
diagram as an example, traffic that ingresses node I and egresses node L can follow I > A > B > J > L or I
> K > C > D > L, since both have a link path cost of 42. The ingress node has two next-hop peers that
Advanced Features
18
TRILL
can reach the egress node and may choose either path to send the packet. Packet reordering must be
prevented, so the ingress node uses a hashing algorithm to select the next-hop peer. The hashing
algorithm operates on the encapsulated packet header so that individual flows always follow the same
path.
Figure 3: Edge ECMP Unicast Forwarding
As with IP Routing, each hop along the path performs its own next-hop look-up independent of the
previous hops. This means that at each hop along the path, there may be multiple paths that were not
available to the previous hops. This provides yet another level of load sharing not available to Layer 2
networks and as an aside, not supported in Service Provider Bridging (SPB). An example of this is
shown in the following diagram. The ingress node is M and the egress node is B. There is only one
shortest best path from M’s perspective to reach B, and that’s through the next-hop node of C. Once
the TRILL packet reaches C, C performs its own look up to reach B and finds that there are two equal
cost best paths: one through node A and the other through node D. C then performs a hash on the
encapsulated packet header to choose either the next hop node of A or D. Thus, some flows from M to
B take the path M->C->A->B and the some take the path M->C->D->B.
Advanced Features
19
TRILL
Figure 4: Intermediate Hop ECMP Unicast Forwarding
Note
With respect to ECMP TRILL forwarding, bi-directional packet flows may not take the same
path. This is an artifact of the hash algorithm operating on encapsulated packet headers that
are formatted differently and the specific hash algorithm implemented.
TRILL addresses the network scaling and data forwarding aspect of network access flexibility through a
few key concepts. When TRILL is deployed in conjunction with Data Center virtualization and VLAN
registration protocols, the network benefits of deploying VLANs can be realized while retaining the
plug-and-play network access flexibility of using a single VLAN. Within the TRILL core, TRILL network
VLANs are used to carry encapsulated access ethernet data traffic. The encapsulated packet’s IEEE
802.1Q tag is carried across the TRILL network, extending a VLAN across the TRILL network. The TRILL
packet's outer tag identifies the network VLAN and the encapsulated inner tag identifies the Access
VLAN.
Logically, the Data Center network can be considered to have two independent sets of 4K VLANs: one
set for the access devices and one set for the TRILL core network. Each TRILL node, or Route Bridge
(RBridge), has a configured set of Access VLAN IDs that it provides traffic forwarding. To maintain full
plug-and-play capability, the VLAN access list encompasses the entire 4K VLAN ID space. Native
Ethernet tagged traffic received on a VLAN with a VLAN ID that matches an ID in the access tag space
is encapsulated and forwarded across the TRILL network as shown in the following figure:
Advanced Features
20
TRILL
Figure 5: VLAN Interconnect Across TRILL Network
Extending Access VLANs across the TRILL core network means that there are potentially multiple
access points into the core. This multipoint topology requires multicast forwarding rules to deliver flood
packets to each access point. Layer 2 networks use MSTP to block ports such that one copy of each
flood packet reaches every node for every VLAN. This solution has a number of deficiencies, including
maintaining multiple spanning trees and requiring every flood packet on a VLAN to take the same path.
TRILL uses multipath distribution trees, but only one tree is required to support all 4K Access VLANs.
Additional TRILL multipath distribution trees can be deployed to improve flood packet link utilization in
the core.
Note
Although TRILL supports this, multiple distribution trees are not supported in the initial
release of TRILL.
Optionally, each RBridge can restrict forwarding of packets with VLAN tags to only those tree
adjacencies that have downstream matching Access VLANs. This type of packet filtering eliminates
unnecessary packet forwarding with in the TRILL core. Distribution trees are bi-directional and can be
rooted at any node. This is referred to as VLAN pruning. The previous figure shows a TRILL network
with VLAN X attached at RBridge nodes E, F, H, L, and M.
Advanced Features
21
TRILL
One potential general distribution tree is shown in the following figure. Distribution trees may be
rooted at multiple RBridges. VLAN X access RBridges are colored green. In the example below, RBridge
F is configured with the highest priority distribution tree and thus is used by all the RBridges in the
TRILL network to forward flood and multicast traffic. All RBridges in the network must maintain the
same topological view and be able to calculate the same distribution trees. For VLAN X, RBridges F, K,
G, and L are not required to forward traffic to some or all of the distribution tree adjacencies. This
effectively prunes the distribution tree and reduces packet replication and unnecessary traffic
forwarding. Pruned RBridge nodes that will not receive VLAN X traffic are colored orange. If the
distribution tree pruning is not employed by RBridges, the RBridge leaves must still discard any
received traffic on VLAN X, provided no locally configured Access VLANs for VLAN X.
Figure 6: Logical Forwarding Tree Diagram
TRILL adds load sharing improvements on the access interfaces. VLANs may optionally be connected
to multiple RBridges, as shown in the previous figure. The Designated RBridge determines which node
provides forwarding access for each attached VLAN. RBridges providing packet forwarding are
referred to as the appointed forwarders. The RBridge appointed forwarder is specified for each VLAN
by the Designated RBridge. Various VLAN distribution algorithms can be employed. The result is that
multiple RBridges can provide designated forwarding for a mutually exclusive set of shared Access
VLANs. If one of the RBridges fails, one of the remaining active RBridges assumes the forwarding role
as directed by the Designated RBridge as shown below:
Advanced Features
22
TRILL
Figure 7: RBridge Appointed Forwarder for Access VLAN
Data Path Packet Forwarding
To achieve the data encapsulation forwarding functionality, TRILL defines a new Ethertype and TRILL
packet header that fully encapsulates the access VLAN Ethernet packet. The format of the TRILL
header is illustrated in the following figure:
Figure 8: Data Packet Header
V = TRILL Protocol Version (2-bits)
R = Reserved (2 bits)
M = Multi-destination (1 bit)
Op-Length = Options length (5 bits)
Hop Count = TRILL RBridges Traversed (6 bits)
Advanced Features
23
TRILL
RBridge Nickname = Network Unique RBridge ID (16 bits)
Unlike SPB, the outer MAC addresses representing RBridges along with the TRILL header is rebuilt with
each hop along the TRILL data path to the egress RBridge. The next hop RBridge is determined by
executing a lookup of the Egress RBridge Nickname in the TRILL packet header. The forwarding
process also differs from MPLS, since LSP forwarding labels (which have only local router significance)
are replaced by RBridge nicknames that have network wide significance. Even though the TRILL data
plane differs from both SPB and MPLS, this does not preclude TRILL data packets from being
encapsulated and transmitted over an SPB or MPLS network or vice versa.
Let’s take a quick look at how an Ethernet VLAN tagged packet would be transported across the TRILL
reference network shown in the following figure. First, let’s look at a packet transmit for a known
unicast destination.
Figure 9: Simple TRILL Reference Network
Unicast Packet Forwarding
The device PC is sending a known unicast packet to a server. The device formats the packet from
transmission with the following Ethernet header, illustrated in the following figure:
Figure 10: Native Ethernet Unicast Packet
RBridge A receives the packet and does a look up in its FDB table. The FDB table entry would have an
FDB Server MAC address, PC VLAN, and RBridge D nickname table entry and the FDB entry would
point to the next hop RBridge B’s MAC address. The RBridge outer MAC DA is set to the functional All-
Advanced Features
24
TRILL
RBridges-Multicast MAC address. Since RBridge A is an edge boundary RBridge, the received packet
from the PC is encapsulated with a TRILL header as follows. The ingress RBridge nickname is set to
RBridge A’s nickname and the egress RBridge nickname is set to RBridge D’s nickname.
Figure 11: TRILL Unicast Data Packet (RBridge A to RBridge B)
RBridge B receives the TRILL formatted data packet. Because the packet’s DA is RBridge B’s MAC
Address and has a TRILL Ethertype, RBridge B looks in the TRILL header to determine if the egress
RBridge Nickname in the TRILL header matches its local RBridge nickname. Since it does not match, it
merely does an RBridge nickname lookup for RBridge D and finds the next hop RBridge MAC address
(which happens to be RBridge D’s MAC address). RBridge B changes the RBridge SA to its MAC
address and sets the RBridge DA to that of RBridge D. It also decrements the hop count in the TRILL
header.
RBridge D receives the TRILL formatted packet and determines that the egress RBridge for the packet
is itself. Since the RBridge is located at the TRILL egress boundary, RBridge D must decapsulate the PC
data packet by removing the TRILL header and performs an L2 lookup of the Server DA located in the
encapsulated Ethernet packet header. The Server DA lookup returns the egress port for the Server and
the Ethernet packet is sent.
Broadcast and Unknown Unicast Packet Forwarding
Flows that require flooding are handled similarly. Distribution trees can be optimized to minimize
unwanted packet forwarding. These control plane optimizations to reduce flooding are discussed in
more detail in Section 4.1.15. If the PC doesn’t know the MAC address of the Server, the PC formats a
broadcast packet. In the case of IP, this would be an IP ARP request, but the type of packet is irrelevant
for the purpose of this example.
Figure 12: Native Ethernet Broadcast Packet
RBridge A receives the packet and determines that the packet is formatted as a broadcast packet.
RBridge A encapsulates the packet in a TRILL header and sets the M-bit in the TRILL header to ‘1’ to
indicate that encapsulated packet is a multicast packet. The selected egress RBridge nickname
represents a distribution tree and not specific egress RBridge. This instructs transit RBridges to flood
the packet along the calculated tree topology so that each egress RBridge receives one copy of the
packet. The ingress RBridge nickname is set to RBridge A’s nickname and the hop count value is
initialized to the configured maximum number of RBridge hops. The RBridge outer MAC DA is set to
the functional All-Bridges-Multicast MAC address.
Advanced Features
25
TRILL
Figure 13: TRILL Broadcast Packet from RBridge A
RBridge B receives the TRILL formatted packet and assumes that the egress RBridge nickname is a
distribution tree nickname and the packet must be flooded, as indicated by the ‘M’ bit in the TRILL
header. RBridge B must forward the packet to both RBridge C and RBridge D. RBridge B decrements
the hop count, updates the RBridge SA, and replicates the packet sending two copies, one to RBridge C
and one to RBridge D.
Figure 14: TRILL Broadcast Packet from RBridge B
RBridge C receives the TRILL data packet and decapsulates the packet and forwards the broadcast
packet onto its local VLAN. RBridge C also learns that the PC MAC Address is associated with the
nickname of RBridge A. Since the server doesn’t reside on the local VLAN of RBridge C, no response to
the broadcast packet is received. RBridge D performs the same forwarding action as RBridge C and
also learns that RBridge A (by examining the ingress nickname field in the TRILL header) is the egress
RBridge to reach PC MAC Address. Since the server is located on the local VLAN connected to RBridge
D, after receiving the broadcast packet, the server replies with a unicast response to the PC. RBridge D
forwards the unicast response back to the PC. Since RBridge D has now learned the egress RBridge for
the PC MAC address, the TRILL header ingress RBridge nickname is set to RBridge D and the egress
RBridge nickname is set to RBridge A. The TRILL header M-bit is set to zero, indicating that the
encapsulated packet is a Unicast Packet. The RBridge next hop lookup is executed to determine the
next-hop that reaches RBridge A’s nickname and the response is returned to the PC via RBridge B and
RBridge A.
TRILL Hop Count
The RBridge will not continue forwarding the TRILL frame on the TRILL network upon receiving a TRILL
frame with hop count value zero. However, it will decapsulate and forward it to the access even if the
hop count is zero, meaning it may terminate the tunnel. The hop count field in the TRILL header is
decremented prior to forwarding. The packet may traverse non-TRILL bridges too. Non-TRILL bridges
will not decrement the hop count field. The ingress RBridge must initialize the hop count to a value
larger than the number of hops needed to reach the destination. The maximum hop count value is 63.
Advanced Features
26
TRILL
Inner and Outer VLAN Tags
A TRILL packet contains an inner and outer VLAN Tag. The inner 802.1Q tag represents the native
Ethernet VLAN tag for the transport packet and must be present in the TRILL data packet. The inner
frame must always have a VLAN ID of 1-4094. This is required to properly prune forwarding trees and
reduce packet flooding. The outer 802.1Q tag represents the TRILL Designated VLAN and is determined
by the Designated RBridge (DRB). All TRILL control traffic and data traffic is transmitted over the TRILL
Designated VLAN, except for some TRILL Hello packets. The TRILL Designated VLAN Tag may or may
not appear in the Ethernet header of the packet on the wire. This is determined by the Ethernet port
configuration. By default, the priority bits in the outer 802.1Q tag should match the priority bits of the
inner 802.1Q tag. Remapping of VLAN IDs and 802.1Q priority bits is permitted and is a local RBridge
configuration option.
Header Options
A non-zero options length field in the TRILL header indicates the inclusion of TLV options in the data
plane packet. If the options length field is non-zero, the packet contains one or more options. The first
two bits indicate if the packet requires special processing. The first bit indicates a critical hop-by-hop
(CHbH) RBridge processing option is contained in the options data. The second bit indicates a critical
egress (CItE) RBridge processing option has been included by the ingress RBridge in the options data.
Since the initial release of TRILL for ExtremeXOS does not support any data plane options, if options
length field is non-zero and either of the first two bit flags in the options data are set, the packet is
discarded. If both the CHbH and CItE flags are zero, then the options field is skipped and the packet is
forwarded using the same logic as if no options field were present.
TRILL Control Plane Protocol
TRILL RBridge network topologies are constructed and managed using ISIS. ISIS was chosen because it
does not require IP and is easily extended using new TLVs for carrying TRILL-specific data elements.
There are a few TRILL specific protocol additions not covered by ISIS:
• TRILL Hello Protocol
• MTU Size Probe
• Ethernet Station Address Distribution Information (ESADI) Protocol
Although ISIS is used to distribute RBridge and TRILL bridge link information, TRILL’s use of ISIS is
distinctly separate from L3 ISIS. TRILL ISIS control protocol packets use a different L2-ISIS Ethertype
and different multicast destination address to exchange control plane information between RBridges as
compared to L3 ISIS. TRILL ISIS control protocol packets do not have a TRILL header.
All RBridges must participate in the TRILL protocol using a single Level 1 ISIS area using the fixed area
address 0.0.0.0. TRILL ISIS packets are never forwarded by an RBridge. All RBridges should be
configured to use the same VLAN ID, called the Designated TRILL VLAN. All TRILL ISIS packets are sent
over the Designated TRIILL VLAN except for some TRILL Hello packets.
Each RBridge is identified by its System ID, which defaults to its local MAC address. The System ID can
be configured to any 6-octet value. A zero octet is appended to the end of the System ID to form the
Advanced Features
27
TRILL
TRILL ISIS-ID. If the concatenated octet is non-zero, the TRILL ISIS-ID represents a TRILL pseudonode.
Pseudonodes are used by TRILL ISIS to identify separate TRILL links over a shared Ethernet segment.
RBridges announce themselves to other RBridges by sending Hellos. There are two types of RBridge
Hellos: one for P2P Ethernet links (P2P Hellos) and the other for shared Ethernet or bridged segments
(TRILL Hellos). All RBridges must support TRILL Hellos unless specifically configured to use P2P Hellos
on a per port basis. P2P links represent directly connected RBridges over a single Ethernet segment
and have no directly connected Ethernet end stations. Any received non-TRILL Ethernet data traffic on
a P2P link must never be encapsulated and forwarded over the TRILL network nor should native
Ethernet packets encapsulated in a TRILL header be decapsulated and transmitted on the Designated
VLAN.
The TRILL Hello protocol is used to determine the RBridge that is the Designated RBridge (DRB) on
each link based on configured priority and RBridge System ID. If there are multiple RBridges that share
the highest priority, the RBridge with the highest TRILL-ID becomes the DRB. If there are multiple links,
the DRB will be represented as an RBridge pseudonode. A DRB is selected for both TRILL and native
Ethernet links.
The Designated DRB has the following responsibilities:
• Determine VLAN ID to use for inter-RBridge communication.
• Appoint an RBridge as the appointed forwarder for each VLAN.
RBridges that are appointed forwarders for an Access VLAN are responsible for providing connectivity
for all connected devices on the VLAN:
• Implementing loop avoidance.
• Learning MAC addresses for local connected devices (tuple of port, VLAN, MAC Address).
• Learning MAC addresses for remote connected devices (tuple of egress RBridge, VLAN MAC
Address).
• Listening to STP BPDUs and reporting list of root bridges in its LSP.
• Sending TRILL Hello packets on designated VLANs.
• Sending Hellos on VLANS for which they are the appointed forwarder.
There are optional responsibilities that may also be performed by the RBridge appointed forwarder.
These optional operations include:
• Learning local MAC port bindings based on any registration or authentication protocol such as
802.1X.
• Observing native IGMP, MLD, and or MRD packets to learn the presence of multicast routers and
receivers.
• Listening for ESADI messages for learning TRILL RBridge MAC bindings.
• Advertising local RBridge MAC bindings in ESADI messages.
TRILL Hellos
TRILL Hellos are sent on all ports in a VLAN that have TRILL enabled and on all ports of a native
Ethernet VLAN that has a VLAN ID that is operationally an Access VLAN for the TRILL network. Each
RBridge learns and maintains an RBridge-VLAN-Port association in its neighbor table based on
received TRILL Hello packets. If multiple RBridges are attached to the same VLAN interface, TRILL
Advanced Features
28
TRILL
pseudonodes are used to simplify management of the link state database and each pseudonode is
implicitly mapped to a single RBridge that is connected to a single port in the VLAN.
TRILL Hellos sent on TRILL VLANs will have the access port (AC) flag set to zero. If there are only only
two TRILL ports on a link and they are configured as broadcast, then Hellos are sent with the Bypass
(BY) pseudonode flag set to one. If there are less than two ports on a broadcast link, then a
pseudonode is created. If multiple RBridges are detected on the port, subsequent TRILL Hellos are sent
with the BY flag cleared. TRILL Hellos sent on Access VLANs will have the AC flag set to one. This
instructs TRILL neighbors not to include this link in the TRILL link path and tree computations. A DRB is
elected on the Access VLAN RBridge links for the purpose of assigning appointed forwarding status to
each RBridge connected to the Access VLAN.
VLAN Mapping is not supported in the initial release, so the VLAN Mapping (VM) flag is always cleared.
If a TRILL Hello is received with the VM flag set, VLAN Pruning is operationally disabled.
Hello Protocol
The TRILL Hello Protocol is similar to ISIS LAN Hello Protocol with the following differences. Hello
packets are sent at the same interval as ISIS Hello packets and are formatted similarly, with the
following exceptions:
• TRILL Hello packets are not padded
• TRILL elects only one Designated Node per LAN
The TRILL Hello packet header is format is shown in the following figure:
Figure 15: TRILL Hello Packet Header
The TRILL Hello includes the following encoded information carried in the Multi-Topology Aware Port
Capabilities TLV (MT-PORT-CAP) and Special VLAN and Flags sub-TLV (VLAN-FLAG):
• VLAN ID of Designated VLAN
• Copy of VLAN ID used to send TRILL Hello
• 16-bit unique port ID of sending RBridge
• Sending RBridge’s nickname
• Bypass pseudonode flag (BY)
• VLAN mapping indicator flag (VM)
• Access port indicator flag; no TRILL data traffic (AC)
Advanced Features
29
TRILL
•
•
Appointed forwarder indicator flag (AF)
Sending port is a trunk port; no end-station access (TR)
Figure 16: TRILL Hello Port Capabilities TLV
RBridges that detect no other RBridges on a port must assume the role of the Designated RBridge and
be the appointed forwarder for all Forwarding VLANs. If an RBridge detects that the elected
Designated RBridge is no longer active, the remaining RBridges must re-elect a new Designated
RBridge or if no other RBridges are present, the last remaining RBridge must assume the role of the
Designated RBridge.
MTU Probe
RBridges must be able to determine the maximum MTU size supported by its neighbors on every link.
To determine this, there are two new TRILL messages that are used: MTU-Probe and MTU-Ack. Both
packets are always padded to the maximum MTU size supported by the sending RBridge. Sending of
the MTU-Probe is optional, but the successful reception of an MTU-Probe must always be
acknowledged. RBridges will advertise maximum MTU supported for the link in subsequent Hellos.
RBridges may also advertise the supported MTU size determined for each of its link in the LSP.
Note
This MTU discovery is only used for sizing the control plane messages, the data plane packet
size is independent of this.
Appointing RBridge VLAN Forwarding
Each RBridge has a configured (or dynamically registered) set of VLANs. In order to determine which
RBridge will be appointed the forwarder for each VLAN, each RBridge must advertise the set of VLANs
for which it is announcing (VLANs that have connected edge devices that are configured to forward
traffic over the TRILL network). It must also announce the Desired Designated VLAN, Designated
VLAN, and the set of forwarding VLANs (the set of VLANs for which the RBridge believes it is the
appointed forwarder). When multiple RBridges are connected to the same VLANs, it is up to the DRB
to decide which RBridge is the appointed forwarder. How this is accomplished is an implementation
decision.
Advanced Features
30
TRILL
Link State Protocol
TRILL uses ISIS to exchange link state and cost between all RBridges in the network. Each node
maintains the same link state database network representation. Like ISIS and OSPF, the Dijkstra's
Algorithm is used to determine the best path to the egress RBridge. Using the reference RBridge
network diagram in the following figure, the Link State Database representation is also shown. The
information stored in the Link State Database also allows each RBridge to calculate the same
distribution tree and eliminates the need to have a separate spanning tree.
Figure 17: Link Cost Network Example
1G = 20000 metric
10G = 2000 metric
40G = 500 metric
100G = 200 metric
(LAG metric) = (Metric of any active LAG member) / (number of port in LAG group, active or not)
This means that a LAG group of five 40G ports with one of the ports down is (LAG metric) = 500 / 5 =
100. However, if all the ports in the group are down then the metric is MAX value, 16777214.
Determining RBridge Nickname
The RBridge nickname is used to forward packets along the data path. Thus, every RBridge in the
network must have a unique nickname. The nickname can be configured but is not required to be
specified. The intent is to minimize required configuration, so RBridges must support being able to
generate their own nickname. The recommended process is for each RBridge to randomly select a
nickname, but the selection algorithm is a vendor implementation choice.
Advanced Features
31
TRILL
Once an RBridge selects a nickname, the RBridge must verify that the chosen nickname is not already
in-use. The RBridge accomplishes this by comparing its chosen nickname against the known
neighboring RBridges and with nicknames shared and maintained in the Link State DB. If the nickname
is a duplicate, the RBridge with lower priority nickname must choose another nickname. Configured
nicknames have higher priority than dynamically chosen nicknames. If duplicate nicknames are both
configured or both dynamically chosen, the nickname associated with the RBridge with highest priority
TRILL-ID is used (based on the most significant bit).
Pseudonodes
RBridge’s are typically represented as a single node. An RBridge will use pseudonodes when there are
multiple RBridges on the same link (i.e., shared Ethernet segment). Representing each link would
require n(n-1) link database entries. Instead, each link is represented as a P2P link between
pseudonodes, reducing the number of entries to (n-1)*2 entries. This improves database scaling by
converting an N2 scaling problem into a linear scaling problem. Each RBridge can have up to 254
pseudonodes and is identified in the TRILL-ID by the appended octet to the RBridge MAC address.
Examining the RBridge topology shown below demonstrates how the use of pseudonodes reduces the
number of links state database entries. If a pseudonode was not introduced, there would be 12
database entries. By introducing a pseudonode, as represented by the last octet value of 17, the number
of database entries is reduced to six.
Figure 18: Pseudonode Link Cost Network Example
Neighbor Adjacencies
Neighbor adjacencies are negotiated using the TRILL Hello protocol. If the link is point-to-point, the BY
flag should be set to bypass pseudonode logic. Each RBridge sends TRILL Hellos on all TRILL
configured VLAN ports and TRILL Access VLAN ports for which it believes it is the DRB. TRILL Hellos
Advanced Features
32
TRILL
sent on all VLANs must be sent with the same MAC address, priority, desired Designated VLAN, and
Port ID. If another RBridge is detected on the port, the RBridges progress through the following states
as shown in the following figure, until the adjacency is established.
Figure 19: Neighbor Adjacency States
Once the adjacency has been established, the RBridges in the adjacency table negotiate which RBridge
is the Designed RBridge. The Designated RBridge is the RBridge with the highest priority assumes the
DRB role. If there is a priority tie, then the System ID (based on the MSB) breaks the tie. The suspension
timer is used as a hold timer to allow other potential RBridges to advertise themselves on the link. Once
the suspension timer expires, and if there is no higher priority RBridges on the link, then the local
RBridge assumes the role of DRB. If a higher priority RBridge is seen, then the RBridge does not
assume the DRB role. If at any time later, a higher priority RBridge is seen and the local RBridge is the
DRB, then the local RBridge returns to Suspend state. If a Hello timeout occurs with the elected DRB
and the local RBridge is the now the highest priority RBridge, then the local RBridge assumes the role
of DRB.
Advanced Features
33
TRILL
Figure 20: RBridge Role States
Equal Cost Multipath
Equal Cost Multipath (ECMP) can be formed across a TRILL network, allowing for improved network
utilization and load sharing. If there are multiple best cost paths to reach the egress RBridge that are
equal, the ingress RBridge will have multiple next-hop RBridge entries that can be used to reach the
egress RBridge. In the example below, RBridge E has two equal-cost best paths for reaching RBridge F.
One is through the next-hop RBridge B and the other through RBridge A. Known destination unicast
packets can be sent along either path. Flows must always take the same path to prevent packets from
being received out-of-order. This accomplished by implementing a hashing algorithm against the
encapsulated packet header to choose one of the two potential RBridge next hops. An example is
shown below:
Advanced Features
34
TRILL
Figure 21: ECMP TRILL Link Cost Network Example
Flooding/Multicast Trees
TRILL networks require a minimum of one distribution tree for the purpose of flooding broadcast,
unknown unicast, and multicast traffic so that each egress RBridge receives one copy of the packet.
RBridge trees are bi-directional. All RBridges in the TRILL network must know:
• How many trees to compute.
• Which trees to compute.
• What the nickname (16-bit number) is for each tree.
• Which trees each ingress bridge might choose.
At a minimum, each RBridge will request one tree be computed with itself as the root (default
configuration). Since all RBridges in the network must use the same set of distribution trees to forward
flood and multicast traffic and there are a limited number of trees that can be reasonably supported
(due to computational load on the CPU), all of the RBridges compute the number of trees supported by
the RBridge advertising the minimum number of supported trees and which trees computed are
determined by the distribution tree priority.
Distribution tree nicknames may be configured or auto-generated. Configured distribution tree
nicknames always have priority over auto-generated nicknames. So as to minimize nickname collisions,
RBridges attempt to reuse auto generated nicknames across system restarts. If multiple distribution
trees are maintained within the TRILL network, by default the ingress RBridge forwards flood traffic to
the tree whose root is least cost from itself.
The figure below shows how trees are determined and used. In the network example, all of the
RBridges advertise the number of trees to compute is four. They also advertise the number of trees to
Advanced Features
35
TRILL
use as two. Each RBridge also advertises that it wants all of the other RBridges to compute a tree with
itself as the root. Thus, the total number of potential trees is six. The tree priorities are set in the
following order from highest to lowest priority: B, D, A, C, E, and then F. Thus, all RBridges compute
four trees with an RBridge root of B, D, A, and C. But all RBridges will forward using only the tree
rooted at RBridge B or D. If RBridge E needed to flood a packet, it would choose the distribution tree
rooted at RBridge B’s nickname as the egress RBridge nickname. Similarly, RBridge A would also flood
packets using the tree rooted at RBridge B. RBridge C on the other hand would choose the tree rooted
at RBridge D.
Figure 22: Multiple TRILL Distribution Trees
Trees are bidirectional and transit nodes must only forward to next-hop RBridges that are represented
in the tree. except for the RBridge from which the packet was received. Reverse Path Forwarding is
recommended as a loop avoidance mechanism and to provide network security from spoofing attacks.
Tree Pruning Optimization
RBridges may prune trees to reduce the amount of unneeded flood or multicast traffic. For example, if
a leaf RBridge is not locally connected to a set of VLANs then there is no need to flood packets that
contain 802.1Q tags matching those VLANs to that RBridge leaf. The set of VLANs enabled on each
RBridge is communicated in the ENABLED-VLANS sub-TLV sent in the MT-PORT-CAP TLV.
TRILL Network Configuration Example
Use the following TRILL network example as a reference for configuration details. The numbers indicate
the TRILL network port numbers that connect each switch. The RBridges are named A, B, C, and D and
have the following nicknames, respectively: 101, 102, 103, and 104. The default VLAN is the TRILL
designated VLAN. Access VLAN 10 is connected to the TRILL network using Rbridges A and D, while
access VLAN 20 is attached using Rbridges A and B. The access VLAN 30 is connected using Rbridges
C and D. For this example, all of the VLANs are connected through ports 10-20 on each switch.
Advanced Features
36
TRILL
Figure 23: TRILL Network Configuration
RBridge A
Remove all of the ports from the Default VLAN and then add back ports 1 and 2.
configure vlan Default delete ports all
configure vlan Default add ports 1,2 tagged
Create VLANs 10 and 20 on RBridge A.
create vlan rgiii tag 10
configure vlan rgiii add ports 10-20 tagged
create vlan flacco tag 20
configure vlan flacco add ports 10-20 tagged
Configure the RBridge’s nickname as “RBridge-A”. Optionally, the root and nickname priority could also
be specified on this command, but because they are not specified, the default values are used.
create trill nickname 101 name RBridge-A
Configure VLANs 10 and 20 as access TRILL VLANs.
disable igmp snooping rgiii
disable igmp snooping flacco
configure trill add access tag 10
configure trill add access tag 20
Enable TRILL.
enable trill
RBridge B
Remove all of the ports from the Default VLAN and then add back ports 1 and 2.
configure vlan Default delete ports all
configure vlan Default add ports 1,2 tagged
Advanced Features
37
TRILL
Create VLAN 20 on RBridge B.
create vlan flacco tag 20
configure vlan flacco add ports 10-20 tagged
Enable TRILL.
enable trill
Configure the RBridge’s nickname as “RBridge-B”. Optionally, the root and nickname priority could also
be specified on this command, but because they are not specified, the default values are used.
create trill nickname 102 name RBridge-B
Configure VLANs 20 as access TRILL VLANs.
configure trill add access tag 20
RBridge C
Remove all of the ports from the default VLAN and then add back ports 1 and 2.
configure vlan Default delete ports all
configure vlan Default add ports 1,2 tagged
Create VLAN 30 on RBridge C.
create vlan rodgers tag 30
configure vlan rodgers add ports 10-20 tagged
Enable TRILL.
enable trill
Configure the RBridge’s nickname as “RBridge-C”. Optionally, the root and nickname priority could also
be specified on this command, but because they are not specified, the default values are used.
create trill nickname 102 name RBridge-C
Configure VLANs 30 as access TRILL VLANs.
configure trill add access tag 30
RBridge D
Remove all of the ports from the Default VLAN and then add back ports 1 and 2.
configure vlan Default delete ports all
configure vlan Default add ports 1,2 tagged
Create VLANs 10 and 20 on RBridge A.
create vlan rgiii tag 10
configure vlan rgiii add ports 10-20 tagged
create vlan rodgers tag 30
configure vlan rodgers add ports 10-20 tagged
Enable TRILL.
enable trill
Configure the RBridge’s nickname as “RBridge-D”. Optionally, the root and nickname priority could also
be specified on this command, but because they are not specified, the default values are used.
create trill nickname 101 name RBridge-D
Advanced Features
38
TRILL
Configure VLANs 10 and 20 as access TRILL VLANs.
configure trill add access tag 10configure trill add access tag 30
Restrictions and Limitations
The following list identifies TRILL feature limitations in ExtremeXOS 15.4:
• Multicast, flood, and broadcast traffic is limited to 6G per 240G packet processor.
• Multicast is not supported. All multicast traffic is transmitted over a single DTree.
• Only supports forwarding to one neighbor RBridge per port.
• No support for Hybrid TRILL VLANs. A VLAN must either be a TRILL network VLAN or an access
VLAN.
• Hybrid ports are not supported (though VLANs can have TRILL network ports and native 802.1Q
Ethernet ports in the same VLAN).
• On a transit Rbridge, the VLANs being transported still consume hardware resources (multicast
indices and FDB entries) if VLAN pruning is enabled, even if the VLAN is not present on the transit
Rbridge.
• Hitless failover high availability is not supported.
• TRILL is supported on the default VR only.
• Network recovery times are similar to other routing protocols, such as Open Shortest Path First
(OSPF).
• No Operations and Management (OAM) protocol (for example, Bidirectional Forwarding Detection
[BFD]) fault detection is provided— only link LoL and Hello timeouts.
• No RBridge TRILL peering authentication to prevent network spoofing.
• IGMP snooping must be disabled on access VLANs before they are added to TRILL (disable igmp
snooping vlan vlan_name).
•
•
MLAG and TRILL are not supported on the same VLANs/ports. Enabling MLAG for a different set of
VLANs/ports puts the entire switch in software learning mode, including TRILL FDB entries.
The following protocol features cannot be configured on a TRILL network VLAN:
• IP forwarding
• IP routing protocols
• IP multicast protocols
• MPLS
• ESRP
• Ring protocols (for example: EAPS, ERPS)
• MLAG
• Private VLANs
• VLAN translation
• VLAN aggregation
• VMANs
• VPLS
• VRR
• STP
• Customer edge ports (CEP)
Advanced Features
39
TRILL
• Multicast snooping
• Any type of tunneling (for example: GRE, IPv6-to-IPv4, IPv6-in- IPv4)
Configuring TRILL
•
To enable TRILL data plane forwarding on the switch, use the following command:
enable trill
•
To disable the TRILL protocol on the switch, use the following command:
disable trill
•
To administratively add a VLAN tag, or a range of VLAN tags that represent edge (or access)
VLANs attached to the TRILL network, use the following command:
configure trill add access tag first_tag {- last_tag}
•
To administratively delete a VLAN tag, or a range of VLAN tags from the configured access VLAN
set, use the following command:
configure trill delete access tag first_tag {- last_tag}
•
To configure the desired VLAN to use as the designated TRILL VLAN, use the following command:
configure trill designated-vlan desired vlan_name
•
To configure the TRILL protocol on the specified VLAN, use the following command:
•
To remove TRILL from the specified network VLAN from the TRILL configuration, use the following
command:
configure trill add network vlan vlan_name
configure trill delete network vlan [vlan_name | all]
•
To allocate a nickname for use by the local RBridge, use the following command:
create trill nickname nickname_id {nickname-priority id_priority} {rootpriority root_priority} {name nickname_string}
•
To delete an RBridge nickname, use the following command:
delete trill nickname [nickname_id | nickname_string | all]
•
To configure the nickname parameters, use the following command:
configure trill nickname [nickname_id | nickname_string] {new-nicknname
new_nickname_id} {nickname-priority nickname_id_priority} {root-priority
new_root_priority} {name new_nickname_string}
•
To enable and disable the TRILL Hello protocol per port, use the following command:
configure trill ports [port_list| all] protocol [enable | disable]
•
To configure the designated RBridge election priority, use the following command:
configure trill ports [port_list | all] {drb-election priority}
•
To configure the TRILL interface link type for the specified port, use the following command:
configure trill ports [port_list | all] {link-type [broadcast | point-to-point]}
•
To configure the TRILL link metric for the specified link, use the following command:
configure trill ports [port_list| all] {metric [metric | automatic]}
•
To configure the RBridge’s TRILL System ID, use the following command:
configure trill system-id [switch-mac | system_id]
Advanced Features
40
TRILL
•
To configure the TRILL link metric for the specified link, use the following command:
configure trill ports [port_list| all] {metric [metric | automatic]}
•
To configure the RBridge to represent multiple devices on a shared link as being connected to a
TRILL pseudonode, use the following command::
configure trill pseudonode [enable | disable]
•
To configure the amount of time the RBridge does not forward traffic to end stations after detecting
a root RBridge topology change, or under certain conditions when the appointed forwarder status
changes, use the following command:
configure trill inhibit-time seconds
•
To enable and disable the RBridge maintenance mode, use the following command:
configure trill maintenance-mode [enable | disable]
•
To configure the maximum amount of next-hops calculated to an egress RBridge, use the following
command:
configure trill sharing max-next-hops max_next_hops
•
To configure the TRILL MTU size, use the following command:
configure trill mtu size mtu_size
Note
Jumbo frames must be enabled on TRILL Network ports.
•
To configure the TRILL MTU probe protocol, use the following command:
configure trill mtu probe [enable | disable]
•
To configure the MTU probe failure count, use the following command:
configure trill mtu probe fail-count probes_sent
•
To configure tree pruning for all trees in-use as specified by the use count, use the following
command:
configure trill tree prune vlans [enable | disable]
•
To configure the TRILL Link State Protocol timers, use the following command:
configure trill timers lsp [generation-interval generation_seconds |
refresh-interval refresh_seconds | lifetime lifetime_seconds | transmitinterval transmit_milliseconds | retransmit-interval restransmit_seconds |
checksum [enable | disable]]
•
To configure the TRILL SPF restart time and periodic calculation intervals, use the following
command:
configure trill timers spf {restart restart_interval} {interval seconds}
•
To configure the TRILL SPF back-off timer delay, use the following command:
configure trill timers spf backoff-delay {minimum minimum_delay} {maximum
maximum_delay}
•
To configure the TRILL Hello protocol timers, use the following command:
configure trill timers hello {multiplier number} {interval [seconds | minimal]}
•
To set the minimum time between consecutive complete sequence number packet (CSNP)
transmissions on the specified interface, use the following command:
configure trill timers csnp {interval seconds}
Advanced Features
41
TRILL
•
To display general configuration information related to TRILL, use the following command:
show trill {detail | counters}
•
To display status information related to RBridges in the TRILL network, use the following command:
show trill rbridges
•
To display network information related to TRILL RBridge neighbors, use the following command:
show trill neighbor {nickname nickname | system-id system_id | mac-address
mac_address}
•
To display operational TRILL information associated with the switch ports, use the following
command:
show trill ports {port_list} {counters {no-refresh | detail}}
•
To display the links state database associated with TRILL network, use the following command:
show trill lsdb {lsp-id lsp_id | detail}
•
To display the egress RBridge forwarding database for the TRILL network, use the following
command:
show trill distribution-tree {[pruning vlan | rpf] {dtree_nickname}}
•
To clear all protocol and port counters associated with TRILL, use the following command:
clear trill counters
•
To ping a remote RBridge, use the following command:
ping trill {count count} {interval interval} rbridge_nickname
•
To perform a traceroute to a remote RBridge, use the following command:
traceroute trill rbridge_nickname
•
To clear the TRILL configuration and remove the TRILL protocol from all VLANs, use the following
command:
unconfigure trill
Advanced Features
42
2 OpenFlow
OpenFlow Overview
Provisioning Flows with FDB Entries
OpenFlow provides a standardized, flexible tool to build virtualized networks by separating and
abstracting the switching network’s control plane from the forwarding data plane. OpenFlow enables
switching control plane features to be implemented and evolved in a hardware-independent manner.
Network operators who manage large-scale data centers can optimize path selection and forwarding
strategies based on their specific network needs.
OpenFlow Overview
The ExtremeXOS OpenFlow implementation enables an external OpenFlow Controller to manipulate
data flows within an Extreme switch using a standard protocol to dynamically configure a flow table
abstraction. Flow table entries consist of a set of packet matching criteria (L2, L3, and L4 packet
headers), a set of actions associated with a flow (flood, modify, forward, divert to controller, etc.), and a
set of per flow packet and byte counters. Flow table entries are implemented using hardware ACLs and
FDB entries.
ExtremeXOS supports a subset of OpenFlow classification capabilities, forwarding actions, and
statistics operations based as defined in the following tables. OpenFlow Table Match Conditions on
page 47
Additionally, ExtremeXOS supports hybrid switch operations with OpenFlow in these instances:
•
•
On the same switch, OpenFlow-enabled ports coexist with standard non-OpenFlow-enabled
Ethernet ports on the same switch.
A switch port also supports the hybrid mode, and is able to process Openflow traffic as well as
standard Ethernet non-OpenFlow traffic in the following instances:
• OpenFlow is enabled at the VLAN level. All ports associated with an OpenFlow VLAN only
process OpenFlow flows associated within that VLAN.
• Ports in VLANs that are not OpenFlow-enabled behave as standard Ethernet ports for these
VLANs.
ExtremeXOS CLI commands are used to enable OpenFlow, and to assign VLANs to the OpenFlow
domain. The OpenFlow operations on a switch are controlled by an OpenFlow Controller that is
connected to a switch using either the switch outband management port, or using a switch port in a
VLAN that is not configured for OpenFlow.
ExtremeXOS Release 15.4 and above provides the following OpenFlow enhancements:
• EXOS Release 15.4 and above increases the number of OpenFlow VLANs supported to the memory
scaling capabilities of the platform.
• Adds VLAN ID editing functions (VLAN ID add, strip, and modify).
• Adds source and destination MAC modify actions to the platforms that can support it.
Advanced Features
43
OpenFlow
•
•
•
•
Supports the increased scaling of simple L2 flows by including the use of the FDB table to support
OpenFlow flows.
Adds OpenFlow platform Demo support only for BlackDiamond X8, and BlackDiamond 8K chassis
platforms using select interface cards. OpenFlow will work with a single MM/MSM module. Failover
with dual MM/MSM’s is not supported.
Provides the ability for multiple OpenFlow controllers to be configured to support high availability.
Provides for VLANs to be configured for OpenFlow control. The same port on a switch can support
both OpenFlow-managed, and non-OpenFlow managed VLANs.
Limitations
The following list identifies limitations in this release that are the result of hardware restrictions:
• Supported platforms do not implement both packet and byte counters simultaneously on dynamic
ACL entries. Only packet counters are supported in current implementation. Counters are not
supported with FDB flows.
• IN_PORT, FLOOD, NORMAL, and TOS/DSCP editing actions are not supported.
• Flows implemented using ACL hardware have platform limitations on the simultaneous
combinations of flow match conditions that can be supported. These limitations are described in
each version of ExtremeXOS Release Notes under the ACL description section, and in the Flow
Match combinations table later in this section. When receiving a flow match combination that
cannot be supported with the platform’s ACL hardware, the switch will generate an OpenFlow error
message to the controller.
• Flows implemented using FDB entries are subject to normal FDB constraints, including platformdependent table sizes.
• FDB-based OpenFlow idle-timeout follows the configured FDB Aging Time.
• ExtremeXOS OpenFlow supports one physical table, and ingress table. The concept of an
emergency flow table is not supported.
• OpenFlow 1.0 describes a “secure fail” model where a switch immediately removes all of its flows
when it loses connectivity to its controller. ExtremeXOS implements an “open fail” mode. In this
mode the switch maintains its existing flows after losing connectivity to a controller. The "open fail"
model is required to support controller high availability solutions.
• High availability for controllers is available through the following two mechanisms:
• Some controller clusters present a single IP address. The switch treats the cluster as a single
controller.
• Some controller clusters present multiple IP addresses. The switch connects simultaneously to
primary and secondary controller targets and enables the controllers to manage failover.
• OpenFlow, XNV, and IDM are all features that enable an external agent to control resources on a
switch. Due to their interaction models and resource requirements, these features are mutually
exclusive. The ExtremeXOS OpenFlow implementation prevents these services from being
simultaneously configured on the same port.
Note
There are other ExtremeXOS features that may not perform optimally when configured
on OpenFlow enabled VLANs, or switch ports with OpenFlow supported VLANS. We
make no attempt to prevent you from configuring additional services on these interfaces.
Advanced Features
44
OpenFlow
Supported Platforms
EXOS wide-key ACL platform is required to support OpenFlow because of the potential for L2, L3, and
L4 simultaneous header match conditions. OpenFlow is supported on the following platforms:
• Summit X440
• Summit X430
• Summit X460
• Summit X480
• Summit X670
• Summit X770
• E4G-200 and 400
• BlackDiamond X8 with a single MM module (Demo version support only).
• BlackDiamond 8K – 8900 (XL-Series) and C-Series (Demo version support only).
EXOS OpenFlow Licensing
OpenFlow is a license enabled XMOD EXOS feature. To use OpenFlow, the OpenFlow XMOD must be
installed and a switch specific OpenFlow license must be enabled.
OpenFlow Control Transport Services
The implementation of OpenFlow in ExtremeXOS does not include a functional SDN controller. Instead,
Extreme Networks' OpenFlow solution can work with other major vendors' SDN controllers:
• Beacon/Floodlight—Floodlight is an open source SDN controller that enables a diverse set of
applications running on top of it. You can obtain Floodlight at Extreme Networks' website at
https://xkit.extremenetworks.com/app/v/sdnfloodlightcontroller. This version of Floodlight is
modified to run only a subset of applications that are tested and verified with Extreme Networks
switches (Circuit Pusher, Static Flow Entry Pusher, and Forwarding). The Floodlight controller, when
integrated with Extreme Network switches, provides simple capabilities such as network topology
updates, newly provisioned end-host pings in an OpenFlow-enabled network, and the ability to
establish static bi-directional circuits between end hosts.
• NEC ProgrammableFlow Controller—The ProgrammableFlow Controller allows you to build
multitenant networks, enable rapid scaleout of new applications, balance workloads, and gain higher
levels of availability. ProgrammableFlow's centralized control of the network eliminates the need for
distributed protocols such as Spanning Tree.
Some controller clusters present a single IP address to EXOS which should be configured for a primary
controller only. The controller cluster manages failover transparently to EXOS.
ExtremeXOS supports Out-Of-Band control connections to controllers. The OpenFlow control traffic
between a switch and the OpenFlow controller (management traffic) can come either from the switch
outband management port, or from a non-OpenFlow VLAN configured on the switch.
ExtremeXOS supports clear TCP connections with controllers.
Advanced Features
45
OpenFlow
Configuring Multiple SDN Controllers
ExtremeXOS allows you to configure up to two SDN controllers (designated the primary and secondary
controllers). Both SDN controllers are active and control flows through a process negotiated between
the controllers.
Configuring two SDN controllers provides controller redundancy. If one SDN controller goes down or
connectivity is lost, OpenFlow repeatedly attempts reconnection. If connectivity cannot be
reestablished, then the remaining SDN controller takes over all flow control.
Stacking and Redundancy
The OpenFlow implementation supports stacking operation; however, stacking redundancy is not
currently supported.
It is important to note that what happens after a switchover is determined by the OpenFlow controller,
and not the OpenFlow switch. The OpenFlow 1.0 standard does not support the concept of a stateful
switchover. The switch and the controller communicate using a TCP session. On switchover/failover
this session is broken, and a new active OpenFlow TCP session with the controller has to be established.
The OpenFlow 1.0 standard requires the switch and the controller to flush any existing flows when their
TCP connection is terminated.
EXOS OpenFlow Port Numbering
Using OpenFlow port numbers in EXOS corresponds directly to the EXOS chassis physical port number
for platforms with a non-hierarchical port addressing model (stand-alone switches). For platforms
utilizing a hierarchical port addressing model (stacks and chassis), the OpenFlow 16 bit port number
consists of two fields representing slot and port.
Port numbering in hierarchical addressed platforms use the lower seven bits (bits 0 – 6; port number
value 1-127) of the port number as an unsigned value that represents the physical port number (starting
at 1). The next three bits (bits 7-9) represent the slot (starting at 0 for slot 1) that the port resides on.
Example:
SLOT
PORT
0 1 0 0 0 1 1 1 0 0
9 8 7 6 5 4 3 2 1 0
The above port is slot 3 port 28, and is represented as a decimal 284 port in OpenFlow.
Note:
Note
Slot 9 and Slot 10 are currently not supported.
Advanced Features
46
OpenFlow
EXOS switch ports are reported to the controller using the in the OpenFlow Features Reply message.
You should rely on the port number model reported to the controller in the Features Reply message
instead of algorithmically determining port numbering.
OpenFlow Table Match Conditions
An OpenFlow flow table entry consists of header field match conditions, counters, and specified
forwarding actions. The header field match conditions include Ethernet, IP, and TCP/UDP/ICMP/ARP
header fields. Each of these may be specified within a single flow table entry, or some of them may be
fully wildcarded, or subnet masked. The required header fields are described in the following table.
Table 3: OpenFlow Match Condition Dependencies
Ingress Source Destinatio VLAN
Port
MAC
n MAC
ID
VLAN Ether
Priority type
Source Destinatio
IP /
n IP /
Sender Target IP
IP
IP ToS IP
Protoc
ol
L4 field L4 field
1
2
ANY
ANY
ANY
ANY
ANY
NO
NO
NO
NO
NO
NO
NO
ANY
ANY
ANY
ANY
ANY
8100
NO
NO
NO
NO
NO
NO
ANY
NO
NO
ANY
ANY
0806
Any
Any Target NA
Sender IP
IP
NA
NA
NA
ANY
ANY
ANY
ANY
ANY
0800
Any
Any
Source Destinatio
IP
n IP
ANY
NO
NO
NO
ANY
NO
NO
ANY
ANY
0800
Any
Any
Source Destinatio
IP
n IP
ANY
1
ICMP
Type
ICMP
Code
ANY
ANY
ANY
ANY
ANY
0800
Any
Any
Source Destinatio
IP
n IP
ANY
6
TCP Src TCP
port
Dst
port
ANY
ANY
ANY
ANY
ANY
0800
Any
Any
Source Destinatio
IP
n IP
ANY
17
UDP
Src
port
UDP
Dst
port
Table 4: OpenFlow Classification/Match Rule Support
Field
Width (Bits)
Wildcard
Support
When Applicable
Notes
EXOS Support
Ingress Port
N/A
Yes
All packets
Starts at 1
Supported
Ethernet source 48
address
Yes
All packets on
enabled ports
Supported
Ethernet
destination
address
Yes
All packets on
enabled ports
Supported
Advanced Features
48
47
OpenFlow
Table 4: OpenFlow Classification/Match Rule Support (continued)
Field
Width (Bits)
Wildcard
Support
When Applicable
Notes
EXOS Support
Ethernet type
16
Yes
All packets on
enabled ports
Switch is required to match Conditional
the type in both standard
support1
Ethernet and 802.2 with a
SNAP header and OUI of
0x000000. The special
value of 0x05FF is used to
match all 802.3 packets
without SNAP headers.
VLAN ID
12
Yes
All packets of
Ethernet type
0x8100
VLAN priority
3
Yes
All packets of
Ethernet type
0x8100
VLAN PCP field
Supported
IPv4 source
address
32
Yes
All IP and ARP
packets
Can be subnet masked
Conditional
Support2
IPv4
destination
address
32
Yes
All IP and ARP
packets
Can be subnet masked
Conditional
Support2
IP Protocol
8
Yes
All IP and IP over
Ethernet, ARP
packets
Only the lower 8 bits of the Conditional
ARP opcode are used
Support2
IP ToS bits
6
Yes
All IP packets
Transport
source port/
ICMP Type
16
Yes
All TCP, UDP, and
ICMP packets
Only lower 8 bits used for
ICMP Type
Supported
Transport
destination
port / ICMP
Code
16
Yes
All TCP, UDP, and
ICMP packets
Only lower 8 bits used for
ICMP code
Supported
Supported
Supported
1. Ethernet Type 2 packets (i.e., with Ethertype) are supported.
2. Support for IP address matching in ARP packets is being investigated.
A particular flow table entry may specify exact or wildcard values for each field, and may specify
subnet-masked values for the IPv4 source and destination addresses. Entries that specify an exact flow
match (i.e., have no wildcarded or subnet masked fields) are installed with higher priority than other
flow table entries. Entries with wildcarded or subnet-masked header fields have a priority associated
Advanced Features
48
OpenFlow
with them, specified by the controller. Entries are inserted in priority order into the forwarding
hardware.
Note
ACL-based flows are implemented using ACL hardware. Platform hardware has limitations on
the simultaneous combinations of flow match conditions that can be supported. These
limitations are described in the ExtremeXOS Release Notes. When receiving a flow match
combination that cannot be supported with the platform’s ACL hardware, the switch sends
an OpenFlow error message to the controller.
Link Aggregation Group
EXOS OpenFlow supports Link Aggregation Groups. Using the standard EXOS CLI, a LAG group can be
defined. When the master port of the LAG group is included in an OpenFlow VLAN, the LAG is reported
to the controller using the LAG’s master port (Other member ports of the LAG group are not reported
to the controller.).
A flow policy is applied to all packets arriving on OpenFlow VLANs on the LAG member links. Outgoing
packets directed to the EXOS LAG egress the switch according to the hardware hash established for
the LAG.
Quality of Service Support
The EXOS OpenFlow implementation provides basic Quality-of-Service (QoS) support by a simple
queuing mechanism. Each queue is represented by an EXOS QoS profile. Queuing configuration and
statistics can be queried by the controller. Additionally, you can use the enqueue action to forward a
packet through a queue attached to a port. When a switch registers with a controller, the controller
may query the switch for queuing configuration through QOS profiles. Please refer to the QoS chapter
for additional information on qosprofile behaviors.
You should configure QOS profiles before registering with the OpenFlow controller. By default, QP1 and
QP8 are already created.
For example, to provision an OpenFlow queue ID2 with a minimum bandwidth of 25%, issue the
following commands:
create qosprofile qp3
configure qp3 minbw 25 ports all
Table 5: Queue ID to QoS Profile Mapping
QoS Profile
Queue ID
QP1
0
QP2
1
QP3
2
Advanced Features
49
OpenFlow
Table 5: Queue ID to QoS Profile Mapping (continued)
QP4
3
QP5
4
QP6
5
QP7
6
QP8
7
A rule specifying multiple enqueue actions with the same queue ID is supported.
Rules specifying both enqueue and output-only actions are not supported.
Rules specifying multiple enqueue actions to different queues in the same rule are not supported. This
is due to the ExtremeXOS ACL implementation constraint.
Increased VLAN Support
ExtremeXOS 15.4 and above supports the OpenFlow hybrid mode of operation with multiple VLANs. A
switch port can support both traditional networking services and OpenFlow based networking services.
The forwarding model selected is configurable per VLAN.
The maximum number of VLANs supported is specified in the Release Notes.
Provisioning Flows with FDB Entries
The EXOS OpenFlow implementation leverages both the ACL TCAM hardware, and the FDB table. The
OpenFlow process evaluates FlowMod requests from the controller, and maps them to the most
scalable hardware resources available that match the flow requirements. Flows that require complex
matching conditions and actions utilize ACL hardware. Simple flows that require destination MAC
addresses and VLANs with an action of forwarding out of a port are implemented using the FDB table.
This model greatly improves flow scalability of EXOS switches for applications requiring only simple
flows.
ExtremeXOS Release 15.4 and above supports two physical tables for implementing flows, but
represents a single logical flow table to the controller. It is important to note that when an FDB flow
entry and an ACL flow entry conflict, the ACL-based flow always takes precedence over the FDB-based
flow. Controller-specified flow priorities cannot be applied across physical tables.
The following sections discuss FDB Flow support in ExtremeXOS.
OpenFlow Layer 2 FDB Extensions
Without the L2 FDB Extensions, the OpenFlow table size is limited by the number of ACLS supported
by the switch. As packets ingress the switch chips, they pass through the L2 lookup stage, followed by
ACL matching.
Advanced Features
50
OpenFlow
With OpenFlow L2 FDB extensions, the EXOS OpenFlow component manages a subset of the L2 FDB
entries. The remote OpenFlow controller may describe a larger number of flows according to an exact
match of the VLAN ID and destination MAC address. As packets arrive on OpenFlow-enabled ports in
the EXOS OpenFlow switch, the L2 switching stage can recognize a match and mark the packet for
forwarding.
Flow Table entries enabled by OpenFlow L2 FDB Extensions can match only on VLAN ID and
Destination MAC Address, and must be exact matches.
OpenFlow Table Counter
Counters in an OpenFlow switch are maintained per-table, per-flow, per-port, and per-queue. In
Extreme switch hardware, packet (or byte) counters are maintained per-dynamic ACL entry.
Flow Table entries enabled by OpenFlow L2 FDB Extensions do not maintain per-flow counters.
L2 FDB Extensions Action
Each flow entry is associated with zero or more actions that determine how the switch is expected to
process matching packets.
Flow Table entries enabled by OpenFlow L2 FDB Extensions support only one action which must be to
forward the packet to a physical port.
Limitations
This feature has the following limitations:
• An FDB entry will implement only an OpenFlow rule based on exact match of VLAN ID and
Destination MAC Address.
• The only action supported for an FDB entry match is to forward the packet to a port.
• For each OpenFlow-enabled VLAN, the OpenFlow priority of flow entries to be represented in the
L2 FDB must be lower than the OpenFlow priority of all other flows that could match that VLAN ID.
• The Destination MAC address cannot be in the IP multicast range. (01:00:5e:xx:xx:xx) This limitation
allows non-OpenFlow VLAN's to use IGMP snooping.
• The L2 switching hardware does not count packets and bytes forwarded for each entry. The single
wide-key ACL per OpenFlow VLAN can provide summary counts.
• FDB installation and other operations are subject to hash collisions and other infrastructure faults
that could cause unreliable state.
• Platforms using hardware-accelerated aging do not provide aging based on SA-Mac and DA-Mac
activity at a per-entry level.
• L2 flows shadowed by ACL flows may are subject to ACL flow activity.
Supported Platforms
The L2 FDB Extensions feature is supported on all the platforms that support OpenFlow.
OpenFlow Table Action
Each flow entry is associated with zero, or more actions that determine how the switch is expected to
process matching packets.
Advanced Features
51
OpenFlow
Currently, additional Flow Table entries enabled by OpenFlow L2 FDB Extensions support only one
action, which is to forward the packet to a physical port.
The following table describes the OpenFlow action implementation in ExtremeXOS:
Openflow Actions
Equivalent to in Standard
Networking
ExtremeXOS
Implemented
Forward Out Port
L2 Forward /Switching
YES
Forward ALL
L2 Broadcast
NO
Forward CONTROLLER
YES
Forward LOCAL
NO
Forward TABLE
NO
Forward IN_PORT
Reflective-relay
Forward NORMAL
Notes
NO
YES*
* For OpenFlow-enabled
VLANs only.
Forward FLOOD
STP Flood
NO
Enqueue
Assign to QoS Profile and
forward
YES*
Drop
Blackhole
YES
Set VLAN ID
Routing
YES*
* If there is an OpenFlow
tagged VLAN with that
VLAN ID and the
appropriate output ports
added as tagged.
Set VLAN Priority
Class of Service
modifications
YES*
* Not with Enqueue.
Strip VLAN Header
Output through an
untagged port
YES*
* If there is an untagged
VLAN with the appropriate
output ports added
untagged. Not with Set
VLAN ID.
Modify Ethernet source MAC
Address
Routing
YES
Modify Ethernet Destination
MAC address
Routing
YES
Modify IPv4 Source address
Redirection/ NAT
NO
Modify IPv4 Destination address Redirection/ NAT
NO
Modify IPv4 ToS bits
DSCP modifications
NO
Modify L4 source port
Redirection/ NAT
NO
Modify L4 destination port
Redirection/ NAT
NO
Advanced Features
* Not with Set VLAN
Priority or Output actions.
52
OpenFlow
OpenFlow Layer 2 Aging and Idle Timeout
ExtremeXOS OpenFlow implementation supports OpenFlow idle and hard timeouts for ACL-based
flows. FDB-based flows support OpenFlow hard timeout only. FDB-based OpenFlow idle-timeout
follows the configured FDB Aging Time.
OpenFlow Barrier Requests
OpenFlow barrier requests require the switch to wait for previously requested actions to complete
before it replies. Barrier requests and replies are supported for ACL-based flows.
Configuring OpenFlow on Switches
In order to utilize all of the ExtremeXOS supported OpenFlow actions, you need to implement a proper
switch configuration. This implementation includes the correct ACL, controller, and VLAN configuration.
In the following example, the network consists of four fully meshed ExtremeXOS switches, one
management ExtremeXOS switch, two desktop computers, two phones, two servers, and two
controllers. Only the switches are vendor-specific. Please refer to the following figure for the physical
connections:
Advanced Features
53
OpenFlow
Figure 24: OpenFlow Network Topology
To configure OpenFlow on your switches:
Advanced Features
54
OpenFlow
1
On the four switches, create these four VLANs -- data (untagged), voice (tag 100), servers (tag
200), and OF_Control (untagged) -- using the following commands:
create vlan data
create vlan voice tag 100
create vlan servers tag 200
create vlan OF_Control
Note
Additionally, issue this command on the management switch.
2 Remove the appropriate ports from the VLAN Default using the following command: configure
vlan default delete ports port_list.
3 The OpenFlow XMOD corresponding to the ExtremeXOS version is required for OpenFlow
functionality. To download and install the XMOD, use the following command:
download image SERVER_IP_ADDRESS XMOD_NAME.xmod {vr vr_name}. Agree to the
installation if prompted.
4 Once the OpenFlow XMOD is installed, an OpenFlow license needs to be applied using the following
command: enable license openflow feature license key.
5 Since it is highly likely that the matching criteria for the flows will be complex, we recommend using
double-wide access lists.
A reboot is required for the changes to take effect.
6 After the switches reboot, you can configure OpenFlow. First, configure the OpenFlow controllers
by issuing the following commands (in this example, the VR-Default is used):
configure openflow controller primary out-of-band active ipaddress ip address
of the primary controller vr VR-Default
configure openflow controller secondary out-of-band active ipaddress ip
address of the secondary controller vr VR-Default
7 Enable OpenFlow on the VLANs data, voice, and servers by issuing the following commands:
enable openflow vlan data
enable openflow vlan voice
enable openflow vlan servers
8 Enable Openflow globally using the following command:
enable openflow
9 Add ports to the VLANs according to the topology. The data, voice, and servers VLANs are
controlled by OpenFlow, while the OF_Control VLAN is used to connect to the controllers. Issue the
following commands, substituting for the appropriate ports:
configure vlan data add ports port_list untagged
configure vlan voice add portsport_list tagged
configure vlan servers add ports port_list tagged
configure vlan OF_Control add ports port_list untagged
10 The data, voice, and servers networks should now be controlled by the OpenFlow controller.
11 To view the OpenFlow controllers status, issue the following command:
show openflow controller
Advanced Features
55
OpenFlow
12 To view the OpenFlow flows installed on each switch, use the following command:
show openflow flows
Verifying OpenFlow Configuration and Operation
You can verify the OpenFlow setup using the following commands.
To verify that OpenFlow is enabled correctly on the switch, type:
show openflow
The following sample output of the command shows that the switch has OpenFlow enabled, that FDB
is on, and that the ACL width is double.
* (Private) SDN-1.1 # show openflow
OpenFlow:
Enabled
FDB:
On
Access-list width: Double
Controller
Status
Datapath ID
VR
Mode
Target
Uptime(secs)
:
:
:
:
:
:
:
Primary
ACTIVE
00000004968374d4
VR-Default
out-of-band Active
tcp:10.66.65.242:6633
1134555
Controller
: Secondary
Not configured.
Flows
VLAN
VID Ports Active Error
-------------------------------- ---- ----- ------ -----major
4089
3
2
0
Total number of VLAN(s): 1
To verify the setup of the SDN controller on the switch, type:
show openflow controller {primary | secondary}
The following sample output of the command shows that the switch has a primary SDN controller (but
no secondary controller), located at 10.66.65.242, and that it is communicating with the SDN controller
through the virtual router "VR-Default."
* (Private) SDN-1.2 # show openflow controller
Controller
: Primary
Configured
: Yes
Datapath ID : 00000004968374d4
VR
: VR-Default
Mode
: out-of-band Active
Target
: tcp:10.66.65.242:6633
Status
: ACTIVE
TLS
Probe(secs) : 30
Uptime(secs)
Rate Limit
: 1000
Burst Size
Advanced Features
: Disabled
: 1135034
: 250
56
OpenFlow
Packets Sent : 348705
Controller
Configured
Packets Received : 274586
: Secondary
: No
To view the number of flows on the switch so that you can ensure that it is not exceeding the capacity
of the switch, type:
show openflow flows
The following sample output of the command shows that the switch has two flows.
* (Private) SDN-1.3 # show openflow flows
Total number of flows: 2
Flow name
Type Duration (secs)
Prio Packets
------------- ---- ------------------- ----- -------------------of_48
ACL
172915
10
172913
Match:
Input Port:
14
Src MAC:
00:0c:29:02:10:d3
Dst MAC:
00:0c:29:80:ac:0a
Ethernet Type:
0x0800
Actions: output:10, cookie:0x20000000000000, idle:5:4
of_49
ACL
172915
10
172913
Match:
Input Port:
12
Src MAC:
00:0c:29:80:ac:0a
Dst MAC:
00:0c:29:02:10:d3
Ethernet Type:
0x0800
Actions: output:14, cookie:0x20000000000000, idle:5:4
Advanced Features
57
3 AVB
Overview
AVB Feature Pack License
Configuring and Managing AVB
Displaying AVB Information
This chapter provides information about Audio Video Bridging support. It specifically discusses the
AVB Feature Pack License, as well as how to configure and manage the AVB feature.
Overview
Audio Video Bridging (AVB) supports the deployment of professional quality audio and/or video (AV)
over standard Ethernet while coexisting with other "legacy" (or non-AV) Ethernet traffic. This supports
"Network Convergence," or using one simple standard Ethernet network for all communication needs.
To support AV applications, it is necessary for AVB systems to provide time synchronization and
quality of service (QoS).
Time Synchronization is needed so that multiple streams may be synchronized with respect to each
other. For example:
• Voice and video
• Multiple audio streams for a multi-digital speaker deployment in a large venue
• Multiple Video streams in a security surveillance application
QoS is needed to ensure:
• Bandwidth guarantees sufficient for each application
• Worst Case Delay Bounds, particularly for interactive applications
• Traffic shaping to limit traffic burstiness and reduce buffering requirements
The time synchronization and QoS requirements for AVB systems are defined in the following set of
IEEE Standards:
• IEEE 802.1AS: Timing and Synchronization for Time-Sensitive Applications in Bridged Local Area
Networks (gPTP)
• IEEE 802.1Q
• Clause 10: Multiple Registration Protocol (MRP) and Multiple MAC Registration Protocol (MMRP)
• Clause 11: VLAN Topology Management (MVRP)
• Clause 34: Forwarding and Queuing for Time-Sensitive Streams (FQTSS)
• Clause 35: Stream Reservation Protocol (SRP)
• IEEE 802.1BA: Audio Video Bridging (AVB) Systems
Advanced Features
58
AVB
AVB Feature Pack License
The AVB feature (including AVB, gPTP and MSRP commands) requires the AVB Feature Pack. After
obtaining the AVB Feature Pack license, use the enable license command to install it. MRP and
MVRP do not require the AVB Feature Pack. AVB is supported on the following platforms: Summit
X430, X440, X460, and X670.
Configuring and Managing AVB
AVB is not enabled in the default configuration, and must be enabled both globally on the switch and
on the ports where you want to use it.
Note
AVB is supported only on individual ports, not on Link Aggregated Ports.
In the simplest case, when starting with a blank configuration, AVB may be enabled by executing the
following two commands:
# enable avb
enable avb ports all
The status of AVB can be seen by using the following command:
# show avb
gPTP status
gPTP enabled ports
MSRP status
MSRP enabled ports
MVRP status
MVRP enabled ports
: Enabled
: *1s
*2m
*11m
*12m
*17m
*13m
*14m
*15m
*16m
*18m
*19m
*20m
*21m
*10ab
*11ab
*12ab
*17ab
: Enabled
: *1ab
*2ab
*13ab
*14ab
*15ab
*16ab
*18ab
*19ab
*20ab
*21ab
*10
*11
*12
*15
*20
*16
*21
*17
: Enabled
: *1
*2
*13
*18
Flags:
*10m
*14
*19
(*) Active,
(!) Administratively disabled,
(a) SR Class A allowed,
(b) SR Class B allowed,
(d) Disabled gPTP port role, (m) Master gPTP port role,
(p) Passive gPTP port role,
Advanced Features
(s) Slave gPTP port role
59
AVB
The show avb command displays high level information about each of the three main protocols
(gPTP, MSRP, and MVRP). Each protocol section indicates that all three protocols are enabled both
globally, and on ports 1,2 and 11-21. The “*” indicates that we have link on each of the ports.
The gPTP status indicates that port 1 is a slave port, which means that the Grand Master Clock (GMC) is
reachable through port 1. The gPTP status also indicates that the rest of the ports are master ports.
Furthermore, the fact that no ports are shown to be in the Disabled role means that gPTP is operational
on all the ports.
The "ab" on the MSRP status indicates that all ports are members of both the class A and class B
domain domains. The MVRP status simply shows which ports are enabled and active.
The user interface for AVB includes the following five protocols:
•
•
•
•
•
gPTP
MRP
MVRP
MSRP
FQTSS
The "avb" commands shown above are part of a set of AVB macro commands provided to simplify the
process of enabling and disabling AVB. The AVB macro commands have the form:
[ enable | disable | unconfigure ] avb { ports [ all | port_list ] }
Using one of the macro commands is the same as executing the following three commands:
[ enable | disable | unconfigure ] network-clock gptp { ports [ all |
port_list ]}
[ enable | disable | unconfigure ] mvrp { ports [ all | port_list ]}
[ enable | disable | unconfigure ] msrp { ports [ all | port_list ]}
MRP does not need to be enabled or disabled, and the only MRP properties that may be configured are
timer values. The defaults should be sufficient for most deployments, though it may be necessary to
increase the leave-all and leave time values when supporting a large number of streams.
Multiple Registration Protocol/Multiple VLAN Registration Protocol is used for dynamically creating
VLANs and/or dynamically adding ports to VLANs. As per IEEE Std 802.1Q-2011, some VLANs can be
marked as forbidden VLANs on some ports so that when MVRP PDU is received on the port with the
particular forbidden VLAN Id, the VLAN is not created and if the VLAN is already there, the port is not
added to the VLAN. This functionality was added in 15.3.2.
The VLAN registration is of three types:
• Forbidden—Port is forbidden to be added to the VLAN
• Normal—Port is allowed to be added to the VLAN
• Fixed—Port is statically added to the VLAN
The forbidden / normal setting is only for dynamic addition of ports to VLANs. Any static addition of
ports to the VLANs, overrides this setting and marks the status as fixed. The forbidden setting can be
Advanced Features
60
AVB
used to control MSRP advertisements, in typical scaling scenarios. In addition to support for forbidden
VLANs, support for periodic timer and extended-refresh timer has been added in 15.3.2.
The FQTSS settings are managed by MSRP, and may not be configured directly.
The disable commands disable the AVB protocols globally or per port without changing any other
configured settings, while the unconfigure commands reset all AVB settings to the initial states, and
release all switch resources that were allocated when the protocols were enabled.
More detailed configuration options are provided on a per-protocol basis using the corresponding
configure commands:
configure
configure
configure
configure
network-clock gptp
mvrp
msrp
mrp
Details for these commands can be found in the EXOS User Guide.
Displaying AVB Information
The complete set of "show" commands are detailed in the EXOS Command Reference Guide. Some of
the more commonly used commands are outlined here.
gPTP
Detailed information about gPTP can be displayed using the following set of commands:
show network-clock gptp ...
For example, the show network-clock gptp ports command can be used to view the gPTP
properties of a given port, and is useful for debugging when the summary avb command shows that
the port is not operational for gPTP.
# show network-clock gptp ports 1
Physical port number
gPTP port status
Clock Identity
gPTP Port Number
IEEE 802.1AS Capable
Port Role
Announce Initial Interval
Announce Current Interval
Announce Receipt Timeout
Sync Initial Interval
Sync Current Interval
Sync Receipt Timeout
Sync Receipt Timeout Interval
Measuring Propagation Delay
Propagation Delay
Propagation Delay Threshold
Propagation Delay Asymmetry
Peer Delay Initial Interval
Advanced Features
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1
Enabled
00:04:96:ff:fe:51:ba:ea
1
Yes
9 (Slave)
0 (1.000 secs)
0 (1.000 secs)
3
-3 (0.125 secs)
-3 (0.125 secs)
3
375000000 ns
Yes
623 ns
3800 ns (auto)
0
0 (1.000 secs)
61
AVB
Peer Delay Current Interval
Peer Delay Allowed Lost Responses
Neighbor Rate Ratio
PTP Version
:
:
:
:
0 (1.000 secs)
3
1.000020
2
MSRP
Detailed information about MSRP can be displayed using the following set of commands:
show msrp ...
Several that are commonly used are:
show
show
show
show
msrp
msrp streams
msrp listeners
msrp streams propagation
Examples of these commands are shown below.
The show msrp command displays the summary information included in the show avb command, but
also displays the total number of streams and reservations on the switch.
# show msrp
MSRP Status
MSRP Max Latency Frame Size
MSRP Max Fan-in Ports
MSRP Enabled Ports
:
:
:
:
Enabled
1522
No limit
*1ab
*2ab
*10ab
*11ab
13
14
15
16
18
19
20
21
Total MSRP streams
: 2
Total MSRP reservations
: 6
Flags: (*) Active,
(!) Administratively disabled,
(a) SR Class A allowed, (b) SR Class B allowed
12
17
The show msrp streams command displays all of the streams that the switch is aware of.
# show msrp streams
Stream Id
Destination
Port Dec
Vid Cls/Rn
BW
---------------------- ----------------- ---- ---- ---- -------------00:50:c2:4e:db:02:00:00 91:e0:f0:00:ce:00
1 Adv
2 A/1
6.336
Mb
00:50:c2:4e:db:06:00:00 91:e0:f0:00:0e:82
2 Adv
2 A/1
6.336
Mb
Total Streams: 2
-----------------------------------------------------------------------------BW
: Bandwidth,
Cls
: Traffic
Class,
Dec
: Prop. Declaration Types, Rn
:
Rank
MSRP Declaration Types:
Advanced Features
62
AVB
Adv
: Talker Advertise,
Failed,
Fail : Talker Fail,
Failed,
Ready : Listener Ready
AskFail
: Listener Asking
RdyFail
: Listener Ready
The show msrp listeners command displays all of the listeners the switch is aware of. If the
declaration type is either Ready or RdyFail, a reservation has been made, and the Stream Age will show
the length of time this reservation has been active.
# show msrp listeners
Stream Id
----------------------00:50:c2:4e:db:02:00:00
Port
----2
Dec
Dir
------- ------Ready
Ingress
State
App
--VO
Reg
--IN
Stream Age
(days,hr:mm:ss)
---------------0, 01:40:23
10 Ready
Ingress VO
IN
0, 01:27:05
11 Ready
Ingress VO
IN
0, 01:27:05
00:50:c2:4e:db:06:00:00
1 Ready
Ingress VO
IN
0, 01:40:15
10 Ready
Ingress VO
IN
0, 01:27:05
11 Ready
Ingress VO
IN
0, 01:27:05
---------------------------------------------------------------------------App
Types
Dir
State
: Applicant State,
Dec
: MSRP Declaration
: Direction of MSRP attributes,
Reg
: Registrar
MSRP Declaration Types:
AskFail : Listener Asking Failed,
Failed,
Ready
: Listener Ready
RdyFail : Listener Ready
Applicant States:
AA
: Anxious active,
AO
: Anxious observer,
LA
: Leaving active,
QA
: Quiet active,
QP
: Quiet passive,
VO
: Very anxious observer,
AN
AP
LO
QO
VN
VP
:
:
:
:
:
:
Registrar States:
IN
: In - Registered,
LV
: Leaving - Timing out
MT
Anxious new,
Anxious passive,
Leaving observer,
Quiet observer,
Very anxious new,
Very anxious passive
: Empty - Not Registered
The show msrp streams propagation command is useful for debugging the propagation of
Talkers and Listners for each stream.
# show msrp streams propagation stream-id 00:50:c2:4e:db:02:00:00
Stream Id
Destination
Port Dec
Vid
Cls/Rn
BW
--------------------------------------- ---- ---- ---- -------------00:50:c2:4e:db:02:00:00
91:e0:f0:00:ce:00
1 Adv
2
A/1
Mb
Advanced Features
6.336
63
AVB
Talker Propagation:
Ingress
Ingress
Propagated
DecType
Port
DecType
-------
-------
----------
1
Adv
Adv
-->
-->
-->
Propagated
Egress
Ports
DecType
----------
-------
2
-->
10
-->
Adv
11
-->
Adv
Adv
Listener Propagation:
Egress
Egress
Propagated
DecType
Port
-------
-------
Ready
<--
1
Listener
Ingress
DecType
Ports
DecType
----------
----------
-------
<--
Ready
<--
2
<--
Ready
<-<--
Ready
Ready
<-<--
10
11
<-<--
Ready
Ready
Total Streams: 1
-----------------------------------------------------------------------------BW
: Bandwidth,
Cls
: Traffic
Class,
Dec
: Prop. Declaration Types, Rn
:
Rank
MSRP Declaration Types:
Adv
Failed,
Fail
Failed,
Ready
: Talker Advertise,
AskFail
: Listener Asking
: Talker Fail,
RdyFail
: Listener Ready
: Listener Ready
MVRP
Other than the MVRP summary information displayed in the show avb command, information about
dynamically created VLANs is shown using the "vlan" commands as follows.
In the show vlan command, it can be seen that SYS_VLAN_0002 is a dynamically created VLAN due
to the “d” flag.
# show vlan
-------------------------------------------------------------------------------------------Name
VID Protocol Addr
Flags
Proto
Ports Virtual
Advanced Features
64
AVB
Active router
/
Total
-------------------------------------------------------------------------------------------Default
1
--------------------------------T--------------- ANY
4 /33 VR-Default
Mgmt
4095 ------------------------------------------------ ANY
1 /1
VR-Mgmt
SYS_VLAN_0002
2
--------------------------------T------d-------- ANY
4 /4
VR-Default
-------------------------------------------------------------------------------------------Flags : (B) BFD Enabled, (c) 802.1ad customer VLAN, (C) EAPS Control VLAN,
(d) Dynamically created VLAN, (D) VLAN Admin Disabled,
(e) CES Configured, (E) ESRP Enabled, (f) IP Forwarding Enabled,
(F) Learning Disabled, (i) ISIS Enabled, (I) Inter-Switch Connection
VLAN for MLAG,
(k) PTP Configured, (l) MPLS Enabled, (L) Loopback Enabled,
(m) IPmc Forwarding Enabled, (M) Translation Member VLAN or
Subscriber VLAN,
(n) IP Multinetting Enabled, (N) Network Login VLAN, (o) OSPF
Enabled,
(O) Flooding Disabled, (p) PIM Enabled, (P) EAPS protected VLAN,
(r) RIP Enabled, (R) Sub-VLAN IP Range Configured,
(s) Sub-VLAN, (S) Super-VLAN, (t) Translation VLAN or Network VLAN,
(T) Member of STP Domain, (v) VRRP Enabled, (V) VPLS Enabled, (W)VPWS
Enabled,
(Z) OpenFlow Enabled
Total number of VLAN(s) : 3
Details about SYS_VLAN_0002 can be displayed using the following command.
# show SYS_VLAN_0002
VLAN Interface with name SYS_VLAN_0002 created dynamically
Admin State:
Enabled
Tagging:
802.1Q Tag 2
Description:
None
Virtual router:
VR-Default
IPv4 Forwarding: Disabled
IPv4 MC Forwarding: Disabled
IPv6 Forwarding: Disabled
IPv6 MC Forwarding: Disabled
IPv6:
None
STPD:
s0(Enabled)
Protocol:
Match all unfiltered protocols
Loopback:
Disabled
NetLogin:
Disabled
OpenFlow:
Disabled
QosProfile:
None configured
Flood Rate Limit QosProfile:
None configured
Ports:
4.
(Number of active ports=4)
Tag:
*1H, *2H,
*10H,
*11H
Flags:
(*) Active, (!) Disabled, (g) Load Sharing port
Advanced Features
65
AVB
(b) Port blocked on the vlan, (m) Mac-Based port
(a) Egress traffic allowed for NetLogin
(u) Egress traffic unallowed for NetLogin
(t) Translate VLAN tag for Private-VLAN
(s) Private-VLAN System Port, (L) Loopback port
(e)
(x)
(G)
(H)
(U)
(V)
Advanced Features
Private-VLAN End Point Port
VMAN Tag Translated port
Multi-switch LAG Group port
Dynamically added by MVRP
Dynamically added uplink port
Dynamically added by VM Tracking
66
4 OAM
CFM
Y.1731--Compliant Performance Monitoring
Y.1731 MIB Support
EFM OAM--Unidirectional Link Fault Management
Bidirectional Forwarding Detection (BFD)
Operation, Administration, and Maintenance (OAM) includes functions used to detect network faults,
measure network performance and distribute fault-related information, including CFM, Y.1731, EFM, and
BFD.
CFM
Connectivity Fault Management (CFM), discussed in the IEEE 802.1Q-2011 standard and originally
specified in the IEEE 802.1ag-2007 standard, allows you to detect, verify, and isolate connectivity
failures in virtual bridged LANs.
Part of this specification is a toolset to manually check connectivity, which is sometimes referred to as
Layer 2 ping.
Note
The ExtremeXOS implementation of CFM is based on the IEEE 802.1Q-2011 standard.
There is no direct interaction between CFM and other Layer 2 protocols; however, blocked Spanning
Tree Protocol (STP) ports are taken into consideration when forwarding CFM messages.
CFM Overview
You can create hierarchical networks, or domains, and test connectivity within a domain by sending
Layer 2 messages, known as Connectivity Check Messages (CCMs).
Note
Extreme Networks uses values defined in IEEE 802.1Q-2011 for the MAC addresses and
Ethernet type for CFM.
The following figure shows an example of hierarchical CFM domains.
Advanced Features
67
OAM
Figure 25: CFM Hierarchical Domains Example
Note
The arrows in the above figure indicate the span that CCM messages take, not the direction.
(See Figure 26: CFM UP and DOWN MEP at the Logical Level on page 69 for more
information on spans for CCM messages.) This has been removed until the missing xref can
be fixed.
To achieve this hierarchical connectivity testing, create and configure the following entities:
• Maintenance domains, or domains
• Maintenance domain (MD) level; a unique hierarchical numeric value for each domain
• Maintenance associations (MAs)
• Maintenance points (MPs) and maintenance end points (MEPS), which are one of the following
types:
• UP MEPs
• DOWN MEPs
• Maintenance intermediate points (MIPs)
Note
The CFM filter function (CFF) is no longer supported from ExtremeXOS 12.1. The functionality
of CFF is implicitly performed by MEPs.
An UP MEP sends CFM frames toward the frame filtering entity, which forwards the frames to all other
ports of a service instance other than the port on which the UP MEP is configured. This is similar to how
the frame filtering entity forwards a normal data frame, taking into account the port's STP state. For an
UP MEP, a CFM frame exits from a port if only if the STP state of the port is in the forwarding state.
A DOWN MEP sends CFM frames directly to the physical medium without considering the port STP
state. For a DOWN MEP, a CFM frame exits from a port even if the port STP state is in blocking state.
The following figure shows the concept of UP and DOWN MEP at logical level:
Advanced Features
68
OAM
Figure 26: CFM UP and DOWN MEP at the Logical Level
You must have at least one MP on an intermediate switch in your domain. Ensure that you map and
configure all ports in your domain carefully, especially the UP MEPs and the DOWN MEPs. If these are
incorrectly configured, the CCMs are sent in the wrong direction in your network, and you will not be
able to test the connectivity within the domain.
You can have up to eight domains on an Extreme Networks switch. A domain is the network or part of
the network for which faults are to be managed; it is that section where you are monitoring Layer 2
connectivity. A domain is intended to be fully connected internally.
Note
Domains may cross VR boundaries; domains are not virtual router-aware.
You assign each domain an MD level, which functions in a hierarchy for forwarding CFM messages. The
MD levels are from 0 to 7. The highest number is superior in the CFM hierarchy.
The IEEE standard 802.1Q-2011 recommends assigning different MD levels to different domains for
different network users, as follows:
• 5 to 7 for end users
• 3 and 4 for Internet service providers (ISPs)
• 0 to 3 for operators (entities carrying the information for the ISPs)
All CFM messages with a superior MD level (numerically higher) pass throughout domains with an
inferior MD level (numerically lower). CFM messages with an inferior MD level are not forwarded to
Advanced Features
69
OAM
domains with a superior MD level. Refer to the following table for an illustration of domains with
hierarchical MD levels.
Table 6: MD Levels and Recommended Use
MD level
0
1
2
3
Use
Operator
Superiority
Most inferior < ----- Inferior / Superior ----- >
4
Service provider
5
6
7
Customer
Most
superior
Within a given domain, you create maintenance associations (MAs). Extreme Networks’
implementation of CFM associates MAs with service instances (a service instance can be a VLAN,
VMAN, BVLAN, or SVLAN). All of the ports in that VLAN service instance are now in that MA and its
associated domain. In general, you should configure one MIP on each intermediate switch in the domain
and a MEP on every edge switch.
Each MA associates with one service instance, and a service instance can be associated with more than
one MA. The MA is unique within the domain. One switch can have 8 domains, 128 ports, and 256
associations (see Supported Instances for CFM).
Note
You cannot associate the Management VLAN with an MA or a domain.
You assign the MPs to ports: UP MEPs, DOWN MEPs, and MIPs. These various MPs filter or forward the
CFM messages to test the connectivity of your network.
Each configured MEP periodically sends out a Layer 2 multicast or unicast CCM message.
The destination MAC address in the CCM frame is from a multicast MAC address range that is reserved
for CFM messages. Each MEP must have a MEP ID that is unique within the MA. The MEPs send the CCM
messages differently, depending on the configuration, as follows:
• The DOWN MEPs sends out a single CCM message.
• The UP MEPs potentially sends the CCM message to all ports on the service instance (MA)—except
the sending port—depending on the MPs configured on the outgoing ports.
Note
Ensure that you configured the UP and DOWN MEPs correctly, or the CCMs will flow in the
wrong direction through the domain and not allow connectivity testing.
MIPs define intermediate points within a domain. MIPs relay the CCM messages to the next MIP or MEP
in the domain.
You configure the time interval for each MEP to send a CCM. We recommend setting this interval for at
least one second. Each MEP also makes a note of what port and what time it received a CCM. This
information is stored in the CCM database.
Each CCM has a time-to-live (TTL) value also noted for that message. This TTL interval is 3.5 times the
CCM transmission interval you configured on the switch that is originating the CCM. After the TTL
expires, the connectivity is considered broken, and the system sends a message to the log. One
Advanced Features
70
OAM
important result of the continual transmission of CCM frames is that the MAC address of the originating
MEP is known to all MPs in the association.
Note
All MEPs in an MA must be configured with the same CCM transmission interval.
The MD values are from 0 to 7; in the hierarchy, the MD level of 0 is lowest and 7 is highest.
Not all combinations of MPs are allowed on the same port within an MA; only the following
combinations can be on the same port within an MA:
• UP MEP and MIP
• DOWN MEP with neither UP MEP nor MIP
CFM protocol imposes the following MP restrictions within an MA on a switch:
• MA can have either up MEP or down MEP and not both.
• MA can have multiple Down MEPs.
• Only one Up MEP per MA.
• MA can have both up MEP and MIP.
• MA cannot have MIP if down MEP is present.
• Down MEPs on regular ports are created in hardware for all CCM intervals 3.3 msec–600000 sec on
Summit X460, E4G-400, and E4G-200.
• Up MEPs and MEPs on LAG ports are created in software with CCM intervals 100 msec–600000 sec
on all platforms.
• Dynamic Remote MEP learning is not supported for the MEPs created in hardware. You must
explicitly create static Remote MEPs.
• Sender-Id-IP Address cannot be configured for the MEPs created in hardware.
• Unicast CCM transmission is not supported by the MEPs created in hardware.
• Domain name format should be of string type to create any MEPs in hardware in that domain.
• The CCM transmission state is disabled by default for the MEPs created in hardware by the CFM
user interface.
• The CCM transmission state is enabled by default for the MEPs created in hardware by CFM clients
like ERPS.
• The hardware Remote MEP status appears in show cfm detail. It is also forwarded to the client if
created by a client like ERPS.
• CFM objects like domain, association, MEP, Remote MEP created by a client are not saved by dot1ag.
Note
An MA can have an UP MEP in one switch and a DOWN MEP on another switch for the same
MA.
Ping and Traceroute
When operators see a connectivity fault message from CCM in the system log, they can send a
loopback message (LBM) or a link trace message (LTM).
These are also referred to as a Layer 2 ping or a traceroute message. You can send with an LBM or an
LTM only from an MEP (either UP or DOWN).
Advanced Features
71
OAM
You can only send a ping from a MEP, and you ping to the unique system MAC address on the switch
you are testing connectivity to. The operator sends out a unicast LBM, and the first MIP or MEP on the
switch with the destination MAC address matching the embedded MAC address replies with an LBR
(loopback reply).
You can only send a traceroute (LTM) from a MEP. You send the traceroute to the unique system MAC
address on the switch to which you are testing connectivity. The system sends out an LTM to the
special multicast address. If the destination address is not present in the FDB, the LTM is flooded on all
the ports in the MIP node. Each MIP in the path passes the frame only in the direction of the path and
sends a link trace reply (LTR) message back to the originating with information that the LTM passed.
The traceroute command displays every MIP along the path (see traceroute mac port ).
Supported Instances for CFM
The following table displays the CFM support in ExtremeXOS.
Table 7: ExtremeXOS CFM Support
1
Item
Limit
Notes
Domains
8
Per switch; one for each MD level
Associations (MAs)
256
Per switch
UP MEPs
32 on Summit Family switches,
SummitStack, E4G-200, E4G-400,
BDx8, and BlackDiamond 8000
series modules.
Per switch
DOWN MEPs
256 hardware-placed MEPs 1 on
Per switch
Summit series X460, E4G-400,
E4G-200 (non-load shared ports)
32 on Summit series X460,
E4G-400, E4G-200 (load shared
ports)
32 on other Summit family
switches, BDx8, and BlackDiamond
8000 series
MIPs
32 on Summit Family switches,
SummitStack, BDx8, and
BlackDiamond 8000 series
modules.
Per switch
Total CFM ports
128
Per switch; total number of all ports for all
service instances assigned to an MA (see
command for ports configured for CFM)
Entries in the CCM database
2000
Number of remote end points stored in a
CCM database on each MEP; 64 end points
per MEP (additional CCMs discarded after
this limit is reached)
RMEPs need to be explicitly configured for hardware MEPs. Unlike software MEPs, hardware MEPs do not support
dynamic RMEP learning.
Advanced Features
72
OAM
Table 7: ExtremeXOS CFM Support (continued)
Item
Limit
Notes
CFM Segments
1000
Maximum number of CFM segments for Y.
1731.
CFM Groups
1000
Maximum number of CFM groups.
Note
The total number of CFM ports is a guideline, not a limit enforced by the system.
CFM Groups
Loop detection protocols like EAPS/ERPS want to depend upon CFM to detect link status for faster
failover recovery.
They register with LMEP and RMEP objects created by CFM in order to receive the link status event
notifications to take the necessary action.
Currently LMEP is identified with domain, association, port, MEPId quadruples. And RMEP is identified
with domain, association, LMEP, RMEPId quadruples. Each LMEP can be tied up to multiple RMEPs. So
applications need to configure domain, association, LMEP and RMEPs through a client/server interface.
To simplify this, CFM provides a simple API to client applications to register/deregister CFM with a
specified string name. The string name can be identified as a CFM group that binds an LMEP to multiple
RMEPs. The group name is unique across the switch. Each application can create its own group for a
required LMEP/RMEP combination.
You can associate a group to each LMEP created on a port. There exists a one-to-one relationship
between LMEP-port-group. Whenever CFM stops receiving CCMs on this port, it informs a group
DOWN event to registered clients like ERPS/EAPS. Whenever CFM starts receiving the CCMs again on
this port, a group UP event is sent to registered clients.
Configuring CFM
To configure CFM, create a maintenance domain and assign it a unique MD level. Next, associate MAs
with the specified domain and assign MPs within that MA. Optionally, you can configure the
transmission interval for the CCMs, destination MAC type for an MA and remote MEPs statically in an
MA.
If a MEP fails to receive a CCM before the last advertised TTL value expires, the system logs a message.
After the network administrator sees the system log message, he can send a Layer 2 ping and/or a
traceroute message to isolate the fault.
Note
CFM does not use ACL; there are no additional ACL entries present for CFM in the show
access-list dynamic command output.
Advanced Features
73
OAM
ExtremeXOS 15.5 provides support for transmitting and receiving ITU-T Y.1731 CCMs. The main
difference between IEEE 802.1ag and ITU-T Y.1731 CCMs is between the MAID and MEG ID formats in
CCMs:
•
•
•
•
•
•
MAID ---- MA (format + length + name) with/without MD (format + length +name) details.
MEG ID ---- MEG (format + length + name) without MD details.
MA is referred to as MEG in Y.1731 and both are same.
MA assumes four formats (string/integer/vpn-id/vlan-id) for its name.
MEG assumes ICC format which is a combination of ICC (6 bytes) + organization specific UMC (6
bytes).
To support Y.1731 CCMs, an additional name format for MEG name is added for association.
Creating Maintenance Domains
You can create maintenance domains (MDs), or domains, and assign a unique MD level at that time.
Available MD levels are numbered from 0 to 7. Higher numerical values are superior MD levels in the
CFM hierarchy. Each switch can have a total of eight domains, each with a unique MD level.
You can name domains using any one of the following three formats:
• Simple string—Use an alphanumeric character string with a maximum of 43 characters.
• Domain name server (DNS) name—Use an alphanumeric character string with a maximum of 43
characters.
• MAC address plus 2-octet integer—Use a MAC address and a 2-octet integer. The display format is
XX.XX.XX.XX.XX.XX.YYY, where X is the MAC address, and Y is the 2-octet integer. For example, a
domain name in this format using 123 as the 16-bit unsigned integer appears as follows:
00:11:22:33:44:55.123.
Note
Whatever convention you choose, you must use that same format throughout the entire
domain.
The CFM messages carry the domain name, so the name and naming format must be identical to be
understood throughout the domain. You can, however, use different naming conventions on different
domains on one switch (up to eight domains allowed on one switch). User-created CFM names are not
case sensitive.
•
To create a domain and assign an MD level using the DNS convention, use the following command:.
create cfm domain dns name md-level level
•
To create a domain and assign an MD level using the MAC address convention, use the following
command:.
create cfm domain mac mac-addr int md-level level
•
Although you assign an MD level to the domain when you create that domain, you can change the
MD level on an existing domain by running:
configure cfm domain domain_name md-level level
•
To delete a domain, use the following command:
delete cfm domain domain
Advanced Features
74
OAM
Creating and Associating MAs
Within a given domain, you can associate maintenance associations (MAs). Extreme Networks’
implementation of CFM associates MAs with service instances. All of the ports in that service instance
are now in that MA and its associated domain.
Each MA associates with one service instance, and each service instance may associate with more than
one MA; you can configure more than one MAs in any one domain.
Like the domains, ExtremeXOS supports multiple formats for naming the MA. The following formats are
supported for naming the MAs:
• Character string
• 2-octet integer
• RFC 2685 VPN
• VLAN ID
•
To add an MA to a domain using the character string format, use the following command:
configure cfm domain domain_name add association string name [vlan vlan_name|
vman vman_name]
•
To add an MA to a domain using the 2-octet integer format, use the following command:
configure cfm domain domain_name add association integer int [vlan vlan_name|
vman vman_name]
•
To add an MA to a domain using the RFC 2685 VPN ID format, use the following command:
configure cfm domain domain_name add association vpn-id oui oui index index
[vlan vlan_name|vman vman_name]
•
To add an MA to a domain using the VLAN ID format, use the following command:
configure cfm domain domain_name add association vlan-id vlanid [vlan
vlan_name|vman vman_name]
•
To delete an MA from a domain, use the following command:
configure cfm domain domain_name delete association association_name
In addition to supporting multicast destination MAC address for CCM and LTM frames specified by
the 802.1ag standard, ExtremeXOS CFM supports the use of a unicast destination address for CCM
and LTM frames.
•
This allows the support of a CFM operation in a network where use of multicast address is
prohibited.
To configure the destination MAC address type for an MA, use the following command:
configure cfm domain domain-name association association_name destination-mactype [unicast | multicast]
•
Use the following command to add a remote MEP to an MA statically:
configure cfm domain domain-name association association_name add remote-mep
mepid { mac-address mac_address }
•
ExtremeXOS CFM supports configuring remote MEPs statically for CFM operation where dynamic
discovery of MEPs in an MA using multicast address is prohibited.
To delete a remote MEP from an MA, use the following command:
Advanced Features
75
OAM
configure cfm domain domain-name association association_name delete remotemep mepid
•
To configure a remote MEP MAC address, use the following command:
configure cfm domain domain-name association association_name remote-mep mepid
mac-address mac_address
Creating MPs and the CCM Transmission Interval
Within an MA, you configure the following MPs:
•
•
Maintenance end points (MEPs), which are one of the following types:
• UP MEPs—transmit CCMs, and maintain CCM database.
• DOWN MEPs—transmit CCMs, and maintain CCM database.
Maintenance intermediate points (MIPs)—pass CCMs through.
Each MEP must have an ID that is unique for that MEP throughout the MA.
•
To configure UP and DOWN MEPs and its unique MEP ID, use the following command:
configure cfm domain domain_nameassociationassociation_name [portsport_listadd
[[end-point [up|down] mepid { groupgroup_name } ] | [intermediate-point]]
•
To change the MEP ID on an existing MEP, use the following command:
configure cfm domain domain-nameassociationassociation_nameportsport_listendpoint [up | down] mepidmepid
•
To delete UP and DOWN MEPs, use the following command:
configure cfm domain domain_nameassociationassociation_name [portsport_list
delete [[end-point [up|down]] | [intermediate-point] ] ]
•
To configure a MIP, use the following command:
configure cfm domain domain_nameassociationassociation_name [portsport_listadd
[[end-point [up|down] mepid { groupgroup_name } ] | [intermediate-point]]
•
To delete a MIP, use the following command:
configure cfm domain domain_nameassociationassociation_name
[portsport_listdelete [[end-point [up|down]] | [intermediate-point] ] ]
•
To configure the transmission interval for the MEP to send CCMs, use the following command:
configure cfm domain domain_nameassociationassociation_name
{portsport_listend-point [up | down]} transmit-interval [3|10|100|1000|10000|
60000|600000]
•
To unconfigure the transmission interval for the MEP to send CCMs and return it to the default, use
the following command:
unconfigure cfm domain domain_nameassociationassociation_name
{portsport_listend-point [up | down]} transmit-interval
•
To enable or disable a MEP, use the following command:
configure cfm domain domain_nameassociationassociation_nameportsport_listendpoint [up | down] [enable | disable]
Configuring EAPS for CFM Support
Advanced Features
76
OAM
Assigning MEP Group Names to New MEP
To assign MEP Group name when creating a MEP, use the following command:
configure cfm domain domain_name association association_name [ports port_list
add [[end-point [up|down] mepid {group group_name} ] |[intermediate-point]]
Assign MEP Group Name to Existing MEP
To assign a MEP Group name to an existing MEP, use the following command:
configure cfm domain domain_name association association_name ports port_list
end-point [up|down] [add|delete] group group_name
Add a RMEP to MEP Group
To add specific RMEPs for a MEP Group to monitor, use the following command:
configure cfm group group_name [add|delete] rmep mepid
Monitoring CFM in EAPS
Displaying MEP Groups
To display MEP groups, use the following command:
show cfm groups {group_name}
X480-48t.1 # sh cfm groups
Group : eapsCfmGrp1
Status : UP
Local MEP
: 11
port : 41
Remote MEPs
: 10
Client(s)
: eaps
Domain
: MD1
Association
: MD1v2
Group : eapsCfmGrp2
Status : UP
Local MEP
: 12
port : 31
Remote MEPs
: 13
Client(s)
: eaps
Domain
: MD1
Association
: MD1v2
Executing Layer 2 Ping and Traceroute Messages
If the system logs a missed CCM message, the operator can use Layer 2 ping and traceroute messages
to isolate the fault. (See Ping and Traceroute for information on how each MP handles these messages.)
Note
You must have all the CFM parameters configured on your network before issuing the ping
and traceroute messages.
Advanced Features
77
OAM
•
To send a Layer 2 ping, use the following command:
ping mac mac port port {domain} domain_name {association} association_name
•
To send a Link Trace Message (LTM) and receive information on the path, use the following
command:
traceroute mac mac {up-end-point} port port {domain} domain_name {association}
association_name {ttl ttl}
Displaying CFM
To verify your CFM configuration, you can display the current CFM configuration using the show cfm
command.
The information this command displays includes the total ports configured for CFM, the domain names
and MD levels, the MAs and associated service instances, and the UP and DOWN MEPs.
To display the CCM database for each MEP, use the show cfm detail command.
CFM Example
As shown in the following figure, this example assumes a simple network and assumes that CFM is
configured on the access switches, as well as the necessary VMANs configured with the ports added.
This example shows a VMAN associated with two maintenance domains and two different MAs. UP
MEPs are configured for an MA with MD level 6 and DOWN MEPs are configured for an MA with MD
level 3.
Figure 27: CFM Configuration Example
•
Configure switch 1 for this example.
create cfm domain string cust-xyz-d6 md-level 6
configure cfm domain cust-xyz-d6 add association string cust-xyz-d6-m100
vman m100
configure cfm domain cust-xyz-d6 association cust-xyz-d6-m100 port 1:1 add
end-point up 10
configure cfm domain cust-xyz-d6 association cust-xyz-d6-m100 port 2:1 add
intermediate-point
create cfm domain string core-d3 md-level 3
configure cfm domain core-d3 add association string core-d3-m100 vman m100
Advanced Features
78
OAM
configure cfm domain core-d3 association core-d3-m100 port 2:1 add endpoint down 10
•
Configure switch 2 for this example.
create cfm domain string core-d3 md-level 3
configure cfm domain core-d3 add association string core-d3-m100 vman m100
configure cfm domain core-d3 association core-d3-m100 port 2:1 add
intermediate-point
configure cfm domain core-d3 association core-d3-m100 port 2:2 add
intermediate-point
•
Configure switch 3 for this example.
create cfm domain string cust-xyz-d6 md-level 6
configure cfm domain cust-xyz-d6 add association string cust-xyz-d6-m100
vman m100
configure cfm domain cust-xyz-d6 association cust-xyz-d6-m100 port 1:1 add
end-point up 20
configure cfm domain cust-xyz-d6 association cust-xyz-d6-m100 port 2:1 add
intermediate-point
create cfm domain string core-d3 md-level 3
configure cfm domain core-d3 add association string core-d3-m100 vman m100
configure cfm domain core-d3 association core-d3-m100 port 2:1 add endpoint down 20
•
To display the group database, use the following command:
show cfm groups
Y.1731--Compliant Performance Monitoring
Compliant performance monitoring is based on the ITU-T Y.1731 standard and deals with the Ethernet
Delay Measurement (ETH-DM) function and Ethernet Frame-Loss Measurement (ETH-LM).
Frame-Delay Measurement
ExtremeXOS software supports:
•
•
•
Two-way delay measurement—Delay Measurement Message (DMM) and Delay Measurement Reply
(DMR).
Continuous (proactive) measurement of frame delay and frame delay variation.
On-demand measurement of frame delay and frame delay variation.
By default, DMM is not enabled. You must explicitly enable the DMM transmission for a CFM segment,
either as continuous or on-demand mode.
A network interface is considered attached to a subnetwork. The term "segment" is used to refer to
such a subnetwork, whether it be an Ethernet LAN, a ring, a WAN link, or even an SDH virtual circuit.
Frame-Delay measurement is done between two specific end points within an administrative domain.
Frame delay and frame delay variation measurements are performed in a maintenance association end
Advanced Features
79
OAM
point (MEP) by sending and receiving periodic frames with ETH-DM information to and from the peer
end point during the diagnostic interval.
When a CFM segment is enabled to generate frames with ETH-DM information, it periodically sends
frames with ETH-DM information to its peer in the same maintenance association (MA) and expects to
receive frames with ETH-DM information from its peer in the same MA.
The following list offers specific configuration information that is required by a peer to support ETHDM:
• Maintenance domain (MD) level—The MD level at which the peer exists.
• Priority—The priority of the frames with ETH-DM information.
• Drop eligibility—Frames with ETH-DM information that are always marked as drop ineligible.
• Transmission rate.
• Total transmit interval.
A node transmits frames with ETH-DM information with the following information element:
•
•
TxTimeStampf: Timestamp at the transmission time of the ETH-DM frame.
RxTimeStampb: Timestamp at which the switch receives the DMR back.
Whenever a valid DMM frame is received by the peer, a DMR frame is generated and transmitted to
the requesting node.
•
A DMM frame with a valid MD level and a destination MAC address equal to the receiving node’s
MAC address is considered to be a valid DMM frame. Every field in the DMM frame is copied to the
DMR frame with the following exceptions:
• The source and destination MAC addressed are swapped.
• The OpCode field is changed from DMM to DMR.
The switch makes two-way frame delay variation measurements based on its ability to calculate the
difference between two subsequent two-way frame delay measurements.
To allow a more precise two-way frame delay measurement, the peer replying to the frame with ETHDM request information may include two additional timestamps in the ETH-DM reply information:
• RxTimeStampf—Timestamp at the time of receiving a frame with ETH-DM request information
• TxTimeStampb—Timestamp at the time of transmitting a frame with ETH-DM reply information
Here the frame delay is calculated by the peer that receives the DMR as follows:
• Frame Delay = (RxTimeStampb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)
The following figure describes the DMM and DMR message flows between two end points.
Advanced Features
80
OAM
Figure 28: Two-Way Frame Delay and Frame Delay Variance Measurement
The PDUs used to measure frame delay and frame delay variation are the DMM and the DMR PDUs
where DMM is initiated from a node as a request to its peer and DMR is the reply from the peer.
Note
When Summit X460, E4G-200 series switches are running EXOS 15.1 or later firmware, the
down MEPs are performed in the hardware when configured on a normal port and the down
MEPs are performed in the software when configured on a LAG port and Up MEPs are
performed in the software for all the ports. When E4G-200 series switch running EXOS 15.1 or
later firmware, the measurement (time stamping) of frame delay and loss measurements are
performed in the hardware. On all other ExtremeXOS-based platforms, time stamping is
always performed in the software.
If you try to enable the transmission for a CFM segment whose configuration is not complete, the
trigger is rejected and an error message similar to the following is given:
ERROR: CFM Configuration is not complete for segment "s1" to start transmission
Note
A CFM segment without a domain and an association is considered to be an incomplete
segment.
Upon enabling the transmission from a CFM segment, the segment transmits DMM frames, one at each
transmit-interval which is configured through the CLI. If the user enables on-demand transmission, the
segment transmits "X" number of DMMs and moves back to the disabled state, where "X" is the number
of frames specified by the user through the CLI.
For continuous transmission, the segment continues to transmit DMM frames until stopped by the user.
This transmission continues even after reboot for both continuous and on-demand mode. For ondemand transmission, the segment, which was enabled to transmit "X" number of frames, and is still
transmitting, starts transmitting again "X" number of frames after reboot, or MSM failover, or process
restart. The old statistics are not preserved for both continuous and on-demand mode for all the above
three scenarios.
Upon transmitting a DMM, the segment is expected to get a reply from the destination within the
specified time. If a reply is received after that time, that reply will be considered as a delayed one.
Advanced Features
81
OAM
If a reply is not received within the transmit-interval, that is, between two subsequent DMM
transmissions, then that frame is considered as lost. Once the percentage of the sum of lost and
delayed frames reaches the alarm threshold, an alarm is generated and the segment is moved to the
alarming state. This state is maintained until the percentage of valid replies reaches the clear threshold.
These alarm and clear states are maintained for a specified window, which holds a set of recent frames
and their corresponding delays.
Various times are recorded at the segment level during the transmission of DMM frames.
• Start time—Time at which the segment started the current transmission.
• Min delay time—Time at which the minimum delay occurred in the current transmission window.
• Max delay time—Time at which the maximum delay occurred in the current transmission window.
• Alarm time—The recent alarm time, if any, during the current transmission.
The mean delay and delay variance for the current window is also measured whenever the user polls
the segment statistics.
Frame-Loss Measurement
Frame-loss is measured by sending and receiving frames with frame-loss information between peer
maintenance end points (MEPs).
Frame-loss ratio is defined as a percentage of the number of service frames not delivered divided by
the total number of service frames during a defined time interval, where the number of service frames
not delivered is the difference between the number of service frames arriving at the ingress Ethernet
flow point and the number of service frames delivered at the egress Ethernet flow point in a point-topoint Ethernet connection (see the following figure).
Figure 29: Frame-Loss Ratio Formula
To support frame-loss measurement, a MEP requires the following configuration information:
• Maintenance domain (MD) level—MD level at which the MEP exists.
• Frame-loss measurement transmission period—time interval when frame-loss measurement frames
are sent.
• Priority—identifies the priority of the frames with frame-loss measurement information
(configurable per operation).
• Drop eligibility—frames with frame-loss measurement information are always marked as drop
ineligible (not necessarily configured).
A maintenance intermediate point (MIP) is transparent to frames with frame-loss measurement
information. Therefore MIPs do not require any information to support frame-loss measurement
functionality.
There are two frame-loss measurement methods:
Advanced Features
82
OAM
•
•
Dual-Ended Frame-Loss Measurement
Single-Ended Frame-Loss Measurements
Dual-Ended Frame-Loss Measurement
Dual-ended frame-loss measurement is a form of proactive OAM for performance monitoring and is
useful for fault management.
Note
ExtremeXOS does not support dual-ended frame-loss measurement.
MEPs send periodic dual-ended frames with frame-loss measurement information to peer MEPs in a
point-to-point MD. Each MEP terminates the dual-ended frames with frame-loss measurement
information and makes the near-end and far-end loss measurements. Near-end frame loss refers to
frame loss associated with ingress data frames, while far-end frame loss refers to frame loss associated
with egress data frames. This function is used for performance monitoring at the same priority level as
used for CCM.
The protocol data unit (PDU) for dual-ended frame-loss measurement information is Continuity Check
Message (CCM).
Single-Ended Frame-Loss Measurements
Single-ended frame-loss measurement facilitates on-demand OAM. MEPs carry out frame-loss
measurments by sending frames to peer MEPs with frame-loss measurement request information and
receiving frames with frame-loss measurement reply information.
The PDU for single-ended frame-loss measurement requests is Loss Measurement Message (LMM). The
PDU for single-ended frame-loss measurement reply is Loss Measurement Reply (LMR). The following
figure shows the transmission of LMM and LMR for frame-loss measurement.
Figure 30: Two-Way Frame-Loss Measurement
A MEP maintains two local counters for each peer MEP it is monitoring for frame-loss:
• TxFCl—in-profile data frames transmitted to the peer MEP.
• RxFCl—in-profile data frames received from the peer MEP.
Advanced Features
83
OAM
For an on-demand loss measurement, a MEP periodically transmits LMM frames with TxFCf (value of
the local TxFCl counter at the time of LMM frame transmission). Upon receiving a valid LMM frame, a
MEP sends an LMR frame to the requesting MEP. (Valid LMM frames have a valid MD level and a
destination MAC address equal to the receiving MEP's MAC address.)
An LMR frame contains the following values:
• TxFCf—TxFCf value copied from the LMM frame.
• RxFCf—RxFCl value when the LMM frame was received.
• TxFCb—TxFCl value when the LMR frame was transmitted.
Upon receiving an LMR frame, a MEP uses the following values to make near-end and far-end loss
measurements:
• Received LMR frame's TxFCf, RxFCf, and TxFCb values, and local counter RxFCl value at the time
this LMR frame was received. These values are represented as TxFCf[tc], RxFCf[tc], TxFCb[tc], and
RxFCl[tc]; where tc is the time the current reply frame was received.
• Previous LMR frame's TxFCf, RxFCf, and TxFCb values, and local counter RxFCl value at the time the
previous LMR frame was received. These values are represented as TxFCf[tp], RxFCf[tp],
TxFCb[tp], and RxFCl[tp],where tp is the time the previous reply frame was received.
Far-End Frame Loss = (TxFCf[tc] – TxFCf[tp]) – (RxFCf[tc] – RxFCf[tp])
Near-End Frame Loss = (TxFCb[tc] – TxFCb[tp]) – (RxFCl[tc] – RxFCl[tp])
Availability Time and Severly Errored Seconds (SES)
Frame loss is measured by sending and receiving frames with frame-loss information between peer
MEPs.
Each MEP performs frame-loss measurements which contribute to unavailable time. Since a
bidirectional service is defined as unavailable if either of the two directions is declared unavailable,
frame-loss measurement must facilitate each MEP to perform near-end and far-end frame loss
measurements.
Near-end frame loss refers to frame loss associated with ingress data frames, while far-end frame loss
refers to frame loss associated with egress data frames. Both near-end and far-end frame loss
measurements contribute to near-end severely errored seconds (near-end SES) and far-end severely
errored seconds (far-end SES) respectively, which together contribute to unavailable time.
A period of unavailable time begins at the onset of x consecutive Severely Errored Seconds (SES)
events. These x seconds are part of unavailable time. A new period of available time begins at the onset
of x consecutive non-SES events. These x seconds are part of available time.
A SES is declared when, during one measurement period, the number of frames lost exceeds a
threshold. ExtremeXOS logs the start and end time of the unavailable periods (see the following figure
from ITU-T G.7710).
Advanced Features
84
OAM
Figure 31: SES
Configuring a CFM Segment
Use the following commands to configure a CFM segment.
Some of these commands are optional and, if not configured, the default values are used. The following
table lists the default values for delay measurement for a CFM segment.
Table 8: Default Values for Delay Measurement for a CFM Segment
Configuration
Default Values
Transmit interval
10 seconds
Window
60 frames
Timeout
50 milliseconds
Alarm threshold
10%
Clear threshold
95%
Dot1p priority
6
The following table lists the default values for loss measurement for a CFM segment.
Table 9: Default Values for Loss Measurement for a CFM Segment
Configuration
Default Values
LMM Transmit interval
90 seconds
Dot1p priority
6
Window
1200 frames
SES threshold
0.01
Consecutive available count
4
Note
The statistics for a particular transmission are preserved until the user triggers the
transmission once again or if clear counters cfm segment is triggered from the CLI.
Advanced Features
85
OAM
Managing a CFM Segment
You can create, delete, add CFM segments.
• To create a CFM segment, use the following command:
create cfm segment segment_name destination mac_addr {copy
segment_name_to_copy}
•
To delete a CFM segment, use the following command:
delete cfm segment [segment_name | all]
•
To add a CFM domain to a CFM segment, use the following command:
configure cfm segment segment_name add domain domain_name association
association_name
•
To delete a CFM domain from a CFM segment, use the following command:
configure cfm segment segment_name delete domain association
•
To configure the transmission interval between two consecutive DMM or two consecutive LMM
frames, use the following command:
configure cfm segment segment_name {frame-delay | frame-loss} transmitinterval interval
•
The same transmit-interval is used for both delay and loss measurements.
To get separate values for delay and loss measurements, use the following command:
•
To configure the dot1p priority of a DMM frame, use the following command:
configure cfm segment frame-delay/frame-loss transmit interval interval
configure cfm segment segment_name frame-delay dot1p dot1p_priority
•
To configure the dot1p priority of a LMM frame, use the following command:
•
To configure the dot1p priority of the CFM segment, use the following command:
configure cfm segment segment_name frame-loss dot1p dot1p_priority
configure cfm segment segment_name dot1p dot1p_priority
•
The same priority is used for both delay and loss measurements.
To get separate values of priority for delay and loss measurements, use the following command:
configure cfm segment segment_name frame-delay dot1p dot1p_priority
configure cfm segment segment_name frame-loss dot1p dot1p_priority
•
To configure the alarm and clear threshold value for CFM segment, use the following command:
configure cfm segment segment_name [alarm-threshold | clear-threshold] value
•
To configure the window size to be used for calculating the threshold values, use the following
command:
configure cfm segment segment_name window size
•
The same window size is used for both delay and loss measurements.
To get separate values of window size for delay and loss measurements, use the following:
configure cfm segment segment_name frame-loss window window_size
configure cfm segment segment_name frame-delay window window_size
Advanced Features
86
OAM
•
To configure the window size of a DMM frame to be used for calculating the threshold values, use
the following command:
configure cfm segment segment_name frame-delay window window_size
•
To configure the window size of a LMM frame to be used for calculating the threshold values, use
the following command:
configure cfm segment segment_name frame-loss window window_size
•
To trigger DMM frames at the specified transmit interval, use the following command:
enable cfm segment frame-delay measurement segment_name mep mep_id [continuous
| count ] value
•
To disable the transmission of the DMM frames for a particular CFM segment, use the following
command:
disable cfm segment frame-delay measurement segment_name mep mep_id
•
To show the configuration and status of a specific CFM segment, use the following command:
show cfm segment {segment_name}
•
To show the configuration and status of a specific CFM segment doing delay measurement, use the
following command:
show cfm segment frame-delay {segment_name]}
•
To show the configuration and status of a specific CFM segment doing loss measurement, use the
following command:
show cfm segment frame-loss {segment_name]}
•
To display the frame delay statistics for the CFM segment, use the following command:
•
To configure the timeout value for a CFM segment, use the following command:
•
To add or delete the local MEP for a given CFM segment, use the following command:
show cfm segment frame-delay statistics {segment-name}
configure cfm segment segment_name timeout msec
configure cfm segment segment_name frame-loss [add|delete] mep mep_id
•
To set the percentage of frames lost in a measurement period so that it will be marked as SES
(severely errored second), use the following command:
configure cfm segment segment_name frame-loss ses-threshold percent
•
To set the number of consecutive measurements used to determine the availability status of a CFM
segment, use the following command:
configure cfm segment segment_name frame-loss consecutive frames
•
To start the transmission of LMM frames for the set transmit interval, use the following command:
enable cfm segment frame-loss measurement segment_name mep mep_id [continuous
| count frames]
Note
For the above command, If the the segment is not completely configured, frames are not
transmitted and an error occurs.
•
To stop the transmission of the LMM frames for a particular CFM segment, use the following
command:
Advanced Features
87
OAM
disable cfm segment frame-loss measurement segment_name mep mep_id
•
To display the frame loss or frame delay statistics for the CFM segment, use the following
command:
show cfm segment {{segment_name} | {frame-delay {segment_name}} | {frame-loss
{segment_name {mep mep_id}}}}
Note
Frame-loss measurements are not supported on platforms where the VLAN packet
statistics are not retrieved, and on up-meps.
Clearing CFM Information
•
To clear cfm segment counters, use the following commands:
clear counters cfm segment segment_name
clear counters cfm segment all
•
To clear cfm segment counters specific to DMM, use the following command:
clear counters cfm segment segment_name frame-delay
•
To clear cfm segment counters specific to LMM, use the following commands:
clear counters cfm segment segment_name frame-loss
clear counters cfm segment segment_name frame-loss mep mep_id
Y.1731 MIB Support
ExtremeXOS 15.5 supports Y.1731 performance measurement MIB defined by MEF - 36. The
performance monitoring process is made up of a number of performance monitoring instances, known
as performance monitoring (PM) sessions. A PM session can be initiated between two MEPs in a MEG
and be defined as either a loss measurement (LM) session or delay measurement (DM) session. The LM
session can be used to determine the performance metrics frame loss ratio, availability, and resiliency.
The DM session can be used to determine the performance metrics Frame Delay.
The MIB is divided into a number of different object groupings: the PM MIB MEP objects, PM MIB loss
measurement objects, PM MIB delay measurement objects, and SOAM PM notifications. The initial
implementation of MIB supports GET operations for Frame Loss& Frame Delay.
MIB Specific Data
•
•
•
•
A measurement interval of 15 min to be supported
Default message period/transmit-interval of LMMs is 1 sec (Min = 1sec in current CLI) * Default
message period/transmit-interval of DMMs is 100msec (Min = 1 sec in current CLI)
Repetition Time can be set to 0 which means that there is no gap between measurement intervals
Number of History measurement intervals can be 2-1000, though it expects at least 32
measurement intervals to be stored and 96 are recommended.
Advanced Features
88
OAM
•
•
Both DM and LM sessions are MEP to MEP sessions. The index of all the DM/LM tables includes MD,
MA, MEP table indices as well as the particular DM/LM session.
Currently DM sessions are not MEP-to MEP based but only segment based sessions. To support DM
tables in the MIB, changes are required in the current CLI & backend delay implementation.
Limitations
•
•
Currently we are storing a maximum of 1800 frames data for each LMM/DMM session. But to
support at least 2 history and 1 current measurement intervals, we need to store 2700 frames (if
message period is 1 sec, Repetition time is 0, measurement interval is 15 min) for each delay/loss
session.
Each frame’s data is about 60 bytes for LMM and which takes about 44 MB of memory for 288
sessions
EFM OAM--Unidirectional Link Fault Management
Unidirectional Link Fault Management
With EFM OAM, certain physical layers can support a limited unidirectional capability.
The ability to operate a link in a unidirectional mode for diagnostic purposes supports the maintenance
objective of failure detection and notification. Unidirectional OAM operation is not supported on some
legacy links but is supported on newer links such as 100BASE-X PCS, 1000BASE-X PCS, and 10GbE RS.
On technologies that support the feature, OAM PDUs can be transmitted across unidirectional links to
indicate fault information. To the higher layers, the link is still failed in both directions, but to the OAM
layer, some communication capabilities exist. The distinction between a unidirectional link and a normal
link is shown in the following figure.
Figure 32: Normal Link and Unidirectional Operation
Advanced Features
89
OAM
You can enable unidirectional link fault detection and notification on individual ports with CLI
commands. This allows appropriate register settings to transmit OAM PDUs even on a link that has a
slowly deteriorating quality receive path or no receive path at all. Then, when a link is not receiving a
signal from its peer at the physical layer (for example, if the peer’s laser is malfunctioning), the local
entity can set a flag in an OAM PDU to let the peer know that its transmit path is inoperable.
The operation of OAM on an Ethernet interface does not adversely affect data traffic because OAM is a
slow protocol with very limited bandwidth potential, and it is not required for normal link operation. By
utilizing the slow protocol MAC address, OAM frames are intercepted by the MAC sub layer and cannot
propagate across multiple hops in an Ethernet network. This implementation assures that OAM PDUs
affect only the operation of the OAM protocol itself and not user data traffic.
The IEEE 802.3ah standard defines fault notifications based on one-second timers. But by sending
triggered OAM PDUs on detecting link down/local fault rather that waiting to send on periodic PDUs,
failure detection is less than one second can be achieved, thereby accelerating fault recovery and
network restoration.
EFM OAM uses standard length Ethernet frames within the normal frame length of 64 to 1518 bytes as
PDUs for their operation. The following table describes the fields of OAM PDUs.
Table 10: OAM PDU Fields
Field
Octets
Description
Value
Destination Address
6
Slow protocol multicast address
01:80:C2:00:00:02
Source Address
6
Port’s individual MAC address
Switch MAC
Length/Type
2
Slow protocol type
0x8809
Subtype
1
Identifies specific slow protocol
0x03
Flags
2
Contains status bits
see the following figure
Code
1
Identifies OAM PDU type
0x00 (Information TLV)
Data/Pad
42-1496
OAM PDU data
0x00 (END of TLV)
FCS
4
Frame check sequence
Configuring Unidirectional Link Fault Management
To configure unidirectional link fault management on a port or ports, use the following command:
enable ethernet oam ports [port_list | all] link-fault-management
To clear the counters on a configured port, use the following command:
clear ethernet oam {ports [port_list} counters
To unconfigure unidirectional link fault management, use the following command:
disable ethernet oam ports [port_list | all] link-fault-management
To display the Ethernet OAM settings, use the following command:
Advanced Features
90
OAM
show ethernet oam {ports [port_list} {detail}
When configured, the following behavior on the port is observed:
•
•
•
A log indicates that traffic on the port is blocked.
All received traffic on that port is blocked except for Ethernet OAM PDUs.
To higher layers, a failure is reported as a link down but OAM can use the link to send OAM traffic.
Bidirectional Forwarding Detection (BFD)
BFD Overview
Bidirectional Forwarding Detection (BFD) is a hello protocol that provides the rapid detection of
failures in the path and informs the clients (routing protocols) to initiate the route convergence.
It is independent of media, routing protocols, and data protocols. BFD helps in the separation of
forwarding plane connectivity and control plane connectivity.
Different routing protocol hello mechanisms operate in variable rates of detection, but BFD detects the
forwarding path failures at a uniform rate, thus allowing for easier network profiling and planning, and
consistent and predictable re-convergence time.
The following figure shows a BFD topology.
Figure 33: BFD Topology
The routing protocols first learn the neighbor and make entries in the forwarding table. Then protocols
can register the neighbor address with BFD and ask to monitor the status of the path. BFD establishes
the session with a remote BFD and monitors the path status.
You can configure detection multipliers and TX and RX intervals on a directly connected interface
(VLAN).
• The detection multiplier signifies the number of BFD packets the BFD server waits for after which a
timeout is declared.
• The receive interval is the interval at which the BFD server is ready to receive packets.
Advanced Features
91
OAM
•
The transmit interval is the interval at which the BFD server is ready to transmit packets.
For example, when two nodes, A and B, initiate a BFD session between them, a negotiation about the
receive and transmit intervals occurs.
The receive interval of node A is calculated as the maximum of the configured receive interval of node
A and the configured transmit interval of node B. The same applies to node B.
If multiple clients ask for the same neighbor on the same interface, then a single BFD session is
established between the peers.
The following figure shows the behavior when a failure occurs.
Figure 34: BFD Failure Detection
BFD detects the failure first and then informs the registered clients about the neighbors.
BFD operates in an asynchronous mode in which systems periodically send BFD control packets to one
another. If a number of those packets in a row are not received by the other system, the session is
declared to be down.
Simple password authentication can be included in the control packet to avoid spoofing.
This feature is available on all platforms.
Note
BFD can be used to protect IPv4 & IPv6 static routes, OSPFv2 & OSPFv3 interfaces and MPLS
interfaces. For more information, see Configuring Static Routes, BFD for OSPF, or refer to
Managing the MPLS BFD Client.
Limitations
The following limitations apply to BFD in this release:
•
•
Direct connection (single hop) networks only are supported.
OSPF, MPLS and static routes act as BFD clients.
Advanced Features
92
OAM
•
•
•
Hitless failover is supported.
The echo function is not supported.
BFD protocol has been implemented in software. The number of sessions handled by BFD at
minimal timers (less than 100ms) varies depending on platform type and processing load (which is
effected by other protocols being enabled, or other system conditions such as software
forwarding).
Configuring BFD
You can enable, disable, configure, and unconfigure BFD.
• To enable or disable BFD, use the following command:
[enable | disable] bfd vlan vlan_name
•
To configure the detection multipliers and TX and RX intervals, use the following command:
configure bfd vlan vlan_name [{detection-multiplier multiplier} {receiveinterval rx_interval} {transmit-interval tx_interval}]
•
To specify either authentication using a simple password or no authentication, use the following
command:
configure bfd vlan vlan_name authentication [none | simple-password
{encrypted} password]]
•
To unconfigure BFD, use the following command:
unconfigure bfd vlan vlan_name
Displaying BFD Information
The following commands display information regarding BFD configuration and process.
• To display information on BFD sessions, use the following command:
show bfd
•
To display information on BFD global counters, use the following command:
show bfd counters
•
To display information on BFD session counters, use the following command:
show bfd session counters vr all
•
To display the configuration of a specific interface or those specific counters, use the following
command:
show bfd vlan {vlan_name}
•
To display the counters of a specific interface, use the following command:
show bfd vlan {vlan_name} counters
•
To display the session status of a particular client, use the following command:
show bfd session client [mpls | ospf {ipv4 | ipv6} | static {ipv4 | ipv6}] {vr
[vrname | all]}
•
To display the session status information for all VRs, use the following command:
Advanced Features
93
OAM
show bfd session vr all
•
To display session status information in detail for all VRs, use the following command:
show bfd session {ipv4| ipv6} detail vr all
Clearing BFD Information
To clear global, session, or interface counters, use the following command:
clear counters bfd {session | interface}
BFD MIB Table Support
ExtremeXOS Release 15.5 supports read-only for all BFD MIB tables, global objects, and supports BFD
notifications as well. BFD-MIB implementation is based on draft-ietf-bfd-mib-14, and draft-ietf-bfd-tcmib-02. Currently, the BFD MIB is kept under the enterprise MIB in EXOS implementation.
The SET operation is supported only for MIB object 'bfdSessNotificationsEnable' (to control up/down
traps). The default value for this object is disabled state. No notification is sent in disabled state. Thus,
the SET operation is also supported for this MIB object in order to control the emission of traps.
BFD Session Up/Down Traps
BFD has two traps, one for notifying that the session moved to the UP state, and the other trap for
notifying that the session moved to DOWN state. To reduce the number of traps sent to NMS, a single
trap is generated to combine the status changes of multiple sessions if the sessions have contiguous
session IDs and multiple sessions move to either the UP or DOWN state in the same window of time.
However, status changes of different types (UP & DOWN), will not be mixed in single trap. The window
of time to combine the traps can be configured using the CLI command configure snmp traps
batch-delay bfd.
For example, if sessions with session IDs 1, 2, 3, 4, and 5 are moving to the UP state in the same window
of time, then a single trap is sent with low range index 1 and high range index 5. As a second example,
after all sessions moved to the UP state, session ID 2 goes DOWN and comes back UP before
generating the first trap. In this case also, the first trap which is the UP trap, is set to include all sessions.
Then, the second trap would be the DOWN trap for session ID 2, and finally the third trap would be the
UP trap again for session ID 2. Thus, events are not missed or reordered.
NMS relates traps to sessions using only the session index which is provided in traps. It is necessary that
the session index does not change until NMS retrieves session details via GET requests. To achieve this,
the session will be retained for fifteen minutes after deletion is initiated by the BFD client (control
protocol). During this period transmission and reception of BFD control packets will be stopped. If BFD
protection is requested for the same destination again within this period, the same session index is
reused. With this change, NMS can also have good history of the session to a particular destination.
Configuring SNMP Traps for BFD
To enable snmp traps for bfd:
Advanced Features
94
OAM
enable snmp traps bfd {session-down | session-up}
To disable snmp traps for bfd:
disable snmp traps bfd {session-down | session-up}
To configure batch delay for sending the traps:
configure snmp traps batch-delay bfd {none | <delay>}
To display the configuration:
show snmp traps bfd
Note
SNMP traps for BFD are disabled by default for both session-down and session-up.
Configuration Example
Figure 35: BFD Configuration Example
Consider the network segment like above, wherein two routers R1 and R2 are connected via an L2
switch. Following is the list of commands to configure BFD protection for static routes.
Router R1:
1
Create vlan and configure IP address.
create vlan v1 tag 100
configure vlan v1 add port 2 tagged
configure vlan v1 ipaddress 10.0.0.1/24 2
2 Create BFD session to the next-hop which is being monitored.
enable iproute bfd 10.0.0.2 vr VR-Default
Advanced Features
95
5 Data Center Solutions
Data Center Overview
Managing the DCBX Feature
Managing the XNV Feature, VM Tracking
Managing Direct Attach to Support VEPA
Managing the FIP Snooping Feature
This chapter provides information about Extreme Network's Data Center Solutions. It provides an
overview of data centers and provides information about how to configure and manage data center
features, including DCBX, XNV, VM Tracking, Direct Attach to support VEPA, and FIP Snooping.
Data Center Overview
Typical data centers support multiple Virtual Machines (VMs) on a single server. These VMs usually
require network connectivity to provide their services to network users and to other VMs. The following
sections introduce ExtremeXOS software features that support VM network connectivity:
Note
For additional information on using ExtremeXOS features to implement Data Center Bridging,
see the application note titled Enhanced Transmission Selection (ETS) Deployment and
Configuration for ExtremeXOS on the Extreme Networks Website.
Introduction to Data Center Bridging
Data Center Bridging (DCB) is a set of IEEE 802.1Q extensions to standard Ethernet, that provide an
operational framework for unifying Local Area Networks (LAN), Storage Area Networks (SAN) and
Inter-Process Communication (IPC) traffic between switches and endpoints onto a single transport
layer.
Data Center Bridging Exchange Protocol
The Data Center Bridging eXchange (DCBX) protocol is used by Data Center Bridging (DCB) devices to
exchange DCB configuration information with directly connected peers. In an ExtremeXOS enabled
switch, the switch uses DCBX to advertise its DCB configuration to end stations. The end stations can
then configure themselves to use the switch DCB services. If the peers do not support a common
configuration for one or more features, the switch generates messages to alert network management.
The switch does not accept configuration change requests from end stations.
The DCBX protocol advertises the following types of information:
Advanced Features
96
Data Center Solutions
•
•
•
•
DCBX version information, so that the peers can negotiate a common version to use.
Enhanced Transmission Selection (ETS) information for QoS parameters such as bandwidth
allocation per traffic class (802.1p COS), priority for each traffic class, and the algorithm used for
servicing traffic classes.
Priority-based Flow Control (PFC) information for managing flow control between peers.
Application priority information for prioritizing traffic for special applications that do not map
directly to an established traffic class.
The ExtremeXOS software supports two versions of DCBX standards. The first version is a pre-standard
version known as the baseline version, or more specifically as Baseline Version 1.01. The DCBX baseline
version is specified in DCB Capability Exchange Protocol Base Specification Rev 1.01 and was developed
outside of the IEEE and later submitted to the IEEE for standardization. The IEEE agreed to standardize
DCBX as part of IEEE 802.1Qaz Enhanced Transmission Selection for Bandwidth Sharing Between
Traffic Classes. While IEEE 802.1Qaz has progressed through the standards process, many companies
have released support for the baseline version. IEEE 802.1Qaz is nearing completion, and support is
expected to start rolling out during 2011.
After you enable DCBX, the protocol collects most of the information to be advertised from other
switch services such as QoS and PFC. The only DCBX feature that needs configuration is the application
priority feature.
DCBX uses the Link Layer Discovery Protocol (LLDP) (IEEE 802.1AB) to exchange attributes between
two link peers. DCBX attributes are packaged into organizationally specific TLVs, which are different for
the Baseline and IEEE 802.1Qaz versions. Information on the TLV support differences is provided in the
ExtremeXOS Command Reference under the command description for the command: show lldp
{port [all | port_list]} dcbx {ieee|baseline} {detailed}
Custom Application Support
The DCBX custom application support feature allows you to prioritize and manage traffic flow through
the switch based on the application type. This feature allows you to configure DCBX handling of the
following applications:
• Fiber Channel Over Ethernet (FCoE)
• FCoE Initiation Protocol (FIP)
• Internet Small Computer System Interface (iSCSI)
• Any application that can be defined by:
• Ethertype value
• Layer 4 port number
• TCP port number
• UDP port number
When you configure a custom application, you define a priority number that applies to traffic related to
that application. DCBX advertises this priority to end stations in an application TLV. End stations that
support this feature use the priority number for communications with the switch. The priority number
maps to an 802.1p value, which determines which QoS profile in the switch manages the application
traffic.
The software supports a maximum of eight application configurations.
Advanced Features
97
Data Center Solutions
Enhanced Transmission Selection
Enhanced Transmission Selection is defined in IEEE P802.1Qaz/D2.3, Virtual Bridged Local Area
Networks-Amendment XX: Enhanced Transmission Selection for Bandwidth Sharing Between Traffic
Classes. This IEEE 802.1Qaz standard also defines one of the DCBX versions supported by the
ExtremeXOS software.
ETS, and similar features in the Baseline DCBX standard, define methods for managing bandwidth
allocation among traffic classes (called Priority Groups (PGs) in Baseline DCBX) and mapping 802.1p
COS traffic to those traffic classes.
The rest of this section provides general guidelines for configuring the ExtremeXOS QoS feature to
conform to the ETS requirements. After you configure QoS, DCBX advertises the ETS compatible
configuration to DCBX peers on all DCBX enabled ports.
ETS configuration is affected by the following set of QoS objects:
• QoS scheduler
• QoS profile
• dot1p
By default, the scheduling is set to strict-priority.
The following command enables ETS compatible (weighted) scheduling:
configure qosscheduler [strict-priority | weighted-round-robin | weighteddeficit-round-robin]
Each QoS profile supports an IEEE ETS traffic class (TC) or a Baseline DCBX priority group (PG). To
determine which QoS profile serves a TC or PG, add the number 1 to the TC or PG number. For example,
TC 0 and PG 0 are served by QoS profile 1. ExtremeXOS switches support up to eight QoS profiles and
can therefore support up to eight TCs or PGs. The following QoS configuration changes affect the
ETS/PG configuration:
• QoS profile:
• When you create or delete a QoS profile, you add or remove support for the corresponding TC
or PG.
• The weight configuration helps determine the bandwidth for a TC or PG.
• The use-strict-priority configuration overrides ETS scheduling and selects strict priority
scheduling for the corresponding TC or PG.
• The dot1p configuration maps each 802.1p priority, and the associated TC and PG, to a QoS
profile. If you change the 802.1p mapping, it will change which QoS profile services each TC or
PG.
• Per port configuration parameters:
• minbw: Sets a minimum guaranteed bandwidth in percent.
• maxbw: Sets a maximum guaranteed bandwidth in percent.
• committed_rate: Sets a minimum guaranteed bandwidth in Kbps or Mbps.
• peak_rate: Sets a maximum guaranteed bandwidth in Kbps or Mbps.
Advanced Features
98
Data Center Solutions
For example, the following set of commands creates a QoS profile (qp5) in preparation to support iSCSI
traffic, maps packets with 802.1p priority 4 to QoS profile 5, indicates that QoS profile 8 should use
strict priority, and sets the weight for the ETS classes:
create qosprofile qp5
configure dot1p type 4 qosprofile qp5
configure qosprofile qp1 weight 1
configure qosprofile qp5 weight 2
configure qosprofile qp8 use-strict-priority
Note
All Extreme Networks DCB-capable switches are configured with qp1 and qp8 by default, and
some platforms support additional QoS profiles by default. When stacking is used for Summit
switches, qp7 is created by default for internal control communications, and is always set to
strict priority.
DCBX only advertises the bandwidth for ETS classes, so in the example, the available bandwidth is
divided only between qp1 and qp5. The total bandwidth for all ETS classes must add up to 100%, so if
the weights don't divide evenly, one or more of the reported bandwidth numbers are rounded to satisfy
this requirement. With this in mind, the above configuration results in reported bandwidth guarantees
of 33% for TC/PG 0 (qp1) and 67% for TC/PG 4 (qp5).
Weighted round robin scheduling is packet based, so when packets are queued for both classes 0 and
4, the above configuration results in two TC/PG 4 packets being transmitted for each single TC/PG 0
packet. As such, the exact percentages are realized only when the average packet sizes for both classes
are the same and the measurement is taken over a long enough period of time. Another consideration
is that using the lowest weights possible to achieve the desired ratios results in a more even
distribution of packets within a class (that is, less jitter). For example, using weights 1 and 2 are usually
preferable to using weights 5 and 10—even though the resulting bandwidth percentages are the same.
Enhanced Transmission Selection allows you to configure QoS scheduling to be weighted-deficitround-robin. In this approach, you can configure a weight in the range of 1–127 on the QoS profiles. The
difference between weighted-round-robin (WRR) and weighted-deficit-round-robin (WDRR) is that, in
the latter approach, the algorithm uses a “credit counter” mechanism.
The algorithm works in slightly different ways on different platforms:
Platform:
Summit X480, X460, X440 series switches; BlackDiamond 8800 series switches with 8900-G96T-c,
8900-10G24X-c, 8900-MSM128, 8900-G48T-xl, 8900-G48X-xl, and 8900-10G8X-xl modules; E4G-400,
E4G-200 cell site routers.
Methodology:
•
•
•
Credit counter—A token bucket that keeps track of bandwidth overuse relative to each queue’s
specified weight.
Weight—Relative bandwidth allocation to be serviced from a queue in each round compared with
other queues. Range is between 1 and 127. A weight of 1 equals a unit of 128 bytes.
MTU Quantum Value—2 Kbytes.
Advanced Features
99
Data Center Solutions
1 Set credit counter to quantum value for all queues.
2 Service queues in round robin order, according to the weight value. When a packet from a queue is
sent, the size of the packet is subtracted from the credit counter. A queue is serviced until it is either
empty or its credit counter is negative.
3 When all queues are either empty or their credit counter is less than 0, replenish credits by: MTU
quantum value x weight of queue. No queue’s credit can ever be more than quantum value x
weight.
Repeat steps two and three until all queues are empty.
Platform:
Summit X670 and X770 series switches; BlackDiamond 8800 series switches with 8900-40G6X-xm
module; BlackDiamond X8 series swithes with BDX-MM1, BDXA-FM960, BDXA-FM480, BDXA-40G24X,
and BDXA-40G12X modules.
Methodology:
•
•
•
Credit counter—A token bucket used to keep track of bandwidth overuse relative to each queue’s
specified weight.
Weight—Relative bandwidth allocation to be serviced from a queue in each round compared with
other queues. Range is between 1 and 127.
K—Minimum value required to make all credit counters positive. This value is recalculated after each
round.
1 Set credit counter for each queue to queue’s weight value.
2 Service queues in round robin order, according to the weight value. When a packet from a queue is
sent, the size of the packet is subtracted from the credit counter. A queue is serviced until it is either
empty or its credit counter is negative.
3 When all queues are either empty or their credit counter is less than 0, replenish credits by: 2^K ×
weight of queue. K is calculated so that it is the minimum value required to make all credit counters
positive. No queue’s credit can ever be more than 2^K × weight of queue.
Repeat steps two and three until all queues are empty.
Platform:
BlackDiamond 8800 series switches with G48Te, G48Te2, G24Xc, G48Xc, G48Tc, 10G4Xc, 10G8Xc,
MSM-48, S-G8Xc, S-10G1Xc, 8500-G24X-e, 8500-G48T-e, and S-10G2Xc modules.
Methodology:
These cards have a weight range of 1 to 15. Credit is replenished by 2^(weight – 1) × 10KB.
The number of bytes that can be transmitted in a single round is:
• Weight 0 = Strict Priority
• Weight 1 = 10 KB
• Weight 2 = 20 KB
• Weight 3 = 40 KB
• Weight 4 = 80 KB
• Weight 5 = 160 KB
• Weight 6 = 320 KB
Advanced Features
100
Data Center Solutions
•
•
•
•
•
•
•
•
•
Weight 7 = 640 KB
Weight 8 = 1,280 KB
Weight 9 = 2,560 KB
Weight 10 = 5,120 KB
Weight 11 = 10 MB
Weight 12 = 20 MB
Weight 13 = 40 MB
Weight 14 = 80 MB
Weight 15 = 160 MB
When ETS scheduling is used without a minbw or committed_rate configured, packets from strict
priority classes always preempt packets from ETS classes, so the reported percentages reflect the
distribution of the bandwidth after strict priority classes use what they need.
Because of this, one might consider limiting the bandwidth for any strict priority classes using the
maxbw parameter. For example, the following command limits TC/PG 7 to 20% of the interface
bandwidth:
configure qosprofile qp8 maxbw 20 ports 1-24
The per-port bandwidth settings described above can also be used to either limit or guarantee
bandwidth for an ETS class.
For example, the following command guarantees 40% of the bandwidth to TC/PG 0:
configure qosprofile qp1 minbw 40 ports 1-24
The DCBX protocol takes these minimum and maximum bandwidth guarantees into account when
calculating the reported bandwidth. With the addition of this minimum bandwidth configuration, the
reported bandwidth would change to 40% for class 0 (qp1) and 60% for class 4 (qp5).
The following are some important considerations when using minimum and maximum bandwidth
guarantees:
• They change the scheduling dynamic such that a class with a minbw will have priority over other
classes (including strict priority classes) until the minbw is met, which differs from the standard ETS
scheduling behavior described in 802.1az
• If the minbw is set on multiple classes such that the total is 100%, these classes can starve other
classes that do not have a configured minbw. So, for example, if the minbw for both class 0 and
class 4 is set to 50% (100% total), traffic from these classes can starve class 7 traffic. This can lead to
undesirable results since DCBX and other protocols are transmitted on class 7. In particular, DCBX
may report the peer TLV as expired. This effect can be magnified when an egress port shaper is
used to limit the egress bandwidth.
If
• all ETS classes have a maxbw set, and the total is less than 100%, the total bandwidth reported by
DCBX will be less than 100%. Extreme does not report an error in this case, but some DCBX peers
may report an error.
• Packet size is a factor in the minimum and maximum bandwidth guarantees.
Advanced Features
101
Data Center Solutions
In light of these considerations, the following are a set of guidelines for using minimum and maximum
bandwidth guarantees:
• If minbw guarantees are used for ETS classes, and strict priority classes exist:
• Make sure that the total minbw reserved is less than 100%.
• Configure minbw for the strict priority classes.
• If strict priority classes exist, you may want to configure a maxbw for the strict priority classes so
they don't starve the ETS classes.
• If maxbw is configured on some ETS classes, ensure that either the total of the maxbw settings for
all ETS classes is equal to 100%, or at least one ETS class does not have a maxbw configured.
For more information on the QoS features that support ETS, see QoS.
Priority-based Flow Control
Priority flow control (PFC) is defined in the IEEE 802.1Qbb standard as an extension of the IEEE 802.3x
flow control standard. When buffer congestion is detected, IEEE 802.3x flow control allows the
communicating device to pause all traffic on the port, whereas PFC allows the device to pause just a
portion of the traffic and allow other traffic on the same port to continue.
The rest of this section provides general guidelines for configuring the ExtremeXOS PFC feature for
DCB operation. After you configure PFC, DCBX advertises the PFC compatible configuration to DCBX
peers on all DCBX enabled ports.
•
PFC configuration is controlled per-port using the following command:
enable flow-control [tx-pause {priority priority} | rx-pause {qosprofile
qosprofile}] ports [all | port_list]
The rx-pause option is configured on the QoS profile.
The PFC priority to which a QoS profile responds is fixed and is determined by the QoS profile
number such that qpN responds to a PFC frame for priority N-1.
For example, the following command enables PFC priority 4 for qp5 on ports 1-24:
enable flow-control rx-pause qosprofile qp5 ports 1-24
After the above command is entered, if a PFC frame is received indicating that priority 4 should be
paused, then qp5 will be paused. Note that qp5 is paused regardless of whether the packets
mapped to qp5 have priority 4 or other priorities. For example, if we enter the command configure
dot1p type 3 qosprofile qp5, priority 3 packets are queued in qp5, and a PFC pause frame for priority
4 pauses priority 3 frames, which might not be desired. For this reason, you should be careful about
mapping multiple priorities to the same QoS profile when PFC is enabled for that profile.
The tx-pause option is configured on the priority itself. For example, the following command enables
the transmittal of PFC Pause frames for priority 4 when frames with priority 4 are congested:
enable flow-control tx-pause priority 4 ports 1-24
The tx-pause configuration determines what is advertised in the DCBX PFC TLV. In order for PFC to
work correctly, it is important to ensure that all switches in the DCB network are receiving and
transmitting PFC consistently for each priority on all ports.
Advanced Features
102
Data Center Solutions
In summary, the following three commands ensure that PFC is enabled for priority 4 traffic on ports
1-24:
configure dot1p type 4 qosprofile qp5
enable flow-control rx-pause qosprofile qp5 ports 1-24
enable flow-control tx-pause priority 4 ports 1-24
For more information on PFC, see IEEE 802.1Qbb Priority Flow Control.
Introduction to the XNV Feature
The Extreme Network Virtualization (XNV) feature, which is also known as Virtual Machine (VM)
tracking, enables the ExtremeXOS software to support VM port movement, port configuration, and
inventory on network switches. VM movement and operation on one or more VM servers is managed
by a VM Manager (VMM) application. The XNV feature enables a network switch to respond to VM
movement and report VM activity to network management software.
VM network access support enables a switch to support VMs as follows:
• Identify a VM by its MAC address and authenticate the VM connection to the network.
• Apply a custom port configuration in response to VM authentication.
• Remove a custom port configuration when a VM FDB entry ages out.
• Detect a VM move between switch ports or switches and configure the old and new ports
appropriately.
To support VM mobility, the XNV feature requires that each VM use unique, static MAC and IP
addresses. Switch port operation for a VM can be configured with a policy file or an ACL.
VM Port Configuration
An important part of the XNV feature is the ability to configure a switch port to support a particular VM.
A Virtual Port Profile (VPP) identifies a policy file or ACL rule to associate with a VM entry in the
authentication database. You can define both ingress and egress policies in VPPs to configure a port
separately for each direction. When the VPP is configured for a VM entry and the VM is detected on a
port, any associated policy or rule is applied to the port in the specified direction.
The XNV feature supports two types of VPPs, Network VPPs (NVPPs) and Local VPPs (LVPPs).
NVPPs are stored on an FTP server called a repository server. The XNV feature supports file
synchronization between XNV-enabled switches and the repository server. One of the advantages of
the repository server is centralized storage for NVPPs.
LVPPs must be configured on each switch. LVPPs are a good choice for simple network topologies, but
NVPPs offer easier network management for more complex network topologies.
VM Authentication Process
The XNV feature supports three methods of authentication:
• NMS server authentication.
• Network authentication using a downloaded authentication database stored in the VMMAP file.
Advanced Features
103
Data Center Solutions
•
Local authentication using a local database created with ExtremeXOS CLI commands.
The default VM authentication configuration uses all three methods in the following sequence: NMS
server (first choice), network based VMMAP file (second choice), and finally, local database. If a service
is not available, the switch tries the next authentication service in the sequence.
NMS Server Authentication
If NMS server authentication is enabled and a VM MAC address is detected on a VM-tracking enabled
port, the software sends an Access-Request to the configured NMS server for authentication. When the
switch receives a response, the switch does one of the following:
• When an Access-Accept packet is received with an NVPP specified, the policies are applied on VM
enabled port.
• When an Access-Accept packet is received and no NVPP is specified, the port is authenticated and
no policy is applied to the port.
• When an Access-Reject packet is received, the port is unauthenticated and no policy is applied.
• When an Access-Reject packet indicates that the NMS server timed-out or is not reachable, the
switch tries to authenticate the VM MAC address based on the next authentication method
configured, which can be either network authentication or local authentication.
The Access-Accept packet from the NMS server can include the following Vendor Specific Attributes
(VSAs):
• VM name
• VM IP address
• VPP configured for the VM
An Access-Reject packet contains no VSA.
Network (VMMAP) Authentication
If network (VMMAP) authentication is enabled and a VM MAC address is detected on a VM-tracking
enabled port, the switch uses the VMMAP file to authenticate the VM and applies the appropriate VPP.
Local Authentication
If local authentication is enabled and a VM MAC address is detected on a VM-tracking enabled port, the
switch uses the local database to authenticate the VM and apply the appropriate VPP.
Authentication Failure
If all configured authentication methods fail, EMS messages are logged and no VPP is applied.
Possible remedies include:
• Fix the authentication process that failed. Look for misconfiguration or down segments.
• Configure UPM to take action on the related EMS message.
• If one or two authentication methods are configured, configure additional authentication methods.
Duplicate VM MAC Detected
Each VM MAC must be unique. If duplicate MAC addresses are detected on the switch, whether on the
same VLAN or different VLANs, the switch supports only the last MAC detected.
Advanced Features
104
Data Center Solutions
File Synchronization
The XNV feature supports file synchronization between XNV-enabled switches and the repository
server. The files stored on the repository server include the .map, .vpp, and .pol files. One of the
advantages of the repository server is that multiple XNV-enabled switches can use the repository
server to collect the network VM configuration files. The XNV feature provides for access to a
secondary repository server if the primary repository server is unavailable.
Through file synchronization, the network files are periodically downloaded to the XNV-enabled
switches, which allows these switches to continue to support VM authentication when the NMS server
is unavailable.
Network Management and Inventory
The XNV feature is designed to support network management programs such as Ridgeline. The
ExtremeXOS software contains SNMP MIBs, which allow network management programs to view VM
network configuration data, discover the VM inventory, and make configuration changes. Ridgeline is
enhanced to interface with VMMs and perform most VM network configuration tasks. We recommend
that you use Ridgeline to manage VM network connectivity.
For instructions on managing the XNV feature using the switch CLI, see Managing the XNV Feature, VM
Tracking on page 107.
Introduction to the Direct Attach Feature
The direct attach feature is a port configuration feature that supports VM-to-VM communication on a
directly connected server that uses the Virtual Ethernet Port Aggregator (VEPA) feature on that server.
Without VEPA and direct attach, a VM server must use a virtual Ethernet bridge or switch on the VM
server to enable Ethernet communications between VMs. With VEPA, the VM server can rely on a
directly connected switch to receive and reflect VM-to-VM messages between VMs on the same server.
The ExtremeXOS direct attach feature works with VEPA software on a VM server to intelligently
forward unicast, flood, and broadcast traffic. Without direct attach, frames are never forwarded back
out the same port on which they arrive. With direct attach, frames can be forwarded back out the
ingress port, and VEPA software on the VM server ensures that the frames are forwarded
appropriately.
For instructions on managing the Direct Attach feature, see Managing Direct Attach to Support VEPA
on page 127.
Managing the DCBX Feature
Enabling DCBX on Switch Ports
DCBX uses LLDP to advertise DCB capabilities to DCB peers.
Advanced Features
105
Data Center Solutions
Use the following commands to enable LLDP and the DCBX feature on switch ports:
enable lldp ports [all | port_list] {receive-only | transmit-only}
configure lldp ports [all | port_list] [advertise | no-advertise] vendor-specific
dcbx {ieee|baseline}
Configuring DCBX Application Priority Instances
Each DCBX application priority instance maps traffic from one of the supported application types to a
TC or PG priority, which selects a specific QoS profile for traffic management. Supported application
types include:
•
•
•
Fiber Channel Over Ethernet (FCoE)
FCoE Initiation Protocol (FIP)
Internet Small Computer System Interface (iSCSI)
Use the following commands to add or delete DCBX application priority instances:
configure lldp ports [all | port_list] dcbx add application [name
application_name | ethertype ethertype_value | L4-port port_number | tcp-port
port_number | udp-port port_number] priority priority_value
configure lldp ports [all | port_list] dcbx delete application [all-applications
| name application_name | ethertype ethertype_value | L4-port port_number | tcpport port_number | udp-port port_number]
Displaying DCBX Configuration and Statistics
Use the following commands to display DCBX feature configuration and statistics:
show lldp {port [all | port_list]} {detailed}
show lldp {port [all | port_list]} dcbx {ieee|baseline} {detailed}
DCBX Configuration Example
The following is a sample DCBX configuration:
enable lldp ports 1
configure lldp port 1 advertise vendor-specific dcbx ieee
configure lldp port 1 advertise vendor-specific dcbx baseline
enable lldp ports 2
configure lldp port 2 advertise vendor-specific dcbx ieee
configure lldp port 2 advertise vendor-specific dcbx baseline
configure lldp ports 1 dcbx add application name iscsi priority 4
configure lldp ports 1 dcbx add application name fcoe priority 3
Advanced Features
106
Data Center Solutions
configure
configure
configure
configure
configure
configure
configure
configure
lldp
lldp
lldp
lldp
lldp
lldp
lldp
lldp
ports
ports
ports
ports
ports
ports
ports
ports
1
2
2
2
2
2
2
2
dcbx
dcbx
dcbx
dcbx
dcbx
dcbx
dcbx
dcbx
add
add
add
add
add
add
add
add
application
application
application
application
application
application
application
application
name fip priority 3
name iscsi priority 4
name fcoe priority 3
name fip priority 3
L4-port 25 priority 4
tcp-port 4500 priority 4
udp-port 45 priority 5
ethertype 2536 priority 4
Managing the XNV Feature, VM Tracking
Limitations
The following limitations apply to this release of the VM tracking feature:
•
•
•
•
•
When VM tracking is configured on a port, all existing learned MAC addresses are flushed. MAC
addresses will be relearned by the switch and the appropriate VPP (if any) for each VM will be
applied.
If a VM changes MAC addresses while moving between ports on a switch, the VM remains
authenticated on the original port until the original MAC address ages out of the FDB.
VM counters are cleared when a VM moves between ports on the same switch (because the ACLs
are deleted and recreated).
Each VPP entry supports a maximum of eight ingress and four egress ACL or policies.
For Network VPP, only policy files can be mapped. For Local VPP, either ACL or policy files can be
mapped. You cannot map a mixture of both ACL and policy files to a particular VPP.
Managing VM Tracking on the Switch
Use the following steps to manage VM tracking on the switch:
•
Issue the following command to enable the VM tracking feature on the switch:
enable vm-tracking
•
Issue the following command to disable the VM tracking feature on the switch:
disable vm-tracking
Note
When the VM tracking feature is disabled, file synchronization with the repository server
stops.
•
Issue the following command to view the VM tracking feature configuration and the list of
authenticated VMs:
show vm-tracking
Advanced Features
107
Data Center Solutions
Managing VM Tracking on Specific Ports
Before you enable the VM tracking feature on specific ports, you must enable VM tracking on the
switch, configure the authentication method and sequence, and the VM authentication databases.
• When this configuration is complete, you can use the following command to enable VM tracking on
one or more ports:
enable vm-tracking ports port_list
•
To disable the VM tracking feature on a group of ports, use the following command:
disable vm-tracking ports port_list
•
To view the VM tracking feature configuration on one or more ports, use the following command:
show vm-tracking port port_list
Configuring the Authentication Method and Sequence
You can configure VM authentication through the following services:
• NMS server
• Network based VMMAP file
• Local database
The default VM authentication configuration uses all three methods in the following sequence: NMS
server (first choice), network based VMMAP file (second choice), and finally, local database. If a service
is not available, the switch tries the next authentication service in the sequence.
To configure one or more authentication methods and a preferred sequence, use the following
command:
configure vm-tracking authentication database-order [[nms] | [vm-map] | [local] |
[nms local] | [local nms] | [nms vm-map] | [vm-maplocal] | [local vm-map] | [nms
vm-map local] | [localnmsvm-map]]
XNV Dynamic VLAN
Starting in release 15.3, when a virtual machine is detected, ExtremeXOS dynamically creates the VLAN
that is required for the VM to send traffic. If a virtual machine shuts down or is moved, its VLAN is
pruned to preserve bandwidth. This feature creates an adaptive infrastructure in which the network
responds to changes dynamically in the virtual machine network.
Enabling/Disabling XNV Dynamic VLAN
Enabling the XNV dynamic VLAN feature must be done on a per-port basis. XNV requires that the port
on which dynamic VLANs is enabled is part of the "default or "base" VLAN as untagged. This "default"
or "base" VLAN for the port is the VLAN on which untagged packets are classified to when no VLAN
configuration is available for the MAC. This default VLAN should be present before enabling the feature
and the port should already be added to this VLAN by the user manually before enabling the feature.
Enabling this feature on a port results in a failure if any of the following conditions are true:
• If XNV is not enabled, the command only results in a warning, and does not fail. XNV can be enabled
later.
Advanced Features
108
Data Center Solutions
•
The port is not an untagged member of any VLAN.
When a VLAN's MAC is detected on a port, XNV consults the configuration database to determine the
VLAN configuration for the VM. For a case where the VM sends tagged traffic, the VLAN tag of the
received frame is used to determine VLAN classification for the VM's traffic. If VLAN configuration
exists for the VM and it conflicts with the actual tag present in received traffic, XNV reports an EMS
message and does not trigger VLAN creation or port addition. However, if no configuration is present
for the VM, XNV assumes that there are no restrictions for classifying traffic for the VM to the received
VLAN.
For untagged traffic, XNV can determine the VLAN for the VM from any one of the three possible
sources:
• VLAN configuration for the VM MAC entry.
• VLAN configuration for the VPP associated with the VM's MAC. The VPP can either be a network
VPP or a local VPP.
• In case of untagged traffic from the VM, the "default" VLAN for the port that is specified as part of
the dynamic VLAN enable configuration.
This list determines the order of precedence for VLAN classification for untagged traffic only. For
tagged VLAN traffic, XNV validates the tag of the received traffic with then VLAN tag configuration for
that VM.
In addition to the VLAN tag, you can specify the VR to which the dynamically created VLAN needs to
be associated. The VR configuration is relevant only if a VLAN tag is configured for the VM.
Table 11:
Configured VR on Port
Configured VR for VM (from
VM Mapping Entry or VPP)
VLAN Already Exists on
the Switch
Dynamic VLANs VR
None
None
No
VR-Default
None
None
Yes
VLAN's VR
None
VR-X
No
VR-X (Configured VR for
VM) if VR-X is valid.)
Otherwise an EMS error is
displayed indicating the
VR-X is invalid.
None
VR-X
Yes
VLAN's VR. An EMS error is
displayed if the VLAN's VR
is not VR-X.
VR-X
None
No
VR-X (Port's VR).
VR-X
None
Yes
VR-X if VLAN's VR is VR-X.
If it is not, an EMS error is
displayed indicating the
VR-X is invalid.
Advanced Features
109
Data Center Solutions
Table 11: (continued)
Configured VR on Port
Configured VR for VM (from
VM Mapping Entry or VPP)
VLAN Already Exists on
the Switch
Dynamic VLANs VR
VR-X
VR-Y
No
Dynamic VLAN is not
created when Port Level
VR and VM-MAC VR are
different, and FDB is
learned on a system
generated VMAN. An EMS
warning is generated on
the switch log, because a
Dynamic VLAN cannot be
created.
VR-X
VR-Y
Yes
VR-X if VLAN is part of VRX. Otherwise, EMS error is
displayed.
When you disable dynamic VLAN on a port, XNV does the following:
•
•
•
Triggers deletion of MAC-based entries on that port in the hardware.
If the port has been added to any VLAN by XNV, XNV triggers a flush for those VLANs.
If the port has been added to an VLAN by XNV, XNV requests VLAN manager to remove the port
from the VLAN.
Note
It is up to the VLAN manager to decide if the port actually needs to be removed from the
VLAN.
When XNV is disabled on a port, the XNV dynamic VLAN feature is also disabled. The XNV dynamic
VLAN configuration is not persistent, and needs to be re-enabled after XNV is re-enabled on that port.
Tracking XNV Per VM Statistics
Beginning in release 15.3, each local and network VPP has the option to specify whether a counter
needs to be installed to count traffic matching the virtual machine MAC which gets the VPP mapping.
You can choose to install a counter to collect statistics for ingress traffic only, egress traffic only, or
traffic in both directions.
Once the ingress counter installation option is selected for a specific local or network VPP and the
virtual machine which has this VPP mapping is detected on the switch, the counter is installed with the
name "xnv_ing_dyn_cnt_vmxxxxxxxxxxxx" for the port on which the VM MAC is detected. In this case,
xxxxxxxxxxxx denotes the virtual machine MAC for which the counter is installed. In the same way, the
egress counter is installed using the name "xnv_egr_dyn_cnt_vmxxxxxxxxxxxx" for that port.
You can view a list of packet/byte counts for this counter name using the command show access
dynamic-counter. The counter is uninstalled only when the virtual machine MAC is deleted on the
switch or the VPP is mapped to a virtual machine MAC which has the counter option set to none. If the
VM MAC move happens then the counter installed on the previous port is uninstalled and the counter is
installed on the new port. The counter values are not maintained during the MAC move.
Advanced Features
110
Data Center Solutions
Managing the Repository Server
Selecting the Repository Server Directory
All files for NMS and network authentication must be placed in the configured repository server
directory. These files include the following:
• MANIFEST
• VMMAP
• NVPP policy files
By default, the XNV feature tries to access the FTP server with anonymous login and fetch the files
from the pub directory within the FTP server root directory.
To configure a different directory for repository server files, use the following command:
configure vm-tracking repository
Creating the MANIFEST File
The MANIFEST file identifies the VMMAP, NVPP, and policy files that are to be used for either NMS or
network authentication. The MANIFEST file is downloaded to the switch at the specified refresh
interval. Each time the MANIFEST file is downloaded, the switch scans the file and compares the file
entries and timestamps to those files on the switch. If the switch detects newer files, it downloads those
files to the switch.
You can create the MANIFEST file with a text editor. The MANIFEST file must be placed on the
repository server as described in Selecting the Repository Server Directory on page 111.
The format of MANIFEST files is:
File1 yyyy-mm-dd hh:mm:ss
File2 yyyy-mm-dd hh:mm:ss
Because the definition for each file in the MANIFEST includes a date and time, you must update the
MANIFEST file every time you update the VMMAP file or a policy file.
The following is a sample MANIFEST file:
a1.map 2010-07-07 18:57:00
a1.vpp 2010-07-07 18:57:00
a2.map 2010-07-07 18:57:00
a2.vpp 2010-07-07 18:57:00
policy1.pol 2010-07-07 18:57:00
epolicy1.pol 2010-07-07 18:57:00
The file extensions for the files in the MANIFEST file identify the supported file types:
• .map—VMMAP files
• .vpp—VPP files
Advanced Features
111
Data Center Solutions
•
.pol—Policy files
Creating a VMMAP File
Use a text editor to create a VMMAP file. VMMAP file entries must use the following XML format:
<VMLIST>
<VM>
<MAC>00:00:00:00:00:21</MAC>
<NAME>network_vm1</NAME>
<IPV4>10.10.10.10</IPV4>
<VPP>nvpp1</VPP>
</VM>
<VM>
<MAC>00:00:00:00:00:22</MAC>
<NAME>network_vm2</NAME>
<IPV4>20.20.20.20</IPV4>
<VPP>nvpp2</VPP>
</VM>
</VMLIST>
When creating VMMAP file entries, use the following guidelines:
• The VPP file supports up to 400 child nodes.
• The MAC address is required.
• If you do not want to specify a VM name, specify none.
• If you do not want to specify an IP address, specify 0.0.0.0.
• If you do not want to specify a VPP name, specify none.
• If a value such as the VM name contains any space characters, the entire value must be specified
between double quotation marks ( " ).
For information on where to place the VMMAP file, see Selecting the Repository Server Directory on
page 111.
Creating VPP Files
]
Use a text editor to create a VPP file. VPP file entries must use the following XML format:
<vppList>
<vpp>
<name>nvpp1</name>
<last-updated>2002-05-30T09:00:00</last-updated>
<policy>
<name>policy1</name>
<direction>ingress</direction>
<order>1</order>
</policy>
<policy>
<name>policy4</name>
<direction>ingress</direction>
Advanced Features
112
Data Center Solutions
<order>4</order>
</policy>
<policy>
<name>epolicy1</name>
<direction>egress</direction>
<order>1</order>
</policy>
<policy>
<name>epolicy4</name>
<direction>egress</direction>
<order>4</order>
</policy>
</vpp>
</vppList>
The VPP file supports up to 400 child nodes, and each VPP entry supports up to eight ingress and four
egress ACL or policies. If multiple policies are defined within a VPP entry for either ingress or egress,
the switch uses the policy with the lowest order number. If two ingress or egress policies have the same
order number, the switch selects the policy based on which name is lexicographically lower.
To refresh all policies which are all associated and applied to each VPP, use the following command:
refresh policy policy-name
The NVPP policy files must be placed on the repository server as described in Selecting the Repository
Server Directory on page 111.
Creating Policy Files
For instructions on creating policy files, see Policy Manager.
To display the policy file or ACL associated with one or all VPPs, use the following command:
show vm-tracking vpp {vpp_name}
Managing Switch Access to the Repository Server
•
To enable and configure file synchronization between an XNV-enabled switch and a repository
server, use the following command:
configure vm-tracking repository [primary | secondary] server [ipaddress |
hostname] {vr vr_name} {refresh-interval seconds} {path-name path_name} {user
user_name {encrypted} password}
•
To force file synchronization with the repository server, use the following command:
•
To remove the configuration for one or both repository servers, use the following command:
•
To display the repository server configuration and status, use the following command:
run vm-tracking repository sync-now
unconfigure vm-tracking repository {primary | secondary}
show vm-tracking repository {primary | secondary}
Advanced Features
113
Data Center Solutions
Manage NMS Server Authentication
NMS server authentication uses the RADIUS protocol to authenticate VM access to the network with
the RADIUS server included with Ridgeline. Ridgeline is designed to perform VM network management
tasks, such as creating and associating NVPPs with VM authentication entries.
To use NMS authentication, you must do the following:
•
•
•
•
Select NMS authentication as described in Configuring the Authentication Method and Sequence on
page 108.
Prepare the network repository server as described in Managing the Repository Server on page 111.
Configure the NMS client software in the switch as described in Configure the NMS Client Software
on page 114.
Configure the NMS server as described in Configuring the NMS Server Software on page 114.
You can display NMS authenticated VMs as described in Displaying NMS Authenticated VMs on page
115.
Configuring the NMS Server Software
The Ridgeline product includes a RADIUS server that you can use for NMS server authentication. To
configure this server, do the following:
1
Add the IP address of each XNV-enabled switch as a RADIUS client.
2 Add each VM MAC address as a username (in upper case and should not contain semicolon) and
add the MAC address as the password.
3 Add a remote access policy with the Extreme Networks VSAs:
•
•
Vendor code: 1916
VSA ID: 213 (EXTREME_VM_NAME)
•
Example: MyVM1
VSA ID: 214 (EXTREME_VM_VPP_NAME)
•
Example: nvpp1
VSA ID: 215 (EXTREME_VM_IP_ADDR)
Example: 11.1.1.254
For instructions on configuring the Ridgeline RADIUS server, refer to the Ridgeline documentation.
Configure the NMS Client Software
•
The switch uses NMS client software to connect to an NMS server for VM authentication. Use the
following commands to configure the NMS client software in the switch:
configure vm-tracking nms [primary | secondary] server [ipaddress | hostname]
{udp_port} client-ip client_ip shared-secret {encrypted} secret {vr vr_name}
configure vm-tracking nms timeout seconds
configure vm-tracking timers reauth-period reauth_period
•
To remove the NMs client configuration for one or both NMS servers, use the following command:
unconfigure vm-tracking nms {server [primary | secondary]}
Advanced Features
114
Data Center Solutions
•
To display the NMS client configuration, use the following command:
show vm-tracking nms server {primary | secondary}
Displaying NMS Authenticated VMs
To display the VMs and corresponding policies in the NMS authentication database, use the following
command:
show vm-tracking network-vm
Managing Network Authentication (Using the VMMAP File)
To use network authentication, you must do the following:
1
Select network authentication as described in Configuring the Authentication Method and Sequence
on page 108.
2 Prepare the network repository server as described in Managing the Repository Server on page 111.
To display the VMs and corresponding policies in the network authentication database, use the
following command:
show vm-tracking network-vm
Manage Local Database Authentication
To use local database authentication, you must do the following:
1
Select local database authentication as described in Configuring the Authentication Method and
Sequence on page 108.
2 Create and manage local VPPs (LVPPs) as described in Managing the Local VPP Database on page
115.
3 Create VM entries as described in Managing VM Entries in the Local Authentication Database on
page 116.
Managing the Local VPP Database
Only one dynamic ACL or policy can be added to a VPP. Ingress LVPPs apply to traffic flowing from the
VM, into the switch port, and then to the client. Egress LVPPs apply to traffic flowing from the client,
out the switch port, and to the VM.
For instructions on creating policy files, see Policy Manager. For instructions on creating dynamic ACLs,
see ACLs.
•
To create and configure entries in the LVPP database, use the following commands:
create vm-tracking vpp vpp_name
configure vm-tracking vpp vpp_name add [ingress | egress] [policy policy_name
| dynamic-rule rule_name] {policy-order policy_order}
•
To delete or unconfigure entries in the local VPP database, use the following commands:
delete vm-tracking vpp {vpp_name}
Advanced Features
115
Data Center Solutions
unconfigure vm-tracking vpp vpp_name
•
To display the policy file or ACL associated with one or more VPPs , use the following command:
show vm-tracking vpp {vpp_name}
Managing VM Entries in the Local Authentication Database
•
To create and configure entries in the local authentication database, use the following commands:
create vm-tracking local-vm mac-address mac {name name | ipaddress ipaddress
vpp vpp_name }
configure vm-tracking local-vm mac-address mac [name name | ip-address
ipaddress | vpp vpp_name]
•
To remove a configuration parameter for a local authentication database entry, or to remove an
entry, use the following commands:
unconfigure vm-tracking local-vm mac-address mac [name | ip-address | vpp]
delete vm-tracking local-vm {mac-address mac}
•
To display the local VPP database entries, use the following command:
show vm-tracking local-vm {mac-address mac}
Example XNV Configuration
The following figure displays a sample XNV topology that will be used for the examples in the following
sections:
Advanced Features
116
Data Center Solutions
Figure 36: Sample XNV Topology
The example configuration supports the following:
• VM authentication using NMS server, network, or local authentication
• Ingress and egress port configuration for each VM
• VM movement from one switch port to another
• VM movement from one switch to another
Note
Ingress ACLs or policies apply to traffic flowing from the VM, into the switch port, and then to
the client. Egress ACLs apply to traffic flowing from the client, out the switch port, and to the
VM.
MAC and IP Addresses
The following are the MAC and IP addresses for the example topology:
VM1 MAC address: 00:04:96:27:C8:23
VM2 MAC address: 00:04:96:27:C8:24
VM1 IP address: 11.1.1.101
VM2 IP address: 11.1.1.102
Client1 MAC address: 00:04:96:00:00:01
Client2 MAC address: 00:04:97:00:00:02
Advanced Features
117
Data Center Solutions
Repository server IP address: 10.127.8.1
NMS server IP address: 10.127.5.221
General VLAN Configuration
The following is the core switch VLAN configuration:
create vlan v1
configure vlan v1 tag 100
configure vlan v1 add ports 1:22,1:23 tagged
configure vlan v1 ipaddress 11.1.1.50/24
The following is the Switch1 VLAN configuration:
create vlan v1
configure vlan v1 tag 100
configure vlan v1 add ports 21,22, 23 tagged
configure vlan v1 ipaddress 11.1.1.1/24
The following is the Switch2 VLAN configuration:
create vlan v1
configure vlan v1 tag 100
configure vlan v1 add ports 21,22 tagged
configure vlan v1 ipaddress 11.1.1.2/24
Note
For NMS server and network authentication, the NMS server and repository server must be
accessible to all XNV-enabled switches through VR-Mgmt.
VMWare Server Setup
The VMWare servers must be connected to Switch1 and Switch2 and should have dual quad-core
processors. The VMWare servers require the following software:
• VMWare server: ESXi license
• Vsphere EXSI client
• V-Center client
Each physical VMWare server should be configured with two VMs. Use the V-Center client to trigger
Vmotion.
Repository Server Setup
The repository server setup for this topology is the same for NMS server authentication and network
authentication. The following shows the FTP server setup:
FTP login: anonymous
Password: "" (no password)
Advanced Features
118
Data Center Solutions
Repository directory path: pub
[root@linux pub]# pwd
/var/ftp/pub
The following is an example MANIFEST file:
vm.map 2011-05-11 18:57:00
vpp.vpp 2011-05-11 18:57:00
nvpp1.pol 2011-05-11 18:57:00
nevpp1.pol 2011-05-11 18:57:00
nvpp2.pol 2011-05-11 18:57:00
nevpp2.pol 2011-05-11 18:57:00
The following is an example VMMAP file named vm.map:
<VMLIST>
<VM>
<MAC>00:04:96:27:C8:23</MAC>
<NAME>vm_1</NAME>
<IPV4>11.1.1.101</IPV4>
<VPP>nvpp1</VPP>
<CTag>1000</CTag>
<VRName>Vr-Default</VRName>
</VM>
<VM>
<MAC>00:04:96:27:C8:24</MAC>
<NAME>vm_2</NAME>
<IPV4>11.1.1.102</IPV4>
<VPP>nvpp2</VPP>
</VM>
</VMLIST>
The following is an example VPP file named vpp.vpp:
<vppList>
<vpp>
<name>nvpp1</name>
<last-updated>2011-05-30T09:00:00</last-updated>
<policy>
<name>nvpp1.pol</name>
<direction>ingress</direction>
<order>1</order>
</policy>
<policy>
<name>nevpp1.pol</name>
<direction>egress</direction>
<order>1</order>
<CTag>1000</CTag>
<VRName>Vr-Default</VRName>
</policy>
</vpp>
<vpp>
<name>nvpp2</name>
<last-updated>2011-05-30T09:00:00</last-updated>
<policy>
Advanced Features
119
Data Center Solutions
<name>nvpp2.pol</name>
<direction>ingress</direction>
<order>1</order>
</policy>
<policy>
<name>nevpp2.pol</name>
<direction>egress</direction>
<order>1</order>
</policy>
</vpp>
</vppList>
The following is the nvpp1.pol file:
entry nvpp1 {
if match all {
ethernet-destination-address 00:04:96:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count host1
} }
The following is the nvpp2.pol file:
entry nvpp2 {
if match all {
ethernet-destination-address 00:04:97:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count host2
} }
The following is the nevpp1.pol file:
entry nevpp1 {
if match all {
ethernet-source-address 00:04:96:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count h1
} }
The following is the nevpp2.pol file:
entry nevpp2 {
if match all {
ethernet-source-address 00:04:97:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count h2
} }
Advanced Features
120
Data Center Solutions
Example ACL Rules
The following are some example ACL rules:
entry etherType1 {
if {
ethernet-source-address 00:a1:f1:00:00:01;
}
then {
permit;
count etherType1;
}
}
entry denyall {
if {
source-address 10.21.1.1/32;
}
then {
deny;
}
}
entry allowall {
if {
source-address 11.1.1.1/32;
source-address 12.1.0.0/16;
}
then {
allow;
}
}
entry destIp {
if {
destination-address 192.20.1.0/24;
protocol UDP;
}
then {
deny;
count destIp;
}
}
entry denyAll {
if {
}
then {
deny;
count denyAll;
}
}
General Switch XNV Feature Configuration
The following configuration enables the XNV feature on the switch and the specified ports:
enable vm-tracking
enable vm-tracking ports 21-22
Advanced Features
121
Data Center Solutions
Local VM Authentication Configuration
If you only want to use local authentication, configure the XNV-enabled switches as follows:
configure vm-tracking authentication database-order local
To enable dynamic VLAN, issue the following command:
enable vm-tracking dynamic-vlan ports 19
To add Uplinkports to Dynamic VLAN:
configure vlan dynamic-vlan uplink-ports add ports <port_no>
To delete the uplink port:
configure vlan dynamic-vlan uplink-ports delete ports <port_no>
The following is the policy1.pol file for Port 21 in the ingress direction:
entry nvpp1 {
if match all {
ethernet-destination-address 00:04:96:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count host1
} }
The following is the policy2.pol file for Port 21 in the egress direction:
entry nevpp1 {
if match all {
ethernet-source-address 00:04:96:00:00:00 / ff:ff:ff:00:00:00 ;
} then {
deny ;
count h1
} }
The following commands configure VM authentication in the local database:
create vm-tracking local-vm mac-address 00:04:96:27:C8:23
configure vm-tracking local-vm mac-address 00:04:96:27:C8:23 ip-address
11.1.1.101
configure vm-tracking local-vm mac-address 00:04:96:27:C8:23 name myVm1
create vm-tracking vpp vpp1
configure vm-tracking vpp vpp1 add ingress policy policy1
configure vm-tracking vpp vpp1 add egress policy policy2
configure vm-tracking local-vm mac-address 00:04:96:27:C8:23 vpp vpp1
Advanced Features
122
Data Center Solutions
The following commands used to create VM-mac with vlan-tag, and Vr for Dynamic vlan creation:
create vm-tracking local-vm mac-address 00:00:00:00:00:01
configure vm-tracking local-vm mac-address 00:00:00:00:00:01 vpp lvpp1
configure vm-tracking local-vm mac-address 00:00:00:00:00:01 vlan-tag 1000 vr
VR-Default
configure vm-tracking vpp lvpp1 vlan-tag 2000
The following commands display the switch XNV feature status after configuration:
* Switch.67 # show vm-tracking local-vm
MAC Address
IP Address
Type
Value
-----------------------------------------------------------------------------00:00:00:00:00:01
VM
VPP
lvpp1
VLAN Tag 1000
VR Name VR-Default
Number of Local VMs: 1
* Switch.69 # show vm-tracking vpp
VPP Name
Type
Value
---------------------------------------------------------------------------------lvpp1
origin
local
counters
none
VLAN Tag
2000
VR Name Vr-Default
ingress
policy1
egress
policy2
Number of Local VPPs : 1
Number of Network VPPs: 0
Switch.71 # show vm-tracking
----------------------------------------------------------VM Tracking Global Configuration
----------------------------------------------------------VM Tracking
: Enabled
VM Tracking authentication order: nms vm-map local
VM Tracking nms reauth period
: 0 (Re-authentication disabled)
VM Tracking blackhole policy
: none
----------------------------------------------------------Port
VM Tracking
VM Tracking Dynamic VLAN
: 19
: Enabled
: Enabled
Flags
MAC
APC
IP Address
Type
Value
----------------------------------------------------------------------------------------------------------------------------------------------------------------Flags :
(A)uthenticated
(P)olicy Applied
Ingress
Advanced Features
: L - Local, N - NMS, V - VMMAP
: B - All Ingress and Egress, E - All Egress, I - All
123
Data Center Solutions
(C)ounter Installed : B - Both Ingress and Egress, E - Egress Only, I Ingress Only
Type :
IEP - Ingress Error Policies
EEP - Egress Error Policies
Number of Network VMs Authenticated: 0
Number of Local VMs Authenticated : 0
Number of VMs Authenticated
: 0
Switch.73 # show policy
Policies at Policy Server:
PolicyName
ClientUsage
Client
BindCount
-------------------------------------------------------------------------policy1
1
acl
1
policy2
1
acl
1
Network (VMMAP) Authentication Configuration
If you only want to use network authentication, configure the XNV-enabled switches as follows:
configure vm-tracking authentication database-order vm-map
After the repository server is configured (see Repository Server Setup on page 118), the following
commands can be used to display the switch XNV feature status:
* Switch.32 # show vm-tracking repository
--------------------------------VMMAP FTP Server Information
--------------------------------Primary VMMAP FTP Server :
Server name:
IP Address
: 10.127.8.1
VR Name
: VR-Mgmt
Path Name
: /pub (default)
User Name
: anonymous (default)
Secondary VMMAP FTP Server : Unconfigured
Last sync
: 16:56:11
Last sync server : Primary
Last sync status
: Successful
* Switch.69 # show vm-tracking vpp
VPP Name
Type
Name
--------------------------------------------------------------------------nvpp1
origin
network
ingress
nvpp1
egress
nevpp1
nvpp2
origin
network
ingress
nvpp2
egress
nevpp2
Number of Local VPPs : 0
Number of Network VPPs: 2
* Switch.15 # show vm-tracking
----------------------------------------------------------VM Tracking Global Configuration
-----------------------------------------------------------
Advanced Features
124
Data Center Solutions
VM Tracking
: Enabled
VM Tracking authentication order: vm-map
VM Tracking nms reauth period
: 0 (Re-authentication disabled)
VM Tracking blackhole policy
: none
----------------------------------------------------------Port
: 21
VM TRACKING
: ENABLED
Flags
MAC
AP
IP Address
Type
Name
--------------------------------------------------------------------------------00:04:96:27:c8:23 VB
11.1.1.101
VM
vm_1
VPP
nvpp1
00:04:96:27:c8:24 VB
11.1.1.102
VM
vm_2
VPP
nvpp2
--------------------------------------------------------------------------------Flags :
(A)uthenticated : L - Local, N - NMS, V - VMMAP
(P)olicy Applied : B - Both, E - Egress, I – Ingress
Number of Network VMs Authenticated
: 2
Number of Local VMs Authenticated
: 0
Number of VMs Authenticated
: 2
* Switch.16 # show vm-tracking network-vm
MAC Address
IP Address
Type
Name
-----------------------------------------------------------------------------00:04:96:27:c8:23 11.1.1.101
VM
vm_1
VPP
nvpp1
00:04:96:27:c8:23 11.1.1.102
VM
vm_2
VPP
nvpp2
Number of Network VMs: 2
* Switch.16 # show policy
Policies at Policy Server:
PolicyName
ClientUsage
Client
BindCount
-------------------------------------------------------------------------vmt/nvpp1
1
acl
1
vmt/nvpp2
1
acl
1
vmt/nevpp1
1
acl
1
vmt/nevpp2
1
acl
1
show vm-tracking nms server
VM Tracking NMS : enabled
VM Tracking NMS server connect time out: 3 seconds
Primary VM Tracking NMS server:
Server name :
IP address : 10.127.6.202
Server IP Port: 1812
Client address: 10.127.11.101 (VR-Mgmt)
Shared secret : qijxou
Access Requests : 0 Access Accepts : 0
Access Rejects : 0 Access Challenges : 0
Access Retransmits: 0 Client timeouts : 0
Bad authenticators: 0 Unknown types : 0
Round Trip Time : 0
Advanced Features
125
Data Center Solutions
NMS Server Authentication Configuration
•
If you only want to use NMS server authentication, configure the XNV-enabled switches as follows:
•
Configure the NMS server as follows:
configure vm-tracking authentication database-order nms
a Add Switch1 and Switch2 as RADIUS clients.
b Add the MAC addresses for VM1 and VM2 as users, and configure the passwords to match the
user names.
c Add a remote access policy with the Extreme Networks VSAs:
• Vendor code: 1916
• VSA ID: 213 (EXTREME_VM_NAME)
Example: MyVM1
• VSA ID: 214 (EXTREME_VM_VPP_NAME)
Example: nvpp1
• VSA ID: 215 (EXTREME_VM_IP_ADDR)
Example: 11.1.1.254
Note
For the Dynamic VLAN feature, the following VSAs are used:
EXTREME_VM_VLAN_ID with VSA ID as 216
EXTREME_VM_VR_NAME with VSA ID as 217
•
The following command configures the switch as an NMS server client:
configure vm-tracking nms primary server 10.127.5.221 client-ip 10.127.8.12
shared-secret secret
After the repository server is configured (see Repository Server Setup on page 118), the following
commands can be used to display the switch XNV feature status:
* Switch.33 # show vm-tracking nms server
VM Tracking NMS : enabled
VM Tracking NMS server connect time out: 3 seconds
Primary VM Tracking NMS server:
Server name
:
IP address
: 10.127.5.221
Server IP Port: 1812
Client address: 10.127.8.12 (VR-Mgmt)
Shared secret : qijxou
Access Requests
: 7
Access Accepts : 2
Access Rejects
: 5
Access Challenges : 0
Access Retransmits: 0
Client timeouts : 0
Bad authenticators: 0
Unknown types : 0
Round Trip Time
: 0
* Switch.32 # show vm-tracking
----------------------------------------------------------VM Tracking Global Configuration
-----------------------------------------------------------
Advanced Features
126
Data Center Solutions
VM Tracking
: Enabled
VM Tracking authentication order: nms
VM Tracking nms reauth period
: 0 (Re-authentication disabled)
VM Tracking blackhole policy
: none
----------------------------------------------------------Port
: 21
VM TRACKING
: ENABLED
Flags
MAC
AP
IP Address
Type
Name
----------------------------------------------------------------------------00:04:96:27:c8:23 VB
11.1.1.101
VM
vm_1
VPP
nvpp1
00:04:96:27:c8:24 VB
11.1.1.102
VM
vm_2
VPP
nvpp2
----------------------------------------------------------------------------Flags :
(A)uthenticated : L - Local, N - NMS, V - VMMAP
(P)olicy Applied : B - Both, E - Egress, I – Ingress
Number of Network VMs Authenticated: 1
Number of Local VMs Authenticated : 0
Number of VMs Authenticated : 1
* Switch.32 # show policy
Policies at Policy Server:
PolicyName ClientUsage Client BindCount
--------------------------------------------------------------------vmt/nvpp1 1 acl 1
vmt/nvpp2 1 acl 1
---------------------------------------------------------------------
Managing Direct Attach to Support VEPA
You should only enable the Direct Attach feature on ports that directly connect to a VM server running
VEPA software.
• To enable or disable the direct attach feature on a port, enter the command:
configure port port reflective-relay [on | off]
•
To see if the direct attach feature (reflective-relay) is enabled on a switch port, enter the command:
show ports information detail
Note
When the Direct Attach feature is configured on a port, the port number cannot be
included in the port list for a static FDB entry. For example, the Direct-Attach enabled
port can be the only port number specified in a static FDB entry, but it cannot be included
in a port-list range for a static FDB entry.
Managing the FIP Snooping Feature
Advanced Features
127
Data Center Solutions
Introduction to FIP Snooping
Many data centers use Ethernet for TCP/IP networks and Fibre Channel for storage area networks
(SANs).
Implementing Fibre Channel over Ethernet (FCoE) allows transmission over Ethernet networks, while
preserving Fibre Channel’s lossless, point-to-point transmission ability for reliable and efficient access
of disk servers. FCoE is part of the International Committee for Information Technology Standards T11
FC-BB-5 standard.
FCoE Initialization Protocol (FIP) allows Ethernet nodes (Enode) to find, and set up virtual links with,
FCoE forwarders (FCFs) that then connect to the fibre channel fabric.
FIP snooping monitors FCoE’s virtual links and suppresses traffic not related to maintaining or
establishing these virtual links to achieve a level of security comparable to native Fibre Channel.
FIP Snooping Requirements
FIP snooping requires the following capabilities:
•
•
•
Priority flow control (PFC) enabled
Data center bridging capability exchange (DCBX) enabled
FCoE application priority advertised by DCBX
Extreme’s Implementation of FIP Snooping
This section describes the Extreme Networks implementation of FIP snooping in more detail.
Supported Platforms
FIP snooping is supported on the following Extreme platforms:
•
•
•
•
BlackDiamond X8
BlackDiamond 8800 series BD 8900-40G6X-xm
Summit X670
Summit X770
Limitations
•
•
VLAN discovery is not supported, only configured FIP VLANs.
Virtual links between FCFs are not monitored.
Example FIP Snooping Configuration
The following figure illustrates an example FIP snooping configuration.
Advanced Features
128
Data Center Solutions
Figure 37: Example FIP Snooping Configuration
The following commands enable FIP snooping on VLAN “v1” with two ports (1:1 and 1:2) with PFC,
jumbo frames, and DCBX enabled.
create vlan "v1"
configure vlan v1 tag 20
configure vlan v1 add ports 1:1-2 tagged
create qosprofile qp4
configure qosscheduler weighted-round-robin
configure qosprofile qp4 weight 1
enable jumbo-frame ports 1:1-2
enable flow-control rx-pause qosprofile qp4 ports 1:1-2
enable flow-control tx-pause priority 3 ports 1:1-2
enable lldp ports 1:1-2
configure lldp ports 1:1-2 advertise vendor-specific dcbx baseline
configure lldp ports 1:1-2 dcbx add application name fcoe priority 3
configure lldp ports 1:1-2 dcbx add application name fip priority 3
configure fip snooping add vlan v1
configure fip snooping vlan v1 port 1:1 location perimeter
configure fip snooping vlan v1 port 1:2 location fcf-to-enode
enable fip snooping vlan v1
Advanced Features
129
6 Advanced Feature Commands
clear counters bfd
clear counters cfm segment all frame-delay
clear counters cfm segment all frame-loss
clear counters cfm segment all
clear counters cfm segment frame-delay
clear counters cfm segment frame-loss mep
clear counters cfm segment frame-loss
clear counters cfm segment <segment_name>
clear ethernet oam counters
show vm-tracking repository
clear msrp counters
clear mvrp counters
clear network-clock gptp counters
clear openflow counters
clear trill counters
configure bfd vlan authentication
configure bfd vlan
configure cfm domain add association integer
configure cfm domain add association string
configure cfm domain add association vlan-id
configure cfm domain add association vpn-id oui index
configure cfm domain association add remote-mep
configure cfm domain association add
configure cfm domain association delete remote-mep
configure cfm domain association delete
configure cfm domain association destination-mac-type
configure cfm domain association end-point add group
configure cfm domain association end-point delete group
configure cfm domain association end-point transmit-interval
configure cfm domain association ports end-point ccm
configure cfm domain association ports end-point mepid
configure cfm domain association ports end-point sender-id-ipaddress
configure cfm domain association ports end-point
configure cfm domain association remote-mep mac-address
configure cfm domain delete association
configure cfm domain md-level
configure cfm group add rmep
Advanced Features
130
Advanced Feature Commands
configure cfm group delete rmep
configure cfm segment add domain association
configure cfm segment delete domain association
configure cfm segment dot1p
configure cfm segment frame-delay dot1p
configure cfm segment frame-delay window
configure cfm segment frame-delay/frame-loss transmit interval
configure cfm segment frame-loss consecutive
configure cfm segment frame-loss dot1p
configure cfm segment frame-loss mep
configure cfm segment frame-loss ses-threshold
configure cfm segment frame-loss window
configure cfm segment threshold
configure cfm segment timeout
configure cfm segment transmit-interval
configure cfm segment window
configure fip snooping add fcf
configure fip snooping add vlan
configure fip snooping delete fcf
configure fip snooping delete vlan
configure fip snooping fcf-update
configure fip snooping fcmap
configure fip snooping port location
configure lldp ports dcbx add application
configure lldp ports dcbx delete application
configure lldp ports vendor-specific dcbx
configure mrp ports timers
configure msrp latency-max-frame-size
configure msrp ports sr-pvid
configure msrp ports traffic-class delta-bandwidth
configure msrp timers first-value-change-recovery
configure mvrp stpd
configure mvrp tag ports registration
configure mvrp tag ports transmit
configure mvrp vlan auto-creation
configure mvrp vlan registration
configure network-clock gptp default-set
configure network-clock gptp ports announce
configure network-clock gptp ports peer-delay
configure network-clock gptp ports sync
configure openflow controller
configure port reflective-relay
Advanced Features
131
Advanced Feature Commands
configure snmp traps batch-delay bfd
configure trill add access tag
configure trill add network vlan
configure trill appointed-forwarder
configure trill delete access tag
configure trill delete network vlan
configure trill designated-vlan
configure trill inhibit-time
configure trill mtu probe fail-count
configure trill mtu probe
configure trill mtu size
configure trill nickname
configure trill ports protocol
configure trill ports
configure trill pseudonode
configure trill system-id
configure trill timers csnp
configure trill timers hello
configure trill timers lsp
configure trill timers spf backoff-delay
configure trill timers spf
configure trill tree prune vlan
configure vlan dynamic-vlan uplink-ports
configure vm-tracking authentication database-order
configure vm-tracking blackhole
configure vm-tracking local-vm
configure vm-tracking nms timeout
configure vm-tracking nms
configure vm-tracking repository
configure vm-tracking timers
configure vm-tracking vpp add
configure vm-tracking vpp counters
configure vm-tracking vpp delete
configure vm-tracking vpp vlan-tag
create cfm domain dns md-level
create cfm domain mac md-level
create cfm domain string md-level
create cfm segment destination
create trill nickname
create vm-tracking local-vm
create vm-tracking vpp
debug openflow show flows
Advanced Features
132
Advanced Feature Commands
debug openflow
delete cfm domain
delete cfm segment
delete trill nickname
delete vm-tracking local-vm
delete vm-tracking vpp
disable avb ports
disable avb
disable cfm segment frame-delay measurement
disable cfm segment frame-loss measurement mep
disable ethernet oam ports link-fault-management
disable fip snooping
disable msrp
disable mvrp ports
disable mvrp
disable network-clock gptp ports
disable network-clock gptp
disable openflow vlan
disable openflow
disable snmp traps bfd
disable trill
disable vm-tracking dynamic-vlan ports
disable vm-tracking ports
disable vm-tracking
disable msrp ports
enable avb ports
enable avb
enable cfm segment frame-delay measurement
enable cfm segment frame-loss measurement mep
enable ethernet oam ports link-fault-management
enable fip snooping
enable msrp ports
enable msrp
enable mvrp ports
enable mvrp
enable network-clock gptp ports
enable network-clock gptp
enable openflow vlan
enable openflow
enable snmp traps bfd
enable trill
enable vm-tracking dynamic-vlan ports
Advanced Features
133
Advanced Feature Commands
enable vm-tracking ports
enable vm-tracking
enable/disable bfd vlan
ping mac port
ping trill
run vm-tracking repository
show avb
show bfd counters
show bfd session client
show bfd session counters vr all
show bfd session detail vr all
show bfd session vr all
show bfd vlan counters
show bfd vlan
show bfd
show cfm detail
show cfm groups
show cfm segment frame-delay statistics
show cfm segment frame-delay
show cfm segment frame-delay/frame-loss mep id
show cfm segment frame-loss statistics
show cfm segment frame-loss
show cfm segment mep
show cfm segment
show cfm
show ethernet oam
show fip snooping access-list
show fip snooping counters
show fip snooping enode
show fip snooping fcf
show fip snooping virtual-link
show fip snooping vlan
show lldp dcbx
show mrp ports
show msrp listeners
show msrp ports bandwidth
show msrp ports counters
show msrp ports
show msrp streams
show msrp talkers
show msrp
show mvrp ports counters
Advanced Features
134
Advanced Feature Commands
show mvrp tag
show mvrp
show network-clock gptp ports
show network-clock gptp
show openflow controller
show openflow flows
show openflow vlan
show openflow
show snmp traps bfd
show trill distribution-tree
show trill lsdb
show trill neighbor
show trill ports
show trill rbridges
show trill
show vlan dynamic-vlan
show vm-tracking local-vm
show vm-tracking network-vm
show vm-tracking nms
show vm-tracking port
show vm-tracking repository
show vm-tracking vpp
show vm-tracking
traceroute mac port
traceroute trill
unconfigure avb
unconfigure bfd vlan
unconfigure cfm domain association end-point transmit-interval
unconfigure mrp ports timers
unconfigure msrp
unconfigure mvrp stpd
unconfigure mvrp tag
unconfigure mvrp
unconfigure network-clock gptp ports
unconfigure openflow controller
unconfigure vm-tracking local-vm
unconfigure vm-tracking nms
unconfigure vm-tracking repository
unconfigure vm-tracking vpp vlan-tag
unconfigure vm-tracking vpp
Advanced Features
135
Advanced Feature Commands
clear counters bfd
clear counters bfd {session | interface}
Description
Clears the counters associated with BFD specific settings.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to clear the counters in the BFD session or interface (VLAN). If neither session or
interface are specified, the command clears all counters in BFD.
Example
The following command clears all counters in BFD:
clear counters bfd
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
clear counters cfm segment all frame-delay
clear counters cfm segment all frame-delay
Description
This command clears only frame-delay information for all existing segments.
Advanced Features
136
Advanced Feature Commands
Syntax Description
N/A.
Default
N/A.
Usage Guidelines
Use this command to clear only frame-delay information for all existing segments.
Example
E4G-200.70 # clear co cfm seg all frame-delay
E4G-200.71 #
E4G-200.71 #
E4G-200.71 #
E4G-200.71 # sho cfm segment
CFM Segment Name
: cs10
Domain Name
: dom1
Association
: a10
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 30
Frames Received
: 1
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:59 2012
Min Delay
: Mon Mar 12 10:28:59 2012
Max Delay
: Mon Mar 12 10:28:59 2012
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 10
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Advanced Features
137
Advanced Feature Commands
Total Frames to be sent
:
Frames Transmitted
:
Pending Frames
:
Frames Received
:
Availability Status
:
Unavailability Start Time :
Unavailability End Time
:
Tx Start Time
:
CFM Segment Name
Domain Name
Association
MD Level
Destination MAC
Frame Delay:
DMM Transmission
Transmission Mode
Total Frames to be sent
Frames Transmitted
Pending Frames
Frames Received
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames
Frame Loss:
LMM Tx Interval
SES Threshold
Consecutive Available Count
Measurement Window Size
Class of Service
Total Configured MEPs
Total Active MEPs
MEP ID
:
LMM Transmission
:
Transmission Mode
:
Total Frames to be sent
:
Frames Transmitted
:
Pending Frames
:
Frames Received
:
Availability Status
:
Unavailability Start Time :
Unavailability End Time
:
Tx Start Time
:
CFM Segment Name
Domain Name
Association
MD Level
Destination MAC
Frame Delay:
DMM Transmission
Advanced Features
45
4
30
4
Available
None
None
Mon Mar 12 10:28:29 2012
: cs11
: dom1
: a11
: 1
: 00:04:96:52:a7:38
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
In Progress
On Demand
45
1
30
1
10 secs
50 msec
10 %
95 %
60
6
Mon Mar 12 10:28:59 2012
Mon Mar 12 10:28:59 2012
Mon Mar 12 10:28:59 2012
None
Not Set
0
: 10 secs
: 1.000000e-02
: 4
: 1200
: 6
: 1
: 1
11
In Progress
On Demand
45
12
30
12
Available
None
None
Mon Mar 12 10:27:09 2012
: cs12
: dom1
: a12
: 1
: 00:04:96:52:a7:38
: In Progress
138
Advanced Feature Commands
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 30
Frames Received
: 1
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:59 2012
----------------------------------------------------------Total Configured Segments
: 11
Total Active Segments
: 11
E4G-200.72 #
E4G-200.72 #
E4G-200.72 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment all frame-loss
clear counters cfm segment all frame-loss
Description
This command clears only frame-loss information for all existing segments.
Syntax Description
N/A.
Default
N/A.
Usage Guidelines
Use this command to clear only frame-loss information for all existing segments.
Advanced Features
139
Advanced Feature Commands
Example
E4G-200.72 # clear co cfm seg all frame-loss
E4G-200.73 #
E4G-200.73 #
E4G-200.73 #
E4G-200.73 # sho cfm segment
CFM Segment Name
: cs10
Domain Name
: dom1
Association
: a10
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 2
Pending Frames
: 29
Frames Received
: 2
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:59 2012
Min Delay
: Mon Mar 12 10:29:09 2012
Max Delay
: Mon Mar 12 10:29:09 2012
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 10
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 29
Frames Received
: 0
Availability Status
: Idle
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: None
CFM Segment Name
: cs11
Domain Name
: dom1
Association
: a11
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Advanced Features
140
Advanced Feature Commands
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 2
Pending Frames
: 29
Frames Received
: 2
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:59 2012
Min Delay
: Mon Mar 12 10:29:09 2012
Max Delay
: Mon Mar 12 10:28:59 2012
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 11
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 28
Frames Received
: 0
Availability Status
: Idle
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: Mon Mar 12 10:29:19 2012
CFM Segment Name
: cs12
Domain Name
: dom1
Association
: a12
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 2
Pending Frames
: 29
Frames Received
: 2
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:59 2012
----------------------------------------------------------Total Configured Segments
: 11
Total Active Segments
: 11
Advanced Features
141
Advanced Feature Commands
E4G-200.74 #
E4G-200.74 #
E4G-200.74 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment all
clear counters cfm segment all
Description
This command clears both frame-delay and frame-loss information for all existing segments.
Syntax Description
N/A.
Default
N/A.
Usage Guidelines
Use this command to clear both frame-delay and frame-loss information for all existing segments.
Example
E4G-200.53 # clear co cfm seg all
E4G-200.54 # sho cfm seg
CFM Segment Name
:
Domain Name
:
Association
:
MD Level
:
Destination MAC
:
Frame Delay:
DMM Transmission
: In
Transmission Mode
: On
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 42
Frames Received
: 0
Advanced Features
cs10
dom1
a10
1
00:04:96:52:a7:38
Progress
Demand
142
Advanced Feature Commands
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames
Frame Loss:
LMM Tx Interval
SES Threshold
Consecutive Available Count
Measurement Window Size
Class of Service
Total Configured MEPs
Total Active MEPs
MEP ID
:
LMM Transmission
:
Transmission Mode
:
Total Frames to be sent
:
Frames Transmitted
:
Pending Frames
:
Frames Received
:
Availability Status
:
Unavailability Start Time :
Unavailability End Time
:
Tx Start Time
:
CFM Segment Name
Domain Name
Association
MD Level
Destination MAC
Frame Delay:
DMM Transmission
Transmission Mode
Total Frames to be sent
Frames Transmitted
Pending Frames
Frames Received
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames
Frame Loss:
LMM Tx Interval
SES Threshold
Advanced Features
:
:
:
:
:
:
:
:
:
:
:
:
10 secs
50 msec
10 %
95 %
60
6
None
None
None
None
None
0
: 10 secs
: 1.000000e-02
: 4
: 1200
: 6
: 1
: 1
10
In Progress
On Demand
45
0
42
0
Idle
None
None
None
: cs11
: dom1
: a11
: 1
: 00:04:96:52:a7:38
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
In Progress
On Demand
45
0
42
0
10 secs
50 msec
10 %
95 %
60
6
Mon Mar 12 10:26:39 2012
Mon Mar 12 10:26:49 2012
Mon Mar 12 10:26:49 2012
None
None
0
: 10 secs
: 1.000000e-02
143
Advanced Feature Commands
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 11
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 42
Frames Received
: 0
Availability Status
: Idle
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: None
CFM Segment Name
: cs12
Domain Name
: dom1
Association
: a12
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 42
Frames Received
: 0
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:26:39 2012
Min Delay
: Mon Mar 12 10:26:49 2012
Max Delay
: Mon Mar 12 10:26:39 2012
Last Alarm Time
: None
Alarm State
: None
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 12
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 41
Frames Received
: 1
Availability Status
: Available
----------------------------------------------------------Total Configured Segments
: 11
Advanced Features
144
Advanced Feature Commands
Total Active Segments
E4G-200.55 #
E4G-200.55 #
E4G-200.55 #
E4G-200.55 #
: 11
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment frame-delay
clear counters cfm segment segment_name frame-delay
Description
This command clears only frame-delay information for segment with given segment name.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to clear only frame-delay information for segment with given segment name.
Example
E4G-200.59 # clear co cfm seg cs10 frame-delay
E4G-200.60 #
E4G-200.60 #
E4G-200.60 #
E4G-200.60 # sho cfm seg cs10
CFM Segment Name
: cs10
Domain Name
: dom1
Association
: a10
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
Advanced Features
145
Advanced Feature Commands
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 34
Frames Received
: 1
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:19 2012
Min Delay
: Mon Mar 12 10:28:19 2012
Max Delay
: Mon Mar 12 10:28:19 2012
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 10
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 8
Pending Frames
: 34
Frames Received
: 8
Availability Status
: Available
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: Mon Mar 12 10:27:09 2012
----------------------------------------------------------Total Configured Segments
: 11
Total Active Segments
: 11
E4G-200.61 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment frame-loss mep
clear counters cfm segment segment_name frame-loss mep mep_id
Advanced Features
146
Advanced Feature Commands
Description
This command clears only frame-loss information for the given MEP in segment with given segment
name.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to clear only frame-loss information for the given MEP in segment with given
segment name.
Example
E4G-200.24 # clear counters cfm segment "cs2" frame-loss mep 3
E4G-200.25 #
E4G-200.25 #
E4G-200.25 #
E4G-200.25 # sho cfm segment
CFM Segment Name
: cs2
Domain Name
: dom2
Association
: a2
MD Level
: 2
Destination MAC
: 00:04:96:52:a7:64
Frame Delay:
DMM Transmission
: Disabled
Frames Transmitted
: 0
Frames Received
: 0
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: None
Min Delay
: None
Max Delay
: None
Last Alarm Time
: None
Alarm State
: None
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Advanced Features
147
Advanced Feature Commands
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 3
LMM Transmission
: In Progress
Transmission Mode
: Continuous
Frames Transmitted
: 0
Frames Received
: 0
Availability Status
: Idle
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: None
----------------------------------------------------------Total Configured Segments
: 1
Total Active Segments
: 1
E4G-200.26 #
E4G-200.26 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment frame-loss
clear counters cfm segment segment_name frame-loss
Description
This command clears only frame-loss information for segment with given segment name for all
associated MEPs.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to clear only frame-loss information for segment with given segment name for all
associated MEPs.
Advanced Features
148
Advanced Feature Commands
Example
E4G-200.61 # clear co cfm seg cs10 frame-loss
E4G-200.62 #
E4G-200.62 #
E4G-200.62 #
E4G-200.62 # sho cfm seg cs10
CFM Segment Name
: cs10
Domain Name
: dom1
Association
: a10
MD Level
: 1
Destination MAC
: 00:04:96:52:a7:38
Frame Delay:
DMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 34
Frames Received
: 1
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: Mon Mar 12 10:28:19 2012
Min Delay
: Mon Mar 12 10:28:19 2012
Max Delay
: Mon Mar 12 10:28:19 2012
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 10
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 1
Pending Frames
: 33
Frames Received
: 1
Availability Status
: Available
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: Mon Mar 12 10:28:29 2012
----------------------------------------------------------Total Configured Segments
: 11
Total Active Segments
: 11
E4G-200.63 #
E4G-200.63 #
E4G-200.63 #
Advanced Features
149
Advanced Feature Commands
E4G-200.63 #
E4G-200.63 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
clear counters cfm segment <segment_name>
clear counters cfm segment segment_name
Description
This command clears both frame-delay and frame-loss information for segment with given segment
name.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to clear both frame-delay and frame-loss information for segment with given
segment name.
Example
E4G-200.56 # clear co cfm seg cs2
E4G-200.57 #
E4G-200.57 # sho cfm seg cs2
CFM Segment Name
:
Domain Name
:
Association
:
MD Level
:
Destination MAC
:
Frame Delay:
DMM Transmission
: In
Transmission Mode
: On
Total Frames to be sent
: 45
Advanced Features
cs2
dom1
a2
1
00:04:96:52:a7:38
Progress
Demand
150
Advanced Feature Commands
Frames Transmitted
: 0
Pending Frames
: 40
Frames Received
: 0
DMM Tx Interval
: 10 secs
DMR Rx Timeout
: 50 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 6
Tx Start Time
: None
Min Delay
: None
Max Delay
: None
Last Alarm Time
: None
Alarm State
: None
Lost Frames
: 0
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 2
LMM Transmission
: In Progress
Transmission Mode
: On Demand
Total Frames to be sent
: 45
Frames Transmitted
: 0
Pending Frames
: 40
Frames Received
: 0
Availability Status
: Idle
Unavailability Start Time : None
Unavailability End Time
: None
Press <SPACE> to continue or <Q> to quit:
Tx Start Time
: None
----------------------------------------------------------Total Configured Segments
: 11
Total Active Segments
: 11
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
E4G-200.58 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
Advanced Features
151
Advanced Feature Commands
clear ethernet oam counters
clear ethernet oam {ports [port_list} counters
Description
Clears Ethernet OAM counters.
Syntax Description
port_list
Specifies the particular port(s).
Default
N/A.
Usage Guidelines
Use this command to clear the Ethernet OAM counters on one or more specified ports. If you do not
specify the port(s), counters for all ports are cleared.
Example
The following command clears Ethernet OAM counters on port 2:
clear ethernet oam ports 2 counters
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on the Summit X450a series switch only.
show vm-tracking repository
show vm-tracking repository {primary | secondary}
Description
Displays the FTP file synchronization configuration for NVPP and VMMAP files.
Advanced Features
152
Advanced Feature Commands
Syntax Description
primary | secondary
Specifies whether you are displaying the primary or secondary FTP server
configuration.
Default
If you do not specify primary or secondary, the default action is to display both the primary and
secondary FTP server configurations.
Usage Guidelines
None.
Example
The following command displays the configuration for the primary and secondary FTP servers:
show vm-tracking repository
Primary VM-Map FTP server:
Server name:
IP address
: 10.100.1.200
VR Name
: VR-Mgmt
Refresh-interval: 600 seconds
Path Name
: /pub (default)
User Name
: anonymous (default)
Secondary vm-map FTP server: Unconfigured
Last sync
: 16:35:15
Last sync server
Last sync status : Successful
: Primary
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
clear msrp counters
clear msrp counters {ports [port_list | all]}
Description
Clears both the PDU and attribute event counters per port.
Advanced Features
153
Advanced Feature Commands
Syntax Description
msrp
Multiple Stream Registration Protocol.
counters
MSRP packet and attribute event counters.
port_list
Port list separated by a comma or "-".
all
All ports.
Default
N/A.
Usage Guidelines
Use this command to clear both the PDU and attribute event counters per port.
Example
clear msrp counters
clear msrp counters ports 1-5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
clear mvrp counters
clear mvrp counters {event | packet} {ports [port_list | all]}
Description
Clears MVRP statistics.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
event
MVRP event counters.
packet
MVRP packet counters.
Advanced Features
154
Advanced Feature Commands
Default
Clears both event and packet counters if none of the options are specified.
Usage Guidelines
Use this command to clear MVRP statistics. The default behavior clears both event and packet counters
if none of the options are specified. The statistics that are reset are the number of failed registrations on
that port, number of MVRPDUs sent, number of MVRPDUs received with error and without error for
packet counters and different MVRP events rx/tx counters for event counters. If no port is specified,
MVRP statistics of all ports are reset.
Example
The following command clears event counters:
clear mvrp event counters
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
clear network-clock gptp counters
clear network-clock gptp ports counters {ports [port_list | all]}
Description
Clears gPTP port counters.
Syntax Description
gptp
IEEE 802.1AS Generalized Precision Time Protocol.
counters
gPTP port counters.
port_list
Specifies one or more of the switch's physical ports.
all
Specifies all of the switch's physical ports.
Default
N/A.
Advanced Features
155
Advanced Feature Commands
Usage Guidelines
Use this command to clear gPTP port counters. The command clear counters also clears the gPTP
port counters (along with all other counters).
Example
clear network-clock gptp counters
clear network-clock gptp counters ports 2-4
clear network-clock gptp counters ports all
History
This command was first available in ExtremeXOS 15.3
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
clear openflow counters
clear openflow counters {flow | controller {primary | secondary}}
Description
Globally clears the flow error count, packets sent and received. controller {primary |
secondary} clears the connection counters of the primary, secondary, or both controllers.
Syntax Description
This command has no keywords or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command clears Openflow counters on the switch:
clear openflow counters
Advanced Features
156
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
clear trill counters
clear trill counters
Description
This command clears all protocol and port counters associated with TRILL.
Syntax Description
trill
Transparent Interconnection of Lots of Links
counters
Reset all TRILL counters to zero.
Default
N/A.
Usage Guidelines
Use this command to clear all protocol and port counters associated with TRILL.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
Advanced Features
157
Advanced Feature Commands
configure bfd vlan authentication
configure bfd vlan vlan_name authentication [none | simple-password {encrypted}
password]]
Description
Configures authentication for BFD on a VLAN.
Syntax Description
vlan_name
Specifies the VLAN name.
none
Specifies that no authentication is to be used. (Default)
encrypted
Indicates that the password is already encrypted.
password
Specifies a simple password to use to authenticate.
Default
The authentication default is none.
Usage Guidelines
Use this command to configure authentication for BFD on a VLAN using a password or specify that
none is required.
Use the show bfd vlan command to display the authentication setting.
The encrypted keyword is primarily for the output of the show configuration command, so that the
password is not revealed in the command output. Do not use it to set the password
Example
The following command configures authentication using the password password:
configure bfd vlan vlan1 authentication simple-password password
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
Advanced Features
158
Advanced Feature Commands
configure bfd vlan
configure bfd vlan vlan_name [{detection-multiplier multiplier} {receive-interval
rx_interval} {transmit-interval tx_interval}]
Description
Configures BFD transmit (TX) and receive (RX) intervals and multipliers on the VLAN.
Syntax Description
vlan_name
Specifies the VLAN.
multiplier
Specifies the detection multiplier. The range is 1 to 255.
rx_interval
Specifies the receive interval for control packets in milliseconds. The range is
100 to 4294967 ms.
tx_interval
Specifies the transmit interval for control packets in milliseconds. The range is
100 to 4294967 ms.
Default
The default value for RX and TX intervals is 1000 ms.
The default value for the detection-multiplier is 3.
Usage Guidelines
Use this command to configure BFD.
Use the show bfd vlan command to display the current settings.
Example
The following command configures a transmit and receive interval of 2000 ms and a detection
multiplier of 2 on the VLAN vlan1:
configure bfd vlan vlan1 detection-multiplier 2 receive-interval 2000
transmit-interval 2000
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
Advanced Features
159
Advanced Feature Commands
configure cfm domain add association integer
configure cfm domain domain_name add association integer int [vlan vlan_name|vman
vman_name]
Description
Creates a maintenance association (MA) related to a specified maintenance domain (MD). This
command supports the 2-octet integer MA format.
Syntax Description
domain_name
Specifies the domain you want to associate with this MA.
int
Enter an integer to name the MA. The range is 0 to 65535.
vlan_name
Specifies the VLAN you want to assign to this MA. Each MA contains only one
VLAN, VMAN, BVLAN or SVLAN.
vman_name
Specifies the VMAN you want to assign to this MA.
Default
N/A.
Usage Guidelines
All ports configured on the specified VLAN are now CFM ports in the specified MA.
You add the MA, or association, to the domain, and the MA uses the MD level assigned to the domain.
Each MA can belong to only one domain, but several MAs can belong to a given domain. The MA is
unique within a given domain.
Example
The following command creates a 2-octet integer MA (350) that associates the domain brazil and the
VLAN admin:
configure cfm domain brazil add association integer 350 vlan admin
History
This command was first available in ExtremeXOS 11.4.
The SVLAN option was added in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
Advanced Features
160
Advanced Feature Commands
configure cfm domain add association string
configure cfm domain domain_name add association string name [vlan vlan_name|vman
vman_name]
Description
Creates a maintenance association (MA) related to a specified maintenance domain (MD). This
command supports the character string MA format.
Syntax Description
domain_name
Specifies the domain you want to associate with this MA.
string
Enter up to 45 alphanumeric characters to name the MA.
vlan_name
Specifies the VLAN you want to assign to this MA. Each MA contains only one
VLAN, VMAN, or BVLAN.
vman_name
Specifies the VMAN you want to assign to this MA.
Default
N/A.
Usage Guidelines
All ports configured on the specified VLAN are now CFM ports in the specified MA.
You add the MA, or association, to the domain, and the MA uses the MD level assigned to the domain.
Each MA can belong to only one domain, but several MAs can belong to a given domain. The MA is
unique within a given domain.
Example
The following command creates an MA named service that associates the MD spain and the VLAN
finance:
configure cfm domain service add association string spain vlan finance
History
This command was first available in ExtremeXOS 11.4.
The SVLAN option was added in ExtremeXOS 12.4.
Advanced Features
161
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
configure cfm domain add association vlan-id
configure cfm domain domain_name add association vlan-id vlanid [vlan vlan_name|
vman vman_name]
Description
Creates a maintenance association (MA) related to a specified maintenance domain (MD). This
command supports the VLAN ID MA format.
Syntax Description
domain_name
Specifies the domain you want to associate with this MA.
vlanid
Specifies the VLAN ID.
vlan_name
Specifies the VLAN you want to assign to this MA. Each MA contains only one
VLAN, VMAN, or BVLAN.
vman_name
Specifies the VMAN you want to assign to this MA.
Default
N/A.
Usage Guidelines
All ports configured on the specified VLAN are now CFM ports in the specified MA.
You add the MA, or association, to the domain, and the MA uses the MD level assigned to the domain.
Each MA can belong to only one domain, but several MAs can belong to a given domain. The MA is
unique within a given domain.
History
This command was first available in ExtremeXOS 12.1.
The SVLAN option was added in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
Advanced Features
162
Advanced Feature Commands
configure cfm domain add association vpn-id oui index
configure cfm domain domain_name add association vpn-id oui oui index index [vlan
vlan_name| meg meg_name|vman vman_name]
Description
Creates a maintenance association (MA) related to a specified maintenance domain (MD). This
command supports the RFC 2685 VPN ID MA format.
Syntax Description
domain_name
Specifies the domain you want to associate with this MA.
association
IEEE 802.1ag Maintenance Association or ITU-T Y.1731 Maintenance Entity
Group
oui
Enter a virtual private network (VPN) Organizational Unique Identifier (OUI)
in the format XX:XX:XX as part of the name for the MA.
index
Enter the 32-bit VPN index you want to append to the OUI to name the MA.
The range is 0 to 4294967295.
vlan_name
Specifies the VLAN you want to assign to this MA. Each MA contains only one
VLAN, VMAN, or BVLAN.
vman_name
Specifies the VMAN you want to assign to this MA.
meg
ITU-T Y.1731 Maintenance Entity Group.
meg_name
MEG name, maximum of 12 characters with 6 bytes ITU Carrier Code and 6
bytes organization specific unique MEG ID code.
Default
N/A.
Usage Guidelines
All ports configured on the specified VLAN are now CFM ports in the specified MA. You add the MA, or
association, to the domain, and the MA uses the MD level assigned to the domain. Each MA can belong
to only one domain, but several MAs can belong to a given domain. The MA is unique within a given
domain.
Example
The following command creates an MA with the VPN ID of 11:22:33 50 that associates the domain spain
and the VLAN accounting:
configure cfm domain spain add association vpn-id oui 11:22:33 index 50 vlan
accounting
Advanced Features
163
Advanced Feature Commands
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm domain association add remote-mep
configure cfm domain domain_name association association_name add remote-mep
mepid { mac_address mac_address }
Description
Allows you to add a remote MEP with the given MEP ID and MAC address to an existing association.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
mepid
Enter the MEP ID of the remote MEP being added. The range is 1 to 8191.
mac_address
Specifies the MAC address for the remote MEP being added.
Default
N/A.
Usage Guidelines
Use this command to add a remote MEP with given MEP ID and MAC address to an existing association.
Use the show cfm detail command to verify your configuration.
Note
Because the Summit X460 does not support unicast CCM generation, creating an RMEP with
unicast MAC address is not meaningful. Therefore, it is an optional parameter on E4G400,
E4G200, and Summit X460 platforms.
History
This command was first available in ExtremeXOS 12.1.
Platform Availability
This command is available on all platforms.
Advanced Features
164
Advanced Feature Commands
configure cfm domain association add
configure cfm domain domain_name association association_name [ports port_list
add [[end-point [up|down] mepid { group group_name } ] | [intermediate-point]]
Description
This command allows you to create an up MEP, down MEP, intermediate-point (MIP) on a maintenance
association, a group. You can also combine different maintenance points.
Combining different Maintenance points is restricted per the following:
• Up MEP and Down MEP in a single association is not allowed.
• Down MEP and MIP in a single association is not allowed.
• More than one Up MEP in a single association is not allowed.
• Up MEP and MIP in a single association is allowed.
• More than one Down MEP in a single association is allowed.
• A group can be created while creating a MEP.
• With CFM Support over VPLS, this command is used to associate pseudo wires of a VPLS service
instance to an association & domain.
• Portlist can have only one port configured for a MEP configuration but can have multiple ports in
MIP configuration, when Hwaoam is supported on the system.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Specifies the port number(s).
up
Enter the port to be the UP port of the MA; this MEP sends CCM messages to
all ports—other than the sending switch port—in this MA on this switch.
down
Enter the port to be the DOWN port of the MA; this MEP sends CCM
messages out of the configured physical port.
mepid
Specifies a value for this MEP. The range is 1 to 8191.
NOTE: On each MA, each MEPID must be unique.
group
CFM group that binds an LMEP to RMEPS. If not specified, the client does not
receive events from the respective RMEPs.
group_name
Group name, maximum of 31 characters.
Default
N/A.
Usage Guidelines
These ports must already be in the MA (VLAN or VMAN) prior to assigning a MEP function to them. If
you try to assign a port not in the MA as an end-point, the system returns the following message:
Advanced Features
165
Advanced Feature Commands
The following port(s) <portlist> are not part of the associations VLAN.
Note
Ensure that you assigned the port number correctly to the UP MEP and to the DOWN MEP, or
the CCM messages go in the wrong direction.
Each MA needs at least two MEPs that can reach each other to exchange CCM messages.
You can also combine different maintenance points. The following are CLI restrictions on MP
combinations:
• DOWN and UP MEP cannot be present on the same association
• DOWN MEP and MIP cannot be present on the same association
• UP MEP and MIP can be present on the same association
• Only one UP MEP is allowed in an association
• Multiple DOWN MEPs are allowed in an association
You can configure a total of 32 MIPs on a single switch.
Use the show cfm command to verify your configuration.
Example
The following command configures port 1:20 as a MIP on the 350 association in the spain domain:
configure cfm domain spain association 350 ports 1:20 add intermediate-point
The following command configures port 5:10 to be the UP MEP on the test association in the brazil
domain, with a mepid of 500:
configure cfm domain brazil association test ports 5:10 add end-point up 500
History
This command was first available in ExtremeXOS 11.4.
This command was updated in ExtremeXOS 15.2 to include the optional group parameter.
Platform Availability
This command is available on all platforms.
configure cfm domain association delete remote-mep
configure cfm domain domain_name association association_name delete remote-mep
mepid
Advanced Features
166
Advanced Feature Commands
Description
Allows you to delete a remote MEP for a specific MEP ID and MAC address.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
mepid
Enter the MEP ID of the remote MEP that is to be deleted.
Default
N/A.
Usage Guidelines
Use this command to delete a remote MEP of an MA for a specific MEP ID.
Use the show cfm detail command to verify your configuration.
History
This command was first available in ExtremeXOS 12.1.
Platform Availability
This command is available on all platforms.
configure cfm domain association delete
configure cfm domain domain_name association association_name [ports port_list
delete [[end-point [up|down]] | [intermediate-point] ] ]
Description
Deletes a maintenance end point (MEP) or maintenance intermediate point (MIP) from that MA.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name
port_list
Specifies the port number(s).
up
Specifies that an UP MEP is to be deleted.
down
Specifies that a DOWN MEP is to be deleted.
Advanced Features
167
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Use this command to delete an MEP or MIP.
If the VPLS option is chosen then the CFM deletes all the VPLS-based MIPs.
Use the show cfm command to verify your configuration.
Example
The following command deletes port 5:12 as an MIP on the test association in the brazil domain:
configure cfm domain brazil association test ports 5:12 delete intermediatepoint
The following command deletes an UP MEP on port 5:10 on the test association in the brazil domain:
configure cfm domain brazil association test ports 5:10 delete end-point up
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm domain association destination-mac-type
configure cfm domain domain-name association association_name destination-mactype [unicast | multicast]
Description
Allows you to choose the destination MAC type for sending CFM PDUs for an MA.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
Advanced Features
168
Advanced Feature Commands
unicast
CFM PDUs are sent to the unicast MAC address configured in static remote MEP
creation.
multicast
CFM PDUs are sent to the standard multicast destination address.
Default
Multicast.
Usage Guidelines
Use this command to change the MAC type on a previously configured MA. If multicast is selected, CFM
PDUs are sent to the standard multicast destination. If unicast is selected, CFM PDUs are sent to the
unicast MAC address configured in static remote MEP creation.
Use the show cfm command to verify your configuration.
E4G400, E4G200, and Summit X460 do not support unicast CCM (Continuity Check Message)
generation. When the user configures the destination MAC type as unicast, the following message
appears:
Error: IEEE 802.1ag PDUs can be sent only to standard multicast address
on this platform
History
This command was first available in ExtremeXOS 12.1.
Platform Availability
This command is available on all platforms.
configure cfm domain association end-point add group
configure cfm domain domain-name association association-name ports port-list
end-point [up | down] add group group_name
Description
This command allows you to create a group for an existing local end-point.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number you want to configure as either an UP or DOWN MEP.
Advanced Features
169
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Use this command to add a group to the association.
Example
configure cfm domain "MD1" association "MD1v1" ports 17 end-point down add
group "eapsCfmGrp"
History
This command was first available in ExtremeXOS 15.2.
Platform Availability
This command is available on all platforms.
configure cfm domain association end-point delete group
configure cfm domain domain_name association association_name ports port_list
end-point [up|down] delete group [group_name | all ]
Description
This command allows you to delete one or all groups.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number you want to configure as either an UP or DOWN MEP.
delete
Delete configuration from the association
Default
N/A.
Usage Guidelines
Use this command to delete one or all groups from the association.
Advanced Features
170
Advanced Feature Commands
Example
configure cfm domain "MD1" association "MD1v1" ports 17 end-point down delete
group "eapsCfmGrp"
History
This command was first available in ExtremeXOS 15.2.
Platform Availability
This command is available on all platforms.
configure cfm domain association end-point transmit-interval
configure cfm domain domain_name association association_name {ports port_list
end-point [up | down]} transmit-interval [3|10|100|1000|10000|60000|600000]
Description
Allows you to change time interval for an MEP to send out a CCM. We recommend configuring this
value as at least 1 second.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number of the MEP on which you are changing the time
interval it sends out a CCM.
up
Enter this variable if you are changing the time interval for sending a CCM on
an UP MEP.
down
Enter this variable if you are changing the time interval for sending a CCM on
a DOWN MEP.
Default
1000 ms.
Advanced Features
171
Advanced Feature Commands
Usage Guidelines
Use this command to change the time interval between sending out CCMs on a previously configured
UP or DOWN MEP. If you attempt to change the interval on a port that is either not an MEP or having
wrong MEP type, the system returns an error message.
Note
We recommend that you use a transmit interval of at least 1 second (1000 ms).
The receiving system also uses this value multiplied by 3.5 to determine when the MEP is no longer
alive.
Use the show cfm command to verify your configuration and the show cfm detail command to
display the configured lifetime.
Note
The transmit interval value “3” is 3.3 msec. The values 3 and 10 are supported on platforms
x460, E4G400 and E4G200 only for down MEPS. Also, the values 60000 and 600000 are
supported in hardware.
Example
The following command changes the interval the UP MEP (previously configured on port 2:4) uses to
send CCM messages on the 350 association in the finance domain to 10 seconds:
configure cfm domain finance association 350 ports 2:4 end-point up transmitinterval 10000
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm domain association ports end-point ccm
configure cfm domain domain_name association association_name ports port_list
end-point [up | down ] ccm [disable | enable]
Description
This command is used to enable or disable sending CCMs on a given MEP.
Advanced Features
172
Advanced Feature Commands
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number you want to configure as either an UP or DOWN MEP.
Default
Enabled.
Usage Guidelines
Each MA needs at least two MEPs that can reach each other to exchange CCM messages.
Note
Ensure that you assigned the port number correctly to the UP MEP and to the DOWN MEP, or
the CCM messages go in the wrong direction.
These ports must already be in the MA (VLAN or VMAN) prior to assigning a MEP function to them. If
you try to assign a port not in the MA as an end-point, the system returns the following message:
The following port(s) <portlist> are not part of the associations VLAN.
Use the show cfm command to verify your configuration.
Example
configure cfm domain "MD1" association "MD1v1" ports 17 end-point down delete group "eapsCfmGrp"
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm domain association ports end-point mepid
configure cfm domain domain-name association association_name ports port_list
end-point [up | down] mepid mepid
Description
Allows you to change the MEP ID for a previously configured MEP. Each MEP within a single MA must
have a unique MEP ID.
Advanced Features
173
Advanced Feature Commands
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number you want to change the MEP ID.
up
Enter this variable if you are changing the MEP ID on an UP MEP.
down
Enter this variable if you are changing the MEP ID on a DOWN MEP.
mepid
Enter the new value for this MEP. The range is 1 to 8191.
NOTE: On each MA, each MEPID must be unique.
Default
N/A.
Usage Guidelines
Use this command to change the MEPID on a previously configured UP or DOWN MEP. If you attempt
to change the MEPID on a port that is either not an MEP or having wrong MEP type, the system returns
an error message.
Use the show cfm command to verify your configuration.
Example
The following command changes the MEP ID to 75 on the previously configured port 2:4 UP MEP on the
350 association in the finance domain:
configure cfm domain finance association 350 ports 2:4 end-point up mepid 75
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm domain association ports end-point sender-idipaddress
configure cfm domain domain_name association association_name ports port_list
end-point [up | down ] sender-id-ipaddress [disable | enable ip-address]
Advanced Features
174
Advanced Feature Commands
Description
This command is used to disable or enable configuring the sender-id-ipaddress on a given MEP.
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the port number.
ip-address
Specifies the IP address that is sent in the sender-id TLV of the CFM PDUs.
Default
Disable.
Usage Guidelines
Each MA needs at least two MEPs that can reach each other to exchange CCM messages.
Note
Ensure that you assigned the port number correctly to the UP MEP and to the DOWN MEP, or
the CCM messages go in the wrong direction.
You must create the MEP for which the configuration is being made before changing the configuration.
Otherwise, the following error message is displayed:
The following port(s) <portlist> are not part of the associations VLAN.
Use the show cfm command to verify your configuration.
Note
E4G400, E4G200, and Summit X460 do not support this option. When the user configures a
sender-id-ipaddress on an end-point, the following message appears:
Error: Sender ID IP Address configuration is not supported on this
platform.
History
This command was first available in ExtremeXOS 12.1.
Platform Availability
This command is available on all platforms except E4G400, E4G200, and Summit X460.
Advanced Features
175
Advanced Feature Commands
configure cfm domain association ports end-point
configure cfm domain domain_name association association_name ports port_list
end-point [up | down] [enable | disable]
Description
Enables or disables an MEP.
Syntax Description
domain_name
Specifies the domain name.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Specifies the ports to configure.
up
Specifies that the end point is up.
down
Specifies that the end point is down.
Default
MEP is enabled by default.
Usage Guidelines
Use this command to enable or disable an MEP.
Use the show cfm command to verify your configuration.
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm domain association remote-mep mac-address
configure cfm domain domain-name association association_name remote-mep mepid
mac-address mac_address
Description
Allows you to modify the MAC address of an existing MEP.
Advanced Features
176
Advanced Feature Commands
Syntax Description
domain_name
Enter the domain associated with the MA you are configuring.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
mepid
Specifies the MEP ID of the remote MEP being modified. The range is 1 to 8191.
mac_address
Specifies the MAC address for the remote MEP being modified.
Default
N/A.
Usage Guidelines
Use this command to modify a remote MEP with given MEP ID and MAC address in an existing
association. Use the show cfm detail command to verify your configuration.
History
This command was first available in ExtremeXOS 12.1.
Platform Availability
This command is available on all platforms.
configure cfm domain delete association
configure cfm domain domain_name delete association association_name
Description
Deletes a maintenance association (MA), including all its configured values, from the switch.
Syntax Description
domain_name
Enter the domain associated with the MA you are deleting.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
Default
N/A.
Usage Guidelines
When you delete an association, or MA, you also remove all its configured values from the switch.
These values include all configured MEPs, MIPs, and static remote MEPs.
Advanced Features
177
Advanced Feature Commands
Example
The following command deletes the MA test, in the domain of brazil, from the switch, along with all its
configured MIPs, MEPs, and static remote MEPs:
configure cfm domain brazil delete association test
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm domain md-level
configure cfm domain domain_name md-level level
Description
Changes a previously configured MD level for the specified domain.
Syntax Description
domain_name
Enter the name of the domain for which you want to change the MD level.
level
Specifies the new MD level you are assigning to this domain. Enter a value
between 0 and 7.
Default
N/A.
Usage Guidelines
You can have up to 8 domains on a switch, and each one must have a unique MD level. Thus, a given
MD level exists only once one a switch.
The IEEE standard 801.2ag specifies different levels for different network users, as follows:
• 5 to 7 for end users
• 3 and 4 for Internet service providers (ISPs)
• 0 to 2 for operators (entities carrying the information for the ISPs)
Advanced Features
178
Advanced Feature Commands
Example
The following command changes the MD level of a previously created domain extreme to 2:
configure cfm domain extreme md-level 2
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
configure cfm group add rmep
configure cfm group group_name add rmep mepid
Description
This command allows you to create and associate an RMEP to a group.
Syntax Description
mepid
Specifies the MEP ID of the remote MEP being created. The range is 1 to 8191.
Default
N/A.
Usage Guidelines
Use this command to create and associate an RMEP to a group.
Example
configure cfm group “eapsCfmGroup” add rmep 2
History
This command was first available in ExtremeXOS 15.2.
Advanced Features
179
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
configure cfm group delete rmep
configure cfm group group_name delete rmep [mepid | all]
Description
This command allows you to delete one or all RMEPs from a group.
Syntax Description
mepid
Specifies the MEP ID of the remote MEP being created. The range is 1 to 8191.
Default
N/A.
Usage Guidelines
Use this command to delete one or all RMEPs from a group.
Example
configure cfm group “eapsCfmGroup” delete rmep 2
History
This command was first available in ExtremeXOS 15.2.
Platform Availability
This command is available on all platforms.
configure cfm segment add domain association
configure cfm segment segment_name add domain domain_name association
association_name
Description
Adds a CFM domain and association to a CFM segment.
Advanced Features
180
Advanced Feature Commands
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
domain_name
Specifies the IEEE 802.1ag maintenance domain.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
Default
N/A.
Usage Guidelines
Use this command to add a CFM domain and an association to a CFM segment. It is used to enable
DMM/DMR in the association that is configured in the CFM domain.
Example
The following command adds the domain cfm3 and the association as3 to the segment s2.
configure cfm segment s2 add domain cfm3 association as3
To delete the domain and/or association, use the command, configure cfm segment delete
domain association .
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment delete domain association
configure cfm segment segment_name delete domain association
Description
Deletes a CFM domain from a CFM segment.
Syntax Description
segment_name
Advanced Features
An alpha numeric string identifying the segment name.
181
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Use this command to delete a CFM domain from a CFM segment.
Example
The following command deletes the domain and association from the segment s2.
configure cfm segment s2 delete domain association
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment dot1p
configure cfm segment segment_name dot1p dot1p_priority
Description
Configures the priority for the segment.
Syntax Description
segment-name
An alpha numeric string identifying the segment name.
dot1p_priority
Priority value that is set in the DMM/DMR. The range is 0 to 7.
Default
The default is “6.”
Usage Guidelines
Use this command to configure the dot1p priority that a DMM/DMR frame can get.
Advanced Features
182
Advanced Feature Commands
Example
The following command configures a dot1p priority of 3 for segment s2.
configure cfm segment s2 dot1p 3
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-delay dot1p
configure cfm segment segment_name frame-delay dot1p dot1p_priority
Description
This command configures the class of service for a particular cfm segment. This value is used to fill the
dot1p priority bit in the Ethernet header during transmission.
If the optional keyword frame-delay is not specified, the same value of Dot1p will be used for both
DMM and LMM. The optional keyword allows configuring different values for DMM and LMM.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
dot1p_priority
Priority value that is set in the DMM/DMR. The range is 0 to 7.
Default
N/A.
Usage Guidelines
Use this command to configure the class of service for a particular cfm segment.
Example
configure cfm segment frame-delay dot1p 4
Advanced Features
183
Advanced Feature Commands
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-delay window
configure cfm segment segment_name frame-delay window window_size
Description
This command is used to configure the window size for calculating the alarm/clear threshold values for
DMM and Severely Errored Second (SES) threshold for LMM. This window size denotes the total
number of recent frames for which the threshold values will be measured.
If the optional keyword frame-delay or frame-loss is not specified, the same value of window size will
be used for both DMM and LMM. The optional keyword allows configuring values for DMM and LMM.
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
frame-delay
Y.1731 Ethernet frame delay measurement.
window_size
Window size for delay measurement; number of frames 1-1800 to be used.
Default
60.
Usage Guidelines
Use this command to configure the window size for calculating the alarm/clear threshold values for
DMM and Severely Errored Second (SES) threshold for LMM.
Example
configure cfm segment cs2
frame-delay window 1000
History
This command was first available in ExtremeXOS 15.1.
Advanced Features
184
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
configure cfm segment frame-delay/frame-loss transmit interval
configure cfm segment segment_name {frame-delay | frame-loss} transmit-interval
interval
Description
Configures the delay between two consecutive DMM/LMM frames.
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
frame-delay
Y.1731 Ethernet frame delay measurement.
frame-loss
Y.1731 Ethernet frame loss measurement.
interval
Trasmit interval in seconds, with a range of 1 to 90.
Default
N/A.
Usage Guidelines
Configures the delay between two consecutive DMM/LMM frames. The configured delay would be for
both continuous and on-demand transmission. This command is optional, and if not configured, the
default interval would be 10 seconds.
If the optional keyword frame-delay or frame-loss is not specified, the same value of transmit-interval
will be used for both DMM and LMM. The optional keyword allows configuring different values for DMM
and LMM.
Example
configure cfm segment cs2
configure cfm segment cs2
frame-delay transmit-interval 10
frame-loss transmit-interval 10
History
This command was first available in ExtremeXOS 15.1.
Advanced Features
185
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
configure cfm segment frame-loss consecutive
configure cfm segment segment_name frame-loss consecutive frames
Description
This command is used to configure the number of consecutive measurements to be used to determine
the availability status of a CFM segment.
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
frame-loss
Y.1731 Ethernet frame loss measurement.
Default
10.
Usage Guidelines
This configuration is optional.
Example
configure cfm segment cs2
frame-loss
consecutive 10
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-loss dot1p
configure cfm segment segment_name frame-loss dot1p dot1p_priority
Advanced Features
186
Advanced Feature Commands
Description
This command configures the class of service for a particular cfm segment. This value is used to fill the
dot1p priority bit in the Ethernet header during transmission.
If the optional keyword frame-loss is not specified, the same value of Dot1p will be used for both DMM
and LMM. The optional keyword allows configuring different values for DMM and LMM.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
dot1p_priority
Priority value that is set in the DMM/DMR. The range is 0 to 7.
Default
N/A.
Usage Guidelines
Use this command to configure the class of service for a particular cfm segment.
Example
configure cfm segment frame-loss dot1p 4
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-loss mep
configure cfm segment segment_name frame-loss [add|delete] mep mep_id
Description
This command is used to add/delete the local MEP for a given CFM segment.
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
frame-loss
Y.1731 Ethernet frame loss measurement.
Advanced Features
187
Advanced Feature Commands
Default
N/A.
Usage Guidelines
The MEP with the given MEP ID should already be created in the system. The domain and association
for the segment should be configured before executing this command. If the domain and association
are not configured, the command throws an error.
Configuring of local MEP is mandatory to start the Frame Loss measurements.
Example
configure cfm segment cs2
configure cfm segment cs2
add mep 3
delete mep 3
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-loss ses-threshold
configure cfm segment segment_name frame-loss ses-threshold percent
Description
This command is used to configure the percentage of frames lost in a measurement period for it to be
marked as SES (Severely Errored Second).
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
ses
Severely errored second.
frame-loss
Y.1731 Ethernet frame loss measurement.
Default
30%.
Advanced Features
188
Advanced Feature Commands
Usage Guidelines
This configuration is optional.
Example
configure cfm segment cs2
frame-loss
ses-threshold .02
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
configure cfm segment frame-loss window
configure cfm segment segment_name frame-loss window window_size
Description
This command is used to configure the window size for calculating the alarm/clear threshold values for
DMM and Severely Errored Second (SES) threshold for LMM. This window size denotes the total
number of recent frames for which the threshold values will be measured.
If the optional keyword frame-delay or frame-loss is not specified, the same value of window size will
be used for both DMM and LMM. The optional keyword allows configuring values for DMM and LMM.
Syntax Description
segment_name
Alphanumeric string identifying the segment name.
frame-loss
Y.1731 Ethernet frame loss measurement.
window_size
Window size for loss measurement; number of frames 1-1800 to be used.
Default
1200.
Usage Guidelines
Use this command to configure the window size for calculating the alarm/clear threshold values for
DMM and Severely Errored Second (SES) threshold for LMM.
Advanced Features
189
Advanced Feature Commands
Example
configure cfm segment cs2
frame-loss
window 900
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
configure cfm segment threshold
configure cfm segment segment_name [alarm-threshold | clear-threshold] value
Description
Configures the alarm threshold and clear threshold.
Syntax Description
alarm-threshold
Specifies the minimum threshold percentage.
clear-threshold
Specifies the maximum threshold percentage.
value
Specified the threshold percentage in a range of 1-99%.
Default
Alarm threshold is 10% of the total frames received during the current window.
Clear-threshold is 95% of the total frames received during the current window.
Usage Guidelines
Use this command to configure the alarm and clear threshold value for a CFM segment. Upon reaching
the alarm threshold, an error message is generated and displayed once, and the state is maintained
until the threshold reaches the clear threshold value.
This command is optional, and if not configured the default intervals are used.
Advanced Features
190
Advanced Feature Commands
Example
The following commands configure an alarm threshold of 15% and a clear-threshold of 90% for
segment-first.
configure cfm segment segment-first alarm-threshold 15
configure cfm segment segment-first clear-threshold 90
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment timeout
configure cfm segment segment_name timeout msec
Description
Configures the timeout for a segment.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
msec
Specifies the number of milliseconds. The range is 1 to 65535.
Default
50 milliseconds.
Usage Guidelines
Use this command to configure the timeout value for the reception of a DMR frame. If a DMR frame is
not received within this specified time, that frame is considered as an errored frame, and if the number
of errored frames reaches the alarm threshold of the current window size, an alarm is generated.
This command is optional, and if not configured, timeout is set to the default.
Advanced Features
191
Advanced Feature Commands
Example
The following command configures a timeout value of 45 milliseconds for the s4 segment:
configure cfm segment s4 timeout 45
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment transmit-interval
configure cfm segment segment_name { frame-delay | frame loss }transmit-interval
interval
Description
Configures the transmission interval of DMM frames.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
frame-delay
Y.1731 Ethernet Frame Delay Measurement.
frame loss
Y.1731 Ethernet Frame Loss Measurement.
interval
Specifies the transmit interval in seconds. The range is 1 to 90.
Default
10 seconds.
Usage Guidelines
Use this command to configure the delay between two consecutive DMM frames. The configured delay
is for both continuous and on-demand transmission. This command is optional, and if not configured
the default interval is used.
Advanced Features
192
Advanced Feature Commands
Example
The following command configures a transmission interval of 5 seconds for segment s2.
configure cfm segment s2 transmit-interval 5
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure cfm segment window
configure cfm segment segment_name window size
Description
Configures the measurement window size.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
size
Specifies the number of frames to be used for delay measurement. The range
is 1 to 1800.
Default
60 frames.
Usage Guidelines
Use this command to configure the window size to be used for calculating the threshold values. This
window size denotes the total number of recent frames for which the threshold values are to be
measured.
This is an optional command and if not configured, the lower of either the default value or the total
number of frames sent is used.
Note
MEPs with intervals 3 and 10 cannot be created in this domain as the domain name format is
of dns type.
Advanced Features
193
Advanced Feature Commands
Example
The following command configures the measurement window size for the CFM segment segment-first
at 55:
configure cfm segment segment-first window 55
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
configure fip snooping add fcf
configure fip snooping {vlan} vlan_name add fcf mac_addr port port
Description
This command is used to add an FCF to a FIP Snooping VLAN port when in manual fcf-update mode.
If the fcf-update mode is manual, this command adds a new FCF MAC to the list of FCFs. The command
does not allow the same FCF MAC to be added to multiple ports in the same VLAN.
When a new FCF is added, ACLs are added to accept FIP frames from the new FCF.
An FCF can only be configured on a FIP Snooping VLAN port that has port location FCF-to-Enode or
All configured.
If the fcf-update mode is automatic and this command is executed, the add is not allowed and the user
is informed.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping on FIP frames.
vlan_name
Name of a FIP Snooping VLAN where fcf-update is configured to be in
manual mode.
add
Add to the list of FCoE forwarders.
mac_addr
MAC address of the FCoE Forwarder specified in the format of
hh:hh:hh:hh:hh:hh.
port
Port through which the FCF is reachable.
Advanced Features
194
Advanced Feature Commands
Default
N/A.
Usage Guidelines
This command is used to add an FCF to a FIP Snooping VLAN port when in manual fcf-update mode.
The command does not allow the same FCF MAC to be added to multiple ports in the same VLAN.
Example
configure fip snooping v3 add fcf aa:bb:cc:dd:00:00 port 1:2
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
configure fip snooping add vlan
configure fip snooping add {vlan} vlan_name
Description
FIP Snooping must be configured to operate.
When a VLAN is added to FIP Snooping using this command, a record containing all FIP configuration
information is created for that VLAN with default settings for all configuration elements. If the
configuration is saved, the record persists across reboots. The user can see the record when using the
“show fip snooping vlan”command to see FIP Snooping information for a VLAN. If the record does not
exist, no information appears.
Syntax Description
add
Allows use of FIP Snooping on the VLAN.
vlan
Optional VLAN keyword.
Advanced Features
195
Advanced Feature Commands
Default
•
•
•
•
•
•
•
•
•
Feature is disabled on the specified VLAN.
Port locations default to “perimeter”.
FCF-update mode is “automatic”.
No FCFs exist in the configuration.
The FC-MAP prefix is 0e:fc:00.
There are no ACLs.
There are no ENodes.
There are no virtual links.
All counters contain zero.
Usage Guidelines
This command creates the FIP Snooping configuration record for the specified VLAN. All default
settings are in effect.
Example
configure fip snooping add vlan v3
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
•
•
•
•
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
configure fip snooping delete fcf
configure fip snooping {vlan} vlan_name delete fcf mac_addr port port
Description
This command is used to remove an FCF from a FIP Snooping VLAN port when in manual fcf-update
mode.
If the fcf-update mode is manual, this command removes the FCF MAC from the list of FCFs configured
on the FIP Snooping VLAN. When an FCF is removed from the list, the ACLs referencing the FCF
(including virtual links) are removed.
Advanced Features
196
Advanced Feature Commands
If the fcf-update mode is automatic and this command is executed, the remove is not allowed and the
user is informed.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of a FIP Snooping VLAN where the specified FCF MAC address has
been configured.
delete
Delete from the list of FCoE forwarders.
fcf
The list of FCoE forwarders in the VLAN.
mac_addr
MAC address of the FCoE Forwarder specified in the format of
hh:hh:hh:hh:hh:hh.
port
Port through which the FCF is reachable.
Default
N/A.
Usage Guidelines
This command is used to remove an FCF from a FIP Snooping VLAN port when in manual fcf-update
mode. The fcf-update mode must be “manual”.
Example
configure fip snooping v3 delete fcf aa:bb:cc:dd:00:00 port 1:2
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
configure fip snooping delete vlan
configure fip snooping delete [{vlan} vlan_name | all]
Advanced Features
197
Advanced Feature Commands
Description
This command deletes the FIP Snooping configuration record for the specified VLAN. If “all” is
specified, all FIP Snooping configuration information is removed from the system after the user
confirms this request:
Warning: This command will remove all FIP Snooping configuration for all VLANs.
Do you want to continue? (y/N)
If FIP Snooping is enabled on an affected VLAN it is first disabled causing the removal of related ACL
and FDB information from the system. Also removed are any virtual links, Enodes, and FCFs.
Note
A VLAN cannot be deleted when FIP Snooping is configured. For example: * BDX8.60 #
delete vlan v1 Error: Failed to delete VLAN v1; FIP Snooping is configured on this VLAN.
Configuration failed on backup MM, command execution aborted! * BDX8.61 # configure fip
snooping delete vlan v1 * BDX8.62 # delete vlan v1 * BDX8.63 #
Syntax Description
delete
Remove use of FIP Snooping from the VLAN.
vlan
Optional VLAN keyword
Default
N/A.
Usage Guidelines
Use this command to delete the FIP Snooping configuration record for the specified VLAN.
Example
configure fip snooping delete vlan v3
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
•
•
•
•
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
Advanced Features
198
Advanced Feature Commands
configure fip snooping fcf-update
configure fip snooping {vlan} vlan_name fcf-update [auto | manual]
Description
This command configures the update mode of the list of FCFs per FIP Snooped VLAN. The default
mode is auto.
The list of FCFs to which ENodes establish FCoE virtual links is updated either administratively or
dynamically via snooped FIP frames. This command selects the method of updating the list of FCFs per
VLAN. When the updating method changes, the following events occur.
• FDB entries of FCFs' MACs are removed.
• ACLs checking the FCFs' MACs are removed.
In automatic mode, the list of FCFs is automatically constructed through observation of FCF discovery
advertisement packets. An attempt to configure an FCF while in automatic mode is rejected.
In manual mode the list of FCFs is configured by the user. Use the following commands to configure the
list of FCFs:
• configure fip snooping add fcf
•
•
configure fip snooping delete fcf
configure fip snooping fcf-update
When the fcf-update mode is changed from manual to automatic, all configured FCFs are removed.
Syntax Description
vlan_name
Name of a FIP Snooping VLAN where the fcf-update mode is to be
configured.
auto
Learn the list of FCoE forwarders from snooped FIP frames.
manual
FCoE forwarders are configured manually using the “configure fip snooping
vlan add fcf” command.
Default
Auto.
Usage Guidelines
This command configures the update mode of the list of FCFs per FIP Snooped VLAN. In automatic
mode, the list of FCFs is automatically constructed through observation of FCF discovery
advertisement packets. An attempt to configure an FCF while in automatic mode is rejected. In manual
mode the list of FCFs is configured by the user. When the fcf-update mode is changed, all FCFs are
removed.
Advanced Features
199
Advanced Feature Commands
Example
configure fip snooping vlan v3 fcf-update manual
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
•
•
•
•
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
configure fip snooping fcmap
configure fip snooping {vlan} vlan_name fcmap mac_prefix
Description
An FCF and an Enode negotiate whether the FCF or the Enode will provide a VN_Port MAC address for
each virtual link. The Enode (also called a server) can provide a Server Provided MAC Address (SPMA),
or the FCF can provide a Fabric Provided MAC Address (FPMA). An individual FPMA is assigned by the
FibreChannel fabric to the VN_Port during fabric login. An FPMA address begins with the 24-bit FCMAP prefix. The default value of the FC-MAP prefix is 0E:FC:00 but can be changed. The low order
three octets of the FPMA will contain the FibreChannel fabric-assigned FibreChannel ID (also called a
VN_Port_ID) for the virtual link.
This command configures the expected MAC address prefix (used when in FPMA mode) of all FPMA
used on the FIP Snooping VLAN. The FPMA for a VN_Port is assigned by the FCF using its configured
FC-MAP prefix to construct the VN_Port FPMA. Therefore the FC-MAP prefix configured on the switch
must be the same as that configured on the FCF for the VLAN. The default value of mac_prefix is
0E:FC:00:00:00:00.
The mac_prefix value must be between 0e:fc:00 and 0e:fc:ff and the lower three MAC octets must be
specified as zero or the following message will be displayed:
Error: Invalid FC-MAP, use 0e:fc:xx:00:00:00 where xx is a two-digit
hexadecimal value.
The user should not use the same FIP Snooping VLAN for connection to more than one FibreChannel
fabric or storage area network. Duplicate FPMA could be assigned by the different fabrics causing
connectivity issues.
Advanced Features
200
Advanced Feature Commands
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of the VLAN for which the FC-MAP prefix is to be changed.
fcmap
24 prefix for MAC address assigned to VN Port in an FPMA mode.
mac_prefix
24bit prefix of MAC followed by 24 zeros formatted as 0e:fc:xx:00:00:00
where xx is a two-digit hexadecimal number.
Default
The default value of mac_prefix is 0E:FC:00:00:00:00.
Usage Guidelines
This command configures the expected MAC address prefix (used when in FPMA mode) of all FPMA
used on the FIP Snooping VLAN.
Example
configure fip snooping vlan v3 fcmap 0e:fc:01:00:00:00
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
configure fip snooping port location
configure fip snooping {vlan} vlan_name ports port_list {location [perimeter |
enode-to-fcf | fcf-to-enode | all]}
The default ACLs on the port are changed to be consistent with the new location.
Advanced Features
201
Advanced Feature Commands
Description
This command configures the port location for a member of a VLAN that is configured to perform FIP
Snooping. The default port location type is perimeter. If no FIP Snooping configuration record was
previously created for the VLAN, this command causes its creation with defaults (except for the
particular port's location as specified) set.
The acceptable FIP frames differ per port location. The command specifies the port location and guides
the switch to install different ACLs. The default port location, i.e. port type, is perimeter, where the port
is expected to be connected toENodes. The change of the port type triggers the following events.
If FIP Snooping is enabled:
• All FDB entries previously stored for the VLAN on the specified port are removed, except for those
related to manually configured FCFs.
• All virtual links are removed.
• All knowledge of Enodes (if any) learned on this port is removed.
• All knowledge of discovered FCFs (if any) learned on this port is removed.
Syntax Description
vlan-name
Name of the VLAN whose port(s) will have the location changed.
port_list
A port or a list of ports.
perimeter
Port is directly connected to Enodes. Per virtual link ACLs are installed
providing the most security.
enode-to-fcf
Port sees packets from FCoE nodes to FCoE forwarders only.
fcf-to-enode
Port sees packets from FCoE forwarders to FCoE nodes only.
all
Port sees packets both from FCoE forwarders and FCoE nodes.
Default
Perimeter.
Usage Guidelines
This command configures the port location for a member of a VLAN that is to perform FIP Snooping.
Example
configure fip snooping vlan "v3" port 1:1 location fcf-to-enode
History
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
Advanced Features
202
Advanced Feature Commands
•
•
Summit X670
Summit X770
configure lldp ports dcbx add application
configure lldp ports [all | port_list] dcbx add application [name
application_name | ethertype ethertype_value | L4-port port_number | tcp-port
port_number | udp-port port_number] priority priority_value
Description
Configures an application priority to be advertised to DCBX end stations.
Syntax Description
all
Specifies all ports on the switch.
port_list
Specifies one or more ports or slots and ports.
application_name
Specifies an application. Supported values are:
•
•
•
fcoe—Fiber Channel Over Ethernet (FCoE).
fip—FCoE Initiation Protocol (FIP).
iscsi—Internet Small Computer System Interface (iSCSI).
ethertype_value
Specifies an ethertype value in the range of 1536 to 65535.
L4-port port_number
Specifies a Layer 4 port number in the range of 0 to 65535. Supported Layer4
protocols include TCP, SCTP, UDP, and DCCP.
tcp-port port_number
Specifies a TCP port number in the range of 0 to 65535.
udp-port port_number
Specifies a UDP port number in the range of 0 to 65535.
priority_value
Specifies a priority in the range of 0 to 7.
Default
N/A.
Usage Guidelines
This command configures the switch to advertise the priority that an end station should use for the
specified application or port number. The priority number is mapped to an 802.1p value, which
determines how the switch manages traffic from that application or port.
The switch supports a maximum of 8 DCBX applications per port. If an application configuration
already exists on the specified port or ports, the priority is updated to the new value. If the maximum
number of applications for a port is exceeded, the switch logs an error message.
Advanced Features
203
Advanced Feature Commands
Example
The following command configures the switch to advertise priority 4 for the iSCSI application on ports1
to 24:
configure lldp ports 1-24 dcbx add application name iscsi priority 4
The following command configures the switch to advertise priority 3 for ethertype value 34525 on
port1:
configure lldp ports 1 dcbx add application ethertype 34525 priority 3
The following command configures the switch to advertise priority 6 for Layer 4 port 992 on port1:
configure lldp ports 1 dcbx add application L4-port 992 priority 6
History
This command was first available in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure lldp ports dcbx delete application
configure lldp ports [all | port_list] dcbx delete application [all-applications
| name application_name | ethertype ethertype_value | L4-port port_number | tcpport port_number | udp-port port_number]
Description
Removes the priority configuration for one or all applications from the specified ports.
Syntax Description
all
Specifies all ports on the switch.
port_list
Specifies one or more ports or slots and ports.
application_name
Specifies an application. Supported values are:
•
•
•
ethertype_value
Advanced Features
fcoe—Fiber Channel Over Ethernet (FCoE).
fip—FCoE Initiation Protocol (FIP).
iscsi—Internet Small Computer System Interface (iSCSI).
Specifies an ethertype value in the range of 1536 to 65535.
204
Advanced Feature Commands
L4-port port_number
Specifies a Layer 4 port number in the range of 0 to 65535. Supported Layer4
protocols include TCP, SCTP, UDP, and DCCP.
tcp-port port_number
Specifies a TCP port number in the range of 0 to 65535.
udp-port port_number
Specifies a UDP port number in the range of 0 to 65535.
Default
N/A.
Usage Guidelines
This command configures the switch to advertise the priority that an end station should use for the
specified application or port number. The priority number is mapped to an 802.1p value, which
determines how the switch manages traffic from that application or port.
If an application configuration already exists on the specified port or ports, the priority is updated to
the new value.
Example
The following command removes the priority configuration for Layer 4 port 30 on port 23:
configure lldp ports 23 dcbx delete application L4-port 30
History
This command was first available in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure lldp ports vendor-specific dcbx
configure lldp ports [all | port_list] [advertise | no-advertise] vendor-specific
dcbx {ieee|baseline}
Description
Configures the LLDP port to advertise or not to advertise Data Center Bridging Exchange (DCBX)
information to its neighbors.
Advanced Features
205
Advanced Feature Commands
Syntax Description
all
Specifies all ports on the switch.
port_list
Specifies one or more ports or slots and ports.
advertise
Specifies to send the information to neighbors.
no-advertise
Specifies not to send the information to neighbors.
ieee
Specifies the DCBX protocol defined in IEEE 802.1Qaz.
baseline
Specifies the DCBX protocol known as Baseline Version 1.01, which was
defined before IEEE 802.1Qaz.
Default
No advertisement for both DCBX protocols.
Usage Guidelines
If you do not specify a protocol with this command, the advertise option enables advertisement for the
IEEE 802.1Qaz protocol, and the no-advertise option disables advertisement for both protocols.
Example
The following command advertises DCBX information according to IEEE 802.1Qaz for port 1:5:
configure lldp ports 1:5 advertise vendor specific dcbx
The following command advertises DCBX information according to Baseline Version 1.01 for port 2:1:
configure lldp ports 2:1 advertise vendor specific dcbx baseline
The following command disables advertisement of DCBX information on all ports:
configure lldp ports all no-advertise vendor specific dcbx
History
This command was first available in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure mrp ports timers
configure mrp ports [port_list | all] timers [ {join join_msec} {leave
leave_msec} {leave-all leave_all_msec} {periodic [periodic_msec | off]}{refresh
[ auto-refresh | refresh_msec | off ]} ]
Advanced Features
206
Advanced Feature Commands
Description
This command sets the join, leave, leave all, periodic, and extended-refresh timer values for a list of
ports. The unit value is in milliseconds. The join timer, leave all timer, and periodic timer are started for
each MRP application per port. The leave timer is started for each state machine that is in LV (leave)
state. The default values for join, leave, leave-all, are 200, 600, and 10000, respectively. The default
values for join, leave, leave-all, periodic and extended-refresh timers are 200, 600, 10000, 1000, and 0
milliseconds, respectively.
Syntax Description
mrp
Multiple Registration Protocol.
ports
Ports.
port_list
Port list separated by a comma or -" type="portlist_t".
all
All ports.
timers
Multiple Registration Protocol timers.
join
The time interval to delay sending MRP advertisements.
join_msec
Join timer value in milliseconds (range is 0 ms to 500 ms, default is 200 ms).
leave
The time interval to wait in the leaving state before transitioning to the empty
state.
leave_msec
Leave timer value in milliseconds (range is 600 ms to 3000 ms, default is 600
ms).
leave-all
The time interval used to control the frequency of "leave all" messages.
leave_all_msec
Leave All timer value in milliseconds (range is 5000 ms to 20000 ms, default
is 10000 ms).
periodic
The time interval between two periodic events.
periodic_msec
Periodic timer value in milliseconds (range is 1000ms to 300000 ms, default
is 1000 ms); type="uint32_t".
off
Turn off timer.
refresh
Timer value to use in place of regular timer, only in cases when leave-all is
received or sent.
auto-refresh
Automatically calculate timer values based on number of talkers and listeners.
refresh_msec
Refresh timer value in milliseconds (range is 600ms to 300000ms, default is
0ms (off)).
Default
The default values for join, leave, leave-all, are 200, 600, and 10000, respectively. The default values for
join, leave, leave-all, periodic and extended-refresh timers are 200, 600, 10000, 1000, and 0
milliseconds, respectively.
Advanced Features
207
Advanced Feature Commands
Usage Guidelines
This command is used to set the join, leave, and leave-all timer values for a list of ports. The unit value is
in milliseconds. The join timer and leave all timer are started for each MRP application per port. The
leave timer is started for each state machine that is in LV (leave) state. The default values for these
timers are 200, 600, and 10000, respectively.
configure mrp ports 4 timers join 300
configure mrp ports all timers leave-all 15000
configure mrp ports all timers join 300 leave-all 15000
History
This command was first available in ExtremeXOS 15.3. The extended-refresh and period timer options
were added in 15.3.2.
Platform Availability
This command is available on all platforms.
configure msrp latency-max-frame-size
configure msrp [ latency-max-frame-size frame_size | [ igonore-latency-changes |
talker-vlan-pruning ] [ on | off ] ]
Description
This command configures the system-wide MSRP variables.
Syntax Description
msrp
Multiple Stream Registration Protocol.
latency-max-frame-size
Maximum size of interfering frame (used in latency calculations).
frame_size
The maximum frame size in bytes (range 64 to 2000, default is 1522).
ignore-latency-changes
Ignore accumulated latency changes when evaluating first value change.
talker-vlan-pruning
Talker propagation is filtered on ports where VLAN does not exist.
on
Turn on.
off
Turn off.
Default
1522.
Advanced Features
208
Advanced Feature Commands
Usage Guidelines
Use this command to configure the system-wide MSRP variables.
Example
configure msrp latency-max-frame-size 100
History
This command was first available in ExtremeXOS 15.3. The ignore-latency-changes, talker-vlan-pruning,
and on | off options were added in 15.3.2.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure msrp ports sr-pvid
configure msrp ports [port_list | all] sr-pvid vlan_tag
Description
Specifies the default VLAN ID on the port for MSRP data stream. The sr-pvid serves as a
recommendation to connected AVB devices; AVB devices may still use other VLAN IDs if they are
configured to do so.
Syntax Description
msrp
Multiple Stream Registration Protocol
port_list
List of ports in the switch.
all
All the ports in the switch.
sr-pvid
Default VLAN Identifier for stream-related traffic.
vlan_tag
VLAN ID ranging from 1 to 4094 (default is 2).
Default
2.
Usage Guidelines
Use this command to specify the default VLAN ID on the port for MSRP data streams. The sr-pvid
serves as a recommendation to connected AVB devices; AVB devices may still use other VLAN IDs if
they are configured to do so.
Advanced Features
209
Advanced Feature Commands
Example
configure msrp ports 1,2,3 sr-pvid 2
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure msrp ports traffic-class delta-bandwidth
configure msrp ports [port_list | all] traffic-class [A | B] delta-bandwidth
percentage
Description
Configures delta-bandwidth value per traffic class per MSRP port.
Syntax Description
msrp
Multiple Stream Registration Protocol.
port_list
List of ports in the switch.
traffic-class
Traffic class.
A
Traffic class A.
B
Traffic class B.
delta-bandwidth
Delta-bandwidth percentage (range 0 to 100, default 75 for class A, 0 for
class B).
Default
Class A: 75, Class B: 0.
Usage Guidelines
The delta bandwidth configuration limits the amount of bandwidth that can be used by the given
stream reservation class. Each class is allowed to use a maximum of its delta bandwidth plus the delta
bandwidth configured for each of the higher classes. For example, if the delta bandwidth for classes A
and B are configured to 10 and 10 respectively, class A streams can use up to 10 percent of the link
bandwidth, and class B streams can us up to 20 percent of the link bandwidth. The sum of the class A
and B delta bandwidth values must be less than 100 percent.
Advanced Features
210
Advanced Feature Commands
Example
configure msrp ports all traffic-class A delta-bandwidth 50
configure msrp ports 1-5 traffic-class B delta-bandwidth 0
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure msrp timers first-value-change-recovery
configure msrp timers first-value-change-recovery [first_value_change_msec | off]
Description
This command configures MSRP first value change recovery timer, or disables the timer. If configured,
the system waits until the configured timer value before allowing recovery of streams from first value
change failure. If disabled, the system does not recover from first value change failure.
Syntax Description
msrp
Multiple Stream Registration Protocol.
timers
Multiple Stream Registration Protocol timers.
first-value-changerecovery
The time interval to wait to allow recovery of stream from first value
change failure.
first_value_change_msec
First Value Change Recovery time in milliseconds (range is 10000 ms to
5400000 ms, default is 30000 ms); type="uint32_t"; range="[10000,
5400000]".
off
Turn off first value change recovery timer, and do not recover from first
value change failure.
Default
30000 ms.
Usage Guidelines
Use this command to allow streams to recover from first value change failure.
Advanced Features
211
Advanced Feature Commands
Example
configure msrp timers first-value-change recovery 20000
configure msrp timers first-value-change recovery off
History
This command was first available in ExtremeXOS 15.3.2.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure mvrp stpd
configure mvrp stpd stpd_name
Description
Configures the STP domain to use for dynamically created VLANs.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
stpd
The STP domain used for MVRP.
stpd_name
The STP domain the VLAN is to be associated. All ports of the domain will be
advertised, when this VLAN gets registered.
Default
s0.
Usage Guidelines
Use this command to configure the STP domain used for MVRP.
Example
The following example configures the default STP domain for MVRP to "stpd2":
configure mvrp stpd stpd2
Advanced Features
212
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
configure mvrp tag ports registration
configure mvrp tag vlan_tag ports [port_list |all] registration [forbidden |
normal ]
Description
This command is used to configure MVRP VLAN registration as forbidden or normal for specific VLANs
on specific ports. If registration for a VLAN is configured forbidden on a specific port, then when MVRP
PDU is received on the port with the particular forbidden VLAN Id, the VLAN is not created and if the
VLAN is already there, the port is not added to the VLAN. For normal MVRP behavior, the registration
needs to be normal. The forbidden / normal setting is only for dynamic addition of ports to VLANs. Any
static addition of ports to the VLANs will override this setting and will mark the status as fixed. The
forbidden setting can be used to control MSRP advertisements, in typical scaling scenarios.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
tag
The 802.1Q VLAN ID.
vlan_tag
VLAN ID ranging from 1 to 4094; type=uint16_t"; range="[1,4094]".
ports
Ports.
port_list
Port list separated by a comma or -"; type="portlist_t";
all
All ports.
registration
Whether port can be added dynamically to the VLAN.
forbidden
Port cannot be added dynamically to the VLAN.
normal
Port can be added dynamically to the VLAN.
Default
Normal.
Usage Guidelines
Use this command to control dynamic addition of ports to VLANs.
Advanced Features
213
Advanced Feature Commands
Example
configure mvrp tag 2 ports 2,3,4 registration forbidden
configure mvrp tag 2 ports all registration normal
History
This command was first available in ExtremeXOS 15.3.
The registration option, and forbidden and normal keywords were added in 15.3.2.
Platform Availability
This command is available on all platforms.
configure mvrp tag ports transmit
configure mvrp tag vlan_tag ports [port_list | all] transmit [on | off ]
Description
Controls whether the given VLAN ID may be advertised in MVRP messages transmitted on the given
set of ports.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
tag
The 802.1Q VLAN ID.
transmit
When enabled, MVRP message are sent on the ports.
on
Transmission of MVRP messages are enabled on the port(s) for the given tag.
off
Transmission of the MVRP messages are disabled on the port(s) for the given
tag.
Default
Transmit on.
Usage Guidelines
Use this command to control whether the given VLAN ID may be advertised in MVRP messages
transmitted on the given set of ports.
Advanced Features
214
Advanced Feature Commands
Example
The following command configures transmit off for VLAN ID 100 on all MVRP ports:
configure mvrp tag 100 ports all transmit off
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
configure mvrp vlan auto-creation
configure mvrp vlan auto-creation [on | off]
Description
Enables or disables the dynamic VLAN creation feature of MVRP.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
auto-creation
When enabled, results in VLANs added dynamically on the switch through
MVRP.
on
Enable auto-creation.
off
Disable auto-creation.
Default
Enabled.
Usage Guidelines
Use this command to enable or disable the dynamic VLAN creation of MVRP. By default, auto-creation
is enabled. If disabled, the switch may participate in the MVRP protocol, and advertised static VLANs,
but will not dynamically create VLANs.
Example
The following command enables MVRP VLAN auto creation:
configure mvrp vlan auto-creation on
Advanced Features
215
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
configure mvrp vlan registration
configure mvrp vlan registration forbidden | normal
Description
This command is a global system setting. If global registration is forbidden, ports cannot be added to
any VLAN dynamically.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
vlan
VLAN.
registration
Whether all ports can be added to new dynamic VLANs. This can be
overridden by static port addition to VLAN.
forbidden
Ports cannot be added dynamically to the VLAN. This can be overridden by
static port addition.
normal
Ports can be added dynamically to the VLAN (default).
Default
Normal.
Usage Guidelines
Use this command to set global registration. If global registration is forbidden, ports cannot be added
to any VLAN dynamically.
Example
The following command allows ports to be added dynamically to the VLAN:
configure mvrp vlan registration normal
History
This command was first available in ExtremeXOS 15.3.
The registration keyword was first available in ExtremeXOS 15.3.2.
Advanced Features
216
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
configure network-clock gptp default-set
configure network-clock gptp default-set [{priority1 priority1_value} {priority2
priority2_value}]
Description
This command configures the switch's default-set parameters, specifically its grandmaster clock
priority values that are used to elect the grandmaster clock in the network.
Syntax Description
priority1_value
The switch's grandmaster clock priority1 value. This is the most significant
parameter used to select the grandmaster clock in the network. Lower values
indicate higher priority, and 255 prevents the switch from becoming the
grandmaster clock.
priority2_value
The switch’s grandmaster clock priority2 value. This is one of the least
significant parameters used to select the grandmaster clock in the network.
Lower values indicate higher priority.
Default
•
•
Priority1_value = 246 (from 802.1AS 8.6.2.1)
Priority2_value = 248 (from 802.1AS 8.6.2.5)
Usage Guidelines
Use this command to configure the switch's default-set parameters, specifically its grandmaster clock
priority values that are used to elect the grandmaster clock in the network. The Best Master Clock
Algorithm uses six parameters from each time-aware system in the network to select the grandmaster
clock in the network. Priority1 is the highest precedence value; it allows users to preemptively configure
which systems they prefer to be the grandmaster clock. Priority2 is a lower precedence value; it allows
users to configure tiebreaker priorities.
The default priority1 values defined by IEEE 802.1AS-2011 clause 8.6.2.1 give preference to network
infrastructure systems such as Extreme switches.
Example
configure network-clock gptp default-set priority1 248
configure network-clock gptp default-set priority2 100
configure network-clock gptp default-set priority1 248 priority2 100
Advanced Features
217
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure network-clock gptp ports announce
configure network-clock gptp ports [port_list | all] announce [initial-interval
log_2_interval | receipt-timeout timeout_count]
Description
Configures gPTP Announce parameters on the specified ports. Announce messages are used to elect
the grandmaster clock and determine the time-synchronous spanning tree.
Syntax Description
port_list
Specifies one or more of the switch's physical ports.
all
Specifies all of the switch's physical ports.
log_2_interval
The interval between Announce messages used by the switch on the port
when the port is initialized or when the switch receives a message interval
request TLV with announceInterval value 126. This value is in log 2 seconds.
The valid range of values is -3 (2-3 = 0.125 seconds) to 17 (217 = 131072
seconds).
timeout_count
On a gPTP slave port, the number of announce intervals to wait without
receiving an Announce message before assuming the master is no longer
sending Announce messages.
Default
•
•
log_2_interval = 0 (1 second; 802.1AS-2011 10.6.2.2)
timeout_count = 3 (802.1AS-2011 10.6.3.2)
Usage Guidelines
Use this command to configure gPTP Announce parameters on the specified ports. Announce
messages are used to elect the grandmaster clock and determine the time-synchronous spanning tree.
Announce selects the grandmaster in the network and establishes the tree from the grandmaster to all
other time-aware systems in the network.
initial-interval corresponds to 802.1AS parameter initialLogAnnounceInterval.
receipt-timeout corresponds to 802.1AS parameter announceReceiptTimeout.
Advanced Features
218
Advanced Feature Commands
Example
configure network-clock gptp ports 1-2 announce initial-interval 127
configure network-clock gptp ports all announce receipt-timeout 5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure network-clock gptp ports peer-delay
configure network-clock gptp ports [port_list | all] peer-delay [{allowed-lostresponses lost_responses_value} {initial-req-interval log_2_interval} {[asymmetr
asymmetry_time [nanoseconds | microseconds | milliseconds | seconds] | neighborthresh [auto | neighbor_thresh_time [nanoseconds | microseconds | milliseconds |
seconds]]}]
Description
Configures gPTP peer delay parameters on the specified ports.
Syntax Description
port_list
Specifies one or more of the switch’s physical ports.
all
Specifies all of the switch’s physical ports.
lost_responses_value
The number of consecutive Peer Delay RequestPdelay_Req messages that
the switch must send on a port without receiving a valid response before it
considers the port not to be exchanging Peer Delay messages with its
neighbor.
log_2_interval
The interval between Peer Delay RequestPdelay_Req messages sent by the
switch on the port when the port is initialized or when the switch receives on
the port a message interval request TLV with linkDelayInterval value of 126.
This value is in log2 seconds. The valid range of values is -3 (2-3 = 0.125
seconds) to 17 (217 = 131072 seconds).
Advanced Features
219
Advanced Feature Commands
asymmetry_time
The time that the propagation delay from this switch to the neighbor is less
than the estimated one-way propagation delay between the switch and its
neighbor (which is also the time that the propagation delay from the
neighbor to this switch is greater than the estimate). This value is negative if
the propagation delay to the neighbor is greater than the estimate. It can be
in nanoseconds, microseconds, milliseconds, or seconds. The maximum value
is 4,294,967,295 nanoseconds (approximately 4.3 seconds). Let tIR be the
propagation delay from this switch (initiator) to the neighbor (responder),
tRI be the propagation delay from the neighbor to this switch, and
meanPathDelay be the estimated one-way propagation delay. Then:
• meanPathDelay = (tIR + tRI) / 2
• tIR = meanPathDelay – asymmetry_time
• tRI = meanPathDelay + asymmetry_time
neighbor_thresh_time
The maximum measured mean of the propagation delay between this switch
and the neighbor above which the switch considers the port unable to run
gPTP. This value can be in nanoseconds, microseconds, milliseconds, or
seconds.
auto
Use a media specific default value for the neighbor_thresh_time:
• Copper: 800 nanoseconds. This category includes short range copper
cables such as SFP+ Direct Attach and QSRP+ Passive Copper.
• Multi-mode fiber: 11 microseconds. This category includes the QSFP+
Active Optical cables. 11 microseconds allows 10 microseconds for
100BASE-FX 2 km plus 10% tolerance.)
• Single-mode fiber: 550 microseconds. This allows 500 microseconds for
our “LX100” transceiver plus 10% tolerance.
Note
These values may change. A draft of the 802.1AS corrigendum
(P802.1AS-Cor-1/D1.1) specifies 800 ns for 100BASE-TX and
1000BASE-T.
Default
•
•
•
•
Lost_responses_value = 3 (802.1AS 11.5.3)
Log_2_interval = 0 (1 second; not specified in 802.1AS)
Asymmetry_time = 0 (802.1AS 10.2.4.8)
Neighbor_thresh_time = Copper media: 800 nanoseconds, fiber media: 4,294,967,295 nanoseconds
Usage Guidelines
Peer Delay messages determine whether a neighboring system is gPTP capable and measure the
propagation delay on the link between the switch and a neighboring gPTP capable system.
•
•
•
•
allowed-lost-responses corresponds to 802.1AS parameter allowedLostResponses.
initial-req-interval corresponds to 802.1AS parameter initialLogPdelayReqInterval.
asymmetry corresponds to 802.1AS parameter delayAsymmetry.
neighbor-thresh corresponds to 802.1AS parameter neighborPropDelayThresh.
Advanced Features
220
Advanced Feature Commands
Example
configure network-clock gptp ports 1-3 peer-delay allowed-lost-responses 5
configure network-clock gptp ports 1-2 peer-delay initial-log-interval -3
configure network-clock gptp ports 1-2 peer-delay neighbor-thresh 3
nanoseconds
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure network-clock gptp ports sync
configure network-clock gptp ports [port_list | all] sync [initial-interval
log_2_interval receipt-timeout timeout_count]
Description
Configures gPTP synchronization parameters on the specified ports.
Syntax Description
port_list
Specifies one or more of the switch's physical ports.
all
Specifies all of the switch's physical ports.
log_2_interval
The interval between Sync messages used by the switch for the port when
the port is initialized or when the switch receives a message interval request
TLV with timeSyncInterval value of 126. This value is in log2 seconds. The valid
range of values is -3 (2-3 = 0.125 seconds) to 17 (217 = 131072 seconds).
timeout_count
On a gPTP slave port, the number of sync intervals to wait without receiving a
Sync message before assuming the adjacent master port is no longer sending
Sync messages.
Default
•
•
log_2_interval = -3 (0.125 second; 802.1AS 11.5.2.3)
timeout_count = 3 (802.1AS 10.6.3.1)
Usage Guidelines
Synchronization distributes the time from the grandmaster to all other time-aware systems in the
networks.
Advanced Features
221
Advanced Feature Commands
initial-interval corresponds to 802.1AS parameter initialLogSyncInterval.
receipt-timeout corresponds to 802.1AS parameter syncReceiptTimeout.
Example
configure network-clock gptp ports 1-2 sync initial-interval -1
configure network-clock gptp ports all sync receipt-timeout 5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
configure openflow controller
configure openflow controller [primary | secondary] [in-band [port port-number |
discovery] | out-of-band [active [ipaddress ipaddress | hostname host_name]
{port} | passive port]] {tls} {vr vr_name} {rate-limit rate_limit {burst-size
burst-size}}
Description
Configures the OpenFlow controller(s) that the switch will communicate with.
Syntax Description
primary
Specifies the primary openflow controller.
secondary
Specifies the secondary openflow controller.
port
Specifies the port number for in-band mode .
port-number
Specifies the physical port number.
out-of-band
Specifies the out-of-band connection to the controller.
active
Specifies that you actively connect to the controller .
ipaddress
Specifies that you use an IP address for active out-of-band mode; it might be
followed by tcp port.
ipaddress
Configures an IP address, for example: 192.168.32.25.
hostname
Specifies the hostname.
port
Specifies the TCP port. for example: 6643.
passive
Configures the passive mode for out-of-band; you must specify a tcp port.
Advanced Features
222
Advanced Feature Commands
tls
Specifies that you use the Transport Layer Security (TLS) option.
vr
Specifies that you use the virtual router option.
vr_name
Specifies the name of the virtual router.
rate-limit
Specifies the rate-limit Packet-In packets sent to the controller.
rate_limit
Specifies packets per second. Default is 1000, the range is 100-2147483647.
burst-size
Specifies that you use the burst-size with rate-limit.
burst-size
Specifies the burst size in bytes; the range is 1500-65536.
Default
If burst-size is not specified, the default is 1500 bytes. If rate_limit is not specified, the default
value is 1000.
Usage Guidelines
Use this command to configure the OpenFlow controller(s) that the switch will communicate with.
If only a secondary controller is configured, it will be treated as a primary controller until a primary
controller is configured.
OpenFlow attempts to communicate with the primary controller until connectivity fails, in which case it
automatically fails over to the secondary controller, if configured. 'out-of-band' control enables
controller(s) to connect to the switch using a non-OpenFlow vlan. ‘vr’ specifies the virtual router used
by the switch to communicate with the controller(s).
The rate-limit rate and burst-size burstSize options limit the rate and burst-size of
messages sent from the switch to the controller.
Example
The following example illustrates how to use the configure openflow controller command:
configure openflow controller primary out-of-band active ipaddress
10.1.1.1 6633 vr vr-mgmt
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the Openflow feature, see the Feature License Requirements document.
Advanced Features
223
Advanced Feature Commands
configure port reflective-relay
configure port port reflective-relay [on | off]
Description
Enables the direct attach feature on the specified port.
Syntax Description
port
Specifies a single port on which to enable the direct attach feature.
Default
Off.
Usage Guidelines
You should only enable the direct attach feature on ports that directly connect to a VM server running
VEPA software.
This feature requires installation of the Direct Attach feature pack. For more information, see the
Feature License Requirements document..
Example
The following command enables the direct attach feature on port 2:1:
configure port 2:1 reflective-relay on
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all Summit family switches and BlackDiamond X8, BlackDiamond 8000
series modules.
configure snmp traps batch-delay bfd
configure snmp traps batch-delay bfd none | delay
Advanced Features
224
Advanced Feature Commands
Description
This command allows you to configure the time during which the set of affected sessions will be
collected and a single trap will be set for contiguous session IDs. This means that there is a small delay
between event occurence and trap generation. You have the option to disable this optimization delay
using the none option.
Syntax Description
snmp
Configure SNMP specific settings.
traps
Configure SNMP Trap generation settings.
batch-delay
Maximum delay before trap generation in order to combine multiple traps
into a single trap.
none
Disables trap optimization which results in generation of one trap for status
change of each session.
delay
Choose delay to balance between number of traps and delay in trap
generation. Range is 50 to 65535 ms.
Default
1000 ms.
Usage Guidelines
Use this command to configure the time window during which the set of affected sessions is collected
and single trap is set for contiguous sessions IDs.
Example
The following command configures the BFD batch-delay:
configure snmp traps batch-delay bfd 1000
History
This command was first available in ExtremeXOS 15.5.
Platform Availability
This command is available on all platforms.
configure trill add access tag
configure trill add access tag first_tag {-last_tag}
Advanced Features
225
Advanced Feature Commands
Description
This command administratively adds a VLAN tag or range of VLAN tags that represent edge (or
access) VLANs attached to the TRILL network. The VLAN can be created using any method, for
example, via the CLI, XNV, ID Manager, or MVRP.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
add
Add entities to TRILL.
access
Access VLAN.
tag
VLAN ID values.
first_tag
Start VLAN ID between 1 and 4094";type="int32_t";range="[1,4094]
-
Range separator.
last_tag
End VLAN ID between 1 and 4094";type="int32_t";range="[1,4094]
Default
N/A.
Usage Guidelines
Use this command to add a VLAN tag or range of VLAN tags that represent edge (or access) VLANs
attached to the TRILL network. The VLAN can be created using any method, for example, via the CLI,
XNV, ID Manager, or MVRP. If the VLAN is already associated with a TRILL network, the operation is
ignored and the command continues configuring the remaining VLAN IDs in the specified set. The
last_tag is optional. When specified, all VLANs including the first_tag and last_tag are
configured as TRILL Access VLANs. If the last_tag is not specified, only the first_tag is
configured as a TRILL access VLAN. By default, no VLANs are configured as access VLANs when TRILL
is enabled. VLAN one (also called the Default VLAN) is also the default TRILL Network VLAN used to
carry TRILL data traffic. TRILL Hellos are sent on all TRILL access VLANs. TRILL Hellos sent on access
VLANs are sent with the AC flag set, indicating that the VLAN link should not be used in the TRILL
shortest best path and distribution tree topology calculations. The valid tag range is one to 4094.
Example
History
This command was first available in ExtremeXOS 15.4.
Advanced Features
226
Advanced Feature Commands
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill add network vlan
configure trill add network vlan vlan_name
Description
This command configures the TRILL protocol on the specified VLAN. If the specified VLAN name does
not exist, an error is returned. Once TRILL is added to a VLAN, the VLAN may become a designated
TRILL VLAN and carry TRILL data traffic. If TRILL is already configured on vlan_name, the command
completes with no errors.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
add
Add entities to TRILL.
network
Trunk network.
vlan
VLAN.
vlan_name
VLAN name.
Default
N/A.
Usage Guidelines
Use this command to configure the TRILL protocol on the specified VLAN. If the specified VLAN name
does not exist, an error is returned. Once TRILL is added to a VLAN, the VLAN may become a
designated TRILL VLAN and carry TRILL data traffic. If TRILL is already configured on vlan_name, the
command completes with no errors.
There are three types of TRILL VLANs: access, network, and hybrid. An access VLAN carries only native
Ethernet data traffic. Traffic associated with TRILL edge VLANs is either encapsulated for transmit over
the TRILL network or decapsulated from the TRILL network and transmitted as native tagged or
untagged traffic on the local VLAN. TRILL Network VLANs carry only TRILL encapsulated VLAN traffic.
Any native Ethernet traffic received on a TRILL Network VLAN is discarded and TRILL encapsulated
packets are never decapsulated and transmitted as native Ethernet traffic on a TRILL Network VLAN.
Link state information associated with Network TRILL VLANs is advertised and the associated links to
each RBridge neighbor are used in SPF calculations when building broadcast/multicast forwarding
trees. By default, when TRILL is enabled, the Default VLAN is a TRILL Network VLAN.
If the switch receives a TRILL Hello packet on a VLAN that is not configured for TRILL Network or
Access VLAN, an error message is logged. If the DRB specifies a designated VLAN ID and there is no
TRILL configured Network VLAN with that VLAN ID, then an error message is logged and the TRILL
Advanced Features
227
Advanced Feature Commands
peer session is not established. It is recommended that the TRILL Network VLAN ID be one (the Default
VLAN), which is the default TRILL Network VID stated in the TRILL IETF RFCs. This should allow
networks to be automatically configured and easily setup for network operation.
TRILL hybrid VLANs are VLANs that are configured as TRILL Network VLANs and a TRILL Access VLAN
and thus operate as both an Access and Network TRILL VLAN. TRILL Hybrid VLANs are not supported.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill appointed-forwarder
configure trill appointed-forwarder {distribution [shared {reappoint-mode [sticky
| balanced]} | priority]} {timer hold-time seconds }
Description
This command configures the algorithm the RBridge will use to appoint forwarders if the RBridge is the
Designated RBridge (DRB). By default, the DRB will assign VLAN IDs from the common set of access
VLANs configured by the RBridges on the shared link based on RBridge priority.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
appointed-forwarder
Appointed Forwarder control. Only valid if the RBridge is the Designated
RBridge.
distribution
Algorithm for assigning Appointed Forwarders.
shared
Evenly distribute the VLANs across all RBridges (default).
reappoint-mode
Method for managing Appointed Forwarders when new RBridges become
active or inactive.
sticky
Newly active RBridges don't change current VLAN assignments. Newly
inactive RBridge VLANs are reappointed (default).
balanced
Forces a recalculation of VLAN assignments for all VLANs when an RBridge
goes active or inactive.
Advanced Features
228
Advanced Feature Commands
priority
The RBridge with the highest priority becomes the Appointed Forwarder for
the VLAN.
timer
Timers for Appointed Forwarders.
hold-time
Amount of time Designated RBridge will remember VLAN appointments for
an RBridge that has gone inactive.
seconds
Hold time in seconds (0-600). (Default 180).
Default
Shared, 180 seconds.
Usage Guidelines
Use this command to configure the algorithm the RBridge will use to appoint forwarders if the RBridge
is the Designated RBridge (DRB). By default, the DRB will assign VLAN IDs from the common set of
access VLANs configured by the RBridges on the shared link based on RBridge priority. This provides
the simplest algorithm for assigning Access VLANs. The shared keyword assigns each access VLAN to
the set of connected RBridges such that each RBridge has the same number of forwarding VLANs. If an
RBridge becomes unavailable, the DRB reassigns VLAN IDs that were appointed to the down RBridge
to one of the remaining active RBridges. If the DRB fails, then the next highest priority RBridge assumes
the role of the DRB and takes over the responsibility of assigning appointed forwarders for each VLAN.
The default mode of appointing RBridge forwarding status is priority.
If the distribution algorithm is shared, the optional reappoint-mode keyword configures how VLAN
forwarding appointments are managed as RBridges become active or go inactive on a shared VLAN
distribution link. The default mode is sticky. In sticky reappoint mode, VLAN forwarding appointments
are maintained so long as the appointed forwarder RBridge is active. Only the VLANs that are
appointed to a failed RBridge are reappointed. This mode provides the most consistent and least
packet forwarding disruption when an RBridge fails. The downside to the sticky mode is that over time,
VLAN appointments between RBridges may become unbalanced. The balanced mode maintains VLAN
appointments based on the VLAN appointed forwarder algorithm. If an RBridge fails, The DRB
recalculates VLAN appointments after the appointed-forwarder hold time expires and communicates
the new assignments to the remaining active RBridges.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
Advanced Features
229
Advanced Feature Commands
configure trill delete access tag
configure trill delete access tag first_tag {-last_tag}
Description
This command administratively deletes a VLAN tag or range of VLAN tags from the configured access
VLAN set. VLANs that match the specified VLAN ID to be deleted are detached (disassociated) from
the TRILL network.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
delete
Delete entities from TRILL.
access
Access VLAN.
tag
VLAN ID values.
first_tag
Start VLAN ID between 1 and 4094";type="int32_t";range="[1,4094]
-
Range separator.
last_tag
End VLAN ID between 1 and 4094";type="int32_t";range="[1,4094]
Default
N/A.
Usage Guidelines
Use this command to delete a VLAN tag or range of VLAN tags from the configured access VLAN set.
VLANs that match the specified VLAN ID to be deleted are detached (disassociated) from the TRILL
network. If the VLAN has already been deleted from the TRILL network, the operation is ignored and
the command continues disassociating the remaining specified VLAN tags. The last_tag is optional.
When specified, all VLANs including the first_tag and last_tag are disassociated from the TRILL
network as access VLANs. If the last_tag is not specified, then only the VLAN identified by the
first_tag is disassociated with the TRILL network. By default, no VLANs are configured as access
VLANs when TRILL is enabled. The VLAN of one (also called the Default VLAN) also defaults to the
TRILL Network (or native) VLAN and is used to carry TRILL data traffic. If a VLAN is disassociated from
the TRILL network, the RBridge will cease sending TRILL Hellos on the specified VLAN. If the RBridge
was the appointed forwarder for the VLAN, one of the remaining RBridges (if any) is assigned the
appointed forwarding status for the VLAN. If there are no other RBridges connected to the VLAN,
traffic for this VLAN is no longer transported across the TRILL network and any received TRILL traffic
destined for devices attached to the VLAN is discarded.
Advanced Features
230
Advanced Feature Commands
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill delete network vlan
configure trill delete network vlan [ vlan_name | all ]
Description
This command removes TRILL from the specified network VLAN from the TRILL configuration. Once
deleted, no TRILL data packets are sent and any TRILL packets received are discarded. Any RBridge
links associated with the Network VLAN are removed from the database and the updated information
is communicated to remaining known RBridge peers. Deleting TRILL from a VLAN or deleting the VLAN
entirely may trigger RBridges to recalculate their dtrees. There must be at least one TRILL network
VLAN configured for the RBridge to participate in the TRILL network.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
delete
Delete entities to TRILL.
network
Trunk network.
vlan
VLAN.
vlan_name
VLAN name.
all
All VLANs.
Default
N/A.
Usage Guidelines
Use this command to remove TRILL from the specified network VLAN from the TRILL configuration.
Once deleted, no TRILL data packets are sent and any TRILL packets received are discarded. Any
RBridge links associated with the Network VLAN are removed from the database and the updated
information is communicated to remaining known RBridge peers. Deleting TRILL from a VLAN or
Advanced Features
231
Advanced Feature Commands
deleting the VLAN entirely may trigger RBridges to recalculate their dtrees. There must be at least one
TRILL network VLAN configured for the RBridge to participate in the TRILL network.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill designated-vlan
configure trill designated-vlan vlan_name
Description
This command configures the desired VLAN to use as the designated TRILL VLAN. The designated
VLAN is the VLAN that is used to carry TRILL data traffic between RBridges.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
designated-vlan
Desired designated VLAN.
vlan_name
Desired designated VLAN name.
Default
N/A.
Usage Guidelines
Use this command to configure the desired VLAN to use as the designated TRILL VLAN. The
designated VLAN is the VLAN that is used to carry TRILL data traffic between RBridges. By default, the
designated-vlan is the default VLAN, VLAN ID = 1. The designated VLAN may use any VLAN tag from
one through 4094. Only one VLAN per VR can be configured as the designated VLAN. In the event that
two RBridges are configured with different Designated VLAN IDs, the lowest value VLAN ID is used as
the designated VLAN tag. In this event, a informational message is logged indicating that another
RBridge was detected attempting to communicate using a different designated VLAN ID.
Advanced Features
232
Advanced Feature Commands
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill inhibit-time
configure trill inhibit-time seconds
Description
This command configures the amount of time the RBridge does not forward traffic to end stations after
detecting a root RBridge topology change or under certain conditions when the appointed forwarder
status changes.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
inhibit-time
Amount of time the RBridge does not forward traffic after detecting an
RBridge topology change.
seconds
Inhibit time in seconds (0-30). (Default 15).
Default
15.
Usage Guidelines
Use this command to configure the amount of time the RBridge does not forward traffic to end stations
after detecting a root RBridge topology change or under certain conditions when the appointed
forwarder status changes. The inhibit time is set to avoid packet loops when there are network
topology changes. The parameter seconds has a valid range of zero to 30 seconds and defaults to 15
seconds. A value of zero means that no packets will be inhibited from being forwarded.
Advanced Features
233
Advanced Feature Commands
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill mtu probe fail-count
configure trill mtu probe fail-count probes_sent
Description
This command configures the MTU probe failure count. RBridges send MTU probes to known peers to
determine and verify that the configured MTU size is supported on TRILL links. MTU probes are only
transmitted and acknowledged on the each link’s designated VLAN.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
mtu
Maximum Transmission Unit.
probe
Send MTU probes to determine and verify the configured MTU size supported
on TRILL links.
fail-count
Number of probe requests sent out before declaring failure.
probes_sent
Number of probes sent to determine the MTU size (1-10). (Default 2.)
Default
2.
Usage Guidelines
Use this command to configure the MTU probe failure count. RBridges send MTU probes to known
peers to determine and verify that the configured MTU size is supported on TRILL links. MTU probes are
only transmitted and acknowledged on the each link’s Designated VLAN. The MTU probe packet is
padded to the MTU size tested. If the RBridge fails to receive an MTU acknowledgement after fail-count
attempts, the MTU size test fails. When the RBridge’s configured MTU size is not supported, the
RBridge attempts to determine the peer’s MTU setting by lowering the MTU size and resending the
MTU probe. A modified binary algorithm of lowering and increasing the MTU size continues until the
Advanced Features
234
Advanced Feature Commands
exact MTU size is determined. MTU probe packets are sent at 500ms intervals until either an
acknowledgement is received or the configured probe fail-count is reached. The default fail-count
setting is 2 and the valid range is 1 to 10. Incoming Ethernet packets that are larger than the supported
MTU size and cannot be entirely encapsulated into a TRILL packet are discarded.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill mtu probe
configure trill mtu probe [enable | disable]
Description
This command configures the TRILL MTU probe protocol. When enabled, the RBridge will transmit an
MTU probe to known peers to validate that the RBridge peers are reachable using the configured MTU
size.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
mtu
Maximum Transmission Unit.
probe
Send MTU probes to determine and verify the configured MTU size supported
on TRILL links.
enable
Enable MTU probing (default).
disable
Disable MTU probing.
Default
Enabled.
Advanced Features
235
Advanced Feature Commands
Usage Guidelines
Use this command to configure the TRILL MTU probe protocol. When enabled, the RBridge will
transmit an MTU probe to known peers to validate that the RBridge peers are reachable using the
configured MTU size. MTU probes are only transmitted and acknowledged on the each link’s designated
VLAN. The MTU probe packet is padded to the MTU size tested. When MTU probes are disabled, no
MTU probe packets are transmitted and the network administrator must ensure that all TRILL links
support the configured MTU size. The default MTU probe setting is enable.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill mtu size
configure trill mtu size mtu_size
Description
This command configures the TRILL MTU size. Jumbo frames must be enabled on TRILL Network ports.
Jumbo frames allow fully formed non-jumbo Ethernet packet to be encapsulated and transported
across the TRILL network without fragmentation.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
mtu
Maximum Transmission Unit.
mtu_size
Size of Maximum Transmission Unit in octets (1470-9188). (Default 1518).
Default
1518 octets.
Advanced Features
236
Advanced Feature Commands
Usage Guidelines
Use this command to configure the TRILL MTU size. Jumbo frames must be enabled on TRILL Network
ports. Jumbo frames allow fully formed non-jumbo Ethernet packet to be encapsulated and
transported across the TRILL network without fragmentation. The default TRILL MTU size is 1518 octets.
Thus the minimum jumbo frame size is 1518 plus the size of the TRILL header plus any TRILL options.
The minimum TRILL header size with no options is 28 octets.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill nickname
configure trill nickname [nickname_id | nickname_string ] {new-nickname
new_nickname_id} {nickname-priority new_id_priority} {root-priority
new_root_priority} {name new_nickname_string}
Description
This command configures nickname parameters. By default, the switch randomly chooses a nickname
and verifies that the nickname is not already being used by another RBridge in the TRILL network.
Syntax Description
trill
Transparent Interconnection of Lots of Links
nickname
Nickname
nickname_id
Identifier between 1 and 0xFFBF in hex.
nickname_string
Name string up to 32 characters.
new-nickname
Priority value between 128 and 255. Lower numbers represent lower priority.
Default is 192.
new_nickname_id
Identifier between 1 and 0xFFBF in hex";type="hex_t";range="[1,65471].
nickname-priority
Nickname priority.
new_id_priority
Priority value between 128 and 255. Lower numbers represent lower priority.
root-priority
Root priority.
Advanced Features
237
Advanced Feature Commands
new_root_priority
Priority value between 0 and 65535. Lower numbers represent lower
priority.";type="uint16_t";range="[0,65535].
name
Human readable name associated with nickname.
new_nickname_string
Name string up to 32 characters";type="string";range="[1,32].
Default
N/A.
Usage Guidelines
Use this command to configure the nickname parameters. By default, the switch randomly chooses a
nickname and verifies that the nickname is not already being used by another RBridge in the TRILL
network. Each created nickname is advertised to the other RBridges in the TRILL network. If the
nickname is randomly generated, the nickname default priority is 0x00 (lowest priority). Optionally,
nickname string name may be configured.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill ports protocol
configure trill ports [port_list | all] protocol [enable | disable]
Description
This command enables and disables the TRILL Hello protocol per port. By default, the Hello protocol is
enabled on all ports. When enabled the RBridge is able to discover its neighbors and to exchange
topology information.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
ports
Port options.
Advanced Features
238
Advanced Feature Commands
port_list
Port list to configure.
all
Modify all ports in the system.
protocol
Enable or disable the TRILL protocol on port.
enable
Enable (default).
disable
Disable.
Default
Enabled.
Usage Guidelines
Use this command to enable and disable the TRILL Hello protocol per port. By default, the Hello
protocol is enabled on all ports. When enabled the RBridge is able to discover its neighbors and to
exchange topology information. This information is used to dynamically program the data plane for
TRILL packet forwarding. If the TRILL Hello protocol is disabled, the RBridge is not able to peer with
any other RBridges in the TRILL network on the disabled port. This command can be used to reduce
the number of Hello packets transmitted on TRILL Access VLANs, by disabling TRILL on ports that are
not connected to a peer RBridge.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill ports
configure trill ports [port_list | all] {link-type [broadcast | point-to-point] }
{metric [ metric | automatic] } {drb-election priority}
Description
Advanced Features
239
Advanced Feature Commands
Syntax Description
trill
Transparent Interconnection of Lots of Links.
ports
Port options.
port_list
Port list to configure.
all
Modify all ports in the system.
link-type
Interface type for link.
broadcast
Indicates there may be multiple RBridges on the link. Does not run Hello
Protocol (default).
point-to-point
Assumes only one RBridge on the link. Does not run Hello Protocol.
metric
Link cost metric.
metric
Manual link cost metric. Range is 1 - 16777214.
automatic
Automatically determine link cost metric (default).
drb-election
Designated RBridge election.
priority
Priority value between 0 and 127. Lower numbers represent lower priority.
(Default is 64).
Default
Defaults are broadcast, automatic, and priority = 64.
Usage Guidelines
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill pseudonode
configure trill pseudonode [enable | disable]
Advanced Features
240
Advanced Feature Commands
Description
This command configures the RBridge to represent multiple devices on a shared link as being
connected to a TRILL pseudonode. By default, TRILL will automatically allocate a pseudonode ID when
two or more devices are connected to the RBridge on the same interface.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
pseudonode
Allow bypassing of pseudonodes on links.
enable
Enable bypass pseudonodes.
disable
Disable bypass pseudonodes.
Default
Enabled.
Usage Guidelines
Use this command to configure the RBridge to represent multiple devices on a shared link as being
connected to a TRILL pseudonode. By default, TRILL will automatically allocate a pseudonode ID when
two or more devices are connected to the RBridge on the same interface. Enabling pseudonode
support simplifies the LSDB topology graph. Specifying the disable keyword disables the capability.
When disabled, three or RBridges on the same interface is represented as a full mesh topology in the
LSDB.
The hardware data plane supports only one neighbor RBridge per port. If a second RBridge is detected
on the same port, a warning message is logged. The control plane will continue to exchange control
packetx with all RBridges on the port, but only one RBridge per port will go to active state. The second
RBridge may transition to active state if the peer session to the active RBridge terminates.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill system-id
Advanced Features
241
Advanced Feature Commands
configure trill system-id [switch-mac | system_id]
Description
This command configures the RBridge’s TRILL System ID. If not specified, the RBridge automatically
generates the TRILL ID by using internal system MAC address as the system-id.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
system-id
System ID.
switch-mac
Use the System MAC address as the system-id (default).
system_id
System ID. A six octet value in the format of xxxx.xxxx.xxxx; type=string;
range=[14,14]
Default
System MAC address.
Usage Guidelines
This command configures the RBridge’s TRILL System ID. The system-id is a six octet value. If not
specified, the RBridge automatically generates the TRILL ID by using internal system MAC address as
the system-id. An additional octet is appended to the end of the system ID to form the TRILL ID. The
default TRILL ID is formed by appending 0x00 to the end of the system ID. If the appended octet is
non-zero, then the TRILL ID represents a pseudonode.
The TRILL ID is used to identify the RBridge node in the Links State Database. When multiple RBridge
nodes are attached to the same link, the RBridge dynamically creates a pseudonode by assigning a
non-zero octet to the system ID. All of the TRILL neighbors on the shared link are represented in the
LSDB as being connected to the RBridge’s pseudonode. This simplifies the TRILL topology
representation. Up to 254 pseudonodes are supported.
Specifying the keyword switch-mac instructs the RBridge to use the switch’s universally administered
system MAC address to generate the TRILL ID. This is the default setting for the system-id.
Example
History
This command was first available in ExtremeXOS 15.4.
Advanced Features
242
Advanced Feature Commands
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill timers csnp
configure trill timers csnp interval seconds
Description
This command sets the minimum time between consecutive complete sequence number packet
(CSNP) transmissions on the specified interface.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
timers
Timers.
csnp
Complete Sequence Number Packet.
interval
Minimum time between CSNP transmissions on the specified interface.
seconds
Interval in seconds (1-65535). (Default 10).
Default
N/A.
Usage Guidelines
Use this command to set the minimum time between consecutive complete sequence number packet
(CSNP) transmissions on the specified interface. Periodic CSNPs are only sent on broadcast interfaces
and only by the DRB. Point-to-point adjacencies also use CSNPs also, but they are not periodic and are
unaffected by this command. The valid range for this parameter is 1-65535 seconds with a default value
of 10 seconds.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
Advanced Features
243
Advanced Feature Commands
configure trill timers hello
configure trill timers hello {multiplier number} {interval [seconds | minimal]}
Description
This command configures the TRILL Hello protocol timers. The multiplier keyword specifies the hello
multiplier. The hello multiplier is used in conjunction with the hello interval to compute the hold time.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
timers
Timers.
hello
Hello protocol.
multiplier
Hello multiplier.
number
Hello multiplier value from 2 to 100. (Default 3).
interval
Interval between two consecutive Hello transmissions.
seconds
Interval in seconds (1-65535). (Default 10).
minimal
Set interval based on 1 sec hold time. Hold time = interval * multiplier.
Default
N/A.
Usage Guidelines
Use this command to configure the TRILL Hello protocol timers. The multiplier keyword specifies the
hello multiplier. The hello multiplier is used in conjunction with the hello interval to compute the hold
time. The hold time is included in Hello PDUs and is calculated by multiplying the hello multiplier by the
hello transmit interval. The hold time tells the neighboring RBridge how long to wait before declaring
the sending RBridge inactive. The valid range for this parameter is from two to 100 with a default value
of 3. Interval specifies the interval between two consecutive Hello transmissions. The valid range for this
parameter is from one to 65535 seconds with a default value of 10 seconds.
Example
History
This command was first available in ExtremeXOS 15.4.
Advanced Features
244
Advanced Feature Commands
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill timers lsp
configure trill timers lsp {generation-interval generation_seconds} {refreshinterval refresh_seconds} {lifetime lifetime_seconds} {transmit-interval
milliseconds} {retransmit-interval retransmit_seconds} {checksum [enable |
disable]}
Description
This command configures the TRILL Link State Protocol timers.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
timers
Timers.
lsp
Link State Protocol.
generation-interval
Minimum time required to wait before regenerating the same LSP.
generation_seconds
Generation interval in seconds (1-120). (Default 30).
refresh-interval
Refresh rate for locally originated LSPs.
refresh_seconds
Refresh interval in seconds (1-65535). (Default 90).
lifetime
Remaining time for locally originated LSPs.
lifetime_seconds
Lifetime in seconds (350-65535). (Default 1200).
transmit-interval
Minimum time between LSP transmissions.
milliseconds
Transmit interval in milliseconds (1-4294967295). (Default 33).
retransmit-interval
Time to wait for an acknowledgement of the transmitted LSP on a point-topoint interface.
retransmit_seconds
Retransmit interval in seconds (1-65535). (Default 5).
checksum
Checksum calculation for Link State PDUs.
enable
Enable checksum.
disable
Disable checksum.
Default
N/A.
Usage Guidelines
Use this command to configure the TRILL Link State Protocol timers.
Advanced Features
245
Advanced Feature Commands
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill timers spf backoff-delay
configure trill timers spf backoff-delay {minimum minimum_delay} {maximum
maximum_delay}
Description
This command configures the TRILL SPF back-off timer delay. The backoff-delay keyword specifies the
exponential back-off delays between SPF calculations.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
timers
Timers.
spf
Shortest Path First.
backoff-delay
Exponential back-off delays between SPF calculations.
minimum
Minimum value for backoff-delay.
minimum_delay
Minimum backoff delay in milliseconds (1-2147483647). (Default 500).
maximum
Maximum value for backoff-delay.
maximum_delay
Maximum backoff delay in milliseconds (1-2147483647). (Default 50000).
Default
N/A.
Usage Guidelines
Use this command to configure the TRILL SPF back-off timer delay. The backoff-delay keyword
specifies the exponential back-off delays between SPF calculations. The minimum keyword specifies
the minimum duration between SPF calculations. The maximum keyword specifies the maximum
duration between SPF calculations. The valid range for these parameters is from one to 2,147,483,647
Advanced Features
246
Advanced Feature Commands
milliseconds with a default minimum value of 500 milliseconds and a default maximum value of 50000
milliseconds.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill timers spf
configure trill timers spf {restart restart_interval} {interval seconds}
Description
This command configures the TRILL SPF restart time and periodic calculation interval. The restart
keyword specifies the restart timer for the RBridge LSP database.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
timers
Timers.
spf
Shortest Path First.
restart
Restart timer for the RBridge LSP database.
restart_interval
Restart interval in seconds (5-65535). (Default 60).
interval
Minimum time to wait between SPF calculations.
seconds
Interval in seconds (1-120). (Default 10).
Default
N/A.
Usage Guidelines
Use this command to configure the TRILL SPF restart time and periodic calculation interval. The restart
keyword specifies the restart timer for the RBridge LSP database. If timer expires before the LSDB has
Advanced Features
247
Advanced Feature Commands
been resynchronized, the SPF is run. The valid range for this parameter is from five to 65535 seconds
with a default value of 60 seconds.
This interval keyword specifies the minimum time to wait between SPF calculations. This helps prevent
overloading the switch CPU in the event a link flap causes several back-to-back SPF calculations. The
valid range for this parameter is from one to 120 seconds with a default value of 10 seconds.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure trill tree prune vlan
configure trill tree prune vlan [enable | disable]
Description
This command configures tree pruning for all trees in-use as specified by the use count. VLAN tags can
be pruned from trees to reduce unnecessary traffic flooding.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
tree
Distribution Tree.
prune
Prune unreachable destinations.
vlan
Prune unreachable VLAN destinations.
enable
Enable pruning (default).
disable
Disable pruning.
Default
Enabled.
Advanced Features
248
Advanced Feature Commands
Usage Guidelines
Use this command to configure tree pruning for alltrees in-use as specified by the use count. VLAN tags
can be pruned from trees to reduce unnecessary traffic flooding. VLANs cannot be pruned when
RBridges are configured to perform VLAN translation. This is indicated by the VLAN Mapping (VM) flag
in the RBridge TRILL Hellos. By default, tree pruning is disabled. When VLAN pruning is enabled, leaves
of trees may be filtered for Access VLANs that are not configured at the edge of an RBridge. Thus,
flood traffic is only transported to remote RBridges that have devices connected to the encapsulated
packet’s VLAN.
Example
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
configure vlan dynamic-vlan uplink-ports
configure vlan dynamic-vlan uplink-ports [ add {ports} port_list | delete {ports}
[port_list | all] ]
Description
Statically provisions uplink ports for all dynamically created VLANs.
Syntax Description
dynamic-vlan
Configuration options for dynamically created VLANs.
uplink-ports
Tagged uplink ports for VLANs created by EXOS.
add
Add ports to dynamic VLAN uplink port list.
delete
Remove ports from dynamic VLAN uplink port list.
ports
Ports to be configured as uplink ports.
port_list
List of ports separated by a comma or -." ;type=portlist_t";
all
Clear the dynamic VLAN uplink port list.
Default
N/A.
Advanced Features
249
Advanced Feature Commands
Usage Guidelines
Use this command to statically provision uplink ports for dynamically created VLANs.
Example
X460-48p.3 # conf vlan dynamic-vlan uplink-ports add ports 16-18X460-48p.4 #
conf vlan dynamic-vlan uplink-ports add 20,22,24X460-48p.5 # configure vlan
dynamic-vlan uplink-ports delete ports 22X460-48p.7 # configure vlan dynamicvlan uplink-ports delete 16-18X460-48p.8 # configure vlan dynamic-vlan uplinkports delete all
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
configure vm-tracking authentication database-order
configure vm-tracking authentication database-order [[nms] | [vm-map] | [local] |
[nms local] | [local nms] | [nms vm-map] | [vm-maplocal] | [local vm-map] | [nms
vm-map local] | [localnmsvm-map]]
Description
Configures the authentication database options and sequence for VM authentication.
Syntax Description
nms
Specifies the configured Network Management System (NMS).
vm-map
Specifies the configured VMMAP file.
local
Specifies the configured local database.
Default
nms vm-map local.
Usage Guidelines
The switch attempts VM authentication in the sequence specified. For example, in the default
configuration, the switch attempts NMS authentication first, VMMAP authentication second, and local
authentication third. If nms is specified, the switch always attempts NMS authentication before
attempting VMMAP file authentication.
Advanced Features
250
Advanced Feature Commands
Example
The following command configures the database authentication order:
configure vm-tracking authentication database-order local nms vm-map
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
configure vm-tracking blackhole
configure vm-tracking blackhole [policy policy_name | dynamic-rule rule_name |
none]
Description
Specifies a policy file or dynamic ACL rule to apply to VMs during periods that are outside of the
approved time slot for that VM.
Syntax Description
policy_name
Specifies the name of a policy file to apply to the VM authentication request.
rule_name
Specifies the name of an ACL rule to apply to the VM authentication request.
Default
N/A.
Usage Guidelines
This command is not supported in this software release. It will be supported in a future release.
The none option applies no policy name or ACL rule during periods that are outside of the approved
time slot for that VM.
Note
This command is provided to support future identity management features. It serves no
practical purpose in this release.
Advanced Features
251
Advanced Feature Commands
Example
The following command applies no policy name or ACL rule during periods that are outside of the
authorized authentication period:
configure vm-tracking blackhole none
History
This command was first visible in ExtremeXOS 12.5, but it is not supported in this release. This
command will be supported in a future release.
Platform Availability
This command is available on all platforms.
configure vm-tracking local-vm
configure vm-tracking local-vm mac-address mac [name name | ip-address ipaddress
| vpp vpp_name] | vlan-tag tag {vr vr_name}]
Description
Configures the parameters associated with a local VM database entry to be used for VM MAC local
authentication.
Syntax Description
mac
Specifies the MAC address for the VM database entry you want to configure.
name
Specifies a name to represent this VM in show vm-tracking command display.
ipaddress
Specifies the IP address for the VM. This must match the IP address
configured on the VM.
vpp_name
Specifies the name of a VPP to apply to the local VM.
tag
VLAN tag between 1 and 4094.
vr_name
Virtual router name.
Default
N/A.
Usage Guidelines
Before you configure a VM entry in the local VM database, you must create the entry with the create
vm-tracking local-vm command.
Advanced Features
252
Advanced Feature Commands
Before you assign an VPP to a VM entry in the local VM database, you must create the VPP with the
create vm-tracking vpp command.
Example
The following command configures an IP address for the VM entry specified by the MAC address:
configure vm-tracking local-vm mac-address 00:E0:2B:12:34:56 ip-address
10.10.10.1
History
This command was first available in ExtremeXOS 12.5.
The ingress-vpp and egress-vpp options were replaced with the vpp option in ExtremeXOS 12.6.
The vlan-tag and vr-name options were added in 15.3.
Platform Availability
This command is available on all platforms.
configure vm-tracking nms timeout
configure vm-tracking nms timeout seconds
Description
Configures the timeout period for authentication attempts with the configured NMS servers.
Syntax Description
seconds
Specifies the timeout period in seconds.
Default
3 seconds.
Usage Guidelines
None.
Advanced Features
253
Advanced Feature Commands
Example
The following command configures the switch to allow 1 minute for successful authentication of a VM
with the NMS server:
configure vm-tracking nms timeout 60
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
configure vm-tracking nms
configure vm-tracking nms [primary | secondary] server [ipaddress | hostname]
{udp_port} client-ip client_ip shared-secret {encrypted} secret {vr vr_name}
Description
Configures the switch RADIUS client to an NMS for VM authentication.
Syntax Description
primary | secondary
Specifies the whether you are configuring the primary or secondary NMS.
ipaddress
Specifies the NMS IP address.
hostname
Specifies the NMS DNS hostname.
udp_port
Specifies the UDP port number of the NMS application.
client_ip
Specifies the client IP address, which is the switch IP address on the interface
leading to the NMS.
encrypted
Specifies that the secret key for communications with the NMS is encrypted.
secret
Specifies a key or password for communications with the NMS.
vr_name
Specifies the VR that is used to access the NMS.
Default
N/A.
Usage Guidelines
The NMS is a RADIUS server such as the one provided with Ridgeline.
Advanced Features
254
Advanced Feature Commands
Example
The following command configures the switch to authenticate VMs through the primary NMS server
Ridgeline using the password password:
configure vm-tracking nms primary server Ridgeline client-ip 10.10.3.3 sharedsecret password
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
configure vm-tracking repository
configure vm-tracking repository [primary | secondary] server [ipaddress |
hostname] {vr vr_name} {refresh-interval seconds} {path-name path_name} {user
user_name {encrypted} password}
Description
Configures FTP file synchronization for NVPP and VMMAP files.
Syntax Description
primary | secondary
Specifies the whether you are configuring the primary or secondary FTP
server.
ipaddress
Specifies the FTP server IP address.
vr_name
Specifies the VR that is used to access the FTP server.
seconds
Specifies how often the switch updates the local files that are synchronized
with the FTP server. The range is 40 to 3600 seconds.
path_name
Specifies the path to the repository server files from the FTP server root
directory. The default directory for repository server files is: pub.
user_name
Specifies a user name for FTP server access. If no username is specified, the
switch uses user name anonymous.
encrypted
This keyword indicates that the specified password is encrypted.
password
Specifies the password for the specified user name.
Default
Refresh interval: 600 seconds.
Advanced Features
255
Advanced Feature Commands
Usage Guidelines
Some jitter is added to the refresh interval period to prevent all switches from downloading files at the
same time.
Example
The following command configures the switch to refresh the VMMAP and NVPP files from primary FTP
server ftp1 every 5 minutes:
configure vm-tracking repository primary server ftp1 refresh-interval 300
History
This command was first available in ExtremeXOS 12.5.
Support for specifying an FTP user name was added in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure vm-tracking timers
configure vm-tracking timers reauth-period reauth_period
Description
Configures the RADIUS reauthentication period for VM MAC addresses.
Syntax Description
reauth_period
Specifies the reauthentication period in seconds. The ranges are 0 and
30-7200 seconds.
Default
0 seconds.
Usage Guidelines
One way to periodically apply Virtual Port Profiles (VPPs) to VM MAC addresses is to configure a
reauthentication period. At the end of each reauthentication period, the switch reauthenticates each
VM MAC address and applies any updated VPPs.
Advanced Features
256
Advanced Feature Commands
This command applies to only those VMs that authenticate through RADIUS. Reauthentication is
disabled when the reauthentication period is set to 0 seconds. When reauthentication is disabled, the
VM MAC address remains authenticated until the FDB entry for that VM expires.
Example
The following command enables RADIUS server reauthentication at 2 minute intervals:
configure vm-tracking timers reauth-period 120
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
configure vm-tracking vpp add
configure vm-tracking vpp vpp_name add [ingress | egress] [policy policy_name |
dynamic-rule rule_name] {policy-order policy_order}
Description
Configures an LVPP to use the specified policy or ACL rule.
Syntax Description
vpp_name
Specifies the name of an existing LVPP.
add
Specifies whether the LVPP should start using the specified policy or rule.
ingress
Specifies that the policy mapped to the LVPP is for ingress traffic.
egress
Specifies that the policy mapped to the LVPP is for egress traffic.
policy_name
Specifies a policy to add to or delete from the LVPP.
rule_name
Specifies a dynamic ACL rule to add to or delete from the LVPP.
Default
N/A.
Advanced Features
257
Advanced Feature Commands
Usage Guidelines
Multiple ACL or policy files can be mapped to each LVPP. A maximum of 8 ingress and 4 egress ACL or
policies are available to be mapped to each LVPP. If the policy file or dynamic rule specified in this
command fails to bind, then the CLI command is rejected.
Before you can configure an LVPP, you must first create it with the create vm-tracking vpp
command.
Example
The following command configures LVPP vpp1 to use the dynamic ACL rule named rule1 for ingress
traffic:
configure vm-tracking vpp vpp1 add ingress dynamic-rule rule1
History
This command was first available in ExtremeXOS 12.5.
The ingress and egress keywords were added in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure vm-tracking vpp counters
configure vm-tracking vpp vpp_name counters [ingress-only | egress-only | both |
none]
Description
Configures whether counters need to be installed for Virtual Machine MAC which receives this VPP
mapping.
Syntax Description
ingress-only
Only counts packets ingressing the switch whose source MAC address
matches VM MAC.
egress-only
Only counts packets egressing the switch whose source MAC address
matches VM MAC.
both
Counts packets ingressing and egressing the switch whose source MAC
address matches VM MAC.
none
No packets will be counted.
Advanced Features
258
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Use this command to configure whether counters need to be installed for Virtual Lachine MAC which
receives this VPP mapping.
Example
Example output not yet available and will be provided in a future release.
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms that support egress ACLs.
configure vm-tracking vpp delete
configure vm-tracking vpp vpp_name delete [ingress | egress] [policy policy_name
| dynamic-rule rule_name] {policy-order policy_order}
Description
Specifies that the LVPP should stop using the specified policy or rule.
Syntax Description
vpp_name
Specifies the name of an existing LVPP.
delete
Specifies whether the LVPP should stop using the specified policy or rule.
ingress
Specifies that the policy mapped to the LVPP is for ingress traffic.
egress
Specifies that the policy mapped to the LVPP is for egress traffic.
policy_name
Specifies a policy to add to or delete from the LVPP.
rule_name
Specifies a dynamic ACL rule to add to or delete from the LVPP.
Default
N/A.
Advanced Features
259
Advanced Feature Commands
Usage Guidelines
Multiple ACL or policy files can be mapped to each LVPP. A maximum of 8 ingress and 4 egress ACL or
policies are available to be mapped to each LVPP. If the policy file or dynamic rule specified in this
command fails to bind, then the CLI command is rejected.
Before you can configure an LVPP, you must first create it with the create vm-tracking vpp
command.
Example
The following command configures LVPP vpp1 to use the dynamic ACL rule named rule1 for ingress
traffic:
configure vm-tracking vpp vpp1 add ingress dynamic-rule rule1
History
This command was first available in ExtremeXOS 12.5.
The ingress and egress keywords were added in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
configure vm-tracking vpp vlan-tag
configure vm-tracking vpp vpp_name vlan-tag tag {vr vr_name}
Description
This command configures the VLAN tag and VR name for VPP. If the detected VM MAC uses this VPP,
then the port in which the VM MAC is detected will be placed on this VR/VLAN.
Syntax Description
vpp_name
Specifies a name for the LVPP.
tag
Specifies a name for the VLAN tag.
vr_name
Specifies a name for the Virtual Router.
Default
N/A.
Advanced Features
260
Advanced Feature Commands
Usage Guidelines
Use this command to configure the VLAN tag and VR name for VPP. If the detected VM MAC uses this
VPP, then the port in which the VM MAC is detected will be placed on this VR/VLAN.
Example
Example output not yet available and will be provided in a future release.
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
create cfm domain dns md-level
create cfm domain dns name md-level level
Description
Creates a maintenance domain (MD) in the DNS name format and assigns an MD level to that domain.
Syntax Description
name
Assigns the name you want for this domain, using the DNS name format.
Enter alphanumeric characters for this format; the maximum is 43 characters.
level
Specifies the MD level you are assigning to this domain. Enter a value
between 0 and 7.
Default
N/A.
Usage Guidelines
You can have up to 8 domains on a switch, and each one must have a unique MD level.
You assign each domain a maintenance domain (MD) level, which function in a hierarchy for forwarding
CFM messages. The levels are from 0 to 7; with the highest number being superior in the hierarchy.
The IEEE standard 801.2ag specifies different levels for different network users, as follows:
• 5 to 7 for end users
• 3 and 4 for Internet service providers (ISPs)
Advanced Features
261
Advanced Feature Commands
•
0 to 2 for operators (entities carrying the information for the ISPs)
Note
MEPs with intervals 3 and 10 cannot be created in this domain as the domain name format
is of dns type.
Example
The following command creates a domain, using the DNS name format, named extreme and assigns
that domain an MD level of 2:
create cfm domain dns extreme md-level 2
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
create cfm domain mac md-level
create cfm domain mac mac-addr int md-level level
Description
Creates a maintenance domain (MD) in the MAC address + 2-octet integer format and assigns an MD
level to that domain.
Syntax Description
mac-addr
Enter a MAC address in the format XX:XX:XX:XX:XX:XX to specify part of the domain name.
int
Enter the 2-octet integer you want to append to the MAC address to specify the domain name.
level
Specifies the MD level you are assigning to this domain. Enter a value between 0 and 7.
Default
N/A.
Usage Guidelines
You can have up to 8 domains on a switch, and each one must have a unique MD level.
Advanced Features
262
Advanced Feature Commands
You assign each domain a maintenance domain (MD) level, which function in a hierarchy for forwarding
CFM messages. The levels are from 0 to 7; with the highest number being superior in the hierarchy.
The IEEE standard 801.2ag specifies different levels for different network users, as follows:
• 5 to 7 for end users
• 3 and 4 for Internet service providers (ISPs)
• 0 to 2 for operators (entities carrying the information for the ISPs)
Example
The following command creates a domain, using the MAC + 2-octet integer format, with the MAC
address of 11:22:33:44:55:66 and an integer value of 63; it also assigns that domain an MD level of 2:
create cfm domain mac 11:22:33:44:55:66 63 md-level 2
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
create cfm domain string md-level
create cfm domain string str_name md-level level
Description
Creates a maintenance domain (MD) in the string name format and assigns an MD level to that domain.
Syntax Description
str_name
Enter a character string to specify part of the domain name. The maximum length is 43
characters.
level
Specifies the MD level you are assigning to this domain. Enter a value between 0 and 7.
Default
N/A.
Usage Guidelines
You can have up to 8 domains on a switch, and each one must have a unique MD level.
Advanced Features
263
Advanced Feature Commands
You assign each domain a maintenance domain (MD) level, which function in a hierarchy for forwarding
CFM messages. The levels are from 0 to 7; with the highest number being superior in the hierarchy.
The IEEE standard 801.2ag specifies different levels for different network users, as follows:
• 5 to 7 for end users
• 3 and 4 for Internet service providers (ISPs)
• 0 to 2 for operators (entities carrying the information for the ISPs)
Example
The following command creates a domain, using the string format having a value of extreme; it also
assigns that domain an MD level of 2:
create cfm domain string extreme md-level 2
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
create cfm segment destination
create cfm segment segment_name destination mac_addr {copy segment_name_to_copy}
Description
Creates a CFM segment.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
mac_addr
Specifies the MAC address.
segment_name_to_copy
Specifies the CFM segment whose configuration is to be copied.
Default
N/A.
Usage Guidelines
Use this command to explicitly create a CFM segment where the segment name is a 32-byte long
alpha-numeric character string.
Advanced Features
264
Advanced Feature Commands
Example
The following command creates a CFM segment named segment-new using MAC address
00:11:22:11:33:11 and copying segment-old:
create cfm segment segment-new destination 00:11:22:11:33:11 copy segment-old
Here, the copy existing cfm segment is an optional parameter, and if used, the following
configurations from the existing CFM segment are copied to the newly created segment:
• DMM transmission interval
• Class of service
• Threshold values
• Measurement window size
• Timeout value
Note
The copy option is not shown in "show config" as it is used only for copying the existing
values when creating a segment.
If you later configure any of the above mentioned information in segment-new, the old value(s) which
were copied from segment-old will be overwritten with the new one in segment-new, as is done for any
other commands. The same will not be true on the reverse case. If you modify the values of segmentold, the modified value will NOT be propagated to the CFM segments which use segment-old's
configurations. In other words, the configurations of segment-old that are at the time of creating
segment-new will alone be copied and not any other changes that are made to segment-old later on.
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
create trill nickname
create trill nickname nickname_id {nickname-priority id_priority } { rootpriority root_priority } {name nickname_string }
Description
This command allocates a nickname for use by the local RBridge. The nickname is a 16-bit number that
is unique within the TRILL network.
Advanced Features
265
Advanced Feature Commands
Syntax Description
trill
Transparent Interconnection of Lots of Links.
nickname
Nickname.
nickname_id
Identifier between 1 and 0xFFBF in hex";type="hex_t";range="[1,65471]
nickname-priority
Nickname priority
id_priority
Priority value between 128 and 255. Lower numbers represent lower priority.
Default is 192.
root-priority
Root priority
root_priority
Priority value between 0 and 65535. Lower numbers represent lower priority.
Default is 32768.
name
Human readable name associated with nickname.
nickname_string
Name string up to 32 characters";type="string";range="[1,32]
Default
N/A.
Usage Guidelines
Use this command to allocate a nickname for use by the local RBridge. The nickname is a 16-bit number
that is unique within the TRILL network. Each nickname identifies a distribution tree rooted at the local
RBridge and is used to identify an RBridge for the purpose of learning the unicast MAC address to
RBridge mapping. All of the nicknames are advertised to the other RBridges in the TRILL network in the
Nickname sub-TLV as part of the Group Address TLV. The optional nickname nickname_string is
locally significant and allows the network administrator to reference the nickname by an easily
remembered descriptive string. The nickname_string parameter has a maximum length of 32
octets and must start with a character. If the nickname’s string name is not specified, the show output
commands will indicate this by displaying the nickname value prefixed with the string “noname_” as
the string name.
Each RBridge must have a minimum of one nickname. When TRILL is enabled for the first time, a
default nickname is automatically created and the nickname value is randomly generated with the
default priority of 0x40. The default nickname string name is set to Default_nickname. The default
nickname cannot be deleted or modified and the parameters for the Default_nickname are not
configurable. Up to four additional nicknames may be created. The default nickname is only used when
the TRILL Hello protocol is enabled. If the TRILL Hello protocol is not enabled, the nickname_id must be
specified and must be unique within the TRILL network. The RBridge default nickname is not used
when the TRILL Hello protocol is disabled.
Example
The following example configures the RBridge’s nickname as “RBridge-C”. You could also specify the
root and nickname priority for this command, but since it’s not specified, the default values are used:
create trill nickname 102 name RBridge-C
Advanced Features
266
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
create vm-tracking local-vm
create vm-tracking local-vm mac-address mac {name name | ipaddress ipaddress vpp
vpp_name | vlan-tag tag {vr vr_name}}
Description
Creates a local VM database entry to be used for VM MAC local authentication, with optional
parameters.
Syntax Description
mac
Specifies the MAC address for the VM. This must match the MAC address
configured on the VM and be unique among the locally configure VM
addresses.
name
Specifies a name to represent this VM in show vm-tracking command
display.
ipaddress
Specifies the IP address for the VM. This must match the IP address
configured on the VM.
vpp_name
Specifies the virtual port profile to apply for the local VM.
tag
VLAN tag between 1 and 4094.
vr_name
Virtual router name.
Default
N/A.
Usage Guidelines
A VM name can include up to 32 characters. VM names must begin with an alphabetical letter, and only
alphanumeric, underscore ( _ ), and hyphen (-) characters are allowed in the remainder of the name.
VM names cannot match reserved keywords. For more information on VM name requirements and a list
of reserved keywords, see Object Names.
The following command creates a VM entry named VM1 in the local VM database:
create vm-tracking local-vm mac-address 00:E0:2B:12:34:56 name VM1
Advanced Features
267
Advanced Feature Commands
The following command creates a VM entry and assigns IP address 10.10.2.2 to the entry:
create vm-tracking local-vm mac-address 00:E0:2B:12:34:57 ip-address 10.10.2.2
The following command creates a VM entry and assigns VPP vpp1 to it:
create vm-tracking local-vm mac-address 00:E0:2B:12:34:58 vpp vpp1
History
This command was first available in ExtremeXOS 12.5.
The ingress-vpp and egress-vpp options were replaced with the vpp option in ExtremeXOS 12.6.
The vlan-tag and vr-name options were added in 15.3.
Platform Availability
This command is available on all platforms.
create vm-tracking vpp
create vm-tracking vpp vpp_name
Description
Creates a Local VPP (LVPP).
Syntax Description
vpp_name
Specifies a name for the new VPP.
Default
N/A.
Usage Guidelines
A VPP name can include up to 32 characters. VPP names must begin with an alphabetical letter, and
only alphanumeric, underscore (_), and hyphen (-) characters are allowed in the remainder of the
name. VPP names cannot match reserved keywords. For more information on VPP name requirements
and a list of reserved keywords, see Object Names of the .
Advanced Features
268
Advanced Feature Commands
Example
The following command creates a VPP named vpp1:
create vm-tracking vpp vpp1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
debug openflow show flows
debug openflow show [tables | controller stats | flows [vendor-table | exos-tree]
| flow flow_no]
Description
Displays the flows currently configured by the active controller. The command is used to show the
contents of the reference code flow table datastructure, or an EXOS-specific flow table datastructure.
Syntax Description
tables
Displays internal VLAN tables.
controller stats
Displays controller connection counters.
vendor-table
Displays the flows in vendor datastructure .
exos-tree
Displays flows in binary tree maintained by EXOS .
flow flow_no
Displays the match conditions and actions of flow_no
Default
None.
Usage Guidelines
Used to view internal tables, counters, and datastructures for debugging purposes.
Advanced Features
269
Advanced Feature Commands
Example
The following example displays openflow flow statistics:
debug openflow show flows exos-tree
=========================================
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
debug openflow
Short reference description.
debug openflow {on | off | {on} {{{verbosity verbosity} {output output_file}} | {{output
output_file} {verbosity verbosity}}}}
Description
Captures OpenFlow protocol packets for analysis.
Syntax Description
on
Turn debug on.
off
Turn debug off.
verbosity
Verbosity of output.
output
Output packet capture information to a file.
output_file
Output filename.
verbosity
0 (default) is the least detailed, 5 is the most detailed.
Default
0 is the default value for verbosity.
Usage Guidelines
Use this command to decode OpenFlow protocol packets sent to and from the connected OpenFlow
controllers for analysis.
Advanced Features
270
Advanced Feature Commands
Example
The following example turns debugging off:
debug openflow off
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
delete cfm domain
delete cfm domain domain
Description
Deletes the specified maintenance domain (MD) from the switch, as well as all configuration setting
related to this MD.
Syntax Description
domain
Enter the name of the domain you want to delete.
Default
N/A.
Usage Guidelines
This command deletes all configuration settings related to the domain—for example, all MAs, MIPs, and
MEPs—as well as the domain itself.
Example
The following command deletes the domain atlanta (as well as all settings related to this domain):
delete cfm domain atlanta
History
This command was first available in ExtremeXOS 11.4.
Advanced Features
271
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
delete cfm segment
delete cfm segment [segment_name | all]
Description
Deletes one or all CFM segments.
Syntax Description
segment_name
An alpha-numeric string identifying the segment name.
all
Specifies all CFM segments.
Default
N/A.
Usage Guidelines
Use this command to delete one or all CFM segments.
Example
The following command deletes the CFM segment named segment-new:
delete cfm segment segment-new
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
delete trill nickname
delete trill nickname [nickname_id | nickname_string | all]
Advanced Features
272
Advanced Feature Commands
Description
This command deletes a locally created nickname. Deleting a nickname removes the nickname from the
TRILL network.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
nickname
Nickname.
nickname_id
Identifier between 1 and 0xFFBF in hex.
nickname_string
Name string up to 32 characters.
all
All nicknames.
Default
N/A.
Usage Guidelines
Use this command to delete a locally created nickname. Deleting a nickname removes the nickname
from the TRILL network. This may cause a temporary network traffic disruption. The distribution tree
associated with the deleted nickname cannot be used by any other RBridge to forward multicast or
flood traffic. If the nickname is associated with a computed in-use distribution tree, another nickname
(associated with a tree that is possibly rooted at another RBridge) must be chosen, if one is available.
RBridges must flush MAC address FDB entries that are associated with the deleted nickname. The
default nickname cannot be deleted. Specifying the all keyword deletes all user-created nicknames on
the local RBridge, except for the default nickname.
Example
The following example illustrates how to delete all user-created nicknames on the local RBridge:
delete trill nickname all
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
delete vm-tracking local-vm
delete vm-tracking local-vm {mac-address mac}
Advanced Features
273
Advanced Feature Commands
Description
Deletes the specified VM entry in the local VM database.
Syntax Description
mac
Specifies the MAC address for a VM entry to delete.
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the VM entry for MAC address 00:E0:2B:12:34:56 in the local VM
database:
delete vm-tracking local-vm mac-address 00:E0:2B:12:34:56
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
delete vm-tracking vpp
delete vm-tracking vpp {vpp_name}
Description
Deletes the specified LVPP.
Syntax Description
vpp_name
Advanced Features
Specifies a name for the LVPP to delete.
274
Advanced Feature Commands
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the VPP named vpp1:
delete vm-tracking vpp vpp1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
disable avb ports
disable avb ports [port_list | all]
Description
This command is a macro command that can be used to disable all AVB protocols on the given ports. It
is equivalent to issuing the following three commands:
disable mvrp ports [port_list | all]
disable msrp ports [port_list | all]
disable network-clock gptp ports [port_list | all]
Syntax Description
avb
Audio Video Bridging.
port_list
Port list separated by a comma or "-".
all
All ports.
Default
Disabled.
Advanced Features
275
Advanced Feature Commands
Usage Guidelines
Use this command to disable all AVB protocols on the given ports.
Example
disable avb ports all
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
disable avb
disable avb
Description
This command is a macro command that can be used to disable all AVB protocols globally on the
switch. It is equivalent to issuing the following three commands:
disable mvrp
disable msrp
disable network-clock gptp
Syntax Description
avb
Audio Video Bridging
Default
Disabled.
Usage Guidelines
Use this command to disable all AVB protocols globally on the switch.
Advanced Features
276
Advanced Feature Commands
Example
disable avb
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
disable cfm segment frame-delay measurement
disable cfm segment frame-delay measurement segment_name {mep mep_id}
Description
Stops DMM frame transmission.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
mep mep_id
Specifies the maintenance association End Point that helps trigger a particular
MEP level session on that segment. The range is 1-8191. The default is all MEPs
on the segment.
Default
N/A.
Usage Guidelines
Use this command to stop transmission of DMM frames for a selected CFM segment. This command
stops transmission that has been triggered using the command enable cfm segment framedelay measurement .
This stops the transmission for both continuous and on-demand mode.
Example
The following command stops frame transmission on the CFM segment segment-first:
disable cfm frame-delay measurement segment-first
Advanced Features
277
Advanced Feature Commands
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
disable cfm segment frame-loss measurement mep
This stops the transmission for both continuous and on-demand mode.
disable cfm segment frame-loss measurement segment_name mep mep_id
Description
This command stops the transmission of the LMM frames for a particular cfm segment.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
This below command stops the transmission of the LMM frames for a particular cfm segment. This
stops the transmission for both continuous and on-demand mode.
Example
disable cfm segment cs2 frame-loss measurement mep 3
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
Advanced Features
278
Advanced Feature Commands
disable ethernet oam ports link-fault-management
disable ethernet oam ports [port_list | all] link-fault-management
Description
Disables Ethernet OAM on ports.
Syntax Description
port_list
Specifies the particular ports.
all
Specifies all fiber ports.
Default
Ethernet OAM is disabled on all ports.
Usage Guidelines
Use this command to disable Ethernet OAM on one or more specified ports or on all fiber ports.
When operating as a stack master, the Summit switch can process this command for ports on
supported platforms.
Example
The following command disables Ethernet OAM on port 1:
X460-48x.1 # disable ethernet oam ports 1 link-fault-management
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on the Summit X450a series switch only.
disable fip snooping
disable fip snooping {{vlan} vlan_name}
Advanced Features
279
Advanced Feature Commands
Description
This command disables FIP Snooping on one VLAN, or on all VLANS on which FIP Snooping is currently
enabled.
Disabling FIP Snooping on a VLAN causes the following changes on that VLAN:
•
•
All ACLs installed for the VLAN for FIP Snooping operation are removed.
All FDB entries for the VLAN are removed.
Note
Depending on the activity of connected devices, some dynamic FDB entries may appear.
•
•
•
All Enodes and virtual links learned on the VLAN are removed.
If the fcf-update mode is automatic, all FCFs learned on the VLAN are removed.
FDB learning is turned on for the VLAN.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of the VLAN on which FIP Snooping is to be disabled.
Default
Disabled.
Usage Guidelines
Use this command to disable FIP Snooping in the VLAN. This command has no effect if executed on a
VLAN for which no configuration record has been created. If a vlan_name is not specified, the
command disables FIP Snooping on all VLANS on which it is enabled.
Example
disable fip snooping vlan v3
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
Advanced Features
280
Advanced Feature Commands
•
•
Summit X670
Summit X770
disable msrp
disable msrp
Description
Disables MSRP on the switch.
Syntax Description
msrp
Multiple Stream Registration Protocol.
Default
Disabled.
Usage Guidelines
Use this command to disable MSRP on a switch.
Example
The following command disables MSRP:
disable msrp
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
disable mvrp ports
disable mvrp ports [port_list | all]
Description
Disable MVRP on a given set of ports.
Advanced Features
281
Advanced Feature Commands
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
port_list
Port(s) on which MVRP is to be enabled.
all
All ports.
Default
Disabled.
Usage Guidelines
Use this command to disable MVRP on given set of ports. MVRP is run on the MVRP enabled ports only
if the global setting is enabled. By default MVRP is disabled globally and on individual ports. When
MVRP is disabled globally, all MVRP packets will be forwarded transparently.
Example
The following command disables MVRP on ports 4 and 5:
disable mvrp ports 4-5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
disable mvrp
disable mvrp
Description
Disables MVRP globally on a switch.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
Default
Disabled.
Advanced Features
282
Advanced Feature Commands
Usage Guidelines
Use this command to disable MVRP globally on a switch. MVRP is run on the MVRP enabled ports only
if the global setting is enabled. By default, MVRP is disabled globally and on individual ports. When
MVRP is disabled globally, all MVRP packets are forwarded transparently.
Example
The following command disables MVRP:
disable mvrp
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
disable network-clock gptp ports
disable network-clock gptp ports [port_list | all]
Description
Disables gPTP on one or more ports.
Syntax Description
port_list
Specifies one or more the the switch's physical ports.
all
Specifies all of the switch's physical ports.
Default
Disabled.
Usage Guidelines
Use this command to configure on which ports gPTP runs. gPTP runs on no ports if it is not enabled in
the switch by enable network-clock gptp.
Example
disable network-clock gptp ports 1-3
Advanced Features
283
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
disable network-clock gptp
disable network-clock gptp
Description
Disables gPTP on the switch.
Syntax Description
network-clock
Network clock.
gptp
IEEE 802.1AS Generalized Precision Time Protocol (gPTP).
Default
Disabled.
Usage Guidelines
Use this command to disable gPTP after having enabled it.
Example
disable network-clock gptp
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
disable openflow vlan
Advanced Features
284
Advanced Feature Commands
disable openflow {vlan} vlan_name
Description
Disables OpenFlow on a specific VLAN.
Syntax Description
vlan
Specifies that OpenFlow is disabled on a VLAN.
vlan_name
Specifies the name of the VLAN to disable.
Default
None.
Usage Guidelines
You must specify a VLAN name to disable.
Example
The following command disables OpenFlow on VLAN 1:
disable openflow vlan 1
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document..
disable openflow
disable openflow
Description
Globally disables the Openflow application on the switch.
Advanced Features
285
Advanced Feature Commands
Syntax Description
disable
Disables openflow.
Default
The default is disabled.
Usage Guidelines
None.
Example
The following command disables Openflow on the switch:
disable openflow
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the Openflow feature, see the Feature License Requirements document.
disable snmp traps bfd
Short reference description.
disable snmp traps bfd session down | session-up
Description
This command disables session up/down trap reception for BFD.
Syntax Description
snmp
Configure SNMP specific settings.
traps
Configure SNMP Trap generation settings.
bfd
BFD-specific traps.
session-down
Generate trap when BFD session goes down.
session-up
Generate trap when BFD session goes up.
Advanced Features
286
Advanced Feature Commands
Default
Both session-down and session-up.
Usage Guidelines
Use this command to disable trap reception for BFD session up/down.
Example
The following command will disable trap generation for BFD session down events.
disable snmp traps bfd session-down
History
This command was first available in ExtremeXOS 15.5.
Platform Availability
This command is available on all platforms.
disable trill
disable trill
Description
This command disables the TRILL protocol on the switch. When disabled, the RBridge does not send
TRILL Hellos, calculate forwarding trees, and exchange LSPs and does clear the Link State Database
and terminates all TRILL packet forwarding.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
Default
N/A.
Usage Guidelines
Use this command to disable the TRILL protocol on the switch. When disabled, the RBridge does not
send TRILL Hellos, calculate forwarding trees, and exchange LSPs, but does clear the Link State
Database and terminates all TRILL packet forwarding. The All-RBridges and All-ISIS-RBridges functional
MAC addresses are removed from the local delivery filter table. Packets received with the RBridge
Advanced Features
287
Advanced Feature Commands
functional MAC addresses are treated as generic broadcast packets. The disable command will not
reset any TRILL configuration. Use the unconfigure trill command to clear all related TRILL
configuration.
Example
This example illustrates how to disable the TRILL protocol on the switch:
disable trill
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
disable vm-tracking dynamic-vlan ports
disable vm-tracking dynamic-vlan ports port_list
Description
This command disables VM-tracking dynamic VLAN on specific ports.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Use this command to disable VM-tracking dynamic VLAN on specific ports. The ALL option is not
supported because VM-tracking dynamic VLAN should not be enabled on a switch's uplink port.
Example
Example output not yet available and will be provided in a future release.
History
This command was first available in ExtremeXOS 15.3.
Advanced Features
288
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
disable vm-tracking ports
disable vm-tracking ports port_list
Description
Disables the XNV feature on the specified ports.
Syntax Description
port_list
Specifies one or more ports or slots and ports.
Default
Disabled.
Usage Guidelines
This command disables VM tracking on the specified ports.
Example
The following command disables VM tracking on port 2:1:
disable vm-tracking ports 2:1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
disable vm-tracking
disable vm-tracking
Description
Disables the Extreme Network Virtualization (XNV) feature on the switch.
Advanced Features
289
Advanced Feature Commands
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command disables the XNV feature, which tracks virtual machines (VMs) that connect to the
switch.
Note
When the VM tracking feature is disabled, file synchronization with the FTP server stops.
Example
The following command disables the XNV feature:
disable vm-tracking
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
disable msrp ports
disable msrp ports [port_list | all]
Description
Disables MSRP on the ports listed in the command after the keyword ports.
Syntax Description
msrp
Multiple Stream Registration Protocol.
port_list
Port list separated by a comma or "-".
all
All ports.
Advanced Features
290
Advanced Feature Commands
Default
Disabled.
Usage Guidelines
Use this command to disable MSRP in the ports listed or all ports.
Example
disable msrp ports all
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable avb ports
enable avb ports [port_list | all]
Description
This command is a macro command that can be used to enable all AVB protocols on the switch. It is
equivalent to issuing the following three commands:
enable mvrp
enable msrp
enable network-clock gptp
Syntax Description
avb
Audio Video Bridging.
port_list
Port list separated by a comma or "-".
all
All ports.
Default
Disabled.
Advanced Features
291
Advanced Feature Commands
Usage Guidelines
Use this command to enable all AVB protocols on the given ports.
Example
enable avb ports 1-5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable avb
enable avb
Description
This command is a macro command that can be used to enable all AVB protocols globally on the
switch. It is equivalent to issuing the following three commands:
enable mvrp
enable msrp
enable network-clock gptp
Syntax Description
avb
Audio Video Bridging.
Default
Disabled.
Usage Guidelines
Use this command to globally enable all AVB protocols globally on the switch.
Advanced Features
292
Advanced Feature Commands
Example
enable avb
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable cfm segment frame-delay measurement
enable cfm segment frame-delay measurement segment_name { mep mep_id }
[continuous | count value]
Description
Triggers DMM frame transmission.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
mep
Specifies the maintenance association End Point that helps trigger a particular
MEP level session on that segment.
mep_id
Specifies the MEP-ID. The range is 1-8191. The default is all MEPs on the
segment.
continuous
Specifies that frames are to be sent continuously until stopped.
count
Specifies that a number of frames are to be sent.
value
Specifies the number of frames to send. The range is 1 to 4294967295.
Default
N/A.
Usage Guidelines
Use this command to trigger DMM frames at the specified transmit interval configured using the
command configure cfm segment transmit-interval .
Advanced Features
293
Advanced Feature Commands
Continuous transmission continues until it is stopped with the command disable cfm segment
frame-delay measurement or delete cfm segment .
Note
If you try to trigger the DMM frames for a segment that is not completely configured, the
frames are not transmitted for that segment, and an error message is displayed on the
console.
Example
The following command triggers continuous frame transmission on the CFM segment segment-first:
enable cfm frame-delay measurement segment-first continuous
History
This command was first available in ExtremeXOS 12.3.
The mep keyword was added in ExtremeXOS 15.4.
Platform Availability
This command is available on all platforms.
enable cfm segment frame-loss measurement mep
If the user specifies the mode as continuous, the LMM transmission will continue till it is stopped by the
user.
enable cfm segment frame-loss measurement segment_name mep mep_id [continuous |
count frames]
Description
This command is used to trigger LMM frames at the configured transmit-interval.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
continuous
Specifies that frames are to be sent continuously until stopped.
count
Specifies that a number of frames are to be sent.
value
Specifies the number of frames to send. The range is 1 to 4294967295.
Advanced Features
294
Advanced Feature Commands
Default
N/A.
Usage Guidelines
This command is used to trigger LMM frames at the configured transmit-interval. If the user specifies
the mode as continuous, the LMM transmission will continue till it is stopped by the user.
Note
If the user tries to trigger the LMM frames for a segment which is not completely configured,
the frames will not be transmitted for that segment, and an error message will be thrown.
Example
enable cfm segment cs2 frame-loss measurement mep 3 count 10
enable cfm segment cs2 frame-loss measurement mep 3 continuous
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
enable ethernet oam ports link-fault-management
enable ethernet oam ports [port_list | all] link-fault-management
Description
Enables Ethernet OAM on ports.
Syntax Description
port_list
Specifies the particular ports.
all
Specifies all fiber ports.
Default
Ethernet OAM is disabled on all ports.
Advanced Features
295
Advanced Feature Commands
Usage Guidelines
Use this command to enable Ethernet OAM on one or more specified ports or on all fiber ports.
Unidirectional link fault management is supported only on fiber ports.
Before enabling Ethernet OAM, autonegotiation must be turned off. The link should be a full duplex link.
If some ports cannot be enabled because, for instance, autonegotiation is not turned off, the command
is executed for those ports that can be enabled and reasons for the failed ports are displayed.
To display the Ethernet OAM configuration, use the show ethernet oam command.
When operating as a stack master, the Summit X450e switch can process this command for ports on
supported platforms.
Example
The following command enables Ethernet OAM on all fiber ports:
enable ethernet oam ports all link-fault-management
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on the Summit X450a series switches only.
enable fip snooping
enable fip snooping {{vlan} vlan_name}
Description
This command enables FIP Snooping in the VLAN. If no VLAN is specified, FIP Snooping is enabled on
all VLANs that have been added using the configure fip snooping add the {vlan} vlan_name
command.
A FIP Snooping VLAN is disabled by default.
Once FIP Snooping is enabled on a VLAN, the following events occur:
•
•
•
FDB learning is turned off for the VLAN.
All FDB entries of the VLAN are removed. If FCFs are manually configured FDB entries are added
for each such FCF.
ACLs are installed to block most FIP and FCoE frames.
Advanced Features
296
Advanced Feature Commands
Syntax Description
fip
FCoE Initialization Protocol
snooping
Snooping FIP frames
vlan_name
Name of the vlan on which FIP Snooping is to be enabled.
Default
Disabled.
Usage Guidelines
This command enables FIP Snooping in the VLAN.
Example
enable fip snooping vlan v3
History
This command was first available in ExtremeXOS 15.1
Platform Availability
This command is available on the following platforms:
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
•
•
•
•
enable msrp ports
enable msrp ports [port_list | all]
Description
Enables MSRP in the ports listed in the command after the keyword ports.
Syntax Description
msrp
Multiple Stream Registration Protocol.
port_list
Port list separated by a comma or "-".
all
All ports.
Advanced Features
297
Advanced Feature Commands
Default
Disabled.
Usage Guidelines
Use this command to enable MSRP in the ports listed or all ports.
Note
MSRP is not supported for Link Aggregated Ports.
Example
enable msrp ports 1-3
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable msrp
enable msrp
Description
Enables MSRP globally on the switch.
Syntax Description
msrp
Multiple Stream Registration Protocol.
Default
Disabled.
Usage Guidelines
Use this command to enable MSRP globally on a switch.
Advanced Features
298
Advanced Feature Commands
Example
The following command enables MSRP:
enable msrp
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable mvrp ports
enable mvrp ports [port_list | all]
Description
Enables MVRP on a given set of ports.
Syntax Description
mvrp
Multiple VLAN Registration Protocol
port_list
Port(s) on which MVRP is to be enabled.
all
All ports.
Default
Disabled.
Usage Guidelines
Use this command to enable MVRP on given set of ports. MVRP is run on the MVRP enabled ports only
if the global setting is enabled. By default, MVRP is disabled globally and on individual ports. When
MVRP is disabled globally, all MVRP packets will be forwarded transparently.
Note
MVRP is not supported for Link Aggregated Ports.
Advanced Features
299
Advanced Feature Commands
Example
The following command enables MVRP on ports 4 and 5:
enable mvrp ports 4-5
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
enable mvrp
enable mvrp
Description
Enables MVRP globally on a switch.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
Default
Disabled.
Usage Guidelines
Use this command to enable MVRP globally on a switch. MVRP is run on the MVRP enabled ports only if
the global setting is enabled. By default, MVRP is disabled globally and on individual ports. When MVRP
is disabled globally, all MVRP packets are forwarded transparently.
Example
The following command enables MVRP globally on the switch:
enable mvrp
History
This command was first available in ExtremeXOS 15.3.
Advanced Features
300
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
enable network-clock gptp ports
enable network-clock gptp ports [port_list | all]
Description
Enables gPTP on one or more ports.
Syntax Description
port_list
Specifies one or more of the switch’s physical ports.
all
Specifies all of the switch’s physical ports.
Default
Disabled.
Usage Guidelines
Use this command to configure on which ports gPTP runs. gPTP does not run on any ports if it is not
first enabled in the switch by the enable network-clock gptp command.
Example
enable network-clock gptp ports 4
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable network-clock gptp
enable network-clock gptp
Advanced Features
301
Advanced Feature Commands
Description
Enables gPTP on the switch.
Syntax Description
network-clock
Network clock.
gptp
IEEE 802.1AS Generalized Precision Time Protocol (gPTP).
Default
Disabled.
Usage Guidelines
Use this command to enable gPTP.
Example
enable network-clock gptp
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
enable openflow vlan
enable openflow {vlan} vlan_name
Description
Enables OpenFlow on specific VLANs .
Syntax Description
vlan
Specifies the VLAN on which to enable Openflow.
vlan_name
Specifies the VLAN name.
Advanced Features
302
Advanced Feature Commands
Default
No VLANs are enabled for OpenFlow by default.
Usage Guidelines
Only one VLAN can be enabled for OpenFlow on the switch.
Example
The following command specifies the ports to enable Openflow on the switch:
enable openflow
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the OpenFlow feature, see the Feature License Requirements document.
enable openflow
enable openflow
Description
Globally enables the Openflow application on the switch.
Syntax Description
enable
Enables openflow.
Default
The default is disabled.
Usage Guidelines
You do not have to issue this command before you issue other OpenFlow commands.
Advanced Features
303
Advanced Feature Commands
Example
The following command enables Openflow on the switch:
enable openflow
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
enable snmp traps bfd
enable snmp traps bfd session down | session-up
Description
This command enables session up/down trap reception for BFD.
Syntax Description
snmp
Configure SNMP specific settings.
traps
Configure SNMP Trap generation settings.
bfd
BFD-specific traps.
session-down
Generate trap when BFD session goes down.
session-up
Generate trap when BFD session goes up.
Default
Both session-down and session-up.
Usage Guidelines
Use this command to enable trap reception for BFD session up/down.
Advanced Features
304
Advanced Feature Commands
Example
The following command will enable trap generation for BFD session down events.
enable snmp traps bfd session-down
History
This command was first available in ExtremeXOS 15.5.
Platform Availability
This command is available on all platforms.
enable trill
enable trill
Description
This command enables TRILL data plane forwarding on the switch. Once enabled, the switch is capable
of operating as an RBridge.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
Default
N/A.
Usage Guidelines
Use this command to enable TRILL data plane forwarding on the switch. Once enabled, the switch is
capable of operating as an RBridge. By default, The default VLAN, VLAND ID of one, is automatically
configured to support TRILL forwarding. The default access VLAN tag space defaults to one through
4094. When TRILL is enabled, the All-RBridges and All-ISIS-RBridges functional MAC addresses are
installed and any packets sent to those addresses will be received and processed by the switch. TRILL
data packets are only transmitted on TRILL configured VLANs. TRILL Hello packets are transmitted on
all ports that are members of a TRILL configured VLANs and any VLAN that has a VLAN ID that
matches a VLAN ID in the TRILL Access VLAN tag space.
Example
This example illustrates how to enable TRILL data plane forwarding on the switch:
enable trill
Advanced Features
305
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
enable vm-tracking dynamic-vlan ports
enable vm-tracking dynamic-vlan ports port_list
Description
This command enables VM-tracking dynamic VLAN on specific ports. The ALL option is not supported
because VM-tracking dynamic VLAN should never be enabled on a switch's uplink port.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Use this command to enable VM-tracking dynamic VLAN on specific ports. The ALL option is not
supported because VM-tracking dynamic VLAN should not be enabled on a switch's uplink port.
Example
Example output not yet available and will be provided in a future release.
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
enable vm-tracking ports
enable vm-tracking ports port_list
Advanced Features
306
Advanced Feature Commands
Description
Enables the XNV feature on the specified ports.
Syntax Description
port_list
Specifies one or more ports or slots and ports.
Default
Disabled.
Usage Guidelines
You must enable VM tracking on the switch with the enable vm-tracking command before you can
use this command. This command enables VM tracking on the specified ports. You should enable VM
tracking only on ports that connect directly to a server that hosts VMs that you want to track. You
should never enable VM tracking on a switch uplink port.
Example
The following command enables VM tracking on port 2:1:
enable vm-tracking ports 2:1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
enable vm-tracking
enable vm-tracking
Description
Enables the XNV feature on the switch.
Syntax Description
This command has no arguments or variables.
Advanced Features
307
Advanced Feature Commands
Default
Disabled.
Usage Guidelines
This command enables the XNV feature, which tracks VMs that connect to the switch.
This command does not enable XNV on any ports. To start tracking VMs, you must enable VM tracking
on one or more ports using the enable vm-tracking ports command.
Example
The following command enables the XNV feature:
enable vm-tracking
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
enable/disable bfd vlan
[enable | disable] bfd vlan vlan_name
Description
Enables or disables BFD on a VLAN.
Syntax Description
vlan_name
Specifies the VLAN name.
Default
N/A.
Usage Guidelines
Use this command to enable or disable BFD on a VLAN.
Advanced Features
308
Advanced Feature Commands
Example
The following command enables the bfd on the VLAN named finance:
enable bfd vlan finance
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
ping mac port
The ping, or loopback message (LBM), goes from the MEP configured on the port toward the given
MAC address.
ping mac mac port port {domain} domain_name {association} association_name
Description
Allows you to ping on the Layer 2 level throughout the specified domain and MA.
Syntax Description
mac
Enter the unique system MAC address on the device you want to reach. Enter
this value in the format XX:XX:XX:XX:XX:XX.
port
Enter the port number of the MEP from which you are issuing the ping.
domain
Enter this keyword.
domain_name
Enter the name of the domain from which you are issuing the ping.
association
Enter this keyword.
association_name
Enter the name of the association from which you are issuing the ping.
Default
N/A.
Usage Guidelines
You must have CFM parameters configured prior to issuing a Layer 2 ping.
In order to send a Layer 2 ping, you must specify the port (MEP), the domain, and the MA from which
you are issuing the ping. An UP MEP sends the ping to all ports (except the sending port) on the VLAN
Advanced Features
309
Advanced Feature Commands
that is assigned to the specified MA, and a DOWN MEP sends the ping out from that port from that MA
toward the specified MAC address.
All MIPs along the way forward the LBM to the destination. The destination MP responds back to the
originator with a loopback reply (LBR).
This command sends out a ping from the MEP configured on the specified port toward the specified
MAC address. If you attempt to send a ping message from a port that is not configured as a MEP, the
system returns an error message. If the specified MAC address is not present in the Layer 2 forwarding
table (FDB), the system cannot send the ping (applies to UpMEP, not DownMEP).
Example
The following command sends a Layer 2 ping to the unique system MAC address 00:04:96:1F:A4:31
from the previously configured UP MEP (port 2:4) in the speed association in the atlanta domain:
ping mac 00:04:96:1F:A4:31 port 2:4 atlanta speed
The following is sample output from the Layer 2 ping command:
BD-12802.48 # ping mac 00:04:96:1e:14:70 port 2:12 "extreme" 100
Send L2 Ping from Down MEP on 2:12, waiting for responses [press Ctrl-C to
abort].
42 bytes from 00:04:96:1e:14:70, seq=4 time=17 ms
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
ping trill
Short reference description.
ping trill {count count} {interval interval} rbridge_nickname
Description
The TRILL ping command is used for debugging RBridge if there is any problem, or for verifying
RBridge connectivity.
Advanced Features
310
Advanced Feature Commands
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to debug RBridge if there is any problem, or for verifying RBridge connectivity.
Example
# ping count 2 interval 5 trill 0x3e
Reply from 0x003e (0004.966D.6562) RX on port: 1 time: 359 msec
Reply from 0x003e (0004.966D.6562) RX on port: 1 time: 249 msec
--- 0x003e
TRILL Echo
TRILL Echo
TRILL Echo
(0004.966D.6562) --Requests sent: 2
Replies received: 2
Frames lost: 0
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 series of switches.
run vm-tracking repository
run vm-tracking repository sync-now
Description
Manually starts FTP file synchronization for NVPP and VMMAP files.
Syntax Description
This command has no arguments or variables.
Advanced Features
311
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Before you can manually start FTP file synchronization, you must configure FTP servers using the
configure vm-tracking repository command.
Example
The following command starts file synchronization with the configured FTP server:
run vm-tracking repository sync-now
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show avb
show avb
Description
Displays a summary of MSRP, MVRP, and gPTP configuration on the switch.
Syntax Description
avb
Audio Video Bridging.
Default
N/A.
Usage Guidelines
Use this command to display a summary of MSRP, MVRP, and gPTP configuration and status on the
switch.
Advanced Features
312
Advanced Feature Commands
Example
#show avb
gPTP status
gPTP enabled ports
: Enabled
: *17d *19d
MSRP status
MSRP enabled ports
: Enabled
: !3 *17ab *19a
MVRP status
MVRP enabled ports
: Enabled
: *17 *19
Flags:
(*)
(a)
(d)
(p)
Active, (!) Administratively disabled,
SR Class A allowed, (b) SR Class B allowed,
Disabled gPTP port role, (m) Master gPTP port role,
Passive gPTP port role, (s) Slave gPTP port role.
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show bfd counters
show bfd counters
Description
Displays the readings of the global BFD counters.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to display global BFD counters.
To clear the counters, use the clear counters bfd command.
Advanced Features
313
Advanced Feature Commands
Example
The following command displays BFD global counters:
show bfd counters
Following is sample output from this command:
Valid Tx Pkt
Rx Invalid TTL
Interface Not found
Rx Invalid Length Pkt
Rx Invalid Demand Mode
Rx Invalid My Discriminator
Rx Invalid Auth Length
Auth Type Fails
Tx Fails
:
:
:
:
:
:
:
:
:
177
0
0
0
0
0
0
0
0
Valid Rx Pkt
Rx Invalid UDP SrcPort
Rx Invalid Version
Rx Invalid Multiplier
Rx Poll & Final set
Rx Invalid Your Discriminator
Rx session Not Found
Authentication Fails
Rx Discarded Pkt
:
:
:
:
:
:
:
:
:
177
0
0
0
0
0
6
0
0
Note
The Rx session Not Found counter is incremented when the BFD session corresponding to
the received BFD packet is not found. The Rx Discarded Pkt counter is incremented when the
neighbor state indicated in the BFD packet is not one of the expected/allowed states.
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
show bfd session client
show bfd session client [mpls | ospf {ipv4 | ipv6} | static {ipv4 | ipv6}] {vr
[vrname | all]}
Description
Displays the BFD session information for a specified client.
Syntax Description
mpls
Specifies an MPLS client.
ospf
OSPF Protocol.
ipv4
Displays sessions requested by IPv4 version client, e.g. OSPFv2 (Default).
ipv6
Displays sessions requested by IPv6 version client, e.g. OSPFv3.
Advanced Features
314
Advanced Feature Commands
static
Specifies a static route.
vrname
Specifies the name of the virtual router.
Default
IPv4.
Usage Guidelines
Use this command to display session information for a specified client.
Example
The following command displays the BFD sessions for an MPLS client on all VRs:
show bfd session client mpls vr all
Following is sample output from this command:
Neighbor
Interface
Detection
Status
---------------------------10.10.10.2
vlan10
3000
Up
===============================================
NOTE: All timers in milliseconds.
History
This command was first available in ExtremeXOS 12.4.
Support for BFD protected static route was added in ExtremeXOS 12.5.3.
The ospf keyword was added in ExtremeXOS 15.3.2.
Platform Availability
This command is available on all platforms.
show bfd session counters vr all
show bfd session {ipv4 | ipv6} {ipaddress} counters {vr [vrname | all]}
Syntax Description
ipv4
Displays all IPv4 sessions.
ipv6
Displays all IPv6 sessions.
ipaddress
Displays sessions in specified VR.
Advanced Features
315
Advanced Feature Commands
Default
Displays all IPv4 sessions counters by default if IPv4 or IPv6 is not specified.
Usage Guidelines
Use this command to display BFD session counters.
To clear the counters, use the clear counters bfd command.
Example
The following command displays the session counters:
show bfd session counters vr all
Following is sample output from this command:
Neighbor : 10.10.10.1
Valid Rx Pkt
:
Total Tx Pkt
:
Auth Type Fails
:
Authentication Fails :
Discarded Pkt
:
Interface : vlan10Vr-Name :
bfd_vr10
87
87
0
0
0
History
This command was first available in ExtremeXOS 12.4.
IPv6 version of this command was added in ExtremeXOS 15.3.2.
Platform Availability
This command is available on all platforms.
show bfd session detail vr all
show bfd session {ipv4 | ipv6} {ipaddress } detail {vr [vrname | all]}
Description
Displays detailed information about a BFD session.
Syntax Description
ipv4
Displays all IPv4 sessions.
ipv6
Displays all IPv6 sessions.
Advanced Features
316
Advanced Feature Commands
ipaddress
Displays sessions in specified VR.
vrname
Displays sessions in specified VR.
Default
Displays all IPv4 sessions by default if ipv4 or ipv6 is not specified.
Usage Guidelines
Use this command to display BFD session information in detail.
Example
The following command displays the BFD session information in detail:
show bfd session detail vr all
Following is sample output from this command:
# show bfd session detail vr all
Neighbor
: 10.10.10.1
Local
: 10.10.10.2
Vr-Name
: bfd_vr10
Interface
: vlan10
Session Type
: Single Hop
State
: Up
Detect Time
: 3000 mc
Age
: 250 ms
Discriminator (local/remote)
: 1 / 1
Demand Mode (local/remote)
: 0 / 0
Poll (local/remote)
: 0 / 0
Tx Interval (local/remote)
: 1000 / 1000 ms
Rx Interval (local/remote)
: 1000 / 1000 ms
oper Tx Interval
: 1000 ms
oper Rx Interval
: 1000 ms
Multiplier (local/remote)
: 3 / 3
Local Diag
: 0 (No Diagnostic)
Remote Diag
: 0 (No Diagnostic)
Authentication
: None
Clients
: MPLS,
Uptime
: 00 days 00 hours 00 minutes 41 seconds
Up Count
: 1
Last Valid Packet Rx
: 00:51:49.300000
Last Packet Tx
: 00:51:48.820000
The following command displays a specified IPv6 BFD session in detail:
# show bfd session fe80::204:96ff:fe1f:a800%v2 detail
Neighbor
: fe80::204:96ff:fe1f:a800
Local
: fe80::204:96ff:fe27:2c6a
VR-Name
: VR-Default
Interface
Session Type
: Single Hop
State
Detect Time
: 60000 ms
Age
Discriminator (local/remote)
: 1 / 1
Demand Mode (local/remote)
: Off / Off
Poll (local/remote)
: Off / Off
Advanced Features
: v2
: Up
: 460 ms
317
Advanced Feature Commands
Tx Interval (local/remote)
Rx Interval (local/remote)
Oper Tx Interval
Oper Rx Interval
Multiplier (local/remote)
Local Diag
Remote Diag
Authentication
Clients
Uptime
Up Count
Last Valid Packet Rx
Last Packet Tx
:
:
:
:
:
:
:
:
:
:
:
:
:
20000 / 1000 ms
20000 / 1000 ms
20000 ms
20000 ms
3 / 3
0 (No Diagnostic)
0 (No Diagnostic)
None
OSPFv3
00 days 01 hours 35 minutes 43 seconds
9
12:27:36.464105
12:27:19.34236
History
This command was first available in ExtremeXOS 12.4.
IPv6 version was added in ExtremeXOS 15.3.2.
Platform Availability
This command is available on all platforms.
show bfd session vr all
show bfd session {ipv4 | ipv6} {ipaddress } { vr [vrname |all ] }
Description
Displays general information about a BFD session.
Syntax Description
ipv4
Displays all IPv4 sessions.
ipv6
Displays all IPv6 sessions.
ipaddress
Displays session that has specified address as destination address.
vrname
Displays sessions in specified VR.
Default
Displays all IPv4 sessions by default if ipv4 or ipv6 keyword is not specified.
Usage Guidelines
Use this command to display general information about a BFD session.
Advanced Features
318
Advanced Feature Commands
Example
The following command displays general information about the BFD session:
show bfd session vr all
Following is sample output from this command:
Neighbor
Interface
Clients Detection
=============================================
30.30.30.2
bfdVlan
----s
0
=============================================
Clients Flag: m - MPLS, o - OSPF, s - Static
NOTE: All timers in milliseconds.
Status
VR
Down
VR-Default
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
show bfd vlan counters
show bfd vlan {vlan_name} counters
Description
Displays BFD counters on a specified VLAN.
Syntax Description
vlan_name
Specifies the VLAN name.
Default
N/A.
Usage Guidelines
Use this command to display counter readings for a specified VLAN.
Advanced Features
319
Advanced Feature Commands
Example
The following command displays the counter readings for the VLAN vlan10:
show bfd vlan vlan10 counters
Following is sample output from this command:
VLAN
Valid Rx Pkt
Total Tx Pkt
Auth Type Fails
Authentication Fails
Discarded Pkt
Rx session Not Found
: vlan10
:
:
:
:
:
:
144
144
0
0
0
6
Note
The Discarded Pkt counter is incremented when the neighbor state indicated in the BFD
packet is not one of the expected/allowed states. The Rx session Not Found counter is
incremented when the BFD session corresponding to the received BFD packet is not found.
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
show bfd vlan
show bfd vlan {vlan_name}
Description
Displays the BFD settings for the specified VLAN.
Syntax Description
vlan_name
Specifies the VLAN name.
Default
N/A.
Advanced Features
320
Advanced Feature Commands
Usage Guidelines
Use this command to display the BFD settings on a specified VLAN.
Example
The following command displays the BFD settings for the VLAN vlan10:
show bfd vlan vlan10
Following is sample output from this command:
VLAN
BFD
Tx Interval
Rx Interval
Detection Multiplier
Authentication
:
:
:
:
:
:
vlan10
Enabled
1000
1000
3
None
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
show bfd
show bfd
Description
Displays information on existing BFD sessions.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to show the status of the current BFD sessions.
Advanced Features
321
Advanced Feature Commands
The following session states are displayed:
• Init—The state when BFD is establishing the session.
• Down—The state when BFD detects that the session is down.
• Admin Down—The state when the user disables BFD on that interface.
• Up—The state when the BFD session is established.
Example
The following command displays information on current BFD sessions:
show bfd
Following is sample output from this command:
Number of sessions
Sessions in Init State
Sessions in Down State
Sessions in Admin Down State
Sessions in Up State
:
:
:
:
:
2
0
0
1
1
SNMP Traps for Session Down
SNMP Traps for Session Up
SNMP Traps Batch Delay
: Enabled
: Enabled
: 1000 ms
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
show cfm detail
show cfm {domain_name {association_name {ports port_list} {[end-point [up |
down]]}}}} detail
Description
Displays the MEP CCM database.
Syntax Description
domain_name
Enter the name of the domain for which you want to display the MEP CCM
databases.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
Advanced Features
322
Advanced Feature Commands
port_list
Enter the ports in the domain/association for which you want to display the
CCM databases.
up
Enter this to display the CCM database on the UP MEP for the specified MA.
down
Enter this to display the CCM database on the DOWN MEP for the specified
MA.
Default
N/A.
Usage Guidelines
If you do not specify any parameters or variables, the system displays information on all CCM
databases on the switch.
This command displays the following items of the CCM database:
• The name of the domain and association
• Port number
• MP and type
• MAC address of remote end points
• MEP IDs
• Lifetime for CCM messages from each remote end point
• Actual age of CCM messages
Note
The TTL for the CCM messages from the MP you are working on is 3.5 times the
transmission interval.
Example
The following command displays the CCM databases on the switch:
show cfm detail
The following is sample output from this command:
# show cfm detail
Domain/
Port
MP
Remote End-Point
Remote End-Point MEP
Life
Flags
Association
MAC Address
IP Address
ID
time
Age
==============================================================================
=====
dnsname
10
1
UE
00:04:96:51:5f:15 0.0.0.0
300
3500
650
DMA
dom1
Advanced Features
323
Advanced Feature Commands
VSNLMEG1
11
0
11
0
35
0
1
SMA
1
SMI
15
SMA
15
SMI
DE
-------------
0.0.0.0
300
DE
-------------
0.0.0.0
400
DE
-------------
0.0.0.0
300
DE
------------0.0.0.0
400
35
0
dom1
short_ma_name 1
DE
------------0.0.0.0
300
11
0
SMA
1
DE
------------0.0.0.0
400
11
0
SMI
15
DE
------------0.0.0.0
300
3500 0
SMA
15
DE
------------0.0.0.0
400
3500 0
SMI
dom2
VSNLMEG1
1
UE
00:04:96:51:5f:15 0.0.0.0
300
3500
750
SUA
00:11:22:33:4
VSNLMEG1
1
UE
00:04:96:51:5f:15 0.0.0.0
300
3500
760
DMA
00:11:22:33:4
short_ma_name 1
UE
00:04:96:51:5f:15 10.10.10.2
300
3500
90
DMA
==============================================================================
=====
Maintenance Point: (UE) Up End-Point, (DE) Down End-Point
Flags: (S) Static Entry, (D) Dynamic Entry
CCM Destination MAC: (U) Unicast, (M) Multicast
Status: (A) Active, (I) Inactive
NOTE: The Domain and Association names are truncated to 13 characters,
Lifetime
and Age are in milliseconds.
==============================================================================
=====
Total Number of Dynamic Up RMEP
: 3
Total Number of Dynamic Down RMEP
: 0
Total Number of Active Static RMEP
: 5
Total Number of Inactive Static RMEP : 4
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
show cfm groups
show cfm groups {group_name}
Advanced Features
324
Advanced Feature Commands
Description
This command displays the details of specified or all groups. The information contains group name,
grop status, LMEP id, the physical port of the LMEP, RMEP ids, registered clients, domain and
association names.
Syntax Description
group_name
Group name, maximum of 31 characters.
Default
N/A.
Usage Guidelines
Use this command to display the details of specified or all groups. The information contains group
name, grop status, LMEP id, the physical port of the LMEP, RMEP ids, registered clients, domain and
association names.
Example
The following output shows the typical output of this command:
X480-48t.1 # sh cfm groups
Group : eapsCfmGrp1
Status : UP
Local MEP
: 11
port : 41
Remote MEPs
: 10
Client(s)
: eaps
Domain
: MD1
Association
: MD1v2
Group : eapsCfmGrp2
Status : UP
Local MEP
: 12
port : 31
Remote MEPs
: 13
Client(s)
: eaps
Domain
: MD1
Association
: MD1v2
The following example shows the output for ERPS with Y.1731 CCMs:
# show configuration cfm
#
# Module dot1ag configuration.
#
create cfm domain string "dom" md-level 5
configure cfm domain "dom" add association meg "VSNLMEG1" vlan "v1"
configure cfm domain "dom" association "VSNLMEG1" ports 1 add end-point down
100
configure cfm domain "dom" association "VSNLMEG1" ports 15 add end-point down
200
configure cfm domain "dom" association "VSNLMEG1" ports 1 end-point down add
Advanced Features
325
Advanced Feature Commands
group" erps-g1"
configure cfm domain "dom" association "VSNLMEG1" ports 15 end-point down add
group "erps-g2"
configure cfm group "erps-g1" add rmep 300
configure cfm group "erps-g2" add rmep 400
* X460-48t.2 #
* X460-48t.2 # show configuration "erps"
#
# Module erps configuration.
#
create erps erps_major_1
configure erps erps_major_1 add control vlan v1
configure erps erps_major_1 ring-port east 1
configure erps erps_major_1 ring-port west 15
configure erps erps_major_1 timer wait-to-restore 5000
configure erps erps_major_1 cfm port east add group erps-g1
configure erpserps_major_1 cfm port west add group erps-g2*
* X460-48t.3 #
* X460-48t.4 # show cfm detail
Domain/
Port
MP
Remote End-Point
Remote End-Point MEP
Life
Flags
Association
MAC Address
IP Address
ID
time
Age
==============================================================================
========
dom
VSNLMEG1
1
DE
------------0.0.0.0
300
3500
0
SMA
15
DE
------------0.0.0.0
400
3500
0
SMA
==============================================================================
========
Maintenance Point: (UE) Up End-Point, (DE) Down End-Point
Flags: (S) Static Entry, (D) Dynamic Entry
CCM Destination MAC: (U) Unicast, (M) Multicast
Status: (A) Active, (I) Inactive
NOTE: The Domain and Association names are truncated to 13 characters,
Lifetime
and Age are in milliseconds.
==============================================================================
========
Total Number
Total Number
Total Number
Total Number
* X460-48t.5
of Dynamic Up RMEP
of Dynamic Down RMEP
of Active Static RMEP
of Inactive Static RMEP
# show cfm groups
Group : erps-g1 Status
Local MEP
Remote MEPs
Client(s)
Domain
Association
Group : erps-g2 Status
Local MEP
Advanced Features
:
:
:
:
:
:
:
:
:
:
:
:
UP
100
port
300
erps
dom
VSNLMEG1
UP
200
port
0
0
2
0
: 1
: 15
326
Advanced Feature Commands
*
*
*
*
Remote MEPs
: 400
Client(s)
: erps
Domain
: dom
Association
: VSNLMEG1
X460-48t.8 #
X460-48t.8 # disable ports 1
X460-48t.9 #
X460-48t.9 # show cfm detail
Domain/
Port
MP
Remote End-Point
Remote End-Point
MEP
Life
Flags
Association
MAC Address
IP Address
ID
time
Age
==============================================================================
========
dom
VSNLMEG1
1
DE
------------0.0.0.0
300
3500
0
SMI
15
DE
------------0.0.0.0
400
3500
0
SMA
==============================================================================
========
Maintenance Point: (UE) Up End-Point, (DE) Down End-Point
Flags: (S) Static Entry, (D) Dynamic Entry
CCM Destination MAC: (U) Unicast, (M)Multicast
Status: (A) Active, (I) Inactive
NOTE: The Domain and Association names are truncated to 13 characters,
Lifetime
and Age are in milliseconds.
==============================================================================
========
Total Number of Dynamic Up RMEP
Total Number of Dynamic Down RMEP
Total Number of Active Static RMEP
Total Number of Inactive Static RMEP
* X460-48t.10 # show cfm groups
:
:
:
:
0
0
1
1
Group : erps-g1 Status : DOWN
Local MEP
: 100
port
: 1
Remote MEPs
: 300
Client(s)
: erps
Domain
: dom
Association
: VSNLMEG1
Group : erps-g2 Status : UP
Local MEP
: 200
port
: 15
Remote MEPs
: 400
Client(s)
: erps
Domain
: dom
Association
: VSNLMEG1
* X460-48t.12 # enable ports 1
* X460-48t.13 #
* X460-48t.13 # show cfm detail
Domain/
Port
MP
Remote End-Point
Remote End-Point MEP
Life
Flags
Association
MAC Address
IP Address
ID
time
Age
==============================================================================
Advanced Features
327
Advanced Feature Commands
========
dom
VSNLMEG1
3500
0
1
DE
------------0.0.0.0
300
SMA
15
DE
------------0.0.0.0
400
3500
0
SMA
==============================================================================
========
Maintenance Point: (UE) Up End-Point, (DE) Down End-Point
Flags: (S) Static Entry, (D) Dynamic Entry
CCM Destination MAC: (U) Unicast, (M) Multicast
Status: (A) Active, (I) Inactive
NOTE: The Domain and Association names are truncated to 13 characters,
Lifetime
and Age are in milliseconds.
==============================================================================
========
Total Number of Dynamic Up RMEP
: 0
Total Number of Dynamic Down RMEP
: 0
Total Number of Active Static RMEP
: 2
Total Number of Inactive Static RMEP : 0
* X460-48t.14 # show cfm groups
Group : erps-g1 Status
Local MEP
Remote MEPs
Client(s)
Domain
Association
Group : erps-g2 Status
Local MEP
Remote MEPs
Client(s)
Domain
Association
:
:
:
:
:
:
:
:
:
:
:
:
UP
100
port
300
erps
dom
VSNLMEG1
UP
200
port
400
erps
dom
VSNLMEG1
: 1
: 15
History
This command was first available in ExtremeXOS 15.2.
Platform Availability
This command is available on all platforms.
show cfm segment frame-delay statistics
show cfm segment frame-delay statistics {segment-name} {mep mep_id}
Description
This command displays frame-delay information for the given CFM segment.
Advanced Features
328
Advanced Feature Commands
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
mep
Maintenance association End Point.
mep_id
MEP-ID. The range is 1-8191.
Default
N/A.
Usage Guidelines
Use this command to display the delay for the last received frame, the minimum, maximum and
average delay, and the delay variance during the current transmission. When the segment name is not
specified, only the segments which have valid statistics alone are displayed. When the segment name is
specified, that particular segment’s information, although not present, is displayed.
Example
The following command displays the frame delay statistics for the CFM segment:
show cfm segment frame-delay statistics
Following is sample output for this command:
-------------------------------------------------------------------------Segment Name
Mep
Recent Min
Max
Mean
Jitter
Errored
ID
Delay
Delay
Delay
Delay
Delay
Frames*
(ms)
(ms)
(ms)
(ms)
(ms)
-------------------------------------------------------------------------segment1
---0.000
0.000
0.000
0.000
0.000
0
segment2
100
0.000
0.000
0.000
0.000
0.000
0
200
0.000
0.000
0.000
0.000
0.000
0
segment3
100
0.000
0.000
0.000
0.000
0.000
0
300
0.000
0.000
0.000
0.000
0.000
0
-------------------------------------------------------------------------Flags: (*) % of frames beyond alarm threshold in the current measurement
window
Total Configured Segments
: 3
Total Active Segments
: 3
History
This command was first available in ExtremeXOS 12.3.
The mep id show output was added in ExtremeXOS 15.4.
Advanced Features
329
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
show cfm segment frame-delay
show cfm segment frame-delay {segment_name]}
Description
This command displays frame-delay information for the given CFM segment.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to display frame-delay information for the given CFM segment.
Example
Example output not yet available and will be provided in a future release.
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
show cfm segment frame-delay/frame-loss mep id
show cfm segment {{segment_name} | {frame-delay {segment_name}} | {frame-loss
{segment_name {mep mep_id}}}}
Description
This command is used to display the current status and configured values of a cfm segment.
Advanced Features
330
Advanced Feature Commands
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to display the current status and configured values of a cfm segment.
Note
In this command, the row “pending frames” will be displayed only for on-demand mode of
transmission.
A segment is considered as active if any of the MEPs in the segment is enabled for Frame Loss
measurement. Active Segment count will be incremented by one only even if there are multiple MEPs
enabled for Frame Loss. For example, assume that there are 3 segments created - seg1, seg2 and seg3.
Segment "seg1" is enabled for Frame Delay measurement. Segment "seg3" has 10 MEPs added with 4
enabled for Frame Loss measurement, the following are the valid counts. Switch wide "Total
Configured Segments" will be 3 and "Total Active Segments" will be 2. For Segments "seg1" and "seg2",
"Total Configured MEPs" and "Total Active MEPs" will be 0. For segment "seg3", "Total Configured
MEPs" will be 10 and "Total Active MEPs" will be 4.
By default, both the Frame Delay and Frame Loss sections are displayed for all the CFM segments. The
user has option to filter out based on Segment Name or Frame Delay / Frame Loss.
The behavior for each of the optional parameters is explained below:
• Show cfm segment: Displays frame-delay and frame-loss information for all the CFM segments.
• Show cfm segment segment_name: Displays frame-delay and frame-loss information for the given
CFM segment.
• Show cfm segment frame-delay: Displays frame-delay information for all the CFM segments.
• Show cfm segment frame-delay segment_name: Displays frame-delay information for the given
CFM segment.
• Show cfm segment frame-loss: Displays frame-loss information for all the CFM segments (and all
the MEPs under each of the segment).
• Show cfm segment frame-loss segment_name: Displays frame-loss information for the given CFM
segment (and all the MEPs under the given segment).
• Show cfm segment frame-loss segment_name mep mep_id: Displays frame-loss information for
the given CFM segment - MEP ID combination.
Example
Switch#show cfm segment sc-rtp
CFM Segment Name
Domain Name
Advanced Features
: sc-rtp
: pbt-d2
331
Advanced Feature Commands
Association
MD Level
Destination MAC
Frame Delay:
MEP ID
DMM Transmission
Transmission mode
Frames Transmitted
Frames Received
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames in Current Window
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
100
In Progress
Continuous
24
15
2 secs
10 msec
10 %
95 %
60
0
Fri Apr 17 01:29:45
Fri Apr 17 01:30:29
Fri Apr 17 01:30:03
Fri Apr 17 01:29:59
Set
9
MEP ID
DMM Transmission
Transmission mode
Frames Transmitted
Frames Received
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames in Current Window
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
200
In Progress
Continuous
24
15
2 secs
10 msec
10 %
95 %
60
0
Fri Apr 17 01:29:45
Fri Apr 17 01:30:29
Fri Apr 17 01:30:03
Fri Apr 17 01:29:59
Set
9
Frame Loss:
LMM Tx Interval
LMR Rx Timeout
SES Threshold
Consecutive Available Count
Measurement Window Size
Class of Service
Total Configured MEPs
Total Active MEPs
MEP ID
LMM Transmission
Transmission mode
Frames Transmitted
Frames Received
Availability Status
Unavailability Start Time
Unavailability End Time
Advanced Features
: pbt-d2-protecting
: 2
: 00:04:96:1e:14:70
:
:
:
:
:
:
:
:
2009
2009
2009
2009
2009
2009
2009
2009
: 2 secs
: 10 msec
: 30 %
: 10
: 60
: 0
: 2
: 2
100
In Progress
Continuous
24
15
Available/Unavailable
Fri Apr 17 01:10:45 2011
Fri Apr 17 01:20:45 2011
332
Advanced Feature Commands
Tx Start Time
: Fri Apr 17 01:10:45 2011
Min Near-End Frame Loss
: Fri Apr 17 01:29:45 2009
Max Near-End Frame Loss
: Fri Apr 17 01:39:45 2009
Min Far-End Frame Loss
: Fri Apr 17 01:49:45 2009
Max Far-End Frame Loss
: Fri Apr 17 01:59:45 2009
MEP ID
: 200
LMM Transmission
: In Progress
Transmission mode
: Continuous
Frames Transmitted
: 24
Frames Received
: 15
Availability Status
: Available/Unavailable
Unavailability Start Time
: Fri Apr 17 01:10:45 2011
Unavailability End Time
: Fri Apr 17 01:20:45 2011
Tx Start Time
: Fri Apr 17 01:10:45 2011
Min Near-End Frame Loss
: Fri Apr 17 01:29:45 2009
Max Near-End Frame Loss
: Fri Apr 17 01:39:45 2009
Min Far-End Frame Loss
: Fri Apr 17 01:49:45 2009
Max Far-End Frame Loss
: Fri Apr 17 01:59:45 2009
------------------------------------------------------Total Configured Segments
: 1
Total Active Segments
: 1
History
This command was first available in ExtremeXOS 12.3.
The mep id show output was added in ExtremeXOS 15.5.
Platform Availability
This command is available on all platforms.
show cfm segment frame-loss statistics
show cfm segment frame-loss statistics {segment-name}
Description
Displays shows frame-loss statistics.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Advanced Features
333
Advanced Feature Commands
Usage Guidelines
The below output is an example for displaying the frame-loss stats for the cfm segments. This
command shows the recent, minimum, maximum and average near-end and far-end frame loss ratios
during the current transmission. The stats for a particular segment will be preserved till the user
triggers the next LMM transmission or until it does a clear counter.
Example
The following command displays the frame loss statistics for the CFM segment:
LEFT.93 # show cfm segment frame-loss statistics
--------------------------------------------------------------Segment Name
MEP
Last
Last
Min
Max
Min
Max
Mean
Mean
ID
NE
FE
NE
NE
FE
FE
NE
FE
FLR
FLRFLRFLRFLRFLRFLR
NLR
---------------------------------------------------------------------seg1
111
10
10
10
10
10
10
10
seg1
222
10
10
10
10
10
10
10
seg2
333
10
10
10
10
10
10
10
---------------------------------------------------------------------Legend: FE - Far End, NE - Near End, FLR - Frame Loss Ratio
Window FE FLR
Last FE Tx
----------------- -----cs2
0.000000e+00
3
501936465
10
10
10
Last FE Rx
-------------
----------
----------
0.000000e+00
509467221
526672689
544907407
--------------------------------------------------------------Legend: FE - Far End, NE - Near End, FLR - Frame Loss Ratio
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on all platforms.
show cfm segment frame-loss
show cfm segment frame-loss {segment_name}
Advanced Features
334
Advanced Feature Commands
Description
This command displays frame-loss information for the given CFM segment.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to display frame-delay information for the given CFM segment.
Example
sho cfm seg frame-loss
CFM Segment Name
: cs2
Domain Name
: dom2
Association
: a2
MD Level
: 2
Destination MAC
: 00:04:96:52:a7:64
Frame Loss:
LMM Tx Interval
: 10 secs
SES Threshold
: 1.000000e-02
Consecutive Available Count : 4
Measurement Window Size
: 1200
Class of Service
: 6
Total Configured MEPs
: 1
Total Active MEPs
: 1
MEP ID
: 3
LMM Transmission
: In Progress
Transmission Mode
: Continuous
Frames Transmitted
: 483
Frames Received
: 483
Availability Status
: Available
Unavailability Start Time : None
Unavailability End Time
: None
Tx Start Time
: Mon Apr 23 12:28:28 2012
----------------------------------------------------------Total Configured Segments
: 1
Total Active Segments
: 1
E4G-200.31 #
E4G-200.31 #
History
This command was first available in ExtremeXOS 12.3.
Advanced Features
335
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
show cfm segment mep
show cfm segment {segment_name} {mep mep_id }
Description
This command displays frame-delay information for the given CFM segment – MEP ID combination.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to display frame-delay information for the given CFM segment – MEP ID
combination.
Example
Switch#showcfm segment sc-rtp
CFM Segment Name
: sc-rtp
Domain Name
: pbt-d2
Association
: pbt-d2-protectingMD
Level
: 2
Destination MAC
: 00:04:96:1e:14:70
Frame Delay:
MEP ID
: 100
__________________________________________________________
DMM Transmission
: In Progress
Transmission mode
: Continuous
Frames Transmitted
: 24
Frames Received
: 15
DMM Tx Interval
: 2 secs
DMR Rx Timeout
: 10 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 0
Tx Start Time
: Fri Apr 17 01:29:45 2009
Min Delay
: Fri Apr 17 01:30:29 2009
Max Delay
: Fri Apr 17 01:30:03 2009
Last Alarm Time
: Fri Apr 17 01:29:59 2009
Alarm State
: Set
Advanced Features
336
Advanced Feature Commands
Lost Frames in Current Window
MEP ID
DMM Transmission
Transmission mode
Frames Transmitted
Frames Received
DMM Tx Interval
DMR Rx Timeout
Alarm Threshold
Clear Threshold
Measurement Window Size
Class of Service
Tx Start Time
Min Delay
Max Delay
Last Alarm Time
Alarm State
Lost Frames in Current Window
Frame Loss:
LMM Tx Interval
LMR Rx Timeout
SES Threshold
Consecutive Available Count
Measurement Window Size
Class of Service
Total Configured MEPs
Total Active MEPs
: 9
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
200
In Progress
Continuous
24
15
2 secs
10 msec
10 %
95 %
60
0
Fri Apr 17 01:29:45
Fri Apr 17 01:30:29
Fri Apr 17 01:30:03
Fri Apr 17 01:29:59
Set
9
:
:
:
:
:
:
:
:
2 secs
10 msec
30 %
10
60
0
2
2
2009
2009
2009
2009
MEP ID
LMM Transmission
Transmission mode
Frames Transmitted
Frames Received
Availability Status
Unavailability Start Time
Unavailability End Time
Start Time
Near-End Frame Loss
Near-End Frame Loss
Far-End Frame Loss
Far-End Frame Loss
:
:
:
:
:
:
:
:
:
:
:
:
:
100
In Progress
Continuous
24
15
Available/Unavailable
Fri Apr 17 01:10:45 2011
Fri Apr 17 01:20:45 2011
Fri Apr 17 01:10:45 2011
Fri Apr 17 01:29:45 2009
Fri Apr 17 01:39:45 2009
Fri Apr 17 01:49:45 2009
Fri Apr 17 01:59:45 2009
MEP ID
LMM Transmission
Transmission mode
Frames Transmitted
Frames Received
Availability Status
Unavailability Start Time
Unavailability End Time
Tx Start Time
Min Near-End Frame Loss
Max Near-End Frame Loss
Min Far-End Frame Loss
Max Far-End Frame Loss
:
:
:
:
:
:
:
:
:
:
:
:
:
200
In Progress
Continuous
24
15
Available/Unavailable
Fri Apr 17 01:10:45 2011
Fri Apr 17 01:20:45 2011
Fri Apr 17 01:10:45 2011
Fri Apr 17 01:29:45 2009
Fri Apr 17 01:39:45 2009
Fri Apr 17 01:49:45 2009
Fri Apr 17 01:59:45 2009
Tx
Min
Max
Min
Max
-------------------------------------------------------
Advanced Features
337
Advanced Feature Commands
Total Configured Segments
Total Active Segments
: 1
: 1
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
This command is available on all platforms.
show cfm segment
show cfm segment {segment_name}
Description
Displays information for CFM segments.
Syntax Description
segment_name
An alpha numeric string identifying the segment name.
Default
N/A.
Usage Guidelines
Use this command to display information for the selected CFM segment.
If a segment name is not specified, the information for all of the segments that are currently configured
are displayed.
Example
The following command displays information for an active CFM segment that is configured to transmit
with a specific count:
show cfm segment s2
CFM Segment Name
Domain Name
Association
MD Level
Destination MAC
DMM Transmission
Advanced Features
:
:
:
:
:
:
s2
pbt-d2
pbt-d2-protecting
2
00:04:96:1e:14:70
In Progress
338
Advanced Feature Commands
Transmission mode
: Continuous
Frames Transmitted
: 2
Frames Received
: 2
DMM TX Interval
: 2secs
DMR RX Timeout
: 10 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 0
Tx Start Time
: Sun Apr 19 21:18:58 2009
Min Delay
: Sun Apr 19 21:18:58 2009
Max Delay
: Sun Apr 19 21:19:00 2009
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames in Current window
: 0
------------------------------------------------------Total Configured Segments
: 2
Total Active Segments
: 1
The following command displays information for a disabled segment:
BD-12804.1 # sh cfm seg s2
CFM Segment Name
: s2
Domain Name
: pbt-d2
Association
: pbt-d2-protecting
MD Level
: 2
Destination MAC
: 00:04:96:1e:14:70
DMM Transmission
: Disabled
Frames Transmitted
: 10
Frames Received
: 10
DMM TX Interval
: 2secs
DMR RX Timeout
: 10 msec
Alarm Threshold
: 10 %
Clear Threshold
: 95 %
Measurement Window Size
: 60
Class of Service
: 0
Tx Start Time
: Sat Apr 18 05:39:54 2000
Min Delay
: Sat Apr 18 05:40:12 2000
Max Delay
: Sat Apr 18 05:39:56 2000
Last Alarm Time
: None
Alarm State
: Not Set
Lost Frames in Current window
: 1
------------------------------------------------------Total Configured Segments
: 2
Total Active Segments
: 0
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
Advanced Features
339
Advanced Feature Commands
show cfm
show cfm { domain_name { association_name {{ports port_list {[intermediate-point
| [end-point [up|down]]]}}}
Description
Displays the current CFM configuration on the switch.
Syntax Description
domain_name
Enter the name of the domain you want to display.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Enter the ports in the domain and association you want to display.
up
Enter this to display the UP MEP for the specified MA.
down
Enter this to display the DOWN MEP for the specified MA.
intermediate-point
Enter this to display the MIPs for the specified MA.
Default
N/A.
Usage Guidelines
This command displays the following information:
• Domain names
• MA levels
• Association names
• VLAN names
• Transmit Interval
• UP MEPs
• MEPIDs
• MEP transmit intervals
• MEP State
• DOWN MEPs
• Intermediate points (MIPs)
• Total number of CFM ports on the switch
• Destination MAC Type
• VPLS-based MPs
• Sender ID information
• ISID Intermediate Point
See Supported Instances for CFM on page 72 for the number of domains, ports, MEPs, MIPs, and
associations supported on the switch.
Advanced Features
340
Advanced Feature Commands
Example
The show cfm command displays the current CFM configuration on the switch:
* switch # show cfm
Domain: "dnsname", MD Level: 2
Association: "10", Destination MAC Type: Multicast, VLAN "v1" with 2 cfm
ports
Transmit Interval: 1000 ms, Type : IEEE 802.1ag Maintenance
Association
port 1; Up End Point,
mepid: 100, transmit-interval: 1000 ms (from
association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: No
Last Faulting State Change
: Wed Jun 19 09:12:13
2013
MEP Error Defects
: None
Port Status
: Up
port 15; Intermediate Point ( Dynamic )
Association: "VSNLMEG1", Destination MAC Type: Multicast, VLAN "none"
with 0 cfm ports
Transmit Interval: 1000 ms, Type : ITU-T Y.1731 Maintenance Entity
Group
Association: "snmp_ma_name", Destination MAC Type: Multicast, VLAN
"none" with 0 cfm ports
Transmit Interval: 1000 ms, Type : IEEE 802.1ag Maintenance
Association
Domain: "dom1", MD Level: 5
Association: "VSNLMEG1", Destination MAC Type: Multicast, VLAN "v2"
with 2 cfm ports
Transmit Interval: 10 ms, Type : ITU-T Y.1731 Maintenance Entity
Group
port 1; Down End Point, mepid: 100, transmit-interval: 3.3 ms
(configured)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: Yes
Last Faulting State Change
: Wed Jun 19 09:08:12
2013
MEP Error Defects
: Remote
Port Status
: Up
port 15; Down End Point, mepid: 200, transmit-interval: 10 ms (from
association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: Yes
Last Faulting State Change
: Wed Jun 19 09:08:13
2013
MEP Error Defects
: Remote
Port Status
: Up
Association: "short_ma_name", Destination MAC Type: Multicast, VLAN
"v1" with 2 cfm ports
Transmit Interval: 1000 ms, Type : IEEE 802.1ag Maintenance
Association
port 1; Down End Point, mepid: 100, transmit-interval: 3.3 ms
(configured)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Advanced Features
341
Advanced Feature Commands
Disabled
Faulting State
Last Faulting State Change
: Yes
: Wed Jun 19 09:09:47
2013
MEP Error Defects
: Remote
Port Status
: Up
port 15; Down End Point, mepid: 200, transmit-interval: 1000 ms
(from association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: Yes
Last Faulting State Change
: Wed Jun 19 09:09:47
2013
MEP Error Defects
: RDI, Remote
Port Status
: Up
Domain: "dom2", MD Level: 6
Association: "VSNLMEG1", Destination MAC Type: Unicast, VLAN "v2"
with 2 cfm ports
Transmit Interval: 1000 ms, Type : ITU-T Y.1731 Maintenance Entity
Group
port 1; Up End Point,
mepid: 100, transmit-interval: 1000 ms
(from association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: No
Last Faulting State Change
: Wed Jun 19 09:39:14
2013
MEP Error Defects
: None
Port Status
: Up
port 15; Intermediate Point ( Dynamic )Domain:
"00:11:22:33:44:55.6666", MD Level: 7
Association: "VSNLMEG1", Destination MAC Type: Multicast, VLAN "v3"
with 2 cfm ports
Transmit Interval: 1000 ms, Type : ITU-T Y.1731 Maintenance Entity
Group
port 1; Up End Point,
mepid: 100, transmit-interval: 1000 ms
(from association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Disabled
Faulting State
: No
Last Faulting State Change
: Wed Jun 19 09:10:10
2013
MEP Error Defects
: None
Port Status
: Up
port 15; Intermediate Point ( Dynamic )
Association: "short_ma_name", Destination MAC Type: Multicast, VLAN
"v4" with 2 cfm ports
Transmit Interval: 1000 ms, Type : IEEE 802.1ag Maintenance
Association
port 1; Up End Point,
mepid: 100, transmit-interval: 1000 ms
(from association)
MEP State: Enabled, CCM Message: Enabled, Send SenderId TLV:
Enabled IPaddress:
10.10.10.1
Faulting State
: No
Last Faulting State Change
: Wed Jun 19 09:15:08
2013
MEP Error Defects
: None
Advanced Features
342
Advanced Feature Commands
Total
Total
Total
Total
Total
Total
Total
Total
Total
Port Status
: Up
port 15; Intermediate Point ( Dynamic )
Number of Domain
: 4
Number of Association
: 8
Number of Up MEP
: 4
Number of Down MEP
: 4
Number of MIP
: 4
Number of CFM port
: 12
Number of SW MEP
: 4
Number of HW MEP
: 4
Number of VPLS MIP(Static/Up): 0 / 0
==============================================================================
==
MEP Error Defect Types:
Remote : Not receiving CCMs from Remote MEP
Error : Erroneous CCM received
XCON
: Cross-connect CCM received
RDI
: Remote Defect Indication sent by some MEP
History
This command was first available in ExtremeXOS 11.4.
Transmit Interval and MEP State were added in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
show ethernet oam
show ethernet oam {ports [port_list} {detail}
Description
Displays Ethernet OAM information.
Syntax Description
port_list
Specifies the particular ports.
detail
Specifies that detailed information be displayed.
Default
N/A.
Advanced Features
343
Advanced Feature Commands
Usage Guidelines
Use this command to display basic Ethernet OAM information for specified ports on the switch. If you
do not specify the port(s), information for all ports is displayed.
Use the detail option for additional information.
When operating as a stack master, the Summit switch can process this command for ports on
supported platforms.
Example
The following command displays basic Ethernet OAM information for all ports:
show ethernet oam
Following is sample output from the command:
X450a-24x.13 # show ethernet oam
=================================================
Port Flags
Tx Cnt Rx Cnt Tx Err Rx Err
=================================================
1
E--u
2
2
0
0
2
---u
0
0
0
0
3
E-Ru
2
2
0
0
4
---u
0
0
0
0
5
EU-u
0
0
0
0
6
---u
0
0
0
0
7
---u
0
0
0
0
8
---u
0
0
0
0
9
---u
0
0
0
0
10
---u
0
0
0
0
11
---u
0
0
0
0
12
---u
0
0
0
0
13
---u
0
0
0
0
14
---u
0
0
0
0
15
---u
0
0
0
0
16
---u
0
0
0
0
17
---u
0
0
0
0
18
---u
0
0
0
0
19
---u
0
0
0
0
20
---u
0
0
0
0
21
---0
0
0
0
22
---0
0
0
0
23
---0
0
0
0
24
---0
0
0
0
25
---0
0
0
0
26
---0
0
0
0
---------------------------------------------------Flags
: (E) OAM Enabled, (U) OAM Operationally Up,
(R) Remote Port Fault Exists,
(u) Unidirectional OAM Supported
Advanced Features
344
Advanced Feature Commands
The following command displays detailed information for port 1:
show ethernet oam port 1 detail
Following is sample output from the command:
X450a-24x.41 # show ethernet oam port 1 detail
Port Number
: 1
Admin Status
: Enabled
Unidirectional OAM : Supported
Oper Status
: Disabled
Remote Fault
: Not Exists
Tx Pkts
: 2527
Rx Pkts
: 2550
Tx Error
: 0
Rx Error
: 0
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on the Summit X450a series switch only.
show fip snooping access-list
show fip snooping {vlan} vlan_name access-list {[fcf mac_addr | virtual-link
mac_addr | all]}
Description
The command lists all the FCoE ACLs meeting the criteria.
The list can be shortened by specifying the MAC of an FCF or the VN_Port MAC assigned to a virtual
link in the VLAN. The ACL with higher priority appears first.
By default, the command lists all the ACLs installed by the VLAN. The example below shows the output
of the command followed by the default ACLs installed when fip-snooping is enabled on the VLAN.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of the VLAN for which the access-list is shown.
fcf
List FCoE access-lists matching the FCoE forwarder’s MAC.
mac_addr
MAC address of the FCoE forwarder.
virtual-link
List FCoE access-lists matching FCoE virtual link’s MAC.
Advanced Features
345
Advanced Feature Commands
mac_addr
MAC address assigned to a VN-Port in the form xx:xx:xx:xx:xx:xx where xx is a
pair of hexadeximal digits.
all
All FCoE access-lists in the VLAN.
Default
N/A.
Usage Guidelines
The command lists all the FCoE ACLs meeting the criteria.
Example
BDXA.112 # show fip snooping vlan v3
VLAN
FIP Snooping
FCF Update
FC-MAP
:
:
:
:
v3
Enabled
Auto
0e:fc:00:00:00:00
Port
Location
------ --------------1:1
Perimeter
1:2
FCF-to-Enode
1:3
Enode-to-FCF
1:4
All
---------------------?
BDXA.113 # show fip snooping vlan v3 access-list
VLAN
: v3
entry f424c0TffffS0efc00000000 { if match all {
ethernet-type 0x0;
ethernet-destination-address 0e:fc:00:00:00:00;
} then {
deny ;
do-not-learn ;
}}
entry f424c1T8914D011018010002 { if match all {
ethernet-type 0x8914;
ethernet-destination-address 01:10:18:01:00:02;
} then {
permit ;
mirror-cpu ;
}}
entry f424c2T8914D011018010001 { if match all {
ethernet-type 0x8914;
ethernet-destination-address 01:10:18:01:00:01;
} then {
Advanced Features
346
Advanced Feature Commands
permit ;
mirror-cpu ;
}}
entry f424c3T8906 { if match all {
ethernet-type 0x8906;
} then {
deny ;
do-not-learn ;
}}
entry f424c3T8914 { if match all {
ethernet-type 0x8914;
} then {
deny ;
do-not-learn ;
}}
Total number of ACL : 5
BDXA.114 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
show fip snooping counters
show fip snooping {vlan} vlan_name counters
Description
This command shows the number of FIP frames snooped per type.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
Advanced Features
347
Advanced Feature Commands
vlan_name
Name of the VLAN for which the counters are shown.
counters
Number and types of FIP frames snooped on the VLAN.
Default
N/A.
Usage Guidelines
The command shows the number of FIP frames snooped per type.
Example
BDX8.62 # show fip snooping vlan v1 counters
VLAN : v1
FIP Frame type
Snooped
---------------------------------------------------- ---------Solicited Discovery Request
0
Unsolicited Discovery Request
1
Solicited Discovery Advertisement
1
Unsolicited Discovery Advertisement
12
Fabric Login (FLOGI)
1
FLOGI Accept
1
FLOGI Reject
0
NPortID Virtualization Fabric Discovery (NPIV FDISC)
5
NPIV FDISC Accept
5
NPIV FDISC Reject
0
Fabric Logout (FLOGO)
0
FLOGO Accept
0
FLOGO Reject
0
Exchange Link Parameters (ELP)
0
ELP Accept
0
ELP Reject
0
ENode Keep-alive
11
VN_Port Keep-alive
6
Clear Virtual-link
0
VLAN Request
0
VLAN Notify
0
Unknown FIP Frame Type
0
BDX8.63 #
History
This command was first available in ExtremeXOS 15.1.
Advanced Features
348
Advanced Feature Commands
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
show fip snooping enode
show fip snooping {vlan} vlan_name enode
Description
This command shows the list of ENodes that are learned from FIP protocol packets on the specified
VLAN.
The maximum FCoE size is in the snooped FIP discovery request from the ENode.
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of the VLAN for which the ENodes are shown.
enode
FCoE node. A Fiber Channel node that isable to transmit FCoE frames using
one or more ENode MACs.
Default
N/A.
Usage Guidelines
This command shows the list of Enodes that are learned from FIP protocol packets on the specified
VLAN.
Example
BDX8.92 # show fip snooping vlan v2 enode
VLAN : v2
Max
FCoE
ENode MAC
Port Location
Age Size
------------------- ----- --------------- ---- --------------00:00:00:A2:10:25
1:1
Perimeter
23
2098
00:00:01:C9:64:32
1:1
Perimeter
11
2098
Advanced Features
349
Advanced Feature Commands
00:00:05:A2:03:53
1:3
ENode to FCF
11
2098
00:00:00:9A:12:32
1:3
ENode to FCF
19
2098
Age
:The time in seconds since last FIP frame from the FCoE forwarder.
Total number of Enode MAC : 0
BDX8.93 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
show fip snooping fcf
show fip snooping {vlan} vlan_name fcf
Description
This command shows the list of FCFs in a VLAN on each member port. If the FCFs are added manually,
the age is set to 0.
Syntax Description
fip
FCoE Initializaton Protocol
snooping
Snooping on FIP frames
vlan_name
Name of the VLAN for which the FCFs are shown.
fcf
FCoE forwarder. A Fiber Channel switching element that is able to forward
FCoE frames.
Default
N/A.
Usage Guidelines
This command shows the list of FCFs in a VLAN on each member port. If the FCFs are added manually,
the age is set to 0.
Advanced Features
350
Advanced Feature Commands
Example
BDX8.74 # show fip snooping vlan v2 fcf
VLAN
: v2
FCF Update : Manual
FCF MAC
Port Location
Age
------------------- ----- --------------- ---e2:ee:00:00:00:01
1:2
FCF-to-Enode
0
e2:ee:00:00:00:02
1:2
FCF-to-Enode
0
e2:ee:00:00:00:03
1:4
All
0
e2:ee:00:00:00:04
1:4
All
0
---------------------------------------------Age
:The time in seconds since last FIP frame from the FCoE forwarder.
Total number of FCF MAC : 4
BDX8.75 #
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
• BlackDiamond X8
• BlackDiamond 8800 series BD8900-40G6X-c
• Summit X670
• Summit X770
show fip snooping virtual-link
show fip snooping {vlan} vlan_name virtual-link {[enode mac_addr | fcf mac_addr]}
Description
This command lists the virtual links established in the VLAN. The list can be narrowed down to per
ENode or per FCF where the ending point of the virtual link resides. The display shows all virtual links
on the VLAN (as limited by the specification of enode or fcf) regardless of whether they are using
SPMA or FPMA. Virtual links are differentiated within a VLAN by the VN_Port_ID (which is also
contained in the low-order three octets of an FPMA MAC address, but not that of an SPMA MAC
address).
Syntax Description
fip
FCoE Initialization Protocol.
snooping
Snooping FIP frames.
vlan_name
Name of the VLAN for which the FCFs are shown.
Advanced Features
351
Advanced Feature Commands
virtual-link
FCoE virtual link.
enode
Show virtual links related to the specified ENode only.
mac_addr
MAC of FCoE node originating the virtual link.
fcf
Show virtual links related to the specified FCF only.
mac_addr
MAC address of FCoE forwarder ending the virtual linkin the form
xx:xx:xx:xx:xx:xx where xx is a pair of hexadecimal digits.
Default
N/A.
Usage Guidelines
This command lists the virtual links established in the VLAN.
Example
BDX8.93 # show fip snooping v1 virtual-link
VLAN : v1
Port
ENode MAC
VN_Port MAC
VNPortId FCF MAC
----- ----------------- ----------------- -------- --------------------1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:01 01:00:01 aa:bb:cd:00:00:00
2856
1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:02 01:00:02 aa:bb:cd:00:00:00
3106
1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:03 01:00:03 aa:bb:cd:00:00:00
3106
1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:04 01:00:04 aa:bb:cd:00:00:00
3106
1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:05 01:00:05 aa:bb:cd:00:00:00
3106
1:1
aa:bb:cc:00:00:00 0e:fc:00:01:00:06 01:00:06 aa:bb:cd:00:00:00
3106
VN_Port : Virtual N_Port instantiated on successful completion of
FIP FLOGI or FIP NPIV FDISC Exchange
Age
: The time in seconds since last FIP frame from the VN_Port
Total number of Virtual Link : 6
BDX8.94 #
Age
History
This command was first available in ExtremeXOS 15.1.
Platform Availability
This command is available on the following platforms:
Advanced Features
352
Advanced Feature Commands
•
•
•
•
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
show fip snooping vlan
show fip snooping {vlan} vlan_name
Description
This command shows the FIP-snooping configuration status in the VLAN.
Syntax Description
vlan_name
Name of the VLAN for which the FIP Snooping configuration is shown.
Default
N/A.
Usage Guidelines
Use this command to show the FIP-snooping configuration status in the VLAN.
Example
BDX8.73 # show fip snooping vlan v2
VLAN
: v2
FIP Snooping : Disabled
FCF Update
: Manual
FC-MAP
: 0e:fc:00:00:00:00
Port
Location
------ --------------1:1
Perimeter
1:2
FCF-to-Enode
1:3
Enode-to-FCF
1:4
All
---------------------BDX8.74 #
History
This command was first available in ExtremeXOS 15.1.
Advanced Features
353
Advanced Feature Commands
Platform Availability
This command is available on the following platforms:
BlackDiamond X8
BlackDiamond 8800 series BD8900-40G6X-c
Summit X670
Summit X770
show lldp dcbx
show lldp {port [all | port_list]} dcbx {ieee|baseline} {detailed}
Description
Displays DCBX configuration and statistics information for one or all ports.
Syntax Description
all
Specifies all ports on the switch.
port_list
Specifies one or more ports or slots and ports.
ieee
Specifies IEEE 802.1Qaz information only.
baseline
Specifies Baseline v1.01 information only.
detailed
Shows information on the configured VLANs on the port.
Default
N/A.
Usage Guidelines
The summary display (without the detailed option) displays the status for each DCBX TLV on each port.
For each TLV, the status is reported as shown in the following table.
DISABLED
DCBX is disabled on the port. This port status appears only in the summary
display when DCBX is enabled for one version and disabled for the other. In
the detailed display, ports on which DCBX are disabled are not shown.
OK
This TLV has been received by the peer, and either the configuration matches,
or the peer is reporting that it is in willing mode and is not reporting an
explicit error.
UNKNOWN
This TLV has not been received by the peer since the port has been active.
EXPIRED
This TLV has been received by the peer, but the time to live has expired.
Advanced Features
354
Advanced Feature Commands
ERROR
Either a mismatch exists between the local and remote configuration and the
peer is not willing, or the peer is reporting an error.
MULTIPLE PEERS
More than one LLDP peer has been detected on the link.
When you specify a port or the detailed option, local TLV information includes the information that will
be contained in the next TLV that is sent, and if the configuration hasn't changed, this is the same
information that was sent in the last TLV. Peer TLV information displays the information from the last
TLV that has been received. For each TLV, statistics are reported as follows:
• Sent: Total number of TLVs sent since port has been operational.
• Received: Total number of TLVs received since port has been operational.
• Errors: Total number of mal-formed TLVs received since port has been operational.
You can clear the statistics using the clear counters command.
Table 12: IEEE 802.1Qaz DCBX TLVs on page 356 describes the IEEE 802.1Qaz DCBX TLVs that can be
displayed. Table 13: Baseline v1.01 DCBX TLVs on page 358 describes the Baseline v1.01 DCBX TLVs.
Advanced Features
355
Advanced Feature Commands
Table 12: IEEE 802.1Qaz DCBX TLVs
TLV/Description
Contents/Description
ETS TLV
Advertises the ETS configuration
of the local port and the
configuration recommended
to/by the peer for the specified
port, respectively.
Willing—Whether or not the device is willing to accept configuration from its
DCBX peer. Zero (0) means No, and one (1) means Yes. The Willing bit does
not apply to the ETS Recommendation TLV, and should always be zero.
CBS—Whether the device supports the credit-based shaper algorithm. Zero
(0) means No, and one (1) means Yes.
Max TCs— Maximum number of traffic classes that the node can support.
Priority Assgn—Priority Assignment Table. A priority group (PG) table
describing how 802.1p priorities are assigned to PGs. The table is laid out as
follows:
Priority-0 : Priority-1 : Priority-2 : Priority-3 : Priority-4 : Priority-5 : Priority-6 :
Priority-7
The value in the Priority-N position indicates the TC ID to which packets with
an 802.1p priority of N are mapped.
Note
For Extreme Networks products, a traffic class (TC) is
synonymous with a QoS Profile (QP), except that TCs are zerobased, and QPs are one-based, so TC 1 maps to QP 0.
TC Bwdth—TC Bandwidth Table. Indicates the percentage of bandwidth
allocated for each traffic class. The table is laid out as follows:
TC%-0 : TC%-1 : TC%-2 : TC%-3 : TC%-4 : TC%-5 : TC%-6 : TC%-7
The value in the TC%-N position indicates the percentage of the link
bandwidth allocated to TC N. The total of all positions must equal 100.
TSA—Transmission Selection Algorithm (TSA) Assignment Table. The table is
laid out as follows:
TC-0 : TC-1 : TC-2 : TC-3 : TC-4 : TC-5 : TC-6 : TC-7
The value in the TC-N position indicates the TSA used by TC N, which is one
of the following:
S - Strict priority (TSA 0)C - Credit-based shaper (TSA 1)E - Enhanced
Transmission Selection (TSA 2)V - Vendor-specific Transmission Selection
algorithm (TSA 255)
Note
TSA values 3 to 254 are reserved for future standardization.
Common Feature TLVs
Oper Vers—Operating version of the feature.
TLVs common to the Priority
Max Vers—Highest feature version supported by the system.
Group, PFC, and Application TLVs Enabled—Locally administered parameter that indicates whether the DCB
feature is enabled. Zero (0) means No, and one (1) means Yes.
Willing—Indicates whether the device is willing to accept configuration from
its DCBX peer. Zero (0) means No, and one (1) means Yes.
Error—Indicates whether an error has occurred during the configuration
exchange with the peer. Zero (0) means No, and one (1) means Yes.
Advanced Features
356
Advanced Feature Commands
Table 12: IEEE 802.1Qaz DCBX TLVs (continued)
TLV/Description
Contents/Description
Priority Group TLV
Advertises priority to priority
group mapping, priority group
bandwidth and the scheduling
algorithm.
PG IDs—Priority Allocation Table. A priority group (PG) table describing how
802.1p priorities are assigned to PGs. The table is laid out as follows:
Priority-0 : Priority-1 : Priority-2 : Priority-3 : Priority-4 : Priority-5 : Priority-6 :
Priority-7
The value in the Priority-N position indicates the PG ID to which packets with
an 802.1p priority of N are mapped. If the value is in the range of 0 to 7, this is
the actual PG. If the value is equal to 15, this priority is mapped to a non-ETS
group. In the case of Extreme Networks products, this would be a strict
priority group.
Note
For Extreme Networks products, a priority group (PG) is
synonymous with a QoS Profile (QP), except that PGs are zerobased, and QPs are one-based, so PG1 maps to QP 0.
PG%—Priority Group Allocation Table. Indicates the percentage of bandwidth
allocated for each priority group. The table is laid out as follows:
PG%-0 : PG%-1 : PG%-2 : PG%-3 : PG%-4 : PG%-5 : PG%-6 : PG%-7
The value in the PG%-N position indicates the percentage of the link
bandwidth allocated to PG N. The total of all positions must equal 100.
Num TCs—Maximum number of priority groups that the node can support.
PFC TLV
Describes the PFC configuration
for the given port.
Willing—Whether or not the device is willing to accept configuration from its
DCBX peer. Zero (0) means No, and one (1) means Yes.
MBC—MACsec Bypass Capability. If set to zero (0), the device is capable of
bypassing MACsec processing when MACsec is disabled. If set to one (1), the
sending station is not capable of bypassing MACsec processing when MACsec
is disabled.
PFC Cap—PFC Capability. The maximum number of classes on which the
device may simultaneously support PFC.
PFC Enable—List of priorities on which PFC is enabled.
Application TLV
Displays the priority the device
expects to be used for the
specified application.
Priority—The priority to be used for the given protocol.
Application—Specifies one of the following:
• FCoE
• FIP
• iSCSI
• EtherType: ethertype
• TCP/UDP Port: port number
• TCP Port: port number
• TCP Port: port number
Advanced Features
357
Advanced Feature Commands
Table 13: Baseline v1.01 DCBX TLVs
TLV/Description
Contents/Description
Control TLV
Contains general information
about the DCBX session.
Oper Vers—Operating version of the DCBX protocol.
Max Vers—Highest DCBX protocol version supported by the system.
Seq No—A value that changes each time an exchanged parameter in one or
more of the DCB feature TLVs changes.
Ack No—The SeqNo value from the most recent peer DCBX TLV that has
been handled. This value acknowledges to the peer that a specific SeqNo has
been received.
Common Feature TLVs
Oper Vers—Operating version of the feature.
TLVs common to the Priority
Max Vers—Highest feature version supported by the system.
Group, PFC, and Application TLVs Enabled—Locally administered parameter that indicates whether the DCB
feature is enabled. Zero (0) means No, and one (1) means Yes.
Willing—Indicates whether the device is willing to accept configuration from
its DCBX peer. Zero (0) means No, and one (1) means Yes.
Error—Indicates whether an error has occurred during the configuration
exchange with the peer. Zero (0) means No, and one (1) means Yes.
Priority Group TLV
Advertises priority to priority
group mapping, priority group
bandwidth and the scheduling
algorithm.
PG IDs—Priority Allocation Table. A priority group (PG) table describing how
802.1p priorities are assigned to PGs. The table is laid out as follows:
Priority-0 : Priority-1 : Priority-2 : Priority-3 : Priority-4 : Priority-5 : Priority-6 :
Priority-7
The value in the Priority-N position indicates the PG ID to which packets with
an 802.1p priority of N are mapped. If the value is in the range of 0 to 7, this is
the actual PG. If the value is equal to 15, this priority is mapped to a non-ETS
group. In the case of Extreme Networks products, this would be a strict
priority group.
Note
For Extreme Networks products, a priority group (PG) is
synonymous with a QoS Profile (QP), except that PGs are zerobased, and QPs are one-based, so PG1 maps to QP 0.
PG%—Priority Group Allocation Table. Indicates the percentage of bandwidth
allocated for each priority group. The table is laid out as follows:
PG%-0 : PG%-1 : PG%-2 : PG%-3 : PG%-4 : PG%-5 : PG%-6 : PG%-7
The value in the PG%-N position indicates the percentage of the link
bandwidth allocated to PG N. The total of all slots must equal 100.
Num TCs—Maximum number of priority groups that the node can support.
PFC TLV
Describes the PFC configuration
for the given port.
PFC Enable—List of priorities on which PFC is enabled.
Num TC PFCs—The maximum number of classes on which the device may
simultaneously support PFC.
Application TLV
Displays the priority the device
expects to be used for the
specified application.
Priority—The priority to be used for the given protocol.
Application—Specifies one of the following:
• FCoE
• FIP
• iSCSI
• EtherType: ethertype
• TCP/UDP Port: port number
Advanced Features
358
Advanced Feature Commands
Example
The following example displays the summary DCBX configuration and statistics:
# show lldp dcbx
==============================================================================
==
Baseline DCBX TLV Status:
IEEE DCBX TLV Status:
Port
Control PG
PFC
App
ETS-Conf ETS-Rec PFC
App
==============================================================================
==
1
OK
OK
OK
OK
OK
OK
OK
OK
2
OK
OK
OK
OK
OK
OK
OK
OK
3
OK
OK
OK
OK
OK
OK
OK
OK
4
OK
OK
OK
OK
OK
OK
OK
OK
5
UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN
UNKNOWN
9
UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN
UNKNOWN
10
UNKNOWN UNKNOWN UNKNOWN UNKNOWN DISABLED DISABLED DISABLED
DISABLED
16
DISABLED DISABLED DISABLED DISABLED UNKNOWN UNKNOWN UNKNOWN
UNKNOWN
23
UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN
UNKNOWN
24
UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN UNKNOWN
UNKNOWN
==============================================================================
==
Control - Control TLV
PG
- Priority Group TLV
PFC
- Priority-Based Flow Control TLV
App
- Application Configuration TLV
ETS-Conf - ETS Configuration TLV
ETS-Rec - ETS Recommendation TLV
The following example displays detailed IEEE 802.1Qaz DCBX configuration and statistics information
for port 1:
# show lldp ports 1 dcbx ieee
Port number : 1
IEEE 802.1Qaz DCBX Information:
-------------------------------ETS Configuration TLV: Sent: 5996, Received: 5997, Errors: 0, Status: OK
Local TLV : Willing: 0, CBS: 1, Max TCs: 8
Priority Assgn: 0:0:0:0:0:0:0:7, TC Bwdth: 33:0:0:33:34:0:0:0, TSA:
E:S:S:E:E:S:S:S
Peer TLV : Willing: 0, CBS: 1, Max TCs: 8
Priority Assgn: 0:0:0:0:0:0:0:7, TC Bwdth: 33:0:0:33:34:0:0:0, TSA:
E:S:S:E:E:S:S:S
ETS Recommendation TLV: Sent: 5996, Received: 5997, Errors: 0, Status: OK
Local TLV : Willing: 0, CBS: 0, Max TCs: 8
Priority Assgn: 0:0:0:0:0:0:0:7, TC Bwdth: 33:0:0:33:34:0:0:0, TSA:
E:S:S:E:E:S:S:S
Peer TLV : Willing: 0, CBS: 0, Max TCs: 8
Priority Assgn: 0:0:0:0:0:0:0:7, TC Bwdth: 33:0:0:33:34:0:0:0, TSA:
Advanced Features
359
Advanced Feature Commands
E:S:S:E:E:S:S:S
PFC TLV: Sent: 5996, Received: 5997, Errors:
Local TLV : Willing: 0, MBC: 0, Max PFCs: 8,
Peer TLV : Willing: 0, MBC: 0, Max PFCs: 8,
Application TLV: Sent: 5987, Received: 5988,
Local TLV : Priority: 4, iSCSI
Priority: 3, FCoE
Priority: 3, FIP
Peer TLV : Priority: 4, iSCSI
Priority: 3, FCoE
Priority: 3, FIP
0, Status: OK
PFC Enable: 3,4
PFC Enable: 3,4
Errors: 0, Status: OK
The following example displays detailed Baseline v1.01 DCBX configuration and statistics information
for port 1:
# show lldp ports 1 dcbx baseline
Port number : 1
Baseline v1.01 DCBX Information:
-------------------------------Control TLV: Sent: 5999, Received: 6000, Errors: 0, Status: OK
Local TLV : Oper Vers: 0, Max Vers: 0, Seq No: 17, Ack No: 17
Peer TLV : Oper Vers: 0, Max Vers: 0, Seq No: 17, Ack No: 17
Priority Group TLV: Sent: 5999, Received: 6000, Errors: 0, Status: OK
Local TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
PG IDs: 0:0:0:0:0:0:0:15, PG%: 33:0:0:33:34:0:0:0, Num TCs: 8
Peer TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
PG IDs: 0:0:0:0:0:0:0:15, PG%: 33:0:0:33:34:0:0:0, Num TCs: 8
PFC TLV: Sent: 5999, Received: 6000, Errors: 0, Status: OK
Local TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
Max PFCs: 8, PFC Enable: 3,4
Peer TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
Max PFCs: 8, PFC Enable: 3,4
App TLV: Sent: 5990, Received: 5991, Errors: 0, Status: OK
Local TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
Priority: 4, iSCSI
Priority: 3, FCoE
Priority: 3, FIP
Peer TLV : Oper Vers: 0, Max Vers: 0, Enabled: 1, Willing: 0 Error: 0
Priority: 4, iSCSI
Priority: 3, FCoE
Priority: 3, FIP
History
This command was first available in ExtremeXOS 12.6.
Platform Availability
This command is available on all platforms.
show mrp ports
show mrp ports {port_list}
Advanced Features
360
Advanced Feature Commands
Description
Shows the MRP timers configured on the given list of ports on the switch.
Syntax Description
mrp
Multiple Registration Protocol.
port_list
Ports on which MRP timers are configured or unconfigured.
Default
N/A.
Usage Guidelines
Use this command to view MRP timers configured on the given list of ports on the switch.
Example
# show mrp ports 1, 4, 5
----------------------------------------------------------------------------------------------------------------------------------Ports
Join Time (ms)
Leave Time (ms)
Leave All
Time (ms)
Periodoc (ms)
Extended
Refresh (ms)
----------------------------------------------------------------------------------------------------------------------------------1
200
600
10000
1000
10000
4
300
800
10000
1000
10000
5
200
600
10000
1000
10000
-----------------------------------------------------------------------------------------------------------------------------------
History
This command was first available in ExtremeXOS 15.3.
Output for periodic and extended refresh timers added in 15.3.2.
Platform Availability
This command is available on all platforms.
Advanced Features
361
Advanced Feature Commands
show msrp listeners
show msrp listeners {egress | ingress | ingress-and-egress} {port port_num}
{source-mac-addr source_mac_addr | stream-id stream_id}
Description
Shows MSRP listener information.
Syntax Description
msrp
Multiple Stream Registration Protocol.
listeners
Listener attributes.
egress
Display egress listeners only.
ingress
Display ingress listeners only (default).
ingress-and-egress
Display all listeners.
port_num
Filter based on ingress port number of the stream.
source-mac-addr
Filter based on source MAC address of a data stream.
stream-id
Filter based on stream ID of a data stream.
Default
N/A.
Usage Guidelines
Use this command to show MSRP listener information. The output can be filtered based on the stream
id, source MAC, or port number on which the listener is registered.
Example
X460-24t.1 # show msrp listeners
Stream Id
Port Dec
Dir
State
Stream Age
App Reg (days, hr:mm:ss)
----------------------- ----- ------- ------- --- --- ---------------00:50:c2:4e:d3:2d:00:00
19 Ready
Ingress VO
IN
0, 00:58:12
00:50:c2:4e:d3:2d:00:01
19 Ready
Ingress VO
IN
0, 00:58:12
00:50:c2:4e:d3:2d:00:02
19 Ready
Ingress VO
IN
0, 00:58:12
-----------------------------------------------------------------------------App
: Applicant State,
Dec
: MSRP Declaration
Types,
Dir
: Direction of MSRP attribute,
Reg
: Registrar State
MSRP Declaration Types:
Advanced Features
362
Advanced Feature Commands
AskFail : Listener Asking Failed,
Ready
: Listener Ready
Applicant
AA
:
AO
:
LA
:
QA
:
QP
:
VO
:
States:
Anxious active,
Anxious observer,
Leaving active,
Quiet active,
Quiet passive,
Very anxious observer,
Registrar States:
IN
: In - Registered,
MT
RdyFail : Listener Ready Failed,
AN
AP
LO
QO
VN
VP
:
:
:
:
:
:
Anxious new,
Anxious passive,
Leaving observer,
Quiet observer,
Very anxious new,
Very anxious passive
LV
: Leaving - Timing out,
: Empty - Not Registered
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show msrp ports bandwidth
show msrp ports {port_list} bandwidth
Description
Displays bandwidth information of an MSRP port.
Syntax Description
msrp
Multiple Stream Registration Protocol.
ports
Ports.
port_list
Port list separated by a comma or "-".
bandwidth
Bandwidth information per port per traffic-class.
Default
N/A.
Usage Guidelines
Use this command to display bandwidth information of an MSRP port.
Advanced Features
363
Advanced Feature Commands
Example
# show msrp ports bandwidth
Port
Port
Class
Delta
Maximum
Reserved Available
Speed
Effective
------ ------- ----- --------- --------- --------- --------5ab
0 M A
75.00%
0.00%
0.00%
0.00%
*21ab
Flags:
1000 M
B
A
0.00%
75.00%
0.00%
75.00%
0.00%
0.00%
0.00%
75.00%
B
0.00%
75.00%
0.00%
75.00%
(*) Active,
(a) SR Class A allowed,
(!) Administratively disabled,
(b) SR Class B allowed.
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show msrp ports counters
show msrp ports {port_list} counters {event | packet}
Description
Shows PDU or event counters per port.
Syntax Description
msrp
Multiple Stream Registration Protocol.
ports
Ports.
port_list
Port list separated by a comma or "-".
counters
MSRP packet and attribute event counters.
event
MSRP attribute event counters.
packet
MSRP packet counters (default).
Default
N/A.
Advanced Features
364
Advanced Feature Commands
Usage Guidelines
Use this command to display PDU or event counters per port. The counters count the received
attributes from talkers and listeners per attribute event, or the number of PDUs received. show msrp
counters by itself displays PDU counters.
Example
#show msrp ports 17 counters packet
Port
Streams
Reservations
Rx Pkt
----- ------------ ------------ ---------17
0
0
2
#show msrp ports 17 counters event
Port : 17
MRP Attribute Events
Rx
----------------------- ---------In
250
JoinIn
0
JoinMt
224
Lv
0
Mt
0
New
0
MSRP Declarations
----------------------Listener Asking Failed
Listener Ready
Listener Ready Failed
Talker Advertise
Talker Failed
---------0
56
0
8
0
Rx Error
---------0
Tx Pkt
---------2
Tx
---------56
0
386
0
152
0
---------0
8
0
56
3
----------------------------------------------------------------------------In
JoinIn
JoinMt
Lv
Mt
New
: Not declared, but registered
: Declared and Registered
: Declared, but not registered
: Previously registered, but now withdrawn
: Not declared, and not registered
: Newly declared, and possibly not previously
registered
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
Advanced Features
365
Advanced Feature Commands
show msrp ports
show msrp ports {port_list}{detail}
Description
Displays the MSRP configured port information.
Syntax Description
msrp
Multiple Stream Registration Protocol.
ports
Ports.
port_list
Port list separated by a comma or "-".
detail
Port information with more detail.
Default
N/A.
Usage Guidelines
Displays the MSRP configured port information. Specifying detail displays port information with more
detail.
Example
# show msrp ports
Port Enabled
State
Sr-Pvid
Oper
Port
Dplx
Jumbo
Speed
Jumbo
Cls
Bndry
Size
App/
Reg
----------
------5
2
IN
IN
2
*21
2
IN
Y
Y
------
------
----
Up/dbg
Up
----N
1000 M
Full
N
----9216
9216
---
-----
-------
A
N
QA/
B
N
QA/
A
N
QA/
B
N
QA/
IN
2
------------------------------------------------------------------------------Flags
: (*) Active,
(!) Administratively disabled
App
Cls
Oper
Reg
:
:
:
:
Advanced Features
Applicant State,
Bndry
Traffic Class,
Dplx
MSRP Operational State, Prop
Registrar State
: Boundary,
: Duplex,
: Propagated,
366
Advanced Feature Commands
MSRP Declaration Types:
Adv
: Talker Advertise,
Fail : Talker Fail,
Ready : Listener Ready
Applicant States:
AA
: Anxious active,
AO
: Anxious observer,
LA
: Leaving active,
QA
: Quiet active,
QP
: Quiet passive,
VO
: Very anxious observer,
Registrar States:
IN
: In - Registered,
MT
: Empty - Not Registered
AskFail
RdyFail
: Listener Asking Failed,
: Listener Ready Failed,
AN
AP
LO
QO
VN
VP
:
:
:
:
:
:
LV
: Leaving - Timing out,
Anxious new,
Anxious passive,
Leaving observer,
Quiet observer,
Very anxious new,
Very anxious passive
#show msrp ports
21 detail
Port Enabled
Oper
Port
Dplx Jumbo Jumbo Cls Bndry
State
Sr-Pvid
Speed
Size
App/Reg
---- ------------ ------ ---- ----- ----- --- ----------- ------*21
Y
Up
1000 M Full N
9216
A
N
QA/IN
2
B
N
QA/IN
2
Talkers:
Stream Id
Declaration
State
Rx
Prop
App Reg
----------------------- ------------- --- --00:50:c2:4e:d3:2d:00:00 Adv
Adv
VO
IN
00:50:c2:4e:d3:2d:00:01 Adv
Adv
VO
IN
Listeners:
Stream Id
Declaration
State
Rx
Prop
App Reg
----------------------- ------------- --- --00:50:c2:4e:d3:3d:00:00 Ready
Ready
VO
IN
00:50:c2:4e:d3:3d:00:01 Ready
Ready
VO
IN
------------------------------------------------------------------------------Flags
: (*) Active,
(!) Administratively disabled
App
: Applicant State,
Bndry
: Boundary
Cls
: Traffic Class,
Dplx
:
Duplex
Oper
: MSRP Operational State, Prop
: Propagated
Reg
: Registrar State
MSRP Declaration
Types:
Adv
:
Talker Advertise,
AskFail : Listener Asking Failed,
Fail : Talker
Fail,
RdyFail : Listener Ready Failed,
Ready :
Listener Ready
Applicant
States:
AA
:
Anxious active,
AN
: Anxious new,
AO
:
Anxious observer,
AP
: Anxious passive,
LA
:
Advanced Features
367
Advanced Feature Commands
Leaving active,
Quiet active,
Quiet passive,
anxious observer, VP
States:
IN
: In
Registered,
LV
Empty - Not Registered
LO
QO
VN
:
:
:
: Very
Leaving observer,
Quiet observer,
Very anxious new,
anxious passive
QA
:
QP
:
VO
: Very
Registrar
: Leaving - Timing out
MT
:
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show msrp streams
show msrp streams {detail | propagation} {port port_num} {source-mac-addr
source_mac_addr | stream-id stream_id}{destination-mac-addr destination_mac_addr}
Description
Shows the MSRP stream information collected from the talker's attributes.
Syntax Description
msrp
Multiple Stream Registration Protocol.
streams
Data streams advertising QoS specification using MSRP.
detail
Show stream information with more detail.
propagation
Show stream propagation through switch.
port
Filter based on ingress port number of the stream.
source-mac-addr
Filter based on source MAC address of a data stream.
stream-id
Filter based on stream ID of a data stream.
destination-mac-addr
Filter based on destination MAC address of a data stream.
Default
N/A.
Advanced Features
368
Advanced Feature Commands
Usage Guidelines
Use this command to show the MSRP stream information collected from the talker’s attributes. The
output can be filtered based on the stream id, source MAC, destination MAC, or port number on which
the stream is registered.
Example
# show msrp streams
Stream Id
Destination
Port Dec
VID Cls/Rn
BW
----------------------- ----------------- ---- ---- ---- -------------00:50:c2:4e:d3:2d:00:00 91:e0:f0:00:35:80
17 Adv
2 A/1
6.336
Mb
00:50:c2:4e:d3:2d:00:01 91:e0:f0:00:35:81
17 Adv
2 A/1
6.336
Mb
00:50:c2:4e:d3:2d:00:02 91:e0:f0:00:35:82
17 Adv
2 A/1
6.336
Mb
00:50:c2:4e:d3:2d:00:03 91:e0:f0:00:35:83
17 Adv
2 A/1
6.336
Mb
00:50:c2:4e:d3:2d:00:04 91:e0:f0:00:35:84
17 Adv
2 A/1
6.336
Mb
Total Streams: 5
-----------------------------------------------------------------------------BW
: Bandwidth,
Cls
: Traffic Class,
Dec : Prop Declaration Types,
Rn
: Rank
(!)
: Talker pruned or forbidden
MSRP Declaration Types:
Adv
: Talker Advertise,
AskFail : Listener Asking Failed,
Fail : Talker Fail,
RdyFail : Listener Ready Failed,
Ready : Listener Ready
#show msrp streams detail
Stream Id
Destination
----------------------- ------------------------00:50:c2:4e:d3:2d:00:00 91:e0:f0:00:0e:80
Mb
Accumulated Latency(nSec) :
Max Frame Size
:
Max Interval Frames
:
Frame Rate (fps)
:
00:50:c2:4e:d3:2d:00:01 91:e0:f0:00:0e:81
Mb
Failure Code
:
Port
---17
0
56
1
8000
17
Dec
----
VID
----
Cls/Rn
------
BW
Adv
2
A/1
6.336
Fail
2
A/1
6.336
(10) Out of MSRP resrc
Fail Bridge
:
08:00:e0:e0:e0:e0:e0:e0
Accumulated Latency(nSec) : 0
Max Frame Size
: 56
Max Interval Frames
: 1
Frame Rate (fps)
: 8000
Total Streams: 2
------------------------------------------------------------------------------
Advanced Features
369
Advanced Feature Commands
BW
Dec
(!)
: Bandwidth,
Cls
: Prop. Declaration Types,
Rn
: Talker pruned or forbidden
MSRP Declaration Types:
Adv
: Talker Advertise,
Fail : Talker Fail,
Ready : Listener Ready
: Traffic Class,
: Rank
AskFail
RdyFail
# show msrp streams propagation
Stream Id
Destination
: Listener Asking Failed,
: Listener Ready Failed,
Prop
VID
Cls/Rn
-----------------
----
Dec
----
----
------
91:e0:f0:00:35:80
17
------------------------------00:50:c2:4e:d3:2d:00:00
Mb
Port
Talker Propagation:
Ingress
Ingress
Adv
2
BW
A/1
6.336
Propagated
Propagated
Egress
DecType
Port
DecType
Ports
DecType
-------
-------
----------
----------
-------
Adv
-->
17
-->
Adv
-->
19
-->
Adv
21
-->
Adv
Listener Propagation:
Egress
Egress
Propagated
DecType
Port
DecType
-------
------
----------
RdyFail <--
17
<-<--
Ready
AskFail
Listener
Ingress
Ports
DecType
---------<-<--
-------
19 <-- Ready
21 <-- AskFail
Total Streams: 1
-----------------------------------------------------------------------------BW
: Bandwidth,
Cls
: Traffic Class,
Dec
: Prop. Declaration Types,
Rn
: Rank
(!)
: Talker pruned or forbidden
MSRP Declaration Types:
Adv
: Talker Advertise,
Fail : Talker Fail,
Ready : Listener Ready
AskFail
RdyFail
: Listener Asking Failed,
: Listener Ready Failed,
History
This command was first available in ExtremeXOS 15.3.
Advanced Features
370
Advanced Feature Commands
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show msrp talkers
show msrp talkers {egress | ingress | ingress-and-egress} {port port_num}{sourcemac-addr source_mac_addr | stream-id stream_id}
Description
Shows MSRP talker attributes.
Syntax Description
msrp
Multiple Stream Registration Protocol.
talkers
Talker attributes.
egress
Display egress talkers only (default).
ingress
Display ingress talkers only.
port
Filter based on ingress port number of the stream.
source-mac-addr
Filter based on source MAC address of a data stream.
stream-id
Filter based on stream ID of a data stream.
Default
N/A.
Usage Guidelines
Use this command to shows MSRP talker attributes. The output can be filtered based on the stream id,
source MAC, or port number on which the talker is registered.
Example
X460-24t.1 # show msrp talkers
Stream Id
Port Dec
-------------------------------------------00:50:c2:4e:d3:2d:00:00
port(8)
00:50:c2:4e:d3:2d:00:01
Advanced Features
-----
----
Dir
State
Failure Code
App Reg
--- ---
-------
19
Adv
Egress
QA
MT
-
21
Fail
Egress
QA
MT
AVB incapbl
19
Adv
Egress
QA
MT
-
371
Advanced Feature Commands
21
Fail
Egress
QA
MT
AVB incapbl port(8)
-----------------------------------------------------------------------------App
: Applicant State,
Dec
: MSRP Declaration Types,
Dir
: Direction of MSRP attribute,
Reg
: Registrar State
MSRP Declaration Types:
Adv
: Talker Advertise,
Fail
: Talker Fail
Applicant States:
AA
: Anxious active,
AO
: Anxious observer,
LA
: Leaving active,
QA
: Quiet active,
QP
: Quiet passive,
VO
: Very anxious observer,
AN
AP
LO
QO
VN
VP
:
:
:
:
:
:
LV
: Leaving - Timing out,
Registrar States:
IN
: In - Registered,
MT
: Empty - Not Registered
Anxious new,
Anxious passive,
Leaving observer,
Quiet observer,
Very anxious new,
Very anxious passive
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show msrp
show msrp
Description
Displays the MSRP configuration on the switch.
Syntax Description
msrp
Multiple Stream Registration Protocol.
Default
N/A.
Advanced Features
372
Advanced Feature Commands
Usage Guidelines
Use this command to display MSRP configuration on the switch.
Example
# show msrp
MSRP Status
MSRP Max Latency Frame Size
MSRP Max Fan-in Ports
: Enabled
: 1522
: No limit
MSRP First Value Change Recovery Time
MSRP Ignore Latency Changes
MSRP Talker VLAN Pruning
: 10000 (ms)
: On
: On
MSRP Enabled Ports
: *17ab
*19a
!5
Total MSRP streams
: 4
Total MSRP reservations
: 2
Flags:
(*) Active,
(!) Administratively disabled,
(a) SR Class A allowed, (b) SR Class B allowed.
History
This command was first available in ExtremeXOS 15.3.
The MSRP First Value Change Recovery Time, MSRP Ignore Latency Change, and MSRP Talker VLAN
Pruning example outputs were added in 15.3.2.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show mvrp ports counters
show mvrp ports {port_list} counters {event | packet}
Description
Shows the port MVRP statistics. The statistics for packet or event counters are displayed as per input.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
ports
Ports.
port_list
List of ports in the switch separated by a comma or "-".
counters
MVRP packet and attribute event counters.
event
MVRP attribute event counters.
packet
MVRP packet counters (default).
Advanced Features
373
Advanced Feature Commands
Default
Packet counters.
Usage Guidelines
This command is to show the port MVRP statistics. The statistics for packet or event counters will be
displayed as per input. The default is packet counters. The packet counters include Number of VLANs
registered on the port, Number of Failed Registrations, Number of MVRPDUs received, Number of
MVRPDUs sent, Number of erroneous MVRPDUs received, and the source address of the MVRP
message last received by the port. The event counters include the number of different events received/
transmitted.
Example
X460-24t.5 # show mvrp ports 9,11,13 counters
Port
VLANs
Failed
Rx Pkt Rx Error
Regs
Regs
Count
Count
--------------------- --------
packet
Tx Pkt
Count
--------
Last Source
Address
-----------------
9
2
0
0
0
64
00:00:00:00:00:00
11
2
0
806836
0
433754
00:22:97:00:41:e7
13
2
0
784176
0
404794
00:22:97:00:41:e8
-------------------------------------------------------------------Regs: Registrations
X460-24t.7 # show mvrp ports 9 counters event
Port : 17
MRP Attribute Events
Rx
Tx
----------------------- ---------- ---------In
250
56
JoinIn
0
0
JoinMt
224
386
LeaveAll
5
0
Lv
0
0
Mt
0
152
New
-------------------------------------------------------------------------In
: Not declared, but registered
JoinIn
: Declared and Registered
JoinMt
: Declared, but not registered
LeaveAll : All registrations will shortly be deregistered
Lv
: Previously registered, but now withdrawn
Mt
: Not declared, and not registered
New
: Newly declared, and possibly not previously registered
History
This command was first available in ExtremeXOS 15.3.
Advanced Features
374
Advanced Feature Commands
Platform Availability
This command is available on all platforms.
show mvrp tag
show mvrp tag vlan_tag {ports {port_list}}
Description
Shows the port specific applicant and registrar states and the configured control values for all MVRP
enabled ports.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
tag
The 802.1Q VLAN ID.
vlan_tag
VLAN ID ranging from 1 to 4094 (default is 2).
port_list
Port list separated by comma or "-".
Default
N/A.
Usage Guidelines
Use this command to show the port specific applicant and registrar states and the configured control
values for all MVRP enabled ports. The registrar control value is derived as follows:
• Normal = Dynamically ordered port.
• Fixed = Statically added port.
• Forbidden = VLAN is configured to be forbidden on the port.
Example
X460-24t.4 # show mvrp tag 2
Port
Applicant
State
----9
11
13
Applicant
Control
---------
Registrar
State
---------
VN
QA
QA
On
On
On
Applicant States:
AA
: Anxious active,
AO
: Anxious observer,
Advanced Features
Registrar
Control
--------MT
IN
IN
AN
AP
--------Normal
Normal
Normal
: Anxious new,
: Anxious passive,
375
Advanced Feature Commands
LA
QA
observer,
QP
new,
VO
: Leaving active,
: Quiet active,
LO
QO
: Leaving observer,
: Quiet
: Quiet passive,
VN
: Very anxious
: Very anxious observer, VP
Registrar States:
IN
: In – Registered,
LV
MT
: Empty - Not Registered
Applicant Control:
On
: Transmit On,
Off
Registrant Control:
Fixed : Statically added,
Normal : Dynamically added
: Very anxious passive
: Leaving - Timing out,
: Transmit Off
Forbidden : Forbidden VLAN,
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
show mvrp
show mvrp
Description
Shows MVRP settings.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
Default
N/A.
Usage Guidelines
Use this command to show the MVRP settings.
Advanced Features
376
Advanced Feature Commands
Example
X460-24t.3 # show mvrp
MVRP enabled
: Enabled
MVRP dynamic VLAN creation : Enabled
MVRP VLAN registration
: Forbidden
MVRP default STP domain
: s0
MVRP enabled ports
: 9
*11
*13
Flags: (*) Active, (!) Administratively disabled.
History
This command was first available in ExtremeXOS 15.3.
MRVP VLAN registration output was added in 15.3.2.
Platform Availability
This command is available on all platforms.
show network-clock gptp ports
show network-clock gptp ports [port_list | all] {counters}
Description
Displays gPTP port parameters and counters.
Syntax Description
port_list
Specifies one or more of the switch’s physical ports.
all
Specifies all of the switch’s physical ports.
Default
N/A.
Usage Guidelines
The command show network-clock gptp port displays the specified port’s gPTP parameters:
Physical port number
The switch’s number for this physical port.
gPTP port status
Indicates whether gPTP is enabled on this port.
Clock Identity
This switch’s gPTP Clock Identity.
gPTP Port Number
gPTP number for this physical port.
IEEE 802.1AS Capable
Indicates whether this switch and the neighboring systemdevice connected
via this port can interoperate via gPTP.
Advanced Features
377
Advanced Feature Commands
Port Role
The port’s gPTP role:
• Disabled (3)
• Master (6)
• Passive (7)
• Slave (9)
Announce Initial Interval
The initial announce interval on this port. The interval is represented as the log
base 2 of the interval in seconds; for example, 0 = 1 second.
Announce Current Interval
The current announce interval on this port. The interval is represented as the
log base 2 of the interval in seconds; for example, 1 = 2 seconds.
Announce Receipt Timeout
The number of announce intervals a slave port waits without receiving an
Announce message before it assumes the master port is no longer sending
Announce messages and the BMCA needs to be run.
Sync Initial Interval
The initial time-synchronization transmission interval on this port. The interval
is represented as the log base 2 of the interval in seconds; for example, -1 =
500 milliseconds.
Sync Current Interval
The current time-synchronization transmission sync interval on this port. The
interval is represented as the log base 2 of the interval in seconds; for
example, -2 = 250 milliseconds.
Sync Receipt Timeout
The number of time-synchronization transmission intervals a slave port waits
without receiving a Sync message before it assumes the master port is no
longer sending Sync messages and the BMCA needs to be run.
Sync Receipt Timeout Interval
Sync Receipt Timeout in time units.
Peer Delay Initial Interval
The initial Peer Delay Request interval on this port. The interval is represented
as the log base 2 of the interval in seconds; for example, 2 = 4 seconds.
Peer Delay Current Interval
The current Peer Delay Request interval on this port. The interval is
represented as the log base 2 of the interval in seconds; for example, 3 = 8
seconds.
Peer Delay Allowed Lost
Responses
The number of consecutive Peer Delay Request messages that the switch
must send on this port without receiving a valid response before it considers
the port not to be exchanging Peer Delay messages with its neighbor.
Measuring Propagation Delay
Indicates whether this port is measuring its link’s propagation delay.
Mean Propagation Delay
The link’s estimated one-way propagation delay. The peer delay protocol
measures the sum of the link’s propagation delays in each direction, and this
is that sum divided by two, which is accurate only if the link is symmetrical.
Mean Propagation Delay
Threshold
The propagation delay above which the switch considers this port unable to
run gPTP.
Propagation Delay Asymmetry
The configured time that the propagation delay from this switch to the
neighbor is less than the estimated one-way propagation delay between the
switch and its neighbor (which is also the time that the propagation delay
from the neighbor to this switch is greater than the estimate). This value is
negative if the propagation delay to the neighbor is greater than the estimate.
Let tIR be the propagation delay from this switch (initiator) to the neighbor
(responder), tRI be the propagation delay from the neighbor to this switch,
and meanPathDelay be the estimated one-way propagation delay. Then:
meanPathDelay = (tIR + tRI) / 2
tIR = meanPathDelay – asymmetry_time
tRI = meanPathDelay + asymmetry_time
Advanced Features
378
Advanced Feature Commands
Neighbor Rate Ratio
The estimated ratio of the frequency of the local clock in the neighboring
systemdevice connected via this port, to this switch’s local clock’s frequency.
The ratio is represented as the ratio minus 1, multipled by 241: (ratio – 1) * 241
PTP Version
The PTP version number used on this port. Always 2.
The command show network-clock gptp port counters displays the specified port’s gPTP
counters:
Physical port number
The switch's number for this physical port.
gPTP port status
Indicates whether gPTP is enabled on this port.
Announce
The number of Announce messages received and sent.
Sync
The number of Sync messages received and sent.
Follow Up
The number of Follow Up messages received and sent.
Peer Delay Request
The number of Peer Delay Request messages received and sent.
Peer Delay Response
The number of Peer Delay Response messages received and sent.
Peer Delay Response Followup
The number of Peer Delay Response Follow Up messages received and sent
gPTP packet discards
The number of received gPTP packets discarded or lost for one of the
following reasons (from 802.1AS-2011 14.7.8):
• Announce message from this switch
• Announce message with stepsRemoved >= 255
• Announce message with a Path Trace TLV that includes this switch
• Follow Up message not received following Sync message received
• Peer Delay Response message not received following Peer Delay Request
message sent
• Peer Delay Response Follow Up message not received following Peer
Delay Request message sent
Announce Receipt Timeout Count The number of Announce Receipt timeouts.
Sync Receipt Timeout Count
The number of Sync Receipt timeouts.
Peer Delay Allowed Lost
Responses Exceeded Count
The number of times the number of consecutive Peer Delay Request
messages sent without receiving a valid response exceeded the Peer Delay
Allowed Lost Responses.
Example
# show network-clock gptp ports 2
Physical port number
: 2
gPTP port status
: Enabled
Clock Identity
: 00:04:96:FF:FE:52:2C:BE
gPTP Port Number
: 2
IEEE 802.1AS Capable
: Yes
Port Role
: 9 (Slave)
Announce Initial Interval
: 0 (1 second)
Announce Current Interval
: 1 (2 seconds)
Announce Receipt Timeout
: 3
Sync Initial Interval
: -3 (125 milliseconds)
Sync Current Interval
: -2 (250 milliseconds)
Advanced Features
379
Advanced Feature Commands
Sync Receipt Timeout
Sync Receipt Timeout Interval
Peer Delay Initial Interval
Peer Delay Current Interval
Peer Delay Allowed Lost Responses
Measuring Propagation Delay
Mean Propagation Delay
Mean Propagation Delay Threshold
Propagation Delay Asymmetry
Neighbor Rate Ratio
PTP Version
:
:
:
:
:
:
:
:
:
:
:
3
750 milliseconds
2 (4 seconds)
4 (8 seconds)
3
Yes
1000 nanoseconds
10000 nanoseconds
0
200
2
# show network-clock gptp ports 3 counters
Physical port number
: 3
gPTP port status
: Enabled
----------------------------------------------------------Parameter
Receive
Transmit
----------------------------------------------------------Announce
1000
2000
Sync
1000
500
Follow Up
2000
2500
Peer Delay Request
3000
1000
Peer Delay Response
500
1500
Peer Delay Response Follow Up
200
1000
gPTP packet discards
2000
----------------------------------------------------------Announce Receipt Timeout Count
: 1000
Sync Receipt Timeout Count
: 500
Peer Delay Allowed Lost Responses Exceeded Count : 2000
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show network-clock gptp
show network-clock gptp {default-set | current-set | parent-set | timeproperties-set}
Description
Displays global gPTP configuration and data.
Advanced Features
380
Advanced Feature Commands
Syntax Description
default-set
Displays this switch’s native time capabilities.
current-set
Displays this switch’s state relative to the grandmaster system.
parent-set
Displays the upstream (i.e., toward the grandmaster) system’s parameters.
time-properties-set
Displays the grandmaster’s parameters.
Default
N/A.
Usage Guidelines
Use this command to display whether gPTP is enabled in the switch and the ports on which gPTP is
enabled.
Example
# show network-clock gptp
gPTP status:
Enabled
gPTP enabled ports: *1m,
Flags:
*2s,
*3p,
*4d,
!5d,
11d
12d
13d
14d
*15d
*16d
17d
18d
19d
20d
21d
22d
23d
24d
25d
26d
27d
28d
29d
30d
31d
32d
33d
34d
(*) Active, (!) Administratively disabled,
(d) Disabled gPTP port role, (m) Master gPTP port role,
(p) Passive gPTP port role, (s) Slave gPTP port role
# show network-clock gptp default-set
Local Clock Identity
:
Number of gPTP ports
:
Local Clock Class
:
Local Clock Accuracy
:
Local Offset Scaled Log Variance
:
GM Capable
:
Local Priority1
:
Local Priority2
:
Current UTC Offset
:
Leap 59
:
Leap 61
:
Time Traceable
:
Frequency Traceable
:
Time Source
:
00:04:96:FF:FE:52:2C:BE
24
255 (slave only clock)
254 (unknown)
65535
No
255
248
unknown
No
No
No
No
160 (Internal Oscillator)
# show network-clock gptp current-set
Steps Removed
: 1
Offset from GM
: 10 nanoseconds
Last GM Phase Change
: 548 nanoseconds
Last GM Frequency Change
: 100
GM Time Base Indicator
: 2
GM Change Count
: 1
Advanced Features
381
Advanced Feature Commands
Last GM Change Event
Last GM Frequency Change Event
Last GM Phase Change Event
: Tue Nov 22 03:32:07 2011
: Tue Nov 22 03:32:07 2011
: Tue Nov 22 03:32:07 2011
# show network-clock gptp parent-set
Parent Clock Identity
:
Parent port number
:
Cumulative Rate Ratio
:
GM Clock Identity
:
GM Clock Accuracy
:
GM Offset Scaled Log Variance
:
GM Priority1
:
GM Priority2
:
00:04:96:FF:FE:52:34:5F
21
10000
00:12:34:FF:FE:56:78:9A
32 (25 ns)
32767
245
248
# show network-clock gptp time-properties-set
Current UTC Offset
: 33 seconds
Leap 59
: No
Leap 61
: No
Time Traceable
: Yes
Frequency Traceable
: Yes
Time Source
: 32 (GPS)
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
show openflow controller
show openflow controller {primary | secondary}
Description
Shows the OpenFlow controller configuration and status on the switch.
Syntax Description
primary
Specifies the primary openflow controller.
secondary
Specifies the secondary openflow controller.
Default
None.
Advanced Features
382
Advanced Feature Commands
Usage Guidelines
None.
Example
The following example displays the current configuration for the primary controller:
show openflow controller
Controller
: Primary
Configured
: Yes
Datapath ID
: abcdef0123456789
Target
: tcp:10.1.1.1:6633
VR
: VR-Default
Mode
: out-of-band Active
Status
: ACTIVE
SSL
Probe(secs)
: 30
Uptime(secs)
Rate Limit
: 1000
Burst Size
Packets Sent : 9
Packets Received
Controller
: Secondary
Configured
: No
: Disabled
: 130
: 250
: 8
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
show openflow flows
show openflow flows {flow_name}
Description
Display the match conditions and actions of installed OpenFlow flows.
Syntax Description
flow_name
Specifies the flow name.
Default
None.
Advanced Features
383
Advanced Feature Commands
Usage Guidelines
Use this command to determine the number and details of OpenFlow flows installed on the switch by
an OpenFlow controller.
Example
The following example displays the current OpenFlow flows:
show openflow flows
Total number of flows: 1
Flow name Type Duration (secs)
Prio Packets
--------- ---- ------------------- ----- -------------------of_12345 FDB 9223372036854775807 65535 18446744073709551615
Match:
Input port:
2
Src MAC:
00:11:22:33:44:55
Dst MAC:
00:11:22:33:44:55
VLAN ID:
1234
VLAN priority:
255
Ethernet type:
0x8888
IP TOS:
0x1234
IP protocol:
0x1234
IP src address:
255.255.255.255
IP dst address:
255.255.255.255
Transport src port: 65535
Transport dst port: 65535
Actions: Output port: 3, Output port: 4, Drop
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
show openflow vlan
show openflow {vlan} vlan_name
Description
Shows the OpenFlow configuration state for the specified ports.
Syntax Description
vlan
Specifies that show output is restricted to a specified VLAN.
vlan_name
Specifies a named VLAN.
Advanced Features
384
Advanced Feature Commands
Default
None.
Usage Guidelines
If the VLAN name is specified, the output is restricted to that VLAN.
Example
The following command displays show output for all configured OpenFlow ports:
show openflow
OpenFlow is enabled.
Controller
: Primary
Status
: ACTIVE
Datapath ID : 000011112222
VR
: VR_Default
Mode
: out-of-band Active
Target
: tcp:10.1.1.2:6633
Uptime(secs) : 200s
Secondary controller: Not configured.
VLAN
------------------------------of1
Total number of VLAN(s): 1
VID
---20
Ports
----5
Flows
Active
Error
------ -----999999
999999
show openflow vlan of1
Primary controller: tcp:10.1.1.2:6633, out-of-band, Active, Uptime: 200s
Secondary controller: Disabled.
Flows
VLAN
VID Ports Active Error
------------------------------- ---- ----- ------ -----of1
20
5 999999 999999
Total number of VLAN(s): 1
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
show openflow
show openflow
Advanced Features
385
Advanced Feature Commands
Description
Shows whether OpenFlow is enabled or disabled globally on the switch.
Syntax Description
This command has no keywords or variables.
Default
None.
Usage Guidelines
None.
Example
The following example displays the current configuration for the primary controller:
show openflow
openflow is enabled!
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the BGP feature, see the Feature License Requirements document.
show snmp traps bfd
show snmp traps bfd
Description
This command displays session up/down trap reception for BFD.
Syntax Description
snmp
Configure SNMP specific settings.
traps
Configure SNMP Trap generation settings.
bfd
BFD-specific traps.
Advanced Features
386
Advanced Feature Commands
Default
Not applicable.
Usage Guidelines
Use this command to display SNMP trap reception for BFD session up/down.
Example
The following command displays SNMP Trap configuration for BFD:
#show snmp
SNMP Traps
SNMP Traps
SNMP Traps
traps bfd
for Session Down
for Session Up
Batch Delay
: Enabled
: Enabled
: 1000 ms
History
This command was first available in ExtremeXOS 15.5.
Platform Availability
This command is available on all platforms.
show trill distribution-tree
show trill distribution-tree { [ pruning [vlan] | rpf] {dtree_nickname} }
Description
This command displays the egress RBridge forwarding database for the TRILL network. The tabular
display output includes the egress RBridge nickname, System ID, hop count, next hop nickname, next
hop System ID, and port number associated with the next hop RBridge.
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links.
distribution-tree
TRILL Campus wide Distribution Tree.
pruning
Show pruning information.
vlan
Show pruning information related to VLAN destinations.
rpf
Show TRILL Reverse Path Forwarding table.
dtree_nickname
Nickname of dtree (in hex value)";type="hex_t";range="[1,65471].
Advanced Features
387
Advanced Feature Commands
Default
N/A.
Usage Guidelines
Use this command to display the egress RBridge forwarding database for the TRILL network. The
tabular display output includes the egress RBridge nickname, System ID, hop count, next hop
nickname, next hop System ID, and port number associated with the next hop RBridge.
Example
show trill distribution-tree
D-Tree D-Tree
Hop
Adj.
Adjacency
Name
System ID
Count Name
System ID
Port
-----------------------------------------------------0x0002 1111.1111.0001
1 0x0001 1111.1111.0000 1
0x0003 0004.966D.5D85 2
-----------------------------------------------------Hop Count: Number of D-Tree hops to the furthest node from local RBridge
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
show trill lsdb
show trill lsdb {lsp-id lsp-id | detail}
Description
This command displays the links state database associated with TRILL network. The display is
essentially the same as the output displayed by the show isis lsdb command.
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links.
lsdb
TRILL Campus wide Link State Database.
lsp-id
TRILL Link State PDU.
Advanced Features
388
Advanced Feature Commands
lsp_id
TRILL Link State PDU ID, In the format of xxxx.xxxx.xxxx.xxxx";type="string";range="[1,21].
detail
Detailed information.
Default
N/A.
Usage Guidelines
Use this command to display the links state database associated with TRILL network. The display is
essentially the same as the output displayed by the show isis lsdb command.
Example
#show trill lsdb
TRILL Link State Database
LSP ID
Seq Num
Checksum
Hold Time
OL Flag
--------------------------------------------------------------------0004.966D.5D85.00-00
0x00000002
0x0f69
1164
0
* 0004.966D.6F4E.00-00
0x00000002
0x07c7
1165
0
0204.966D.6528.00-00
0x00000002
0x47aa
1165
0
--------------------------------------------------------------------(*) - Self
OL - Overload
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
show trill neighbor
show trill neighbor {nickname nickname | system-id system | mac-address macaddress }
Description
This command displays network information related to TRILL RBridge neighbors. By default, the tabular
display output includes the neighbor RBridge MAC Address, System ID, Nickname, connected Port,
RBridge priority, and operational state.
Advanced Features
389
Advanced Feature Commands
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links.
neighbor
TRILL Campus wide neighbors.
nickname
Show TRILL neighbor associated with a particular nickname.
nickname
TRILL neighbor nickname between 1 and 0xFFBF in hex";
type="hex_t";range="[1,65471.]
system-id
Show TRILL neighbor associated with a particular system id.
system
TRILL neighbor system id. In the format of
xxxx.xxxx.xxxx";type="string";range="[1,14].
mac-address
Show TRILL neighbor associated with a particular MAC address.
mac-address
TRILL neighbor MAC address. In the format of xx:xx:xx:xx:xx:xx";type="mac_t.
Default
N/A.
Usage Guidelines
Use this command to display network information related to TRILL RBridge neighbors. By default, the
tabular display output includes the neighbor RBridge MAC Address, System ID, Nickname, connected
Port, RBridge priority, and operational state. The RBridge operational states are Detect, 2Way, Report,
and DR. The display out can be filtered by optionally specifying the keyword nickname, system-id, or
mac-address and the appropriate associated parameter. Specifying one of the optional filter keywords
displays additional information related to the specified object in detail format.
Example
#show trill neighbor
Neighbor
Hold DRB
Mac
System ID
Nickname Port Time Priority State
---------------------------------------------------------------------00:04:96:6d:5d:85 0004.966D.5D85 0x00c5
1:3
21
64 REPORT
02:04:96:6d:65:28 0204.966D.6528 0x941e
1:5
8
64 REPORT/DR
----------------------------------------------------------------------
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
Advanced Features
390
Advanced Feature Commands
show trill ports
.
show trill ports port_list {counters {no-refresh | detail}}
Description
This command displays operational TRILL information associated with the switch ports. By default, the
tabular display output includes the port number, port state, link state, DRB election priority, TRILL port
type, TRILL link type, link metric, and associated VLAN. Displayed port states include Disabled, Enabled,
Forwarding, and Inhibited.
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links.
ports
TRILL Ports.
port_list
Port list separated by a comma or (-).
counters
TRILL data packet counters.
no-refresh
Page by page display without auto-refresh.
detail
Detailed information.
Default
N/A.
Usage Guidelines
This command displays operational TRILL information associated with the switch ports. By default, the
tabular display output includes the port number, port state, link state, DRB election priority, TRILL port
type, TRILL link type, link metric, and associated VLAN. Displayed port states include Disabled, Enabled,
Forwarding, and Inhibited. The link states include Active, Ready, Port not Present, and Loopback. The
link types are Broadcast and P2P. The port types are Access, Trunk, and Hybrid. Optionally specifying
the port_number displays detailed TRILL information pertaining to the specified port. Optionally
specifying the keyword counters displays incoming and outgoing TRILL packet counts per port.
Counters associated with RPF check failures, hop count exceeded, and TRILL option drops are
maintained globally and are displayed using the show trill counters command.
Example
#show trill ports
Port Link DRB Election Port
Link
Designated
Port State State Priority
Type
Type
Metric
VLAN
----------------------------------------------------------------------
Advanced Features
391
Advanced Feature Commands
1:3 E F
A
64 Trunk
Broadcast
20000 * Default
1:5 E F
A
64 Trunk
Broadcast
20000 * Default
---------------------------------------------------------------------Port State: D-Disabled, E-Enabled
F-Forwarding, S-Suspended, d-Protocol Disabled
Link State: A-Active, R-Ready, NP-Port not present, L-Loopback
Metric:
(*)-Auto Metric
(!)-TRILL maintenance mode enabled
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
show trill rbridges
show trill rbridges
Description
This command displays status information related to RBridges in the TRILL network.
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links
rbridges
TRILL campus-wide RBridges
Default
N/A.
Usage Guidelines
Use this command to display status information related to RBridges in the TRILL network. The tabular
display output includes the RBridge’s nickname, system ID, DRB priority, root tree priority, and status.
RBridges highlighted with an asterisk indicate RBridge information associated with the local switch.
Example
#show trill rbridges
Nickname System ID
Count
Advanced Features
Nickname Root
Pri
Pri
Hop
Status
Next Hop Port
Metric
392
Advanced Feature Commands
-----------------------------------------------------------------------------# 0x0081 1111.1111.0000
64 32768 NotActive
0x5ac5 1111.1111.0001
64 32768 Active
0x5ac5 3
1
1
% 0x8000 1111.1111.0000
193 32768 Active
-----------------------------------------------------------------------------(#)-Automatically created default nickname for local RBridge
(%)-User created nickname for local RBridge
(*)-Static nexthop
(!)-TRILL maintenance mode enabled
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
show trill
show trill {detail}
Description
This command displays general configuration information related to the TRILL. This information
includes enabled status, nicknames, priorities, configured number of Dtrees to compute, support, and
use, timer configurations, System ID, Designated VLAN, Access VLAN IDs, MTU Size, MTU Probe status,
and Tree Pruning status.
Syntax Description
show
Show information.
trill
Transparent Interconnection of Lots of Links.
detail
Show detailed TRILL information.
Default
N/A.
Usage Guidelines
Use this command to display general configuration information related to the TRILL. This information
includes enabled status, nicknames, priorities, configured number of Dtrees to compute, support, and
use, timer configurations, System ID, Designated VLAN, Access VLAN IDs, MTU Size, MTU Probe status,
and Tree Pruning status.
Advanced Features
393
Advanced Feature Commands
Example
#show trill
TRILL
MAC)
Hello Interval
MTU Probe
Configured MTU
: Enabled
System ID
: 0004.966D.5D9D (Switch
: 10 sec
: Disabled
: 1470
Inhibition timer
: 30 sec
Negotiated MTU
: 1470
TRILL Maintenance Mode:
Disabled
Nickname:
0x0008 (Default_nickname)
Nickname-Priority: 64
32768
Desired Designated VLAN : Default
Network VLANs
: Default
Access Tags
:
#show trill detail
TRILL:
TRILL Maintenance Mode:
Root-Priority:
Enabled
Disabled
Configured Nickname
* 0x0002 ()
Nickname-Priority: 19
Root-Priority: 32768
Generated Nickname
0x00cd (Default_nickname)
Nickname-Priority: 64
Root-Priority:
32768
(*) Active
System ID:
Desired Designated VLAN:
DTrees To Compute:
DTrees To Support:
DTrees To Use:
Bypass Pseudonode:
Inhibit Time:
RPF Check:
maintenance Window:
0004.966D.6F4E (Switch MAC)
Default
1
1
1
Enabled
10 sec
Enabled
Enabled
VLANs
Network:
Access VLAN IDs:
Default
100
MTU
Configured MTU Size:
Negotiated MTU Size:
Probe:
Probe Fail Count:
1470 octets
1470 octets
Enabled
3
Tree Pruning
VLANs:
Enabled
TRILL Hello Timer
Hello Protocol:
Multiplier:
Interval:
Enabled
3
10 sec
Advanced Features
394
Advanced Feature Commands
TRILL LSP Timer
Generation Interval:
Refresh Interval:
Lifetime:
Transmit Interval:
Retransmit Interval:
CheckSum:
30 sec
90 sec
1200 sec
33 sec
5 sec
Enabled
TRILL SPF Timer
Minimum Backoff Delay:
Maximum Backoff Delay:
500 ms
50000 ms
TRILL CSNP Timer
Interval:
10 sec
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
show vlan dynamic-vlan
show vlan dynamic-vlan
Description
Displays the configuration related to dynamically created VLANs.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Advanced Features
395
Advanced Feature Commands
Example
The following command displays configuration related to dynamically created VLANs.
X460-48p.7 # sh vlan dynamic-vlan
Uplink Ports
: 12-15, 18-20
X460-48p.8 #
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
show vm-tracking local-vm
show vm-tracking local-vm {mac-address mac}
Description
Displays one or all of the VM entries in the local VM database.
Syntax Description
mac
Specifies the MAC address of a VM database entry that you want to display.
Default
N/A.
Usage Guidelines
If you do not enter a MAC address with this command, the command displays all entries in the local VM
database.
Example
The following command displays the local database VMs:
* Switch.52 # show vm-tracking local-vm
MAC Address
IP Address
Type
Value
--------------------------------------------------------------00:00:00:00:00:21
VM
VLAN Tag
100
Advanced Features
396
Advanced Feature Commands
VR Name
VR-Default
VPP
vpp1
--------------------------------------------------------------Number of Local VMs: 1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show vm-tracking network-vm
show vm-tracking network-vm
Description
Displays all of the VM entries in the network VM database.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the configuration for all entries in the network VM database:
* Switch.52 # show vm-tracking network-vm
MAC Address
IP Address
Type
Value
--------------------------------------------------------------00:00:00:00:00:11
192.168.100.200 VM
KVM-VM-#101
VPP
vpp300
00:01:02:03:04:06
192.168.100.201 VM
VM #200
VPP
vpp201
Number of Network VMs: 2
Advanced Features
397
Advanced Feature Commands
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show vm-tracking nms
show vm-tracking nms server {primary | secondary}
Description
Displays the RADIUS client configuration and operating statistics for one or both NMS servers.
Syntax Description
primary | secondary
Specifies whether you are displaying the primary or secondary NMS server
information.
Default
If you do not specify primary or secondary, the default action is to display both the primary and
secondary NMS server configurations.
Usage Guidelines
None.
Example
The following command displays the RADIUS client information for the primary and secondary NMS
servers:
show vm-tracking nms server
VM Tracking NMS (RADIUS): enabled
VM Tracking Radius server connect time out: 3 seconds
Primary VM Tracking NMS server:
Server name
:
IP address
: 10.127.5.221
Server IP Port: 1812
Client address: 10.127.10.173 (VR-Mgmt)
Shared secret : pmckmtpq
Access Requests
: 0
Access Accepts
Access Rejects
: 0
Access Challenges
Access Retransmits: 0
Client timeouts
Bad authenticators: 0
Unknown types
Round Trip Time
: 0
Advanced Features
:
:
:
:
0
0
0
0
398
Advanced Feature Commands
Secondary VM Tracking NMS server:
Server name
:
IP address
: 10.127.5.223
Server IP Port: 1812
Client address: 10.127.10.173 (VR-Mgmt)
Shared secret : rjgueogu
Access Requests
: 0
Access Accepts
Access Rejects
: 0
Access Challenges
Access Retransmits: 0
Client timeouts
Bad authenticators: 0
Unknown types
Round Trip Time
: 0
:
:
:
:
0
0
0
0
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show vm-tracking port
show vm-tracking port port_list
Description
Displays the XNV feature configuration for the specified port and information for all VMs authenticated
on the port.
Syntax Description
port_list
Specifies one or more ports or slots and ports.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the XNV configuration for port 1:20 and the authenticated VMs:
* (Private) Slot-1 Access3.14 # sh vm-tracking port 1:20
---------------------------------------------------------
Advanced Features
399
Advanced Feature Commands
VM Tracking Global Configuration
--------------------------------------------------------VM Tracking
: Enabled
VM Tracking authentication order
: nms vm-map local
VM Tracking nms reauth period
: 0 (Re-authentication disabled)
VM Tracking blackhole policy
: none
----------------------------------------------------------Port
: 1:20
VM Tracking
: Enabled
VM Tracking Dynamic VLAN
: Enabled
Flags
MAC
AP
IP Address
Type
Value
----------------------------------------------------------00:00:00:00:00:11 LBI
255.255.255.255 VM
VLAN Tag
100
VR Name
VR-Default
VPP
lvpp1
IEP
EEP
-----------------------------------------------------------Flags :
(A)uthenticated : L - Local, N - NMS, V - VMMAP
(P)olicy Applied : B - All Ingress and Egress, E - All Egress, I - All
Ingress
(C)ounter Installed : B - Both Ingress and Egress, E - Egress, I Ingress
All Ingress and Egress, E - All Egress, I - All Ingress
Type :
IEP – Ingress Error Policies
EEP – Egress Error Policies
Number of Network VMs Authenticated: 0
Number of Local VMs Authenticated : 1
Number of VMs Authenticated
: 1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show vm-tracking repository
show vm-tracking repository {primary | secondary}
Description
Displays the FTP file synchronization configuration for NVPP and VMMAP files.
Advanced Features
400
Advanced Feature Commands
Syntax Description
primary | secondary
Specifies whether you are displaying the primary or secondary FTP server
configuration.
Default
If you do not specify primary or secondary, the default action is to display both the primary and
secondary FTP server configurations.
Usage Guidelines
None.
Example
The following command displays the configuration for the primary and secondary FTP servers:
show vm-tracking repository
Primary VM-Map FTP server:
Server name:
IP address
: 10.100.1.200
VR Name
: VR-Mgmt
Refresh-interval: 600 seconds
Path Name
: /pub (default)
User Name
: anonymous (default)
Secondary vm-map FTP server: Unconfigured
Last sync
: 16:35:15
Last sync server
Last sync status : Successful
: Primary
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
show vm-tracking vpp
show vm-tracking vpp {vpp_name}
Description
Displays the configuration of one or all VPPs.
Advanced Features
401
Advanced Feature Commands
Syntax Description
vpp_name
Specifies the name of an existing local VPP.
Default
All.
Usage Guidelines
You can only specify local VPPs with this command. If you do not enter a VPP name with this
command, the command displays all local and network VPPs.
Example
The following command displays the configuration of all VPPs:
* (Private) Slot-1 Access3.14 # sh vm-tracking vpp
VPP Name
Type
Value
---------------------------------------------------------------------------------nvpp1
origin
network
counters
ingress-only
VLAN Tag
200
VR Name
VR-Default
ingress
ingLocal1.pol(1)
ingLocal2.pol(2)
egress
egrLocal1.pol(1)
egrLocal2.pol(2)
lvpp1
origin
counters
VLAN Tag
VR Name
ingress
egress
local
egress-only
100
VR-Default
ing1.pol(1)
egr1.pol(1)
egr2.pol(2)
Number of Local VPPs : 1
Number of Network VPPs: 1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
Advanced Features
402
Advanced Feature Commands
show vm-tracking
show vm-tracking
Description
Displays the XNV feature configuration and the authenticated VM information.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the XNV configuration and the authenticated VMs:
* Switch.51 # sh vm-tracking
----------------------------------------------------------VM Tracking Global Configuration
----------------------------------------------------------VM Tracking
: Enabled
VM Tracking authentication order: nms vm-map local
VM Tracking nms reauth period
: 0 (Re-authentication disabled)
VM Tracking blackhole policy
: none
----------------------------------------------------------Port
VM TRACKING
: 1:20
: ENABLED
Flags
MAC
APC
IP Address
Type
Value
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------00:00:00:00:00:11 LBI
00:00:00:00:00:12 ---
Advanced Features
255.255.255.255
VM
VPP
IEP
EEP
VM
VPP
lvpp1
403
Advanced Feature Commands
IEP
EEP
00:00:00:00:00:13 V--30.30.30.30
VM
VMware-VM#2
VPP
nvpp1
IEP
a1.pol
EEP
a2.pol
------------------------------------------------------------------------------------------------------Flags :
(A)uthenticated : L - Local, N - NMS, V - VMMAP
(P)olicy Applied : B - All Ingress and Egress, E - All Egress, I - All Ingress
(C)counter Installed: B - Both Ingress and Egress, E - Egress, I - Ingress
Type :
IEP - Ingress Error Policies
EEP - Egress Error Policies
Number of Network VMs Authenticated: 1
Number of Local VMs Authenticated : 1
Number of VMs Authenticated
: 2
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
traceroute mac port
traceroute mac mac {up-end-point} port port {domain} domain_name {association}
association_name {ttl ttl}
Description
Allows you to send out a Link Trace Message (LTM) for the specified MA from the MEP configured on
the port for the specified MAC address to the end of the MA.
Syntax Description
mac
Enter the unique system MAC address on the port configured as a MEP for the
specified MA. Enter this value in the format XX:XX:XX:XX:XX:XX.
up-end-point
Use this keyword to force the LTM to be send from an UP MEP if both a DOWN MEP
and an UP MEP are configured on the same port.
port
Enter the port number of the MEP from which you are issuing the LTM.
domain
Enter this keyword.
domain_name
IEEE 802.1ag or ITU-T Y.1731 association name.
Advanced Features
404
Advanced Feature Commands
association
Enter this keyword.
association_name
Enter the name of the association from which you are issuing the ping.
ttl
Enter this keyword.
ttl
Enter the upper limit of MIPs the LTM can pass prior to reaching its destination.
Default
TTL default value is 64.
Usage Guidelines
Use this command to send an LTM from the MEP on the port for the given MAC address. If no MEP is
configured on the port, the system returns an error message.
If both an UP and DOWN MEP are configured on the same port, the system uses the DOWN MEP. If you
want to use the UP MEP in this situation, enter the up-end-point keyword. After you issue the
command, the system prints out the route the LTM message took.
Each MIP along the route passes the LTM along only in the direction of the path and sends a packet
back to the originating MAC notifying that it passed the LTM. If the destination MAC type is configured
as unicast on the association to which this MEP belongs to, link trace replies will not be received from
any of the MIPs configured on the intermediate switches. If there is a MIP on the switch that originated
the trace route, the MIP sends a link trace reply.
Example
The following commands send an LTM:
1. A trace route invoked from a customer device CE1 to another customer device CE3 connected
through an MPLS cloud (MTU1 -' PE1 'PE3), where a VPLS MIP is configured to encode a system-name,
will have a response as follows:
(debug) Switch # traceroute mac 00:04:96:28:02:15 port 1 "extr_cfm5" "extr_ma"
Send out Link Trace Message(LTM), collecting responses [press Ctrl-C to
abort].
TTL CFM Source MAC
Reply
Reply Mac
Port ID
==============================================================================
=
63
00:04:96:1e:6d:40 I F-f- 00:04:96:1e:6d:40 o-- 1:8
62
00:04:96:1e:6d:40 E F-f- 00:04:96:1e:6d:40 o-- vp100:MTU-1
61
00:04:96:1e:16:10 I F-f- 00:04:96:1e:16:10 o-- vp100:PE-1
60
00:04:96:1e:16:10 E F-f- 00:04:96:1e:16:10 o-- vp100:PE-1
59
00:04:96:1e:14:90 I F-f- 00:04:96:1e:14:90 o-- vp100:PE-3
58
00:04:96:1e:14:90 E F-f- 00:04:96:1e:14:90 o-- 1:8
57
00:04:96:28:02:15 I -h-- 00:04:96:28:02:15 o-- 1
==============================================================================
=
Reply Flags: (I) Ingress, (E) Egress, (F) FwdYes, (h) RlyHit,(f) RlyFDB
Advanced Features
405
Advanced Feature Commands
Flags: (o) Ok, (d) Down, (b) Blocked
2. A trace route Invoked within an MPLS Cloud from MTU1 to PE3 (MTU1 -' PE1 'PE3), where a VPLS MIP
is configured to encode a private-ip, will have a response as follows:
(debug) Switch # traceroute mac 00:04:96:1e:14:90 port 1:8 extr_cfm2 "extr_ma"
Send out Link Trace Message(LTM), collecting responses [press Ctrl-C to
abort].
TTL CFM Source MAC
Reply
Reply Mac
Port ID
==============================================================================
=
63
00:04:96:1e:6d:40 E F-f- 00:04:96:1e:6d:40 o-- vp100:3.3.3.3
62
00:04:96:1e:16:10 I F-f- 00:04:96:1e:16:10 o-- vp100:1.1.1.1
61
00:04:96:1e:16:10 E F-f- 00:04:96:1e:16:10 o-- vp100:5.5.5.5
60
00:04:96:1e:14:90 I F-f- 00:04:96:1e:14:90 o-- vp100:3.3.3.3
59
00:04:96:1e:14:90 E -h-- 00:04:96:1e:14:90 o-- 1:8
==============================================================================
=
Reply Flags: (I) Ingress, (E) Egress, (F) FwdYes, (h) RlyHit,(f) RlyFDB
Flags: (o) Ok, (d) Down, (b) Blocked
If in PE1 alone, a VPLS MIP is configured to encode a system name, the response will be as follows:
(debug) Switch # traceroute mac 00:04:96:1e:14:90 port 1:8 extr_cfm2 "extr_ma"
Send out Link Trace Message(LTM), collecting responses [press Ctrl-C to
abort].
TTL CFM Source MAC
Reply
Reply Mac
Port ID
==============================================================================
=
63
00:04:96:1e:6d:40 E F-f- 00:04:96:1e:6d:40 o-- vp100:3.3.3.3
62
00:04:96:1e:16:10 I F-f- 00:04:96:1e:16:10 o-- vp100:PE1
61
00:04:96:1e:16:10 E F-f- 00:04:96:1e:16:10 o-- vp100:PE1
60
00:04:96:1e:14:90 I F-f- 00:04:96:1e:14:90 o-- vp100:3.3.3.3
59
00:04:96:1e:14:90 E -h-- 00:04:96:1e:14:90 o-- 1:8
==============================================================================
=
Reply Flags: (I) Ingress, (E) Egress, (F) FwdYes, (h) RlyHit,(f) RlyFDB
Flags: (o) Ok, (d) Down, (b) Blocked
History
This command was first available in ExtremeXOS 11.4.
Platform Availability
This command is available on all platforms.
traceroute trill
Short reference description.
Advanced Features
406
Advanced Feature Commands
traceroute trill rbridge_nickname
Description
This command traces the path TRILL takes through the network.
Syntax Description
trill
Transparent Interconnection of Lots of Links.
rbridge_nickname
TRILL campus-wide RBridge nickname in hex value;
type="hex_t";range="[1,65471]"
Default
N/A.
Usage Guidelines
Use this command to trace the path TRILL takes through the network.
Example
traceroute trill 0x3e
traceroute to 0x003e, 64 hops max
Hop
1
Nickname
0x001d
0x003e
Time
60 msec
358 msec
Nexthop
Nickname
0x003e2
traceroute to 0x003e completed
History
This command was first available in ExtremeXOS 15.4.
Platform Availability
TRILL is supported on the BD-X series and Summit X670 and X770 series of switches.
unconfigure avb
unconfigure avb
Advanced Features
407
Advanced Feature Commands
Description
This command is a macro command that can be used to unconfigure all AVB protocols globally on the
switch. It is equivalent to issuing the following four commands:
unconfigure mvrp
unconfigure msrp
unconfigure network-clock gptp
unconfigure mrp ports all
Syntax Description
avb
Audio Video Bridging
Default
N/A.
Usage Guidelines
Example
Use this command to unconfigure all AVB protocols globally on the switch.
unconfigure avb
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
unconfigure bfd vlan
unconfigure bfd vlan vlan_name
Description
Unconfigures BFD settings from a specified VLAN.
Advanced Features
408
Advanced Feature Commands
Syntax Description
vlan_name
Specifies the VLAN name.
Default
N/A.
Usage Guidelines
Use this command to unconfigure BFD settings from a specified VLAN.
Example
The following command unconfigures the BFD settings on the VLAN named vlan1:
unconfigure bfd vlan vlan1
History
This command was first available in ExtremeXOS 12.4.
Platform Availability
This command is available on all platforms.
unconfigure cfm domain association end-point transmit-interval
unconfigure cfm domain domain_name association association_name {ports port_list
end-point [up | down]} transmit-interval
Description
Unconfigures the CCM interval of the association or MEP to the default interval.
Syntax Description
domain_name
Specifies the domain associated with the MA.
association_name
IEEE 802.1ag or ITU-T Y.1731 association name.
port_list
Specifies the ports to unconfigure.
up
Enter this variable if you are changing the time interval for sending a CCM on
an UP MEP.
down
Enter this variable if you are changing the time interval for sending a CCM on
a DOWN MEP.
Advanced Features
409
Advanced Feature Commands
Default
1000 ms.
Usage Guidelines
Use this command to revert the CCM interval of either the association or the MEP back to the default
CCM interval.
Example
The following command changes the interval the UP MEP (previously configured on port 2:4) uses to
send CCM messages on the 350 association in the finance domain to the default of 1000 ms:
unconfigure cfm domain finance association 350 ports 2:4 end-point up
transmit-interval
History
This command was first available in ExtremeXOS 12.3.
Platform Availability
This command is available on all platforms.
unconfigure mrp ports timers
unconfigure mrp ports [port_list | all] {timers {refresh} {join} {leave} {leaveall} {periodic}}
Description
Unconfigure MRP timers, or only reset the MRP timer values to default if the timer keyword is
specified.
Syntax Description
mrp
Multiple Registration Protocol.
ports
Ports on which MRP timers are to be configured.
all
All ports.
timers
Multiple Registration Protocol timers.
refresh
Timer value to use in place of regular leave timer, only in cases when leave-all
is received or sent.
join
The time interval to delay sending MRP advertisements.
Advanced Features
410
Advanced Feature Commands
leave
The time interval to wait in the leaving state before transitioning to the empty
state.
leave-all
The time interval used to control the frequency of "leave all" messages.
periodic
The time interval between two periodic events.
Default
The default values for join, leave, leave-all, are 200, 600, and 10000, respectively. The default values for
join, leave, leave-all, periodic and extended-refresh timers are 200, 600, 10000, 1000, and 0
milliseconds, respectively.
Usage Guidelines
Use this command to unconfigure MRP timers, or only reset the MRP timer values to default if the
timer keyword is specified. If none of the timers are specified, this command resets all three timers to
the default values. The default values for the join, leave, and leave-all timers are 200, 600, and 10000
ms respectively.
Example
unconfigure mrp ports all
unconfigure mrp ports all timers
unconfigure mrp ports all timers join
History
This command was first available in ExtremeXOS 15.3.
The extended-refresh and periodic timer options were added in 15.3.2.
Platform Availability
This command is available on all platforms.
unconfigure msrp
unconfigure msrp {ports [port_list | all]}
Description
Disables MSRP and removes all configuration. If a list of ports is specified, MSRP is disabled and the
related configuration is removed only on the ports and the system-wide MSRP configuration stays
intact.
Advanced Features
411
Advanced Feature Commands
Syntax Description
msrp
Multiple Stream Registration Protocol.
port_list
List of ports in the switch.
all
All the ports in the switch.
Default
N/A.
Usage Guidelines
Use this command disable MSRP and remove all configuration. If a list of ports is specified, MSRP is
disabled and the related configuration is removed only on the ports and the system-wide MSRP
configuration stays intact.
Example
unconfigure msrp
unconfigure msrp ports all
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
unconfigure mvrp stpd
unconfigure mvrp stpd
Description
Resets the MVRP STP domain.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
stpd
The STP domain the VLAN is to be associated with. All ports of the domain
will be advertised when this VLAN is registered.
Advanced Features
412
Advanced Feature Commands
Default
s0.
Usage Guidelines
Use this command to reset the STP domain associated with a particular VLAN or all VLANs to default. If
a VLAN is specified, the specific VLAN will be associated to the default STP, which is configured using
the configure mvrp stpd stpd_name default command. If VLAN is not specified, all VLANs are
associated to STP domain s0.
Example
The following example illustrates the unconfigure mvrp stpd command:
unconfigure mvrp stpd
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
unconfigure mvrp tag
unconfigure mvrp tag vlan_tag
Description
Resets all MVRP settings for the given VLAN id. The STP domain, the registrar state machine settings,
applicant state machine settings for the given VLAN are reset to default values.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
vlan_tag
The 802.1Q VLAN ID.
Default
N/A.
Usage Guidelines
Use this command to reset all MVRP settings for the given VLAN id. The STP domain, the registrar state
machine settings, and the applicant state machine settings for the given VLAN are reset to default
Advanced Features
413
Advanced Feature Commands
values. All dynamically added ports of the VLAN are removed. If the VLAN was created dynamically, it
is removed. If VLAN is not specified, MVRP settings for all VLANs are reset and the dynamic VLAN
creation feature is reset to “enabled”.
Example
The following example shows unconfiguring an MVRP:
unconfigure mvrp tag 100
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
unconfigure mvrp
unconfigure mvrp
Description
Unconfigures MVRP on a switch and all MVRP port and bridge settings.
Syntax Description
mvrp
Multiple VLAN Registration Protocol.
Default
N/A.
Usage Guidelines
Use this command to unconfigure MVRP on a switch. This command unconfigures all MVRP port and
bridge settings.
Example
The following command unconfigures MVRP:
unconfigure mvrp
Advanced Features
414
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
unconfigure network-clock gptp ports
unconfigure network-clock gptp ports [port_list | all]
Description
Restores all configuration parameters on the specified ports to their default values. This command does
not disable gPTP on the ports.
Syntax Description
port_list
Specifies one or more of the switch's physical ports.
all
Specifies all of the switch's physical ports.
Default
N/A.
Usage Guidelines
Use this command to restore all configuration parameters on the specified ports to their default values.
Example
unconfigure network-clock gptp ports all
unconfigure network-clock gptp ports 1,2
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on Summit X430, X440, X460, and X670 switches if the AVB feature pack
license is installed on the switch.
Advanced Features
415
Advanced Feature Commands
unconfigure openflow controller
unconfigure openflow controller [primary | secondary]
Description
Unconfigures the OpenFlow controller(s).
Syntax Description
primary
Specifies the primary openflow controller.
secondary
Specifies the secondary openflow controller.
Default
N/A.
Usage Guidelines
None.
Example
The following exampleunconfigures the primary controller:
unconfigure openflow controller primary
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on platforms that support the appropriate license. For complete information
about software licensing, including how to obtain and upgrade your license and which licenses support
the Openflow feature, see the Feature License Requirements document.
unconfigure vm-tracking local-vm
unconfigure vm-tracking local-vm mac-address mac [name | ip-address | vpp | vlantag]
Advanced Features
416
Advanced Feature Commands
Description
Unconfigures the parameters associated with a local VM database entry to be used for VM MAC local
authentication.
Syntax Description
mac
Specifies the MAC address for the local VM database entry you want to
unconfigure.
name
Removes the name configured for the VM database entry.
ip-address
Removes the IP address configured for the VM database entry.
vpp
Removes the VPP configured for the VM database entry.
vlan-tag
Removes the VLAN tag configured for the VM database entry.
Default
N/A.
Usage Guidelines
None.
Example
The following command removes the IP address configuration for the VM entry specified by the MAC
address:
unconfigure vm-tracking local-vm mac-address 00:E0:2B:12:34:56 ip-address
History
This command was first available in ExtremeXOS 12.5.
The ingress-vpp and egress-vpp options were replaced with the vpp option in ExtremeXOS 12.6.
The VLAN-tag option was added in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
unconfigure vm-tracking nms
unconfigure vm-tracking nms {server [primary | secondary]}
Advanced Features
417
Advanced Feature Commands
Description
Removes the configuration for one or both NMS servers.
Syntax Description
primary | secondary
Specifies the whether you are unconfiguring the primary or secondary NMS.
Default
N/A.
Usage Guidelines
If you do not specify primary or secondary, this command removes the configuration for both NMS
servers.
Example
The following command removes the configuration for the secondary NMS server:
unconfigure vm-tracking nms server secondary
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
unconfigure vm-tracking repository
unconfigure vm-tracking repository {primary | secondary}
Description
Removes the configuration for FTP file synchronization for NVPP and VMMAP files.
Syntax Description
primary | secondary
Advanced Features
Specifies the whether you are unconfiguring the primary or secondary FTP
server.
418
Advanced Feature Commands
Default
If you do not specify primary or secondary, the default action is to remove both the primary and
secondary FTP server configurations.
Usage Guidelines
None.
Example
The following command removes the configuration for the primary and secondary FTP servers:
unconfigure vm-tracking repository
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
unconfigure vm-tracking vpp vlan-tag
unconfigure vm-tracking vpp vpp_name vlan-tag
Description
Unconfigures the VLAN tag of VPP.
Syntax Description
vpp_name
Specifies a name of the VPP.
Default
N/A.
Usage Guidelines
Use this command to unconfigure the VLAN tag of VPP.
Example
Example output not yet available and will be provided in a future release.
Advanced Features
419
Advanced Feature Commands
History
This command was first available in ExtremeXOS 15.3.
Platform Availability
This command is available on all platforms.
unconfigure vm-tracking vpp
unconfigure vm-tracking vpp vpp_name
Description
Removes the association of a policy or ACL rule to an LVPP.
Syntax Description
vpp_name
Specifies the name of an existing LVPP.
Default
N/A.
Usage Guidelines
None.
Example
The following command removes the configuration of LVPP vpp1:
unconfigure vm-tracking vpp vpp1
History
This command was first available in ExtremeXOS 12.5.
Platform Availability
This command is available on all platforms.
Advanced Features
420