76 8600 50122i 8600 smart routers IP forwarding and traffic management configuration guide

8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 76.8600-50122I 20.05.2015 Document Information Revision History Document No Date Description of Changes 76.8600-50122I 20.05.2015 Added 8665 Smart Router supported functionality in: • 6.5 Platform ACL Support Summary • Differentiated Services Added support of QinQ and Multi-VLANs shaping in 8615 Smart Router Reworked the following: • Document TOC • Network Level Policies • 8.2.4 QoS Classification and Remarking in QinQ Interface in 8.2.2 QoS Mapping Tables • 8.5.3 Shaping in 8615 Smart Router and ELC1 Updates/changes applied in: • Access Control Lists • 8.1 DiffServices Features • 8.2.2 QoS Mapping Tables • 8.3 QoS Policing • 8.4.3 Maximum Configurable Queue Length • Multi-VLANs Shaping Configuration • 9.4.4 Port Shaping Configuration Added: • 8.2.3 QoS Classification • 8.2.4 QoS Classification and Remarking in QinQ Interface • 8.2.5 LU1 Ingress Overbooking Management • 9.1.1 Configuring Hierarchical QoS Classification 76.8600-50122H 04.11.2014 Added 8615 Smart Router supported functionality in: • 6.5 Platform ACL Support Summary • Differentiated Services Reworked 2.2 DHCP Support Changes applied in Access Control Lists Updated 8.2.6 Graceful QoS Added ELC1 support of QinQ and multi-VLANs shaping in 8.5.3 Shaping in 8615 Smart Router and ELC1 Updates applied in Differentiated Services Configuration Examples section: • 9.3 Queue Management and Scheduling Configuration • VLAN Shaping Configuration • Multi-VLANs Shaping Configuration • 9.4.4 Port Shaping Configuration 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 76.8600-50122I © 2015 Coriant This revision of the manual documents the following network elements and the corresponding feature packs or higher 8602 Smart Router FP7.0 8605 Smart Router FP1.6 8607 Smart Router FP1.1 8609 Smart Router, 8611 Smart Router FP7.0 8615 Smart Router FP7.0 8620 Smart Router FP4.1 8630 Smart Router, 8660 Smart Router FP7.0 8665 Smart Router FP7.0 If a different feature pack of 8600 Smart Routers is in use, please refer to the relevant product document program on the Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data Networking > 8600 Smart Routers> Technical Documentation The functionality described in this document for 8615 Smart Router is also applicable to 8615 Smart Router stacked, unless otherwise stated © 2015 Coriant All rights reserved This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied Users must take full responsibility for their application of any products Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 76.8600-50122I © 2015 Coriant Document Information Terms and Abbreviations 76.8600-50122I © 2015 Coriant Term Explanation ACL Access Control List AFx Assured Forwarding (x = 4) ARP Address Resolution Protocol ATM Asynchronous Transfer Mode BE Best Effort BFD Bidirectional Forwarding Detection BGP Border Gateway Protocol bps Bit per Second CBS Committed Burst Size CDC Control and DC Power Card CE Customer Edge CIDR Classless Inter-Domain Routing CIR Committed Information Rate CLI Command Line Interface CoS Class of Service CPU Central Processing Unit CS7 Class Selector C-VLAN Customer VLAN DA Destination Address DBA DiffServ Behavior Aggregate DHCP Dynamic Host Configuration Protocol DiffServ Differentiated Services DNS Domain Name System DS3 Digital Signal level (T3) DSCP DiffServ Code Point ECMP Equal-Cost Multi-Path EF Expedited Forwarding ELC1 Ethernet Line Card in 8630 Smart Router, 8665 Smart Router ELP Ethernet Link Protection E-LSP EXP-Inferred-PSC LSPs, or Explicitly TC-Encoded-PSC LSPs FCS Frame Check Sequence FE Fast Ethernet FIB Forwarding Information Base 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide Document Information FTP File Transfer Protocol GE Gigabit Ethernet GS Group Shaper ICMP Internet Control Message Protocol IETF Internet Engineering Task Force IFC Interface Module Concentrator is the line card baseboard IFC line card The IFC line card in 8630 Smart Router and 8660 Smart Router and consists of an IFC and up to two IFMs There are two types of IFC line cards: IFC1 and IFC2 IFM Interface Module IGP Interior Gateway Protocol INM 8000 Intelligent Network Manager IOM Ingress Overbooking Management IP Internet Protocol IPv4 IP version IPv6 IP version IRB Integrated Routing and Bridging IS-IS Intermediate System to Intermediate System kbps Kilobit per Second LDP Label Distribution Protocol (MPLS) L-LSP Label-Only-Inferred-PSC LSP LM Line Module LSP Label Switched Path Lx Layer in the OSI model, where x refers to the number LU1 Line Unit in 8665 Smart Router MAC Media Access Control Mbps Megabit per Second MF Multi-Field MGMT Management Port MLPPP Multilink PPP MPLS Multiprotocol Label Switching MTU Maximum Transfer Unit aka Maximum Transmission Unit NA Not Applicable/Applied NBMA Nonbroadcast Multiaccess NE Network Element NSSA OSPF Not-so-Stubby Area OSPF Open Shortest Path First PBR Policy-Based Routing 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 76.8600-50122I © 2015 Coriant Document Information 76.8600-50122I © 2015 Coriant PBS Peak Burst Size PE Provider Edge PHB Per-Hop Behavior PIR Peak Information Rate PPP Point-to-Point Protocol POS Packet over SDH/SONET PSC PHB Scheduling Class PSN Packet-Switched Network PTP Precision Time Protocol PWE3 Pseudowire Emulation Edge to Edge QinQ IEEE 802.1 QinQ QoS Quality of Service RAL Reverse Address Lookup RED Random Early Detection RIB Routing Information Base RIP Routing Information Protocol RNC Radio Network Controller RR Round Robin RSVP-TE Resource Reservation Protocol with Traffic Engineering Extensions RTT Round-Trip Time SA Source Address SCM Switching Control Module in 8611 Smart Router SFQ Start-Time Fair Queuing SHDSL Single-pair High-speed Digital Subscriber Line SLA Service Level Agreement SP Strict Priority SU1 Switch Unit in 8665 Smart Router S-VLAN Service VLAN TCP Transmission Control Protocol TDM Time Division Multiplexing tr-TCM two-rate Three-Color Marker UDP User Datagram Protocol VCI Vendor Class Identifier VGS VLANs Group Shaping VoIP Voice over IP VPN Virtual Private Network VRF VPN Routing and Forwarding 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide Document Information VRRP Virtual Router Redundancy Protocol VSI Virtual Switching Instance WAN Wide Area Network WFQ Weighted Fair Queuing WRED Weighted Random Early Detection 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 76.8600-50122I © 2015 Coriant Table of Contents Table of Contents About This Manual 13 Objectives 13 Audience 13 8600 Smart Routers Technical Documentation 13 Interface Numbering Conventions 17 Document Conventions 17 Documentation Feedback 17 8600 Smart Routers Discontinued Products 18 Internet Protocol 19 1.1 1.2 1.3 1.4 Dynamic Host Configuration Protocol (DHCP) 24 2.1 2.2 2.3 2.4 2.5 2.6 Overview 19 IP Addressing 19 1.2.1 IPv4 Addressing 19 Neighbor Maintenance 20 1.3.1 Address Resolution Protocol (ARP) 20 IP References 23 Overview 24 DHCP Support 24 DHCP Client 25 2.3.1 8600 NEs Behavior 26 2.3.2 DHCP Client Vendor Class Identifier (Option 60) 26 DHCP Relay Agent 26 2.4.1 DHCP Relay Agent Information Option (Option 82) 27 2.4.2 DHCP Relay-Server Configuration 28 NE Autoconfiguration 28 2.5.1 Enabling Autoconfiguration 29 2.5.2 Interface Scanning 29 2.5.3 Automatic Configurations 30 DHCP References 30 IP Static Routing 31 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide Table of Contents 3.1 3.2 3.3 3.4 3.5 IP Configuration Examples 40 4.1 4.2 4.3 IP Basic Configuration 40 4.1.1 Configuring an IPv4 Address 40 4.1.2 Configuring Static ARP entry 40 DHCPv4 Configuration 41 4.2.1 DHCP Manual Autoconfiguration 41 4.2.2 DHCP Relay Configuration 42 4.2.3 DHCP Configuration Status 43 IP Static Routing Configuration Examples 44 4.3.1 IPv4 Static Routing 44 4.3.2 Management Network Connectivity with Static Routes 47 4.3.3 Inter VRF Static Routing 48 4.3.4 Recursive Static Routing 50 Network Level Policies 53 5.1 5.2 5.3 Static Route Configuration 31 Static Routes 32 3.2.1 Null Static Route 35 Recursive Routes 36 MPLS Recursive Routes 38 IP Static Routes References 39 Overview 53 Concept of MTU 53 References 55 Access Control Lists 56 6.1 6.2 6.3 6.4 6.5 6.6 Hidden Rules 56 Packet Handling 57 6.2.1 Action QoS 57 6.2.2 Action Map-Route 57 6.2.3 Action Service-Policer 58 Filter 58 6.3.1 Address Fields 59 6.3.2 TCP Code Bits 59 6.3.3 Source and Destination Port Fields 60 6.3.4 Fragments Field 63 6.3.5 Simple Fields 63 ACL Resources 64 6.4.1 ACL Resources Usage Behavior 64 6.4.2 ACL Resources Optimization 64 Platform ACL Support Summary 64 ACL Statistics 65 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 10 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples Step All incoming IP packets carried inside Ethernet frames marked with the VLAN User Priority value will be classified to be PHB router(config)# qos mapping ingress vlan-pri qos be Step On the Ethernet port, all Ethernet frames carrying outgoing af43 packets will be marked with the VLAN User Priority value router(config)# interface fe 2/1/1 router(cfg-if[fe2/1/1])# qos mapping egress qos af4 drop-precedence high vlan-pri router(cfg-if[fe2/1/1])# exit In case of using PPP/MLPPP, the QoS mapping should be enabled at the module which is used QoS mapping can be enabled under any physical interface of the module Note that in the running-config the setting is shown under pdh x/x/0 or so x/x/0 Step Configure the PPP/MLPPP interface to use QoS mappings router(cfg-if[pdh4/1/0])# qos mapping enable 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 112 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples 9.1.1 Configuring Hierarchical QoS Classification Sometimes, different logical interfaces may use different packet fields for QoS classification, this chapter illustrates how QoS classification settings can be managed at different levels of configuration (please see more details in 8.2.3 QoS Classification) as follows: • Node level - in this case, all logical interfaces in a node will use this setting • Port level - in this case, this setting will apply to all logical interfaces on this port, including the port itself, as well as all VLAN and QinQ interfaces (IP, PWE3 and SLI) This setting will override the node level setting for this particular Ethernet port • VLAN level - in this case, this setting will override the node and port level settings for this particular VLAN Step Set VLAN PRI based QoS classification at node level router(config)# qos mapping use ingress traffic layer2–frame Step Set QoS classification based on IP DSCP field at port level router(config)# interface ge 2/1/1 router(cfg-if[ge2/1/1])# qos mapping use ingress traffic ip-dscp ip-dscp-on-layer2-interface Step Set traffic to be classified to EF traffic class at VLAN level regardless of packet header fields router(config)# interface ge 2/1/1.100 router(cfg-if[ge2/1/1.100])# qos vlan ingress qos ef 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 113 Differentiated Services Configuration Examples 9.2 QoS Policers Configuration This chapter provides CLI configuration examples of QoS policers in 8600 NEs An overview of QoS policers is provided in 8.3 QoS Policing An example showing how to configure ACL based QoS policers is provided in 7.8 Action Service-Policer To configure a policer, at least the following steps are required: • Creating a policer • Setting the policer parameters • Setting the policer marker options, i.e the way a policer treats conformed/excess traffic • Binding the policer to an interface: Ethernet, VLAN, POS • Optionally defining the minimum policed packet size, if applicable 9.2.1 Policing High Priority Traffic The following is an example showing how to configure a policer for high priority (EF, CS7) traffic The policed traffic profile comprises only of CIR and CBS For EF and CS7 traffic the following are the supported options for setting the policer marker drop actions Please always refer to 8600 Smart Routers CLI Commands Manual for the latest information on options supported marker [ use-pre-set-markings ] cir-conform-action none cir-exceed-action { drop | none } Step Create an EF policer policer1 router(config)# policer policer1 qos ef Step Set policer parameters: CIR = 5000 kbps and CBS = 5000 bytes router(cfg-policer[policer1])# police cir 5000 cbs 5000 router(cfg-policer[policer1])# exit Step Set policer drop markers actions router(cfg-policer[policer1])# marker use-pre-set-markings cir-conform-action none cir-exceed-action drop Step Bind the policer to the required ingress interface(s) In this example the policer is bound to a L1 Ethernet interface, i.e it will affect all L1 traffic If there are VLANs created to this interface, then traffic from these VLANs will subject to the same policer treatment router(config)# interface ge 2/0/0 router(cfg-if[ge2/0/0])# service-policer policer1 layer1 router(cfg-if[ge2/0/0])# exit In the 8600 system, a QoS policer can be associated to multiple instances In the following example the same policer1 created above is bound to another interface instance Step Bind the policer1 to another desired instance, in this example to a VLAN router(config)# interface ge 3/0/1.100 router(cfg-if[ge3/0/1.100])# service-policer policer1 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 114 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples router(cfg-if[ge3/0/1.100])# exit 9.2.2 Policing AFx Traffic The following is an example showing how to configure a policer for AFx traffic For AFx traffic there are several options supported for setting the policer marker drop actions, which are provided below Please always refer to 8600 Smart Routers CLI Commands Manual for the latest information on options supported marker [ use-pre-set-markings ] cir-conform-action { low-drop-precedence | high-drop-precedence | none } cir-exceed-action { low-drop-precedence | medium-drop-precedence | high-drop-precedence | drop | none } pir-exceed-action { low-drop-precedence | high-drop-precedence | drop | none } Step Create an AF1 policer af1policer router(config)# policer af1policer qos af1 Step Set policer parameters (bandwidth and burst sizes): CIR = 5000 kbps, CBS = 1000 bytes, PIR = 7000 kbps, PBS = 1000 bytes router(cfg-policer[af1policer])# police cir 5000 cbs 1000 pir 7000 pbs 1000 Step Set how the policer treats conformed/excess traffic Any pre-marked drop precedence level on CIR-conforming packets will never be improved (e.g from AFx3 –> AFx1), packets exceeding CIR will be marked with high drop precedence (i.e AFx3), and packets exceeding PIR will be dropped router(cfg-policer[af1policer])# marker use-pre-set-markings cir-conform-action none cir-exceed-action high-drop-precedence pir-exceed-action drop Step Optionally, the minimum policed packet size can also be changed from the default of 128 bytes In this case, packets smaller than 64 bytes will be calculated as 64-byte packets router(cfg-policer[af1policer])# min-policed-packet-size 64 router(cfg-policer[af1policer])# exit Step Bind the af1policer to an interface In this example, the binding is done to a VLAN interface router(config)# interface ge 2/1/0.100 router(cfg-if[ge2/1/0.100])# service-policer af1policer router(cfg-if[ge2/1/0.100])# exit 9.2.3 Policing BE Traffic The following is an example showing how to configure a policer for BE traffic For BE traffic there are several options supported for setting the policer marker drop actions, which are provided below Please always refer to 8600 Smart Routers CLI Commands Manual for the latest information on options supported marker [ use-pre-set-markings ] pir-exceed-action { drop | none } Step Create a BE policer BEpolicer router(config)# policer BEpolicer qos be Step 76.8600-50122I © 2015 Coriant Set policer parameters: PIR = 7000 kbps, PBS = 1000 bytes 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 115 Differentiated Services Configuration Examples router(cfg-policer[BEpolicer])# police pir 7000 pbs 1000 Step Set how the policer treats conformed/excess traffic router(cfg-policer[BEpolicer])# marker use-pre-set-markings drop Step Bind the BEpolicer to an interface In this example, the binding is done to a POS interface router(config)# interface so 3/0/0 router(cfg-if[so3/0/0])# service-policer BEpolicer layer1 router(cfg-if[so3/0/0])# exit 9.2.4 Removing QoS Policer If the policing requirements change, each binding to an interface can be individually removed Once all bindings have been removed, and thus a policer becomes obsolete, it can also be deleted from the system as illustrated below Step Remove a policer binding to an interface router(config)# interface ge 2/0/0 router(cfg-if[ge2/0/0])# no service-policer policer1 layer1 router(cfg-if[ge2/0/0])# exit Step Delete a policer1 settings from the system router(config)# no policer policer1 9.3 Queue Management and Scheduling Configuration The overview functionality of queue management and scheduling is presented in 8.4 Queue Management and Scheduling and the features supported by each interface type are presented in 8.1 DiffServices Features The 8600 NEs have predefined system default settings for the queuing and scheduling parameters However, the default settings can be adjusted at the node level Also a new QoS queue group can be created into the system and the group parameters set accordingly, as it is illustrated in the following chapters Two types of queue groups can be configured in the system: • Port queues • Single interface queues in MS interfaces, i.e PPP, MLPPP and cHDLC (cHDLC only on the MS IFMs) 9.3.1 Port Queues Configuration The following tables provide guidelines for port queues configuration levels in 8600 NEs Refer to 8600 Smart Routers CLI Commands Manual for more information on parametric range and default settings 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 116 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples 8605 Smart Router, 8607 Smart Router Parameter Configuration Level Port (QoS Queue Group) Node QoS queue group — — Queue length — Yes Queue weight — Yes WRED drop criteria — — RED drop criteria — — 8602 Smart Router, 8609 Smart Router and 8611 Smart Router Parameter Configuration Level Port (QoS Queue Group) Node QoS queue group Yes — Queue length Yes Yes Queue weight Yes Yes WRED drop criteria Yes Yes RED drop criteria Yes Yes 8615 Smart Router, 8620 Smart Router, 8630 Smart Router, 8660 Smart Router and 8665 Smart Router Parameter Configuration Level Port (QoS Queue Group) Node QoS queue group Yes — Queue length Yes Yes Queue weight Yes Yes WRED drop criteria Yes Yes RED drop criteria Yes Yes In order to configure a new port queue group, the following tasks are required: • Create a new QoS queue group • Set queue group parameters: • Queue length • Queue weight • Queue management • Apply the QoS queue group settings to the physical port(s) Step Create a new QoS queue group queue1 and change the command mode to configure the group router(config)# qos queue-group queue1 Step 76.8600-50122I © 2015 Coriant Configure the length of the BE queue to 150 packets Refer to 8600 Smart Routers CLI Commands Manual for the parametric range and default values per NE 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 117 Differentiated Services Configuration Examples router(cfg-qos-que[queue1])# queue length qos be 150 Step Configure the BE queue weight as relative number to the other queues' weights router(cfg-qos-que[queue1])# queue weight qos be router(cfg-qos-que[queue1])# exit Also for the NEs supporting RED and WRED queue management disciplines (see 8.1 DiffServices Features), these can be configured to the queue group as illustrated below Step Configure the BE queue RED algorithm drop probability at the maximum threshold point (%), the maximum threshold point (# of packets), and the minimum threshold point (# of packets) router(config)# qos queue-group queue1 router(cfg-qos-que[queue1])# red 10 20 50 Step Configure the AF4 queue WRED algorithm drop probability at the maximum threshold point (%), the maximum threshold point (# of packets), and the minimum threshold point (# of packets), for each of the three drop precedence levels (i.e low (AF41), medium (AF42), and high (AF43)) router(cfg-qos-que[queue1])# wred qos af4 drop-precedence low 60 180 10 medium 15 50 high 10 100 router(cfg-qos-que[queue1])# exit Next, after the queue group has be configured, it can be taken into use in those ports, where the specifically defined deviations from the node level default settings are needed Step Take the QoS queue group settings into use to the Ethernet port router(config)# interface ge 2/0/0 router(cfg-if[ge2/0/0])# tx-qos-queue queue1 router(cfg-if[ge2/0/0])# exit The NE default QoS queue group settings can be individually taken back into use on each interface, and once all interface bindings of the queue group have been removed, it can be also deleted from the system as illustrated below Step Return the QoS queue group settings to the node level defaults on the Ethernet port router(config)# interface ge 2/0/0 router(cfg-if[ge2/0/0])# no tx-qos-queue queue1 router(cfg-if[ge2/0/0])# exit Step Delete the QoS queue group from the system router(config)# no qos queue-group queue1 9.3.2 Single Interface Queues Configuration Single interface queues are configured for the MS interfaces: PPP, MLPPP and also cHDLC (cHDLC supported only on the MS IFMs) Refer to 8600 Smart Routers CLI Commands Manual for the parametric range and default values 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 118 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples Parameter Configuration Level Interface (QoS Queue Group) Node QoS queue group Yes — Queue length Yes Yes Queue weight Yes Yes These queues are configured with reduced option and the configuration requires the following tasks: • Create a new queue group using the reduced option • Set the queue group parameters: • Queue length with the reduced option • Queue weight • Apply the queue group settings to the MS interface(s) In 8607 Smart Router queue length configuration in MS interfaces is not supported Step Create new QoS queue group queueMSIF router(config)# qos queue-group queueMSIF reduced Step Configure the length of the AF1 queue to 150 packets router(cfg-qos-que[queueMSIF])# queue length—reduced qos af1 150 Step Configure the AF1 queue weight as relative number to the other queues' weights router(cfg-qos-que[queueMSIF])# queue weight qos af1 100 router(cfg-qos-que[queueMSIF])# exit Next, after the queue group has be configured, it can be taken into use in those MS interfaces, where the specifically defined deviations from the node level default settings are needed Step Configure the MS interface router(config)# interface pdh 1/0 router(cfg-if[pdh1/0])# pdh framed router(cfg-if[pdh1/0])# exit Step Configure a timeslot group and apply the queue group settings to be taken into use router(config)# interface pdh 1/0:0 router(cfg-if[pdh1/0:0])# pdh timeslots - 15 17 - 31 router(cfg-if[pdh1/0:0])# port-protocol ppp router(cfg-if[pdh1/0:0])# no shutdown router(cfg-if[pdh1/0:0])# tx-qos-queue queueMSIF router(cfg-if[pdh1/0:0])# exit 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 119 Differentiated Services Configuration Examples 9.4 Shaping Configuration Examples The following chapters provide an illustration of to configure shapers in 8600 NEs The overview of shaping functionality is presented in 8.5 Shaping and the features supported by each interface type are presented in 8.1 DiffServices Features 9.4.1 Port Queue Shaping Configuration The following is an example showing how to configure per-queue shapers The overview functionality is presented in Port Queue Shaping Step Create a shaper efshaper, set the type to EF, and change command mode to configure a shaper router(config)# shaper efshaper qos ef Step Configure the shaper bandwidth to 1000 kbps and the allowed burst size to 500 bytes router(cfg-shaper[efshaper])# shape cir 1000 bucket-depth 500 Step Optionally, the minimum shaped packet size can also be changed from the default of 128 bytes In this case, packets smaller than 100 bytes will be calculated as 100-byte packets router(cfg-shaper[efshaper])# min-shaped-packet-size 100 router(cfg-shaper[efshaper])# exit After creating the efshaper, it can be bound to the desired egress interfaces Step Bind efshaper to the L1 Ethernet port router(config)# interface fe 2/0/0 router(cfg-if[fe2/0/0])# service-shaper efshaper layer1 router(cfg-if[fe2/0/0])# exit In the case of shaping AF traffic, also PIR has to be configured in order to limit the instantaneous packet transmit rate during the allowed bursts Step Create a shaper of type AF1, having CIR = 1000 kbps, PIR = 1500 kbps, and the allowed burst size of 500 bytes router(config)# shaper af1shaper qos af1 router(cfg-shaper[af1shaper])# shape cir 1000 pir 1500 bucket-depth 500 router(cfg-shaper[af1shaper])# exit Step Optionally, the minimum shaped packet size can also be changed from the default of 128 bytes In this case, packets smaller than 100 bytes will be calculated as 100-byte packets Note, when executed in this command mode, the end result will be a global default setting for all shapers router(config)# min-shaped-packet-size 100 Step Bind af1shaper to the L1 Ethernet port router(config)# interface fe 2/0/0 router(cfg-if[fe2/0/0])# service-shaper af1shaper layer1 router(cfg-if[fe2/0/0])# exit If the shaper becomes obsolete, it can be removed from the system Step Remove shaping binding to the Ethernet port 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 120 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples router(config)# interface fe 2/0/0 router(cfg-if[fe2/0/0])# no service-shaper af1shaper layer1 router(cfg-if[fe2/0/0])# exit Step Deleting a shaper router(config)# no shaper af1shaper Step Remove the global minimum shaped packet size setting and return to the node defaults router(config)# no min-shaped-packet-size 100 In the case of shaping BE traffic, only PIR has to be configured as illustrated below Step Create a shaper with PIR = 1500 kbps router(config)# shaper beshaper qos be router(cfg-shaper[beshaper])# shape pir 1500 router(cfg-shaper[beshaper])# exit 9.4.2 VLAN Queue Shaping Configuration The VLAN queue shaping functionality is described in VLAN Queue Shaping in IFC1 Line Card and 8620 Smart Router Instead of binding to a L1 port, shapers of the type BE can alternatively also be bound to a user-selected VLAN subinterface In this case, a VLAN will be bound to a dedicated scheduling queue, on which shaping and also the RED queue management discipline will be individually performed Step Bind the beshaper to a VLAN subinterface identified by VLAN ID #1 on the Ethernet port router(config)# interface fe 2/0/0.1 router(cfg-if[fe2/0/0.1])# service-shaper beshaper router(cfg-if[fe2/0/0.1])# exit If beshaper becomes obsolete, the interface binding instances can be removed and the shaper deleted from the system as illustrated below Step Remove shaper binding to the VLAN subinterface router(config)# interface fe 2/0/0.1 router(cfg-if[fe2/0/0.1])# no service-shaper beshaper router(cfg-if[fe2/0/0.1])# exit Step Deleting a shaper router(config)# no shaper beshaper 9.4.3 Group Shaping Configuration Examples The following sub-chapters provide an illustration on how to configure group shapers IFC2 Line Card VLAN Shaping Configuration The shaping functionality in IFC2 line card is described in VLAN Shaping in IFC2 Line Card For a group shaper to function properly, the following rules apply: 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 121 Differentiated Services Configuration Examples • Both ingress and egress line cards must be based on IFC2 for MPLS/PWE3 traffic • For IP traffic, IFC1 based line card can be used in ingress • Concurrent group shaper and single flow queue shaper are not supported • Concurrent group shaper and single or multiple flow queues are supported To configure VLAN shaping in IFC2 line card at least the following steps are required: • Creating a group shaper • Setting the attributes of the group shaper • VLAN interface configuration and binding to a group shaper • Optionally setting of QoS treatment for CS7 and EF traffic classes Step Create a group shaper IFC2VGshaper router(config)# shaper-group IFC2VGshaper router(cfg-shaper-group[IFC2VGshaper])# Step Set the group shaper rate to 3000000 bps The configuration is done in steps of 1000 router(cfg-shaper-group[IFC2VGshaper])# shape cir 3000000 router(cfg-shaper-group[IFC2VGshaper])# exit Step Configure a VLAN ge7/0/6.1 interface and bind it to the group shaper router(config)# interface ge 7/0/6.1 router(cfg-if[ge7/0/6.1])# no shutdown router(cfg-if[ge7/0/6.1])# service-shaper-group IFC2VGshaper router(cfg-if[ge7/0/6.1])# exit Additionally, in some network applications it might be undesirable to shape CS7 and EF traffic For example, the shaping of Precision Time Protocol (PTP) packets carrying synchronization information may lead to a significant degradation of timing performance, due to the delay caused by shaper (for PTP details refer to 8600 Smart Routers Synchronization Configuration Guide) Therefore, QoS treatment must be used in this case as illustrated below Step Set QoS treatment for CS7 and EF to bypass the group shaper with calculated option Note that if the calculated option is not set, the shaper will only control the aggregate bandwidth consumed by AF and BE traffic router(config)# shaper-group IFC2VGshaper router(cfg-shaper-group[IFC2VGshaper])# qos-treatment cs7 ef by-pass calculated router(cfg-shaper-group[IFC2VGshaper])# exit When there are unused traffic classes, it is possible to optimise the resources by disabling queue allocations for those traffic classes The following is an example showing how to disable queue allocation Step Disable AF4 and AF3 flow queues allocation router(config)# shaper-group IFC2VGshaper router(cfg-shaper-group[IFC2VGshaper])# no qos-usage af4 af3 router(cfg-shaper-group[IFC2VGshaper])# exit 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 122 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples VLAN Shaping Configuration This chapter provides an illustration of how VLAN shapers are configured in: • 8615 Smart Router • ELC1 (8630 Smart Router, 8660 Smart Router) • LU1 (8665 Smart Router) VLAN shaping functionality is described in 8.5.3 Shaping in 8615 Smart Router and ELC1 and 8665 Smart Router in 8.5.4 Shaping in LU1 For a group shaper to function properly the following rules apply: • The template option for the group shaper is mandatory • Once a VLAN is attached to a shaper template, it will have its own set of queues The length and weight of these queues are configurable • The burst-size and pir options are not configurable The VLAN shaping configuration requires at least the following tasks: • Creation of a shaper template • Setting the parameters of the shaper template • VLAN interface configuration and binding to the shaper template The following example illustrates how to configure a shaper template for a VLAN shaping in ELC1 Step Create a shaper template router(config)# shaper-group VST template Step Set the rate of the shaper template In this example, CIR is set in kbps (k) router(cfg-shaper-group[VST])# shape cir 400000 k router(cfg-shaper-group[VST])# exit Step Configure a VLAN interface and associated it to the shaper template router(config)# interface xe 7/0/0.100 router(cfg-if[xe7/0/0.100])# no shutdown router(cfg-if[xe7/0/0.100])# service-shaper-group VST router(cfg-if[xe7/0/0.100])# exit Multi-VLANs Shaping Configuration This chapter provides a configuration example of Multi-VLANs shaping In multi-VLANs shaping, a configuration of the group shaper attributes (CIR, PIR and burst-size) is not the same across the 8600 NEs and the following table provides an outline of the configurable attributes per NE Please refer to 8600 Smart Routers CLI Commands Manual for more details The notation “—” below stands for not configurable 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 123 Differentiated Services Configuration Examples Multi-VLANs Shaping Attributes Configuration NE/Unit Configurable Group Shaper Attributes burst-size CIR PIR 8602 Smart Router 8605 Smart Router 8607 Smart Router 8609 Smart Router 8611 Smart Router Yes Yes Yes 8615 Smart Router — Yes — ELC1 (8630 Smart Router, 8660 Smart Router) — Yes — LU1 (8665 Smart Router) — Yes — To configure multi-VLANs shaping at least the following steps are required: • Creating a Group Shaper (GS) In this case, a GS shapes traffic aggregated from a group of queues associated with multiple VLANs • Setting attributes of the group shaper Note however, that not all shaper attributes are configurable in some NEs (see details in Multi-VLANs Shaping Attributes Configuration) • VLAN interface(s) configuration and binding to a group shaper In this case, multiple VLANs of the same physical Ethernet port can be bound to the group shaper Step Create a group shaper VGS0 router(config)# shaper-group VGS0 router(cfg-shaper-group[VGS0])# Step Set the group shaper attributes CIR =1000000 bps, PIR = 1000000 bps (in steps of 1000) and burst-size = 50000 bytes It shall be noted that not all of these three attributes are configurable in some NEs (see details in Multi-VLANs Shaping Attributes Configuration) router(cfg-shaper-group[VGS0])# shape cir 1000000 burst-size 50000 pir 1000000 router(cfg-shaper-group[VGS0])# exit Step Configure a VLAN ge0/1.1000, enable label switching on the interface and bind it to the group VGS0 router(config)# interface ge 0/1.1000 router(cfg-if[ge0/1.1000])# label-switching router(cfg-if[ge0/1.1000])# no shutdown router(cfg-if[ge0/1.1000])# service-shaper-group VGS0 router(cfg-if[ge0/1.1000])# exit Step Configure a VLAN ge0/1.2000, enable label switching on the interface and bind it to the group VGS0 router(config)# interface ge 0/1.2000 router(cfg-if[ge0/1.2000])# label-switching router(cfg-if[ge0/1.2000])# no shutdown router(cfg-if[ge0/1.2000])# service-shaper-group VGS0 router(cfg-if[ge0/1.2000])# exit 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 124 76.8600-50122I © 2015 Coriant Differentiated Services Configuration Examples 9.4.4 Port Shaping Configuration This chapter provides an example of port level shaping configuration in 8600 NEs A port level shaper limits the egress bandwidth of an Ethernet interface The shaping value (rate-limit) is user-configurable using the eth bandwidth rate-limit command Please always refer to 8600 Smart Routers CLI Commands Manual for the range of allowed shaping values NE Ethernet Interface on: Hierarchical Shaping Configuration 8602 Smart Router All virtual modules — (multi-VLANs shaping and port shaping are mutually exclusive) 8605 Smart Router Virtual M0 (GE) — (multi-VLANs shaping and port shaping are mutually exclusive) Virtual M0 (FE) — (Port level shaping only) Virtual M3 (GE) — (multi-VLANs shaping and port shaping are mutually exclusive) 8x10/100BASE-TX LM — (Port level shaping only) Virtual M0, M1 & M2 — (multi-VLANs shaping and port shaping are mutually exclusive) 8x10/100BASE-TX LM — (Port level shaping only) All supported HMs — (multi-VLANs shaping and port shaping are mutually exclusive) 8x10/100BASE-TX LM — (Port level shaping only) 8615 Smart Router All virtual modules Yes 8620 Smart Router IFM0 &/or IFM1 Yes 8630 Smart Router 8660 Smart Router IFC1 line card (IFM0 &/or IFM1) Yes IFC2 line card (IFM0 &/or IFM1) Yes ELC1 Yes LU1 Yes 8607 Smart Router 8609 Smart Router 8611 Smart Router 8665 Smart Router This example illustrates how to set the egress port shaping in ELC1 The configuration of ELC1 VLAN shaping is covered in VLAN Shaping Configuration Therefore, when both VLAN group and port shaping are configured, it also enables hierarchical shaping Step Set the egress port shaping values for ELC1 virtual M0 interfaces in slot The shaping value can be set between 20 10000 Mbps in Mbps steps router(config)# eth bandwidth rate-limit 6/0 limits max 7000 Step Set the egress port shaping values for ELC1 virtual M1 interfaces in slot The shaping value can be set between 20 1000 Mbps in Mbps steps router(config)# eth bandwidth rate-limit 6/1 limits 500 600 700 490 580 800 850 900 max max max max 76.8600-50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 125 Differentiated Services Configuration Examples Port level shaping for other module(s)/interface(s)/NEs than ELC1 is configured in similar way as illustrated above using the same eth bandwidth rate-limit command Please always refer to 8600 Smart Routers CLI Commands Manual for the CLI command syntax of the specific NE module/interface types in case QoS Treatment Within hierarchical shaping, it is also possible to configure QoS treatment for packets with CS7 and EF traffic classes to bypass the port level shaping The configuration is done with eth bandwidth qos-treatment command as illustrated in the following step Step Set how CS7 and EF traffic classes are treated by port shaper The illustration in this example uses an ELC1 interface of the virtual M0 in slot router(config)# eth bandwidth qos-treatment interface 6/0/0 cs7 ef by-pass calculated 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 126 76.8600-50122I © 2015 Coriant ... States and/ or other countries 76. 8600- 50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 8600 Smart Routers IP Forwarding and Traffic Management Configuration. .. Router) 76. 8600- 50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide (76. 8600- 50122) Provides an overview of 8600 NEs IP, forwarding and traffic management. .. fi-documentation@tellabs.com 76. 8600- 50122I © 2015 Coriant 8600 Smart Routers IP Forwarding and Traffic Management Configuration Guide 17 8600 Smart Routers Discontinued Products 8600 Smart Routers Discontinued