- play_arrow Introduction
- play_arrow Router Data Extraction
- play_arrow Routing Protocols
- play_arrow Equal Cost Multiple Paths
- play_arrow Static Routes
- play_arrow Policy-Based Routes
- play_arrow Border Gateway Protocol
- NorthStar Planner Border Gateway Protocol Overview
- Border Gateway Protocol Recommended Instructions
- BGP Data Extraction
- BGP Reports
- BGP Options
- BGP Map
- BGP Live Status Check
- BGP Routing Table
- BGP Routes Analysis
- BGP Information at a Node
- BGP Neighbor
- Apply, Modify, or Add BGP Polices
- BGP Subnets
- Getipconf Usage Notes
- BGP Report
- play_arrow Virtual Private Networks
- NorthStar Planner Virtual Private Networks Overview
- Importing VPN Information from Router Configuration Files
- Viewing the Integrity Checks Reports
- Accessing VPN Summary Information
- Accessing Detailed Information for a Particular VPN
- VPN Topology View
- Route-Target Export/Import Relationships
- Additional Methods to Access VPN Information
- VPN Path Tracing
- VPN Design and Modeling Using the VPN Module
- L3 (Layer 3) VPN
- L3 Hub-and-Spoke VPN
- L2M (Layer2-Martini) VPN
- L2K (Layer2-Kompella) VPN
- VPLS-BGP VPN (for Juniper)
- VPLS-LDP VPN
- L2CCC (Circuit Cross-Connect) VPN
- Inter-AS VPN
- Forming VPN Customer Groups
- Deleting or Renaming VPNs
- VPN Configlet Generation
- Adding Traffic Demands in a VPN
- VPN Traffic Generation
- VPN-Related Reports
- VPN Monitoring and Diagnostics
- play_arrow GRE Tunnels
- play_arrow Multicast
- NorthStar Planner Multicast Overview
- NorthStar Planner Recommended Multicast Instructions
- Add Multicast Groups
- Creating Multicast Demands
- Viewing Multicast Demands in the Network
- Comparing Multicast with Unicast
- Multicast SPT Threshold
- Multicast Reports
- Multicast Simulation
- Collecting Multicast Path Data from Live Network
- Importing Multicast Path Data
- Multicast Data Processing
- Viewing Multicast Trees
- play_arrow Class of Service
- NorthStar Planner Class of Service Overview
- NorthStar Planner Recommended CoS Instructions
- The QoS Manager
- Define Class Maps
- Create Policies for Classes
- Attach Policies to Interfaces
- Adding Traffic Inputs
- Using the Text Editor
- Reporting Module
- IP Flow Information
- Link information
- Traffic Load Analysis
- Traffic Load by Policy Class
- CoS Alias File
- Bblink File
- Policymap File
- Demand File
- Traffic Load File
- play_arrow Routing Instances
- play_arrow Traffic Matrix Solver
- play_arrow LSP Tunnels
- NorthStar Planner LSP Tunnels Overview
- Viewing Tunnel Info
- Viewing Primary and Backup Paths
- Viewing Tunnel Utilization Information from the Topology Map
- Viewing Tunnels Through a Link
- Viewing Demands Through a Tunnel
- Viewing Link Attributes/Admin-Group
- Viewing Tunnel-Related Reports
- Adding Primary Tunnels
- Adding Multiple Tunnels
- Mark MPLS-Enabled on Links Along Path
- Modifying Tunnels
- Path Configuration
- Specifying a Dynamic Path
- Specifying Alternate Routes, Secondary and Backup Tunnels
- Adding and Assigning Tunnel ID Groups
- Making Specifications for Fast Reroute
- Specifying Tunnel Constraints (Affinity/Mask or Include/Exclude)
- Adding One-Hop Tunnels
- Tunnel Layer and Layer 3 Routing Interaction
- play_arrow Optimizing Tunnel Paths
- play_arrow Tunnel Sizing and Demand Sizing
- play_arrow Tunnel Path Design
- Tunnel Path Design Overview
- Tunnel Path Design Instructions
- Designing Tunnel Paths Overview
- Backup Path Configuration Options
- Set Default Diversity Level
- Evaluate/Tune Options
- Advanced Options
- Viewing Design Results
- Tunnel Modifications
- Exporting and Importing Diverse Group Definitions
- Advanced Path Modification
- play_arrow Inter-Area MPLS-TE
- play_arrow Point-to-Multipoint (P2MP) Traffic Engineering
- NorthStar Planner P2MP Traffic Engineering Overview
- Point-to-Multipoint Traffic Engineering Instructions
- Import a Network That Already has Configured P2MP LSP Tunnels
- Examine the P2MP LSP Tunnels
- Create P2MP LSP Tunnels and Generate Corresponding LSP Configlets
- Examine P2MP LSP Tunnel Link Utilization
- Perform Failure Simulation and Assess the Impact
- play_arrow Diverse Multicast Tree Design
- Diverse Multicast Tree Design Overview
- Diverse Multicast Tree Instructions
- Open a Network That Already Has a Multicast Tree
- Set the Two P2MP Trees of Interest to be in the Same Diversity Group
- Using the Multicast Tree Design Feature to Design Diverse Multicast Trees
- Using the Multicast Tree Design Feature
- play_arrow Fast Reroute
- NorthStar Planner Fast Reroute Overview
- Fast Reroute Supported Vendors
- Import Config and Tunnel Path
- Viewing the FRR Configuration
- Viewing FRR Backup Tunnels
- Viewing Primary Tunnels Protected by a Bypass Tunnel
- Modifying Tunnels to Request FRR Protection
- Modifying Links to Configure Multiple Bypasses (Juniper only)
- Modifying Links to Trigger FRR Backup Tunnel Creation (Cisco)
- FRR Design
- FRR Auto Design
- FRR Tuning
- Viewing Created Backup Tunnels
- Generating LSP Configlets for FRR Backup Tunnels
- Failure Simulation—Testing the FRR Backup Tunnels
- Exhaustive Failure
- Link, Site and Facility Diverse Paths
- play_arrow Cisco Auto-Tunnels
- play_arrow Integrity Check Report
- play_arrow Compliance Assessment Tool
- Compliance Assessment Tool Overview
- Using The Compliance Assessment Tool
- CAT Testcase Design
- Creating a New Project
- Loading the Configuration Files
- Creating Conformance Templates
- Reviewing and Saving the Template
- Saving and Loading Projects
- Run Compliance Assessment Check
- Compliance Assessment Results
- Publishing Templates
- Running External Compliance Assessment Scripts
- Scheduling Configuration Checking in Task Manager
- Building Templates
- Special Built-In Functions
- Paragon Planner Keywords For Use Within a Rule
- More on Regular Expressions
- IP Manipulation
- play_arrow Virtual Local Area Networks
- play_arrow Overhead Calculation
- play_arrow Router Reference
Hardware Support for DS-TE LSP
Juniper Networks supports two kinds of DS-TE LSPs: DiffServ-aware single-class LSPs and DiffServ-aware multi-class LSPs. Single-class LSPs are similar to traditional L-LSPs, and support only one class per LSP. Multi-class LSPs can be thought of as L-LSPs that can handle multiple classes. Each multi-class LSP can support up to four classes with specific bandwidth reservation assigned to each class. When DiffServ-aware LSPs are routed on a network, consideration is given to the amount of bandwidth reserved on each interface for each class. If there is insufficient bandwidth on a particular interface for a given class on the multi-class or single-class LSP, the LSP will not be routed over that interface.
Class Type
A class type is a collection of traffic flows that is treated equivalently in a DiffServ domain. A class type maps to a queue and is much like a class-of-service (CoS) forwarding class in concept. It is also known as a traffic class.EXP Bits
EXP Bits
The Experimental bits, or EXP bits, in the MPLS header are used to define the class to which a packet belongs. A unique EXP bit pattern is associated with each class type and forwarding class defined on a DiffServ-aware router.
Forwarding Class
Forwarding classes are defined on each router and assigned to internal queues. The default forwarding classes are: best-effort, expedited-forwarding, assured-forwarding, and network-control. Individual class types in DiffServ-aware LSPs are mapped to individual forwarding classes at the router. The default mapping is shown in the table below.
Class Type | Forwarding Class Name |
---|---|
CT0 | best-effort |
CT1 | expedited-forwarding |
CT2 | assured-forwarding |
CT3 | network-control |
Scheduler Map
The treatment given to each forwarding class on an interface is defined by the scheduler map assigned to that interface. The scheduler map includes a list of schedulers which map specific forwarding classes to specific scheduler configurations. These determine the per-class bandwidth allocations on each interface, which are taken into consideration when routing DiffServ-aware LSPs.
Bandwidth Model
A bandwidth model must be configured on all routers participating in the DiffServ domain. The three types of bandwidth models supported by Juniper are MAM, Extended MAM, and RDM, which are defined in the following table.
MAM | Defined in Internet draft draft-ietf-tewg-diff-te-mam-03.txt |
Extended-MAM | A proprietary bandwidth model that behaves much like standard MAM. If you configure multiclass LSPs, you must configure the extended MAM bandwidth model. |
RDM | Makes efficient use of bandwidth by allowing the class types to share bandwidth. RDM is defined in Internet draft draft-ietf-tewg-diff-te-russian-05.txt |
Operation
In order to take advantage of DiffServ aware single-class and multi-class LSPs, each class type must be configured consistently across the differentiated service domain. In other words, each router in the network must follow a consistent class type configuration. On each node router, each class type is mapped to a queue.
The available bandwidth for a particular class type on a link is determined by the configuration of class of service queues for that interface. Any DiffServ-aware LSP that requires bandwidth from a particular class cannot be established through routers that do not understand the Classtype object. It is possible for DiffServ-aware LSPs and regular LSPs to be established on the same router. In this case, the regular LSP will carry best-effort traffic by default. However, you cannot simultaneously configure multi-class LSPs and single-class LSPs on the same router.