008. FPMR Commissioning.pdf

.

FlexiPacket MultiRadioRel. 2.4

Configuring FPMR

Extracted from A25000-A1600-B030-01-76P1

Issue: 1 Issue date: February 2012

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their components.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

.

.

A25000-A1600-B030-01-76P1Issue: 1 Issue date: February 2012

29

Commission Requirements for WebLCT PC

4 Requirements for WebLCT PCRefer to Table 4 Test Instruments on page 15.

.

.30 A25000-A1600-B030-01-76P1Issue: 1 Issue date: February 2012

CommissionPC connection to the FlexiPacket MultiRadio

5 PC connection to the FlexiPacket MultiRadio • Connect the Ethernet interface of the PC to the FlexiPacket MultiRadio depending

on the test bench scenario (refer to para. 2.2 on page 16). • FlexiPacket MultiRadio has two IP addresses:

• For the default configuration, the IP address of the PC needs to be 192.168.255.x, where x (between 4 and 253) provides an available IP address.

• If no DCN Planning configuration is available (or Stand alone Link) it is suggested to configure on the equipment the following IP addresses (refer to para. 6.7 to set these parameters).

Consequently the PC must be set with an IP address belonging to the same IP Subnet.

Before opening the PC it is suggested to verify the connectivity between the PC and the Equipment. To check apply a ping command from the Windows DOS Prompt.

IP Default IP address

IPpublic (configurable) 0.0.0.0

IPdefault (fixed) 192.168.255.3

Table 8 IP addresses scheme

FlexiPacket MultiRadio Configuration Description

Station A Station B

IP Address (1+0) 10.10.10.16 10.10.10.18

IP Addresses (1+1) 10.10.10.16

10.10.10.17

10.10.10.18

10.10.10.19

IP Netmask 255.255.255.0 255.255.255.0

DHCP Client Disabled Disabled

Table 9 FlexiPacket MultiRadio configuration

.

.


31

Commission Equipment configuration (station A)

6 Equipment configuration (station A)This chapter gives all the information to configure the main parameters of the NE in order to implement the commissioning.

t In case of 1+1 configuration configure first the Main FlexiPacket MultiRadio and then the Protection FlexiPacket MultiRadio.

Steps

1 Open the Web browser:

2 Enter http:\\192.168.255.3 (default IP address)

t From a single PC it is possible to open at least 16 WebLCT instances at the same time in order to configure at least 16 FlexiPacket MultiRadios.

3 The Java authentication screen opens.

Figure 14 Open NE screen

4 Enter:

• User name: admin • Password: sysmanager

t After the first launch you can install a shortcut into the desktop through the Java Control Panel.

5 The NE main view is presented.

.


CommissionEquipment configuration (station A)

Figure 15 FlexiPacket MultiRadio - Main view

The left-hand part of the window contains a tree structure organized in folders, which represent the main functionalities. In turn, each main functionality is divided into functions, according to the above structure. The Commission, included in Status and Config > Equipment, comprises:

• System Configuration • Operation Administration & Maintenance • Gbe: Physical • Gbe: Switch • Radio: BB Modem • Radio: RF • Networking • Date & Time

.

.


33


6.1 System Configuration

Figure 16 System Configuration

The dialog box is divided into System Type, System and Configure areas.

System Type areaSteps

1 In the System Type area click on the Change System Type button. The following screen opens.

2 Select the System Type and the Cables (one or two) to be used to interconnect the FlexiPacket MultiRadios to the Indoor Device. The supported configurations are shown in Table 10.

.



t Note 1 - In order to provide resilience against hardware failures FlexiPacket Multi-Radio supports two different behaviours according to the type of IDU which the Flex-iPacket MultiRadio is connected to:

• HW Protection mode 1 (CCM based): for interoperability with IDUs which support the protection mechanism (Ax200, and IDU FirstMile).

• HW Protection mode 3 (Standalone): for interoperability with a generic L2 Bridge which implements Learning, Forwarding and Filtering.

3 Select the Mode: CCM based or Standalone, as explained in the previous table. The mode can be changed only in configurations with 2 cables.

4 Only for 2+0 XPIC System Type select the Polarization to be associated to the FlexiPacket MultiRadio: horizontal polarization or vertical polarization.

5 Enter the P-CCM VID: specific VID for each Protection Group (from 16 to 49).

Configuration HW protection

Mode (Note 1)

ETSI supported

system type

NAM supported

system type

1+0 - x x

1+0 Ring - x x

1+1 Hot Stand-by - 2 cables CCM based x x

Standalone x -

1+1 Hot Stand-by - single cable - x -

1+1 FD - 2 cables CCM based x x

1+1 SD - 2 cables CCM based x -

2+0 FD - 2 cables CCM based x x

2+0 XPIC - 2 cables CCM based x x

Standalone x -

2+0 XPIC - single cable - x -

Table 10 System configurations

.

.


35


System areaSteps

1 Four comment fields are provided for Customer convenience: Name/Con-tact/Location/User Data.

2 Field Powered by can take one of the following values:

• Info Not Used: No information in the field • External PS: Power supply on the dedicated cable • Midspan-injector: Power supply coming from the Power Injector • Switch-pse: Power + Ethernet from the Indoor Device

This field is only for user information.

Configure areaSteps

1 Click on the Synchronization button to configure the synchronization parameters (refer to paragraph 6.1.1).

2 Click on the Protection button in case of 1+1 System Types to configure the protec-tion parameters (refer to paragraph 6.1.2).

6.1.1 SynchronizationClicking on the Synchronization button (in the Configure area of the System Config-uration menu) the Synchronization menu opens.

Figure 17 Synchronization

The menu has 2 tab-panels:

• In Use Configuration • Local Status

.



6.1.1.1 Synchronization parameter overviewDifferent parameters have to be configured:

• Operation Mode: to configure the direction of clock propagation; three options are available: • No clock transfer: the system is not configured to carry synchronization infor-

mation (Free Run); • Fixed Clock Transfer: the direction of the synchronization propagation is stati-

cally configured (by means of Source Port item in the Synchronization menu); it is not changed run-time based on quality or priority;

• Priority Based Clock Transfer: the direction of clock propagation is determined on the basis of the source priority: the source with the highest priority is the one selected as a source port.

• GbE source type: to declare if the characteristics of GbE interface are compliant to Synchronous Ethernet quality; to allow this interface to be selected as synchroniza-tion source this option MUST be flagged.

• Source for synch propagation: to select the source port. The effect depends on the selected direction of clock propagation: in particular, in case of : • No Clock Transfer: it has no effect; • Fixed Clock Transfer: it indicates the fixed clock source; • Priority based Clock Transfer: it indicates the preferred source clock (highest

priority). • SSM management: to enable//disable the management of SSM messages; two

options are available: • Disabled: it foresees the following behavior:

• The FlexiPacket MultiRadio does not handle the received SSM messages and it discards them;

• The FlexiPacket MultiRadio does not generate the SSM messages; • Enabled: The SSM messages are taken into account for determining the quality

associated to a synchronization source. This option has to be selected also in case of the quality of a source is forced by means of the clock source table in the synchronization menu.

t The Local capabilities field (menu GbE > Physical) must be set to 1000Base-T Full Duplex for the selection as synchronization source.

t The Synchronization via Synchronous Ethernet requires the configuration of the QoS capabilities for the proper management of the SSM messages. This configuration must be done in GbE > Switch menu.

Several parameters have to be configured: the first one is the classification criteria for the identification of the SSM messages. The criterion according to which they are clas-sified can be either:

• Ether-Type: the option has to be flagged; the value is 8809 (showed in this example)Or

• Destination MAC address: the value is 01-80-C2-00-00-02

In the EtherType Priority Add menu two parameters have to be configured:

• EtherType value (8809);

.

.


37


• Priority Value, which has to be set equal to a priority associated to a non-congestion subject WFQ queue.

t SSM management (Quality Level)The Sync source quality levels are transmitted via SSM messages. The SSM contains the quality level of the transmitting clock, and hence represents a unidirectional channel between the Sync control in the transmitter NE and that of the receiver NE.

The quality criterion can be disabled (enabled / disabled modes) upon configuration, that is quality level shall not be considered in order to choose the sync source.

In the disabled mode, the selection is based on the criteria of enabling / alarm / priority. Furthermore, no SSM messages shall be transmitted from the Sync interfaces, and possible received SSM messages shall be ignored. Finally, in this mode, lack of received SSMs is not considered a fault condition of the Sync source.

In the enabled mode, among all the available sources, the one with highest quality is selected. Only Sync sources with received quality level higher than QL-DNU are quali-fied for the system clock selection. A received signal carrying a SSM with QL-DNU must not be used for synchronization because a timing loop situation could result if it is used.

To protect against possible failure, the lack of the messages for a 5 second period is considered to be a failure condition. That Sync source is then subject to a wait-to-restore period (see below).

Upon reception of an event SSM, the QL state is changed to the new QL value, and the information timer is reset.

The transmitted SSMs contain the quality level of the selected source (and, as men-tioned, QL-DNU in case of free-running); however, in order to avoid timing loops, the system transmits from some interfaces the QL-DNU quality level instead of the system clock quality level.

More in detail, the system must always transmit an SSM with QL-DNU from the interface which is used as the actual synchronization source for the NE clock; the system must always transmit an SSM with QL-DNU from the 1000Base-T GbE interface if it is slave-clock; the other cases of QL-DNU insertion depend on the configured system type and are detailed within the relevant subsections.

.



6.1.1.2 Synchronization configuration

Steps

1 Click on the Modify button in the In Use Configuration tab-panel.

Figure 18 Modify

2 Select the Operation mode: No Clock Transfer/Fixed Based Clock Trasfer/Priority Base Clock Transfer.

3 Select in the GbE source type “Synchronous” to propagate the synch.

4 Select in the Source for synch propagation field the source to be used to lock the system clock:

1. “GbE”: the clock extracted from the Ethernet interface to the IDU;2. “Radio”: the clock extracted from the received radio data IDU;3. “ODU-ODU”: the clock extracted from the data received from the other co-

located ODU (only in Configurations with two FlexiPacket MultiRadios).

5 Select the SSM management (Synchronous Status Message): enabled/disabled.

6 If the SSM management has been enabled, the Port quality level area appear.

.

.


39


Figure 19 Port Quality level

If the ports, as default, are in “Auto”, the clock recovered from the in use sync source is transported on the ports. On the port currently in use as sync source is written “Don’t use” (qlDUS).

By clicking on Modify it is possible to force the quality level for each port.

7 In the Local Status tab-panel in the Clock source area a summary of the current synchronization is shown.

.



Figure 20 Clock source

8 In the Local Synchronization status area the following information is given:

• ODU synch status: the source to which the synch is locked; • Sync switch counter: number of the sync switches occurred from the last reset; • SSM missing check box: it is automatically flagged in case of loss of the SSM.

.

.


41


6.1.2 ProtectionClicking on the Protection button (in the Configure area of the System Configuration menu) the below menu opens.

Figure 21 Protection

This menu is divided in two areas:

• CCM (paragraph 6.1.2.1 on page 41) • Link Protection Group (paragraph 6.1.2.2 on page 42)

6.1.2.1 CCM areaThe CCM area is a read-only area showing the configuration and the status of the CCM.

Column VID shows the ID assigned to each CCM (Continuity Check Message):

• IDU (E-CCM): embedded in the IDU • Protection (P-CCM): this ID must be unique for each LPG connected to the same

IDU. It must be assigned when the System Type is assigned (refer to the System Configuration menu)

• ODU-ODU (A-CCM): this ID is fixed to 50 and it is the same for each LPG.

Table 11 shows the summary of the CCM in the different System Types.

.



t Legenda:ns = not supported / not presentx = supported/present- = not applicablex (only if activated) = supported if the relevant configuration is enabled.

6.1.2.2 Link Protection Group areaThis area allows to configure the role and the other parameters depending on the System Type as shown in Table 12.

System Type HW protection

Mode

ODU Role IDU (E-CCM)

ODU-ODU (A-CCM)

Protection (P-CCM)

1+0 Chain - x x (only if activated) ns ns

1+0 Ring - x x (only if activated) x ns

1+1 SD 2 cables1+1 FD 2 cables2+0 FD 2 cables

CCM based Don’t Care x x x

2+0 XPIC 2 cables CCM based Don’t Care x x x

Standalone Don’t Care ns x x

1+1 HSBY 2 cables CCM based Don’t Care x ns x

Standalone Don’t Care ns x x

1+1 HSBY 1 cable - Main ns x ns

Protection x (only if activated) x ns

2+0 XPIC 1 cable - Main x (only if activated) x ns

Protection ns x ns

Table 11 CCM use summary


Mode

Role/Status Interfaces

GbE Radio ODU-ODU

1+0 Chain - x x x inactive

1+0 Ring - x x x x

1+1 SD 2 cables1+1 FD 2 cables2+0 FD 2 cables

CCM based Active Master/Active Slave x x x

2+0 XPIC 2 cables CCM based Active Master/Active Slave x x x

Standalone Active Master/Active Slave x x x

Table 12 FlexiPacket MultiRadio Interfaces

.

.


43


The terminology used to identify the role and the status of the ODUs among the various System types is summarized in Table 13.

Main/Protection and Active/Standby: the first couple (it is a configuration) gives the priority of the ODU (useful when the revertive mode of operation is selected), while the second couple (it is a status) gives the actual role played.

Master/Slave configuration defines the priority of the ODU (useful when the revertive mode of operation is selected in the system types with two IDU-ODU cables), while the Active-Master/Active-Slave couple refers to the actual role played, which can change according to the status of the ODUs.

Steps

1 Set the Switching mode: revertive or unrevertive (available only with 1+1 HSB)

2 Set the Suspend interval: select the suitable time interval. Default: 160 sec. The Suspend interval is the time interval during which the controller is in freezing state. During this time the stand-by FlexiPacket MultiRadio receives no message from the active FlexiPacket MultiRadio, except the Suspend Interval message, which disables the switching for the time configured in the Suspend Interval.

3 Set the ODU role: depending on the configured System Type as shown in Table 12.

t The Force Down command acts on the protection group, causing a switching operation.

t The Rx Clock Switch field must be used to force the Rx switch in case of 1+1 FD or 1+1 SD.

1+1 HSBY 2 cables CCM based Active/Standby x x inactive

Standalone Active/Standby x x x

2+0 XPIC 1 cable

1+1 HSBY 1 cable

- Active Master x x x

Active Slave inactive x x


Mode

Role/Status Interfaces

GbE Radio ODU-ODU

Table 12 FlexiPacket MultiRadio Interfaces (Cont.)

Role Status

Main / Protection Active / Standby

Master / Slave Active-Master / Active-Slave

Table 13 ODUs roles

.



6.2 GbE - PhysicalFrom the left-side tree select GbE > Physical.

Figure 22 GbE - Physical (1+0)

Figure 23 GbE - Physical (1+1)

.

.


45


Steps

1 Verify that the Operational Status in the Ethernet area is up.

2 Set the MDI/MDI-X Autosensing field: automatic (default), manMDI and manMDIX. If set to Automatic the Ethernet cable to be connected to the FlexiPacket MultiRadio can be straigh or cross.

3 Set the Autonegotiation Protocol field: Enabled (default), Disabled.

If set to Enabled the bit rate and the operation type is automatically set by the Ethernet interface.

t In the Local Capabilities field, from the selection subwindow, select the desired value. The selected value is shown in Enabled Capabilities. It is possible to enter the max. capabilities to be negotiated.

4 For the 1000 BaseT interface the Autonegotiation Protocol must be always enabled. Use the default settings for the Master/Slave Selection field.

t To change the selection (Master or Slave) in the Synchronization screen the Settings must be Freerun (refer to par. 6.1.1).

5 The Flow Control field can be set to:

• Asymmetric Pause • Symmetric Pause • Asymmetric & Symmetric Pause • No Pause

6 Configure the Fast link down feature, if required.

When disabled, the link down is reported following IEEE standard after 750ms. When enabled, the notification is sent after the timeout defined in the Fast link down timing field.

7 Configure the Interface Shutdown on Radio Link feature (if required).

This features is available only with the System Types 1+0 and 1+0 Ring.

The user can enable/disable the feature and set its related configurable parameters:

• Interface Down Time:It is the time after which the Ethernet interface is turned on again.Range: [1…30]Default value: 6 secs. Step: 1 sec.

• Wait to Restore Time:It is the time that must elapse before enabling the radio port of the switch after the air-loss condition has ended.Range: [30...300]Default value: 60 secs. Step: 10 secs.

t This feature (available only in 1+0) speeds up the reconfiguration of the FlexiPacket MultiRadio-based rings beyond the possibilities of the standard xSTP protocol.

In a scenario defined by ring topology managed by RSTP, the FlexiPacket MultiRa-dio is requested to signal to the IDU, that runs the RSTP, a loss of connectivity on the radio interface by shutting down the GbE interface.

.



The IDU reacts instantly, i.e. not waiting for the timeout defined in the protocol, to such event (Ethernet link-down) by re-routing the data traffic towards the other direc-tion in the ring.

The behavior is:

• Upon detection of air-loss condition, the Ethernet interface of the GbE port is shut down, so that a link loss is detected at the other side of the Ethernet con-nection.

• The radio port of the switch is disabled (in order to avoid unidirectional link after the connection with the IDU has been restored) and the MAC forwarding table of the bridge is flushed.

• After a configurable timeout has elapsed the Ethernet interface is turned on again (to allow local management).

• The radio port of the switch is restored after the air-loss alarm is off only when a wait-to-restore time has elapsed.

8 Press pushbutton Reset to restart the physical interface.

.

.


47


6.3 GbE - SwitchFrom the left-side tree select GbE > Switch.

Figure 24 Switch configure

In the screen seven areas are present, which have to be configured:

1. Forwarding area2. VLAN Support area3. E1 Prioritization area4. Header Compression5. Priority Settings6. Scheduling7. Jumbo frame management

.

.


71


6.4 Radio - BB/ModemFrom the left-hand side tree select Radio > BB-Modem.

Figure 59 BB/Modem Configuration

To change the parameters click on the Modify button. The following screen opens.

Steps

1 Select the Standard mode according to the market: etsi or ansi.

2 Select the Channel bandwidth.

.



3 Select the Profile Criteria: "Standard profile" or "High Performance profile". In the latter case the LDPC (more robust) coding is used.

4 Select the ACM TX: adaptive or static.

5 If the Static Modulation has to be used, enter in the relevant Tx Static Profile field the Modulation scheme to be used:

• QPSK • 16 QAM • 32 QAM • 64 QAM • 128 QAM • 256 QAM

t In Rx side the Modulation scheme automatically changes according to the Modula-tion scheme used in Tx side in the remote equipment.

6 If the Adaptive Modulation has to be used, enter the Lowest Tx Profile and the Highest Tx Profile.

t In Rx side the Modulation scheme automatically changes according to the Modula-tion scheme used in Tx side in the remote equipment.

7 Click OK to confirm the new parameters.

t By clicking on Profiles Details the following read-only screen opens.

Figure 60 Profiles Details

This screen shows the modulation schemes selected for the Adaptive Modulation, the max. Tx power for each modulation scheme and the switching thresholds (based on the S/MSE) from one modulation scheme to another one.

.

.


73


6.5 Radio - RFFrom the left-hand side tree select Radio > RF.

Figure 61 RF Configuration (ATPC)

Figure 62 RF Configuration (RTPC)

.



Steps

1 Click on Service State field. The Input dialog box appears.

Figure 63 BB/Modem Configuration: service state selection

2 Tick up and click on OK.

3 Enter the Tx RF frequency (in kHz) in the Tx Value field or Rx RF frequency (in kHz) in the Rx Value field (250 kHz steps). The dual RF frequency (Rx or Tx) is automat-ically calculated according to the selected frequency and the frequency shifter.

Figure 64 Tx RF frequency

4 If the ATPC is not used, enter the Tx Power value (RTPC).

Figure 65 RTPC

5 Enable the ATPC, if required, and enter the relevant parameters.

Figure 66 ATPC

.

.


75


6 The Continuous Wave Test is only for maintenance and test purposes. With this test the RF Transmitter emits an unmodulated carrier.

Figure 67 Continuous Wave Test

7 By clicking on HW Parameters button the following screen opens.

Figure 68 HW Inventory

This screen is read-only and shows the remote inventory of the FlexiPacket Mul-tiRadio.

.



6.6 Station A correct operation checkCheck the correct operation of the station by using the RF loopback.

t The loopback cannot be performed in 1+1 configuration.

Steps

• When the time for the RF loopback is over, click on the pushbutton View Result. • File TestLoopResult.xml opens. If during the loopback no error occurred, station

A works properly: In Bad Octets counter must be zero, In Octets counter must be equal to the Out Octets counter and both must be in the In Good Octets counter.

t The report file can be exported by clicking on the button Export XML.

.

.


77


6.7 IP address assignmentFlexiPacket MultiRadio has two IP addresses.

t The IP default address is always available. By using this address the NE is always reachable from the Ethernet interface (not from the Radio side).

t The Management VLAN is used only with the IP public address.

FlexiPacket MultiRadio supports a DHCP client in order to automatically retrieve IPpub-lic, subnet mask and default gateway parameter settings. DHCP client can be enabled / disabled; DHCP client is default-set to enabled.

It is assumed that only one DHCP server is present in the LAN, so that the response to the broadcast DHCP discovery is unique.

With DHCP client disabled, the IP address, subnet mask and default gateway can be manually configured by using the Admin user privileges.

IP Reference Scenario

IPpublic Used for remote or local management operations

IPdefault Used to access the ODU locally without knowing the IPpublic or IPpri-vate. It is a fixed address.

Table 14 IP addressing scheme

.



Steps:

1 From the left-side tree select Status and Config > Equipment > Networking.

2 Select the IP Settings tab-panel.

Figure 69 Networking

3 Click on IP Setting Mode field. The following Input dialog box opens.

Figure 70 IP Setting Mode

4 Tick check box Obtain an IP address Automatically, if the DHCP Client has to be used, otherwise tick check box Use the Manual IP Settings and click on OK.

Configurable parameters Default configuration

DHCP enabling Enabled

IPpublic address 0.0.0.0

Subnet mask 255.255.255.0

Default gateway 0.0.0.0

Secondary gateway 0.0.0.0

Table 15 Available parameters for DHCP

.

.


79


5 In the Manual IP Settings area click on Modify. In the Input dialog box enter the IP parameters according to the DCN plan.

6 If the IP Setting Mode is Obtain an IP address automatically, the DHCP Setting area is available. In this area set:

• Discovery Message IntervalTime interval (ms) for discovery messages issued before the client received the first reply. Range is 0 - 2,147,483,647 and default value is 125.

• Lease TimeRequested lease time option to be used with DHCP Discover or DHCP Request messages. Range is 0 - 2,147,483,647 and default value is 24.

• DHCP RestartDHCP protocol restart command. Any value set greater than 0 causes the IP address to be renewed.

7 Enter the parameters of the default Gateway by clicking on Modify. The default Gateway could be a Router, if FlexiPacket MultiRadio is connected to a router.

8 Enter the IP address of the Secondary default Gateway, if any.

9 In the Management VLAN Management tab-panel enter the VLAN id to be used for the “In Band” management and the relevant Priority (VPRI from 0 to 7).

.



10 In the LLDP tab-panel you can activate (if required) the Physical Topology Discov-ery.

11 The LLDP protocol (Link Layer Discovery Protocol) can be enabled on the Giga Ethernet port and on the Radio port to discover the neighbouring NEs connected to these ports.

The enabling can be:

• txOnly: the information is only transmitted to the neighbour, but nothing is read in Rx side;

• rxOnly: the information is received from the neighbour, but nothing is transmit-ted;

• txAndrx: the information is send and received.

12 In the Tx Message Rate and Time To Leave Multiplier fields keep the default values.

13 Press LLDP Information button to show the list of the neighbouring NEs.

.

.


81


14 Press the Static Information button to insert manually the neighbour NEs which do not have the LLDP feature. Click on Add and insert the NE parameters.

t The LLDP protocol is used to allow the NMS to build the physical topology of the network under its supervision. In order to obtain a complete picture of the network controlled, the underlying assumption is that all the Network Elements in the con-trolled network support the LLDP protocol. An example is shown in figure below, where the NMS is able to build a draw of the physical connections between the Network Elements by inspecting the information stored in the MIBs.

Figure 71 Physical Topology discovery via LLDP

.



15 In case of configuration with 2 FlexiPacket MultiRadios with single cable, assign the IP address of the colocated ODU in menu Operation, Administration and Main-tenance >tab-panel Colocated ODU Config.

6.7.1 Networking parameter change in the “Single cable” configurationsThis paragraph gives the sequence of steps to be adopted in order to make effective the Networking Parameters in the Co-located ODU in "single cable" protected system types (1+1 HSBY 1c and 2+0 XPIC 1c). This workaround is needed because, following a change in the Networking parameters of the Co_localed ODU (IP_address, IP_mask, IP_gateway and M_VID) configured in the Direct_Connected ODU (and sent to the Co_located via LLDP Protocol), these new parameters are not effective. The new parameters can be made available in different ways:

• HW Reset of the Direct_connected ODU, • Disabling/Enabling of ACCM Timer and Disabling/Enabling MAC Learning in Direct

Connected ODU • Topology change (disconnect and reconnect the ODU-ODU cable or connect/dis-

connect the GbE cable of Co-located ODU)

.

.


83


Figure 72 Single cable topology

The above triggers must be done after the modifications of the Network parameters.

Three cases are taken into account:

1 New Installation - In this case, for simplicity, it is suggested to perform an HW Reset on the Direct Connected ODU as workaround for the described problem.

2 Swap&Repair - In this case, since it is possible that live traffic is running in the Direct Connected ODU, is strongly suggested not to issue the HW Reset on this ODU, but apply on the same ODU the procedure described here below.

3 Networking parameters change - Also in this case it is suggested to apply the pro-cedure described below (a part the cases, where no live traffic is running in the Direct Connected ODU).

.



Procedure

f WARNING! - Disable the “Transfer IP Address to colocated ODU” functionality as shown in the figure, before to run the commands on port 23001 and do not re-enable it

t 172.31.219.105 is supposed, in the following procedure, to be the Public IP address of the Direct Connected ODU.

a) telnet 172.31.219.105 23001 (telnet connection to the Public IP address and PORT 23001)

b) admin (user ID)c) sysmanager (PSWD)d) [RTP]>e) [RTP]>cmd f) [WxWorks *]#g) [WxWorks *]# rtp (will dispay a 0xabcdef register address)h) [WxWorks *]# rtp attach 0xabcdefi) [uApplication]#j) [uApplication]# func call &disableTimerClkACCM &k) wait T (5 seconds)l) [uApplication]# func call &enableTimerClkACCM &m) [uApplication]# func call &LearningDisable &n) [uApplication]# func call &LearningEnable &o) [WxWorks *]# rtp detach 0xabcdefp) [WxWorks *]#Cq) [RTP]> logout

.

.


85


6.8 Date & Time configurationThe date and time have a particular importance during the execution and the analysis of the measurements and recordings on the equipment.

The date and time configuration can now be executed only in case of login with admin-istrator privileges and of proprietary synchronization.

6.8.1 Manual setting of date and time

Steps

1 Select menu Status & Config > Data & Time.

2 In the “Manual Settings” area press Host Time button; the PC date and time will synchronize the FlexiPacket MultiRadio.

Figure 73 Manual setting of date and time

3 As an alternative in the “Manual Setting” area the time can be manually selected.

6.8.2 Synchronization of the NE via Time Server SNTP (Time server Setting)It is possible to synchronize the clock of the NE to the time reference provided by a SNTP Time Server reachable via IP network.

The Time Server distributes the GMT time, which can be adjusted depending on its own time zone and of the daylight saving time.

Selecting Time Server Configuration command in the Time Settings menu opens the Time Server IP Address window , where it is possible to enable and configure the SNTP synchronization

The default value of the address IP of the Time Server (0.0.0.0) causes the disabling of the SNTP synchronization.

Figure 74 Synchronization of NE via Time Server SNTP

Steps

1 Insert the IP address of the SNTP Time Server in the IP address field.

.



2 Select the offset to correct the GMT time in the Time Zone field. The possible offset values go from GMT-12 to GMT+13.

3 To correct the time reference of the SNTP synchronization (addition of the GMT time received by the Time Server and the possible correction due to the time zone) according to the daylight saving time, select the Daylight saving time check-box.

6.9 Before leaving terminal station AIn order to prepare the system configuration for the antenna adjustment phase (align-ment) set the Tx Power data with the ATPC Disable mode with the Maximum power transmission and disable the Adaptive Modulation (if configured).

Disconnect the PC and move to the opposite station.

t After the antenna alignment reconfigure the ATPC and the Adaptive Modulation as the project requirements.

6.9.1 Alarms status checkAt the end of the configuration of the parameters and before to leave the terminal station verify that no particular alarms are active except the Radio (with related indication) and the alarm related to the Ethernet interface.

Selecting the Alarms menu the following screen opens.

Figure 75 Alarms menu

.

.


87

Commission Equipment configuration (station B)

7 Equipment configuration (station B)Repeat all the steps done for station A in section 6.

.


CommissionAntenna alignment

8 Antenna alignmentBefore starting with the alignment phase, verify the ATPC and the Adaptive Modula-tion in both terminal stations are disabled.

t After the antenna alignment reconfigure the ATPC and the Adaptive Modulation as the project requirements.

Verify also that the Transmission power is configured with the maximum output power.

The Nominal setting values depend on the frequency range. Apply this setting in both stations.

By properly using the safety device and observing the security rules, climb near the FlexiPacket MultiRadio and connect the Multimeter on the main FlexiPacket MultiRadio to the BNC connector.

t It is not compulsory but for antenna pointing it is suggested to use an analog multimeter.

The multimeter must be connected in DC voltage measure.

Start with the antenna adjustment following the indication reported in the installation manual of the antenna supplier.

t Take care that the antennas alignment procedure is not a single station activities, but require a synchronizing tasks between Installation Team on both terminal stations.The alignment operations must be possible only after that all above system configuration and controlling are done also on the remote terminal station. For the mechanical antennas adjustment points, refer to the installation documentation supplied by the antennas sup-plier.

A general alignment procedure is available on request.

After the alignment verify on both terminal station and for all RF channels, that the Received power level agrees with the project specification. (See the RSL value on the Status Bar of the Web Interface).

t The update and refresh time of RSL value on Status Bar are slow, don't use only this Item for the antennas adjustment phase, but it is suggested to use the multimeter on BNC ODU port and refer to the Maximal Voltage value received. Afterwards read the RSL value.

t For RSL, consider a Prx read value tolerance of about ±3 dB.

.

.


89

Commission Antenna alignment

Figure 76 Example BNC Connection on FlexiPacket MultiRadio

The alignment steps and antennas pointing mode depend on the system type and project specifications.

See the examples below.

t In 1+1 configuration it is reccommended to force the active channel on the ODU with the Main role in both Sites and get the relevant RSL reference values (only for antenna adjustment operations) from the Main ODUs. This operation must be done because typ-ically the 1+1 hot standby system uses an unbalanced coupler and RSL on the protec-tion ODU should be lower than the main ODU.

After the antennas adjustment operation to be reconfigure all in automatically mode.

Figure 77 Standard antenna pointing for 1 antenna system

.


CommissionAntenna alignment

Figure 78 Antennas aim for 2 antenna system in Hot Stand By configuration

Figure 79 Antennas aim for 2 antenna system in Frequency Diversity configuration

.

.


91

Commission System commissioning and testing

9 System commissioning and testing

9.1 Link connectivity check (using the remote loopback)

Figure 80 Link connectivity test

t In case of 1+1 configuration no loopback is available.

To check the link connectivity ping the remote station.

Steps

1 Connect the LCT to Station A, as shown in Figure 80.

t The complete sequence to create a loopback is shown in para. 6.6 on page 76.

.


CommissionSystem commissioning and testing

2 Enter Station B: Create the following loopback:

• Interface: GbE Port • Test Type: Link Test Remote Payload (RL3) • Time Out: more than 60 sec.

t The complete sequence to create a loopback is shown in para. 6.6 on page 76.

3 Enter Station A: Create the following loopback:

• Interface: Micro Port • Test Type: Link Test Starting Point (LsRL3) • Time Out: 60 sec.

4 Enter Station B: Activate the loop

5 Enter Station A: Activate the loop

6 During the loop activation time the NE is not reachable.

7 When the time is over click on pushbutton View Result. File TestLoopResult.xml opens.

8 If during the loopback no error occurred, the link works properly: In Bad Octets counter must be zero, In Octets counter must be equal to the Out Octets counter and both must be in the In Good Octets counter.

.

.


93

Commission System commissioning and testing

9.2 Interferences evaluation checkAfter the frequency setting and power setting, before starting with the Alignment phase or remote station configuration phase (considering the remote station in Power OFF condition), check the Prx value to evaluate the presence of any interfering signal from other MW Links.

The operator can measure the value of the power received by the FlexiPacket MultiRa-dio installed in the system by means of the Measurements > RF & Other menu, where the measurement of the reception power is displayed.

Check that all the Rx power values are less than -94 dBm (or in any case with the appro-priate fade margin written in the RF Network Plan).

Figure 81 Measurements menu

If the link is already operational (but not in service), it is possible to set the Remote Tx amplifier to OFF (squelching activation) for a settable timing (the time necessary to read a local Rx Power, about 60 second). This command is also suitable, if any operator is present in the remote station.

By using the WebLCT enter the remote NE and activate the Timed Tx Squelch as shown in the next figure.

Insert an appropriate Squelch Time (example 60 seconds) and activate the command.

On the local station check the Prx value.

.


CommissionSystem commissioning and testing

Steps

Figure 82 Remote squelch command

Date post:	19-Dec-2015
Category:	Documents
Upload:	ismailttl
View:	67 times
Download:	17 times

008. FPMR Commissioning.pdf

Documents