5-configure the ne with 1320ct commparameterconfig_vnr_ed00_32_vnese

Section @@SECTION @@SECTIONTITLEAll Rights Reserved © Alcatel-Lucent 2008
Mô un 3
3JK11477AAAAWBZZA Issue 1
· 1320 CT V3.X Operation
5 · *
Khi hoàn thành mô un này, bn có th:
Cu hình trao i thông tin và nh tuyn các tham s phc v giám sát toàn b mng t OS
Section 1 · Module 3 · Page *
All Rights Reserved © Alcatel-Lucent 2008
5 · *
This page is left blank intentionally
5 · *
Page
1.1 Stacks overview 8
1.3 NSAP address definition 10
1.4 Three ways to reach an OSI NE 11
2 Local configuration 13
2.1 Local configuration 14
3 LAPD configuration 15
3.2 LAPD Configuration for SDH Network Element 17
3.3 LAPD Configuration for WDM Network Element 19
4 Ethernet configuration 21
4.1 L2 parameter 22
5 OS configuration 25
5.1 OS configuration 26
6 RAP/MESA configuration 27
6.2 RAP configuration 29
6.3 MESA configuration 30
7.1 Introduction 32
7.3 Stacks and layers relations 34
7.4 OSPF area description 35
7.5 IP static routing configuration 36
7.6 Configuration steps 37
8 ISA board supervision from 1320 CT 39
8.1 Step #1 _ Get or set the Point-To-Point IP address 40
8.2 Step #2 _ Set the ISA board IP address 41
8.3 Step #3 _ OSPF area management 42
8.4 Step #4 _ IP over OSI management 43
8.5 Step #5 _ Check the IP stack configuration 44
8.6 Step #6 _ Check the IP stack state 46
8.7 Step #7 _ Realign ISA board population 47
8.8 Step #8 _ Start the ISA board supervision 48
8.9 Step #9 _ Open the ISA board “Equipment view” 49
8.10 Trouble shooting 50
9.1 OSI over IP: Why ? 54
9.2 Setting the OSI over IP tunnel in the NE 55
9.3 Setting the GNE interface IP address in the NE 56
9.4 Setting OSI over IP tunnel in the CT 57
9.5 Checking the IP stack state over LLMAN 58
9.6 IP static routing configuration 59
6 Alcatel Network Time Protocol 61
10.1 ANTP overview 62
10.3 NE time 64
11 NE Autodiscovery 67
11.1 NE autodiscovery 68
5 · *
Page
5 · *
5 · *
QB3*
X.216
X.215
Abbreviation and Acronym (cf. Section 2 Module 1 of the 1320 CT student guide)
OSI Layer 1 to layer 3 provide routing of OSI management information in the Data Communication Network (DCN).
The Physical layer provides the bit transfer over the physical medium (Coaxial cable, optical fibre,…). The most frequency used protocol for local area network (LAN) is Ethernet (10 Base 2, 10 Base T), which may be used for OSI and TCP/IP traffic in equally.
The Data Link Layer transfer data between network entities and detect errors that may occur in the Physical layer. Broadcast connections like Ethernet run the LLC (Logical Link Control) Protocol. Point-to point connection like ECC Channel run LAPD protocol.
The Network Layer provides routing and delivering of data packets to any node in the network. It can be divided into two main parts:
The basic part of forwarding data packets from one node to the next node based on the information in the node's local forwarding database. This part is specified by the CLNP.
The advanced part of automatically creating and updating the local forwarding database used by the first part. This part is specified by ES-IS and IS-IS protocols.
This layer manages the NSAP (Network Service Access Point) address.
The Transport Layer provides an end-to-end connection. This layer is specified by ISO 8073.
The Session Layer provides the session management, e.g. opening and closing of sessions.
The Presentation Layer translates the data from the session layer to the application layer and provides a standard interface for the application layer.
The Application Layer provides specific services dedicated to NE and server software packages.
5 · *
1.2 Thông tin và nh tuyn vùng trong OSI DCN
L1
L2
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L1
L2
= NE h tr IS-IS
Partitioning into Routing Domains
During the TMN design process, a network is partitioned into domains; each domain consists of a collection of two types of nodes:
Nodes supporting the IS-IS protocol; these nodes are called adaptive routers.
The IS-IS protocol allows automatic network (re)configuration by dynamically building routing tables.
Nodes not supporting this protocol; these nodes are called static routers.
Network partitions consisting of the former type of node are called adaptive routing domains; network partitions consisting of the later type of node are called static routing domains.
Moreover, nodes which have to take routing decisions are called Intermediate Systems (ISs), all others are called End Systems (ESs).
Partitioning into Routing Subdomains
In order to reduce the overhead associated with distributed adaptive routing, it may be useful to divide an adaptive routing domain into smaller routing subdomains, called areas or level 1 subdomain. In one area, we can find different type of nodes:
Level 1 Intermediate Systems (L1 ISs) for every node pertaining to an area.
Level 2 Intermediate Systems (L2 ISs) for every node which act as boundary ISs between areas. These ISs act as L1 ISs with respect to their own area and as L2 ISs with respect to other areas.
5 · *
1.3 nh ngha a ch NSAP
Mt a ch NSAP mô t toàn din mt v trí duy nht trong môi trng OSI (nó phi là duy nht i vi thit b c th)
a ch NSAP gm hai phn :
IDP: nh ngha cu trúc a ch
DSP: phn a ch
IDP Initial Domain Part
39 identifies an ISO DCC (Data Country Code) (ANSI format)
47 identifies an ISO6523 ICD (GOSIP format)
49 identifies the local format of variable lenght (from 16 to 40 characters).
IDI Initial Domain Identifier
710F:RSA 826F:UK 840F:USA
RSD Reserved
Area Area Identifier
ID System Identifier (useful for using the MAC address as the ID field, but this is not mandatory)
SEL NSAP Selector: provides the distinction among users of the network service
for further information on NSAP refer to RFC1629, for example, at http://www.alternic.org/rfcs/rfc1600
NSAP
IDP
DSP
AFI
IDI
DFI
ORG
RSD
RD
Area
ID
SEL
5 · *
Vn chuyn
3
LLMAN (Lower layers MANager) is Alcatel-Lucent proprietary.
OS (Operation System) includes at least 1353 NM software application
- When the Ethernet interface is activated, the Network Element becomes GNE (Gateway Network Element). In that case, the Ethernet interface is identified by its own MAC address. Refer to the next pages for more details : “Ethernet interface configuration”.
Note (1): LAPD (Link Access protocol channel D) is in charge of layer 2 data processing.
In case of SDH NE, the Physical layer represents DCC bytes (D1-D3 and/or D4-D12) in the SDH frames over coaxial or optical cable
In case of WDM NE, the Physical layer represents DCC bytes (D1-D3 and/or D4-D12) in the OSC (Optical Supervisory Channel) frames over optical cable
OSI over IP communication can be used to reach a given NE. This particular case is described in the next pages.
5 · *
5 · *
5 · *
T bng tng quan thit b:
1) Chn
Local Configuration
2) Thit lp cu hình và xác nhn li bng Ok
In the « Local Configuration » window, the following fields are present:
Local Address
Presentation Selector (P Sel.) identifies a presentation entity at the location identified by the NSAP Address.
Section Selector (S Selector) identifies a section entity at the location identified by the NSAP Address.
Transport Selector (T Sel.) identifies a transport entity at the location identified by the NSAP Address.
NSAP (Network Service Access Point) Address identifies a location in the network.
Synonymous Area Address – Optional
This section allows to have multiple synonymous area addresses within a level 1 subdomain. The compilation of the two network addresses is optional and if they are inserted, the last two fields, System Id and Network selector, of the mandatory address and of the synonymous addresses must be the same.
System Type
This section determines whether the local NE acts as a « Intermediate System Level 1 » or as a « Intermediate System Level 2 » or as a « End System ». Note that a level 2 intermediate system performs functions of a level 1 too.
NB: After modifying the local configuration, the NE restarts automatically.
5 · *
5 · *
MS
RS
RS
MUX
MUX
REG
LAPD: Link Access Protocol channel D
The CT communicates with remote NEs through the DCC (Data Communication Channels) that support QECC protocol.
It is suggested (but not mandatory) to follow a predetermined order for the Network/User sequence in the complete network.
Two groups of DCC can be configured in case of SDH network (as an example):
D1-D3 RsTTP: DCC in RSOH
D4-D12 MsTTP: DCC in MSOH
5 · *
T tng quan thit b:
Configuration Comm/Routing
5 · *
T ca s trc ó :
Nhn nút Create
Ca s (to giao din LAPD) xut hin:
Nhn Choose chn TP liên quan n LAPD (RST hoc MST)
Chn vai trò (Network or User)
Chn giao thc
Regarding the LAPD protocol, all former Alcatel equipment have been designed to support connection oriented mode, so effectively the option has been introduced for interworking with some particular "not fomer Alcatel equipment", that support only connection-less protocol; former Lucent equipment are just one case of this situation, because they have the possibility to enable or disable the LAPD, but is only connection-less.
When “Connection-less” is used, the Role of the LAPD interface must be set as “Network”.
5 · *
5 · *
5 · *
L2
L2
NE
No
5 · *
T tng quan thit b:
1) Chn Configuration
Interfaces Configuration
Ethernet Configuration
2) Thit lp cu hình và xác nhn li bng nhn Apply
Ethernet Interface
This field allows to define or remove a Local Area Network (LAN) port for the access to the Data Communication Network (DCN). When you disable the Ethernet interface, the CPU restart.
MAC Address
This section displays the address of the NE in the Ethernet LAN only if Ethernet Interface is enabled. It is a read only field.
OSI Section
L2 Only Parameter
This field indicates if the port can be used for level 2 traffic only, thus avoiding transmitting L1 packets. Note that the flag shall be set to No if some other nodes (NEs or OSs) of the same area are connected to the Ethernet LAN.
L1 Default Metric is a not modifiable field, Priority field can be set (default value for Ethernet is 64)
L2 Default Metric is a not modifiable field, Priority field can be set (default value for Ethernet is 64)
IP Section
This section allows to define the IP Address, the IP Mask and the Routing IP Protocol of the Ethernet Interface; if OSPF or Both options are selected, also the Associated OSPF Area must be set.
5 · *
5 · *
5 · *
1)Chn Configuration
OS Configuration
2) Thit lp cu hình và xác nhn li bng nhn Ok
This window allows to configure the addresses of the Main and Spare OS that have to manage the NE.
Main/Spare OS Address
This section contains the same type of information than the one in the Local Configuration dialog-box.
5 · *
5 · *
5 · *
6.1 Tng quan ANTP
One common Time Basis is necessary when locating any alarm :
To perform the adequate diagnosis about the origin of the error and the triggering element.
To avoid and limit unexpected consequences in case of failure.
To retrieve one global and faithful view of the network by determining all simultaneous events.
ANTP (Alcatel Network Time Protocol) is one adaptation on OSI layer 3 CLNP of the native NTP which
allows to have a very precise real time clock alignment between the NEs and a reference source (ANTP
server, normally located on NMS).
The behavior is very simple and is based on a periodic enquiry by the client (NE) in order to discover
the current time and date on the server (NM).
This mechanism allows to calculate round trips delays and average statistical values to obtain the best real time alignment between client and server.
The unique goal of ANTP is to keep synchronized the NE with the reference clock servers, independently of the accuracy of the reference source. This mechanism guarantees the alignment of the OS and NE clocks.
A global solution is to have a network synchronized not only internally but also with external time reference systems (e.g. GPS). In this scenario, ANTP protocol is in charge of distributing the clock to the Network Elements, getting this clock from a UNIX based Workstation. It’s then up to native NTP protocol to distribute the clock within the Operation Systems, getting the Real Time Clock from a GPS external device. In conclusion, the clock is distributed by one WS likely the OS itself) to the NE using ANTP protocol.
In order to be resilient against DCN or WS failures, two ANTP servers are present in the management network, one of them having higher priority. In case one of them fails, the NE shall automatically refer to the other one. Only a double ANTP servers’ failure, or a failure in the related DCN, will let the NEs working with RTC in free–running. In general, the two ANTP servers do not have to be located in the same station, even if they can.
5 · *
6.2 Cu hình máy ch NTP
cu hình máy ch FTP:
Configuration Comm/Routing NTP Server Configuration
This dialog-box allows to configure the addresses of the Main and Spare NTP (Network Time Protocol) Servers reachable by the NE, used for time distribution in the network. The following fields are present :
Enabling NTP protocol section allows to enable (Yes) or disable (No) the NTP protocol.
Main NTP Server Address section contains the same type of information than the one into the Local Address section in the Local Configuration dialog-box.
Spare NTP Server Address section contains the same type of information than the one into the Local Address section in the Local Configuration dialog-box.
If the NTP server is coincident with the OS (same hardware), the OS NSAP address must be assigned.
5 · *
6.3 Thi gian NE
Configuration NE Time
ng thi quan sát: biu tng NTP, màu sc và hình dáng
NTP Status
NTP Protocol = Disabled or Enabled; it depends on Enabling NTP Protocol setting (No or Yes) in NTP Server Configuration window.
NTP Main/Spare = Unreachable or Reachable; it depends on the connection with the NTP Servers whose addresses are written in NTP Server Configuration window.
Time
NE Time refers to the NE
OS Time refers to the PC
Set NE Time With OS Time put the NE Time equal to the OS Time; it is a manual command and is available only if NTP Protocol is disabled.
5 · *
6.4 Cu hình ANTP t môi trng CT
Hai phng thc kh dng:
ANTP Client mode
Time : NE CT
ANTP Server mode
Time : CT NE
The ANTP component is able to provide both the ANTP–client and ANTP–server role at the same time.
The ANTP is configurable inside the CT to cover one role or both depending on need as follows:
The Enable Client mode: when selected, the CT receives the time from the NE
The Enable Server mode: when selected, the CT transmits the time to the NE
5 · *
6.4 Cu hình ANTP t môi trng CT
Thit lp giao thc thi gian mng ALcatel t môi trng CT
The “ANTP client” part of the window display two fields for the Server network addresses Main and Spare
subdivided in “Area Address” and “System Identifier”.
Click OK to apply the ANTP configuration parameters
The ANTP option is disabled (greyed) if the ANTP component is not installed.
The ANTP component is inside the Lower Layer manager software component that is a software layer of the CD–ROM.
The Enable Client option is absent in the view when the operator using the CT has not privilege to set the NE time.
The privilege is always available for operators belonging to ”Administrators” or ”Power Users”.
The specific Right is called ”Change the system time”.
For the ANTP Server address automatic management there are two operating mode:
when selected, the previously selected Enable Client and Enable Server are operative. After the “Start” of the “Supervision”, the NE and CT times are automatically controlled as described in the “details on Automatic Controls” in the following. Automatic assignment of the Main ANTP Address option gives the opportunity to have the Craft Terminal time synchronized with the local NE you are plugged in: after each Start Supervision on the local NE its NSAP address is written in the ANTP Settings so that it will be used as the source of the time.
when not selected, the Start up only behaviour is enable i.e., the CT starts only the ANTP component but the Enable Client and Enable Server selections are not operative and no automatic control of the NE and CT time is made. See ANTP configured by the user.
When a Start Supervision request is completed, the CT gets the NE time and compares it with the PC time.
If the difference is lower than 1 day, the CT assumes that the NE and CT have both an acceptable time and the difference is due to clock misalignment. In this case the CT will realign the PC time with the NE time.
If the difference is higher than 1 day, the CT assumes that the NE or the CT has unacceptable time difference. In this case the operator is informed with a Time Mismatch report.
5 · *
NSAP
IDP
DSP
AFI
IDI
DFI
ORG
RSD
RD
Area
ID
SEL

5-configure the ne with 1320ct commparameterconfig_vnr_ed00_32_vnese

Documents