MSP C&W Labs

Lab 1: create inventory objects needed by TETs. Step 1. Create Resource Mgr project of type MSP Generic Project. Name is <your name>_proj. Provision Status is In Progress. Set project as default. Create test Location. Location type is MSP Unknown Location. Name of location is <your name>_loc. Provision Status is Planned. Provide a location code. After creating that location, look under Resource Brower tab Projects/DesignRecords for node Projects/MSP Generic Project/<your name>_proj. Expand the node, and verify it contain a reference to the design record for the location creation. If not, you forget to set project as default Create test Subscriber. Subscriber type is MSP Subscriber, location is the location that was created above. Name is <your name>_sub, provision status is planned. Step 2. Create ADVA devices and cards. o Create ADVA device. Device type is MSP Devices, subtype is ADVA FSP 150-CCF825. Its location is <your name>_loc. Device Name is <your name>_ADVA_# where # is an integer incremented each time you create an ADVA device (e.g 1 2 3 4). Set Provision status to Planned. Set 3rd party maintainer attribute to any value. Set attribute MORI Ref Expected Flag to No. Activate option Continue after confirm, since we are going to create more ADVA devices. o Repeat previous step, to create another ADVA devices. So now, you should have create 2 ADVA devices, called xxx_1, xxx_2. Now populate these 2 devices, with cards. Create in each of these devices, 2 cards of type GigabitEthernetElectrical: one in slot lan-5, one in slot wan-1. Provision status is Planned. o At the end, you should have created 2 ADVA devices, each having 2 GigabitEthernetElectrical card in slot lan-5 and wan-1 Step 3. Create MSAN device and cards. (IPVPN service). MSAN devices are used by IPVPN services. o Create one MSAN device. Device type is MSP Devices, subtype is AXH 2500. Its location is <your name>_loc. Device Name is <your name>_MSAN_1. Set Provision status to Planned. Set 3rd party maintainer attribute to any value. Set attribute MORI Ref Expected Flag to No. o Add a card of type AXH 2510 CP to that device in shelf 1 slot CP slot. Name of card is <your name>_MSAN_CARD_TO_PE, provision status is

planned. This card provides 1 GigabitEthernet port required to connect to the MSP Core device (PE). o Add a card of type SDSL card to that device in shelf 1 slot SDSL. Name of card is <your name>_MSAN_CARD_TO_CPE, provision status is planned. This card provides 32 SDSL ports, one is required to connect to the CPE device. Step 4. Create cards in ALCATEL 7750 devices to provide free GigabitEthernet Ports. o Perform fast find of type Node by Node def. Look for devices of type Alcatel 7750. Perform Relation on any of the matching device, looking for one that is related to at least one MPLS LS(QoS) circuit (not a dummy device). o In Relation Browser, go to Devices tab, expand device, expand shelf 1. Under shelf1 are listed IOM2 Line Card. This card type provides 2 sub-slots. Find a IOM2 Line Card with an empty slot. o Launch the Card Wizard. Create a card in the empty slot of the IOM2 Line Card. Card type is M10-1GB-SFP. Provision Status is Planned. Name of card is M10-1GB-SFP-# where # is an integer incremented each time you create a card of this type (e.g 1 2 3 4). o The card of type M10-1GB-SFP provides 10 sub-slots. Use again the card wizard, to create a sub-card in first of the 10 sub-slots. Card type is PBA GIGE LX SFP OPTICS MODULE LC. Card Name is PE_CARD_ETHERNET_# where # is an integer incremented each time you create a card of this type (e.g 1 2 3 4). Provision status is Planned. This card provides one GigabitEthernet Port, to which we would connect our Ethernet access legs. o Repeat entire process 2 more times. Make sure to select different devices: we want to end-up with 3 ALCATEL 7750 devices with free GigabitEthernet Ports Repeat the entire process to provide free Ethernet port on these devices. o At the end, you should have 3 ALCATEL 7750 (PE), in which you inserted required cards to provide 1 free GigabitEthernet Port. Step 5. Create cards in ALCATEL 7750 devices to provide free TDM Ports. o Look for another Alcatel 7750 devices (not one that was used on previous step). Perform Relation on device, and verify it is related to at least one MPLS LS(QoS) circuit (not a dummy device). o In Relation Browser, go to Devices tab, expand device, expand shelf 1. Under shelf1 are listed IOM2 Line Card. This card type provides 2 sub-slots. Find a IOM2 Line Card with an empty slot. o Launch the Card Wizard. Create a card in the empty slot of the IOM2 Line Card. Card type is M4-CHOC3-AS-SFP. Provision Status is Planned. Name of card is M4-CHOC3-AS-SFP-1. o The card of type M4-CHOC3-AS-SFP provides 4 sub-slots. Use again the card wizard, to create a sub-card in first of the 4 sub-slots. Card type is PBA OC-3/STM-1 SFP IR-1/I-1 OPTIC MODE. Card Name is

PE_CARD_TDM_1. Provision status is Planned. This card provides one OC3 Port, to which we would connect our TDM access legs. Step 6. Create Cisco CE (model Cisco 878). For IPVPN services, access leg via a MSAN devices, uses in first CE Hop a Cisco CE of type 878. Cisco 878 are non-generic devices o Create CE router for IPVPN service Access Leg. Run device wizard. Device type is MSP device, subtype is Cisco 878. Location the location you created earlier. Fill attributes. Provide name for device: <your name>_CE878_1 Create Cisco CE (model Cisco 7304). For IPVPN services, TDM access leg uses a Cisco CE of type 7304. Cisco 7304 are non-generic devices o Create CE router for IPVPN service TDM Access Leg. Run device wizard. Device type is MSP devices, subtype is Cisco 7304. Location the location you created earlier. Fill attributes. Provide name for device: <your name>_CE7304_1 o Create in CE router a card of type 7300-4OC3POS-SMI. Insert that card in slot 2. Provision Status is planned. Card name is <your name>_CARD_C7304_TO_PE. This card type provides 4 OC3 ports. One OC3 port is going to be used to connect towards the Alcatel MSPE device o We need also an Ethernet Port towards the CPE. Create in CE router a card of type NSE-150, in slot 0: this card type provides 4 sub-slots. Insert in first sub-slot a daughter card of type GLC-LH-SM. Card name is <your name>_CARD_C7304_TO_CPE. This daughter card provides 1 Gigabit Ethernet Port.

Lab 2: create access legs and CE Hop: Step 1: Create first Access Leg. It is an Ethernet Access leg, Using ADVA device, C&W end to end. Can host VPLS, VPWS, IPVPN Service.

Create task engine Design Project: type is MSP Design Project , template is Access Leg Creation Ethernet (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_Access_leg_1

Process above design project, so that the access leg goes from ALCATEL MSPE that contains card PE_CARD_ETHERNET_1, to ADVA NTE called <your name>_ADVA_1. Remember you need to create 3 groups: MSPE1TRX1, TRX1 TRX2 , TRX2 ADVA1. o Please follow indications on diagram o Do not forget to connect on ADVA device on the WAN Port. o Find the ODF associated with Alcatel MSPE o Create all generic devices at location <your name>_loc. o Call the two TRX devices respectively <your name>_TRX_leg1_1 and <your name>_TRX_leg1_2. Device type is MSP Generic, subtype is Generic Transmission.

o Bandwidth for access leg is GigabitEthernet (provide same answer each time asked). o Call Generic Device ports, whatever name. o Do not provide MORI reference. o Connect on Alcatel MSPE on Gigabit Ethernet port that you created in lab1 o Do not create optional service. Launch a Technical Routing View on Ethernet Access Circuit created, and verify it match the diagram. Create task engine Design Project: type is MSP Design Project, template is Access Leg Creation CE Hop (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_CEHOP_1 Process above design project, so that the access leg goes from ADVA NTE <your name>_ADVA_1, to Generic CPE. o Please follow indications on diagram o Connect CE Hop, on one of the static port (Fast Ethernet) provided on the chassis of ADVA. o Bandwidth of CE Hop is FastEthernet o Create generic CPE at location <your name>_loc. Call Generic CPE <your name>_CPE_Leg1 Launch a Technical Routing View on Ethernet Access Circuit created, and verify it match the diagram. Step 2: Create second Access Leg and CE Hop. It is an Ethernet Access leg, Using ADVA device, C&W end-to-end. Can host VPLS, VPWS, IPVPN Service. Now we use a shortcut. Instead of modelling the ODF and Generic TX, we connect directly Alcatel MSPE to the ADVA NTE 1 group only in Access Leg creation TET.

Create task engine Design Project: type is MSP Design Project, template is Access Leg Creation Ethernet (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_Access_leg_2. Process above design project, so that the access leg goes from ALCATEL MSPE that contains card PE_CARD_ETHERNET_2, to ADVA NTE called

<your name>_ADVA_2. Remember you need this time to create only 1 groups: MSPE2 ADVA 2. o Please follow indications on diagram o Connect Alcatel MSPE on Gigabit Ethernet port that you created in lab1 directly to ADVA NTE 2. o Create no generic devices. o Bandwidth is GigabitEthernet o Do not forget to connect on ADVA device on the WAN Port. o No Mori reference o Do not create optional service. Launch a Technical Routing View on Ethernet Access Circuit created, and verify it matches the diagram. Create task engine Design Project: type is MSP Design Project, template is Access Leg Creation CE Hop (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_CEHOP_2 Process above design project, so that the access leg goes from ADVA NTE <your name>_ADVA_2, to Generic CPE. o Please follow indications on diagram o Create generic CPE at location <your name>_loc. o Call Generic CPE <your name>_CPE_Leg2 o Connect CE Hop on ADVA device, on the card inserted in the LAN slot. o CE Hop bandwidth is GigabitEthernet Launch a Technical Routing View on Ethernet Access Circuit created, and verify it matches the diagram. Step 3: Create third Access Leg. Ethernet Access leg, Using MSAN device, for IPVPN Service. This time again, we do not model ODF and NTE Transmission devices (shortcut). We use a shortcut. Instead of modelling the ODF and Generic TX, we connect directly Alcatel MSPE to the MSAN 1 group only in Access Leg creation TET. Note also, that when using MSAN, first CEHop uses SDSL circuit hierarchy.

Create task engine Design Project: type is MSP Design Project, template is Access Leg Creation Ethernet (CoS). Do not forget to set select parent

project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_Access_leg_3. Process above design project, so that the access leg goes from ALCATEL MSPE that contains card PE_CARD_ETHERNET_3, to MSAN NTE called <your name>_MSAN_1. o Please follow indications on diagram o Create no generic devices. o Connect on Alcatel MSPE on port provided by card PE_CARD_ETHERNET_3 o Access leg bandwidth is GigabitEthernet o Connect on MSAN device on card providing GigabitEthernet Port (name of card is <your name>_MSAN_CARD_TO_PE). o Do not create optional service. Launch a Technical Routing View on Ethernet Access Circuit created, and verify it matches the diagram. As can be seen from diagram, We need to run twice CE Hop TET. o firstly between MSAN and Cisco 878 o Secondly between Cisco 878 and Generic CPE Create first task engine Design Project for the first CEHop: type is MSP Design Project, template is Access Leg Creation CE Hop (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_CEHOP_3_1. This TET build circuitry between MSAN and Cisco CE (878 model). We will create later a second TET for going from CiscoCE to GenericCPE Process above design project, so that the access leg goes from MSAN NTE <your name>_MSAN_1, to Cisco CE model 878 we have created in lab1. o Please follow indications on diagram o A-end device is the MSAN device you created. Any SDSL port will do on that device o Z-end device is the Cisco CE model 878 that was created in lab 1 (name was <your name>_CE878_1). Chose an available SDSL port on that device. o When requested, enter following values for attributes: Bandwidth = 10 000 (in Mb) CWA Circuit Reference: 123 Provide Ethernet Access = Yes. Launch a Technical Routing View on Ethernet Access Circuit created, and verify it match the diagram. Create task engine Design Project for the second CEHop: type is MSP Design Project, template is Access Leg Creation CE Hop (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1.

Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_CEHOP_3_2. This TET builds circuitry between Cisco CE (878 model) and GenericCPE. o Process above design project, so that the access leg goes from Cisco CE model 878 we have created in lab1, to a Generic CPE. o Please follow indications on diagram o A-end device is the Cisco CE device model 878 o Select for A-End port any fastEthernet port on Cisco CE. o For Z-end device create a new Generic CPE device. Call it <your name>_CPE_Leg3. o For z-end port provide any port name. o Bandwidth: select FastEthernet. Launch a Technical Routing View on Ethernet Access Circuit created, and verify it match the diagram. Step 4: Create fourth Access Lge and CE Hop. TDM Access leg, for IPVPN Service. This time again, we do provide an Ethernet Access, but a TDM one.

Create task engine Design Project: type is MSP Design Project, template is Access Leg Creation TDM (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_TDM_Access_leg_4. o Process above design project, so that the access leg goes from ALCATEL MSPE that contains card PE_CARD_TDM_1, to Cisco CE (model 7304) called <your name>_CE7304_1. o Please follow indications on diagram o Create no generic devices. o Connect on Alcatel MSPE on port provided by card PE_CARD_TDM_1 o Connect on Cisco CE device on card providing TDM Port (name of card is <your name>_CARD_CE7304_TO_PE). o Provide no value for Circuit Name. o Provide circuit type TDM over C&W o Provide link type Generic o Provide bandwidth as 622 o Provide channel as 1 o No Frame Relay Bearer required

o PPP circuit is required o Do not create optional service. Launch a Technical Routing View on PPP Circuit created, and verify it matches the diagram. Create task engine Design Project for the CEHop: type is MSP Design Project, template is Access Leg Creation CE Hop (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_Ethernet_CEHOP_4. This TET builds circuitry between Cisco CE (model 7304) and a Generic CPE. Process above design project, so that the access leg goes from Cisco CE model 7304 named <your name>_CE7304_1, to a Generic CPE we are going to create. o Please follow indications on diagram o A-end device is the Cisco CE model 7304 device (name is <your name>_CE7304_1) o A-End port is the Gigabit Ethernet Port, which appears in a list if you have correctly created the needed card in device (name of card was <your name>_CARD_C7304_TO_CPE, that provides one GigabitEthernet port). o Z-end device is a Generic CPE you need to create from the TET. Call that CPE <your name>_CPE_Leg4 o Select bandwidth of GigabitEthernet Launch a Technical Routing View on Ethernet Access Circuit created, and verify it match the diagram.

Lab 3: provide VPLS service over Access Leg. We are going to provide a VPLS (L2-VPN) service, for subscriber <your name>_sub. We first create VPLS Parent Service. Then we build each customer site individually. For this lab, we only build one customer site, to save time Step 1: Create VPLS Parent Service. Create task engine Design Project: type is MSP Design Project , template is Create VPLS Parent Service (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_VPLS_PARENT_SERVICE Process that TET. o Provide as subscriber name: <your name>_sub. We created that subscriber in first lab o Provide Service type Ethernet VPN. Verify that an Ethernet VPN service and a L2 VPN topology (empty) have been created, and that they are related. Verify that topology is empty at this stage (launch for example a topology view). Step 2: build a Customer site, by creating a VPLS Access Service, associated to the VPLS parent Service. We are going to use TET, to build a VPLS Access Service (representing a customer site), which is related to the VPLS Parent Service. We are going to use Access Leg 1 to provide the customer site. This is what we are to create for the customer site.

 Create task engine Design Project: type is MSP Design Project, template is Create VPLS Access Service (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_VPLS_ACCESS_SERVICE_1 Process that TET. o First input attribute window Provide Bearer Group Cos Managed value is Yes. Provide as Ethernet Circuit the First Ethernet Access circuit of the first access leg. Look in TET called TET_Ethernet_Access_Leg_1 Look under task Create Ethernet Access Circuit/Create Overlying Ethernet access Circuit. Find the Ethernet Access circuit created Copy&Paste name of that Ethernet Access circuit. MultiCos or CosNotSet Circuit. Provide MultiCos Second Consumer to be provisioned. Provide Yes. That will be for the second part of the access leg, that was created using CEHop TET. VLAN provide value 11,101. Check above diagram to understand (QinQ). VPLSParentServiceName expects the name of the Ethernet VPN Service that has been created in Step 1. Look to previous TET, look for the service that was created. Copy&Paste name of service in that field. o Second input attribute window ask about MSS Group Input (see diagram below). When we are going to go through CoS training, youll understand it better. For now I just provide a short explanation. When connecting an ADVA to an Alcatel MSPE, there is some special configuration that can be done on the Alcatel MSPE. MSS Group model the first level of that configuration. Please select for Existing MSS Group value new For new MSS group group bandwidth provide value in kb of 100 000. This must match the bandwidth of the LAN port on ADVA to which we connected the CE Hop: its bandwidth was FastEthernet. For MSS Group Name enter CUST_SITEA_A825_LAN1

o Third input attribute task asks about SG Group Input. Again this corresponds to configuration that can be done on Alcatel MSPE when connected to an ADVA. This will be explained in CoS Training. In few words, the same access leg could be used to provide several types of Services: VPLS, VPWS, IPVPN. SG, which stands for Service Group, is basically how much of available bandwidth (fastEthernet CE Hop) do we reserve for this service type (e.g VPLS). Again this corresponds to actual configuration that can be done on Alcatel MSPE when connected to an ADVA. Existing SG group = new New SG Bandwidth = 40 000 MSS Group Name is SGE3-2. o Fourth input attribute task, ask about CosPolicyName: select EthernetVPN. o Next input tasks, are going to ask you characteristics of Cos partition characteristics for L2 consumer circuit. As can be seen from above diagram: Standard value is 3000 (expressed in kb) Enhanced value is 2000 Premium value is 7000 Burstable: no value Standard burstable: no value o Last input task in TET ask you for characteristics for the second L2 consumer (the one from ADVA to CPE) For Ethernet Circuit Look for TET called TET_Ethernet_CEHOP_1 Look for circuit that was created during that TET of type Ethernet Access Copy&paste name of circuit in that field. For VLAN: by looking to first diagram, value we need to provide is 101 Verification: Make a relation on TET called TET_VPLS_ACCESS_SERVICE Go to the L2 VPN topology associated to parent Ethernet VPN service. Launch a topology view. Confirm that the topology was populated with the 2 L2 consumers that were created during that TET. If we were to create more customer sites, they would appear under that topology. Launch a technical routing view on the first consumer (from Alcatel MSPE ADVA). In the technical Routing View, is it what you were supposed to build, and do you see the VLAN circuits you expected?

 Now get a CoS Partition Mapping View on first consumer. Where are the VLAN circuits? Clueless? VLAN are transparent circuits. Does that help? o Whats the size of the partition at the Ethernet over C&W circuit level (bearer)? Why?

Launch a CoS Partition Mapping View on second consumer circuit (from ADVA to CPE). Do you have the same as diagram below? Take some time to analyse how your TET input was used.

Check the

Lab 4: provide VPWS service over Access Legs. We are going to provide a VPWS (L2-VPN) service, for subscriber <your name>_sub. This VPWS service connects (point-to-point) two customer sites of this customer (access leg 2 access leg3). A pseudo wire is created between the 2 Alcatel MSPE.

The following circuitry is created over each of the two access legs:

Step 1: Create VPWS Service. We are going to create a VPWS Service over leg 1( access 1 + ce hop 1) and leg2 (access 2 + ce hop 2). Create task engine Design Project: type is MSP Design Project , template is Create VPWS Service (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_VPWS_SERVICE Process that TET. o First attribute input task prompt you for ServiceType. Select value Ethernet Wireline o Second attribute input task prompt you for subscriber (provide <your name>_sub) and for location (leave it empty) o Third input task prompt you for pseudo-wire ports. A pseudo-wire is going to be created between the 2 legs Alcatel MSPE. Look for TET TET_Ethernet_Access_Leg_1 (yes we pass VPLS and VPWS over same leg). Open its tasks Look for the a-end device of the first group task; it should be the Alcatel MSPE of that leg. Perform a relation on that device. Look for circuit of type MPLS LS (QoS) that are connected to that device (core). For one of these circuits, find the port that is used on Alcatel MSPE for that circuit. Thats the first pseudo-wire port. Do the same steps for Access Leg 2.

o Next task ask you to create a new group. Click on new group

o Next input task ask you for some information. The information is relative to the first access leg, and its first Ethernet access part (between Alcatel MSPE and ADVA NTE) Ethernet Circuit: first Ethernet Access circuit (between Alcatel MSPE and ADVA) of the first access leg used by VPWS service: Go to TET called TET_Ethernet_Access_Leg_1. Look for the Ethernet Access circuit that was created by this TET. Copy&paste its name VLAN: provide value 11,101 (check diagram) MultiCos Bearer Group Cos Managed: Yes Second Consumer Group to be provisioned: Yes (between ADVA and CPE) o Next input task ask you for MSS Group Partition Input. If you remember we already used access-leg-1 and CE hop 1 to provide a VPLS service in previous lab. Thats why, you see now for existing MSS Group attribute value CUST_SITEA_A825_LAN1. If you remember, MSS corresponds to some configuration done on Alcatel MSPE when connected to an ADVA, accounting for the LAN port used on ADVA. Existing MSS Group: select value CUST_SITEA_A825_LAN1 we are providing the VPWS service to same customer on same LAN port on ADVA. No value need to be provided for the other two attributes. o Next input task ask you for SG Groups. If you remember we can pass several type of service (VPLS,VPWS,IPVPN) to the same customer over the same connection. In previous lab, we created SG3-2 as 40 000 kb/s means we reserve 40 000 kbp/s for VPLS services on that FastEthernet Customer connection. Now for VPWS (SG3-1 by naming convention) we reserve 30 000 kbp/s. Existing SG Groups: select value New.

 SG Bandwidth: provide value 30000 New SG Group Name: provide value SG3-1. o Next task ask for AendGroupCosPolicyName: select EthernetWireline. Then in subsequent tasks provide Enhanced: no value EnhancedBurstable: no value. Premium: provide value 5000. Standard: provide value 2000 Standard Burstable: provide value 1000 Verification: Look for consumer circuit created by VPWS TET at this stage. Launch a Cos Partition Mapping View on that circuit. Note in that view that you have now 2 partitions called SG3-1 and SG3-2 on the Ethernet Access Circuit.

o Next attribute input task, ask you for information on the second consumer group of the first access leg. Ethernet Circuit: name of Ethernet Access circuit running between ADVA NTE and CPE of the first access leg. Look for TET called TET_Ethernet_CE_Hop_1 Look under that TET for Ethernet Access circuit that was created. Copy&paste circuit name VLAN: check diagram above. Value to provide is 101.

o Next window is the one displayed below. At that stage, we provided information for first access leg: first consumer group (Alcatel MSPE ADVA NTE) + second consumer group (ADVA CPE). Circuitry for VPLS was created over the first access leg. We do not want to provide a protection leg for first access, so just click button Finish Task.

o Next window is similar to previous one, but as explained in training slides, we know start processing second VPLS access leg. Click this time button New Group

o We start processing second VPLS access leg. Redo as was done for the first access leg. But this time use Ethernet Access circuits created by TET TET_Ethernet_Access_Leg_2 and TET_CEHop_Leg_2 o Process TET till the end, providing your own values. Verify that TET. o Check the list of design records that were creating during that TET. Try to verify the diagram below from what you see was created

o Launch a topology view on the L2 VPN topology. Do you get something similar to below screenshot?

o Launch a technical routing view on the Routed PW. Do you get something similar to below screenshot?

o Launch a Cos Partition Mapping view on one circuit of type Ethernet Connection (Qos) running between Alcatel MSPE and ADVA NTE. Do you get something similar to below screenshot?

o Perfect then. Lab 5: provide IPVPN service over Access Legs. We are going to provide an IPVPN (L3-VPN) service, for subscriber <your name>_sub. This IPVPN service connects two customer sites of this customer (access leg 3 + ce hop3 access leg4 + cehop 4).

Step 1: Create Subscriber IP Range. Launch the Number Wizard in RM. Chose number type Subscriber IP Range. Associate number to your subscriber: <your name>_sub. Enter in the number name field the following value: 172.xx.0.0/16, where xx is an integer (every student group should use a different value). Step 2: Create IPVPN (QoS) Parent Service. Create task engine Design Project: type is MSP Design Project, template is Create IPVPN QoS Service (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to

Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_IPVPN_PARENT_SERVICE. Process that TET: o Provide subscriber name <your name>_sub o Leave location name blank (we are using an existing subscriber) o Leave Subscriber IP Range blank (we are using an existing subscriber) Verify objects created by that TET: o Verify that an IPVPN service and a Customer VPN topology have been created during this TET. Rename IPVPN parent service to <your name>_sub_VRF1 o Find IP VPN parent Service o Run Service Wizard to modify that object o Change its name. Step 3: Create first IPVPN (QoS) Access Service. First IPVPN customer site is going to be created over Access Leg 3. In Lab 2, we created the following Access Leg 3, going via a MSAN device. This is an Ethernet Access Leg. We are going to build an IPVPN service using that Access Leg. (Access Leg 3)

(IP VPN service using Access Leg 3)

Create task engine Design Project: type is MSP Design Project, template is Create IPVPN QoS Access Service (CoS). Do not forget to set select parent project to be the Resource Mgr project you created in lab 1. Set provision status to Design Project In Progress, set Planned Finish Date to current Date. Set Name to TET_IPVPN_ACCESS_SERVICE_ONLEG_3. Process that TET: o On first input task (1.1) provide the following values: 01- PE Device Name: look for the Alcatel MSPE device to which leg 3 is connected. Copy & paste its name. Perform a relation on TET called TET_Ethernet_Access_Leg_3

Look for related device being an Alcatel 7750. 02 Ethernet Circuit(s): expect the name of two Ethernet access circuit separated by ,: First Ethernet Access Circuit, runs between Alcatel MSPE and MSAN device. Perform a relation on TET TET_Ethernet_Access_leg_3, look for related circuit of type Ethernet Access. Copy&paste name of circuit in above field. Then type , Second Ethernet Access Circuit, runs between MSAN device and Cisco CE. Perform a relation on TET TET_Ethernet_CEHop_3_1, look for related circuit of type Ethernet Access. Copy&paste name of circuit in above field after the , 03- VLAN(s) (Alcatel NTE): expects the VLAN numbers on section between PE and MSAN. Check diagram above, and understand that on that section we have 2 VLAN circuits 11 and 101. Provide value in that field 11,101. 04- VLAN(s) (NTE Cisco): expects the VLAN numbers on section between MSAN and Cisco CE. Check diagram above, and understand why this field is to be left empty. 05 FR Bearer/PPP Circuit: this field refers to an access leg over TDM. Access Leg 3 is over Ethernet. Leave that field empty. 06 FR DLC Number: empty (TDM) 07 IPVPN QoS Service Name: provide name of parent IPVPN service that was created in previous step. 08 Service Model: {N/A, IP Connect, IP Native}. Select value IP Connect. N/A is the old Blue Services IP Native, and IP connect are for the old Green Services. IP Native is an unmanaged service, which means that C&W does not manage the CE. 09 Service Agent: Service Agent is an Extension Class. Provide name of an existing Service Agent. In Resource Browser, go to tab Service Agent. Expand. Look for an instance that may correspond to C&W. Copy&paste its name in that field. Note: TET is going to create a relationship between this Service Agent and the Cisco CE device. 10 MultiCos or CosNotSet: select MultiCos 11 Bearer Group CoS Managed: select No 12 Second Consumer to be provisioned. Select Yes (between Cisco CE and CPE)

NB: At this stage, TET create VLANs between Alcatel MSPE and Cisco CE. o On second input task (1.13.1.1) you are requested to select an existing Cos Policy group for A End: select value IPSelect AAQ. This CoS Policy Group is having some attributes, that you need to fill in subsequent input tasks Policy Attribute IPSelect AAQ-AF1: 1000 (expressed in kb) Policy Attribute IPSelect AAQ-AF2: 3000(expressed in kb) Policy Attribute IPSelect AAQ-AF3: no value Policy Attribute IPSelect AAQ-AF4: no value Policy Attribute IPSelect AAQ-Control: no value Policy Attribute IPSelect AAQ-Default: no value Policy Attribute IPSelect AAQ-Premium: no value Policy Attribute IPSelect AAQ-RealTime: no value Policy Attribute IPSelect AAQ-Scavenger: no value o On next input task (1.17.1.1) you are requested to provide information for Second consumer (between Cisco CE CPE). 01 Ethernet Circuit: that field expect the name of the Ethernet Access Circuit running between Cisco CE and CPE. Perform a relation on TET called TET_Ethernet_CEHOP_3_2 02 VLANs: from diagram above, understand you should provide value 101. NB: at this stage TET creates the following objects:

VLAN circuit on the last section (between Cisco CE and CPE) Create 2 IP Consumer Circuits (circuit type is IP Consumer (QoS). First one goes from Alcatel MSPE to Cisco CE. Second one goes from Cisco CE to CPE Create an access service (type is IPVPN Access). This Access Service is related to the 2 IP Consumer Circuit. Topology (type is Customer VPN) is updated: it now contains the leg consumer circuits. Service Agent is added one relationship with Cisco CE device of that leg. Name of relation is managed.

o On next input task (1.11) you are requested to provide information for the different configuration information of that VPN. 01 ASN: What is the Autonomous System Number to use. Pick from the list 4445 02 Customer Subnet: provide value 172.xx.0.8/30. IP subnet that is assigned to network between Alcatel MSPE and Cisco CE. That subnet need to belong to the IP Subscriber Range assigned to Subscriber, and is usually a /30 network. In step 1 you have created an IP Subscriber IP Range 172.xx.0.0/16. Provide for Customer Subnet between Alcatel MSPE and Cisco CE the following Customer Subnet value: 172.xx.0.8/30. 03 PE IP Address: provide value 172.xx.0.9. IP address of the interface on PE that connects to the CE. As can be seen, that IP address belongs to Customer subnet defined above. 04 CE IP Address: provide value 172.xx.0.10. Same comment as above. 05 Use an existing VRF. Select value no 06 VRF: provide value <your name>_VRF. Usually VRF would be called by colour names. Remember that VRFs are the virtual router as configured on PE. VRF are usually assigned interfaces on PE connecting to CEs. VRF are usually configured with 2 important parameters: Route Distinguisher (RD) and Route Target (RT). 07 RD Type Scheme: Select value Type 0. A Route Distinguisher can have several format <ASN>:<unique number> or <ip address>:<unique number>. Here we use RD format <ASN>:<unique number> 08 RD: enter value 4445:1000. This parameter provides the actual value of RD. Its value mandatory follows the RD Type Scheme that have been selected in parameter 07 (we chose <ASN>:<unique number>, and the ASN part is mandatory equal to the ASN Number that was selected in parameter 01. 09 RT Type Scheme: Select type 0. Route Target must be in format <ASN>:<unique number>

 10 Export RTs: provide value 4445:1000. Same remarks than RD apply here. Customer routes learnt on that leg are exported as RT 4445:1000 11 Import RTs: provide value 4445:1000. From value of Import/Export statements, it looks like we are creating a full-meshed VPN.

NB: at this stage TET creates the following objects: VRF related to port on PE connecting to CE RD Number related to number of type VRF Number of type RT Import, related to number of type VRF Number of type RT Export, related to number of type VRF Number of type Customer Subnet, related to Subscriber IP Range. 2 IP Addresses, related to ports on PE and CE.
o On next input task, TET ask input on Router Policy & Queues. Add Group CoS Attributes as follows; o IPSelect AAQ o o o A-End Alcatel Ingress Policy ID = 106 A-End Alcatel Ingress Queue Name = IPVPN_Std_E3_E2_E1_EF_Ingress A-End Alcatel Egress Policy ID = 106

o o o o

A-End Alcatel Egress Queue Name = IPVPN_Std_E3_E2_E1_EF_Engress Z-End Cisco Inbound Policy Name = a420a310a210a110d50-2048k aaq-pnt-

Z-End Cisco Outbound Policy Name = aaq-pnta420a310a210a110d50-2048k

Add Individual CoS Attributes as follows; o IPSelect AAQ-AF4 o o o o o A-End Alcatel Ingress Queue ID = 4 A-End Alcatel Egress Queue ID = 4 Z-End Cisco Inbound Queue ID = 4 Z-End Cisco Outbound Queue ID = 4

IPSelect AAQ-AF3 o o o o A-End Alcatel Ingress Queue ID = 3 A-End Alcatel Egress Queue ID = 3 Z-End Cisco Inbound Queue ID = 3 Z-End Cisco Outbound Queue ID = 3

IPSelect AAQ-AF2 o o o o A-End Alcatel Ingress Queue ID = 2 A-End Alcatel Egress Queue ID = 2 Z-End Cisco Inbound Queue ID = 2 Z-End Cisco Outbound Queue ID = 2

- The End -