Configuring Avaya Fabric Connect on Avaya Virtual Services Platform 7000 Series
Release 10.4 NN47202-510 Issue 04.03 November 2017 © 2017, Avaya Inc. license is granted will be one (1), unless a different number of All Rights Reserved. licenses or units of capacity is specified in the documentation or other materials available to You. “Software” means computer programs in Notice object code, provided by Avaya or an Avaya Channel Partner, While reasonable efforts have been made to ensure that the whether as stand-alone products, pre-installed on hardware products, information in this document is complete and accurate at the time of and any upgrades, updates, patches, bug fixes, or modified versions printing, Avaya assumes no liability for any errors. Avaya reserves thereto. “Designated Processor” means a single stand-alone the right to make changes and corrections to the information in this computing device. “Server” means a Designated Processor that document without the obligation to notify any person or organization hosts a software application to be accessed by multiple users. of such changes. “Instance” means a single copy of the Software executing at a particular time: (i) on one physical machine; or (ii) on one deployed Documentation disclaimer software virtual machine (“VM”) or similar deployment. “Documentation” means information published by Avaya in varying Licence types mediums which may include product information, operating instructions and performance specifications that Avaya may generally Designated System(s) License (DS). End User may install and use make available to users of its products and Hosted Services. each copy or an Instance of the Software only on a number of Documentation does not include marketing materials. Avaya shall not Designated Processors up to the number indicated in the order. be responsible for any modifications, additions, or deletions to the Avaya may require the Designated Processor(s) to be identified in original published version of documentation unless such the order by type, serial number, feature key, Instance, location or modifications, additions, or deletions were performed by Avaya. End other specific designation, or to be provided by End User to Avaya User agrees to indemnify and hold harmless Avaya, Avaya's agents, through electronic means established by Avaya specifically for this servants and employees against all claims, lawsuits, demands and purpose. judgments arising out of, or in connection with, subsequent Heritage Nortel Software modifications, additions or deletions to this documentation, to the extent made by End User. “Heritage Nortel Software” means the software that was acquired by Avaya as part of its purchase of the Nortel Enterprise Solutions Link disclaimer Business in December 2009. The Heritage Nortel Software currently Avaya is not responsible for the contents or reliability of any linked available for license from Avaya is the software contained within the websites referenced within this site or documentation provided by list of Heritage Nortel Products located at http://support.avaya.com/ Avaya. Avaya is not responsible for the accuracy of any information, LicenseInfo under the link “Heritage Nortel Products” or such statement or content provided on these sites and does not successor site as designated by Avaya. For Heritage Nortel necessarily endorse the products, services, or information described Software, Avaya grants You a license to use Heritage Nortel Software or offered within them. Avaya does not guarantee that these links will provided hereunder solely to the extent of the authorized activation or work all the time and has no control over the availability of the linked authorized usage level, solely for the purpose specified in the pages. Documentation, and solely as embedded in, for execution on, or for communication with Avaya equipment. Charges for Heritage Nortel Warranty Software may be based on extent of activation or use authorized as Avaya provides a limited warranty on Avaya hardware and software. specified in an order or invoice. Refer to your sales agreement to establish the terms of the limited Copyright warranty. In addition, Avaya’s standard warranty language, as well as information regarding support for this product while under warranty is Except where expressly stated otherwise, no use should be made of available to Avaya customers and other parties through the Avaya materials on this site, the Documentation, Software, Hosted Service, Support website: http://support.avaya.com or such successor site as or hardware provided by Avaya. All content on this site, the designated by Avaya. Please note that if You acquired the product(s) documentation, Hosted Service, and the product provided by Avaya from an authorized Avaya Channel Partner outside of the United including the selection, arrangement and design of the content is States and Canada, the warranty is provided to You by said Avaya owned either by Avaya or its licensors and is protected by copyright Channel Partner and not by Avaya. and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, Licenses reproduce, republish, upload, post, transmit or distribute in any way THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA any content, in whole or in part, including any code and software WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO OR unless expressly authorized by Avaya. Unauthorized reproduction, SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE transmission, dissemination, storage, and or use without the express APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR written consent of Avaya can be a criminal, as well as a civil offense INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., under the applicable law. ANY AVAYA AFFILIATE, OR AN AVAYA CHANNEL PARTNER (AS Third Party Components APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. UNLESS OTHERWISE “Third Party Components” mean certain software programs or AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND portions thereof included in the Software or Hosted Service may THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM contain software (including open source software) distributed under ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN third party agreements (“Third Party Components”), which contain AVAYA CHANNEL PARTNER; AVAYA RESERVES THE RIGHT TO terms regarding the rights to use certain portions of the Software TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING (“Third Party Terms”). As required, information regarding distributed OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY Linux OS source code (for those products that have distributed Linux INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR OS source code) and identifying the copyright holders of the Third AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF Party Components and the Third Party Terms that apply is available YOURSELF AND THE ENTITY FOR WHOM YOU ARE in the products, Documentation or on Avaya’s website at: http:// INSTALLING, DOWNLOADING OR USING THE SOFTWARE support.avaya.com/Copyright or such successor site as designated (HEREINAFTER REFERRED TO INTERCHANGEABLY AS “YOU” by Avaya. You agree to the Third Party Terms for any such Third AND “END USER”), AGREE TO THESE TERMS AND CONDITIONS Party Components. AND CREATE A BINDING CONTRACT BETWEEN YOU AND Preventing Toll Fraud AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE (“AVAYA”). “Toll Fraud” is the unauthorized use of your telecommunications Avaya grants You a license within the scope of the license types system by an unauthorized party (for example, a person who is not a described below, with the exception of Heritage Nortel Software, for corporate employee, agent, subcontractor, or is not working on your which the scope of the license is detailed below. Where the order company's behalf). Be aware that there can be a risk of Toll Fraud documentation does not expressly identify a license type, the associated with your system and that, if Toll Fraud occurs, it can applicable license will be a Designated System License. The result in substantial additional charges for your telecommunications applicable number of licenses and units of capacity for which the services. Avaya Toll Fraud intervention If You suspect that You are being victimized by Toll Fraud and You need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1-800-643-2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Support website: http://support.avaya.com or such successor site as designated by Avaya. Suspected security vulnerabilities with Avaya products should be reported to Avaya by sending mail to: [email protected]. Downloading Documentation For the most current versions of Documentation, see the Avaya Support website: http://support.avaya.com, or such successor site as designated by Avaya. Contact Avaya Support See the Avaya Support website: http://support.avaya.com for product or Hosted Service notices and articles, or to report a problem with your Avaya product or Hosted Service. For a list of support telephone numbers and contact addresses, go to the Avaya Support website: http://support.avaya.com (or such successor site as designated by Avaya), scroll to the bottom of the page, and select Contact Avaya Support. Trademarks The trademarks, logos and service marks (“Marks”) displayed in this site, the Documentation, Hosted Service(s), and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the Documentation, Hosted Service(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya trademarks are the property of their respective owners. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Contents
Chapter 1: Introduction...... 8 Purpose...... 8 Related resources...... 8 Documentation...... 8 Training...... 9 Viewing Avaya Mentor videos...... 9 Support...... 9 Searching a documentation collection...... 10 Subscribing to e-notifications...... 10 Chapter 2: New in this release...... 13 Features...... 13 Fabric Attach...... 13 Transparent UNI over static SMLT...... 14 Chapter 2: Other changes...... 15 Chapter 3: SPBM and IS-IS fundamentals...... 16 MAC-in-MAC encapsulation...... 17 I-SID...... 17 BCBs and BEBs...... 18 Basic SPBM network topology...... 18 IS-IS...... 20 Fabric Connect and Switch Cluster interoperability...... 20 Triangle-SMLT...... 22 Square-SMLT...... 24 Switch Clustering with Fabric Connect considerations...... 25 Standard TLVs...... 25 IS-IS hierarchies...... 27 IS-IS PDUs...... 27 IS-IS configuration parameters...... 27 SPBM B-VLAN...... 30 Pre-populated FIB...... 31 RPFC...... 31 SPBM FIB...... 31 SPBM script...... 32 Rear port mode...... 33 Fabric Connect and Stack-mode DToR...... 35 Fabric Attach...... 36 Fabric Attach fundamentals...... 37 FA Element Discovery...... 37 FA agent startup and initialization...... 38
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 4 Comments on this document? [email protected] Contents
FA proxy I-SID-to-VLAN assignment...... 38 FA data processing...... 39 FA Proxy and FA Server connection maintenance...... 42 FA message authentication and integrity protection...... 43 FA Clients...... 44 FA Zero Touch...... 44 FA Auto Provision...... 45 FA Standalone Proxy...... 46 Chapter 4: SPBM and IS-IS infrastructure configuration using ACLI...... 47 Running the SPBM script...... 47 Configuring minimum SPBM and IS-IS parameters...... 48 Displaying global SPBM parameters...... 53 Displaying global IS-IS parameters...... 54 Displaying IS-IS areas...... 56 Configuring SMLT parameters for SPBM...... 57 Configuring optional SPBM parameters...... 59 Configuring optional IS-IS global parameters...... 62 Configuring optional IS-IS interface parameters...... 66 Displaying IS-IS interface parameters...... 68 Displaying the multicast FIB, unicast FIB, and unicast tree...... 71 Displaying IS-IS LSDB and adjacencies...... 74 Displaying IS-IS statistics and counters...... 78 Fabric Attach configuration using the Avaya Command Line Interface ...... 80 Displaying FA-specific settings...... 81 Displaying Fabric Attach elements...... 81 Configuring external client proxy support...... 82 Configuring FA on switch ports...... 82 Displaying switch port FA operation status...... 83 Configuring the FA authentication key...... 84 Configuring FA message authentication support...... 84 Configuring FA VLANs...... 85 Displaying Fabric Attach VLAN information...... 86 Enabling or disabling FA Zero Touch support...... 86 Configuring FA Zero Touch options...... 87 Displaying FA Zero Touch option settings...... 87 Configuring FA Standalone Proxy mode...... 88 Displaying FA uplink values...... 88 Configuring the static uplink for FA Standalone Proxy mode...... 89 Configuring Fabric Attach extended-logging...... 89 Configuring the FA timeout...... 90 Creating an I-SID-to-VLAN assignment on an FA proxy...... 90 Displaying I-SID-to-VLAN assignment information ...... 91 Chapter 5: SPBM and IS-IS infrastructure configuration using EDM...... 92
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 5 Comments on this document? [email protected] Contents
Configuring required SPBM and IS-IS parameters...... 92 Displaying the SPBM I-SID information...... 97 Displaying Level 1 Area information...... 97 Configuring SMLT parameters for SPBM...... 98 Enabling or disabling SPBM globally...... 99 Configuring SPBM parameters...... 100 Displaying SPBM nicknames...... 101 Configuring interface SPBM parameters...... 102 Configuring SPBM on an interface...... 103 Displaying the unicast FIB...... 103 Displaying the multicast FIB...... 104 Displaying LSP summary information...... 105 Displaying IS-IS adjacencies...... 106 Configuring IS-IS globally...... 107 Configuring system level IS-IS parameters...... 109 Configuring IS-IS interfaces...... 110 Configuring IS-IS interface level parameters...... 111 Configuring an IS-IS Manual Area...... 112 Displaying IS-IS system statistics...... 113 Displaying IS-IS interface counters...... 114 Displaying IS-IS interface control packets...... 115 Fabric Attach configuration using Enterprise Device Manager...... 116 Configuring Fabric Attach...... 116 Configuring per-port FA settings...... 117 Displaying Fabric Attach elements...... 118 Configuring an I-SID/VLAN assignment...... 119 Displaying Fabric Attach I-SID...... 119 Chapter 6: SPBM infrastructure configuration example...... 120 Triangle-SMLT configuration example...... 120 Verifying SPBM configuration...... 125 Chapter 7: Layer 2 VSN configuration fundamentals...... 133 SPBM L2 VSN...... 133 C-VLAN UNI...... 134 Switched UNI...... 135 Transparent UNI...... 136 SPBM L2 VSN sample operation...... 137 Chapter 8: Layer 2 VSN configuration using ACLI...... 143 Configuring an SPBM Layer 2 VSN C-VLAN...... 143 Configuring an SPBM Layer 2 VSN Switched UNI...... 144 Configuring an SPBM Layer 2 Transparent UNI...... 146 Displaying C-VLAN, Switched UNI, and Transparent UNI I-SID information...... 148 Chapter 9: Layer 2 VSN configuration using EDM...... 152 Configuring SPBM Layer 2 VSN C-VLANs...... 152
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 6 Comments on this document? [email protected] Contents
Displaying the MAC address table for a C-VLAN...... 153 Configuring Switched UNI and Transparent UNI...... 154 Chapter 10: CFM fundamentals...... 156 MD...... 156 MA...... 157 MEP...... 158 Fault verification...... 159 LBM...... 159 Layer 2 ping...... 159 Fault isolation...... 160 LTM...... 160 Layer 2 traceroute...... 161 Layer 2 tracetree...... 161 MIP...... 162 Nodal MPs...... 162 Configuration considerations...... 162 Chapter 11: CFM configuration using ACLI...... 163 Configuring CFM...... 163 Triggering a LBM Layer 2 ping...... 165 Triggering a LTM Layer 2 traceroute...... 167 Triggering a LTM Layer 2 tracetree...... 168 Chapter 12: CFM configuration using EDM...... 170 Configuring CFM...... 170 Displaying CFM MD...... 171 Displaying CFM MA...... 172 Displaying CFM MEP...... 173 Configuring Layer 2 ping...... 174 Initiating a Layer 2 traceroute...... 176 Viewing Layer 2 traceroute results...... 178 Glossary...... 180
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 7 Comments on this document? [email protected] Chapter 1: Introduction
Purpose This document provides instructions to configure Avaya Virtual Enterprise Network Architecture Fabric Connect on the on the Avaya Virtual Services Platform 7000 Series. Fabric Connect includes the MAC-in-MAC variant of IEEE 802.1aq Shortest Path Bridging (SPB), Intermediate System to Intermediate System (IS-IS), Layer 2 Virtual Service Networks (VSN), and Connectivity Fault Management (CFM). Using the document The document is organized into feature sections: 1. SPB and IS-IS infrastructure configuration — You must first configure your base SPB and IS- IS architecture described in the infrastructure configuration chapters. This allows SPB to operate on the switch. You must perform the initial steps to configure the minimum SPB and IS-IS parameters to enable Fabric Connect on your network. Configuring minimum SPBM and IS-IS parameters on page 48 or Running the SPB script on page 47. 2. Layer 2 VSN services configuration — Once you complete the infrastructure configuration, you can configure the appropriate services. Services run on top of your base architecture, such as Layer 2 VSNs. 3. CFM configuration — Finally, the VSP 7000 provides tools to monitor and troubleshoot your Fabric Connect network.
Related resources
Documentation For a list of the documentation for this product, see Documentation Roadmap Reference for Avaya Virtual Services Platform 7000 Series, NN47202–103.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 8 Comments on this document? [email protected] Related resources
Training Ongoing product training is available. For more information or to register, see http://avaya- learning.com/. Enter the course code in the Search field and click Go to search for the course.
Course code Course title 7D00080W Avaya Stackable ERS and VSP Product Overview 7D00085V Stackable ERS & VSP Installation, Configuration, and Maintenance 7D00085I Stackable ERS & VSP Installation, Configuration, and Maintenance
Viewing Avaya Mentor videos Avaya Mentor videos provide technical content on how to install, configure, and troubleshoot Avaya products. About this task Videos are available on the Avaya Support website, listed under the video document type, and on the Avaya-run channel on YouTube. Procedure • To find videos on the Avaya Support website, go to http://support.avaya.com and perform one of the following actions: - In Search, type Avaya Mentor Videos to see a list of the available videos. - In Search, type the product name. On the Search Results page, select Video in the Content Type column on the left. • To find the Avaya Mentor videos on YouTube, go to www.youtube.com/AvayaMentor and perform one of the following actions: - Enter a key word or key words in the Search Channel to search for a specific product or topic. - Scroll down Playlists, and click the name of a topic to see the available list of videos posted on the website. Note: Videos are not available for all products.
Support Go to the Avaya Support website at http://support.avaya.com for the most up-to-date documentation, product notices, and knowledge articles. You can also search for release notes,
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 9 Comments on this document? [email protected] Introduction
downloads, and resolutions to issues. Use the online service request system to create a service request. Chat with live agents to get answers to questions, or request an agent to connect you to a support team if an issue requires additional expertise.
Searching a documentation collection On the Avaya Support website, you can download the documentation library for a specific product and software release to perform searches across an entire document collection. For example, you can perform a single, simultaneous search across the collection to quickly find all occurrences of a particular feature. Use this procedure to perform an index search of your documentation collection. Before you begin • Download the documentation collection zip file to your local computer. • You must have Adobe Acrobat or Adobe Reader installed on your computer. Procedure 1. Extract the document collection zip file into a folder. 2. Navigate to the folder that contains the extracted files and open the file named
Subscribing to e-notifications Subscribe to e-notifications to receive an email notification when documents are added to or changed on the Avaya Support website. About this task You can subscribe to different types of general notifications, for example, Product Correction Notices (PCN), which apply to any product or a specific product. You can also subscribe to specific types of
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 10 Comments on this document? [email protected] Related resources
documentation for a specific product, for example, Application & Technical Notes for Ethernet Routing Switch 8800. Procedure 1. In an Internet browser, go to https://support.avaya.com. 2. Type your username and password, and then click Login. 3. Under My Information, select SSO login Profile. 4. Click E-NOTIFICATIONS. 5. In the GENERAL NOTIFICATIONS area, select the required documentation types, and then click UPDATE.
6. Click OK. 7. In the PRODUCT NOTIFICATIONS area, click Add More Products.
8. Scroll through the list, and then select the product name. 9. Select a release version. 10. Select the check box next to the required documentation types.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 11 Comments on this document? [email protected] Introduction
11. Click Submit.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 12 Comments on this document? [email protected] Chapter 2: New in this release
The following sections indicate what’s new in this document for Avaya Virtual Services Platform 7000 (VSP 7000) Series Release 10.4.
Features See the following sections for information about new features.
Fabric Attach With the Fabric Attach (FA) feature, you can extend the fabric edge to devices that do not have full Shortest Path Bridging - MAC (SPBM) support. Fabric Attach allows non-SPBM devices to take advantage of full SPBM support if it is available. FA also decreases the configuration requirements on SPBM devices by off-loading some configuration to the attached non-SPBM devices and by automating certain configuration steps that occur most often. For more information about the FA feature, see the following: • Fabric Attach on page 36 • Fabric Attach configuration using the Avaya Command Line Interface on page 80 Fabric Attach Zero Touch FA Zero Touch eases the configuration process on FA-capable devices by automating specific configuration tasks required for FA functionality. Base Zero Touch operation, when enabled, extracts management VLAN data from the primary FA Server advertisements and uses this data to update the in-use management VLAN if applicable. An FA Client may also utilize FA-provided management VLAN data once an FA Proxy/Server is discovered. You must manually configure Zero Touch options on an FA device. Zero Touch supports the following configuration options: • Zero Touch IP Address Source Mode Update: When this option is activated, Zero Touch updates IP address source mode on the receiving FA device to DHCP-When-Needed to initiate DHCP-based IP address acquisition if an IP address has not already been manually configured. The IP address source mode is only updated when the management VLAN is updated as part of the base Zero Touch operation.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 13 Comments on this document? [email protected] New in this release
• Zero Touch automated trusted FA Client connection: When this option is enabled and FA Clients are present, the QoS settings for the interface on which the client is discovered are automatically updated to QoS 'Trusted'. • Automated PVID/Mgmt vlan update FA Client Port Mode: When this option is enabled, the port PVID for certain client types (WAP Type 1(6)/Switch(8)) is updated to the current management VLAN. The port also becomes a member of the current management VLAN. For more information, see FA Zero Touch on page 44. Fabric Attach Standalone Proxy Fabric Attach Standalone Proxy introduces FA Proxy functionality in environments without an FA Server. Regardless of whether the FA Proxy upstream device is a non-Avaya component or an Avaya device on which FA Server functionality is not available, Fabric Attach Standalone Proxy operation supports standard FA Proxy processing as if an FA Server has been discovered. For more information, see FA Standalone Proxy on page 46.
Transparent UNI over static SMLT
Release 10.4 supports Transparent UNI over static SMLT. In order for a Transparent UNI to work correctly in a SMLT configuration, the same ISID must be configured on both SMLT peers. When an ISID that has Transparent UNIs on only one of the two SMLT peers is configured, a transparent smlt-peer UNI on the other SMLT peer must also be created. For more information, see Configuring SMLT parameters for SPBM on page 57.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 14 Comments on this document? [email protected] Chapter 2: Other changes
See the following sections for information about changes that are not feature-related. Document title change Configuring Avaya VENA Fabric Connect on Avaya Virtual Services Platform 7000 Series (NN47202–510) is renamed Configuring Avaya Fabric Connect on Avaya Virtual Services Platform 7000 Series, NN47202–510.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 15 Comments on this document? [email protected] Chapter 3: SPBM and IS-IS fundamentals
Shortest Path Bridging MAC (SPBM) is a next generation virtualization technology that revolutionizes the design, deployment, and operations of enterprise campus core networks along with the enterprise data center. SPBM provides massive scalability while at the same time reducing the complexity of the network. SPBM simplifies deployments by eliminating the need to configure multiple points throughout the network. When you add new connectivity services to an SPBM network you do not need intrusive core provisioning. The simple endpoint provisioning is done where the application meets the network, with all points in between automatically provisioned through the robust link-state protocol, Intermediate-System-to-Intermediate-System (IS-IS). SPBM eliminates the need for multiple overlay protocols in the core of the network by reducing the core to a single Ethernet based link-state protocol that provides all virtualization services in an integrated model. In addition, by relying on endpoint service provisioning only, the idea of building your network once and not touching it again becomes a true reality. This technology provides all the features and benefits required by carrier-grade deployments to the enterprise market without the complexity of alternative technologies traditionally used in carrier deployments, for example, Multiprotocol Label Switching (MPLS). Most Ethernet based networks use 802.1Q tagged interfaces between the routing switches. SPBM uses two Backbone VLANs (BVLANs) that are used as the transport instance. A B-VLAN is not a traditional VLAN in the sense that it does not flood unknown, broadcast or multicast traffic, but only forwards based on IS-IS provisioned backbone MAC (B-MAC) tables. After you configure the B- VLANs and the IS-IS protocol is operational, you can map the services to service instances. SPBM uses IS-IS to discover and advertise the network topology, which enables computation of the shortest path to all nodes in the SPBM network. SPBM uses IS-IS shortest path trees to populate forwarding tables for the individual B-MAC addresses of each participating node. To forward customer traffic across the core network backbone, SPBM uses IEEE 802.1ah Provider Backbone Bridging (PBB) MAC-in-MAC encapsulation, which hides the customer MAC (C-MAC) addresses in a backbone MAC (B-MAC) address pair. MAC-in-MAC encapsulation defines a B-MAC destination address (BMAC-DA) and a B-MAC source address (BMAC-SA). Encapsulating customer MAC addresses in B-MAC addresses improves network scalability (no end-user C-MAC learning is required in the core) and also significantly improves network robustness (loops have no effect on the backbone infrastructure.) The SPBM B-MAC header includes a Service Instance Identifier (I-SID) with a length of 32 bits with a 24-bit ID. I-SIDs identify and transmit virtualized traffic in an encapsulated SPBM frame. You can use I-SIDs in a Virtual Services Network (VSN) for VLANs or VRFs across the MAC-in-MAC backbone: • For a Layer 2 VSN, the device associates the I-SID with a customer VLAN, which the device then virtualizes across the backbone. Layer 2 VSNs associate one VLAN per I-SID.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 16 Comments on this document? [email protected] MAC-in-MAC encapsulation
VSP 7000 Series supports the IEEE 802.1aq standard of SPBM, which allows for larger Layer 2 topologies and permits faster convergence.
MAC-in-MAC encapsulation To forward customer traffic across the core network backbone, SPBM uses IEEE 802.1ah Provider Backbone Bridging (PBB) MAC-in-MAC encapsulation, which hides the customer MAC (C-MAC) addresses in a backbone MAC (B-MAC) address pair. MAC-in-MAC encapsulation defines a BMAC- DA and BMAC-SA to identify the backbone destination and source addresses. The originating node creates a MAC header that is used for delivery from end to end. As the MAC header stays the same across the network, there is no need to swap a label or do a route lookup at each node, allowing the frame to follow the most efficient forwarding path end to end. The encapsulation of customer MAC addresses in backbone MAC addresses greatly improves network scalability, as no end-user MAC learning is required in the backbone, and also significantly improves network robustness, as customer-introduced network loops have no effect on the backbone infrastructure.
I-SID SPBM introduces a service instance identifier called I-SID. SPBM uses I-SIDs to separate services from the infrastructure. After you create an SPBM infrastructure, you can add additional services (such as VLAN extensions) by provisioning the endpoints only. The SPBM endpoints are Backbone Edge Bridges (BEBs), which mark the boundary between the core MAC-in-MAC SPBM domain and the edge customer 802.1Q domain. I-SIDs are provisioned on the BEBs to be associated with a particular service instance. In the SPBM core, the bridges are Backbone Core Bridges (BCBs). BCBs forward encapsulated traffic based on the BMAC-DA. The SPBM B-MAC header includes an I-SID. The length of the I–SID is 32 bits with a 24–bit ID. I- SIDs identify and transmit virtualized traffic in an encapsulated SPBM frame. These I-SIDs are used in a VSN for VLANs across the MAC-in-MAC backbone: Note: I-SID configuration is required only for virtual services such as Layer 2 VSN.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 17 Comments on this document? [email protected] SPBM and IS-IS fundamentals
BCBs and BEBs The boundary between the core MAC-in-MAC SPBM domain and the edge customer 802.1Q domain is handled by Backbone Edge Bridges (BEBs). I-SIDs are provisioned on the BEBs to be associated with a particular service instance. In the SPBM core, the bridges are referred to as Backbone Core Bridges (BCBs). BCBs forward encapsulated traffic based on the BMAC-DA. Important: SPBM separates the payload from the transport over the SPBM infrastructure. Configure all virtualization services on the BEBs at the edge of the network. There is no provisioning required on the core SPBM switches. This provides a robust carrier grade architecture where configuration on the core switches never needs to be touched when adding new services. A BEB performs the same functionality as a BCB, but it also terminates one or more Virtual Service Networks (VSN). A BCB does not terminate any VSNs and is unaware of the VSN traffic it transports. A BCB simply knows how to reach any other BEB in the SPBM backbone.
Basic SPBM network topology The following figure shows a basic SPBM network topology, specifically a Layer 2 VSN. Switches A and D are the Backbone Edge Bridges (BEB) that provide the boundary between the customer VLANs (C-VLAN) and the Backbone. Switches B and C are the Backbone Core Bridges (BCB) that form the core of the SPBM network.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 18 Comments on this document? [email protected] Basic SPBM network topology
Figure 1: SPBM L2 VSN
SPBM uses IS-IS in the core so that all BEBs and BCBs learn the IS-IS System-ID (B-MAC) of every other switch in the network. For example, BEB-A uses IS-IS to build an SPBM unicast forwarding table containing the B-MAC of switches BCB-B, BCB-C, and BEB-D. The BEBs provide the boundary between the SPBM domain and the virtualized services domain. For a Layer 2 VSN service, the BEBs map a C-VLAN to an I-SID based on local service provisioning. Any BEB in the network that has the same I-SID configured can participate in the same Layer 2 VSN. In this example, BEB A and BEB D are provisioned to associate C-VLAN 20 with I-SID 100. When BEB A receives traffic from C-VLAN 20 that must be forwarded to the far-end location, it performs a lookup and determines that C-VLAN 20 is associated with I-SID 100 and that BEB D is the destination for I-SID 100. BEB A then encapsulates the data and C-MAC header into a new B-MAC header, using its own nodal B-MAC: A as the source address and B-MAC: D as the destination address. BEB A then forwards the encapsulated traffic to BCB B. To forward traffic in the core toward the destination node D, BCB B and BCB C perform Ethernet switching using the B-MAC information only. At BEB D, the node strips off the B-MAC encapsulation, and performs a lookup to determine the destination for traffic with I-SID 100. BEB D identifies the destination on the C-VLAN header as C- VLAN 20 and forwards the packet to the appropriate destination VLAN and port.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 19 Comments on this document? [email protected] SPBM and IS-IS fundamentals
IS-IS To provide a loop-free network and to learn and distribute network information, SPBM uses the Intermediate-System-to-Intermediate-System (IS-IS) link state routing protocol. IS-IS is designed to find the shortest path from any one destination to any other in a dynamic fashion. IS-IS creates any- to-any connectivity in a network in an optimized, loop-free manner, without the long convergence delay experienced with the Spanning Tree Protocol. IS-IS does not block ports from use, but rather employs a specific path. As such, all links are available for use. IS-IS is a link-state, interior gateway protocol that was developed for the International Organization for Standardization (ISO). ISO terminology refers to routers as Intermediate Systems (IS), hence the name Intermediate System-to-Intermediate System (IS-IS). SPBM eliminates the need for multiple overlay protocols in the core of the network by reducing the core to a single Ethernet-based, link-state protocol (IS-IS). IS-IS provides virtualization services , using a pure Ethernet technology base. SPBM also uses IS-IS to discover and advertise the network topology, which enables it to compute the shortest path to all nodes in the SPBM network. IS-IS dynamically learns the topology of a network and constructs unicast and multicast mesh connectivity. Each node in the network calculates a shortest-path tree to every other network node based on System-IDs (B-MAC addresses). Unlike in an IP Open Shortest Path First (OSPF) environment, the SPBM use of IS-IS does not require transport of any IP addressing for topology calculations. In the SPBM environment for Layer 2 VSNs, IS-IS carries only pure Layer 2 information with no requirement for an underlying IP control plane or forwarding path. IS-IS runs directly over Layer 2. In SPBM networks, IS-IS performs the following functions: • Discovers the network topology • Builds shortest path trees between the network nodes: - Forwards unicast traffic - Determines the forwarding table for multicast traffic • Communicates network information in the control plane: - Service Instance Identifier (I-SID) information SPBM can distribute I-SID service information to all SPBM nodes, as the I-SIDs are created. SPBM includes I-SID information in the IS-IS Link State protocol data units (PDUs). When a new service instance is provisioned on a node, its membership is flooded throughout the topology using an IS-IS advertisement.
Fabric Connect and Switch Cluster interoperability Fabric Connect and Switch Clustering improve Layer 2 (bridged) resiliency and provide failure redundancy with subsecond failover.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 20 Comments on this document? [email protected] Fabric Connect and Switch Cluster interoperability
Switch Clustering, also known as Split Multi-Link Trunking (SMLT), is a Layer 2 feature that allows two aggregation switches to function as one logical unit to provide enhanced load sharing and faster error recovery. Fabric Connect refers to the MAC-in-MAC variant of IEEE 802.1aq Shortest Path Bridging (SPB), Intermediate System to Intermediate System (IS-IS), Connectivity Fault Management (CFM), and enhancements by Avaya to features and services that leverage SPB technology. Fabric Connect with Switch Clustering is also called SMLT over SPB. Fabric Connect provides a logical Ethernet network infrastructure using a link-state protocol to advertise both topology and logical network membership. Switch Clustering connects a device that supports some form of link aggregation, whether a switch or a server, to two distinct separate SMLT endpoints or switches. These SMLT devices form a Switch Cluster called an interswitch trunk (IST) Core Switch pair. Note: SMLT is supported on UNI ports only. SMLT on NNI ports are not supported. Fabric Connect and Switch Cluster topologies In the current release, VSP 7000 supports the following SMLT topologies over SPB: • a triangle topology • a square topology Note: In this release, Fabric Connect with Switch Clustering (SMLT over SPB) does not support a full- mesh topology. Switch clustering advantages SMLT eliminates all single points of failure and creates multiple paths from all user access switches to the network core. In case of failure, SMLT recovers quickly. SMLT provides a transparent and interoperable solution that requires no modification on the part of the majority of existing user access devices. SMLT improves the reliability of Layer 2 networks that operate between user access switches and the network center aggregation switch by providing: • Load sharing among all links • Fast failover in case of link failure • Elimination of single points of failure • Fast recovery in case of node failure • Transparent and interoperable solutions • Removal of MSTP and RSTP convergence issues
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 21 Comments on this document? [email protected] SPBM and IS-IS fundamentals
Switch Clustering and interswitch trunking You must connect SMLT aggregation switches through an interswitch trunk (IST). Aggregation switches use the interswitch trunk to do the following: • Confirm that they are alive and exchange MAC address forwarding tables. • Send traffic between single switches that attach to the aggregation switches. • Serve as a backup if one SMLT link fails. Because SMLT requires the IST, Avaya recommends that you use multiple links on the interswitch trunk to ensure reliability and high availability. Avaya also recommends that you use Gigabit Ethernet links for IST connectivity to provide enough bandwidth for potential cross traffic. Typical customer deployments require redundancy all the way to the access side of the network. Typical SPBM fabric deployments use two or more B-VLANs for Equal Cost Multipath (ECMP) and resiliency. For simplicity in understanding how the SPBM network works, assume that two B-VLANs (primary and secondary) are configured. The master switch uses the primary B-VLAN for enacapsulation of ingress packets from the SMLT or SLT ports. The secondary switch uses the secondary B-VLAN for encapsulation of ingress packets from the SMLT or SLT ports. The aggregation unit can be a single switch or a stack. No restriction exists on the number of units in the SMLT stack, but for better recovery Avaya recommends a stack of at least three units. In the stack, IST and SMLT trunks can be an MLT or Distributed MultiLink Trunking (DMLT). Avaya also recommends you have at least one IST port that resides on the base unit for better performance. You can configure SLT ports on any unit within the stack. For more information about SMLT configuration, see Switch Clustering using Split-MultiLink Trunking (SMLT) with VSP 7000, ERS 8600/8800, 8300, and 5000 Technical Configuration Guide (NN48500-518).
Triangle-SMLT Triangle-SMLT is a switch clustering topology that consists of one pair of aggregation units and one or two access units. Aggregation switches connect together by IST link, which is usually an MLT or a DMLT. An aggregation switch uses the IST to exchange control and status messages with its peer. For the two aggregation switches to act as a single logical switch, each switch sends its local MAC address information and port link status to its peer. During the start up process, the switches enable IST ports first to allow each aggregation switch to establish a communication channel with its peer. After the IST session is up, then the switches enable SMLT and SLT ports. A triangle design is an SMLT configuration that connects edge switches or SMLT clients to two aggregation switches. Connect the aggregation switches together with an IST that carries all the SMLT trunks configured on the switches. Note: In this release, Fabric Connect with Switch Clustering (SMLT over SPB) does not support a full- mesh topology.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 22 Comments on this document? [email protected] Fabric Connect and Switch Cluster interoperability
The following figure shows a Triangle-SMLT. For a full configuration example, see Triangle-SMLT configuration example on page 120.
Figure 2: Triangle-SMLT Learning of C-VLAN packets In the above example, when CE1 sends data to CE3 or CE4, depending on the MLT hashing, traffic can reach BEB 1 or BEB 2. If you assume traffic from CE1 to CE3 reaches BEB1. Traffic from CE1 to CE4 reaches BEB2. BEB2 can learn the CE1 MAC address of 00:00:11:00:00:00 from two sources: 1. Unknown unicast packet from the B-VLAN on NNI port 4. 2. MAC learn IST message from the IST interface. In order to prevent MAC movement, IST switches do not learn MAC addresses in the C-VLAN if the BMAC-SA is equal to the Nodal MAC of the IST peer or the virtual B-MAC. Forwarding C-VLAN packets In the above example, when CE1 sends data to CE3 or CE4, depending on the MLT hashing, traffic can reach BEB 1 or BEB 2. If you assume traffic from CE1 to CE3 reaches BEB 1. Traffic from CE1 to CE4 reaches BEB 2. 1. A packet from Edge 1 to BEB 1 is encapsulated with I-SID 10 and secondary B-VLAN 41, because BEB 1 is the secondary IST switch. 2. A packet from Edge 1 to BEB 2 is encapsulated with I-SID 10 and primary B-VLAN 40, because BEB 2 is primary IST switch. BEB 3 learns the CE1 MAC address on both B-VLAN 40 and 41. From BEB 3 two paths exist to reach CE1, one from BEB 3 to BEB 1, and the other from BEB 3 to BEB 2. The SMLT edge switches dual-home to the aggregation switches yet they require no knowledge of whether they connect to a single switch or to two switches. You need SMLT only on the aggregation switches. Logically, the aggregation switches appear as a single switch to the edge switches. The
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 23 Comments on this document? [email protected] SPBM and IS-IS fundamentals
connection between the SMLT aggregation switches and the SMLT edge switches are the SMLT links.
Square-SMLT The Square-SMLT topology consists of two pairs of aggregation units that connect back to back. Aggregation switches connect together by IST link, which is usually an MLT or a DMLT. An aggregation switch uses the IST to exchange control and status messages with its peer. For the two aggregation switches to act as a single logical switch, each switch sends its local MAC address information and port link status to its peer. During the start up process, the switches enable IST ports first to allow each aggregation switch to establish a communication channel with its peer. After the IST session is up, then the switches enable SMLT and SLT ports. Edge devices form an SMLT pair that connects to the BEB 1 and BEB 2 SMLT pair through UNI links. Note: In this release, Fabric Connect with Switch Clustering (SMLT over SPB) does not support a full- mesh topology. The following figure shows a Square-SMLT. The Square-SMLT topology consists of two pairs of aggregation units that connect back to back in the following figure. End devices Edge 1 and Edge 2 form an SMLT pair that connects to the BEB 1 and BEB 2 SMLT pair through UNI links.
Figure 3: Square-SMLT
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 24 Comments on this document? [email protected] Standard TLVs
The SMLT edge switches dual-home to the aggregation switches yet they require no knowledge of whether they connect to a single switch or to two switches. You need SMLT only on the aggregation switches. The connection between the SMLT aggregation switches and the SMLT edge switches are the SMLT links.
Switch Clustering with Fabric Connect considerations Refer to the following information to review the requirements for Switch Clustering with Fabric Connect. Consider the following items when you configure Switch Clustering with Fabric Connect: • VSP 7000 does not support Layer 3 routing with SPB. • VSP 7000 does not support Transparent UNI over SMLT or SLT. • You cannot enable IST on a VLAN that has SPBM configured. Similarly, you cannot configure SPBM on a VLAN with IST enabled. The IST carries SPBM traffic, but you cannot configure UNIs on the IST ports. • Configure two B-VLANs, a primary and secondary B-VLAN, for redundancy and load sharing. • Enable Shortest Path Forwarding (SPF) on each B-VLAN. • Enable IP routing on the IST VLAN.
Standard TLVs IS-IS uses Type-Length-Value (TLV) encoding. SPBM employs IS-IS as the interior gateway protocol and implements additional TLVs to support additional functionality. VSP 7000 Series also supports Sub-TLVs. TLVs exist inside IS-IS packets and Sub-TLVs exist as additional information in TLVs. Avaya VSP 7000 Series supports standard 802.1 aq TLVs. The IEEE ratified the 802.1aq standard that defines SPBM and the Type-Length-Value (TLV) encoding that IS-IS uses to support SPBM services. Avaya is in full compliance with the IEEE 802.1aq standard. The following table lists a the TLVs that the VSP 7000 Series supports. Figure 4: Standard TLVs
TLV Description Usage 1 Area addresses — The Area IS-IS area Addresses TLV contains the area addresses to which the IS-IS is connected. 22 Extended IS reachability — The SPBM link metric Sub TLV (type Extended IS Reachability TLV 29) is carried within this TLV. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 25 Comments on this document? [email protected] SPBM and IS-IS fundamentals
TLV Description Usage contains information about adjacent neighbors. 129 Protocol supported — The SPBM in addition to existing Protocol supported TLV carries the NLPID (IPV4 0xCC, IPV6 0x*E..), Network Layer Protocol Identifiers IEEE 802.1aq defined SPBM (NLPID) for the Network Layer NLPID as 0xC1. protocols where the IS-IS can be used. 135 TE IP reachability — The SPBM uses this existing IS-IS TLV Extended IP Reachability TLV 135 to carry IP Shortcut routes through is used to distribution IP the SPBM core. reachability between IS-IS peers. 143 Multi-topology port aware This TLV carries the following capability (MT-Port-Capability) SPBM Sub TLVs: TLV • MCID Sub TLV: The MCID is a This TLV carries the SPB instance digest of the VLANs and MSTI. ID in a multiple SPB instances Neighboring SPBM nodes must environment. This TLV is carried agree on the MCID to form an within IS-IS Hello Packets (IIH). adjacency. In the current release, the MCID is set to all zeros (0). After the VSP 7000 receives a none-zero MCID Sub TLV, it reflects content back to the neighbor. • SPB B-VID Sub TLV (type 6): The Sub TLV indicates the mapping between a VLAN and its equal cost tree (ECT) algorithm. To form an adjacency, both nodes must have a matching primary (BVLAN, ECT) pair, and secondary (BVLAN, ECT) pair. 144 Multi-topology Capability (MT- This TLV carries the following Sub Capability) TLV. TLVs: This TLV carries the SPB instance • SPB instance Sub TLV (type 1): ID in a multiple SPB instance This Sub TLV contains a unique environment. This TLV is carried SPSourceID (nickname) to within LSPs. identify the SPBM node within this SPB topology. • SPB Service ID Sub TLV (type 3): This Sub TLV carries service group membership (I-SIDs) for a particular SPB BVLAN. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 26 Comments on this document? [email protected] IS-IS hierarchies
TLV Description Usage 184 SPBM IP VPN reachability — IS- IP reachability for Layer 3 VSNs IS TLV 184 is used to advertise SPBM L3 VSN route information across the SPBM cloud.
IS-IS hierarchies IS-IS is a dynamic routing protocol that operates within an autonomous system (or domain). IS-IS provides support for hierarchical routing, which enables you to partition large routing domains into smaller areas. IS-IS uses a two-level hierarchy, dividing the domain into multiple Level 1 areas and one Level 2 area. The Level 2 area serves as backbone of the domain, connecting to all the Level 1 areas. Important: The IEEE 802.1aq standard currently only defines the use of one hierarchy, Level 1. Level 2 function is disabled in the current release.
IS-IS PDUs Intermediate System to Intermediate System Hello (IIH) packets discover IS-IS neighbors and establish and maintain IS-IS adjacencies. An IIH is sent in every Hello-interval to maintain the established adjacency. If a node has not heard IIHs from its neighbor within the adjacency holdtime (hello-interval x hello-multiple) seconds, the node tears down the adjacency. In the current release, IIH carries TLV 143 and SPB-B-VLAN Sub-TLV (among other sub-TLVs). For two nodes to form an adjacency the B-VLAN pairs for primary B-LVAN and secondary B-VLAN must match. Link State Packets (LSP) advertise link state information. The system uses the link state information to compute the shortest path. LSP also advertises MT-capability TLV 144 and SPB instance Sub- TLV, and SPB I-SIDs Sub-TLV. Complete Sequence Number Packets (CSNP) contain the most recent sequence numbers of all LSPs in the database. CSNP notifies neighbors about the local LSDB. After a neighbor receives a CSNP, it compares the LSPs in the CSNP with the LSP in the local LSDB. If the neighbor is missing LSPs, it sends a Partial Sequence Number Packets (PSNP) to request the missing LSPs. This process synchronizes the LSDBs among neighbors. A synchronized LSDB among all nodes in the network is crucial to producing a loop-free shortest path.
IS-IS configuration parameters The following sections describe IS-IS configuration parameters.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 27 Comments on this document? [email protected] SPBM and IS-IS fundamentals
IS-IS system identifiers The IS-IS system identifiers consist of three parts: • System ID — The system ID is any 6 bytes that are unique in a given area or level. The system ID defaults to the baseMacAddress of the chassis but you can configure a default value. • Manual area — The manual area or area ID is up to 13 bytes long. The first byte of the area number (for example, 49) is the Authority and Format Indicator (AFI). The next bytes are the assigned domain (area) identifier, which is up to 12 bytes (for example, 49.0102.0304.0506.0708.0910.1112). IS-IS supports a maximum of three manual areas, but the current VSP 7000 release only supports one manual area. • NSEL — The last byte (00) is the n-selector. In the VSP 7000 implementation, this part is automatically attached. There is no user input accepted. The Network Entity Title (NET) is the combination of all three global parameters. All routers have at least one manual area. Typically, a Level 1 router does not participate in more than one area. The following are the requirements for system IDs: • All IS-IS enabled routers must have one manual area and a unique system ID. • All routers in the same area must have the same area ID. • All routers must have system IDs of the same length (6 bytes). • All IS-IS enabled routers must have a unique nickname. PSNP interval You can change the PSNP interval rate. A longer interval reduces overhead, while a shorter interval speeds up convergence. CSNP periodic and interval rate You can configure the CSNP periodic and interval rate. A longer interval reduces overhead, while a shorter interval speeds up convergence. Parameters for the link state packet (LSP) LSPs contain vital information about the state of adjacencies, which must be exchanged with neighboring IS-IS systems. Routers periodically flood LSPs throughout an area to maintain synchronization. You can configure the LSP to reduce overhead or speed up convergence. The following list describes IS-IS parameters related to LSPs: • The max-lsp-gen-interval is the time interval at which the generated LSP is refreshed. The default is 900 seconds with a range of 30 to 900. • The retransmit-lspint is the minimum amount of time between retransmission of an LSP. When transmitting or flooding an LSP an acknowledgement (ACK) is expected. If the ack is not received within retransmit-lspint, the LSP is re-transmitted. The default is 5 seconds with a range of 1 to 300. Point-to-point mode All SPBM links are point-to-point links. VSP 7000 does not support broadcast links.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 28 Comments on this document? [email protected] IS-IS configuration parameters
IS-IS interface authentication Configure IS-IS interface authentication to improve security and to guarantee that only trusted routers are included in the IS-IS network. Interface level authentication only checks the IIH PDUs. If the authentication type or key in a received IIH does not match the locally-configured type and key, the IIH is rejected. By default, authentication is disabled. You can use either one of the following authentication methods: • Simple password authentication — Uses a text password in the transmitted packet. The receiving router uses an authentication key (password) to verify the packet. • MD5 authentication — Creates a Message Digest (MD5) key. Password considerations The passwords for all authentications are saved as cleartext in the configuration file on the Avaya Virtual Services Platform 7000. The passwords for simple and HMAC-MD5 are displayed in cleartext through ACLI. The HMAC-MD5 packet is encrypted when transmitted over the network. To reset the authentication password type, you must set the type to none. The current release supports only interface level authentication. The current release does not support area level or domain level authentication. Hellos To update the identities of neighboring routers, you can configure the: • Interface Hello interval • Interface Hello multiplier Interface Hello interval IS-IS uses Hello packets to initialize and maintain adjacencies between neighboring routers. You can configure the interface level Hello interval to change how often Hello packets are sent out from an interface level. Hello multiplier You can configure the Hello multiplier to specify how many Hellos the Avaya Virtual Services Platform 7000 must miss before it considers the adjacency with a neighboring switch down. The hold (wait) time is the Hello interval multiplied by the Hello multiplier. By default, if the Hello interval is 9 and the Hello multiplier is 3, the hold time is 27. If the Hello multiplier is increased to 10, the hold time is increased to 90. Link metric You can configure the link metric to overwrite the default metric value. By configuring the metric, you can specify a preferred path. Low cost reflects high-speed media, and high cost reflects slower media. For the wide metric, the value ranges from 1 to 16,777,215. In this release, only the wide metric is supported. The total cost of a path equals the sum of the cost of each link. The default value for wide metrics is 10.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 29 Comments on this document? [email protected] SPBM and IS-IS fundamentals
Disabling IS-IS You can disable IS-IS globally or at the interface level. If IS-IS is globally disabled, then all IS-IS functions stop. If IS-IS is enabled at the global level and disabled at one of the interface levels, then IS-IS continues on all other interfaces. Overload bit If the overload bit parameter is configured, the Avaya Virtual Services Platform 7000 sets the overload bit in its LSP. The overload parameter works in conjunction with the overload-on- startup parameter. When the overload-on-startup timer expires, the SPBM node clears the overload bit and re-advertises its LSP. When an LSP with an overload bit is received, the Avaya Virtual Services Platform 7000 ignores the LSP in its SPF calculation so that the transit traffic will not go through the overloaded node. The overloaded node can still receive traffic that is destined for the node itself. The overload bit is usually enabled on stub nodes, which are not used for traversing traffic. By default, overload is set to false.
SPBM B-VLAN Each SPBM network instance is associated with at least one backbone VLAN (B-VLAN) in the core SPBM network. This VLAN is used for both control plane traffic and dataplane traffic. Note: Avaya recommends to always configure two B-VLANs in the core to allow load distribution over both B-VLANs. SPBM alters the behavior of the VLAN. When a B-VLAN is associated with an SPBM network the following VLAN attributes and behaviors are modified for the B-VLAN: • Flooding is disabled • Broadcasting is disabled • Source address learning is disabled • Unknown MAC discard is disabled Ports cannot be added to a B-VLAN manually, IS-IS takes care of adding ports to the B-VLAN. Essentially the B-MAC addresses are programmed into the B-VLAN Forwarding Information Bases (FIBs) by IS-IS instead of the traditional VLANs flooding and learning approach. Modification of the VLAN behavior is necessary to ensure proper control over the SPBM traffic. Note: When configuring a Vlan ID (VID) for a B-VLAN, some VIDs might be unavailable due to other system features. For example, the STP tagged PBDUs default VID range is 4001–4008. Tagged BPDUs cannot use the same VID as an active B-VLAN. For more information, see Configuring Layer 2 on Avaya Virtual Services Platform 7000 Series (NN47202–502).
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 30 Comments on this document? [email protected] Pre-populated FIB
Pre-populated FIB An Ethernet network usually learns MAC addresses as frames are sent through the switch. This process is called reverse learning and is accomplished through broadcast. SPBM does not allow any broadcast flooding of traffic on the B-VLAN in order to prevent looping accomplished through flooding packets with unknown destinations (although multicast traffic is supported). As such, MAC addresses must be distributed within SPBM. This is accomplished by carrying the necessary B-MAC addresses inside the IS-IS link state database. To that end, SPBM supports an IS-IS TLV that advertises the I-SID and B-MAC information across the network. This functionality enables the powerful end-point-provisioning of SPBM. These Backbone MAC addresses are populated into the SPBM VLAN Forwarding Information Base (FIB) to maximize efficiency and to allow Reverse Path Forwarding Check (RPFC) to operate properly.
RPFC A loop prevention mechanism is required at Layer 2 to stop wayward traffic from crippling the network. Reverse Path Forwarding Check (RPFC) is the chosen method of suppressing loop traffic with SPBM. RPFC was originally designed for IP traffic at Layer 3 where it checks the source address of the packet against the routing entry in the routing table. The source address must match the route for the port it came in on otherwise the packet is illegitimate and therefore dropped. With SPBM, the node matches the source MAC address against the ingress port to establish validity. If the frame is not supposed to come in that port, it is immediately suppressed imposing a guaranteed loop control. If there is no VLAN FDB entry to the source MAC address with the outgoing port as the ingress port, the frame will be dropped.
SPBM FIB This section describes the SPBM unicast and multicast FIBs. Unicast FIB The unicast computation runs a single Dijkstra (unlike all pair Dijkstras for multicast). SPBM produces only one Shortest Path First (SPF) tree and the tree is rooted on the computing node. The unicast computation generates an entry for each node in the network. The Destination Address (DA) for that entry is the system-id of the node. In addition, if a node advertises MAC addresses other than the system-id, each MAC address has an entry in the unicast FIB table, and the shortest path to that MAC should be exactly the same as the path to the node. Unicast FIB entries are installed to the vlan-fdb table.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 31 Comments on this document? [email protected] SPBM and IS-IS fundamentals
The following text shows an example of the unicast FIB. 7024XLS(config-if)#show isis spbm unicast-fib ======SPBM UNICAST FIB ENTRY INFO ======DESTINATION BVLAN SYSID HOST-NAME OUTGOING COST ADDRESS NAME INTERFACE ------00:01:20:00:00:d1 1000 0001.2000.00d1 D1 Port: 37 10 00:01:20:00:00:d1 1001 0001.2000.00d1 D1 Port: 37 10 00:01:20:00:00:d2 1000 0001.2000.00d2 D2 Port: 37 20 00:01:20:00:00:d2 1001 0001.2000.00d2 D2 Port: 37 20 00:01:20:00:00:d3 1000 0001.2000.00d3 D3 Port: 37 20 00:01:20:00:00:d3 1001 0001.2000.00d3 D3 Port: 37 20 00:01:20:00:00:d4 1000 0001.2000.00d4 D4 Port: 37 20 00:01:20:00:00:d4 1001 0001.2000.00d4 D4 Port: 37 20 Multicast FIB SPBM runs all pair Dijkstras to produce the multicast FIB. The computing node loops through each node to run Dijkstra using that node as the root, and then prunes paths to only keep the shortest paths. The computing node then computes the intersection of the set of I-SIDs for which the root node transmits, with the set of I-SIDs for which the path endpoints receive. The multicast addresses are built out of two pieces: the instance-ID (nickname) and the I-SID ID converted to hexadecimal format to form the multicast MAC address. |------3 bytes ------|------| nickname & 3 hexadecimal I-SID For example, if the nickname is c.04.00 and the I-SID is 101 (0x65), the multicast address is c3:04:00:00:00:65. The following text shows an example of the multicast FIB. 7024XLS#show isis spbm multicast-fib ======SPBM MULTICAST FIB ENTRY INFO ======MCAST DA ISID BVLAN SYSID HOST-NAME OUTGOING INTERFACES ======c3:04:00:00:00:65 101 1000 0020.c040.0000 VSP7k-c4 NNI T:13 T:12 UNI T:11 V101 1/11 V101 d3:01:00:00:00:65 101 1000 0020.d010.0000 VSP7k-d1 NNI T:13 T:12 UNI T:11 V101 1/11 V101
SPBM script You can use an ACLI script to quickly configure the SPB and IS-IS infrastructure to enable Avaya VENA Fabric Connect on a switch or stack. You can use the SPB script, rather than manually configure the minimum SPBM and IS-IS parameters.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 32 Comments on this document? [email protected] Rear port mode
You can use the command run spbm to quickly configure the following: • Configure the SPB Ethertype. • Create an SPB instance. • Create an SPBM backbone VLAN and associate it to the SPB instance. • Create an SPBM secondary backbone VLAN and associate it to the SPB instance. • Add an SPB nickname. • Create a manual area. • Enable IS-IS on one of the switch interfaces. • Enable IS-IS globally. • Configure the IS-IS system name. • Configure the IS-IS system ID. The following table displays the default values applied if you use the run spbm command. The SPB script creates some of the default values based on the MAC address of the switch, including the nickname and System ID value.
Parameter Default values Ethertype 0x8100 Primary BVLAN 4051 Secondary BVLAN 4052 Manual area 49.0000 Nickname Derived from the chassis MAC System name Derived from the ACLI prompt System ID value Derived from the chassis MAC, using a different algorithm from that for the Nickname
Note: The SPB script only creates the SPBM instance, VLAN, or other parameters if they do not already exist. For example, if the SPBM instance and VLAN already exist, the SPB script does not create them. If the SPB script cannot create one of the parameters because the parameter is already configured, the script stops and an error message displays.
Rear port mode By default, the Fabric Interconnect (FI) ports on the rear of the VSP 7000 Series are configured for Stack-mode Distributed Top-of-Rack deployments, leveraging the Flexible Advanced Stacking Technology (FAST) protocol. When you enable rear port mode, the unit reboots and reconfigures the FI ports as multiple 40 gigabit per second Avaya interface ports for use with other protocols. You can use rear port mode to interconnect multiple stand-alone VSP 7000 units using FI cables. Depending on the rear port mode of operation, either seven or eight 40 Gbps interfaces are available over the four FI ports on the rear of the switch.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 33 Comments on this document? [email protected] SPBM and IS-IS fundamentals
The following table provides detailed information about the FI ports and rear port modes:
FI port Rear port mode Bandwidth Port interface UP 1 (right top Standard (Raw-mode) 120 Gbps 34, 35, 36 connector) UP 2 (right bottom Standard (Raw-mode) 40 Gbps 33 connector) DOWN 1 (left top Standard (Raw-mode) 120 Gbps 38, 39, 40 connector) DOWN 2 (left bottom Standard (Raw-mode) 40 Gbps 37 connector) UP 1 (right top SPB (Fabric-mode DToR) 120 Gbps 34, 35, 36 connector) UP 2 (right bottom SPB (Fabric-mode DToR) 40 Gbps 33 connector) DOWN 1 (left top SPB (Fabric-mode DToR) 80 Gbps 38, 39 connector) DOWN 2 (left bottom SPB (Fabric-mode DToR) 40 Gbps 37 connector)
On the rear of each VSP 7000 Series unit is a pair of FI-up and FI-down ports. In each FI port pair there is a top and bottom connector. In rear port mode, each top connector can provide up to three 40 Gbps ports, and each bottom connector can provide one 40 Gbps port. You can enable a rear port mode and connect the FI ports between stand-alone VSP 7000 Series units to deploy in a Fabric-mode Distributed Top-of-Rack (DToR) or Raw-mode configuration. Fabric- mode DToR leverages the Shortest Path Bridging (SPB) protocol. Standard is a Raw-mode, that can support various port configurations and protocols, such as Inter-Switch Trunking (IST) for Switch Clustering. Note: Due to the different bandwidth support of the FI port top and bottom connectors, you must connect the top connector to the top connector of another unit, and connect the bottom connector to the bottom connector of another unit. Important: Make sure that both ends of the cable are properly inserted into the ports in order to avoid any traffic impact on the front panel. Rear port mode is disabled by default. With rear port mode disabled, the FI ports on the rear of the chassis can be interconnected between units to deploy in a Stack-mode DToR.
Caution: Enabling, disabling, or changing rear port mode, and answering yes to the confirmation prompt, resets the switch configuration to partial defaults.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 34 Comments on this document? [email protected] Fabric Connect and Stack-mode DToR
When you enable rear port mode, the switch applies the following default settings to all FI ports on the rear of the chassis: • VLAN tagging for rear ports is set to tagAll. • The LACP administration key is set to 4095. • The LACP operating mode for rear ports is set to active. • The LACP rear ports time-out value is set to short. • LACP for rear ports is set to enable. Note: Rear port mode allows the VSP 7000 Series to automatically aggregate multiple connections between adjacent units without additional configuration. LACP mode is disabled on a rear port if you remove the port from the default VLAN (VLAN 1) and the port is not configured for any other VLAN. You can activate LACP mode after you add the port to a VLAN. When you enable the Shortest Path Bridging (SPB) rear port mode to deploy in a Fabric-mode DToR, the switch configures port 40 as loopback. Port 40 in loopback mode is not accessible by applications, or displayed on the port list. Note: Rear port Raw-mode does not support SPB. You must enable SPB rear port mode to deploy a Fabric-mode DToR configuration. Changing between rear port modes results in a reboot and a partial configuration reset. Important: Do not interconnect the FI ports of a VSP 7000 unit operating in Fabric-mode DToR or Raw- mode with a VSP 7000 unit operating in Stack-mode DToR. This is an invalid configuration that causes the rear port mode enabled unit to show ports 33–40 as enabled and up, while the Stack unit ports 33–40 are not visible and not available.
Fabric Connect and Stack-mode DToR You can configure VSP 7000 Series units to deploy Fabric Connect with a Stack-mode Distributed Top-of-Rack (DToR) network configuration. Fabric Connect and Stack-mode DToR is also called Shortest Path Bridging (SPB) stack. The SPB stack can support a maximum of eight units. After you enable SPBM, the unit or stack reboots. In a SPB stack the FI ports can provide three physical stack ports for upstream, and three physical stack ports for downstream. The device reserves the two stack ports that remain. One reserved port is the internal loopback required for SPBM functionality.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 35 Comments on this document? [email protected] SPBM and IS-IS fundamentals
Important: You must disable the rear port mode to support a Fabric Connect and Stack-mode DToR configuration. Rear port SPB mode is not a SPB stack. Rear port SPB mode is also called a Fabric-mode DToR configuration. Fabric Connect and Stack-mode DToR functionality SPB stack uses a global and local database of saved settings: • Local database — Circuit related data (four SNMP tables) and Switched UNI data. • Global database — All other data. The databases are stored in the unit NVRAM and are restored during boot. The local data for the circuits and Switched UNIs are stored on each unit with associated ports. The global database stores on each unit. The initial stack formation causes a full SPBM re-configuration, IS-IS stops, re-configures, and restarts automatically. Any non-base unit (NBU) that joins the stack later does not require an IS-IS restart. Unit joining a Fabric Connect and Stack-mode DToR Once a non-base unit (NBU) joins a SPB stack, the NBU compares the following with the Base unit (BU): • VLAN configuration • Global database (except state of router isis enable) If any VLAN or global data is not identical to the BU data, the entire NBU configuration (global and local databases) discards and the BU sends the configuration to the NBU. Once the VLAN and global database match, the local circuits and Switched UNIs activate and become available in the stack. Unit leaving a Fabric Connect and Stack-mode DToR If the Base unit resets or leaves the stack (remove stack cables), an initial stack formation occurs when a Temporary Base unit is available. If a non-base unit leaves the stack, IS-IS disables on the non-base unit regardless of the Base unit state. If the stack breaks in a two unit stack configuration, IS-IS enables on the previous Base unit and disables on the previous non-base unit. If the Base unit leaves the stack in a three (or more) unit configuration, IS-IS remains enabled on the previous Base unit and also on the stack with the Temporary Base unit. If a non-base unit leaves the stack, IS-IS disables on the non-base unit regardless of the Base unit state.
Fabric Attach The following sections provide conceptual information to help you understand and configure Fabric Attach on switch.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 36 Comments on this document? [email protected] Fabric Attach
Fabric Attach fundamentals Fabric Attach (FA) extends the fabric edge to devices that do not support Shortest Path Bridging MAC (SPBM). With FA, non-SPBM devices can take advantage of full SPBM support, when support is available. FA also decreases the configuration requirements on SPBM devices by off-loading some configuration to the attached non-SPBM devices and by automating certain configuration steps that occur most often. FA Signaling The FA elements communicate between themselves using FA Signaling . FA Signaling is Avaya’s application level protocol that leverages standard network protocols, such as LLDP, to exchange messages and data between FA elements to orchestrate network automation. FA Network Elements The FA architecture involves the following FA elements: • FA Server–An SPB capable network device connected to the fabric edge running the FA agent in FA Server mode. FA Servers receive requests to create services with specific I-SID/VLAN bindings. • FA Proxy–A non-SPB network device running the FA agent in FA Proxy mode. FA Proxies support I-SID/VLAN assignment definition and have the ability to advertise these assignments for possible use by an FA Server, if connectivity permits. • FA Client–A non-SPB network attached device running the FA agent in FA Client mode and able to advertise ISID/VLAN binding requests for service creation to an FA Proxy or FA Server. • FA Standalone Proxy–An FA device running the FA agent in FA Standalone Proxy mode. FA Standalone Proxy supports FA Proxy functionality in environments without an FA Server. Note: This release only supports FA Proxy and FA Standalone Proxy operation. FA Server functionality is not supported. For more details about FA Standalone Proxy operation, see FA Standalone Proxy on page 46.
FA Element Discovery An FA agent which controls FA functionality resides on all FA-capable devices (FA Server, FA Proxy, FA Standalone Proxy or FA Client). The agent executes as a normal priority task and no agent- specific configuration is necessary. FA Proxy and FA Server elements control FA through a global FA service setting (global SPBM setting) and through per-port settings that control the transmission of FA information using FA Signaling. The first stage of establishing FA connectivity involves element discovery. In order for FA discovery to function, FA service and per-port settings must be enabled. Once these settings are enabled, the FA agent advertises its capabilities (FA Server, FA Proxy or FA Client) through FA Signaling.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 37 Comments on this document? [email protected] SPBM and IS-IS fundamentals
Following discovery, an FA agent is aware of all FA services currently provided by the network elements to which it is directly connected. Based on this information, an FA Client or an FA Proxy agent can determine whether FA data (I-SID/VLAN assignments) should be exported to an FA Proxy that acts as an external client proxy or an FA Server. Per-port settings are, by default, enabled on FA Proxies and disabled on FA Servers. Note: An FA Proxy can communicate with, at most, one FA Server at a time. If multiple server connections exist, the first discovered server is considered the primary server. Multiple links (trunked) to a single server are supported as long as they form a logical interface. Multiple non- trunked links are not supported and data received on non-primary ports is ignored by an FA Proxy. FA Proxies or FA Clients can connect through a LAG/MLT to two FA Servers which form a Split-LAG or SMLT pair. Connections which may create loops, to multiple servers that are not in Split-LAG or SMLT mode, are not supported. An FA Server can communicate with multiple, different FA Proxies and FA Clients.
FA agent startup and initialization During the FA agent startup and initialization sequence, the following are restored from non-volatile memory: • FA service status • FA port-level settings • external client proxy status • message authentication status and keys for all ports • previously configured I-SID/VLAN assignments • Zero Touch settings • FA Standalone Proxy settings • extended logging support In a stack environment, FA agent startup and initialization occurs on every unit in the stack, using the data restored from non-volatile memory. The initialization sequence can also include operations geared towards cleaning-up settings that were previously configured in support of FA I-SID/VLAN assignments that were active on an FA proxy or an FA server before a system reset.
FA proxy I-SID-to-VLAN assignment Although administrators may configure I-SID-to-VLAN bindings on FA Proxies, I-SID-to-VLAN bindings are typically received by FA Proxies from FA Clients. If external client proxy support is
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 38 Comments on this document? [email protected] Fabric Attach
enabled, standard processing requirements for bindings received from an FA Client are managed the same way that processing requirements for locally configured bindings are managed. If an I-SID-to-VLAN assignment is accepted by the FA Server, the assignment state is updated to active. If an I-SID-to-VLAN assignment is not accepted by the FA Server, the assignment state is updated to rejected. The FA Proxy receives and displays assignment status information from the FA Server for each pending I-SID-to-VLAN assignment. Possible responses include: • Assignment accepted (2) • Rejection: generic (3) • Rejection: Fabric Attach resources unavailable (4) • Rejection: VLAN invalid (6) • Rejection: VLAN resources unavailable (8) • Rejection: application interaction issue (9) Note: Data exchanges (I-SID/VLAN assignments) between an FA Proxy and an FA Server/FA Client are supported, as are exchanges between an FA Server and an FA Proxy/FA Client. FA Proxy to FA Proxy and FA Server to FA Server interactions are not supported. Note: VLANs that are automatically created on an FA Proxy due to I-SID/VLAN assignment acceptance are automatically deleted when bindings are rejected or deleted. Other feature settings (i.e dhcp-snoopig, arp-inspection, etc) undertaken based on assignment acceptance are undone after I-SID/VLAN assignment transitions (assignment transition to pending state or assignment deletion). The amount of clean-up required depends on whether the port VLAN membership was established by the FA Proxy agent or by the administrator outside of the FA feature operation.
FA data processing Following discovery, an FA Proxy or FA Client transmits locally-defined I-SID/VLAN assignments through FA Signaling to an FA Server, which accepts or rejects these assignments. The I-SID/VLAN assignment acceptance by the server can require actions to be performed by the FA agent on both the FA Proxy and the FA Server, to appropriately configure the communication channel (uplink) between the FA Proxy or FA Client and FA Server. Most actions undertaken based on assignment acceptance are undone when the I-SID/VLAN assignment is no longer needed. I-SID/VLAN assignment rejection by the FA Server requires the FA Proxy to clean up any settings that the FA agent made related to feature operation, as well as log the rejection and any associated error type information for later analysis by an administrator. The amount of clean-up required depends on whether the port VLAN membership was established by the FA Proxy agent or by the administrator outside of the FA feature operation. An uplink port that is associated with a VLAN
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 39 Comments on this document? [email protected] SPBM and IS-IS fundamentals
because of an accepted FA Proxy I-SID/VLAN assignment, and not because of an explicit administrator port VLAN membership action, will have the port VLAN membership cleared when the related I-SID/VLAN assignment is rejected by the FA Server or deleted by the FA Proxy administrator. The port tagging status will remain in effect regardless of I-SID/VLAN assignment status, once it has been established by the FA agent.. VLANs that are automatically created on an FA Proxy due to I-SID/VLAN assignment acceptance are automatically deleted when bindings are rejected or deleted. No more than a single log message is generated for a rejected I-SID/VLAN assignment, regardless of how many times the assignments have been requested and rejected. Assignments that are rejected, accepted, and later rejected result in a log message being generated for each “new” rejection (two I-SID/VLAN assignment rejection log messages are generated in this case). FA Proxy I-SID/VLAN assignment addition actions: • Create port-based VLAN corresponding to I-SID/VLAN assignment VLAN. • Update port VLAN membership to include I-SID/VLAN assignment VLAN. • Update port VLAN tagging status to ensure egress traffic is tagged. FA Server I-SID/VLAN assignment addition actions: • Create SPBM switched UNI VLAN corresponding to I-SID/VLAN assignment VLAN. - C-VLAN join operation does not initiate VLAN creation (VLAN already exists and is associated with the I-SID/VLAN binding I-SID). • Update downlink port VLAN tagging status to ensure egress traffic is tagged. Tagging status for FA client connections is determined by the client link tagging requirements. • Update I-SID/VLAN mapping data to ensure Shortest Path Bridging-MAC (SPBM)-switched UNI support is enabled for the I-SID/VLAN/port tuple (in other words, create switched UNI). Port VLAN membership is updated by this action. Additional actions can be required for I-SID/VLAN binding state transitions involving FA Client- generated data. The communication channel (that is, the downlink) between the FA Client and FA Proxy must be appropriately configured. This can require actions to be performed on the switch. FA Proxy external client proxy I-SID/VLAN assignment addition actions: • Update downlink port VLAN membership to include I-SID/VLAN assignment VLAN. • Update downlink port VLAN tagging status based on the FA Client state data (tagged – ‘tagAll’/ untagged – ‘untagPvidOnly’). Each of these actions is performed by the FA Proxy and FA Server for each I-SID/VLAN assignment, unless the required data/settings have already been configured by the administrator. The successful transition from ‘pending’ to ‘active’ is gated by the successful completion of these actions. The FA agent tracks which settings have been updated based on I-SID/VLAN assignment processing (comparing them with settings established by the administrator), and cleans-up or undoes the settings that are related to I-SID/VLAN assignment support as much as possible when an assignment is no longer needed. I-SID/VLAN assignment state transitions from ‘active’ to ‘rejected’ require complementary actions be performed by the FA Proxy and the FA Server to eliminate assignment-related settings:
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 40 Comments on this document? [email protected] Fabric Attach
FA Proxy I-SID/VLAN assignment deletion actions: • Update uplink port VLAN membership to exclude I-SID/VLAN assignment VLAN. • Delete port-based VLAN corresponding to I-SID/VLAN assignment VLAN. Uplink port VLAN tagging status remains unchanged. FA Server I-SID/VLAN assignment deletion actions: • Delete I-SID/VLAN/port association data to disable SPBM-switched UNI support for the I- SID/ VLAN/port tuple (to delete switched UNI). This action updates port VLAN membership. • Delete SPBM-switched UNI VLAN corresponding to I-SID/VLAN assignment VLAN. - Previously joined C-VLANs are not deleted. State transitions related to FA Client-generated bindings require additional complementary actions to be performed by the FA Proxy to eliminate assignment-related settings: FA Proxy external client proxy I-SID/VLAN assignment deletion actions: • Update downlink port VLAN membership to exclude I-SID/VLAN assignment VLAN. • Delete port-based VLAN corresponding to I-SID/VLAN assignment VLAN. Note: Downlink port VLAN tagging status remains unchanged Assignment status data returned by the FA Server for each pending I-SID/VLAN assignment drives the FA Proxy response processing. Assignment rejections can include information to indicate the reason for the rejection. Rejection error codes include: • FA resources unavailable(4)–the resources that are required for the FA agent to support additional I-SID/VLAN assignments are currently exhausted. The maximum number of assignments that can be supported has been reached. • VLAN invalid(6)–the specified VLAN can’t be used to create a switched UNI at this time. The VLAN already exists and is either inactive or has an incorrect type for this application. This error is also returned if an FA Client or FA Proxy exports an bindings with an I-SID value of 0 and SPBM provisioning is enabled. • VLAN resources unavailable(8)–the maximum number of VLANs that can be supported by the device has been reached. • Application interaction issue(9)–a failure has been detected during FA interactions with the VLAN and/or the SPBM applications. The VLAN operations to create the required SPBM switched UNI VLAN or enable port tagging may have failed or the SPBM operation to create the switched UNI may have failed. As with the actions initiated to support an assignment addition, actions related to assignment deletion are performed only if the targeted data was created during the I-SID/VLAN assignment addition phase. Previously-existing configuration data is not changed. No artifacts are left behind to indicate that automated operations have taken place, following an addition or deletion sequence. This goal may not always be achievable but all attempts are made to satisfy this requirement.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 41 Comments on this document? [email protected] SPBM and IS-IS fundamentals
In addition to explicit I-SID/VLAN assignment state transitions, several events can occur that initiate assignment deletion processing. These include: • I-SID/VLAN assignment timeout–A “last updated” timestamp is associated with all active assignments on the FA Server. When this value is not updated for a pre-determined amount of time, the I-SID/VLAN assignment is considered obsolete. Obsolete assignment data and related settings are removed by the FA server agent. The timeout duration value allows FA Server settings to be maintained if temporary connectivity issues are encountered. I-SID/VLAN binding timeout is also performed by an FA Proxy when it is providing client proxy services and FA Client data is present. Processing similar to that performed by the FA Server related to data aging is supported. • I-SID/VLAN assignment list updates–The current I-SID/VLAN assignment list is advertised by an FA Proxy at regular intervals (dictated by FA Signaling). During processing of this data, an FA Server must handle list updates and delete assignments from previous advertisements that are no longer present. Though these entries would be processed appropriately when they timeout, the FA agent attempts to update the data in real-time and initiates deletion immediately upon detection of this condition. • FA Server inactivity timeout–If primary FA Server advertisements are not received for a pre- determined amount of time, the I-SID/VLAN assignments accepted by the server are considered rejected. I-SID/VLAN assignment data is defaulted (reverts to the ‘pending’ state) and related settings are removed by the FA Proxy agent. The timeout duration value has been chosen to allow FA Proxy settings to be maintained if temporary connectivity issues are encountered. You can configure the timeout value used for FA device or binding aging with the fa timeout command. The default value is 75 seconds.
FA Proxy and FA Server connection maintenance An FA Proxy can only interact with one FA Server at a time. If multiple server connections exist, the first discovered server is considered the primary server. All other servers discovered after this point in time are considered alternates. Typically only a single FA Server is discovered. If multiple servers are discovered, an indication is logged to identify this situation in case it is not intended. I-SID/VLAN assignment data is only exchanged between the FA Proxy and the primary FA Server. When using LACP for uplink/downlink trunk, ports should be aggregated into trunk. Primary server failure is detected using a capabilities advertisement timeout. Once a predefined period of time without an FA Server advertisement from the current primary server expires, the primary server becomes undefined. Any FA Proxy I-SID/VLAN assignments previously accepted by the server are defaulted (reset to the ‘pending’ state) and related settings are cleared. An informational message (primary server lost) is logged when this transition occurs. I-SID/VLAN assignment data is not advertised until a new primary FA Server is selected. The same algorithm used at startup to select an initial primary server is used to select a new primary server. FA Proxy/FA Server connectivity using Multi-link Trunking (MLT), Distributed Multi-Link Trunking (DMLT) or Split Multi-Link Trunking (SMLT) connections is supported.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 42 Comments on this document? [email protected] Fabric Attach
Multiple links associated with the same trunk are treated as a single logical connection. The FA agent reconciles any issues related to MLT, DMLT and SMLT server connectivity and recognizes server uniqueness in the presence of (potentially) multiple capabilities advertisements (that is, FA Signaling received on multiple ports generated by the same server). In MLT, DMLT and SMLT environments, FA Signaling is generated and received on all links connecting the FA Proxy and FA Server. An FA Proxy receiving an FA Server advertisement determines if a primary FA Server has been selected. If not, the FA Element System ID associated with an advertising FA Server is saved and primary server selection is completed. Once a primary server has been selected, system ID data associated with FA Server advertisements received on other ports is compared against the primary server data. If the system ID values are not the same, an error indication is logged. In all cases, the FA Proxy only generates FA Signaling containing I- SID/VLAN assignment data on the interfaces associated with the primary FA Server. Note: The FA Element System ID is structured such that the same system ID is generated on all links associated with a trunk connection between an FA Proxy and an FA Server even in an SMLT scenario where different physical devices are acting as a single logical entity. In an SMLT environment, an FA Server takes additional actions to ensure that data is synchronized on both SMLT aggregation peers. In this configuration, the FA Server that receives and accepts advertised FA I-SID/VLAN assignments is responsible for generating messages that are sent across the Inter-Switch Trunk (IST) to inform the partner aggregation switch about FA settings that have been configured (for example, SPBM switched UNI VLAN). Similar actions are required when I-SID/ VLAN assignments are deactivated. Agent Stacking functionality The FA agent is able to function in both standalone and stacked configurations. In a stack, the base unit FA agent acts as the master and pushes its configuration settings to all non-base units (NBUs), to synchronize data across all units. FA agents are active on all units and are able to process stack events as well as data distribution messages. On an FA Proxy, connections to the primary FA Server can exist on any unit in the stack. When the unit with the active FA Proxy-to-FA primary server interface leaves the stack, any I-SID-to-VLAN assignments accepted by the server are aged-out. I-SID-to-VLAN assignment data is restored to the default pending state and related settings are removed by the FA Proxy agent.
FA message authentication and integrity protection In order to secure the FA communication in terms of data integrity and authenticity, a keyed-hash message authentication code transmitted with FA TLV data is used to protect all FA signaling exchanges. The standard HMAC-SHA256 algorithm is used to calculate the message authentication code (digest) involving a cryptographic hash function (SHA-256) in combination with a shared secret key. The key is symmetric (known by both source and destination parties). By default, FA message authentication is enabled and a default key is defined to provide secure communication out-of-the- box. Message authentication and authentication key settings are maintained on a per-port basis.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 43 Comments on this document? [email protected] SPBM and IS-IS fundamentals
When FA message authentication is enabled, the FA key (default or configured) is used to generate a Hash-based Message Authentication Code (HMAC) digest that is included in FA I-SID/VLAN Assignment TLVs. Upon receipt, the HMAC digest is recomputed for the TLV data and compared against the digest included in the TLV. If the digests are the same, the data is valid. If not, the data is considered invalid and is ignored. The FA secure communication setting (enabled/disabled) and the symmetric key data are maintained across resets and restored during FA initialization.
FA Clients FA Clients connect to an FA Proxy through standard, non MAC-in-MAC access ports, advertising configured I-SID/VLAN requests to the FA Server. In this scenario, the FA Proxy acts as a client proxy for the FA Client by passing I-SID/VLAN binding requests to a discovered FA Server and returning assignment status information to the FA Client. FA Clients may connect directly to an FA Server as well. Note: External client proxy support must be enabled on an FA Proxy switch before FA client data is accepted by the FA Proxy. By default, external client proxy support is enabled on an FA Proxy. I-SID/VLAN bindings received from an FA Client by an FA Proxy acting as a proxy for external clients are processed in much the same way locally administered assignments are processed. FA Proxy response processing takes care of VLAN creation and updates VLAN membership and tagging of the FA Server uplink port if necessary. If the I-SID/VLAN client assignment is rejected by the FA Server, the FA Proxy performs any required clean-up tasks and also logs the rejection and any associated error type information for later analysis by an administrator.
FA Zero Touch FA Zero Touch eases the configuration process on FA-capable devices by automating specific configuration tasks required for FA functionality. For situations when you prefer or require manual configuration of the settings affected by Zero Touch, feature control is provided. Fabric Attach must be enabled in order for Zero Touch to function. When base Zero Touch functionality is enabled, FA Proxy and FA Client devices can acquire management VLAN data from the connected FA Server or FA Proxy and use it to facilitate manageability and network configuration. By default, base Zero Touch support is enabled. In addition to base Zero Touch functionality, you can configure the following Zero Touch options on an FA device:
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 44 Comments on this document? [email protected] Fabric Attach
IP Address Source Mode Update When this option is enabled, IP address source mode is updated on the FA Proxy device (receiver) to DHCP-When-Needed and initiates DHCP-based IP address acquisition if an IP address is not manually configured. IP address source mode update only occurs during base Zero Touch processing when a new management VLAN is processed if this option is enabled. Automated trusted FA Client connection This option enables automatic trusted FA Client connection. When this option is enabled and FA Clients are present, the QoS settings for the interface on which the client is discovered are automatically updated to QoS 'Trusted'. If the FA Clients of the appropriate type are deemed no longer valid (when element aging causes the FA Client to be deleted from the discovered elements list), the QoS port settings revert to the previous state. QoS interface class data is updated based on the discovery and deletion (based on aging) of the following FA Client types: • Wireless Access Point Type 1 • Switch Automated configuration only applies to FA-enabled ports. Note: This option is applicable to FA Proxy, FA Standalone Proxy, and FA Server devices. Automated PVID FA Client Port Mode When this option is enabled, automatic port PVID and management VLAN membership updates are initiated based on the type of discovered FA Clients. This is applicable for FA Proxy, FA Server, and FA Standalone Proxy devices. Automated configuration is only applied to FA-enabled ports.
FA Auto Provision Auto Provision enables devices that can function both as an FA Proxy (SPBM disabled) or an FA Server (SPBM enabled) to function as an FA Server with SPBM disabled. FA VLAN definitions, configured locally on an FA Proxy or through client processing, transparently replace I-SID/VLAN binding definitions and allow all of the automated FA processing, with the exception of switched UNI- related operations, to be performed in the absence of SPBM operations. All existing FA default settings remain unchanged. FA Auto provision can be used on an FA server device. An FA Server can operate in SPBM or VLAN provisioning mode. In an SPB environment, when SPBM provisioning is operational, for each VLAN associated with an accepted I-SID/VLAN assignment, the FA Server creates an SPBM switched UNI VLAN , if the VLAN does not already exist. In a non-SPB environment, when VLAN auto-provisioning is operational, the FA Server creates port-based VLANs instead of SPBM switched UNI VLANs. Once the FA Proxy selects a primary FA Server, the FA Proxy provision mode transitions to the provisioning mode operational on the FA Server.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 45 Comments on this document? [email protected] SPBM and IS-IS fundamentals
The current provisioning mode on an FA Server determines the range of I-SID values that are acceptable in the proposed I-SID/VLAN assignment list. When SPBM is enabled, the acceptable I- SID range is 0-16777214. When SPBM is disabled and the auto provision mode is set to server, the FA Server only accepts bindings with an I-SID value of 0.
FA Standalone Proxy FA Standalone Proxy introduces FA Proxy functionality in environments without an FA Server. Regardless of whether the FA Proxy upstream device is a non-Avaya component or an Avaya device on which FA Server functionality is not available, standalone FA Proxy operation supports standard FA Proxy processing as if an FA Server has been discovered. You can enable or disable FA Standalone Proxy support. By default, it is disabled. Note: In FA Standalone Proxy mode, I-SID values are not specified and are implicitly 0. Only bindings with an I-SID value equal to 0 are accepted for processing. In FA Standalone Proxy mode you must provide the FA Server uplink information, which is typically gathered through FA Server discovery. Once you provide this information, FA Standalone Proxy mode operates as if an FA Server has been discovered and is accepting I-SID/VLAN binding requests. The binding clean-up is similar to an FA Server timeout event, and occurs when the static uplink is deleted and when FA Standalone Proxy operation is disabled. Note: No interactions with an FA Server are supported in FA Standalone Proxy mode. Note: Before creating static uplink over a LAG, it`s highly recommended to manually bind LACP-key to an MLT-ID. When using LACP for uplink trunk, ports should be aggregated into trunk.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 46 Comments on this document? [email protected] Chapter 4: SPBM and IS-IS infrastructure configuration using ACLI
This section provides procedures to configure SPBM and IS-IS using Avaya Command Line Interface (ACLI).
Running the SPBM script Use the following procedure to run the SPBM script to automate the minimum required SPBM and IS-IS parameters to allow Fabric Connect to operate on the switch. About this task You can use this procedure to quickly configure the minimum SPBM and IS-IS parameters. However, a manual procedure is available instead of using this script. Note: You must enable the SPBM before running the SPBM script. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. To run the SPBM script, enter the following command at the command prompt: run spbm Note: If the script causes a configuration conflict or cannot execute a command, an error message displays and the script stops. Example Run the SPBM script: 7024XLS> run spbm SPBM Secondary Backbone VLAN <2-4059>[4052]: SPBM Nickname []:8 ISIS System Name [7024XLS]: ISIS System ID
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 47 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
SPBM parameters... %% SPBM Ethertype is set to 0x8100 %% SPBM Backbone VLAN is set to 4051 %% SPBM Secondary Backbone VLAN is set to 4052 %% VLANs 4051,4052 are associated with SPBM instance %% SPBM Nickname is set to e.ed.00 %% Manual-area is set to 49.0000 %% ISIS is enabled on Ethernet 8 %% ISIS System Name is set to 7024XLS %% ISIS System ID is set to 7030.183e.efdf
Configuring minimum SPBM and IS-IS parameters Use the following procedure to configure the minimum required SPBM and IS-IS parameters to allow Fabric Connect to operate on the switch. About this task An SPB script is available instead of using this procedure. However, you can use this procedure to manually configure the minimum SPBM and IS-IS parameters. When you enable SPBM, the switch automatically configures the QoS agent buffer mode to spb- scaled. For more information about this mode, see Configuring Quality of Service on Avaya Virtual Services Platform 7000 Series, NN47202–504. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Enable SPBM globally: spbm Note: When you enable SPBM, the switch reboots. A reboot might be required to enable the SPB loopback port. 3. Create the primary SPBM backbone VLAN (B-VLAN): vlan create <2–4094> type spbm-bvlan 4. Create the secondary SPBM backbone VLAN (B-VLAN): vlan create <2–4094> type spbm-bvlan 5. Log on to the IS-IS Router Configuration mode: router isis 6. Create the SPBM instance (in this release, only one SPBM instance is supported):
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 48 Comments on this document? [email protected] Configuring minimum SPBM and IS-IS parameters
spbm <1–100> 7. Add the SPBM B-VLANs to the SPBM instance: spbm <1–100> b-vid {
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 49 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
After you configure the basic infrastructure, see Layer 2 VSN configuration using ACLI on page 143 to configure Layer 2 services. 18. Display the SPBM configurations: show isis spbm 19. Display the global IS-IS configuration: show isis 20. Display the interface IS-IS configuration: show isis interface Example 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# spbm This operation will require a reboot to configure the loopback port. Are you sure (y/n) y 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# vlan create 1000 type spbm-bvlan 7024XLS(config)# vlan create 2000 type spbm-bvlan 7024XLS(config)# router isis 7024XLS(config-isis)# spbm 1 7024XLS(config-isis)# spbm 1 b–vid 1000,2000 primary 1000 7024XLS(config-isis)# spbm 1 nick-name 1.11.16 7024XLS(config-isis)# manual-area c0.2000.0000.0000 7024XLS(config-isis)# exit 7024XLS(config)# interface Ethernet 3 7024XLS(config-if)# isis 7024XLS(config-if)# isis spbm 1 7024XLS(config-if)# isis enable 7024XLS(config-if)# exit 7024XLS(config)# vlan member remove 1 3 7024XLS(config)# router isis enable
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 50 Comments on this document? [email protected] Configuring minimum SPBM and IS-IS parameters
7024XLS(config)# show isis spbm ======ISIS SPBM Info ======SPBM B-VID PRIMARY NICK LSDB INSTANCE VLAN NAME TRAP ------1 1000,2000 1000 1.11.16 disable ======ISIS SPBM SMLT Info ======SPBM SMLT-SPLIT-BEB SMLT-VIRTUAL-BMAC SMLT-PEER-SYSTEM-ID INSTANCE ======1 primary 00:00:00:00:00:00 0000.0000.0000
7024XLS(config)# show isis ======ISIS General Info ======AdminState : enabled RouterType : Level 1 System ID :0014.c7e1.33df Max LSP Gen Interval : 900 Min LSP Gen Interval : 30 Metric : wide Overload-on-startup : 20 Overload : false Csnp Interval : 10 PSNP Interval : 2 Rxmt LSP Interval : 5 spf-delay : 100 Router Name : Num of Interfaces : 2 Num of Area Addresses : 1 7024XLS(config)# show isis interface ======ISIS Interfaces ======IFIDX TYPE LEVEL OP-STATE ADM-STATE ADJ UP-ADJ SPBM-L1-METRIC ------Mlt2 pt-pt Level 1 UP UP 1 1 10 Port3 pt-pt Level 1 UP UP 1 1 10
Variable definitions Use the data in the following table to use the isis command.
Variable Value enable Enables or disables the IS-IS circuit/interface on the specified port. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 51 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Variable Value The default is disabled. Use the no option to disable IS-IS on the specified interface. spbm <1–100> Enable the SPBM instance on the IS-IS interfaces.
Use the data in the following table to use the manual-area command.
Variable Value
Use the data in the following table to use the spbm command.
Variable Value <1–100> Creates the SPBM instance. In this release, only one SPBM instance is supported. b-vid {
Use the data in the following table to use the vlan create command.
Variable Value <2–4094> Specifies the VLAN ID. Creates an SPBM Backbone VLAN (B-VLAN). You can optionally specifiy a name for the SPBM B-VLAN. type {ipsubnet-mstprstp|port-mstprstp|protocol- Specifies the type of VLAN created. mstprstp|spbm-bvlan|srcmac-mstprstp} • ipsubnet-mstprstp — Create a VLAN by IP subnet. • port-mstprstp — Create a VLAN by port. • protocol-mstprstp — Create a VLAN by protocol. • spbm-bvlan — Create an SPBM-BVLAN. • srcmac-mstprstp — Create a VLAN by source MAC address.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 52 Comments on this document? [email protected] Displaying global SPBM parameters
Job aid
Important: After you configure the SPBM nickname and enable IS-IS, if you require a change of the system ID, you must also change the nickname. However, for naming convention purposes or configuration purposes, you might not want to change the nickname. To maintain the same nickname with a different system ID, perform the following steps: 1. Disable IS-IS. 2. Change the system ID. 3. Change the nickname to a temporary one. 4. Enable IS-IS. 5. Disable IS-IS. 6. Change the nickname to the original nickname. 7. Enable IS-IS.
Displaying global SPBM parameters Use the following procedure to display and verify the proper global SPBM configuration. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. At the command prompt, enter the following command: show isis spbm 3. You can also use the following command to identify SPBM VLANs. For spbm-bvlan, the attribute TYPE displays B-VLAN instead of Port. show vlan Example 7024XLS# show isis spbm ======ISIS SPBM Info ======SPBM B-VID PRIMARY NICK LSDB INSTANCE VLAN NAME TRAP ------1 1000,2000 1000 1.11.16 disable ======ISIS SPBM SMLT Info ======SPBM SMLT-SPLIT-BEB SMLT-VIRTUAL-BMAC SMLT-PEER-SYSTEM-ID
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 53 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
INSTANCE ======1 primary 00:00:00:00:00:00 0000.0000.0000
7024XLS# show vlan Id Name Type Protocol PID Active IVL/SVL Mgmt ------1 VLAN #1 Port None 0x0000 Yes IVL Yes Port Members: ALL 2 VLAN #2 Port None 0x0000 Yes IVL No Port Members: 15-18 3 VLAN #3 Port None 0x0000 Yes IVL No Port Members: NONE 4 VLAN #4 B-VLAN None 0x0000 Yes IVL No Port Members: NONE
Variable definitions The following table describes the fields in the output for the show isis spbm command.
Parameter Description SPBM INSTANCE Indicates the SPBM instance identifier. You can only create one SPBM instance. B-VID Indicates the SPBM B-VLAN associated with the SPBM instance. PRIMARY VLAN Indicates the primary SPBM B-VLAN. NICK NAME Indicates the SPBM node nickname. The nickname is used to calculate the I-SID multicast MAC address. LSDB TRAP Indicates the status of the IS-IS SPBM LSDB update trap on this SPBM instance. The default is FALSE. SMLT-SPLIT-BEB Specifies whether the switch is the primary or secondary IST peer. SMLT-VIRTUAL-MAC Specifies a virtual MAC address that can be used by both peers. SMLT-PEER-BMAC Specifies the IST peer BMAC address.
Displaying global IS-IS parameters Use the following procedure to display the global IS-IS parameters. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. Display IS-IS configuration information: show isis 3. Display the IS-IS system-id:
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 54 Comments on this document? [email protected] Displaying global IS-IS parameters
show isis system-id 4. Display IS-IS net info: show isis net Example 7024XLS#show isis ======ISIS General Info ======AdminState : enabled RouterType : Level 1 System ID : 0000.0000.0000 Max LSP Gen Interval : 900 Min LSP Gen Interval : 30 Metric : wide Overload-on-startup : 20 Overload : false Csnp Interval : 10 PSNP Interval : 2 Rxmt LSP Interval : 5 Spf-delay : 100 Num of Interfaces : 2 Num of Area Addresses : 1
7024XLS#show isis system-id ======ISIS System-Id ======SYSTEM-ID ======0014.c7e1.33df 7024XLS#show isis net ======ISIS Network Entity Title Info ======NET ======c0.2000.0000.0000.14c7.e133.df00
Variable definitions The following sections describe the fields in the outputs for the global IS-IS show commands. show isis The following table describes the fields in the output for the show isis command.
Parameter Description AdminState Indicates the administrative state of the router. RouterType Indicates the router Level: l1, l2, or l1/2. System ID Indicates the system ID. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 55 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Parameter Description Max LSP Gen Interval Indicates the maximum time between LSP updates in seconds. Min LSP Gen Interval Indicates the minimum time between LSP updates in seconds. Metric Indicates if the metric is narrow or wide. Overload-on-startup Indicates the overload-on-startup value. Overload Indicates if there is an overload condition. Csnp Interval Indicates the interval between CSNP updates in seconds. PSNP Interval Indicates the interval between PSNP updates in seconds. Rxmt LSP Interval Indicates the received LSP time interval. spf-delay Indicates the Shortest Path First delay in milliseconds. Router Name Indicates the IS-IS name of the router. Num of Interfaces Indicates the number of interfaces on the router. Num of Area Addresses Indicates the number of area addresses on the router.
show isis system-id The following table describes the fields in the output for the show isis system-id command.
Parameter Description SYSTEM-ID Shows the system ID. Output from this show command is from the global IS- IS configuration of the system ID. There is one system ID configured. The system ID is 6 bytes in length.
show isis net The following table describes the fields in the output for the show isis net command.
Parameter Description NET Shows the NET address. Output from this command is from the global IS-IS configuration of the manual area and the configuration of the system ID. There is only one manual areas defined and only one system ID. The manual area is from 1-13 bytes in length. The system ID is 6 bytes in length.
Displaying IS-IS areas Use the following procedure to display IS-IS areas. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. At the command prompt, enter the following command: show isis manual-area
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 56 Comments on this document? [email protected] Configuring SMLT parameters for SPBM
Example 7024XLS#show isis manual-area ======ISIS Manual Area Address ======
AREA ADDRESS ------c0.2000.0000.00
Variable definitions The following table describes the fields in the output for the show isis manual-area command.
Parameter Description AREA ADDRESS Shows the manual areas defined. There can only be one area. The manual area can be from 1-13 bytes in length.
Configuring SMLT parameters for SPBM Use the following procedure to configure the required Split MultiLink Trunking (SMLT) parameters to allow SPBM to interoperate with SMLT on the switch. About this task The assignment of primary and secondary roles to the IST peers is automatic. The switch with the lower system ID (between the two IST peers) is primary, and the switch with the higher system ID is secondary. SMLT virtual B-MAC is an optional configuration. If you do not configure SMLT virtual B-MAC, the system derives SMLT virtual B-MAC from the configured SMLT peer system ID and the nodal MAC of the device (IS-IS system ID). The system compares the nodal MAC of the device with the SMLT peer system ID configured and takes the small one, plus 0x01, as the SMLT virtual B-MAC. Note: The SMLT virtual B-MAC has to be a unique B-MAC in the SPBM network. If the SMLT virtual B- MAC is manually configured, make sure the same B-MAC is not being used by another SPBM switch or the same SMLT virtual B-MAC on another SMLT split BEB pair. If the SMLT virtual B- MAC is not manually configured, make sure there is no other system ID which is the same as the primary split BEB system ID plus 0x01. Good practice is to end each system ID in an SPBM network containing SMLT split BEBs with a 0 to avoid a situation where the default SMLT virtual B-MAC is the same as another B-MAC in the network. If you map a customer VLAN (C-VLAN) to a Service Instance Identifier (I-SID), you must map the same C-VLAN to I-SID on its IST peer. In case of single-homed UNIs in an SMLT setup, the same I- SID must be configured on both peers. For switched UNis, an empty C-VLAN must be configured on
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 57 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
the same I-SID on the peer. For transparent UNIs, a transparent smlt-peer UNI must be configured on the same I-SID on the peer. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To disable IS-IS on the switch, enter the following command at the command prompt: no router isis enable 3. Enter IS-IS Router Configuration mode: router isis 4. To specify the system ID of the IST peer, enter the following command at the command prompt: spbm <1–100> smlt-peer—system—id
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 58 Comments on this document? [email protected] Configuring optional SPBM parameters
7024XLS(config-isis)# router isis enable Display the configuration: 7024XLS(config-isis)# show isis spbm ======ISIS SPBM Info ======SPBM B-VID PRIMARY NICK LSDB INSTANCE VLAN NAME TRAP ======1 7,40 7 0.00.01 disable
======ISIS SPBM SMLT Info ======SPBM SMLT-SPLIT-BEB SMLT-VIRTUAL-BMAC SMLT-PEER-SYSTEM-ID INSTANCE ======1 secondary 00:14:c7:e1:33:e0 0018.b0bb.b3df
Variable definitions Use the data in the following table to use the spbm command.
Variable Value smlt-peer-system-id
Note: • If SMLT virtual B-MAC is not configured, the system derives SMLT virtual B-MAC from the configured SMLT peer system ID and the nodal MAC of the device (IS-IS system ID). The system compares the nodal MAC of the device with the SMLT peer system ID configured and takes the small one, plus 0x01, as the SMLT virtual B- MAC.
Configuring optional SPBM parameters Use the following procedure to configure optional SPBM parameters.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 59 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Configure the SPBM ethertype: spbm ethertype {0x8100 | 0x88a8} 3. Configure the optional link-state database (LSDB) trap global parameter. To configure this parameter, you must globally disable IS-IS on the switch: a. Disable IS-IS on the switch: no router isis enable b. Log on to the IS-IS Router Configuration mode: router isis c. Enable a trap when the SPBM LSDB changes: spbm <1–100> lsdb-trap enable d. Enable IS-IS on the switch: router isis enable e. Exit IS-IS Router Configuration mode: exit 4. Configure the optional SPBM interface parameters. To configure these parameters, you must disable IS-IS on the interface: a. Specify an SPBM interface to configure: interface Ethernet
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 60 Comments on this document? [email protected] Configuring optional SPBM parameters
7024XLS(config)# spbm ethertype 0x8100 7024XLS(config-isis)# no router isis enable 7024XLS(config)# router isis 7024XLS(config-isis)# spbm 1 lsdb-trap enable 7024XLS(config-isis)# router isis enable 7024XLS(config-isis)# exit 7024XLS(config)# interface Ethernet 3 7024XLS(config-if)# no isis enable 7024XLS(config-if)# isis spbm 1 interface-type pt-pt 7024XLS(config-if)# isis spbm 1 l1–metric 500 7024XLS(config-if)# isis enable
Variable definitions Use the data in the following table to use the spbm command.
Variable Value ethertype {0x8100 | 0x88a8} Configures the SPBM ethertype. The default value is 0x8100. <1–100> lsdb-trap enable Configures whether to enable or disable a trap when the SPBM LSDB changes. The default is disabled. Use the no or default options to disable LSDB traps.
Use the data in the following table to use the isis spbm command.
Variable Value <1–100> interface-type {broadcast|pt-pt} Configures the SPBM instance interface-type on the IS-IS interface located on the specified port or MLT. SPBM only supports the point-to-point (pt-pt) interface type. The default is pt-pt. Use the no or default options to set this parameter to the default value of pt-pt. <1–100> l1–metric <1–16777215> Configures the SPBM instance l1-metric on the IS-IS interface located on the specified port or MLT. The default value is 10. Use the no or default options to set this parameter to the default.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 61 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Configuring optional IS-IS global parameters Use the following procedure to configure optional IS-IS global parameters. Procedure 1. Enter IS-IS Router Configuration mode: enable configure terminal router isis 2. Configure optional IS-IS global parameters: a. Specify the Complete Sequence Number Packet (CSNP) interval in seconds: csnp-interval <1–600> b. Configure the router type globally: is-type {l1} c. Configure the maximum level, in seconds, between generated LSPs by this Intermediate System: max-lsp-gen-interval <30–900> d. Configure the IS-IS metric type: metric {wide} e. Set or clear the overload condition: overload f. Configure the overload-on-startup value in seconds: overload-on-startup <15–3600> g. Configure the Partial Sequence Number Packet (PSNP) in seconds: psnp-interval <1–120> h. Configure the minimum time between retransmission of an LSP: retransmit-lsp-interval <1–300> i. Configure the SPF delay in milliseconds: spf-delay <0–5000> j. Configure the name for the system: sys-name WORD <0–255> k. Configure the IS-IS system ID for the switch: system-id
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 62 Comments on this document? [email protected] Configuring optional IS-IS global parameters
Example 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# router isis 7024XLS(config-isis)# csnp-interval 10 7024XLS(config-isis)# is-type l1 7024XLS(config-isis)# max-lsp-gen-interval 800 7024XLS(config-isis)# metric wide 7024XLS(config-isis)# overload 7024XLS(config-isis)# overload-on-startup 30 7024XLS(config-isis)# psnp-interval 10 7024XLS(config-isis)# retransmit-lsp-interval 10 7024XLS(config-isis)# default sys-name 7024XLS(config-isis)# spf-delay 200 7024XLS(config-isis)# default system-id
Variable definitions Use the data in the following table to use the csnp-interval command.
Variable Value <1–600> Specifies the CSNP interval in seconds. This is a system level parameter that applies for level 1 CSNP generation on all interfaces. A longer interval reduces overhead, while a shorter interval speeds up convergence. The default value is 10. Use the no or default options to set this parameter to the default value of 10.
Use the data in the following table to configure the is-type command.
Variable Value {l1} Sets the router type globally: • l1: Level-1 router type The default value is l1. Use the no or default options to set this parameter to the default value of l1.
Use the data in the following table to configure the max-lsp-gen-interval command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 63 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Variable Value <30–900> Specifies the maximum interval, in seconds, between generated LSPs by this Intermediate System. The default value is 900 seconds. Use the no or default options to set this parameter to the default value of 900.
Use the data in the following table to configure the metric command.
Variable Value {wide} Specifies the IS-IS metric type. Only wide is supported in this release. The default value is wide. Use the no or default options to set this parameter to the default value of wide.
Use the data in the following table to configure the overload command.
Variable Value overload Sets or clears the overload condition. The default value is disabled. Use the no or default options to set this parameter to the default value of disabled.
Use the data in the following table to configure the overload-on-startup command.
Variable Value <15–3600> Specifies the IS-IS overload-on-startup value in seconds. The overload-on-startup value is used as a timer to control when to send out LSPs with the overload bit cleared after IS-IS startup. The default value is 20. Use the no or default options to set this parameter to the default value of 20.
Use the data in the following table to configure the psnp-interval command.
Variable Value <1–120> Specifies the PSNP interval in seconds. This is a system level parameter that applies for level 1 PSNP generation on all interfaces. A longer interval reduces overhead, while a shorter interval speeds up convergence. The default value is 2. Use the no or default options to set this parameter to the default value of 2.
Use the data in the following table to configure the retransmit-lsp-interval command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 64 Comments on this document? [email protected] Configuring optional IS-IS global parameters
Variable Value <1–300> Specifies the minimum time between retransmission of an LSP. This defines how fast the switch resends the same LSP. This is a system level parameter that applies for Level1 retransmission of LSPs. The default value is 5 seconds. Use the no or default options to set this parameter to the default value of 5.
Use the data in the following table to configure the spf-delay command.
Variable Value <0–5000> Configures the delay, in milliseconds, to pace successive Shortest Path First (SPF) runs. The timer prevents more than two SPF runs from being scheduled back-to-back. The mechanism for pacing SPF allows two back-to-back SPF runs. The default value is 100 milliseconds. Use the no or default options to set this parameter to the default value of 100 milliseconds.
Use the data in the following table to configure the sys-name command.
Variable Value WORD<0–255> Specifies a name for the system. This may be used as the host name for dynamic host name exchange in accordance with RFC 2763. By default, the system name comes from the host name configured at the system level. Use the no or default options to set this parameter to the default value (host name).
Note: In this release, no consistency checks appear when you edit sys-name on Virtual Services Platform 7000.
Use the data in the following table to configure the system-id command.
Variable Value
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 65 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Job aid
Important: After you configure the SPBM nickname and enable IS-IS, if you require a change of the system ID, you must also change the nickname. However, for naming convention purposes or configuration purposes, you might not want to change the nickname. To maintain the same nickname with a different system ID, perform the following steps: 1. Disable IS-IS. 2. Change the system ID. 3. Change the nickname to a temporary one. 4. Enable IS-IS. 5. Disable IS-IS. 6. Change the nickname to the original nickname. 7. Enable IS-IS.
Configuring optional IS-IS interface parameters Use the following procedure to configure optional IS-IS interface parameters. Procedure 1. Enter Ethernet Interface Configuration mode: enable configure terminal interface Ethernet
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 66 Comments on this document? [email protected] Configuring optional IS-IS interface parameters
isis [l1-dr-priority <0–127>] Note: This parameter is not used for SPBM because SPBM only runs on point-to-point interfaces. This parameter is for designated router election on a broadcast LAN segment, which is not supported. e. Configure the level 1 hello interval: isis [l1-hello-interval <1–600>] f. Configure the level 1 hello multiplier: isis [l1-hello-multiplier <1–600>] Example 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# interface Ethernet 3 7024XLS(config-if)# isis 7024XLS(config-if)# isis hello-auth type hmac-md5 key test 7024XLS(config-if)# isis l1–dr-priority 100 7024XLS(config-if)# isis l1–hello-interval 20 7024XLS(config-if)# isis l1–hello-multiplier 10
Variable definitions Use the data in the following table to configure the isis command.
Variable Value hello-auth type {none|simple|hmac-md5}] Specifies the authentication type used for IS-IS hello packets on [key[key WORD<1–16>] [key-id <1– the interface. type can be one of the following: 255>] • none • simple: If selected, you must also specify a key value but the key id is optional. Simple password authentication uses a text password in the transmitted packet. The receiving router uses an authentication key (password) to verify the packet. • hmac-md5: If selected, you must also specify a key value but the key-id is optional. MD5 authentication creates an encoded checksum in the transmitted packet. The receiving router uses an authentication key (password) to verify the MD5 checksum of the packet. There is an optional key ID. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 67 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Variable Value The default is none. Use the no or default options to set the hello-auth type to none. l1-dr-priority <0–127> Configures the level 1 IS-IS designated router priority to the specified value. The default value is 64. Use the no or default options to set this parameter to the default value of 64.
Note: This parameter is not used for SPBM because SPBM only runs on point-to-point interfaces. This parameter is for designated router election on a broadcast LAN segment, which is not supported. l1-hello-interval <1–600> Configures the level 1 hello interval. The default value is 9 seconds. Use the no or default options to set this parameter to the default value of 9 seconds. l1-hello-multiplier <1–600> Configures the level 1 hello multiplier. The default value is 3 seconds. Use the no or default options to set this parameter to the default value of 3 seconds.
Displaying IS-IS interface parameters Use the following procedure to display the IS-IS interface parameters. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. Display IS-IS interface configuration and status parameters (including adjacencies): show isis interface [l1] 3. Display IS-IS interface authentication configuration: show isis int-auth 4. Display IS-IS interface timers: show isis int-timers 5. Display IS-IS circuit level parameters: show isis int-ckt-level
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 68 Comments on this document? [email protected] Displaying IS-IS interface parameters
Example 7024XLS#show isis interface ======ISIS Interfaces ======IFIDX TYPE LEVEL OP-STATE ADM-STATE ADJ UP-ADJ SPBM-L1-METRIC ------Trunk: 2 pt-pt Level 1 UP UP 1 1 10 Port: 21 pt-pt Level 1 UP UP 1 1 10 7024XLS#show isis int-auth ======ISIS Interface Auth ======IFIDX AUTH-TYPE AUTH-KEYID AUTH-KEY ------Trunk: 3 none 0 Port: 21 none 0 7024XLS#show isis int-timers ======ISIS Interface Timers ======IFIDX LEVEL HELLO HELLO HELLO INTERVAL MULTIPLIER DR ------Trunk: 2 Level 1 9 3 3 Port: 21 Level 1 9 3 3
7024XLS#show isis int-ckt-level ======ISIS Circuit level parameters ======IFIDX LEVEL DIS CKTID ------Trunk: 2 Level 1 1 Port: 21 Level 1 2
Variable definitions Use the data in the following table to use the IS-IS interface show command.
Variable Value [l1] Displays the interface information for the specified level: l1.
Job aid The following sections describe the fields in the outputs for the IS-IS interface show commands. show isis interface The following table describes the fields in the output for the show isis interface command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 69 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Parameter Description IFIDX Indicates the interface index for the Ethernet or MLT interface. TYPE Indicates the type of interface configured (in this release, only pt-pt is supported). LEVEL Indicates the level of the IS-IS interface (Level 1 [default] or Level 2). OP-STATE Shows the physical connection state of the interface. ADM-STATE Shows the configured state of the interface. ADJ Shows how many adjacencies are learned through the interface. UP-ADJ Shows how many adjacencies are active through the interface. SPBM-L1–METRIC Indicates the SPBM instance Level 1 metric on the IS-IS interface.
show isis int-auth The following table describes the fields in the output for the show isis int-auth command.
Parameter Description IFIDX Shows the interface index for the Ethernet or MLT interface. AUTH-TYPE Shows the type of authentication configured for the interface. Types include: • none for no authentication. • simple for a simple password. • hmac-md5 for MD5 encryption. AUTH-KEYID Shows the authentication password configured for the interface. AUTH-KEY Shows the HMAC-MD5 key needed for encryption. This is used only for HMAC-MD5.
show isis int-timers The following table describes the fields in the output for the show isis int-auth command.
Parameter Description IFIDX Indicates the interface index for the Ethernet or MLT interface. LEVEL Indicates the IS-IS interface level. HELLO INTERVAL Indicates the interval at which a Hello packet is sent to the IS-IS network. HELLO MULTIPLIER Indicates the multiplier that is used in conjunction with the Hello Interval. HELLO DR Indicates the interval at which a Hello packet is sent to the IS-IS network if the router is a designated router (DIS).
show isis int-ckt-level The following table describes the fields in the output for the show isis int-ckt-level command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 70 Comments on this document? [email protected] Displaying the multicast FIB, unicast FIB, and unicast tree
Parameter Description IFIDX Shows the interface index for the ethernet or MLT interface. LEVEL Shows the level of the IS-IS interface (Level 1 [default] or Level 2). DIS Shows the Designated Intermediate System (DIS) of the circuit. CKT ID Displays the CKT ID.
Displaying the multicast FIB, unicast FIB, and unicast tree Use the following procedure to display SPBM IP unicast Forwarding Information Base (FIB), SPBM multicast FIB, unicast FIB, and the unicast tree. In SPBM, Backbone MAC (B-MAC) addresses are carried within the IS-IS link-state database. To do this, SPBM supports an IS-IS Type-Length-Value (TLV) that advertises the Service Instance Identifier (I-SID) and B-MAC information across the network. Each node has a System ID, which also serves as B-MAC of the switch. These B-MAC addresses are populated into the SPBM Forwarding Information Base (FIB). When the network topology is discovered and stored in the IS-IS link-state database, each node calculates shortest path trees for each source node, so that a unicast path now exists from every node to every other node. With this information, each node populates unicast information received from SPBM into the FIB for forwarding purposes. I-SIDs are only used for virtual services (Layer 2 VSNs and Layer 3 VSNs). If you only enable IP Shortcuts on the Backbone Edge Bridges, I-SIDs are never exchanged in the network as IP Shortcuts allows for Global Routing Table (GRT) IP networks to be transported across IS-IS. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. Display the SPBM multicast FIB: show isis spbm multicast-fib [vlan <0–4094>] [i-sid <1–16777215>] [nick-name
7024XLS#show isis spbm multicast-fib ======SPBM MULTICAST FIB ENTRY INFO ======
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 71 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
MCAST DA ISID BVLAN SYSID HOST-NAME OUTGOING INTERFACES ======c3:04:00:00:00:65 101 1000 0020.c040.0000 VSP7k-c4 NNI T:13 T:12 UNI T:11 V101 1/11 V101 d3:01:00:00:00:65 101 1000 0020.d010.0000 VSP7k-d1 NNI T:13 T:12 UNI T:11 V101 1/11 V101 d3:01:00:00:00:67 103 1000 0020.d010.0000 VSP7k-d1 NNI T:13 UNI T:32 V103 T:11 V103 f3:01:00:00:00:65 101 1000 0020.f010.0000 ERS4k-f1 NNI T:12 1/24 2/23 UNI T:11 V101 1/11 V101 f3:01:00:00:00:67 103 1000 0020.f010.0000 ERS4k-f1 NNI 1/24 2/23 UNI T:32 V103 T:11 V103 f3:03:00:00:00:65 101 1000 0020.f030.0000 VSP7k-f3 NNI T:13 T:12 1/24 2/23 UNI T:11 V101 1/11 V101 f3:03:00:00:00:67 103 1000 0020.f030.0000 VSP7k-f3 NNI T:13 1/24 2/23 UNI T:32 V103 T:11 V103 f3:04:00:00:00:65 101 1000 0020.f040.0000 VSP4k-f4 NNI T:13 1/24 2/23 UNI T:11 V101 1/11 V101 7024XLS#show isis spbm unicast-fib ======SPBM UNICAST FIB ENTRY INFO ======DESTINATION BVLAN SYSID HOST-NAME OUTGOING COST ADDRESS INTERFACE ------00:16:ca:23:73:df 1000 0016.ca23.73df SPBM-1 3/21 10 00:16:ca:23:73:df 2000 0016.ca23.73df SPBM-1 3/21 10 00:18:b0:bb:b3:df 1000 0018.b0bb.b3df SPBM-2 MLT-2 10 00:14:c7:e1:33:e0 1000 0018.b0bb.b3df SPBM-2 MLT-2 10 00:18:b0:bb:b3:df 2000 0018.b0bb.b3df SPBM-2 MLT-2 10
------Total number of SPBM UNICAST FIB entries 5 ------7024XLS#show isis spbm unicast-tree 1000 Node:0018.b0bb.b3df.00 (7024XLS) -> ROOT Node:0016.ca23.73df.00 (7024XLS) -> ROOT
Variable definitions
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 72 Comments on this document? [email protected] Displaying the multicast FIB, unicast FIB, and unicast tree
Use the data in the following table to use the show isis spbm multicast-fib command.
Variable Value vlan <0–4094> Displays the FIB for the specified SPBM VLAN. i-sid <1–16777215> Displays the FIB for the specified I-SID. nick-name
Use the data in the following table to use the show isis spbm unicast-fib command.
Variable Value b-mac <0x00:0x00:0x00:0x00:0x00:0x00> Displays the FIB for the specified BMAC. vlan <0–4094> Displays the FIB for the specified SPBM VLAN. summary Displays a summary of the FIB.
Use the data in the following table to use the show isis spbm unicast-tree command.
Variable Value <1–4094> Specifies the SPBM B-VLAN ID. destination
Job aid The following sections describe the fields in the outputs for SPBM multicast FIB, unicast FIB, and unicast tree show commands.
show isis spbm multicast-fib The following table describes the fields in the output for the show isis spbm multicast-fib command.
Parameter Description MCAST DA-INTERFACES Indicates the multicast destination MAC address of the multicast FIB entry. ISID Indicates the I-SID of the multicast FIB entry. BVLAN Indicates the B-VLAN of the multicast FIB entry. SYSID Indicates the system identifier of the multicast FIB entry. HOST-NAME Indicates the host name of the multicast FIB entry. OUTGOING Indicates the outgoing interface of the multicast FIB entry.
show isis spbm unicast-fib The following table describes the fields in the output for the show isis spbm unicast-fib command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 73 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Parameter Description DESTINATION ADDRESS Indicates the destination MAC Address of the unicast FIB entry. BVLAN Indicates the B-VLAN of the unicast FIB entry. SYSID Indicates the destination system identifier of the unicast FIB entry. HOST-NAME Indicates the destination host name of the unicast FIB entry. OUTGOING INTERFACE Indicates the outgoing interface of the unicast FIB entry. COST Indicates the cost of the unicast FIB entry.
Displaying IS-IS LSDB and adjacencies Use the following procedure to display the IS-IS LSDB and adjacencies. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. Display the IS-IS LSDB: show isis lsdb [level {l1|l2|l12}] [sysid
------Level-1 : 3 out of 3 Total Num of LSP Entries Level-2 : 0 out of 0 Total Num of LSP Entries
7024XLS# show isis adjacencies ======ISIS Adjacencies ======INTERFACE L STATE UPTIME PRI HOLDTIME SYSID HOST-NAME ------Mlt2 1 UP 1d 03:57:25 127 20 0018.b0bb.b3df VSP-Lab1
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 74 Comments on this document? [email protected] Displaying IS-IS LSDB and adjacencies
Port3/21 1 UP 1d 03:57:16 127 27 0016.ca23.73df VSP-Lab2 ------2 out of 2 Total Num of Adjacencies ------7024XLS>show isis lsdb detail
======ISIS LSDB (DETAIL) ======------
Level-1 LspID: 0001.bcb0.0003.00-001 SeqNum: 0x00000522 Lifetime: 1144 Chksum: 0x32f7 PDU Length: 312 Host_name: C0 Attributes: IS-Type 1 TLV:1 Area Addresses: 1 c1.3000.0000.00
TLV:22 Extended IS reachability: Adjacencies: 7 TE Neighbors: 7 0000.beb1.0007.01 (VSP0) Metric:10 SPBM Sub TLV: port id: 640 num_port 1 Metric: 10 0000.beb1.00b1.01 (VSP1) Metric:10
SPBM Sub TLV:
port id: 643 num_port 1
Metric: 10
0000.bcb1.0004.01 (C1) Metric:10
SPBM Sub TLV:
port id: 6144 num_port 1
Metric: 10
0000.beb1.00ca.01 (VSP2) Metric:10
SPBM Sub TLV:
port id: 6156 num_port 1
Metric: 10
0000.beb1.00a5.01 (VSS0) Metric:10
SPBM Sub TLV:
port id: 651 num_port 1
Metric: 10
0000.beb1.00b2.01 (VSS1) Metric:10
SPBM Sub TLV:
port id: 645 num_port 1
Metric: 10
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 75 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
0000.beb1.0008.01 (VSP1) Metric:10
SPBM Sub TLV:
port id: 652 num_port 1
Metric: 10
TLV:129 Protocol Supported: SPBM
TLV:137 Host_name: C0#
TLV:144 SUB-TLV 1 SPBM INSTANCE: Instance: 0 bridge_pri: 0 OUI: 00-33-33 num of trees: 2 vid tuple : u-bit 1 m-bit 1 ect-alg 0x80c201 base vid 1000 vid tuple : u-bit 1 m-bit 1 ect-alg 0x80c202 base vid 1001 TLV:144 SUB-TLV 3 ISID: Instance: 0 Metric: 0 B-MAC: 00-00-bc-b1-00-03 BVID:1000 Number of ISID's:8 3001(Both),3002(Rx),3003(Both),3004(Rx),4001(Both),4002( Rx),4003(Both),4004(Rx)
Instance: 0 Metric: 0 B-MAC: 00-00-bc-b1-00-03
--More-- (q = quit)
Variable definitions Use the data in the following table to use the show isis lsdb command.
Variable Value level {l1|l2|l12}] Displays the LSDB for the specified level: l1, l2, or l12.
Note: Level 1 is supported in this release. sysid
Use the data in the following table to use the clear isis command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 76 Comments on this document? [email protected] Displaying IS-IS LSDB and adjacencies
Variable Value lsdb Clears the IS-IS Link State Database (LSDB). The command clears learned LSPs only. The command does not clear local generated LSPs. As soon as the platform clears the LSDB the LSP synchronization process starts immediately and the LSDB synchronizes with its neighbors.
Job aid The following sections describe the fields in the outputs for the IS-IS LSDB and adjacencies show commands. show isis lsdb The following table describes the fields in the output for the show isis lsdb command.
Parameter Description LSP ID Indicates the LSP ID assigned to external IS-IS routing devices. LEVEL Indicates the level of the external router: l1, l2, or l12. LIFETIME Indicates the maximum age of the LSP. If the max-lsp-gen-interval is set to 900 (default) then the lifetime value begins to count down from 1200 seconds and updates after 300 seconds if connectivity remains. If the timer counts down to zero, the counter adds on an additional 60 seconds, then the LSP for that router is lost. This happens because of the zero age lifetime, which is detailed in the RFC standards. SEQNUM Indicates the LSP sequence number. This number changes each time the LSP is updated. CHKSUM Indicates the LSP checksum. This is an error checking mechanism used to verify the validity of the IP packet. HOST-NAME Indicates the hostname listed in the LSP. If the host name is not configured, then the system name is displayed.
show isis adjacencies The following table describes the fields in the output for the show isis adjacencies command.
Parameter Description INTERFACE Indicates the interface port or MLT on which IS-IS exists. L Indicates the level of the adjacent router. STATE Indicates the state of IS-IS on the interface (enabled [UP] or disabled [DOWN]). The state is non-configurable. UPTIME Indicates the length of time the adjacency has been up in ddd hh:mm:ss format. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 77 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Parameter Description PRI Indicates the priority of the neighboring Intermediate System for becoming the Designated Intermediate System (DIS). HOLDTIME Indicates the calculated hold time for the Hello (hello multiplier x hello interval); if the route is determined to be a designated router, then the product is divided by 3. SYSID Indicates the adjacent system ID of the router. HOST-NAME Indicates the hostname listed in the LSP. If the host name is not configured, then the system name is displayed.
Displaying IS-IS statistics and counters Use the following procedure to display the IS-IS statistics and counters. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. Display IS-IS system statistics: show isis statistics 3. Display IS-IS interface counters: show isis int-counters 4. Display IS-IS level 1 control packet counters: show isis int-l1-cntl-pkts Note: The current release uses level 1 IS-IS. The current release does not support level 2 IS- IS. The ACLI command show isis int-l2-contl-pkts is not supported in the current release because the IEEE 802.1aq standard currently only defines the use of one hierarchy, Level 1. 5. Clear IS-IS statistics: clear isis stats [error-counters] [packet-counters] Example 7024XLS# show isis statistics ======ISIS System Stats ======
LEVEL CORR AUTH AREA MAX SEQ SEQ NUM OWN LSP BAD ID PART LSP DB LSPs FAILS DROP EXCEEDED SKIPS PURGE LEN CHANGES OLOAD
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 78 Comments on this document? [email protected] Displaying IS-IS statistics and counters
------Level-1 0 0 0 0 1 0 0 0 0 7024XLS#show isis int-counters ======ISIS Interface Counters ======
IFIDX LEVEL AUTH ADJ INIT REJ ID LEN MAX AREA LAN DIS FAILS CHANGES FAILS ADJ CHANGES ------Mlt2 Level 1 0 1 0 0 0 0 0 Port3/21 Level 1 0 1 0 0 0 0 0
7024XLS#show isis int-l1-cntl-pkts ======ISIS L1 Control Packet counters ======IFIDX DIRECTION HELLO LSP CSNP PSNP
------Mlt2 Transmitted 13346 231 2 229 Mlt2 Received 13329 230 1 230 Port3/21 Transmitted 13340 227 2 226 Port3/21 Received 13335 226 1 227
Variable definitions Use the data in the following table to use the clear isis stats command.
Variable Value error-counters Clears IS-IS stats error-counters. packet-counters Clears IS-IS stats packet-counters.
Job aid show isis statistics The following table describes the fields in the output for the show isis statistics command.
Parameter Description LEVEL Shows the level of the IS-IS interface. CORR LSPs Shows the number of corrupted LSPs detected. AUTH FAILS Shows the number of times authentication has failed on the global level. AREA DROP Shows the number of manual addresses dropped from the area. MAX SEQ EXCEEDED Shows the number of attempts to exceed the maximum sequence number. SEQ NUM SKIPS Shows the number of times the sequence number was skipped. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 79 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Parameter Description OWN LSP PURGE Shows how many times the local LSP was purged. BAD ID LEN Shows the number of ID field length mismatches. PART CHANGES Shows the number of partition link changes. LSP DB OLOAD Show the number of times the Virtual Services Platform 7000 was in the overload state.
show isis int-counters The following table describes the fields in the output for the show isis int-counters command.
Parameter Description IFIDX Shows the interface index for the Ethernet or MLT interface. LEVEL Shows the level of the IS-IS interface (Level 1 in the current release). AUTH FAILS Shows the number of times authentication has failed per interface. ADJ CHANGES Shows the number of times the adjacencies have changed. INIT FAILS Shows the number of times the adjacency has failed to establish. REJ ADJ Shows the number of times the adjacency was rejected by another router. ID LEN Shows the ID field length mismatches. MAX AREA Shows the maximum area address mismatches. LAN DIS CHANGES Shows the number of times the DIS has changed.
show isis int-l1-cntl-pkts The following table describes the fields in the output for the show isis int-l1-cntl-pkts command.
Parameter Description IFIDX Shows the interface index for the Ethernet or MLT interface. DIRECTION Shows the packet flow (Transmitted or Received). HELLO Shows the amount of interface-level Hello packets. LSP Shows the amount of LSP packets. CSNP Shows the amount of CSNPs. PSNP Shows the amount of PSNPs.
Fabric Attach configuration using the Avaya Command Line Interface This section provides procedural information you can use to configure Fabric Attach (FA) using the Avaya Command Line Interface (ACLI).
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 80 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
Displaying FA-specific settings Use this procedure to display the FA configuration status. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. To display the FA configuration status, enter the following command: show fa agent Example This example shows sample output for the show fa agent command. Switch(config)#show fa agent
Fabric Attach Service Status: Enabled Fabric Attach Element Type: Proxy Fabric Attach Zero Touch Status: Enabled Fabric Attach Auto Provision Setting: Proxy Fabric Attach Provision Mode: Disabled Fabric Attach Client Proxy Status: Enabled Fabric Attach Standalone Proxy Status: Disabled Fabric Attach Agent Timeout: 240 seconds Fabric Attach Extended Logging Status: Disabled Fabric Attach Primary Server Id:
Displaying Fabric Attach elements Use this procedure to display discovered Fabric Attach elements. Procedure 1. Enter Privileged EXEC mode: enable 2. To display the discovered FA elements, enter the following: show fa elements [
Unit/ Element Element Element Port Type Subtype VLAN Auth System ID ------1/10 Client Wireless AP (Type 1) 1 AP 00:22:67:00:58:00:00:00:01:0a MLT2 Server Server (Auth) 1234 AP fc:a8:41:fa:f8:00:20:00:00:02
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 81 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
2/10 Client Wireless AP (Type 1) 0 NA 64:a7:dd:03:38:29:00:00:00:01 3/12 Client Wireless AP (Type 1) 0 AF 64:07:34:03:12:ac:00:00:00:08 Variable definitions The following table describes the parameters for show fa elements command.
Variable Value
Configuring external client proxy support Use this procedure to enable or disable external client proxy support. About this task Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To enable external client proxy support, enter either of the following commands: fa proxy OR default fa proxy 3. To disable external client proxy support, enter the following command: no fa proxy
Configuring FA on switch ports Use this procedure to enable or disable the FA operation on one or more switch ports. Note: Disabling FA at the port level causes FA Client, FA Proxy and FA Server data associated with the port, such as I-SID/VLAN binding data or discovered element data, to be immediately flushed. A link-down event also causes port-specific FA Client data to be cleared.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 82 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To configure the FA operation on switch ports, enter the following command: [no][default] fa port-enable [
Displaying switch port FA operation status Use this procedure to display per-port FA operation status. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. To display FA configuration information, enter the following command: show fa port-enable [
Unit Port IfIndex Trunk Service Advertisement Authentication ------1 1 1 Enabled Enabled 1 2 2 Enabled Enabled 1 3 3 Enabled Enabled 1 4 4 2 Enabled Enabled 1 5 5 2 Enabled Enabled 1 6 6 Enabled Enabled Variable definitions The following table describes the parameters for the show fa port-enable [
Variable Value [
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 83 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Variable Value disabled-auth Displays only authentication disabled ports.
Configuring the FA authentication key Use the following command to configure the FA authentication key on specified ports. Note: You can configure the FA authentication key only on secure images. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Configure the FA authentication key: [default] fa authentication-key
Variable Value
Configuring FA message authentication support Use the following procedure to configure the FA message authentication support on specified ports. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Enable the FA message authentication support: fa message-authentication
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 84 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
default fa message-authentication Note: The default setting is enabled. 4. (Optional) Disable the FA message authentication support: no fa message-authentication Variable Definitions The following table describes the parameters for the fa message-authentication command.
Variable Value
Configuring FA VLANs Use this procedure to create or delete FA VLANs on an FA Proxy or FA Standalone Proxy. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To create FA VLANs, enter the following command: fa vlan
VLAN Source Status ------6 Proxy Pending
Binding Count: 1 Variable Definitions The following table describes the parameters for the fa vlan command.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 85 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Variable Value [
Displaying Fabric Attach VLAN information Use this procedure to display Fabric Attach-specific VLAN information. Procedure 1. Enter Privileged EXEC mode: enable 2. To display Fabric Attach VLAN information, enter the following command: show fa vlan [<1-4094>] Example The following example displays sample output for the show fa vlan command. Switch(config)#show fa vlan
VLAN Source Status ------1007 Proxy Pending 1008 Proxy Pending
Enabling or disabling FA Zero Touch support Use this procedure to enable or disable the global FA Zero Touch support on an FA Proxy, FA Server, or FA Standalone Proxy. By default, FA Zero Touch support is enabled. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To enable FA Zero Touch support on an FA Proxy, FA Server, or FA Standalone Proxy, enter the following command: fa zero-touch 3. To disable FA Zero Touch support on an FA Proxy, FA Server, or FA Standalone Proxy, enter the following command: no fa zero-touch 4. To reset the FA Zero Touch support state to default, enter the following command:
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 86 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
default fa zero-touch
Configuring FA Zero Touch options Use this procedure to configure FA Zero Touch option settings.. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To enable an FA Zero Touch option, enter the following command: fa zero-touch-options {auto-pvid-mode-fa-client | auto-trusted-mode- fa-client | ip-addr-dhcp} 3. To disable a specific FA Zero Touch option, enter the following command: no fa zero-touch-options {auto-pvid-mode-fa-client | auto-trusted- mode-fa-client | ip-addr-dhcp} 4. To clear all FA Zero Touch option settings, enter the following command: default fa zero-touch-options Variable Definitions The following table describes the parameters for the fa zero-touch-options command.
Variable Value auto-pvid-mode-fa-client Automates client PVID/Mgmt VLAN updates. auto-trusted-mode-fa-client Automates the FA Client connection. ip-addr-dhcp Automates DHCP IP address acquisition.
Displaying FA Zero Touch option settings Use this procedure to verify the FA Zero Touch option settings. Procedure 1. Enter Privileged EXEC mode: enable 2. To display the FA Zero Touch option settings, enter the following command: show fa zero-touch-options
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 87 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
Example The following is an example of configuring and displaying FA Zero Touch options. Switch(config)#fa zero-touch-options auto-trusted-mode-fa-client Switch(config)#show fa zero-touch-options
Fabric Attach Zero Touch Options:
auto-trusted-mode-fa-client
Configuring FA Standalone Proxy mode Use this procedure to enable or disable the FA Standalone Proxy mode on the switch. Before you begin Disable SPBM globally on switch. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To enable FA Standalone Proxy mode, enter the following command: fa standalone-proxy 3. To disable FA Standalone Proxy mode, enter the following command: no fa standalone-proxy 4. To restore the FA Standalone Proxy mode to default, enter the following command: default fa standalone-proxy Note: FA Standalone Proxy mode is disabled by default on an FA Proxy.
Displaying FA uplink values Use this procedure to display FA static uplink values used in FA Standalone Proxy mode. Procedure 1. Enter Privileged EXEC mode: enable 2. To display FA static uplink values, enter the following command: show fa uplink
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 88 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
Example The following example displays sample output for the show fa uplink command. Switch(config)#show fa uplink
Fabric Attach Static Uplinks: port 21 trunk 0
Configuring the static uplink for FA Standalone Proxy mode Use this procedure to specify a port or trunk to use as a static uplink associated with FA Standalone Proxy operation. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To specify a port uplink or a trunk uplink to use in FA Standalone Proxy mode, enter the following command: fa uplink {port
Variable Value
Configuring Fabric Attach extended-logging Use the following procedure to configure Fabric Attach extended-logging. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Enable Fabric Attach extended-logging: fa extended-logging
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 89 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using ACLI
3. (Optional) Disable Fabric Attach extended-logging: no fa extended-logging
Configuring the FA timeout Use this procedure to configure the FA timeout. The default is 75 seconds. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To configure the FA timeout, enter the following command: fa timeout <45–480> 3. To reset the timeout to its default value, enter the following command: default fa timeout
Creating an I-SID-to-VLAN assignment on an FA proxy About this task Use this procedure to create an association between an I-SID and a VLAN on an FA Proxy, when SPBM is disabled on switch. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To create an I-SID-to-VLAN assignment, enter the following command: i-sid <1–16777214> vlan <1–4094> Result Each FA Proxy I-SID-to-VLAN assignment creates a C-VLAN User Network Interface (UNI) when the assignment is active and accepted by an FA server. Example The following example creates an association between I-SID 600 and VLAN 3: Switch(config)#i-sid 600 vlan 3 Switch(config)#
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 90 Comments on this document? [email protected] Fabric Attach configuration using the Avaya Command Line Interface
Variable definitions The following table describes the parameters for the i-sid <1–16777214> vlan <1–4094> command
Variable Value i-sid <1-16777214> Specifies the I-SID to associate with the selected VLAN. Values range from 1 to 16777214. vlan <1-4094> Specifies the VLAN to associate with the selected I-SID. Values range from 1 to 4094.
Displaying I-SID-to-VLAN assignment information Use this procedure to display information about I-SID-to-VLAN assignments. Procedure 1. Log on to ACLI to enter User EXEC mode. 2. To display I-SID-to-VLAN assignment information, enter the following command: show fa i-sid [<1–16777214>] Example The following example displays sample output for the show fa i-sid command. Switch#show fa i-sid
I-SID VLAN Source Status ------500 5 Proxy Pending 600 6 Proxy Pending 13849 138 Proxy Pending
16000000 1000 Proxy Pending Variable definitions The following table describes the parameters for the show fa i-sid [<1–16777214>] command
Variable Value [<1-16777214>] Specifies the Fabric Attach I-SID for which to display I-SID-to- VLAN assignment information. Values range from 1 to 16777214. If you do not specify a I-SID value, the switch displays information for all configured I-SID-to-VLAN assignments.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 91 Comments on this document? [email protected] Chapter 5: SPBM and IS-IS infrastructure configuration using EDM
This section provides procedures to configure basic SPBM and IS-IS infrastructure using Enterprise Device Manager (EDM).
Configuring required SPBM and IS-IS parameters Use the following procedure to configure the minimum required SPBM and IS-IS parameters to allow SPBM to operate on the switch. SPBM uses the Intermediate-System-to-Intermediate-System (IS-IS) link state routing protocol to provide a loop free Ethernet topology that creates a shortest path topology from every node to every other node in the network based on node MAC addresses. About this task When you enable SPBM, the switch automatically configures the QoS agent buffer mode to spb- scaled. For more information about this mode, see Configuring Quality of Service on Avaya Virtual Services Platform 7000 Series, NN47202–504. Procedure 1. From the navigation tree, select Configuration > VLAN > VLANs. 2. Click the Basic tab. 3. Click Insert. 4. In the Type field, click spbm-bvlan. 5. Click Insert to create the primary B-VLAN. 6. Click Insert. 7. In the Type field, click spbm-bvlan. 8. Click Insert to create the secondary B-VLAN. 9. In the navigation tree, select Configuration > IS-IS > SPBM. 10. From the Globals tab, select enable to enable SPBM globally, and click Apply. Note: When you enable SPBM, the switch reboots.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 92 Comments on this document? [email protected] Configuring required SPBM and IS-IS parameters
A reboot can happen to enable the SPB loopback port. 11. Click the SPBM tab. 12. Click Insert to create an SPBM instance (in this release, only one SPBM instance is supported). 13. In the Id field, specify the SPBM instance ID. 14. In the NodeNickName field, specify the node nickname (valid value is 2.5 bytes in the format
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 93 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
31. In the Interfaces SPBM tab, click Insert. 32. In the Spbmid field, specify a SPBM identifier. 33. In the State field, select enable. 34. Click Insert to enable the SPBM instance on the IS-IS circuit. 35. Under the IS-IS tab, click the Interfaces tab. 36. In the AdminState field for the IS-IS circuity entry, select on to enable the IS-IS circuit. 37. Click Apply. 38. From the navigation tree, select Configuration > VLAN > VLANs. 39. Click the Basic tab. 40. Select the row for VLAN#1, and double-click the PortMembers cell. 41. Click the port number you specified for the IS-IS interface to remove it from the default VLAN, and click Ok. 42. In the toolbar, click Apply. Note: Ensure to remove the port specified for the IS-IS interface from all non-SPBM VLANs. If a rear-port is specified for the IS-IS interface, you can remove the rear-port from a VLAN membership using ACLI. After you configure the basic infrastructure, see Layer 2 VSN configuration using EDM on page 152 to configure Layer 2 services.
SPBM field descriptions
Note: The following tables list the minimum required SPBM and IS-IS parameters to allow SPBM to operate on the switch. For more detailed information on all of the parameters see the procedures that follow. For more information on how to configure VLANs, see Configuring Layer 2 on Avaya Virtual Services Platform 7000 Series, NN47202–502 Use the data in the following table to use the SPBM > Globals tab.
Name Description GlobalEnable Enables or disables SPBM globally. GlobalEtherType Specifies the global Ethertype value as 0x8100 or 0x88a8. The default value is 0x8100.
Use the data in the following table to use the SPBM > SPBM tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 94 Comments on this document? [email protected] Configuring required SPBM and IS-IS parameters
Name Description Id Specifies the SPBM instance ID. In this release, only one SPBM instance is supported. NodeNickName Specifies a nickname for the SPBM instance globally. Valid value is 2.5 bytes in the format
Use the data in the following table to use the VLANs > Basic tab.
Name Description Type Specifies the type of VLAN: • byPort • byProtocolId • spbm-bvlan • spbm-switchedUni
Use the data in the following table to use the IS-IS > Manual Area tab.
Name Description AreaAddr Specifies the IS-IS manual area. Valid value is 1–13 bytes in the format
Use the data in the following table to use the IS-IS > Globals tab.
Name Description AdminState Specifies the global status of IS-IS on the switch: on or off. The default is off. LevelType Sets the router type globally: • level1 — Level-1 router type • level2 — Level-2 router type • Level1and2 — Level–1 and Level-2 router type
Note: level2 and level1and2 is not supported in this release. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 95 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description ID Specifies the system ID. Valid value is a 6–byte value in the format
Note: Although it is not strictly required for SPBM operation, Avaya recommends that you change the IS-IS system ID from the default B-MAC value to a recognizable address to easily identify a switch (using the ID field under the IS- IS Globals tab) . This helps to recognize source and destination addresses for troubleshooting purposes.
Use the data in the following table to use the IS-IS > Interfaces tab.
Name Description IfIndex The identifier of this circuit, unique within the Intermediate System. This value is for SNMP Indexing purposes only and need not have any relation to any protocol value. This object cannot be modified after creation. AdminState Specifies the administrative state of the circuit: on or off. The default is off.
Use the data in the following table to use the SPBM > Interface SPBM tab.
Name Description State Specifies whether the SPBM interface is enabled or disabled.
Job aid
Important: After you configure the SPBM nickname and enable IS-IS, if you require a change of the system ID, you must also change the nickname. However, for naming convention purposes or configuration purposes, you might not want to change the nickname. To maintain the same nickname with a different system ID, perform the following steps: 1. Disable IS-IS. 2. Change the system ID. 3. Change the nickname to a temporary one. 4. Enable IS-IS. 5. Disable IS-IS.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 96 Comments on this document? [email protected] Displaying the SPBM I-SID information
6. Change the nickname to the original nickname. 7. Enable IS-IS.
Displaying the SPBM I-SID information Use the following procedure to display the SPBM Service Instance Identifier (I-SID) information. The SPBM B-MAC header includes an I-SID with a length of 24 bits. This I-SID can be used to identify and transmit any virtualized traffic in an encapsulated SPBM frame. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the I-SID tab.
I-SID field descriptions Use the data in the following table to use the I-SID tab.
Name Description SysId Indicates the system identifier. Vlan Indicates the B-VLAN where this I-SID was configured or discovered. McastDestMacAddr Indicates the multicast destination MAC address based on the NickName and I-SID to build the Multicast-FIB. Isid Indicates the IS-IS SPBM I-SID identifier. NickName Indicates the nickname of the node where this I-SID was configured or discovered. HostName Indicates the host name listed in the LSP, or the system name if the host name is not configured. Type Indicates the SPBM I-SID type; either configured or discovered.
Displaying Level 1 Area information Use the following procedure to display Level 1 area information. IS-IS provides support for hierarchical routing, which enables you to partition large routing domains into smaller areas. IS-IS uses a two-level hierarchy, dividing the domain into multiple Level 1 areas and one Level 2 area. The Level 2 area serves as backbone of the domain, connecting to all the Level 1 areas.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 97 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Important: The IEEE 802.1aq standard currently only defines the use of one hierarchy, Level 1. Level 2 function is disabled in the current release. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click IS-IS. 3. Click the L1 Area tab.
L1 Area field descriptions Use the data in the following table to use the L1 Area tab.
Name Description AreaAddr Specifies an area address reported in a Level 1 link-state packets (LSP) generated or received by this Intermediate System.
Configuring SMLT parameters for SPBM Use the following procedure to configure the required Split MultiLink Trunking (SMLT) parameters to allow SPB to interoperate with SMLT on the switch. About this task The assignment of primary and secondary roles to the IST peers is automatic. The switch with the lower system ID (between the two IST peers) is primary, and the switch with the higher system ID is secondary. On Virtual Services Platform 7000 Series, when you map a customer VLAN (C-VLAN) to a Service Instance Identifier (I-SID), you must add the C-VLAN to both SMLT split BEBs. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS > SPBM. 2. Click the SPBM tab. 3. Use the SmltSplitBEB field to see if the switch is the primary or secondary IST peer. 4. Type a MAC address in the SmltBmac field. 5. Type a B-MAC address in the SmltPeerSysId field. 6. Click Apply.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 98 Comments on this document? [email protected] Enabling or disabling SPBM globally
SPBM field descriptions Use the data in the following table to use the SPBM tab.
Name Description Id Specifies the SPBM instance ID. In this release, only one SPBM instance is supported. NodeNickName Specifies a nickname for the SPBM instance globally. Valid value is 2.5 bytes in the format
Enabling or disabling SPBM globally Use the following procedure to enable or disable SPBM at the global level. SPBM uses the Intermediate-System-to-Intermediate-System (IS-IS) link state routing protocol to provide a loop free Ethernet topology that creates a shortest path topology from every node to every other node in the network based on node MAC addresses. About this task When you enable SPBM, the switch automatically configures the QoS agent buffer mode to spb- scaled. For more information about this mode, see Configuring Quality of Service on Avaya Virtual Services Platform 7000 Series, NN47202–504.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 99 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the Globals tab. 4. To enable or disable SPBM, click enable or disable in the GlobalEnable field. 5. To configure the global ethertype value, click the desired option in the GlobalEtherType field. 6. Click Apply.
Globals field descriptions Use the data in the following table to use the Globals tab.
Name Description GlobalEnable Enables or disables SPBM globally. The default is disabled. GlobalEtherType Specifies the global ethertype value as 0x8100 or 0x88a8. The default value is 0x8100.
Configuring SPBM parameters Use the following procedure to configure SPBM global parameters. SPBM uses the Intermediate- System-to-Intermediate-System (IS-IS) link state routing protocol to provide a loop free Ethernet topology that creates a shortest path topology from every node to every other node in the network based on node MAC addresses. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the SPBM tab. 4. To create an SPBM instance, click Insert. 5. Configure the SPBM parameters. 6. Click Apply.
SPBM field descriptions Use the data in the following table to use the SPBM tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 100 Comments on this document? [email protected] Displaying SPBM nicknames
Name Description Id Specifies the SPBM instance ID. In this release, only one SPBM instance is supported. NodeNickName Specifies a nickname for the SPBM instance globally. Valid value is 2.5 bytes in the format
Displaying SPBM nicknames Use the following procedure to display SPBM nicknames. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the Nick Names tab.
Nickname field descriptions Use the data in the following table to use the NickName tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 101 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description Level Indicates the level at which this LSP appears. ID Indicates the 8 byte LSP ID, consisting of the SystemID, Circuit ID, and Fragment Number. LifetimeRemain Indicates the remaining lifetime in seconds for the LSP. NickName Indicates the nickname for the SPBM node. HostName Indicates the hostname listed in the LSP, or the system name if the host name is not configured.
Configuring interface SPBM parameters Use the following procedure to configure SPBM interface parameters. Procedure 1. In the navigation tree, expand the following folders:Configuration > IS-IS. 2. Click SPBM. 3. Click the Interface SPBM tab. 4. Configure the SPBM interface parameters. 5. Click Apply.
Interface SPBM field descriptions Use the data in the following table to use the Interface SPBM tab.
Name Description Index Specifies an Index value for the SPBM interface. Id Specifies an ID value for the SPBM interface. State Specifies whether the SPBM interface is enabled or disabled. Type Configures the SPBM instance interface-type on the IS-IS interface located on the specified port or MLT: ptpt or bcast. In this release, only the point-to-point (ptpt) interface type is supported. WideL1Metric Configures the SPBM instance l1-metric on the IS-IS interface located on the specified port or MLT. The default value is 10.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 102 Comments on this document? [email protected] Configuring SPBM on an interface
Configuring SPBM on an interface Use the following procedure to configure SPBM on an interface. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click IS-IS. 3. Click the Interfaces tab. 4. Click the SPBM button. 5. In the Interfaces SPBM tab, click Insert. 6. Click Insert.
Interface SPBM field descriptions Use the data in the following table to use the Interfaces SPBM tab.
Name Description Index Specifies an Index value for the SPBM interface. Id Specifies the SPBM instance ID. State Specifies whether the SPBM interface is enabled or disabled. The default is disabled. Type Configures the SPBM instance interface-type on the IS-IS interface located on the specified port or MLT. In this release, only the pt-pt interface type is supported. The default is pt-pt. WideL1Metric Configures the SPBM instance l1-metric on the IS-IS interface located on the specified port or MLT. The default value is 10.
Displaying the unicast FIB Use the following procedure to display the unicast FIB. In SPBM, B-MAC addresses are carried within the IS-IS link-state database. SPBM supports an IS- IS TLV that advertises the I-SID and B-MAC information across the network. Each node has a System ID, which also serves as Backbone MAC address (B-MAC) of the switch. The Backbone MAC addresses are populated into the SPBM VLAN Forwarding Information Base (FIB). When the network topology is discovered and stored in the IS-IS link-state database, each node calculates shortest path trees for each source node. A unicast path now exists from every node to every other node. With this information, each node populates unicast information received from SPBM into the FIB for forwarding purposes.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 103 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the Unicast FIB tab.
Unicast FIB field descriptions Use the data in the following table to use the Unicast FIB tab.
Name Description SysId Specifies the system ID of the node where the unicast FIB entry originated. Vlan Specifies the VLAN of the unicast FIB entry. DestinationMacAddr Specifies the destination MAC Address of the unicast FIB entry. OutgoingPort Specifies the outgoing port of the unicast FIB entry. HostName Specifies the host name of the node where unicast FIB entry originated. Cost Specifies the cost of the unicast FIB entry.
Displaying the multicast FIB Use the following procedure to display the multicast FIB. In SPBM, B-MAC addresses are carried within the IS-IS link-state database. SPBM supports an IS- IS TLV that advertises the I-SID and B-MAC information across the network. Each node has a System ID, which also serves as Backbone MAC address (B-MAC) of the switch. The B-MAC addresses are populated into the SPBM VLAN Forwarding Information Base (FIB). When the network topology is discovered and stored in the IS-IS link-state database, each node calculates shortest path trees for each source node. A unicast path now exists from every node to every other node. With this information, each node populates unicast information received from SPBM into the FIB for forwarding purposes. The multicast FIB is not produced until virtual services are configured and learned. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the Multicast FIB tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 104 Comments on this document? [email protected] Displaying LSP summary information
Multicast FIB field descriptions Use the data in the following table to use the Multicast FIB tab.
Name Description SysId System ID of the node where the multicast FIB entry originated. Vlan VLAN of the multicast FIB entry. McastDestMacAddr Multicast destination MAC Address of the multicast FIB entry Isid I-SID of the multicast FIB entry. OutgoingPorts NNI port of the multicast FIB entry. HostName Host name of the node where the multicast FIB entry originated.
Displaying LSP summary information Use the following procedure to display link-state packet (LSP) summary information. Link State Packets (LSP) contain information about the state of adjacencies or defined and distributed static routes. Intermediate System to Intermediate System (IS-IS) exchanges this information with neighboring IS-IS routers at periodic intervals. Procedure 1. From the navigation tree, choose Configuration > IS-IS. 2. Click IS-IS. 3. Click the LSP Summary tab.
LSP Summary field descriptions Use the data in the following table to use the LSP Summary tab.
Name Description Level Specifies the level at which this LSP appears. ID Specifies the 8 byte LSP ID, consisting of the SystemID, Circuit ID, and Fragment Number. Seq Specifies the sequence number for this LSP. Checksum Specifies the 16 bit Fletcher Checksum for this LSP. LifetimeRemain The remaining lifetime in seconds for this LSP. HostName The hostname listed in LSP, or the system name if host name is not configured.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 105 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Displaying IS-IS adjacencies Use the following procedure to display IS-IS adjacency information. The platform sends IS-IS Hello (IIH) packets to discover IS-IS neighbors and establish and maintain IS-IS adjacencies. The platform continues to send IIH packets to maintain the established adjacencies. For two nodes to form an adjacency the B-VLAN pairs for the primary B-VLAN and secondary B-VLAN must match. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click IS-IS. 3. Click the Adjacency tab.
Adjacency field descriptions Use the data in the following table to use the Adjacency tab.
Name Description CircIndex Specifies the circuit identifier for the IS-IS interface. This value is for SNMP indexing purposes only. Index A unique value identifying the IS adjacency from all other such adjacencies on this circuit. This value is automatically assigned by the system when the adjacency is created. IfIndex Specifies the IS-IS interface on which the adjacency is found. Usage Specifies how the adjacency is used. On a point-to-point link, this can be level 1 and 2. But on a LAN, the usage is level 1 on the adjacency between peers at level 1, and level 2 for the adjacency between peers at level 2. State Specifies the state of the adjacency: • down • initializing • up • failed LastUpTime Indicates when the adjacency most recently entered the state up, measured in hundredths of a second since the last re-initialization of the network management subsystem. Displays 0 if the adjacency has never been in state up. NeighPriority Specifies the priority of the neighboring Intermediate System for becoming the Designated Intermediate System. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 106 Comments on this document? [email protected] Configuring IS-IS globally
Name Description HoldTimer Specifies the holding time in seconds for this adjacency. This value is based on received IS-IS Hello (IIH) PDUs and the elapsed time since receipt. NeighSysID Specifies the system ID of the neighboring Intermediate System. HostName Specifies the host name listed in the LSP, or the system name if host name is not configured.
Configuring IS-IS globally Use the following procedure to configure IS-IS global parameters. SPBM uses IS-IS to discover network topology, build shortest path trees between network nodes, and communicate network information in the control plane. Procedure 1. In the navigation tree, expand the following folders:Configuration > IS-IS. 2. Click IS-IS. 3. From the Globals tab, configure the global IS-IS parameters. 4. Click Apply.
Globals field descriptions Use the data in the following table to use the Globals tab.
Name Description AdminState Specifies the global status of IS-IS on the switch: on or off. The default is off. LevelType Sets the router type globally: • level1: Level-1 router type • level1and2: Level–1/2 router type is not supported in this release. The default value is level1. ID Specifies the IS-IS system ID for the switch. Valid value is a 6– byte value in the format
Important: After you configure the SPBM nickname and enable IS-IS, if you require a change of the system ID, you must also Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 107 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description
change the nickname. However, for naming convention purposes or configuration purposes, you might not want to change the nickname. To maintain the same nickname with a different system ID, perform the following steps: 1. Disable IS-IS. 2. Change the system ID. 3. Change the nickname to a temporary one. 4. Enable IS-IS. 5. Disable IS-IS. 6. Change the nickname to the original nickname. 7. Enable IS-IS. MaxLSPGenInt Specifies the maximum interval, in seconds, between generated LSPs by this Intermediate system. The value must be greater than any value configured for RxmtLspInt. The default value is 900 seconds. CsnpInt Specifies the Complete Sequence Number Packet (CSNP) interval in seconds. This is a system level parameter that applies for L1 CSNP generation on all interfaces. The default value is 10. RxmtLspInt Specifies the minimum time between retransmission of an LSP. This defines how fast the switch resends the same LSP. This is a system level parameter that applies for L1 retransmission of LSPs. The default value is 5 seconds. PSNPInterval Specifies the Partial Sequence Number Packet (PSNP) interval in seconds. This is a system level parameter that applies for L1 PSNP generation on all interfaces. The default value is 2. SpfDelay Specifies the SPF delay in milliseconds. This value is used to pace successive SPF runs. The timer prevents two SPF runs from being scheduled very closely. The default value is 100 milliseconds. HostName Specifies a name for the system. This may be used as the host name for dynamic host name exchange in accordance with RFC 2763. By default, the system name comes from the host name configured at the system level.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 108 Comments on this document? [email protected] Configuring system level IS-IS parameters
Configuring system level IS-IS parameters Use the following procedure to configure system-level IS-IS parameters. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS > IS-IS. 2. Click the System Level tab. 3. Configure the IS-IS system level parameters. 4. Click Apply.
System Level field descriptions Use the data in the following table to use the System Level tab.
Name Description Index Specifies the level: l1 or l2. In this release, only l1 is supported. State Specifies the state of the database at this level. The value 'off' indicates that IS-IS is not active at this level. The value 'on' indicates that IS-IS is active at this level, and not overloaded. The value 'waiting' indicates a database that is low on an essential resources, such as memory. The administrator may force the state to 'overloaded' by setting the object SetOverload. If the state is 'waiting' or 'overloaded', you originate LSPs with the Overload bit set. MinLSPGenInt Specifies the minimum time between successive generation of LSPs with the same LSPID. This a system level parameter that applies to both L1 and L2 LSP generation. The default value is 30 seconds. SetOverload Sets or clears the overload condition. The possible values are true or false. The default value is false. SetOverloadUntil Sets the IS-IS overload-on-startup value in seconds. The overload-on-startup value is used as a timer to control when to send out LSPs with the overload bit cleared after IS-IS startup.
Note: If you configure SetOverloadUntil to a number other than zero, then the overload bit is set at this level when the AdminState variable goes to the state 'on' for this Intermediate System. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 109 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description
After the SetOverloadUntil seconds elapse, the overload flag remains set if the implementation runs out of memory or if you configured it manually using SetOverload to true. If SetOverload is false, the system clears the overload bit after SetOverloadUntil seconds elapse, if the system has not run out of memory. The default value is 20. MetricStyle Specifies the IS-IS metric type. Available values are narrow, wide or both. Only wide is supported in this release.
Configuring IS-IS interfaces Use the following procedure to configure IS-IS interfaces. SPBM uses IS-IS to discover network topology, build shortest path trees between network nodes, and communicate network information in the control plane. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click IS-IS. 3. Click the Interfaces tab. 4. Configure the IS-IS interface parameters. 5. Click Apply.
Interfaces field descriptions Use the data in the following table to use the Interfaces tab.
Name Description Index The identifier of this circuit, unique within the Intermediate System. This value is for SNMP Indexing purposes only and need not have any relation to any protocol value. IfIndex Specifies the interface on which the circuit is configured (port or MLT). Type Specifies the IS-IS circuit type. In this release, only the point-to- point (PtToPt) interface type is supported. AdminState Specifies the administrative state of the circuit: on or off. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 110 Comments on this document? [email protected] Configuring IS-IS interface level parameters
Name Description OperState Specifies the operational state of the circuit. AuthType Specifies the authentication type: • none • simple: If selected, you must also specify a key value but the key id is optional. Simple password authentication uses a text password in the transmitted packet. The receiving router uses an authentication key (password) to verify the packet. • hmac-md5: hmac-md5: If selected, you must also specify a key value but the key-id is optional. MD5 authentication creates an encoded checksum in the transmitted packet. The receiving router uses an authentication key (password) to verify the MD5 checksum of the packet. There is an optional key ID. The default is none. AuthKey Specifies the authentication key. KeyId Specifies the authentication key ID. LevelType Specifies the router type globally: • level1: Level-1 router type • level 1and2: Level–1/2 router type. Not supported in this release. The default value is level1. NumAdj Specifies the number of adjacencies on this circuit. NumUpAdj Specifies the number of adjacencies that are up.
Configuring IS-IS interface level parameters Use the following procedure to configure IS-IS interface level parameters. SPBM uses IS-IS to discover network topology, build shortest path trees between network nodes, and communicate network information in the control plane. Procedure 1. From the navigation tree, choose Configuration > IS-IS. 2. Click IS-IS. 3. Click the Interfaces Level tab. 4. Configure the IS-IS interface level parameters. 5. Click Apply.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 111 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Interfaces Level field descriptions Use the data in the following table to use the Interfaces Level tab.
Name Description Index Indicates the identifier of the circuit, unique within the Intermediate System. This value is for SNMP Indexing purposes only and does not have any relation to any protocol value. LevelIndex Specifies the router type globally: • l1: Level1 router type • l12: Level1/Level2 router type. Not supported in this release. The default value is l1. ISPriority Specifies an integer sub-range for IS-IS priority. Range of 0–127. The default is 0 for SPBM interfaces.
Note: ISPriority only applies to broadcast interfaces. HelloTimer Specifies the level 1 hello interval. Specifies the maximum period, in seconds, between IS-IS Hello Packets (IIH) PDUs on multiaccess networks at this level for LANs. The value at Level1 is used as the period between Hellos on Level1/Level2 point to point circuits. Setting this value at Level 2 on an Level1/Level2 point-to-point circuit results in an error of InconsistentValue. The default value is 9 seconds. HelloMultiplier Specifies the level 1 hello multiplier. The default value is 3 seconds. DRHelloTimer Specifies the period, in seconds, between Hello PDUs on multiaccess networks when this Intermediate System is the Designated Intermediate System. The default is 3 seconds.
Configuring an IS-IS Manual Area Use the following procedure to configure an IS-IS manual area. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click IS-IS. 3. Click the Manual Area tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 112 Comments on this document? [email protected] Displaying IS-IS system statistics
4. Click Insert. 5. Specify an Area Address in the AreaAddr field, and click Insert.
Manual Area field descriptions Use the data in the following table to use the Manual Area tab.
Name Description AreaAddr Specifies the IS-IS manual area. Valid value is 1-13 bytes in the format
Displaying IS-IS system statistics Use the following procedure to display Intermediate-System-to-Intermediate-System (IS-IS) system statistics. Procedure 1. In the navigation tree, choose Configuration > IS-IS. 2. Click Stats. 3. Click the System Stats tab.
System Stats field descriptions Use the data in the following table to use the System Stats tab.
Name Description CorrLSPs Indicates the number of corrupted in-memory link-state packets (LSPs) detected. LSPs received from the wire with a bad checksum are silently dropped and not counted. AuthFails Indicates the number of authentication key failures recognized by this Intermediate System. LSPDbaseOloads Indicates the number of times the LSP database has become overloaded. ManAddrDropFromAreas Indicates the number of times a manual address has been dropped from the area. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 113 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description AttmptToExMaxSeqNums Indicates the number of times the IS has attempted to exceed the maximum sequence number. SeqNumSkips Indicates the number of times a sequence number skip has occurred. OwnLSPPurges Indicates the number of times a zero-aged copy of the system's own LSP is received from some other node. IDFieldLenMismatches Indicates the number of times a PDU is received with a different value for ID field length to that of the receiving system. PartChanges Indicates partition changes. AbsoluteValue Displays the counter value. Cumulative Displays the total value since you opened the Stats tab. Average/sec Displays the average value for each second. Minimum/sec Displays the minimum value for each second. Maximum/sec Displays the maximum value for each second. LastVal/sec Displays the last value for each second.
Displaying IS-IS interface counters Use the following procedure to display IS-IS interface counters. Procedure 1. From the navigation tree, choose Configuration > IS-IS. 2. Click Stats. 3. Click the Interface Counters tab.
Interface Counters field descriptions Use the data in the following table to use the Interface Counters tab.
Name Description Index Shows a unique value identifying the IS-IS interface. uitType Shows the level type for the IS-IS interface. AdjChanges Shows the number of times an adjacency state change has occurred on this circuit. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 114 Comments on this document? [email protected] Displaying IS-IS interface control packets
Name Description InitFails Shows the number of times initialization of this circuit has failed. This counts events such as PPP NCP failures. Failures to form an adjacency are counted by isisCircRejAdjs. RejAdjs Shows the number of times an adjacency has been rejected on this circuit. IDFieldLenMismatches Shows the number of times an IS-IS control PDU with an ID field length different to that for this system has been received. MaxAreaAddrMismatches Shows the number of times an IS-IS control PDU with a max area address field different to that for this system has been received. AuthFails Shows the number of times an IS-IS control PDU with the correct auth type has failed to pass authentication validation. LANDesISChanges Shows the number of times the Designated IS has changed on this circuit at this level. If the circuit is point to point, this count is zero.
Displaying IS-IS interface control packets Use the following procedure to display IS-IS interface control packets. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click Stats. 3. Click the Interface Control Packets tab.
Interface Control Packets field descriptions Use the data in the following table to use the Interface Control Packets tab.
Name Description Index Shows a unique value identifying the Intermediate-System-to- Intermediate-System (IS-IS) interface. Level Indicates the level at which this LSP appears. Direction Indicates whether the switch is sending or receiving the PDUs. IIHello Indicates the number of IS-IS Hello frames seen in this direction at this level. LSP Indicates the number of IS-IS LSP frames seen in this direction at this level. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 115 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
Name Description CSNP Indicates the number of IS-IS Complete Sequence Number Packets (CSNP) frames seen in this direction at this level. PSNP Indicates the number of IS-IS Partial Sequence Number Packets (PSNP) frames seen in this direction at this level.
Fabric Attach configuration using Enterprise Device Manager Use the procedures in this section to configure Fabric Attach (FA) using Enterprise Device Manager.
Configuring Fabric Attach Procedure 1. From the navigation tree, select Edit > Fabric Attach. 2. Click the Agent tab. 3. To enable or disable FA Standalone Proxy mode, click enable or disable in the StandaloneProxy field. 4. To enable or disable external client proxy support, click enable or disable in the ClientProxy field. 5. Specify the port to use as a static uplink associated with FA Standalone Proxy operation in the UplinkPort field. 6. Specify the trunk to use as a static uplink associated with FA Standalone Proxy operation in the UplinkTrunk field. 7. Specify the agent timeout in the Timeout field. 8. To enable or disable extended logging, click enable or disable in the ExtendedLogging field. 9. To enable or disable Zero Touch support, click enable or disable in the ZeroTouchService field. 10. To enable Zero Touch options, select the appropriate checkbox in the OptionFlags field. 11. Click Apply. Variable definitions Use the data in the following table to use the Agent tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 116 Comments on this document? [email protected] Fabric Attach configuration using Enterprise Device Manager
Variable Value Service Displays the service status. ProvisionMode Displays the provision mode status StandaloneProxy Specifies whether FA Standalone Proxy mode is enabled or disabled. The default is disabled. ClientProxy Specifies whether external client proxy is enabled or disabled. The default is enabled. UplinkPort Specifies the port to use as a static uplink associated with FA Standalone Proxy operation. UplinkTrunk Specifies the trunk to use as a static uplink associated with FA Standalone Proxy operation. Timeout Specifies the agent timeout in seconds. The default value is 75 seconds. ExtendedLogging Specifies whether extended logging is enabled or disabled. The default is disabled. ZeroTouchService Specifies whether Zero Touch support is enabled or disabled. The default is enabled. OptionFlags Specifies the option flags for Zero Touch: • ipAddrDhcp— automates DHCP IP address acquisition The default is enabled. • autoTrustedModeFaClient— automates the FA Client connection • autoPvidModeFaClient — automates client PVID/Mgmt VLAN updates
Configuring per-port FA settings Use the following procedure to determine whether FA data is included in FA Signaling. Procedure 1. From the navigation tree, select Edit. 2. In the Edit tree, double-click Fabric Attach. 3. On the work area, click the Ports tab. 4. To enable or disable the transmission of FA information in FA Signaling, select enabled or disabled in the State field for a specific port or ports. 5. To enable or disable message authentication, select enabled or disabled in the MsgAuthStatus field for a specific port or ports.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 117 Comments on this document? [email protected] SPBM and IS-IS infrastructure configuration using EDM
6. To configure the authentication key, enter an alphanumeric string of up to 32 characters in the MsgAuthKey field for a specific port or ports. 7. Click Apply. Variable Definition Variable Value IfIndex Indicates the interface for which to configure FA operation and message authentication. State Enables or disables FA operation on the interface. The default is enabled. MsgAuthStatus Enables or disables FA message authentication on the interface. The default is enabled. MsgAuthKey Configures the authentication key for the specified interface.
Displaying Fabric Attach elements Use the following procedure to view discovered FA elements. Procedure 1. In the navigation tree, expand the following folders: Configuration>Edit. 2. Click Fabric Attach. 3. In the work area, click the Elements tab. Variable definitions Use the data in the following table to use the Elements tab.
Name Description Ifindex Indicates the interface through which the FA element was discovered. Type Indicates the FA element type. Vlan Indicates the FA element VLAN. Id Indicates the FA Element System ID, which is the unique system identifier used for connection management and limited device state distribution. State Indicates the state flag data associated with the discovered FA element. Auth Indicates the authentication status for the discovered element.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 118 Comments on this document? [email protected] Fabric Attach configuration using Enterprise Device Manager
Configuring an I-SID/VLAN assignment Use the following procedure to configure an I-SID/VLAN assignment on an FA Proxy. Procedure 1. In the navigation tree, expand the following folders: Configuration>Edit. 2. Click Fabric Attach. 3. In the work area, click the I-SID tab. 4. Click Insert. 5. Specify an I-SID in the Isid field. 6. Specify a VLAN in the Vlan field. 7. Click Insert. Variable definitions Use the data in the following table to use the I-SID tab.
Name Description Isid Specifies the I-SID to associate with a VLAN. Vlan Specifies the VLAN to associate with an I-SID. State Indicates the state of the VLAN/I-SID assignment.
Displaying Fabric Attach I-SID Use the following procedure to view discovered FA I-SID. Procedure 1. In the navigation tree, expand the following folders: Configuration>Edit. 2. Click Fabric Attach. 3. In the work area, click the I-SID tab. Variable definitions Use the data in the following table to use the I-SID tab.
Name Description Isid Indicates the FA I-SID. Vlan Indicates the FA I-SID VLAN. State Indicates the state flag data associated with the discovered FA I-SID.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 119 Comments on this document? [email protected] Chapter 6: SPBM infrastructure configuration example
Use the following examples to configure SPBM infrastructure.
Triangle-SMLT configuration example The following information displays a Triangle-SMLT configuration. On each IST switch, you must configure a virtual B-MAC, which both peers share and advertise, and a peer system ID for each, so that if the other peer goes down the local peer can forward packets for the failed peer. In the following example, the virtual B-MAC for both IST switches is 00:00:0b:eb:ff:ff. The System ID for BEB 1 is 0000.0beb.0001 and the System ID for the BEB 2 is 0000.0beb.0002. Note: The following information displays the running configuration.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 120 Comments on this document? [email protected] Triangle-SMLT configuration example
Figure 5: Triangle-SMLT BEB 1 configuration Configure B-VLAN: ***SPBM***
spbm
***VLAN***
vlan create 40,41 type spbm-bvlan vlan name 40 "SPBM-PRI" vlan name 41 "SPBM-SEC" Configure SPBM: ***SPBM***
router isis spbm 1 spbm 1 b-vid 40-41 primary 40 spbm 1 nick-name 0.00.01 spbm 1 smlt-virtual-bmac 0000.0beb.ffff spbm 1 smlt-peer-system-id 0000.0beb.0002 manual-area 00.7000.0001 system-id 0000.0beb.0001 exit router isis enable Configure ports 1, 2 and 4 for NNI: ***SPBM***
interface Ethernet 1-2,4 isis isis spbm 1 isis enable exit
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 121 Comments on this document? [email protected] SPBM infrastructure configuration example
Configure IST: ***VLAN***
vlan create 50 type port 1 vlan name 50 "IST" vlan members 50 1-2
interface vlan 50 ip address 10.0.5.1 255.255.255.0 exit
***MLT (Phase 1)*** mlt 1 name "IST" enable member 1-2
***SMLT***
interface mlt 1 ist peer-ip 10.0.5.2 ist vlan 50 ist enable exit
***SPBM***
router isis enable Configure port 3 as the SLT port ***SMLT***
interface Ethernet ALL smlt port 3 3 exit Configure the Layer 2 VSN Blue: ***VLAN***
vlan create 1000 type port 1 vlan name "VSN-Blue" vlan ports 3 tagging tagAll vlan members 1000 1-3
***SPBM***
i-sid 10 vlan 1000 Configure Layer 2 VSN Red: ***VLAN***
vlan create 1001 type port 1 vlan name "VSN-Red" vlan members 1001 1-3
***SPBM***
i-sid 11 vlan 1001 BEB 2 configuration Configure B-VLAN: ***SPBM***
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 122 Comments on this document? [email protected] Triangle-SMLT configuration example
spbm
***VLAN***
vlan create 40,41 type spbm-bvlan vlan name 40 "SPBM-PRI" vlan name 41 "SPBM-SEC" Configure SPBM: ***SPBM***
router isis spbm 1 spbm 1 b-vid 40-41 primary 40 spbm 1 nick-name 0.00.02 spbm 1 smlt-virtual-bmac 0000.0beb.ffff spbm 1 smlt-peer-system-id 0000.0beb.0001 manual-area 00.7000.0001 system-id 0000.0beb.0002 exit router isis enable Configure ports 1,2 and 4 for NNI: ***SPBM***
interface Ethernet 1-2,4 isis isis spbm 1 isis enable exit Configure IST: ***VLAN***
vlan create 50 type port 1 vlan name 50 "IST" vlan members 50 1-2
interface vlan 50 ip address 10.0.5.2 255.255.255.0 exit
***MLT (Phase 1)***
mlt 1 name "IST" enable member 1-2
***SMLT***
interface mlt 1 ist peer-ip 10.0.5.1 ist vlan 50 ist enable exit
***SPBM***
router isis enable Configure port 3 as the SLT port ***SMLT***
interface Ethernet ALL
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 123 Comments on this document? [email protected] SPBM infrastructure configuration example
smlt port 3 3 exit Configure the Layer 2 VSN Blue: ***VLAN***
vlan create 1000 type port 1 vlan name "VSN-Blue" vlan members 1000 1-3
***SPBM*** i-sid 10 vlan 1000 Configure Layer 2 VSN Red: ***VLAN***
vlan create 1001 type port 1 vlan name "VSN-Red" vlan members 1001 1-3
***SPBM*** i-sid 11 vlan 1001 BEB 3 configuration Configure B-VLAN: ***SPBM***
spbm
***VLAN***
vlan create 40,41 type spbm-bvlan vlan name 40 "SPBM-PRI" vlan name 41 "SPBM-SEC" vlan ports 1-4 tagging tagAll Configure SPBM: ***SPBM***
router isis spbm 1 spbm 1 b-vid 40-41 primary 40 spbm 1 nick-name 0.00.03 system-id 0000.0beb.0003 manual-area 00.7000.0001 exit router isis enable Configure ports 3-4 as SPBM NNI: ***SPBM***
interface Ethernet 3,4 isis isis spbm 1 isis enable exit Configure the Layer 2 VSN Blue and Layer 2 VSN Red: ***VLAN***
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 124 Comments on this document? [email protected] Verifying SPBM configuration
vlan create 1000-1001 type port 1 vlan name "VSN-Blue" vlan name "VSN-Red" vlan members 1000 1-3 vlan members 1001 1-3
***SPBM***
i-sid 10 vlan 1000 i-sid 11 vlan 1001
Verifying SPBM configuration The following sections show the output from verifying the sample IS-IS SPBM configuration. Display the global IS-IS configuration and confirm that IS-IS is enabled on each of the BEBs. AdminState should display as enabled if IS-IS is functioning. BEB1:(config)#show isis ======ISIS General Info ======AdminState : enabled RouterType : Level 1 System ID : 0000.0beb.0001 Max LSP Gen Interval : 900 Min LSP Gen Interval : 30 Metric : wide Overload-on-startup : 20 Overload : false Csnp Interval : 10 PSNP Interval : 2 Rxmt LSP Interval : 5 Spf-delay : 100 Router Name : BEB1 Num of Interfaces : 2 Num of Area Addresses : 1
BEB2:(config)#show isis ======ISIS General Info ======AdminState : enabled RouterType : Level 1 System ID : 0000.0beb.0002 Max LSP Gen Interval : 900 Min LSP Gen Interval : 30 Metric : wide Overload-on-startup : 20 Overload : false Csnp Interval : 10 PSNP Interval : 2 Rxmt LSP Interval : 5 Spf-delay : 100 Router Name : BEB2 Num of Interfaces : 2 Num of Area Addresses : 1
BEB3:(config)#show isis ======
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 125 Comments on this document? [email protected] SPBM infrastructure configuration example
ISIS General Info ======AdminState : enabled RouterType : Level 1 System ID : 0000.0beb.0003 Max LSP Gen Interval : 900 Min LSP Gen Interval : 30 Metric : wide Overload-on-startup : 20 Overload : false Csnp Interval : 10 PSNP Interval : 2 Rxmt LSP Interval : 5 Spf-delay : 100 Router Name : BEB3 Num of Interfaces : 2 Num of Area Addresses : 1 Display the IS-IS net address: BEB1(config)#show isis net ======ISIS Network Entity Title Info ======NET ======00.7000.0001.0000.0beb.0001.00
BEB2(config)#show isis net ======ISIS Network Entity Title Info ======NET ======00.7000.0001.0000.0beb.0002.00
BEB3(config)#show isis net ======ISIS Network Entity Title Info ======NET ======00.7000.0001.0000.0beb.0003.00 Display the interface IS-IS configuration. OP-STATE and ADM-STATE should display as UP. BEB1(config)#show isis interface ======ISIS Interfaces ======IFIDX TYPE LEVEL OP-STATE ADM-STATE ADJ UP-ADJ SPBM-L1-METRIC ======Port: 4 pt-pt Level 1 UP UP 1 1 10 Trunk: 1 pt-pt Level 1 UP UP 1 1 10
BEB2(config)#show isis interface ======ISIS Interfaces ======IFIDX TYPE LEVEL OP-STATE ADM-STATE ADJ UP-ADJ SPBM-L1-METRIC ======Port: 4 pt-pt Level 1 UP UP 1 1 10 Trunk: 1 pt-pt Level 1 UP UP 1 1 10
BEB3(config)#show isis interface ======
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 126 Comments on this document? [email protected] Verifying SPBM configuration
ISIS Interfaces ======IFIDX TYPE LEVEL OP-STATE ADM-STATE ADJ UP-ADJ SPBM-L1-METRIC ======Port: 4 pt-pt Level 1 UP UP 1 1 10 Trunk: 1 pt-pt Level 1 UP UP 1 1 10 Display IS-IS adjacencies. • Use the command for each BEB to show the HOST-NAME and SYSID for the other two BEBs. The STATE should display as UP. BEB1(config)#show isis adjacencies ======ISIS Adjacencies ======INTERFACE L STATE UPTIME PRI HOLDTIME SYSID HOST-NAME
======Port: 4 1 UP 01:21:58 127 24 0000.0beb.0003 BEB3
Trunk: 1 1 UP 01:25:08 127 27 0000.0beb.0002 BEB2
------2 interfaces have formed an adjacency ------
BEB2(config)#show isis adjacencies ======ISIS Adjacencies ======INTERFACE L STATE UPTIME PRI HOLDTIME SYSID HOST-NAME
======Port: 4 1 UP 01:47:24 127 22 0000.0beb.0003 BEB3
Trunk: 1 1 UP 01:50:31 127 25 0000.0beb.0001 BEB1
------2 interfaces have formed an adjacency ------
BEB3(config)#show isis adjacencies ======ISIS Adjacencies ======INTERFACE L STATE UPTIME PRI HOLDTIME SYSID HOST-NAME
======Port: 4 1 UP 01:25:20 127 23 0000.0beb.0001 BEB1
Trunk: 1 1 UP 01:25:23 127 21 0000.0beb.0002 BEB2
------2 interfaces have formed an adjacency ------Display the IS-IS SPBM multicast-FIB calculation results by I-SID: BEB1(config)#show isis spbm i-sid all ======SPBM ISID INFO ======ISID SOURCE NAME VLAN SYSID TYPE HOST-NAME ======10 0.00.01 40 0000.0beb.0001 config BEB1
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 127 Comments on this document? [email protected] SPBM infrastructure configuration example
11 0.00.01 41 0000.0beb.0001 config BEB1 10 0.00.02 40 0000.0beb.0002 discover ERS-2 11 0.00.02 41 0000.0beb.0002 discover ERS-2 10 0.00.03 40 0000.0beb.0003 discover ERS-3 11 0.00.03 41 0000.0beb.0003 discover ERS-3 ------Total number of SPBM ISID entries configured: 2 ------Total number of SPBM ISID entries discovered: 4 ------Total number of SPBM ISID entries: 6 ------
BEB2(config)#show isis spbm i-sid all ======SPBM ISID INFO ======ISID SOURCE NAME VLAN SYSID TYPE HOST-NAME ======10 0.00.01 40 0000.0beb.0001 discover BEB1 11 0.00.01 41 0000.0beb.0001 discover BEB1 10 0.00.02 40 0000.0beb.0002 config BEB2 11 0.00.02 41 0000.0beb.0002 config BEB2 10 0.00.03 40 0000.0beb.0003 discover BEB3 11 0.00.03 41 0000.0beb.0003 discover BEB3 ------Total number of SPBM ISID entries configured: 2 ------Total number of SPBM ISID entries discovered: 4 ------Total number of SPBM ISID entries: 6 ------
BEB3(config)#show isis spbm i-sid all ======SPBM ISID INFO ======ISID SOURCE NAME VLAN SYSID TYPE HOST-NAME ======10 0.00.01 40 0000.0beb.0001 discover BEB1 11 0.00.01 41 0000.0beb.0001 discover BEB1 10 0.00.02 40 0000.0beb.0002 discover BEB2 11 0.00.02 41 0000.0beb.0002 discover BEB2 10 0.00.03 40 0000.0beb.0003 config BEB3 11 0.00.03 41 0000.0beb.0003 config BEB3 ------Total number of SPBM ISID entries configured: 2 ------Total number of SPBM ISID entries discovered: 4 ------Total number of SPBM ISID entries: 6 ------Display the unicast Forwarding Information Base (FIB): BEB1(config)#show isis spbm unicast-fib ======SPBM UNICAST FIB ENTRY INFO ======DESTINATION BVLAN SYSID HOST-NAME OUTGOING COST ADDRESS INTERFACE ======00:00:0b:eb:00:01 40 0000.0beb.ffff BEB1 cpp 0 00:00:0b:eb:00:01 40 0000.0beb.0001 BEB1 cpp 0 00:00:0b:eb:00:01 41 0000.0beb.0001 BEB1 cpp 0
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 128 Comments on this document? [email protected] Verifying SPBM configuration
00:00:0b:eb:00:02 40 0000.0beb.0002 BEB2 Trunk: 1 10 00:00:0b:eb:00:02 41 0000.0beb.ffff BEB2 Trunk: 1 10 00:00:0b:eb:00:02 41 0000.0beb.0002 BEB2 Trunk: 1 10 00:00:0b:eb:00:03 40 0000.0beb.0003 BEB3 Port: 4 10 00:00:0b:eb:00:03 41 0000.0beb.0003 BEB3 Port: 4 10 ------Total number of SPBM UNICAST FIB entries 8 ------
BEB2(config)#show isis spbm unicast-fib ======SPBM UNICAST FIB ENTRY INFO ======DESTINATION BVLAN SYSID HOST-NAME OUTGOING COST ADDRESS INTERFACE ======00:00:0b:eb:00:01 40 0000.0beb.ffff BEB1 Trunk: 1 10 00:00:0b:eb:00:01 40 0000.0beb.0001 BEB1 Trunk: 1 10 00:00:0b:eb:00:01 41 0000.0beb.0001 BEB1 Trunk: 1 10 00:00:0b:eb:00:02 40 0000.0beb.0002 BEB2 cpp 0 00:00:0b:eb:00:02 41 0000.0beb.ffff BEB2 cpp 0 00:00:0b:eb:00:02 41 0000.0beb.0002 BEB2 cpp 0 00:00:0b:eb:00:03 40 0000.0beb.0003 BEB3 Port: 4 10 00:00:0b:eb:00:03 41 0000.0beb.0003 BEB3 Port: 4 10 ------Total number of SPBM UNICAST FIB entries 8 ------
BEB3(config)#show isis spbm unicast-fib ======SPBM UNICAST FIB ENTRY INFO ======DESTINATION BVLAN SYSID HOST-NAME OUTGOING COST ADDRESS INTERFACE ======00:00:0b:eb:00:01 40 0000.0beb.ffff BEB1 Port: 3 10 00:00:0b:eb:00:01 40 0000.0beb.0001 BEB1 Port: 3 10 00:00:0b:eb:00:01 41 0000.0beb.0001 BEB1 Port: 3 10 00:00:0b:eb:00:02 40 0000.0beb.0002 BEB2 Port: 4 10 00:00:0b:eb:00:02 41 0000.0beb.ffff BEB2 Port: 4 10 00:00:0b:eb:00:02 41 0000.0beb.0002 BEB2 Port: 4 10 00:00:0b:eb:00:03 40 0000.0beb.0003 BEB3 cpp 0 00:00:0b:eb:00:03 41 0000.0beb.0003 BEB3 cpp 0 ------Total number of SPBM UNICAST FIB entries 8 ------Display the multicast FIB: BEB1(config)#show isis spbm multicast-fib i-sid 10 ======SPBM MULTICAST FIB ENTRY INFO ======MCAST DA ISID BVLAN SYSID HOST-NAME OUTGOING INTERFACES ======03:00:10:00:00:0a 10 40 0000.0beb.0001 BEB1 NNI 4 T:1 UNI 3 V1000 03:00:20:00:00:0a 10 40 0000.0beb.0002 BEB2 UNI 3 V1000 03:00:30:00:00:0a 10 40 0000.0beb.0003 BEB3 UNI 3 V1000 ------Total number of SPBM MULTICAST FIB entries 3 ------
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 129 Comments on this document? [email protected] SPBM infrastructure configuration example
BEB2(config)#show isis spbm multicast-fib i-sid 10 ======SPBM MULTICAST FIB ENTRY INFO ======MCAST DA ISID BVLAN SYSID HOST-NAME OUTGOING INTERFACES ======03:00:01:00:00:0a 10 40 0000.0beb.0001 BEB1 UNI 3 V1000 03:00:02:00:00:0a 10 40 0000.0beb.0002 BEB2 NNI 4 T:1 UNI 3 V1000 03:00:03:00:00:0a 10 40 0000.0beb.0003 BEB3 UNI 3 V1000 ------Total number of SPBM MULTICAST FIB entries 3 ------
BEB3(config)#show isis spbm multicast-fib i-sid 10 ======MCAST DA ISID BVLAN SYSID HOST-NAME OUTGOING INTERFACES ======03:00:01:00:00:0a 10 40 0000.0beb.0001 BEB1 UNI 1 V1000 03:00:02:00:00:0a 10 40 0000.0beb.0002 BEB2 UNI 1 V1000 03:00:03:00:00:0a 10 40 0000.0beb.0003 BEB3 NNI 3 NNI 4 UNI 1 V1000 ------Total number of SPBM MULTICAST FIB entries 3 ------Display forwarding database tables: BEB1(config)#show mac-address-table Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 10
MAC Address Vid Type Source ------00-11-58-18-6C-01 1 Dynamic Port:20 00-11-F9-35-FC-00 1 Dynamic Port: 1 00-11-F9-35-FC-01 1 Dynamic Port: 1 70-30-18-26-14-00 1 Self 70-30-18-26-80-01 1 Dynamic Port: 4 FC-A8-41-F6-24-01 1 Dynamic Trunk: 1 00-00-11-00-00-00 1000 SPBm Port: 3 00-00-33-00-00-00 40 SPBm I-SID: 10 00-00-22-00-00-00 1001 SPBm Port: 3 00-00-44-00-00-00 40 SPBm I-SID: 11
BEB2(config)#show mac-address-table Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 7
MAC Address Vid Type Source ------70-30-18-26-14-01 1 Dynamic Trunk: 1 70-30-18-26-80-01 1 Dynamic Port: 4 FC-A8-41-F6-24-00 1 Self 00-00-11-00-00-00 1000 SPBm Port: 3 00-00-33-00-00-00 40 SPBm I-SID: 10 00-00-22-00-00-00 1001 SPBm Port: 3 00-00-44-00-00-00 41 SPBm I-SID: 11
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 130 Comments on this document? [email protected] Verifying SPBM configuration
BEB3(config)#show mac-address-table Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 8
MAC Address Vid Type Source ------00-0E-62-A0-24-01 1 Dynamic Port: 1 70-30-18-26-14-01 1 Dynamic Port: 4 70-30-18-26-80-00 1 Self FC-A8-41-F6-24-01 1 Dynamic Trunk: 1 00-00-11-00-00-00 40 SPBm I-SID: 10 00-00-22-00-00-00 41 SPBm I-SID: 11 00-00-33-00-00-00 1000 SPBm Port: 1 00-00-44-00-00-00 1001 SPBm Port: 1 BEB1#show mac-addr spbm Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 4
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 1000 00-00-33-00-00-00 10 Port 4 40 00-00-0B-EB-00-03 BEB3 00-00-22-00-00-00 11 Port 3 1001 00-00-44-00-00-00 11 Port 4 40 00-00-0B-EB-00-03 BEB3
BEB2#show mac-addr spbm Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 4
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 1000 00-00-33-00-00-00 10 Port 4 40 00-00-0B-EB-00-03 BEB3 00-00-22-00-00-00 11 Port 3 1001 00-00-44-00-00-00 11 Port 4 40 00-00-0B-EB-00-03 BEB3
BEB3#show mac-addr spbm Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 4
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 40 00:00:0B:EB:FF:FF BEB1 00-00-33-00-00-00 10 Port 1 1000 00-00-22-00-00-00 11 Port 4 40 00:00:0B:EB:FF:FF BEB2 00-00-44-00-00-00 11 Port 1 1001
BEB1#show mac-address-table spbm i-sid 10 Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 2
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 1000
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 131 Comments on this document? [email protected] SPBM infrastructure configuration example
00-00-33-00-00-00 10 Port 4 40 00-00-0B-EB-00-03 BEB3
BEB2#show mac-address-table spbm i-sid 10 Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 2
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 1000 00-00-33-00-00-00 10 Port 4 40 00-00-0B-EB-00-03 BEB3
BEB3#show mac-address-table spbm i-sid 10 Mac Address Table Aging Time: 300 Learning Enabled Ports ALL Number of addresses: 2
MAC Address I-SID Source Vid BVid Dest-MAC Dest-Sys-Name ------00-00-11-00-00-00 10 Port 3 40 00:00:0B:EB:FF:FF BEB1 00-00-33-00-00-00 10 Port 1 1000
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 132 Comments on this document? [email protected] Chapter 7: Layer 2 VSN configuration fundamentals
This section provides fundamentals concepts for Layer 2 Virtual Services Networks (VSN).
SPBM L2 VSN Shortest Path Bridging MAC-in-MAC (SPBM) supports Layer 2 VSN functionality where Customer VLANs (C-VLANs) and Switched UNIs are bridged over the SPBM core infrastructure. At the Backbone Edge Bridges (BEBs), customer VLANs (C-VLAN) and Switched UNIs are mapped to I-SIDs based on the local service provisioning. Outgoing frames are encapsulated in a MAC-in- MAC header, and then forwarded across the core to the far-end BEB, which strips off the encapsulation and forwards the frame to the destination network based on the I-SID to C-VLAN or I- SID to Switched UNI provisioning. In the backbone VLAN (B-VLAN), Backbone Core Bridges (BCBs) forward the encapsulated traffic based on the BMAC-DA, using the shortest path topology learned using IS-IS. The following figure shows a sample campus SPBM Layer 2 VSN network.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 133 Comments on this document? [email protected] Layer 2 VSN configuration fundamentals
Figure 6: SPBM L2 VSN in a campus One of the key advantages of the SPBM Layer 2 VSN is that you can achieve network virtualization provisioning by configuring only the edge of the network (BEBs). As a result, the intrusive core provisioning that other Layer 2 virtualization technologies require is not needed when you add connectivity services to the SPBM network. For example, when you create new virtual server instances that require their own VLAN instances, you can provision at the network edge only and do not need configure throughout the rest of the network infrastructure. Based on its I-SID scalability, this solution can scale much higher than any 802.1Q tagging based solution. Also, due to the fact that there is no need for Spanning Tree in the core, this solution does not need any core link provisioning for normal operation. You can achieve redundant connectivity between the C-VLAN domain and the SPBM infrastructure by operating two SPB enabled units in Switch Cluster mode, also referred to as Split Multi-Link Trunk (SMLT) over SPB. This allows the dual homing of any traditional link aggregation capable device into a Fabric Connect network.
C-VLAN UNI Customer VLAN (C-VLAN) User Network Interface (UNI) is created when you map a specific VLAN, or several VLANs, to an I-SID. A VLAN with an I-SID configured becomes a C-VLAN. Switching takes place based on the I-SID, not based on the VLAN or VLANs. All ingress traffic of the VLAN from any member ports belong to the configured I-SID. C-MAC learning occurs inside the I- SID, on both UNI and Network to Network Interface (NNI) side (C-MAC + I-SID pointing to UNI port
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 134 Comments on this document? [email protected] SPBM L2 VSN
from the UNI side traffic, or C-MAC + I-SID pointing to a remote SPBM node - where the source C- MAC is connected). Broadcast, unknown multicast and unknown unicast traffic in the I-SID is replicated to all local I-SID endpoints, including all C-VLAN member ports along with switched UNIs, and to all remote endpoints carried by the multicast group of the I-SID. For UNI originated broadcast traffic, the originating endpoint is excluded from flooding, and the ingress port for broadcast traffic coming in on an NNI is excluded from flooding. C-VLAN UNI summary: • C-VLAN UNI is a VLAN (or VLANs) associated with an I-SID. • Global significance on the BEB. • Performs Layer 2 (L2) switching on local VLAN port members and transports over L2VSN for remote end-points. • Untagged traffic is assigned to the VLAN corresponding to the PVID configured on the port. Use C-VLAN UNI when either of the following apply: • Multiple ports must belong to the same broadcast domain. • A routing interface is required on a broadcast domain. Note: On a tagged port, use UntagPVIDOnly mode to force PVID traffic to egress untagged. An example of an application for C-VLAN UNI is a typical enterprise deployment that includes platform-based VLANs with bridging and routing.
Switched UNI Switched User Network Interface (UNI) allows the association of local endpoints to I-SIDs based on local port and VLAN together. With switched UNI, the same VLAN can be used on one port to create an endpoint to one I-SID, and on another port to create an endpoint to another I-SID. Switched UNI summary: • Switched UNI is a VLAN and ports associated with I-SIDs. • Local significance on the ports. • You can re-use the same VLAN to associate different ports with different I-SIDs. • You can use a different VLAN on the same ports, or you can assign different ports to the same I-SID. • Supports VLAN mapping on local switch. • VLAN tagging is automatically set to untagPvidOnly when a port is configured to be a Switched UNI. • Untagged traffic is assigned to the VLAN corresponding to the PVID configured on the port.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 135 Comments on this document? [email protected] Layer 2 VSN configuration fundamentals
Use Switched UNI when either of the following apply: • Vlan ID (VID) reuse is required. The same VID is used on different broadcast domains (multi- tenant applications). • Multiple VLANs must be part of the same broadcast domain. • VID translation is required. An example of an application for Switched UNI is a typical host and provider deployment, with a port and VID-based classification.
Transparent UNI A Transparent UNI (T-UNI) maps an entire port or MLT to an I-SID. Transparent UNI configures a transparent port where all traffic switches on an internal virtual port using the assigned I-SID, with no VLAN involved. Devices switch tagged and untagged traffic in the assigned I-SID regardless of the VLAN ID. The T-UNI port or MLT is not a member of any VLAN or STG, and is always in the forwarding state. You can map multiple ports to a T-UNI I-SID. Multiple ports on the same switch and on other BEBs can use the common I-SID to switch traffic. Transparent Transparent UNI is considered transparent because the MAC learning occurs within the I-SID. Devices switch tagged and untagged traffic in the assigned I-SID. Devices switch control protocols, such as BPDU, LACP, LLDP, and others, in the assigned I-SID, rather than forwarding to the CP. The service classification of packets that a T-UNI port receives is independent of any VLAN-ID values present in the packets. All data packets the T-UNI port receives are classified into the same service. As data packets enter and exit the T-UNI service no VLAN tag modifications are performed on the data packets. MAC learning MAC learning is against the I-SID and the port or MLT. When a packet ingresses on a port or MLT associated with a T-UNI I-SID, the MAC lookup performs based on the I-SID. A packet can ingress to a T-UNI port and transfer through the SPB network, or can egress out another T-UNI port configured to the same I-SID. A packet can ingress to a NNI port, and the system performs a MAC Destination Address (DA) lookup based on the I-SID. If the DA lookup fails, the packet floods to all T-UNI ports. Considerations Consider the following when you configure a Transparent UNI: • You cannot configure a Transparent UNI on the same I-SID as a C-VLAN or a Switched UNI. • In the current release, Transparent UNI supports a static UNI MLT only. This release supports Transparent UNI over static SMLT. • No Layer 3 processing takes place on packets that ingress on a T-UNI port. • Pause frames do not switch through the T-UNI I-SID.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 136 Comments on this document? [email protected] SPBM L2 VSN sample operation
• A Transparent UNI port is not a member of any VLAN and does not belong to any STG. Use Transparent UNI when either of the following apply: • All tagged and untagged traffic on a port must be classified into the same broadcast domain. • You want to offer a transparent provider solution. An example of an application for Transparent-UNI is a typical Ethernet provider deployment with port-based classification and transparent forwarding.
SPBM L2 VSN sample operation The following section shows how a SPBM network is established, in this case, a Layer 2 VSN. 1. Discover network topology
Figure 7: SPBM topology discover
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 137 Comments on this document? [email protected] Layer 2 VSN configuration fundamentals
IS-IS runs on all nodes of the SPBM domain. IS-IS is the basis of SPBM, the IS-IS adjacency must be formed first. After the neighboring nodes see hellos from each other, the nodes look for the same Level (Level 1) and the same area (for example, Area 2f.8700.0000.00). After the hellos are confirmed both nodes send Link State Protocol Data Units, which contain connectivity information for the SPBM node. These nodes also send copies of all other LSPs they have in their databases. This establishes a network of connectivity providing the necessary information for each node to find the best and proper path to all destinations in the network. Each node has a system ID, which is used in the topology announcement. This system ID also serves as the switch Backbone MAC address (B-MAC), which is used as the source and destination MAC address in the SPBM network. 2. Each IS-IS node automatically builds trees from itself to all other nodes When the network topology is discovered and stored in the IS-IS link state database (LSDB), each node calculates shortest path trees for each source node. A unicast path now exists from every node to every other node With this information, each node populates unicast information received from SPBM into the FIB for forwarding purposes. Multicast FIB is not produced until Layer 2 VSN services are configured and learned. 3. IS-IS advertises new service communities of interest When a new service is provisioned, its membership is flooded throughout the topology with an IS-IS advertisement.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 138 Comments on this document? [email protected] SPBM L2 VSN sample operation
Figure 8: SPBM BMAC and I-SID population
BMAC and I-SID information floods throughout the network to announce new I-SID memberships. In this case, VLAN 20 is mapped to I-SID 100. Note: I-SIDs are only used for virtual services (Layer 2 VSNs and Layer 3 VSNs). If IP Shortcuts only is enabled on the BEBs, I-SIDs are never exchanged in the network as IP Shortcuts allow for IP networks to be transported across IS-IS. Each node populates its FDB with the BMAC information derived from the IS-IS shortest path tree calculations. No traditional flooding and learning mechanism in place for the B- VLAN, but FDBs are programmed by the IS-IS protocol. 4. When a node receives notice of a new service AND is on the shortest path, it updates the FDB In this scenario, where there are three source nodes having a membership on I-SID 100, three shortest path trees are calculated (not counting the Equal Cost Trees (ECTs).
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 139 Comments on this document? [email protected] Layer 2 VSN configuration fundamentals
Figure 9: Shortest path tree for source node A
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 140 Comments on this document? [email protected] SPBM L2 VSN sample operation
Figure 10: Shortest path tree for source node B
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 141 Comments on this document? [email protected] Layer 2 VSN configuration fundamentals
Figure 11: Shortest path tree for source node C
The paths between any two nodes are always the shortest paths. Also, the paths in either direction are congruent, therefore a bidirectional communication stream can be monitored easily by mirroring ingress and egress on a link to a network analyzer. VLAN traffic arriving on switch A and VLAN 20 is forwarded following the blue path, traffic arriving on switch B and VLAN 20 the orange path and on switch C VLAN 20 traffic is following the green path. If the destination CMAC is unknown at the SPBM ingress node or the traffic is of type broadcast or multicast, then it floods to all members of the topology which spans VLAN 20. If the destination CMAC is already known, then the traffic is only forwarded as a unicast to the appropriate destination. In the SPBM domain, the traffic is switched on the BMAC header only. The bridge filtering database (FDB) at the VLAN to I-SID boundary (backbone edge bridge BEB), maintains a mapping between CMACs and corresponding BMACs. For example, Switch B learns all CMACs which are on VLAN 20 connected to switch A with the BMAC of A in its FDB and the CMACs that are behind C are learned with the BMAC of C.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 142 Comments on this document? [email protected] Chapter 8: Layer 2 VSN configuration using ACLI
This section provides procedures to configure Layer 2 Virtual Services Networks (VSN) using Avaya Command Line Interface (ACLI).
Configuring an SPBM Layer 2 VSN C-VLAN Shortest Path Bridging MAC (SPBM) supports Layer 2 Virtual Service Network (VSN) functionality where customer VLANs (C-VLANs) are bridged over the SPBM core infrastructure. At the BEBs, customer VLANs (C-VLAN) are mapped to I-SIDs based on the local service provisioning. Outgoing frames are encapsulated in a MAC-in-MAC header, and then forwarded across the core to the far-end BEB, which strips off the encapsulation and forwards the frame to the destination network based on the I-SID-to-C-VLAN provisioning. Before you begin • You must configure the required SPBM and IS-IS infrastructure, which includes the creation of SPBM BVLANs. • You must create the customer VLANs (C-VLANs) and add slots/ports. About this task You can use C-VLAN UNI when either of the following apply: • Multiple ports must belong to the same broadcast domain. • A routing interface is required on a broadcast domain. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Map a customer VLAN (C-VLAN) to a Service Instance Identifier (I-SID): i-sid <1–16777214> vlan <1–4094>
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 143 Comments on this document? [email protected] Layer 2 VSN configuration using ACLI
Important: When a protocol VLAN is created, all ports are added to the VLAN including SPBM ports. To configure a protocol-based VLAN as a C-VLAN, you must first remove the SPBM-enabled ports from the protocol based VLAN, and then configure the protocol- based VLAN as a C-VLAN.
3. Display C-VLAN information: show i-sid <1–16777214> Example 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# i-sid 200 vlan 200 7024XLS(config)# show i-sid 200 I-SID Vid UNI-type Ports ------200 200 C-VLAN 7
Variable definitions Use the data in the following table to use the i-sid vlan command.
Variable Value i-sid <1–16777214> vlan<1–4094> Specifies the customer VLAN (CVLAN) to associate with the I- SID. Use the no or default options to remove the I-SID from the specified VLAN.
Note: Virtual Services Platform 7000 reserves I-SID 0x00ffffff. Virtual Services Platform 7000 uses this I-SID to advertise the virtual B-MAC in a SMLT dual-homing environment. The platform clears the receive and transmit bit of this I- SID, therefore I-SID 0x00ffffff cannot be used for any other service.
Configuring an SPBM Layer 2 VSN Switched UNI Shortest Path Bridging MAC (SPBM) supports Layer 2 Virtual Service Network (VSN) functionality where Switched UNIs are bridged over the SPBM core infrastructure.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 144 Comments on this document? [email protected] Configuring an SPBM Layer 2 VSN Switched UNI
At the BEBs, Switched UNIs are mapped to I-SIDs based on the local service provisioning. Outgoing frames are encapsulated in a MAC-in-MAC header, and then forwarded across the core to the far- end BEB, which strips off the encapsulation and forwards the frame to the destination network based on the I-SID-to-Switched UNI VLAN provisioning. Before you begin • You must configure the required SPBM and IS-IS infrastructure, which includes the creation of SPBM BVLANs. About this task To configure a Switched UNI, you must create a Switched UNI VLAN, and map an I-SID to the Switched UNI VLAN and a port. You can use Switched UNI when either of the following apply: • VLAN ID reuse is required. The same VLAN ID is used on different broadcast domains (multi- tenant applications). • Multiple VLANs must be part of the same broadcast domain. • VLAN ID translation is required. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Create a Switched UNI VLAN: vlan create <2–4094> type spbm-switchedUni 3. Map a Switched UNI VLAN to a Service Instance Identifier (I-SID): i-sid <1–16777214> vlan <2–4094> port
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 145 Comments on this document? [email protected] Layer 2 VSN configuration using ACLI
7024XLS(config)# show i-sid 100 I-SID Vid UNI-type Ports ------100 100 switched 1
You can map a Switched VLAN UNI to multiple I-SIDs. 7024XLS(config)# i-sid 101 vlan 100 port 2 7024XLS(config)# show i-sid I-SID Vid UNI-type Ports ------100 100 switched 1 101 100 switched 2
Variable definitions Use the data in the following table to use the i-sid vlan command to configure a Switched UNI.
Variable Value i-sid <1–16777214> vlan<2–4094> port Specifies the Switched UNI VLAN to associate with the I-SID.
Note: Virtual Services Platform 7000 reserves I-SID 0x00ffffff. Virtual Services Platform 7000 uses this I-SID to advertise the virtual B-MAC in a SMLT dual-homing environment. The platform clears the receive and transmit bit of this I- SID, therefore I-SID 0x00ffffff cannot be used for any other service.
Configuring an SPBM Layer 2 Transparent UNI Transparent UNI (T-UNI) maps a port or MLT to an I-SID. Transparent UNI configures a transparent port where all traffic switches on an internal virtual port using the assigned I-SID, with no VLAN involved. Multiple ports on the same unit and on other Backbone Edge Bridges (BEBs) switch on a common I-SID. The T-UNI port is not a member of any VLAN or STG. Before you begin • You must configure the required SPBM and IS-IS infrastructure, which includes the creation of SPBM BVLANs.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 146 Comments on this document? [email protected] Configuring an SPBM Layer 2 Transparent UNI
About this task You can use Transparent UNI when either of the following apply: • All tagged and untagged traffic on a port must be classified into the same broadcast domain. • You want to offer a transparent provider solution. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. To configure a Transparent UNI, enter the following command at the command prompt: i-sid <1–16777214> port [
Variable definitions Use the data in the following table to use the i-sid command.
Variable Value <1–16777214> Specifies the I-SID information. port
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 147 Comments on this document? [email protected] Layer 2 VSN configuration using ACLI
Variable Value Note: In order for a Transparent UNI to work correctly in an SMLT setup, the same I-SID must be configured on both SMLT peers. When you configure an I-SID that has Transparent UNIs on only one of the two SMLT peers, you must also create a transparent smlt-peer UNI on the other SMLT peer.
Use the data in the following table to use the show i-sid commands
Variable Value <1–16777214> Indicates the I-SID ID.
Displaying C-VLAN, Switched UNI, and Transparent UNI I- SID information Use the following procedure to display C-VLAN, Switched UNI, and Transparent UNI I-SID information. Procedure 1. Enter Privileged EXEC mode: enable 2. Display the C-VLAN to I-SID associations: show vlan i-sid <1–4094> 3. Display I-SID information for C-VLAN, Switched UNI, and Transparent UNI: show i-sid <1–16777214> 4. Display the IS-IS SPBM multicast-FIB calculation results by I-SID: show isis spbm i-sid {all|config|discover} [vlan <1–4094>] [id <1– 16777214>] [nick-name
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 148 Comments on this document? [email protected] Displaying C-VLAN, Switched UNI, and Transparent UNI I-SID information
10 20 Display I-SID information for C-VLAN, Switched UNI, and Transparent UNI: 7024XL:(config):show i-sid I-SID Vid UNI-type Ports ------100 10 C-VLAN 15-20 200 20 switched 10 300 N/A transparent 25 Display UNIs for a particular I-SID: 7024XL:(config):show i-sid 100 I-SID Vid UNI-type Ports ------100 10 C-VLAN 15-20 Display the IS-IS SPBM multicast-FIB calculation results by I-SID: 7024XLS#show isis spbm i-sid all ======SPBM ISID INFO ======ISID SOURCE NAME VLAN SYSID TYPE HOST_NAME ------200 1.11.16 1000 0014.c7e1.33df config VSP-7000 300 1.11.16 1000 0014.c7e1.33df config VSP-7000 400 1.11.16 1000 0014.c7e1.33df config VSP-7000 200 1.11.16 2000 0014.c7e1.33df config VSP-7000 300 1.11.16 2000 0014.c7e1.33df config VSP-7000 400 1.11.16 2000 0014.c7e1.33df config VSP-7000 200 1.12.45 1000 0016.ca23.73df discover VSP-9001 300 1.12.45 1000 0016.ca23.73df discover VSP-9001
------Total number of SPBM ISID entries configed: 6 ------Total number of SPBM ISID entries discovered: 2 ------Total number of SPBM ISID entries: 8 ------
Variable definitions Use the data in the following table to use the show vlan i-sid commands.
Variable Value <1–4094><1–16777214> Displays I-SID information for the specified C-VLAN. You can specify the VLAN ID and I-SID ID.
Use the data in the following table to use the show i-sid commands
Variable Value <1–16777214> Displays I-SID information. You can specify the I-SID ID.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 149 Comments on this document? [email protected] Layer 2 VSN configuration using ACLI
Use the data in the following table to use the show isis commands.
Variable Value spbm i-sid {all|config|discover} • all: displays all I-SID entries • config: displays configured I-SID entries • discover: displayes discovered I-SID entries vlan <1–4094> Displays I-SID information for the specified SPBM VLAN. id <1–16777214> Displays I-SID information for the specified I-SID. nick-name
Job aid The following sections describe the fields in the outputs for the C-VLAN I-SID show commands. show vlan i-sid The following table describes the fields in the output for the show vlan i-sid command.
Parameter Description VLAN_ID Indicates the VLAN IDs. I-SID Indicates the I-SIDs associated with the specified C- VLANs.
show i-sid The following table describes the fields in the output for the show i-sid command.
Parameter Description I-SID Indicates the I-SID IDs. Vid Indicates the VLAN IDs. UNI-type Indicates the UNI-type as CVLAN, switched, or transparent. Ports Indicates ports associated with the specific I-SIDs and VLANs.
show isis spbm i-sid The following describes the fields in the output for the show isis spbm i-sid command.
Parameter Description ISID Indicates the IS-IS SPBM I-SID identifier. SOURCE NAME Indicates the nickname of the node where this I-SID was configured or discovered. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 150 Comments on this document? [email protected] Displaying C-VLAN, Switched UNI, and Transparent UNI I-SID information
Parameter Description Note: SOURCE NAME is equivalent to nickname. VLAN Indicates the B-VLAN where this I-SID was configured or discovered. SYSID Indicates the system identifier. TYPE Indicates the SPBM I-SID type as either configured or discovered. HOST_NAME Indicates the host name of the multicast FIB entry.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 151 Comments on this document? [email protected] Chapter 9: Layer 2 VSN configuration using EDM
This section provides procedures to configure Layer 2 Virtual Services Networks (VSNs) using Enterprise Device Manager (EDM).
Configuring SPBM Layer 2 VSN C-VLANs After you configure the SPBM infrastructure, you can enable the SPBM Layer 2 Virtual Service Network (VSN) using the following procedure. SPBM supports Layer 2 VSN functionality where customer VLANs (C-VLANs) are bridged over the SPBM core infrastructure. At the BEBs, customer VLANs (C-VLAN) are mapped to I-SIDs based on the local service provisioning. Outgoing frames are encapsulated in a MAC-in-MAC header, and then forwarded across the core to the far-end BEB, which strips off the encapsulation and forwards the frame to the destination network based on the I-SID-to-C-VLAN provisioning. Before you begin • You must configure the required SPBM and IS-IS infrastructure, which includes the creation of SPBM B-VLANs. • You must create the customer VLANs (C-VLANs) and add slots/ports. About this task You can use C-VLAN UNI when either of the following apply: • Multiple ports must belong to the same broadcast domain. • A routing interface is required on a broadcast domain. Procedure 1. In the navigation pane, expand the following folders: Configuration > VLAN. 2. Click VLANs. 3. Click the Basic tab. 4. To map a C-VLAN to a Service instance identifier (I-SID), in the I-sid column, specify the I- SID to associate with the specified VLAN.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 152 Comments on this document? [email protected] Displaying the MAC address table for a C-VLAN
5. Click Apply. Important: • When a protocol VLAN is created, all ports are added to the VLAN including SPBM ports. To configure a protocol-based VLAN as a C-VLAN, you must first remove the SPBM-enabled ports from the protocol based VLAN, and then configure the protocol- based VLAN as a C-VLAN.
Displaying the MAC address table for a C-VLAN Use the following procedure to view the MAC Address table for a C-VLAN. Procedure 1. In the navigation tree, expand the following folders: ISIS > SPBM. 2. In the work area, click the MAC Addresses tab.
MAC Addresses field descriptions Use the data in the following table to use the MAC Addresses tab.
Name Description Isid Indicates the I-SID for this MAC address. Addr Indicates the customer MAC address for which the bridge has forwarding and/or filtering information CPort Either displays the value 0, or indicates the port on which a frame came from. CVlanId Indicates the VLAN ID for this MAC address. BDestAddr Indicates the provider MAC address for which the bridge has forwarding and/or filtering information. Type Indicates the MAC address learned type as local (C-VLAN or Switched UNI) or remote (B-VLAN). • Type remote shows a BDestAddr associated, but no CVlanID. • Type local shows a CVlanID associated, but no BDestAddr. Status Indicates the status of this entry: • other • invalid • learned • self Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 153 Comments on this document? [email protected] Layer 2 VSN configuration using EDM
Name Description • mgmt
Configuring Switched UNI and Transparent UNI Use the following procedure to configure a Switched UNI or to configure a Transparent UNI. About this task You map I-SIDs, VLANs, and ports for a Switched UNI. You map an I-SID to ports for a Transparent UNI. If you configure a Switched UNI, the VLAN must be type spbm-switchedUni. The port does not need to be a member of the VLAN; the port is automatically added to the associated VLAN when you create the Switched UNI. You do not configure the VLAN option if you configure a Transparent UNI. You can use Switched UNI when either of the following apply: • VLAN ID reuse is required. The same VLAN ID is used on different broadcast domains (multi- tenant applications). • Multiple VLANs must be part of the same broadcast domain. • VLAN ID translation is required. You can use Transparent UNI when either of the following apply: • All tagged and untagged traffic on a port must be classified into the same broadcast domain. • You want to offer a transparent provider solution. Procedure 1. In the navigation tree, expand the following folders: Configuration > IS-IS. 2. Click SPBM. 3. Click the Switched/Transparent UNIs tab. 4. To create a Switched UNI or Transparent UNI, click Insert. 5. Configure the parameters as required. You map I-SIDs, VLANs, and ports for a Switched UNI. You only map an I-SID to ports for a Transparent UNI. 6. Click Insert. 7. Click Apply.
Switched/Transparent UNIs field descriptions The following table describes fields on the Switched/Transparent UNIs tab.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 154 Comments on this document? [email protected] Configuring Switched UNI and Transparent UNI
Name Description Isid Specifies the I-SID of the Switched UNI or Transparent UNI. Port Specifies the port of the Switched UNI or Transparent UNI. UNI-type Specifies a UNI type of Switched or Transparent. The default is switched. Vlan Specifies the VLAN of the Switched UNI.
Note: You do not configure the VLAN option for Transparent UNIs. The Transparent UNI port or Transparent MLT is not a member of any VLAN or STG.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 155 Comments on this document? [email protected] Chapter 10: CFM fundamentals
The Shortest Path Bridging MAC (SPBM) network needs a mechanism to debug connectivity issues and to isolate faults. Connectivity Fault Management (CFM) operates at Layer 2 and provides an equivalent of ping and traceroute. To support troubleshooting of the SPBM cloud, Virtual Services Platform 7000 supports a subset of CFM functionality. CFM is based on the IEEE 802.1ag standard. IEEE 802.1ag Connectivity Fault Management (CFM) provides OAM tools for the service layer, which allows you to monitor and troubleshoot an end-to-end Ethernet service instance. CFM is the standard for Layer 2 ping, Layer 2 traceroute, and the end-to-end connectivity check of the Ethernet network. The 802.1ag feature divides or separates a network into administrative domains called Maintenance Domains (MD). Each MD is further subdivided into logical groupings called Maintenance Associations (MA). A single MD can contain several MAs. Each MA is defined by a set of Maintenance Points (MP). An MP is a demarcation point on an interface that participates in CFM within an MD. Two types of MP exist: • Maintenance End Point (MEP) • Maintenance Intermediate Point (MIP) CFM supports three kinds of standard CFM messages: Continuity Check Message (CCM), Loopback Message (LBM), and Link Trace Message (LTM). Messages are sent between Maintenance Points (MP) in the system. On Avaya Virtual Services Platform 7000 Series, CFM is implemented using the LBM and LTM features only to debug SPBM. CCM messages are not required or supported in the current release.
MD A Maintenance Domain (MD) is the part of a network that is controlled by a single administrator. For example, a customer can engage the services of a service provider, who, in turn, can engage the services of several operators. In this scenario, there can be one MD associated with the customer, one MD associated with the service provider, and one MD associated with each of the operators. You assign one of the following eight levels to the MD: • 0–2 (operator levels) • 3–4 (provider levels)
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 156 Comments on this document? [email protected] MA
• 5–7 (customer levels) The levels separate MDs from each other and provide different areas of functionality to different devices using the network. An MD is characterized by a level and an MD name (optional). A single MD can contain several Maintenance Associations (MA). Note: Avaya VSP 7000 Series supports one global MD, named spbm. The spbm MD has a default maintenance level of 4.
MA A Maintenance Association (MA) A represents a logical grouping of monitored entities within its Domain. It can therefore represent a set of Maintenance association End Points (MEPs), each configured with the same Maintenance Association ID (MAID) and MD Level, established to verify the integrity of a single service instance. The following figure shows MD level assignment in accordance with the 802.1ag standard. As shown in the figure, MIPs can be associated with MEPs. However, MIPs can also function independently of MEPs.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 157 Comments on this document? [email protected] CFM fundamentals
MEP A Maintenance Endpoint (MEP) represents a managed CFM entity, associated with a specific Domain Service Access Point (DoSAP) of a service instance, which can generate and receive CFM Protocol Data Units (PDU) and track any responses. A MEP is created by MEP ID under the context of an MA. MEP functionality can be divided into the following functions: • Fault Detection • Fault Verification • Fault Isolation
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 158 Comments on this document? [email protected] Fault verification
• Fault Notification Fault detection and notification are achieved through the use of Continuity Check Messages (CCM). CCM messages are not supported in the current release.
Fault verification Fault verification is achieved through the use of Loopback Messages (LBM). An LBM is a unicast message triggered by the operator issuing an operational command. LBM can be addressed to either a MEP or Maintenance Intermediate Point (MIP) but only a MEP can initiate an LBM. The destination MP can be addressed by its MAC address. The receiving MP responds with a Loopback Response (LBR). LBM can contain an arbitrary amount of data that can be used to diagnose faults as well as performance measurements. The receiving MP copies the data to the LBR.
LBM The Loopback Message (LBM) packet is often compared to a ping. A MEP transmits the LBM packet. This packet can be addressed to another MEP or to the MAC address of the MP; in the case of SPBM, this is the SPBM system ID. Only the MP for which the packet is addressed responds with an LBR message. You can trigger an LBM with the l2 ping command. • Provides “ICMP ping like” functionality natively at Layer 2. • DA is the MAC address of the target. • Includes a transaction identifier that allows the corresponding LBR to be identified when more than one LBM request is waiting for a response. • Only the target (MIP or MEP) responds. • Initiator can choose the size and contents data portion of the LBM frame. • Can be used to check the ability of the network to forward different sized frames.
Layer 2 ping The l2 ping command is a proprietary command that allows a user to trigger an LBM message. For B-VLANs, specify either the destination MAC address or node name. The l2 ping command provides a ping equivalent at Layer 2 for use with nodes on the SPBM B- VLAN in the customer domain.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 159 Comments on this document? [email protected] CFM fundamentals
Note: Layer 2 ping supports B-VLANs only.
Fault isolation Fault isolation is achieved through the use of Linktrace Messages (LTM). LTM is intercepted by all the MPs on the way to the destination MP. VSP 7000 supports two types of LTM. The first type, the unicast LTM, can be addressed to either MEP or MIP MAC address. Each MP on the way decrements the TTL field in the LTM frame, sends Linktrace Reply (LTR), and forwards the original LTM to the destination. The LTM forwards until it reaches the destination or the TTL value is decremented to zero. LTR is a unicast message addressed to the originating MEP. The second type, the proprietary LTM, is used to map the MAC addresses of the SPBM network; in this case the target MAC is a service instance identifier (I-SID), not an MP.
LTM CFM offers Linktrace message (LTM) for fault isolation. LTM allow operators, service providers and customers to verify the connectivity that they provide or use and to debug systems. Link trace message — unicast The LTM is often compared to traceroute. A MEP transmits the LTM packet. This packet specifies the target MAC address of an MP, which is the SPBM system ID. MPs on the path to the target address respond with an Linktrace reply (LTR). You can trigger an LTM with the l2 traceroute command. • LTM trace the path to any given MAC address or System Name. • DA is unicast • LTM contains: - Time to live (TTL) - Transaction Identifier - Originator MAC address - Target MAC address • CFM unaware entities forward the frame as is like any other data frame. • MIP or MEP that is not on the path to the target discards the LTM and does not reply. • MIP that is on the path to the target - Forwards the LTM after decrementing the TTL and replacing the SA with its own address. - Sends an LTR to the originator.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 160 Comments on this document? [email protected] Layer 2 traceroute
- Identifies itself in the forwarded LTM and LTR by modifying TLV information. • If the MIP or MEP is a target - Sends an LTR to the originator. - Identifies itself in the forwarded LTM and LTR by modifying TLV information. • A MEP that is not the target but is on the path to the target - Generates a reply as described above. - It also sets one of the flags fields in the reply to indicate that it is the terminal MEP. Link trace message — multicast The multicast LTM can be used to trace the multicast tree from any node on any I- SID using the nickname MAC address and the I-SID multicast address. Specifying a multicast target address for an LTM allows for the tracing of the multicast tree corresponding to that destination address (DA). With a multicast target every node that is in the active topology for that multicast address responds with a LTR and also forwards the LTM frame along the multicast path. Missing LTRs from the nodes in the path indicate the point of first failure. This functionality allows you to better troubleshoot I-SID multicast paths in a SPBM network. You can use the command l2 tracetree to trace the I-SID tree root.
Layer 2 traceroute The l2 traceroute command is a proprietary command that allows a user to trigger an LTM message. For B-VLANs, specify either the destination MAC address or node name. The l2 traceroute command provides a trace equivalent at Layer 2 for use with nodes on the SPBM B-VLAN in the customer domain. Note: Layer 2 traceroute supports B-VLANs only.
Layer 2 tracetree The l2 tracetree command is a proprietary command that allows you to trigger a multicast LTM by specifying the B-VLAN and I-SID. Layer 2 tracetree allows you to view a multicast tree on the SPBM B-VLAN from the source node to the destination nodes for a particular I-SID.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 161 Comments on this document? [email protected] CFM fundamentals
MIP Maintenance domain intermediate points (MIPs) do not initialize any CFM messages. MIPs passively receive CFM messages, process the messages received and respond back to the originating MEP. By responding to received CFM messages, MIPs can support discovery of hop-by- hop path among MEPs, allow connection failures to be isolated to smaller segments of the network to help discover location of faults along the paths. MIP functionality can be summarized as: • Respond to Loopback (ping) messages at the same level as itself and addressed to it. • Respond to Linktrace (traceroute) messages. • Forward Linktrace messages after decrementing the TTL.
Nodal MPs Nodal MPs provide both MEP and MIP functionality for SPBM deployments. Nodal MPs are associated with a B-VLAN and are VLAN encapsulated packets. The Nodal MEP provides traceability and troubleshooting at the system level for a given B-VLAN. Each switch has a given MAC address and communicates with other switches. The SPBM instance MAC address is used as the MAC address of the Nodal MP. The Nodal B-VLAN MPs supports eight levels of CFM.
Configuration considerations When you configure CFM, be aware of the following configuration considerations: • The Maintenance level for MEPs and MIPs on a given B-VID (in a network) must be configured to the same level for them to respond to a given CFM command. • CFM is supported only on B-VLANs.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 162 Comments on this document? [email protected] Chapter 11: CFM configuration using ACLI
This section provides procedures to configure and use Connectivity Fault Management (CFM) using Avaya Command Line Interface (ACLI). The Shortest Path Bridging MAC (SPBM) network needs a mechanism to debug connectivity issues and to isolate faults. This is performed at Layer 2, not Layer 3. To support troubleshooting of the SPBM cloud, Virtual Services Platform 7000 Series supports a subset of CFM functionality. Note: When you enable CFM in an SBPM network, Avaya recommends that you enable CFM on the Backbone Edge Bridges (BEB) and on all Backbone Core Bridges (BCB). If you do not enable CFM on a particular node, you cannot obtain CFM debug information from that node.
Configuring CFM Use this procedure to configure auto-generated CFM Maintenance End Points (MEPs) and Maintenance Intermediate Point (MIP) level for every SPBM B-VLAN on the VSP 7000. This procedure automatically configures a Maintenance Domain (MD) , Maintenance Associations (MAs), MEP ID, and also associates the MEPs and MIP level to the SPBM VLANs. About this task When you enable CFM, you create a global MD (named spbm) for all the SPBM Nodal MEPs. The spbm MD has a default maintenance level of 4, which you can change with the level attribute. All the MEPs created use the MEP ID configured under the global context, which has a default value of 1. You can only modify the global context when CFM is disabled. The Nodal MEPs automatically associate with SPBM VLANs and associate to any SPBM VLAN added later. The MIP level maps to the global level. The MIP level automatically associates with the SPBM VLANs when CFM is enabled, and associate to any SPBM VLAN added later. Procedure 1. Enter Global Configuration mode: enable configure terminal 2. Configure the maintenance level for every CFM MEP and MIP level on all SPBM VLANs:
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 163 Comments on this document? [email protected] CFM configuration using ACLI
Note: You can change the level before or after CFM is enabled. The default level is 4. cfm spbm [level <0–7>] 3. Assign a global CFM MEP ID for all CFM SPBM MEPs: Note: You can change the MEP ID only when CFM is disabled. cfm spbm mepid <1–8191> 4. Enable the CFM: cfm spbm enable 5. Display the global CFM SPBM configuration: show cfm spbm 6. If you want to default the CFM MD level, use the following command: default cfm spbm level 7. If you want to default the MEP identifier, use the following command: default cfm spbm mepid 8. If you want to disable CFM, use one of the following commands: no cfm spbm enable default cfm spbm enable Example 7024XLS> enable 7024XLS# configure terminal 7024XLS(config)# cfm spbm level 4 7024XLS(config)# cfm spbm mepid 200 7024XLS(config)# cfm spbm enable 7024XLS(config)# show cfm spbm ======Cfm Spbm ======LEVEL ADMIN MEP ID MAC ------4 disabled 1 00:00:00:00:00:00
Variable definitions Use the data in the following table to use the cfm spbm commands.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 164 Comments on this document? [email protected] Triggering a LBM Layer 2 ping
Variable Value cfm spbm level <0–7> Specifies the CFM MD level. The default is 4. cfm spbm mepid <1–8191> Specifies the MEP ID. The default is 1.
Note: You can only modify the MEP ID when CFM is disabled. cfm spbm enable Enables CFM globally. no cfm spbm enable Disables CFM globally. default cfm spbm level Defaults the CFM MD level. default cfm spbm mepid Defaults the CFM MEP ID. default cfm spbm enable Defaults CFM. Default is globally disabled. show cfm spbm Displays the current CFM configuration.
Triggering a LBM Layer 2 ping Use this procedure to trigger a Layer 2 ping, which acts like native ping. This feature enables CFM to debug Layer 2. Before you begin CFM SPBM must be enabled. About this task The LBM packet is often compared to ping. An MEP transmits the loopback message to an intermediate or endpoint within a domain for the purpose of fault verification. This can be used to check the ability of the network to forward different sized frames. Procedure 1. Enter Privileged EXEC mode: enable 2. Trigger a Layer 2 ping: l2 ping {vlan <1–4094> routernodename WORD<0–255> | vlan <1–4094> mac <0x00:0x00:0x00:0x00:0x00:0x00>} [burst-count <1–200>] [data- tlv-size <0–400>] [frame-size <64–1500>] [priority <0–7>] [source- mode
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 165 Comments on this document? [email protected] CFM configuration using ACLI
Example 7024XLS# l2 ping vlan 500 mac 00.14.0d.bf.a3.df Please wait for l2ping to complete or press any key to abort ----00:14:0d:bf:a3:df L2 PING Statistics---- 0(68) bytes of data 1 packets transmitted, 0 packets received, 100.00% packet loss 7024XLS# l2 ping vlan 500 routernodename VSP-MONTI0 Please wait for l2ping to complete or press any key to abort
----00:14:0d:a2:b3:df L2 PING Statistics---- 0(68) bytes of data 1 packets transmitted, 1 packets received, 0.00% packet loss round-trip (us) min/max/ave/stdv = 26895/26895/26895.00/ 0.00
Variable definitions Use the data in the following table to configure the l2 ping parameters.
Variable Value vlan <1–4094> routernodename Specifies the destination for the Layer 2 ping: WORD<0–255> • <1–4094> — Specifies the VLAN ID. vlan <1–4094> mac • WORD<0–255> — Specifies the Router node name. <0x00:0x00:0x00:0x00:0x00:0x00> •
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 166 Comments on this document? [email protected] Triggering a LTM Layer 2 traceroute
Triggering a LTM Layer 2 traceroute Use this procedure to trigger a Layer 2 traceroute, which acts like native traceroute. This feature enables CFM to debug Layer 2. Important: The MAC address must be learned before you can trace a route to a MAC address. For B- VLANs, IS-IS learns the MAC addresses and populates the FDB table. linktrace traces the path up to the closest device to that MAC address that supports CFM. Before you begin CFM SPBM must be enabled. About this task The link trace message is often compared to traceroute. An MEP transmits the Linktrace Message packet to a maintenance endpoint with intermediate points responding to indicate the path of the traffic within a domain for the purpose of fault isolation. The packet specifies the target MAC address of an MP, which is the SPBM system ID. MPs on the path to the target address respond with an LTR. Procedure 1. Enter Privileged EXEC mode: enable 2. Trigger a Layer 2 traceroute: l2 traceroute {
l2traceroute to VSP-MONTI0 (00:14:0d:a2:b3:df), vlan 500 0 VSP-PETER4 (00:15:9b:11:33:df) 1 VSP-MONTI0 (00:14:0d:a2:b3:df)
Variable definitions Use the data in the following table to use the l2 traceroute command.
Variable Value vlan <1–4094> routernodename Specifies the destination for the Layer 2 traceroute: WORD<0–255>} • <1–4094> — Specifies the VLAN ID Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 167 Comments on this document? [email protected] CFM configuration using ACLI
Variable Value vlan <1–4094> mac • WORD<0–255> — Specifies the Router Node Name <0x00:0x00:0x00:0x00:0x00:0x00>} •
Triggering a LTM Layer 2 tracetree Use this procedure to trigger a Layer 2 tracetree. Layer 2 tracetree allows a user to trigger a multicast LTM message by specifying the B-VLAN and I-SID. The command allows the user to view a multicast tree on the SPBM B-VLAN from the source node to the destination nodes for a particular I-SID. Before you begin CFM SPBM must be enabled. Procedure 1. Enter Privileged EXEC mode: enable 2. Trigger a Layer 2 tracetree: l2 tracetree vlan <1–4094> isid <1–16777215> [routernodename WORD<0– 255> | mac <0x00:0x00:0x00:0x00:0x00:0x00>] [priority <0–7>] [source-mode
Please wait for l2tracetree to complete or press any key to abort
l2tracetree to 53:55:10:00:00:01, vlan 2 i-sid 1 nickname 5.55.10 hops 64 1 VSP-PETER4 00:15:9b:11:33:df -> VSP-MONTI0 00:14:0d:a2:b3:df 2 VSP-MONTI0 00:14:0d:a2:b3:df -> VSP-LEE2 00:15:e8:b8:a3:df
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 168 Comments on this document? [email protected] Triggering a LTM Layer 2 tracetree
Variable definitions Use the data in the following table to use the l2 tracetree command.
Variable Value vlan<1–4094>isid <1–16777215> • <1–4094> — Specifies the VLAN ID. • <1–16777215> — Specifies the I-SID. routernodename WORD<0–255> WORD<0–255> — Specifies the Router Node Name. mac <0x00:0x00:0x00:0x00:0x00:0x00> <0x00:0x00:0x00:0x00:0x00:0x00> — Specifies the MAC address. priority <0–7> Specifies the priority value. The default is 7. source-mode
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 169 Comments on this document? [email protected] Chapter 12: CFM configuration using EDM
This section provides procedures to configure Connectivity Fault Management (CFM) using Enterprise Device Manager (EDM). Note: When you enable CFM in an SBPM network, Avaya recommends that you enable CFM on the Backbone Edge Bridges (BEB) and on all Backbone Core Bridges (BCB). If you do not enable CFM on a particular node, you cannot obtain CFM debug information from that node.
Configuring CFM Use this procedure to configure auto-generated CFM Maintenance End Points (MEPs) and Maintenance Intermediate Point (MIP) level for every SPBM B-VLAN on the VSP 7000. This procedure automatically configures a Maintenance Domain (MD), Maintenance Associations (MAs), MEP ID, and also associates the MEPs and MIP level to the SPBM VLANs. About this task When you enable CFM, you create a global MD (named spbm) for all the SPBM Nodal MEPs. The spbm MD has a default maintenance level of 4, which you can change with the level attribute. All the MEPs created use the MEP ID configured under the global context, which has a default value of 1. You can only modify the global context when CFM is disabled. The Nodal MEPs automatically associate with SPBM VLANs and associate to any SPBM VLAN added later. The MIP level maps to the global level. The MIP level automatically associates with the SPBM VLANs when CFM is enabled, and associate to any SPBM VLAN added later. Procedure 1. From the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click CFM. 3. Click the Globals tab. 4. In the SpbmAdminState field, click a radio button to enable or disable CFM. specify an index value, name, and level for the MD. 5. In the SpbmLevel field, configure the maintenance level for every CFM MEP and MIP level on all the SPBM VLANs. 6. In the SpbmMepId field, assign a global CFM MEP ID for all CFM SPBM MEPs.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 170 Comments on this document? [email protected] Displaying CFM MD
7. On the toolbar, click Apply.
Globals field descriptions Use the data in the following table to use the Globals tab.
Name Description EtherType Read only Ethernet type value. Value of 0x8902 SpbmAdminState Enables or disables the SPBM CFM MD. Click the enable or disable radio button. SpbmLevel Specifies the MD level. Default is level 4. SpbmMepId Specifies the MEP identifier. Default is 1
Displaying CFM MD Use this procedure to display the Connectivity Fault Management (CFM) Maintenance Domain (MD). An MD is the part of a network that is controlled by a single administrator. A single MD can contain several Maintenance Associations (MA). Procedure 1. From the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click CFM. 3. Click the MD tab. 4. On the toolbar, click Refresh to display the current MD configuration.
MD field descriptions Use the data in the following table to use the MD tab.
Name Description Index Specifies a maintenance domain entry index. Name Specifies the MD name. NumOfMa Indicates the number of MAs that belong to this maintenance domain. Level Specifies the MD maintenance level. The default is 4. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 171 Comments on this document? [email protected] CFM configuration using EDM
Name Description NumOfMip Indicates the number of MIPs that belong to this maintenance domain Type Indicates the type of domain.
Displaying CFM MA Use this procedure to display a CFM Maintenance Association (MA). An MA represents a logical grouping of monitored entities within its Domain. It can therefore represent a set of Maintenance Endpoints (MEPs), each configured with the same Maintenance Association ID (MAID) and MD Level, established to verify the integrity of a single service instance. Before you begin You must configure a CFM MD. Procedure 1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click CFM. 3. Click the MD tab. 4. Select an existing MD. 5. On the toolbar, click MaintenanceAssociation.
MA field descriptions Use the data in the following table to use the MA tab.
Name Description DomainIndex Specifies the maintenance domain entry index. AssociationIndex Specifies a maintenance association entry index. DomainName Specifies the MD name. AssociationName Specifies the MA name. NumOfMep Indicates the number of MEPs that belong to this maintenance association.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 172 Comments on this document? [email protected] Displaying CFM MEP
Displaying CFM MEP Use this procedure to display the CFM Maintenance Endpoint (MEP). A MEP represents a managed CFM entity, associated with a specific Domain Service Access Point (DoSAP) of a service instance, which can generate and receive CFM Protocol Data Units (PDU) and track any responses. A MEP is created by MEP ID under the context of an MA. Procedure 1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click CFM. 3. Click the MD tab. 4. Select an existing MD, and then click MaintenanceAssociation. 5. In the MA tab, select an existing MA, and then click MaintenanceEndpoint.
MEP field descriptions Use the data in the following table to use the MEP tab.
Name Description DomainIndex Specifies the MD index. AssociationIndex Specifies the MA index. Id Specifies the MEP ID. DomainName Specifies the MD name. AssociationName Specifies the MA name. AdminState Specifies the administrative state of the MEP. The default is disable. MepType Specifies the MEP type: • trunk • sg • endpt • vlan • port • endptClient • nodal • remotetrunk • remotesg • remoteendpt Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 173 Comments on this document? [email protected] CFM configuration using EDM
Name Description • remoteVlan • remotePort • remoteEndptClient ServiceDescription Specifies the service to which this MEP is assigned.
Configuring Layer 2 ping Use this procedure to configure a Layer 2 ping. This feature enables CFM to debug Layer 2. It can also help you debug ARP problems by providing the ability to troubleshoot next hop ARP records. Before you begin CFM SPBM must be enabled. Procedure 1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click L2Ping/L2Trace Route. 3. From the L2Ping tab, configure the Layer 2 ping properties. 4. To initiate a Layer 2 ping, highlight an entry and click the Start button. 5. To update a Layer 2 ping, click the Refresh button. 6. To stop the Layer 2 ping, click the Stop button.
L2Ping field descriptions Use the data in the following table to use the L2Ping tab.
Name Description VlanId Identifies the backbone VLAN. DestMacAddress Specifies the target MAC address. HostName Specifies the target host name. DestIsHostName Indicates whether the host name is (true) or is not (false) used for L2Ping transmission. Messages Specifies the number of L2Ping messages to be transmitted. The default is 1. Status Specifies the status of the transmit loopback service: • ready: the service is available. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 174 Comments on this document? [email protected] Configuring Layer 2 ping
Name Description • transmit: the service is transmitting, or about to transmit, the L2Ping messages. • abort: the service aborted or is about to abort the L2Ping messages. This field is also used to avoid concurrency or race condition problems that can occur if two or more management entities try to use the service at the same time. The default is ready. ResultOk Indicates the result of the operation: • true: the L2Ping Messages will be (or have been) sent. • false: the L2Ping Messages will not be sent. The default is true. Priority Specifies a 3–bit value to be used in the VLAN header, if present in the transmitted frame. The default is 7. TimeoutInt Specifies the interval to wait for an L2Ping time-out. The default value is 3 seconds. TestPattern Specifies the test pattern to use in the L2Ping PDU: • allZero: null signal without cyclic redundancy check • allZeroCrc: null signal with cyclic redundancy check with 32-bit polynomial • pseudoRandomBitSequence: pseudo-random-bit- sequence without cyclic redundancy check • pseudoRandomBitSequenceCrc: pseudo-random- bit-sequence with cyclic redundancy check with 32- bit polynomial. A cyclic redundancy check is a code that detects errors. The default value is allZero. DataSize Specifies an arbitrary amount of data to be included in the data TLV, if the data size is selected to be sent. The default is 0. FrameSize Specifies the frame size. If the frame size is specified then the data size is internally calculated and the calculated data size is included in the data TLV. The default is 0. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 175 Comments on this document? [email protected] CFM configuration using EDM
Name Description SourceMode Specifies the source mode of the transmit loopback service: • nodal • smltVirtual–Use this value with B-VLANs only. The default is nodal. SeqNumber The transaction identifier/sequence number of the first loopback message (to be) sent. The default is 0. Result Displays the Layer 2 Ping result.
Initiating a Layer 2 traceroute Use this procedure to trigger a Layer 2 traceroute. This feature enables CFM to debug Layer 2. If you configure IsTraceTree to false then EDM performs Traceroute on the unicast path. If you configure IsTraceTree to true then EDM performs TraceTree on the multicast tree. Important: The MAC address must be learned before you can trace a route to a MAC address. For B-VLANs, IS-IS learns the MAC address and populates the FDB table. Linktrace traces the path up to the closest device to that MAC address that supports CFM. Before you begin CFM SPBM must be enabled. Procedure 1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click L2Ping/L2Trace Route. 3. Click the L2 Traceroute/TraceTree tab. 4. To configure the traceroute or tracetree, highlight an entry and populate the required column fields. 5. To start the traceroute, click the Start button. 6. To update the traceroute, click the Refresh button. 7. To stop the traceroute, click the Stop button.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 176 Comments on this document? [email protected] Initiating a Layer 2 traceroute
L2Traceroute field descriptions Use the data in the following table to use the L2Traceroute tab.
Name Description VlanId Specifies a value that uniquely identifies the Backbone VLAN (B-VLAN). Priority Specifies a 3–bit value to be used in the VLAN header, if present in the transmitted frame. The default is 7. DestMacAddress Specifies the target MAC address. HostName Specifies the target host name. DestIsHostName Specifies whether the host name is (true) or is not (false) used for the L2Trace transmission. Isid Specifies the Service Instance Identifier (I-SID). NickName Indicates the SPBM node nickname IsidTree Specifies whether the multicast tree or unicast path is traced. If you configure IsidTree to false then EDM performs Traceroute on the unicast path. If you configure IsifTree to true then EDM performs TraceTree on the multicast tree. Status Indicates the status of the transmit loopback service: • ready: the service is available. • transmit: the service is transmitting, or about to transmit, the L2Trace messages. • abort: the service aborted or is about to abort the L2Trace messages. This field is also used to avoid concurrency or race condition problems that can occur if two or more management entities try to use the service at the same time. The default is ready. ResultOk Indicates the result of the operation: • true: the L2Trace messages will be (or have been) sent. • false: the L2Trace messages will not be sent. The default is true. Ttl Specifies the number of hops remaining to this L2Trace. Table continues…
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 177 Comments on this document? [email protected] CFM configuration using EDM
Name Description This value is decremented by 1 by each Bridge that handles the L2Trace. The decremented value is returned in the L2Trace. If 0 on output, the L2Trace is not transmitted to the next hop. The value of the time-to-live (TTL) field in the L2Trace is defined by the originating MEP. The default value is 64. SourceMode Specifies the source mode of the transmit loopback service. • nodal • smltVirtual–Use this value with B-VLANs only. The default is nodal. SeqNumber Specifies the transaction identifier/sequence number of the first loopback message (to be) sent. The default is 0. Flag L2Trace result flag indicating L2Trace status or error code: • none (1): No error • internalError (2): L2Trace internal error • invalidMac (3): Invalid MAC address • mepDisabled (4): MEP must be enabled in order to perform L2Trace • noL2TraceResponse (5): No L2Trace response received • l2TraceToOwnMepMac (6): L2Trace to own MEP MAC is not sent • l2TraceComplete (7): L2Trace completed • l2TraceLookupFailure (8): Lookup failure for L2Trace • l2TraceLeafNode (9): On a leaf node in the I-SID tree • l2TraceNotInTree (10): Not in the I-SID tree
Viewing Layer 2 traceroute results Use this procedure to view Layer 2 traceroute results. This feature enables CFM to debug Layer 2. You can use Layer 2 traceroute to debug ARP problems by troubleshooting next hop ARP records.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 178 Comments on this document? [email protected] Viewing Layer 2 traceroute results
About this task You can display Layer 2 tracetree results to view a multicast tree on the SPBM B-VLAN from the source node to the destination nodes for a particular I-SID. Procedure 1. In the navigation tree, expand the following folders: Configuration > Edit > Diagnostics. 2. Click L2Ping/L2Trace Route. 3. Click the L2Traceroute/TraceTree tab. 4. Click the Refresh button to update the results. 5. To view the traceroute results, highlight an entry, and then click Result.
L2 Traceroute Result field descriptions Use the data in the following table to use the L2 Traceroute Result tab.
Name Description VlanId A value that uniquely identifies the Backbone VLAN (B-VLAN). SeqNumber The transaction identifier/sequence number returned by a previous transmit linktrace message command, indicating which L2Trace's response of the L2Trace is going to be returned. The default is 0. Hop The number of hops away from L2Trace initiator. ReceiveOrder An index to distinguish among multiple L2Trace responses with the same Transaction Identifier field value. This value is assigned sequentially from 1, in the order that the Linktrace Initiator received the responses. Ttl Time-to-Live (TTL) field value for a returned L2Trace response. SrcMac MAC address of the MP that responds to the L2Trace request for this L2TraceReply. HostName The host name of the replying node. LastSrcMac The MAC address of the node that forwarded the L2Trace to the responding node. LastHostName The host name of the node that forwarded the L2Trace to the responding node.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 179 Comments on this document? [email protected] Glossary
Access switch An access switch is located at the edge of the network. An access switch connects to multiple end devices, such as PCs and work stations.
Aggregation switch An aggregation switch is located at the center of the network. An aggregation switch connects one or more access-switches.
Autonomous System A set of routers under a single technical administration, using a single IGP (AS) and common metrics to route packets within the AS, and using an EGP to route packets to other ASs.
autonomous system A router attached at the edge of an OSPF network. An ASBR uses one or border router (ASBR) more interfaces that run an interdomain routing protocol such as BGP. In addition, a router distributing static routes or Routing Information Protocol (RIP) routes into OSPF is considered an ASBR.
Autonomous System A two-byte number that is used to identify a specific AS. Number (ASN)
Avaya command line A textual user interface. When you use ACLI, you respond to a prompt by interface (ACLI) typing a command. After you enter the command, you receive a system response.
Backbone Core Backbone Core Bridges (BCB) form the core of the SPBM network. Bridge (BCB) Backbone Core Bridges (BCBs) forward encapsulated traffic based on the Backbone MAC Destination Address (BMAC-DA).
Backbone Edge Backbone Edge Bridge (BEB) handle the boundary between the core MAC- Bridge (BEB) in-MAC Shortest Bath Bridging MAC (SPBM) domain and the edge customer 802.1Q domain. I-SIDs are provisioned on the BEBs to be associated with a particular service instance. In the SPBM core, the bridges are referred to as Backbone Core Bridges (BCBs). BCBs forward encapsulated traffic based on the Backbone MAC Destination Address (BMAC-DA).
Backbone MAC In Provider Backbone Bridging (PBB) MAC-in-MAC encapsulation, (BMAC) customer MAC addresses are encapsulated in Backbone MAC (BMAC) addresses. MAC-in-MAC encapsulation defines a BMAC-DA and BMAC-SA to identify the backbone source and destination addresses. The originating node creates a MAC header that is used for delivery from end to end. As the MAC header stays the same across the network, there is no need to
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 180 Comments on this document? [email protected] Backbone VLAN identifier (B-VID)
swap a label or do a route lookup at each node, allowing the frame to follow the most efficient forwarding path end to end. In Shortest Path Bridging MAC (SPBM), each node has a System ID, which is used in the topology announcement. This same System ID also serves as the switch Backbone MAC address (B-MAC), which is used as the source and destination MAC address in the SPBM network.
Backbone VLAN The Backbone VLAN identifier (B-VID) indicates the Shortest Path Bridging identifier (B-VID) MAC (SPBM) B-VLAN associated with the SPBM instance.
Border Gateway An inter-domain routing protocol that provides loop-free inter-domain Protocol (BGP) routing between Autonomous Systems (AS) or within an AS.
Circuitless IP (CLIP) A virtual interface that does not map to any physical interface. This interface is often called a loopback.
Complete Sequence Complete Sequence Number Packets (CSNP) contain the most recent Number Packets sequence numbers of all Link State Packets (LSPs) in the database. When (CSNP) all routers update their LSP database, synchronization is complete.
Connectivity Fault Connectivity Fault Management is a mechanism to debug connectivity Management (CFM) issues and to isolate faults within the Shortest Path Bridging-MAC (SPBM) network. CFM operates at Layer 2 and provides the equivalent of ping and traceroute. IEEE 802.1ag Connectivity Fault Management (CFM) divides or separates a network into administrative domains called Maintenance Domains (MD). Each MD is further subdivided into logical groupings called Maintenance Associations (MA). Each MA is defined by a set of Maintenance Points (MP). An MP is a demarcation point on an interface that participates in CFM within an MD.
Control Processor The Control Processor module is responsible for running all high level (CP) module protocols (BGP, OSPF) and distributing the results (routing updates) to the rest of the system, managing and configuring the IO and Switch Fabric modules, and maintaining and monitoring the health of the chassis.
Customer MAC (C- For customer MAC (C-MAC) addresses, which is customer traffic, to be MAC) forwarded across the service provider back, SPBM uses IEEE 802.1ah Provider Backbone Bridging MAC-in-MAC encapsulation. The C-MAC addresses are hidden in a backbone MAC (B-MAC) address pair made up of a BMAC destination address (BMAC-DA) and a BMAC source address (BMAC-SA).
Designated A Designated Intermediate System (DIS) is the designated router in Intermediate System Intermediate System to Intermediate System (IS-IS) terminology. You can (DIS) modify the priority to affect the likelihood of a router being elected the designated router. The higher the priority, the more likely the router is to be elected as the DIS. If two routers have the same priority, the router with the
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 181 Comments on this document? [email protected] Glossary
highest MAC address (Sequence Number Packet [SNP] address) is elected as the DIS.
Distributed MultiLink A point-to-point connection that aggregates similar ports from different Trunking (DMLT) modules to logically act like a single port, but with the aggregated bandwidth.
Enterprise Device A Web-based embedded management system to support single-element Manager (EDM) management. EDM provides complete configuration management functionality for the supported devices and is supplied to the customer as embedded software in the device. equal cost multipath Distributes routing traffic among multiple equal-cost routes. (ECMP) graphical user A graphical (rather than textual) computer interface. interface (GUI)
IEEE 802.1aq IEEE 802.1aq is the standard for Shortest Path Bridging MAC (SPBM). SPBM makes network virtualization much easier to deploy within, reducing the complexity of the network while at the same time providing greater scalability. SPBM eliminates the need for multiple overlay protocols in the core of the network by reducing the core to a single Ethernet based link state protocol which can provide virtualization services, both layer 2 and layer 3, using a pure Ethernet technology base.
Institute of Electrical An international professional society that issues standards and is a member and Electronics of the American National Standards Institute, the International Standards Engineers (IEEE) Institute, and the International Standards Organization.
Interior Gateway Distributes routing information between routers that belong to a single Protocol (IGP) Autonomous System (AS).
Intermediate System Intermediate System to Intermediate System( IS-IS) is a link-state, interior to Intermediate gateway protocol that was developed for the International Organization for System (IS-IS) Standardization (ISO). ISO terminology refers to routers as Intermediate Systems (IS), hence the name Intermediate System-to-Intermediate System (IS-IS). IS-IS operation is similar to Open Shortest Path First (OSPF). Both protocols divide large domains into smaller areas, and both use the shortest path first (SPF) algorithm and link state information to determine the best path to a destination. In Shortest Path Bridging-MAC (SPBM) networks, IS-IS discovers network topology and builds shortest path trees between network nodes that are used for forwarding unicast traffic and determining the forwarding table for multicast traffic. In SPBM networks, IS-IS also communicates information in the control plane, which is instance service indentifier (I-SID) information.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 182 Comments on this document? [email protected] Internet Protocol multicast (IPMC)
SPBM employs IS-IS as the interior gateway protocol and implements additional Type-Length-Values (TLVs) to support additional functionality.
Internet Protocol The technology foundation for audio and video streaming, push multicast (IPMC) applications, software distribution, multipoint conferencing, and proxy and caching solutions.
interswitch trunking A feature that uses one or more parallel point-to-point links to connect two (IST) aggregation switches. The two aggregation switches use this channel to share information and operate as a single logical switch. Only one interswitch trunk can exist on each Split Multilink Trunking (SMLT) aggregation switch. interswitch trunking A feature that uses one or more parallel point-to-point links to connect two (IST) aggregation switches. The two aggregation switches use this channel to share information and operate as a single logical switch. Only one interswitch trunk can exist on each Split Multilink Trunking (SMLT) aggregation switch.
IS-IS Hello packets Intermediate System to Intermediate System (IS-IS) uses Hello packets to initialize and maintain adjacencies between neighboring routers. IS-IS Hello packets contain the IP address of the interface over which the Hello is transmitted. These packets are broadcast to discover the identities of neighboring IS-IS systems and to determine whether the neighbor is a Level 1 router.
Layer 1 The Physical Layer of the Open System Interconnection (OSI) model. Layer 1 interfaces with the MAC sublayer of Layer 2, and performs character encoding, transmission, reception, and character decoding.
Layer 2 The Data Link Layer of the OSI model. Examples of Layer 2 protocols are Ethernet and Frame Relay.
Layer 2 Virtual Layer 2 Virtual Services Network (L2 VSN) feature provides IP connectivity Services Network over SPBM for VLANs. Layer 2 virtualization is handled by the Backbone Edge Bridges (BEBs) where the end-user VLAN is mapped into a Backbone Service Instance Identifier (I-SID) by local provisioning. Any BEB that has the same I-SID configured can participate in the same Layer 2 Virtual Services Network (VSN). IS-IS within the SPBM backbone is used as the Layer 2 routing protocol to forward traffic between the BEB and Provider Backbone Core Bridges (BCBs). Only the BEB has knowledge of the Layer 2 VSN and corresponding MAC addresses. The BCB only has knowledge of each Backbone MAC address (B-MAC) used to send traffic across an SPBM network.
Link Layer Discovery Link Layer Discovery Protocol is used by network devices to advertise their Protocol (LLDP) identities. Devices send LLDP information at fixed intervals in the form of
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 183 Comments on this document? [email protected] Glossary
Ethernet frames, with each frame having one Link Layer Discovery Protocol Data Unit.
Link State Packets Link State Packets (LSP) contain information about the state of adjacencies (LSP) or defined and distributed static routes. Intermediate System to Intermediate System (IS-IS) exchanges this information with neighboring IS-IS routers at periodic intervals. Every router in the domain has an identical link state database and each runs shortest path first to calculate routes.
Link State Protocol Link State Protocol Data Unit is similar to a Link State Advertisement in Data Unit (LSPDUs) Open Shortest Path First (OSPF). Intermediate System to Intermediate System (IS-IS) runs on all nodes of Shortest Path Bridging-MAC (SPBM). Since IS-IS is the basis of SPBM, the IS-IS adjacency must be formed first by first sending out hellos and then Link State Protocol Data Units. After the hellos are confirmed both nodes sends Link State Protocol Data Units (LSPDUs) that contain connectivity information for the SPBM node. These nodes also send copies of all other LSPDUs they have in their databases. This establishes a network of connectivity providing the necessary information for each node to find the best and proper path to all destinations in the network. link trace message The link trace message (LTM) is often compared to traceroute. A MEP transmits the LTM packet. This packet specifies the target MAC address of an MP which is the SPBM system id or the virtual SMLT MAC. MPs on the path to the target address respond with an LTR. LTM contains: • Time to live (TTL) • Transaction Identifier • Originator MAC address • Target MAC address link-state database A database built by each OSPF router to store LSA information. The router (LSDB) uses the LSDB to calculate the shortest path to each destination in the Autonomous System (AS), with itself at the root of each path.
Local Area Network A data communications system that lies within a limited spatial area, uses a (LAN) specific user group and topology, and can connect to a public switched telecommunications network (but is not one).
Loopback Messages A Loopback Message (LBM) is a unicast message triggered by the operator (LBM) issuing an operational command. LBM can be addressed to either a Maintenance End Point (MEP) or Maintenance Intermediate Point (MIP), but only a MEP can initiate an LBM. The destination MP can be addressed by its MAC address. The receiving MP responds with a Loopback Response (LBR). LBM can contain an arbitrary amount of data that can be used to diagnose faults as well as performance measurements. The
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 184 Comments on this document? [email protected] Loopback Response (LBR)
receiving MP copies the data to the LBR. Fault verification is achieved through the use of Loopback Messages (LBM).
Loopback Response Loopback Response (LBR) is the response from a Maintenance Point (MP). (LBR)
MAC-in-MAC MAC-in-MAC encapsulation defines a BMAC-DA and BMAC-SA to identify encapsulation the backbone source and destination addresses. The originating node creates a MAC header that is used for delivery from end to end. As the MAC header stays the same across the network, there is no need to swap a label or do a route lookup at each node, allowing the frame to follow the most efficient forwarding path end to end.
Maintenance Maintenance Associations (MA) are administrative associations in a Associations (MA) network that is divided by the 802.1ag Connectivity Fault Management (CFM) feature. MAs are grouped within Maintenance Domains. Each MA is defined by a set of Maintenance Points (MP). An MP is a demarcation point on an interface that participates in CFM within an MD. Connectivity Fault Management is a mechanism to debug connectivity issues and to isolate faults within the Shortest Path Bridging MAC (SPBM) Network.
Maintenance Maintenance Domains (MD) are administrative domains that a network is Domains (MD) divided by the 802.1ag Connectivity Fault Management (CFM) feature. Each MD is further subdivided into logical groupings called Maintenance Associations (MA). Connectivity Fault Management is a mechanism to debug connectivity issues and to isolate faults within the Shortest Path Bridging MAC (SPBM) Network.
Maintenance Points Maintenance Points (MP) are a demarcation point on an interface that (MP) participates in Connectivity Fault Management (CFM) within a Maintenance Domain (MD). There are two types of MP: Maintenance End Point (MEP) and Maintenance Intermediate Point (MIP). Connectivity Fault Management is a mechanism to debug connectivity issues and to isolate faults within the Shortest Path Bridging MAC (SPBM) Network.
MD5 Authentication MD5 authentication creates an encoded checksum in the transmitted packet. The receiving router uses an authentication key (password) to verify the packet’s MD5 checksum. There is an optional key ID.
Media Access Arbitrates access to and from a shared medium. Control (MAC) multicast group ID The multicast group ID (MGID) is a hardware mechanism the switch uses to (MGID) send data to several ports simultaneously. Instead of sending the data to a specific port number, the data is directed to an MGID. The switch maintains a table that maps MGIDs to their member ports. Both virtual LAN (VLAN) and IP multicast (IPMC) use MGIDs.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 185 Comments on this document? [email protected] Glossary
MultiLink Trunking A method of link aggregation that uses multiple Ethernet trunks aggregated (MLT) to provide a single logical trunk. A multilink trunk provides the combined bandwidth of multiple links and the physical layer protection against the failure of a single link.
Network Entity Title The Network Entity Title (NET) is the combination of all three global (NET) parameters: Manual area, System ID and NSEL. • Manual area — The manual area or area ID is up to 13 bytes long. The first byte of the area number (for example, 49) is the Authority and Format Indicator (AFI). The next bytes are the assigned domain (area) identifier, which is up to 12 bytes (for example, 49.0102.0304.0506.0708.0910.1112). • System ID — The system ID is any 6 bytes that are unique in a given area or level. The system ID defaults to the node BMAC. • NSEL — The last byte (00) is the n-selector. In the Avaya Ethernet Routing Switch 8800/8600 implementation, this part is automatically attached. There is no user input accepted.
Open Shortest Path A link-state routing protocol used as an Interior Gateway Protocol (IGP). First (OSPF)
Packet Capture Tool A data packet capture tool that captures ingress and egress (on Ethernet (PCAP) modules only) packets on selected ports. You can analyze captured packets for troubleshooting purposes.
Partial Sequence Partial Sequence Number Packets (PSNP) are requests for missing Link Number Packets State Packets (LSPs). When a receiving router detects that it is missing an (PSNP) LSP, it sends a PSNP to the router that sent the Complete Sequence Number Packets (CSNP). port A physical interface that transmits and receives data.
Protocol Data Units A unit of data that is specified in a protocol of a given layer and that (PDUs) consists of protocol-control information of the given layer and possibly user data of that layer.
Provider Backbone To forward customer traffic across the service provider backbone, SPBM Bridge (PBB) uses IEEE 802.1ah Provider Backbone Bridging (PBB) MAC-in-MAC encapsulation, which hides the customer MAC (C-MAC) addresses in a backbone MAC (B-MAC) address pair. MAC-in-MAC encapsulation defines a BMAC-DA and BMAC-SA to identify the backbone source and destination addresses. reverse path Prevents packet forwarding for incoming IP packets with incorrect or forged checking (RPC) (spoofed) IP addresses.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 186 Comments on this document? [email protected] reverse path forwarding (RPF)
reverse path Prevents a packet from forging its source IP address. Typically, the system forwarding (RPF) examines and validates the source address of each packet.
Routing Information A distance vector protocol in the IP suite, used by IP network-layer protocol, Protocol (RIP) that enables routers in the same AS to exchange routing information by means of periodic updates. The RIP is most often used as a very simple IGP within small networks.
Service Instance The SPBM B-MAC header includes a Service Instance Identifier (I-SID) Identifier (I-SID) with a length of 24 bits. This I-SID can be used to identify and transmit any virtualized traffic in an encapsulated SPBM frame. These I-SIDs are used to virtualize VLANs (Layer 2 Virtual Services Network [VSN]) or VRFs (Layer 3 Virtual Services Network [VSN]) across the MAC-in-MAC backbone. With Layer 2 VSN, the I-SID is associated with a customer VLAN, which is then virtualized across the backbone. With Layer 3 VSN, the I-SID is associated with a customer VRF, which is also virtualized across the backbone.
Shortest Path Shortest Path Bridging is a control Link State Protocol that provides a loop Bridging (SPB) free Ethernet topology. There are two versions of Shortest Path Bridge: Shortest Path Bridging VLAN and Shortest Path Bridging MAC. Shortest Path Bridging VLAN uses the Q-in-Q frame format and encapsulates the source bridge ID into the VLAN header. Shortest Path Bridging MAC uses the 802.1 ah MAC-in-MAC frame format and encapsulates the source bridge identifier into the B-MAC header.
Shortest Path Shortest Path Bridging MAC (SPBM) uses the Intermediate-System-to- Bridging MAC Intermediate-System (IS-IS) link state routing protocol to provide a loop free (SPBM) Ethernet topology that creates a shortest path topology from every node to every other node in the network based on node MAC addresses. SPBM uses the 802.1ah MAC-in-MAC frame format and encapsulates the source bridge identifier into the B-MAC header. SPBM eliminates the need for multiple overlay protocols in the core of the network by reducing the core to a single Ethernet based link state protocol which can provide virtualization services, both layer 2 and layer 3, using a pure Ethernet technology base.
Split MultiLink An Avaya extension to IEEE 802.1AX (link aggregation), provides nodal Trunking (SMLT) and link failure protection and flexible bandwidth scaling to improve on the level of Layer 2 resiliency. time-to-live (TTL) The field in a packet used to determine the valid duration for the packet; the TTL determines the packet lifetime. The system discards a packet with a TTL of zero.
Top of Rack (TOR) A Top of Rack (TOR) switch refers to a switch that sits at the top or near the top of a rack often found in data centers.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 187 Comments on this document? [email protected] Glossary
Virtual Link Virtual Link Aggregation Control Protocol (VLACP) is a Layer 2 Aggregation Control handshaking protocol that can detect end-to-end failure between two Protocol (VLACP) physical Ethernet interfaces.
Virtual Local Area A Virtual Local Area Network is a group of hosts that communicate as if Network (VLAN) they are attached to the same broadcast domain regardless of their physical location. VLANs are layer 2 constructs.
Virtual Private A Virtual Private Network (VPN) requires remote users to be authenticated Network (VPN) and ensures private information is not accessible to unauthorized parties. A VPN can allow users to access network resources or to share data.
VLAN Identifier (VID) VLAN Identifier (VID) is a data field in IEEE 802.1Q VLAN tagging.
November 2017 Configuring Avaya Fabric Connect on Avaya VSP 7000 Series 188 Comments on this document? [email protected]