SAM IP-MPLS Service Provisioning Lab Guide

SAM IP-MPLS Service
Provisioning Lab Guide

TOS36024 Issue 1
LAB GUIDE
All Rights Reserved Alcatel-Lucent 2011
All rights reserved Alcatel-Lucent 2011

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

SAM IP-MPLS Service Provisioning Lab Guide - Page 1
Empty page
Switch to notes view!
SAM IP-MPLS Service Provisioning Lab Guide
This page is left blank intentionally

Terms of Use and Legal Notices

1. Safetyto
Warning
Switch
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent.
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page

About this Student Guide

Conventions
used
in this guide
Switch
to notes
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

6

Do not delete this graphic elements in here:
Lab 1
Router Discovery
Blank Page

Router Discovery
Lab Module Objectives

Upon completion of this lab module, you will be able to:

Provide the basic configuration to the labs network devices to enable the
5620 SAM to discover and manage them
Configure a Mediation Policy to discover network devices
Create a Discovery Rule to discover network devices on 5620 SAM
Verify that network devices are discovered and are managed by the 5620 SAM
Perform manual reconciliation of network devices

Router Discovery
Introduction to the BOF

Switch
notes
view!
Save
thetoBOF
and
Configuration File
Note: When a 7750 SR boots up, it will execute the bootloader (boot.ldr) on the Compact Flash card
CF3 (CF1 for a simulator), then load the BOF (bof.cfg), also on CF3 (CF1 for a simulator), which
indicates where to find the image (.tim files) and configuration files (.cfg files), installs the
management Ethernet and serial console port (default value 115200) and (de)activates
persistence, used for the SAM application.
1. View the BOF and verify the configuration and image files and their location on the flash cards
using the file structure. What is the image file used, and where is it stored?
PEx# show bof
PEx# file
PEx>file cf3: \# dir
2. Create your personal directory that will contain your configuration file.
PEx>file cf3: \# md <your_directory>

3. Change the configuration file in the BOF to a filename of your choice in the directory created in
Router Discovery
step 2.
PEx# bof
PEx>bof# primary-config cf3:\<your_directory>\<your_filename>.cfg
4. Activate persistence on the BOF
PEx>bof# persist on
5. Save the BOF
PEx>bof# save
PEx>bof# exit
PEx#
Preparing the Node for SAM

1. Follow your instructor's directions to initiate a CLI or SSH session with the appropriate router network

element.
Use the table below to register the routers Basic boot Parameters provided by the instructor:
Labs router Basic Boot Parameters
Ethernet Interface IP Address / Network Mask:
System IP Address / Network Mask:
2. Verify the current configured boot parameters on the bof file:
NODE_X# bof
NODE_X>bof# show bof
If the Internet address of the Ethernet interface is not configured or does not match the address
provided by your instructor enter the following command:
NODE_X>bof# address <IP address/subnet>
3. Set persistence on
NODE_X>bof# persist on
Router Discovery
4. Define
a location to save the configuration file
NODE_X>bof# primary-config <file location:/file path/filename.cfg>

5. Save the boot parameters changes
NODE_X>bof# save bof

6. Specify SSH Preserve Key
NODE_X# configure system security ssh preserve-key

7. Define the routers ID (System Address)
NODE_X# configure router interface system address <IP address/32>

8. Configure SNMP Security
NODE_X# configure system security snmp

NODE_X# community <community string> rwa version both
9. Enable SNMP
NODE_X# configure system snmp

NODE_X# packet-size 9216
NODE_X# no shutdown
Preparing the Node for SAM

10. Confirm changes
NODE_X# show bof

NODE_X# show router interface
NODE_X# show system security communities
NODE_X# configure system snmp
NODE_X>config>system>snmp# info
11. Save the network devices configuration
NODE_X# admin save

Router Discovery
Blank Page

Router Discovery
Network Devices Discovery Configure Mediation Policy

Create a mediation policy to define the interval and ratio used by 5620 SAM to poll the network devices for
SNMP MIB configuration changes.
Technical Reference
See Alcatel-Lucent 5620 SAM, Release 7.0 User Guide Section 10.7 Discovery
procedures Procedure 10-1 for the procedure to configure NE mediation.
The following lines summarize the steps recommended to configure a Mediation Policy for this lab:
1. Choose Administration Mediation from the main menu. The Mediation (Edit) form opens with the
General tab displayed.

2. Configure as required the parameters:
Polling Synchronization Time is the reference time for all polling intervals, which are typically
defined in a given policy.
Polling Admin State (Up or Down)
Discovery Rule Scan Interval specifies how often 5620 SAM database rescans the network according
to discovery rules that are enabled.
Router Discovery
3. Click on the MIB Entry Policies tab to configure MIB polling intervals for network devices, as required.
The MIB Entry Policies tab window displays a list of MIBs organized by the product name of the device
that supports the MIB.
i.
ii. Configure the search filter to look for the 7701 MIBS and click on the Search button. The Mediation
(Edit) form displays the MIB entry policies for the 7701.
iii. Select one or more MIBs from the list.
iv. Click on the Properties button. The MIB Entry Policy (Edit) form opens.
v. Configure the parameters:
Polling Interval specifies how often MIB elements of discovered and managed devices are polled for
changes to their MIBs. When changes are detected, the 5620 SAM rereads the MIB element and
updates the database. The default is 15 minutes. When this parameter is disabled, synchronization
between network elements and the database do not occur.
Administrative State (Up or Down)
vi. Click on the OK button.

vii. Confirm the action. The MIB Entry Policy (Edit) form closes and the Mediation (Edit) form reappears.
viii. Click on the Apply button on the Mediation (Edit) form to save the changes, if required.
Network Devices Discovery Configure Mediation Policy

4. Click on the Mediation Security tab button.
i.
Click on the Add button to create a new SNMP mediation security policy, or select an existing policy
and click on the Properties button to modify the policy. The MediationPolicy form opens.
ii. Configure the Display Name and the Security Model from the general mediation parameters.
iii. Configure the parameters in the CLI and File Transfer panels. Set the User Name and User Password
as required. Ensure that the user and password are already configured on the network devices to
which this mediation security policy will be associated. Register the values on the table bellow.
Labs Network Device CLI Parameters
User Name:
User Password:
Labs Network Device File Transfer Parameters

User Name:
User Password:

Discovery
iv.Router
Click
on the OK button. The MediationPolicy form closes and the Mediation (Edit) form reappears.
5. Click on the OK or Apply button on the Mediation (Edit) form to save the changes to the database.
Network Devices Discovery Create Discovery Rule

Create a discovery rule to discover for the labs network devices.
Technical Reference
See Alcatel-Lucent 5620 SAM, Release 7.0 User Guide Section 10.7 Discovery
procedures Procedure 10-4 To discover devices for the procedure to discover
network devices. In addition, refer to TOS36013 - 5620 SAM R7.0 Operator
Student Guide Section 4.1 Discovery Management for detailed screenshots of
the configuration process.
The following lines summarize the steps recommended to create a discovery rule for this lab:
1. Choose Administration Discovery Manager from the 5620 SAM main menu. The Discovery Manager
(Edit) form opens with the Discovery Rules tab displayed.

i.
Click on the Add button. The Create Discovery Rule - Specify General Attributes form opens.
ii. Specify a Description for the discovery rule that is up to 80 characters. Specify the Administrative
State. When the administrative state is set to Up, the network is scanned according to the discovery
rule when the discovery rule is saved. The network is also scanned according to the discovery rule as
specified by the Discovery Rule Scan Interval parameter in the Mediation window. If the
administrative state is set to Down, the network is not scanned as specified by these conditions.
iii. Click on the Next button. The Add Rule Elements form opens.
iv. Click on the Add button. The TopologyDiscoveryRuleElement
(Create) form opens.
Router Discovery
v. Configure the network devices parameters IP Address and Mask Bits. Enter the parameters previously
used to configure the network device during the Basic Network Device Configuration Lab.
vi. Click on the OK button. The TopologyDiscoveryRuleElement (Create) form closes. The discovery rule
is saved.
vii. Add more rule elements as required by performing substeps iv to vi.
viii. Click on the Next button. The Configure Mediation Security form opens.
ix. Specify the mediation policies for Read Access, Write Access, and SNMP Trap Access. Click on the
Select button and choose the mediation policy created on the Network Device Discovery Configure
Mediation Policy Lab.
x. Click on the Finish button to complete creation of the Discovery Rule using default values. The Create
Discovery Rule Configure Mediation Security form closes and a warning dialog box opens.
xi. Click on the OK button on the warning dialog box to close it. The Discovery Manager form reappears.
2. Click on the Apply button on the Discovery Manager form to discover the network devices by scanning
the network as specified on the created discovery rule.

The 5620 SAM discovers devices by scanning the network as specified by the discovery rules. After a
device is discovered, the 5620 SAM sets the device in a managed state and reconciles the device
elements into its database.
Discovery rules that are disabled or shut down are not applied.
Network Devices Discovery Verify Discovery

The following lines summarize the steps recommended to verify the Labs network device is discovered and
is managed by the 5620 SAM:
1. Open the Discovery Manager form and click on the Managed State tab button. A list of managed
devices opens.
i.
Verify the labs newly discovered network device is on the managed devices list.
ii. Verify the management state of the labs network device displayed in the Site State column.
Managed is the default state. If the device is unmanaged, select the device from the list and click on
the Manage button.
2. Perform a management IP address ping to ensure connectivity to the network managed device. From
the Managed State tab

i.
Click on the managed network device in the list.
ii. Click on the appropriate ping button.

iii. Review the ping information to verify connectivity.
3. Verify the network device configuration has been reconciled with the 5620 SAM database by clicking on
the Resync Status tab button. The status is displayed in the Resync Status column.
4. If required, initiate manual reconciliation of the network device. From the Resync Status tab on the
Discovery Manager form:

Discovery the network device or devices from the list
i. Router
Choose
ii. Click on the Resync button.

5. Close the Discovery Manager form.
6. Move the discovered network device icon into a group on the topology map. All newly discovered
network devices should be listed in the Discovered NEs group.

i.
Double-click on the Discovered NEs group icon. The Discovered NEs window opens with the list of
discovered nodes.
ii. Select the discovered network node(s) from the list and drag-and-drop the listing into the appropriate
group.
iii. The network node icon will appear in that group.
7. The network devices that have been successfully reconciled appear in the 5620 SAM navigation tree
and the Equipment Manager form.
End of Lab
Router Discovery Labs

Router Discovery
Lab 2
Routing


Create Network Interface

Create Static Routes
Create OSPF Area(s)
Add Network Interfaces to OSPF
Create ISIS Area
Add Network Interfaces to ISIS

OSPF Configuration Lab
Interface Configuration
The following lab exercises will guide you through the steps necessary to configure Static Routes & OSPF
protocol in the labs managed network.
1. Create Network Interface
2. Create Static Routes
3. Create OSPF Area(s)
4. Add Network Interfaces to OSPF
5. Create ISIS Area
6. Add Network Interfaces to ISIS
Create Network Interfaces

The following lines summarize the steps recommended to configure Network Ports to act as Layer 3
interfaces for this lab:
1. Choose Equipment from the view selector in the navigation tree. The navigation tree displays the
Equipment view. Following your instructors directions, navigate to the appropriate Port under a
managed device.
2. Right-click on a Port object in the Equipment view and choose Properties from the contextual menu.
The Physical Port (Edit) form opens with the General tab displayed.
3. Ensure the port is in Network Mode
4. Select
theLabRouting from the view selector in the navigation tree. Click the plus button beside the
OSPF Configuration
router. Right click Routing Instance and select Create Interface. The Network Interface wizard opens.
This is a multiple step process and is repeated for each network interface to be created. Selecting
Finish at any point in the wizard will apply the default settings of the remaining steps to the interface
and close the wizard.
Step 1 Configure Interface Name
Step 2 Configure IP Address click on the Add button. Configure the following parameters:
Network ID primary address (ID # 1) or up to 15 secondary addresses
IP Address and Prefix Length (Subnet) (Numbered) as per network configuration
Step 3 Select Port click on the Select button. The Select Port form opens with a list of all Network ports
available on the device. Following your instructors directions select the appropriate port from the list
and click on the OK button. The list will clear and the selected port designator will appear in the Port
block.
Follow your instructor's directions to configure the Policies and Filters on the next steps of the wizard.
Alternatively, clicking the Finish button in the Create Network Interface wizard window at any time
will apply the default values for each parameter within the successive steps.
Static Route Configuration

Create
Static
Switch
toRoutes
notes view!
1. Continue working from the Routing tab. Click the plus button beside the router. Right click Static
Routes and select Create Static Route. The Static Route wizard opens.
Step 1 Configure a Destination IP and Subnet (Prefix Length)
Step 2 Configure the next hop IP Address
Follow your instructor's directions to configure Preference / Metric
Verify Operational State

1. From the Tools Menu select Service Test Manager (STM)
2. Select Create ICMP Create ICMP Ping
3. Look for two yellow fields: In the From IP Address select the System IP of your router, from the Target
IP Address enter the destination of your ping

Optional: You can specify a Source IP Address for additional testing granularity
2. Click on the OK button
3. Click on the Search button
All Rights Reserved
Alcatel-Lucent
2011tab
4. Open the Test you just created and navigate
to the
Results
5. At the bottom of the window select Execute and note results
Note: It may be useful to create an ICMP Trace using the same series of steps
If your ping failed, why? If your pinging your partners system IP address, in the icmp ping packet the
source address used is your system IP address. If your partner has not made a static route (a path back
to your routers system IP address) the ping reaches the destination but has no route back. In this case
try specifying the source address as your interface IP and the ping should now be successful.
OSPF
Enable
OSPFto notes view!
Switch
1. Continue working from the Routing drop-down menu. Click the plus button beside the router. Right-
click on a Routing Instance and choose Properties

2. Click on the Protocols Tab and following your instructors directions check the appropriate protocol
(OSPFv2 or OSPFv3)
4. Verify the protocol appears on the list
5. Repeat the above steps (enable OSPFv2 or OSPFv3) for each router in your network
Create an OSPF Area & Add Interfaces

1. Continue working from the Routing drop-down menu. Click the plus button beside the OSPFv2 Instance.
Right-click on the OSPFv2 Instance and choose Create Area

Note: The 7705 and 7750 behavior is slightly different in this regard
7705: Right-click on the OSPFv2 Instance and choose Create Area
7750: Click the plus button beside OSPFv2 Instances, right-click on Instance and choose Create Area
2. From the General Tab add Area 0. From the Interface Tab add the network interfaces to be included in
Area 0
Note: Interfaces can be added at a laterAlltime
by right
clicking
on the area and selecting Create
Rights Reserved
Alcatel-Lucent
2011
Interface
4. Repeat the above steps for each router in your network until OSPF is fully populated
5. Click the plus button beside Area 0.0.0.0 Backbone and verify that all the interfaces you added are
there and all the warnings are cleared

1. Expand Area 0.0.0.0. Ensure all the interfaces are there including the system interface. As your
partners come online look for your warnings and minor alarms to clear.
Step 1: From the Tools Menu select Service Test Manager (STM)
Step 2: Select Create ICMP Create ICMP Ping
Step 3: Look for two yellow fields: In the From IP Address select the System IP of your router, from the
Target IP Address enter the destination of your ping
4. Open the Test you just created and navigate to the Results tab
ISIS
Enable
ISIS to notes view!
Switch
1. Continue working from the Routing drop-down menu. Click the plus button beside the router. Right-
click on a Routing Instance and choose Properties

(ISIS)
5. Repeat the above steps (enable ISIS) for each router in your network
Create an ISIS Area

1. Continue working from the Routing drop-down menu. Click the plus button beside the ISIS Instance.
Right-click on the ISIS Instance and choose Add NET Address

2. Within the NET Address Section specify an Area ID (49.0051)
4. Repeat the above steps for each router
5. Click the plus button beside Area 0.0.0.0 Backbone and verify that all the interfaces you added are
there and all the warnings are cleared

Add Interfaces & Specify Level 1 / 2

1. Continue working from the Routing drop-down menu. Click the plus button beside the ISIS Instance.
Right-click on the ISIS Instance and choose Create Interface

2. Within the Interface click the Select button to add an interface
3. Specify the Interface Capability from the Type and Level Capability pulldown menus (Broadcast /
Level 1 and 2)
3. Repeat the above steps for each Interface
4. Verify that all the interfaces you added are there and all the warnings are cleared

1. Expand Area 0.0.0.0. Ensure all the interfaces are there including the system interface. As your
partners come online look for your warnings and minor alarms to clear.
Step 1: From the Tools Menu select Service Test Manager (STM)
Step 2: Select Create ICMP Create ICMP Ping
Step 3: Look for two yellow fields: In the From IP Address select the System IP of your router, from the
Target IP Address enter the destination of your ping
4. Open the Test you just created and navigate to the Results tab
Configure Ports



Static Routes

Create Static Routes

2
5
OSPF

Enable OSPF



ISIS

Enable ISIS

Create an ISIS Area

1

Add Interfaces & Specify Level 1 / 2

1

End of Lab
Routing Configuration

Lab 3
MPLS
Blank Page

MPLS


Enable the LDP protocol on routing instances

Create LDP Interface
Create Targeted Peers
Create RSVP Paths
Create RSVP LSPs

MPLS

MPLS
MPLS Using LDP Configuration

MPLS
MPLS Using LDP Configuration

Configure the MPLS using LSPs for the lab network.
Technical Reference
See Alcatel-Lucent 5620 SAM, Release 7.0 User Guide 38.5 Routing protocol
configuration procedures / LDP for the procedures to configure LDP in the
managed network. In addition, refer to TOS36013 - 5620 SAM R7.0 Operator
Student Guide Section 7.2 MPLS using LDP for detailed screenshots of the
configuration process.
The following lab exercises will guide you through the steps necessary to configure OSPF protocol in the
labs managed network.
1. Create LDP Interface
2. Create Targeted Peers
3. Manage LDP interfaces
Enable LDP Protocol

1. Continue working from the Routing tab. Click the plus button beside the router. Right-click on a
Routing Instance and choose Properties

(LDP Enabled)
MPLS

5. Repeat the above steps (enable LDP) for each router in your network
Add LDP Interfaces

1. Continue working from the Routing tab. Click the plus button beside LDP. Right-click on LDP and choose
Create Interface
2. From the General Tab click Select (from the Interface Section) and add the network interface to be
included in LDP
Note: Repeat steps 1 & 2 until all interfaces have been added
Note: Click the plus button beside the LDP Interfaces field to see the interfaces you just added
3. Repeat the above steps for each router in your network until all interfaces are included in LDP
Create LDP Targeted Peers

1. Continue working from the Routing tab. Click the plus button beside LDP. Right-click on LDP and choose
Create Targeted Peer

2. From the General Tab fill in the system IP of your peer router in the Peer Address Field (highlighted
yellow)
Note: Click the plus button beside the LDP Targeted Peers field to see peers you just added
4. Repeat the above steps for each peer & on all routers in your network

Verify
Operational
Switch
to notesState
view!
2. Select Create MPLS LDP Tree Trace
3. From the General Tab:
1.
Name the LDP Test
2.
Click the Select button and specify the originating node
3.
Specify the System IP of the target node
4.
Click Apply
5.
Click Execute
4. From the Results Tab note the test results

MPLS
Enable LDP

MPLS
Add LDP Interfaces

MPLS
Create LDP Targeted Peers

MPLS

MPLS
2
3
5

MPLS

MPLS
MPLS Using RSVP-TE Configuration

MPLS
MPLS Using RSVP-TE Configuration

The following lab exercises will guide you through the steps necessary to configure OSPF protocol in the labs managed network.
1. Enable Traffic Engineering
2. Enable MPLS/RSVP
3. Add MPLS Interfaces
4. Create RSVP-TE Paths
5. Configure RSVP-TE LSPs
Enable OSPF Traffic Engineering

1.
2.
3.
Right-click the OSPF Instance and select Properties

Click on the Behavior Tab and change the Traffic Engineering Support setting to true
Click on the OK button
Enable MPLS & RSVP

1.
2.
Right-click Routing Instance. Select Properties.

From the Protocol Tab click MPLS Enabled
Note: By enabling MPLS, RSVP will also be enabled
Add MPLS Interfaces

1.
2.
3.
Right-click MPLS. Select Create Interface

From the General Tab click Select
Click OK
Note: Repeat the above steps for all Interfaces
Create RSVP-TE Paths

1.
2.
3.
4.
5.
6.
7.
Choose
Manage MPLS MPLS Paths from the main menu
MPLS
From the Manage MPLS Paths window select Create
Specify the name of the MPLS Path, click Next
Select the path starting point
Add the hops through the network by clicking Insert Hop
Note: During this process specify the Hop Type as Strict/Loose
Click OK
Click Finish
Create RSVP-TE LSPs

1.
2.
3.
4.
5.
6.
Choose Manage MPLS Dynamic LSPs from the main menu

From the Manage Dynamic LSPs window select Create
Specify the name of the LSP, click Next
Use the Select button to specify the path Source and Destination
Click the Add button to select the RSVP-TE Path created earlier
1.
Specify the Path Type (Primary), Click Next
2.
Choose the RSVP-TE Path, Click Next
3.
Optionally: Configure a Reserved Bandwidth and Hop Limit
4.
Specify the initial state of the LSP-Path binding (Admin: UP)
5.
Click Finish
The remainder of the steps are Optional:
1.
Specify Fast Reroute
2.
Specify Backup Type (One-to-One / Many-to-One)
3.
Specify Path Signalling Properties such as Retry timers/limits and RSVP Reserve style
4.
Specify Make before Break (True/False)
5.
Enable CSPF (True/False)
6.
Specify a Route Selection Metric
7.
Assign Administrative Groups
8.
Allow LDP over RSVP
9.
Enable Auto-Bind
10. Specify the initial state of the LSP-Path binding (Admin: UP)
11. Click Finish

Verify
Operational
Switch
to notesState
view!
2. Select Create MPLS LSP Ping
1.
Name the LSP Ping Test
2.
Click the Select button and specify the originating node
3.
Click the Select button and specify the LSP Path ID
4.
Click Apply
5.
Click Execute

MPLS
Enable OSPF Traffic Engineering

MPLS
Enable MPLS & RSVP

MPLS
Add MPLS Interfaces

MPLS
Create RSVP-TE Path

MPLS
Create RSVP-TE Path

MPLS
Create RSVP-TE Path
8
MPLS
Create RSVP-TE LSP

MPLS
RSVP-TE LSP Name LSP & Specify Source / Destination

3

MPLS
RSVP-TE LSP Add Primary / Secondary Paths
3
2
5
MPLS
RSVP-TE LSP Specify LSP Properties
11
MPLS

MPLS
2
3

MPLS
End of Lab
MPLS

MPLS

MPLS
Lab 4
Service Tunnels


Create Service Tunnels
Configure Access Ports

Service Tunnels Configuration
Service Tunnel Configuration

The following lab exercises will guide you through the steps necessary to configure service tunnels in the
labs managed network.
1. Create SDP Tunnels
2. Configure Access Port

1. From the Menu select Manage Service Tunnels
2. Select Create then IP/MPLS Service Tunnel (SDP)
Step 1 Configure Service Tunnel Name

Note: Auto-Assigning the SDP ID is fine as long as you use a Clear Tunnel Name
Step 2 Pick Source Node: Type or use the Select Button to enter the source system address
Step 3 Pick Destination Node: Type or use the Select Button to enter destination system address
Step 4 Specify Transport
Underlying Transport: MPLS
LDP Enabled: True
Signaling: TLDP
Note: From the Service Tunnel Topology view you can see the SDP link you created
Note: As shown Step 4 may look different depending on 7705/7750/release to release

2. Select Create Service Transport Tunnel Ping
1.
Name the Service Site Ping Test
2.
Click the Select button and specify the node the ping will originate from
Optionally Specify the Return Tunnel ID (SDP number)
3.
Click Apply
4.
Click Execute



1
2
4
4




End of Lab

Lab 5
EPipe


Create an EPipe
Assign a Port to SAP
Assign an LSP to SDP

EPipe Configuration
EPipe Configuration
Configure EPipe.

Technical Reference
See Alcatel-Lucent 5620 SAM, Release 7.0 User Guide 54.7 Creating a VLL
EPipe service.
The following lab exercises will guide you through the steps necessary to configure traffic engineering in
the labs managed network.
1. Create a EPipe
2. Assign a Port to SAP
3. Assign an SDPs
Configure Access Port

1. From the Equipment tab. Right click the equipment facing port and select Properties.
2. Change the Mode to Access, and Encap Type to Dot1Q
Note: From the Port MTU will automatically increase from 1514 to 1518 when you select OK
EPipe Configuration
EPipe Creation
The following lines summarize the steps recommended to create a EPipe for this lab:
1. Choose Create Service VLL Epipe from the main menu
2. From the General Tab, click the Select button to add the Customer and specify a Service Name
3. From the Components Tab, right-click on Epipe Service and choose Create Site
- Select both nodes that will be included in the Epipe Service

4. Right-click the Access Interface and select the Access Port (From the Port Tab)
Note: Access Ports: When adding the access port, to specify a vlan tag uncheck the box beside AutoAssign ID
5. Right-click on Spoke SDP Bindings and select Create Spoke SDP Binding
- When adding the Spoke SDPs (From the General Tab) after selecting the Tunnel Termination Site you
may Auto-Select the Tunnel or use the Select button to specify a SDP
- From the Return Tab you may Auto-Select the Return Tunnel or once again use the Select button to
specify the return tunnel you created
6. Once the service is populated with your access port and spoke SDP, select the Topology View button to
view the service you have created

Note: If your network port MTUs are too small this is the stage you will see problems. When you select
View Topology your service will be painted red. Right click either node and select Properties. You
may see SDP Binding Down. If you right click the SDP links and select Properties you may see Tunnel
MTU Too Small. Simply adjust your network port MTUs to an appropriate value on both ends and your
service should come up.

Verify
Operational
Switch
to notesState
view!
2. Select Create Service Service Site Ping
1.
Name the Service Site Ping Test
2.
Click the Select button and specify the node the ping will originate from
4. From the Test Parameters Tab:

1.
Click the Select button and specify the Target IP Address
2.
Click the Select button and choose the service to be tested
3.
Click Apply
4.
Click Execute

EPipe Configuration

EPipe Configuration
Add the EPipe Service

1

EPipe Configuration
Add the EPipe Service

EPipe Configuration
View Topology

EPipe Configuration
Adjust Network Port MTUs

Eth. Frame
IFG
Preamble
DA
SA
Type
VLAN
Tunnel
PW Header
CW (opt)
Payload
FCS
Total MTU Required

EPipe Configuration
Null
6
6
2
4
4
1514
1536

EPipe Configuration
2
3

EPipe Configuration
End of Lab
EPipe Configuration

EPipe Configuration
Lab 6
VPLS
Objectives
Upon successful completion of this module, the student will be familiar

with:
Steps in configuring a Virtual Private LAN Service (VPLS)

Virtual Private LAN Service (VPLS)
VPLS Configuration
Configure Access Port(s)

1. From the Equipment tab. Right click the equipment facing port and select Properties.
2. Change the Mode to Access, and Encap Type to Dot1Q
Note: From the Port MTU will automatically increase from 1514 to 1518 when you select OK
Create VPLS Service

1. Select Create Service VPLS from the Main Menu
2. From the General Tab, click the Select button to add the Customer.
Note (1) It is not necessary to add a service name but a service name is very helpful to have to
identify your service when performing searches
Note (2) To specify a Service ID uncheck the box beside Auto-Assign ID
3. Select the Components Tab, right-click on Site, select Create VPLS Site
4. Select the devices to be included within the VPLS service, Click OK
5. Click on the plus box to expand the Sites, right-click the Access Interface or Mesh SDP Bindings.
Select the Access Port (From the Port Tab) or SDP created earlier in this lab
Access
Ports:
- When adding the access port, to specify a vlan tag uncheck the box beside Auto-Assign ID
Mesh SDPs:
- When adding the Mesh SDPs (From the General Tab) after selecting the Tunnel Termination Site
you may Auto-Select the Tunnel or use the Select button to specify the SDP you created
- From the Return Tab you may Auto-Select the Return Tunnel or once again use the Select button to
specify the return tunnel you created
6. Once the service is populated with your access ports and mesh SDPs, select the Topology View button
to view the service you have created
Blank


Create VPLS
1

Create VPLS
3
4

Create VPLS

Create VPLS

End of Module
Configure VPLS

Lab 7
T1 Bundle Groups & IPipe


Configure Ports
Configure T1 Bundle Groups
Create an IPipe
Assign a Port to SAP
Assign an LSP to SDP

T1 Bundle Group Configuration

The following lines summarize the steps recommended to create a T1 Bundle Group:
1. Working from the Equipment view select the port(s) you would like to add to the Bundle. Right-click
and select Create Channel

2. From the States Tab change the Administrative State to Up, click OK
3. Click the plus button beside the port and right-click Channel, once again select Create Channel. From
the General tab specify the Local Channel ID. Continue working from the General tab, select IPCP as
the Encap Type
Note: The Local Channel ID is a numerical value (Use number 1)
Aside: You may select any number from 1-24 for T1, meaning we could create a channel for every
timeslot however in the backhaul application the entire T1 is used
4. Select the Channel Group tab. Add all time-slots, click OK
5. Continue working from the Equipment view. Click the plus button to expand the Channel Group, right-
click the Channel Group and select Turn Up

- Repeat steps 1 to 5 for each ASAP port to be included in the bundle
6. Right-click on Bundles select Create Bundle
7. Click next through each of the three Create Multilink Bundle Wizard steps. Click Finish.
Note: The simplest way to create Bundles is leave all fields of the Bundle Wizard blank and add the
ports we configured after a blank bundle has been created
8. Click the plus button beside Bundles. Right-click
the bundle you created in the previous step and select
Create
T1 Bundle Groups
Bundle
& IPipe
Members
9. Select all ports created in steps 1 to 5 that will be included as bundle members. Click Finish
Note: The Bundle will have a critical error, and will remain operationally down until it is included in the
IPipe. If you view the port state you will see that the port state is Link Up however until the MLPPP
connection is established the port will not become operationally up. The MLPPP connection is
established when the IPipe service is created and IP addresses are assigned to the SAP (T1 Bundle)
IPipe Configuration
Configure IPipe.

Technical Reference
See Alcatel-Lucent 5620 SAM, Release 7.0 User Guide 54.7 Creating a VLL
Ipipe service.
The following lab exercises will guide you through the steps necessary to configure traffic engineering in
the labs managed network.
1. Create a IPipe
2. Assign a Port to SAP
3. Assign an LSP to SDP
IPipe Creation
Follow your instructors instructions to create a IPipe.
The following lines summarize the steps recommended to create a IPipe for this lab:
1. Choose Create Service VLL Ipipe from the main menu

2. From the General Tab, click the Select button to add the Customer and specify a Service Name
3. From the Components Tab, right-click on Ipipe Service and choose Create Site
- Select both nodes that will be included in the Ipipe Service

4. Right-click the Access Interface and select the Access Port (From the Port Tab)
Note: Access Ports: When adding the access port, to specify a vlan tag uncheck the box beside AutoAssign ID
5. Select the Ipipe tab and add a CE IP Address. Click OK
6. Right-click on Spoke SDP Bindings and select Create Spoke SDP Binding
- When adding the Spoke SDPs (From the General Tab) after selecting the Tunnel Termination Site you
may Auto-Select the Tunnel or use the Select button to specify a SDP
- Because we require Peer CE IP Addresses add a return SDP from the appropriate site rather than
selecting a return path
7. Once the service is populated with your access port and spoke SDP, select the Topology View button to
view the service you have created

Note: Now that the IPipe has been created, return to the equipment view. Notice that the port errors have
cleared and if you view the port state, it has changed from Link Up to Up
Configure Ports

Configure Ports
3

Configure Ports

Configure Ports
6
7
8
9
Note Port State Link Up

Add the IPipe Service
2
1
3
4

Configure Ipipe

View Service

Note Port State Up

End of Lab

Lab 8
IES
Module Objectives
Upon completion of this module, you will be able to:

Describe the characteristics of an Internet Enhanced Service (IES)
List the steps in configuring an IES service

IES
IES Configuration
IES Creation
The following lines summarize the steps recommended to create a EPipe for this lab:
1. Choose Create Service IES from the main menu
2. From the General Tab, click the Select button to add the Customer
3. From the Components Tab, right-click on IES Service and choose Create Site
4. Click OK
5. Click the plus button to expand the site. Right-click on Access Interfaces select Create IES L3 Access
Interface
1.
From the General tab specify an interface name
2.
From the Port tab specify the terminating port
3.
From the Address tab specify the IP Address
6. Add the IES Access Interface to OSPF Right-click the newly created interface select Properties. Select
the Protocols tab. Click Add, select OSPF, click OK

7. Working in the OSPF Interface window and the General Tab, click the Select button to add the inteface to
area 0
8. Once the service is populated with your access interface, select the Topology View button to view the
service you have created
IES

IES
Create IES Service

IES
Create IES Service

IES
Create IES Service Access Interface

IES

IES

IES

IES
End of Module
IES

IES

IES
Lab 9
VPRN Services


Configure BGP Peering

Create a VPRN
Create a Service Site
Create a L3 Interface

VPRN Services
Configuration Notes
The following lab exercises will guide you through the steps necessary to configure VPRN and assign the service sites upon which the
service will terminate in the labs managed network.
1.
2.
3.
4.
Configure a BGP mesh among participating sites

Create a VPRN
Create a Service Site
Create an L3 Interface (SAP)
Enable BGP
Working from the Routing drop-down menu item. Click the plus button beside the router. Right-click on a Routing Instance and
choose Properties
2. Click on the Protocols Tab and check the appropriate protocol (BGP)
3. Continue working in the Routing Instance window. Click on the Routing Tab. Specify the Autonomous System value (65530)
6. Right-click BGP, select properties. From the VPN tab, check the VPN IPv4 box.
7. Repeat the above steps (BGP) for each router in your network
Note(1): If you do not specify the Autonomous System Value, BGP will stay Admin: UP, Status: DOWN
Note(2): By ticking the VPN IPv4 box, all BGP groups inherit this setting making creating BGP Groups easier
1.
Create BGP Group

Right click BGP from the list and select Create Group. From the General tab, assign a Group name (VPRN)
Continue working from the Peer Group window. Select the Behaviour tab, assign a Local Address (System IP)
3. Continue working from the Peer Group window. Select
the AS Properties tab, the Peer AS value (65530)
VPRN Services working from the Peer Group window. Select the VPN tab, ensure that within Family: VPN IPv4 and IPv4 are already
4. Continue
selected
Note: If the values for steps 2, 3, 4 will be inherited from the steps completed in Enable BGP if completed correctly
1.
2.
Create Peers
Right click Peer Group VPRN select Create Peer
Enter the Peer Address (System IP)
Note: The peer will stay in Critical status until the other end is completed
1.
2.
Creating the VPRN:

Choose Create Service VPRN from the main menu
From the General Tab, click the Select button to add the Customer
3. From the Components Tab, right-click on Sites and choose Create VPRN Site
4. Select the routers that will participate in the VPRN Service
5. Right-click each VPRN site and select Properties. Click the Routing Tab. Working from the General Tab:
1.
Select the Route Distinguisher Type (Type 0)
6. Still working in the Routing Tab, switch from the General Tab to the VRF Target Tab:
1.
Set the VRF Target Type (Typically for this lab Define Default)
2.
Select a Target Format (Typically for this lab AS)
3.
Enter the Target AS Value and Target Extended Community Value (The Suggest Value Button is useful)
7. Click on the Auto-Bind tab to configure the binding of the site to service tunnels
8. Click on the SNMP Community tab to configure the Community String
9. Click OK
10. Right-click Access Interface and select Create VPRN L3 Access Interface
1.
From the General Tab, specify the interface name
2.
From the Port Tab, specify the access port
3.
From the Address Tab, specify the interface address
1.
2.
Viewing the VPRN:

1.
2.
Choose Manage Services from the main menu.

Select your VPRN service from the list and click on the Topology View button
Blank Page

VPRN Services
Enable BGP
2
3

VPRN Services
Enable BGP

VPRN Services
Create BGP Group

VPRN Services
Create BGP Peers

VPRN Services
Creating the VPRN

VPRN Services
Creating the VPRN Add The Site(s)

VPRN Services
Creating the VPRN Route Distinguisher

VPRN Services
Creating the VPRN Route Target
2
3

VPRN Services
Creating the VPRN Auto-Bind

VPRN Services
Creating the VPRN Specify SNMP Community

VPRN Services
Creating the VPRN Access Interface
10

VPRN Services
Creating the VPRN - Access Interface

VPRN Services
End of Lab
VPRN Services

VPRN Services

VPRN Services
Last But One Page

1
@@PRODUCT
@@COURSENAME

@@COURSENAME - Page 1

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

SAM IP-MPLS Service Provisioning Lab Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SAM IP-MPLS Service Provisioning Lab Guide

Transféré par

Droits d'auteur :

Formats disponibles

SAM IP-MPLS Service

Provisioning Lab Guide

All Rights Reserved Alcatel-Lucent 2011

All rights reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011

All Rights Reserved Alcatel-Lucent 2011