The document provides instructions for commissioning a network element including: 1. Configuring the board manager, radio parameters like frequency and power, and bridge mode. 2. Creating VLANs and assigning ports as members to forward traffic for different VLAN IDs. 3. Configuring the management port and IP address for network management and SNMP. 4. Adding the IP of remote network elements to manage them remotely.

1. Commissioning

2. NMS Group & User creation

9. 1. BOARD Manager
• Card Provisioning
• Core Protection [Equipment > Core Protection]
2. Radio Configuration :
• Radio Configurator [Equipment > Radio Configurator]
• Radio Aggregation [Equipment > Radio Aggregation]
• Bandwidth & Modulation/Link ID [Equipment >BW & Mod. / Link ID]
• Duplex spacing [Radio > Radio Branch > ODU Settings]
• Tx Frequency [Radio > Radio Branch > ODU settings]
• Tx Power control [Radio > Radio Branch > ODU Powers].
3. Bridge Mode Config [Baseband > Ethernet > Bridge Mode Conf.]
4. Management VLAN [Baseband > Ethernet > VLAN > Static VLANs]
5. MNGT Port configuration [Baseband > DCN > MNGT Port Configuration]
6. Agent IP [Main > Equipment properties]
7. Routing Table [Baseband> DCN > Routing Table]
8. Remote element List
9. SW/HW Restart equipment [Main > Equipment properties]
Line up

10. Board Manager
2
3
1
4
5
Provisioning by press double click on
the slot. Others options are present:
-Card Reset
-Card Power Off
-Card Unprovisioned
-Hw Inventory card
-Sw Inventory card
Another way you can also provisioned the card by clicking on each card and provision it.

11. Radio Configurator for 4+4XPIC with SD
2
3
1
4 5
Select ODU 3A,3B,7A &7B
6
Select link type 1+1XPIC HS
a – Create New Link [press Next >]
b – Select config. ( 1+0, 1+1 HS, 1+1 FD, 2+0 XPIC, 1+1XPIC HS, 1+1XPIC FD) for available radio
[press Next >]
c – Bandwidth and Modulation [press Next >]
d – Duplex (MHz) [press Next >]
e – Frequency (MHz) [press Done]
For 4+4XPIC with Space
diversity link:
In our case select “Create New
Link” with link type “1+1XPIC
HS” in link 1 select radio 3A,3B,
7A &7B radio and click Done.
Then again select “Create New
Link” with link type “1+1XPIC
HS” in link 2 select 4A,4B, 8A
&8B radio and click Done.

12. Set Channel spacing and
modulation reference as from
planning data and click next

13. Note 1+1XPIC HS mean actually 2+2XPIC with
HSB for our project.
So again create a new link as we had only
created 2+2XPIC HS link only and our
requirement is of 4+4XPIC HS and repeat the
same procedure.

14. Select ODU 4A,4B,8A & 8B

15. Set Channel spacing and
modulation reference as from
planning data and click next.
Select the duplex for all ODU
or/and click Done

16. Step 1, 3, 5, 7
2
4
6
8
9
Select drag & drop
Radio Link AGgregation
Go in Equipment>Radio Aggregation Scheme
For step 2, 4, 6 & 8
select RIM radio port and
drag it to core “10 G aggregator 1”

17. Radio Configurator for 4+0XPIC
2
3
1
4 5
Select link type 2+0 XPIC
a – Create New Link [press Next >]
b – Select config. ( 1+0, 1+1 HS, 1+1 FD, 2+0 XPIC, 1+1XPIC HS, 1+1XPIC FD) for available radio
[press Next >]
c – Bandwidth and Modulation [press Next >]
d – Duplex (MHz) [press Next >]
e – Frequency (MHz) [press Done]
Select ODU 3A & 3B
6

18. In case of 8+0 XPIC config same steps to be followed creating Link 2 & Link 3 & Link 4
In case of 4+0 XPIC config same steps to be followed creating Link 2

20. Set Channel spacing and
modulation reference as from
planning data and click next.
Select the duplex for all ODU
or/and click Done
In case of 8+0 XPIC config same steps to be followed creating Link 3 & Link 4

21. Step 1, 3, 5, 7
2
4
6
8
9
Select drag & drop
Radio Link AGgregation
Go in Equipment>Radio Aggregation Scheme

22. Bandwidth & Modulation / Link ID
Radio capacity:
Global Capacity –
STM-1 Bulk –
Permanent TDM =
------------------------
Ethernet Capacity
Permanent TDM Traffic are E1 present always in all ACM profiles.
Range allowed
change one
configuration
per time.
Change ACM switching threshold
During antenna aiming ACM , ATPC = DISABLE
Native STM1
Exclude ODU in RLAG when the
modulation is = lower profile +1
In our case Select
Bandwidth 28 MHz
Reference Modulation 1024QAM
ACM engine: Enabled
Lower Profile: 128 QAM
Upper Profile: 1024QAM

23. Tx Power Ramp mode
dBm
4 16S 16 32 64 128
+23
+22
+21
+20
+19
+18
+17 Tx power constant for each
modulation
Ramp to Ref Modulation (Tx
power max allowed for each
modulations)
AGS20L 18GHz
Ramp to Tx Power limit (Max
Tx power fixed by Operator)
Ramp to Tx Power limit
256 512 10242048
56MHz@2048AM Ptx=max
56MHz@4QAM Ptx=max
56MHz@4QAM Ptx=+26dBm
ACM =Enabled
Lower Profile = 4-S QAM
Upper Profile = 2048 QAM
QAM
TX power
4S

24. Tx Power Ramp to Ref. Modulation
Modulation
TX power
56MHz@32QAM Ptx=MAX
NO
Reference Modulation
dBm
4 16S 16 32 64 128
+23
+22
+21
+20
+19
+18
+17
256 512 10242048
QAM
4S

25. Local Link ID
• It’s a radio trace identifier (sent/expected) to avoid unwanted traffic when
LLI Local ≠ LLI Remote
• 0 = LLI function Disabled
D
Example (2 Radio Link different traffic in the same direction and close to each other)
Radio A1
Radio B1
Radio A2
Radio B2
PRX A2
PRX B2
In case of
Failure
A1
A1
LLI=10
LLI=20
If LLI.B2≠LLI.A1,
A1 traffic doesn’t
pass on B2

26. Radio Branch: Frequencies
High Low
FTx1A=18765.0MHz FTx1A=17755.0MHz
FRx1A=17755.0MHz FRx1A=18765.0MHz
Remote
Local
4
8 second to confirm
17700 MHz 19700 MHz
18200 MHz 18700 MHz 19200 MHz
ODU 1L
ODU 2L
ODU 3L
1 SubBand
2 SubBand
3 SubBand
ODU 1H
ODU 2H
ODU 3H
1 3
2
First fix the Tx Frequency channel in
Remote ODU and after in Local ODU

27. Radio Branch: Powers
Manual: TX Power Fixed;
Automatic: ATPC enabled (indipendent
of modulation)
ATPC allows to increase and reduce Ptx
automatically when fading occurs.
ATPC vs constant Ptx:
- Less power consumption,
- higher MTBF,
- reduced interference on other links
In general the threshold Low ATPC = threshold Upshift of
upper modulation; in this way ATPC work before the
downshift.
Zone ACM ATPC reduces Ptx
ATPC let Ptx unchanged
ATPC increases up to the maximum
RTPC

28. Traffic Configuration
Transparent mode example

29. Change the bridge mode to Provider Edge Bridge

30. Enable the admin status of the port which will be going to be used.
Kindly refer Site configuration sheet for the same

32. Change the bridge port type to Customer Network for the traffic port only.
Let the bridge port type for RLAG be Provider Network only
And also change the MTU size for RLAG & traffic port to 9600

34. Add VLAN
First change the service type to EVC instead of VLAN
Then give the VLAN ID:
Select the membet port as RLAG and all traffic port which need to used for this EVC Vlan ID pipe
Select the untagged port only of all traffic port used for this EVC Vlan ID pipe. Do not select RLAG in this.
Give the VLAN name
Then apply

35. Example

37. 7
In port setting for traffic port
enable the Ingress filtering
enter the PVID for traffic port only
with the VLAN id as defined in static vlan
table for traffic.
For MNGT port just give priority to 7 for MNGT port

39. For traffic port change the Priority type to Copy

41. Bridge Mode Configuration
Traffic affective and automatic software restart
Command Purpose
SM-OS# c t ; bridge-mode customer #Enable Customer Bridge (802.1q) [untag and C-VLAN frames]
SM-OS# c t ; bridge-mode provider-core #Enable Provider Bridge (802.1ad) [S-VLAN frame only]
SM-OS# c t ; bridge-mode provider-edge #Enable Provider Edge Bridge [untag, C-VLAN and S-VLAN frames]
For non transparent mode select
Bridge mode “Customer Bridge”

42. Enable the admin state of traffic port and give MTU size 9600

43. VLAN: Static VLANs
• the VLAN packet is forwarded in each Member
Ports keeping the original VLAN
• the VLAN packet is forwarded in each Untagged
Ports removing the original VLAN
0x8100, VLAN tagged frame (IEEE 802.1q )
0x88A8, Provider Bridging (IEEE 802.1ad)
declare which interfaces belong at
the VLAN (internal forwarding).
declare which interfaces member
remove the VLAN in output of the
switch.
Single VLAN
Single VLAN
In our case for traffic vlan id
we to add each vlan id
in the static vlan table with
member ports as RLAG and
the traffic port where the traffic
need to be forwarded.
Do not select any port in
untagged port column.
In our case for NMS vlan id
we to add each vlan id
in the static vlan table with
member ports as RLAG and
the NMS port where the traffic
need to be forwarded along
with Gi1/1 MNGT port
In untagged port column select
only Gi1/1 MNGT port.

44. 7
In port setting just give default user
priority to 7 for MNGT port

45. MNGT Port Configuration
2
3
4
1
Fixed 100Mbit
Full Duplex
MNGT
Layer 2
Example5
configure terminal
vlan 1
ports gi 1/1 untagged gi 1/1 name MNGT
ports add gi 0/6 ; exit
#MNGT settings
interface gi 1/1; no negotiation; speed 100; negotiation
switchport priority default 7 ; no shutdown ; exit
#ODU A settings
interface gi 3/1; no negotiation; speed 2500; no shutdown ; exit
#Set new Interface VLAN 1
default ip vlan id 1
#Set new Ip address/SubnetMask
default ip address 192.168.79.30 subnet-mask 255.255.255.0
#Set default gateway
default gateway route 192.168.79.1 ; end
set hitless-restart enable; sleep 5
reload
5
Using WebLCT...
... or using CLI
Restart to take effect
Layer 3
Management Ctag allowed on pPNP
port in PEB L2 emulated Out of
Band using N33030 v01.01.01
Core card (Slot 1)

46. Agent IP
Web LCT: Main Menu – Equipment Properties
Equipment ID: name view of radio.
Put Near end - Far site id.
Restart without cut the traffic
In case of static routing the Agent
IP = IP Ethernet (MNGT port)
CPU
Network Element
SWITCH
(VLAN)
Interface VLAN 1
PPP ODU A (OOB L3)
Agent IP address
LAN (MNGT)
ODU A (IB/OOB L2)
Agent IP is used to identify
the Network Element and
Set/Get SNMP commands
or Traps alarms.

47. Remote element List
172.18.71.43 172.18.71.46
Create Station and Insert the
Network Element using the IP
AGENT
Local
Managed by SCT
Remote
Remote Link
3
5
2
6
7
8
9
4
In order to know and manager the remote Network Element, local
equipment is declared “managed by SCT”, remote one is declared
“remote link”. Opposite configuration on remote side.
1