HUB Structure PDF

FlexiPacket HUB Structure
1.2
Interfaces
According to the FPFM200 front panel view (see Fig. 1), it has the following
interfaces:
1. 1x DC input (-48 V)
2. 4 x 10/100/1000 BaseT electrical ports with synchronous Ethernet (two ports
support ODU power feeding)
3. 2 x Small Form Pluggable (SFP) Ethernet ports
4. 8 x E1/T1/J1 ports with 120, 100 and 75 Ohm impedance
5. 1 x DCN (In-band management)
6. 1 x OOB management port (local management and dual-IDU management)
7. 1 x Dry contact (two inputs and five outputs, used for alarm interface)
8. 1 x Memory key
Fig. 1 Front panel view in R2.0 EP1
WARNING
The optical Ethernet port (SFP) cannot be used to connect the FlexiPacket
Radio ODU. Both SFP optical and electrical ports can be connected to other
equipment for local traffic.
Respect to the Release 1.0 and 1.0 EP1 there are some differences on the front
panel as reported in Fig. 2 and in Fig. 3.
FT48927EN03GLA0
2012 Nokia Siemens Networks
/2.0 EP1
In R2.0, Reset button is marked with RST and FlexiPacket FirstMile is changed to
FlexiPacket FirstMile 200.
The name of local management interface is changed from Dual-IDU to OOB.
The name of in band management interface is changed from OOB to DCN.
The name of TDM port is changed from E1/T1/ to E1/T1/J1.
The names of GE port 3 and 4 are changed to 3 (PWR) and 4 (PWR).
DC power is marked with + and - respectively.
Fig. 2 Changes of label marks between R1.0, R1.0 EP1 and R2.0/2.0EP1 (1)
Fig. 3 Changes of label marks between R1.0, R1.0 EP1 and R2.0/2.0EP1 (2)
FT48927EN03GLA0
WARNING
The optical Ethernet port (SFP) cannot be used to connect the FlexiPacket
Radio ODU. Both SFP optical and electrical ports can be connected to other
equipment for local traffic.
There are two choices of SFP connectors when connecting to the SFP Ethernet ports
according to the Fig. 4.
Fig. 4 SFP connectors
FT48927EN03GLA0
1.3
Memory Key
The memory key is used for FPFM200 IDU configuration and licenses backup. It
provides an easy IDU replacement in case of system failure.
The memory key must be pre-formatted by the factory and contains a serial number
with the right equipment name. The storage size of memory key is 32 Mb.
The following information is stored in memory key:
equipment configuration data

available licenses
Equipment name
System type
Memory key Product Identification Data (PID)
Memory key serial number
WARNING
When the system is boot up, it will first check the data in the memory key,
therefore, a valid memory key is required to boot-up the system successfully.
WARNING
A reset button is located beside the Memory key interface on the FPFM200
front panel (Fig. 5). When the reset button is pressed, the microprocessor of
the system is reset but leaving the rest of hardware running.
Fig. 5 The Reset button
FT48927EN03GLA0
1.4
Power supply
FPFM200 requires a power supply input of -48 VDC.

The system is equipped with an internal PSU (DC/DC unit) for the power feeding of
the internal circuitry.
The internally dissipated power is within 30 W, including the PSU efficiency.
Besides, the IDU provides power feeding to the connected ODUs.
Up to 2 ODUs are supported.
The IDU forwards the DC battery voltage towards the central terminal of the Ethernet
transformers (Fig. 6).
IDU continuously performs a load control to detect abnormal working condition.
Short-circuit protection prevents the system from over-voltage.
Fig. 6 Fig. 6 Power supply
1.5
Handling requirements
FPFM200 is sensitive to electromagnetic discharge. The user should be sure that the
module is properly grounded and wear an antistatic wrist wrap when handling it.
FT48927EN03GLA0
1.6
Connection to FlexiPacket ODU
There are two ways to inter-connect FlexiPacket ODU and FPFM200:
through a single Ethernet cable with ODU powering support using the proper
FPFM200 Ethernet ports (Fig. 7)
using 2 cables: one Ethernet cable and a separate one for ODU powering
Power plus Ethernet
Fig. 7
Up to two Link Protection Groups (LPG) can be configured:
LPG1 GE1+GE2
LPG2 GE3+GE4
FT48927EN03GLA0
1.7
LED Indications
FPFM200 has four types of LEDs on the front panel to indicate the operational status
of the system:
System (Fig. 8 and Fig. 10)

Memory key (Fig. 8 and Fig. 10)
Ethernet electrical and SFP interfaces (Fig. 9 and Fig. 11)
E1/T1 interfaces (Fig. 9 and Fig. 11).
Fig. 8 System and Memory Key LEDs position
Fig. 9 Ethernet electrical, SFP interfaces and E1/T1 Interfaces LEDs position
10
FT48927EN03GLA0
Fig. 10 System and Memory Key LEDs meaning
Fig. 11 Ethernet electrical, SFP interfaces and E1/T1 interfaces LEDs meaning
FT48927EN03GLA0
11
1.8
Licensing
The customer who wants to use certain features has to purchase the corresponding
license.
A license can be bought by the customer together with the hardware and the
application software in the initial purchase order, or it can be later purchased and
installed into an already operating appliance.
The FPFM200 is delivered to customer with latest available software (SW) version
preinstalled, providing the basic and essential functions needed in-field, which is the
basic license configuration, while there are additional features that could be required,
for instance, when the network scales up.
The basic configuration is:
two Ethernet ports can be activated out of 6 Ethernet ports (including the 2 SFP
ports).
configuration 1 + 1 hot standby (HSB) is not enabled.

No support for RSTP/MSTP, Security, OAM
FPFM200 R2.0EP1 provides the following upgrading license:
FPFM200 full configuration: Enabling of 1+ 1 hot standby (HSB) protection and all
6 Ethernet ports
Support of RSTP/MSTP: Rapid Spanning Tree Protocol/Multiple Spanning Tree

Protocol
Support of security management SSH, SFTP, SNMPv3, ACL (ACL means Access
Control Log, not Access Control List and is used to record user logging).
Support of OAM (Operations, Administration and Maintenance)

WARNING
For the detailed license upgrading procedure, please refer to FlexiPacket
FirstMile 200 Operate and Maintain Chapter.
WARNING
In FPFM200 R2.0/ R2.0 EP1, about the in-field license upgrading, the license file
will be delivered through an electronic channel, so that there will be no more
need of the USB hardware key like in FPFM200 R1.0 EP1. There is no preinstalled license in factory.
If the upgrading licenses are ordered together with the equipment, licenses are
installed during commissioning.
In-field license upgrading is also supported, which can be done by Nokia Siemens
Networks service staff or by the operator themselves.
The upgrading can be done locally or remotely through the EMS (Element
Management System) while the equipment is running without traffic disruption.
12
FT48927EN03GLA0
2
2.1
FlexiPacket HUB 800 Indoor Unit

Introduction
FPH800 is an indoor unit with1U (1U=44.45 mm) high (Fig. 12).

It can be connected to Flexi-Packet Radio to support Ethernet uplink and downlink
traffic.
It offers advanced Ethernet processing features as well as maximum flexibility to
support TDM traffic via circuit emulation.
Access interfaces include Fast and Gigabit Ethernet, E1, and T1.
FPH800 provides STM-1(STM-4 will be supported in R2.5) interface for core net
access to fit the requirement of hub and edge site function; It also provides the
compatibility of Nokia Siemens legacy products.
The previous FlexiHopper (plus) family product is also supported.
FPH800 provides FlexBus (FB) interface for FTFA, FTFB, FIU19 (E), FXC RRI, and
IFUE and all other FB interface products.
FPH800 uses multi-slots structure with optional cards to fit the requirements of
different applications (Fig. 13). FPH800 includes the following parts:
Main board
16 x E1/T1 card
4 x GE card
2 x FlexBus card (available with the Release 2.0EP1)
2 x STM-1/4 card (available with the Release 2.5
Power injector card
ODU can be connected to FPH800 through a single Ethernet cable using ports with
ODU power feeding support. Alternative option is to use 2 cables (with a separate
power supply cable).
FPH800 can be commissioned by Nokia Siemens Networks FlexiPacket
Commissioning Tool through the local Ethernet connection.
FPH800 can be configured, monitored, and administered by Web-based Local Craft
Terminal (LCT) or Nokia Siemens Networks NetViewer management tool remotely
through connection via Data Communication Network (DCN).
FT48927EN03GLA0
13
FPH
800R2.0
R2.0EP1
SLOT 1
SLOT 2
Line cards
Card 16xE1 (with high density
connector)
Card 4xGbE (El.)
Power injector card (2xP+E
IN/OUT)
2x FlexiBus card (2.0EP1)
Main Board:
4x 100/1000 Base T (2 electrical ports with
embedded power to FlexiPacket Radio)
2x SFP (Port can be either Gb Eth or STM1

depending on equipped SFP)
16x E1
Local management Port
DCN port (10/100BaseT)
2 in and 2 out dry contacts
2 x STM-1/4 line card in SVR 2.5
2 x DC input -48V
Memory key (config backup/restore)
Fig. 12 FlexiPacket HUB800 Svr 2.0 (1)
14
FT48927EN03GLA0
2xPower Injector
4xGB(e)
2x Flex Bus
16xE1
2x STM1/4
Available with the Release 2.0EP1

Available with the Release 2.5
Fig. 13 FlexiPacket HUB 800 Svr 2.0 (2)
FT48927EN03GLA0
15
2.2
Interfaces
FPH800 supports the following interfaces:

Main board
2 x DC input (-48 V)
6 x GE interface, 4 for RJ45 and 2 for SFP (alternatively used by GE or STM-1 by
SW configuration)
16 x E1/T1 interface, 75 ohm/120 ohm,T1 100 ohm. MDR68 is used as front panel
connector
1 x dry contact (two input and two output, used for alarm interface)
1 x Out-of-Band port
1 x Alarm port
1 x DCN port
1 x USB key
Each of the two slots can support:
16 x E1 card
4 x GE card
2 x STM-1/4 card (R2.5)
2 x FlexiBus card (R2.0EP1) with Flexbus TNC connectors (local traffic)
power injector card (2xP+E IN/OUT)
WARNING
Up to 48 E1 can be managed per system: 16 E1 in Main Board, 32 E1 by means
of the two cards 16xE1.
WARNING
Up to 12 ODUs can be connected: 4 in Main Board and 8 by means of the two
4xGb card
16
FT48927EN03GLA0
2.3
Configuration Rules
Configuration rules are reported in Fig. 14.
Full configuration flexibility with line cards into Slot 1 and slot 2
FPH 800
R2.0EP1
SLOT 1
SLOT 2
Line cards
SLOT2
SLOT 1
Card
16xE1
Card
4xGbE
power
2x
injector Flexbus
Card
16xE1
OK
OK
OK
OK
Card
4xGbE
OK
OK
Ok
OK
power
injector
OK
OK
NO
OK
2x Flexbus
OK
OK
OK
OK
Fig. 14 Configuration Rules
WARNING
Only one power injector can be inserted in slot 1 or in slot 2
FT48927EN03GLA0
17
2.4
USB Key
The USB Key of FPH800 is used for the backup of IDU/ODU configuration and
software load.
FPH800 could start up and run without USB-key.
The USB Key is pre-formatted to FAT modes by the factory.
Configurations are handled by means of SNMP Set/Get requests and backup/restore
operations.
The configuration parameters are stored in a non-volatile memory.
After system startup they must be reloaded into RAM from the flash of FPH800,
translated into the hardware configuration and made available by the Agent for read
and modification by the EMS.
The following backuped information can be stored in USB key:
IDU Configuration data file

software load of IDU
software load of ODU
configuration of ODU
18
FT48927EN03GLA0
2.5
Internal fan tray
The internal fan tray will is used for the heat dissipation of FPH800.
The fan tray is an extractable unit with four fans mounted.
Fig. 15 Fan tray view
FT48927EN03GLA0
19
2.6
Power supply
FPH800 requires a power supply input of -48 V DC. The system is equipped with an
internal PSU (DC/DC unit) for the power feeding the internal circuitry.
The internally dissipated power is within 30 W, including the PSU efficiency.
FPH800 has two" -48 V DC" power feeding inputs (see Fig. 16).
It requires at least one - 48 VDC power feeding, however two DC power feedings are
recommended to support the power supply failure.
Fig. 16 Power feeding inputs
20
FT48927EN03GLA0
Besides the feeding of the internal circuitry, the IDU provides power feeding to the
connected ODUs.
The IDU forwards the DC battery voltage towards the central terminal of the Ethernet
transformers. See Fig. 17.
IDU continuously performs a load control to detect abnormal working condition.
Short-circuit protection of FPH800 prevents the system from over-voltage.
Fig. 17 Power supply
2.7
Handling requirements
FPHUB800 is sensitive to electromagnetic discharge. The user should be sure that

the module is properly grounded and wear an antistatic wrist wrap when handling it.
2.8
Reset
A reset button is located beside the USB key interface on the FPH800 front panel.
When the reset button is pressed, the microprocessor of the system is reset but
leaving the rest of hardware running.
FT48927EN03GLA0
21
2.9
Connection to FlexiPacket ODU
There are several ways to connect the FlexiPacket ODU and the FPH800:
through a single Ethernet cable with ODU powering support either from GE3 or
GE4on main board (Fig. 18)
one Ethernet cable from an ODU port on power injector card and a separate cable
connecting the corresponding Ethernet port on power injector card with a GE port
(GE1/GE2) on main board (Fig. 18).
one Ethernet cable from GE1 or GE2 or any 4x GE Port Card and a separate
cable for Power Supply (Fig. 19).
one Ethernet cable from an ODU port on the external power injector unit and a
separate cable connecting the corresponding Ethernet port on power injector unit
with a GE port (GE1/GE2) on main board
(Fig. 20).
Two types of external Power Injector are available: Indoor Power Injector (to interface
up to 4 FlexiPacket MultiRadios) and Outdoor Power Injector (to interface 1
FlexiPacket MultiRadio). In Fig. 20 the Indoor Power Injector is shown.
Power
Injector Unit
Power plus ethernet
Power plus ethernet
Fig. 18 Connection to FlexiPacket ODU (1)
22
FT48927EN03GLA0
Power
Power
ethernet
ethernet
Power
Power plus ethernet
Power plus ethernet
FT48927EN03GLA0
23
2.9.1
Deploying Power plus Ethernet (P+E)
1 Power Injector card supported

P+E 3
P+E 4
Ethernet 1
Ethernet 2
P+E 1
P+E 2
2x Power Injector
Fig. 21 P+E
Due to the attribute of the circuitry of P+E interface, it is harmful to plug and unplug
the UTP cable to and from the P+E interface very frequently with short intervals. It is
strongly suggested to leave at least 5 seconds between plugging and unplugging
(and vice-versa) the cable.
When using P+E ports of IDU to feed DC power to ODUs, please keep the P+E cable
and the DC input voltage to IDU within the safe border reported in Fig. 22
and the overall current to all the ODUs should be lower than 6A.
Nokia Siemens Networks

length
WARNING
The P+E solution is not compatible with Power over Ethernet (PoE) defined by
IEEE 802.3af and 802.3at since P+E intends to provide higher power (watts)
than that provided by the two standards. Thus, it is harmful to connect FPH800
P+E interfaces to other devices than NSNs FlexiPacket ODUs.
WARNING
It is forbidden to connect other P+E ports (for example, the P+E ports of the
external Power Injector) to the P+E ports of FPH800 whether the P+E function
of FPH800 is disabled or enabled.
24
FT48927EN03GLA0
2 x ODU
4 x ODU
Mainboard
Max IDU- ODU distance 100m

Voltage limits: 40.5V<V<53V
PWI Card
Max IDU- ODU distance 80 m

Voltage limits: 40.5V<V<53V
Max IDU- ODU distance 80m

Voltage limits: 43V<V<53V
FPH 800 Mainboard supports 2 ODUs with P+E, IDU-ODU lengths up to 100m.
when FPH 800 is supporting 4 ODUs with P+E (2 on Mainboard and 2 with
Power Injector card) the minimum voltage is - 43 V and max IDU-ODU
distance is 80m.
Minimum voltage shall be considered
Fig. 22
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
FT48927EN03GLA0
. . . . . . .
. . . . . . .
. . . . . . .
Nokia Siemens Networks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
25
2.10
LED Indications
FPH800 LEDs located on the front panel are reported in Fig. 23.
Fig. 23 LED information
FT48927EN03GLA0
27
2.11
Licensing
The NSN license management principles are adopted by the FlexiPacket Hub
architecture:
the customer who wants to use certain feature has to purchase the corresponding
license. A license can be bought by the customer together with the hardware and
the application software with the initial purchase order, or it can be later purchased
and installed into an already operating appliance.
The following functions require software license:
Ethernet OAM support

MSTP/RSTP
1588 v2 precision time protocol support
Security
G.8031 Ethernet Linear Protection(2.0EP1)
CES Linear Protection(2.0EP1)
The basic configuration is defined as follows:
enabling all the E1, STM-1 and Ethernet ports in Main Board
All SW features out of scope of licenses
The secure management protocols associated to the security license are the
following:
SNMP v3.0
SSH
SFTP
Https
In-field license upgrading can be done by NSN service staff or by the customer.
In-field upgrading of licenses is supported locally and remotely through ClicS with
web, SMS while the equipment is running and without traffic disruption.
Each generated license allows the activation of the related feature.
License is in alphanumeric code format

License is delivered via
28
ClicS web interface (NOLS)
SMS text message request to ClicS
FT48927EN03GLA0
FM200/FPH800 Main features
3.1
Introduction
FlexiPacket First Mile 200/ HUB 800 main features are:
Carrier Ethernet Services (E-Line/E-LAN) according to MEF (Metro Ethernet

Forum) service model
QoS
Circuit Emulation Service (CES) via TDM over Packet (TDMoP)
Synchronization over Packet networks
LLDP (Link Layer Discovery Protocol)
RSTP/MSTP (Rapid Spanning Tree Protocol/Multiple Spanning Tree Protocol)
Web-based Local Craft Terminal (LCT) management
Performance Management
Security Management
Ethernet OaM
FT48927EN03GLA0
29
3.1.1
E-Line service
FM200/HUB 800 supports both E-Line service and E-LAN service.

In E-Line service, traffic from any configurable port can go to any other configurable
port.
In Fig. 24, packets received from ingress port, are parsed and processed, e.g.,
policing, countering, editing etc.
The selection of egress port is not based on L2 bridging, but it's based on rule
definition.
Fig. 24 E-Line illustration
30
FT48927EN03GLA0
3.1.2
E-LAN service
E-LAN service is based on L2 bridging by learning the source MAC address and
matching the destination MAC address. The packet destination MAC address +
VLAN ID determines its egress port, see the illustration in Fig. 25.
E-LAN service is a multipoint-to-multipoint service that can be used for both
management plane (management E-LAN) and for data plane. For example in 4G
networks, packets received from a BTS can be directed either to core network or a
neighbor BTS, the forwarding decision is based on destination MAC address
matching.
Fig. 25 E-LAN service illustration
3.1.3
UNI port shutdown on service failure
UNI port is switched off in case of loss of E2E connectivity.

This feature is only applicable when there is only one E-line service on a UNI.
When a UNI has multiple E-Line services or E-LAN service on it, this feature cannot
be applied to this UNI.
It's used to fast forward the loss of connectivity (e.g. due to microwave link
propagation outages, or equipment failure) to connected device.
FT48927EN03GLA0
31
3.1.5
TDM over Packet
The TDMoP processing in FlexiPacket FM200/ HUB 800 R2.0 complies with:
RFC5086 standard for CESoP

RFC4553 for SAToP
CESoP features are reported in Fig. 39.
SAToP features are reported in Fig. 40.
WARNING
SAToP and CESoP mixed configuration: Each E1 tributary or VC12 of STM-1
can be configured either as SAToP or CESoP independently
TDM Pseudo Wire Emulation with CESOP

TDM PWE:
CES over IP (CESoPSN) with and without Real Time Protocol RTP (RFC 5086)
64Kb/s (time slot) granularity
TDM synchronization per port. Sources:
System clock
Loopback: clock from ingress signal of the port
Differential clock recovery: used on top of system clock to manage different clock
domain for different E1
Interfaces:
E1/T1
VC-12 ch-STM-1
TDM performance monitoring according to G.826

PWE related performance monitoring
Fig. 39 TDM PWE with CESoP
40
FT48927EN03GLA0
TDM Pseudo Wire Emulation with SATOP

TDM PWE:
SATOP: Structure-Agnostic TDM over Packet (RFC 4553)

Encapsulation: IPV4/IPV6 with UDP
TDM synchronization per port. Sources:
System clock
Loopback: clock from ingress signal of the port
Differential clock recovery: used on top of system clock to manage different clock
domain for different E1
Interfaces:
E1
VC-12 ch-STM-1 (FPH800)
TDM performance monitoring according to G.826

PWE related performance monitoring
Fig. 40 TDM PWE with SATOP
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
FT48927EN03GLA0
. . . . . . .
. . . . . . .
. . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
41
3.1.6
Synchronization over packet networks
Synchronization on FlexiPacket HUB800 is reported in Fig. 42 and in Fig. 43.
Synchronization on FlexiPacket FM 200
E1 interface
FlexiPacket
FM200
Synchronous
Ethernet
FlexiPacket FM 200
System clock source from
physical i/f
Synchrounous Ethernet
E1
(Master/Slave) over all Ethernet
interface
ports
Support of SSM for clock
Synchronous
source management
Ethernet
Fig. 41 Synchronization on FlexiPacket FM 200
Synchronization on FlexiPacket Hub 800
E1 interface
Synchronous
Ethernet
FlexiPacket
Hub 800
IEEE1588 ToP
slave ck
FlexiPacket Hub 800

System clock source from
physical i/f or ToP slave
ToP IEEE1588-2008 slave

E1
clock
interface
ToP IEEE1588-2008 boundary
clock (FP Hub 800 R2.5)
Synchronous
Ethernet
Synchrounous Ethernet
(Master/Slave) over all Ethernet
ports
Support of SSM for clock
source management
Fig. 42 Synchronization on FlexiPacket HUB 800
42
FT48927EN03GLA0
Synchronization
FM200/FPH800
R2.0/R2.0 EP1
System Clock
Source (user configurable) selection from:
any Ethernet port (SynchEth)
any TDM port
ToP slave (only FPH800)
Internal clock with hold over state and Free running state
TDM ports
Generation of empty (w/o traffic) synchronization E1 as clock source
AIS generation in case of synch degradation (config. threshold)
Synchronous Ethernet over all Ethernet ports
According to G.8261/G.8262/G.8264
Support of SSM
Timing over Packet IEEE 1588-2008 (only FPH800)
Slave in FPH800 Main Board
Support up to two masters (redundancy)
Fig. 43 Synchronization on FlexiPacket HUB
The FlexiPacket FM200/ HUB 800 system can operate in two clock modes as:
normal mode
SSM (Synchronization Status Message) mode
In normal mode, if one E1 or one Ethernet interface is selected as synchronization
source, when the source fails the system goes to internal source (holdover or freerun
state).
While two synchronization interfaces are selected, one as primary source and the
other as secondary, when the primary source is not available, the system
automatically uses the secondary one.
Once the primary source is recovered, the system comes back to the primary source
if the revertive mode is set, or stays on the secondary source if the non-revertive
mode is configured.
In SSM mode, the system selects the best synchronization source based on following
criteria stated in the SSM message received:
signal fail
signal received QL (Quality Level)
priority
External commands
FT48927EN03GLA0
43
3.1.6.1
Synchronization states
If using internal source, only one synchronization state is foreseen: freerun.

If using external source, the following states are foreseen:
Freerun: this is the state selected after startup. The system will keep on working in
this state if there is no valid source available.
Locked: this is the state selected after a qualified reference source is available at
the selected interface and no synchronization alarms are present.
Holdover: this is the state selected when the reference source is no longer
qualified due to some problems.
3.1.6.2
TDM synchronization interface
Two E1/T1 interfaces can be selected as TDM synchronization output interface.

The E1/T1 interface selected as TDM synchronization output interface carries a
locally generated E1/T1 with pseudorandom payload in case of no synchronization
alarms; vice versa it carries full Alarm Indication Signal (AIS) in case of
synchronization alarms exist.
WARNING
The E1/T1 interface selected as TDM synchronization output interface is not
bounded to a TDMoP EVC and does not carry usable traffic.
An E1/T1 port can be used as TDM synchronization input interface. The system
detects alarms related to the TDM synchronization input interface as in the following:
LOS (local alarm, the traceability to PRS is lost)

AIS (remote alarm)
structured E1/T1 with pseudorandom payload
full pseudorandom payload
44
FT48927EN03GLA0
3.1.6.3
ToP IEEE1588V2 slave /boundary clock (only for HUB800)
The IEEE1588V2 protocol is implemented inside FPHUB800 Release 2.0 (Fig. 44).
The HUB can be configured like ToP Slave.
Two Master Clock connections are supported for redundancy.
WARNING
ToP Boundary clock will be available with the Release 2.5EP1
FPHUB800 Synchronization Timing Over Packet - slave
Timing over Packet (IEEE1588-2008)

slave in FPH800 MainBoard
Support up to two master (redundancy)
FPH800
R2.0/R2.0 EP1
1588
master
2M
Packet
BTS
(w/o 1588v2)
FPH800
Timing packets
controller site
Fig. 44 FPHUB800 ToP Synchronization
FT48927EN03GLA0
45
3.1.7
Link Layer Discovery Protocol
LLDP is supported in FM200/ HUB 800 R2.0/2.0EP1 to advertise the system key
capabilities on the Ethernet LAN and also learn the key capabilities of other systems
on the same Ethernet LAN.
Information like system name and description, IP management address, etc., can be
sent or received as LLDPDU (LLDP Data Unit) for every station to know their
neighbors.
LLDP frames are sent at a fixed rate on each port of every station and no
acknowledgement is expected from the receiver.
It is so-called one way connectionless data link layer protocol which runs on MAC
layer.
LLDP allows the NMS to build the physical topology of the network under its
supervision.
The NMS can only get a complete picture of the controlled network when all the NEs
support LLDP.
WARNING
For the detailed information of LLDP, please refer to IEEE 802.1 ABTM-2005.
46
FT48927EN03GLA0
3.1.8
Link Aggregation Groups (LAG)
Link Aggregation grouping is performed according to the IEEE802.3 clause 43

standard.
Link Aggregation allows multiple links to be aggregated together to form a Link
Aggregation Group (LAG) as reported in Fig. 45.
A MAC Client treats the LAG as if it were a single logical link.
For Bridge functionality (i.e. VLAN, STP, etc.), the LAG is considered as a single
bridge port.
A LAG operates in CET mode and is supported on UNI ports.
The LAG consists of N parallel, full-duplex, point-to-point links operating at the same
speed between a pair of systems.
3G
LAG
3G
HUB
HUB
2G
3G
Aggregation
Multiservice router
/ switch
2G
Fig. 45 Link Aggregation Group
FT48927EN03GLA0
47
3.1.9
Spanning Tree Protocol
STP (Spanning Tree protocol) is supported in FlexiPacket FM200/ HUB 800 to

provide a loop-free redundant network topology.
Besides basic STP configuration, RSTP (Rapid Spanning Tree Protocol) and MSTP
(Multiple Spanning Tree Protocol) are supported.
RSTP(IEEE 802.1w) supersedes the basic STP (IEEE 802.1D).It provides rapid
reconfiguration of the spanning tree active topology in case of physical network
changes with reduced port states as forwarding, learning, and discarding only.
MSTP (IEEE 802.1) allows frames assigned to different VLANs to follow separate
paths, each based on an independent MSTI (Multiple Spanning Tree Instance), within
MST (Multiple Spanning Tree) regions composed of LANs and MST bridges. That is
to say each VID is mapped with a MSTI.
WARNING
FlexiPacket FM200 R2.0 supports up to 8 MSTI instances
WARNING
FlexiPacket HUB 800 R2.0 supports up to 16 MSTI instances
3.1.10
Web-based LCT management
Through an embedded LCT program in FPFM200/HUB800, the user can access the
system through the network and launch the LCT program to monitor, administer, and
configure the system remotely.
All the parameters are divided into different groups, such as Hardware, Service,
Licensing, etc.
WARNING
For detailed information, please refer to Operate and Maintain chapter.
48
FT48927EN03GLA0
3.1.12.4
Account log
FlexiPacket FM200 HUB800 R2.0/2.0 EP1 embedded software stores a list of

records (up to 120 records) regarding log actions (Login or Logout) performed by
users.
All successful log actions will be recorded.
Each record includes the following information fields:

IP address of the user
Authentication name or community in case of SNMPv2c
Protocol type
Log action type (login, logout, password)
Date and time of the log action
Once an alarm is triggered, it needs to be downloaded and cleared from EMS.
Then NE clears alarm.
Following is the procedure for the alarm and log file:
NE sends the alarm to EMS

Download log file from NE and clears the log file manually
NE clears alarm
FT48927EN03GLA0
59
4
4.1
First Mile200/ HUB800 Management

Network management using Nokia Siemens
Networks NetAct
Nokia Siemens Networks NetAct (later referred to as NetAct) is the central network
management system for collecting alarms and measurement data from
FPFM200/HUB800 and associated FlexiPacket radio in the network.
Communication between NetAct and the network elements is enabled via IP DCN.
Fault and performance management data is collected to NetAct via NetViewer-NetAct
Connector that's integrated to NetViewer EMS.
WARNING
For more detailed information, please refer to NetAct documentation.
4.2
Network management using Nokia Siemens

Networks Net-Viewer
NetViewer is a PC-based software application for controlling and monitoring

FlexiPacket FM200/ HUB800 and associated FlexiPacket Radio.
NetViewer communications with FlexiPacket FM200/ HUB800 via IP DCN.
It reads and interprets the information directly from the node and the information can
then be easily modified and sent back to the node.
WARNING
For more detailed information, please refer to NetViewer documentation.
FT48927EN03GLA0
61
4.3
Network management using Web-based LCT
Embedded FlexiPacket FM200 HUB800 LCT program can be launched as a Java

program through the network connection. With the user-friendly GUI, the user can do
the following task:
Device settings
NE management
Clock synchronization setting
Ethernet general configuration
Service management
QoS setting
Protection settings
OAM configuration
Performance settings
Maintenance settings
Security settings
WARNING
For the detailed information about Web-LCT and how to manage FM200/
HUB800 using web-LCT, please refer to the Operate and Maintain manual.
62
FT48927EN03GLA0
4.3.1
Accessing IDU
FlexiPacket FM200/HUB800 IDU has a default private IP address for local

management and a default public IP address for remote management, see Fig. 50:
Fig. 50 Accessing IDU
4.3.2
SNMP agent
FlexiPacket FM200/HUB 800 has an inbuilt SNMP (Simple Network Management

Protocol) agent that provides management functions for the whole radio terminal.
Fault, performance, and configuration management functions can be performed using
SNMP actions. The version supported is the SNMP version 2c.
4.3.3
SNTP, FTP, and Telnet
The SNTP (Simple Network Time Protocol) functionality is used to update the nodes
real time clock by connecting to an NTP server, which must be accessible through
the IP-based DCN.
The SNTP can be enabled or disabled in Element Manager.
FTP (File Transfer Protocol) is supported for the purpose of software download and
large file size, e.g., performance monitoring data.
Telnet is supported for remote command interface control.
FT48927EN03GLA0
63

HUB Structure PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

HUB Structure PDF

Загружено:

Авторское право:

Доступные форматы

FlexiPacket HUB Structure

Fig. 1 Front panel view in R2.0 EP1

FlexiPacket HUB Structure

FlexiPacket HUB Structure

Fig. 4 SFP connectors

FlexiPacket HUB Structure

equipment configuration data

Fig. 5 The Reset button

FlexiPacket HUB Structure

FPFM200 requires a power supply input of -48 VDC.

Fig. 6 Fig. 6 Power supply

FlexiPacket HUB Structure

Connection to FlexiPacket ODU

There are two ways to inter-connect FlexiPacket ODU and FPFM200:

Power plus Ethernet

Up to two Link Protection Groups (LPG) can be configured:

FlexiPacket HUB Structure

System (Fig. 8 and Fig. 10)

Fig. 8 System and Memory Key LEDs position

FlexiPacket HUB Structure

Fig. 10 System and Memory Key LEDs meaning

FlexiPacket HUB Structure

configuration 1 + 1 hot standby (HSB) is not enabled.

Support of RSTP/MSTP: Rapid Spanning Tree Protocol/Multiple Spanning Tree

Support of OAM (Operations, Administration and Maintenance)

FlexiPacket HUB Structure

FlexiPacket HUB 800 Indoor Unit

FPH800 is an indoor unit with1U (1U=44.45 mm) high (Fig. 12).

FlexiPacket HUB Structure

2x SFP (Port can be either Gb Eth or STM1

2 x STM-1/4 line card in SVR 2.5

Memory key (config backup/restore)

Fig. 12 FlexiPacket HUB800 Svr 2.0 (1)

FlexiPacket HUB Structure

Available with the Release 2.0EP1

Fig. 13 FlexiPacket HUB 800 Svr 2.0 (2)

FlexiPacket HUB Structure

FPH800 supports the following interfaces:

FlexiPacket HUB Structure

Configuration rules are reported in Fig. 14.

Fig. 14 Configuration Rules

FlexiPacket HUB Structure

IDU Configuration data file

FlexiPacket HUB Structure

Internal fan tray

Fig. 15 Fan tray view

FlexiPacket HUB Structure

Fig. 16 Power feeding inputs

FlexiPacket HUB Structure

Fig. 17 Power supply

FPHUB800 is sensitive to electromagnetic discharge. The user should be sure that

FlexiPacket HUB Structure

Connection to FlexiPacket ODU

Power plus ethernet

Power plus ethernet

Fig. 18 Connection to FlexiPacket ODU (1)

FlexiPacket HUB Structure

Fig. 19 Connection to FlexiPacket ODU (2)

Power plus ethernet

Power plus ethernet

Fig. 20 Connection to FlexiPacket ODU (3)

FlexiPacket HUB Structure

Deploying Power plus Ethernet (P+E)