Professional Documents
Culture Documents
ADD-DROP MULTIPLEXER
MULTIPLEXEUR ADD-DROP
A 155 MBIT/S COMPACT
ADR155C P5.2
Installation and User Guide / Guide d'Installation et d'Utilisation – 288 091 808-02
Sagem Communication document. Reproduction and disclosure prohibited
Document Sagem Communication. Reproduction et divulgation interdites
Page 0-2
COMPACT 155 MBIT/S
ADD-DROP MULTIPLEXER
ADR155C P5.2
The subrack must be mounted only in racks with a bottom part that is closed
) or fitted with a class V1 or HF1 or better air filter, or that stand on a non-
flammable floor.
) Handling precaution: For any work to be carried out inside the equipment, an
antistatic wrist strap must be worn.
1
Safety Extra Low Voltage Circuit
PACKAGING
The presence of the logo (green dot) means that a contribution is paid to an approved
national organisation to improve packaging recovery and recycling infrastructures.
To facilitate recycling, please respect the sorting rules set up locally for this kind of waste.
BATTERIES
If your product contains batteries, they must be disposed of at appropriate collection points.
THE PRODUCT
The crossed-out waste bin stuck on the product (or on its accessories) means that the
product belongs to the family of electrical and electronic equipment.
In this way you can participate in the re-use and upgrading of Electrical and Electronic Equipment
Waste, which can have an effect on the environment and human health.
ENVIRONMENT.......................................................................................................................A0-3
CONTENTS.................................................................................................................A0-4 to A0-8
4. SPECIFICATIONS............................................................................................................................ 4-1
Figure 2-1 - Synchronization from the 2 MHz external sync input (T3) .............................................. 2-20
Figure 2-2 - Synchronization from a 2 Mbit/s port............................................................................... 2-20
Figure 2-3 - Remote loopback function (registering alarms on central site)....................................... 2-21
TABLES
1.1 - Generalities
The ADR155C is an optical STM-1/STM-4 add-drop multiplexer used to build STM-1/STM-4
point-to-point links, STM-1 or STM-4 rings, or mesh networks with conduct (SNC) or STM-1 line
(MSP) protection, so performing the conveyance of PDH links at 2 Mbit/s, 34 or 45 Mbit/s, of
SDH STM-1 links, of 10/100 Mbit/s Ethernet links.
Management network connections are performed via DCC D1-D3 or D4-D12 of the STM1 or
STM-4, via VC12_192K (compatible mode ADR2500C or ADR2500 eXtra) of the STM1 or STM-
4 or on Ethernet (ETH) interfaces of the equipment.
For the connection of the different ports of cards, see § 1.3 - Connecting ports
Remark :
The informations concerning the STM1-1G optical cards that can be inserted, recognized and
managed therefore by the system, are defined in the User Guide N56717020108 of January
2005.
A B
F
E
C M D
Left uprights
of rack
ADR 155C
ADR 155C ETSI rack
19" rack
76,2 76,2
mm mm
2U
2U
SYNC E1 OUTPUT
SYNC E1 OUTPUT
2 2
Two M6x12 Two M6x12
1 HM screw 1 HM screw
Two M6 Two M6
cage nuts cage nuts
19" rack mounting ETSI rack mouting
1.2.1 - Generalities
The ADR155C subrack can be mounted in a 19" or ETSI rack. (see Figure 1-2 - ADR155C
Subrack Installation)
The ADR155C package is provided with a mounting kit to adapt the subrack to a 19" or ETSI
rack.
This kit contains :
two brackets for adaptation to the rack,
4 screws M3x4,
4 flat washers M3
8 screws CBLXS M3x6 to attach optional cards
The mounting kit for installation of the subrack on the uprights of the rack, containing 4 cage
nuts and 4 screws M6x12, is not supplied with the subrack.
The ADR155C has, in option, a system of thermal control by ventilation ; during the installation,
provide for sufficient space for the ventilation aperture on the left of the subrack, and also for the
aeration, at the top and right of the subrack. On the other hand, never hinder the natural air
convection on the right side.
Perform the following operations :
provide a 2U place in the rack for each equipment and a 1U space between equipments.
Deflectors are recommended to limit the temperature of the ambient air around the
equipment.
secure the attaching brackets for mounting in 19" rack, on either side of the subrack,
clip, on either side of the rack, two M6 cage nuts (item 1),
position the subrack back in front of the rack,
slide the subrack until attaching brackets are in contact with uprights, opposite the 4 cage
nuts, and then secure the subrack with 4 M6x12 hex head screws (item 2).
Installation of cards
RECALL : Prior to any operation on the cards, the operator must be provided with an
antistatic bracelet.
ADR155C slots are non-dedicated. However, in order to make wiring easier and ensure the
homogeneity among sites, it is advisable to proceed as follows :
position the tributary cards from C slot clockwise
position the agregate cards from D slot counter-clockwise
check the ventilation module presence in its reserved slide if the configuration requires it.
This module is mandatory as soon as :
a GFP150 card is inserted in the shelf
the shelf is at an ambient temperature out of class 3. 2 of ETS 300019 : between 45°C
and 55°C.
This module can only be set out if no GFP150 card is inserted in the shelf.
the ADR155C shelf is provided with the mothercard and, according to the chosen options,
with FAN module and Holdover card already inserted.
Secure each card through M3 screws of Torx type (6-branch star), using a suited screwdriver
FACOM reference AZX.10X75
Or STANLEY reference 1-67-494
The ADD/DROP mode is the only one available (no terminal mode with line protection)
The B and D slots are, in this case, dedicated to STM-4 cards. In case of only one STM-4
card utilization, the second slot can however be used by another type of card.
Only one STM-1 channel can be extracted from the STM-4 flow, the three other one being in by-
pass ; the choice of this channel is selected by the menu "AU-4 Selection" of the STM-4 card.
The cards can be extracted without intervening on the other cards or on their connections.
The connections to be performed on the equipment depend on the chosen configuration :
Connection requirements :
Ö For a right distribution of cords on either side of the subrack, the connections of slots A and
C, the 21x2Mbit/s access ports and synchronization access of the mothercard are oriented
leftward. All other connections are oriented rightward.
Ö The run of cords must not hinder the extraction of a module; in particular, connecting cables
of the left subrack half is to be secured to the frame with enough backlash to enable the
ventilation module (optional) to be extracted during a maintenance operation.
Refer to the list of available cables in chapter 3 - Spare parts and Cables.
PWRA/B PWR
Figure 1-3 – Connecting motherboard
Ö "PWR" and "PWRA" and/or "PWRB" Power supply ports can be connected simultaneously
provided that the OB of PWRA/PWRB is not joined to the electrical ground (mechanical
ground).
Ö Always connect the equipment side before the energy source side.
Ö The power block must be installed far from any heat source, and no traction must be
exercised on its connecting wires.
Ö The used cable to connect the power block to the energy source must have a minimal
section of 1,5 mm² and be qualified <HAR> H03 VV_F ou <HAR> H03 VVH2_F.
Ö The connecting land between the power block and the energy source must be respected.
Ö The connecting electrical installation must be realized according to the present national
standard.
Input voltage One or two Safety Extra Low Voltage (SELV) type – 48V sources
Voltage range allowed : - 36 V to - 60 V
Maximum voltage range : - 36 V to - 72 V
Power 100 VA maximum
Connector Male 9-way HE5
5 1
9 6
"LOOPS" Interface :
Ports 4 remote indication inputs for floating contacts (Local user inputs),
biased to -48 V internally, active when closed and with electrical
isolation (loop current = from 1 to 10 mA),
2 dry loop outputs (common, normally closed and normally open)
M C B
(Local user outputs) for station alarm or remote control use
(maximum current = 100 mA on resistive load). The common point
of each loop is internally connected to OB ; by default, the loop A is
normally open and the loop B is normally closed.
(Schematic diagram of a dry loop)
NOTE : OB is the result of a logical "OR" between signals OBJ, OB1 and OB2 on the "PWR", "PWRA" and
"PWRB" power supply interfaces.
"COMM" Interface :
5 1
9 6
Wiring diagram
1 1
6 6
9
5 9
5
"ETH" Interface :
Pin 1 Pin 8
Front view
"SYNC" Interface
Ports Two G.703 2MHz external synchronization inputs (T3) and two
G.703 2MHz clock outputs (T4) compliant with ITU-T G.703
Recommendation (§ 13.3 for input port, § 13.2 for output port)
Impedance 120 Ω balanced
Connector Female 9-way HE5 (120 Ω).
5 1
9 6
Pin N° Signal name Comments
1 GND Ground
6 TX1 RING (T4-) Output T4-1 (cold point)
2 TX1 TIP (T4+) Output T4-1 (hot point)
7 RX2 TIP (T3+) Input T3-2 (hot point)
3 RX1 TIP (T3+) Input T3-1 (hot point)
8 RX1 RING (T3-) Input T3-1 (cold point)
4 RX2 RING (T3-) Input T3-2 (cold point)
9 TX2 RING (T4-) Output T4-2 (cold point)
5 TX2 TIP (T4+) Output T4-2 (hot point)
NOTA : The shielding of the connector case is connected to the subrack front panel ground
The 75 Ω ohm unbalanced interfaces are obtained by adding a cable which also provides BNC
connectors.
This interface uses two connectors : E1 INPUT connector for inputs (named RX) and
E1 OUTPUT connector for outputs (named TX)
15 1
30 16
44 31
NOTA : The shielding of the connector case is connected to the subrack front panel ground
10 TOFPB (+) Transmit mode byte sync output indicating the positioning of bit 1
3 TOFPA (-) and sent on the rising edge of clock T64 (B-A)
11 RB (+) Output for data extracted from SDH line and sampled on the falling
4 RA (-) edge of clock R64 (B-A)
12 ROFPB (+) Receive mode byte sync output indicating the setting of bit 1 and
5 ROFPA (-) sent on the falling edge of clock R64 (B-A)
Pin 1 Pin 8
Front view
3 TB (+) Input for data to send over the SDH line and sampled on the rising
6 TA (-) edge of clock T64 (B-A)
4 T64B (+) 64 kHz clock accompanying the transmit data T(B-A) . Input in
5 T64A (-) codirectional mode and output in contradirectional master mode.
7 R64B (+) 64 kHz clock output accompanying the receive data R(B-A)
8 R64A (-)
Timing diagram for the "EOW/AUX" interface in contra-directional mode (64 kbit/s
synchronous use) :
T64 (B-A)
(transmit clock output)
T (B-A) B8 B1 B2
(input for data to transmit
over STM1/STM4 line)
TOFP (B-A)
(transmit synchro byte
pulse output
Only for STM4 and ERE)
R64 (B-A)
(receive clock output)
R (B-A)
(output for data received B8 B1 B2
from STM1/STM4 line)
ROFP (B-A)
(receive synchro byte
pulse output
Only for STM4 and ERE)
As EOW / AUX port is physically integral with Optical modules, operating the order wire /
auxiliary channel with MSP protection requires the use of a "Y" cord electrically connecting the
signals of EOW / AUX connectors.
TR REC
EOW / AUX
TR REC
EOW / AUX
Likewise, in order to ensure a good behavior during the changeover from one module to the
other, the operator should take care to keep identical configurations on both Optical cards ; in
case of modification, automatic recopy is done and a warning message appears.
Only the connections are not identical. There must be no connections on the "Protection"
module, as in all the connections are made to the "Working" module.
More over, the management links (PPP over DCC) must be created on the « Working » module
and not on the « Protect » module.
This cord is gotten by linkage of two Sub-D / RJ45 adapters cords on one "Y" cord.
As EOW and AUX ports are physically integral with Electrical modules, operating the order wire
and auxiliary channels with MSP protection requires the use of a "Y" cord electrically connecting,
one by one, identically, the signals of EOW and AUX connectors.
Likewise, in order to ensure a good behavior during the changeover from one module to the
other, the operator should take care to keep identical configurations on both Electrical cards ; in
case of modification, automatic recopy is done and a warning message appears.
Only the connections are not identical. There must be no connections on the "Protection"
module, as in all the connections are made to the "Working" module.
More over, the management links (PPP over DCC) must be created on the « Working » module
and not on the « Protect » module.
"ETH" Interface :
Pin 1 Pin 8
Pin 8 Pin 1
2 Mbit/s traffic connections (75Ω or 120Ω according to the card), performed on "E1 INPUT" and
"E1 OUTPUT" ports on the 21E120, 21E75, 21E1R8 card are identical with those performed on
"E1 INPUT" and "E1 OUTPUT" ports on the front side of the motherboard (see § 1.3.1.5)
LOCAL TEST
Equipment Inventory
- 48 V redundancy Check
* case of underequipped
Local transmission test (30 mn) *
unitary equipment
Optical connection
Configuration Elaboration
yes
Link established
Optical measurements
Counters reset
24 H link Performance
Equipment operational
(constitution of installation file)
Configuration Save
1.4 - Commissioning
This paragraph describes the Equipment commissioning at general way. For more details, see
the chapter 5 "Startup Guide".
The equipment can be operated from a PC fitted with VT100 emulation and HTTP Web
browser; its minimum configuration is defined in the paragraph 5.2 of "Startup Guide"
A local terminal with VT100 emulation is indispensable during the first commissioning, in order
to be able to access the equipment via the management function ; however, this terminal only
enables the communication function to be parameterized (definition of the equipment IP
address).
Procedure.
) On the first commissioning, the equipment scans its constitution and considers it as the
expected configuration, in service, monitored. It is thus advisable to insert the traffic cards
before power-up, in order to speed up the commissioning.
) Switch on the power supply connected to the equipment.
) The equipment conducts self-tests :
When self-tests have run correctly, the "ON" indicator is lit,
In the opposite case, an indicator flashing code defines the faulty self-test (contact the
Hotline).
) Parameterize the communication interface, using the VT100 (see § 1.4.3).
) Using the HTTP Web browser, (see § 1.4.4).
Update the equipment time and date
Configure the remote management ports using the Web browser
) Connect the 2 Mbit/s, 34/45 Mbit/s, Ethernet, Fast Ethernet, STM-1, STM-4 and SYNC
ports, according to the required equipment composition,
) Connect the AUX and EOW ports required.
) Download a predefined configuration or prepare the desired configuration, using the HTTP
Web browser :
Create the connections
Establish the wished protection (MSP protection, SNC protection ...)
Choose the synchronization source, and change its parameters if required.
Change, if necessary, the monitoring parameters and the alarms configuration.
The default configuration of the various parameters is provided by § 2.3.
) Conduct the tests on STM-n links, complying with the process described in Figure 1-12
) From that moment, the equipment is operational.
) Operating alarms can signal a wrong connection of interfaces. Check the connection of
ports, the alarms corresponding to the connected ports, and correct any problems that may
arise.
) Save configuration.
REMARK : It is possible, once the commissioning is performed, to connect additional 2 Mbit/s G.703,
E3/DS3, Ethernet,STM1 or STM-4 ports, and to insert or extract powered cards.
IONOS
D 4 - D 12
D1 - D 3
STMn
STMn
on West
on East
D 4 - D 12STMn
HTTP on East
E P
ADR T
H
R P
P
D 1 - D 3 STMn
S NMP on West
IONOS is necessary
to operate this FOT C D1 - D 3 D1 - D 3 D1 - D 3
(but the ADR can be on STMn STMn STMn
operated from the ETH tributary on East on West
interface of the FOT C
PP P
FOT C * S H
D1 - D 3
N T
on STMn
aggregate M R T ADR
E P P P
T
H
R P
P
ETH
SNMP
The VC12_192K management mode is compatible with those of ADR2500C and ADR2500
eXtra ; it is configurable via HTTP.
The transparency functionality of the DCC flows (D1-D3, D4-D12) allows to transport, in an ADR
network, the management flows in transparency of another operator by using the DCCr (D1-
D3).
The DCCm of ADR155C are not compatible with those of ADR2500C or ADR2500 eXtra ; their
rates are different.
The transparency of the DCC is independent of the protection mechanisms. The operator must
use a mechanism of routage to protect its path of DCC.
The transparency of the DCCr and DCCm is only configurable by HTTP and is always bi-
directional
The system of transparency does not go up alarm or information on the state of the transported
flow.
Figure 1-13 presents the available resources and various configurations possible for the
communication function :
1. Connect the "COMM" access to a free "COM" port on the PC with VT100 emulation.
2. Switch on the PC.
3. If it is the first time you run the "Hyperterminal"application on this PC :
successively select, in the Windows desktop, the Start, Programs, Accessories and
Hyper terminal buttons,
select the icon representing the "Hyperterminal"application : a description window for
the application is displayed.
enter a name and choose an icon for the connection, then validate your choices : a new
window is displayed.
select the "COM" port on the PC which is connected to the equipment then validate your
choice. A new window is displayed :
configure the port parameters as indicated below :
Bits per second : 19200
Data bits :8
Parity : none
Stop bits :1
Flow control : none
validate the configuration.
save the connection ("Save" command in application File menu).
NOTE : The next time you want to open the "Hyperterminal" application, you will simply
need to choose the connection icon to connect to the equipment. Once the equipment is
powered up, the operation menu is displayed.
to exit the "Hyperterminal" application, select Exit in the File menu.
4. Open a session and enter your password (to configure the communication function, you
need to have "supervisor" rights)
NOTE : by default, for the initial commissioning procedure, the password is empty.
To select a command, type the command number in the "Choice ?" text area and press the
"ENTER" key to validate your choice.
The IP address must be different from that of the other equipment and must be defined in a
different subnetwork of the one of the Ethernet.
The default value 000.000.000.000 corresponds to no configuration of the IP address.
When the IP address exists and is modified, equipment REBOOT is proposed. This REBOOT
operates itself without affecting the trafic.
Error message : "Equipment address is mandatory" : the equipment address is mandatory
when at least one PPP link is not numbered.
The above screen presents an Ethernet communication interface with its characteristics :
"Interface State" : choice of interface state : 0 (Interface off) or 1 (Interface on).
"IP Address" : IP address.
"Subnet mask" : sub-network mask.
"Route Protocol" : protocol : 0 (None), 1 (RIP) or 2 (OSPF)
The addresses of the gateway and no gateway equipment must be defined in different
subnetworks.
When the IP address exists and is modified, equipment REBOOT is proposed. This REBOOT
operates itself without affecting the trafic.
This command is used to immediately reboot the application and restart with the parameters
already stored in the equipment.
This REBOOT is performed with no impact on the traffic.
Once the parameter definition process is completed, this command closes the current session.
An automatic session exit is performed after a few minutes if no activity is detected (this time
period can be configured using the manager).
The screen displays the management routes already defined with their characteristics :
¾ Hops : hop 1, 2, 3…Path used to go from one machine to another.
1 2 3
¾ Unit. size : Maximum size of IP packet which can reach the remote equipment.
IE 5.0 configuration
NOTE : It is preferable not to have a cache with the IE 5.0; otherwise, you are never sure to
have updated data when the screen opens.
1. In the Internet Explorer Tools menu, click Internet options.
2. In the General tab, click Parameters.
3. Tick the radio button : On each page visit, then define the disk space to be used for
1 Mbyte. Click [OK].
4. In the Temporary Internet files tab, click Delete Files.
5. Tick Delete all offline content, then click [OK].
6. In the Internet options dialog box, click [OK], then close the IE browser to allow the
options to be acknowledged.
With IE 6. 0, it is possible to configure the level of confidentiality, that is to say the choice of the
cookies type that is allowed to copy on the target PC. To open the ADRs, it is necessary to let
the parameter of confidentiality of Internet to the default value "Medium" for the access to the
Web sites.
With IE6. 0 and a PC equipped of Windows XP SP2, the installed Center of Security modifies
the manner of which IE displays the HTTP windows. In order to correctly open an ADR, it is
necessary to untick the parameter "Block pop-ups" of the tab " Privacy" of IE properties .
In the same way, the installed Center of Security blocks the program Tftpd32 used by the ADRs
for the Upload and the Download. On the warning window , to click on the button "Unblock" : this
action adds the program tftpd32 in the list of exceptions.
Remark
After an upgrade of the application code, the cache must be cleared as following :
In the Internet Explorer "Tools" menu click "Internet Options / General tab / Temporary Internet
files tab / Delete Files".
Tick "Delete all offline content", then click "OK".
Then close and start again the Browser.
PC Configuration
To get a correct date for the equipment HTTP, the environment variable "TZ" must not be
defined. To list all environment variables, type "Set" in the MS DOS console.
To get a correct display of HTML pages, fonts must not be defined as "large" in display
properties of the configuration panel.
The PC is connected via Ethernet (the PC's gateway must be in the same subnetwork as the
Ethernet interface of the ADR).
On session opening on the HTTP Web browser, the " Shelf View" screen represents the
equipment global view, where each slot is marked with a letter, A, B, C, D, E, F or M for
mothercard, according to the following screen.
The connectors inside in-alarm modules are colored according to the severity of the most
serious alarm
present and configured out of service modules include an icon representing a red cross to
indicate this administrative status
present and configured on maintenance modules include an icon representing a caution to
indicate this administrative status
Absent modules configured out of service appear as all black panel.
the coloration of LEDs is dynamic. Their meaning is specified to § 2.5
For each function viewed, the configuration parameters, operating commands, active
parameters and alarm states are grouped together on the same screen, with the various actions
possible being accessible or not by the operator according to his/her clearance level.
The upper edge of the Web browser window recalls the equipment name, its IP address, the
clearance level acquired and, if required, the slot concerned.
LOGIN
2. OPERATION
2.2 - Generalities
The ADR155C operation and maintenance are carried out :
- either directly on the equipment, through the front panel indicator lights and two engineering
management loops (loops A and B),
- or from a PC fitted with Web browser,
- or from a network manager, using the SNMP protocol for the network and supervision
aspects, and the included Web browser
Configuration constraints
When configuring the name (Equipment > Name menu), you are limited to using upper and
lower case characters, numbers, the space and the – and _ characters.
Accented characters and certain special characters will not be displayed on the VT100 interface.
Configuration parameters
NOTE :
1) The functional blocks naming, configuration parameters and their default value, noted
"XXXXXX", are displayed on Web browser.
2) The default values are indicated when a connection is created.
"Sf/Sd priority"
SF/SD priority according to Recommendation G.783 [1994] annex A.1.2.1 "Low"
possible value :"high" or "low" (compatibility with MXA)
Path trace expected, received and transmitted for VC3 (J1 Byte) or VC12
(J2 Byte)
- "Trace Expected" (configurable) "UNNAMED VC"
+ CRC7
- "Trace Received" (displayed in the same mode as 'Expected')
- "Trace sent" (16 bytes) "UNNAMED VC"
+ CRC7
"TIMdis" TIM (Trace Identifier Mismatch) enable or disable clicked (no TIM)
LAN1 Card
Ethernet port configuration (exclusive choice)
"LAN Interface"
Choice of the "Automatic" (with autonegotiation) or "Manual" LAN interface : 100Mbps Full
10 Mbps/Half Duplex, 10 Mbps/Full Duplex, 100 Mbps/Half Duplex, Duplex
100 Mbps/Full Duplex.
In "Automatic" the capabilities represent the local capacities of the
equipement that are negotiated with the remote equipment. The result of
this autonegotiation is visualisable in the Status " field ".
In "Manual" no autonegotiation, the "Status" field reflects the operator
configuration.
In order to have a correct link, it is recommended to configure both local
and remote equipment Ethernet interfaces with the same configuration :
- "Automatic" on both side or
- "Manual" and same duplex/speed configuration on both side
Note : in "Automatic" mode, if the remote equipment is set to "Manual",
local interface automatically switches to half duplex.
Flow control (multi point mode only)
- LAN towards VC3_# i 60 %
- VC3_# i towardsVC3_# j or LAN 60 %
Interface configuration
- LAN in service / no service Service
- Maximum route Age 300 s
- LAN interconnection mode (point to point over 2VC3/multipoint) multi-point
-
"TIMdis" TIM (Trace Identifier Mismatch) enable or disable clicked (no TIM)
SETS : Synchronous Equipment Timing Source
Synchronization Sources
Synchronization T0
"Name"
Choice of 2 Mbit/s port number for T2 source "1"
(1 port per enabled 2 Mbit/s card)
"SSM"
Use of synchronization status messages (SSM) "True"
"Quality Provided" (when "SSM" is "False")
Quality level of synchronization sources :
- "PRC" (Primary Reference Clock), T3 : PRC
- "SSUT" (Synchronization Supply Unit Transit), T1 : DNU
- "SSUL" (Synchronization Supply Unit Local), T2 : SEC
- "SEC" (Synchronization Equipment Clock),
- "DNU" (Do Not Use).
"T0 Priority"
T0 priority Table, according to enabled sources ; "P1" for T3_1
possible values : P1 to P7 (P1 have the most priority) "Dis" for T3_2
and T2_M
"P2" for others
"LOS Severity" Minor for T3
Alarm severity associated to the source status . Warning for T1
and T2
"Mode"
Synchronization operating mode
Choice between "Automatic" and "Free-run" "Automatic"
"Overheat Avoidance" :
Fan is ON, if Tamb°> 35°C (95°F)
Fan is OFF, if Tamb° ≤ 30°C (86°F)
Synchronization
Synchronization of the local and remote equipment is managed in accordance with the available
synchronization sources, their quality and the priority assigned to each.
The possible synchronization sources include :
standalone operation (holdover* or local oscillator mode),
T1 extracted from one of the incoming STM-n streams (1 to 4 possibilities according to the
number of Optical cards present in the equipment),
T2 : one 2 Mbit/s G.703 source per declared 2 Mbit/s module, and selected from the various
2 Mbit/s G.703 accesses
T3_1 and T3_2 : two external 2 MHz G.703 sources
Until 60s can be necessary after a source selection to validate the holdover mode.
Holdover mode is available when an holdover card is inserted in extension slot. If there is no
card or if it is defective then standalone operation is assume only by local oscillator
NOTE : On creation of an MSP protection, the « Protection » link inherits the configurations of
the « Working » link and therefore, in particular,those of synchronization.
The Synchronization screen summarizes the status of the timing obtained from the
traffic link under the « Working » interface reference.
The following figures give typical synchronization examples according to equipment connections.
2 MHz external
sync input (T3):
- Quality = PRC,
- Priority = 1.
STM-n port (T1-C): STM-n port (T1-C):
- Quality = DNU - Quality = DNU
- Priority = 2. - Priority = 2.
ADR155C 1 ADR155C 2
ADR155C 3 Synchronization
of other equipments
SSM = PRC
T0 = T1-c
Synchronization
of other equipments
Figure 2-1 - Synchronization from the 2 MHz external sync input (T3)
ADR155C 3 Synchronization
of other equipments
SSM = SEC
T0 = T1-c
Synchronization
of other equipments
NOTE : Synchronization is applied to the 2 Mbit/s port of the ADR155C which is enabled first
(local ADR155C in the example).
Loops Management
On remote sites, two local outgoing loops (Local user outputs A and B) are activated on the
appearance of a local equipment alarm or remote indication loops 3 and 4 (Local user input #3
or #4).
The remote loopback function allows an equipment named "central site", to register faults
present on remote sites.
This function requires each site to transmit to the central site an alarm presence message. This
messages which corresponds to remote monitoring loopback 1 or 2 (Local user input #1 or #2)
is transmitted in the S1 byte. To link this message to equipment's alarms, the outputs of the A
and B loops (Local user outputs A and B) should be connected to remote monitoring loops 1 and
2 (Local user input #1 or #2) respectively.
Data chaining in a bus or ring type network architecture is provided by "OR" function validation
between the data received (Far user inputs #1 et #2) via S1 STM-n West and S1 STM-n East,
and local data, for each site in the network.
At the "central site" equipment, "OR" function validation between the data received (Far user
inputs #1 and #2) via S1 STM-n West and S1 STM-n East, and local data (Local user input #1 or
#2 and local alarm), enables local alarm loopbacks to be activated (Local user outputs A and B).
To configure the remote loopback function, the following parameters should be programmed :
"Line remote loopback" and " central site". The Figure 2-3 gives an example of remote
management of the local outgoing loops according to the equipment connections.
NOTE 1 : When Local User #1 and #2 gather major / critical and minor alarm informations (local
user outputs A and B) it is necessary to give them a "warning" severity in order to avoid
permanently activation.
NOTE 2 :Status of incoming loops (Local user inputs #1 to #4), far incoming loops (Far user
inputs #1 to #2) and outgoing loops (Local user outputs A and B) may be displayed on
Web browser.
Ö "STATUS" indicator light on all cards except the Motherboard and the FAN :
Green LED Red LED Meaning
On Off Card in service
On On Card in service and in alarm
Off Off Hardware default on card (fuse)
Off On Card out of service
Flashing Self-test default
Ö Pushbuttons :
Designation Location Role Action initiated
"ACK" Motherboard Alarm Pressing disables the outgoing alarm
acknowledge loops. The visual alarm is kept.
"INIT Motherboard Configuration "Factory" Configuration reload
CONFIG"(*) reload
(*) To activate "INIT", keep button pressed for at least 5 seconds. This button is
inaccessible (and unused) in normal operation. It is necessary to remove the cover to
access it.
An alarm of gravity "major" or "critical" activates the major outgoing loops of the "POWER"
connector of the mothercard.
An alarm of gravity "minor" activates the minor outgoing loops of the "POWER" connector of the
mothercard.
An alarm of gravity "warning" does not activate any outgoing loop (available on HTTP).
(*)This alarm is raised when the "Automatic" mode and the "Pause" capability are selected and
the Pause status = No Pause (the remote equipment has refused the negotiation of Pause).
(***)These alarms are indications of state of the path elaborated for the network manager in
supplement of faults indications ; of this fact 2 indications can be transmitted in logs for only
one default.
Correlation of faults
A correlation mechanism is implemented on all faults detected.
This correlation mechanism, implemented on each change of information collected, is used to
eliminate faults induced by other faults to facilitate fault finding and fault locating.
The following tables define the faults that are masked for each fault detected in the system..
Key :
: The fault concerned on the current line is masked by the fault in the current
X
column.
For example : The LOF fault is masked by fault 2 (LOS).
FAULTS 1 2 3 4 5 6 7 8 9 10
FAULTS TF LOS LOF TIM EBER AIS EBER- SD-B2 RDI REI
-B1 B2
1 TF
2 LOS
3 LOF X
4 TIM X X
5 EBER-B1 (RS- X X X
EBER)
6 AIS (MS-AIS) X X X X
7 EBER-B2 (MS- X X X X X
EBER)
8 SD-B2 X X X X X X
9 RDI (MS-RDI) X X X
10 REI (MS-REI) X X X X
FAULTS 1 2 3
FAULTS PAM SCM OTM
1 PAM
2 SCM X
3 OTM X
Correlation of AU faults
The AU faults are masked by the STM-n LOS, LOF and AIS (MS-AIS) faults.
The TU-LOM fault is filtered, if there is no configured VC12 connection on this STM-n.
FAULTS 1 2 3 4 5 6 7 8 9 10
FAULTS AU-AIS AU-LOP UNEQ TIM RDI REI PLM TU-LOM EBER SD-
-B3 B3
1 AU-AIS
2 AU-LOP
3 UNEQ (VC4 UNEQ) X X
4 TIM X X X
5 RDI (VC4 RDI) X X X X
6 REI (VC4-REI) X X X X X
7 PLM (HPT) X X X X
8 TU-LOM X X X X X
9 EBER-B3 (VC4) X X
10 SD-B3 (VC4) X X X
FAULTS 1 2 3 4 5 6 7 8 9
FAULTS TU-AIS TU-LOP UNEQ TIM RDI REI PLM EBER SD
1 TU-AIS
2 TU-LOP
3 UNEQ X X
4 TIM X X X
5 RDI X X X X
6 REI X X X X X
7 PLM (LPT) X X X X
8 EBER- X X
9 SD X X X
FAULTS 1 2
FAULTS LOS AIS
1 LOS
2 AIS X
The LOA, LFD, LOCS, LOCCS, EXM, UPM, DEFECT and DEGRADED alarms are VCG
alarms.
The LOM, SQM, LCAS_MemberFail alarms are alarms of member constituting a VCG.
1 2 3 4 5 6 7 8 9 10 11
FAULTS LOA LFD LOCS LOCCS EXM UPM LOM#i SQM#i LCAS_ DEFE DEGR
Member CT ADED
FAULTS Fail#i
1 LOA
2 LFD X
3 LOCS X X
4 LOCCS X X
5 EXM X X
6 UPM X X X X
7 LOM#i
8 SQM#i X
9 LCAS_
Member
Fail#i
10 DEFECT X
11 DEGRADE
D
Definitions :
When LCAS mode is not active,
- VCG_DEFECT is set whenever one of the LOCS, LOCCS, UPM, EXM, LFD, LOA failure
indications is raised or at least one of the SF Member#i is raised.
- VCG_DEGRADED is never set
When LCAS mode is active,
- VCG_DEFECT is set if one of the LOCS, LOCCS, UPM, EXM, LFD, LOA failure indications is
raised and all SF Member#1 to SF Member#X are simultaneously raised.
- VCG_DEGRADED is set if VCG_DEFECT is not set and at least one of the SF Member#i is
raised.
VCG_DEGRADED alerts the operator that, although Ethernet over SDH traffic is still going on, -
thanks to LCAS scheme – the requested SLA may not be achieved due to lack of SDH
bandwidth.
The result of these calculations is then aggregated for each of the monitoring points in :
24-hour counters (BBE, ES, SES and UAS),
15-minute counters (BBE, ES, SES and UAS).
The last 6 UNAVAILABLE PERIODS are stored and displayed on Web browser.
The performance process is initialized when the equipment is powered up and the monitoring
point is monitored.
The last 16 non-zero 15-minute counters, the current 15-minute counter, the last non-zero 24-
hour counter, the current 24-hour counter and the last 6 unavailable periods are displayed on
Web browser.
Remarks :
Alarms appear whenever a card is extracted from the subrack. In order to prevent feedback
of alarms and ALA 1 and ALA 2 loops, the card should be declared out of service.
Each module can be extracted or inserted without acting on other modules or their wiring.
Only the traffic of the concerned module is disturbed.
Procedure :
The procedure described below can apply, unless otherwise specified, to all the cards in the
equipment.
1. Put the card concerned "no service" from Web browser.
2. Remove the external connections performed on the card front side.
NOTE : When the external optical fibers are disconnected, reinstall the protective
covers on connectors.
3. Screw off the TORX screws located on the front side, using the suited screwdriver and
unplug the card
4. Extract the card, complying with the measures of protection against electrostatic discharges.
NOTE : For any card handling, the operator must wear an anti-static bracelet well
tight around the wrist and earthed.
5. Package the extracted card in an anti-static bag.
6. Take the new card out of its anti-static bag.
7. Carefully insert the card into its cell, complying with the measures of protection against
electrostatic discharges, and secure it with the TORX screws.
8. Restore connections on the card front side.
NOTE : For the optical STM-n card, remove the protective covers from connectors.
To clean the optical connectors, use a pressurized air aerosol.
9. Configure the card, if necessary, and put it into service.
The FAN module consists of two redundant fans in order to ensure sufficient ventilation when
either of them is defective. Fan failures are detected on the motherboard by monitoring the
power consumed; failures are viewed on " Shelf View" screen of Web browser.
Default parameters lead to the following behaviour :
The default configuration of severities of the module is :
Minor : one of two fans is faulty
Major : both fans are faulty.
NOTE : The operation of FAN is not continuous; its initiation is related to the
equipment internal temperature and to the operating mode selection.
FAN can be extracted, it can be replaced at any moment without disturbing the traffic.
Procedure :
1. Screw off the TORX screws located on the front side, using the suited screwdriver and
unplug the card.
2. Extract the card, complying with the measures of protection against electrostatic discharges.
NOTE : For any card handling, the operator must wear an anti-static bracelet well
tight around the wrist and earthed.
3. Package the extracted module in an anti-static bag.
4. Take the new module out of its anti-static bag.
5 Carefully insert the module into its place, complying with the measures of protection against
electrostatic discharges, and secure it with TORX screws
ADR155C
ADR155C 120Ω / ADR155 120 HOLDOVER GENERIC SHELF 252 134 830
HOLDOVER
FAN FAN ADR155C GENERIC 252 124 433
Fan Cover MODULE FAN ADR155C COVER 251 856 367 (*)
CARDS
21E120 A155 BLK BNC 21E1/120 ITFE CARD 251 137 402
21E1R8 21E1/8E1 RET/120 BLK A155 ITFE CARD 251 259 985
LAN1 A155 BLK ADRLAN 10/100BT ETH ITFE CARD 251 137 410
GFP150 A155 BLK ADRGFP 10/100 BT ETH ITFE CARD 251 347 772
4E/FE ITFE ETH 10/100 BT 4E/FE ADR155 CARD 252 173 134
External
transformer
COMM port
VT100 Management port 1,8 m 4 980 214
ETH port
Ethernet port on mother board, LAN1 card,
GFP150 card, 4E/FE card : cable FTP category 5
Right cable male – male 3m 55 670 422
Crossover cable male – male 3m 55 670 610
LOOPS port
Remote indication, remote control and station alarm 2,5 m 6 013 628
loops (1/2 cable) 12 m 6 013 161
POWER port Power supply
Free extremity cable 3m 251 065 817
PAPA cable 3m 55 670 797
4. SPECIFICATIONS
EQUIPMENT
Optical specifications
Interface type S1.1-2G ; IC1.1-2G ; IC1.2-2G ; S4.1 ; L4.1 ; L4.2
Bit rate STM-1 : 155.520 Mbit/s ± 20 ppm
STM-4 : 622.08 Mbit/s ± 20 ppm
Standard ITU-T G.957 for single mode interface
EQUIPMENT
Environmental specifications
Mechanical ETS 300 119-4 (19") or CEI 297-3 (ETSI)
ETS 300 019-2-3
Climatic conditions CEI 721-1 (1993)
ETS300 019 part 1-3, class 3.1, 3.2
Operating temperature range - 5 °C à + 45°C
Extended operating temperature range - 5 °C to + 55°C (the MTBF [Mean Time Between
(non destructive degraded mode Failure] is significantly degraded)
requiring a FAN module)
Packaged transportation and storage - 40°C to + 70°C
temperature ETS 300 019 part 1-1 class 1.2
Relative humidity < 85%
EMC (Electromagnetic Compatibility)
EN 300386 / ES 201468
And ESD
Safety NF EN 60950 -1 April 2002
(the equipment does not provide the fire envelope)
Energy ETS 300132-2
(is VLV equipment)
(*)
Predicted reliability
-6
Motherboard 1.51 10
-6
21E120 card 0.29 10
-6
21E75 card 0.29 10
-6
21E1R8 card 0.43 10
-6
IC1.1-2G card 0.98 10
-6
IC1.2-2G card 0.98 10
-6
S1.1-2G card 0.98 10
-6
S4.1 card 1.1 10
-6
L4.1 card 1.1 10
-6
L4.2 card 1.1 10
-6
ERE card 0.29 10
-6
E3DS3 card 0.21 10
-6
LAN1 card 0.52 10
-6
GFP150 card 0.77 10
-6
4E/FE card 0,42 10
-6
Holdover card 0.1 10
-6
Background 0.26 10
-6
FAN Module 3 10
Table 4-2 - ADR155C technical characteristics
(*) The predicted reliability computations have been realized with the RAM COMMANDER
software issue 7.2 according to the UTE C80 810 of july 2000 standard, on the assumption
of specific requirements for the following: ambient temperature 20°C (with ventilation
conditions such as the subrack internal middle temperature is less than 40°C), environment
(mounted on the ground, fixed and protected), qualification, and component ageing (year of
components production : 2005).
Any changes in the above requirements may entail variations in the results.
EQUIPMENT
* These power consumptions are typical values and may be used for dissipation evaluation. It
is necessary to add 20% to estimate peak values which determine power rack capacity. This
allows to take into account the dynamic power variations and the converter efficiency
variations according to total power supply.
Warning : It is necessary to add another 10% when powered by 72V supply.
5. STARTUP GUIDE
Introduction
Thank you for acquiring the ADR155c equipment.
The start up procedure is supplied with the equipment to help you, using examples, to configure it in accordance with the topology of the network to
be build.
PC minimum requirements
Memory 32 MB 64 MB 128 MB
Softwares
Web Browser : Internet Explorer1 5.0 (*)
(*) The operating PC can be equipped with Internet Explorer 5.5 or 6.0 (Windows XP delivered issue)
1
Trademark of Microsoft Corporation
In order to be managed, the ADR155c subrack must have the Equipment address and the Ethernet port address configured in two different sub-
networks.
The Equipment and Ethernet port addresses are configured using the Windows HyperTerminal application.
¾ Connect the equipment's "COMM" port to an unused "COM" port of the PC using the 9pts Male / Female SUB-D straight cable
¾ Power up the PC
¾ Start Windows and run the HyperTerminal application
(Menus: Start/Programs/Accessories/HyperTerminal)
¾ Give a name and select an icon for the connection then apply the choices
¾ Select the PC's "COM" port that is connected to the equipment then apply the choice
¾ Configure the port parameters according to the characteristics below then apply the settings
• Bits per second : 19200
• Data bits : 8
• Parity : None
• Stop bits : 1
• Flow control : None
) Save the connection settings. The next time you will run the HyperTerminal, just click on the connection icon to connect to the
equipment.
¾ Press "ENTER" twice on the keyboard
The MAIN MENU window appears on screen.
The equipment address will be used to notify alarms and events to the Manager. This address is mandatory when using Unnumbered PPP links ( In the
example below, the Equipment address is 192.168.30.30 ).
: Values to be input
The equipment will be restated after the configuration of the Ethernet port address.
This port's address must be located in the same network as the PC's Ethernet port one (in the example given below, the sub-network address is
135.11.110.8 and the sub-network mask is 255.255.255.252).
NOTE: With Windows 9x, the PC's address can be viewed by selecting (right-click) Properties of the Network Neighborhood icon, then (left-click)
Properties of the TCP/IP component (TCP/IP -> "Network Card Name").
With Windows NT, the PC's address can be viewed by selecting (right-click) Properties of the Network Neighborhood icon, then (left-click)
Properties of the TCP/IP component (TCP/IP protocol).
With Windows 2000/XP, the PC's address can be viewed by selecting, in succession, (right-click) Properties of the My Network Places
icon, Properties of the Local Area Connection icon, then (left-click) Properties of the TCP/IP component (Internet Protocol (TCP/IP)).
: Values to be input
¾ After restarting the equipment, the word Password: appears at the top left of the window. Close HyperTerminal application.
The equipment can now be managed by an HTTP browser.
Example:
To be able to manage the equipment, consult the help menu by clicking on the Help link of the main window.
Example:
¾ Refer to the chapter Connecting to
an ADR155c to configure the
Ethernet port and the Equipment
address of each equipment.
¾ Refer to the chapter Configuring a
PPP port to configure the PPP ports
of each equipment.
Example:
Example:
¾ The three ADR155c units can be managed by an HTTP browser. The management links are secured by the OSPF protocol.
¾ Refer to the chapter Connecting to an ADR155c for managing the equipment by the HTTP browser.
Details on configuring the PPP3 port of ADR155c N°3 and the PPP1 port of ADR155c N°4
6. GFP150 CARD
All the services mentioned in this document can be performed between the GFP150 cards from ADR155C but
also between the GFP150 cards and the GFP150 eXtra cards from ADR2500 eXtra.
Only the EPLine and EPLAN services can be interconnected with the EPLine service proposed by a 4E/FE
card.
Only one GFP150 can be installed in an ADR155C shelf either in the A slot or in the C slot ; the presence of
FAN module is mandatory.
This chapter has for objective to guide the user for the commissioning of the GFP150 card in the ADR155C. It
gives simple examples which should be easily adapted to the needs.
The EPLine service (Ethernet Private Line) allows Ethernet 10/100 BaseT point to point interconnection
through a SDH network by using, for each connection, a VCG (VC-Group) based on virtual concatenation
(VCAT). It is possible to obtain up to 8 independant point to point connections per GFP150 card. Rate
granularity for each VCG is based either on VC12, or on VC3. With each VCG, it is possible to
concatenate from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated Ethernet rates, on the
whole of the 8 ETH ports, cannot be above the STM1 payload (about 150Mbit/s).
The EVPLine service (Ethernet Virtual Private Line) allows several Ethernet 10/100 BaseT point to point
interconnection through a SDH network by using over shared VCG (VC-Group) based on virtual
concatenation (VCAT). These VMAN are separated by Tag VMAN, that adds a level of VLAN in relation to
the possible VLANs of Customers. It is possible to put until 16 aggregation traffic (VMAN) on a VCG. In the
GFP150 card we can have 64 (63 if the MSTP protection is used) different VMAN maximum.
The rate granularity for each VCG is the same as EPLine.
The EPLAN service (Ethernet Private LAN) allows Ethernet 10/100 BaseT multipoint to multipoint
interconnection through a SDH network by using, for each connection between two points of the network, a
VCG (VC-Group) based on virtual concatenation (VCAT). It is possible to obtain up to 8 independant
connections per GFP150 card. Rate granularity for each VCG is based either on VC12, or on VC3. With
each VCG, it is possible to concatenate from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated
Ethernet rates, on the whole of the 8 ETH ports, cannot be above the STM1 payload (about 150Mbit/s). In
this case, each GFP150 card includes a switch allowing Ethernet 10/100 BaseT multipoint to multipoint
interconnection.
The EVPLAN service (Ethernet Virtual Private LAN) allows several Ethernet 10/100 BaseT multipoint to
multipoint interconnection through a SDH network by using over shared VCG (VC-Group) based on virtual
concatenation (VCAT).
It is possible to configure 4 VMANs by COS1 class of traffic and 12 VMANs by COS0 class of traffic
(2 classes of traffic are available on the GFP150 card).It is therefore possible to put until 16 aggregation
traffic (VMAN) on a VCG. In the GFP150 card we can have 64 (63 if the MSTP protection is used) different
VMAN maximum.
In this case, each GFP150 card includes a switch function allowing Ethernet 10/100 BaseT multipoint to
multipoint interconnection
• multilink application (Star) : LAN interconnection between a central site and remote sites
• multipoint to multipoint application : to share a LAN between several sites in a BUS topology
The use of the GFP protocol and the advanced Switch features allows to offer Quality of Services features
(QoS). The QoS in GFP150 card is based on a traffic differentiation : metering, congestion control and
scheduling.
Hardware design
Micro
MicroProcessor
Processor
To switch
8
fabric GFP
GFPMapper
Mapper Switch
Switch E/FE TX
155 Mb/s
In the diagram below, one intends to deport a full duplex LAN Ethernet 100 BaseT between 2 sites equipped of
ADR155C. In a first time, one supposes that the rate of the Ethernet traffic exchanged between the 2 sites does
not exceed 10Mbps. The QoS configuration is explained later in this document in greater details.
Eth/VC12
AD R 155C
SDH
AD R 155C
E th e r n e t 1 0 /1 0 0 M E th e r n e t 1 0 /1 0 0 M
Note : The Ethernet interface of the remote equipment (switch, IP router, PC, …) connected to the GFP150
card MUST always be configured the same way. Due to possible interoperability issues with Auto-
Negotiation between equipments from different origins, this feature (“Automatic” option) should
preferably not be used.
This screen is also used to set the severity associated to the interface defect of that interface.
Logical Interface
Select the UNI mode (User to Network Interface) : this type of interface corresponds to an interface customer
with one service per port. On these interfaces the provider OAM and BPDU MSTP management frames are
filtered : they are not sent to the customer network.
The NNI untagged choice (Network to Network Interface) corresponds to a provider interface without provider
VMAN tag (no VLAN aggregation).
The NNI tagged choice (Network to Network Interface) corresponds to a provider interface on which a
provider VMAN tag is inserted in the outcoming frames and a provider VMAN tag is treated in the incoming
frames.
The Link Down Retransmit function can only be used in point to point mode on a VMAN constituted of one ETH
port and one VCG port in each equipment.
Tick "Enable" allows to report the state of the Ethernet Down or VCG Down link on the remote Ethernet link.
Pause Mode
The Pause function (IEEE 802.3 Flow control) can only be used in point to point mode/full duplex on a VMAN
constituted of one UNI ETH port and one NNI untagged VCG port (or of two UNI and NNI untagged ETH ports).
- At reception of a pause frame on the ETH port, the transmission of Ethernet frames on the ETH port is
suspended temporarily
- On detection of traffic obstruction on the VMAN considered in the sense ETH = > VCG, a pause frame is
transmitted on the ETH port to ask the remote equipment to stop the transmission of Ethernet frame
temporarily.
Warning : When the Pause mode is activated, be careful to configure the CIR and PIR to the maximum of the
capacity of the VCG
Configuring a VCG
Click on the “VCG” block, then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then on
the “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last
connection. Click on “Apply” in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Click on the “Settings” link. Verify that VCG#1 is set with the default configuration : “Admin Status” at “Up”,
"Logical Interface NNI " at "untagged", “LCAS” at “Yes” and “FCS” at “No”. We choose to keep the default
options for this example. This screen also displays the type of VCG#1 (VC12) and the number of constituting
VC members (6).
- untagged : corresponds to a provider interface without provider VMAN tag (no VLAN aggregation).
- tagged : corresponds to a provider interface on which a provider VMAN tag is inserted in the outcoming
frames and a provider VMAN tag is treated in the incoming frames.
Click on the "VCG" block and then on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and
click on "APPLY " in order to start monitoring alarms on this port (see Figure 6-9).
Click on the “Switch” block, then on the “VMAN Create” link. Enter “2” as new VMAN ID and click on “Apply” in
order to add it. A new screen comes up in order to associate ports to this VMAN.
Click on the “Add Port” link. Select the Ethernet interface ETH#1, the “trTCM” policing algorithm, enter 10Mbps
for the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more information on the notion of
priority, see the chapter on the QoS). The CBS and EBS values are left to default. Then click on “Add” to
complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#1, the “trTCM” policing algorithm, and
enter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default value. Then click on “Add” to complete the addition of this port to VMAN 2.
The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching between
these 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwarded
between these 2 ports cannot leak out on other ports and vice versa.
Note : In order to install a point-to-point connection (EPLine service), there should never be more than 2 ports
(1 customer UNI Ethernet port and 1 untagged NNI Ethernet or VCG port) in the same VMAN on the
GFP150 card.
To double check the configuration click on the “VMAN List” link. A table displays what ports are associated with
each VMAN configured on the GFP150 card.
Click on the “ETH” block, then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up” and
click on “Apply”.
Note : This screen can be used to configure the severity of the alarms related to concatenated VC’s.
5. Click on the “Settings” link and verify that the VCG#1 is “Up”.
6. Try sending bi-directional Ethernet traffic across the end-to-end connection. You could for example:
• Run a “ping” or a file transfer between 2 PC’s to control Ethernet connectivity.
• Use an Ethernet traffic generator in order to further qualify the end-to-end connection.
As a final step, double-check compliance of the GFP150 counters on both ends based on the traffic being
forwarded. Namely the following counters:
- Ethernet counters: click on the “ETH” block and then on the “MIB2 Counters” link
- GFP counters: click on the “VCG” block and then on the “MIB2/GFP Counters” link
- SLA compliance counters: click on the “Switch” block. Select VMAN ID “2”, click on the “VMAN SLA
counters” link. Verify the set of counters for interfaces ETH#1 and VCG#1. These counters are
described later in this document in greater details.
In the diagram below, one intends to deport two full duplex LAN Ethernet 100 BaseT between 2 sites equipped
of ADR155C by sharing the same VCG for the two traffics (aggregation), this in order to optimize the SDH
bandwidth.
One supposes that the Ethernet traffic rate exchanged between the 2 sites does not exceed 10Mbps for each
flow.
1 VCG
ADR155C
ADR155C
Eth/VC12
SDH
Configuring a VCG
Click on the “VCG” block, then on the “List” link. For the VCG#1 interface, select the VC#1 and click on the
“Multiple Add Member” link. In the new window, select “VC12” as type and the VC#12 as last connection. Click
on “Apply” in order to create the virtually concatenated group of 12 VC12 (VC12#1 to VC12#12) that will be
used to transport Ethernet traffic.
Click on the “Settings” link. to configure VCG#1 as following : “Admin Status” at “Up”, "Logical Interface NNI " at
"tagged", “LCAS” at “Yes” and “FCS” at “No”. These options correspond to the needed example for the
aggregation, on the VCG1 the frames must be tagged
This screen also displays the type of VCG#1 (VC12) and the number of constituting VC members (12).
Click on the "Alarms " link. Select the interface VCG#1 . Tick "Monitor " option and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 6-9)..
Click on the “Add Port” link again. Select the Ethernet interface VCG#1, the “trTCM” policing algorithm, enter
10Mbps for the CIR and PIR, and 7 for the "User Priority ". The CBS and EBS values are left to default values.
Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link. Select the Ethernet interface ETH#2, the “trTCM” policing algorithm, enter 10Mbps
for the CIR and PIR, and 7 for the "User Priority " (maximun priority) (for more oinformation on the notion of
priority, see the chapter on the QoS). The CBS and EBS values are left to default values. Then click on “Add” to
complete the addition of this port to VMAN 3
Click on the “Add Port” link again. Select the Ethernet interface VCG#1, the “trTCM” policing algorithm, enter
10Mbps for the CIR and PIR, and 7 for the "User Priority ". The CBS and EBS values are left to default values.
Then click on “Add” to complete the addition of this port to VMAN 3.
The association of these 2 ports to the same and unique VMAN ID isolates the Ethernet Switching between
these 2 ports from the rest of the ports (all the other Ethernet and VCG interfaces). Ethernet traffic forwarded
between these 2 ports cannot leak out on other ports and vice versa.
With the selection of tagged mode for the VCG1, it is possible to differentiate traffics of the two Eth links on the
VCG.
Note : In order to install a point-to-point connection (EVPLine service), there should never be more than 2
ports (1 customer UNI Ethernet port and 1 tagged NNI Ethernet or VCG port) in the same VMAN on the
GFP150 card.
To check the configuration click on the “VMAN List” link. A table displays the associated ports to each
configured VMAN on the GFP150 card.
Click on the “XCN” block and configure the connections from VC12#1 to VC12#12 of the GFP150 card as usual
in order to have end-to-end SDH connectivity with the remote GFP150 card.
Just do the configuration on the second ADR155C by following the exact same steps again.
Once both ADR155C systems are configured, the ports used by the point-to-point links can be activated on
each ADR155C.
Click on the “ETH” block, then on the “Interface Settings” link. For ETH#1 and ETH#2 interfaces, tick
“ifAdminStatus up” and click on “Apply”.
Take again the procedure of the paragraph 6.2.2.1.2 - to do controls, by verifying the 2 links.
In the network below, we show interconnection of three remote sites with one central site in a “hub and spoke”
topology. Although Ethernet interfaces are 100BaseT full duplex, the load of traffic between the remote sites
and the central site is as follows:
• remote sites 1 and 2 : 10Mbps (6VC12),
• remote site 3 : 5Mbps (3VC12).
The sum of the data rates going to the central site is 25Mbps. However we consider in this example that the
total rate of traffic going in the opposite direction (a.k.a. from the central site to the remote sites) doesn’t go over
20Mbps ; this is just for the purpose of the example.
In this example, the central site acts as a full bridge : Ethernet frames can be forwarded between remote sites.
If no traffic must be allowed between remote sites (for security purpose for instance), one should use 3 separate
Ethernet interfaces on the central site, and 1 point to point connection between each remote site and the central
site. In this case configure 3 independent point-to-point connections as described in the previous section.
Site distant 1
Eth / 6xVC12
Ethernet 10/100
Site distant 2
Ethernet 10/100
Site distant 3
Ethernet 10/100
Click on the "ETH" block then on the “Interface Settings” link. By default the Ethernet interface is forced in
100Base T full duplex. We choose to keep the default configuration for this example.
Note : The Ethernet interface of the remote equipment (switch, IP router, PC, …) connected to the GFP150
card MUST always be configured the same way. Due to possible interoperability issues with Auto-
Negotiation between equipments from different origins, this feature (“Automatic” option) should
preferably not be used.
Click on the “VCG” block and then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then
on the “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last
connection. Click on “Apply” in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Select interface VCG#2 and redo the same operation to add a new group of 6 VC12 (VC12#7 to VC12#12) ; if
the request is refused, verify that the VCG#2 is configured to Down in the "VCG > Settings" window.
Select interface VCG#3 and redo the same operation to add a new group of 3 VC12 (VC12#13 to VC12#15).
Click on the “Settings” link. Verify that VCG#1, VCG#2 and VCG#3 are set with default configuration: “Admin
Status” at “Up”, "Logical Interface NNI " at "untagged", “LCAS” at “Yes” and “FCS” at “No”. We choose to keep
the default options for this example. This screen also displays the type of VCG#1,#2,#3 (VC12) and the number
of constituting VC members (6,6,3).
Click on the "Alarms" link. Select interface VCG#1. Tick option "Monitor " and click on "APPLY " in order to start
monitoring alarms on this port (see Figure 6-9). Repeat with VCG#2 and VCG#3.
Click on the “Switch” block and then on the “VMAN Create” link. Enter “2” as new VMAN ID and click on “Apply”
in order to add it. A new screen comes up in order to associate ports to this VMAN.
Click on the “Add Port” link. Select the Ethernet interface ETH#1, the “trTCM” policing algorithm, and enter
20Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are left
to default. Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#1, the “trTCM” policing algorithm, and
enter 10Mbps for the CIR, and PIR and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default. Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#2, the “trTCM” policing algorithm, and
enter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default. Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#3, the “trTCM” policing algorithm, and
enter 5Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are
left to default. Then click on “Add” to complete the addition of this port to VMAN 2.
To double check the configuration click on the “VMAN List” link. A table displays what ports are associated with
each VMAN configured on the GFP150 card.
Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card as usual in
order to have end-to-end SDH connectivity between the central site and remote site 1.
Configure the connections from VC12#7 to VC12#12 of the GFP150 card as usual in order to have end-to-end
SDH connectivity between the central site and remote site 2.
Configure the connections from VC12#13 to VC12#15 of the GFP150 card as usual in order to have end-to-end
SDH connectivity between the central site and remote site 3.
Once both GFP150 cards at the ends of a connection are configured, the Ethernet interfaces should be
activated.
Click on the “ETH” block and then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up”
and click on “Apply”.
2. Click on the “ETH” block and select Ethernet interface ETH#1. Verify that the interface is running in
100BaseT full duplex and that there is no alarm (the “Fault” option of the Interface Defect alarm is
unchecked). Otherwise double-check both the cables and the configuration of the connected Ethernet
interface.
3. Verify that there are no alarms on all the VC’s being used. Otherwise double-check end-to-end SDH
configuration as well as the signal quality over the various links.
4. Click on the “VCG” block and on the “Alarms” link, then select the VCG#1, VCG#2 and VCG#3 on the
central site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappear
after a few seconds. Otherwise double-check the configuration in the “VCG” functional block on both ends
as well as the configuration of the SDH cross-connects.
5. Click on the “Settings” link and verify that the VCG is “Up”.
6. Try sending bi-directional Ethernet traffic over each point-to-point connection. You could for example:
• Run a “ping” or a file transfer between 2 PC’s to control Ethernet connectivity.
• Use an Ethernet traffic generator in order to further qualify the end-to-end connection.
As a final step, double-check compliance of the GFP150 counters on both ends based on the traffic being
forwarded.
In the network below, we setup an Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR155C.
In this example, sites 2 and 4 play the role of a full bridge: : Ethernet frames can be forwarded between all
remote sites based on MAC address learning.
Each inter-site link of the bus topology is configured to transport a load of 10Mbps (6 VC12). Similarly, on each
ADR155C the Ethernet interface connected to the bus is policed at 10Mbps.
E th / 4 x V C 1 2
E th / 4 x V C 1 2 Site n°3
Site n°1 SDH
E th e r n e t 1 0 / 1 0 0 E th e r n e t 1 0 / 1 0 0
E th e r n e t 1 0 / 1 0 0
E th e r n e t 1 0 / 1 0 0
Click on the “VCG” link and then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then on
the “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last
connection. Click on “Apply” in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Select interface VCG#2 and redo the same operation to add a new group of 6 VC12 (VC12#7 to VC12#12).
Click on the “Settings” link. Verify that VCG#1 is set with the default configuration: “Admin Status” at “Up”,
"Logical Interface NNI " at "untagged", “LCAS” at “Yes” and “FCS” at “No”. We choose to keep the default
options for this example. This screen also displays the type of VCG#1 and VCG#2 (VC12) and the number of
constituting VC members (6).
Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 6-9). Repeat with VCG#2.
Click on the “Switch” block and then on the “VMAN Create” link. Enter “2” as new VMAN ID and click on “Apply”
in order to add it. A new screen comes up in order to associate ports to this VMAN.
Click on the “Add Port” link. Select the Ethernet interface ETH#1, the “trTCM” policing algorithm, and enter
10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values are left
to default. Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#1, the “trTCM” policing algorithm, and
enter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default. Then click on “Add” to complete the addition of this port to VMAN 2.
Click on the “Add Port” link again. Select the Ethernet interface VCG#2, the “trTCM” policing algorithm, and
enter 10Mbps for the CIR and PIR, and 7 for the "User Priority " (maximun priority). The CBS and EBS values
are left to default. Then click on “Add” to complete the addition of this port to VMAN 2.
To double check the configuration click on the “VMAN List” link. A table displays what ports are associated with
each VMAN configured on the GFP150 card.
Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card as usual in
order to have end-to-end SDH connectivity between each middle site (2 or 4) and each edge site (respectively 1
or 3, see Figure 6-21).
Configure the connections from VC12#7 to VC12#12 of the GFP150 card as usual in order to have end-to-end
SDH connectivity between both middle sites (2 and 4).
Once both GFP150 cards at the ends of a connection are configured, the Ethernet and VCG interfaces should
be activated.
Click on the “ETH” block and then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up”
and click on “Apply”.
1. Click on the "ETH" block, check that the Ethernet ports in use are not highlighted (the given box would be
marked yellow or red depending on alarm severity) ; then click on the "VCG" block and on the "Alarms" link,
check that the VCG ports in use are not highlighted (the given box would be marked yellow or red
depending on alarm severity). Otherwise click on the alarmed port to go to the proper screen, where the
specific alarm is displayed (this brings you directly to step 2, 3 or 4 below). Repeat the operation for every
alarmed port.
2. Click on the “ETH” block and select Ethernet interface ETH#1. Verify that the interface is running in
100BaseT full duplex and that there is no alarm (the “Fault” option of the Interface Defect alarm is
unchecked). Otherwise double-check both the cables and the configuration of the connected Ethernet
interface.
3. Verify that there are no alarms on all the VC’s being used. Otherwise double-check end-to-end SDH
configuration as well as the signal quality over the various links.
4. Click on the “VCG” block and on the “Alarms” link, then select the VCG#1, VCG#2 and VCG#3 on the
central site and only VCG#1 on a remote site. Once configuration is complete all alarms should disappear
after a few seconds. Otherwise double-check the configuration in the “VCG” functional block on both ends
as well as the configuration of the SDH cross-connects.
5. Click on the “Settings” link and verify that the VCG is “Up”.
6. Try sending bi-directional Ethernet traffic over each point-to-point connection. You could for example:
• Run a “ping” or a file transfer between 2 PC’s to control Ethernet connectivity.
• Use an Ethernet traffic generator in order to further qualify the end-to-end connection.
As a final step, double-check compliance of the GFP150 counters on both ends based on the traffic being
forwarded.
In the network below, we setup two Ethernet 100BaseT LAN spanning over 4 sites connected to an ADR155C.
To the difference of the EPLAN service, the two LAN use the same VCG to circulate, it is possible with the
aggregation in the same VCG. For this the VCG ports of the N°1, N°2, N°3 and N°4 equipment must be
configured in fashion NNI tagged.
In this example, 2 and 4 sites play the role of a full bridge: : Ethernet frames can be forwarded between all
remote sites based on MAC address learning.
Each inter-site link of the bus topology is configured to transport a load of 20Mbps (12 VC12). Similarly, on each
ADR155C, the Ethernet interface connected to the bus is policed at 10Mbps.
Site n°1
Site n°3
Eth/12xVC12 Eth/12xVC12
SDH
Ethernet 10/100
Ethernet 10/100
Site n°4
Site n°2
Ethernet 10/100 Ethernet 10/100
NNI
NNI
CE UNI UNI
SDH Network
CE
In the example of the figure N°1, a source probe is declared in the equipment N°1 and a sink probe in the
equipment N°2 on the same VMANi, that allows the monitoring of the VMANi customer traffic between
equipment N°1 and equipment N°2 in one sense
To supervise the other sense of this VMANi it is necessary to add two supplementary probes, a source probe on
the equipment N°2 and a sink probe on the equipment N°1.
The number of source probes is limited to 10 and the number of sink probes to 64 by GFP150 card.
The frame multicast OAM is not distributed on the UNI port (customer), and is distributed tagged on tagged NNI
port and no tagged on untagged NNI port
The OAM CC multicast MAC address is by default: 01-80-C2-00-00-67.
Notes:
- The periodic OAM defect, can mean that network capacity for the VCG are not adjusted, and that congestions
appear (example : a VC link loss in a VCG with LCAS).
- No OAM probe must be activated on a flow created between a GFP150 card and a 4E/FE card. The provider
OAMcc frames are not filtered by the 4E/FE card and are forwarded to the customer network.
The GFP150 card provides various QoS functions. These functions format outgoing traffic flows on all
interfaces. Namely:
Functional diagram
The goal of this mechanism is to encourage an important customer by report on a lower customer in aggregate
traffic to respect times of latency associated to every class of service.
The egress treatment (side port broadcast) permits a differentiated treatment according to the priority of the
VMAN with these different queues of transmission (TC: Traffic Class) as well as the means of outgoing
(scheduling in priority the TC1 SP (Strict Priority) file untill its shaping is reached).
This diagram applies to all ports: the 8 Ethernet interfaces plus the 8 Ethernet over SDH interfaces. All functions
are configured separately per port.
Compteurs SLA
Rate control compares the temporal characteristics of received traffic (based on the rate and length of bursts)
with a contract subscribed by the customer sending this traffic. This type of contract is commonly called a
“Service Level Agreement” (SLA).
In the first stage, the temporal characteristics of the actual traffic flow are measured (“metering”). By comparing
them to the configured profile (or contract), each frame is colored according to the following rule:
• Green: the frame is “in profile”
• Yellow: the frame is “partially out of profile”
• Red: the frame is “entirely out of profile”
The GFP150 card provides counters displaying the number of frames associated with each color.
In a second stage, all frames run through the policing function and all Red frames are dropped. Only Green and
Yellow frames can progress.
Metering of the GFP150 card is based on two IETF standards that can be selected via configuration:
• “Single Rate Three Color Marker” (srTCM) per the IETF RFC 2697
• “Two Rate Three Color Marker” (trTCM) per the IETF RFC 2698
When an interface is added to a VMAN, a traffic profile must be configured to be used with traffic entering that
interface. In the current version of the GFP150 card, an interface can be associated to only one VMAN, hence
only one profile.
Traffic profiles
Traffic profiles use the following parameters on the GFP150 card:
The QoS parameters strictly apply to the Ethernet traffic. The overhead generated by GFP encapsulation is not
accounted for in these rates.
The GFP150 card uses a standard algorithm to control the distribution of resources between classes of service
LP (Low Priority) and SP (Strict Priority) in order to manage congestion phases.
The QOS configuration in the GFP150 holds account of the priority information affected to every aggregate
customer. The priority affectation to a customer is done according to a SLA (service level agreement), via the
field configuration "User Priority" (between 0 and 7). To a priority data,.(configured in UNI (or NNI untagged )
ports or extracted from VMAN tags in NNI tagged ports corresponds a traffic class :
• User Priority 0,1,2,3,4,5 => TC0 (Low Priority)
• User Priority 6,7 => TC1 (Strict Priority)
In the current version of GFP150 card, congestion can happen on transmission on an Ethernet or an Ethernet
over SDH interface under the following two (non exclusive) circumstances:
• In a point-to-multipoint topology, when traffic coming from several ports must be mixed for transmission over
another port of the GFP150. There can be more or less transitory phases where the sum of incoming traffic
is significantly greater than the bandwidth available on the outbound port. Point-to-multipoint topologies
especially subject to this type of congestion are those involving an Ethernet port configured at 10Mbps or an
Ethernet over SDH port configured with a small number of VC’s.
• Regardless of the actual topology, when a large quantity of traffic goes through the policing stage but with
the Yellow color (only partially compliant traffic). There can be more or less transitory phases where the
excess rate is actually too high to be transmitted fast enough over the outbound port. Traffic profiles
especially subject to this type of congestion are those with a large differential between the configured CIR
and PIR.
Some repetitive or lasting congestion problems generally require an evolution of the topology network.
Examples above with Point-to-Point, Hub-and-Spoke and Bus topologies already describe the configuration of a
traffic profile when adding a new port to a VMAN (see “Configuring the Ethernet Switch” for each example).
Instructions are different to configure a traffic profile on ports already associated with a VMAN. Click on the
“Switch” block and on the “VMAN List” link. Then three commands are available:
• “Add Port”: use this link to add a new port in a VMAN with a traffic profile
• “Delete Port”: use this link to remove a port from a VMAN and remove the associated traffic profile
• “Modify Port”: use this link to change the traffic profile associated with a VMAN configured on a port
The following screen shows the configuration of a “srTCM” traffic profile on an Ethernet port.
The following screen shows the configuration of a “trTCM” traffic profile on an Ethernet port.
If the operator wants to modify one of these parameters he must disactivate the calculation mode automatic.
For this, click on the "Global Params " block then on the "Advanced " link, select the wanted port for the mode
change, then pass from ON to OFF the column parameter " Auto ", then one can modify the SP bandwidth.
SP Bandwidth % (1-100%) — Translation in percentage of configured bandwidth for Strict Priority waiting
queue.
This queue encourages flux latency times that are affected to it, but with a limited queue shaping in order to
keep bandwidth for low priority queue
The GFP150 card provides counters with the quantity of compliant (green), partially compliant (yellow) and non-
compliant (red) traffic received on a specific interface for a specific VMAN. Click on the “Switch” block and on
the “VMAN List” link. Select the row of the VMAN, click on the “VMAN SLA Counters” link. Then select a port.
The GFP150 card also offers supplementary counters by port/VMAN.To read these counters, click on the
"Switch " block then on the "VMANPortCounters " link. In the top window, select the ETH and VCG ports on
which one wants these counters. The number is limited to 2.
In the below window, select the wanted port for the visualization.
6.2.5 - Using the Multiple Spanning Tree Protocol on the GFP150 card
6.2.5.1 - Description of the Multiple Spanning Tree Protocol on the GFP150 card
The GFP150 card enables activation of the "Multiple Spanning Tree Protocol " (MSTP), standard Ethernet
protocol defined in IEEE 802.1S.
MSTP can remove loops in an Ethernet network setup with redundant links. Without MSTP, these loops are
forbidden by the Ethernet standard to avoid a "broadcast storm ". With a loop and no MSTP, all broadcast
frames or unicast frames with an unknown address are endlessly replicated on all the links to the point where
the whole bandwidth is consumed.
However, in ring or meshed topologies, MSTP is recommended since the network contains Ethernet loops.
Notes :
- A SDH loop to activate SDH protection mechanisms does not imply a loop at the Ethernet level. Ethernet links
are terminated by Ethernet ports or Ethernet over SDH ports.
- No MSTP must be activated on a flow created between a GFP150 card and a 4E/FE card. The provider BPDU
MSTP frames are not filtered by the 4E/FE card and are forwarded to the customer network.
On the GFP150 card, MSTP can be turned ON/OFF at a global level first. Then, once globally activated, each
port Ethernet or Ethernet over SDH can be included or not in the Spanning Tree. Once a port is configured with
MSTP, the protocol controls transmission over this port. Namely, MSTP can block transmission on the port
momentarily or until MSTP converges again following a link loss on an Ethernet port.
The MSTP protocol on the GFP150 card permanently exchanges control packets called "BPDUs " with all other
GFP150 cards running MSTP in the network. These packets are only forwarded on links included in the
Spanning Tree by configuration.
Note : In the present configuration, only the VMAN of which the identifying is between 4032 and 4094 can use
MSTP. Therefore, MSTP can only be used on 63 VMANs.
Warning :
- The VMAN ID of an activated VMAN cannot be modified ; this VMAN must be formerly suppressed.
- The aggregation of a VMAN using MSTP (VMAN ID from 4032 to 4094) with a VMAN without MSTP (VMAN
ID from 2 to 4031) can broke the traffic associated to the VMAN without MSTP because this last is automatically
in the CIST.
CIST (Common Instance Spanning Tree) manages a region, when more than 63 instances are used.
MSTI (Multi Spanning Tree Instance) manages a VLAN.
CIST and MSTI are independent .
Each MSTI is independent of other one. Each MSTI corresponds to one and only one VLAN.
Once a port is included in the Spanning Tree, MSTP compute the state of the port based both on the
information of the BPDUs received from the network as well as the transitions of the operational state of any
local port (in case of link loss/recovery for example).
Each MSTP port is managed by two different informations “PORT STATE” and “PORT ROLE”.
The following example displays a network with an Ethernet loop annihilated by MSTP. It shows the principle of
convergence towards a Tree topology ("Multiple Spanning Tree ") with a node elected as root of the tree ("Root
Bridge ").
Root Port
1
Bridge C
Designated
Port
2 Bridge A
3
Designated
1 1
Ports
Bridge Z Bridge D
Root Ports Blocking
(Root)
2
Root Ports
Designated 4
Port
3 1
Bridge B 2
1
Bridge E
Designated
Ports
A specific MSTP cost can be configured on every port (port priority), and on every Bridge (Bridge priority) in
order to control the Tree topology of the network during stable phases. At times where there is no link loss on
any port, either Ethernet or Ethernet over SDH. Naturally, redundant links blocked by MSTP during stable
phases can be unblocked when a link is lost in the network. Later, when the link failure is fixed and the primary
link comes back up, MSTP re-converges towards the stable topology and blocks back the redundant links.
Per IEEE 802.1D standard, MSTP BPDUs must be sent with a reserved multicast address as MAC destination :
01-80-C2-00-00-00 ("Bridge Group Address "). "). By default, the GFP150 card uses the address :
01-80-C2-00-00-08.
However, the MSTP implementation on the GFP150 card supports configuration of a different multicast address
(standard : 01-80-C2-00-00-00 or non standard : inside the range 01-80-C2-00-00-04 to 01-80-C2-00-00-0F) for
use by the protocol. Using a different address does not change the MSTP algorithm at all. It is just a way to
distinguish the BPDUs sent by the GFP150 card from BPDUs sent by any other Ethernet bridge (which would
logically use the standard address).
The GFP150 cards are useful to interconnect client Ethernet LANs across a network provider’s backbone
(Ethernet over SDH). There can be cases where the clients themselves would be running STP between their
remote sites. By using a non standard address only known by the ADR155C, the GFP150 card can transport
BPDUs coming from client networks in a totally transparent manner.
This way, the STP protocol in the operator network is completely isolated from any MSTP instances running in
the client networks. Moreover, the ADR155C ensures continuity of clients’ STP across remote client sites.
Note : It is recommended not to activate MSTP on the Ethernet ports unless otherwise required by the
topology. It is generally useless to activate the operator MSTP on ports connected to client networks.
The MSTP utilization by the GFP150 card is submitted to a Licence. To activate this Licence, proceed as
following :
1) note the GFP150 MAC address on which the MSTP Licence must be activated
2) provide these informations to the Hotline via phone or E-MAIL to get the Licence key
3) enter the MSTP Licence key (32 characters) provided by the Hotline, via the "MSTP > Licence Activation"
menu, then click on Apply.
Note :
An alarm "No MSTP Licence" of card level is activated if at least one port has a MSTP configuration to ON and
if the MSTP licence is not activated.
The severity of this alarm is major and no configurable.
Use the previous example with a bus topology. Just a redundant link between the remote ADR155C 1 and 3 is
added. The final topology works like a ring.
First the 4 ADR155C should be configured according to the instructions of the bus topology section of this
document (*). Then, the three steps below should be followed in order :
Once the link is activated, one should see that MSTP puts each end of the redundant link in the
"DISCARDING " state. All other ports of the bus go in "FORWARDING " or “ROOT” state.
(*) Warning : the used VMAN for MSTP should have a VMAM ID between 4032 and 4094 ; it will be 4032 for
this example.
Site n°4
Site n°2
Ethernet 10/100
Ethernet 10/100
Bus configuration
Configure the VCG#2 port on ADR155C 1 and 3 with the same instructions as for VCG#2 between ADR155C 2
and 4.
In the end, ADR155C 1 and 3 must be connected via VCG#2 configured with 6 VC12 and included in the same
VMAN as all other ports (VMAN ID "4032").
Note : The link is not activated yet in order to avoid creating an Ethernet loop in the network before MSTP is
running.
Click on the "MSTP" block then on the "Bridge settings " link of the GFP150 card. Set the "MSTP Procotol "
parameter at the "MSTP " value and click on "Apply ".
The default values of fields of the Bridge Configuration screen are those of the 802.1d norm ; to optimize the
times of convergence of the MSTP protocol, it is necessary to adjust the parameters "Forward Delay",
"Hello Time" and "Max Age".
The other parameters allow to configure MSTP according to the user's , Before modify these fields, read the
802.1s standard.
Click on the "Port Settings " link. Set ports VCG#1 and VCG#2 at the "Enable " value and leave other field at
default value, then click on "Apply ".
Once the two interfaces are activated, MSTP starts exchanging BPDUs across the new link and a new state is
calculated. However, after a few seconds each port of this link goes in "BLOCKING " state thanks to the
difference in "Path Cost " over the ring. Except for MSTP BPDUs, no Ethernet frame is forwarded over this link.
Connectivity check
Select MSTI Id 1and click on the “MSTI-Port informations and Settings” link to see the next panel.
The GFP150 card enables activation of the standard protocol "Link Capacity Adjustment System " (LCAS)
independently on each of the 8 VCGs.
LCAS is useful to :
• Dynamically add or remove VC members from a VCG without deactivating the VCG (making it a hitless
operation for traffic)
• Dynamically adjust the available bandwidth when alarms are triggered ON/OFF on the VC members of a
VCG. The bandwidth of every VC under failure is subtracted from the VCG bandwidth. Hence, in case of
failures the VCG continues to forward traffic as long as there is still at least one operational VC.
Without LCAS :
• The GFP150 card requires deactivation of a VCG before VC members can be added or removed (it forces a
traffic interruption)
• A VCG becomes completely broken as soon as an alarm is triggered on at least one VC member. Plus, it
becomes operational again only once no VC is under failure anymore.
In order to run, LCAS only needs to be activated on both ends of a VCG. LCAS is transparent for the SDH
backbone point of view. Once both ends of a VCG are configured with LCAS they start exchanging control
information in the SDH overhead (namely, in the multi-frame of virtual concatenation).
LCAS can be used as a mechanism to protect transmission of Ethernet traffic : when a part of the VCs of a VCG
fail, transmission continues with the remaining operational VCs.
This protection mechanism makes sense only if the VCs of a VCG are not all configured the same way across
the SDH network :
• Either they must take different path via independent SDH links ;
• Or a part of the VCs must be protected at the SDH level (SNC, etc.) ;
• Or some of both.
We use again the point-to-point connection example described earlier in this document. The VCs just use two
different SDH paths. The LCAS option is at “Yes” by default.
Click on the VCG block and then on the “List” link. For the VCG#1 interface, select VC#1 and click on the
“Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last connection.
Click on “Apply” in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6) that will be
used to transport Ethernet traffic.
Click on the “Settings” link. Verify that VCG#1 is set with the default configuration: “Admin Status” at “Up”,
“LCAS” at “Yes” and “FCS” at “No”. This screen also displays the type of VCG#1 (VC12) and the number of
constituting VC members (6).
Click on the "Alarms " link. Select interface VCG#1 . Tick option "Monitor " and click on "APPLY " in order to
start monitoring alarms on this port (see Figure 6-9).
Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the GFP150 card in way where
3 VC12 go through a SDH card and the 3 other VC12 go through a second SDH card. Make sure you have end-
to-end SDH connectivity with the remote ADR155C.
1. The configuration of the Ethernet interface must be identical between the GFP150 card and the
transmission equipment present on the LAN. It is preferable to use the “manual” modes rather than the
"auto negotiation" mode because of the incompatibility of operation of this mode between certain
equipment.
2. The changes of configuration of VCG interface (LCAS, FCS) must be done when the interface is "OFF "
(AdminStatus ticked "down"). The interface is configured to "ON " (AdminStatus ticked "up") when
configurations of the 2 extremities of the link are effective. However, when LCAS is activated on a VCG
interface and when this interface is itself in the state "ON ", it is possible to modify the VCG composition
(add/delete VC members) without putting the interface "OFF " before. In this case, these modifications are
directly taken into account.
3. For each VCG, it is preferable to configure the FCS parameter to "No ".
6.4 - APPLICATIONS
• The Ethernet rate configured for each interface of the GFP150 card is corresponding to the payload
avalaible at the Ethernet interface.
• This rate is called MTU (64 to 1548 bytes including 6 Bytes @dest, 6 Bytes @src, 2 Bytes lgd trame, and 4
Bytes FCS).
• Knowing there is 12 intergap Bytes between 2 Ethernet frames, which are outside the payload, and 8
preamble Bytes per Ethernet frame, which are also outside the payload, when an Ethernet 100 BaseT
interface is used to the maximum of its capacity (end to end frames at 100Mbit/sec), payload rate in
100BaseT is 76.19Mbit/sec for 64 Bytes (MTU) frames, and 98.72Mbit/sec for 1548 Bytes (MTU) frames.
• In the same way, payload rate in 10BaseT is 7.62Mbit/sec for 64 Bytes (MTU) frames, and 9.87Mbit/sec for
1548 Bytes (MTU) frames.
• Because we don’t control Ethernet frames lengths in a link, which may change from frame to frame, we
have to imagine the most critical case, in order to configure the VCG rate for the link. Note the GFP protocol
adds an 8 Bytes header (12 Bytes when the GFP FCS is ON), header taken into account in
§ 6.5.3 -and § 6.5.4 -
Note that even if we know how to configure, in the case of 100BaseT, a CIR upper than 1 and under 100
Mbit/sec (per 1Mbit/sec step) at the customer Ethernet interface (and in the case of the 10BaseT mode a CIR
between 1 and 10Mbit/sec sec (per 1Mbit/sec step)), some normal limitations are to be taken into account :
Of course, if others VC3 and/or VC12 are used for transporting flows coming from other cards in
ADR155C, it must be taken into account.
Note than all VCG VC3 based in the GFP150 card can’t use more than 2 VC3.
We suppose customer Ethernet interfaces CIR and PIR in the link are already configured.
In point to point (EPLine service), the minimal number N of VC12 necessary for transmitting a CIR of E
Mbit/sec at the customer Ethernet interface is :
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E and we advise to configure
PIR=CIR.
Example :
• If we suppose E=PIR=20Mbit/sec
• We obtain N=UPPER_ROUND_NUMBER(20*1.125/2.176)=UPPER_ROUND_NUMBER(10.34)=11 (≤46)
In all cases, we advise after the configuration of customers interfaces Ethernet CIR/PIR and the corresponding
VCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.
We suppose customer Ethernet interfaces CIR and PIR in the link are already configured.
In point to point (EPLine service), the minimal number N of VC3 necessary for transmitting a CIR of E
Mbit/sec at the customer Ethernet interface is :
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E and we advise to configure
PIR=CIR.
Example :
• If we suppose E=PIR=60Mbit/sec
• We obtain N=UPPER_ROUND_NUMBER(60*1.125/48.384)=UPPER_ROUND_NUMBER(1.395)=2 (≤2)
In all cases, we advise after the configuration of customers interfaces Ethernet CIR/PIR and the corresponding
VCG, to configure Ethernet over SDH interfaces CIR/PIR as CIR=PIR=VCG payload.
7. 4E/FE CARD
The EPLine service proposed by the 4E/FE card can be interconnected with the EPLine and EPLAN services
proposed by the GFP150 card of the ADR155C and by the GFP150 eXtra card of the ADR2500 eXtra.
Each ADR155C can include up to four 4E/FE cards which must take place in "A", "B", "C" or "D".slots.
Each "ETH #n" port is necessarily associated to the "VCG #n" port.
In case of management by IONOS-NMS, it will always be necessary to create a VMAN associating an ETH#n to
a VCG#n.
This chapter has for objective to guide the user for the commissioning of the 4E/FE card. It gives simple
examples which should be easily adapted to the needs.
Service provided by 4E/FE card allows to build an Ethernet LAN between 2 remote sites :
• An EPLine service (Ethernet Private Line) allowing Ethernet 10/100 BaseT point to point interconnection
through a SDH network by using, for each connection, a VCG (VC-Group) based on virtual concatenation
(VCAT). It’s possible to obtain up to 4 independant point to point connections per 4E/FE card. Rate
granularity for each VCG is based either on VC12, or on VC3. With each VCG, it’s possible to concatenate
from 1 to 46 VC12 or from 1 to 2 VC3. The sum of the concatenated Ethernet rates, on the whole of the 4
ETH ports, can’t be above the STM1 payload (about 150Mbit/s).
Eth/VC12
AD R 155C
SDH
AD R 155C
E th e r n e t 1 0 /1 0 0 M E th e r n e t 1 0 /1 0 0 M
Login on the first ADR155C to open the “Shelfview” HTTP screen. On this screen, click on the 4E/FE card then
on the “ETH” block.
Click on the “Interface Settings” link. By default the Ethernet interface is forced in 100Base T full duplex. We
choose to keep the default configuration for this example.
Note : The Ethernet interface of the remote equipment (switch, IP router, PC, …) connected to the 4E/FE card
MUST always be configured the same way. Due to possible interoperability issues with Auto-
Negotiation between equipments from different origins, this feature (“Automatic” option) should
preferably not be used.
This screen is also used to set the severity associated to the interface defect of that interface.
Logical Interface
Logical Interface UNI (User to Network Interface) : this type of interface corresponds to an interface customer
with one service per port. On these interfaces the provider OAM and BPDU MSTP management frames from
GFP150 or GFP150 eXtra cards are not filtered : they are sent to the customer network. Therefore, no OAM or
MSTP must be activated on a flow created between a GFP150 or GFP150 eXtra card and a 4E/FE card.
The Link Down Retransmit function is used on a point to point link constituted of one ETH port and one VCG
port in each equipment.
Tick "Enable" allows to report the state of the Ethernet Down or VCG Down link on the remote Ethernet link.
Pause Mode
The Pause function (IEEE 802.3 Flow control) is used on a point to point/full duplex link constituted of one ETH
port and one VCG port.
- At reception of a pause frame on the ETH port, the transmission of Ethernet frames on the ETH port is
suspended temporarily
- On detection of traffic obstruction in the sense ETH = > VCG, a pause frame is transmitted on the ETH port
to ask the remote equipment to stop the transmission of Ethernet frame temporarily.
Configuring a VCG
Click on the “VCG” block, then on the “List” link. For the selected VCG#1 interface, click on VC#1 and then on
the “Multiple Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last
connection. Click on “Apply” in order to create the virtually concatenated group of 6 VC12 (VC12#1 to VC12#6)
that will be used to transport Ethernet traffic.
Click on the “Settings” link. Verify that VCG#1 is set with the default configuration: “Admin Status” at “Up”,
“LCAS” at “Yes” and “FCS” at “No”. We choose to keep the default options for this example. This screen also
displays the type of VCG#1 (VC12) and the number of constituting VC members (6).
Logical Interface NNI (Network to Network Interface), untagged : corresponds to a provider interface
without provider VMAN tag (no VLAN aggregation).
Click on the « Alarms » link. Select interface VCG#1 . Tick option « Monitor » and click on « APPLY » in order to
start monitoring alarms on this port (see Figure 7-6).
Click on the “XCN” block and configure the connections from VC12#1 to VC12#6 of the 4E/FE card as usual in
order to have end-to-end SDH connectivity with the remote 4E/FE card.
Just do the configuration on the second ADR155C following the exact same steps again.
Once both ADR155C systems are configured, the ports used by the Point-to-Point can be activated on each
ADR155C.
Click on the “ETH” block, then on the “Interface Settings” link. For interface ETH#1 , tick “ifAdminStatus up” and
click on “Apply”.
Note : This screen can be used to configure the severity of the alarms related to concatenated VC’s.
5. Click on the “Settings” link and verify that the VCG#1 is “Up”.
6. Try sending bi-directional Ethernet traffic across the end-to-end connection. You could for example:
• Run a “ping” or a file transfer between 2 PC’s to control Ethernet connectivity.
• Use an Ethernet traffic generator in order to further qualify the end-to-end connection.
As a final step, double-check compliance of the 4E/FE counters on both ends based on the traffic being
forwarded. Namely the following counters:
- Ethernet counters: click on the “ETH” link and then on the “MIB2 Counters” link
- GFP counters: click on the “VCG” link and then on the “MIB2 GFP Counters” link
The 4E/FE card enables activation of the standard protocol « Link Capacity Adjustment System » (LCAS)
independently on each of the 4 VCGs.
LCAS is useful to :
• Dynamically add or remove VC members from a VCG without deactivating the VCG (making it a hitless
operation for traffic)
• Dynamically adjust the available bandwidth when alarms are triggered ON/OFF on the VC members of a
VCG. The bandwidth of every VC under failure is subtracted from the VCG’s bandwidth. Hence, in case of
failures the VCG continues to forward traffic as long as there is still at least one operational VC.
Without LCAS :
• The 4E/FE card requires deactivation of a VCG before VC members can be added or removed (it forces a
traffic interruption)
• A VCG becomes completely broken as soon as an alarm is triggered on at least one VC member. Plus, it
becomes operational again only once no VC is under failure anymore.
In order to run, LCAS only needs to be activated on both ends of a VCG. LCAS is transparent for the SDH
backbone’s point of view. Once both ends of a VCG are configured with LCAS they start exchanging control
information in the SDH overhead (namely, in the multi-frame of virtual concatenation).
LCAS can be used as a mechanism to protect transmission of Ethernet traffic : when a part of the VCs of a VCG
fail, transmission continues with the remaining operational VCs.
This protection mechanism makes sense only if the VCs of a VCG are not all configured the same way across
the SDH network :
• Either they must take different path via independent SDH links ;
• Or a part of the VCs must be protected at the SDH level (SNC, etc.) ;
• Or some of both.
We use again the point-to-point connection example described earlier in this document. The VCs just use two
different SDH paths. The LCAS option is at “Yes” by default.
Click on the VCG link and then on the “List” link. For the VCG#1 interface, select VC#1 and click on the “Multiple
Add Member” link. In the new screen coming up, select “VC12” as type and VC#6 as last connection. Click on
“Apply” in order to create the virtually concatenated group of 6 VC12 (VC#1 to VC#6) that will be used to
transport Ethernet traffic.
Click on the “VCG” link and then on the “Settings” link. Verify that VCG#1 is set with the default configuration:
“Admin Status” at “Up”, “LCAS” at “Yes” and “FCS” at “No”. This screen also displays the type of VCG#1 (VC12)
and the number of constituting VC members (6).
Click on the VCG link and then on the « Alarms » link. Select interface VCG#1 . Tick option « Monitor » and
click on « APPLY » in order to start monitoring alarms on this port (see Figure 7-6).
Click on the “XCN” block. Configure the connections from VC12#1 to VC12#6 of the 4E/FE card in way where 3
VC12 go through a SDH card and the 3 other VC12 go through a second SDH card. Make sure you have end-
to-end SDH connectivity with the remote ADR155C.
1. The configuration of the Ethernet interface must be identical between the 4E/FE card and the transmission
equipment present on the LAN. It is preferable to use the “manual” modes rather than the "auto negotiation"
mode because of the incompatibility of operation of this mode between certain equipment.
7.4 - APPLICATIONS
• The Ethernet rate configured for each interface of the 4E/FE card is corresponding to the payload avalaible
at the Ethernet interface.
• This rate is called MTU (64 to 1548 bytes including 6 Bytes @dest, 6 Bytes @src, 2 Bytes lgd trame, and 4
Bytes FCS).
• Knowing there is 12 intergap Bytes between 2 Ethernet frames, which are outside the payload, and 8
preamble Bytes per Ethernet frame, which are also outside the payload, when an Ethernet 100 BaseT
interface is used to the maximum of its capacity (end to end frames at 100Mbit/sec), payload rate in
100BaseT is 76.19Mbit/sec for 64 Bytes (MTU) frames, and 98.72Mbit/sec for 1548 Bytes (MTU) frames.
• In the same way, payload rate in 10BaseT is 7.62Mbit/sec for 64 Bytes (MTU) frames, and 9.87Mbit/sec for
1548 Bytes (MTU) frames.
• Because we don’t control Ethernet frames lengths in a link, which may change from frame to frame, we
have to imagine the most critical case, in order to configure the VCG rate for the link. Note the GFP protocol
adds an 8 Bytes header (12 Bytes when the GFP FCS is ON), header taken into account in
§ 7.5.3 -and § 7.5.4 -
3. In all cases :
• The addition of payload rates of each active VCG must be under the payload of a VC4. So, we can
consider 4 cases :
1. No VC3 used (neither for VCG, nor by another card in ADR155C) : the number of all VC12 used
must be ≤ 63.
2. 1 VC3 is used among all the VCG and/or the other cards in ADR155C : the number of all VC12
used must be ≤ 42.
3. 2 VC3 are used among all the VCG and/or the other cards in ADR155C : the number of all VC12
used must be ≤ 21.
4. 3 VC3 are used among all the VCG and/or the other cards in ADR155C : No VC12 can be used
Of course, if others VC3 and/or VC12 are used for transporting flows coming from other cards in
ADR155C, it must be taken into account.
Note than all VCG VC3 based in the 4E/FE card can’t use more than 2 VC3.
In point to point (EPLine service), the minimal number N of VC12 necessary for transmitting a rate of
E Mbit/sec at the customer Ethernet interface is :
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E.
Example :
• If we suppose E=20Mbit/sec
• We obtain N=UPPER_ROUND_NUMBER(20*1.125/2.176)=UPPER_ROUND_NUMBER(10.34)=11 (≤46)
In point to point (EPLine service), the minimal number N of VC3 necessary for transmitting a rate of
E Mbit/sec at the customer Ethernet interface is :
This calculation takes into account GFP header with FCS OFF. When FCS is ON, replace 1.125 with 1.1875.
Note that in this case, the customer Ethernet interface remote rate must equals E.
Example :
• If we suppose E=60Mbit/sec
• We obtain N=UPPER_ROUND_NUMBER(60*1.125/48.384)=UPPER_ROUND_NUMBER(1.395)=2 (≤2)
When creating a PPP link, the operator has two choices: either the link is numbered or it is
unnumbered. This is independent of the protocol selected (RIP or OSPF). The unnumbered
links do not have an IP address and therefore more easily enable construction of a network
(since there is no need to define all the IP addresses of all the links).
In the ADR155c, the static routes are used to configure routes which are not learned by the
routing protocols and located "on the periphery" of the protocol areas or domains: routes to
machines on Ethernet network such as manager, for example.
The static routes, as implemented in the ADR155c, have the following characteristics:
• each route is assigned a metric.
• each route is assigned a preference. The preference is used to settle conflicts when routes of
different types (static and dynamic) have the same destination.
• preference is given to the static routes with respect to the dynamic routes.
• the static routes are always exported by the routing protocols to the other equipment.
Depending on whether the interface which the routes take is in the operational state or not, the
static routes are set up or removed to avoid assignment of non-valid routes.
A maximum of twenty static routes is supported by each ADR
Configuration of static routes
In the static tables context, each network node must have its routing table filled in order to
correctly route the packets received.
All IP routes of a routing table of a given equipment comprise the following fields:
• «destination @IP» : corresponds to the IP address of the equipment or sub-network (or
network) to be reached from the given equipment,
• «subnet mask» : this is the sub-network mask associated to the IP address defined in the
«destination @IP» ; all equipment with the IP address part defined by the "1" bits of this field
which corresponds to the same value as the «destination @IP» part defined by this same
mask can be reached through this route,
• «next hop @IP» : IP address of next equipment (connected directly with given equipment) to
which the packet will be sent,
• «metric» (also referred to as "cost" or distance): value from 1 to 15 indicating the number of
hops to reach the corresponding equipment at the «destination @IP» address. 16
corresponds to infinity for the RIP routing daemon. This field is only used by a possible
routing daemon to select a preferential route if several different routes exist for the same
destination. It is always possible to configure this field for 1 to simplify if use of the field is not
indispensable.
• «interf.» : interface number used to reach the next equipment (whose IP address is «next
hop @IP»).
Note: Declaration of the interface IP addresses results in setting up implicit static routes to the
associated SUBNETs. It is therefore not necessary to define static routes to join two
equipments on a single SUBNET.
Note: The IP addresses of an equipment are the addresses of its interfaces (or ports) which
have been configured. The manager only knows one IP address per equipment. This is
why reference is often made to the IP address of an equipment to designate the address
configured in the manager database. This is the address of the port by which the
equipment normally dialogues with the manager.
Note: To operate an equipment via a PC and an Ethernet interface, the IP address of the
operation PC must be modified so that it belongs to the same SUBNET as the Ethernet
interface used to connect to the network.
The HOST 1 number on each SUBNET should be left free, i.e. begin to number the
equipment starting with the HOST 2 number. The PC will thus always take an IP
address such as : NET.SUBNET.1
Note: A default router can be defined (option sometimes available) to which all packets which
cannot be routed by the routing table are transmitted.
The figure below gives an example of an IP network and routing tables associated to two typical
equipments. Note that each port of the on-board routing function corresponds to a different
SUBNET.
140.1.1.3
F3
140.1.0.2 140.1.0.3 140.1.1.2
Manager Fiber 140.1.1.4
F1 F2
128.1.0.1 Ethernet
128.1.0.2 F4
Ethernet 140.1.1.5
NET 128.1 128.1.0.3
NET 140 - 1 F5
F6
PPP1 150.1.0.2
Fiber Fiber
150.1.0.3
F7
150.1.1.2
Ethernet Ethernet
Configuration of ADR155C F6
Interfaces
Eth 128.1.0.3
Subnet mask 255.255.0.0
PPP1 150.1.0.2
Subnet mask 255.255.255.0
Static routes
Dest @IP Subnet mask Next hop Interface Metric Note
Configuration of ADR155C F8
Interfaces
Eth 150.1.1.3
Subnet mask 255.255.255.0
Static routes
Dest @IP Subnet mask Next hop Interface Metric Note
Various theoretical cases for a network are described in the sections below.
A.2.2.1 Network 1
This network is the most simple case of an equipment network (starting with release P3.1), all of
which are connected by unnumbered PPP links.
ppp Unn
ADR 2
ppp Unn
ppp Unn
ppp Unn
ADR 3
ADR 1
Ethernet
ppp Unn
sub-network
Ethernet
A RIP or OSPF routing protocol is implemented (RIP only if size of network allows).
The Ethernet network forms an IP sub-network; the Ethernet interface is thus assigned an
address in the sub-network.
The equipment addresses can be selected in any given way, but not in the Ethernet sub-
network.
The breakdown of the number of addresses per equipment thus gives:
ADR 1 has two addresses (Ethernet address and equipment address), ADRs 2 and 3 each have
one address (equipment address).
A.2.2.2 Network 2
This network has ADRs (starting with release P3.1) and a P1 or P2 equipment.
sub-network
ppp Num 3 ADR 4
3
ADR 2
ppp Unn
FOTC 1 ppp Unn ppp Num 2
ADR 3
sub-network
ADR 1
1 ppp Unn
Ethernet
The PPP links respectively connecting ADR 4 and ADR 2 and ADR3 must be numbered links.
The PPP links between ADR1,ADR2,ADR3 will be preferentially unnumbered links.
Equipment addressing:
The Ethernet network forms an IP sub-network.
Each of the numbered PPP links forms an IP sub-network.
The addresses of ADR 1, 2, 3 (equipment address) can be selected in any given way (but not in
the Ethernet sub-network).
To exceed the RIP constraints (limited to 16 "hops"), the network can be divided into two routing
domains in accordance with the diagram below:
Domain 2
ADR 2
Domain 1
ADR 1
ADR 0
Ethernet
The overall equipment network is divided into domains (1 and 2) in which the RIP routing is
implemented.
The Ethernet network is there to represent the link with the SNMP manager on the PC not using
the RIP.
The two domains are connected via ADR 1 and ADR 2 (which functionally are border routers).
The link between the two border ADRs can be an Ethernet link, numbered PPP or unnumbered
PPP.
The RIP is not activated on the interfaces of this link connecting the two domains.
Routing between the two domains is made possible by static routes configured in the ADRs.
ADR 1 has static routes to the sub-networks forming domain 2 and ADR 2 has routes to the sub-
networks forming domain 1.
The static routes to the sub-networks of a domain (2, for example) in the border ADR of the
other domain (ADR 1) can be reduced to a single route to a sub-network combining the sub-
networks of the domain (2).
This global sub-network must be distinct with respect to the sub-networks of the other domain
(1, in the example).
UN SEUL Email :
ON A SINGLE Email address:
hotline.arp@sagem.com
Installation and User Guide / Guide d'Installation et d'Utilisation – 288 091 808-02
Sagem Communication document. Reproduction and disclosure prohibited
Document Sagem Communication. Reproduction et divulgation interdites
Siège social : 27, rue Leblanc - 75512 PARIS CEDEX 15 - FRANCE
Tél. : +33 1 58 11 77 00 - Fax : +33 1 58 11 77 50
http://www.sagem.com
Société Anonyme au capital de 300 272 000 € - 480 108 158 RCS Paris