Section 3 · Module 2 · Page 1

All Rights Reserved © Alcatel-Lucent 2008
Issue 02
Do not delete this graphic elements in here:
All Rights Reserved © Alcatel-Lucent 2008
Module 2
Network Configuration
Issue 02
Section 3
Operation
Alcatel-Lucent GMRE+ASON
Operation Rel.3.2
3FL35093AAAAZZZZZ Issue Ed02
Section 3 · Module 2 · Page 2
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 2
Blank Page
This page is left blank intentionally
First edition Belgard, Steffen 2006-06-01 01
Remarks Author Date Editi
on
Document History
Section 3 · Module 2 · Page 3
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 3
Module Objectives
Upon completion of this module, you should be able to:
Get to know what has to be considered before configuring a ASON
Learn how to configure the control plane
Learn how to configure the data plane
Explore the creation of drop ports
Enter the creation of UNI-ports
Section 3 · Module 2 · Page 4
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 4
Module Objectives [cont.]
This page is left blank intentionally
Section 3 · Module 2 · Page 5
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 5
Table of Contents
Switch to notes view!
Page
1 Preliminary Considerations 7
1.1 Network Partitioning Guidelines 8
1.2 IP Address assignment 9
1.3 Warning 10
1.4 GMRE Interface Instances 11
1.5 Interface states 13
1.6 Interface indexes 14
1.7 Recommended Interface Index Ranges 15
1.8 Summarize Test 16
2 Control Plane Configuration 17
2.1 Control Plane Interfaces 18
2.2 Interface IPTunnel 19
2.3 Interface RSVP NNI 20
2.4 Interface RSVP UNI 21
2.5 Interface DPR 22
2.6 Interface LMP 23
2.7 Interface Deletion 24
2.8 Config Node 25
2.9 Exercise 26
3 Data Plane Configuration 27
3.1 Data Plane Interfaces 28
3.2 Interface Databearer 29
3.3 Config Interface Databearer – STM-N 30
3.4 Config Interface Databearer – GbE 31
3.5 Interface TE-Link 33
3.6 Interface TE-Link Exchange 34
3.7 Exercise 35
4 Drop ports 36
4.1 Overview 37
4.2 SDH drop port 38
4.3 Ethernet drop port 39
4.4 Exercise 40
5 UNI-N port 41
5.1 Configuration 42
Section 3 · Module 2 · Page 6
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 6
Table of Contents [cont.]
Switch to notes view!
This page is left blank intentionally
Section 3 · Module 2 · Page 7
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 7
1 Preliminary Considerations
Section 3 · Module 2 · Page 8
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 8
1 Preliminary Considerations
1.1 Network Partitioning Guidelines
Large networks should be divided into multiple Domains
The maximum number of nodes per domain is restricted to 50
Location of all network interfaces (I-NNI, E-NNI, UNI, Drop ports) should
be clear
METRO 1
METRO 2 CORE Domain 1
Client 1
UNI
E-NNI
UNI
Client 2
Client 3
Client 4
I-NNI
TNA 1
TNA 41
TNA 2
TNA 3
Drop
Ports
E-NNI
Drop ports
UNI
Section 3 · Module 2 · Page 9
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 9
1 Preliminary Considerations
1.2 IP Address assignment
On Board LAN switch
DCR EM
DCC
Server
Disc
Backpanel LAN
(ISSB)
Management Bus
(to/from I/O boards)
Q3
Q3
Customer DCN
Operation System
FLCCONGI
On Board LAN switch
DCR EM
DCC
Server
Disc
FLCSERV Disc
Matrix LO Copy B
SC
Matrix LO Copy A
SC
Matrix HO Copy A
SC
Matrix HO Copy B
SC
ActiveEM
ActiveDCR
NodeAddress
GMRE Node Address (Control plane protocol addresses)
A non-routable (32 bit netmask, point to point) IPv4 address is used by the RSPV-TE, OSPF-TE and LMP
protocols on each GMRE node
The recommended IP address is <GMRENodeAddressSubnet>.<NodeNr> (e.g. 10.10.255 for
GMRENodeAddressSubnet) with netmask 255.255.255.255
GMRE Signaling Notify address
A routable Ipv4 address is used in addition by the RSVP-TE protocol for fast failure reporting from point
of failure to Ingress node directly (not hop by hop)
On the 1678 MCC, this is normally the ‘activeDCR’ address
GMRE Management interface address
The GMRE’s MTNM and CLI interfaces require an IPv4 address which is reachable from the NMS
On the 1678 MCC, this is normally the ‘activeEM’ address
On each node where the GMRE is installed, the three assigned addresses are retrieved by the GMRE using
(host) name resolution.
The following three entries must be present in the ‘/etc/hosts’ file, e.g. for Node Nr. 33
10.10.255.33 gmreNode
10.10.33.12 activeDCR
10.10.33.14 activeEM
Section 3 · Module 2 · Page 10
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 10
1 Preliminary Considerations
1.3 Warning
The GMRE stores information in persistency.
Once the GMRE applications have been activated, the GMRE Node and
Notify addresses cannot be changed easily.
If it is necessary to change or correct the IP Addresses, either
ALL GMRE nodes have to be stopped and their persistency is deleted, or
Contact Alcatel Product Support Center (PSC) and they can carry out the
numerous manual steps necessary
Warning
Careful planning and preparation is recommended !!
Section 3 · Module 2 · Page 11
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 11
1 Preliminary Considerations
1.4 GMRE Interface Instances
NE B
NE A
STM-4
STM-4
STM-4
STM-16
STM-16
STM-16
Data Bearer
Data Bearer
TE-link #2
STM-4
STM-4
STM-4
STM-16
STM-16
STM-16
GMRE 2 GMRE 1
Routing
Signaling
Link Mgmt
RSVP
DPR
LMP
IP Tunnel
(IP Control Channel)
TE-link #1
Routing
Signaling
Link Mgmt
GMRE Interface Instances:
are common configuration attributes that apply to more than one entity
are done once and ‘re-used’ by others (as Underlying Interface)
This prevents cumbersome CLI commands
Reduces errors and inconsistencies
Allows configuration of default values for attributes
Control Plane interfaces:
IP Tunnel: Specifies the control plane IP neighbor connectivity
RSVP: Specifies the UNI or NNI Signalling neighbor, uses IP Tunnel
DPR: Specifies Data Plane Routing neighbor, uses IP Tunnel
LMP: Specifies LMP neighbor, uses IP Tunnel
Section 3 · Module 2 · Page 12
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 12
1 Preliminary Considerations
1.4 GMRE Interface Instances [cont.]
NE B
NE A
STM-4
STM-4
STM-4
STM-16
STM-16
STM-16
Data Bearer
Data Bearer
TE-link #2
STM-4
STM-4
STM-4
STM-16
STM-16
STM-16
GMRE 2
Routing
NNI Signaling
Link Mgmt
GMRE 1
Routing
NNI Signaling
Link Mgmt
RSVP
DPR
LMP
IP Tunnel
(IP Control Channel)
TE-link #1
Data Plane interfaces
Databearers:
Specifies the STM capability as well as the local and remote interface “addresses”.
“addresses” (not IPv4) are derived from hardware position (rack-subrack-slot-port-channel)
TE-Links:
Specifies the TE parameters (e.g. SRG, Link Metric) for the Databearers.
Uses Databearers and can also bundle them together.
Section 3 · Module 2 · Page 13
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 13
1 Preliminary Considerations
1.5 Interface states
All GMRE interfaces have the following two states:
AdminState: the administrative state set by the Operator
The following values can be configured :
UP = enabled, take into service
DOWN = disabled, take out of service
Entities can be modified or deleted only if their AdminState is set to DOWN first
OpState: the operational state of the entity
Is set by the GMRE and depends on various events, alarms, neighbor state,
etc.
The values displayed can be :
UP = normal, no problems
DOWN = inactive, alarm,
DEG = degraded, partially operational
Section 3 · Module 2 · Page 14
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 14
1 Preliminary Considerations
1.6 Interface indexes
All GMRE configured interfaces have a node-wide unique identifier:
(IfIndex)
Databearer interface index values (or names) cannot be freely assigned.
They are fixed, 8 digits and determined by their physical location
according to the following rule: RSBBPPCC, where
R = Rack number 1 ≤ R ≤ 9
S = Shelf number 1 ≤ S ≤ 9
BB = Board number 01 ≤ BB ≤ 99
PP = Port number 01 ≤ PP ≤ 99
CC = Channel number 01 ≤ CC ≤ 99
All other configurable interface indexes can be freely assigned by the
Operator
Section 3 · Module 2 · Page 15
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 15
1 Preliminary Considerations
1.7 Recommended Interface Index Ranges
To ease operation and maintenance, the following recommendations
are stated in the Network Configuration Guide
IpTunnels: 2000 + Neighbor Node Nr
RSVP-TE NNI: 3000 + Neighbor Node Nr
RSVP-TE UNI: 4000 + Neighbor Node Nr
DPR: 5000 + Neighbor Node Nr
LMP: 7000 + Neighbor Node Nr
TE-Link: 100000 ≤ n ≤ 999999
This enables, amongst others, for example CLI commands to be applied
to all similar instances
gmre1[3][0]# set adminState Down 3000-3020,5000-5020
Section 3 · Module 2 · Page 16
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 16
What is the maximum recommend number of nodes to
be in an ASON?
25 35 50 73 100
Please link the corresponding terms together!
Data Bearer
RSVP Link Management
OSPF Signaling
TeLink I/O Interfaces
LMP Routing
DPR
Where is the following SDH interface situated?
13020101 Rack:___ Shelf:___ Board:___ Port:___
1 Preliminary Considerations
1.8 Summarize Test
Section 3 · Module 2 · Page 17
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 17
2 Control Plane Configuration
Section 3 · Module 2 · Page 18
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 18
2 Control Plane Configuration
2.1 Control Plane Interfaces
There are basically 4 protocol interfaces:
RSVP NNI
RSVP UNI
DPR Routing (mandatory for non-UNI)
LMP Link Mgmt (mandatory for Auto Discovery)
Each of them need some common definitions, which are defined in
another interface type (UnderlyingIf) to save configuring the same
information N times
Hint
The IP Tunnels have to be configured first, because they are the
underlying interfaces for the controlplane.
Section 3 · Module 2 · Page 19
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 19
2 Control Plane Configuration
2.2 Interface IPTunnel
Use ? To view
parameters
Mandatory parameters
are indicated
Encapsulation
IPMinimal (default), should be userd for I-NNI interfaces
NoEncapsulation, should be used for UNI or E-NNI interfaces
RemoteAddress
The remote GMRE node address
Section 3 · Module 2 · Page 20
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 20
2 Control Plane Configuration
2.3 Interface RSVP NNI
Use ? To view
parameters
Mandatory parameters
are indicated
E-NNI: External NNI
I-NNI: Internal NNI
NNI_STAR: deprecated
SPCENDPOINT: Soft Permanent Connection Endpoint (Drop port)
Section 3 · Module 2 · Page 21
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 21
2 Control Plane Configuration
2.4 Interface RSVP UNI
Use ? To view
parameters
Mandatory parameters
are indicated
RSVP UNI: RSVP Signaling for User Network Interface
Section 3 · Module 2 · Page 22
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 22
2 Control Plane Configuration
2.5 Interface DPR
Use ? To view
parameters
Mandatory parameters
are indicated
OSPF Type:
E_NNI: Routing to other networks
I_NNI: Routing in the ASON
Section 3 · Module 2 · Page 23
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 23
2 Control Plane Configuration
2.6 Interface LMP
Use ? To view
parameters
Mandatory parameters
are indicated
Used protocol:
RawIp
UDP
RawIp is a software interface that allows to send own IP packets through the network.
UDP – User Datagram Protocol, works on IP to send connectionless datagrams
Note: LMP the LMP interface is not used in release 3.2
Section 3 · Module 2 · Page 24
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 24
2 Control Plane Configuration
2.7 Interface Deletion
Any GMRE interface can be deleted
Administrative state
The administrative state must be set DOWN to delete GMRE interfaces.
Set adminState down
Occuring Alarm
Deletion of Interface
Section 3 · Module 2 · Page 25
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 25
Node Adminstate is the master activation switch.
If this is DOWN (initial state) the Adminstate of all other interfaces are
ignored
All other interfaces with Adminstate up are activated
AutoMode: AutoDiscovery Mode
Off, Managed, Full
2 Control Plane Configuration
2.8 Config Node
Node Adminstate
The node Adminstate can never be set to DOWN
Section 3 · Module 2 · Page 26
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 26
2 Control Plane Configuration
2.9 Exercise
Configuration of the control plane
Therefore configure the following interfaces to your neighbor
nodes.
IP Tunnel
RSVP
DPR (OSPF)
Please remember numbering conventions corresponding to the
different interfaces
Section 3 · Module 2 · Page 27
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 27
3 Data Plane Configuration
Section 3 · Module 2 · Page 28
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 28
3 Data Plane Configuration
3.1 Data Plane Interfaces
There are 2 basic types:
Databearers
TE-Links
Provide Traffic Engineering attributes to Databearers
Can bundle many Databearers into one TE-Link with common TE attributes
Have Databearers as Underlying Interface(s)
The Databearer interfaces should be configured before TE-Links
TE Link information is used by the Data Plane Routing to build the network topology
for LSP route calculations
The DPR interfaces should be configured before TE-Links
Data Plane Configuration
The dataplane must be configured after the control plane!
Section 3 · Module 2 · Page 29
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 29
3 Data Plane Configuration
3.2 Interface Databearer
Use ? To view
parameters
Mandatory parameters
are indicated
ACD (Access Control Domain) Value is used for multiple Manager sharing of NE resources
GMREPort
RMPort
SharedPort
Client Type
Ethernet
HighOrder (STM-N)
LinkType:
E_NNI
I_NNI
SPCEndpoint (Drop port)
UNI
RemoteIfIndex <integer>
The remote interface index
TeLinkIfIndex
The according TeLink interface index
LocalAddress <IP4value>
The assigned interface’s unique IP address (for numbered interfaces)
Note: will be deprecated in future release when Numbered Interface are no longer supported
Section 3 · Module 2 · Page 30
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 30
3 Data Plane Configuration
3.3 Config Interface Databearer – STM-N
Available resources
Example:
If one VC4 is allocated with priority 3, there will be 63 available with priority 3, 4 and 5.
Due to that, 64 VC4 will be still available with priority 1 and 2.
Section 3 · Module 2 · Page 31
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 31
3 Data Plane Configuration
3.4 Config Interface Databearer – GbE
Concatenation
To transmit GBEthernet through the network VC have to be
concatenated. Therefore the consecutive data bearers have to be
configured.
gmre1(3)[0]# config interface DataBearer 12190301 LinkType SPCENDPOINT ClientType Ethernet
acdValue SharedPort AdminState Up
12190301 - Successfully configured.
gmre1(3)[0]#
gmre1(3)[0]# config interface DataBearer 12190302 LinkType SPCENDPOINT ClientType Ethernet
acdValue SharedPort AdminState Up
12190301 - Successfully configured.
gmre1(3)[0]#
GbE interfaces are not ‘seen’ in the GMRE until they are configured.
Dynamic configuration via the GMRE is not supported in the currently available release.
GbE ports must be virtually concatenated via the 1353 CT/NM to up to 7 VC4 depending on bandwidth
requirements
Each one of the VC4 end points must be configured in the GMRE using the last 2 digits to specify which
VC4 (I.e. 1st, 5th or 7th)
For each one of the VC4, an LSP must be setup
In the current GMRE release, GbE services are normally provided and managed by the Alcatel 1354 RM ASON
Manager.
The following CLI commands are not required if managed by 1354 RM
Section 3 · Module 2 · Page 32
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 32
3 Data Plane Configuration
3.4 Config Interface Databearer – GbE [cont.]
gmre1(3)[0]# show interface DATABEARER 12190302
IfIndex: 12190302
IfName: 01–2–19–03
IfType: DataBearer
LocalAddress: –
RemoteNodeAddress: –
RemoteIfAddress: –
TeLinkIfIndex : 0
IfSpeed: 155 Mbps
LinkType: SPCEndpoint
ACDValue: SharedPort
AdminState: Up
OperState: Up
MuxCapability: –
MinimumServiceType: VC4
AvailableServices: priority 1 2 3 4 5
VC4 1 1 1 1 1
VC4-4c
VC4-16c
VC4-64c
ProtectionType: Unprotected
AutoDiscState: Undiscovered
NumSecLastAdminUp: 254591 sec
NumOpStateChanges: 3
ClientType: Ethernet
TimeLastOpStateChange: Thu Dec 16 15:34:52 2004
Available resources
Section 3 · Module 2 · Page 33
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 33
3 Data Plane Configuration
3.5 Interface TE-Link
Use ? To view
parameters
Mandatory parameters
are indicated
Bundletype: True | False
DprIfIndex: <integer>
Encoding: SDH_SONET
FlexibleCapable: True | False
RemoteIfIndex <integer | IPv4>
RemoteNodeAddress: <IPv4>
TeMetric: <integer>
TnaAddress: <IPv4>
Note: The underlying interface is the databearer not the IPTunnel as mentioned in the help.
Section 3 · Module 2 · Page 34
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 34
3 Data Plane Configuration
3.6 Interface TE-Link Exchange
E-NNI
UNI
UNI
UNI
UNI
TNA
TNA: Transport Network Assigned Address
The TNA has to be exchanged between Customers and Providers or Providers and Providers to enable access
to the network.
Furthermore is represented by an IP address, which is assigned to a TE-Link. It has to be unique in the
whole network.
Section 3 · Module 2 · Page 35
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 35
3 Data Plane Configuration
3.7 Exercise
Configuration of the data plane
Therefore configure the following interfaces to your neighbor
nodes, please
Databearer
TeLink
Section 3 · Module 2 · Page 36
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 36
4 Drop ports
Section 3 · Module 2 · Page 37
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 37
4 Drop ports
4.1 Overview
Drop port
Ethernet
Drop port
ASON
Non-ASON
network
Ethernet
network
A drop port provides end-points for soft permanent connections (SPC) services.
It is located at the edge nodes of a GMRE domain (ASON).
Drop port alarms are ignored since its traffic can not be restored.
The set of linkType to "SPCEndpoint„ is mandatory.
Section 3 · Module 2 · Page 38
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 38
4 Drop ports
4.2 SDH drop port
Link Type
Section 3 · Module 2 · Page 39
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 39
4 Drop ports
4.3 Ethernet drop port
Link Type
Client Type
Ethernet drop ports are similary configured like SDH drop ports. Differences are:
The Gigabit Ethernet TPs must be pre-configured via CT/NM to map the VC4 channels.
Gigabit Ethernet databearers are not seen in the GMRE CLI until they have been configured via CLI.
The ClientType attribute must be specified to "Ethernet".
Section 3 · Module 2 · Page 40
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 40
4 Drop ports
4.4 Exercise
Configuration of drop ports
Therefore configure SPC endpoints according to the training
manual
Section 3 · Module 2 · Page 41
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 41
5 UNI port
Section 3 · Module 2 · Page 42
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 42
5 UNI port
5.1 Configuration
IP,RSVP
Databearer, TE-Link
Ethernet drop ports are similary configured like SDH drop ports. Differences are:
The Gigabit Ethernet TPs must be pre-configured via CT/NM to map the VC4 channels.
Gigabit Ethernet databearers are not seen in the GMRE CLI until they have been configured via CLI.
The ClientType attribute must be specified to "Ethernet".
Section 3 · Module 2 · Page 43
All Rights Reserved © Alcatel-Lucent 2008
Issue 02
All Rights Reserved © Alcatel-Lucent 2008
Alcatel-Lucent GMRE+ASON · Operation Rel.3.2
Operation · Network Configuration
3 · 2 · 43
End of Module
Network Configuration

Sign up to vote on this title
UsefulNot useful