Horizon Quantum, R1.3.7, Volume 2, Advanced Configuration Features, Version 1.7 PDF

Horizon QuantumTM
Release 1.3.7
Volume 2
Advanced Configuration Features
Version 1.7
Document Number: 83-000075-01-01-07
NOTICE
This document contains DragonWave proprietary information. Use,
disclosure, copying or distribution of any part of the information contained
herein, beyond that for which it was originally furnished, requires the written
permission of DragonWave Inc.
The information in this document is subject to change without notice and

relates only the product defined in the introduction of this document.
DragonWave intends that information contained herein is, to the best of its
knowledge, correct and accurate. However, any/all liabilities associated
with the use or accuracy of the information contained herein must be
defined in a separate agreement between DragonWave and the
customer/user.
Copyright (c) DragonWave Inc. 2014. All rights reserved.

Table of Contents
1.0 USER MANUAL STRUCTURE .......................................................................................... 1
1.1 CHANGE HISTORY .................................................................................................... 1
1.2 WHAT’S NEW IN THIS RELEASE? ............................................................................... 1
2.0 ADVANCED CONFIGURATION FEATURES .................................................................... 3
3.0 UPGRADE/DOWNGRADE FEATURE GROUP ................................................................ 5
4.0 ON-BOARD NETWORK SWITCH ..................................................................................... 9
4.1 SAVING SWITCH PARAMETERS ................................................................................ 10
4.2 ETHERNET PORT CONFIGURATION .......................................................................... 10
4.3 PORT STATUS ........................................................................................................ 12
4.4 PORT TRAFFIC STATISTICS ...................................................................................... 13
4.5 ISOLATED PORT GROUP (IPG) ................................................................................ 14
4.6 LINK AGGREGATION GROUP (LAG) ......................................................................... 17
4.7 LAYER 2 NETWORK SWITCH (L2SW) ........................................................................ 19
4.8 MAC ADDRESS LEARNING ...................................................................................... 19
5.0 SYNCHRONOUS ETHERNET (SYNCE) ......................................................................... 23
5.1 MASTER/SLAVE ...................................................................................................... 23
5.2 WANDER FILTER..................................................................................................... 23
5.3 CONFIGURING SYNCE ............................................................................................ 24
6.0 NETWORK MANAGEMENT INTERFACES .................................................................... 29
6.1 IN-BAND MANAGEMENT ........................................................................................... 29
6.2 OUT-OF-BAND MANAGEMENT .................................................................................. 31
7.0 VLAN CONFIGURATION ................................................................................................. 33
7.1 ECFM ................................................................................................................... 37
7.2 RAPID LINK SHUTDOWN (RLS) ................................................................................ 37
8.0 BANDWIDTH MANAGEMENT ......................................................................................... 39
8.1 MAXIMUM THROUGHPUT SPEED .............................................................................. 39
8.2 ASYMMETRIC THROUGHPUT SPEED ......................................................................... 42
8.3 UPGRADING SYSTEM LICENSE SPEED ..................................................................... 44
8.4 DOWNGRADING SYSTEM LICENSE SPEED ................................................................ 46
8.5 THROUGHPUT (BANDWIDTH) LOGGING .................................................................... 48
9.0 CAPACITY EXPANSION FEATURES ............................................................................. 53
9.1 PARTNER NODES COMMUNICATION CHANNEL .......................................................... 53
9.2 BANDWIDTH ACCELERATION ................................................................................... 53
9.3 BANDWIDTH DOUBLING ........................................................................................... 59
9.3.1 PRIMARY AND SECONDARY TRAFFIC STATISTICS ............................................... 63
9.3.2 CONFIGURATION REQUIREMENTS ..................................................................... 64
9.3.2.1. WORKING WITH AUTHENTICATION ................................................................................64
9.3.2.2. WORKING WITH HAAM...............................................................................................65
9.3.3 CONFIGURING BANDWIDTH DOUBLING .............................................................. 65
9.4 CROSS POLARIZATION INTERFERENCE CANCELLATION (XPIC) ................................. 69
9.4.1 SINGLE CHANNEL XPIC ................................................................................... 69
9.4.2 MULTI-CHANNEL XPIC ..................................................................................... 72
9.4.2.1. USING MULTI-CHANNEL XPIC WITH BANDWIDTH DOUBLING ...........................................73
9.4.2.2. USING MULTI-CHANNEL XPIC WITHOUT BANDWIDTH DOUBLING .....................................73
10.0 QUALITY OF SERVICE (QOS) ........................................................................................ 80
DragonWave Inc.
iv
10.1 CLASS OF SERVICE TYPES ...................................................................................... 80

10.2 CLASS OF SERVICE LEVELS .................................................................................... 80
10.3 QUALITY OF SERVICE (QOS) QUEUES ..................................................................... 80
10.4 OPERATION WITH QOS DISABLED............................................................................ 80
10.5 OPERATION WITH QOS ENABLED ............................................................................ 81
10.5.1 SLOW BRIDGE PROTOCOL TRAFFIC .................................................................. 81
10.5.2 COMMITTED INFORMATION RATE (CIR) ............................................................. 81
10.5.3 COMMITTED BURST SIZE (CBS) ....................................................................... 82
10.5.4 CUT-THROUGH ................................................................................................ 82
10.6 QOS SCHEDULER POLICIES .................................................................................... 83
10.6.1 PRIORITY QUEUING .......................................................................................... 83
10.6.2 WEIGHTED FAIR QUEUING (WFQ) .................................................................... 86
11.0 ADAPTIVE TRANSMIT POWER CONTROL (ATPC) ..................................................... 97
11.1 COORDINATED POWER ........................................................................................... 97
12.0 OVER-THE-AIR SYSTEM AUTHENTICATION ............................................................. 101
12.1 NO AUTHENTICATION ............................................................................................ 101
12.2 UNIQUE AUTHENTICATION ..................................................................................... 101
12.3 GROUP AUTHENTICATION ..................................................................................... 101
12.4 AUTHENTICATION POLLING.................................................................................... 102
12.5 AUTHENTICATION FAILURE ACTION ........................................................................ 102
12.6 CONFIGURE AUTHENTICATION ............................................................................... 102
13.0 USER AUTHENTICATION ............................................................................................. 107
13.1 INTERNAL AUTHENTICATION .................................................................................. 107
13.2 RADIUS SERVER USER AUTHENTICATION ............................................................ 107
13.2.1 CONFIGURING RADIUS SERVER USER AUTHENTICATION ................................ 108
13.2.2 CONFIGURING THE RADIUS SERVER ............................................................. 111
13.3 TACACS+ AUTHENTICATION ................................................................................ 112
13.3.1 CONFIGURING TACACS+ SERVER USER AUTHENTICATION ............................. 112
14.0 DATA ENCRYPTION...................................................................................................... 115
14.1 ENCRYPTION KEY GENERATION ............................................................................ 115
14.1.1 MANUAL KEY ENTRY ...................................................................................... 115
14.1.2 AUTOMATIC KEY GENERATION ........................................................................ 115
15.0 THRESHOLD ALARMS ................................................................................................. 121
16.0 RAPID LINK SHUTDOWN (RLS) ................................................................................... 125
16.1 DETERMINATION OF ERROR RATES ON HORIZON QUANTUM SYSTEMS .................... 125
16.2 RLS CONFIGURATION ........................................................................................... 126
16.2.1 BASIC MODE.................................................................................................. 126
16.2.2 ADVANCED MODE .......................................................................................... 126
16.3 SETTINGS FOR BASIC MODE ................................................................................. 127
16.3.1 RLS SIGNAL DEGRADE SETTINGS .................................................................. 127
16.3.2 RLS LINK MONITOR PARAMETERS .................................................................. 127
16.4 SETTINGS FOR ADVANCED MODE .......................................................................... 128
16.4.1 RLS SIGNAL FAULT SETTINGS ........................................................................ 128
16.4.2 RECOVERY FROM A HARD FAILURE ................................................................. 128
16.5 RLS LINK CONTROL SETTINGS ............................................................................. 129
16.6 RLS WORKING WITH HITLESS AUTOMATIC ADAPTIVE MODULATION (HAAM) ........... 129
17.0 CONFIGURING THE TIME SOURCE (SNTP) ............................................................... 137
18.0 HITLESS AUTOMATIC ADAPTIVE MODULATION (HAAM) ....................................... 141
Table of Contents
v
19.0 RADIO REDUNDANCY .................................................................................................. 149

19.1 PRIMARY AND SECONDARY PATH .......................................................................... 149
19.2 HOW AND WHEN PROTECTION SWITCHING OCCURS .............................................. 149
19.3 RECOVERY AFTER PROTECTION SWITCHING.......................................................... 150
19.4 FORCING THE DATA PATH TO A PARTICULAR LINK .................................................. 150
19.5 CHECKING THE STATUS OF A REDUNDANT SYSTEM ................................................ 150
19.6 USING THE RDRM ............................................................................................... 151
19.7 TWO ANTENNAS AND TWO RADIOS ........................................................................ 152
19.8 CONFIGURING REDUNDANCY ................................................................................ 152
19.9 REMOVING A FAULTY WIRELESS PORT “MARKING” ................................................. 155
20.0 SYSTEM REDUNDANCY ............................................................................................... 157
20.1 HOT STAND-BY (HSB) .......................................................................................... 157
20.2 PRIMARY AND SECONDARY QUANTUM ................................................................... 157
20.3 HOW AND WHEN PROTECTION SWITCHING OCCURS .............................................. 157
20.4 HSB SWITCHING ACTION ...................................................................................... 158
20.5 RECOVERY AFTER PROTECTION SWITCHING.......................................................... 158
20.6 FORCING THE DATA PATH TO A PARTICULAR LINK .................................................. 158
20.7 REDUNDANCY CLI COMMANDS ............................................................................. 159
20.7.1 REDUNDANCY MODE: ..................................................................................... 159
20.7.2 REDUNDANCY SWITCH MODE ......................................................................... 159
20.7.3 REDUNDANCY STATE SWITCH ......................................................................... 159
20.7.4 REDUNDANCY STANDBY ENET STATE ............................................................... 159
20.7.5 REDUNDANCY LINK MONITOR PARAMETERS ..................................................... 160
20.7.6 REDUNDANCY LINK SWITCH PARAMETERS........................................................ 160
20.7.7 REDUNDANCY ETHERNET PORT CONFIG .......................................................... 160
20.7.8 REDUNDANCY STATUS ................................................................................... 160
20.8 REDUNDANCY SWITCHING AND MANAGEMENT OPTIONS ......................................... 161
20.8.1 HSB CONFIGURATION WITH IN-BAND MANAGEMENT ....................................... 161
20.8.2 HSB CONFIGURATION WITH OUT-OF-BAND MANAGEMENT – CASE 1 ................ 164
20.8.3 HSB CONFIGURATION WITH OUT-OF-BAND MANAGEMENT – CASE 2 ................ 167
20.8.4 HSB CONFIGURATION WITH MORE THAN ONE HSB PORT .............................. 171
21.0 PEER LINK COMPATIBILITY MODE (PLCM) .............................................................. 177
21.1 QUANTUM AND DUO INTEROPERABILITY ................................................................. 177
21.1.1 CONFIGURING PLCM – DUO INTEROPERABILITY - USING CLI ........................... 178
21.2 DUO LIKE CONFIGURATION ................................................................................... 180
21.2.1 CONFIGURING PLCM – DUO LIKE CONFIGURATION - USING CLI ....................... 180
21.3 CONFIGURING PLCM USING SNMP ...................................................................... 182
22.0 SYSTEM MANAGEMENT .............................................................................................. 183
22.1 TELNET ACCESS................................................................................................... 183
22.1.1 SECURE SHELL ACCESS SECURITY ................................................................. 184
22.1.2 CONFIGURING SECURE SHELL (SSH) ............................................................. 184
22.2 ALARMS LIST........................................................................................................ 186
22.3 WEB INTERFACE ................................................................................................... 187
22.3.1 FEATURES ..................................................................................................... 187
22.3.2 CONNECTING TO THE WEB INTERFACE ............................................................ 187
22.3.3 EXITING THE APPLICATION .............................................................................. 188
22.3.4 LOGIN ........................................................................................................... 188
22.3.5 HOME SCREEN .............................................................................................. 189
22.3.6 WEB PAGE TREE DIAGRAM ............................................................................ 191
22.3.7 SSL WEB SERVER ......................................................................................... 192
22.3.7.1. WHAT IS SSL? ......................................................................................................192
22.3.7.2. GENERATING A CERTIFICATE ON THE HORIZON QUANTUM ..........................................193
22.3.7.3. INSTALLING CERTIFICATES ON YOUR WEB BROWSER ................................................195
DragonWave Inc.
vi
22.3.7.4. ENABLING SSL PER USER GROUP...........................................................................197

22.4 EVENT AND PERFORMANCE LOGGING .................................................................... 198
22.4.1 EVENTS LOG ................................................................................................. 198
22.4.2 PERFORMANCE LOG ...................................................................................... 201
22.4.3 SYSLOG FEATURE .......................................................................................... 202
22.5 RADIO AND NETWORK LOOPBACK ......................................................................... 204
22.6 INTERMEDIATE FREQUENCY (IF) LOOPBACK........................................................... 208
23.0 NETWORK MANAGEMENT .......................................................................................... 211
23.1 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP) ........................................... 211
23.1.1 SUPPORTED SNMP VERSIONS ....................................................................... 211
23.1.2 ENTERPRISE MANAGEMENT INFORMATION BASE (MIB) .................................... 218
23.1.3 SNMP TRAPS ............................................................................................... 219
APPENDIX A - DETAILED CLI COMMAND SYNTAX ............................................................ 225
APPENDIX B - SITE SURVEY INFORMATION ...................................................................... 249
APPENDIX C - 802.1P PRIORITY TAGGING OVERVIEW ..................................................... 251
Table of Contents
vii
List of Figures
Figure 4-1 Top Level Network interfaces .................................................................................................. 9
Figure 4-2 Isolated Port Group ................................................................................................................ 14
Figure 4-3 Third Party LAG ...................................................................................................................... 17
Figure 4-4 Third Party LAG and RLS....................................................................................................... 18
Figure 4-5 MAC address learning must be disabled ............................................................................. 19
Figure 6-1 Out-of-band System Management ........................................................................................ 31
Figure 9-1 Bandwidth Doubling Physical Connections . ...................................................................... 59
Figure 9-2 Bandwidth Doubling Management Option 1 ........................................................................ 61
Figure 9-5 Single Channel XPIC .............................................................................................................. 70
Figure 9-6 Multi-Channel XPIC. ................................................................................................................ 72
Figure 9-7 Data Feed Using LAG with OOB Management Option 1.. ................................................... 73
Figure 9-8 Data Feed Using LAG with OOB Management Option 2. .................................................... 74
Figure 10-1 CoS Queues can be allocated a CIR and a Committed Burst Size (CBS). ...................... 85
Figure 10-2 Weighted Fair Queuing Concept. ........................................................................................ 86
Figure 19-1 RDRM and System Redundancy ....................................................................................... 151
Figure 19-2 Connecting RDRM Mounted Radios to Horizon Quantum IDU ...................................... 151
Figure 19-3 Two Antennas, Two Radios and System Redundancy ................................................... 152
Figure 20-1 Over-the-air Path Failure Causes HSB Switch................................................................. 162
Figure 20-2 Node failure causes HSB switch ....................................................................................... 163
Figure 20-3 Node failure causes HSB switch ....................................................................................... 164
Figure 20-4 Case 1 - Over-air failure causes HSB switch (OOB Management) ................................ 165
Figure 20-5 Case 1 - Node failure causes HSB switch (OOB Management) ..................................... 166
Figure 20-9 Case 2 – Over-air failure causes HSB switch (OOB Management)................................ 170
Figure 20-10 HSB Configuration With More Than One HSB IPG Group ............................................ 171
Figure 22-1 Web Interface - Login Screen ............................................................................................ 189
Figure 22-2 Web Interface - Home Screen ............................................................................................ 189
Figure 22-3 Web Interface – Tree Diagram ........................................................................................... 191
DragonWave Inc.
viii
List of Tables
Table 4-1 Quantum ODU modem ports and equivalent IDU modem ports ........................................... 9
Table 8-1 System Mode and Modulation Scheme .................................................................................. 39
Table 17-1 Time Sources ........................................................................................................................ 137
Table 18-1 Modulation Up/Downshift SNR Thresholds ....................................................................... 141
Table 22-1 Simultaneous logins for Web interface ............................................................................. 188
Table 22-2 Performance Log Durations ................................................................................................ 202
1.0 User Manual Structure
This user manual is divided into three volumes:
• Volume 1 – Contains an overview of the product, basic configuration, installation and
alignment procedures that are sufficient to set up a link and have it passing traffic
• Volume 2 (this volume) – includes step-by-step configuration details for the advanced
configuration features and the CLI commands that are described briefly in Volume 1
• Volume 3 – contains a complete list of the frequency tables associated with the radio
bands supported by the Horizon Quantum
• Volume 4 - contains configuration details relating to industry standard networking
features.
1.1 Change History
Version Update Point Date

1.7 New. September, 2014
1.2 What’s New in This Release?

• SFTP is supported;
• SSH session number is extended from 1 to 3.
DragonWave Inc.
2
This page left blank intentionally

2.0 Advanced Configuration Features
Volume 1 describes the configuration of the basic features that allow the Horizon Quantum system to
provide a wireless Ethernet link. Volume 2 (this volume) describes a number of advanced configuration
features that provide enhanced operational capabilities. Each advanced feature is described in detail in
the following sections.
Unless otherwise indicated, all described features pertain to both the Horizon Quantum IDU modem and
the Horizon Quantum ODU modem. Throughout this volume the words “Horizon Quantum” refer to both
the IDU and ODU versions of the Horizon Quantum modems.
DragonWave Inc.
4
This page is left blank intentionally

3.0 Upgrade/Downgrade Feature Group
Some of the features described in this manual are only available if a license for the feature(s) is obtained
from DragonWave Inc. These are as follows:
1. XPIC - Cross Polarization Interference Cancellation

2. BAC – Bandwidth Acceleration
3. RLS, ECFM(802.1ag/Y.1731), LLDP – Rapid Link Shutdown and ECFM support with
LLDP
4. HAAM – Hitless Automatic Adaptive Modulation
5. DualWirelessPorts – Ability to configure dual wireless ports
6. l2switchFeature – Layer 2 network switch with LLDP
7. Data Encryption
To enable/disable any of these features there are CLI commands that provide information about your
system that DragonWave Inc requires before it can provide you with the necessary license upgrade key,
or a refund for a downgraded feature.
The following procedure shows what features may be already enabled and how features are enabled or
disabled.
Procedure 3-1
Ethernet Port Configuration
Required Action Steps
login Log in using the Super user, or a NOC user, account.
List the licensed features This command lists the licensed features available for the Horizon Quantum
and also indicates if they are licensed for this system.
Sequence:
get licensed feature groups press Enter
The system responds:
Index Licensed Feature Group Is Licensed

1 XPIC No
2 BAC Yes
3 RLS,ECFM(802.1ag/Y.1731), LLDP Yes
4 HAAM Yes
5 DualWirelessPorts Yes
6 l2switchFeature, LLDP No
7 Data Encryption No
DragonWave Inc.
6
Get the information that This command pulls key information from the system that is required by
DragonWave Inc. requires in DragonWave Inc. before an upgrade can be obtained.
order to provide an upgrade key. Sequence:
get feature group upgrade information <group index 1 to 6>

Example:
get feature group upgrade information 2 press Enter
Feature group 'BAC' upgrade request information:
Count :0
Unit Serial Number :A1316774M090014
MAC Address :00-07-58-02-92-10
Note that this information needs to be sent to DragonWave Inc. before an
upgrade key can be issued. Fees apply to upgrade licenses.
Upgrade a feature Once you have paid for and received the required upgrade key, use
this command to upgrade your system.
Sequence:
upgrade feature group <group index> <license key>
Example:
upgrade feature group 2 61ba1455c138af096b312efe7f321b98
press Enter
This operation will force to save MIB. Continue? Enter Y(Yes) or

N(No):y
Feature group 'BAC' is licensed!
Saving MIB. Please wait for a while...

Mib saved successfully.
Upgrade/Downgrade Feature Group
7
Downgrade a feature Use this command to downgrade, or unlicense, a feature. Note, once
downgraded you will need another license key from DragonWave in order to
re-license a group.
Sequence:
downgrade feature group <group index>
Example:
downgrade feature group 2 press Enter
This operation will force to save MIB. Continue? Enter Y(Yes) or
N(No):y
BAC is turned off!
The feature group is unlicensed!
Feature group 'BAC' downgrade confirmation information:

Count :1
MAC Address :00-07-58-02-92-10
Confirmation Number :c32d57d9c6765f9df34a99f48dee369d
Confirm downgrade information This command will return the downgrade confirmation information, similar to
that provided by the downgrade feature group command.
Sequence:
get feature group downgrade information <group index>
Example:
get feature group downgrade information 2 press Enter
Feature group 'BAC' downgrade confirmation information:
Count :1
MAC Address :00-07-58-02-92-10
Confirmation Number :c32d57d9c6765f9df34a99f48dee369d
DragonWave Inc.
8

4.0 On-board Network Switch
The Horizon Quantum IDU has eight (8) user network interface ports, two supporting fibre (SFP) and the
remaining six supporting 10/100/1000 Base-T copper interfaces. Each of the eight ports is connected to
an on-board, layer 2, network switch and any port can be assigned to any one of four discreet data paths
transmitted across the radio link. Each of the eight user network interfaces (P1 through P8) may be
configured with the following characteristics, using CLI, Web or SNMP:
• Auto-negotiation enable/disable (P3 to P8) * • Port control enable/disable (P1 to P8)
• Link speed (P3 to P8) • Pause control enable/disable (P1 to P8)
• Ethernet frame size (P1 to P8) • Port duplex
* Ports P1 and P2, being fibre media interfaces, are always configured to operate with auto-negotiation.
The operational status of each port may be accessed using CLI, Web or SNMP methods.
Multiple isolated networks may be interconnected using the Isolated Port Group (IPG) feature. IPG may
be used to create multiple (up to five) switching domains within Quantum. IPG also helps to isolate the
network management domain for Quantum.
Figure 4-1 shows the top level network interfaces detail of Horizon Quantum. P1 through P8 represent the
data input ports. DP1 through DP4 represent the four available data paths.
Figure 4-1 Top Level Network interfaces
P1 P1
P2 P2
P3 DP1 DP1 P3
M M
Classifier
Classifier
P4 DP2 Q o o DP2 P4
Q
o d d
P5 o DP3 P5
DP3 S e e S
m m
P6 DP4 DP4 P6
P7 P7
P8 P8
NOTE: The Horizon Quantum ODU modem has up to six (6) user network interface ports, one supporting
fibre (SFP) only, one supporting fibre or 10/100/1000 Base-T copper and the remaining four supporting
10/100/1000 Base-T copper interfaces. The number and types (copper or fibre) of ports available
depends on the ODU modem network connector option purchased. The user must be aware of which
ports are available on the ODU and that all ports mentioned in the configuration examples for the IDU
modem that follow, may not be available for the ODU. See Table 4-1 for port equivalents.
ODU Interface Types Equivalent IDU Modem Port
J1 (can only be fibre) P1
J2 when fibre P2
J2 when single copper P3
J3 when single copper (and J2 is also copper) P4
J3 MIL (quad copper). (Each of the four RJ-45 P3 (white), P4 (blue),
terminated cables is colour coded.) P5 (green), P6 (yellow)
J3 when single copper (and J1 and J2 are fibre) P3
Table 4-1 Quantum ODU modem ports and equivalent IDU modem ports
DragonWave Inc.
10
4.1 Saving Switch Parameters

Note that any system management and switch port configuration parameters are now captured in a
separate management information base - l2swmib. Configuration settings relating to the following
parameters are now saved in the l2swmib and are no longer part of the main mib:
• VLAN • Port characteristics • IPG
• Network Management • Port Priority
To save these settings to flash memory requires the CLI command save l2swmib to be issued once all
changes have been made. This is required regardless as to the status of the DragonWave
l2switchFeature license group. This is in addition to the usual save mib command which is required to
save other system parameters.
4.2 Ethernet Port Configuration

Use the following procedure to display the current configuration of an Ethernet port and to change the
configuration of an Ethernet port:
Procedure 4-1
Ethernet Port Configuration
login Log in using the Super user, or a NOC user, account.
Display the current configuration Display configuration parameters for the Ethernet port.
of an Ethernet port.
Sequence:
get enet config [port number <1-8>] press Enter
Where
port number <1-8> identifies the Ethernet port number. Range is from 1 to 8.
If no port number is entered, the command will display all ports’ current status
information.
Example:
-->get enet config 1

--------------------------------------------------------------
ETHERNET PORT CONFIGURATION
===================================
Enet Port ID p1
Port Name p1
Auto Negotiation on
Duplex Status full
Port Media fiber
Speed 1000
Mdix Status auto
Pause Frame Enable off
Max. Frame Size 1600
Admin State on
On-board Network Switch
11
Change the configuration of an Configures the characteristics of the specified Ethernet port. This is an
Ethernet port interactive command.
Sequence:
set enet config press Enter
Example:
->set enet config
#Press 'Ctrl-X' to exit config process

#Press 'Enter' to retain previous value
Port [1 - 8] (1) ? 8
Port Name (p8):
Auto Negotiation [ on(1) | off(2)] (on):1
Speed Mbps [10 (1) | 100 (2) | 1000(3) | auto(4)] (auto):
Duplex [full (1) | half (2) | auto(3) (full):
Mdix [auto (1) | normal (2) | xover(3) (auto):2
Pause Frame Enable [tx(1) | rx(2) | both(3) | off(4)] (off):1
Maximum Frame Size (1600):9600
Admin State [on(1) | off(2)] (on):
Apply the above settings ? Enter yes(y) or no(n) y

------------------------------------------------------------------
ETHERNET PORT CONFIGURATION
=====================================
Enet Port ID p8
Port Name p8
Auto Negotiation on
Duplex Status full
Port Media copper
Speed auto
Mdix Status normal
Pause Frame Enable tx on
Max. Frame Size 9600
Admin State on
Save the L2 management Saves the L2 switch MIB to RAM. Perform this command to save setting
information base (l2swmib) to changes to non-volatile memory.
flash memory.
Sequence:
save l2swmib press Enter
MIB saved successfully.
DragonWave Inc.
12
4.3 Port Status

The current status of all Ethernet ports can be displayed using the following procedure:
Procedure 4-2
Port Status
login Log in using the Super user, or a NOC, user account.
View the current operational Display current Ethernet status information.

status of an Ethernet port.
Sequence:
get enet status [port number <1-8>] press Enter
Where
port number <1-8> identifies the Ethernet port number.
Range is from 1 to 8.
If no port number is entered, the command will display all ports’ current status
information.
Example:
-->get enet status 3

------------------------------------------------------
ETHERNET PORT STATUS
===============================
Enet Port ID p3
Link Status up
Port Media fiber
Auto Negotiation on
Duplex Status full
Speed 100
Mdix Status normal
Pause Frame off
Max Frame Size 1600
Mac Address 00:07:58:02:91:f3
13
4.4 Port traffic Statistics

See Volume 1, Section 11.1, for details of where in a system the port traffic statistics are measured. The
traffic statistics for any port can be reviewed and cleared using the following procedure:
Procedure 4-3
Port Traffic Statistics
View the traffic statistics of an Get Ethernet port's traffic statistics.

Ethernet port.
Sequence:
get port traffic statistics [ port number | port name ] press Enter
Where
port number identifies the Ethernet port number. Range is from 1 to 8.
port name identifies the Ethernet port name.
Example 1:
->get port traffic statistics 3
===== Port 3 (p3) Traffic Statistics =====
Rx Bytes :144352145
Rx Unicast :84830
Rx Non-Unicast :1790050
Rx Discarded :151180
Rx Error :0
Rx Unknown :0
Tx Bytes :4400992
Tx Unicast :68528
Tx Non-Unicast :11
Tx Discarded :0
Tx Error :0
Tx Q Length :0
Example 2:
->get port traffic statistics p4
===== Port 4 (p4) Traffic Statistics =====
Rx Bytes :0
Rx Unicast :0
Rx Non-Unicast :0
Rx Discarded :0
Rx Error :0
Rx Unknown :0
Tx Bytes :0
Tx Unicast :0
Tx Non-Unicast :0
Tx Discarded :0
Tx Error :0
Tx Q Length :0
DragonWave Inc.
14
Clear the current statistics of an Clear Ethernet port's traffic statistics.

Ethernet port.
Sequence:
set port traffic statistics clear [ all | port number] press Enter
Where
port number identifies the Ethernet port number. Range is from 1 to 8.
4.5 Isolated Port Group (IPG)

Using the IPG allows Quantum to interconnect multiple isolated networks. IPG can be used to create
multiple switching domains within Quantum. IPG also helps in isolating the network management domain
for Quantum.
A maximum of five (5) IPG’s may be configured.
Figure 4-2 Isolated Port Group
IPG5 IPG5
IPG4 IPG4
IPG3 IPG3
LAN-1
LAN-1
P1 P1 LAN-2
LAN-2
P2 P2
P3 DP1 DP1 P3 LAN-3

M M
Classifier
Classifier
LAN-3 P4 DP2 Q o o DP2 P4

Q
o d d
P5 DP3 o DP3 P5
S e e LAN - 4
S
m m
P6 DP4 DP4 P6
LAN - 4
P7 P7
P8 P8 LAN-5
LAN-5
IPG2 IPG1 IPG2

IPG1
In the example shown in Figure 4-2, five IPGs are created by grouping different Ethernet ports (P1 to P8)
and different data paths (DP1 to DP4). The user can assign the ports to different IPGs. Any given port
can be assigned to only one IPG. All unassigned interfaces form an IPG by themselves. This means that
there can be at most six IPGs active at any given instance. In Figure 4-2, ports P6, P7, P8, and DP4 form
IPG1. At the other end of the link the same ports belong to IPG1. Keeping DP4 in these groups ensures
that a direct wireless path is created between the IPG1 at both ends and the traffic of this group is kept
isolated over the wireless link from traffic in the other groups. Since there are four data paths, the user
can connect four different LAN networks through the wireless link.
15
Note:
1. The data belonging to the data paths are subjected to the same classifier and QoS engine.
This means that separate QoS policy and rate limiting can not be applied to traffic in these
paths.
2. The system has only one switching domain. The members of two different IPG’s should
not use the same SA/VLAN traffic stream.
The following procedure explains how to configure IPG’s:
Procedure 4-4
Configuring IPG’s
View the current status of all Display isolated port groups’ status information.
IPG’s.
Sequence:
get ipg status press Enter
Example:
-->get ipg status
Name Status Port List

---- ------- ------------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 enable p8,dp4
ipg5 enable p3
View the current configuration of Display configuration parameters for all isolated port groups.
all IPG’s
Sequence:
get ipg config press Enter
Example:
-->get ipg config

----- ------- ------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 enable p8,dp4
ipg5 enable p3
DragonWave Inc.
16
Enable or disable IPG’s and Enable or disable an isolated port group.

allocate ports to each as
required. Sequence:
set ipg config [group name] [enable|disable] [port list] press Enter
Where
group name identifies the ipg group name. Available ipg groups are ipg1,
ipg2, ipg3, ipg4, and ipg5.
port list identifies a list of Ethernet port name. Port names are separated by
the comma.
Example 1:
->set ipg config ipg4 disable

----- ------- ------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 disable
ipg5 enable p3
Apply the setting immediately, Continue? Enter Y(Yes) or N(No):y
Configuring isolated port group.
Example 2:
-->set ipg config ipg4 enable p2,p8,dp4

----- ------- ------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 enable p2,p8,dp4
ipg5 enable p3

17
flash memory.
Sequence:
4.6 Link Aggregation Group (LAG)

There are cases where the user wants to use the LAG created on a third party switch, which runs its own
LAG protocol. In this case it is suggested that the third party LAG be transported transparently over
Quantum.
Figure 4-3 Third Party LAG
IPG4 IPG4
Management port IPG3 IPG3
Management port
P1 P1
P2 P2
P3 DP1 DP1 P3
M M
Classifier
Classifier
External P4 DP2 Q o o DP2 P4 External

Q
Switch o d d Switch
P5 DP3 o DP3 P5
S e e S
m m
P6 DP4 DP4 P6
P7 P7
P8 P8
LAG created on the

external switch LAG created on the
IPG2 IPG1 IPG2 external switch
IPG1
Figure 4-3 illustrates this technique. The integrity of the external switch LAG is maintained by creating
four IPG’s on both ends of the link and connecting the LAG ports of the external switch to these IPG’s
individually. In this configuration, make sure to disable mac learning on the IPG ports. However, it is
important to note that, the Rapid Link Shutdown (RLS) feature of Quantum, if configured, will not function
correctly if one of the LAG member ports connecting to one end fails, or is shut down, as the shut down
status of this port is not carried over to the other end. Consequently, the corresponding port at the other
end is not shut down. For example, the situation shown in Figure 4-4 is not supported.
DragonWave Inc.
18
Figure 4-4 Third Party LAG and RLS

IPG4 IPG4
Management port IPG3 IPG3
Management port
P1 P1
P2 P2
P3 DP1 DP1 P3
M M
Classifier
Classifier
External P4 DP2 Q o o DP2 P4 External
Q
Switch o d d Switch
P5 DP3 o DP3 P5
S e e S
m m
P6 DP4 DP4 P6
P7 P7
P8 P8
LAG created on the

external switch LAG created on the
IPG2 IPG1 IPG2 external switch
IPG1
In Figure 4-3, the port connecting to IPG1 at one end is disconnected. In the best case scenario the port
connecting to IPG1 on the other side of the link should be shut down. This requires a more advanced
RLS implementation. This is not supported in the current release.
19
4.7 Layer 2 Network Switch (l2sw)

The on-board network switch also has layer 2 network switching capabilities. DragonWave l2sw is an
integrated software feature for the Horizon Quantum that manages the Layer 2 capabilities of the on-
board network switch. DragonWave l2sw provides basic bridging functionality and also offers advanced
features such as link aggregation, GVRP/GMRP, IGMP Snooping and Network Access Control. Note that
this is a DWI licensed feature. See Volume 4, Networking Features, for more details.
4.8 MAC Address Learning

Network bridges utilize the source MAC address of each received Ethernet packet to build a table of
nodes connected to that bridge. This process is termed MAC address learning and is defined in the IEEE
802.1 standard. This scheme helps minimize traffic on the attached LANs.
The on-board switch in Horizon Quantum also supports MAC address learning. This feature is enabled on
all ports by default but can be disabled on a per port basis, when its use is contraindicated by other
configurable features.
For example, when a subtending switch uses a Link Aggregation Group (LAG) over more than one
Ethernet port connection to Quantum and the system is configured to use an Isolated Port Group (IPG) to
pass all traffic to the far end, then MAC address learning must be disabled for the Ethernet ports
concerned.
In Figure 4-5 the subtending switch is using LAG over ports p7 and p8. p7 and dp3 are in one IPG and p8
and dp4 are in another IPG. For all traffic to be transmitted over the wireless link to the far end MAC
address learning must be disabled for ports p7, p8, dp3 and dp4, at both ends of the link.
Similarly, when Quantum is configured in Bandwidth Doubling mode, the corresponding ports must have
MAC address learning disabled.
Figure 4-5 MAC address learning must be disabled

DragonWave Inc.
20
The following procedure explains how you configure MAC address learning.
Procedure 4-5
Configuring MAC Address Learning
View current status of MAC This command returns the current status of the MAC address learning feature:
address learning Sequence:
get mac-learning press Enter
Port Mac-learning
------ -------------
p1 disabled
p2 disabled
p3 disabled
p4 disabled
p5 disabled
p6 disabled
p7 disabled
p8 disabled
dp1 disabled
dp2 disabled
dp3 disabled
dp4 disabled
Change the status of MAC This command enables or disables MAC address learning for specified ports
address learning Sequence:
set mac-learning [enable|disable (port list)]
Where port list is any combination of p1 – p8 and dp1 – dp4
Example:
set mac-learning enable p1,p2,p3,dp1,dp2 press Enter
Port Mac-learning
------ -------------
p1 enabled
p2 enabled
p3 enabled
p4 disabled
p5 disabled
p6 disabled
p7 disabled
p8 disabled
dp1 enabled
dp2 enabled
dp3 disabled
dp4 disabled
21
Save the layer 2 mib to preserve This command saves the layer 2 mib and preserves the changes made to the
changes. layer 2 switch configuration.
Sequence:
L2 Switch Mib saved successfully.
DragonWave Inc.
22

5.0 Synchronous Ethernet (syncE)
Ethernet has rapidly overtaken legacy communication technologies such as TDM, ATM and SONET/SDH
within the carrier infrastructure. Ethernet is a packet based technology, which, originally, was incapable of
carrying technologies requiring the transfer of accurate synchronization and clock distribution such as that
required for the legacy technologies noted above. With the introduction of Synchronous Ethernet (syncE)
features, Ethernet networks are now able to provide the same level of quality and reliability as legacy
technologies for use in carrier class applications.
The DragonWave Horizon Quantum meets or exceeds ITU-T G.8262 Option 2 requirements..
Typical third party applications that can use syncE are:
• Cellular base station synchronization
• Real time video and teleconferencing
• TDM network extension over Ethernet
SyncE allows accurate clock synchronization information to be transmitted over a DragonWave wireless
Ethernet link, allowing the Horizon Quantum to support synchronous applications, end to end and port to
port.
In order to make use of syncE, any synchronous third party product will need to take its timing information
from an Ethernet port. Note that Horizon Quantum does not have a BITS or other direct clock output.
5.1 Master/Slave
In a Gigabit Ethernet connection, one end device always becomes the Ethernet clock master, and the
other becomes the Ethernet clock slave. This happens automatically as part of Ethernet
autonegotiation. On the Quantum, when 1000 Mbps (GigE) ports are selected as syncE member ports,
the clock master/slave status of the Ethernet port concerned is automatically forced to
correspond. Ethernet ports that are defined as syncE primary, or secondary, sources to the Quantum,
are forced to appear as Ethernet clock slaves to the connected Ethernet devices, so that the connected
device sources the clock to the Quantum. Similarly, syncE member ports which are not defined as clock
sources for the Quantum become Ethernet clock masters, so they can send out the clock.
Any connected Ethernet device which autonegotiates master/slave status, will establish an Ethernet link
as usual. However, if the far end Ethernet device also has its clock master/slave status forced to the
same type as the Quantum port, an Ethernet link will not be established. For instance, if two Quantum
Ethernet ports are both syncE members, and not syncE primary or secondary clock sources, then these
ports are both forced to be GigE clock sources, so will not establish an Ethernet link if connected by an
Ethernet cable.
For 100baseT connections, this is not a consideration, because clock information always flows both ways
simultaneously on a 100baseT Ethernet clock link.
5.2 Wander Filter

To cope with potential clock drift, Ethernet systems may use optional additional wander filtering to
maintain clock accuracy. Quantum provides two wander filtering options, one which meets ITU-T G.8262
Option 2, and another which meets ITU-T G.8262 Option 1. Option 1 is based on E1 hierarchy (Europe
and Asia) and Option 2 on T1 hierarchy (predominantly North America). Ethernet systems close to the
edge of the network may not need the additional filtering, but those further into the network may need it to
maintain clock accuracy.
DragonWave Inc.
24
5.3 Configuring SyncE

Procedure 5-1
Configuring syncE
All the commands in the following procedure are immediately invoked. There is no need to perform a
save mib or reset system to make the feature active.
login Log in using the Super user, or an NAC account.
View current status of syncE This command returns the current status of the syncE feature
Sequence:
get synce status press Enter
The system responds (example):
mode : off
clock source : wp1
acquisition status: holdover
forced holdover : off
remaining time in forced holdover: 0 sec
Add ports that are to be used This command allows you to add all the ports that are required to
for syncE to the member handle syncE into the member port group. Note that in order to
group configure the ports that are to be the primary and secondary clock
sources, the ports must first be made part of the member port group.
Note: Ports that are available on the Quantum ODU modem differ
from those available on the Quantum IDU modem. See Table 4-1
for ports that are available on the Quantum ODU modem and the
equivalent IDU ports.
Sequence:
set synce member port
[p3|p4|p5|p6|p7|p8|wp1|wp2|freerun]
Example: set synce member port p3,p4,wp1 press Enter
synce members: p3,p4,wp1,freerun
Note: valid synce member port includes

p3,p4,p5,p6,p7,p8,wp1,wp2; freerun is always a synce
member.
Synchronous Ethernet
25
Select the port that will be the This command allows you to select which port is to be the primary
primary (master) clock source. Note that the port must be configured as GigE (1000
synchronization clock source Mbps) or 100BaseT (100 Mbps), to be a syncE member port. Note,
also, that ports p1 and p2, being SFP ports cannot be used as a clock
source.
Sequence:
set synce primary source
Example: set synce primary source wp1 press Enter

configured mode : off
configured primary clock source : wp1
configured secondary clock source: freerun
synce members : p3,p4,wp1,freerun
configured revertive mode : off, wait time 0 sec
Wander filter option :option2
Select the port that will be the This command allows you to select the port that will provide the
secondary synchronization secondary clock source. It will take over from the primary clock source
clock source if the primary clock source fails. Note that unless the revertive feature
is enabled (set synce revertive on), if, after a switch to the secondary
clock source, the primary clock source recovers, the system will not
automatically switch back from secondary to the primary clock source.
Sequence:
set synce secondary source
Example: set synce secondary source p3 press Enter

The system reponds:
configured mode : off
configured secondary clock source: p3
configured revertive mode : off, wait time 0 sec
Enable or disable the This command allows you to enable or disable the revertive mode. On
revertive mode a primary clock source failure and provided that the syncE mode is
configured for auto, when revertive mode is enabled (on), it allows the
system to automatically revert back from the secondary to the primary
clock source, once the primary clock source has recovered and
remains stable for a selected time in seconds. The time range is from
10 to 300 seconds. The default time is 10 seconds.
Sequence:
set synce revertive [on|off][time] press Enter
The system responds (example 30 seconds time):
Synchronous Ethernet revertive mode: on, wait time 30 sec.
DragonWave Inc.
26
Select the Wander Filter This command allows the user to select either Ethernet Equipment
Option Clock filter Option 1, or Option 2. Option 1 would be used in the E1
TDM hierarchy and Option 2 in the T1 TDM hierarchy. Option 2 is the
default.
Sequence:
set synce wander filter [option1|option2] press Enter
The system responds (example – option2 selected):
synce mode :off
primary clock source :wp1
secondary clock source :p3
configured revertive mode :on, wait time 30 sec
Enable SyncE feature Use this command to enable syncE. Select manual when you want
the system to go into holdover when the primary clock source fails. If
the primary source recovers, the system will automatically switch back
to the primary source. Select auto if you want the system to switch to
the secondary clock source if the primary clock source fails. In auto
the system will not switch back to the primary if the primary clock
recovers, unless set synce revertive is enabled.
Sequence:
set synce mode [off|manual|auto]
Example: set synce mode auto press Enter
The system responds (example set to auto):
configured mode : auto
configured revertive mode : on, wait time 30 sec
View current syncE Use this command to return the current syncE configursation settings.
configuration Sequence:
get synce config press Enter
configured mode : auto
configured revertive mod : on, wait time 30 sec
Synchronous Ethernet
27
Required for This is a user troubleshooting command which forces the system into
troubleshooting only. holdover mode for a configurable timeout value (time) in seconds. The
Forcing syncE into holdover default timout is 30 seconds. Values can be 0 to 300 seconds. 0 keeps
mode the holdover on indefinitely.
Sequence:
set synce forced holdover [on|off][time]
Example: set synce forced holdover on 60 press Enter
Synchronous Ethernet is put into holdver for 60 sec.
get synce status press Enter

mode: auto
clock source: wp1
acquisition status: holdover
forced holdover: on
remaining time in forced holdover: 52 sec
DragonWave Inc.
28

6.0 Network Management Interfaces
Both in-band and out-of-band management can be configured. For in-band management, any, or all
ports, can be configured for management. For out-of-band management only one port should be
configured for management and that port assigned to an isolated port group (IPG).
6.1 In-band Management

The user can select any user ports (P1 to P8) and data paths (DP1 to DP4) to manage the system.
Procedure 6-1 demonstrates examples of in-band management configuration.
Note: Ports that are available on the Quantum ODU modem differ from those available on the
Quantum IDU modem. See Table 4-1 for ports that are available on the Quantum ODU modem and
the equivalent IDU ports.
Procedure 6-1
Configuring Network Management Interface – In-band
Required Steps
Action
set network Set the network management interface for in-band management of the system. This is an
management interactive command.
interface for in-
band Sequence (Example):
management set network management interface press Enter

Port List (p3) ? p3,dp4 (note - any, or all, ports can be set for management. In
this example both port p3 and data path dp4 are
configured as management ports)
Management Vlan Id [1 - 4095] (1):
vlan priority [0 - 7] (0):
Apply the setting to system immediately, and automatically save Mib,

Continue? Enter Y(Yes) or N(No):y
(Note – although the system response indicates that the “Mib” will be saved it is
actually the l2swmib that will be saved.)
Configuring management interface...
In the example, p3 is configured for management with management traffic being directed to
data path 4 (dp4). This can be verified by using the command:
get network management interface press Enter

----------------------------------------------------------------------
MANAGEMENT INTERFACE CONFIGURATION
======================================================================
management interface :p3,dp4
vlan id :1
vlan priority :0
DragonWave Inc.
30
Required Steps
Action
If desired, This command places the management ports, p3 and dp4, in an isolated port group (IPG) and
allocate the adds a second data path (dp2) to the IPG.
management
interface to an Sequence (Example):
isolated port set ipg config ipg1 enable p3, ,dp2, dp4 press Enter
group (IPG) The system responds:
----- ------- ------------
ipg1 enable p3, dp2, dp4
ipg2 disable
ipg3 disable
ipg4 disable
ipg5 disable
Note: Because dp2 has been added to the same ipg as that of the previously configured
management data path dp4, dp2 and dp4 both form a logical port which will share network
management traffic. This is indicated by an asterix (*) beside dp2 when the following
command is issued. The asterix reminds us that dp2 is not the network management data
path that has been specifically configured by the user.
----------------------------------------------------------------------
======================================================================
management interface :p3,dp2*, dp4
vlan id :1
vlan priority :0
If the isolated port group carrying management traffic (in this case ipg1) is disabled, the
management relationship between dp2 and dp4 is maintained.
set ipg config ipg1 disable press Enter
----- ------- ------------
ipg1 disable
ipg2 disable
ipg3 disable
ipg4 disable
ipg5 disable
----------------------------------------------------------------------
======================================================================
management interface :p3,dp2*, dp4
vlan id :1
vlan priority :0
Network Management Interfaces
31
6.2 Out-of-band Management

By assigning the management ports as the ports belonging to an isolated port group (IPG), the user can
isolate the system management from other user traffic. In a specific case where the system has to be
managed out-of-band using a single port, an IPG is created with the required port as the only member.
Figure 6-1 Out-of-band System Management
IPG1
IPG2
IPG1 IPG2
Management port IPG5
P1 P1 Management port
P2 P2
P3 P3
P4 P4
IPG5 P5 DP1 DP1 P5

M M
Classifier
Classifier
P6 DP2 Q o o DP2 P6
Q
o d d o DP3
P7 DP3 S e e P7
S
m m
P8 DP4 DP4 P8
IPG4
IPG3
IPG4 IPG3
Figure 6-1 illustrates this approach. IPG5 has been configured with port P3 as the only member. The
management interface of the system is also configured as P3.
Note: The above configuration is the default configuration of the system when the system is
shipped out. The user has the option to default to this configuration.
Procedure 6-2
Configuring Network Management Interface – Out-of-band
Required Steps
Action

DragonWave Inc.
32
Required Steps
Action
set network Set the network management interface as a single port. This is an interactive command.
management
interface for out- Sequence:
of-band set network management interface press Enter
management
Example:
->set network management interface

Port List (p3) ? p3 (note - only one port should be set for out-of-band management)
Apply the setting to system immediately, and automatically save Mib,

(Note – although the system response indicates that the “Mib” will be saved it is
actually the l2swmib that will be saved.)
In the example, p3 alone is configured for management. This can be verified by using the
command:
----------------------------------------------------------------------
======================================================================
management interface :p3

vlan id :1
vlan priority :0
To Isolate the management port to an IPG (there are 5 - ipg1 through ipg5 – ipg5 is used in
the example) use the following CLI:
set ipg config ipg5 enable p3

----- ------- ------------
ipg1 disable
ipg2 disable
ipg3 disable
ipg4 disable
ipg5 enable p3

7.0 VLAN Configuration
All user ports (P1 to P8) can be configured as either an access port or a trunk port.
Access Port
When configured as an access port, an access VLAN id is assigned to the port by the user. This port will
allow all packets which are untagged, priority tagged, and VLAN tagged with the user assigned access
VLAN id, to be accepted. All other packets are discarded at the ingress.
Trunk Port
When a port is configured as a trunk port, an access VLAN is also assigned to this port. The user can
configure a range of VLAN id’s to be trunked on this port.
Priority
The user can assign an 802.1p priority level to each port. All untagged packets will be assigned the
priority associated with the port.
Double Tagging
A double tag cannot be inserted at any ingress port. However, the system will pass double tagged
packets. The outer tag should be 8100.
Procedure 7-1
VLAN Configuration
View the VLAN status Display current vlan status information.

Sequence:
get vlan status Press Enter
Example:
---------------------------------------------------------------------
SWITCH PORT VLAN STATUS
=======================================
Vlan Access Port Status:
VlanId Port List

------ ------------------------------
1 p1, p2, p3, p4, p5, p6
Vlan Trunk Port Status:
Port Default Vlan Allowed Vlan List

---- ------------ ---------------------------------------------
p7 1 1-4095
p8 1 1-4095
DragonWave Inc.
34
View the current VLAN Display vlan configuration parameters.

configuration. Sequence:
get vlan config Press Enter
Example:
---------------------------------------------------------------------------
SWITCH PORT VLAN CONFIGURATION
===========================================
Vlan Access Port Configuration:
VlanId Port List

------ ------------------------------
1 p1, p2, p3, p4, p5, p6
Vlan Trunk Port Configuration:

---- ------------ ---------------------------------------------
p7 1 1-4095
p8 1 1-4095
Bandwidth Management
35
set vlan config Configures vlan on a specified Ethernet port. This is an interactive command.
Sequence:
set vlan config press Enter
Example:
->set vlan config

Port [ 1 - 8 ] (1) ? 2
Vlan Port Type [ access(1) | trunk(2) ] (1): 1
Vlan Id [1- 4095 ] (1):10
Apply the setting to system immediately, Continue?

Enter Y(Yes) or N(No):y
Configuring Vlan...
--------------------------------------------------------------------------
SWITCH PORT VLAN CONFIGURATION
==========================================
Vlan Access Port Configuration:
VlanId Port List

------ ------------------------------
1 p1, p2, p3, p4, p5, p6, p7, p8
10 p2
Vlan Trunk Port Configuration:

---- ------------ ---------------------------------------------
p7 1 1-4095
p8 1 1-4095
DragonWave Inc.
36
set port default priority Configures (sets) the default vlan priority on switch port.
Sequence:
set port default priority and press Enter

Port [ 1 - 8 ] (1) ? 2
Vlan Priority [0 - 7] (0):7
Apply the setting to system immediately, Continue? Enter

Y(Yes) or N(No):y
Port# Priority
---- --------
1 0
2 7
3 0
4 7
5 5
6 0
7 0
8 0
View the port default priority This command returns the current port default priority.
Sequence:
get port default priority and press Enter
The stystem responds:
Port# Priority
---- --------
1 0
2 7
3 0
4 7
5 5
6 0
7 0
8 0
37
flash memory.
Sequence:
7.1 ECFM
ECFM is allowed on all user ports (P1 to P8). One instance of ECFM can also be configured on the data
path. The minimum allowed CCM period is 100msec.
Note: The number of supported MEPs will be limited by the CCM period.
See Volume 4 of this manual for more information on ECFM.
7.2 Rapid Link Shutdown (RLS)

The user can select any combination of the eight Ethernet ports to be part of the RLS logic. Out of the
selected Ethernet ports, the user can create three groups of ports to provide the link state input to the
RLS algorithm. When any of the three link state inputs indicates that the link is down, then RLS is
triggered. For example, if the user creates the following groups of ports:
• Group A: port P1 and P2
• Group B: port P3
• Group C: port P4, and P5.
….. RLS will be triggered when both of P1 and P2, or P3, or any of P4 and P5 ports lose the link. RLS
would also be activated at the other end of the link.
In the above example, all the ports indicated above will be shut down when RLS is triggered.
Note: The current RLS implementation does not maintain the user port integrity across the
wireless link. This means that, in the above example, when port P3 is down, ports P1 to P5 are
also shut down, not just P3. Ports that are configured for RLS at the far end will also be shut down
(these do not have to be the same port numbers as the near end).
See Section 16.0 for more information on configuring RLS.
DragonWave Inc.
38

8.0 Bandwidth Management
When you purchase a Horizon Quantum system you receive a unit having two modems, each capable of
giving a throughput speed (bandwidth) of up to 400 Mbps. However, the actual throughput speed
achievable for any given system depends on the specific licensed speed key that you purchased with the
system
You can upgrade your system to a higher licensed speed by purchasing an upgrade key and
reprogramming your system. Any upgraded system can be reconfigured to a lower system speed (CLI
command set system current speed) as required, without losing the ability to return to the upgraded
licensed speed.
Under certain circumstances Horizon Quantum systems may be shipped from the factory with the
Licenced speed set to zero. This also automatically sets the system speed to zero. On upgrading the
licensed speed using a license key, the system speed will remain at zero (and thus prevents any
transmission of traffic over the air). Consequently, the System speed needs to be manually set (CLI
command set system current speed) to the desired value before the system will transmit traffic over the
air.
You may also downgrade the licensed speed to a lower value. Once downgraded, new upgrade keys will
be required for future upgrading.
System speeds do not have to be symmetrical (same speed in both directions on the link). Asymmetric
speeds (different speeds in each direction) can also be configured.
8.1 Maximum Throughput Speed

The maximum throughput speed is determined by the Horizon Quantum licensed speed key you
purchase, however, it is important to note that the maximum speed is also determined by the Channel
bandwidth associated with the configured radio band, and the modulation scheme used. The channel
bandwidth is a function of the radio band and the modulation scheme is selected depending on the
desired maximum throughput. Configuring the Radio Band and System Mode determines the maximum
throughput capability and the modulation scheme applied.
Note that if a System Mode is set with a maximum throughput capability that exceeds the licensed speed
key purchased from DragonWave, then the maximum speed attainable will be limited to the licensed
speed purchased. By default the system speed is set to the licensed speed key purchased, however, it
can be reduced to a lower level without losing the ability to return to the purchased licensed speed.
Table 8-1 shows the modulation schemes that are selected for various System Modes (combination of
channel bandwidth and maximum throughput).
Table 8-1 System Mode and Modulation Scheme
Single Channel Dual Channel
Channel Rx Throughput Throughput
Modulation Schemes Tx Power Tx Power
Bandwidth Sensitivity * *
56 MHz QPSK / 32QAM / 256QAM -80/-70/-59 47/210/373 17/11/9.5 94/420/746 13/7/5.5
50 MHZ QPSK / 64QAM / 256QAM -81/-68/-59 49/209/359 17/12.5/9.5 98/418/718 13/8.5/5.5
40 MHz QPSK / 64QAM / 256QAM -81/-69/-60 42/175/268 17/10.5/9.5 84/350/536 13/6.5/5.5
30 MHZ 32QAM / 128QAM / 256QAM -75/-65/-62 103/160/205 13/10/9.5 206/320/410 9/6/5.5
28 MHZ QPSK / 32QAM / 256QAM -84/-75/-64 35/105/187 13.5/11/9.5 70/210/374 9.5/7/5.5
14 MHz QPSK / 32QAM / 256QAM -87/-80/-68 17/46/92 13.5/13/9.5 34/92/184 9.5/9/5.5
7 MHz QPSK / 64QAM / 128QAM -88/-78/-74 8/32/38 17/10.5/10 16/64/76 13/6.5/6
Note: Not all Horizon Quantum modes are shown in the above table:
Horizon Quantum supports: 7, 10, 13.75, 14, 27.5, 28, 30, 40, 50, 55 & 56 MHz channel spacing
Horizon Quantum supports: QPSK; 16, 32, 64, 128, 256 , 512, 1024, 2048 QAM modes
*Average packet throughput is calculated using 64, 128, 256, 512, 1024, 1280, and 1518 bytes Ethernet frames
DragonWave Inc.
40
Procedure 8-1
Configure Horizon Quantum Throughput Speed (Symmetrical Throughput)
login Log in as a NOC user.
get system speed Returns the licensed speed key value, the current set system speed
and the set mode.
Sequence:
get system speed press Enter
Licensed speed set to : n Mbps
Current speed set to : n Mbps
System mode set to : <system mode>
Example:
Licensed speed set to :100 Mbps
Current speed set to :100 Mbps
System mode set to :hx50_127_16qam
Note that although the mode shows a speed of 125 Mbps, the actual
speed will be limited to the current speed, or the licensed speed,
whichever is the lower.
get system mode Returns the current system mode and a list of available system
modes.
Sequence:
get system mode press Enter
System responds:
Current system mode is : hx50_358_256qam (Example)
System modes available in the system:
cw_test hx50_49_qpsk hx50_127_16qam
hx50_169_32qam hx50_212_64qam hx50_267_128qam
hx50_358_256qam hx50_267ac_128qam hx50_317ac_256qam
41
set system mode Sets the system mode (channel bandwidth, maximum throughput
speed and modulation scheme). You can only select any one of the
modes shown as available when the get system mode command is
used.
Sequence:
set system mode <hc[bandwidth]_[throughput]_[modulation]>
Where [bandwidth] is the channel bandwidth of the configured
radio band; [throughput] is the maximum throughput capability in
Mbps; [modulation] is the modulation scheme.
Example:
set system mode hx50_127_16qam press Enter
(50 MHz channel bandwidth, 127 Mbps throughput and 16QAM
modulation).
System responds:
System mode set to : hx50_127_16qam
save mib Saves the MIB to RAM. Perform this command to save setting
changes to non-volatile memory.
Sequence:
save mib press Enter

Reset system A system reset is required to activate this feature.

Sequence
reset system press Enter
Are you sure you want to reset? Y(yes) or N(no)
press Y
The system will proceed to reset. You will have to log on again to
regain access.
DragonWave Inc.
42
8.2 Asymmetric Throughput Speed

Asymmetric throughput can be achieved by installing the same Horizon Quantum hardware type at each
end of the link, and configuring one end with a different system speed. Note, that the System Mode, must
be identical at each end of the link for this to work. The variable will be the system speed figure.
Procedure 8-2
Configure Horizon Quantum Throughput Speed (Asymmetric)
get system mode Returns the current system mode and a list of available system
modes.
Sequence:
get system mode press Enter
System responds:
Current system mode is : hx50_127_16qam (Example)
System modes available in the system:
cw_test hx50_49_qpsk hx50_127_16qam
hx50_358_256qam hx50_267ac_128qam hx50_317ac_256qam
set system mode Sets the system mode (channel bandwidth, maximum throughput
speed and modulation scheme).
Sequence:
set system mode <hc[bandwidth]_[throughput]_[modulation]>
Example:
set system mode hx50_169_32qam press Enter
(50 MHz channel bandwidth, 169 Mbps throughput and 32QAM
modulation.
System responds:
Note: For asymmetric speeds, the system mode must be set identically
at each end of the link.
43
Set system speed Sets the system speed. (Cannot exceed the speed key purchased with
your system).
Sequence:
set system current speed 50 press Enter
System responds:
System speed set to 50 Mbps
Note: For asymmetric speeds the speed at the other end of the link
would be set to a different value.
Example:
Near end – set system current speed 50 press Enter
Far end – set system current speed 100 press Enter
Note: if the speed at one end was to be the purchased speed (default),
then this command would not need to be invoked at that end.
Sequence:


Sequence
press Y
regain access.
DragonWave Inc.
44
8.3 Upgrading System License Speed

Upgrading the system licensed speed requires an upgrade license key obtainable from DragonWave.
Upgrading the licensed speed does not cause you to lose the ability to reduce the speed and then return
to the new licensed speed at a later time.
Note that the licensed speed is the maximum speed that the system can operate at, regardless of the
setting of the System Mode.
Procedure 8-3
Upgrading Horizon Quantum System License Speed
get system speed Returns the licensed speed key value, the current set system speed
and the set mode.
Sequence:
Example:
System mode set to :hx50_127_16qam
Note that although the mode shows a speed of 127 Mbps, the
actual speed will be limited to the current speed, or the licensed
speed, whichever is the lower.
Upgrade system licensed Upgrades the system to operate at a higher speed. A license key is
speed required for this command. Contact DragonWave.
Sequence:
upgrade system licensed speed [speed] [key] press Enter
Where [speed] is the new licensed speed, and [key] is the license key
obtained from DragonWave
45
Sequence:


Sequence
press Y
regain access.
DragonWave Inc.
46
8.4 Downgrading System License Speed

Downgrading the system license speed to a value lower than previously purchased is supported.
Information presented by the system, when downgraded, needs to be sent to DragonWave in order to
confirm the status of your license.
NOTE: Once the system license speed has been downgraded, a new license key is required if you
wish to return to a higher licensed speed.
Note that the licensed speed is the maximum speed that the system can operate at, regardless of the
setting of the System Mode.
Procedure 8-4
Downgrading Horizon Quantum System License Speed
get system speed Returns the licensed speed value, the current set system speed and the
set mode.
Sequence:
Example:
47
Downgrade system licensed Downgrades the system licensed speed to operate at a lower maximum
speed speed.
Warning: Once you issue this command your current license speed
key will be lost and you will not be able to return to your original
licensed speed without acquiring another license key from
DragonWave.
Sequence:
downgrade system licensed speed [speed] press Enter
Where [speed] is the new lower licensed speed in Mbps.
Example:
downgrade licensed speed to 200
The system responds: (Example)
The current system licensed speed will be downgraded to 200 Mbps.
This operation will force to save Mib. Continue? Enter Y(Yes) or
N(No):y
The current system licensed speed is downgraded to 200 Mbps.
Downgrade Confirmation Information:
Speed Decrement :200
Speed Count :2
Unit Serial Number :DW130AAG0100
MAC Address :00-07-58-00-a2-16
Confirmation Number :bc7ed7dd89a4d98adbab263630a9a27e
To determine the status of your license, the information shown above,
under the heading “Downgrade Confirmation Information”, needs to be
sent to DragonWave.
Licensed speed count This command returns the number of times that the licensed speed has
been changed. This value is required by DragonWave, in addition to the
information returned in the previous step, in order to determine the status
of your license.
Sequence :
get licensed speed count press Enter
The system responds :
Licensed Speed Counter is: 2 (Example)
DragonWave Inc.
48
Licensed speed downgrade This command returns the licensed speed downgrade information that
information was presented during the downgrade process. This is the same
information that DragonWave needs in order to verify the status of your
license.
Sequence :
get licensed speed downgrade information press Enter
The system responds : (Example)
Downgrade Confirmation Information:
Speed Decrement :200
Speed Count :2
Unit Serial Number :DW130AAG0100
MAC Address :00-07-58-00-a2-16
Confirmation Number :bc7ed7dd89a4d98adbab263630a9a27e
8.5 Throughput (Bandwidth) Logging

As discussed earlier, the maximum throughput speed, or bandwidth, of a system is determined by the
purchased licensed speed key. This allows a service provider to provide a limited bandwidth and to bill for
it accordingly.
Another billing method is to use Bandwidth Logging. This feature monitors bandwidth consumption over
time and the customer would be billed for the actual bandwidth consumed and not for a preset maximum
bandwidth. As with the speed key, you will need to consult with DragonWave Inc. if you wish to make use
of this option.
The Bandwidth Logging feature creates records that indicate the bandwidth utilization over a set reporting
period. At the end of the reporting period the record is written to flash. Up to 60 records can be stored in
flash. After 60 records have been written, the oldest records are overwritten. Each record (0 through 59)
represents the bandwidth utilization accrued over a 24 hour period and may be selectively viewed. A
record that is currently being accrued may also be viewed.
Procedure 8-5
Bandwidth Logging
login Log in as the Super User.

49
Configure bandwidth record Up to ten bandwidth utilization thresholds can configured. This command
thresholds will set the bandwidth utilization threshold integers as a percentage. The
ten integers are entered separated by spaces. The values shown below
are the default.
Sequence:
set bandwidth record thresholds 10 20 30 40 50 60 70 80 90
95 press Enter
Bandwidth Utilization Thresholds set to: 10 20 30 40 50 60 70 80
90 95
Note that the average period and the reporting period are preset values.
View bandwidth record This command returns the bandwidth record settings.
thresholds
Sequence:
get bandwidth record thresholds press Enter
Bandwidth Utilization Thresholds:
10 20 30 40 50 60 70 80 90 95
Start bandwidth logging This command turns logging on or off. Note that reports are saved to
flash memory irrespective of whether this is on or off.
Sequence:
set bandwidth record logging [on|off] press Enter
Bandwidth utilization logging to both event log and syslog set to
‘on|off’
View status of bandwidth This command will return the logging status.
logging
Sequence:
get bandwidth record logging press Enter
Bandwidth logging to syslog and flashlog set to ‘on|off’
View the administrative status The command will return the administrative status of bandwidth logging.
of bandwidth logging Sequence:
get bandwidth record admin press Enter
Bandwidth logging admin status set to ‘on’
Bandwidth logging oper status is ‘on
DragonWave Inc.
50
Save changes to mib Saves the MIB to RAM. Perform this command to save setting changes
to non-volatile memory.
Sequence:

View bandwidth records in Up to 60 records are maintained in the Syslog. A brief view of all records
brief can be obtained using the following CLI command.
Sequence:
get bandwidth record brief press Enter
Inst Serial Date of Report Date of Max Utilization Util
---- ------ ----------------------- ----------------------- ----
0 1 02/05/2009 15:52:38 01/05/2009 17:45:15 88%
1 2 03/05/2009 15:52:39 03/05/2009 10:25:09 84%
2 3 07/05/2009 15:46:56 07/05/2009 12:14:36 43%
3 4 09/05/2009 17:15:10 08/05/2009 18:16:35 33%
59 60 10/06/2009 17:15:13 09/06/2009 17:46:52 77%

51
View a specific bandwidth A specified record (0 – 59) can be viewed in detail by using the following
record in detail command.
Sequence:
get bandwidth record instance (0-59) press Enter
Serial Number: :1
Report ending : 02/05/2009 15:52:38
Maximum utilization
Utilization was : 88%
Time and date was : 01/05/2009 17:45:15
Egress Speed was : 397 Mbps
Peer Current Speed was : 450 Mbps
Egress bytes were : 178713641492
Elapsed cycles were : 90021622135
Reporting period duration was : 86400s
Unit serial number was : DW109ABC1016
Peer unit serial number was : DW110ABH1013
Peer Current Speed was : 450 Mbps
MAC Address was : 00075800C01A
Instantaneous Utilization Counts were (average sample duration
1012ms):
10%: 85045 (86088 seconds)
20%: 84986 (86028 seconds)
30%: 84925 (85966 seconds)
40%: 84893 (85934 seconds)
50%: 84720 (85759 seconds)
60%: 84719 (85758 seconds)
70%: 84699 (85737 seconds)
80%: 84103 (85134 seconds)
90%: 2114 (2139 seconds)
95%: 1713 (1734 seconds)
DragonWave Inc.
52
View the current record This command returns the values currently being accrued, but not yet
written to a record. It shows the time left in the sampling period (1319
seconds in the example below) before the running average is valid (the
running average period must elapse before the running average is valid).
The record will be written to flash in 86400s – 2281s = 84119s.
Sequence:
get bandwidth record current press Enter
Current Running-Average Bandwidth Utilization: 90% (valid in
1319s)
Maximum Running-Average Bandwidth Utilization (averaging
period = 3600s):
Date and Time: not available (ready in 1319s)
Utilization: 0%
Elapsed time in reporting period (period = 86400s): 2281s
Instantaneous Utilization Counts were (average sample
duration 1046ms):
10%: 2048 (2143 seconds)
20%: 2048 (2143 seconds)
30%: 2044 (2138 seconds)
40%: 2037 (2131 seconds)
50%: 2036 (2130 seconds)
60%: 1951 (2041 seconds)
70%: 1950 (2040 seconds)
80%: 1947 (2037 seconds)
90%: 1944 (2034 seconds)
95%: 1935 (2024 seconds)
9.0 Capacity Expansion Features
Limitations and/or restrictions to local radio frequency allocations and channel spacings can restrict the
throughput capabilities (bandwidth) of a Quantum system. There are three Quantum features which can
increase system bandwidth and yet still operate within the restrictions noted above. These are:
• Bandwidth Acceleration
• Bandwidth Doubling
• Cross Polarization Interference Cancellation (XPIC)
9.1 Partner Nodes Communication Channel

There are some Quantum features that require two Quantum systems on each end of the wireless link.
These include Bandwidth Doubling, Multi-channel XPIC and HSB (Hot standby). For these features to
work properly, a dedicated Ethernet connection between partner Quantum units at each end is required.
Two Quantum partners exchange control information with each other over this dedicated Ethernet
connection.
To dedicate a port as the intra-partner control connecton use the CLI command get/set partner
When configuring the partner control port, use caution so as not to create an Ethernet loop. This means
that any associated Isolated Port Group (IPG) needs to be properly configured to avoid loops.
9.2 Bandwidth Acceleration

Access to this feature requires a DragonWave license key.
A Quantum dual modem, single radio system, operating at an over-the-air base capacity of 800 Mbps, is
capable of carrying a data rate of up to 2000 Mbps, when DragonWave bandwidth acceleration is
employed. Rates of up to 4000 Mbps, on a single antenna, can be achieved if the DPRM is used. The
amount of acceleration available on any given link is variable and data dependent.
Each of the four data queues in the system (same as those used for QoS) can be independently
configured to support bandwidth acceleration, with related statistics made available through system
management.
Procedure 9-1
Bandwidth Acceleration
Use this procedure to set up and view the status of bandwidth acceleration.
Key to system response headings:
Queue: user traffic queue number as used in QoS
Enable: if BAC is enabled or disabled
Block Size: the compression block size of the queue (bytes)
Uncompressed Ratio: Uncompressed Bytes Out / Bytes In * 100 (The % of
data from a given queue that could not be reduced in
size)
Bac Gain: Bytes In / (Compressed Bytes Out+Uncompressed
Bytes Out) compression gain for a given queue as a
ratio.
Running Average: average of previous n samples taken over a window of
time as specified in the “Record Average Period” CLI
command
DragonWave Inc.
54
Inst/Instance: refers to the index number (instance) used in the flash

buffer that hold 60 records - the instance number wraps
after instance 59
unitsn: unit serial number of the device at the time that the
report was generated
sn/Record serial number/Record num: the serial number of the record which is always
incrementing. Records in the flash are identified by this
unique number. There are up to 60 record positions
available in flash. When all positions are full, then the
oldest record is overwritten with the newest record.
login Log in using the Super user or a NOC account.
View the current This command retrieves the current bac configuration.
status of bandwidth
acceleration (bac) Sequence:
get bac press Enter
Running Average
Queue Enable BlockSize Uncompressed BAC
ratio(%) Gain
1 off - - -
2 on 8000 0 3.14
3 off - - -
4 on 8000 0 3.79
55
Configure This command allows the user to configure BAC per queue. Allowed block sizes are 256,
bandwidth 512, 1024, 4032 and 8000 bytes. User can change the configuration on all queues by
acceleration for specifying the ‘all’ keyword instead of specifying an individual queue number.
one or all queues.
Sequence:
set bac [queue number] [on/off] [block size] press Enter
Where [queue number] is any queue 1 through 4, or ‘all’ for all queues and [block size] is
any one of 256, 512, 1024, 4032 or 8000 bytes.
Example a: set bac 1 on 8000 press Enter

BAC enabled on queue 1, with block size 8000.
Running Average
ratio(%) Gain
1 on 8000 0 -
2 on 8000 0 3.14
3 off - - -
4 on 8000 0 3.79
Example b: set bac 1 off press Enter
Running Average
ratio(%) Gain
1 off - - -
2 on 8000 0 3.14
3 off - - -
4 on 8000 0 3.79
View the bac Returns the number of seconds configured for computing the running average bac gain and
record average uncompressed ratio. Default average period is set to 10 seconds.
period.
Sequence:
get bac record average period press Enter

BAC running average period set to 10 seconds
DragonWave Inc.
56
Set the bac record Allows the user to configure the average period used for computing the running average bac
average period gain and uncompressed ratio. Default average period is set to 10 seconds.
Sequence:
set bac record average period [seconds] press Enter

Where [seconds] is the desired average period in seconds. A value from 10 through 3600 is
recommended.
The system responds (Example):
BAC statistics running average period set to 20 seconds.
View the status of Returns the bac logging recording status to flash and syslog as either 'on' or 'off'. If no queue
logging is specified, then the logging configuration status of all queues is displayed.
configuration.
Sequence:
get bac record logging press Enter
BAC logging to syslog and flashlog on queue 1 set to :off
BAC logging to syslog and flashlog on queue 2 set to :on
Configure bac Allows the user to enable/disable logging of bac related statistics, like Maximum BAC gain
record logging. and Maximum uncompressed ratio, on a per queue basis, to syslog and flashlog. If logging
is disabled for a particular queue, then these statistics will not be logged to either syslog or
flashlog.
Sequence:
set bac record logging [1, 2, 3, 4] [on/ off] press Enter
Example a: set bac record 2 on press Enter
BAC logging to both event log and syslog, for queue 2, set to :on
Example b: set bac record 2 off press Enter

BAC logging to both event log and syslog, for queue 2, set to :off
57
View the active Returns the contents of the active bac record (has not yet get been saved in flash) for the
statistics (still being specified queue.
compiled) for a
specific queue
before they are Sequence:
saved to a record.
get bac record current [queue number] press Enter
Where [queue number] is any queue number from 1 through 4.
Example:
get bac record current 4 press Enter
Queue number is : 4
Average period : 10s
Elapsed time : 125s
(report period = 86400s)
Maximum bac gain
Gain is : 2.31
Time and date is : 03/05/2010 20:32:08
Maximum uncompressed ratio
Ratio is : 0%
Time and date is : 03/05/2010 20:29:47
Unit serial number is : TBD
Peer unit serial number is : TBD
MAC Address is : 0007580291C8
View a brief listing Returns the bac related flash records stored in flash in a brief format for the specified Queue.
of all available Up to a maximum of 60 records can be stored in flash. If the record number of interest is no
records for a longer visible in this list, then that record has been overwritten with the new record.
particular queue
number. Sequence:
get bac record brief [queue number] press Enter
Where [queue number] is any queue number from 1 through 4
Example: get bac record brief 4 press Enter
Queue Number : 4
Record Max BAC Time of MaxUncompress Time of
Inst num. Date of Report Gain MaxBacGain ratio(%) MaxUncompressRatio
---- ------ ----------------------- ----------------------- ----------------------------------------
0 11581 03/05/2010 20:29:14 0.00 03/05/2010 20:28:45 0 03/05/2010 20:28:45
1 11582 03/05/2010 20:29:44 0.00 03/05/2010 20:29:15 0 03/05/2010 20:29:15
2 11583 07/05/2010 20:38:05 0.00 06/05/2010 20:38:14 0 06/05/2010 20:38:14
3 11584 08/05/2010 20:38:08 0.00 07/05/2010 20:38:06 0 07/05/2010 20:38:06
4 11585 09/05/2010 20:38:12 0.00 08/05/2010 20:38:09 0 08/05/2010 20:38:09
5 11526 03/05/2010 19:32:27 5.38 03/05/2010 19:31:59 0 03/05/2010 19:31:58
6 11527 03/05/2010 19:32:57 5.38 03/05/2010 19:32:29 0 03/05/2010 19:32:28
7 11528 03/05/2010 19:33:28 5.38 03/05/2010 19:32:58 0 03/05/2010 19:32:58

DragonWave Inc.
58
View a verbose This command will give a verbose view of the stored bac records stored in flash.
listing of bac
records stored in Sequence:
flash memory.
get bac record verbose [queue number] press Enter
Example: get bac record verbose 4 press Enter
instance:0,sn:11581,date:"03/05/2010 20:29:14 ",elapsed:30,
mac:0007580291C8,unitsn:TBDq4->Max [BAC Gain:0.00 date:03/05/2010 20:28:45 ,
UncompressRatio:0% date
:03/05/2010 20:28:45 ]
:03/05/2010 20:29:15 ]
UncompressRatio:0% d
ate:06/05/2010 20:38:14 ]
ate:07/05/2010 20:38:06 ]
ate:08/05/2010 20:38:09 ]
:03/05/2010 19:31:58 ]
9.3 Bandwidth Doubling
Bandwidth Doubling does not support RLS, ATPC, or Radio Redundancy.
Bandwidth Doubling may be employed where the available radio bands for an installation have
throughput limiting channel spacing that results in a single Horizon Quantum unit not being able to
provide the desired data rate for the link.
In a Bandwidth Doubling configuration two Horizon Quantum links are bound together by using a
proprietary “packet fragmentation” mechanism that segments Ethernet packets into small fragments
(carried in “modem blocks”) and equally shares these fragments between the two radio links. This
combining of channels effectively doubles the available Ethernet Bandwidth of the complete system.
Each of the two links in a Bandwidth Doubling configuration includes a Primary and Secondary unit. User
traffic is connected to the Primary unit. Note that the Primary unit must be configured to handle the
aggregated input rate of the bandwidth doubling link. This may require an upgrade to the licensed
speed (see Section 8.0 for more information).
Setting the bandwidth doubling mode of a unit determines if it is considered a Primary or Secondary unit.
An Ethernet cable is connected between the two Horizon Quantum units on an available Ethernet
faceplate port that is designated as the Bandwidth Doubling Port. It is through this port that the two
Quantum units share packet fragments. If only one of the Quantum pairs has an Ethernet connection
then a second Ethernet cable is connected between the two Horizon Quantum units on an available
Ethernet faceplate port to provide Management traffic interconnection.
Figure 9-1 Bandwidth Doubling Physical Connections .
All Queuing and QoS functions take place on the Primary unit. The Primary unit also performs the
“packet fragmentation” function where Ethernet Packets destined for the air are segmented into small
fragments (modem blocks) and split between the Primary and Secondary units. Modem blocks are
passed to the Secondary unit inside Ethernet frames via the Bandwidth Doubling port. “Packet
fragmentation” occurs automatically in a Bandwidth Doubling configuration, is independent of the shaping
function provided by the QoS feature, and evenly distributes data across both radio links based solely on
the available air bandwidth of each link.
In a Bandwidth Doubling configuration, if the user network feeds more than 1Gbps traffic to the Primary
Quantum, the subtending switch could use LAG (Link Aggregation Group) over more than one Ethernet
port. If the subtending switch uses a LAG to feed traffic into the Quantums, each Quantum front panel
port and a corresponding data port need to have a separate IPG. MAC address learning also needs to be
disabled on these ports (use the CLI command set mac-learning [enable|disable port id]).
DragonWave Inc.
60
For Bandwidth Doubling, there are a few options to manage the Quantum. Out-of-band management is
always supported. If link aggregation is not used over the data ports feeding the Quantum, in-band
management is supported. The Quantum management interface needs to be configured properly
following normal management configuration (see Section 6.0) as in a single Quantum link. In addition, for
the Bandwidth Doubling configuration:
1. Management option 1 (see Figure 9-2), In-band management is used.
On the primary Quantum, P6 and P7 need to be in the same IPG (the same IPG needs to have a
DP in it, so the user data can be forwarded over the air), and needs to be configured as network
management interface shown in below.
On the secondary Quantum, P7 needs to be in its own IPG and configured as network
management interface.
In this example, on the primary Quantum unit
• P6 is connected to user network for Quantum management and payload traffic;
• P8 is used as Bandwidth doubling interconnection port;
• P7 is used as partner discovery management interconnection port;
• DP3 is used to carry over-air traffic.
In this deployment example, the following configurations are needed:
• Set P7 as partner port on both primary and secondary Quantum unit with CLI command set
partner;
• Set P6, P7 and DP3 into one IPG group with command set ipg config ipg3 enable
p8,p6,dp3;
• Set P6, P7 and DP3 as network management interface with command set network
2. Management option 2 (see Figure 9-3), when a LAG is formed by subtending switch, only out-of-
band management can be used. If the LAG is not used, from management perspective, user can
still select this configuration (in other words, one out-of-band management from user network to
manage both Quantums.)
In this example,
On primary Quantum
• P6 is connected to user network for Quantum management;
• P4 is connected to user network for Quantum payload;
• P8 is used as Bandwidth doubling inter-connects port;
• P7 is used as partner discovery management inter-connects port;
• Set P7 as partner port on both primary and seconardy Quantum unit with CLI command set
partner;
• Set P6, and P7 as in one IPG group with command set ipg config ipg3 enable p7,p6;
• Set P4, and DP3 as in one IPG group with command set ipg config ipg3 enable p4,dp3;
• Set P6, and P7 as network management interface with command set network management
interface.
On the primary Quantum, P6 and P7 needs to be in same IPG, and needs to be configured as
network management interface shown in the above example.
On the secondary Quantum, p7 needs to be in its own IPG and configured as network
RADIUS Server User Authentication
61
3. Management option 3 (see
4. Figure 9-4), out-of-band management to both Quantums are used.

On primary Quantum
• P6 is connected to user network for Quantum management;
• P4 is connected to user network for Quantum payload traffic;
• P8 is used as Bandwidth doubling inter-connect por;
• P7 is used as partner discovery management inter-connects port;
• Set P7 as partner port on both primary and seconardy Quantum unit with CLI command set
partner;
• Set P6 as in one IPG group with command set ipg config ipg5 enable p6;
• Set P4, and DP3 as in one IPG group with command set ipg config ipg3 enable p4,dp3;
• Set P6 as network management interface with command set network management
interface.
On the primary and Secondary Quantum, P6 and P7 needs to be in different each own IPG
The following diagrams show management options with Bandwidth Doubling. There are constant inter-
Quantum communications between local Bandwidth Doubling Quantum pairs, and a dedicated inter-
Quantum management communication cable is required for the local inter-Quantum communication.
Figure 9-2 Bandwidth Doubling Management Option 1

DragonWave Inc.
62
Note: With Option 3 (see Figure 9-3) when Data Encryption is enabled on a link with a bandwidth
doubling configuration, it is not recommended to have all four Quantum units with their own out-
of-band management connections.
63
9.3.1 Primary and Secondary Traffic Statistics

Traffic statistics vary between the Primary and Secondary units.
The Primary Unit counts:
1. Transmitted and received Ethernet packets to and from the user network
2. Transmitted and received Ethernet packets to and from the peer unit across the aggregated
wireless link
3. Transmitted and received Modem Blocks to and from the peer unit across the wireless link(s)
4. Transmitted and received Modem Blocks to and from the Secondary unit via the Bandwidth
Doubling connection
To view the traffic statistics use the CLI command get traffic statistics. For the Primary unit the system
will typically respond as follows:
-- Aggregation Ports--
Tx Frames :39164 <- Ethernet frames sent to the user network
Tx Bytes :12597352
Rx Frames OK :39187 <- Ethernet frames received from the user network
Rx Bytes OK :12417455
Rx Frames Error :0
BW Utilization(%) :11
Ingress Data Rate :41.72
Egress Data Rate :44.55
Frames in Queue1 :0
Frames in Queue2 :0
Frames in Queue3 :2117
Frames in Queue4 :37070
Frames in QueueC :0
Frames in Queue1 Discarded :0
Frames in QueueC Discarded :0
-- Aggregated Wireless Port

Tx Frames :39233 <- Ethernet frames sent wirelessly to peer
Rx Frames OK :39212 <- Ethernet frames received wirelessly
Rx Frames Error :0
Rx Queue Frames Discarded :0
-- Wireless Port1 (Wireless Port1)

Tx Blocks :87761 <- Modem blocks sent to peer unit (modem 1)
Rx Blocks OK :87761 <- Modem blocks received from peer (modem 1)
Rx Blocks Error :0

Rx Blocks OK :87821 <- Modem blocks received from peer unit (modem 2)
Rx Blocks Error :0
-- Secondary Wireless Ports

Tx Blocks :175699 <- Modem blocks sent to Secondary unit
Rx Blocks OK :175699 <- Modem blocks received from to Secondary unit
Rx Blocks Error :0
DragonWave Inc.
64
The Secondary Unit counts:

1. Transmitted and received Ethernet frames (containing modem blocks) to and from the Primary
unit on the Bandwidth Doubling port
2. Transmitted and received Modem Blocks to and from the peer unit across the wireless link(s)
3. Transmitted and received Modem Blocks to and from the Primary unit via the Bandwidth
Doubling connection
To view the traffic statistics use the CLI command get traffic statistics. For the Secondary unit the
system will typically respond as follows:
-- Aggregation Ports--
Tx Frames :160103 <- Ethernet frames (modem blocks) to Primary Unit
Tx Bytes :39065024
Rx Frames OK :160103 <- Ethernet frames (modem blocks) from Primary Unit
Rx Bytes OK :39065132
Rx Frames Error :0
BW Utilization(%) :3
Ingress Data Rate :148.72
Egress Data Rate :148.72
Frames in Queue1 :0
Frames in Queue2 :0
Frames in Queue3 :0
Frames in Queue4 :0
Frames in QueueC :0
Frames in QueueC Discarded :0
-- Aggregated Wireless Port

Tx Frames :0
Rx Frames OK :0
Rx Frames Error :0
Rx Queue Frames Discarded :0

Rx Blocks Error :0

Rx Blocks Error :0
9.3.2 Configuration Requirements

Bandwidth Doubling does not support RLS, ATPC, or Radio Redundancy.
All systems configured for Bandwidth Doubling operation must be configured with identical radio bands
and system modes. However, the partners (Primary and Secondary units) should be configured to work
on different frequency channels, with the Secondary on one end of the link matching the frequency
channel of the Primary of the other end. It is recommended that the frequencies on the two links in a
Bandwidth Doubling configuration be programmed to different channels unless the user has implemented
methods in their installation to overcome interference (e.g. XPIC – see Section 9.4) .
The “system current speed” rate setting limits the network traffic into the Bandwidth Doubling system.
9.3.2.1. Working with Authentication
When Bandwidth Doubling is enabled, authentication can only be enabled, and only occurs, on Primary
units. Authentication cannot be enabled on the Secondary unit.
65
9.3.2.2. Working with HAAM

The bandwidth doubling feature supports HAAM. When HAAM is in operation the system modes may be
upshifted or downshifted, as weather conditions dictate, to ensure that the link remains viable. However,
with HAAM enabled, the two links need to be running within ± 1 system mode of each other to pass traffic
properly. If the two links are running system modes that are two or more steps apart, then traffic will be
lost for as long as this condition exists.
Example: HAAM is enabled on both links of a bandwidth doubling configuration. One link undergoes a
HAAM downshift to 128QAM and the second link undergoes a HAAM downshift to 64QAM. Traffic will
continue to flow. If the second link undergoes another downshift to 32QAM and the first link remains at
128QAM, then traffic will be lost until the first link downshifts to 64QAM, or the second link upshifts to
64QAM.
9.3.3 Configuring Bandwidth Doubling

With the aforementioned provisions, the Horizon Quantum system is configured in the usual way but with
the additional configuration steps as shown in the following procedure.
Procedure 9-2
Configuring Bandwidth Doubling – this procedure needs to performed on both Quantum partners
and at each end of the link.
login Log in as a NOC User.

Network management This command configures the network management interface to support
configuration Bandwidth Doubling. The example adds p5 as the management port list.
Sequence (to view current settings):
-----------------------------------------------------------
===========================================================
management interface :p3
vlan id :1
vlan priority :0
Sequence (to configure settings):
set network management interface press Enter
Port List (p3) p5,p3 (We are adding the partner port p5 to the network
management interface, since p5 is used in the set partner example below.)
Apply the setting to system immediately, and automatically

save Mib.
(WARNING: This can affect current management session)
Continue? Enter Y(Yes) or N(No):Y
->
DragonWave Inc.
66
Set the partner control This command configures which port is to be used as the partner control
connection port communication port.
Sequence:
set partner [none | p1 - p8]
Example:
set partner p5 press Enter

Partner control port set to p6.
Select the port that will be The command sets the Bandwidth Doubling option for either the primary
used for inter-Quantum or secondary unit. When a Bandwidth Doubling port is configured, an
proprietary Bandwidth IPG is created internally. DP4 and the Bandwidth Doubling port are put
Doubling traffic. into this IPG. This IPG is only used for inter-Quantum proprietary
Bandwidth Doubling traffic.
Sequence:
set bandwidth doubling port [p1 - p8]
Example:
set bandwidth doubling port p1 press Enter
The ipg config will be changed.
Current ipg config:
----- ------- ------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 enable p8,dp4
ipg5 enable p3
ipg_x2 disable
New ipg config:

----- ------- ------------
ipg1 enable p5,dp1
ipg2 enable p6,dp2
ipg3 enable p7,dp3
ipg4 enable p8
ipg5 enable p3
ipg_x2 enable p1,dp4
Countinue? Enter Y(yes) or N(No):Y

Bandwidth doubling port is configured to : p1
Apply the settings (including ipg, lag config changes)
immediately, continue? Enter Y(yes) or N(No):y
Actual bandwidth doubling port is set to p1!
The system responds with a new IPG configuration, in which a dedicated
Bandwidth Doubling IPG (ipg_x2) is enabled and the data
interconnection port and DP4 are added to it.
67
Enable or disable bandwidth This command enables or disables bandwidth doubling. By selecting
doubling. either primary or secondary the feature is enabled. By selecting off the
feature is disabled.
Sequence:
set bandwidth doubling mode [primary|secondary|off]
Example (enables feature and selects the Quantum to be the Primary
unit):
set bandwidth doubling mode primary press Enter
Bandwidth doubling mode is set to : primary
Change requires a 'save mib' and 'reset system'.

Would you like to 'save mib' now? Enter Y(yes) or N (no):Y
A 'reset system' is required for the change to take effect.
Note that both enabling, or disabling, bandwidth doubling requires a
reset system for the change to take effect.
DragonWave Inc.
68
Get the current status of This command returns the current status of the bandwidth doubling
bandwidth doubling feature.
Sequence:
get bandwidth doubling status press Enter
Example with Bandwidth Doubling disabled:
bandwidth doubling mode in MIB :off
actual bandwidth doubling mode :off
bandwidth doubling port in MIB :none
actual bandwidth doubling port :none
Example with the wireless link down:
bandwidth doubling mode in MIB :primary
actual bandwidth doubling mode :primary
bandwidth doubling port in MIB :p8
actual bandwidth doubling port :p8
primary wireless port1 :Down

primary wireless port2 :Down
Secondary_x2 :Down
Note: Proper configuration is primary wireless port synchronized to
remote secondary wireless port.
Example with the wireless link operational:
bandwidth doubling mode in MIB :primary
actual bandwidth doubling mode :primary
bandwidth doubling port in MIB :p8
actual bandwidth doubling port :p8
primary wireless port1 :Synchronized to remote

secondary wireless port1
primary wireless port2 :Synchronized to remote
secondary wireless port2
secondary wireless port1 :Synchronized to remote primary
wireless port1
secondary wireless port2 :Synchronized to remote primary
wireless port2
Note: Proper configuration is primary wireless port synchronized to

remote secondary wireless port.
69
Reset the system This command resets the system and enables all changes.
Sequence:
Would you like to 'save mib' before reset? Enter Y(yes) or N (no):Y
Saving Mib...Mib saved successfully.
Are you sure you want to reset? Enter Y(yes) or N (no):Y

Resetting the system now.
9.4 Cross Polarization Interference Cancellation (XPIC)

XPIC is a DragonWave licensed feature.
There are two versions of XPIC available.
• single channel – one channel per radio
• multi-channel – two channels per radio
Single channel XPIC can be employed with Bandwidth Acceleration and multi-channel XPIC can be
employed with both Bandwidth Acceleration and Bandwidth Doubling. This capability adds more flexibility
for increasing bandwidth, by enabling two co-located radios to use the same radio frequency channel(s).
XPIC is designed to optimize the operation of the Quantum system when a Dual Polarization Radio
Mount (DPRM) is employed to attach two wireless systems to a common antenna, and when the same
frequency channel is employed on both systems. XPIC reduces cross polarization interference caused by
environmental path effects and the finite isolation between the orthogonally-polarized RF signals in the
antenna feeds and possible antenna misalignment.
For it to function successfully, XPIC requires that the IF cable feeding the horizontally polarized radio and
that feeding the vertically polarized radio be both of the same type and that there be no more than 5
metres difference in the cable lengths.
9.4.1 Single Channel XPIC

This version requires a single Quantum unit hardware configured with two modems and two IF output
ports.
When licensed (see Section 3.0), this feature can only be turned on when the system capacity is set to
Dual Modem Multi Radio (option 3) and both wireless ports are configured with the same frequency
channel, thus doubling the channel throughput.
DragonWave Inc.
70
Figure 9-5 Single Channel XPIC
XPIC can be enabled, or disabled, by issuing the CLI command: set xpic [on|off]. This command takes
effect immediately. To view the current status of XPIC, use the CLI command get xpic.
XPIC statistics can be viewed using the CLI command get modem statistics.
Procedure 9-3
Configure Single channel Cross Polarization Interference Cancellation (XPIC)

Configure the Quantum in the usual way, with the exceptions that
system capacity must be set to DualModemMultiRadio (option 3 – set
system capacity 3) and both frequency channels must be the same.
Get the current status of XPIC Returns the current status of XPIC as ON or OFF
Sequence:
get xpic press Enter
XPIC status in Mib: off
Actual XPIC status: off
71
Turn XPIC on This command enables XPIC, provided that:

• it is licensed
• the system capacity is set to “DualModemMulti Radio” (option
3)
• the frequency channel for both radios has been configured
the same.
Sequence:
set xpic on press Enter
XPIC is turned on!
XPIC is set to 'on' in MIB.Save mib before resetting system to
retain the setting.
Turn XPIC off This command disables XPIC.

Sequence:
set xpic off press Enter
XPIC is turned off!
XPIC is set to 'off' in MIB. Save mib before resetting system to
retain the setting.
View XPIC statistics This command returns modem statistics and includes XPIC numbers
provided that XPIC is enabled.
get modem statistics [wireless_port1|wireless_port2]
Note: “get modem statistics” defaults to “wireless_port1” (Modem 1)
Example:
Sequence:
get modem statistics wireless_port2 press Enter
Modem 2 Performance Statistics:
Eb/No :25.04 dB
Equalizer Stress :100
SNR :33.69 dB
Receiver RSL :-43.0 dBm
XPIC Equalizer Stress :14
XPI :-28.11 dBc
Note: XPIC Equalizer Stress (a decimal number) is an indication of the

degree of cross polarization interference caused by weather and/or
antenna isolation/misalignment problems. XPI is the (co-channel)
Cross-Polarization Interference power level, relative to that of the
desired polarization signal, presented as dBc.
DragonWave Inc.
72
9.4.2 Multi-channel XPIC

Quantum radios can operate on two different frequency channels simultaneously, within the selected
radio band. By employing Multi-channel XPIC, and two radios at each end of a link, you can quadruple
the bandwidth of the system, while employing just two different frequency channels. To achieve this, two
Quantum modem systems are needed at each end of the link. The system hardware of each Quantum
must be configured with two modems and two radio ports.
Multi-channel XPIC requires the XPIC and Dual Wireless Ports feature groups to be licensed (see Section
3.0). This feature can only be turned on when licensed and when the system capacity is set to Multi-
carrier XPIC (option 5).
The configuration steps are different to that of the single channel XPIC.
Both local and remote Quantum system pairs must be configured identically, with the exception that, at
each end of the link, one Quantum is configured as the “master” and its partner unit configured as the
“slave”. A “control link” connection is made between master and slave using any available data port
(configurable). This port is termed the “control port”. This allows the master to communicate with the
slave.
The master Quantum is in control of the radios, consequently any radio related commands are performed
on the master Quantum. The radio related commands are:
• set/get radio transmitter state • set/get radio loopback
• set/get transmit power • all ATPC commands
Figure 9-6 Multi-Channel XPIC.

73
Refering to Figure 9-6, radio port 1 (P1) and radio port 2 (P2) of the master unit will both output
frequency channel 1. Radio port 1 (P1) and radio port 2 (P2) of the slave unit will both output frequency
channel 2.
For multi-channel XPIC to work properly, each Quantum has to lock-on to its proper over-the-air peer.
An IF combiner unit is used to combine the outputs from radio port 1 (P1) of both the master and slave
Quantum systems and connect to the first (vertically polarized) radio. Simlilarly, radio port 2 (P2) of each
Quantum are coupled together through a combiner and connected to the second (horizontally plolarized)
radio. This means that both radios (vertically and horizontally polarized) transmit/receive both frequency
channels 1 and 2, but using opposite polarizations (orthogonally polarized).
The IF combiner has one port that passes DC voltage and a second port that blocks DC voltage. This is
to ensure that, at any given time, the radios have only one power feed.
From the user data perspective, there are two deployment scenarios
• use the Quantum on-board switch to split user traffic over the multi-channel XPIC (i.e. use XPIC
with Bandwidth Doubling)
• use external subtending switch to split user traffic (i.e. external switch creates a LAG over two
Ethernet connections to the multi-channel XPIC).
9.4.2.1. Using Multi-channel XPIC with Bandwidth Doubling
In this scenario, the management and data flow are the same as that described for Bandwidth Doubling
(see Section 9.3). The only difference being that, with multi-channel XPIC, the radio signals are
orthogonally polarized RF signals. When configuring multi-channel XPIC with Bandwidth Doubling, there
are no configuration dependencies for these two features. This means that a Bandwidth Doubling primary
unit can be either a multi-channel XPIC master, or slave unit, and vice versa.
9.4.2.2. Using Multi-channel XPIC without Bandwidth Doubling
In this scenario, the subtending switch forms a LAG over the two Ethernet connections. This aggregates
the data feed between the multi-channel XPIC master and slave units. The Ethernet connection (for
example, p5 in Figure 9-7) needs to be put into an IPG with a DP, so user traffic can flow over the air.
Only out-of-band management is supported for this configuration. There are two out-of-band options one
can configure. Figure 9-7 shows one out-of-band option and Figure 9-8 the other. You can use either
management option.
Figure 9-7 Data Feed Using LAG with OOB Management Option 1..
When using OOB option 1 (Figure 9-7), p8 (the partner control interconnection) has to be configured to
be in its own IPG. Also, p3, on both master and slave units, needs to be in its own IPG and configured as
a network management interface.
DragonWave Inc.
74
Figure 9-8 Data Feed Using LAG with OOB Management Option 2.
When using OOB option 2 (Figure 9-8), on the master unit p8 (the partner control interconnection) and
P3 need to be in same IPG, and they both need to be configured as a network management interface. On
the slave unit, p8 needs to be in its own IPG, and it needs to be configured as a network management
interface.
Procedure 9-4
Configure Multi-channel Cross Polarization Interference Cancellation (XPIC)

The following procedure is similar to the basic configuration process described
in Volume 1. However, Multi-channel XPIC requires a different basic
configuration procedure.
Select the correct system Once properly licensed, this command sets the system capacity to that
capacity required for Multi-carrier XPIC to be configured and become operational.
Sequence:
set system capacity 5 press Enter
Programmed system capacity :MultiCarrierXPIC
Don't forget to set programmed frequency for both ports if not set yet.
Would you like to 'save mib' now? Enter Y(yes) or N (no): y
Note: you can wait to “save mib” and “reset system” until all the command
steps have been completed.
75
Select the desired radio band This command allows you to select the desired radio band. A list of available
bands can be displayed by issuing the CLI command get radio band. Note
that the connected radios must be compatible with the band selected.
Sequence:
set radio band <radio band> press Enter
Example: set radio band fcc18_1_50_R5 press Enter
Radio Band selected :fcc18_1_50_R5
Would you like to 'save mib' now? Enter Y(yes) or N (no): n
'save mib' and 'reset system' for the changes to take effect.
Note: we will “save mib” and “reset system”once all further commands have
been input.
Select the required system mode This command allows you to select a suitable system mode. A list of available
system modes is displayed using the command get system mode.The system
mode determines the modulation scheme and the system bandwidth
(throughput).
Sequence:
set system mode <system mode> press Enter
Example: set system mode hx50_358_256qam press Enter
System mode set to: hx50_358_256qam

Would you like to 'save mib' now? Enter Y(yes) or N (no): n
Select the frequency bank to This command allows the user to match the frequency bank to be used
match that of the radio (TxHigh or TxLow) with that of the connected radio. One end of the link will be
set to TxHigh and the other to TxLow. Consequently the matching radios will
be located accordingly.
Sequence:
set frequency bank <txhigh | txlow> press Enter
Example: set frequency bank txlow press Enter
Frequency Bank selected :txlow
Would you like to 'save mib' now? Enter Y(yes) or N (no):
DragonWave Inc.
76
Display the radio frequency The following command allows you to display the frequency channels available
channels available. for the previously selected radio band.
Example:
get frequency bank press Enter
fcc18_1_50_R5
txLow FREQUENCIES(Selected)
Index TX IF RX IF TX RF RX RF
C1 0 0 17765000 19325000
C2 0 0 17815000 19375000
C3 0 0 17865000 19425000
C4 0 0 17915000 19475000
C5 0 0 17965000 19525000
C6 0 0 18015000 19575000
C7 0 0 18065000 19625000
C8 0 0 18115000 19675000
All Frequencies in kHz
Since the frequency bank selected in the previous step was “txlow”, the above
list shows those channels available in the txlow frequency bank. If the txhigh
bank had been selected then the txhigh channels would be displayed.
Select the desired frequency This command allows you to programme the frequency channels for the
channels that will be used for the master and slave units. In the example below, both the IF (radio) ports on the
master and slave units master unit will output frequency channel C1 and both the IF ports on the slave
unit will output channel C4. Quantum units at the far end need to be configured
similarly.
Sequence:
set programmed frequency [Index ID] [master | slave] press Enter
Example: set programmed frequency C1 master press Enter
C1 525000 1725000 17765000 19325000
All Frequencies in kHz.

Would you like to 'save mib' now? Enter Y(yes) or N (no):n
set programmed frequency C4 slave press Enter
C4 675000 1875000 17915000 19475000
All Frequencies in kHz.

Would you like to 'save mib' now? Enter Y(yes) or N (no):n
77
Select the control port that will be This command allows the user to select a GigE data port that can be used as
used for the control link.between the control port. The master unit is connected to the slave unit via this port.
master and slave. The master and slave units do not have to use the same port number. The
control port allows communication (including OOB management) to take place
between the two systems.
Sequence:
set partner [none | p1-p8] press Enter
Example: set partner p8 press Enter
Select the Quantum that will be This command allows the user to select which of the two Quantum units is to
the “master” and the one to be be the master and which is to be the slave.
the “slave”.
Sequence:
set xpic mode [master | slave] press Enter
Example (on the Quantum designated to be the master):
set xpic mode master press Enter
XPIC mode in Mib: Master
Example (on the Quantum designated to be the slave):
set xpic mode slave press Enter
XPIC mode in Mib: Slave
Turn XPIC on This command enables or disables XPIC.

Sequence:
set xpic [on | off] press Enter
Example: set xpic on press Enter
XPIC is turned on!
XPIC is set to 'on' in MIB.Save mib before resetting system to retain

the setting.
DragonWave Inc.
78
View the status of XPIC This command returns the system status of XPIC.
Sequence:
get xpic press Enter
XPIC mode in Mib: Master
Save the management Saves the MIB to RAM. Perform this command to save setting changes to
information base (mib) non-volatile memory.
Sequence:
Reset the system (traffic A system reset is required to activate Multi-channel XPIC.
affecting).
Sequence
press Y
The system will proceed to reset. You will have to log on again to regain
access.
Note that Multi-band XPIC can work with Bandwidth Doubling. Each feature is configured independently
and operates independently of each other.
79

10.0 Quality of Service (QoS)
QoS implementation is best done on the ingress and egress portions of the transport network. As such,
QoS should be implemented on the Ethernet switches. Once that implementation is in place, the Horizon
Quantum can be configured for QoS, should the potential for congestion exist.
10.1 Class of Service Types

Enabling QoS on Horizon Quantum (set qos [on|off]) ensures that incoming packets are handled with a
priority based on the Class of Service (CoS) bits embedded in several types of data packet. Either VLAN
(802.1p) packets, Super VLAN (Q-in-Q, or double tagged) packets, or the DSCP field in IP packet
headers can be selected.
For Super VLAN (or Q-in-Q) packets, since a standard VLAN packet is encapsulated within the Super
VLAN packet, there may be two sets of CoS bits associated with the Super VLAN packet. One will be the
CoS bits of the encapsulated, or inner, VLAN frame (usually associated with the “customer”) and the
other will be the CoS bits of the Super VLAN packet itself, or outer, header (usually associated with the
“service provider”).
The Horizon Quantum can be configured to use the CoS bits of either, Super VLAN inner
(cos_qinq_itag), or outer (cos_qinq_otag), packets, or the CoS bits of the standard VLAN, or DSCP bits.
To determine the type of packets on which you wish the packet filter to operate you need to configure the
CoS type (set cos type [cos_vlan|cos_qinq_itag|cos_qinq_otag|cos_dscp])
10.2 Class of Service Levels

The CoS bits have a numeric value ranging from 0 to 7, giving eight CoS levels. Network administrators
can allocate CoS levels to data packets in order to prioritize the types of traffic. The higher the level, the
higher the priority of the packet. For example, video, or VoIP traffic needs to be handled with minimal
delay, whereas simple data traffic can tolerate delays in getting to its destination. For this example the
video or VoIP packets will be allocated a higher CoS level than that of the data traffic. This signals other
network elements to handle the packets with the priority that the CoS levels dictate.
10.3 Quality of Service (QoS) Queues

There are four QoS Queues within Horizon Quantum, numbered Q1 to Q4, with Q4 having the highest
priority. These queues are used to process user traffic. Any of the eight CoS levels can be assigned to
any of the four QoS Queues. A packet filter directs frames to the assigned QoS queue based on the CoS
level of that packet (set cos queue mapping [mapping]).
Example: CoS levels 6 and 7 could be directed to Q4
CoS levels 4 and 5 directed to Q3
Any arriving packet not having a CoS level assigned to it can be classified at a level (0 – 7) based on the
configured default CoS value (set cos default value [0 though 7).
Once queues are populated with packets, a “scheduler” is responsible for moving queued packets out of
the queues in a specific order. The scheduling policy decides the behavior of the scheduler.
10.4 Operation with QoS Disabled

If QoS is disabled in the Horizon Quantum system, all incoming user data packets are treated equally and
are forwarded on a first-come first-served basis. The system operates on a first-in-first-out (FIFO) basis.
Quality of Service (QoS)
81
If the Pause Frames feature is enabled, pause frames will be sent to the connected switch when the input
buffer is close to being full (internally set threshold). This allows time for the queue to empty prior to more
frames being received and thus avoids congestion.
When QoS is enabled, the pause frame feature is not available.
By default, control frames, or slow bridge protocol packets, are always directed to a high priority queue,
QC, ensuring that this type of traffic always has the highest priority compared with that of user data traffic.
10.5 Operation with QoS Enabled

In Horizon Quantum, when QoS is enabled, a packet filter directs user data packets to any one of four
QoS queues based on the CoS (priority) levels assigned to each packet. The four QoS queues are
labeled Q1 to Q4.
Slow bridge protocol frames, by default, are directed to a fifth queue labeled QC, however, if QoS is
enabled, these frames can be directed to any one of the four QoS queues, or QC. (set cos control flow
mapping [on/off][Q1 Q2 Q3 Q4 or QC])
Queues Q1 to Q4 can also be allocated a committed Information Rate (CIR) and a committed burst size
(CBS).
Traffic statistics for each queue (Q1 to Q4 and QC) can be viewed using get traffic statistics. For details
of where in the system traffic statistics are measured see Volume 1, Section 11.1.
10.5.1 Slow Bridge Protocol Traffic

Slow bridge protocol frames are those that are destined for the 01-80-C2-00-00-xx MAC addresses.
Examples: STP, RSTP, MSTP LACP, Pause Frames, GARP (GMRP,GVRP), bridge broadcasts, OAM,
LLDP, Port based authentication, are all transmitted in an expedited fashion.
By default, slow bridge protocol packets are handled by a separate buffer, or queue, named QC. QC is
the highest priority queue in the system and it ensures slow bridge protocol packets are passed at the
highest priority.
However, when QoS is enabled, Quantum can also be configured to direct slow bridge protocol packets
to any one of the four QoS queues, or to QC, allowing the user to control the priority of slow bridge
protocol packets. This feature is called Class of Service Control Flow Mapping. If this feature is not
configured, then slow bridge protocol packets are directed only to QC, regardless of the status of QoS.
Similarly, when QoS is enabled, Quantum can be configured to direct ECFM frames arriving over the
network (not generated on the node) to any one of the four QoS queues, or to QC, allowing the user to
control the priority of the ECFM frames. This feature is called Class of Service ECFM Flow Mapping. This
feature does not work if QoS is turned off. Note that this feature is overridden if the ECFM feature on the
node is enabled. All ECFM frames would then be directed to the CPU.
Other frames, such as “keep-alive” frames and MRP frames, that the user determines must be treated
with a desired priority, must be assigned a CoS within a connected switch, then assigned to the
appropriate QoS queue within Horizon Quantum. Note that user data traffic can never be directed to QC.
10.5.2 Committed Information Rate (CIR)

The Horizon Quantum system allows the user to assign a percentage of the maximum bandwidth
available to the data in each of the four QoS queues (set cos queue cir [0-100,0-100,0-100,1-100]). The
default is 25% for each queue. Its purpose is to ensure that each queue gets at least a portion of the
bandwidth and does not get “starved” of bandwidth resulting in no bandwidth being allocated.
The behavior of the CIR is different for the two scheduling policies (Priority Queuing or Weighted Fair
Queuing - see Section 10.6). For the priority queuing policy, with expedite disabled, the sum of the CIR
for all queues adds up to 100% of the system bandwidth. With expedite on, any queue can be
DragonWave Inc.
82
oversubscribed to 100% of the wireless bandwidth. The selection of the appropriate scheme is
dependent on the application.
10.5.3 Committed Burst Size (CBS)

Since IP traffic is “bursty” by nature, the Horizon Quantum provides a feature, called QoS queue
Committed Burst Size (CBS), to handle Ethernet bursts. The Horizon Quantum system contains a data
buffer that is used to accommodate bursts of traffic in excess of the user allocated amount as specified
through the CIR setting for each queue.
The CBS defines the portion of the total amount of burst buffer available that is allocated to each queue.
At GigE rate, there is a total of 100 mS (16 MB) of buffer allocated to QoS queues. Each queue can be
allocated a percentage of this memory (set cos queue cbs [0-100,0-100,0-100,1-100]). The default
allocation for all four QoS queues is 25%. The total percentage assigned to all queues must equal 100%.
If ECFM flow mapping, or control flow mapping, is enabled, then QC can also be allocated a percentage
of available CBS, bringing the default value of CBS for the five queues to 20%.
The CBS function will “smooth out” the output and transmit at the CIR of the queue by flushing the burst
buffer allocation. Note that the CIR of QC is preset and not user adjustable.
The CBS operates as a FIFO for each individual queue. Burst traffic will be buffered into the queue as it
arrives. This may have the effect of creating a short delay for subsequent traffic arriving at that queue if
the subsequent traffic is at the CIR level of that queue. Conversely, if the burst is followed by traffic that
is less than the CIR level, then no delay should occur provided the scheduling of this queue is not
interrupted by the higher priority traffic.
For example: Q3 has 25% CIR or 25 Mbps on a 100 Mbps link. The Q3 CBS is set to 25% or ~25 mS at
GigE rate. If Q3 receives a burst of traffic in excess of 25 Mbps then Q3 would continue to transmit at 25
Mbps until the “burst buffer” is empty, regardless of whether or not the traffic source is sending packets. If
the traffic source continues to send packets, then the original 25 Mbps is transmitted, followed by the
“burst buffer” traffic, followed by new incoming packets.
10.5.4 Cut-through
Enabling the Cut-through feature on a queue reduces the amount of packet delay variation that packets
flowing through that queue will be subject to as they are transferred across the Horizon Quantum radio
link.
If a packet arrives in the Cut-through queue while a packet is being forwarded over the air from a non
Cut-through queue, then transmission of the packet from the non Cut-through queue is suspended at the
start of the next modem block and the packet from the Cut-through Queue is sent. After transmission of
the packet from the Cut-through queue is complete, the packet from the queue that was suspended (i.e.
being cut-through) is resumed. For example, if a packet is currently being transmitted from Q3 and a
packet arrives on Q4 (and Cut-through is enabled on Q4) then the packet from Q4 will interrupt the
transmission of the packet currently being transmitted from Q3.
In Strict Priority Queuing mode only Q4 may be selected as a cut-through queue.
In Weighted Fair Queuing, Cut-through may only be enabled when Expedite Mode is enabled on Q4.
Enabling Cut-through on a queue does not have any affect on the assignment of bandwidth (rate) to that
queue by the QoS engine.
83
10.6 QoS Scheduler Policies

A scheduler services all the queues, Q1, Q2, Q3, Q4 and also QC. Each of the four queues, Q1 to Q4, is
serviced by a scheduler in a manner dependant on one of two selectable queuing policies (set qos
policy [strict_priority | wfq]).
These policies are:
• Priority Queuing
• Weighted Fair Queuing
Regardless of the policy used, QC always gets serviced first.
10.6.1 Priority Queuing

If the Priority Queuing policy is enabled in the Horizon Quantum system, the scheduling mechanism can
be described as follows:
1. Select the highest priority queue (Q1 to Q4 only) which has a frame in it, and hasn’t used up its
CIR budget
2. Send that frame
The priority queues are serviced by the scheduler always in the order Q4, Q3, Q2, Q1 with Q4 always
being polled first out of the four queues. Note QC, the fifth queue, will always be serviced first.
The operation of the Scheduler is affected by both the user-configurable CIR and CBS settings as
described above. In the priority queuing mode, with the expedite option disabled, the CIR of all four
queues must add up to 100% of the system speed (system current speed). When the expedite option is
enabled, the user is allowed to oversubscribe the CIR of any queue up to 100% of the current speed.
Note that the CIR of QC cannot be controlled by the user.
Priority Queuing - Expedite Queues

With the priority queuing policy, the expedite queuing mechanism allows the user to oversubscribe the
CIR of any queue to 100% of the system current speed. With this feature the higher priority queues can
use the excess bandwidth when required. When the higher priority queues do not need their full allocated
CIR, the lower priority queues can use the leftover bandwidth up to their assigned CIR. This allows better
bandwidth utilization under dynamic loading conditions. However, it is important to note that
oversubscribed higher priority queues can starve the lower priority queues of bandwidth.
Once the set cos expedite queue on command has been issued the user can assign the CIR for any
Queue to 100%. Each of the four queues can be assigned a CIR of 100%. The sum of the CIRs can now
be greater than 100%, up to a maximum of 400% (4 queues). A total CIR of 400% means each one can
use 100% of the bandwidth if it is available. It does not mean that the Horizon Quantum system can
achieve 400% of the Horizon Quantum maximum bandwidth, simply that if any bandwidth is
available after a previous queue has been serviced, the next queue in line will be given full access
to the remaining bandwidth until fully serviced. IF Expedite Queuing is turned OFF, then the sum of
all the CIRs cannot exceed 100%.
As network services increase, the need for multiple priority queues becomes evident. A network
administrator may require three Expedite Queues and decide to send all network routing protocols
through the highest priority queue; send IP Voice through the next highest priority queue; send Video over
IP through the next highest priority queue and send all other traffic to the remaining queue, which can be
oversubscribed to utilize the unused bandwidth.
DragonWave Inc.
84
Example 1: Queues configured with the following settings :

• Q4 = 100%
• Q3 = 100%
• Q2 = 75%
• Q1 = 25%
In this example, voice traffic could be assigned to Q4, IPTV could be assigned to Q3, Database
transfers assigned to Q2, and Internet traffic assigned to Q1
Q4 is serviced as a priority queue until empty
Q3 is serviced as a priority queue until empty or until Q4 receives packets
If neither Q4 nor Q3 have packets, service Q2 until empty or CIR limit is met, or until Q4 or Q3
packets arrive
Service Q1 when no other packets exist in Q4, Q3, Q2 or Q2 has met CIR and Q1 CIR limit has not
been met
Example 2: Assuming that the total bandwidth available is 200Mbps, if the Expedite Queue is “ON” and
the CIR for the remaining queues are set to:
• Q4 = 100%
• Q3 = 100%
• Q2 = 0%
• Q1 = 0%
In this scenario, with Expedite Queue “on” and Q4 set to 100%, Q4 will be given priority access to the
full bandwidth available on the link.
Once the throughput requirements of Q4 have been satisfied, 100% of any remaining bandwidth will
be given to Q3.
Note that in this example traffic assigned to Q1 or Q2 will not be transmitted due to them being set to
0% CIR.
A representative drawing of the Priority Queuing QoS components and functional blocks is shown in
Figure 10-1.
85
Figure 10-1 CoS Queues can be allocated a CIR and a Committed Burst Size (CBS).
DragonWave Inc.
86
10.6.2 Weighted Fair Queuing (WFQ)

Priority Queuing scheduling has the drawback of wasting bandwidth when any of the queues’ bandwidth
requirements are below the set CIR for that queue. Any unused bandwidth allocated to a queue cannot
be redistributed to the other queues. Also, there is a possibility of starving the lower priority queues when
the higher priority queues are over subscribed. WFQ helps in solving these problems.
In WFQ, each of the queues are assigned a weight. Any unused bandwidth of the system is distributed
among the queues proportional to their assigned weights. Each queue is also assigned a CIR which
guarantees the minimum bandwidth for the traffic in that queue when congestion occurs. Note that the
sum of all CIRs must not exceed 100%, but can be less if desired. When a queue meets its CIR, it is
serviced only when bandwidth is not consumed by the other queues which have not met their CIR.
See Figure 10-2 for a graphical representation of the above statements.
Figure 10-2 Weighted Fair Queuing Concept.
The user sets the CIR and the weight (set cos wfq weight [w1 w2 w3 w4] for each queue and the
scheduler processes each queue based on those parameters. One expedite queue can also be
configured.
The queues are serviced in a round-robin fashion (in order Q4, Q3, Q2, Q1) except for the expedite
queue (if enabled) which is serviced with highest priority.
Any queue can utilize any excess bandwidth, proportional to its assigned weight, provided all queues with
pending packets have their CIR met.
When all the queues meet their CIR, the remaining bandwidth is distributed amongst the queues,
proportional to their weights.
87
Example:
Each queue, Q1 to Q4, is configured with a weight of w1, w2, w3 and w4 respectively. Assuming
a total bandwidth capability of 200 Mbps (system current speed), and the CIR for each queue is
set to 10% (20 Mbps), this means that there is a surplus bandwidth of 200 – 80 = 120 Mbps if all
queues are meeting their CIR. This surplus bandwidth is made available to all queues in a
proportion determined by the weight assigned to each queue.
The surplus bandwidth share of queues Q1 to Q4 shall be:
Q1 = 120 * w1 / (w1+w2+w3+w4)
Q2 = 120 * w2 / (w1+w2+w3+w4)
Q3 = 120 * w3 / (w1+w2+w3+w4)
Q4 = 120 * w4 / (w1+w2+w3+w4)
If Q1 does not have any traffic at a given time then the surplus bandwidth will increase to 120 +
20 = 140 Mbps. The surplus bandwidth share will now be distributed amongst the remaining
queues as follows:
Q2 = 140 * w2 / (w2+w3+w4)
Q3 = 140 * w3 / (w2+w3+w4)
Q4 = 140 * w4 / (w2+w3+w4)
The benefits of WFQ include :
• the queues are serviced in a fair way
• bandwidth is not wasted when system is not congested.
• CIR to queues is guaranteed.
• The expedite queue, if enabled, will have the highest scheduling priority until the CIR
is met.
The peak information rate (PIR) of each WFQ queue is the same as the configured system current speed.
Weighted Fair Queuing – Expedite Queue

In the WFQ policy, only one queue can be configured as the expedite queue. This is achieved by
assigning the desired queue with a weight of zero (0) (set cos wfq weight [w1 w2 w3 w4]) and enabling
the expedite function (set cos expedite queue [on|off]). The traffic directed to the expedite queue will
now be given priority up to its assigned CIR, but the expedite queue will not be able to access any
available surplus bandwidth in the system. This will be shared by the remaining three queues based on
their weighting values.
DragonWave Inc.
88
Procedure 10-1
Enable Quality of Service
Perform this procedure to enable Quality of Service for the Horizon Quantum.
Note: To perform this procedure, you must have either SuperUser or NOC user rights.
login Log in as a SuperUser or NOC user.
Enable Quality of Service

Enables or disables (on or off) quality of service (QoS) on the Horizon
Quantum system. QoS is part of the 802.1P specification.
Sequence:
set qos [on|off] press Enter
where on will enable QoS and off will disable QoS
qos is : [on/off]
get qos press Enter
qos is [on/off]
If desired enable ECFM flow
mapping. Enables the system to direct ecfm frames arriving from the network
(not originating on the node) to either one of the four QoS queues or to
QC. Note that this feature does not work if QoS is turned off.
Sequence:
set cos ecfm flow mapping [on/off][queue_id] press Enter
where queue_id is any queue Q1, Q2, Q3, Q4 or QC
CoS ECFM flow mapping is mapped to [Q1, Q2, Q3, Q4, QC]
get cos flow mapping press Enter
Cos Control flow mapping is OFF
Cos ECFM flow is mapped to [Q1, Q2, Q3, Q4, QC]
Enable control flow mapping if

desired Enables the system to direct control frames (slow bridge protocol
packets) to either one of the four QoS queues or to QC.
Sequence:
set cos control flow mapping [on/off][queue_id] press Enter
where queue_id is any queue Q1, Q2, Q3, Q4 or QC
CoS control flow mapping is mapped to [Q1, Q2, Q3, Q4, QC]
get cos flow mapping press Enter
Cos Control flow is mapped to [Q1, Q2, Q3, Q4, QC]
Cos ECFM flow is mapped to [Q1, Q2, Q3, Q4, QC]
89
Select the priority bits type to

use Sets the QoS system to use priority bits provided by standard VLAN
frames, Super VLAN (Q-in-Q) inner or outer tags, or dscp priority bits.
Sequence:
set cos type
[cos_vlan/cos_qinq_itag/cos_qinq_otag/cos_dscp] press Enter
CoS type is set to :
cos_vlan/cos_qinq_itag/cos_qinq_otag/cos_dscp
Note: cos_vlan uses the priority tag of standard VLAN frames
cos_qinq_itag uses the inner priority tag of a Q-in-Q frame
cos_qinq_otag uses the outer priority tag of a Q-in-Q frame
cos_dscp uses the 3 bit priority information in the DSCP field
of the IP header (also referred to as ToS).
get cos type press Enter

Cos type is : cos_vlan.
Available cos types in the system are :
cos_vlan cos_qinq_itag cos_qinq_otag cos_dscp cos_mplsexp.
DragonWave Inc.
90
Assign the CoS priority bits to Assigns each of the incoming 802.1P CoS levels to either of the four
a queue Horizon Quantum QoS Queues. The Horizon Quantum system
supports all eight 802.1P CoS levels (0-7).
Sequence:
set cos queue mapping [x x x x x x x x ] press Enter
where each x is a value of either 1, 2, 3 or 4 representing the
Horizon Quantum QoS Queues allocated to each of the 801.1P CoS
levels (0-7) in order. Any values not explicitly assigned by the user
will not be affected by the command.
dot1p Queue assignment is as follows :
dot1p value CoSQueue
----------- -- ---------
0 [x]
1 [x]
2 [x]
3 [x]
4 [x]
5 [x]
6 [x]
7 [x]
Where [x] is a value of either 1, 2, 3 or 4
Examples:
set cos queue mapping [1 1 2 2 3 3 3 4 ] press Enter
will allocate 802.1P CoS levels 0-1 to Horizon Quantum QoS Queue
1, CoS levels 2-3 to Horizon Quantum QoS Queue 2 CoS levels 4-
6. to Horizon Quantum QoS Queue 3 and CoS level 7 to Horizon
Quantum QoS Queue 4. Note that there is a space between each of
the digits in the command.
cos queue assignment is as follows :
dot1p value CoSQueue
----------- -- ---------
0 1
1 1
2 2
3 2
4 3
5 3
6 3
7 4
91
Select the QoS policy

Selects the Priority Queuing or Weighted Fair Queuing policy.
Sequence:
set qos policy [strict_priority | wfq] press Enter
where strict_priority selects Prority Queuing and wfg selects
Weighted Fair Queuing.
Qos is set to : [strict_priority | wfq]
**Priority Queuing Only** Sets the Committed Information Rate (CIR) for each of the 4 QoS
queues. The CIR defines the minimum amount of bandwidth allocated
Set the queue CIR and
for that queue. Note that queues set as Expedite Queues can override
allocate expedite queues if
the CIR for other queues should congestion occur.
required
Sequence:
set cos queue cir [%1 %2 %3 %4] press Enter
where %1 %2 %3 %4 is the percentage of the available bandwidth to
be allocated to QoS queues 1 through 4 respectively. The total cannot
exceed 100% unless Expedite Queuing has been enabled.
The system responds: (example shown using 25% settings for each
queue - default)
Expedite queue is :off.
All queues bandwidth are guaranteed.
Queue CIR(%) CIR(Mbps)
1 25 25
2 25 25
3 25 25
4 25 25
If Expedite Queuing has been enabled, then each queue that has been
configured for 100% CIR is treated as an Expedite Queue.
Sequence:
set cos queue cir 25 100 25 100
Expedite queue is :on
Bandwidth for higher priority queues are guaranteed over
lower priority queues
1 25 25
2 100 Full
3 25 25
4 100 Full
“Full” indicates that the queue is oversubscribed and can consume the
full remaining bandwidth over lower priority queues.
DragonWave Inc.
92
**For Weighted Fair Sets the Committed Information Rate (CIR) for each of the 4 QoS
Queuing Only** queues. The CIR defines the minimum amount of bandwidth allocated
for that queue.
Set the queue CIR
Sequence:
set cos queue cir [%1 %2 %3 %4] press Enter
where %1 %2 %3 %4 is the percentage of the available bandwidth to
be allocated to CoS Queues 1 through 4 respectively. The total
cannot exceed 100% , but can be less than 100% if desired.
The system responds: (example shown using 25% settings for each
queue - default)
Expedite queue is :off.
All queues bandwidth are guaranteed.
1 25 25
2 25 25
3 25 25
4 25 25
**For Weighted Fair Applies weights to each of the four priority queues. The higher the
Queuing Only** weighting value, the greater the share of surplus bandwidth is
allocated to that queue.
If wfq policy is selected, then Sequence:
apply weights to each queue
set cos wfq weight [w1 w2 w3 w4] press Enter
and allocate an expedite
queue if required. where w1 is the weighting for QoS queue 1, w2 is the weighting for
QoS queue 2, w3 is the weighting for QoS queue 3 and w4 is the
weighting for QoS queue 4 and all are integers. Note that the sum of
all weights must equal 16. Valid weight values 0 – 15.
Example w1= 1, w2 = 3, w3 = 5, w4 = 7.
The system responds (using the example values shown above):
Queue Weight
1 1
2 3
3 5
4 7
If an expedite queue is required, only queue 4 can be configured as an
expedite queue. Q4 is configured as an expedite queue when its
weight is set to zero (0).
Example w1= 2, w2 = 6, w3 = 8, w4 = 0
Note that the sum of all weights must still equal 16
93
**For Weighted Fair Enables or disables the expedite queue function. See section 10.6.1.
Queuing Only**
Note: Only one queue (Q4) can be assigned in this release.
Enable the expedite queue
Sequence:
function
set cos expedite queue {on {number of expedite queue (1-4)} |
off} press Enter
Expedite queue is :on/off
**For Weighted Fair This command returns the current status of the cut through feature.
Queuing Only**
Sequence:
View the current status of the
get cos cut through queue press Enter
cut through queue
**For Weighted Fair This command enables or disables the Cut-through queue feature.
Queuing Only** The expedite function must be enabled before this command can be
applied. The queue name must be any one of the configured expedite
Enable the Cut Through
queues Q1 to Q4.
queue as desired
Note: Only Q4 can be assigned in this release.
Sequence:
set cos cut through queue {on {queue name (q1 - q4)} | off }
press Enter
Cut through processing is on in Hardware.
DragonWave Inc.
94
Set the committed burst size Sets the committed burst size for each of the four QoS queues (and
for each queue QC if ecfm or control flow mapping is enabled**), as a percentage of
the total queue memory available. There is a total of 100 msec worth
(16MB) of memory space allocated to QoS queues. A percentage of
this space is allocated to each of the four queues (or five queues (QC)
if ecfm or control flow mapping is enabled **).
Sequence:
set cos queue cbs [%1 %2 %3 %4 %C**] press Enter
where %1 %2 %3 %4 %C**is the percentage of the total queue
memory to be allocated to QoS Queues 1 through 4 (and C**)
respectively. Note that the total of all queues must not exceed 100%
Queue Size (%)
1 %1
2 %2
3 %3
4 %4
C** %C**
Example:
get cos queue cbs press Enter
The system responds (default values shown):
Queue Size (%)
1 25 (20**)
2 25 (20**)
3 25 (20**)
4 25 (20**)
C (20**)
set cos queue cbs 10 20 30 40 press Enter
Queue Size (%)
1 10
2 20
3 30
4 40
set cos queue cbs 10 15 20 25 30** press Enter
Queue Size (%)
1 10
2 15
3 20
4 25
C 30
** = ecfm or control flow mapping enabled

95
set the default CoS level for Assigns packets that do not have CoS levels to any one of the eight
packets not having a level 802.1p CoS levels (0-7).
already assigned.
Sequence:
set cos default value [n] press Enter
where “n” is any number 0 through 7.
Packets without VLAN tag are treated as 802.1p priority: n
Sequence:


Sequence
press Y
regain access.
This concludes the steps to configuring Quality of Service using the CLI manager.
DragonWave Inc.
96

11.0 Adaptive Transmit Power Control (ATPC)
Adaptive Transmit Power Control (ATPC) allows a Horizon Quantum system to adjust its transmit power
to compensate for far end signal loss caused by changes in atmospheric conditions e.g. heavy rain.
Note: ATPC and HAAM cannot be enabled at the same time.
ATPC and HSB cannot be enabled at the same time.
ATPC maintains the far end RSL at a target value (target RSL depends on the configured system mode)
and adjusts the near end transmit power by up to 20dB (depends on level of transmit power set), as
necessary, in order to maintain the specific RSL value during fade conditions.
Example:
Scenario – Horizon Quantum system A at one end of a link and Horizon Quantum system B at the other
end of the link.
With ATPC disabled, the RSL of system A is -35 dBm and the RSL of system B is -33 dBm, with a target
RSL of -50 dBm (this value will depend on the configured system mode). The transmit power of A is
configured at 10 dBm and the transmit power of B is configured at 8 dBm. Turn ATPC on at both ends
and the RSL of both A and B should be -50 dBm, with the transmit power of A and B both adjusted by the
system to -7dBm. As the conditions across the link change (attenuation in the link is added/removed), the
transmit power of A and B will adjust accordingly to meet the target RSL.
The Horizon Quantum system is able to discriminate between RSL levels that are reduced as a result of
interference and those as a result of genuine path loss, so that ATPC is not invoked unnecessarily.
ATPC provides several potential advantages, compared with a fixed transmit power system. These are:
• less transmitter power consumption
• longer power amplifier component life
• reduced interference into other wireless systems
Some jurisdictions require the use of ATPC so that power levels are kept as low as possible (reduced
possibility of interference to other systems) when wireless communication conditions are good.
ATPC is enabled or disabled by issuing the CLI command set atpc [on/off] The current status of ATPC
can be determined by using the CLI command get atpc status.
Note that using the CLI command get transmit power, will return the adjusted transmit power and not the
value originally configured using the set transmit power command (usually set at the maximum power
for the system by default).
11.1 Coordinated Power

When ATPC is to be used, if it can be shown by the user that the maximum power of the system would be
applied only on infrequent occasions, then some jurisdictions will allow a lower power level to be used in
the calculations that determine interference criteria. This offers some advantage to the installation. This
lower power is termed the “coordinated power”. The DragonWave ATPC feature supports a coordinated
power parameter.
When ATPC is enabled, if conditions result in the maximum configured transmit power being applied, this
power level will be maintained for a period of no greater than five minutes, after which ATPC will be
disabled and the system will reduce the transmit power to the coordinated power level. The assumption
here is that if the maximum power is required for more than five minutes, a fault condition likely exists,
which should be addressed. The CLI alarm “ATPC auto-disabled (transmitting at coordinated power)” will
be issued along with corresponding SNMP and Web page alarms. Once this alarm has been issued and
the cause determined and corrected, the system power will need to be re-configured and ATPC re-
enabled to return to the previous status.
DragonWave Inc.
98
See the following procedure for ATPC configuration details.
Procedure 11-1
Configure Horizon Quantum Adaptive Transmit Power Control

get atpc status Returns the current status of the atpc
Sequence:
get atpc status press Enter
System responds:
Atpc configuration local: off Peer: off
Atpc status: Disabled-manual
Rsl threshold:-62.0 dBm
Maximum attenuation change: 0.0 dBm
Last written attenuation: 0 dBm
set atpc parameters Sets the fade step and the hysteresis for atpc to operate.
Sequence:
set atpc parameters [fade step] [hysteresis] press Enter
System responds:
Note: the maximum power change allowed is calculated based on the
following:
max change = 20 – (max allowed Tx power – actual set Tx power)
set atpc Enables or disables atpc.

Sequence:
set atpc [on/off] press Enter
System responds:
Atpc is [on/off]
Adaptive Transmit Power Control (ATPC)
99
Coordinated power This command enables the coordinated power feature.

Sequence:
set atpc coordinatedpower [on/off][offset] press Enter
Where [offset] is the difference between the configured transmit
power and the required coordinated power.
Example:
set atpc coordinatedpower on 5
System responds:
Coordinated power configuration local: on Peer:off
Coordinated power offset: 5.0 dBm
Sequence:

This concludes the steps to setting atpc.

DragonWave Inc.
100

12.0 Over-the-air System Authentication
This feature is only necessary if you wish to restrict communication from a Horizon Quantum unit to a
specific peer or to a group of Horizon Quantum units. Authentication is generally used as a security
measure. It is not recommended to enable Authentication prior to alignment of the radios.
Authentication restricts a Horizon Quantum unit from communicating with other Horizon Quantum units
unless the other units match an authentication string. There are three types of authentication:
1. No Authentication
2. Unique Authentication
3. Group Authentication
A new Horizon Quantum system inline with the signal cannot authenticate and receive data if another
Horizon Quantum system is already authenticated. The system authenticates its peer(s) at an interval of
approximately five seconds.
The Horizon Quantum system does not accept data from other manufacturers’ systems.
12.1 No Authentication
No Authentication is the default mode of operation for Horizon Quantum. The Horizon Quantum does not
attempt to create a dialogue or establish authentication between Horizon Quantum nodes. For No
Authentication Mode, setting the failure condition has no effect since there is no dialogue or
authentication between Horizon Quantum systems. Any other Horizon Quantum node transmitting on
exactly the same frequency can send Ethernet data to the corresponding Horizon Quantum node. The
Horizon Quantum only accepts data from other Horizon Quantum nodes that:
a. are transmitting on the same frequency;
b. are properly aligned in polarity; and
c. have adequate signal strength.
The Horizon Quantum system does not accept data from any other manufacturers’ products.
12.2 Unique Authentication

Unique authentication establishes a dialogue between two Horizon Quantum nodes. Unique
authentication is used in a point-to-point configuration where two Horizon Quantum systems
communicate only with each other and not any additional Horizon Quantum systems. Once Unique
Authentication is set, the Horizon Quantum only accepts Ethernet data from its peer. It ignores all other
sources of traffic arriving over the airwaves. Each node is programmed with its peer’s identification
number. Use CLI command get hw inventory. The Unit Serial Number is the identification number to be
used. The identification number corresponds to the Unit Serial Number of the peer node. For example,
endpoint A has a Unit Serial Number ‘1234’ and endpoint B has Unit Serial Number ‘5678’. The peer
identifier for endpoint B is ‘1234’ (serial number of its peer) and the peer identifier for endpoint A is ‘5678’
(serial number of its peer).
When you select Unique Authentication, you must set the authentication failure action.
12.3 Group Authentication

Group authentication is used when more than two Horizon Quantum nodes communicate with each other
and are contained within a geographical area under the control of a service provider or enterprise. The
advantage of using Group Authentication for a group of Horizon Quantum nodes is that only traffic
destined for that particular network is accepted.
DragonWave Inc.
102
A group of Horizon Quantum nodes uses a group ID to establish inter-node communication.

Administrators create a group ID string consisting of up to eight characters. You must program the group
ID string on each node. The group ID string can consist of the characters 0 to 9, a to z, and A to Z. Illegal
characters that cannot be used are {! @ # $ % ^ &* (,) ; : ’ ” + - ~}.
12.4 Authentication Polling

When authentication is enabled, the system attempts to communicate (poll) a specified Horizon Quantum
node every five seconds to re-authenticate the node. If the Authentication Mode is set to NONE, the
system does not attempt to authenticate.
When the corresponding nodes complete the authentication dialogue, the Horizon Quantum reverts to
normal operation. Once the corresponding nodes respond, authentication is re-established, operation
reverts to normal, and any failure action reverts to normal.
The system reports an authentication failure if 24 polls receive no positive response. This means that
there must be an authentication failure for approximately two consecutive minutes before the system
determines there is a failure and reports it. An authentication failure is not necessarily an indication of a
failed transmission issue. There are other alarms for issues with the transmission path such as loss of
signal or loss of Ethernet traffic.
12.5 Authentication Failure Action

If authentication fails, you can specify how the Horizon Quantum system responds:
• allow Ethernet traffic to continue to flow and do not raise an alarm , i.e., does nothing.
• allow Ethernet traffic to continue to flow, but raise an alarm.
• block the flow of Ethernet traffic.
Note: Authentication takes place out–of–band.
12.6 Configure Authentication

Should you require more security than that offered by the default authentication mode of “No
Authentication”, you will need to configure the authentication key to suit your requirements. Follow the
steps in the following procedure.
Procedure 12-1
Setting Unique Authentication
Perform this procedure to set system authentication to unique.
Note: You must perform the authentication procedures in the sequence that they appear in this manual.
login Log in as a NOC user on both ends of the system and run the CLI
command get hw inventory as shown below, to retrieve the
authentication keys from each unit.
System Authentication
103
get hw inventory Displays the serial numbers of the various sections in the system.
Perform this command at each end of the link and record the
authentication keys (Unit Serial Number) for each end.
Sequence:
get hw inventory press Enter

Frequency File PartNumber :VDD-67-00nnnn-01-01
System MAC address :00-07-58-02-91-C4
Unit Serial Number :TBD
Unit Assembly Number :60-000471-02
CCA Serial Number :A1178487H090029

CCA Part Number :61-000235-01-01
Radio Serial Number :G

Radio Hardware ID :28979
Radio Hardware Unit Type :R4
set air interface authentication Sets the authentication type. This needs to be set to unique.
type The default type is none.
Sequence:
set air interface authentication type [none, unique, group] press
Enter
where [none, unique, group] identifies the authentication type. Use
unique on this occasion.
Air Interface Authentication Type set to :unique

Would you like to 'save mib' now? Enter Y(yes) or N (no):y
Set unique peer Sets the unique peer authentication key of the peer node with which
authentication key <xxxx> you wish to authenticate, generally the far-end unit.
Sequence:
set unique peer authentication key <xxxx> press Enter
where <xxxx> is the Unit Serial Number of the far-end unit
determined from the get hw inventory command performed earlier.
Unique Peer Authentication Key: xxxx.
Note: You will need to repeat this procedure for each unit.
DragonWave Inc.
104
NOTE: Once the unique authentication key is set, you will need to verify the
authentication settings and set the authentication failure parameter
before saving the mib and resetting the system. See Procedure 3-21.
This concludes the steps to setting authentication to unique.
Procedure 12-2
Setting Group authentication
Perform this procedure to set group authentication using the CLI manager.

Set air interface Sets the authentication type. This needs to be set to group.
authentication type The default type is none.
Sequence:
set air interface authentication type [none, unique, group] press
Enter
where [none, unique, group] identifies the authentication type. Use
group on this occasion.
AIR INTERFACE AUTHENTICATION type set to : group
Set group authentication key Sets the group authentication key.

Sequence:
set group authentication key <xxxxxxxx> press Enter
where <xxxxxxxx> is a character string consisting of up to eight
characters that may be: 0 to 9, a to z, and A to Z but may not contain
any of the following: !@#$%^&*(,);:’”+-~
Group Authentication Key: xxxxxxxx.
Note: The <xxxxxxxx> is the unique eight-character string you have
assigned to be the group authentication key. You will need to repeat
this procedure for each unit in the group that uses the same group key.
NOTE: Once the group authentication key is set, you will need to verify the
authentication settings and set the authentication failure parameter
before saving the mib and resetting the system. See Procedure 3-21.
This concludes the steps to set the group authentication key using the CLI manager
System Authentication
105
Procedure 12-3
Verify Authentication status
Use this procedure to verify the authentication action for the system.
Note: To perform this procedure, you must be logged into the system as an NOC user.
login Log in using a NOC account.
Get authentication status Displays the authentication status between two corresponding Horizon
Quantum systems.
Sequence:
get authentication status press Enter
Where
[authentication Status] is one of the following:
Authenticated
NotAuthenticated
ExplicitAuthenticationFailure

Authentication status:[Authenticated
NotAuthenticated
ExplicitAuthenticationFailure]
Explanations:
If authentication has failed:
check the setting for action on authentication failure; and
ensure it is not set to Block Traffic (unless that is the intended action).
If authentication has not failed:
check to see if traffic is now flowing.
If traffic is flowing then the authentication has been re-established and
the system is operating normally
If traffic is not flowing, the problem is not due to authentication.
set authentication failure Configures the action to take on peer authentication failure.
[block_traffic/pass_traffic] Sequence:
set authentication failure [block_traffic/pass_traffic] press Enter

System will [block_traffic/pass_traffic] on peer authentication failure.
DragonWave Inc.
106

Sequence
press Y
regain access.
This concludes the steps to verify the authentication status using the CLI manager.
13.0 User Authentication
Horizon Quantum supports three methods of User Authentication:
• Internal
• Remote Authentication Dial In User Service (RADIUS)
• TACACS+
Procedure 13-1
Setting up User Authentication
login Log in using the Super user.

Select the type of User This command allows the user to select the type of Authentiation you wish to
Authentication to configure. configure. Note that internal is the default.
Sequence:
set user authentication method [internal | radius | tacacsplus] press
Enter
Example: set user authentication method radius press Enter
User login authentication method is: radius
13.1 Internal Authentication

The default User Authentication is Internal. Internal Authentication allows access to a node only to
those knowing a valid account user name and password already set up on that node. A total of 50
Admin, 5 Noc and one Super User accounts can be set up in the system. See Volume 1 “User
Accounts” for details on setting up user accounts.
13.2 RADIUS Server User Authentication

The DragonWave Remote Authentication Dial In User Service (RADIUS) server option enables users to
be centrally authenticated before being allowed access to a modem. This adds another layer of security
by removing user access control away from individual modems and moving it to a central server.
User names and passwords must be entered into the RADIUS server(s) before authentication can occur
and access granted or denied. Up to five (5) RADIUS servers can be configured.
When one, or more, RADIUS server is configured, the username and password authentication system
on the modem is bypassed, in favour of the RADIUS system. If, on attempting to log in, a user does not
receive a response from a configured RADIUS server, the user will not be allowed to log in. This could
be the case if the server was off line. However, the system can be configured to allow the Super User to
still access the modem via the local modem access control, even when a RADIUS server does not
respond.
DragonWave Inc.
108
13.2.1 Configuring RADIUS Server User Authentication

Only the Super user can issue any of the RADIUS “set” commands and view any of the security related
entries returned with “get” commands (passwords, shared key etc..)
Procedure 13-2
Use this procedure to set up user authentication using a RADIUS server and enable the Super user
to access a modem if the RADIUS server does not respond.
Note: To perform this procedure, you must be logged into the system as the Super user.
login Log in using the Super user account.
get radius servers Returns a list of RADIUS servers already configured on the system.
Sequence:
get radius servers press Enter
index active_host active_key cfgd_host cfgd_key

===== =============== =============== ===============
1 192.168.1.48 testing123 192.168.1.48 testing123
2 192.168.1.20
3
4
5
Note that the second radius server is not active because the radius key has
not been configured.
set radius server host This command sets up a RADIUS server host. Note that once the RADIUS
server host details have been entered, the server key has to be entered before
the server becomes active (see next command).
Sequence:
set radius server host [index] [ip address] press Enter
Where [index] is the server index 1…5 and [ip address] is the ip
address of the RADIUS server concerned
Example:
set radius server host 2 192.168.1.48
Host set. When server Host and Key are set,
'save mib' and 'reset system' for changes to take effect

User Authentication
109
set radius server key Adds the required shared key to the RADIUS server host configuration. Note
that the previous command has to be issued and the server key entered
before the RADIUS server will become active.
Sequence:
set radius server key [index] [someString] press Enter
Where [index] is the server index 1…5 and [someString] is an alpha-
numeric string of up to 32 characters in length.
Example : set radius server key 2 test1234
Key set. When server Host and Key are set,
'save mib' and 'reset system' for changes to take effect
get radius servers Check that servers have been set up correctly by issuing this command
Sequence:
get radius servers press Enter

index active_host active_key cfgd_host cfgd_key
===== =============== =============== ===============
1
2 192.168.1.48 test1234 192.168.1.48 test1234
3
4
5
set radius super user This commands enables or disables the Super user from accessing a
authentication modem, when the RADIUS server does not respond, or is not
available. If set to “off” the Super user is allowed to log in using the
name and password set in the modem. The default setting is “off”.
Sequence:
set radius super user authentication strict [on/off] press Enter

Radius authentication for Super User is now [strict/not strict]
A save mib command will make this command effective immediately.

WARNING: If super user authentication is set to ON, and the Super
user name and password are not entered into the RADIUS system, the
Super user will not be able to regain access to the modem after a
reset.
DragonWave Inc.
110
get radius super user This command returns the status of the radius super user.
authentication strict
Sequence:
get radius super user authentication strict press Enter

Radius authentication for Super User is [strict/not strict]
(not strict means SU flash password still works under Radius)
save mib Saves the MIB to RAM. Perform this command to save setting changes to
non-volatile memory.
Sequence:


Sequence
press Y
The system will proceed to reset. You will have to log on again to regain
access.
User Authentication
111
13.2.2 Configuring the RADIUS Server

To support the DragonWave RADIUS application, each RADIUS server on the network must be
provided with a Vendor Specific Attribute (VSA) file. The VSA file contains the definition of the
DragonWave user privilege level (Admin, NOC, Super-User) allocated to users. User definitions can use
the DragonWave-Privilege-Level attribute to assign access privileges. If the VSA is missing, then the
RADIUS logs the user in at an Admin level only. If a VSA is present, but is invalid, then access is
denied.
A typical VSA file is shown below. Without the DragonWave-Privilege-Level attribute AND with “radius
super user strict on”, users cannot gain access to the device using CLI.
Note that the Web server does not use RADIUS authentication at all. If you want the system to be
100% RADIUS secured, then you need to disable the Web server (set web server off).
############################################################################
#
# DragonWave VSAs
#
############################################################################
VENDOR DragonWave 7262
BEGIN-VENDOR DragonWave
# Used to determine the user login privilege level.

ATTRIBUTE DragonWave-Privilege-Level 1 integer
# Read-only access.
VALUE DragonWave-Privilege-Level DragonWave-Admin-User 1
# Limited read-write access.

VALUE DragonWave-Privilege-Level DragonWave-NOC-User 2
# Unlimited read-write access.

VALUE DragonWave-Privilege-Level DragonWave-Super-User 3
END-VENDOR DragonWave
DragonWave Inc.
112
13.3 TACACS+ Authentication

The DragonWave TACACS+ option is similar to RADIUS. Whereas RADIUS combines authentication
and authorization in a user profile, TACACS+ separates the two operations. Another difference is that
TACACS+ uses the Transmission Control Protocol(TCP) while RADIUS uses the User Datagram
Protocol (UDP). Also, after configuring TACACS+, the feature becomes active immediately. A save mib
command is only required if the configuration is to be saved in flash memory so that it is restored after a
reset system or a power cycle.
13.3.1 Configuring TACACS+ Server User Authentication

All TACACS+ “get” commands are available to all user levels. Only the Super user can issue any of the
TACACS+ “set” commands. All set commands take effect immediately, without the need to reset
system. However, a save mib command is required if you wish to preserve the system configuration
during a reset system or power cycle.
Procedure 13-3
TACACS+ Server User Authentication
Use this procedure to set up user authentication using a TACACS+ server and enable the Super user to
access a modem if the TACACS+ server does not respond.
Note: To perform this procedure, you must be logged into the system as the Super user.
login Log in using the Super user account.
View TACACS+ servers Returns a list of TACACS+ servers already configured on the system.
Sequence:
get tacacsplus servers press Enter
index host key port

===== ============= ================= ===============
1 192.168.1.48 testing123 49
2 192.168.1.20 secure 987 77
3 192.168.1.22
4
5
Note that the index 3 TACACS+ server is not active because the key and port
number have not yet been entered.
User Authentication
113
Delete an existing TACACS+ To delete an existing TACACS+ server on the system use the following
server command:
Sequence:
delete tacacsplus server [index] press Enter
Example:
delete tacacsplus server 2 press Enter
index host key port
===== ============= ================= ===============
1 192.168.1.48 testing123 49
2
3 192.168.1.22
4
5
Note that index 2 position is now blank, confirming that the server is deleted.
Configure TACACS+ server ip This command sets up a TACACS+ server host ip address.
address Sequence:
set tacacsplus server host [index] [ip address] press Enter
Where [index] is the server index 1 to 5 and [ip address] is the ip
address of the TACACS+ server concerned
Example:
set tacacsplus server host 4 192.168.55.100 press Enter
index host key port
===== ================ ================= ===============
1 192.168.1.48 testing123 49
2
3 192.168.1.22
4 192.168.55.100
5
Configure TACACS+ server key Adds the server key to the TACACS+ server host ip address configuration.
Sequence:
set tacacsplus server key [index] [key] press Enter
Where [index] is the server index 1 to 5 and [key] is an alpha-
numeric string of up to 32 characters in length.
Example:
set tacacsplus server key 4 abcd4567 press Enter
index host key port
===== ================ ================= ===============
1 192.168.1.48 testing123 49
2
3 192.168.1.22
4 192.168.55.100 abcd4567
5
DragonWave Inc.
114
Configure the TACACS+ server Sets the port number that the server will listen on.
port Sequence:
set tacacsplus server port [index] [port] press Enter
Example:
set tacacsplus server port 4 199 press Enter
index host key port
===== ================ ================= ===============
1 192.168.1.48 testing123 49
2
3 192.168.1.22
4 192.168.55.100 abcd4567 199
5
Check the status of TACACS+ This command returns the status of super user authentication.
super user authentication Sequence:
get tacacsplus super user authentication press Enter
TACACS+ authentication for Super User is not strict
(not strict means SU flash password still works under TACACS+)
“not strict” means that the super user can gain access to the system by using
their name and password that is stored on the Horizon Compact + modem.
“strict” means that no users can gain access to the modem without TACACS+
authentication. See next command.
Configure TACACS+ super user This command enables or disables the Super user from accessing a modem,
authentication when the TACACS+ server does not respond, or is not available.
If set to “off” the Super user is allowed to log in using the name and password
set in the modem. The default setting is “off”. When set to “on” no user can
gain access to the system without TACACS+ authentication.
Sequence:
set tacacsplus super user authentication strict [on/off] press Enter
TACACS+ authentication for Super User is now [strict/not strict]
WARNING: If super user authentication is set to ON, and the super user name
and password are not entered into the TACACS+ system, the super user will
not be able to regain access to the modem after a reset.
Note: save mib is not necessary Saves the MIB to RAM. Perform this command to save setting changes to
as the commands take effect non-volatile memory.
immediately. However, if you
wish to preserve this Sequence:
configuration so that it is still in save mib press Enter
effect after a reset system or a The system responds:
power cycle, you will need to
issue the save mib command Mib saved successfully.
as shown opposite.
14.0 Data Encryption
Data encryption is a DragonWave Inc. licensed feature. The DragonWave proprietary system for
transmitting Ethernet data over-the-air is very secure in its own right. Adding an optional data encryption
process to the over-the-air transmission system adds another layer of security to the transmitted data.
Horizon Quantum uses a data encryption process which is compliant with FIPS 140-2 security level 1,
along with an encryption algorithm that is AES-256 FIPS-197 compliant.
Only the Superuser can access the encryption feature. In order to monitor and control the encryption
option, the Superuser needs to access the system through a command line interface (CLI) connection
using secure shell (SSH) client software (see Section 22.1.1).
Encryption is supported in both Hot Standby and Bandwidth Doubling options.
Although data encryption is a licensed feature, it is possible to fully configure it at any time, on any one, or
all, nodes, with, or without, a license key. However, the system will only encrypt data over-the-air once a
license key is obtained from DragonWave Inc..
All commands take effect immediately (CLI commands save mib or reset system are not required)
14.1 Encryption Key Generation

There are two options for generating the required encryption key:
• Manual key entry
• Automatic key generation (default)
On system startup the default encryption setting is for auto mode and disabled. Note: To change the
system from automatic key generation to manual key entry, always start with the active TxHigh unit.
Updating encryption keys is hitless, with no loss, or latency, of user data over-the-air.
14.1.1 Manual Key Entry

The user has the option to manually enter a 32 byte, 48 byte, or 64 byte long encryption key into the
system. The same key must be entered on all systems that comprise a link, including any redundant
partners. Applying the CLI command activate on the active TxHigh node, activates the encryption key on
all nodes. The system will validate the keys, using a secured connection between the crypto modules in
each node on the link, to ensure that they are all identical, before allowing encryption to be enabled (CLI
command enable).
The system will provide an explicit alarm if there is a key mismatch between nodes in the link.
Once encryption is enabled and traffic over-the-air is being encrypted, manual updating (changing) the
encryption key is hitless, with no loss, or latency, of user data over-the-air.
14.1.2 Automatic Key Generation

Automatic key generation is the default option and includes the periodic regeneration of a new encryption
key. The default rekeying period is 2 hours. The minimum rekey period is 1 hour.
Updating encryption keys is hitless, with no loss, or latency, of user data over-the-air.
The CLI command enable needs to be applied before over-the-air encryption can take place.
Note: To change the system from automatic key generation, to manual key entry, always start with the
active TxHigh unit.
DragonWave Inc.
116
Procedure 14-1
Configuring Encryption
login Log in as the Superuser using secure shell (SSH) access software.
The following example uses PuTTY SSH client software. Start PuTTY and when
prompted, enter the IP address of the target system. You will then be prompted to log in
(default Superuser account shown in example) with the following system response:
login as: energetic
Horizon Quantum, Release x.x.x(4368)
Copyright 20xx-20xx DragonWave Inc.
All rights reserved.
Using keyboard-interactive authentication.

WARNING! Logins are restricted on this machine.
Please Enter password: wireless
Note that the password will not be visible on the screen.
Access the encryption This command gives access to the crypto module and encryption feature configuration
feature commands. Only the Superuser can access this command.
Sequence:
crypto press Enter
crypto->
Manual Key Entry This command allows you to enter a 32 byte, 48 byte, or 64 byte encryption key
manually. Note that this same key must be entered on all systems on the link, including
standby units when redundancy is employed. If there is a mismatch of keys the system
will indicate same.
Sequence (Example with a random 32 byte key used):
crypto->key press Enter
Enter a 256/192/128bit key in hexadecimal notation (e.g. 4A12B96955...) (use
'q' to quit):
******************************** (Note that the characters entered are hashed out)
Please Re-Enter Key:
********************************Sending key...
This command can take several seconds to complete, please wait...

Sending command ...
...Acknowledgment received with response ...: key mismatch. please check for
matching key on peer .
crypto->
This response indicates that the new encryption key needs to be entered on the peer
node before the encryption key can be activated.
Data Encryption
117
Activate the manual This command activates the manual key on all units on the link. To do this, the identical
key. encryption key must have been entered on all the other nodes on the link first (including
This command is only redundant partners) . This activate command must be applied on the active TxHigh node
required for the for it to be propagated to all other nodes on the ink. Note that if the encryption feature is
manual key entry disabled, you can still “activate” the encryption key, but data over the air will NOT be
option encrypted until the feature is enabled.
Sequence:
crypto->activate press Enter
Sending command ...
...Acknowledgment received with response ...: .
crypto->
If this command was applied to a unit which was not the active TxHigh unit:
Sending command ...
...Acknowledgment received with response ...:This command must be applied
on the peer (High Active modem) .
crypto->
Auto key entry This command allows the system to generate an encryption key automatically and uses
the default time of 2 hours for periodically regenerating a new key. This command must
be configured on all the nodes on the link, but the active TxHigh node MUST be
configured last in order to activate the encryption feature on all nodes. Note that the
activate command is not required for this feature.
Sequence:
crypto->autokeygen press Enter
When this command is applied to a node other than the TxHigh active unit:
Sending command ...
...Acknowledgment received with response ...: Switched to auto mode. please
apply from peer TxHigh modem to take effect. ..
crypto->
When this command is applied to the active TxHigh node (must be last node to be
configured)
Sending command ...
...Acknowledgment received with response ...: .
crypto->
This will place all nodes in auto mode and activate encryption.
Note that if this command is entered on the TxHigh node during encryption, it will force a
rekey.
DragonWave Inc.
118
Adjust the auto rekey This command is only supported on the active TxHigh node and will allow you to change
time period. the time period between auto rekeying operations. On a redundant system both the
This command is only TxHigh nodes must have this command applied.
supported with the The default rekeying period is 2 hours (120 minutes). The minimum rekeying period is 60
auto rekey option. minutes.
Sequence:
crypto->rekey [minutes]
Example:
crypto->rekey 90
Sending command ...
...Acknowledgment received with response ...:new rekey interval 90min, takes
effect after next rekey. Note, ensure this is applied to both Active and Standby
units in Redundant Configuration. .
crypto->
Note that this will only take effect once the remainder of the rekeying period currently
running times out.
Enable encryption When input on the active TxHigh node, this command will be propagated to all nodes on
the link and enable encryption on the link.. However, if there is a key mismatch, user data
will not be encrypted.
Sequence (Example of command applied to a node that is not the active TxHigh):
crypto->enable press Enter
Sending command ...
...Acknowledgment received with response ...: (no peer) Encryption Enabled.
command applied locally .
This response indicates that you need to configure encryption on the peer node before
encryption can be enabled.
Data Encryption
119
Show status of This command returns the current status of encryption on the system. Bold text
encryption describes the item.
Sequence:
crypto->status press Enter
Sending command ...
...Acknowledgment received with response ...:
Status[Driver Status]: Enabled[Encrypting)
Indicates admin status and over-the-air encryption status, either “encrypting” or “bypass”.
Data Path: off
Indicates whether the user data path has been allowed (on) or blocked (off).
Key Generation Mode: auto
“manual” implies a key has been entered. “auto” implies that a key has been auto generated
at the rekey interval.
Peer Key Match: unknown
This unit’s key either matches or does not match with that of the peer.
Partner Key Match: match
Only appears for a redundant system. This unit’s key either matches or does not match that
of the partner.
Power Up Tests: Passed
During power up, self-tests are executed. If any of the tests fail, an alarm is raised and
encryption is not permitted.
Rekey Period: 90min
Only appears on TxHigh nodes. At the specified interval the node will perform a key
agreement with its peer.
Derived Key:
'829918a89861ccd3e2437079dd86d547291297fe42364693b9b166e0ca4c87bd'
This shows an indication of the entered key (not the real key) which can be compared with
and matched with, that of its peer and partner.
Rekey Count: 0
Only appears on TxHigh nodes. Shows the number of times that this unit has performed a
key agreement with its peer.
Modem: txHigh-Standby
Describes the configuration of the node. It can be any one of TxHigh, TxLow, TxHigh-
Standby, TxLow-Standby, TxHigh-Active, TxLow-Active.
[ Configuration Mismatch with Partner ] .
Indicates a configuration mismatch with that of its partner. Either the partner admin status is
different, or one unit is licensed and the other is not.
[Configuration Mismatch with Peer].
Indicates a configuration mismatch with that of its peer. Either the peer admin status is
different, or one unit is licensed and the other is not.
[Peer Encryptor Key Bank Mismatch. Please Enter and Activate Key]
In manual mode, internal key bank mismatch with partner, encryption over-the-air will fail.
[Partner Encryptor Key Bank Mismatch. Please Enter and Activate Key]
In manual mode, internal key bank mismatch with partner, encryption over-the-air will fail if
there is a redundant switch-over.
DragonWave Inc.
120
Disable encryption This command disables encryption on the target node. If input on the active TxHigh
node, the command is propagated to all nodes in the link and implies that data will be
sent in the clear (unencrypted).
Sequence:
crypto->disable press Enter
Sending command ...
...Acknowledgment received with response ...: (no peer) Encryption
Disabled.command applied locally .
crypto->
Note that, in this example, the command was not input on the active TxHigh node so it
only takes effect locally. Encryption on all other nodes is not disabled.
To exit encryption This command returns you to the Horizon Quantum CLI entry level.
feature Sequence:
crypto->exit (or quit) press Enter
->
15.0 Threshold Alarms
Horizon Quantum provides Threshold Alarms to assist in managing the performance of the system.
Threshold alarms are available for the following parameters:
• RSL (Receive Signal Level)
• Signal To Noise (SNR)
• Bandwidth Utilization
• Dropped Frames
Each Threshold Alarm has two associated parameters:
1. Threshold value
2. A time limit over which the Threshold value must be exceeded before the alarm is
reported.
The combination of the value and the time limit is user defined. The proper combination of the two
parameters will prevent false alarms from occurring.
Procedure 15-1
Configure Threshold Alarms
Perform this procedure to configure the Threshold Alarms for the Horizon Quantum system. Each
Threshold Alarm may be configured independently of each other, and each end of the link may be
configured for different values.
Note: To perform this procedure, you must have NOC user rights.
get RSL threshold alarm Displays the current settings for the Threshold Alarm for the Receive
settings Signal Level (RSL). Once the RSL Value Threshold is reached and
continues for the Time Limit duration then an alarm is raised.
Sequence:
get rsl threshold press Enter

RSL threshold set to : <rsl value> dbm
RSL timelimit set to : <timelimit> secs
Where
<rsl value> is the current RSL value in integers, given in dBm.
<timelimit> is the current time limit that the condition must occur
before the alarm is raised. Timelimit is in integers, given in number
of seconds
DragonWave Inc.
122
set RSL threshold alarm Sets the current settings for the Threshold Alarm for the Receive
settings Signal Level (RSL). Once the RSL Value Threshold is reached and
continues for the Time Limit duration then an alarm is raised.
Sequence:
set rsl threshold <rsl value> <timelimit> press Enter
Where
<rsl value> is the desired RSL value in integers, given in dBm.
<timelimit> is the desired time limit that the condition must occur
of seconds

RSL threshold set to : <rsl value> dbm
RSL timelimit set to : <timelimit> secs
get snr threshold Returns the current signal to noise ration alarm threshold.
Sequence:
get snr threshold press Enter
SNR threshold set to : n
Where n is the current SNR threshold setting
set snr threshold Sets the SNR level below which a threshold alarm will be raised.
Sequence:
set snr threshold <snr value> press Enter
Where <snr value> is in dB and between 0 and 30
SNR threshold set to : n
Where n is the new SNR threshold setting
get bandwidth utilization Displays the current settings for the Bandwidth Utilization Threshold
threshold alarm settings Alarm.
Sequence:
get bandwidth utilization threshold press Enter
Bandwidth utilization threshold set to : <value> % Bandwidth
utilization timelimit set to : <timelimit> secs.
Where
<value> is the current bandwidth utilization value expressed in
percentage
of seconds
Threshold Alarms
123
set bandwidth utilization Sets the values for the Threshold Alarm for the Bit Error Rate (BER) as
threshold alarm settings calculated by the Horizon Quantum modem. Once the BER Value
Threshold is reached and continues to remain between the Threshold
value and the hysteresis value, then an alarm is raised. Once the
value drops below the hysteresis value then the alarm is cleared.
Sequence:
set bandwidth utilization threshold <value> <timelimit> press
Enter
Where
<value> is the current bandwidth utilization value expressed in
percentage
of seconds. Default value is 10 seconds
get dropped frames threshold Displays the current settings for the Dropped Ethernet Frames
alarm settings Threshold Alarm.
Sequence:
get dropped frames threshold press Enter
Dropped frames threshold set to : <value> %
Dropped frames timelimit set to : <timelimit> secs.
Where
<value> is the current dropped frames value expressed in
percentage
before the alarm is raised. Timelimit is an integer, given in number of
seconds
set dropped frames threshold Sets the values for the Dropped Ethernet Frames Threshold Alarm.
alarm settings As the Horizon Quantumtraffic rate from the LAN side exceeds the
programmed limit, frames are dropped in order to maintain the limit.
Sequence:
set dropped frames threshold <value> <timelimit> press Enter
Where
<value> is the current dropped frames value expressed in
percentage
of seconds. Default value is 10 seconds.
DragonWave Inc.
124
Sequence:
This concludes the steps to configure Threshold Alarms for the Horizon Quantum system using the CLI
manager.
16.0 Rapid Link Shutdown (RLS)
Networks containing alternate or redundant routing paths will typically rely on protocols such as Rapid
Spanning Tree Protocol (RSTP) to invoke a reroute when communications to the far end unit fail or
experience high data error rates. The protocols are implemented on the Ethernet switch and rely on
polling or messaging to determine that communications to the far end has been disrupted. Although very
effective, these protocols can result in slow reaction times to determine link issues. It is desirable to
inform a switch or router of a network issue in the quickest manner possible. The Horizon Quantum
system provides the Rapid Link Shutdown feature for this purpose. Notification to the switch or router is
provided by shutting down the Ethernet ports connecting the Horizon Quantum systems to the network.
The Ethernet ports at both ends of the link are shut down. The Ethernet switch immediately recognizes
the loss of Ethernet connection and invokes its alternate path algorithm. This is also true for the on-board
Ethernet switch, with some variations, if the layer 2 switch option (l2sw) is enabled (DWI licensed feature),
(see notes below and Volume 4 of this manual for more details on l2sw features).
The default setting for RLS is OFF, meaning that the Ethernet port will remain connected during failure
conditions.
Notes:
1. RLS is not compatible with the Horizon Quantum redundancy option and should NOT be enabled
when the redundancy option is employed.
2. RLS should be disabled during link alignment to prevent the condition where a link goes in and
out of synchronization resulting in the RLS being invoked and released causing loss of Ethernet
management to the systems.
3. Provided that the RLS logic is true for the group to which an RLS configured Ethernet port
belongs, an Ethernet cable disconnected from that port will trigger an RLS event, which will result
in all the Ethernet ports configured for RLS at the same end being shut down and all the RLS
configured Ethernet ports at the other end being shut down. Note that port numbers configured
for RLS do not have to be the same at each end of the link.
4. If the Layer 2 Switch feature (l2sw) is enabled (DWI licensed feature), any Ethernet ports, that are
configured as part of the isolated port group IPG0, support spanning tree protocol (stp). There are
two categories of event that can trigger RLS:
• configured RLS ports status change
• an over-the-air link error
When RLS is triggered, the data ports that belong to IPG0 will all be shut down, and thus
RSTP/MSTP knows that the over-the-air link is down. This will trigger the RSTP/MSTP to
reconstruct network topology. For Ethernet ports that belong to other IPGs, the RLS action is the
same as before (i.e. the RLS ports will be shutdown).
16.1 Determination of Error Rates on Horizon Quantum Systems

Horizon Quantum systems employ forwards and backwards error correction to compensate for and
correct errors occurring over the RF link. Once these errors are corrected, the user data can flow error-
free. The post-correction data error rate is reported as "Rx Block Receive Errors" within the Horizon
Quantum, accessible through traffic statistics in CLI or through the Performance web page. Rx Block
Error Rate is also available and is reported in scientific notation.
The Horizon Quantum systems communicate with each other via “Rx Blocks” at all times even if there is
no Ethernet traffic. The Rx Blocks are transmitted at a fixed rate and therefore a Rx Block error rate is
also available. The incoming Ethernet data stream is treated as a bit stream and sub-divided into Rx
Blocks for transmission over the RF link. Rx Blocks are continuously transmitted to the far end modem
regardless of whether or not Ethernet traffic exists. Rx Blocks are less than 256 Bytes in length including
overhead. The modems transmit approximately 59,000 blocks per second on a 100 Mbps link. In order to
DragonWave Inc.
126
determine a Rx Block error rate of 1x10e-6 there would have to be a minimum of 1 million Rx Blocks
transmitted. At 59,000 blocks per second, it would take 16.8 seconds to transmit 1 million blocks.
Horizon Quantum enhancements to the DragonWave RLS functionality consist of:
• The fade monitor (“soft failure” mode) analyzes the Rx Block error rate over time increments. RLS
will trigger when the user-configurable error rate threshold is exceeded. The sample time
parameter for both “break” (“break” relates to the shutting down of the link) and “make” (“make”
relates to the re-establishment of the link) can be configured independently.
• A “hard failure” mode triggers on a percentage of erred packets on a link. This mode is applicable
to link outages or severely degraded data transfer.
o The default value of error threshold is a loss of 50% of Rx Blocks (packets) over a default
sample time of 50 mS. The sample time and error threshold are user-configurable.
• Advanced Mode provides support for a combined “hard”/”soft” failure mode
o Fast RLS switch for “hard” failure (severe degradation or link outage)
o Longer sample time and RLS switch for “soft” failure (high error rate)
• Increased flexibility in setting a larger differential for “break vs. make” error values
• Addition of a Receive Signal Level “RSL” threshold monitor to be optionally used in “make”
criteria for link startup
16.2 RLS Configuration

When RLS is enabled there are two options available for determining when RLS should be invoked to
shut down the Ethernet ports. These are the basic and advanced modes.
16.2.1 Basic Mode

In basic mode, the user can configure the modem Block error rate thresholds under which RLS will be
invoked and the Ethernet ports disabled. The user can also set the thresholds for which RLS will be
revoked and the Ethernet ports brought back to service. Complete link outages due to loss of Ethernet
connectivity, loss of RF path, hardware failure, or power failure will trigger an RLS event and the modem’s
Ethernet ports will be shut down until the outage is repaired.
The basic mode relies on the follow situations occurring:
“Soft” failure. This mode monitors the link for data errors either as a steady state error rate or bursts
of data errors.
a. The RLS signal degrade settings correspond to “soft” failure mode.
b. The value being monitored is Modem Receive Block Errors. RF link errors are typically
corrected by the modem and therefore no user data errors occur. The Modem Receive
Block Errors value is a true representation of user data errors occurring between the
modems.
c. The sample time is user configurable
d. An RLS signal degrade threshold setting in percentage is available to allow shorter
sampling times should errors occur on a frequent basis.
16.2.2 Advanced Mode

The advanced mode relies on any of the following situations occurring:
1. “Hard” failure. This mode invokes RLS when the link has deteriorated to a point of a massive
amount of data errors being received over the link.
a. A link outage will trigger an immediate RLS condition.
Rapid Link Shutdown (RLS)
127
b. The RLS signal fault parameters correspond to “hard” failure mode.

c. The user-configurable error rates vary from 5% to 95%.
d. The user-configurable sample time ranges from 5 mS to 1000 mS.
Example: Configuring 50% error rate over the link for a 100 mS time period will invoke RLS if the
error rate equals, or exceeds, 50% over a period of 100 mS.
2. “Soft” failure. This mode monitors the link for data errors either as a steady state error rate or
bursts of data errors.
a. The RLS signal degrade settings correspond to “soft” failure mode.
b. The value being monitored is Modem Receive Block Errors. RF link errors are typically
corrected by the modem and therefore no user data errors occur. The Modem Receive
Block Errors value is a true representation of user data errors occurring between the
modems.
c. The sample time is user configurable
d. An RLS signal degrade threshold setting in percentage is available to allow shorter
sampling times should errors occur on a frequent basis.
While monitoring for a “soft” failure, any “hard failure” will invoke RLS immediately.
Note: When selecting Advanced Mode, both the “hard” failure mode and “soft” failure mode are to be
configured.
16.3 Settings for Basic Mode

Basic mode relies on RLS link monitor parameters consisting of errors in data transfer between the
modems. It monitors Rx Block errors and the user configures the number of errors and sampling time for
those errors for both the invocation and revocation of RLS.
16.3.1 RLS Signal Degrade Settings

These settings correspond to “soft” failure mode.
The following command sets the minimum RSL value that will re-establish, or “make”, the link.
set rls make rsl [RSL Threshold (dB)] [Sample Period (sec)]
Example: set rls make rsl -60.0 100
When the RSL level is maintained at -60.0 or a higher value (less negative) for the duration of the sample
period (100 seconds), the link will be re-established, provided that there are no other existing “soft” or
“hard failures”
Setting the RSL sample period to zero (0), the default value, disables this feature.
16.3.2 RLS Link Monitor Parameters

This CLI only command provides a custom method for the configuration on the “soft error” monitor. The
method directly configures the sampling period, required repeated consecutive samples and the erred
block thresholds per period of the “soft error” monitor. This method allows additional low-level tuning of
the “soft error” monitor.
The RLS link monitor parameters are a measure of the number of block errors per designated sampling
time period. The user configures the RLS settings for:
• the number of desired block errors required in order to invoke, or revoke, RLS
• the number of samples in which the block errors occur
• the sampling time in milliseconds
DragonWave Inc.
128
• a “quick” sampling time that determines a fail condition if the block error threshold is
exceeded before the down sample time period times out
The following command configures the link monitor parameters:
set rls link monitor parameters [dn2up block errors per sample] [up2dn block errors per sample]
[dn2up # of samples] [up2dn # of samples] [dn2up sample time in msec] [up2dn sample time in
msec] [quick sample time]
Example: set rls link monitor parameters 2 4 5 2 1000 100 10
• If there are 4 or more block errors in 100 mS for 2 consecutive samples then invoke RLS
(“break”)
• If the 4 or more block errors occur within the first 10 mS (quick sample time) of the 100 mS
period, count it as a failure and immediately restart the 100 mS sample period.
• If 2 or less block errors occur in 1000 mS period for 5 consecutive samples revoke RLS (“make”)
Note that the quick sample time parameter provides a quicker response to block errors if the block error
threshold occurs early in the configured sample time period. To disable the quick sample time feature,
configure its value the same as the “up2dn” sample time.
16.4 Settings for Advanced Mode

If the user requires a quicker RLS response, the Advanced Mode is recommended.
Note: When selecting Advanced Mode, both the “soft” failure mode (Basic mode parameters) and “hard”
failure mode (Advanced mode parameters) are to be configured.
16.4.1 RLS Signal Fault Settings

These settings correspond to “hard” failure mode The RLS signal fault settings are designed to detect and
react to brief bursts of extreme Rx Block error rates. The RLS signal fault detection and reaction time is
the quickest of the two RLS fault detection methods. RLS signal fault detection works with the RLS signal
degrade settings in Advanced Mode.
set rls signal fault parameters [detect time] [percentage erred blocks]
The RLS signal fault parameters command accepts two parameters:
• [detect time] is the time, in milliseconds, that the [percentage erred blocks] threshold must
be met to activate RLS.
• [percentage erred blocks] is the percentage of erred Rx Blocks required to invoke RLS.
For example, the command set rls signal fault parameters 1000 50 will activate RLS when
50% or more of the Rx Blocks received in 1000 milliseconds are erred.
16.4.2 Recovery from a Hard Failure

Once a “hard” failure has caused an RLS activation, it uses the “soft” failure - RLS signal degrade
parameters – to determine the length of time to wait before reactivating the Ethernet ports.
129
16.5 RLS Link Control Settings

By default, the disabling and enabling of the data Ethernet port is automatically managed by the Horizon
Quantum system in response to detected RLS events. It is possible to enable manual control of RLS
shutdowns, so that the data Ethernet port remains shutdown until a user explicitly re-enables it. There
are two commands that make up RLS link control.
set rls link control [on/off]
To enable manual control of the data Ethernet port link state, set rls link control to on. The
default setting is off, allowing the Horizon Quantum to re-enable the data Ethernet port once the
RLS condition is cleared.
set rls link enable [on/off]
When rls link control is set to on, the data Ethernet port remains in a shutdown state after the
RLS condition has been cleared. The Ethernet port is manually re-enabled by issuing the set rls
link enable on command. The set rls link enable off command disables the Ethernet port.
16.6 RLS Working with Hitless Automatic Adaptive Modulation

(HAAM)
The RLS feature supports HAAM. However, with HAAM enabled, it is recommended that you configure
the system mode to the highest modulation scheme available for the configured radio band. This will
provide a more reliable RLS performance.
Example: if radio band etsi23_2_28_R5 is configured, the system modes available are:
• hx28_27_qpsk
• hx28_36_qpsk
• hx28_71_16qam
• hx28_107_32qam
• hx28_142_128qam
• hx28_190_256qam
From the above list, the system mode having the highest modulation scheme is hx_190_256qam. i.e.
256qam. This is the recommended system mode to configure for this particular radio band. Other radio
bands, in comparison, may have a different highest modulation scheme available. For any radio band,
configure the system mode to the mode having the highest modulation scheme.
When configuring HAAM, the available HAAM modes can be different, compared to those available for
the system mode. Using the above radio band example, the HAAM modes range from hx28_36_qpsk to
hx28_245_2048qam. When HAAM is in operation the HAAM mode (i.e. modulation scheme) may be
upshifted or downshifted, as weather conditions dictate, to ensure that the link remains viable. If, due to
severe weather conditions, the HAAM mode has downshifted to its lowest modulation level, but the link
continues to degrade, then RLS will trigger, shutting down the Ethernet port and hence signalling the
associated data switch to find an alternate route. For more information on HAAM see Section 18.0.
DragonWave Inc.
130
Procedure 16-1
Configure Rapid Link Shutdown Options
Perform this procedure to configure the Rapid Link Shutdown Options for the Horizon Quantum system.
When RLS is used, the Horizon Quantum ports will be set to "down" during modem-to-modem
communication failure. This feature allows a switch/router to select an alternate path should the modem-
to-modem communications fail.
Note: To perform this procedure, you must have NOC user rights.

View rls Displays the state of the Rapid Link Shutdown feature. RLS provides
the ability to shut down the Horizon Quantum Ethernet link (both
endpoints) during system outages.
The default is "off".
Sequence:
get rls press Enter
RLS option is :[off/on][basic/advanced][anyport/bothports].
View rls status Displays the detailed status of the RLS configuration.
Sequence:
get rls status press Enter
RLS Option: On Basic anyp
Network Interface State: Up
RLS Peer Mismatch: OK
RLS Wireless Port1:
Rapid Link Shutdown: Activated

Degrade Monitor State: Activated
Make RSL Threshold: Not Met
Peer RLS State: Activated
Radio Interface State: Down
Network Interface State: Up
User Configured Establish FER: 5.00E-05
Minimum Achievable Establish FER: 2.63E-07
User Configured Shutdown FER: 5.00E-03
Minimum Achievable Shutdown FER: 6.57E-07
User Configured Establish Monitor Time(mSec): 120000
Actual Establish Monitor Time(mSec): 120575
User Configured Shutdown Monitor Time(mSec): 20000
Actual Shutdown Monitor Time(mSec): 20009
131
Configure rls [on/off] Turns the Rapid Link Shutdown (RLS) feature on or off. Turning RLS
[basic/advanced] on, with the optional "advanced" feature, enables use of the signal
[anyport/bothports] fault monitor as well as the signal degrade monitor. Setting RLS on
without issuing the basic or advanced command defaults to RLS on,
basic. You can also select the “anyport” or “bothports” options.
Anyport (default): If the Quantum has two wireless channels, if any
one channel fails, invoke the RLS
Bothports: If the Quantum has two wireless channels, if any one
channel fails, close down that channel and redirect the traffic through
the good channel. If the traffic queues are being monitored for dropped
packets, and the drop rate exceeds the preset value invoke RLS.
Now you can investigate the reason for the RLS shutdown. If you
determine that the reason was one bad channel and the other channel
was carrying the traffic above the channel capacity (as a result,
dropped packets exceed the threshold) you could bring the link up by
shaping the traffic to one channel capacity. Then you would issue the
command “set rls dropped frames override on”. This will bring the
link up and operating on one channel with continued monitoring for
dropped packets.
It is important to remember that dropped packets monitoring will start
only after one channel is down.
RLS provides the ability to shut down the Horizon Quantum Ethernet
ports during system outages.
Note: a save mib and reset system command must be issued in
order for the rls setting to take effect.
Sequence:
set rls [on/off] [basic/advanced] [anyport/bothports] press Enter
RLS option [on/off][basic/advanced][anyport/bothports]
Where
On means the RLS function is active in either basic or advanced option and
with anyport or bothports selected.
Off means the RLS function is inactive.
DragonWave Inc.
132
Force the system to revoke If you determine that the reason for invoking RLS was one bad
from RLS shutdown wireless channel and the other channel was carrying the traffic above
the channel capacity (as a result, dropped packets exceed the
threshold) you could bring the link up by shaping the traffic to one
channel capacity and use the following command to revoke RLS. This
will bring the link up and operating on one channel with continued
monitoring for dropped packets.
Sequence:
set rls dropped frames override on
System responds: (no response unless the action fails)
Failed
View rls link control Displays the state of the Rapid Link Shutdown (RLS) link control
feature. RLS provides the ability to shut down the Horizon Quantum
Ethernet ports (RLS group of Ports on both endpoints) during system
outages. The RLS link control feature determines how the system will
react when link recovery takes place, either providing automatic
recovery of the Ethernet ports by the Horizon Quantum system or
waiting for the user to manually recover the Ethernet ports through use
of the "set rls link enable on" command.
Sequence:
get rls link control press Enter
RLS link control option is set to [on/off]
Where
On means the user has to re-establish the Ethernet connection by
using the "set rls link enable on" command
Off means the system will auto-recover the Ethernet connection.
A save mib and reset system are required to activate this feature.
133
Configure rls link control Determines whether RLS link control performs automatic recovery or
[on/off] requires manual recovery of the Ethernet port. RLS provides the
ability to shut down the Horizon Quantum Ethernet ports (RLS group of
ports on both endpoints) during system outages. The user can
manually recover the Ethernet ports through the use of the "set rls link
enable on" command.
Sequence:
set rls link control [on/off] press Enter
RLS link control is set to [on/off]
Where
On means the user must manually recover the Ethernet port through the use
of the "set rls link enable on" command.
Off means the Horizon Quantum system will automatically recover the
Ethernet port.
View rls link enable Displays the state of the Rapid Link Shutdown (RLS) link enable
feature. RLS provides the ability to shut down the Horizon Quantum
Ethernet ports (RLS group of ports on both endpoints) during system
outages.
Sequence:
get rls link enable press Enter
RLS link enable is set to [on/off]
Where
On means to re-enable the Ethernet port on the modem
Off means the Ethernet port is not re-enabled.
Configure rls link enable Manually enables or disables the Horizon Quantum Ethernet link. This
[on/off] feature requires the rls link control feature to be "on".
Sequence:
set rls link enable [on/off] press Enter
RLS link enable is set to [on/off]
Where
On means to re-enable the Ethernet port on the modem
Off means the Ethernet port is not re-enabled.
DragonWave Inc.
134
Configure rls make rsl This is an optional command. This command sets the minimum RSL
value required to re-establish, or “make”, the link.
Sequence:
set rls make rsl [RSL (dB)] [Duration (sec)]
[wireless_port1/wireless_port2] press Enter
RLS Make RSL Parameters: [RSL (dB)] [Duration (sec)]
Example: set rls make rsl -60.0 100
When the RSL level on wireless port 1 is maintain at -60.0 or a higher
value (less negative) for the duration of the sample period (100
seconds), the link will be re-established.
Setting the RSL sample period to zero (0), the default value, disables
this feature.
Configure rls link monitor This is a custom method for the configuration of the “soft error”
parameters monitor. The method directly configures the sampling period, required
repeated consecutive samples and the errored block thresholds per
period of the “soft error” monitor. This method allows additional low-
level tuning of the “soft error” monitor.
Note: When this command is used, it overrides the set rls signal
degrade parameters and set rls signal degrade threshold
commands invoked by CLI, Web or SNMP methods.
Sequence:
set rls link monitor parameters [dn2up block errors per sample]
[up2dn block errors per sample] [dn2up # of samples] [up2dn # of
samples] [dn2up sample time in msec] [up2dn sample reset time
in msec] [Wireless_port1/wireless_port2]
Please contact DragonWave Customer Support for assistance if the
default “soft error” monitor behaviour needs to be tuned for a specific
application.
View rls link monitor This command returns the current rls link monitor parameters for
parameters wireless port 1 or wireless port 2.
Sequence (for port 1):
get rls link monitor parameters
Link Monitor Values: 2 5 5 2 10000 1000 100
Sequence (for port 2):
get rls link monitor parameters wireless_port2
Link Monitor Values: 2 5 5 2 10000 1000 100
135
Configure rls dropped frames Sets the monitoring parameters for the dropped frames for each
threshold [q1/q2/q3/q4] queue. If the QoS is enabled, all 4 queues are functional, otherwise q4
[dropped rate] [monitoring is the only queue used by the system. It is also important to remember
period] that this will be used only in “bothports” option of RLS.
Sequence:
set rls dropped frames threshold [q1/q2/q3/q4] [dropped
rate] [monitoring period]
System responds:
Link Monitor Values: [q1/q2/q3/q4][dropped rate][monitoring
period]
Example: set rls dropped frames threshold q1 25 100
System responds:
Link Monitor Values: q1 25.00% 100
View dropped frame This command returns the threshold settings for all four queues.
thresholds for all queues
Sequence:
get rls dropped frames threshold
System responds:
q1 25.00% 100
q2 35.00% 75
q3 40.00% 75
q4 10.00% 100
View rls signal fault The RLS signal fault settings are designed to detect and react to brief
parameters bursts of extreme Rx Block error rates or link outages. The RLS signal
fault detection and reaction time is the quickest of the two RLS fault
detection methods. RLS signal fault detection works with the RLS
signal degrade settings in Advanced mode.
Sequence:
get rls signal fault parameters [wireless_port1/wireless_port2]
press Enter
RLS Signal Fault Parameters: 1000 100
DragonWave Inc.
136
Configure rls signal fault Sets the RLS signal fault monitor parameters. The RLS signal fault
parameters [fault period settings are designed to detect and react to brief bursts of extreme Rx
msec] [fault threshold] Block error rates. The RLS signal fault detection and reaction time is
the quickest of the two RLS fault detection methods. RLS signal fault
detection works with the RLS signal degrade settings in Advanced
mode.
Sequence:
set rls signal fault parameters [fault period msec] [fault threshold]
[Wireless_port1/wireless_port2] press Enter
Where
[fault sample period msec] is the sample period to apply Fault
Threshold ratio
[fault threshold percentage] is the ratio of 'fault sample period'
faulted before the link is shut down.
RLS Signal Fault Parameters: 50 50
Save changes to mib Saves the MIB to RAM. Perform this command save setting changes
to FLASH. This command does not restart the system and does not
put any new settings into effect. A system reset command will cause
settings in RAM to be programmed into FLASH and to take effect.
Sequence:
reset system Resets the system to save the settings to FLASH and restart the
system with the new settings taking effect.
Sequence:
press Y
Once the system reboots, login and continue with the RLS
configuration.
This concludes the steps to configure Rapid Link Shutdown for the Horizon Quantum system using the
CLI manager.
17.0 Configuring the Time Source (SNTP)
Date and time information can be entered into the Horizon Quantumsystem. This is maintained for as
long as power is applied to the system. If power fails, then all timing information is lost. An accurate clock
is necessary for time stamping entries in the events and performance logs.
To maintain the time and date in the system, five network sources of timing information are configurable.
Up to five time sources can be configured, which can provide accurate time and date information to the
system. Simple Network Time Protocol (sntp) is used.
Five time sources are configured by default. Each time source is indexed 1 to 5. Indices 1 and 2 are from
Industry Canada servers, 3 and 4 are from U.S. Navy servers and 5 is from a Swiss server. Any other
time sources can be configured. The timing information is polled every 60 minutes.
Table 17-1 Time Sources
Index Stratum Source Source

IP Address
1 2 199.212.17.15 Industry Canada
2 2 199.212.17.20 Industry Canada
3 1 192.5.41.40 U.S. Navy
4 1 192.5.41.209 U.S. Navy
5 2 129.132.2.21 Switzerland
DragonWave Inc.
138
Procedure 17-1
Configuring the Horizon QuantumTime and Date

View date time Returns the current date and time on the system.
Sequence:
get date time press Enter
Date and Time : 15/06/2007 14:17:42:237
Configure date time Sets the system date and time if SNTP is not enabled.
Sequence:
set date time [dd/mm/yyyy hh:mm:ss:ms] press Enter
Where dd – day (01 – 31)
mm – month (01 – 12)
yyyy – year ( 1970 – 2099)
hh – hour (0 – 23)
mm – minutes (0 – 59)
ss – seconds (0 – 59)
ms – milliseconds (0 – 999)
Date and Time : [dd/mm/yyyy hh:mm:ss:ms]
Sequence:

Configuring the Time Source (SNTP)
139
Procedure 17-2
Configuring the Time Source

View sntp settings Displays the current time settings. This example shows the Horizon Quantum
system default settings.
Sequence :
get sntp press Enter
SNTP feature is turned on.
Current system time: 12/10/2005 15:36:54. Last SNTP synch: 12/10/2005
15:27:41.
Index | Status | Stratum | Name

1 Good 2 199.212.17.15
2 Good 2 199.212.17.20
3 Good 1 192.5.41.40
4 Good 1 192.5.41.209
5 Good 2 129.132.2.21
**Notes: SNTP servers are polled every 60 minutes.
Search for SNTP server always starts at index 1, for every poll.
System time will be set to first server found, every poll period.
Stratum level supplied by SNTP server. 0 indicates not available.
You can force a re-synch to all servers by setting SNTP 'on'.
System will not automatically adjust to Daylight Savings Time.
View sntp offset Displays the number of hours offset from GMT entered into the system.
Sequence :
get sntp offset press Enter
The system responds (example shows an offset of -1.5 hours) :
System time offset from GMT: -1.5 hours.
**Notes: System will not automatically adjust to Daylight Savings Time.

North America requires negative offset from GMT e.g. -5.0 hours
DragonWave Inc.
140
Configure sntp server Allows a new time source server to be entered.

Sequence :
set sntp server [index] [ip address] press Enter
Where [index] is a number 1 to 5 corresponding to the desired time source
index to be changed, and [ip address] is the ip address of the server
providing the new time source.
Success: SNTP server information accepted.
Configure sntp offset Allows the time difference from GMT to be entered, so that local time is
available to the system.
Sequence :
set sntp offset [offset hours] press Enter
Note that the offset hours can be negative or positive, depending on
your location relative to Greenwich, U.K. The maximum offset
accepted is ±14 hours
System time offset from GMT: [offset hours] hours.
**Notes: System will not automatically adjust to Daylight Savings Time.
North America requires negative offset from GMT e.g. -5.0 hours
Configure sntp default Sets the five timing sources to the default values shown in the get sntp
command shown at the beginning of this exercise.
Sequence :
set sntp default press Enter
SNTP default values will now be used.
Sequence:

18.0 Hitless Automatic Adaptive Modulation (HAAM)
This is a DragonWave licensed feature.
Note: HAAM cannot be invoked if ATPC or Redundancy is enabled.
The two principal modulation schemes used on the Horizon Quantum system are QPSK and QAM. QPSK
(the lowest order modulation scheme) is ideal for long distance, but has the lowest throughput capability.
Higher throughputs are achieved by using more complex modulation schemes e.g. 16-QAM, 32-QAM,
64-QAM, 128-QAM, 1024-QAM. The higher numbers indicate a progressively more complex scheme and
a higher bandwidth (throughput) capability e.g. 256-QAM is more complex than 128-QAM and provides
a higher throughput. More complex modulation schemes are more susceptible to noise and thus require
a stronger signal for the demodulator to accurately decode the data stream. Consequently, the more
complex the modulation scheme used, the shorter the distance limitation of the radio link.
The Horizon Quantum system can be configured to automatically switch to lower modulation schemes if
environmental conditions deteriorate to the point where a wireless link may otherwise fail. Quantum will
do this without causing a “hit” or losing data. This feature is called Hitless Automatic Adaptive Modulation
(HAAM).
All radio bands available with the Horizon Quantum support HAAM.
To change the modulation scheme, Quantum actually changes the system mode. The maximum system
mode and the minimum system mode is a range that is configurable. This means that the range of
modulation schemes that the system can switch through is configurable.
When HAAM is turned on, the default modulation range configured is the full range which is available for
the selected radio band. Regardless of the user configured system mode (includes modulation scheme),
the system switches to the highest modulation scheme in the configured range and it assumes the
maximum transmit power level associated with the highest available HAAM modulation scheme, unless a
lower power level has been configured by the user.
If weather conditions cause the Signal to Noise Ratio (SNR) to drop below the “Down SNR” threshold for
the modulation scheme in use (see Table 18-1 ), the current modulation scheme will switch to the next
lowest modulation scheme available. If the SNR continues to fall and drops below the “Down SNR”
threshold for that modulation scheme, the system will switch again to the next lowest modulation scheme.
If the SNR still continues to fall, the system will continue to downshift through all the available modulation
schemes until it reaches the lowest order scheme for the radio band in use, or the lowest configured.
Example: Initial modulation scheme is 256QAM. If the SNR falls below the “Down SNR” threshold for
256QAM, which is 30 dB, the system will switch to 128QAM. The “Down SNR” threshold for 128QAM is
27.17 dB. If the SNR drops below this new threshold, then a modulation downshift will occur again to
64QAM. The system will continue downshifting as the SNR thresholds are encountered until QPSK is
reached, or until the lowest configured scheme (system mode) is reached.
Note that in any dual modem configuration, if any one radio port drops below the “Down SNR” threshold,
both channels will switch together.
Table 18-1 Modulation Up/Downshift SNR Thresholds
Regular, 10*-12 performance Regular, 10*-12 performance
Mode Up SNR, dB Down SNR, dB Mode Up SNR, dB Down SNR, dB
QPSK 21 0 256QAM 34 30
16QAM 23 19.5 512QAM 36.7 31
32QAM 26 22 1024QAM 37.4 34.7
64QAM 29 24.2 2048QAM 0 35.1
128QAM 31.5 27.2
DragonWave Inc.
142
These values are common to all radio bands and channel bandwidths.
As conditions improve the SNR will increase. When the “Up SNR” thresholds are exceeded, then
modulation upshift will occur. This will occur in steps as the “Up SNR” threshold for each modulation
scheme is exceeded and until the 256QAM modulation scheme is reached, or the highest configured
scheme is reached. In dual modem configurations, both ports need to stay above the “Up SNR” threshold
before both upshift together.
HAAM is supported by all radio bands available to the Horizon Quantum, however, some jurisdictions
may not allow its use.
The following CLI commands are associated with HAAM:
• get haam • diagnose haam [up/down]
• get haam status • get haam system modes*
• set haam [on/off] • get/set ecfm bw-vsm
• set haam manual mode [on/off] • set haam mode range [highest] [lowest]
The CLI commands are demonstrated in the procedure below:
Procedure 18-1
Configuring Hitless Automatic Adaptive Modulation

Check if haam is on or off Displays the current on/off condition of Hitless Automatic Adaptive
Modulation (HAAM).
Sequence:
get haam press Enter
HAAM status: on/off
View haam status Displays the current status of the HAAM setting.
Sequence :
get haam status press Enter
HAAM status (User config) :off
HAAM status (Running config) :off
HAAM manual mode set to :off
Peer HAAM status :unknown.
Hitless Automatic Adaptive Modulation
143
Show a list of system modes This command returns a range of system modes configured by the
that can be used with haam user to use with HAAM followed by a list of all those system modes
available for HAAM. The example below shows that all modes
available are configured for use with HAAM, which is the default
setting.
Sequence:
get haam system modes press Enter
The system reponds:
Configured modes for HAAM :
hx50_67_qpsk hx50_157_16qam hx50_201_32qam
Available modes for HAAM in the system:

Select a range of modes that This command allows you to set a range of modes over which HAAM
haam will use and confirm the will operate, by selecting the highest and the lowest modes allowed.
setting by reviewing the The system will select any mode within that range, as signal conditions
HAAM system modes require, but will not exceed the highest mode, even though the
configured system mode may well be set to a higher value, and will not
go below the lowest mode in the range.
Sequence:
set haam mode range [highest mode] [lowest mode] press Enter
Example:
set haam mode range hx50_291_128qam hx50_157_16qam Enter
HAAM mode set successfully!
Confirm the selected range by reviewing the HAAM system modes.
Sequence:
get haam system modes press Enter
Configured modes for HAAM :
hx50_291_128qam
Available modes for HAAM in the system:

DragonWave Inc.
144
View haam status Displays the current status of the HAAM setting.
Sequence :
get haam status press Enter
HAAM set to :on
Configured HAAM modes:
hx50_291_128qam
Current running HAAM mode is :hx50_291_128qam
HAAM manual mode set to :off
Peer HAAM status :unknown.

Peer configured HAAM modes :unknown.
View the ecfm packet This command allows you to view the current ecfm packet information
information sent to switches whenever a change in bandwidth is made due to
HAAM.
Sequence:
get ecfm bw-vsm press Enter
===================================
Ecfm Vsm Configuration
===================================
Config Name User Config
--------------- -------------
Vendor OUI 00-00-0c
MEG Level 5
Wait Time 5 sec(s)
Period 10 sec(s)
Vlan Tag disabled
Vlan Id 0
Vlan Priority 0
Port List p1
Status enabled
145
Enable bandwidth vendor This command enables you to configure the content of ecfm packets
specific messaging sent to network switches in relation to changes in bandwidth produced
by HAAM. The associated ecfm PDU can cross the switching
boundary.
Sequence:
set ecfm bw-vsm press Enter
Vendor OUI (00-00-0c):

MEG Level [0-7] (5):
Wait Time (5) second(s):
Period [ 1sec (1) | 10sec (2) | 1min (3) ] (2):
Vlan Tagged [ enabled(1) | disable(2)] (2):
Port List (p1) ?
Vsm Status [ enabled(1) | disable(2)] (1):
===================================
Ecfm Vsm Configuration
===================================
Config Name User Config

--------------- -------------
Vendor OUI 00-00-0c
MEG Level 5
Wait Time 5 sec(s)
Period 10 sec(s)
Vlan Tag disabled
Vlan Id 0
Vlan Priority 0
Port List p1
Status enabled
Where MEG Level is the maintenance level as defined in Y.1731;

Wait Time is the time to wait before first bw-vsm message is
sent out after a modulation down switch.
Period is the time period at which bw-vsm messages are
periodically sent out to the selected port(s) (Port List)
when the system runs at below nominal modulation.
DragonWave Inc.
146
Configure haam This command turns the Hitless Automatic Adaptive Modulation
(HAAM) option on or off.
Note that HAAM cannot be invoked if ATPC or redundancy is enabled.
Sequence :
set haam [<on/off>]
Example:
set haam on and press Enter
HAAM is set to on!
Change requires a ‘save mib’ and ‘reset system’
Would you like to ‘save mib’ now? Enter Y(yes) or N (no):Y
A ‘reset system’ is required for the change to take effect.
Set the system to support the Use this command to put the system into manual switching mode (on)
diagnose haam [up/down] or automatic switching mode (off). Note that manual mode needs to be
command enabled at both ends of the link for manual switching to work. This
command works together with the diagnose haam [up/down]
command.
Sequence:
set haam manual mode [on/off]
Example:
set haam manual mode on and press Enter
Modem1 manual mode set :Success
Modem2 manual mode set :Success
Warning:Please make sure that the peer system has the same
configuration!
Manually change the Use this command to switch the modulation scheme up or down
modulation scheme for manually one modulation step at a time. The command set haam
operational checking or manual mode on must be invoked before this will work. Use the
troubleshooting. command set haam manual mode off once diagnostics have been
completed.
Sequence:
diagnose haam [up/down] and press Enter
Example : diagnose haam down press Enter
Diagnostic status :Success;
Previous: hx50_291_128qam;
Current: hx50_246_64qam.
HAAM interrupt status register: 0x1100044
147
Save changes to mib Saves the MIB to RAM. Perform this command to save setting
Sequence:
Reset the system to make Resets the system to save the settings to FLASH and restarts the
changes effective. system with the new settings taking effect.
Sequence:
Are you sure you want to reset? Y(yes) or N(no) press Y
DragonWave Inc.
148

19.0 Radio Redundancy
Redundancy capabilities are achieved with the Dual Modem variant of the Horizon Quantum connected to
two individual radios. The Horizon Quantum redundancy option relies on the Rapid Link Shutdown (RLS)
feature to determine when a redundancy switch needs to take place. The system can distinguish between
hardware failure and a link failure in order to perform an intelligent handover of traffic from one radio to
another.
The redundancy feature is intended for use with a RDRM (coupler) connecting two radios to a single
antenna with common polarization and will not work for links which are cross-polarized. Alternatively it
could be used with two radios connected to two antennas with common polarization. In this set-up, the
link path with the consistently higher RSL must be the one selected as the primary path. This means that
the wireless port with the higher RSL must be configured as the primary port.
If a redundancy switchover to the secondary path has occurred and the original path is now capable of
carrying traffic, the system will not automatically revert to the original path. Provided that the secondary
path continues to pass traffic successfully, traffic will remain on the secondary path. If the secondary path
fails due to rain fade, for example, the system will test to see if the primary path is capable of passing
traffic (no hardware faults). If there are no hardware faults the system will check the RSL level and if it is
below threshold (being affected by the same rain fade) a switch will not take place. However, if the RSL is
above threshold (capable of passing traffic) a switch will take place.
Be aware that if the primary path has suffered a hardware fault and as such its port is “marked” as faulty,
a switch will never take place if the secondary path fails. The hardware fault on the primary path must be
cleared and the faulty mark manually removed using CLI command remove faulty wireless ports
[wireless_port1|wireless_port2] before the primary is able to receive the traffic switch from the
secondary.
19.1 Primary and Secondary Path

Configuring redundancy requires that one of the Horizon Quantum/radio units has to be configured as the
“Primary” path and the other as the “Secondary” path. The terms “primary” and “secondary” relate solely
to the internal functions of the Horizon Quantum units and have no relationship to which radio is in stand-
by or which is carrying traffic. Either primary or secondary units may be active or in stand-by. The IDU
performs the redundancy controlling and switching functions. The radio or wireless port having the
highest RSL must be configured as the primary unit. The primary unit instructs the secondary Horizon
Quantum unit to attempt to create a link with its peer at the far end. If successful, this link becomes the
active link and the primary Horizon Quantum remains in a stand-by state unless the secondary unit link
fails and thus causes the primary radio to take over the traffic.
19.2 How and When Protection Switching Occurs

Protection switching is triggered as a result of massive data loss caused by link outage, power failure, or
hardware failure. Modem-blocks are constantly being transmitted across the link, whether or not Ethernet
frames are being transmitted. This continuous data stream is used as the trigger for Protection Switching
activation. Therefore, it is able to detect both hardware failures as well as link failures. Switching times are
in the order of 3 to 5 seconds.
In the case of hardware failure (example a faulty radio) the system "marks" the associated wireless port
as faulty. The system cannot automatically switch back to a wireless port which is "marked" as faulty.
When the radio on the faulty wireless port has been replaced, the user must manually remove the faulty
wireless port marking using CLI command remove faulty wireless ports
[wireless_port1|wireless_port2].
DragonWave Inc.
150
19.3 Recovery After Protection Switching

After a successful redundancy switch from a failed active link to a stand-by link has occurred, the system
will continue working on the stand-by link. Return to the original active link (when the stand-by link is
running satisfactorily) can only be achieved with a manual override. If, however, the stand-by link suffers
a failure, the system will attempt to switch back to the previously active link provided that the wireless port
of the previously active link has not been marked as a failure and the RSL is at an acceptable level. If the
wireless port has been marked as faulty a return to the previously active link will not occur. A switch back
to the active link will only occur after the faulty condition has been repaired and the user manually
removes the fault marking by issuing the CLI command remove faulty wireless ports
[wireless_port1|wireless_port2].
19.4 Forcing the Data Path to a Particular Link

It is possible to force the activity to follow a particular path. This option can be used during regular
operation of the link, or it can be used as a trouble-shooting tool. There are two CLI commands required
to achieve this. These are set switching algorithm manual followed by switch radio. If these
commands are issued when the wireless port and radio configured as the "primary" is carrying the traffic,
then the system will switch traffic to the path being supported by the wireless port and radio configured as
the "secondary" and vice versa. Activity will remain with the selected unit, regardless of path conditions,
until the user returns the system to normal operation using CLI commands switch radio and set
switching algorithm algorithm_based. Note that a manual switch can be applied to a wireless port that
is marked as faulty.
19.5 Checking the Status of a Redundant System

The CLI command diagnose redundancy returns the status of the redundant system.
Example: diagnose redundancy and press Enter. If there are no problems with the system the system
responds:
No hard faults on wireless_port1
If there is a problem, the system responds:
Hard faults on wireless_portx: (where x is 1 or 2)
One or more of the following will also be displayed indicating the problem being experienced:
• Radio faulty
• IF Tx Synth faulty
• IF Rx Synth faulty
• Modem flash pwr faulty
• Modem ADC pwr fault
• Modem FPGA err
• Modem not operational
• rsl below threshold
Radio Redundancy
151
19.6 Using the RDRM

The RDRM is designed to mount two individual
radios to a single standard antenna system. The
two IF connectors on the Dual Modem variant
Horizon Quantum are connected to the radios.
With the RDRM coupler, there is approximately a
6 dB difference between the RSL (Receive
Signal Level) of the radio on one RDRM port
compared with that of the radio on the other
RDRM port. For configuration purposes, the
radio with the higher RSL is termed the primary
path and the other radio is termed the secondary
path.
Figure 19-1 RDRM and System

Redundancy
The primary and secondary path radios are mounted to the RDRM in the positions shown in Figure 19-2.
Each face of the RDRM is marked with “Primary” or “Secondary”. Note the orientation of the polarity
marker on the edge of the RDRM. The figure shows the assembly orientated for horizontal polarity.
Radios must be mounted on the RDRM with the radio polarity markers matching those on the mounting
surfaces of the RDRM.
The primary path radio is connected to Port 1 and the secondary to Port 2 of the Horizon Quantum IDU,
also as shown in Figure 19-2.
Figure 19-2 Connecting RDRM Mounted Radios to Horizon Quantum IDU

DragonWave Inc.
152
19.7 Two Antennas and Two Radios

Redundancy can also be configured using two
separate radios on two separate antennas. In
this configuration, the RSLs of the two radios
are approximately the same. However, the
port connected to the radio with the highest
RSL should be configured as the primary
path.
Normally the system is configured to run on
the primary path. The secondary path is in hot
standby with its radio transmitter muted. If
there is any hardware failure on the primary
path, the system will switch over to the
secondary path.
Figure 19-3 Two Antennas, Two Radios and System Redundancy
19.8 Configuring Redundancy

Procedure 19-1
Configuring Horizon Quantum Redundancy

set which port will be the This command sets either port 1 or port 2 to be the primary wireless
primary port port (see Section 19.1).In this example port 1 will be set as the primary
port. Note: for a 2 radio plus 2 antenna installation, the port
having the higher RSL should be configured as the primary
wireless port.
Sequence :
set redundancy primary wireless port wireless_port1 and press
Enter

Primary wireless port is wireless_port1
Radio Redundancy
153
set the system capacity This command sets the system capacity parameter to the redundancy
option.
Sequence:
set system capacity 4 and press Enter
Programmed System Capacity: SingleModemRedundancy
Don't forget to set programmed frequency for both ports if not set
yet.
Select the switching The command allows you to select the redundancy switching method
algorithm. to either manual or algorithm based. In this example we select the
algorithm based option. The system will automatically switch to the
secondary port in the event of a failure on the primary port, or vice
versa.
Sequence :
set switching algorithm algorithm based and press Enter
Redundancy switching algorithm is set to: algorithm based
Selecting the frequency After the radio band has been previously configured, the primary and
channel for each port the secondary radios need to be configured with the frequency at
which they will be operating.
Sequence :
set programmed frequency 1 and press Enter
(this sets the frequency for port 1 to frequency index 1)
1 460000 1625000 10735000 11225000
All Frequency in KHz

set programmed frequency 1 wireless_port2 and press Enter
(this sets the frequency for port 2 to frequency index 1)
1 460000 1625000 10735000 11225000
All Frequency in KHz

DragonWave Inc.
154
Sequence:


Sequence
Would you like to 'save mib' before reset? Enter Y(yes) or N (no):y
Saving Mib...Mib saved successfully.
Are you sure you want to reset? Enter Y(yes) or N (no): y
The system will proceed to reset.
You will have to log on again to regain access.
Radio Redundancy
155
19.9 Removing a Faulty Wireless Port “Marking”

When a redundant switch occurs due to a hardware fault (example: faulty radio, faulty IF cable) the
wireless port associated with the failed hardware is automatically “marked” as faulty by the system.
Before a marked wireless port can, once again, carry traffic, the hardware fault must be corrected and
then the faulty marking manually removed.
Procedure 19-2
Removing a faulty wireless port marking after a hardware failure has been resolved.

Determine if the redundant There are a number of CLI commands that will return details about the
switch was caused by a condition of the system and which may show the cause of a redundant
hardware fault. switch. These are get alarms, diagnose redundancy and get faulty
wireless ports.
Sequence:
get alarms press Enter
Network Interface :
Ethernet Link Down Ports: p1, p2, p4, p5, p6, p8
System:
No Alarms.
Redundancy Alarms:
secondary Port Is Active.
primary Port Faulty.
secondary Port Faulty.
Modem 1:
Modem receiver loss of signal.
Modem 2:
No Alarms.
Radio 1:
No Alarms.
Radio 2:
No Alarms.
Frequency File :
No Alarms.
DragonWave Inc.
156
Sequence:
diagnose redundancy press Enter
The system resonds (Example):

If there is a problem, the system responds:
Hard faults on wireless_portx: (where x is 1 or 2)
One or more of the following will also be displayed indicating the

problem being experienced:
• Radio faulty
• IF Tx Synth faulty
• IF Rx Synth faulty
• Modem flash pwr faulty
• Modem ADC pwr fault
• Modem FPGA err
• Modem not operational
• rsl below threshold
Remove the faulty marking on This command returns the wireless port(s) that has been marked as
a wireless port that has faulty.
caused a redundant switch Sequence:
due to a hardware fault. Note get faulty wireless ports press Enter
that the cause of the The system responds (Example):
hardware failure should be Faulty wireless ports:
cleared first. wireless_port1
wireless_port2
remove faulty wireless ports wireless_port1 press Enter

Successfully removed faulty wireless_port1.
remove faulty wireless ports wireless_port2 press Enter
Successfully removed faulty wireless_port2.

20.0 System Redundancy
The Horizon Quantum system consists of a modem node unit (IDU) plus a radio unit (ODU). In a
redundancy set-up, a system node can be configured to control/monitor its own radio plus that of its
redundant partner. Similarly, each node can communicate with its partner node and determine the status
of its network traffic. This approach allows the redundant system to switch data from one radio to the
other, in the case of a radio or other link failure, and switch the data stream between nodes, in the case of
a port or node failure. The system can also be configured to switch a complete system (both node and
radio)..
20.1 Hot Stand-by (HSB)

HSB is a Quantum redundancy feature. When a system is configured for HSB, there are two Quantums
on each end of a link. The two local partners constantly communicate with each other via a partner port
and exchange control information with each other. If one Quantum fails, then the partner Quantum will
take over. A dedicated partner control port connection is mandatory for HSB to work properly.
At any time, only one node (the modem portion of the Horizon Quantum) of the redundant Horizon
Quantum pair, is in control of the radio transmitter/receivers in both systems. Switching between Quantum
systems is decided by the node in control, based on the fault condition on the wireless link and the front
panel Ethernet connection link status.
Switching traffic between nodes (if there is a node or port failure on the active node) is determined by the
“switch” configuration of the system and the link status of the front panel data port.
Note: ATPC, RSTP/MSTP, HAAM, or ECFM cannot be enabled at the same time as HSB.
20.2 Primary and Secondary Quantum

Configuring redundancy requires that one of the Quantum units has to be configured as the “Primary” unit
and the other as the “Secondary” unit. The terms “primary” and “secondary” relate solely to the internal
functions of the Quantum units and have no relationship to which Quantum unit is in stand-by or which is
carrying traffic (active). Either primary or secondary units may be active or in stand-by. The “active” unit
performs the redundancy controlling and switching functions.
On power up, the unit which boots up first tries to establish the link with its peer. If it is successful in
establishing the link, then the partner unit will go into standby state. This standby unit will be in this state
until the active unit fails and thus causes the standby unit to take over user traffic (node switch) and
become the active unit.
Also, on the wireless link side, if the radio of the active unit fails, for whatever reason, the radio of the
partner takes over and establishes a wireless link depending on the redundancy switch configuration
(radio switch).
20.3 How and When Protection Switching Occurs

Protection switching (node switching) is triggered as a result of a preset level of data loss caused by a link
outage, power failure, hardware failure, or a front panel HSB port failure. Partner nodes (two nodes
connected to the same switch) are interconnected with a dedicated Ethernet port for the proper operation
of the function. In HSB configuration, two types of interconnection ports need to be configured. One is the
dedicated partner control information exchange connection, and the other is for data re-routing.
The partner nodes communicate constantly over the partner control connection to indicate their status.
The standby node gets notified as soon as the active node fails, causing the standby node to become
active and take over the traffic (i.e. a protection switch). The system is able to detect both hardware
failures as well as link failures.
There are two types of HSB switching:
DragonWave Inc.
158
1. Radio only switching:

When modem block errors exceed the user configured HSB link monitor parameter
threshold, the active Quantum will mute its radio transmission, re-route its ingress
Ethernet traffic (from user network) to its HSB partner Quantum via the HSB Ethernet
link, and tells the standby Quantum’s radio to start transmitting.
2. Whole node switching:
When the active Quantum unit has a power failure or the Ethernet connection to the user
network is down, the active Quantum will inform the subtending switch appropriately, then
the active Quantum is switched to standby and the Quantum previously operating as the
standby becomes active.
20.4 HSB Switching Action

Wth HSB configuration, at any given time, only one unit is in service and the other is in standby. The user
can configure how the HSB combination informs the subtending switch by using the CLI command:
set redundancy standby enet state [on | off | pulse].
• on - The Quantum keeps the HSB Ethernet port on all the time regardless if it is in the active or
standby state. It is up to the subtending switch to make sure traffic is only forwarded to the active
Quantum
• off - The standby Quantum will keep its HSB Ethernet port down, so that the subtending switch
does not forward any traffic to the standby Quantum
• pulse - Before the active Quantum goes into the standby state, it brings the HSB Ethernet port
down for a short period of time, then brings it back up. This is to tell the subtending switch not to
forward any traffic to the newly created standby Quantum
20.5 Recovery After Protection Switching

After a redundancy switch has occurred, return to the original path is achieved with a state switch
command. If, however, the path has been switched from previously active to stand-by, then, if a link
failure or outage on the active path occurs the data path will automatically switch back (reverting) to the
previously active path, provided that the system parameters have been set to allow the switch back.
20.6 Forcing the Data Path to a Particular Link

It is possible to force the activity to follow a particular path. This option can be used during regular
operation of the link, or it can be used as a trouble-shooting tool. The CLI command is:
set redundancy switch mode [force_active/force_standby/auto].
Selecting “force_active” on a unit will force the unit to remain active all the time. i.e. if there is a problem
on the Ethernet port carrying user traffic, the unit does not switch. The node remains active all the time.
Selecting “force_standby” will force the unit to remain in standby all the time. In this configuration both
the radio and the node will not be used for carrying user traffic. This is mainly intended for maintenance
purposes.
In “auto” mode, if a failure condition occurs on the Ethernet side, the standby unit switches to “active”
and it takes over user traffic. Similarly, any of the primary and secondary radios can establish a wireless
link in “auto” mode.
System Redundancy
159
20.7 Redundancy CLI Commands

20.7.1 Redundancy Mode:
The redundancy mode is set for both of the units at each end of the link. Set the appropriate units as
either primary or secondary and set the appropriate mode of HSB This command is to be issued on all
4 units.
Command syntax:
get/set redundancy mode [off | primary_hsb | secondary_hsb | primary_radio | secondary_radio]
Note : (hsb = hot stand-by)
20.7.2 Redundancy Switch Mode

The options for redundancy switch mode are force_active, force_standby and auto. Selecting
“force_active” will force the Horizon Quantum unit to remain active (carry the traffic ) all the time and it
will remain there. Traffic will not be switched to the standby link, even if the active link fails. Similarly,
selecting “force_standby” will force the Horizon Quantum unit to remain as standby and it will not switch
away from that unit. Neither the unit nor its radio will be used.
Command syntax:
set redundancy switch mode [force_active | force_standby | auto]
20.7.3 Redundancy state switch

When the redundancy override is set to “auto”, you can toggle between both Horizon redundancy states
by issuing the redundancy state switch command on the active unit only. There is only one choice, that
being “on”. Repeating the command gives the toggling action.
If this command is issued, then the active link will become the stand-by link. i,e user traffic switches
over to the other unit. This command is applicable only on the active unit.
Command syntax: set redundancy state switch on
20.7.4 Redundancy standby enet state

The Enet state determines the action of the Ethernet port on the standby unit, as seen by an external
Ethernet switch.
“On” means that the Ethernet Link will remain in the “on” state on the standby unit.
“Off” means that the Ethernet Link will turn “off” on the standby unit, resulting in the external Ethernet
switch seeing the equivalent condition of the Ethernet cable being disconnected.
“Pulse” means that the configured HSB ports of the standby Horizon Quantum will “pulse” or “toggle”
from ‘off’ to ‘on’ in order to speed up the Ethernet switch switching algorithm. The payload port of the
standby unit will pulse and the external switch will interpret this pulsing and react by accelerating its
algorithm to determine the link over which to send the data traffic.
Command syntax: get/set redundancy standby enet state [on | off | pulse]
DragonWave Inc.
160
20.7.5 Redundancy link monitor parameters

The Horizon redundancy system needs to know how long a stand-by unit should wait when its active
partner is beginning to fail, before it takes over the traffic. The redundancy link monitor parameters
provide this information. Note: It is recommended that the redundancy link monitor parameters
remain at their default values.
Command syntax: (sets the link monitor parameters for HSB when 2 parameters are entered).
get/set redundancy link monitor parameters [fault period(msec)] [fault threshold(%)]
Command syntax: (sets the link monitor parameters for radio redundancy when 10 parameters are
entered).
set redundancy link monitor parameters [1-primary_radio | 2-secondary_radio] [mk erred blks]
[brk erred blks] [mk samples] [brk samples] [mk sample time] [brk sample time] [
brk sample rst time] [fault period(msec)] [fault threshold(%)]
20.7.6 Redundancy link switch parameters

When a system is in the process of switching from active to stand-by, the time that the system needs to
wait, to confirm if the stand-by unit can establish a link, before switching, is provided by the redundancy
link switch parameters. Note: It is recommended that the redundancy link switch parameters
remain at their default values.
Command syntax:
get/set redundancy link switch parameters [prim. time in active state] [prim. switch error thresh]
[second. time in active state] [second. switch error thresh]
Period is in mSec and threshold in percentage.
20.7.7 Redundancy Ethernet port config

For HSB to work properly, the intra-node partner control port connection and HSB IPG ports need to be
configured correctly.. One dedicated intra-partner control communication connection is needed, and up
to three HSB IPG data connections can be configured.
The partner control inter-connection port needs to be in its own IPG. To configure the intra-partner
control port, the CLI command is: set partner.
To read back partner control connection, the command is: get partner
To configure the HSB data connection, the command is: set redundancy ipg.
For example, to configure p7, p8 and dp4 in one HSB IPG, the command is:
set redundancy ipg hsb 1 enable user-port p7 inter-port p8 data-port dp4
When more than one HSB IPG group is needed, the user can configure the HSB switch condition:
• when any one of the HSB IPG’s has a link problem
• or, when all of the HSB IPG’s have link problem.
Command syntax: get/set redundancy port config
20.7.8 Redundancy Status

The status (active, stand-by, link up/down) of the primary and secondary Horizon units can be
determined with this command.
Command syntax: get redundancy status
System Redundancy
161
20.8 Redundancy Switching and Management Options

This section explains some typical HSB deployment scenarios. With HSB, the Quantums can be
managed with in-band management or out-of-band management.
20.8.1 HSB Configuration With In-band Management

You can use In-Band Management with HSB configuration. For example, one deployment scanerio is:
• In-band management
• P7 is connected to user network
• P8 is used as HSB inter-connection
• DP4 is used to carry over-air traffic
• P4 is used as partner port
• Set P4 as partner port on both primary and seconardy HSB Quantum unit with CLI command set
partner
• The partner control port needs to be in its own IPG, i.e. there should be no other Enet port in the
same IPG as the control port. Related CLI command is set ipg config.
• Set P7, P8 and DP4 as one HSB IPG group with command set redundancy ipg hsb 1 enable
user-port p7 inter-port p8 data-port dp4
• Set P7, P8 and DP4 as network management interface with command set network
management interface
With this configuration, there are different HSB switching scenarios as depicited Figure 20-1, Figure 20-2
and Figure 20-3.
DragonWave Inc.
162
Figure 20-1 Over-the-air Path Failure Causes HSB Switch

System Redundancy
163
Figure 20-2 Node failure causes HSB switch

DragonWave Inc.
164
Figure 20-3 Node failure causes HSB switch
20.8.2 HSB Configuration With Out-of-band Management – Case 1

You can use out-of-band Management with HSB configuration. For example, one deployment scanerio is:
• Out-of-band management
• P6 is connected to user network for Quantum management
• P7 is connected to user network for user data
• P8 is used as HSB inter-connection
• Set P4 as partner port on both primary and seconardy HSB Quantum unit with set partner
command
• The partner control port needs to be in its own IPG, i.e. there should be no other Enet port in the
same IPG as the control port. Related command is set ipg config.
• Set P7, P8 and DP4 as one HSB IPG group with command set redundancy ipg hsb 1 enable
• Set P6 as network management interface with command set network management interface
With this configuration (Case 1), there are different HSB switching scenarios as depicited in Figure 20-4,
Figure 20-5 and Figure 20-6.
System Redundancy
165
Note: With Case 1 (see Figure 20-4, Figure 20-5 and Figure 20-6) when Data Encryption is enabled
on a hot standby link configuration, it is not recommended to have all four Quantum units with
their own out-of-band management connections.
Figure 20-4 Case 1 - Over-air failure causes HSB switch (OOB Management)
DragonWave Inc.
166
Figure 20-5 Case 1 - Node failure causes HSB switch (OOB Management)
System Redundancy
167
20.8.3 HSB Configuration With Out-of-band Management – Case 2

Only one management port is connected to the redundant Quantum pair on each end of the link, rather
than two connections as illustrated in Case 1 (see Section 20.8.2).
For example, one deployment scanerio is:
• Out-of-band management with only one primary or secondary management connection
• P6 is connected to the user network for Quantum management
• P7 is connected to the user network for user data
• P8 is used as the HSB inter-connection
• P4 is used as the partner port
• Set P4 as partner port on both primary and seconardy HSB Quantum units using set partner
command
• Set P7, P8 and DP4 as one HSB IPG group using command set redundancy ipg hsb 1 enable
DragonWave Inc.
168
• On the node having the management connection, use CLI command set network management
interface to configure P6 and P4 as the network management interface and also configure P4 as
the partner port.
• On the node having the management connection, use CLI command set ipg config to configure
P4 (partner port) and P6 to the same IPG group.
• On the node NOT having the management connection, use CLI set network management
interface to configure P4 (partner port) as the management port. Also, using CLI command set
ipg config configure P4 into a dedicated IPG group. There should be no other Enet port in the
same IPG as P4.
See Figure 20-7, Figure 20-8 and Figure 20-9 for illustrations of different HSB switching scenarios.
System Redundancy
169
DragonWave Inc.
170
Figure 20-9 Case 2 – Over-air failure causes HSB switch (OOB Management)
System Redundancy
171
20.8.4 HSB Configuration With More Than One HSB Port

If needed, you can configure more than one HSB IPG. Up to three HSB IPGs can be configured. This is
useful when the required throughtput is more than 1Gbps, for example when BAC is enabled. The
following example illustrates the Out-of-band management option. To use In-band management, you
need to change the network management interface to include all HSB front panel ports and HSB data
ports.
• Out-of-band management
• P3 is connected to user network for Quantum management
• P1, P4, and P5 are connected to user network for user data
• P2, P6, and P7 are used as HSB inter-connection
• DP2, DP3, and DP4 are used to carry over-air traffic for each HSB IPG group
Figure 20-10 HSB Configuration With More Than One HSB IPG Group
DragonWave Inc.
172
Procedure 20-1
Configuring Redundancy
Note: A number of commands prompt you to save mib and may also prompt you to reset system. This
action need not be applied until all parameters have been configured as per the procedure below.

Configure the redundancy This command configures the IPG group. Up to three HSB IPG groups can
IPG group. be configured. This configuration includes the user port (connected to the
external switch), interconnect port (carries data traffic between primary and
secondary node) and the data port (a dp wireless port which carries
redundancy traffic to the peer node). This needs to be configured on both the
primary and secondary nodes.
Sequence:
set redundancy ipg [hsb[1 – 3] [enable|disable] user-port [p1 – p8]
inter-port [p1 – p8] data-ports[dp1 – dp4]] press Enter
Example:
set redundancy ipg hsb 1 enable user-port p2 inter-port p3 data-ports
dp2 press Enter
The ipg config will be changed.
Current ipg config:
----- ------- -----------
ipg1 enable p5
ipg2 disable
ipg3 disable
ipg4 disable
ipg5 disable
ipg_x2 disable
ipg_hsb1 enable p7,p8,dp1
New ipg config:

----- ------- -----------
ipg1 enable p5
ipg2 disable
ipg3 disable
ipg4 disable
ipg5 disable
ipg_x2 disable
ipg_hsb2 enable p6
Continue? Enter Y(yes) or N(No): y

redundancy ipg hsb1 has been set.
Note: you need to save l2swmib and save mib for this command to
become active.
System Redundancy
173
Configure the port that will This command configures the port to be used to communicate
be used as the control port control signals between the primary and secondary nodes. This
between the primary and needs to be configured on both primary and secondary units. Once
secondary nodes configured the ports need to be interconnected with Ethernet cable.
Sequence:
set partner [p1 – p8] press Enter
Example:
set partner p1 press Enter
Configure the redundancy This command allows you to set the system as the primary or
mode for one of the partners secondary node, for HSB redundancy modes. The example shows
of the redundant pair and setting one of the partners as the primary. Repeat with secondary
repeat for the other commands for the secondary node.
Sequence:
set redundancy mode [primary_hsb | secondary_hsb | off]
press Enter
Example - Select one of the two partner nodes and configure it as
the primary_hsb node:
set redundancy mode primary_hsb press Enter
System redundancy mode is set to :primary_hsb
Would you like to 'save mib' now? Enter Y(yes) or N (no):
Configure if any one or all This command determines how the system will respond to the failure
ports are down before a of a single, or of all ports. A value of 'all' will cause the node to
redundancy switch will take switch when 'ALL' redundancy ports are down. A value of 'any' will
place. cause the node to switch when 'ANY' redundancy port is down.
Configure both primary and secondary nodes.
Sequence:
set redundancy port config [all | any] press Enter
The system responds (example for “all”):
Redundancy port config set to :all
for redundancy ports :p1,p2,p6
Configure the way the node For a dual modem system only (system capacity 2), this command
reacts to a radio port failure will configure the system to cause a redundancy switch when one or
all radio ports are down. A value of 'all' will cause the node to switch
when 'ALL' modem ports are down. A value of 'any' will cause the
node to switch when 'ANY' modem port is down. Configure both
primary and secondary nodes.
Sequence:
set redundancy wireless port config [any | all] press Enter
The system responds (example for “any”):
Redundancy modem config set to 'any'
DragonWave Inc.
174
Set up the network This command selects the network management interface (port) for
management interface managing the system. The example demonstrates out-of-band
management. Set up both primary and secondary nodes and
connect the ports to the management network.
set network management interface press Enter
Port List (p7,p8,dp1) ?p3
Apply the setting to system immediately, and automatically save
Mib. (WARNING: This can affect current management session)
Standby enet state This command allows the user to program the required action on the
standby redundancy port group when the node switches from active
to the stand-by state. The selection of available options of on, off or
pulse, depends on the capability of the external switch. Configure
both primary and secondary nodes.
Sequence:
set redundancy standby enet state [on|off|pulse] press Enter
Redundancy standby enet state is set to :off

Redundancy switch mode This command allows the user to force the state of the redundant
link. Force_active allows you to make the node the active node. It will
always stay in that state even in the event of a link failure. Similarly
force_standby allows you to force the node into the standby status. It
will always stay in that state even in the event of a link failure.
Selecting auto will enable the system to perform a redundancy switch
when conditions require it. Configure both primary and secondary
nodes.
Sequence:
set redundancy switch mode
[force_active |force_standby |auto ] press Enter
Redundancy switch mode is set to :auto
Sequence:

System Redundancy
175
Save changes to the layer 2 Saves the changes to the layer 2 switch parameters to the l2swmib
software mib
Sequence:
Reset system A system reset is required to activate this feature. This is traffic
affecting.
Sequence
press Y
regain access.
DragonWave Inc.
176

21.0 Peer Link Compatibility Mode (PLCM)
The Quantum Release 1.1.5 can be configured to be compatible with and/or behave like a Horizon Duo
running software release 1.3 or greater. The configuration for each is slightly different.
Note that Quantum and Duo interoperability in a mixed link is only supported in Releases 1.1.5 and
1.1.5.1. The Duo Port Configuration option of the PLCM feature, which is described in Section 19.2, is still
supported in higher releases.
21.1 Quantum and Duo Interoperability

This option allows interoperability between the Quantum and all modem options (single modem, dual
modem, single radio, dual radio etc.) of Duo platforms. Note that no additional configuration is required of
the Duo system.
The Quantum must be configured for “Peer Link Compatibility Mode” (PLCM) in order to interoperate with
a Duo system. Configuration can be performed via CLI, SNMP, or the Web interface.
The following provisos apply:
• For a Quantum, or Duo, dual radio installation, both radios must be of the same type (R4 or R5)
at one end. Dual radios at the opposite end of the link must also be of the same type but do not
have to be the same type as those at the near end. E.g. Near end has two R4 radios, far end can
have two R4 radios, or two R5 radios.
• Since the type of radio(s) (R4 or R5) may be different at each end of a Quantum – Duo
interoperating link, the available radio band structures will likely be different for each. The
selected radio bands at each end of the link will have to overlap so that a common frequency
channel(s) is available.
• Since an R5 radio is, by default, a high power radio, if it is communicating with a standard power
R4 radio, then the R5 radio will need to have its output power reduced to match that of the R4
radio.
• If the Duo is configured for VLAN tagging, then the Quantum also needs to be similarly
configured.
• When configured for PLCM, the Quantum system does not support BAC, XPIC, HAAM, or the
“Friendly” mode network protocol.
DragonWave Inc.
178
21.1.1 Configuring PLCM – Duo Interoperability - using CLI

Procedure 21-1
Configuring PLCM
login Log in as a NOC user or the Super User.

Enable PLCM This command leads you through the process of configuring Peer Link Compatibility
Mode (PLCM) for Duo Interoperability. The example, below, illustrates accepting the
current settings (shown in brackets at the end of each line). To make changes, enter
the number that relates to the desired option shown on each line and press Enter. Note
that applying any changes will force a save mib and system reset, which is traffic
affecting.
Sequence:
set peer link compatibility press Enter
Comment – the next step selects the type of system located at the far end of the link, in
this example a Duo
Wireless link operation type [Quantum (1)| DUO(2)] (2):
Software version of wireless peer: [DUO1.3.xx (1)] (1):
Comment – the following steps allow you to configure the Quantum to match the
configuration of the Duo at the far end.
Bearer (Customer) Ethernet Traffic Port [p1(1) - p8(8)] (7):
Management Interface Type : [Inband{port1} (1) | OutOfBand{port2} (2)] (2):
OutOfBand Management Interface Port [p1(1) - p8(8)] (8):
Implement DUO concept "port 2 extended" on OOB port [yes (y) | no (n)] (n):
VLAN tagging set to "on" in peer DUO [yes (y) | no (n)] (n):
************************************************************
Applying this setting will save MIB and RESET the system immediately
***************************************************************
Do you want to Continue? Enter Y(Yes) or N(No):
PLCM settings remains unchanged.
Note that if the out-of-band management port is changed, you will lose management
capabilities on the port that you are currently using. Remember to reconnect the
management network to the newly configured port.
Peer Link Compatibility Mode (PLCM)
179
View current status of This command returns the current status of Peer Link Compatibility Mode (PLCM).
PLCM
Sequence:
get peer link compatibility press Enter
System Peer link compatibility mode is set to: [DUO]
Peer link software version is set to: [DUO1.3.xx]
Peer link management interface is set to: [out of band].
Ethernet Traffic Port is set to [p7].
Network management Port is set to [p8].
Management vlan tagging is set to [off]
Management vlan id [1]
Management vlan priority [0]
PLCM Supported? Description

==== ======== =========
QCM1 Yes Wireless Peer is a Quantum, software version 1.x
DUO1.3 Yes Wireless Peer is a DUO unit running software
version 1.3.x
Ensure that the Use the following commands to compare the network settings on the Quantum with
those configured on the Duo. If there are differences, reconfigure the Quantum to
Quantum has the same
match the Duo settings.
network configuration
as the peer Duo get peer link compatibility – if “port 2 extended” is on Duo, ensure that
Quantum matches
get enet config – ensure that data and management ports are enabled
get vlan config – ensure that data port is set as “trunk”
- management port set as “access” port
- vlan ID and Priority set properly
get ipg config – ensure that ipg1 is set as data port
- ensure that ipg2 is set for management
get network management interface – ensure that management port is set properly as
either in-band, or out-of-band management to match that of the Duo.
DragonWave Inc.
180
21.2 Duo Like Configuration

Provided that a Quantum system is installed at both ends of the link, one Quantum system can be
configured to behave like a Duo. This is for the benefit of those customers who wish to maintain the
familiar “look and feel” of a Duo after the system may have been upgraded to a Quantum.
Note: the system is still a Quantum and can be further configured to include any other Quantum only
features.
21.2.1 Configuring PLCM – Duo Like Configuration - using CLI

Procedure 21-2
Configuring PLCM
login Log in as a NOC user or the Super User.

Enable PLCM This command leads you through the process of configuring Peer Link Compatibility
Mode (PLCM). The example, below, illustrates accepting the current settings (shown in
brackets at the end of each line). To make changes, enter the number that relates to
the desired option shown on each line and press Enter.
Note that applying any changes will force a save mib and system reset, which is traffic
affecting.
Sequence:
set peer link compatibility press Enter
Comment – the next step determines what type of system you have at the far end of the
link, in this example a Quantum
Wireless link operation type [Quantum (1)| DUO(2)] (1):
Comment – the next step determines if you want the Quantum at the near end to
simulate a Duo. Answering no (n) will exit the process.
Implement a DUO compatible configuration [yes (y) | no (n)] (n): y
Comment – the next steps allow you to configure the near end Quantum to act like a
Duo.
Bearer (Customer) Ethernet Traffic Port [p1(1) - p8(8)] (7):
Ethernet Traffic Port Default Vlan Id[1 - 4095] (1):
Management Interface Type : [Inband{port1} (1) | OutOfBand{port2} (2)] (2):
OutOfBand Management Interface Port [p1(1) - p8(8)] (8): 3
Implement DUO concept "port 2 extended" on OOB port [yes (y) | no (n)] (n):
VLAN tagging set to "on" in peer DUO [yes (y) | no (n)] (n):
************************************************************
Applying this setting will save MIB and RESET the system immediately
Peer Link Compatibility Mode (PLCM)
181

***************************************************************
Do you want to Continue? Enter Y(Yes) or N(No):
Are you sure you want to reset? Enter Y(yes) or N (no):y
Make sure Ethernet port[p3] is connected if management

access is required after reset.
****DUO Network Management concept of "Network Protocol Friendly"

is not supported in Quantum.****
Configuring eth port...
Configuring isolated port group.....
Configuring VLAN...
HAAM, XPIC and BAC featues are disabled
Configuring RLS Port ...
Resetting the system now.
View status of PLCM This command returns the current status of Peer Link Compatibility Mode (PLCM).
after the system reset
Sequence:
get peer link compatibility press Enter
System Peer link compatibility mode is set to: [QTM]
DUO compatible configuration is set to: [on]
Peer link management interface is set to: [out of band].
Ethernet Traffic Port is set to [p7].
Ethernet Traffic Port Default vlan ID is set to [1]
Network management Port is set to [p3].
Management vlan tagging is set to [off]
Management vlan id [1]
Management vlan priority [0]
PLCM Supported? Description

==== ======== =========
QCM1 Yes Wireless Peer is a Quantum, software version 1.x
DUO1.3 Yes Wireless Peer is a DUO unit running software
version 1.3.x
DragonWave Inc.
182
Ensure that the Use the following commands to compare the network settings on the Quantum with
those configured on the Duo. If there are differences, reconfigure the Quantum to
Quantum has the same
match the Duo settings.
network configuration
as the peer Duo get peer link compatibility – if “port 2 extended” is on Duo, ensure that
Quantum matches
get enet config – ensure that data and management ports are enabled
get vlan config – ensure that data port is set as “trunk”
- management port set as “access” port
- vlan ID and Priority set properly
get ipg config – ensure that ipg1 is set as data port
- ensure that ipg2 is set for management
get network management interface – ensure that management port is set properly as
either in-band, or out-of-band management to match that of the Duo.
21.3 Configuring PLCM using SNMP

Review the Quantum SNMP document for more details on configuring PLCM using the SNMP protocol.
22.0 System Management
The Horizon Quantum system can be fully managed locally or remotely. Horizon Quantum supports serial
and Telnet access, SNMP management and a Web interface accessible through the IP network. The
entire Command Line Interface (CLI) command set is available through Telnet. The entire list of system
parameters is available through SNMP access. The Web interface provides access to system
configuration and performance parameters.
Management traffic can be configured as in-band or out-of-band.
In-band management traffic is mixed with customer traffic. Out-of-band management traffic is carried
separate from customer traffic.
To configure the management interface use the procedure described in Section 5.0.
NOTE: Since R1.3.7, up to 5 SSH and telnet sessions (i.e., up to 3 SSH sessions and 5 telnet sessions
respectively, but totally no more than 5 sessions) are allowed to run simultaneously.
22.1 Telnet Access

Once correctly configured, the Horizon Quantum is accessible through a Telnet session using Super
User, NOC and Admin level user accounts. Refer to Appendix A for details of CLI commands. The
Horizon Quantum system can be completely configured, tested and managed through a Telnet session.
The Telnet function is enabled by default but can be disabled within the Horizon Quantum system.
Procedure 22-1
Configuring Telnet Access

get telnet access Returns the status of Telnet access (on by default)
Sequence :
get telnet access press Enter
telnet access is [on/off]
set telnet Enables or disables Telnet access.
Sequence :
set telnet [on/off] press Enter
Service modification passed
save mib Saves the MIB to RAM. Perform this command to save configuration
Sequence:

DragonWave Inc.
184
22.1.1 Secure Shell Access Security

Telnet sessions over a network such as the Internet are not secure. User names and passwords, as well
as commands and system responses, are transmitted in clear text during a Telnet session. A secure shell
(SSH) protocol can be enabled in the Horizon Quantum system to ensure that access to the units is
restricted to authorized clients. Horizon Quantum uses the Secure Shell SSH2 server program to create
the secure environment for Telnet sessions. SSH2 is a recognised industry standard, encrypting, security,
program. When enabled, SSH encrypts the entire Telnet session, including all usernames, passwords,
commands and responses from the system.
A Secure Shell client program needs to be installed on any computer which is to be used to manage a
Horizon Quantum system with SSH enabled. A free SSH client program (PuTTY) is available on the Web.
Note that both SSH and Telnet can be enabled at the same time. To ensure security, once SSH has been
enabled, disable Telnet.
Also note that the Web server must be enabled on the Horizon Quantum before SSH can be enabled.
22.1.2 Configuring Secure Shell (SSH)

Use the following procedure to manage the SSH feature of the Horizon Quantum system.
Procedure 22-2
Configuring Secure Shell (SSH)

get ssh server Returns the status of the Secure Shell SSH2 server.
Sequence :
get ssh server press Enter
ssh server is [on/off]
set ssh server Enables or disables the Secure Shell SSH2 server.
Sequence :
set ssh server [on/off] press Enter
Note: The Web server must be ON before the SSH server can be enabled.
A system reset is required before SSH will be invoked.
System Management
185
Sequence:


Sequence
press Y
regain access.
DragonWave Inc.
186
22.2 Alarms List

Use the CLI command get alarms to display a list of active alarms. Also use get diagnostics to show a
list of critical alarms and suggested steps to resolve the alarm. Alternatively, alarms are listed on the
Alarms page of the Web interface (see Section 22.3). Active alarms are clearly indicated. The diagnostics
feature is also available on the Web Diagnostics page.
The following shows the available System, Ethernet Port and Wireless alarms available on the Web page:
System Management
187
22.3 Web Interface

This section provides an overview of the Horizon Quantum Web interface. To use the Horizon Quantum
Web-based interface, you need a PC with a Web browser (Internet Explorer 5.5 or higher, or Netscape
4.5 or higher) and IP access to the Horizon Quantum system. For the PC requirements refer to the
browser vendor documentation.
The Horizon Quantum Web interface is disabled by default. Enable the Web interface on both systems by
logging on using Telnet and issuing the CLI command set web server on press Enter.
22.3.1 Features
The following list describes the features of the Horizon Quantum Web interface:
• Remote system availability - the Web interface can be used on any computer having
IP access to the Horizon Quantum system.
• Runs in a standard Web browser - the Web interface runs on Internet Explorer 5.5 or
higher or Netscape 4.5 or 4.7
• Requires no local software - the Web interface runs in the browser. All necessary
software is stored on the Horizon Quantum system.
• Controlled access levels depending upon login type - Super User, NOC and Admin
level functions are supported based upon login type.
• Password protected.
• SSL Web server - provides encryption for the Web session and verifies that the Web
browser is indeed connecting to a Horizon Quantum system.
• Near real-time view of the network - the auto-refresh capability allows real-time
monitoring of the Horizon Quantum link.
22.3.2 Connecting to the Web Interface

You may connect to the system through an IP network, either from a location which is local to the Horizon
Quantum Ethernet connection, or through a remote connection which has IP access to the Horizon
Quantum system.
Notes:
User groups may be configured for mandatory use of HTTPS (SSL). If configured, those users (Super
User, Noc, Admin) are required to access the Horizon Quantum Web interface through SSL. Attempts to
access the modem through standard HTTP will result in the user being locked to the login screen.
If HTTPS (SSL) access is not required for the user group, then those users may choose between
standard HTTP and HTTPS (SSL) access, as both modes will work.
When the computer is configured and connected, perform the following procedure.
Procedure 22-3
Connecting to the Horizon Quantum Web Interface
Perform this procedure to monitor RSL, EQ Stress and Eb/No (SNR) for the Horizon Quantum system.
1. In the Address bar of the Internet Explorer or in the Location bar of the web brouser, type the
URL or IP address of the Horizon Quantum System to be managed. Press Return.
2. The system will reply with the login screen.
3. Type your user name (with Super User, NOC, or Admin rights) and password.
4. Press OK. The Horizon Quantum's main Web page launches.
DragonWave Inc.
188
5. Bookmark the page for easy reference later.

A Web browser may be used to configure most, but not all, of the Horizon Quantum system, provided the
IP address of the system is known (default value 192.168.10.100) and you log on as the Super User.
Refer to Volume 1 of this manual for logging on details and basic configuration.
The Horizon Quantum Web interface follows standard Web browser conventions:
• A text box allows keyboard input for that parameter
• Drop-down boxes display the list of available options for that parameter.
Notes:
1. the following functions are not supported through the Web interface :
• User account establishment and account management
• Software upload and download, including backup and restore of system
configuration and user accounts
• Configure Horizon Quantum Type
• Ping
2. Configuration privileges correspond to the login level.
22.3.3 Exiting the Application

To exit the Horizon Quantum Web interface application, close the Web browser window. Closing the
window will cause the user to be logged out of the system.
22.3.4 Login
The login page appears whenever you connect to the Horizon Quantum Web interface. The session will
remain active for as long as your browser stays connected to the Horizon Quantum. Due to security
concerns, if the computer is unattended for any length of time then it is recommended you disconnect
from the Horizon Quantum Web interface by closing your browser window.
Horizon Quantum units support multiple Web sessions. The number of simultaneous sessions is limited
by the number of accounts at each authorization level. For example, since there is a maximum of five
NOC accounts, then five different NOC users may simultaneously log in (see Table 22-1). Additionally,
any one user account may establish multiple sessions on a single Horizon Quantum modem. Therefore a
single Super User, NOC, or Admin account may be used by more than one person to log in to the same
Horizon Quantum modem.
Table 22-1
Simultaneous logins for Web interface
User Level Number of Horizon Number of Simultaneous logins

Quantum Accounts per Horizon Quantum modem
Super User 1 1
NOC 5 5
Admin 50 50
System Management
189
Figure 22-1
Web Interface - Login Screen
22.3.5 Home Screen

The Horizon Quantum Web interface runs in a standard browser. The Home Screen (window) is divided
into four sections. The navigation bar displays seven menu options. The status pane is used to monitor
the system health and link performance. The system information pane displays system parameters and
links to more information. The Sub Menu displays optional information and the IP address of the peer
system.
Figure 22-2 Web Interface - Home Screen
Navigation Bar
System
Information Pane
Sub Menu
System Status Pane

DragonWave Inc.
190
Navigation Bar
Click on the navigation bar across the top of the page to navigate to different screens. Each menu option
displays a single screen.
System Status Pane
The main screen displays system status in the left hand pane. The information can be continually
refreshed. The default is no self-refresh (set to 0 seconds). Click on the “Set” button to manually refresh.
The maximum refresh rate is 99999 seconds. The minimum refresh rate is 3 seconds. Setting the self-
refresh rate also causes the Performance and Alarms screens to be refreshed at that rate. The System
Status Pane is visible on all the screens selected from the Navigation Bar.
System Information Pane
The system information pane contains information on the Horizon Quantum type, management settings,
IP address information, and frequency settings. This pane is not updated automatically. The user must
refresh the screen either by using the browser's refresh button or by clicking on the Home button within
the navigation bar in order to update the system information pane.
Sub-menu Options
The main screen has four Sub-menu options :
• System Summary - opens a window and displays a summary of the system configuration.
• System Name - link to the System Configuration page. If this field has been previously
configured then the value is displayed
• System Location - link to the System Configuration page. If this field has been previously
configured then the value is displayed
• Manage your Peer Horizon system : [IP address] - links to the login screen of the peer node
(provided the peer node has had its IP address configured). This provides the user with a Web
browser interface to each end of the Horizon Quantum link.
System Management
191
22.3.6 Web Page Tree Diagram

Figure 22-3 maps the information available via the Web interface.
Figure 22-3 Web Interface – Tree Diagram
DragonWave Inc.
192
22.3.7 SSL Web Server

The Horizon Quantum Web server can be configured for Secure Sockets Layer (SSL). The Web server
may be configured to operate in standard mode or in SSL mode. Horizon's SSL Web server is HTTP
1.0/1.1 compliant, features full support of HTML 2.0, 3.2, 4.0 and supports SSL 3.0.
Secure Sockets Layer, SSL, is the standard security technology for creating an encrypted link between a
Web server and a browser. This link ensures that all data passed between the Web server and browser,
remain encrypted. In order to be able to verify it’s identity to web clients, a web server requires a valid
SSL Certificate.
Once generated, the web server’s certificate may be held as a private certificate or it may be registered
with a Trusted Certificate Authority such as:
• Microsoft Root Authority
• Thawte Server
• GTE Cybertrust Root
• VeriSign RSA Secure Server
SSL access can be enabled on a per-user group basis. SSL access can be invoked for the Super User,
for all NOC accounts, for all Admin accounts, or any combination of the three. Once SSL access has
been enabled for the user group then all members of that user group can use SSL to connect to the
Horizon Quantum Web browser. Even if SSL access is not required for the user group, those users may
access the Horizon Quantum Web browser through HTTPS (SSL) as a security measure.
22.3.7.1. What is SSL?
SSL stands for Secure Sockets Layer. The SSL protocol, developed by Netscape, is supported by all
popular Web browsers such as Firefox, Internet Explorer, Chrome, and Opera. It is recommended that an
SSL certificate, issued by a Certification Authority (CA), be installed on the Web server in order to use
SSL. SSL can then be used to encrypt the data transmitted between a browser and Web server.
Browsers indicate a secured session is active by changing the URL from “http” to “https” and by
displaying a small padlock in the bottom toolbar.
SSL works as follows:
1. A browser requests a secure page (usually through the https:// format within the URL).
2. The Web server sends its public key with its certificate.
3. The browser checks that the certificate was issued by a trusted party (usually a trusted root
Certificate Authority), that the certificate is still valid and that the certificate is related to the site
contacted. The browser keeps a list of trusted Certificate Authorities. New CA's may be
added to the browser by the user.
4. The browser then uses the public key, to encrypt a random symmetric encryption key and
sends it to the server with the encrypted URL required as well as other encrypted http data.
5. The Web server decrypts the symmetric encryption key using its private key and uses the
symmetric key to decrypt the URL and http data.
6. The Web server sends back the requested html document and http data encrypted with the
symmetric key.
7. The browser decrypts the http data and html document using the symmetric key and displays
the information.
System Management
193
22.3.7.2. Generating a Certificate on the Horizon Quantum

In order to generate a valid SSL certificate on the Horizon Quantum, the user must be logged in as the
Super User, and the system time must be accurate. The SSL certificate is tied to the Horizon Quantum's
IP address. If the IP address is changed, then the SSL certificate should be regenerated. Otherwise the
browser SSL session will allow access but it will report that the certificate is invalid. In this situation, it is
the browser user's responsibility to verify that the proper Horizon Quantum is being accessed and that the
invalid certificate is due to an IP address change. Note, the underlying SSL connection between the
browser and the Horizon Quantum is still encrypted.
Procedure 22-4
Generate SSL Certificate on the Horizon Quantum
Perform this procedure to generate an SSL certificate on the Horizon Quantum.
Note: To perform this procedure, you must have Super User rights.
get ssl certificate status Displays the status of the modem's SSL certificate.
Sequence:
get ssl certificate status press Enter
----------------------------------------------------------------------
SSL Certificate Information
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 2 (0x2)
Signature Algorithm: sha1WithRSAEncryption
Validity
Not Before: Apr 15 21:03:15 2010 GMT
Not After : Jun 14 21:03:15 2010 GMT
Subject: C=US, O='Default Company Inc', CN=192.168.12.108.
Certificate IP Address is not valid.
DragonWave Inc.
194
create ssl certificate Creates an SSL certificate on the Horizon Quantum system. Once
created, users may access the Horizon Quantum system Web
interface through HTTPS (SSL). The SSL certificate is linked to the
Horizon Quantum IP address. If the Horizon Quantum IP address is
changed, then the certificate should be regenerated. Make sure the
system time on the Horizon Quantum is accurate before proceeding
further (from CLI use “get date time” to verify this).
Sequence:
create ssl certificate [<duration> <country> <company name>]
press Enter
Where <duration> is the period in days for which the certificate will
be valid, <country> is a two letter country code and <company
name> is the nameof your company.
Example – create ssl certificate 730 US ClearWire.
This generates a valid DragonWave-signed certificate that the web
server will now use, valid for two years.
Certificate generation in progress...please wait a few seconds...
Certificate Generation was Successful.

Embedded web server is now using the newly generated certificate.
Please accept the certificate in your web client when prompted.
get ssl certificate status Perform this step to verify the certificate is active. Displays the status
of the modem's SSL certificate.
Sequence:
get ssl certificate status press Enter
The system responds with one of the following:
----------------------------------------------------------------------
SSL Certificate Information
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: sha1WithRSAEncryption
Validity
Not Before: Jun 2 14:47:48 2010 GMT
Not After : Nov 3 14:47:48 2013 GMT
Subject: C=US, O=DragonWave Inc., CN=192.168.255.51
Certificate IP Address is valid.
This concludes the steps to generate an SSL certificate on the Horizon Quantum using the CLI manager.
System Management
195
22.3.7.3. Installing Certificates on Your Web Browser

Browsers keep a list of trusted Certificate Authorities (CA) in order to verify SSL certificates. A default list
of CA's is included with the browser software. New CA's can be added to the browser by the user.
Since the DragonWave certificate does not commonly appear in a browser’s list of authorities, you will
need to install it yourself. Once you have installed the DragonWave certificate in your browser’s
database for trusted root authorities, you can securely communicate with devices running the Horizon
Quantum Secure Web server.
Please refer to your Web browser's documentation for instructions on installation of certificates on your
particular browser.
These instructions are provided as an example as to how to install the certificate in Mozilla FireFox
version 3.5.6.
Procedure 22-5
Install SSL Certificates on Your Web Browser
Perform this procedure to install the DragonWave SSL certificate on your Web browser.
1. Download the DragonWave SSL certificate with Super User rights from CLI with the command
“save certificate ftp:dwicacert.pem” or “save certificate sftp:dwicacert.pem” to a trusted location
on a trusted FTP/SFTP server.
2. From the Firefox web browser, open the Tools Menu, click Options, select the Advanced tab,
select the Encryption tab, and the following window should appear:
DragonWave Inc.
196
3. Now click the “View Certificates” button, then on the Certificate Manager window, click the
Authorities tab.:
4. Click the Import button, and choose the dwicacert.pem file that was downloaded above. Be sure
to check mark the “Trust this CA to identify web sites,” box, then click the View button, and it
should look something like the following:
System Management
197
5. Click Close and click OK, and click OK again on the Certificate Manager window (the new
DragonWave certificate should be in the list of CA’s).
At this point, you have installed the DragonWave certificate in the list of trusted certificate authorities.
Your browser should now silently accept the HTTPS communication being offered by the Horizon
Quantum Secure Web server.
This concludes the steps to install SSL certificates on your Web browser.
22.3.7.4. Enabling SSL per User Group

Web interface access for each user group may be configured so that SSL use is mandatory. If the use of
SSL is not mandatory for a user group then that group can choose between standard HTTP access and
HTTPS (SSL) access. For example, SSL may be made mandatory for all Noc and Admin level users, but
not required for the Super User.
Procedure 22-6
Configure Mandatory SSL Access for Each User Group
Perform this procedure to configure mandatory SSL access to the Horizon Quantum modem for each
user group.
Note: To perform this procedure, you must have Super User rights.
get http secure access status Displays the status of the user group's mandatory SSL access to the
Horizon's Web interface. If the secure access is not required then
users may access the Web interface both through standard HTTP and
through HTTPS (SSL).
Sequence:
get http secure access [user group] press Enter
where [user group] is one of: Super, Noc, Admin
Note: [user group] is case sensitive.
The system responds with one of the following:

The HTTP Secure access for [user group] users is [not
enabled/enabled]
Example:
The HTTP Secure access for Noc users is not enabled.
DragonWave Inc.
198
set http secure access Sets the SSL access to mandatory for the selected user group. Once
set, the user group must access the Horizon Quantum Web interface
using HTTPS (SSL). Standard Web access through HTTP will be
restricted for that user group.
Sequence:
set http secure access [user group] [on/off] press Enter
The HTTP secure access is set successfully.
save mib Saves the MIB to RAM. Perform this command save setting changes
Sequence:
This concludes the steps to configure mandatory SSL access to the Horizon Quantum for each user
group.
22.4 Event and Performance Logging

The Horizon Quantum system supports two logs, the Events Log and the Performance Log. Each can be
used to track the behaviour of the system over time. In addition, a “Syslog” feature can be invoked that
sends information stored in the event and performance logs to a remote syslog server, for further
analysis. The Events Log, Performance Log and the Syslog features are independent of one another,
allowing all or either one to be functional without affecting the other.
22.4.1 Events Log

The Events Log is invoked or disabled by issuing the CLI command set logging [on/off]. This log records
alarm and reset events. Approximately 17,500 events can be captured by the Events log. Once the log is
full the oldest entries are overwritten. See Procedure 22-7 for more details.
Procedure 22-7
Events Log
login Log in as a NOC account

View events log status This command returns the status of the events log
Sequence :
get logging press Enter
System Management
199
Logging has been :[enabled/disabled.]

View log entries This command lists all events entries in the log since the log was
enabled, or after it was last cleared. Ctrl-c aborts the listing.
Sequence :
get log entries press Enter
Info: Jun 02 14:56:22 ---TBD--- mib[331799-27]: User energetic
logged out Telnet 2 port
Info: Jun 02 14:52:40 ---TBD--- mib[331799-38]: 1 duplicate logs
not written
Info: Jun 02 14:52:40 ---TBD--- mib[331799-38]: Web User
energetic logged in from IP Address 192.168.3.246
Info: Jun 02 14:51:23 ---TBD--- mib[331799-26]: Saved mib
successfully
Info: Jun 02 14:50:28 ---TBD--- mib[331799-28]: User energetic
logged out Telnet 3 port
<<<<Press any key to continue <Ctrl-C or ‘q’ to exit.>>>>
Configure events logging This command enables and disables events logging
Sequence :
set logging [on/off] press Enter
Logging is :[on/off]
DragonWave Inc.
200
save log Saves the events log to a specified FTP/SFTP server.

Sequence :
save log ftp:[mylogfile] or save log sftp:[mylogfile] press Enter
Note: The maximum system log file size for FTP/SFTP to a server
holds about 1200 events (100KB). If more than 1200 events are
stored on the system, then multiple files will be created and named
as "mylogfile1", "mylogfile2" etc.
Enter the IP address of FTP server followed by 'Enter' Key :[ip
address]
220 ProFTPD 1.2.5 Server (Dragonwave FTP Site)
[support.dragonwaveinc.com]
UserName :username
331 Password required for username.
Password :*******
230 User username logged in.
Copy log entries to a file? Enter Y(yes) or N (no):y

Trying to copy the data to mylogfile File. Please wait for a while.
200 PORT command successful.
150 Opening ASCII mode data connection for mylogfile.
226 Transfer complete.
Data successfully transferred to specified file. 221 Goodbye.

erase log Removes all entries from the events log
Sequence :
erase log press Enter
Erased log succcessfully.
System Management
201
22.4.2 Performance Log

Issuing the CLI command set performance logging [on/off] enables or disables the Performance Log.
This log collects system performance information at time intervals that are configured using the CLI
command set performance log interval [hh:mm:ss]. See Table 22-2 for more details.
Procedure 22-8
Performance Log
login using NOC account Log in as a NOC account
View performance logging Returns the status of performance logging

Sequence :
get performance logging press Enter
Performance Logging has been :[enabled/disabled.]
Configure performance Allows you to enable or disable performance logging

logging Sequence :
set performance logging [on/off] press Enter
Performance Logging is :[on/off]
Configure performance log Sets the time interval between performance log updates
interval
Sequence :
set performance log interval hh:mm:ss press Enter
Where hh is in hours, mm is in minutes and ss is in seconds. Note
that the maximum interval allowed is 24 hours and the minimum is
15 seconds. The default setting is 15 minutes. See Table 22-2 for
log durations for different intervals.
The performance logging interval is set to: hh:mm:ss
View performance log This command lists all performance entries in the log since the log was
enabled, or after it was last cleared. Ctrl-c aborts the listing.
Sequence :
get performance log press Enter
Start of Performance log ...
SNR Eb/No RSL Temp Avg.BW PeakBW
1 06/21/2007 13:15:09 0 526172 I 8.71 6.08 -44.88 30.5 68 85
1 06/21/2007 12:29:56 0 526171 I 8.32 5.69 -44.75 30.6 66 90
.
End of Performance log.
DragonWave Inc.
202
erase performance log Erases the performance log

Sequence :
erase performance log press Enter
Erased log successfully.
Table 22-2 Performance Log Durations

Between 6000 and 8000 entries can be logged before the Performance Log memory is full. Once the
memory is full, new entries will overwrite the oldest entries. The following table assumes that an average
of 7000 entries will occur before memory overflow. If the memory accepts more entries, then the log
duration before overflow will be extended.
Logging Interval Log Duration

15 secs (minimum) ~ 29 hours
1 minute ~ 116 hours (~ 4.8 days)
15 minutes (default) ~ 73 days (~ 2.4 months)
1 hour ~ 292 days (~ 9.7 months)
24 hours (maximum) 7000 days (~ 19.2 years)
22.4.3 Syslog Feature

Note that events and performance data are always being collected and stored, but only made available
for viewing by the user when the logs are enabled. However, these data are always available to the
Syslog feature, whether or not the events and/or performance logs are enabled.
The Syslog feature is invoked by configuring the IP address of a remote syslog server on the network
using the CLI command set syslog forwarding host [ip address] and then turning on log forwarding.
See Procedure 22-9 for more details.
Procedure 22-9
Syslog Feature
login using NOC account Log in as a NOC account
Configure the IP address of Sets the IP address of the PC on which the Syslog Server is running.
the syslog server Sequence :
set syslog forwarding host [ip address] press Enter
Successfully set syslog forwarding destination IP address to [ip
address]
System Management
203
To turn on forwarding, execute ‘set syslog forwarding on’.

Turn on Syslog forwarding Turns on syslog forwarding.
Sequence :
set syslog forwarding on press Enter
Set forwarding rule ‘on’
Syslog Forwarding Admin Status : on
Syslog Forwarding Oper Status : off (waiting for first send request)
Changing the IP address of a If you want to change a Syslog Server IP address and the current
Syslog Server Syslog Server is already running, first turn off syslog forwarding.
Sequence :
set syslog forwarding host [new ip address] press Enter
Error : Could not update syslog server IP address because it is
currently turned ‘on’. Please turn ‘off’ and then change the IP
Address.
set syslog forwarding off press Enter
Set forwarding rule ‘off’
Syslog Forwarding Admin Status : off
Syslog Forwarding Oper Status : off (Admin state is ‘off’)
set syslog forwarding host [new IP address] press Enter
Successfully set syslog forwarding destination IP address to [new
IP address]
To turn on forwarding, execute ‘set syslog forwarding ‘on’.
set syslog forwarding on press Enter
Set forwarding rule ‘on’
Syslog Forwarding Oper Status : off (waiting for first send request)
View syslog status This command returns the status of the syslog server.
Sequence :
get syslog forwarding status press Enter
Syslog Forwarding Oper Satus : on
View the IP address of the Use the following command to return the current syslog server IP
syslog server address.
Sequence :
get syslog forwarding host press Enter
Syslog Forwarding Host : [IP address]
DragonWave Inc.
204
Sequence:
22.5 Radio and Network Loopback

Horizon Quantum provides a radio and network loopback facility for analysis of transmit, or receive, path
issues. This feature is only supported by the Quantum R5 radio. Invoking a loopback is service affecting
and will stop all data transfer. There are two options:
• Straight radio loopback - Ethernet traffic is not looped back to the network, Ethernet traffic is
discarded and the RF portion of the Horizon unit is placed in loopback
• Radio loopback plus network loopback – Ethernet traffic and the radio are placed in loopback
Note: In this release the network loopback option is always disabled (not supported). This means
that Ethernet packets are not looped back during the Radio Loopback operation.
During the loopback, if the modem transmitter loss of sync alarm is not active, then both the transmitter
and receiver of the unit under test (usually the near end unit) are functioning correctly. You can also use
the CLI command get modem statistics wireless_port[1/2] and check that there are no increasing Rx
Block Errors while in loopback.
A user configurable time limit can be applied to the loopback feature (default is 30 seconds). Once the
time limit has expired the loopback will be automatically removed.
The radio loopback is invoked using the CLI command:
set radio loopback [on/off] [-tseconds] [network] [wireless_port1] [wireless_port2].
Working option for this release is the following:
set radio loopback [on/off] [-tseconds] [wireless_port1] [wireless_port2].
System Management
205
Procedure 22-10
Radio Loopback
login into near end system Log in as a NOC account
View radio loopback status Returns the status of the radio loopback feature.
Sequence:
get radio loopback press Enter
RF loopback on radio 1 is OFF
RF loopback on radio 2 is ON
Note that for a dual modem, single radio (system capacity 2), “radio 1”
and “radio 2” would correspond to “port 1” and “port 2” respectively.
DragonWave Inc.
206
Configure radio loopback Enables and disables the radio loopback option. This feature allows
the radio transmitter and receiver system to be tested. In one option
the data signal is dropped and the radio signal alone is looped back. In
the second option, the data as well as the radio signal is looped back.
When in loopback, if no loss of synch alarm is raised, then this
indicates that the radio transmit and receive portions of the system are
working correctly. You can also use the CLI command get modem
statistics wireless_port[1/2] and check that there are no increasing
Rx Block Errors while in loopback.
Note that this command is service affecting.
The default time limit before the loopback is automatically removed is
set to 30 seconds. Setting the time parameter to zero (0) maintains the
loopback in place indefinitely, until it is turned off.
Sequence :
set radio loopback [on/off] [-tseconds]
Where -tseconds is in seconds
Turn on radio loopback for Enables radio loopback on wireless port 1 (or radio 1) by default. Note
wireless port 1 with the that wireless port 2 will be turned off.
default time of 30 seconds Sequence:
set radio loopback on press Enter
This may affect user traffic. Continue? Enter Y (Yes) of N (No): y
Radio loopback mode is on for 30 seconds.
Warning: In-band management will not be available during
loopback.
Turn on radio loopback for Enables the radio loopback on wireless port 2 (or radio 2). Note that
wireless port 2 for a time wireless port 1 will be turned off.
duration of 60 seconds Sequence:
set radio loopback on –t60 wireless_port2 press Enter
This may affect user traffic. Continue? Enter Y (Yes) of N (No): y
Warning: In-band management will not be available during
loopback.
Turn on radio and network Enables both radio and network loopback for wireless port 2 (or radio
loopback on wireless port 2 2).
for 90 seconds Sequence:
set radio loopback on –t90 network wireless_port2 press Enter
“This option is not The system responds:
supported in this release” This may affect user traffic. Continue? Enter Y (Yes) of N (No): y
Warning: In-band management will not be available during loopback.
System Management
207
Turn off radio loopback Turns radio loopback off before it has automatically timed out.
Sequence:
set loopback off press Enter
DragonWave Inc.
208
22.6 Intermediate Frequency (IF) Loopback

Horizon Quantum provides an IF loopback facility for analysis of transmit or receive path issues. Invoking
an IF loopback is service affecting and will stop all data transfer.
Note: In this release the network loopback option is always disabled (not supported). This means that
Ethernet packets are not looped back during the IF loopback operation.
When analysing the near end system using the IF loopback feature, if the far end radio is a Quantum R5
radio there is no need to mute the far end radio. However, if the far end radio is a Quantum R4 radio, you
will have to manually mute the far end radio before initiating the IF loopback.
You can use the CLI command get modem statistics wireless_port[1/2] and check that there are no
increasing Rx Block Errors while in loopback.
A user configurable time limit can be included in the loopback command (default is 30 seconds). Once the
time limit has been reached, the loopback is automatically removed. For a system with a Quantum R5
radio at the far end, communication between systems will be immediately restored. For a system having a
R4 radio at the far end, you will have to manually unmute the radio before communications will be
restored.
Note: Radio loopback and IF loopback cannot be turned on at the same time.
When the system capacity is DualModemSingleRadio, only one modem IF can be put into loopback at
any given time.
NOTE: The IF connector(s) must always be properly terminated when IF loopback is being
performed. This means that either a radio (powered on, or off), or a 50 Ohm terminating resistor
needs to be connected to the IF connector(s). Note that there is a nominal 48 V DC present on the
IF connector(s) at all times, requiring the terminating resistor, if used, to have a power rating of at
least 50 watts.
System Management
209
Procedure 22-11
Intermediate Frequency (IF) Loopback
login into near end system Log in as a NOC account
View IF loopback status Returns the status of the IF loopback feature.

Sequence:
get if loopback press Enter
IF1 loopback is : OFF
IF2 loopback is : ON
Network option is : disabled
Loopback timer is : 23 sec
Invoke the IF loopback This command turns the IF loopback on or off as required, for either Port 1 or
Port 2 (both cannot be on together). You can also specify a time limit after
which the loopback will automatically be removed (default is 30 seconds).
When in loopback, if no loss of synch alarm is raised, then this indicates that
the radio transmit and receive portions of the system are working correctly.
You can also use the CLI command get modem statistics wireless_port[1/2]
and check that there are no increasing Rx Block Errors while in loopback.
Sequence:
set if loopback [on/off] [–tseconds]
Example 1:
set if loopback on –t45 wireless_port2 press Enter
This may affect user traffic. Continue? Enter Y(Yes) or N(No): y
IF loopback mode is on for 45 seconds.
IF1 loopback is : off
IF2 loopback is : on
Loopback timer is : 39 sec (displays remaining loopback time)
Example 2:
set if loopback on press Enter (defaults to Port 1 and 30 seconds time limit)
This may affect user traffic. Continue? Enter Y(Yes) or N(No): y
IF loopback mode is on for 30 seconds.
The stystem responds:
IF1 loopback is : on
Loopback timer is : 20 sec
IF2 loopback is : off
set if loopback off press Enter
IF1 loopback mode is off
DragonWave Inc.
210

23.0 Network Management
This section describes how to use network management to manage the Horizon Quantum units.
23.1 Simple Network Management Protocol (SNMP)

Simple Network Management Protocol (SNMP) is an application-layer protocol used to exchange
management information between network devices. Network management systems contain two primary
elements: a manager and an agent. The manager resides on a Network Management Station (NMS). The
NMS is a console through which the network administrator performs network management functions.
Agents reside on the network devices such as bridges, hubs, routers, or network servers. The Horizon
Quantum system is a network device that contains an agent.
The SNMP manager uses Management Information Bases (MIBs). MIBs are a collection of definitions of
the properties for the managed objects. Every managed device keeps a database of values for each
definition written in the MIB. There are several standard MIBs provided in each NMS software package.
These MIBs are common parameters for network devices such as unit health and IP traffic statistics.
Each manufacturer typically provides an Enterprise MIB. The Enterprise MIB is a collection of definitions
that address the particular aspects of the manufacturer’s product. These Enterprise MIBs must be loaded
onto the NMS, in other words, they must be placed in the MIB “database” directory and enabled, in order
for the NMS to access the parameters.
SNMP includes a limited set of management commands and responses. The management system issues
Get and Set commands and the agent sends a response message in return. The Get command reads a
parameter, and the Set command will configure, or assign a value to, a parameter. The managed agent
also sends an event notification, called a trap, to the management system to identify the occurrence of
conditions such as thresholds that have been exceeded.
Each SMNP managed object belongs to a community, or group. The Network Management Station may
belong to multiple communities. The community string must be set in the agent device in order for the
NMS to access the device.
23.1.1 Supported SNMP Versions

DragonWave Horizon Quantum systems support three versions of SNMP.
• Version 1 (SNMP v1) is the initial implementation of SNMP.
• Version 2 (SNMPv2c) is the second release of SNMP, which has additions and enhancements to
data types, counter size and protocol operations.
• Version 3 (SNMPv3) is the most recent version of SNMP. The functionality of SNMPv1 and
SNMPv2c remain intact, but SNMPv3 has significant enhancements to administration and
security.
SNMPv3 is an interoperable standards-based protocol that provides secure access to devices by
authenticating and encrypting packets over the network. The security features provided in SNMPv3 are
as follows:
• Message integrity
• Authentication
• Encryption
Note that all CLI commands relating to all versions of SNMP take effect immediately, a save mib or reset
system not being required. The default mode for SNMP is “off”.
DragonWave Inc.
212
Procedure 23-1
Setting up SNMP
Perform this procedure to set up SNMP for the Horizon Quantum system.
login Log in as a NOC account for SNMP v1 and v2c, or Super user for
SNMP v1, v2c and v3
set snmp access mode Selects a SNMP access mode.

[v1/v2c/v3/off]
The default mode is SNMP mode v1.
Sequence:
set snmp access mode [v1/v2c/v3/off] press Enter

SNMP Mode: [v1 | v2c | v3 | off]
set snmp set request [on/off] Sets the SNMP access mode to on. This allows SNMP ‘set’ requests.
Sequence:
set snmp set request [on/off] press Enter

SNMP set requests are: [on/off].
get snmp set request Displays SNMP requests state. Displays if SNMP ‘set’ requests are
enabled.
The default state is off.
Sequence:
get snmp set request press Enter

SNMP set requests are: [on | off].
Network Management
213
FOR SNMP v1 or v2c ONLY
get snmp managers Displays a list of managers that can access the system via SNMP v1
and v2c only.
Sequence:
get snmp managers press Enter

Mgr# IpAddress Status CommunityString
1 0.0.0.0 disabled
2 0.0.0.0 disabled
3 0.0.0.0 disabled
4 0.0.0.0 disabled
5 0.0.0.0 disabled
6 any disabled
Note :1.Only maximum of 5 managers are allowed. If all the managers are
filled in, remove 1 manager by overwriting the particular index.
2.By setting the IP address of last index to 'any' and 'enable', anybody can
have access to the system via SNMP.
DragonWave Inc.
214
set snmp manager [mgr#] [ip Specifies the SNMP managers to allow access to the system, v1 and
address] [enable/disable] v2c only.
[community string] Note: You cannot delete a manager IP address entry. You can only
overwrite an existing entry with a valid IP address. If you want less
than five managers and five have been previously configured, you will
have to "disable" the undesired entry.
If Manager index 6 is enabled with "any" and a community string, none
of the five manager entries will function, unless the same community
string is applied to the management entry.
Sequence:
set snmp manager [mgr#] [ip address] [enable/disable]
[community string] press Enter
Mgr# IpAddress Status CommunityString

1 192.7.1.1 enabled teststring
2 0.0.0.0 disabled
3 0.0.0.0 disabled
4 0.0.0.0 disabled
5 0.0.0.0 disabled
6 any disabled
Note :1.Only maximum of 5 managers are allowed. If all the

managers are filled in, remove 1 manager by overwriting the
particular index.
2.By setting the IP address of last index to 'any' and 'enable',
anybody can have access to the system via SNMP.
Network Management
215
FOR SNMPv3 ONLY
set snmpv3 This specifies an snmpv3 external user.

manager {1..5}
There may be up to 5 external SNMP managers configured in the system. Each
This command user should have a unique name. The default security level for the system is
requires the noAuthNoPriv.
following prompts The user is prompted with the current value for each option. User may choose to
to be answered. keep or modify this entry by selecting y\n. For each prompt, available options are
shown.
user username
Example:
securityLevel set snmpv3 manager press Enter
[noAuthNoPriv The system responds:
authNoPriv | Enter the entry number to modify [1-5]: 1
authPriv ]
Snmp V3 UserName []:roger
New user Name for Entry [1] is set to [roger]
[auth {md5 | sha |
none} auth- Authentication Protocol [0=NoAuth | 1=MD5 | 2=SHA] [NoAuth]:
password]
Snmp v3 Status [0=disable| 1=enable ] [Disabled]:1
New activate option for Entry [1] is set to [Enabled]
[priv {DES |
none}
index userName authProt authPass privProt privPass status
priv-password] ============================================================================
1 roger NoAuth NoPriv enabled
2 NoAuth NoPriv disabled
Note :1.Only maximum of 5 managers are allowed. If all the managers are
filled in, remove 1 manager by overwriting the particular index.]
DragonWave Inc.
216
get snmpv3 Displays a list of configured SNMPv3 managers.

managers
get snmpv3 managers press Enter
index userName authProt authPass privProt privPass status

============================================================================
1 roger NoAuth NoPriv enabled
Note :1.Only maximum of 5 managers are allowed. If all the managers are filled in, remove 1 manager
by overwriting the particular index.
get snmpv3 trap Displays a list of configured SNMPv3 trap hosts
hosts Note that only the Super user can view the ip addresses of trap hosts.
Sequence:
get snmpv3 trap hosts press Enter
# IpAddress UserName Auth Auth Priv Priv TrapHost
Proto Passwd Proto Passwd Enabled
= =============== =============== ===== ===============
1 192.168.4.254 guest None - None - y
2 0.0.0.0 None - None - n
3 0.0.0.0 None - None - n
4 0.0.0.0 None - None - n
5 0.0.0.0 None - None - n
set snmpv3 trap To set the trap host ip address to capture v3 traps. This will only set up a trap host
host ip destination without authentication or privacy.
NOTE: You must set a trap host user (see next command) before a configured
trap host will function. Only Super user is allowed to set these parameters.
Sequence:
set snmpv3 trap host ip <index> <ipAddr> press Enter
where <index> indicates which trap host entry you want to set in the
range of 1...5 and <ipAddr> is the ip address of the host on the network.
There is no system response, but changes will have been made
Network Management
217
set snmpv3 trap To set the host user name associated with v3 trap hosts. This will only set up a
host user trap host destination without authentication or privacy.
NOTE: You must set a trap host ip (see previous command) and a host user
name before a configured trap host will function. Only Super user is allowed to set
these parameters.
Sequence:
set snmpv3 trap host user <index> <userName> press Enter
where <index> indicates which trap host ip address entry to which you
want to add the host user name in the range of 1…5
set snmpv3 trap To enable a trap host.

host enable NOTE: Individual traps need to be enabed before they will be received by an
enabled trap host. Only Super user is allowed to set these parameters.
Sequence:
set snmpv3 trap host enable <index> press Enter
Where <index> is the trap host index you wish to enable in the range
1 to 5
set snmpv3 trap To disable a trap host.

host disable NOTE: Only Super user is allowed to set these parameters.
<index> Sequence:
set snmpv3 trap host disable <index> press Enter
Where <index> is the trap host index you wish to disable in the range
1 to 5
set snmpv3 trap Use this command to set up trap host authentication.
host NOTE: Only Super user is allowed to set these parameters.
authentication
Sequence:
set snmpv3 trap host authentication <index> [none|md5|sha] <authKey>
press Enter
Where <index> is the trap host index in the range 1 to 5 on which you wish to
configure authentication, [none|md5|sha] are the protocols available and
<authKey> is a text string of up to 25 alpha numeric characters.
DragonWave Inc.
218
set snmpV3 trap Use this command to set up privacy.

host privacy NOTE: Authentication must be configured before privacy will function. Only Super
<index> user is allowed to set these parameters.
[none|des]
Sequence:
<privKey>
set snmpv3 trap host privacy <index> [none|des] <privKey> press Enter
Where <index> is the trap host index in the range 1 to 5 on which you wish to
configure privacy, [none|des] are the protocols available and <privKey> is a text
string of up to 25 alpha numeric characters.
This concludes the steps to set up the SNMP for the Horizon Quantum system.
23.1.2 Enterprise Management Information Base (MIB)

A Management Information Base (MIB) contains information about a network device that is managed by
SNMP. Horizon Quantum supports industry standards MIB I and MIB II. In addition, DragonWave
provides an enterprise MIB for Horizon Quantum. For a list of objects and their definitions, refer to the
Horizon Quantum MIB definition file included with the DragonWave Toolkit CD-ROM.
You must load the Horizon Quantum MIB onto your own MIB browser or Network Management Station
(NMS). HP OpenView is an example of network management software to be used on the NMS. The
Horizon Quantum Enterprise MIB is provided in a standard MIB format that allows a more direct method
of loading the definitions onto the NMS. On some NMS systems, it is as straightforward as placing the
Horizon Quantum MIB into the proper NMS directory and then enabling it by adding it to the MIB list.
Please consult the instructions provided with your NMS for details on loading the Enterprise MIBs.
Network Management
219
23.1.3 SNMP Traps

A trap is a message that reports a problem or a significant event. Traps are defined in the Horizon
Quantum MIB definition file. A trap destination or trap host is the IP address of a client (network
management station) that receives the SNMP traps.
Procedure 23-2
Enable traps
Perform this procedure to enable traps.
login Log in as a NOC account
get snmp trap hosts Displays a list of receivers of SNMP traps.
Sequence:
get snmp trap hosts press Enter

Host# IpAddress Status CommunityString
1 0.0.0.0 disabled public
Note: A maximum of 5 hosts is allowed. If all the hosts are filled in,
remove 1 host by overwriting the particular index.
DragonWave Inc.
220
set snmp trap host [host #] Adds an SNMP trap host to the list of receivers of SNMP traps. Specify
[ipAddress] [enable/disable] the IP address where the system sends traps.
[communityString]
Sequence:
set snmp trap host [host #] [ipAddress] [enable/disable]
[communityString] press Enter

Host# IpAddress Status CommunityString
3 3.3.3.3 enabled new text string here
Note: A maximum of 5 hosts are allowed. If all the hosts are filled in,
remove 1 host by overwriting the particular index.
Network Management
221
get snmp traps Displays the list of traps available in the system.
Sequence:
get snmp traps press Enter

Trap# TrapName Enabled(Yes | No)
1 ColdStart No
2 Link down No
3 Link up No
4 Explicit Authentication Failure No
5 AAM Configuration mismatch No
6 AAM running on the lowest modulation No
7 ATPC Config Mismatch No
8 SNTP servers unreachable No
9 Frequency file invalid No
10 Dropped Frames Threshold exceeded No
11 Bandwidth utilization Threshold exceeded No
12 RLS mismatch No
13 RLS Queue Based shutdown activated No
14 Modem receiver loss of signal No
15 Modem transmitter loss of sync No
16 Modem SNR below threshold No
17 Modem equalizer stress above threshold No
18 RSL Below Threshold No
19 RLS Shutdown Activated No
20 Modem programming error No
21 User session commenced No
22 User session terminated No
23 Atpc Transmitting at coordinated power No
24 Radio Synthesizer Lost Lock No
25 Radio Lost Communication No
26 Radio Mismatch No
27 Radio Power Amp No
28 Radio: Excessive Tx cable loss No
29 Radio Drain Current No
30 High Power Radio transmit detector No
31 Redundancy, Secondary Radio is active No
32 Redundancy, Radio Serial number mismatch No
33 Radio firmware mismatch No
34 Secondary radio not detected No
35 Primary radio not detected No
36 Faulty primary radio detected No
DragonWave Inc.
222
set snmp trap [trapIndex] Sets the SNMP trap and enables or disables it. DragonWave
[enable/disable] recommends enabling the LossOfSignalLockFromDemod trap. This
trap indicates loss of communication with the peer Horizon Quantum
node.
Sequence:
set snmp trap [trapIndex] [enable/disable] press Enter
Example:
set snmp trap 18 enable
Trap# TrapName Enabled(Yes | No)
1 ColdStart No
2 Link down No
3 Link up No
4 Explicit Authentication Failure No
5 AAM Configuration mismatch No
6 AAM running on the lowest modulation No
7 ATPC Config Mismatch No
8 SNTP servers unreachable No
9 Frequency file invalid No
10 Dropped Frames Threshold exceeded No
11 Bandwidth utilization Threshold exceeded No
12 RLS mismatch No
13 RLS Queue Based shutdown activated No
14 Modem receiver loss of signal No
15 Modem transmitter loss of sync No
16 Modem SNR below threshold No
17 Modem equalizer stress above threshold No
18 RSL Below Threshold Yes
19 RLS Shutdown Activated No
20 Modem programming error No
21 User session commenced No
22 User session terminated No
23 Atpc Transmitting at coordinated power No
24 Radio Synthesizer Lost Lock No
25 Radio Lost Communication No
26 Radio Mismatch No
etc.
Network Management
223
save mib Saves the MIB to RAM. Perform this command save setting changes
Sequence:
This concludes the steps to set SNMP traps using the CLI manager.
DragonWave Inc.
224

Appendix A - Detailed CLI Command Syntax
All commands are accessible by the Super User. Some are only accessible by the Super User. The NOC
user can access most commands. An ADMIN user has limited access to “set” commands.
Underlined commands require the reset system command to be applied before they will take effect.
User
Command Description
Access
? display all commands with their short NOC,
description. ADMIN
clear ecfm errors [domain <domain-name(1..20)> | Clear continuity check error conditions NOC
levelid <level-id(0-7)>] logged on a device.
clear ecfm frame delay buffer Clear the contents of the Frame Delay rolling NOC
buffer. This is an Y.1731 command.
clear ecfm loopback cache Clear the contents of the Loopback Reply NOC
Cache.
clear ecfm maintenance-points remote Clear the contents of continuity check NOC
database.
clear ecfm mip-ccm-database Clear the contents of MIP CCM Database. NOC
clear ecfm traceroute-cache Clear the contents of ECFM traceroute NOC
cache.
commit The commit command will copy the active NOC
bank to the backup bank making the banks
identical. The active OMNI and the
configuration files (MIB and system
configuration) are copied to the backup bank.
The commit command must be done before
upgrading to a new OMNI or Frequency File
giving the operator the ability to “roll-back” to
the previous release (using “switch”
command) in case the system is not
behaving as expected.
copy [ftp:fileName] or copy [sftp:fileName] allows the user to download file from remote NOC
location. To download user accounts file
filename should startwith 'user' keyword and
to download configuration file filename
should start with 'config' keyword.
create ssl certificate creates SSL certificate. SU
delete ecfmmib [newest | both] Delete ecfm MIB.
delete l2swmib [newest|both] deletes the l2sw MIB NOC
delete mib [newest/both] deletes the MIB as requested by the user. NOC
delete radius server [index] delete the host and shared key config for a SU
Radius Server.
diagnose haam [up/down] enable Hitless Automated Adaptive NOC,
Modulation (haam) diagnostic mode ADMIN
[up/down]
diagnose redundancy displays whether there are two radios or two NOC,
wireless ports available for redundancy. ADMIN
DragonWave Inc.
226
User
Command Description
Access
downgrade feature group [index] allows the user to downgrade a feature group NOC
(index 1 through 5) and returns the
downgrade confirmation information required
by DragonWave before a refund can be
given.
downgrade system licensed speed [speed value] downgrades system licensed speed NOC
ecfm ping ethernet [ mac {<aa:bb:bb:bb:bb:bb> | Send unicast or multicast Loopback NOC
multicast } {domain <domain-name(1..20)> | level messages by providing the MAC Address of
<level-id(0-7)>} [vlan <vlan-id(1-4094)>] [interface the MEP or MIP.
<interface-number>] [direction {inward | outward}]
[data-pattern <string> |test-pattern null-signal-without-
crc | null-signal-with-crc | prbs-without-crc |prbs-with-
crc] [size <pdu-size(64-1400)> | variable-bytes] [interval
<milliseconds(1-600000)>] [count <num_of_msgs(1-
8192)>] [deadline <seconds(1-172800)>] [switch
<string(32)>]
ecfm ping ethernet mpid <id> {domain <domain- Send unicast or multicast Loopback NOC
name(1..20)> | level <level-id(0-7)>} [vlan <vlan-id(1- messages by providing MEPID of the
4094)>] [interface <interface-number>] [direction destination MEP of the MEP or MIP.
{inward | outward}] [data-pattern <string> |test-pattern
null-signal-without-crc | null-signal-with-crc | prbs-
without-crc |prbs-with-crc] [size <pdu-size(64-1400)> |
variable-bytes] [interval <milliseconds(1-600000)>]
[count <num_of_msgs(1-8192)>] [deadline <seconds(1-
172800)>] [switch <string(32)>]
ecfm traceroute ethernet mac <aa:aa:aa:aa:aa:aa>

{domain <domain-name(1..20)> | level <level-id(0-7)>} Initiate Linktrace message by providing the NOC
[vlan <vlan-id(1-4094)>] [time-to-live <ttl-value(1-255)> MAC Address of the MEP or MIP.
ecfm traceroute ethernet mpid <id> {domain <domain- Initiate Linktrace message by providing NOC
name(1..20)> | level <level-id(0-7)>} [vlan <vlan-id(1- MEPID of the destination MEP of the MEP or
4094)>] [time-to-live <ttl-value(1-255)> MIP.
ecfm frame delay [start | stop] type {one-way | two-way
} level <level-id(0-7)> [vlan <vlan-id(0-7)>] [port <port- Start or Stop the ecfm delay measurement NOC
num>] [direction {inward | outward}]{mepid <mpid(1- calculations.
8191)> | mac <aa:aa:aa:aa:aa:aa>}
[count<num_of_observations(1-8192)>] [interval
<milliseconds(10-10000)>] [deadline <seconds(1-
172800)>] [switchname <context_name>]]
erase log erases all event log entries. NOC
erase performance log erases all of performance log entries. NOC
exit allows the user to exit from Telnet Session. NOC,
ADMIN
get active wireless port returns the active wireless port. This NOC,
command is only applicable to ADMIN
SingleModemRedundancy mode.
get air interface authentication type returns Authentication type used on the air NOC,
interface. ADMIN
Appendix A
227
User
Command Description
Access
get alarms returns alarms present in the system. NOC,
ADMIN
get alarms counter returns timestamped alarms present in the NOC,
system. ADMIN
get alignment returns the current status of the RSL NOC,
alignment signal on the BNC connector on ADMIN
the Quantum radio
get antenna diameter returns the antenna's diameter. NOC,
ADMIN
get antenna tilt returns the orientation of an installed NOC,
Quantum radio, or radios as vertical, ADMIN
horizontal, or flat. If an AirPair/Duo (R4)
Radio is polled, “unknown” is returned.
get arp cache returns the “arp” table. NOC,
ADMIN
get atpc status returns the atpc status(On/Off) coordinated NOC,
Power status(On/Off) and atpc parameters. ADMIN
get authentication failure action returns action taken by the system on peer NOC,
authentication failure. ADMIN
get authenticated peer returns SN with which system has NOC,
commenced communications with. ADMIN
get authentication status returns status of Authentication in the NOC,
system. ADMIN
get bac returns the current bandwidth acceleration NOC,
(bac) configuration. ADMIN
get bac record average period Returns the number of seconds configured NOC,
for computing the running average bac gain ADMIN
and uncompressed ratio. Default average
period is set to 10 seconds.
get bac record brief [1,2,3,4] Returns the bac related flash records stored NOC,
in flash in a brief format for the specified ADMIN
Queue.
get bac record current [1,2,3,4] Returns the contents of the active bac record NOC,
(has not yet get been saved in flash) for the ADMIN
specified queue.
get bac record logging [1,2,3,4] Returns the bac logging recording status to NOC,
flash and syslog as either 'on' or 'off'. If no ADMIN
queue is specified, then the logging
configuration status of all queues is
displayed.
get bac record verbose [1,2,3,4] Returns a verbose view of the stored bac NOC,
records. ADMIN
get backup ipconfig returns IP Configuration Parameters stored NOC,
as backup. ADMIN
get bandwidth doubling status returns the status of the bandwidth doubling NOC,
feature ADMIN
DragonWave Inc.
228
User
Command Description
Access
get bandwidth record admin returns the administrative status of NOC,
bandwidth logging. ADMIN
get bandwidth record average period returns the running average period, in NOC,
seconds, over which the running average is ADMIN
computed.
get bandwidth record brief displays all 60 bandwidth utilization records NOC,
in brief format. ADMIN
get bandwidth record current retrieves the current record that has yet to be NOC,
written to flash memory. ADMIN
get bandwidth record instance [0…59] retrieves the selected instance of a record NOC,
and displays it in detailed format. ADMIN
get bandwidth record logging returns the status of bandwidth logging. NOC,
ADMIN
get bandwidth record reporting period returns the reporting period in seconds. NOC,
ADMIN
get bandwidth record thresholds retrieves the 10 configured bandwidth NOC,
utilization threshold integers ADMIN
get bandwidth record verbose returns a verbose view of stored bandwidth NOC,
records, including an appended MD5 hash of ADMIN
the information.
get bandwidth utilization threshold returns the % utilization of bandwidth NOC,
threshold. ADMIN
get bandwidth utilization status returns the current bandwidth utilization and NOC,
throughput. ADMIN
get cable loss [wireless_port1/wireless_port2] returns the calculated loss of the IF cable for NOC,
wireless port 1 or port 2. ADMIN
get config commands displays system configuration commands NOC,
and their associated values set in the ADMIN
system.
get cos cut through queue displays the current cut through queue NOC,
ADMIN
get cos default value displays the 802.1p priority assigned to NOC,
untagged packets. ADMIN
get cos expedite queue returns the expedite queue mode. NOC,
ADMIN
get cos flow mapping returns the status of control and ECFM flow NOC,
mapping ADMIN
get cos qinq itag returns the protocol id of dot1q Q_in_Q inner NOC,
tag. ADMIN
get cos qinq otag returns the protocol id of dot1q Q_in_Q outer NOC,
tag. ADMIN
get cos queue cir displays the CIR(Committed Information NOC,
Rate) for user traffic queues ADMIN
get cos queue mapping displays the assignment of CoS priority level NOC,
values to user queues. ADMIN
Appendix A
229
User
Command Description
Access
get cos queue cbs returns the committed burst size of the CoS NOC,
queues. ADMIN
get cos type returns the CoS type. NOC,
ADMIN
get cos wfq weight displays the weights assigned to each of the NOC,
CoS queues ADMIN
get date time displays current Date and Time to the user. NOC,
ADMIN
get default ipconfig displays default IP Configuration of the NOC,
system. ADMIN
get default gateway returns the system default gateway. NOC,
ADMIN
get diagnostics When a system alarm is present, use this NOC,
command to return a list of up to three ADMIN
critical alarms with possible solutions.
get dropped frames threshold returns the dropped frames threshold set by NOC,
the user in %. ADMIN
get ecfm bw-vsm Allows you to view the current ecfm packet NOC,
information sent to switches whenever a ADMIN
change in bandwidth is made due to HAAM.
get ecfm configuration-errors vlan <vlan-id(1-4094)>] Displays the ecfm configuration-related NOC,
[interface <interface-id>] errors (CFM leak, Conflicting VlanIds, ADMIN
Excessive Levels, etc). The default will show
all port’s error message if error configuration
exists.
get ecfm default-domain Displays the global Default-domain NOC,
parameters along with the modified ADMIN
parameters corresponding to a VLAN.
get ecfm domain [brief | domain-number(1-32)] Display information about the ecfm NOC,
maintenance domain. ADMIN
get ecfm errors Display continuity check error conditions NOC,
logged on a device since it was last cleared. ADMIN
get ecfm error-log [domain <domain-name(1..20)> | This is an Y.1731 command. Displays the NOC,
levelid<level-id(0-7)>] [unaware | vlan <vlan-id(1- Error Log containing the information about ADMIN
4094)>] the errors encountered on the MEP.
get ecfm global information Displays ethernet CFM global information. NOC,
ADMIN
get ecfm loopback cache [brief] [level <level-id(0-
7)>][unaware | vlan <vlan-id(1-4094)>] Displays the Loopback transactions related NOC,
information. ADMIN
get ecfm maintenance-point local [mep | mip] [interface
<interface-number>] | domain <domain_name> | Displays the brief information about NOC,
level<id(0-7)>] maintenance points configured on a device. ADMIN
get ecfm maintenance-points local detail
{mpid<mepid(1-8092)> | mac <aa:aa:aa:aa:aa:aa>} Displays the detailed information about the NOC,
[domain <domain_name> | level<level-id(0-7)>] maintenance end points(MEP) locally ADMIN
[unaware | vlan <integer(1-4094)>] configured on the device. The information
includes thevarious MEPs capabilities,
states, threshold values, etc.
DragonWave Inc.
230
User
Command Description
Access
get ecfm maintenance-points remote [domain <domain-
name(1..20)> | levelid <level-id(0-7)>] Display brief information about remote NOC,
MEPs. ADMIN
get ecfm maintenance-points remote crosscheck [mpid
<id>] [domain <domain-name(1..20)> | level <level-id(0- Display details about the maintenance points NOC,
7)>] [unaware | vlan<integer(1-8191)>][{domain configured statically in a List of MEPIDs ADMIN
<string(20)> | level <integer(0-7)>}][{unaware | (cross check list) of Service.
vlan<integer(1-4094)>}]
get ecfm maintenance-points remote detail {mpid id |
mac <aa:aa:aa:aa:aa:aa> }[domain <domain- Display details about remote MEPs. NOC,
name(1..20)> | level <level-id(0-7)> [unaware | ADMIN
vlan<vlan-id(1-4094)>]]
get ecfm mip-ccm-database [vlanid <vlan-id(1-4094)>]
[macaddress <aa:aa:aa:aa:aa:aa>] [port <port-id>] Displays the ecfm MIP CCM Database NOC,
ADMIN
get ecfm service [brief | service-number(1-32) ]
Display information about Ethernet CFM NOC,
Service (Maintenance Association). ADMIN
get ecfm statistics Displays ecfm statistics. NOC,
ADMIN
get ecfm traceroute-cache Display details about traceroute cache. NOC,
(Traceroute cache displays LTR replies ADMIN
corresponding to each LTM transaction).
get ecfm running config Displays the "set ecfm" commands NOC,
necessary to restore the current state of the ADMIN
database. This is for infomration purposes
only, as the system will automatically save
this information on a "save mib".
get ecfm port [port-number] Displays the ethernet CFM port-specific NOC,
parameters. ADMIN
get enet address returns the ethernet MAC address. NOC,
ADMIN
get enet config returns configuration parameters for ethernet NOC,
Port1 and Port2. ADMIN
get enet interface table returns the ECFM MAC address for each of
the 8 Ethernet ports.
get enet status returns status of ethernet Port1 and Port2. NOC,
ADMIN
get enet speed returns current speed configuration for NOC,
ethernet Port1 and Port2. ADMIN
get fans returns status of the system's fans if present. NOC,
ADMIN
get faulty radios returns the hard fault radios. NOC,
ADMIN
get faulty wireless ports returns the fault wireless ports. NOC,
ADMIN
get feature group upgrade information [index] returns upgrade information of the feature NOC,
group identified by the index (1 through 5) ADMIN
required by DragonWave before an upgrade
key can be issued.
Appendix A
231
User
Command Description
Access
get feature group downgrade information [index] returns downgrade information of the feature NOC,
group identified by the index (1 through 5) ADMIN
required by DragonWave before a
downgrade refund can be issued.
get frequency bank displays Frequency Banks available in the NOC,
System. ADMIN
get frequency file status displays the status of the frequency file. NOC,
ADMIN
get group authentication key returns listing of all group authentication NOC,
keys. ADMIN
get haam returns on or off condition of Hitless NOC,
Automated Adaptive Modulation (haam). ADMIN
Default is ‘off’.
get haam status returns the current status of Hitless NOC,
Automated Adaptive Modulation (haam). ADMIN
Shows current modulation scheme in use.
get haam system modes returns the configured and available system NOC,
modes ADMIN
get health returns operational condition of resources in NOC,
the system. ADMIN
get http secure access [Admin/Noc/Super] returns the HTTPS access for a specific SU
group of users.
get hw inventory displays HW inventory. NOC,
ADMIN
get if loopback displays the status of the if loopback
get if statistics displays information related to the IF card. NOC,

ADMIN
get if status returns the Tx and Rx IF synthesizer lock NOC,
status. ADMIN
get install type returns the system installation type (ODU or NOC,
IDU/ODU split). ADMIN
get ip address returns the system ip address. NOC,
ADMIN
get ipg config returns the configuration of any isolated port NOC,
group (ipg) ADMIN
get ipg status returns the status of any isolated port group NOC,
(ipg) ADMIN
get lag config returns the configuration parameters of any NOC,
link aggregation group (lag) ADMIN
get lag status returns the status of any link aggregation NOC,
group (lag) ADMIN
get leds displays system LEDS with On/Off values. NOC,
ADMIN
get licensed feature group returns a list of licensable feature groups and NOC,
the current status of these groups. ADMIN
DragonWave Inc.
232
User
Command Description
Access
get licensed speed counter returns the counter of upgrading or NOC,
downgrading the licensed speed. ADMIN
get licensed speed downgrade information returns the last time's downgrade NOC,
information. ADMIN
get licensed wireless port counter returns the counter for upgrading the NOC,
wireless port. ADMIN
get logging displays logging is enabled or not. NOC,
ADMIN
get log entries displays all of log entries in memory NOC,
ADMIN
get mac learning returns the ports that have MAC address NOC,
learning enabled or disabled ADMIN
get modem transmitter state returns modem channel mute status NOC,
[wireless_port1/wireless_port2] ADMIN
get modem modulation returns modem modulation type. NOC,
ADMIN
get modem statistics [wireless_port1/wireless_port2] displays modem statistics for the specified NOC,
wireless port. Default wireless_port1 ADMIN
get network management interface returns the type of Ethernet interface used NOC,
for managing the system. ADMIN
get network protocol strict returns value on/off and indicates whether NOC,
the system is network protocol strict. ADMIN
get omni file crc displays Omni File CRC's of executing and NOC,
backup softwares. ADMIN
get optical transmitter state displays the current state of the optical NOC,
transmitter as 'on' or 'off'. ADMIN
get partner returns the information about the partner unit NOC,
in a bandwidth doubling configuration ADMIN
get peer link compatibility returns the status of the peer link NOC,
compatibuility feature ADMIN
get performance log returns the performance log NOC,
ADMIN
get performance logging displays performance logging is enabled or NOC,
not. ADMIN
get port traffic statistics returns the traffic statistics from select ports NOC
ADMIN
get port default priority [port] returns the default priority level assigned to NOC
packets that are received without a VLAN tag ADMIN
get programmed frequency returns RX IF RX RF TX IFand TX RF NOC,
[wireless_port1/wireless_port2] frequencies after setting the programmed ADMIN
frequency for either wireless port 1 or port 2.
get qos return value indicates whether the dot1p qos NOC,
is 'on' or 'off'. ADMIN
Appendix A
233
User
Command Description
Access
get radio band returns the radio band in use in the system NOC,
and a list of others that may be used. ADMIN
get radio gain [wireless_port1/wireless_port2] returns the gain set for the radio connected NOC,
to either wireless port 1 or port 2. ADMIN
get radio loopback Returns the status of the loopback for both NOC,
radio 1 (port 1) or radio 2 (port 2). ADMIN
get radio serial number [wireless_port1/wireless_port2] returns the serial number of the radio NOC,
connected to either port 1 or port 2. ADMIN
get radio statistics [wireless_port1/wireless_port2] returns radio statistics in the system for NOC,
either wireless port 1 or port 2. ADMIN
get radio transmitter state returns the state of the radio transmitter on NOC,
[wireless_port1/wireless_port2] either wireless port 1 or port 2. ADMIN
get radius servers displays all active and configured Radius NOC,
Servers. ADMIN
get radius server deadtime displays how long the system will try talking NOC,
to an unresponsive Radius Server before ADMIN
declaring it dead.
get radius server retransmit displays maximum number of times the NOC,
Radius Client will retransmit per server. ADMIN
get radius server timeout displays Radius Client timeout period when NOC,
talking to server. ADMIN
get radius super user authentication strict indicates authentication strict mode. NOC,
OFF: Super User can login using flash ADMIN
password. ON: No one can login without
Radius
get redundancy config returns user configured redundancy NOC,
parameters ADMIN
get redundancy link monitor parameters gets redundancy link monitor parametes for NOC,
Radio redundancy and HSB ADMIN
get redundancy link switch parameters gets redundancy link hard error monitor NOC,
parameter for link establishing ADMIN
get redundancy mode displays system redundancy mode NOC,
ADMIN
get redundancy peek time returns the redundancy peek time in ms NOC,
ADMIN
get redundancy port config returns the redundancy port group NOC,
configuration defining which ports will make ADMIN
the node switch.
get redundancy port group returns the redundancy port group configured NOC,
in the redundancy ipg group. ADMIN
get redundancy primary wireless port returns the redundancy primary wireless port NOC,
id. ADMIN
get redundancy standby enet state gets programmed ethernet state of the NOC,
standby unit used when redundancy is ADMIN
turned on.
DragonWave Inc.
234
User
Command Description
Access
get redundancy status returns current status of the redundancy NOC,
node ADMIN
get redundancy switch cause returns the redundancy switch cause. NOC,
ADMIN
get redundancy wireless port config returns the redundancy modem configuration NOC,
defining which modem ports will make the ADMIN
node switch.
get rls returns rls option in the system as on/off NOC,
basic/advanced. If two wireless ports are ADMIN
used Anyport/Bothports option is also
returned
get rls dropped frames threshold returns Queue1 Queue2 Queue3 & Queue4 NOC,
maximum allowed drop rate and monitoring ADMIN
period
get rls link control returns RLS user control for re- enabling NOC,
failed link. If on then user has to explicitly ADMIN
enable the link
get rls link enable returns RLS global link enable status as on NOC,
or off. If off the link will be shutdown ADMIN
get rls link monitor parameters returns RLS modem link monitor parameters. NOC,
ADMIN
get rls make rsl displays RLS make RSL parameters. NOC,
ADMIN
get rls signal fault parameters displays RLS signal fault monitor NOC,
parameters. ADMIN
get rls status displays RLS status. NOC,
ADMIN
get rsl threshold returns the RSL threshold set by the user. NOC,
ADMIN
get sessions returns information on current Network NOC,
Management sessions. ADMIN
get snmp access mode specifies whether SNMP 'v1' and 'v2c' NOC,
requests are enabled. ADMIN
get snmp managers returns a list of managers that may access NOC,
the system via SNMP. ADMIN
get snmp set request specifies whether SNMP 'v1' and 'v2c' 'Set' NOC,
requests are enabled. ADMIN
get snmp traps returns list of traps that are available in the NOC,
system. ADMIN
get snmp trap hosts returns the list of receivers of snmp traps. NOC,
ADMIN
get snmpv3 managers returns a list of managers that may access SU
the system via SNMP Version 3.
get snmpv3 trap hosts returns the list of receivers of snmp traps in NOC,
V3 mode. ADMIN
Appendix A
235
User
Command Description
Access
get snr threshold returns the SNR threshold. NOC,
ADMIN
get sntp returns the SNTP status: whether it is on/off NOC,
and the list of SNTP servers ADMIN
get sntp offset returns the SNTP time offset in hours: the NOC,
regional time minus Greenwich Mean Time; ADMIN
used to calculate and set the system time
get ssh server returns the status of the SSH server. NOC,
ADMIN
get ssl certificate status returns if the SSL certificate has been SU
created and if it's valid for this IP address.
get subnet mask returns the system subnet mask. NOC,
ADMIN
get super user returns the Super Username and Password SU
stored in the system.
get sw inventory displays Omni File inventory stored in NOC,
FLASH memory; shows primary and backup ADMIN
software in FLASH.
get sw version displays SW versions in the system. NOC,
ADMIN
get switching algorithm returns the radio switching algorithm. NOC,
ADMIN
get synce config Returns the synchronous Ethernet NOC,
configuration details ADMIN
get synce status Returns the status of synchronous Ethernet NOC,
ADMIN
get syslog forwarding host Returns the IP address of the current syslog NOC,
server ADMIN
get syslog forwarding status Displays the status of syslog forwarding NOC,
ADMIN
get system capacity returns the system capacity configuration. NOC
get system mode displays the system mode NOC,
ADMIN
get system speed returns the speeds of system. NOC,
ADMIN
get system summary displays system summary information NOC,
ADMIN
get telnet access displays whether the Telnet Access is NOC,
enabled or disabled. ADMIN
get traffic statistics returns traffic statistics in the system. NOC,
ADMIN
get transmit power [wireless_port1/wireless_port2] returns transmit power level set for the radio NOC,
connected to either wireless port 1 or port 2. ADMIN
DragonWave Inc.
236
User
Command Description
Access
get unique peer authentication key returns SN of system with which system NOC,
communicates within UNIQUE authentication ADMIN
mode.
get user accounts displays both Admin and NOC user accounts SU
get user session displays the LogIn status of the user SU
(including only telnet and SSH sessions).
get vlan config returns the current VLAN configuration NOC,
ADMIN
get vlan status returns the current status of VLAN’s NOC,
ADMIN
get web server returns the web server on or off. NOC,
ADMIN
get xpic returns the status of xpic NOC,
ADMIN
kill ssh sessions terminates all the active ssh sessions. SU
list [ftp:file/directory/empty] or list displays list of files/directories residing in NOC,
[sftp:file/directory/empty] FTP/SFTP Server. If nothing specified ADMIN
displays user's default/current working
directory contents.
lo terminates the user's session with the NOC,
system. ADMIN
ping [-w timeout][-n count][-t] abc.def.ghi.jkl A basic ping utility. t - Ping the specified host NOC,
until stopped. To stop type Control C. n count ADMIN
- Number of echo requests to send. w
timeout - Timeout in milliseconds to wait for
each reply.
remove faulty radio [radio serial#] removes the hard fault radio serial number NOC,
from the hard fault radio list. ADMIN
remove faulty wireless ports removes the faulty wireless port. NOC,
[wireless_port1/wireless_port2] ADMIN
reset [resource id] resets an individual resource or the entire NOC,
system. [resource id] is one of the following: ADMIN
system/modem
save config [ftp:fileName] or save config saves the configuration commands to user SU
[sftp:fileName] specified file in the FTP/SFTP server.
save ecfmmib Perform this command to save ecfm settings
to FLASH. This command does not restart
the system and does not put any new
settings into effect.
save l2swmib saves system management parameters and NOC
the l2sw configuration to flash
save log [ftp:fileName] or save log [sftp:fileName] saves the event logs to user specified file in NOC,
the FTP/SFTP server. ADMIN
save mib saves mib to the flash. NOC
save performance log [ftp:fileName] or save saves the performance logs to user specified NOC,
performance log [sftp:fileName] file in the FTP/SFTP server. ADMIN
Appendix A
237
User
Command Description
Access
save users [ftp:fileName] or save users [sftp:fileName] saves the user account information to user SU
specified file and stores in the FTP/SFTP
server.
set admin user allows the user to set up Admin Accounts. SU

( Max of 50 accounts are allowed)
set air interface authentication type [authentication sets the authentication type of the air NOC
type] interface. [authentication type] is one of the
following: none/ unique/group
set alarms counter [0] clears alarm counters. NOC,
ADMIN
set alignment [on/off] [-tsecs] [wireless_port1] Enables RSL measurement capabilities on NOC,
[wireless_port2] the BNC style connector on the Quantum ADMIN
radio. Gives the option to monitor port 1 or
port 2 and provides for a timeout after which
the feature automatically turns off. The
timeout period [-tsecs] can be set between
60 and 600 seconds with 60 being the
default.
set antenna diameter [index of diameter] sets the programmed antenna diameter. For NOC,
use with radio band un24. ADMIN
set atpc (on/off) sets the atpc status (on/off) NOC
set atpc coordinatedpower (on/off) [0. 0 10.0] sets the atpc coordinated power (on/off) and NOC
[coordinated power offset]
set atpc parameters (0.1 20.0) (0.1 1.5) (0.1 20.0) sets atpc parameters (fade step) (rsl SU
hysteresis) and (max. atpc)
set authentication failure [action] configures the action to take on peer NOC
authentication failure. [action] is either
block_traffic or pass_traffic.
set bac [1,2,3,4,all] [on/off] [block size] sets bandwidth acceleration parameters NOC
(bac) per queue. Allowed block sizes are
256, 512, 1024, 4032 and 8000 bytes.
set bac record average period [seconds] sets the average period used for computing NOC
the running average bac gain and
uncompressed ratio. Default average period
is set to 10 seconds.
set bac record logging [1,2,3,4] [on/off] Allows the user to enable/disable logging of NOC
bac related statistics.
set bandwidth doubling mode [primary|secondary|off] enables or disables a system as either a NOC
primary or secondary unit in the bandwidth
doubling configuration
set bandwidth doubling port [p1 – p8] sets the port that will support bandwidth NOC
doubling
set bandwidth record logging [on|off] turns bandwidth logging on or off. SU
DragonWave Inc.
238
User
Command Description
Access
set bandwidth record thresholds [10 20 30…95] configures the 10 bandwidth utilization SU
threshold integers.
set bandwidth utilization threshold [threshold] [time sets the % utilization of bandwidth Threshold. NOC
limit] The time that the threshold must be crossed
in order for it to be considered an
alarmable/trappable event is specified by the
user. The default time limit is 10 secs.
set cos control flow mapping [on|off][queue_id] sets control flow mapping on/off and directs SU
the frames to any one of the four QoS
queues, or QC
set cos cut through queue [on {q1 – q4]|off] enables or disables the desired cut through NOC
queue
set cos default value [0-7] sets the 802.1p priority level for untagged NOC
packets.
set cos ecfm flow mapping [on|off][queue_id] sets ecfm flow mapping on/off and directs the SU
frames to any one of the four QoS queues, or
QC. This is overridden if ECFM is enabled on
the node.
set cos expedite queue [on/off] sets the expedite queue to on or off. NOC
set cos qinq itag [protocol id] sets the protocol id of dot1q Q_in_Q inner NOC
tag.
set cos qinq otag [protocol id] sets the protocol id of dot1q Q_in_Q outer NOC
tag.
set cos queue cbs [0-100,0-100,0-100,1-100] sets the committed burst size of the cos NOC
queues. Value rangesfrom 1% to 100% of
total memory.
set cos queue cir [0-100 0-100 0-100 0-100] sets the CIRs for user traffic queues NOC
set cos queue mapping [1/2] assigns the user queue to cos value. NOC
Maximum 8 assignments are allowed in a
command one for each priority level value.
set cos type sets the cos type. NOC
[cos_vlan/cos_qinq_itag/cos_qinq_otag/cos_dscp]
set cos wfq weight [w1 w2 w3 w4] assigns a weight value to each priority
queue. Weight values must total 16.
set date time [dd/mm/yyyy hh:mm:ss:ms] sets the calendar date and time on the NOC,
system, where dd = day (01 to 31), mm = ADMIN
month (01 - 12), yy = year (1970 - 2099), hh
= hour (0 - 23), mm = minute (0 - 59), ss
=second (0 - 59), ms = millisec (0 - 999)
set default gateway [abc.def.ghi.jkl] sets the system default gateway. NOC
set dropped frames threshold [threshold] [time limit] sets the threshold limit (in %) for dropped NOC
frames. The time that the threshold must be
crossed in order for it to be considered an
Appendix A
239
User
Command Description
Access
set ecfm [on | off] Enables or disables connectivity fault NOC
management (CFM) processing globally on
this device. The default is "off".
set ecfm associate vlan-id {vlan-id | vlan-list} primary-
vlan-id <vlan-id(1-4094)> Associate a list of Vlan-Ids to a Primary Vlan. NOC
set ecfm bw-vsm enables you to configure the content of ecfm NOC
packets sent to network switches in relation
to changes in bandwidth produced by HAAM.
set ecfm cc enable level [disable] {levelid | level-list} Enables or disables the transmission of NOC
[vlan {vlanid | vlan-list}] continuity check messages (CCMs).The level
ID and Vlan ID identifies the Maintenance
End Points (MEPs)to which the configuration
applies if Vlan is not specified, enables the
transmission of CCMs at specified levels for
Vlan unaware MEPs only.
set ecfm cc level {<level-id(0-7)> | level-list} {<default > Sets parameter (CCM Interval) for continuity NOC
| [vlan {<vlan-id(1-4094)> | vlan-list}] [interval {ten-sec | check messages (CCMs). The level ID and
one-min | ten-min}]} Vlan ID identifies the Service (Maintenance
Association) to which the configuration
applies.
set ecfm ccm-unicast-mac [aa:bb:cc:dd:ee:ff] This is an Y.1731 command. Sets the NOC
destination mac-address for ecfm unicast
Continuity Check Messages.
set ecfm default-domain global levelid <(0-7)> Defines or deletes a connectivity fault NOC
management (CFM) Maintenance Domain
(MD) at a particular maintenance level and
puts the device in Ethernet CFM
configuration mode, where parameters
specific to the maintenance domain can be
set.
set ecfm default-domain vlan <integer(1-4094)> Sets the parameters of default Maintenance NOC
([level<integer(0-7)>][mip-creation-criteria {none | Domain (MD) Level, to control MHF creation
explicit | defer | default}][sender-id-permission {none at the VLAN Ids which are not attached to
|chassis | manage | chassis-mgt-address | defer }]) any Service (Maintenance Association) and
SenderID TLV transmission by those MHFs
set ecfm domain <domain-name(1..20)> level <level- Defines or selects a connectivity fault NOC
id(0-7)> [delete] management (CFM) Maintenance Domain
(MD) at a particular maintenance level,
where parameters specific to the
maintenance domain can be set.
set ecfm error-log [on | off] [size <entries (1-4096)>] This is Y.1731 command. Enables or NOC
disables the logging of Continuity Check
errors that occurred on the device in the
Error Log table and also sets the maximum
size of the table.
set ecfm mep archive-hold-time {<minutes(100-65535) | Sets the amount of in minutes time such that NOC
default } information from a MEP is kept in the CC
database before they are purged. Defaults
set to 100 minutes.
DragonWave Inc.
240
User
Command Description
Access
set ecfm mep-capability level {<level-id(0-7)> | level-list} This is an Y.1731 command. Enable (on) or NOC
[on|off] [vlan {<vlan-id(1-4094)> | vlan-list}]([ping] disable (off) the capabilities of all the MEPs
[muliticast-ping] [turnaround-delay] [rdi]) in a MA at the level and vlan. Defaults to
enable if on/off not specified.
set ecfm mep crosscheck mpid <integer(1-8191)> Statically defines maintenace end point NOC
[delete|define] [vlan <integer(1-4094)>] (MEP) or remote MEP. (MEP is defined in a
list of MEPIDs of a service associated with a
provided VLAN)
set ecfm mep crosscheck start-delay {default} | {start- To configure the number of CCMs to be NOC
delay<3-100>} missed, for which a device waits for the
remote maintenance end points (MEPs) to
come up. The default: the number is reset to
the default value of 3.
set ecfm mep level [<0-7>] [delete] [inward] [mpid <id(1- Configures or deletes a local Maintenance NOC
8191)>] [vlan<vlan-id(1-4094)>] [active] end point (MEP) (Sets an port as a domain
boundary (edge)by defining it as a MEP),
and sets direction for the MEP.)
set ecfm mip ccm-database caching [enable | disable] Enable or disable Ethernet CFM MIP-CCM NOC
database caching
set ecfm mip ccm-database size [<entries (1000- Sets the number of entries in the ecfm ccm- NOC
10000)>] database, in hours. The default is 1000
entries.
set ecfm mip ccm-database hold-time [<hours (24-48)>] Sets the hold time for the ecfm ccm- NOC
database, in hours. The default is 24 hours.
set ecfm mip dynamic evaluation Enables or Disables the implicit evaluation NOC
and creation of a MIP. This command is NOT
supported in this Horizon Quantum release.
set ecfm mip level [delete] <level-id(0-7)> vlan <vlan- Configures a Maintenance intermediate point NOC
id(1-4094)> [active] (MIP) at the specified level and vlan on an
interface. “active” - makes MIP operationally
active, by default MIP is configured as
operationally active.
set ecfm oui [xx :yy :zz] Configure the Organization Unit Identifier NOC
(OUI). Organizationally Unique Identifier
(OUI) is a 24-bit number that is purchased
from the Institute of Electrical and Electronics
Engineers.
set ecfm port [port number] [on |off] Sets the port number that subsequent ecfm NOC
commands will apply to.
set ecfm service <{[config] <service_name> [{icc Configures the provided Service NOC
<icc_code> umc <umc_code>] [vlan <vlan-id(1-4094)>] (Maintenance Association) at the specified
[mip-creation-criteria {none | default | explicit | defer}] vlan. User can configure ICC and UMC when
[sender-id-permission {none | chassis | manage | Y.1731 is enabled.
chassis-mgt-address | defer}]}>| <{delete
<service_name>
set ecfm start Start the Ethernet CFM Module globally on NOC
the ODU
Appendix A
241
User
Command Description
Access
set ecfm traceroute cache Enables Linktrace replies (LTR) caching.The NOC
default: it is disabled.
set ecfm traceroute cachesize Sets maximum size for the Linktrace reply NOC
(LTR) table. Traceroute caching should be
enabled and cache should be empty
set ecfm traceroute holdtime {default | integer(1- Sets Linktrace replies (LTR Table) maximum NOC
65535)} age. The default : hold time is 100 minutes.
set ecfm y1731 [on | off] Enables(on) or disables(off) Y.1731 NOC
processing globally on a device.
For Y.1731 to be enabled, ecfm should be
enabled. When Y.1731 is off, ecfm default
protocol is 802.1ag
set enet config Configures the characteristics of the NOC
specified Ethernet port. This is a interactive
command.
set enet speed port[port1 / port2] sets the ethernet speed for the specified port. NOC
speed[10/100/1000/auto] AutoNeg[auto] Last argument AutoNeg is optional.
set frequency bank [txhigh/txlow] allows the user to select Frequency bank NOC,
available in the system. ADMIN
set group authentication key [key] writes a group authentication key. [key] is a NOC
32 bit integer.
set haam [on/off] set Hitless Automated Adaptive Modulation NOC
(haam) to 'on' or 'off'
set haam manual mode [on/off] Needs to be set ON to enable the “diagnose NOC
haam [up/down]” command.
set haam mode range [highest] [lowest] configures the highest and lowest modes that NOC
will be used for haam. The default is the
same as the available system modes.
set http secure access [Admin/Noc/Super] [on/off] Sets the HTTP Secure access to a group of SU
users on or off.
set if loopback [on/off] [-tseconds] [wireless_port1] sets the IF loopback on for the specified time
[wireless_port2] (seconds) for the specified wireless port
(default is wireless_port1 for 30 seconds).
set ip address [abc.def.ghi.jkl] sets the system ip address. NOC
set ipg config sets the configuration of an isolated port NOC
group (ipg).
set logging [on/off] sets logging on [enabled] or off [disabled]. NOC,
ADMIN
set lag config sets the configuration of a link aggregation NOC
group (lag)
set mac-learning [enable|disable (p1 – p8 dp1 – dp4)] enables or disables the ports that support NOC
MAC address learning
set network management interface [port1/port2/port2 sets the interface network management used NOC
extended] for managing the system.
DragonWave Inc.
242
User
Command Description
Access
set network protocol strict [on/off] sets the system network protocol strict mode NOC
on/off.
set noc user allows the user to set up NOC account. SU
Username and Password cannot be empty. (
Max 5 NOC accounts are allowed).
set optical transmitter state [on/off] sets the state of the optical transmitter as 'on' NOC
or 'off'.
set partner [p1 – p8][hostname] sets the management interconnection port NOC
and the name of the partner system in the
bandwidth doubling feature. Typically, this is
the MAC address of the partner.
set peer link compatibility sets the system to be compatible with a NOC
Horizon Duo
set performance logging sets the performance logging on[enabled] or NOC,
off [disabled]. ADMIN
set performance log interval [hr:min:sec] sets the performance log interval. NOC,
ADMIN
set port default priority [port] sets the deault priority that you wish to apply NOC
to packets arriving without a VLAN tag
set port traffic statistics clear clears the current traffic statistics for a select, NOC
or all, ports.
set programmed frequency [IndexID][wireless_port1 / sets the frequency of the TX IF and RF stage NOC
wireless_port2] for [wireless_port_1 wireless_port_2]. [Index
ID] is the index of frequency list specified in
'get frequency bank' command. Before using
this command first set the available
Frequency.
set qos [on/off] enables or disables quality of service (QoS) NOC
set qos policy [strict_priority|wfq] selects the policy under which the QoS NOC
feature operates
set radio band [radioBandName] sets the radio frequency band to be used in NOC
the system. Radio bands supported by the
system can be obtained using 'get radio
band' command.
set radio loopback [on/off] [-tsecs] [network] Enables either a radio loopback alone or a NOC
[wireless_port1] [wireless_port2] radio and data loopback [network] on either
port 1 or port 2 for a preset period of time [-
tsecs]. Time between 30 and 300 seconds is
The Network Loopback is not supported in this configurable. The loopback will automatically
release. If attempting this command the be turned off after the timeout period has
following message will be displayed. expired, or “set loopback off” is issued. The
far end radio is automatically muted for the
'network' option is not supported same time period when loopback is invoked.
set radio transmitter state [on|off] allows user to mute/unmute the radio NOC,
[wireless_port1/wireless_port2] transmitter connected to either wireless port ADMIN
1 or port 2.
set radio serial number [primary/secondary] sets the [primary/secondary] radio serial NOC,
number. ADMIN
Appendix A
243
User
Command Description
Access
set radius server host [index] [server addr] sets the host address for server specified by SU
[index].
set radius server key [index] [key] sets the shared key for server specified by SU
[index].
set radius super user authentication [On/Off] sets the Radius Authentication Strictness SU
mode. OFF:SUper User can login using flash
password. ON: No one can login without
Radius.
set redundancy ipg [ hsb[1-3] [enable|disable] user- Configures the IPGs for redundancy. Where
port[p1-p8] inter-port[p1-p8] data-ports[dp1..dp4] ] user-port is the user ethernet port and inter-
port is the port connected to the partner.
set redundancy link monitor parameters sets the link monitor parameters for HSB NOC,
[fault period(msec)] [fault threshold(%)] when 2 parameters are entered ADMIN
set redundancy link monitor parameters when 10 parameters are entered, sets the NOC,
[1-primary_radio | 2-secondary_radio] [mk erred blks] link monitor parameters for radio redundancy ADMIN
[brk erred blks] [mk samples] [brk
samples] [mk sample time] [brk sample time] [brk
sample rst time] [fault period(msec)] [fa
ult threshold(%)]
set redundancy link switch parameters [prim. time in sets redundancy hard error monitor NOC,
active state] [prim. switch error thresh] [second. time in parameters for link establishing. Period is ADMIN
active state] [second. switch error thresh] specified in milliSec and threshold in
percentage. (prim. - primary, second. -
secondary)
set redundancy mode [radio_hsb |primary_hsb allows the user to configure redundancy NOC,
|secondary_hsb |off] ADMIN
set redundancy peek time sets the redundancy peek time to (50-5000) NOC,
ms ADMIN
set redundancy port config [all | any] A value of 'all' will cause the node to switch NOC,
when 'ALL' redundancy ports are down. ADMIN
A value of 'any' will cause the node to switch
when 'ANY' redundancy port is down.
set redundancy primary wireless port [wireless_port1 / sets the radio redundancy primary wireless NOC,
wireless_port2] port id. ADMIN
set redundancy standby enet state [on |off |pulse] allows the user to program required action on NOC,
standby redundancy port group. ADMIN
set redundancy state switch [on] allows the user to force a change in the NOC,
redundancy state when the switch mode is ADMIN
'auto'. The user input is not stored in the
system and set to off after the state change.
set redundancy switch mode [force_active Allows the user to force the state of the NOC,
|force_standby |auto ] redundancy link ADMIN
set redundancy wireless port config [ all | any ] a value of 'all' will cause the node to switch NOC,
when 'ALL' modem ports are down. ADMIN
a value of 'any' will cause the node to switch
when 'ANY' modem port is down.
DragonWave Inc.
244
User
Command Description
Access
set rls drop frames threshold [q1/q2/q3/q4] [0-100%] [0- sets Queue1 Queue2 Queue3 & Queue4 NOC,
131] maximum allowed drop rate and monitoring ADMIN
period.
set rls dropped frames override If the rls is down due to dropped frames it will NOC,
bring back the link. If the link condition still ADMIN
exceeds the RLS queue settings, RLS will be
activated.
set rls [on/off] / [basic-advanced] / [anyport-bothports] sets the RLS mode on/off and optionally NOC
basic/advanced if two wireless ports are
used anyport/bothports.
set rls link control [on/off] sets the RLS user link enable option. When NOC
this is set to 'On' the user has to explicitly
enable the link after it recovers from a fault.
set rls link enable [on/off] sets the RLS global link enable status. If on NOC
and no link error exists the link will be
enabled.
set rls link monitor parameters [mk erred blks] [brk sets the RLS link monitor low level NOC
erred blks] [mk samples] [brk samples] [mk sample parameters.
time] [brk sample time] [brk sample rst time]
set rls make rsl [make rsl threshold] [rsl mk sample time sets the RLS make RSL threshold and NOC,
sec] sample period where: [make rsl threshold]: ADMIN
the minimum rsl threshold to establish the
link [make rsl sample period]: the time the
link rsl must be above the threshold to
establish the link.
set rls signal fault parameters [fault period msec] [fault sets the RLS signal fault monitor parameters NOC,
threshold] where [fault sample period msec]: sample ADMIN
period to apply Fault Threshold ratio [fault
threshold percentage]: ratio of 'fault sample
period' faulted before link is shut down.
set rsl threshold [threshold] [time limit] sets the RSL threshold for the system. The NOC
time that the threshold must be crossed in
order for it to be considered an
set snmp access mode [v1/v2c/off] specifies whether SNMP v1 and v2c NOC
requests are enabled.
set snmp manager [Mgr Index] [ipAddress] adds a SNMP manager to the list of allowed NOC
[enable/disable] [communityString] SNMP managers of the system.
set snmp set request [on/off] allows SNMP v1 and v2c 'set' requests. NOC
set snmp trap [trap#] [enable/disable] enables or disables particular SNMP trap in NOC
the system.
set snmp trap host [host#] [ipAddress] [enable/disable] adds an SNMP trap host to the list of NOC
[communityString] receivers of snmp traps.
set snmpv3 manager adds a SNMP v3 manager to the list of SU
allowed SNMP v3 managers of the system.
set snmpv3 trap host authentication [index] sets the authentication protocol and NOC
[none/md5/sha] [passwd] password for an snmpV3 trap host.
Appendix A
245
User
Command Description
Access
set snmpv3 trap host enable [index] enables an snmpV3 trap host. NOC
set snmpv3 trap host disable [index] disables an snmpV3 trap host. NOC
set snmpv3 trap host ip [index] [ipAddress] sets the IP address of an snmpV3 trap host. NOC
set snmpv3 trap host user [index] [userName] sets the user name of an snmpV3 trap host. NOC
set snmpv3 trap host privacy [index] [none/des] sets the privacy protocol and password for NOC
an snmpV3 trap host.
set snr threshold [SnrThreshold] configures the SNR threshold. SNR NOC,
Threshold is an integer. ADMIN
set sntp [on/off] turns SNTP on or off. NOC,
ADMIN
set sntp default sets SNTP to default settings: SNTP is on by NOC,
default. SNTP servers are used, 10 minute ADMIN
polling. SNTP time offset is not altered.
set sntp offset sets the SNTP time offset in hours: the NOC,
regional time minus Greenwich Mean Time; ADMIN
used to calculate and set the system time.
set sntp server writes one SNTP server based on the index NOC,
selected. ADMIN
set ssh server turns the SSH server on or off. SU

set subnet mask [abc.def.ghi.jkl] sets the system subnet mask. NOC
set super user allows the user to change the super SU
Username and Password. Username and
Password cannot be empty.
set switching algorithm [manual/alarm based/algorithm sets the radio switching algorithm NOC,
based] [manual/alarm based/algorithm based]. ADMIN
set synce forced holdover This is a user troubleshooting command NOC
which forces the system into holdover mode
for a configurable timeout value (time) in
seconds. The default timout is 30 seconds.
Values can be 0 to 300 seconds. 0 keeps the
holdover on indefinitely.
set synce member port [p3-p8|wp1|wp2|freerun] This command allows you to add all the ports NOC
that are required to handle SynchE into the
member port group. Note that in order to
configure the ports that are to be the primary
and secondary clock sources, the ports must
first be made part of the member port group.
DragonWave Inc.
246
User
Command Description
Access
set synce mode [off|manual|auto] Use this command to enable SyncE. Select NOC
manual when you want the system to go into
holdover when the primary clock source fails.
If the primary source recovers, the system
will automatically switch back to the primary
source. Select auto if you want the system to
switch to the secondary clock source if the
primary clock source fails. In auto the system
will not switch back to the primary if the
primary clock recovers, unless set synce
revertive is enabled.
set synce primary source [p3-p8|wp1|wp2|freerun] This command allows you to select which NOC
port is to be the primary clock source. Note
that the port must be configured as a GigE
port (1000 Mbps). Note, also, that ports p1
and p2, being SFP ports cannot be used as a
clock source.
set synce revertive [on|off] [time] This command allows you to enable or NOC
disable the revertive mode. On a primary
clock source failure and provided that the
SyncE mode is configured for auto, when
revertive mode is enabled (on), it allows the
system to automatically revert back from the
secondary to the primary clock source, once
the primary clock source has recovered and
remains stable for a selected time in
seconds. Time range is 10 to 300 seconds.
The default time is 10 seconds.
set synce secondary source [p3-p8|wp1|wp2|freerun] This command allows you to select the port NOC
that will provide the secondary clock source.
It will take over from the primary clock source
if the primary clock source fails. Note that
unless the revertive feature is enabled (set
synce revertive on), if, after a switch to the
secondary clock source, the primary clock
source recovers, the system will not
automatically switch back from secondary to
the primary clock source.
set synce wander filter [option1 | option2] This command allows the user to select NOC
either Ethernet Equipment Clock filter Option
1, or Option 2. Option 1 would be used in the
E1 TDM hierarchy and Option 2 in the T1
TDM hierarchy.
set syslog forwarding host [IP address] Sets the IP address of the syslog server to NOC,
which log entries can be sent ADMIN
set syslog forwarding [on|off] Enables or disables syslog forwarding NOC,
ADMIN
set system capacity [optionIndex] sets the system capacity index as listed by NOC
'get system capacity' command.
set system mode [system mode name] sets the system mode. NOC
set system current speed [speed] sets the current speed in Mbps. NOC
Appendix A
247
User
Command Description
Access
set traffic statistics [0] clears all traffic statistics including extended NOC,
statistics to 0. Only parameter accepted is '0'. ADMIN
set telnet [on/off] enables or disables the Telnet Access to the NOC
user. (Access: Only through Serial Port)
set transmit power <value> sets the transmit power level for the system. NOC,
[wireless_port1/wireless_port2] If atpc is enabled transmit power can't be set. ADMIN
set unique peer authentication key [key] stores SN of system that the system will be NOC
communicating with.
set vlan config sets the vlan configuration of the system NOC
set web server [on/off] sets the embedded web server on or off. This SU
applies to both HTTP and SSL.
set xpic mode [master | slave] sets the current system as a master or slave NOC
for xpic purposes.
set xpic [on | off] enables or disables xpic NOC
switch bank [a/b] The switch command sets the next-active NOC
boot bank. The banks are named “Bank A”
and “Bank B”.
switch radio forces a redundancy radio switch over. NOC,
ADMIN
traceroute abc.def.ghi.jkl returns the route taken by Ethernet packets NOC
to the input ip address.
upgrade feature group [index][key] allows the user to upgrade to a feature group NOC
(index 1 through 5) with the license key
provided by DragonWave.
upgrade system licensed speed [speed] [key] allows the user to upgrade the licensed NOC
speed.
upgrade wireless port [key] allows the user to upgrade to two wireless NOC
ports.
DragonWave Inc.
248

Appendix B - Site Survey Information
Planning
When installing a microwave link, proper planning is required. Items to be addressed for proper planning
include:
• RF path planning • lightning and ground
protection
• site preparation, including power and LAN
connections • surge protection
• installation issues for outdoor units including • use of outdoor cabling
modem and Radio
• other radio system at the
• Governing body licensing issues (FCC, etc) same frequency
• Check local, regional, and national building
and electrical codes
Site Survey
A site visit must be done prior to installation to ensure proper line of sight path clearance exists and that
proper facilities exist at the site according to the details listed below.
Line–of–Sight and Path Clearance. Determine optimum location for the radio. Radio and antenna location
are important to ensure optimum radio range and throughput:
• Install the antenna as high as possible to maximize the range of a building-to-
building connection
• Maintain a clear line–of–sight between Horizon Quantum antennas. Obstructions
can impede performance or limit ability to transmit or receive data. Reduced signal
strength could affect performance; and
• Maintain maximum path clearance at both ends for the directional antennas.
When determining maximum path clearance, be aware of objects that restrict performance such as:
• Buildings
• Trees
• Rooftop objects such as a/c units
• Conductive metal surfaces
• standing pools of water
• edges of the roof (parapet) of the building on which the Horizon Quantum is to be
mounted.
DragonWave Inc.
250
Site Preparation
When you visit the site, be sure to record all installation requirements. You will need to determine the
following:
• Other equipment in the area which can potentially interfere with the DragonWave Radios
• Ability to install the Horizon Quantum units.
 Facilities exist on which to mount the unit? (3” – 4” diameter pole/mast mount, tower
mount, wall mount);
 A mast or tower mount exists and is there sufficient room (clearance) to install the
Horizon Quantum unit;
 The mast or tower has the ability to withstand wind load due to mounting of the Horizon
Quantum units;
 Permits that may be required; and
 Documentation required by building or site owner/landlord.
• Obstructions, such as tree growth or new buildings, that may be a problem in the future
If the Outdoor Unit (ODU) is being installed, the all-in-one cable will likely have to transit the outside wall
and terminate on equipment located inside the building. If the Indoor Unit (Rack mount IDU) is being
installed, the IF cable from the radio will likely have to transit the outside wall and terminate at the IDU.
Determine the following:
 Cable distance between Horizon Quantum and network equipment and the distance to
the power source. DragonWave offers 3 lengths (30m, 60m, 90m).
 Location of building penetration point (drainage or service openings, elevator service
sheds, other rooftop openings, or penetration through an outside wall).
 Size (diameter) of hole at the building access point. Check for other cables and
clearance for Horizon Quantum cables.
• Location of the nearest appropriate power outlet
• Location of the nearest ground bar or ground plane bus
• Power backup, such as Uninterruptible Power Supply (UPS)
• Location and ease of access to wiring closets
• Location and ease of access of network equipment (switch, router, etc)
• Grounding points for lightning arrestors and cable shields at building entry point
• Locations and grounding points for surge protectors.
• Check local electrical codes for requirements for lightning rods.
• If possible, ensure that Horizon Quantum installations will be lower in height than existing
lightning rods
Note: Record all installation requirements, including cable lengths, GPS co-ordinates (height, Lat., Long)
and distance between the sites.
Appendix C - 802.1P Priority Tagging Overview
IEEE 802.1P The Institute of Electrical and Electronics Engineering (IEEE) 802.1P signaling method is
used for traffic prioritization at OSI Reference Model Layer 2. 802.1p is a spin-off of the 802.1Q (Vlans)
standard. Network adapters and switches route traffic based on the priority level for best-effort Quality of
Service (QoS).
The 802.1Q VLAN standard specifies a VLAN tag that appends to a MAC frame. The VLAN tag has two
parts: The VLAN ID (12-bit) and Prioritization (3-bit). The prioritization field was not defined in the VLAN
standard and the 802.1P implementation defines this prioritization field.
To be compliant with 802.1p, Layer 2 switches must be capable of grouping incoming LAN packets into
separate traffic classes.
Eight classes are defined by 802.1p. Although network managers must determine actual mappings, IEEE
has made broad recommendations. The highest priority is seven, which might go to network-critical traffic
such as interactive video and voice. Data classes four through one range from controlled-load
applications such as streaming multimedia and business-critical traffic - carrying voice traffic, for instance
- down to "loss eligible" traffic. The zero value is used as a best-effort default, invoked automatically when
no other value has been set.
IP protocols can efficiently transport various data types over the same network resources. IP traffic is
“bursty” in nature and requires flow control, buffering, and other mechanisms to deal with this “bursty”
traffic when networks are heavily loaded. The performance attributes of time-sensitive traffic streams,
such as voice and video conferencing, are of particular concern when implementing IP networks. The
majority of time-sensitive traffic streams (VoIP, TDM over Ethernet, etc) do not have control protocols to
negotiate speeds or re-transmits. Traffic is sent assuming delivery and ordering is unchanged.
Ethernet-based architectures require buffering capacity to absorb typical IP bursty traffic and to prevent
packet loss to maintain Service Level Agreements (SLAs).
802.1P COS/QOS is used to accommodate bursty IP traffic
CoS vs QoS
What Is Quality of Service?
Quality of Service (QoS) is a traffic management scheme that allows you to create differentiated services
for network traffic, thereby providing better service for selected network traffic.
QOS works by slowing down unimportant packets, or discarding those packets under high load. It
therefore delivers the important packets, but at the expense of the unimportant packets.
QoS primarily comes into play when the amount of traffic through an interface is greater than the
interface’s bandwidth.
When the traffic through an interface exceeds the bandwidth, packets form one or more Queues from
which the device selects the next packet to send. By setting the queuing property on a device or interface,
you can control how the Queues are serviced, thus determining the priority of the traffic.
What is Class of Service?
Class of Service (CoS) is an algorithm that tags packets then classifies those packets in order to assign
them to Queues of differing priority. Unlike Quality of Service (QoS) traffic management, CoS does not
ensure network performance or guarantee priority in delivering packets.
In summary: CoS = assigning priority values to data streams
QoS = traffic engineering to process data according to the priority values

Horizon Quantum, R1.3.7, Volume 2, Advanced Configuration Features, Version 1.7 PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Horizon Quantum, R1.3.7, Volume 2, Advanced Configuration Features, Version 1.7 PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Horizon QuantumTM

The information in this document is subject to change without notice and

Copyright (c) DragonWave Inc. 2014. All rights reserved.

10.1 CLASS OF SERVICE TYPES ...................................................................................... 80

19.0 RADIO REDUNDANCY .................................................................................................. 149

22.3.7.4. ENABLING SSL PER USER GROUP...........................................................................197

1.1 Change History

Version Update Point Date

1.2 What’s New in This Release?

This page left blank intentionally

This page is left blank intentionally

1. XPIC - Cross Polarization Interference Cancellation

Required Action Steps

login Log in using the Super user, or a NOC user, account.

Index Licensed Feature Group Is Licensed

Required Action Steps

get feature group upgrade information <group index 1 to 6>

This operation will force to save MIB. Continue? Enter Y(Yes) or

Saving MIB. Please wait for a while...

Required Action Steps

Feature group 'BAC' downgrade confirmation information:

This page is left blank intentionally

4.1 Saving Switch Parameters

4.2 Ethernet Port Configuration

Required Action Steps

login Log in using the Super user, or a NOC user, account.

-->get enet config 1

Required Action Steps

->set enet config

#Press 'Ctrl-X' to exit config process

Apply the above settings ? Enter yes(y) or no(n) y

4.3 Port Status

Required Action Steps

login Log in using the Super user, or a NOC, user account.

View the current operational Display current Ethernet status information.

-->get enet status 3

4.4 Port traffic Statistics

Required Action Steps

login Log in using the Super user, or a NOC, user account.

View the traffic statistics of an Get Ethernet port's traffic statistics.

Required Action Steps

Clear the current statistics of an Clear Ethernet port's traffic statistics.

4.5 Isolated Port Group (IPG)

P3 DP1 DP1 P3 LAN-3

LAN-3 P4 DP2 Q o o DP2 P4

IPG2 IPG1 IPG2

Required Action Steps

login Log in using the Super user, or a NOC, user account.

-->get ipg status

Name Status Port List

-->get ipg config

Name Status Port List

Required Action Steps

Enable or disable IPG’s and Enable or disable an isolated port group.

->set ipg config ipg4 disable

Name Status Port List

Apply the setting immediately, Continue? Enter Y(Yes) or N(No):y

Configuring isolated port group.

-->set ipg config ipg4 enable p2,p8,dp4

Name Status Port List

Apply the setting immediately, Continue? Enter Y(Yes) or N(No):y

Configuring isolated port group.

Required Action Steps