GMPLS Config
GMPLS Config:
To configure GMPLS, you must complete the following tasks:
Configure the Link Management Protocol on page 241
Configure MPLS Label Switched Paths for GMPLS on page 244
Configure the Link Management Protocol
You need to configure the Link Management Protocol (LMP) to define the data channel
connection between devices at the [edit protocols link-management] hierarchy
[edit]
protocols {
link-management {
peer peer-name;
te-link te-link-name {
interface interface-name {
local-address ip-address;
remote-address ip-address;
remote-id id-number;
}
local-address ip-address;
remote-address ip-address;
remote-id id-number;
}
traceoptions {
file filename
<(world-readable | no-world-readable)>;
flag flag ;
}
}
}
Configure a peer name with the peer statement, the peer’s router ID with the address
statement, and the TE link associated with this peer with the te-link statement:
[edit]
protocols {
link-management {
peer peer-name {
address ip-address;
te-link te-link-name;
}
}
}
Using the the te-link statement parameters for LMP, you can define the data channel
connection between devices. You define all the te-link statement parameters, except for the
remote-id statements, at the [edit protocols link-management te-link te-link-name] and [edit
protocols link-management te-link te-link-name interface interface-name] levels.
We recommend that you configure a different IP address subnet for your TE-link addresses
than the subnet configured for your physical interfaces. This enables you to identify which
addresses are physical and which addresses belong to the TE-link.
The local ID for the TE-link is automatically assigned by LMP. It also assigns the
post-identifier and/or labels for the interfaces (resources) in the TE-link. The remote ID for
the interface needs to be configured, based on the post-ID assignment of the peer node at
the [edit protocols link-management te-link te-link-name interface interface-name] hierarchy
level.
To obtain the TE-link and interface local IDs, issue the show link-management te-link
command. Once you have these IDs, configure them as the remote IDs on the peer node.
The remote IDs at the [edit protocols link-management te-link te-link-name interface
interface-name] hierarchy level are needed for static mapping of remote labels to local labels.
To configure a TE-link, you configure the following statements at the [edit protocols
link-management] hierarchy level:
[edit]
protocols {
link-management {
te-link te-link-name {
interface interface-name {
local-address ip-address;
remote-address ip-address;
remote-id id-number;
}
local-address ip-address;
remote-address ip-address;
remote-id id-number;
}
}
GMPLS Configuration
243
As part of the configuration for GMPLS, you need to establish an MPLS path for each unique
device connected through GMPLS. Configure the TE-Link remote address as the address at
the [edit protocols mpls path path-name] hierarchy level. You should include the strict option
with the address.
See “Configure the Link Management Protocol” on page 241 for information about how to
obtain a TE-link remote address.
Configure the MPLS path as follows:
[edit]
protocols {
mpls {
path path-name {
address strict;
}
}
}
See “Create a Named Path” on page 46 for information about how to configure MPLS paths.
Trace LMP Traffic
To trace LMP protocol traffic, specify options with the global traceoptions statement at the
[edit routing-options] hierarchy level. You can specify LMP-specific options by including the
traceoptions statement at the [edit protocols link-management] hierarchy level:
[edit protocols link-management]
traceoptions {
file filename
<(world-readable | no-world-readable)>;
flag flag ;
}
Use the file statement to specify the name of the file that receives the output of the tracing
operation. All files are placed in the directory /var/log.
The following trace flags display the operations associated with the sending and receiving of
various LMP messages:
all—Trace all available operations
init—Output from the initialization messages
parse—Operation of the parser
process—Operation of the general configuration
route-socket—Operation of route socket events
routing—Operation of the routing protocols
Configur e MPLS Label Switched P aths for GMPLS
server—Server processing operations
show—Show command servicing operations
Each flag can carry one or more of the following flag modifiers:
detail—Provide detailed trace information
receive—Packets being received
send—Packets being transmitted
Configure MPLS Label Switched Paths for GMPLS
To enable the proper GMPLS switching parameters, configure the LSP attributes that are
appropriate for your network connection. The default values, which are also appropriate for
standard MPLS, are psc-1 for switching-type.
You configure the LSP attributes statements at the [protocols mpls label-switched-path
lsp-attributes] hierarchy level.
Note that Constrained Shortest Path First (CSPF) is not available for GMPLS. As a result, you
must configure the no-cspf statement for LSPs carrying GMPLS traffic.
[edit]
protocols {
mpls {
label-switched-path lsp-name {
from ip-address;
to ip-address;
primary path-name;
secondary path-name;
no-cspf;
lsp-attributes {
gpid type;
signal-type type;
switching-type type;
}
}
}
}
}
52network,wjunjmt
http://www.52network.cn.st
http://www.52network.hk.st
一起走入网络世界！
