null  null
Preface
Audience
This guide is for the networking professional managing the Cisco Metro Ethernet (ME) 3600X-24CX
switch, hereafter referred to as the switch. We assume that you are familiar with the concepts and
terminology of Ethernet and local area networking. If you are interested in more training and education
in these areas, learning opportunities including training courses, self-study options, seminars, and career
certifications programs are available on the Cisco Training & Events web page:
http://www.cisco.com/web/learning/index.html
Purpose
This guide provides an overview of software functionality that is specific to the Cisco ME 3600X
24CX Series Switch. It is not intended as a comprehensive guide to all of the software features that can
be run using the Cisco ME 3600X 24CX Series Switch, but only the software aspects that are specific to
this platform.
For information on general software features that are also available on other Cisco platforms, see the
Cisco IOS technology guide for that specific software feature.
For the latest documentation updates, see the release notes for this release.
Conventions
This publication uses these conventions to convey instructions and information:
Command descriptions use these conventions:
•
Commands and keywords are in boldface text.
•
Arguments for which you supply values are in italic.
•
Square brackets ([ ]) mean optional elements.
•
Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.
•
Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional
element.
Interactive examples use these conventions:
•
Terminal sessions and system displays are in screen font.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
1
Preface
•
Information you enter is in boldface screen font.
•
Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).
Notes and cautions use these conventions and symbols:
Note
Caution
Means reader take note. Notes contain helpful suggestions or references to materials not contained in
this manual.
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Related Publications
These documents provide complete information about the switch and are available from these Cisco.com
sites:
ME 3600X-24CX switch:
http://www.cisco.com/en/US/products/ps10956/tsd_products_support_series_home.html
Note
Before installing, configuring, or upgrading the switch, see these documents:
•
For initial configuration information, see the “Configuring the Switch with the CLI-Based Setup
Program” appendix in the hardware installation guide.
•
For upgrading information, see the “Downloading Software” section in the release notes.
•
Release Notes for the Cisco ME 3800X and ME 3600X Switch
Note
See the release notes on Cisco.com for the latest information.
•
Cisco ME 3800X and ME 3600X Switch Software Configuration Guide
•
Cisco ME 3800X and ME 3600X Switch Command Reference
•
Cisco ME 3800X and ME 3600X System Message Guide
•
Cisco ME 3600X-24CX Switch Hardware Installation Guide
•
Cisco ME 3600X-24CX Switch Getting Started Guide
•
Installation Note for the Cisco ME 3600X-24CX Switch Power Supply and Fan Modules
•
Regulatory Compliance and Safety Information for the Cisco ME 3600X-24CX Switche
•
Cisco Small Form-Factor Pluggable Modules Installation Notes
•
Cisco CWDM GBIC and CWDM SFP Installation Notes
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
•
Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2
OL-27620-01
Preface
•
Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix
•
Cisco CWDM SFP Transceiver Compatibility Matrix
•
Cisco Small Form-Factor Pluggable Modules Compatibility Matrix
•
Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed
and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free
service and Cisco currently supports RSS version 2.0.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3
Preface
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
4
OL-27620-01
CH A P T E R
2
Using the Command-Line Interface
This chapter describes the Cisco IOS command-line interface (CLI) and how to use it to configure your
Cisco ME 3600X-24CX switch. It contains these sections:
•
Understanding Command Modes, page 2-1
•
Understanding the Help System, page 2-3
•
Understanding Abbreviated Commands, page 2-3
•
Understanding no and default Forms of Commands, page 2-4
•
Understanding CLI Error Messages, page 2-4
•
Using Command History, page 2-4
•
Using Editing Features, page 2-6
•
Searching and Filtering Output of show and more Commands, page 2-8
•
Accessing the CLI, page 2-9
Understanding Command Modes
The Cisco IOS user interface is divided into many different modes. The commands available to you
depend on which mode you are currently in. Enter a question mark (?) at the system prompt to obtain a
list of commands available for each command mode.
When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a
limited subset of the commands are available in user EXEC mode. For example, most of the user EXEC
commands are one-time commands, such as show commands, which show the current configuration
status, and clear commands, which clear counters or interfaces. The user EXEC commands are not saved
when the switch reboots.
To have access to all commands, you must enter privileged EXEC mode. Normally, you must enter a
password to enter privileged EXEC mode. From this mode, you can enter any privileged EXEC
command or enter global configuration mode.
Using the configuration modes (global, interface, and line), you can make changes to the running
configuration. If you save the configuration, these commands are stored and used when the switch
reboots. To access the various configuration modes, you must start at global configuration mode. From
global configuration mode, you can enter interface configuration mode and line configuration mode.
Table 2-1 describes the main command modes, how to access each one, the prompt you see in that mode,
and how to exit the mode. The examples in the table use the hostname Switch.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
2-1
Chapter 2
Using the Command-Line Interface
Understanding Command Modes
Table 2-1
Command Mode Summary
Mode
Access Method
Prompt
User EXEC
Begin a session with Switch>
your switch.
Exit Method
About This Mode
Enter logout or
quit.
Use this mode to
•
Change terminal settings.
•
Perform basic tests.
•
Display system
information.
Privileged EXEC
While in user EXEC Switch#
mode, enter the
enable command.
Enter disable to
exit.
Global configuration
While in privileged
EXEC mode, enter
the configure
command.
Switch(config)#
To exit to privileged Use this mode to configure
EXEC mode, enter parameters that apply to the
exit or end, or press entire switch.
Ctrl-Z.
VLAN configuration
While in global
configuration mode,
enter the
vlan vlan-id
command.
Switch(config-vlan)#
Use this mode to configure
To exit to global
configuration mode, VLAN parameters.
enter the exit
command.
While in global
configuration mode,
enter the interface
command (with a
specific interface).
Switch(config-if)#
Interface
configuration
Use this mode to verify
commands that you have
entered. Use a password to
protect access to this mode.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
Use this mode to configure
To exit to global
configuration mode, parameters for the Ethernet
ports.
enter exit.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
For information about defining
interfaces, see the ‘Using
Interface Configuration Mode’
section in ME 3800x and ME
3600x Switches Software
Configuration Guide.
To configure multiple
interfaces with the same
parameters, see the
‘Configuring a Range of
Interfaces’ section in ME
3800x and ME 3600x Switches
Software Configuration Guide.
Line configuration
While in global
configuration mode,
specify a line with
the line vty or line
console command.
Switch(config-line)#
Use this mode to configure
To exit to global
configuration mode, parameters for the terminal
line.
enter exit.
To return to
privileged EXEC
mode, press Ctrl-Z
or enter end.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2-2
OL-27620-01
Chapter 2
Using the Command-Line Interface
Understanding the Help System
For more detailed information on the command modes, see the command reference guide for this release.
Understanding the Help System
You can enter a question mark (?) at the system prompt to display a list of commands available for each
command mode. You can also obtain a list of associated keywords and arguments for any command, as
shown in Table 2-2.
Table 2-2
Help Summary
Command
Purpose
help
Obtain a brief description of the help system in any command mode.
abbreviated-command-entry?
Obtain a list of commands that begin with a particular character string.
For example:
Switch# di?
dir disable disconnect
abbreviated-command-entry<Tab>
Complete a partial command name.
For example:
Switch# sh conf<tab>
Switch# show configuration
?
List all commands available for a particular command mode.
For example:
Switch> ?
command ?
List the associated keywords for a command.
For example:
Switch> show ?
command keyword ?
List the associated arguments for a keyword.
For example:
Switch(config)# cdp holdtime ?
<10-255> Length of time (in sec) that receiver must keep this packet
Understanding Abbreviated Commands
You need to enter only enough characters for the switch to recognize the command as unique.
This example shows how to enter the show configuration privileged EXEC command in an abbreviated
form:
Switch# show conf
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
2-3
Chapter 2
Using the Command-Line Interface
Understanding no and default Forms of Commands
Understanding no and default Forms of Commands
Almost every configuration command also has a no form. In general, use the no form to disable a feature
or function or reverse the action of a command. For example, the no shutdown interface configuration
command reverses the shutdown of an interface. Use the command without the keyword no to re-enable
a disabled feature or to enable a feature that is disabled by default.
Configuration commands can also have a default form. The default form of a command returns the
command setting to its default. Most commands are disabled by default, so the default form is the same
as the no form. However, some commands are enabled by default and have variables set to certain default
values. In these cases, the default command enables the command and sets variables to their default
values.
Understanding CLI Error Messages
Table 2-3 lists some error messages that you might encounter while using the CLI to configure your
switch.
Table 2-3
Common CLI Error Messages
Error Message
Meaning
How to Get Help
% Ambiguous command:
"show con"
You did not enter enough characters
for your switch to recognize the
command.
Re-enter the command followed by a question mark (?)
with a space between the command and the question
mark.
The possible keywords that you can enter with the
command appear.
You did not enter all the keywords or Re-enter the command followed by a question mark (?)
values required by this command.
with a space between the command and the question
mark.
% Incomplete command.
The possible keywords that you can enter with the
command appear.
% Invalid input detected
at ‘^’ marker.
You entered the command
incorrectly. The caret (^) marks the
point of the error.
Enter a question mark (?) to display all the commands
that are available in this command mode.
The possible keywords that you can enter with the
command appear.
Using Command History
The software provides a history or record of commands that you have entered. The command history
feature is particularly useful for recalling long or complex commands or entries, including access lists.
You can customize this feature to suit your needs as described in these sections:
•
Changing the Command History Buffer Size, page 2-5 (optional)
•
Recalling Commands, page 2-5 (optional)
•
Disabling the Command History Feature, page 2-5 (optional)
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2-4
OL-27620-01
Chapter 2
Using the Command-Line Interface
Using Command History
Changing the Command History Buffer Size
By default, the switch records ten command lines in its history buffer. You can alter this number for a
current terminal session or for all sessions on a particular line. These procedures are optional.
Beginning in privileged EXEC mode, enter this command to change the number of command lines that
the switch records during the current terminal session:
Switch# terminal history
[size number-of-lines]
The range is from 0 to 256.
Beginning in line configuration mode, enter this command to configure the number of command lines
the switch records for all sessions on a particular line:
Switch(config-line)# history
[size number-of-lines]
The range is from 0 to 256.
Recalling Commands
To recall commands from the history buffer, perform one of the actions listed in Table 2-4. These actions
are optional.
Table 2-4
Recalling Commands
Action1
Result
Press Ctrl-P or the up arrow key.
Recall commands in the history buffer, beginning with the most recent command.
Repeat the key sequence to recall successively older commands.
Press Ctrl-N or the down arrow key.
Return to more recent commands in the history buffer after recalling commands
with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively
more recent commands.
show history
While in privileged EXEC mode, list the last several commands that you just
entered. The number of commands that appear is controlled by the setting of the
terminal history global configuration command and the history line configuration
command.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Disabling the Command History Feature
The command history feature is automatically enabled. You can disable it for the current terminal session
or for the command line. These procedures are optional.
To disable the feature during the current terminal session, enter the terminal no history privileged
EXEC command.
To disable command history for the line, enter the no history line configuration command.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
2-5
Chapter 2
Using the Command-Line Interface
Using Editing Features
Using Editing Features
This section describes the editing features that can help you manipulate the command line.
•
Enabling and Disabling Editing Features, page 2-6 (optional)
•
Editing Commands through Keystrokes, page 2-6 (optional)
•
Editing Command Lines that Wrap, page 2-8 (optional)
Enabling and Disabling Editing Features
Although enhanced editing mode is automatically enabled, you can disable it, re-enable it, or configure
a specific line to have enhanced editing. These procedures are optional.
To globally disable enhanced editing mode, enter this command in line configuration mode:
Switch (config-line)# no editing
To re-enable the enhanced editing mode for the current terminal session, enter this command in
privileged EXEC mode:
Switch# terminal editing
To reconfigure a specific line to have enhanced editing mode, enter this command in line configuration
mode:
Switch(config-line)# editing
Editing Commands through Keystrokes
Table 2-5 shows the keystrokes that you need to edit command lines. These keystrokes are optional.
Table 2-5
Editing Commands through Keystrokes
Capability
Keystroke1
Move around the command line to
make changes or corrections.
Press Ctrl-B, or press the Move the cursor back one character.
left arrow key.
Purpose
Press Ctrl-F, or press the
right arrow key.
Move the cursor forward one character.
Press Ctrl-A.
Move the cursor to the beginning of the command line.
Press Ctrl-E.
Move the cursor to the end of the command line.
Press Esc B.
Move the cursor back one word.
Press Esc F.
Move the cursor forward one word.
Press Ctrl-T.
Transpose the character to the left of the cursor with the
character located at the cursor.
Recall commands from the buffer and Press Ctrl-Y.
paste them in the command line. The
switch provides a buffer with the last
ten items that you deleted.
Recall the most recent entry in the buffer.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2-6
OL-27620-01
Chapter 2
Using the Command-Line Interface
Using Editing Features
Table 2-5
Editing Commands through Keystrokes (continued)
Capability
Keystroke1
Purpose
Press Esc Y.
Recall the next buffer entry.
The buffer contains only the last 10 items that you have
deleted or cut. If you press Esc Y more than ten times, you
cycle to the first buffer entry.
Delete entries if you make a mistake Press the Delete or
or change your mind.
Backspace key.
Capitalize or lowercase words or
capitalize a set of letters.
Erase the character to the left of the cursor.
Press Ctrl-D.
Delete the character at the cursor.
Press Ctrl-K.
Delete all characters from the cursor to the end of the
command line.
Press Ctrl-U or Ctrl-X.
Delete all characters from the cursor to the beginning of
the command line.
Press Ctrl-W.
Delete the word to the left of the cursor.
Press Esc D.
Delete from the cursor to the end of the word.
Press Esc C.
Capitalize at the cursor.
Press Esc L.
Change the word at the cursor to lowercase.
Press Esc U.
Capitalize letters from the cursor to the end of the word.
Designate a particular keystroke as
Press Ctrl-V or Esc Q.
an executable command, perhaps as a
shortcut.
Scroll down a line or screen on
displays that are longer than the
terminal screen can display.
Note
Press the Return key.
Scroll down one line.
Press the Space bar.
Scroll down one screen.
Press Ctrl-L or Ctrl-R.
Redisplay the current command line.
The More prompt is used for
any output that has more
lines than can be displayed
on the terminal screen,
including show command
output. You can use the
Return and Space bar
keystrokes whenever you see
the More prompt.
Redisplay the current command line
if the switch suddenly sends a
message to your screen.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
2-7
Chapter 2
Using the Command-Line Interface
Searching and Filtering Output of show and more Commands
Editing Command Lines that Wrap
You can use a wraparound feature for commands that extend beyond a single line on the screen. When
the cursor reaches the right margin, the command line shifts ten spaces to the left. You cannot see the
first ten characters of the line, but you can scroll back and check the syntax at the beginning of the
command. The keystroke actions are optional.
To scroll back to the beginning of the command entry, press Ctrl-B or the left arrow key repeatedly. You
can also press Ctrl-A to immediately move to the beginning of the line.
Note
The arrow keys function only on ANSI-compatible terminals such as VT100s.
In this example, the access-list global configuration command entry extends beyond one line. When the
cursor first reaches the end of the line, the line is shifted ten spaces to the left and redisplayed. The dollar
sign ($) shows that the line has been scrolled to the left. Each time the cursor reaches the end of the line,
the line is again shifted ten spaces to the left.
Switch(config)#
Switch(config)#
Switch(config)#
Switch(config)#
access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1
$ 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.25
$t tcp 131.108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq
$108.2.5 255.255.255.0 131.108.1.20 255.255.255.0 eq 45
After you complete the entry, press Ctrl-A to check the complete syntax before pressing the Return key
to execute the command. The dollar sign ($) appears at the end of the line to show that the line has been
scrolled to the right:
Switch(config)# access-list 101 permit tcp 131.108.2.5 255.255.255.0 131.108.1$
The software assumes you have a terminal screen that is 80 columns wide. If you have a width other than
that, use the terminal width privileged EXEC command to set the width of your terminal.
Use line wrapping with the command history feature to recall and modify previous complex command
entries. For information about recalling previous command entries, see the “Editing Commands through
Keystrokes” section on page 2-6.
Searching and Filtering Output of show and more Commands
You can search and filter the output for show and more commands. This is useful when you need to sort
through large amounts of output or if you want to exclude output that you do not need to see. Using these
commands is optional.
To use this functionality, enter a show or more command followed by the pipe character (|), one of the
keywords begin, include, or exclude, and an expression that you want to search for or filter out:
command | {begin | include | exclude} regular-expression
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
are not displayed, but the lines that contain Output appear.
This example shows how to include in the output display only lines where the expression protocol
appears:
Switch# show interfaces | include protocol
Vlan1 is up, line protocol is up
Vlan10 is up, line protocol is down
GigabitEthernet0/1 is up, line protocol is down
GigabitEthernet0/2 is up, line protocol is up
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2-8
OL-27620-01
Chapter 2
Using the Command-Line Interface
Accessing the CLI
Accessing the CLI
You can access the CLI through a console connection, through Telnet, or by using the browser.
Accessing the CLI through a Console Connection or through Telnet
Before you can access the CLI, you must connect a terminal or PC to the switch console port and power
on the switch as described in the hardware installation guide that shipped with your switch. Then, to
understand the boot process and the options available for assigning IP information, see “Assigning the
Switch IP Address and Default Gateway.” chapter in the ME 3800x and ME 3600x Software
Configuration Guide.
If your switch is already configured, you can access the CLI through a local console connection or
through a remote Telnet session, but your switch must first be configured for this type of access. For
more information, see the “Setting a Telnet Password for a Terminal Line” section on page 9-6.
You can use one of these methods to establish a connection with the switch:
•
Connect the switch console port to a management station or dial-up modem. For information about
connecting to the console port, see the switch hardware installation guide.
•
Use any Telnet TCP/IP or encrypted Secure Shell (SSH) package from a remote management
station. The switch must have network connectivity with the Telnet or SSH client, and the switch
must have an enable secret password configured.
For information about configuring the switch for Telnet access, see the “Setting a Telnet Password
for a Terminal Line” in ME 3800x and ME 3600x Software Configuration Guide. The switch
supports up to 16 simultaneous Telnet sessions. Changes made by one Telnet user are reflected in
all other Telnet sessions.
For information about configuring the switch for SSH, see the “Configuring the Switch for Secure
Shell” section in ME 3800x and ME 3600x Software Configuration Guide. The switch supports up
to five simultaneous secure SSH sessions.
After you connect through the console port, through a Telnet session or through an SSH session, the
user EXEC prompt appears on the management station.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
2-9
Chapter 2
Using the Command-Line Interface
Accessing the CLI
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
2-10
OL-27620-01
CH A P T E R
3
Configuring T1/E1 Interfaces
This chapter provides information about configuring the T1/E1 interface module on the Cisco ME
3600X 24CX Series Switch. It includes the following sections:
•
Configuration Tasks, page 3-1
•
Configuration Examples, page 3-14
For information about managing your system images and configuration files, refer to the Cisco IOS
Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals
Command Reference publications.
For more information about the commands used in this chapter, refer to the Cisco IOS Command
Reference publication for your Cisco IOS software release.
For more information, see the Related Publications, page -2.
Configuration Tasks
This section describes how to configure the T1/E1 interface module for the Cisco ME 3600X
24CX Series Switch and includes information about verifying the configuration.
It includes the following topics:
•
Required Configuration Tasks, page 3-2
•
Optional Configurations, page 3-4
•
Saving the Configuration, page 3-6
Limitations
This section describes the software limitations that apply when configuring the T1/E1 interface module
on the Cisco ME 3600X 24CX Series Switch.
The following features are not currently supported on the T1/E1 interface module:
•
Serial interfaces—The Cisco ME 3600X 24CX Series Switch does not currently support serial
interfaces or features applied to serial interfaces. We recommend that you use a configuration with
CEM as a workaround.
•
Channel groups—The Cisco ME 3600X 24CX Series Switch does not currently support
channel-groups or features applied to channel-groups. We recommend that you use a configuration
with CEM as a workaround.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-1
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
•
Supported BERT patterns—Currently only the 2^11, 2^15, 2^20-O153, and 2^20-QRSS patterns are
supported.
Required Configuration Tasks
This section lists the required configuration steps to configure the T1/E1 interface module. Some of the
required configuration commands implement default values that might be appropriate for your network.
If the default value is correct for your network, then you do not need to configure the command.
•
Setting the Card Type, page 3-2
•
Configuring the Controller, page 3-3
•
Verifying Controller Configuration, page 3-4
•
Optional Configurations, page 3-4
Setting the Card Type
The interface module is not functional until the card type is set. Information about the interface module
is not indicated in the output of any show commands until the card type has been set. There is no default
card type.
Note
Mixing of interface types is not supported. All ports on the interface module must be of the same type.
To set the card type for the T1/E1 interface module, complete these steps:
Command
Purpose
Step 1
Router# configure terminal
Enters global configuration mode.
Step 2
Router(config)# card type {e1 | t1} 0 1
Sets the serial mode for the interface module:
•
t1—Specifies T1 connectivity of 1.536 Mbps.
B8ZS is the default line code for T1.
•
e1—Specifies a wide-area digital transmission
scheme used predominantly in Europe that
carries data at a rate of 1.984 Mbps in framed
mode and 2.048 Mbps in unframed E1 mode.
•
0—Specifies the card.
•
1—Specifies the card bay number.
Step 3
Router(config)# exit
Note
On doing no card type T1/E1 0 1, the peer box controller will not go down untill the device is reloaded
as prompted.
Exits configuration mode and returns to the EXEC
command interpreter prompt.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-2
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Configuring the Controller
To create the interfaces for the T1/E1 interface module, complete these steps:
Step 1
Command
Purpose
Router(config)# controller {t1 | e1}
card/number
Selects the controller to configure and enters controller
configuration mode.
•
t1—Specifies the T1 controller.
•
e1—Specifies the E1 controller.
•
card/number—Specifies the location of the
interface.
Note
Step 2
Step 3
Step 4
Router(config-controller)# clock source
{internal | line}
The card numbers supported are 0 or 1. The
number range for T1 is 0 to 15. The number range
for E1 is 0 to 31.
Sets the clock source.
Note
The clock source is set to internal if the opposite
end of the connection is set to line and the clock
source is set to line if the opposite end of the
connection is set to internal.
•
internal—Specifies that the internal clock source is
used.
•
line—Specifies that the network clock source is
used. This is the default for T1 and E1.
Router(config-controller)# linecode {ami | Selects the linecode type.
b8zs | hdb3}
• ami—Specifies Alternate Mark Inversion (AMI) as
the linecode type. Valid for T1 and E1 controllers.
For T1 Controllers:
•
b8zs—Specifies binary 8-zero substitution (B8ZS)
as the linecode type. Valid for T1 controller only.
This is the default for T1 lines.
•
hdb3—Specifies high-density binary 3 (HDB3) as
the linecode type. Valid for E1 controller only. This
is the default for E1 lines.
Selects the framing type.
Router(config-controller)# framing {sf |
esf}
•
sf—Specifies Super Frame as the T1 frame type.
•
esf—Specifies Extended Super Frame as the T1
frame type. This is the default for E1.
•
crc4—Specifies CRC4 as the E1 frame type. This is
the default for E1.
•
no-crc4—Specifies no CRC4 as the E1 frame type.
For E1 Controllers:
Router(config-controller)# framing {crc4 |
no-crc4}
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-3
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Step 5
Command
Purpose
cablelength {long | short}
To fine-tune the pulse of a signal at the receiver for an E1
cable on a Cisco ME3600X-24CX-M, use the
cablelength command in controller configuration mode.
Example:
Router(config-controller)#
cablelength long
Step 6
exit
Exits configuration mode and returns to the EXEC
command interpreter prompt.
Example:
Router(config)# exit
Verifying Controller Configuration
Use the show controllers command to verify the controller configuration:
Router# show controllers e1 0/11
E1 0/11 is up.
Applique type is Channelized E1 - balanced
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Data in current interval (230 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Total Data (last 24 hours)
136 Line Code Violations, 63 Path Code Violations,
0 Slip Secs, 6 Fr Loss Secs, 4 Line Err Secs, 0 Degraded Mins,
7 Errored Secs, 1 Bursty Err Secs, 6 Severely Err Secs, 458 Unavail Secs
2 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Optional Configurations
There are several standard, but optional, configurations that might be necessary to complete the
configuration of your Ethernet interface module.
•
Configuring Framing, page 3-5
•
Saving the Configuration, page 3-6
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-4
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Configuring Framing
Framing is used to synchronize data transmission on the line. Framing allows the hardware to determine
when each packet starts and ends. To configure framing, use the following commands.
Command
Purpose
Router# configure terminal
Enters global configuration mode.
Router(config)# controller {t1 | e1} card/number Selects the controller to configure.
•
t1—Specifies the T1 controller.
•
e1—Specifies the E1 controller.
•
card/number—Specifies the location of the
controller.
Note
For T1 controllers
The card is always 0.
Set the framing on the interface.
Router(config-controller)# framing {sf | esf}
•
sf—Specifies Super Frame as the T1 frame
type.
•
esf—Specifies Extended Super Frame as the
T1 frame type. This is the default. for T1.
•
crc4—Specifies CRC4 frame as the E1 frame
type. This is the default for E1.
•
no-crc4—Specifies no CRC4 as the E1 frame
type.
For E1 controllers
Router(config-controller)# framing {crc4 |
no-crc4}
Verifying Framing Configuration
Use the show controllers command to verify the framing configuration:
Router# show controllers t1 0/11
T1 0/11 is up.
Applique type is Channelized T1 - balanced
Cablelength is long gain36 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
Data in current interval (740 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Total Data (last 24 hours)
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-5
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Saving the Configuration
To save your running configuration to nonvolatile random-access memory (NVRAM), use the following
command in privileged EXEC configuration mode:
Command
Purpose
Router# copy running-config startup-config
Writes the new configuration to NVRAM.
For information about managing your system images and configuration files, refer to the Cisco IOS
Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals
Command Reference publications.
Troubleshooting E1 and T1 Controllers
You can use the following methods to troubleshoot the E1 and T1 controllers using Cisco IOS software:
•
Setting Loopbacks
•
Run Bit Error Rate Test
Setting Loopbacks
The following sections describe how to set loopbacks:
•
Setting a Loopback on the E1 Controller, page 3-6
•
Setting a Loopback on the T1 Controller, page 3-7
Setting a Loopback on the E1 Controller
To set a loopback on the E1 controller, perform the first task followed by any of the following tasks
beginning in global configuration mode:
Task
Command
Select the E1 controller and enter controller
configuration mode.
controller e1 card/number
Note
The card is always 0.
Set a diagnostic loopback on the E1 line.
loopback diag
Set a network payload loopback on the E1
line.
loopback network {line | payload}
Exit configuration mode when you have
finished configuring the controller.
end
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-6
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Setting a Loopback on the T1 Controller
To set a loopback on the T1 controller, perform the first task followed by any of the following tasks
beginning in global configuration mode:
Task
Command
Select the T1 controller and enter controller
configuration mode.
controller t1 card/number
Set a diagnostic loopback on the T1 line.
loopback diag
Set a local loopback on the T1 line. You can
select to loopback the line or the payload.
loopback local {line | payload}
Note
The card is always 0.
loopback remote iboc
Set a remote loopback on the T1 line. This
loopback setting will loopback the far end at
line or payload, using IBOC (in band
bit-orientated code) or the ESF loopback
codes to communicate the request to the far
end.
Exit configuration mode when you have
finished configuring the controller.
Note
end
To remove a loopback, use the no loopback command.
Table 3-1
Loopback Descriptions
Loopback
Description
loopback diag
Loops the outgoing transmit signal back to the receive signal. This
is done using the diagnostic loopback feature in the interface
module’s PMC framer. The interface module transmits AIS in this
mode. Set the clock source command to internal for this loopback
mode.
loopback local
Loops the incoming receive signal back out the transmitter. You can
specify whether to use the line or payload.
local line
The incoming signal is looped back in the interface module using
the framer’s line loopback mode. The framer does not re-clock or
re-frame the incoming data. All incoming data is receive by the
interface module’s driver.
local payload
The incoming signal is looped back in the interface module using
the framer’s payload loopback mode. The framer re-clocks and
re-frames the incoming data before sending it back out to the
network. When in payload loopback, an all 1s data pattern is
received by the local HDLC receiver, and the clock source is
automatically set to line (overriding the clock source command).
When the payload loopback is ended, the clock source returns to the
last setting selected by the clock source command.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-7
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
Table 3-1
Loopback Descriptions
Loopback
Description
loopback remote
iboc
Attempts to set the far-end T1 interface into line loopback. This
command sends an in-band bit-oriented code to the far-end to cause
it to go into line loopback. This command is available when using
ESF or SF framing mode.
network line
The incoming signal is looped back in the interface module using
the framer's line loopback mode. The framer does not re-clock or
re-frame the incoming data. All incoming data is received by the
interface module's driver.
network payload
The incoming signal is looped back in the interface module using
the framer’s payload loopback mode. The framer re-clocks and
re-frames the incoming data before sending it back out to the
network. When in payload loopback, an all 1s data pattern is
received by the local HDLC receiver, and the clock source is
automatically set to line (overriding the clock source command).
When the payload loopback is ended, the clock source returns to the
last setting selected by the clock source command.
Run Bit Error Rate Test
Bit error rate testing (BERT) is supported on each of the E1 or T1 links. The BERT testing is done only
over a framed E1 or T1 signal and can be run only on one port at a time.
The interface modules contain onboard BERT circuitry. With this, the interface module software can
send and detect a programmable pattern that is compliant with CCITT/ITU O.151, O.152, and O.153
pseudo-random and repetitive test patterns. BERTs allow you to test cables and signal problems in the
field.
When running a BER test, your system expects to receive the same pattern that it is transmitting. To help
ensure this, two common options are available:
•
Use a loopback somewhere in the link or network
•
Configure remote testing equipment to transmit the same BER test pattern at the same time
To run a BERT on an E1 or T1 controller, perform the following optional tasks beginning in global
configuration mode:
Task
Command
Select the E1 or T1 controller and enter
controller configuration mode.
controller {e1 | t1} card/number
Specify the BERT pattern for the E1 or T1
line and the duration of the test in minutes
(1 to 1440 minutes).
Note
Note
The card is always 0.
bert pattern {0s | 1s | 2^11 | 2^15 | 2^20-O153 |
2^20-QRSS | 2^23 | alt-0-1} interval minutes
2^23 and 2^20-O153 patterns are not
supported.
Exit configuration mode when you have
finished configuring the controller.
end
View the BERT results.
show controllers {e1 | t1} card/number
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-8
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuration Tasks
The following keywords list different BERT keywords and their descriptions.
Caution
Currently 2^23, and 2^20-O153 patterns are not supported.
Table 3-2
BERT Pattern Descriptions
Keyword
Description
0s
Repeating pattern of zeros (...000...).
1s
Repeating pattern of ones (...111...).
2^11
Pseudo-random test pattern that is 2,048 bits in length.
2^15
Pseudo-random O.151 test pattern that is 32,768 bits in length.
2^20-O153
Pseudo-random O.153 test pattern that is 1,048,575 bits in
length.
2^20-QRSS
Pseudo-random QRSS O.151 test pattern that is 1,048,575 bits
in length.
2^23
Pseudo-random 0.151 test pattern that is 8,388,607 bits in
length.
alt-0-1
Repeating alternating pattern of zeros and ones (...01010...).
Both the total number of error bits received and the total number of bits received are available for
analysis. You can select the testing period from 1 minute to 24 hours, and you can also retrieve the error
statistics anytime during the BER test.
Note
To terminate a BER test during the specified test period, use the no bert command.
You can view the results of a BER test at the following times:
•
After you terminate the test using the no bert command
•
After the test runs completely
•
Anytime during the test (in real time)
Monitor and Maintain the T1/E1 Interface Module
After configuring the new interface, you can monitor the status and maintain the interface module by
using show commands. To display the status of any interface, complete any of the following tasks in
EXEC mode:
Task
Command
Display the status of the E1 or T1 controller. show controllers {e1 | t1} [card/number] [brief]
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-9
Chapter 3
Configuring T1/E1 Interfaces
Configuring CEM
Configuring CEM
This section provides information about how to configure CEM. CEM provides a bridge between a
time-division multiplexing (TDM) network and a packet network, such as Multiprotocol Label
Switching (MPLS). The router encapsulates the TDM data in the MPLS packets and sends the data over
a CEM pseudowire to the remote provider edge (PE) router. Thus, function as a physical communication
link across the packet network.
The following sections describe how to configure CEM:
Note
•
Configuring a CEM Group, page 3-10
•
Using CEM Classes, page 3-11
•
Configuring CEM Parameters, page 3-12
CEM is used as an element in configuring pseudowires including Structure-Agnostic TDM over Packet
(SAToP) and Circuit Emulation Service over Packet-Switched Network (CESoPSN). For more
information about configuring pseudowires, see Chapter 6, “Configuring Pseudowire.”
Configuring a CEM Group
The following section describes how to configure a CEM group on the Cisco ME 3600X
24CX Series Switch.
SUMMARY STEPS
Step 1
1.
enable
2.
configure terminal
3.
controller {t1 | e1} card/number
4.
cem-group group-number {unframed | timeslots timeslot}
5.
end
Command
Purpose
enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Step 3
controller {t1 | e1}
Enter your password if prompted.
Enters global configuration mode.
card/number
Enters controller configuration mode.
•Use the card, number arguments to specify the card number and bay
number to be configured.
Note
The card number is always 0.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-10
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuring CEM
Step 4
Command
Purpose
cem-group group-number {unframed |
timeslots timeslot}
Creates a circuit emulation channel from one or more time slots of a T1
or E1 line.
•
The group-number keyword identifies the channel number to be
used for this channel. For T1 ports, the range is 0 to 23. For E1 ports,
the range is 0 to 30.
•
Use the unframed keyword to specify that a single CEM channel is
being created including all time slots and the framing structure of the
line.
•
Use the timeslots keyword and the timeslot argument to specify the
time slots to be included in the CEM channel. The list of time slots
may include commas and hyphens with no spaces between the
numbers.
Note
Step 5
The speed keyword is not currently supported.
Exits controller configuration mode and returns to privileged EXEC
mode.
end
Using CEM Classes
A CEM class allows you to create a single configuration template for multiple CEM pseudowires. Follow
these steps to configure a CEM class:
Note
The CEM parameters at the local and remote ends of a CEM circuit must match; otherwise, the
pseudowire between the local and remote PE routers will not come up.
Note
You cannot apply a CEM class to other pseudowire types such as ATM over MPLS.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
class cem classname
4.
payload-size size
5.
dejitter-buffer size
6.
idle-pattern {pattern | length pattern1 [pattern2]}
7.
exit
8.
interface cem card/number
9.
no ip address
10. cem card/number
11. cem group-number
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-11
Chapter 3
Configuring T1/E1 Interfaces
Configuring CEM
12. xconnect peer-ip-address vc-id {encapsulation {l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name] [sequencing {transmit | receive | both}]
13. exit
14. exit
Command
Purpose
Step 1
enable
Enables privileged EXEC mode.
Step 2
configure terminal
Enters global configuration mode.
Step 3
Router(config)# class cem
mycemclass
Creates a new CEM class
Step 4
payload-size size
dejitter-buffer size
idle-pattern {pattern
Enter the configuration commands common to the CEM class. This
example specifies a sample rate, payload size, dejitter buffer, and idle
pattern.
•
| length
pattern1 [pattern2]}
Enter your password if prompted.
Step 5
Router(config-cem-class)# exit
Returns to the config prompt.
Step 6
Router(config)# interface cem 0/1
Router(config-if)# no ip address
Router(config-if)# cem 0
Router(config-if-cem)# xconnect
10.10.10.10 200 encapsulation mpls
Configure the CEM interface that you want to use for the new CEM class.
Step 7
Router(config-if-cem)# exit
Router(config-if)#
Exits the CEM interface.
Step 8
exit
Exits configuration mode.
Note
The use of the xconnect command can vary depending on the type
of pseudowire you are configuring.
Configuring CEM Parameters
The following sections describe the parameters you can configure for CEM circuits.
Note
•
Configuring Payload Size (Optional), page 3-12
•
Setting the Dejitter Buffer Size, page 3-13
•
Setting an Idle Pattern (Optional), page 3-13
•
Enabling Dummy Mode, page 3-13
•
Setting a Dummy Pattern, page 3-13
•
Shutting Down a CEM Channel, page 3-13
The CEM parameters at the local and remote ends of a CEM circuit must match; otherwise, the
pseudowire between the local and remote PE routers will not come up.
Configuring Payload Size (Optional)
To specify the number of bytes encapsulated into a single IP packet, use the pay-load size command. The
size argument specifies the number of bytes in the payload of each packet. The range is from 32 to 1312
bytes.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-12
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuring CEM
Default payload sizes for an unstructured CEM channel are as follows:
•
E1 = 256 bytes
•
T1 = 192 bytes
•
DS0 = 32 bytes
Default payload sizes for a structured CEM channel depend on the number of time slots that constitute
the channel. Payload size (L in bytes), number of time slots (N), and packetization delay (D in
milliseconds) have the following relationship: L = 8*N*D. The default payload size is selected in such
a way that the packetization delay is always 1 millisecond. For example, a structured CEM channel of
16xDS0 has a default payload size of 128 bytes.
The payload size must be an integer of the multiple of the number of time slots for structured CEM
channels.
Setting the Dejitter Buffer Size
To specify the size of the dejitter buffer used to compensate for the network filter, use the dejitter-buffer
size command. The configured dejitter buffer size is converted from milliseconds to packets and rounded
up to the next integral number of packets. Use the size argument to specify the size of the buffer, in
milliseconds. The range is from 1 to 500 ms; the default is 5 ms.
Setting an Idle Pattern (Optional)
To specify an idle pattern, use the [no] idle-pattern pattern1 command. The payload of each lost
CESoPSN data packet must be replaced with the equivalent amount of the replacement data. The range
for pattern is from 0x0 to 0xFF; the default idle pattern is 0xFF.
Enabling Dummy Mode
Dummy mode enables a bit pattern for filling in for lost or corrupted frames. To enable dummy mode,
use the dummy-mode [last-frame | user-defined] command. The default is last-frame. The following
is an example:
Router(config-cem)# dummy-mode last-frame
Setting a Dummy Pattern
If dummy mode is set to user-defined, you can use the dummy-pattern pattern command to configure
the dummy pattern. The range for pattern is from 0x0 to 0xFF. The default dummy pattern is 0xFF.
The following is an example:
Router(config-cem)# dummy-pattern 0x55
Shutting Down a CEM Channel
To shut down a CEM channel, use the shutdown command in CEM configuration mode. The shutdown
command is supported only under CEM mode and not under the CEM class.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-13
Chapter 3
Configuring T1/E1 Interfaces
Configuration Examples
Configuration Examples
This section includes the following configuration examples:
•
Framing and Encapsulation Configuration Example, page 3-14
•
CRC Configuration Example, page 3-14
•
Facility Data Link Configuration Example, page 3-15
•
Invert Data on the T1/E1 Interface Example, page 3-15
Framing and Encapsulation Configuration Example
The following example sets the framing and encapsulation for the controller and interface:
! Specify the controller and enter controller configuration mode
!
Router(config)# controller t1 0/1
! Specify the framing method
!
Router(config-controller)# framing esf
!
! Exit controller configuration mode and return to global configuration mode
!
Router(config-controller)# exit
!
! Specify the interface and enter interface configuration mode
!
Router(config)# interface serial 0/1
!
! Specify the encapsulation protocol
!
Router(config-if)# encapsulation ppp
!
! Exit interface configuration mode
!
Router(config-if)# exit
!
! Exit global configuration mode
!
Router(config)# exit
CRC Configuration Example
The following example sets the CRC size for the interface:
! Specify the interface and enter interface configuration mode
!
Router(config)# interface serial 0/1
!
! Specify the CRC size
!
Router(config-if)# crc 32
!
! Exit interface configuration mode and return to global configuration mode
!
Router(config-if)# exit
!
! Exit global configuration mode
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-14
OL-27620-01
Chapter 3
Configuring T1/E1 Interfaces
Configuration Examples
!
Router(config)# exit
Facility Data Link Configuration Example
The following example configures Facility Data Link:
! Specify the controller and enter controller configuration mode
!
Router(config)# controller t1 0/1
!
! Specify the FDL specification
!
Router(config-controller)# fdl ansi
!
! Exit controller configuration mode and return to global configuration mode
!
Router(config-controller)# exit
!
! Exit global configuration mode
!
Router(config)# exit
Invert Data on the T1/E1 Interface Example
The following example inverts the data on the serial interface:
! Enter global configuration mode
!
Router# configure terminal
!
! Specify the serial interface and enter interface configuration mode
!
Router(config)# interface serial 0/1
!
! Configure invert data
!
Router(config-if)# invert data
!
! Exit interface configuration mode and return to global configuration mode
!
Router(config-if)# exit
!
! Exit global configuration mode
!
Router(config)# exit
CEM Configuration Example
The following example shows how to add a T1 interface to a CEM group as a part of a SAToP pseudowire
configuration. For more information about how to configure pseudowires, see Chapter 6, “Configuring
Pseudowire.”
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
3-15
Chapter 3
Configuring T1/E1 Interfaces
Configuration Examples
Note
This section displays a partial configuration intended to demonstrate a specific feature.
controller T1 0/1
framing unframed
clock source internal
linecode b8zs
cablelength short 110
cem-group 0 unframed
interface CEM0/0
no ip address
cem 0
xconnect 18.1.1.1 1000 encapsulation mpls
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
3-16
OL-27620-01
CH A P T E R
4
Configuring BFD Offload
Bidirectional Forwarding Detection (BFD) offload support provides the functionality to offload a BFD
session to the field-programmable gate array (FPGA). BFD is a forwarding path failure detection
protocol and reduces the overall network convergence time by sending rapid failure detection packets
(messages) to the routing protocols for recalculating the routing table. Previously the performance of
BFD was restricted to the capabilities of CPU and IOS on the RP of the switch. Effective failure
detection requires BFD to run at high frequencies (using aggressive timers as low as 50ms), which was
not possible because of CPU and IOS restrictions.
For information on configuring BFD see Configuring BFD section of ME 3800x and ME 3600x Switches
Software Configuration Guide.
Note
On the Cisco ME 3600X-24CX, BFD session will be supported only on the FPGA, BFD sessions on the
RP are not supported.
Restrictions for BFD Offload Support
•
Only BFD version 1 is supported.
•
Only FPGA offloaded BFD sessions are supported, BFD sessions on RP are not supported on ME
3600X-24CX-M.
•
The switch supports BFD only in Asynchronous mode or no echo mode.
•
The switch supports 511 asynchronous BFD sessions.
•
BFD hardware offload is supported for IPv4 sessions with non-echo mode only.
•
BFD offload is supported on port-channel interfaces.
•
BFD offload is supported only for the ethernet interface.
•
BFD offload is not supported for IPv6 BFD sessions.
•
BFD offload is not supported for BFD with TE/FRR
Configuring BFD Offload Support
The BFD offload functionality is enabled by default. You can configure BFD hardware offload on the
route processor.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
4-1
Chapter 4
Configuring BFD Offload
Verifying BFD Offload Support
You must ensure that the Session host is showing as Hardware. Use the show bfd neighbors detail to
verify the configuration of BFD Offload. Hardware BFD sessions have a LD of 1-511.
Note
Sometimes if BFD session is brought up after the registered protocol is up the session may come up in
Software. Shutdown the interface and apply the BFD config to ensure that session comes back up in
Hardware.
Switch# show bfd neighbours details
NeighAddr
LD/RD
RH/RS
State
34.34.34.3
1/11
Up
Up
Session state is UP and not using echo function.
Session Host: Hardware
OurAddr: 34.34.34.1
Handle: 295
Local Diag: 0, Demand mode: 0, Poll bit: 0
MinTxInt: 50000, MinRxInt: 50000, Multiplier: 3
Received MinRxInt: 100000, Received Multiplier: 3
Holddown (hits): 0(0), Hello (hits): 100(0)
Rx Count: 574748
Tx Count: 673965
Elapsed time watermarks: 0 0 (last: 0)
Registered protocols: ISIS CEF OSPF
Uptime: 14:22:46
Last packet: Version: 1
- Diagnostic: 0
State bit: Up
- Demand bit: 0
Poll bit: 0
- Final bit: 0
C bit: 0
Multiplier: 3
- Length: 24
My Discr.: 11
- Your Discr.: 294
Min tx interval: 100000
- Min rx interval: 100000
Min Echo interval: 0 ould
Int
Vl3336
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
4-2
OL-27620-01
CH A P T E R
5
Configuring Clocking and Timing
Clock synchronization is important for a variety of applications, including synchronization of radio cell
towers. While legacy TDM protocols incorporate timing features, packet-switched networks such as
Ethernet do not natively include these features. The Cisco ME 3600X 24CX Series Switch supports
legacy TDM technologies while supporting a variety of technologies that distribute clocking information
over packet-switched networks.
The following sections describe the clocking and timing features available on the Cisco ME 3600X
24CX Series Switch.
•
Network Clocking Overview
•
Configuring Clocking and Timing
•
Clocking Sample Configurations
Network Clocking Overview
Clocking is typically distributed from the core network outward to the BTS or Node B at the network
edge. The Cisco ME 3600X 24CX Series Switch receives and transmits clocking information using any
of the following ports:
•
T1/E1
•
GigabitEthernet
•
BITS/SYNC port
•
1PPS
•
10Mhz
•
ToD
The Cisco ME 3600X 24CX Series Switch supports the following clocking types:
•
Precision Timing Protocol (PTP)
•
Synchronous Ethernet
Precision Timing Protocol (PTP)
The Cisco ME 3600X 24CX Series Switch supports the Precision Time Protocol (PTP) as defined by the
IEEE 1588-2008 standard. PTP provides for accurate time synchronization on over packet-switched
networks. Nodes within a PTP network can act in one of the following roles:
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-1
Chapter 5
Configuring Clocking and Timing
Network Clocking Overview
•
Ordinary clock—An ordinary clock is a 1588 clock with a single PTP port that can serve in one of
the following roles:
– Master mode—Distributes timing information over the network to one or more slave clocks,
thus allowing the slave to synchronize its clock to the master.
– Slave mode—Synchronizes its clock to a master clock. You can enable slave clocking on up to
two interfaces simultaneously in order to connect to two different master clocks.
•
Note
Boundary clock—The device participates in selecting the best master clock and can act as the master
clock if no better clocks are detected.
The Cisco ME 3600X 24CX Series Switch does not currently act as a transparent clock.
The 1588-2008 standard defines other clocking devices that are not described here.
Note
When a shut/no shut is carried on the loopback interface, the PTP port is deleted and recreated. This
causes the PTP counters to reset.
Clock Synchronization
PTP master devices periodically launch an exchange of messages with slave devices to help each slave
clock recompute the offset between its clock and the master clock. Periodic clock synchronization
mitigates any drift between the master and slave clocks.
Synchronous Ethernet
Synchronous Ethernet is a timing technology that allows the Cisco ME 3600X 24CX Series Switch
switch to transport frequency information over Ethernet. Because frequency is embedded in Ethernet
packets, synchronous Ethernet must be supported by each network element in the synchronization path.
Synchronous Ethernet is defined in the ITU-T G.781, G.8261, G.8262, and G.8264, Telcordia
GR-253-CORE, and Telcordia GR-1244-CORE standards.
Synchronous Ethernet ESMC and SSM
The Cisco ME 3600X 24CX Series Switch supports Ethernet Synchronization Message Channel
(ESMC) and Synchronization Status Message (SSM) to provide clock synchronization on Synchronous
Ethernet. For more information about Ethernet ESMC and SSM, see Chapter 5, “Configuring PTP
Clocking.”
Note
SSM is only supported on BITS interface.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-2
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Configuring Clocking and Timing
The Cisco ME 3600X 24CX Series Switch switch supports the following network clocking types:
•
Precision Time Protocol (PTP)—Clocking and clock recovery based on the IEEE 1588-2008
standard; allows the Cisco ME 3600X 24CX Series Switch switch to receive clocking from another
PTP-enabled device or provide clocking to a PTP-enabled device. To configure PTP clocking, see
Configuring PTP Clocking.
•
Synchronous Ethernet—Allows the network to transport frequency and time information over
Ethernet. To configure synchronous Ethernet, see Configuring Synchronous Ethernet.
•
Verifying Clock Settings—To verify a clocking configuration, see Verifying Clock-Related Settings.
Configuring PTP Clocking
This section describes how to configure PTP-based clocking on the Cisco ME 3600X
24CX Series Switch.
•
Prerequisites for Configuring PTP Clocking, page 5-3
•
Configuring an Ordinary Clock, page 5-3
•
Configuring a Boundary Clock, page 5-7
Note
The settings shown in this section are an example only; you must determine the appropriate PTP settings
based upon your network clocking design.
Note
The configuration sections describing the 1PPS and 10Mhz timing ports only apply to the Cisco ME
3600X-24CX switch.
Prerequisites for Configuring PTP Clocking
To enable PTP v2 Ordinary Slave Clock, one of the following base licenses must be installed on the
switch:
•
Metro IP Access
•
Advanced Metro IP Access
An additional 1588 feature license is required to enable the Ordinary master clock and boundary clock
functionality.
You must reload the switch to activate the license.
Configuring an Ordinary Clock
The followign sections describe how to cofigure the switch as an ordinary clock.
•
Configuring a Master Ordinary Clock, page 5-4
•
Configuring a Slave Ordinary Clock, page 5-5
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-3
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Configuring a Master Ordinary Clock
Enter the following commands to configure the switch to act as a master ordinary clock:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
ptp clock {ordinary | boundary |
e2e-transparent} domain
domain-number [hybrid]
Configures the PTP clock. You can create the following clock types:
Example:
•Boundary—Participates in selecting the best master clock and can act as
the master clock if no better clocks are detected.
Switch(config)# ptp clock ordinary
domain 0
Step 4
priority1 priorityvalue
Example:
Switch(config-ptp-clk)# priority1
128
Step 5
priority2 priorityvalue
Example:
Switch(config-ptp-clk)# priority2
128
•Ordinary—A 1588 clock with a single PTP port that can operate in
Master or Slave mode.
Note
The transparent clock and hybrid mode are not supported on the
Cisco ME 3600X 24CX switch.
Sets the preference level for a clock. Slave devices use the priority1 value
when selecting a master clock: a lower priority1 value indicates a
preferred clock. The priority1 value is considered above all other clock
attributes.
Valid values are from 0-255. The default value is 128.
Sets a secondary preference level for a clock. Slave devices use the
priority2 value when selecting a master clock: a lower priority2 value
indicates a preferred clock. The priority2 value is considered only when
the router is unable to use priority1 and other clock attributes to select a
clock.
Valid values are from 0-255. The default value is 128.
Step 6
clock-port port-name {master | slave}
Sets the clock port to PTP master or slave mode; in master mode, the port
exchanges timing packets with PTP slave devices.
Example:
Switch(config-ptp-clk)# clock-port
Master master
Router(config-ptp-port)#
Step 7
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Sets port transport parameters.
The negotiation keyword configures the router to discover a PTP master
clock from all available PTP clock sources.
Note
PTP redundancy is supported only on unicast negotiation mode.
Example:
Switch(config-ptp-port)# transport
ipv4 unicast interface loopback 0
negotiation
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-4
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Step 8
Command
Purpose
clock-destination destination-address
Specifies the IP address of a clock destination when the router is in PTP
master mode.
Example:
•
The destination-address parameter is required in master mode.
Switch(config-ptp-port)#
•
The destination-address parameter is the loopback address of the
slave clock.
clock-destination 8.8.8.1
Note
Step 9
sync interval value
The clock-destination command is not applicable in unicast
negotiation mode.
Specifies the sync interval.
Example:
Switch(config-ptp-port)# sync
interval 1
Step 10
announce timeout value
Specifies the number of PTP announcement intervals before the session
times out. Valid values are 1-10.
Example:
Switch(config-ptp-port)# announce
timeout 8
Step 11
exit
Exits configuration mode.
Example:
Switch(config)# exit
Configuring a Slave Ordinary Clock
Follow these steps to configure the switch to act as a slave ordinary clock.
Command
Purpose
Step 1
Switch# configure terminal
Enter configuration mode.
Step 2
ptp clock {ordinary | boundary |
e2e-transparent} domain
domain-number [hybrid]
Configures the PTP clock. You can create the following
clock types:
Example:
•
Ordinary—A 1588 clock with a single PTP port that
can operate in Master or Slave mode.
•
Boundary—Participates in selecting the best master
clock and can act as the master clock if no better clocks
are detected.
Switch(config)# ptp clock ordinary
domain 0
Note
Step 3
priority1 priorityvalue
Example:
Switch(config-ptp-clk)# priority1
128
The transparent clock and hybrid mode are not
supported on the Cisco ME 3600X 24CX switch.
Sets the preference level for a clock. Slave devices use the
priority1 value when selecting a master clock: a lower
priority1 value indicates a preferred clock. The priority1
value is considered above all other clock attributes.
Valid values are from 0-255. The default value is 128.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-5
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Step 4
Command
Purpose
priority2 priorityvalue
Sets a secondary preference level for a clock. Slave devices
use the priority2 value when selecting a master clock: a
lower priority2 value indicates a preferred clock. The
priority2 value is considered only when the router is unable
to use priority1 and other clock attributes to select a clock.
Example:
Switch(config-ptp-clk)# priority2
128
Valid values are from 0-255. The default value is 128.
Step 5
clock-port port-name {master | slave}
Example:
Sets the clock port to PTP master or slave mode; in slave
mode, the port exchanges timing packets with a PTP master
clock.
Switch(config-ptp-clk)# clock-port
Slave slave
Step 6
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Sets port transport parameters.
The negotiation keyword configures the router to discover
a PTP master clock from all available PTP clock sources.
Example:
Switch(config-ptp-port)# transport
ipv4 unicast interface loopback 0
negotiation
Step 7
clock-source source-address
Specifies the address of a PTP master clock.
Example:
Switch(config-ptp-port)#
clock-source 8.8.8.1
Step 8
sync interval value
Specifies the sync interval.
Example:
Switch(config-ptp-port)# sync
interval 1
Step 9
announce timeout value
Specifies the number of PTP announcement intervals
before the session times out. Valid values are 1-10.
Example:
Switch(config-ptp-port)# announce
timeout 8
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-6
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Step 10
Command
Purpose
delay-req interval interval
Configures the minimum interval allowed between PTP
delay-request messages when the port is in the master state.
Example:
The intervals are set using log base 2 values, as follows:
Switch(config-ptp-port)# delay-req
interval 1
Step 11
•
3—1 packet every 8 seconds
•
2—1 packet every 4 seconds
•
1—1 packet every 2 seconds
•
0—1 packet every second
•
-1—1 packet every 1/2 second, or 2 packets per second
•
-2—1 packet every 1/4 second, or 4 packets per second
•
-3—1 packet every 1/8 second, or 8 packets per second
•
-4—1 packet every 1/16 seconds, or 16 packets per
second.
•
-5—1 packet every 1/32 seconds, or 32 packets per
second.
•
-6—1 packet every 1/64 seconds, or 64 packets per
second.
•
-7—1 packet every 1/128 seconds, or 128 packets per
second.
Exit configuration mode.
Router(config-ptp-port)# end
Configuring a Boundary Clock
Follow these steps to configure the switch to act as a boundary clock.
Command
Purpose
Step 1
Switch# configure terminal
Enter configuration mode.
Step 2
Router(config)# ptp clock {ordinary |
boundary | e2e-transparent} domain
domain-number [hybrid]
Configures the PTP clock. You can create the following
clock types:
Example:
•
Ordinary—A 1588 clock with a single PTP port that
can operate in Master or Slave mode.
•
Boundary—Participates in selecting the best master
clock and can act as the master clock if no better clocks
are detected.
Switch(config)# ptp clock boundary
domain 0
Note
Step 3
clock-port port-name {master | slave}
Example:
The transparent clock and hybrid mode are not
supported on the Cisco ME 3600X 24CX switch.
Sets the clock port to PTP master or slave mode; in slave
mode, the port exchanges timing packets with a PTP master
clock.
Switch(config-ptp-clk)# clock-port
SLAVE slave
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-7
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
Step 4
Command
Purpose
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Sets port transport parameters.
The negotiation keyword configures the router to discover
a PTP master clock from all available PTP clock sources.
Example:
Switch(config-ptp-port)# transport
ipv4 unicast interface Loopback 0
negotiation
Step 5
clock-source source-address [priority]
Specifies the address of a PTP master clock. You can
specify a priority value as follows:
Example:
•
No priority value—Assigns a priority value of 0.
Switch(config-ptp-port)# clock
source 133.133.133.133
•
1—Assigns a priority value of 1.
•
2—Assigns a priority value of 2, the highest priority.
Note
Step 6
clock-port port-name {master | slave}
Example:
Step 7
This command is optional if PTP is configured in
unicast negotiation mode.
Sets the clock port to PTP master or slave mode; in master
mode, the port exchanges timing packets with PTP slave
devices.
The master clock-port does not establish a clocking
session until the slave clock-port is phase aligned.
Switch(config-ptp-port)# clock-port
Master master
Note
transport ipv4 unicast interface
interface-type interface-number
[negotiation]
Sets port transport parameters.
The negotiation keyword configures the router to discover
a PTP master clock from all available PTP clock sources.
Example:
Switch(config-ptp-port)# transport
ipv4 unicast interface Loopback 1
negotiation
Step 8
Switch(config-ptp-port)# end
Exit configuration mode.
Configuring PTP Input and Output
You can use the 1pps, 10Mhz and BITS timing ports on the Cisco ME 3600X-24CX to do the following:
Note
•
Provide or receive 1PPS time of day messages
•
Provide output clocking at 10Mhz, 2.048Mhz, and 1.544Mhz
•
Receive input clocking at 10Mhz, 2.048Mhz, and 1.544Mhz
This section applies only to the Cisco ME 3600X-24CX.
The following section describes how to configure time of day messages, output clocking, and input
clocking in master clock mode.
•
If you want to configure input clocking using the 10Mhz or BITS timing port, use the following
command:
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-8
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Configuring Clocking and Timing
– Use the network-clock input-source command to enable input clocking at 10Mhz, 2.048Mhz,
or 1.544Mhz.
Switch(config)# network-clock input-source 2 external 1/0/0 10m
Input clocking applies when the switch is in master mode.
•
To configure output clocking using the 10Mhz or BITS timing port, use the network-clock
output-source command to specify 10Mhz, 2.048Mhz, or 1.544Mhz output. Use this command
when the switch is in slave mode.
Switch(config)# network-clock output-source system 2 external 1/0/0 10m
•
To configure the switch to send time of day messages using the 1PPS port, use the output 1pps
command. Use the input or output parameters to specify the direction.
Switch(config)# ptp clock ordinary domain 0
Switch(config-ptp-clk)# output 1pps 0/0
Note
Input 1pps is only supported in master mode. Output 1pps configuration is supported in slave or
boundary clock mode.
•
To configure the time of day message format, use the tod command.
Switch(config)# ptp clock ordinary domain 0
Switch(config-ptp-clk)# tod 0/0 ubx
Configuration Examples
Use commands below for input and output.
network-clock input-source 2 external 1/0/0 10m
Switch(config)#network-clock input-source 2 external 1/0/0 ?
10m
10 MHz signal mode
2048k Option 1 2048kHz on BITS/SSU port
e1
E1 Signal Mode
Tod and 1pps configuration.
Master:
Switch(config)#ptp clock ordinary domain 0
Switch(config-ptp-clk)#input 1pps 0/0
Switch(config-ptp-clk)#tod 0/0 ?
cisco Set TOD format to CISCO
nmea
Set TOD format to NMEA ZDA
ntp
Set TOD format to NTP
ubx
Set TOD format to UBX
Slave:
Switch(config)#ptp clock ordinary domain 0
Switch(config-ptp-clk)#output 1pps 0/0 ?
offset
1PPS output offset
pulse-width 1PPS output pulse width
Switch(config-ptp-clk)#tod 0/0 ?
cisco Set TOD format to CISCO
nmea
Set TOD format to NMEA ZDA
ntp
Set TOD format to NTP
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-9
Chapter 5
Configuring Clocking and Timing
Clocking Sample Configurations
ubx
Note
Set TOD format to UBX
To see further configuration examples for input and output timing, see Clocking Sample Configurations.
Configuring Synchronous Ethernet
The following sections describe how to configure synchronous Ethernet timing on the Cisco ME 3600X
24CX Series Switch switch.
Note
Hybrid mode is not supported therefore, network-clock input-source command cannot be configured
with Ordinary Slave mode or Boundary Clock mode.
Configuring an External Clock Source
To configure an external clock source using Synchronous Ethernet, use the network-clock input-source
priority external 1/0/0 {{E1 {crc4 | cas |fas}} {T1 {d4 | sf | esf}} } command.
Switch(config)# network-clock input-source 1 external 1/0/0
Configuring Synchronous Ethernet ESMC and SSM
For instructions on how to configure synchronous Ethernet Synchronization Message Channel
(ESMC)and Synchronization Status Message (SSM), see Configuring Synchronous Ethernet in Cisco
ME 3800x and ME 3600x Switch Software Configuration Guide
Verifying Clock-Related Settings
Use the following commands to verify the clock settings:
•
show ptp clock dataset
•
show ptp port dataset
•
show ptp clock running
•
show platform ptp all
For more information about these commands, see the Cisco ME 3800X and ME 3600X Switch Command
Reference, Release 15.2(4)S.
Clocking Sample Configurations
The following sections show a sample configurations for clocking features on the switch.
Ordinary Clock—Slave
ptp clock ordinary domain 0
clock-port Slave slave
transport ipv4 unicast interface loopback 0 negotiation
clock-source 8.8.8.1
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-10
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Clocking Sample Configurations
sync interval 1
announce timeout 7
delay-req interval 3
Ordinary Clock—Master
ptp clock ordinary domain 0
clock-port Master master
transport ipv4 unicast interface loopback 0 negotiation
Unicast Configuration—Slave Mode
ptp clock ordinary domain 0
clock-port Slave slave
transport ipv4 unicast interface loopback 0
clock-source 8.8.8.1
Unicast Configuration—Master Mode
ptp clock ordinary domain 0
clock-port Master master
transport ipv4 unicast interface loopback 0
clock-destination 8.8.8.2
sync interval 1
announce interval 2
Unicast Negotiation—Slave
ptp clock ordinary domain 0
priority1 2
priority2 4
clock-port Slave slave
transport ipv4 unicast interface Loopback0 negotiation
clock-source 8.8.8.1
sync interval 3
announce timeout 7
delay-req interval 3
Unicast Negotiation—Master
ptp clock ordinary domain 0
priority1 4
priority2 2
clock-port Master master
transport ipv4 unicast interface Loopback0 negotiation
sync interval 3
announce timeout 7
Boundary Clock
ptp clock boundary domain 0
priority1 2
priority2 4
clock-port Slave slave
transport ipv4 unicast interface Loopback0 negotiation
clock-source 8.8.8.1
sync limit 3
announce timeout 7
delay-req interval 3
clock-port Master master
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-11
Chapter 5
Configuring Clocking and Timing
Clocking Sample Configurations
transport ipv4 interface Loopback1 negotiation
sync interval 3
announce interval 7
Clock Selection Parameters
network-clock synchronization automatic
network-clock synchronization mode QL-enabled
network-clock input-source 1 external 1/0/0 10m
ToD/1PPS Configuration—Master
network-clock input-source 1 external 1/0/0 10m
ptp clock ordinary domain 0
tod 0/0 ntp
input 1pps 0/0
clock-port master master
transport ipv4 unicast interface loopback 0
ToD/1PPS Configuration—Slave
ptp clock ordinary domain 0
tod 0/0 ntp
output 1pps 0/0
clock-port SLA slave
transport ipv4 unicast interface loopback 0 negotiation
clock source 33.1.1.
Show Commands
Router# show ptp clock dataset ?
current
currentDS dataset
default
defaultDS dataset
parent
parentDS dataset
time-properties timePropertiesDS dataset
Router#show ptp port dataset ?
foreign-master foreignMasterDS dataset
port
portDS dataset
Router#show ptp clock running domain 0
PTP Ordinary Clock [Domain 0]
State
Ports
Pkts sent
ACQUIRING
1
98405
Pkts rcvd
296399
Redundancy Mode
Track one
PORT SUMMARY
PTP
Master
Name
Addr
SLAVE
8.8.8.8
Tx Mode
unicast
Role
Transport
slave
Lo0
State
Slave
Sessions
Port
1
SESSION INFORMATION
SLAVE [Lo0] [Sessions 1]
Peer addr
Pkts in
8.8.8.8
296399
Router#
Pkts out
98405
In Errs
0
Out Errs
0
Router#show platform ptp all
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-12
OL-27620-01
Chapter 5
Configuring Clocking and Timing
Clocking Sample Configurations
Slave info : [Loopback0][0x38A4766C]
-------------------------------clock role
: SLAVE
Slave Port hdl
: 486539266
Tx Mode
: Unicast-Negotiation
Slave IP
: 4.4.4.4
Max Clk Srcs
: 1
Boundary Clock
: FALSE
Lock status
: HOLDOVER
Refcnt
: 1
Configured-Flags
: 0x7F - Clock Port Stream
Config-Ready-Flags : Port Stream
----------PTP Engine Handle
: 0
Master IP
: 8.8.8.8
Local Priority
: 0
Set Master IP
: 8.8.8.8
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
5-13
Chapter 5
Configuring Clocking and Timing
Clocking Sample Configurations
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
5-14
OL-27620-01
CH A P T E R
6
Configuring Pseudowire
This chapter provides information about configuring pseudowire features on the Cisco ME 3600X
24CX Series Switch. It contains the following sections:
•
Pseudowire Overview, page 6-1
•
Configuring Structure-Agnostic TDM over Packet (SAToP), page 6-5
•
Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN), page 6-6
•
Configuring Pseudowire Redundancy, page 6-7
•
Verifying the Interface Configuration, page 6-8
Pseudowire Overview
The following sections provide an overview of pseudowire support on the Cisco ME 3600X
24CX Series Switch.
Circuit Emulation Overview
Circuit Emulation (CEM) is a technology that provides a protocol-independent transport over IP
networks. It enables proprietary or legacy applications to be carried transparently to the destination,
similar to a leased line.
The Cisco ME 3600X 24CX Series Switch supports two pseudowire types that utilize CEM transport:
Structure-Agnostic TDM over Packet and Circuit Emulation Service over Packet-Switched Network.
The following sections provide an overview of these pseudowire types.
Structure-Agnostic TDM over Packet
SAToP encapsulates TDM bit-streams (T1, E1) as PWs over PSNs. It disregards any structure that may
be imposed on streams, in particular the structure imposed by the standard TDM framing.
The protocol used for emulation of these services does not depend on the method in which attachment
circuits are delivered to the PEs. For example, a T1 attachment circuit is treated the same way for all
delivery methods, including: PE on copper, mapped into a virtual tributary of a SONET/SDH circuit, or
carried over a network using unstructured Circuit Emulation Service (CES). Termination of specific
carrier layers used between the PE and circuit emulation (CE) is performed by an appropriate network
service provider (NSP).
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
6-1
Chapter 6
Configuring Pseudowire
Pseudowire Overview
In the SAToP mode the interface is considered as a continuous framed bit stream. The packetization of
the stream is done according to IETF RFC 4553. All signaling is carried out transparently as a part of a
bit stream. Figure 6-1 shows the frame format in Unstructured SAToP mode.
Figure 6-1
Unstructured Mode Frame Format
Encapsulation header
CE Control (4Bytes)
CEoP
Payload
Bytes 1-N
230547
RTP (optional 12B)
Table 6-1 shows the payload and jitter limits for the T1 lines in the SAToP frame format.
Table 6-1
SAToP T1 Frame: Payload and Jitter Limits
Maximum
Payload
Maximum
Jitter
Minimum
Jitter
Minimum
Payload
Maximum
Jitter
Minimum
Jitter
960
320
10
192
64
2
Table 6-2 shows the payload and jitter limits for the E1 lines in the SAToP frame format.
Table 6-2
SAToP E1 Frame: Payload and Jitter Limits
Maximum
Payload
Maximum
Jitter
Minimum
Jitter
Minimum
Payload
Maximum
Jitter
Minimum
Jitter
1280
320
10
256
64
2
For instructions on how to configure SAToP, see Configuring Structure-Agnostic TDM over Packet
(SAToP).
Circuit Emulation Service over Packet-Switched Network
CESoPSN encapsulates structured (NxDS0) TDM signals as PWs over public switched networks
(PSNs). It complements similar work for structure-agnostic emulation of TDM bit streams, such as
SAToP. Emulation of NxDS0 circuits saves PSN bandwidth and supports DS0-level grooming and
distributed cross-connect applications. It also enhances resilience of CE devices due to the effects of loss
of packets in the PSN.
CESoPSN identifies framing and sends only the payload, which can either be channelized T1s within
DS3 or DS0s within T1. DS0s can be bundled to the same packet. The CESoPSN mode is based on IETF
RFC 5086.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
6-2
OL-27620-01
Chapter 6
Configuring Pseudowire
Pseudowire Overview
Each supported interface can be configured individually to any supported mode. The supported services
comply with IETF and ITU drafts and standards.
Figure 6-2 shows the frame format in CESoPSN mode.
Figure 6-2
Structured Mode Frame Format
Encapsulation header
CE Control (4Bytes)
RTP (optional 12B)
Frame#1
Timeslots 1-N
Frame#2
Timeslots 1-N
CEoP
Payload
Frame#m
Timeslots 1-N
230546
Frame#3
Timeslots 1-N
Table 6-3 shows the payload and jitter for the DS0 lines in the CESoPSN mode.
Table 6-3
CESoPSN DS0 Lines: Payload and Jitter Limits
DS0
Maximum
Payload
Maximum
Jitter
Minimum
Jitter
Minimum
Payload
Maximum
Jitter
Minimum
Jitter
1
40
320
10
32
256
8
2
80
320
10
32
128
4
3
120
320
10
33
128
4
4
160
320
10
32
64
2
5
200
320
10
40
64
2
6
240
320
10
48
64
2
7
280
320
10
56
64
2
8
320
320
10
64
64
2
9
360
320
10
72
64
2
10
400
320
10
80
64
2
11
440
320
10
88
64
2
12
480
320
10
96
64
2
13
520
320
10
104
64
2
14
560
320
10
112
64
2
15
600
320
10
120
64
2
16
640
320
10
128
64
2
17
680
320
10
136
64
2
18
720
320
10
144
64
2
19
760
320
10
152
64
2
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
6-3
Chapter 6
Configuring Pseudowire
Pseudowire Overview
DS0
Maximum
Payload
Maximum
Jitter
Minimum
Jitter
Minimum
Payload
Maximum
Jitter
Minimum
Jitter
20
800
320
10
160
64
2
21
840
320
10
168
64
2
22
880
320
10
176
64
2
23
920
320
10
184
64
2
24
960
320
10
192
64
2
25
1000
320
10
200
64
2
26
1040
320
10
208
64
2
27
1080
320
10
216
64
2
28
1120
320
10
224
64
2
29
1160
320
10
232
64
2
30
1200
320
10
240
64
2
31
1240
320
10
248
64
2
32
1280
320
10
256
64
2
For instructions on how to configure SAToP, see Configuring Structure-Agnostic TDM over Packet
(SAToP).
Transportation of Service Using Ethernet over MPLS
Ethernet over MPLS (EoMPLS) PWs provide a tunneling mechanism for Ethernet traffic through an
MPLS-enabled Layer 3 core network. EoMPLS PWs encapsulate Ethernet protocol data units (PDUs)
inside MPLS packets and use label switching to forward them across an MPLS network. EoMPLS PWs
are an evolutionary technology that allows you to migrate packet networks from legacy networks while
providing transport for legacy applications. EoMPLS PWs also simplify provisioning, since the provider
edge equipment only requires Layer 2 connectivity to the connected customer edge (CE) equipment. The
Cisco ME 3600X 24CX Series Switch implementation of EoMPLS PWs is compliant with the RFC 4447
and 4448 standards.
The Cisco ME3600-24CX Switch supports VLAN rewriting on EoMPLS PWs. If the two networks use
different VLAN IDs, the router rewrites PW packets using the appropriate VLAN number for the local
network.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
6-4
OL-27620-01
Chapter 6
Configuring Pseudowire
Configuring Structure-Agnostic TDM over Packet (SAToP)
Configuring Structure-Agnostic TDM over Packet (SAToP)
Follow these steps to configure SAToP on the Cisco ME 3600X 24CX Series Switch:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
card type [T1|E1]
Selects the card type as T1 or E1
Step 4
controller [T1|E1] 0/1
Configures the T1 or E1 interface.
Example:
Router(config-controller)#
controller t1
Step 5
cem-group group-number {unframed |
timeslots timeslot }
Example:
Router(config-if)# cem-group 4
unframed
Assigns channels on the T1 or E1 circuit to the CEM channel. This
example uses the unframed parameter to assign all the T1 timeslots to the
CEM channel.
Step 6
Router(config)# interface CEM0/4
Router(config-if)# no ip address
Router(config-if)# cem 4
Defines a CEM group.
Step 7
Router(config-if)# xconnect
30.30.30.2 304 encapsulation mpls
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 304 to the
remote peer 30.30.2.304.
Step 8
exit
Exits configuration mode.
Example:
Router(config)# exit
Router#
Note
When creating IP routes for a pseudowire configuration, we recommend that you build a route from the
xconnect address (LDP router-id or loopback address) to the next hop IP address, such as ip route
30.30.30.2 255.255.255.255 1.2.3.4.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
6-5
Chapter 6
Configuring Pseudowire
Configuring Circuit Emulation Service over Packet-Switched Network (CESoPSN)
Configuring Circuit Emulation Service over Packet-Switched
Network (CESoPSN)
Follow these steps to configure CESoPSN on the Cisco ME 3600X 24CX Series Switch.
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Router# configure terminal
Step 3
card type [T1|E1]
Selects the card type as T1 or E1.
Step 4
Router(config)# controller [e1|t1]
0/0
Router(config-controller)#
Enters configuration mode for the E1 or T1 controller.
Step 5
Router(config-controller)#
cem-group 5 timeslots 1-24
Assigns channels on the T1 or E1 circuit to the circuit emulation (CEM)
channel. This example uses the timeslots parameter to assign specific
timeslots to the CEM channel.
Step 6
Router(config-controller)# exit
Router(config)#
Exits controller configuration.
Step 7
Router(config)# interface CEM0/5
Router(config-if-cem)# cem 5
Defines a CEM channel.
Step 8
Router(config-if-cem)# xconnect
30.30.30.2 305 encapsulation mpls
Binds an attachment circuit to the CEM interface to create a pseudowire.
This example creates a pseudowire by binding the CEM circuit 5 to the
remote peer 30.30.30.2.
Note
When creating IP routes for a pseudowire configuration, we
recommend that you build a route from the xconnect address
(LDP router-id or loopback address) to the next hop IP address,
such as ip route 30.30.30.2 255.255.255.255 1.2.3.4.
Step 9
Router(config-if-cem)# exit
Router(config)#
Exits the CEM interface.
Step 10
exit
Exits configuration mode.
Example:
Router(config)# exit
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
6-6
OL-27620-01
Chapter 6
Configuring Pseudowire
Configuring Pseudowire Redundancy
Configuring Pseudowire Redundancy
A backup peer provides a redundant pseudowire (PW) connection in the case that the primary PW loses
connection; if the primary PW goes down, the Cisco ME 3600X 24CX Series Switch diverts traffic to
the backup PW. This feature provides the ability to recover from a failure of either the remote PE router
or the link between the PE router and CE router.
Figure 6-3 shows an example of pseudowire redundancy.
Figure 6-3
Pseudowire Redundancy
CE1
PE2
PE1
Redundant
attachment CE2
circuits
135058
Primary
pseudowire
Backup
pseudowire
Note
You must configure the backup pseudowire to connect to a router that is different from the primary
pseudowire.
Follow these steps to configure a backup peer:
Step 1
Command
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Router> enable
Step 2
configure terminal
Enters global configuration mode.
Step 3
pseudowire-class [pw-class-name]
Specify the name of a Layer 2 pseudowire class and enter pseudowire
class configuration mode.
Step 4
encapsulation mpls
Specifies MPLS encapsulation.
Step 5
interface cem
card/number
Enters configuration mode for the cem interface.
Note
The card number is always 0.
Step 6
Router(config-if)# xconnect 1.1.1.2
101 encapsulation mpls
Binds the Ethernet port interface to an attachment circuit to create a
pseudowire.
Step 7
Router(xconnect)# backup peer
peer-router-ip-address vcid
[pw-class pw-class name]
Defines the address and VC of the backup peer.
Step 8
exit
Exits configuration mode.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
OL-27620-01
6-7
Chapter 6
Configuring Pseudowire
Verifying the Interface Configuration
Verifying the Interface Configuration
You can use the following commands to verify your pseudowire configuration:
•
show cem circuit—Displays information about the circuit state, administrative state, the CEM ID
of the circuit, and the interface on which it is configured. If xconnect is configured under the circuit,
the command output also includes information about the attached circuit.
Router# show
<0-504>
detail
interface
summary
|
cem circuit ?
CEM ID
Detailed information of cem ckt(s)
CEM Interface
Display summary of CEM ckts
Output modifiers
Router# show cem circuit
CEM Int.
ID
Line
Admin
Circuit
AC
-------------------------------------------------------------CEM0/1
1
UP
UP
ACTIVE
--/-CEM0/1
2
UP
UP
ACTIVE
--/-CEM0/1
3
UP
UP
ACTIVE
--/-CEM0/1
4
UP
UP
ACTIVE
--/-CEM0/1
5
UP
UP
ACTIVE
--/--
•
show cem circuit—Displays the detailed information about that particular circuit.
Router# show cem circuit 1
CEM0/1, ID: 1, Line State: UP, Admin State: UP, Ckt State: ACTIVE
Idle Pattern: 0xFF, Idle cas: 0x8, Dummy Pattern: 0xFF
Dejitter: 5, Payload Size: 40
Framing: Framed, (DS0 channels: 1-5)
Channel speed: 56
CEM Defects Set
Excessive Pkt Loss RatePacket Loss
Signalling: No CAS
Ingress Pkts:
25929
Egress Pkts:
0
CEM Counter Details
Input Errors:
0
Pkts Missing:
25927
Misorder Drops: 0
Error Sec:
26
Unavailable Sec: 5
Pkts Malformed: 0
•
Dropped:
Dropped:
0
0
Output Errors:
Pkts Reordered:
JitterBuf Underrun:
Severly Errored Sec:
Failure Counts:
0
0
1
26
1
show cem circuit summary—Displays the number of circuits which are up or down per interface
basis.
Router# show cem circuit summary
CEM Int.
Total Active Inactive
-------------------------------------CEM0/1
5
5
0
show running configuration—The show running configuration command shows detail on each CEM
group.
Cisco ME-3600X-24CX Series Switch Chassis Configuration Guide
6-8
OL-27620-01
CH A P T E R
7
Configuring MPLS Transport Profile
The Multiprotocol Label Switching (MPLS) Transport Profile (TP) enables you to create tunnels that
provide the transport network service layer over which IP and MPLS traffic traverse. MPLS-TP tunnels
enable a transition from Synchronous Optical Networking (SONET) and Synchronous Digital Hierarchy
(SDH) time-division multiplexing (TDM) technologies to packet switching to support services with high
bandwidth requirements, such as video.
Contents
•
Restrictions for MPLS-TP, page 7-2
•
Information About MPLS-TP, page 7-3
•
How to Configure MPLS-TP, page 7-7
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-1
Chapter 7
Configuring MPLS Transport Profile
Restrictions for MPLS-TP
Restrictions for MPLS-TP
•
Penultimate hop popping is not supported. Only ultimate hop popping is supported, because label
mappings are configured at the MPLS-TP endpoints.
•
Ethernet subinterfaces are not supported.
•
IPV6 addressing is not supported.
L2VPN Restrictions
•
L2VPN interworking is not supported.
•
Local switching with AToM pseudowire as a backup is not supported.
•
L2VPN pseudowire redundancy to an AToM pseudowire by one or more attachment circuits is not
supported.
•
PW ID Forward Equivalence Class (FEC) (type 128) is supported, but generalized ID FEC (type
129) is not supported.
•
BFD VCCV AC status signaling is not supported.
•
Multisegment Pseudowires are not supported.
Ping and Trace Restrictions
•
Ping for Static Pseudowires over MPLS-TP tunnels is not supported.
•
Pseudowire ping and traceroute functionality for multisegment pseudowires that have one or more
static pseudowire segments is not supported.
•
The following packet format is supported:
– A labeled packet with Generic Associated Channel Label (GAL) at the bottom of the label stack.
– ACH channel is IP (0x21).
– RFC 4379-based IP, UDP packet payload with valid source.
– Destination IP address and UDP port 3503.
•
Default reply mode for (1) is 4—Reply via application level control channel. An echo reply consists
of the following elements:
– A labeled packet with a GAL label at the bottom of the label stack.
– ACH channel is IP (0x21).
– RFC 4379-based IP, UDP packet payload with valid source.
– Destination IP address and UDP port 3503.
•
The optional “do not reply” mode may be set.
•
The following reply modes are not allowed and are disabled in CLI:
– 2—Reply via an IPv4/IPv6 UDP packet
– 3—Reply via an IPv4/IPv6 UDP packet with Router Alert
•
Force-explicit-null is not supported with ping and trace.
•
Optional Reverse Path Connectivity verification is not supported. See LSP-Ping Extensions for
MPLS-TP (draft-nitinb-mpls-tp-lsp-ping-extensions-01.txt).
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-2
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
Information About MPLS-TP
Information About MPLS-TP
•
How MPLS-TP Works, page 7-3
•
MPLS-TP Path Protection, page 7-4
•
Bidirectional LSPs, page 7-4
•
MPLS-TP OAM Support, page 7-4
•
MPLS-TP: Static and Dynamic Pseudowires, page 7-5
•
MPLS-TP: L2VPN Pseudowire Redundancy for Static and Dynamic Pseudowires, page 7-6
•
MPLS-TP: OAM Status for Static and Dynamic Pseudowires, page 7-6
•
MPLS-TP Links and Physical Interfaces, page 7-6
•
Tunnel Midpoints, page 7-6
How MPLS-TP Works
MPLS-TP tunnels provide the transport network service layer over which IP and MPLS traffic traverse.
MPLS-TP tunnels help transition from SONET/SDH TDM technologies to packet switching to support
services with high bandwidth utilization and lower cost. Transport networks are connection oriented,
statically provisioned, and have long-lived connections. Transport networks usually avoid control
protocols that change identifiers (like labels). MPLS-TP tunnels provide this functionality through
statically provisioned bidirectional label switched paths (LSPs), as shown in Figure 7-1.
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-3
Chapter 7
Configuring MPLS Transport Profile
Information About MPLS-TP
Figure 7-1
MPLS-TP Tunnel
Working LSP
PE
PE
Pseudowire
Protect LSP
Client Node
MPLS-TP LSP
Client Node
310473
L2VPN Pseudowire
Client Signal
MPLS-TP Path Protection
MPLS-TP LSPs support 1-to-1 path protection. You can configure the working and protect LSPs as part
of configuring the MPLS-TP tunnel. The working LSP is the primary LSP used to route traffic. The
protect LSP is a backup for a working LSP. If the working LSP fails, traffic is switched to the protect
LSP until the working LSP is restored, at which time forwarding reverts back to the working LSP.
Bidirectional LSPs
MPLS-TP LSPs are bidirectional and co-routed and are comprised of two unidirectional LSPs that are
supported by the MPLS forwarding infrastructure. A TP tunnel consists of a pair of unidirectional
tunnels providing a bidirectional LSP. Each unidirectional tunnel can optionally be protected with a
protect LSP that activates automatically upon failure conditions.
MPLS-TP OAM Support
Several OAM protocols and messages support the provisioning and maintenance of MPLS-TP tunnels
and bidirectional LSPs:
•
MPLS-TP OAM: GACH: Generic Associated Channel (G-ACh) is the control channel mechanism
associated with MPLS LSPs in addition to MPLS pseudowire. The G-ACh Label (GAL) (Label 13)
is a generic alert label to identify the presence of the G-ACh in the label packet. It is taken from the
reserved MPLS label space.
G-ACh/GAL is used to support in-band OAMs of MPLS LSPs and PWs. The OAM messages are
used for fault management, connection verification, continuity check and other functions.
The following OAM messages are forwarded along the specified MPLS LSP:
– OAM Fault Management: AIS, LDI and LKR messages. (GAL with fault-OAM channel)
– OAM Connection Verification: ping and traceroute messages. (GAL with IP channel by default)
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-4
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
Information About MPLS-TP
– OAM Continuity Check: BFD (non-IP BFD and IP BFD) messages. (GAL with BFD channel
or IP channel depending on message format)
The following messages are forwarded along the specified PW:
– Static PW OAM messages (static PW status)
– PW ping and traceroute messages
– PW BFD messages
•
MPLS-TP OAM: Fault Management: Link Down Indication (LDI), Alarm Indication Signal (AIS),
and Lock Report (LKR) messages. LDI messages are generated at midpoint nodes when a failure is
detected. At the midpoint, an LDI message will be sent to the endpoint that is reachable with the
existing failure. Similarly, LKR messages will be sent from a midpoint node to the reachable
endpoint when an interface is administratively shut. AIS messages are not generated by Cisco, but
are processed if received. By default, reception of LDI and LKR on the active LSP at an endpoint
will cause a path protection switchover, while AIS will not.
•
MPLS-TP OAM: Fault Management: Emulated Protection Switching for LSP Lockout. Cisco
implements a form of Emulated Protection Switching in support of LSP Lockout using customized
Fault messages. When a Cisco Lockout message is sent, it does not cause the LSP to be
administratively down. The Cisco Lockout message causes a path protection switchover and
prevents data traffic from using the LSP. The LSP remains up so that BFD and other OAM messages
can continue to traverse it. Maintenance of the LSP can take place (such as reconfiguring or
replacing a midpoint LSR). The LSP is shown as UP and OAM can verify connectivity before the
LSP is put back into service by removing the lockout. Lockout of the working LSP is not allowed if
no protect LSP is configured. Alternatively, lockout of the protect LSP is allowed if no working LSP
is configured.
•
LSP ping and trace: For MPLS-TP connectivity verification, you can use ping mpls tp and trace
mpls tp commands. You can specify that the echo requests be sent along either the working LSP, the
protect LSP, or the active LSP. You can also specify that the echo request be sent on a locked out
MPLS-TP tunnel LSP (either working or protect) if the working or protect LSP is explicitly
specified.
•
MPLS-TP OAM: Continuity Check via BFD: You can configure BFD sessions running over
MPLS-TP LSPs. BFD sessions run on both the working LSP and the protect LSP. In order to
perform a path protection switchover within 60 msec on an MPLS-TP endpoint, the BFD Hardware
Offload feature enables the router hardware to construct and send BFD messages, which removes
the task from the software path. You do not need to configure the BFD Hardware Offload feature. It
works automatically on supported platforms. You must enable BFD.
MPLS-TP: Static and Dynamic Pseudowires
MPLS-TP supports the following combinations of static and dynamic pseudowires:
•
Static-static
•
Static-dynamic
•
Dynamic-static
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-5
Chapter 7
Configuring MPLS Transport Profile
Information About MPLS-TP
MPLS-TP: L2VPN Pseudowire Redundancy for Static and Dynamic
Pseudowires
MPLS-TP supports one-to-one L2VPN pseudowire redundancy for the following combinations of static
and dynamic pseudowires:
•
Static pseudowire with a static backup pseudowire
•
Static pseudowire with a dynamic backup pseudowire
•
Dynamic pseudowire with a static backup pseudowire
MPLS-TP: OAM Status for Static and Dynamic Pseudowires
With static pseudowires, status notifications can be provided by BFD over VCCV or static pseudowire
OAM protocol. However, BFD over VCCV is not supported. Therefore, static pseudowire OAM protocol
is preferred.
MPLS-TP Links and Physical Interfaces
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual
interfaces are not supported for MPLS-TP link numbers.
The MPLS-TP link is used to create a level of indirection between the MPLS-TP tunnel and midpoint
LSP configuration and the physical interface. The mpls tp link command is used to associate an
MPLS-TP link number with a physical interface and next-hop node. On point-to-point interfaces or
Ethernet interfaces designated as point-to-point using the medium p2p command, the next-hop can be
implicit, so the mpls tp link command just associates a link number to the interface.
Multiple tunnels and LSPs may then refer to the MPLS-TP link to indicate they are traversing that
interface. You can move the MPLS-TP link from one interface to another without reconfiguring all the
MPLS-TP tunnels and LSPs that refer to the link.
Link numbers must be unique on the router or node.
See Configuring MPLS-TP Links and Physical Interfaces, page 7-17 for more information.
Tunnel Midpoints
Tunnel LSPs, whether endpoint or midpoint, use the same identifying information. However, it is entered
differently.
•
At the midpoint, all the information for the LSP is specified with the mpls tp lsp command, which
enters the submode for configuring forward and reverse information for forwarding.
•
At the midpoint, determining which end is source and which is destination is arbitrary. That is, if
you are configuring a tunnel between your router and a coworker’s router, then your router is the
source. However, your coworker considers his or her router to be the source. At the midpoint, either
router could be considered the source. At the midpoint, the forward direction is from source to
destination, and the reverse direction is from destination to source.
•
At the endpoint, the local information (source) either comes from the global router ID and global
ID, or from locally configured information using the tp source command after you enter the
command interface tunnel-tp number command, where number is the local/source tunnel-number.
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-6
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
•
At the endpoint, the remote information (destination) is configured using the tp destination
command after you enter the command interface tunnel-tp number. The tp destination command
includes the destination node ID, optionally the global ID, and optionally the destination tunnel
number. If you do not specify the destination tunnel number, the source tunnel number is used.
•
At the endpoint, the LSP number is configured in working-lsp or protect-lsp submode. The default
is 0 for the working LSP and 1 for the protect LSP.
•
When configuring the LSPs at the midpoint routers, make that the configuration does not reflect
traffic back to the originating node.
How to Configure MPLS-TP
•
Configuring the MPLS Label Range, page 7-7
•
Configuring the Router ID and Global ID, page 7-8
•
Configuring Bidirectional Forwarding Detection Templates, page 7-9
•
Configuring Pseudowire OAM Attributes, page 7-10
•
Configuring the Pseudowire Class, page 7-11
•
Configuring the Pseudowire, page 7-12
•
Configuring the MPLS-TP Tunnel, page 7-13
•
Configuring MPLS-TP LSPs at Midpoints, page 7-16
•
Configuring MPLS-TP Links and Physical Interfaces, page 7-17
•
Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP, page 7-19
•
Configuring a Template with Pseudowire Type-Length-Value Parameters, page 7-20
•
Configuring Static-to-Dynamic Pseudowires for MPLS-TP, page 7-21
•
Configuring the L2VPN Pseudowire Redundancy for Static Pseudowires Backed Up with Static or
Dynamic Pseudowires, page 7-24
•
Verifying the MPLS-TP Configuration, page 7-26
Configuring the MPLS Label Range
You must specify a static range of MPLS labels using the mpls label range command with the static
keyword.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
mpls label range minimum-value maximum-value {static minimum-static-value
maximum-static-value}
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-7
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
mpls label range minimum-value maximum-value
{static minimum-static-value
maximum-static-value}
Specifies a static range of MPLS labels
Example:
Switch(config)# mpls label range 1001 1003
static 10000 25000
Configuring the Router ID and Global ID
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
mpls tp
4.
router-id node-id
5.
global-id num
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
mpls tp
Enters MPLS-TP configuration mode, from which you can
configure MPLS-TP parameters for the switch.
Example:
Switch(config)# mpls tp
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-8
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 4
Command or Action
Purpose
router-id node-id
Specifies the default MPLS-TP router ID, which is used as
the default source node ID for all MPLS-TP tunnels
configured on the router.
Example:
Router(config-mpls-tp)# router-id 10.10.10.10
Step 5
global-id num
Example:
Switch(config-mpls-tp)# global-id 1
(Optional) Specifies the default global ID used for all
endpoints and midpoints. This command makes the switch
ID globally unique in a multiprovider tunnel. Otherwise, the
router ID is only locally meaningful. The global ID is an
autonomous system number, which is a controlled number
space by which providers can identify each other.
The router ID and global ID are also included in fault
messages by routers at tunnel midpoints to help isolate the
location of faults.
Configuring Bidirectional Forwarding Detection Templates
The bfd-template command allows you to create a BFD template and enter BFD configuration mode.
The template can be used to specify a set of BFD interval values. You invoke the template as part of the
MPLS-TP tunnel. On platforms that support the BFD Hardware Offload feature and can provide 60-ms
cutover for MPLS-TP tunnels, it is recommended to use the higher resolution timers in the BFD
template.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
bfd-template single-hop template-name
4.
interval [microseconds] {both time | min-tx time min-rx time} [multiplier multiplier-value]
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-9
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 3
Command or Action
Purpose
bfd-template single-hop template-name
Creates a BFD template and enter BFD configuration mode.
Example:
Switch(config)# bfd-template single-hop
mpls-bfd-1
Step 4
interval [microseconds] {both time | min-tx
time min-rx time} [multiplier multiplier-value]
Specifies a set of BFD interval values.
Example:
Switch(config-bfd)# interval min-tx 99 min-rx
99 multiplier 3
Configuring Pseudowire OAM Attributes
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
pseudowire-static-oam class class-name
4.
timeout refresh send seconds
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
pseudowire-static-oam class class-name
Creates a pseudowire OAM class and enters pseudowire
OAM class configuration mode.
Example:
Switch(config)# pseudowire-static-oam class
oam-class1
Step 4
timeout refresh send seconds
Specifies the OAM timeout refresh intervals.
Example:
Switch(config-st-pw-oam-class)# timeout refresh
send 20
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-10
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Configuring the Pseudowire Class
When you create the pseudowire class, you specify the parameters of the pseudowire, such as the use of
the control word, preferred path, and OAM class.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
pseudowire-class class-name
4.
encapsulation mpls
5.
control-word
6.
protocol {l2tpv2 | l2tpv3 | none} [l2tp-class-name]
7.
preferred-path {interface tunnel tunnel-number | peer {ip-address | host-name}}
[disable-fallback]
8.
status protocol notification static class-name
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Switch# configure terminal
Step 3
Creates a pseudowire class and enters pseudowire class
configuration mode.
pseudowire-class class-name
Example:
Switch(config)# pseudowire-class mpls-tp-class1
Step 4
Specifies the encapsulation type.
encapsulation mpls
Example:
Switch(config-pw-class)# encapsulation mpls
Step 5
Enables the use of the control word.
control-word
Example:
Switch(config-pw-class)# control-word
Step 6
protocol {l2tpv2 | l2tpv3 | none}
[l2tp-class-name]
Specifies the type of protocol.
Example:
Switch(config-pw-class)# protocol none
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-11
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 7
Command or Action
Purpose
preferred-path {interface tunnel tunnel-number
| peer {ip-address | host-name}}
[disable-fallback]
Specifies the tunnel to use as the preferred path.
Example:
Switch(config-pw-class)# preferred-path
interface tunnel-tp2
Step 8
status protocol notification static class-name
Specifies the OAM class to use.
Example:
Switch(config-pw-class)# status protocol
notification static oam-class1
Configuring the Pseudowire
1.
enable
2.
configure terminal
3.
interface type number
4.
xconnect peer-ip-address vc-id {encapsulation {l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name] [sequencing {transmit | receive | both}]
5.
mpls label local-pseudowire-label remote-pseudowire-label
6.
mpls control-word
7.
backup delay {enable-delay-period | never} {disable-delay-period | never}
8.
backup peer peer-router-ip-addr vcid [pw-class pw-class-name] [priority value]
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
interface type number
Specifies the interface and enters interface configuration
mode.
Example:
Switch(config)# interface Ethernet 1/0
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-12
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 4
Command or Action
Purpose
xconnect peer-ip-address vc-id {encapsulation
{l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name]
[sequencing {transmit | receive | both}]
Binds the attachment circuit to a pseudowire VC and enters
xconnect interface configuration mode.
Example:
Switch(config-if)# xconnect 10.131.191.251 100
encapsulation mpls manual pw-class
mpls-tp-class1
Step 5
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(config-if-xconn)# mpls label 100 150
Step 6
Specifies the control word.
mpls control-word
Example:
Switch(config-if-xconn)# no mpls control-word
Step 7
backup delay {enable-delay-period | never}
{disable-delay-period | never}
Specifies how long a backup pseudowire virtual circuit
(VC) should wait before resuming operation after the
primary pseudowire VC goes down.
Example:
Switch(config-if-xconn)# backup delay 0 never
Step 8
backup peer peer-router-ip-addr vcid [pw-class
pw-class-name] [priority value]
Specifies a redundant peer for a pseudowire virtual circuit
(VC).
Example:
Switch(config-if-xconn)# backup peer 10.0.0.2
50
Configuring the MPLS-TP Tunnel
On the endpoint switchs, create an MPLS TP tunnel and configure its parameters. See the interface
tunnel-tp command for information on the parameters.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface tunnel-tp number
4.
description tunnel-description
5.
tp tunnel-name name
6.
tp bandwidth num
7.
tp source mode-id [global-id num]
8.
tp destination node-id [[tunnel-tp num] global-id num]
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-13
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
9.
bfd bfd-template
10. working-lsp
11. in-label num
12. out-label num out-link num
13. exit
14. protect-lsp
15. in-label num
16. out-label num out-link num
17. exit
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Switch# configure terminal
Step 3
interface tunnel-tp
number
Enters tunnel interface configuration mode. Tunnel
numbers from 0 to 999 are supported.
Example:
Switch(config)# interface tunnel-tp 2
Step 4
description tunnel-description
(Optional) Specifies a tunnel description.
Example:
Switch(config-if)# description headend tunnel
Step 5
Switch(config-if)# tp tunnel-name tunnel22
Specifies the name of the MPLS-TP tunnel. The TP tunnel
name is displayed in the show mpls tp tunnel command
output. This command is useful for consistently identifying
the tunnel at all endpoints and midpoints.
tp bandwidth num
Specifies the tunnel bandwidth.
tp tunnel-name name
Example:
Step 6
Example:
Switch(config-if)# tp bandwidth 10000
Step 7
tp source node-id [global-id num]
Example:
Switch(config-if)# tp source 10.10.11.11
global-id 10
(Optional) Specifies the tunnel source and endpoint. This
command is and not typically used, because the global
router ID and global ID can be used to identify the tunnel
source at the endpoint. All tunnels on the switch generally
use the same (globally specified) source information.
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-14
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 8
Command or Action
Purpose
tp destination node-id [[tunnel-tp num]
global-id num]
Specifies the destination node of the tunnel.
Example:
Switch(config-if)# tp destination 10.10.10.10
Step 9
Specifies the BFD template.
bfd bfd-template
Example:
Switch(config-if)# bfd mpls-tp-bfd-2
Step 10
Switch(config-if)# working-lsp
Specifies a working LSP, also known as the primary LSP.
This LSP is used to route traffic. This command enters
working LSP interface configuration mode
(config-if-working).
in-label num
Specifies the in label.
working-lsp
Example:
Step 11
Example:
Switch(config-if-working)# in-label 111
Step 12
Specifies the out label and out link.
out-label num out-link num
Example:
Switch(config-if-working)# out-label 112
out-link 1
Step 13
Exits from working LSP interface configuration mode.
exit
Example:
Switch(config-if-working)# exit
Step 14
protect-lsp
Example:
Switch(config-if)# protect-lsp
Step 15
Specifies a backup for a working LSP. If the working LSP
fails, traffic is switched to the protect LSP until the working
LSP is restored, at which time forwarding reverts back to
the working LSP. This command enters protect LSP
interface configuration mode (config-if-protect).
Specifies the in label.
in-label num
Example:
Switch(config-if-protect)# in-label 100
Step 16
Specifies the out label and out link.
out-label num out-link num
Example:
Switch(config-if-protect)# out-label 113
out-link 2
Step 17
Exits from protect LSP interface configuration mode.
exit
Example:
Switch(config-if-protect)# exit
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-15
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Configuring MPLS-TP LSPs at Midpoints
Note
When configuring the LSPs at the midpoint switchs, make that the configuration does not reflect traffic
back to the originating node.
1.
enable
2.
configure terminal
3.
mpls tp lsp source node-id [global-id num] tunnel-tp num lsp {lsp-num | protect | working}
destination node-id [global-id num] tunnel-tp num
4.
forward-lsp
5.
bandwidth num
6.
in-label num out-label num out-link num
7.
exit
8.
reverse-lsp
9.
bandwidth num
10. in-label num out-label num out-link num
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
mpls tp lsp source node-id [global-id num]
tunnel-tp num lsp {lsp-num | protect | working}
destination node-id [global-id num] tunnel-tp
num
Enables MPLS-TP midpoint connectivity and enters MPLS
TP LSP configuration mode.
Example:
Switch(config)# mpls tp lsp source 10.10.10.10
global-id 2 tunnel-tp 4 lsp protect destination
10.11.11.11 global-id 11 tunnel-tp 12
Step 4
forward-lsp
Enters MPLS-TP LSP forward LSP configuration mode.
Example:
Switch(config-mpls-tp-lsp)# forward-lsp
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-16
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 5
Command or Action
Purpose
bandwidth num
Specifies the bandwidth.
Example:
Switch(config-mpls-tp-lsp-forw)# bandwidth 100
Step 6
in-label num out-label num out-link num
Specifies the in label, out label, and out link numbers.
Example:
Switch(config-mpls-tp-lsp-forw)# in-label 53
out-label 43 out-link 41
Step 7
Exits MPLS-TP LSP forward LSP configuration mode.
exit
Example:
Switch(config-mpls-tp-lsp-forw)# exit
Step 8
Enters MPLS-TP LSP reverse LSP configuration mode.
reverse-lsp
Example:
Switch(config-mpls-tp-lsp)# reverse-lsp
Step 9
Specifies the bandwidth.
bandwidth num
Example:
Switch(config-mpls-tp-lsp-rev)# bandwidth 100
Step 10
in-label num out-label num out-link num
Specifies the in label, out label, and out link numbers.
Example:
Switch(config-mpls-tp-lsp-rev)# in-label 33
out-label 23 out-link 44
Configuring MPLS-TP Links and Physical Interfaces
MPLS-TP link numbers may be assigned to physical interfaces only. Bundled interfaces and virtual
interfaces are not supported for MPLS-TP link numbers.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface type/num
4.
ip address ip-address mask
5.
mpls tp link link-num {ipv4 ip-address | tx-mac mac-address} rx-mac mac-address
6.
ip rsvp bandwidth [rdm [bc0 interface-bandwidth] [[single-flow-bandwidth [bc1 bandwidth |
sub-pool bandwidth]]] [interface-bandwidth [single-flow-bandwidth [bc1 bandwidth | sub-pool
bandwidth]] | mam max-reservable-bw [interface-bandwidth [single-flow-bandwidth] [bc0
interface-bandwidth [bc1 bandwidth]]] | percent percent-bandwidth [single-flow-bandwidth]]
7.
exit
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-17
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
8.
exit
9.
show mpls tp link-numbers
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Switch# configure terminal
Step 3
Specifies the interface and enters interface configuration
mode.
interface type/num
Example:
Switch(config)# interface ethernet 1/0
Step 4
Assigns an IP address to the interface.
ip address ip-address mask
Example:
Switch(config-if)# ip address 10.10.10.10
255.255.255.0
Step 5
| tx-mac
Associates an MPLS-TP link number with a physical
interface and next-hop node. On point-to-point interfaces or
Ethernet interfaces designated as point-to-point using the
medium p2p command, the next-hop can be implicit, so the
Example:
Switch(config-if)# mpls tp link 1 ipv4 10.0.0.2 mpls tp link command just associates a link number to the
interface.
mpls tp link link-num {ipv4 ip-address
mac-address} rx-mac mac-address
Multiple tunnels and LSPs can refer to the MPLS-TP link to
indicate they are traversing that interface. You can move the
MPLS-TP link from one interface to another without
reconfiguring all the MPLS-TP tunnels and LSPs that refer
to the link.
Link numbers a must be unique on the switch or node.
Step 6
ip rsvp bandwidth [rdm [bc0
interface-bandwidth] [[single-flow-bandwidth
[bc1 bandwidth | sub-pool bandwidth]]]
[interface-bandwidth [single-flow-bandwidth
[bc1 bandwidth | sub-pool bandwidth]] | mam
max-reservable-bw [interface-bandwidth
[single-flow-bandwidth] [bc0
interface-bandwidth [bc1 bandwidth]]] | percent
percent-bandwidth [single-flow-bandwidth]]
Example:
Enables Resource Reservation Protocol (RSVP) bandwidth
for IP on an interface.
If you configure non-zero bandwidth for the TP tunnel or at
a midpoint LSP, make sure that the interface to which the
output link is attached has enough bandwidth available. For
example, if three tunnel LSPs run over link 1 and each LSP
was assigned 1000 with the tp bandwidth command, the
interface associated with link 1 needs bandwidth of 3000
with the ip rsvp bandwidth command.
Switch(config-if)# ip rsvp bandwidth 1158 100
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-18
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 7
Command or Action
Purpose
exit
Exits interface configuration mode.
Example:
Switch(config-if)# exit
Step 8
Exits global configuration mode.
exit
Example:
Switch(config)# exit
Step 9
Displays the configured links.
show mpls tp link-numbers
Example:
Switch# show mpls tp link-numbers
Configuring Static-to-Static Multisegment Pseudowires for MPLS-TP
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
l2 vfi name point-to-point
4.
neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
5.
mpls label local-pseudowire-label remote-pseudowire-label
6.
mpls control-word
7.
neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
8.
mpls label local-pseudowire-label remote-pseudowire-label
9.
mpls control-word
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Switch# configure terminal
Step 3
Creates a point-to-point Layer 2 virtual forwarding
interface (VFI) and enters VFI configuration mode.
l2 vfi name point-to-point
Example:
Switch(config)# l2 vfi atom point-to-point
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-19
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 4
Command or Action
Purpose
neighbor ip-address vc-id {encapsulation mpls |
pw-class pw-class-name}
Sets up an emulated VC. Specify the IP address and the VC
ID of the remote switch. Also specify the pseudowire class
to use for the emulated VC.
Example:
Note: Only two neighbor commands are allowed for each
l2 vfi point-to-point command.
Switch(config-vfi)# neighbor 10.111.111.111 123
pw-class atom
Step 5
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(config-vfi)# mpls label 101 201
Step 6
mpls control-word
Specifies the control word.
Example:
Switch(config-vfi)# mpls control-word
Step 7
neighbor ip-address vc-id {encapsulation mpls |
pw-class pw-class-name}
Sets up an emulated VC. Specify the IP address and the VC
ID of the remote switch. Also specify the pseudowire class
to use for the emulated VC.
Example:
Switch(config-vfi)#
Step 8
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(config-vfi)# Switch(config-vfi)# mpls
label 102 202
Step 9
mpls control-word
Specifies the control word.
Example:
Switch(config-vfi)# mpls control-word
Configuring a Template with Pseudowire Type-Length-Value Parameters
1.
enable
2.
configure terminal
3.
pseudowire-tlv template template-name
4.
tlv [type-name] type-value length [dec | hexstr | str] value
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-20
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
Enters global configuration mode.
configure terminal
Example:
Switch# configure terminal
Step 3
pseudowire-tlv template template-name
Creates a template of pseudowire type-length-value (TLV)
parameters
Example:
Switch(config)# pseudowire-tlv template
statictemp
Step 4
tlv [type-name] type-value length [dec | hexstr
| str] value
Specifies the TLV parameters.
Example:
Switch(config-pw-tlv-template)# tlv statictemp
2 4 hexstr 1
Configuring Static-to-Dynamic Pseudowires for MPLS-TP
When you configure static-to-dynamic pseudowires, you configure the static pseudowire class with the
protocol none command, create a dynamic pseudowire class, then invoke those pseudowire classes with
the neighbor commands.
1.
enable
2.
configure terminal
3.
pseudowire-class class-name
4.
encapsulation mpls
5.
control-word
6.
protocol none
7.
exit
8.
pseudowire-class class-name
9.
encapsulation mpls
10. exit
11. l2 vfi name point-to-point
12. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
13. neighbor ip-address vc-id {encapsulation mpls | pw-class pw-class-name}
14. mpls label local-pseudowire-label remote-pseudowire-label
15. mpls control-word
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-21
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
16. local interface pseudowire-type
17. tlv [type-name] type-value length [dec | hexstr | str] value
or
tlv template template-name
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
pseudowire-class class-name
Creates a pseudowire class and enters pseudowire class
configuration mode.
Example:
Switch(config)# pseudowire-class mpls-tp-class1
Step 4
encapsulation mpls
Specifies the encapsulation type.
Example:
Switch(config-pw-class)# encapsulation mpls
Step 5
control-word
Enables the use of the control word.
Example:
Switch(config-pw-class)# control-word
Step 6
protocol {l2tpv2 | l2tpv3 | none}
[l2tp-class-name]
Specifies the type of protocol. Use the protocol none
command to specify a static pseudowire.
Example:
Switch(config-pw-class)# protocol none
Step 7
exit
Exits pseudowire class configuration mode.
Example:
Switch(config-pw-class)# exit
Step 8
pseudowire-class class-name
Creates a pseudowire class and enters pseudowire class
configuration mode.
Example:
Switch(config)# pseudowire-class mpls-tp-class1
Step 9
encapsulation mpls
Specifies the encapsulation type.
Example:
Switch(config-pw-class)# encapsulation mpls
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-22
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 10
Command or Action
Purpose
exit
Exits pseudowire class configuration mode.
Example:
Switch(config-pw-class)# exit
Step 11
Creates a point-to-point Layer 2 virtual forwarding
interface (VFI) and enters VFI configuration mode.
l2 vfi name point-to-point
Example:
Switch(config)# l2 vfi atom point-to-point
Step 12
neighbor ip-address vc-id {encapsulation mpls |
pw-class pw-class-name}
Example:
Step 13
Switch(config-vfi)# neighbor 10.111.111.111 123
pw-class atom
Note: Only two neighbor commands are allowed for each
l2 vfi point-to-point command.
neighbor ip-address vc-id {encapsulation mpls |
pw-class pw-class-name}
Sets up an emulated VC. Specify the IP address and the VC
ID of the remote switch. Also specify the pseudowire class
to use for the emulated VC.
Example:
Note: Only two neighbor commands are allowed for each
l2 vfi point-to-point command.
Switch(config-vfi-neighbor)# neighbor
10.111.111.111 123 pw-class atom
Step 14
Sets up an emulated VC. Specify the IP address and the VC
ID of the remote switch. Also specify the pseudowire class
to use for the emulated VC. Enters config-vfi-neighbor
command mode.
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(config-vfi-neighbor)# mpls label 101 201
Step 15
Specifies the control word.
mpls control-word
Example:
Switch(config-vfi-neighbor)# mpls control-word
Step 16
local interface pseudowire-type
Specifies the pseudowire type and enters VFI neighbor
interface configuration mode.
Example:
Switch(config-vfi-neighbor)# local interface 4
Step 17
tlv [type-name] type-value length [dec | hexstr
| str] value
or
tlv template template-name
Specifies the TLV parameters or invokes a previously
configured TLV template.
Example:
Switch(config-vfi-neighbor)# tlv statictemp 2 4
hexstr 1
Example
l2 vfi atom point-to-point (static-dynamic MSPW)
neighbor 10.116.116.116 4294967295 pw-class dypw
neighbor 10.111.111.111 123 pw-class stpw
(dynamic)
(static)
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-23
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
mpls label 101 201
mpls control-word
local interface 4
tlv mtu 1 4 1500
tlv description 3 6 str abcd
tlv descr C 4 hexstr 0505
Configuring the L2VPN Pseudowire Redundancy for Static Pseudowires
Backed Up with Static or Dynamic Pseudowires
1.
enable
2.
configure terminal
3.
interface ethernet type/num
4.
service instance id ethernet
5.
encapsulation dot1q vlan-id
6.
xconnect peer-ip-address vc-id {encapsulation {l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name] [sequencing {transmit | receive | both}]
7.
mpls label local-pseudowire-label remote-pseudowire-label
8.
mpls control-word
9.
backup delay {enable-delay-period | never} {disable-delay-period | never}
10. backup peer peer-switch-ip-addr vcid [pw-class pw-class-name] [priority value]
11. mpls label local-pseudowire-label remote-pseudowire-label
12. mpls control-word
DETAILED STEPS
Step 1
Command or Action
Purpose
enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Example:
Switch> enable
Step 2
configure terminal
Enters global configuration mode.
Example:
Switch# configure terminal
Step 3
interface ethernet type/num
Specifies the interfaces and enters interface configuration
mode.
Example:
Switch(config)# interface ethernet 1/0
Step 4
service instance id ethernet
Specifies the service instance and enters service instance
interface configuration mode.
Example:
Switch(config-if)# service instance 1 ethernet
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-24
OL-26702-02
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Step 5
Command or Action
Purpose
encapsulation dot1q vlan-id
Enables the interface to accept 802.1Q VLAN packets.
Example:
Switch(config-if-srv)# encapsulation dot1q 10
Step 6
xconnect peer-ip-address vc-id {encapsulation
{l2tpv3 [manual] | mpls [manual]} | pw-class
pw-class-name} [pw-class pw-class-name]
[sequencing {transmit | receive | both}]
Binds the attachment circuit to a pseudowire VC and enters
xconnect configuration mode.
Example:
Switch(config-if-srv)# xconnect 10.109.10.10
123encapsulation mpls manual pw-class stpw
Step 7
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(cfg-if-ether-vc-xconn)# mpls label 100
150
Step 8
Specifies the control word.
mpls control-word
Example:
Switch(cfg-if-ether-vc-xconn)# no mpls
control-word
Step 9
backup delay {enable-delay-period | never}
{disable-delay-period | never}
Specifies how long a backup pseudowire virtual circuit
(VC) should wait before resuming operation after the
primary pseudowire VC goes down.
Example:
Switch(cfg-if-ether-vc-xconn)# backup delay 0
never
Step 10
backup peer peer-switch-ip-addr vcid [pw-class
pw-class-name] [priority value]
Specifies a redundant peer for a pseudowire virtual circuit
(VC). Enters backup xconnect configuration mode.
Example:
Switch(cfg-if-ether-vc-xconn)# backup peer
10.0.0.2 50
Step 11
mpls label local-pseudowire-label
remote-pseudowire-label
Configures the static pseudowire connection by defining
local and remote circuit labels.
Example:
Switch(cfg-if-ether-vc-xconn-bkup)# mpls label
100 150
Step 12
Specifies the control word.
mpls control-word
Example:
Switch(cfg-if-ether-vc-xconn-bkup)# no mpls
control-word
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
OL-26702-02
7-25
Chapter 7
Configuring MPLS Transport Profile
How to Configure MPLS-TP
Example
interface Ethernet1/0
no ip address
no shutdown
service instance 1 ethernet
encapsulation dot1q 10
xconnect 10.113.113.113 123 encapsulation mpls manual pw-class stpw
mpls label 0 101
mpls control-word
backup peer 1 0.120.120.120 124 pw-class stpw
mpls label 0 105
mpls control-word
Verifying the MPLS-TP Configuration
When the entire tunnel is programmed, use the following commands to verify and help troubleshoot the
configuration:
•
show mpls tp tunnel-tp lsps: To ensure that both LSPs are up and working from a tunnel endpoint.
•
show mpls tp tunnel-tp number detail: To help determine the cause if the tunnel is not up and
working.
•
show bfd neighbors mpls-tp: To display the state of BFD, which must be up for the endpoint LSPs
to be up.
•
trace mpls tp and ping mpls tp: To help isolate any connectivity issues.
•
debug mpls tp: To enable the display of MPLS-TP error messages.
•
logging (MPLS-TP): To enable the display of logging messages related to configuration changes or
state changes.
•
show mpls l2transport static-oam: To enable the display of MPLS-TP messages related to
pseudowires.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The
use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any
examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only.
Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011 Cisco Systems, Inc. All rights reserved.
Cisco ME 3800X and ME 3600X and ME 3600X-24CX Switch Software Configuration Guide
7-26
OL-26702-02
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement