WIN v5.1 BST User-Guide EN
WIN v5.1 BST User-Guide EN
Introduction 1
System Administration 5
Time Synchronization 7
Subscriber Stations 8
Traffic Control 9
Network Discovery and
Management 10
Remote Management 11
Wireless 12
Troubleshooting 13
For WIN7014, WIN7015, WIN7018, WIN7023, WIN7025
WIN7035, WIN7225, WIN7233, WIN7235, WIN7237,
WIN7249, WIN7251, WIN7258
Disclaimer Of Liability
Siemens has verified the contents of this document against the hardware and/or software described. However, deviations between the product
and the documentation may exist.
Siemens shall not be liable for any errors or omissions contained herein or for consequential damages in connection with the furnishing,
performance, or use of this material.
The information given in this document is reviewed regularly and any necessary corrections will be included in subsequent editions. We
appreciate any suggested improvements. We reserve the right to make technical improvements without notice.
Registered Trademarks
RUGGEDCOM™ and ROS™ are trademarks of Siemens Canada Ltd.
Other designations in this manual might be trademarks whose use by third parties for their own purposes would infringe the rights of the
owner.
Security Information
Siemens provides products and solutions with industrial security functions that support the secure operation of plants, machines, equipment
and/or networks. They are important components in a holistic industrial security concept. With this in mind, Siemens' products and solutions
undergo continuous development. Siemens recommends strongly that you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable preventive action (e.g. cell protection concept) and
integrate each component into a holistic, state-of-the-art industrial security concept. Third-party products that may be in use should also be
considered. For more information about industrial security, visit https://www.siemens.com/industrialsecurity.
To stay informed about product updates as they occur, sign up for a product-specific newsletter. For more information, visit https://
support.automation.siemens.com.
Warranty
Refer to the License Agreement for the applicable warranty terms and conditions, if any.
For warranty details, visit https://www.siemens.com/ruggedcom or contact a Siemens customer service representative.
Contacting Siemens
Address Telephone E-mail
Siemens Canada Ltd Toll-free: 1 888 264 0006 ruggedcom.info.i-ia@siemens.com
Industry Sector Tel: +1 905 856 5288
300 Applewood Crescent Fax: +1 905 856 1995 Web
Concord, Ontario https://www.siemens.com/ruggedcom
Canada, L4K 5C7
ii
RUGGEDCOM WIN
User Guide Table of Contents
Table of Contents
Preface ............................................................................................................ xi
Alerts .................................................................................................................................................. xi
Related Documents ............................................................................................................................. xii
System Requirements ........................................................................................................................ xiii
Training ............................................................................................................................................ xiii
Customer Support .............................................................................................................................. xiv
Chapter 1
Introduction ..................................................................................................... 1
1.1 Features and Benefits ................................................................................................................... 1
1.2 Security Recommendations ............................................................................................................ 2
1.3 Supported Modulation Techniques ................................................................................................. 4
1.4 About MIMO ................................................................................................................................ 4
1.5 User Permissions ........................................................................................................................... 5
1.6 SAS Gateway ................................................................................................................................ 5
Chapter 2
Using WIN v5.1 ................................................................................................ 7
2.1 Default User Names and Passwords ................................................................................................ 7
2.2 Logging In .................................................................................................................................... 7
2.3 Logging Out ................................................................................................................................. 8
2.4 Using the Web-Based User Interface ............................................................................................... 8
2.4.1 Dashboard ......................................................................................................................... 9
2.4.2 Navigating the User Interface ............................................................................................ 10
2.4.3 Using Tables .................................................................................................................... 11
Chapter 3
Getting Started ............................................................................................... 13
3.1 Basic Configuration ..................................................................................................................... 13
3.2 Connecting to the Base Station .................................................................................................... 15
3.2.1 Default IP Address ............................................................................................................ 16
3.2.2 Connecting Directly .......................................................................................................... 16
3.2.3 Connecting Remotely ....................................................................................................... 17
3.3 Configuring the Base Station's IP Interface .................................................................................... 18
Chapter 4
Device Management ....................................................................................... 21
4.1 Rebooting the Device .................................................................................................................. 21
4.2 Displaying the Current Status ...................................................................................................... 22
4.3 Displaying Device Information ..................................................................................................... 23
4.4 Configuring Installation Details .................................................................................................... 24
4.5 Viewing Statistics ........................................................................................................................ 26
4.5.1 Enabling/Disabling Select Statistics .................................................................................... 26
4.5.2 Viewing and Clearing Ethernet Statistics ............................................................................ 27
4.5.3 Viewing and Clearing Traffic Statistics ............................................................................... 30
4.5.4 Viewing and Clearing Subscriber Station Statistics .............................................................. 31
4.5.5 Viewing Subscriber Station Connection Statistics ................................................................ 33
4.6 Managing Logs ........................................................................................................................... 35
4.6.1 Configuring Syslog ........................................................................................................... 36
4.6.2 Enabling/Disabling Logs .................................................................................................... 36
4.6.3 Limiting the Size of Log Files ............................................................................................ 38
4.6.4 Manually Uploading Log Files ........................................................................................... 38
4.7 Managing System Files ................................................................................................................ 39
4.7.1 Enabling/Disabling SFTP Sessions ....................................................................................... 40
4.7.2 Configuring the FTP Service .............................................................................................. 40
4.7.3 Uploading Files to the FTP Server ...................................................................................... 41
4.7.4 Downloading a File from the FTP Server ............................................................................ 42
4.7.5 Copying Files from the Primary Memory Bank to the Secondary Memory Bank ....................... 43
4.7.6 Deleting Files from the Secondary Memory Bank ................................................................ 44
4.7.7 Viewing/Cancelling File Transfers ....................................................................................... 45
4.8 Managing Software ..................................................................................................................... 46
4.8.1 Updating RUGGEDCOM WIN .............................................................................................. 46
4.8.2 Changing the Active Software Version ............................................................................... 47
4.8.3 Restoring Factory Defaults ................................................................................................ 47
4.9 Configuring the Maximum Transmission Unit (MTU) ...................................................................... 48
4.10 Managing Redundant Base Stations ............................................................................................ 49
4.10.1 Understanding Redundancy ............................................................................................ 50
4.10.1.1 Master vs. Slave .................................................................................................. 50
4.10.1.2 States ................................................................................................................. 51
4.10.1.3 Faults ................................................................................................................. 52
4.10.1.4 Reachability ........................................................................................................ 52
4.10.2 Configuring Base Station Redundancy .............................................................................. 53
4.10.3 Viewing the Status of Base Station Redundancy ................................................................ 54
iv
RUGGEDCOM WIN
User Guide Table of Contents
Chapter 5
System Administration .................................................................................... 57
5.1 Setting the Operating Mode ........................................................................................................ 57
5.2 Enabling/Disabling SSH Sessions ................................................................................................... 58
5.3 Managing Users and Passwords ................................................................................................... 59
5.3.1 Adding Users ................................................................................................................... 59
5.3.2 Removing Users ............................................................................................................... 61
5.3.3 Changing User Passwords ................................................................................................. 61
5.4 Managing Alarms ........................................................................................................................ 62
5.4.1 Alarm Categories and Severities ........................................................................................ 63
5.4.2 Available Alarms .............................................................................................................. 64
5.4.3 Viewing/Clearing Alarms ................................................................................................... 65
5.5 Displaying the Current Switching Mode ........................................................................................ 68
Chapter 6
Security .......................................................................................................... 71
6.1 Configuring Brute Force Attack Protection .................................................................................... 71
6.2 Enabling Ethernet Port Shutdown Mode ....................................................................................... 72
6.3 Managing Certificates and Keys ................................................................................................... 73
6.3.1 Updating the Certificate and Private Key ............................................................................ 74
6.3.2 Setting the Private Key Passphrase .................................................................................... 75
6.3.3 Generating SSH Keys ........................................................................................................ 76
6.4 Configuring RADIUS Authentication .............................................................................................. 77
6.5 Managing Wireless Authentication ............................................................................................... 78
6.5.1 Configuring Wireless Authentication .................................................................................. 79
6.5.2 Enabling Wireless Authentication ...................................................................................... 79
6.5.3 Configuring AAA Server Settings ....................................................................................... 80
6.5.4 Enabling/Disabling a AAA Server ........................................................................................ 82
6.5.5 Selecting the Active AAA Server ........................................................................................ 83
6.5.6 Viewing the Status of AAA Servers .................................................................................... 84
Chapter 7
Time Synchronization ...................................................................................... 87
7.1 Configuring Time Synchronization ................................................................................................ 87
7.2 Managing GPS ............................................................................................................................ 89
7.2.1 Configuring the GPS Time Source ...................................................................................... 89
7.2.2 Viewing GPS Time Source Information ............................................................................... 91
7.2.3 Viewing Detected GPS Satellites ........................................................................................ 92
7.3 Managing Precision Time Protocol (PTP) ....................................................................................... 94
7.3.1 Understanding Precision Time Protocol (PTP) ...................................................................... 94
Chapter 8
Subscriber Stations ......................................................................................... 97
8.1 Adding a Pre-Provisioned Subscriber Station .................................................................................. 97
8.2 Configuring Uplink and Downlink Settings .................................................................................... 98
8.3 Resetting the Password for a Subscriber Station .......................................................................... 101
8.4 Rebooting a Subscriber Station .................................................................................................. 102
8.5 Deregistering Subscriber Stations ............................................................................................... 103
8.6 Listing the IP Addresses for Registered Subscriber Stations ........................................................... 104
8.7 Accessing the Management Interface for Registered Subscriber Stations ........................................ 105
8.8 Managing Router Adjacency ...................................................................................................... 106
8.8.1 Understanding Router Adjacency ..................................................................................... 106
8.8.2 Enabling/Disabling Broadcasts Between Subscriber Stations ............................................... 107
8.9 Managing Ethernet Traffic ......................................................................................................... 107
8.9.1 Unlocking Ethernet Traffic .............................................................................................. 108
8.9.2 Viewing/Clearing Subscriber Station Traffic Data ............................................................... 108
8.10 Managing Handover ................................................................................................................ 111
8.10.1 Understanding Handover .............................................................................................. 111
8.10.1.1 Neighboring Base Stations ................................................................................. 113
8.10.1.2 DCD Triggers ..................................................................................................... 113
8.10.1.3 Handover in Standalone Mode ........................................................................... 113
8.10.2 Configuring Handover .................................................................................................. 115
8.10.3 Managing Neighboring Base Stations ............................................................................. 115
8.10.3.1 Adding a Neighbor ............................................................................................ 115
8.10.3.2 Verifying the Configuration of a Neighbor ........................................................... 120
8.10.4 Configuring DCD Triggers .............................................................................................. 121
8.10.5 Verifying the Handover Configuration ............................................................................ 123
8.10.6 Manually Handing Over Subscriber Stations .................................................................... 123
8.11 Monitoring Registered Subscriber Stations ................................................................................ 125
8.12 Listing Subscriber Station Connections ...................................................................................... 127
8.13 Listing Subscriber Station Capabilities ....................................................................................... 130
Chapter 9
Traffic Control ............................................................................................... 133
9.1 Enabling/Disabling Priority Tagging Pass-Through ........................................................................ 133
9.2 Managing VLANs ....................................................................................................................... 134
9.2.1 Configuring a VLAN ........................................................................................................ 134
9.2.2 Enabling/Disabling Transparent VLANs ............................................................................. 136
9.2.3 Configuring a VLAN Subscription ..................................................................................... 136
vi
RUGGEDCOM WIN
User Guide Table of Contents
Chapter 10
Network Discovery and Management ............................................................. 165
10.1 Managing SNMP ..................................................................................................................... 165
10.1.1 Configuring SNMP ........................................................................................................ 166
10.1.2 Configuring SNMPv2 .................................................................................................... 166
10.1.3 Configuring SNMPv3 .................................................................................................... 168
10.1.4 Managing SNMP Traps .................................................................................................. 169
10.1.4.1 Available SNMP Traps ........................................................................................ 169
10.1.4.2 Enabling/Disabling SNMP Traps ........................................................................... 179
10.1.4.3 Sending SNMP Traps .......................................................................................... 180
10.1.4.4 Configuring SNMP Trap Destinations ................................................................... 181
10.1.5 Configuring Users for SNMPv3 ...................................................................................... 181
10.1.6 Configuring the SNMP System Group ............................................................................. 184
10.1.7 Viewing SNMPv3 Access Groups .................................................................................... 185
10.2 Managing MAC Addresses ....................................................................................................... 187
10.2.1 Viewing/Clearing the MAC Address Table ....................................................................... 187
Chapter 11
Remote Management .................................................................................... 193
11.1 Configuring Management via a Backhaul Subscriber Station ....................................................... 193
Chapter 12
Wireless ......................................................................................................... 195
12.1 Starting/Stopping Transmissions ............................................................................................... 195
12.2 Managing Wireless Settings ..................................................................................................... 196
12.2.1 Configuring the Base Station Name and ID ..................................................................... 197
12.2.2 Configuring the MAC Layer Settings .............................................................................. 198
12.2.3 Managing the WiMAX Radio .......................................................................................... 199
12.2.3.1 Viewing a Summary of WiMAX Radio Capabilities ................................................. 199
12.2.3.2 Configuring the WiMAX Radio ............................................................................ 200
12.2.3.3 Configuring the Structure of Frames ................................................................... 201
12.2.4 Managing Link Adaptation ............................................................................................ 204
12.2.4.1 Configuring Link Adaptation ............................................................................... 204
12.2.4.2 Configuring DIUCs for Burst Profiles .................................................................... 206
12.2.4.3 Configuring UIUCs for Burst Profiles .................................................................... 207
12.2.4.4 Configuring the Interference Detection Threshold ................................................ 208
12.3 Managing ASN Gateways ......................................................................................................... 209
12.3.1 Configuring the ASN Gateway Connection ..................................................................... 209
12.3.2 Configuring the IP Address for an ASN Gateway .............................................................. 210
12.3.3 Configuring Keep Alive Settings .................................................................................... 210
12.3.4 Determining the R6 Signaling Protocol In Use ................................................................. 211
Chapter 13
Troubleshooting ............................................................................................ 213
13.1 Troubleshooting Resources ...................................................................................................... 213
13.1.1 Pinging an IPv4 Address or Host .................................................................................... 213
13.1.2 Tracing a Route to an IPv4 Host .................................................................................... 214
13.1.3 Viewing/Clearing Aggregate Throughput Statistics .......................................................... 215
13.1.4 Accessing Developer Mode ........................................................................................... 217
13.1.5 Using the Spectrum Analyizer Tool ................................................................................ 217
13.1.5.1 Configuring the Spectrum Analyzer Tool ............................................................. 218
13.1.5.2 Starting/Stopping the Spectrum Analyzer Tool ..................................................... 220
13.1.5.3 Plotting the Spectrum ........................................................................................ 221
13.1.5.4 Freezing the Current Signal ................................................................................ 223
13.1.5.5 Enabling Max Hold ............................................................................................ 223
viii
RUGGEDCOM WIN
User Guide Table of Contents
x
RUGGEDCOM WIN
User Guide Preface
Preface
This guide describes v5.1 of the RUGGEDCOM WIN Web-based user interface and software application running
on RUGGEDCOM WiMAX broadband wireless base stations. The WIN7000 and WIN7200 are members of the
RUGGEDCOM family of mobile WiMAX broadband wireless access systems based on the 802.16e mobile WiMAX
standard. This guide contains instructions and guidelines on how to use the software, as well as some general
theory.
It is intended for use by network operators who are familiar with the operation of networks.
NOTE
Illustrations of the management interface screens are presented for illustrative purposes and may
appear with minor differences in a working system.
CONTENTS
• “Alerts”
• “Related Documents”
• “System Requirements”
• “Training”
• “Customer Support”
Alerts
The following types of alerts are used when necessary to highlight important information.
DANGER!
DANGER alerts describe imminently hazardous situations that, if not avoided, will result in death or
serious injury.
WARNING!
WARNING alerts describe hazardous situations that, if not avoided, may result in serious injury and/or
equipment damage.
CAUTION!
CAUTION alerts describe hazardous situations that, if not avoided, may result in equipment damage.
IMPORTANT!
IMPORTANT alerts provide important information that should be known before performing a procedure
or step, or using a feature.
NOTE
NOTE alerts provide additional information, such as facts, tips and details.
Related Documents
Product Notes
Document Title Link
User/Reference Guides
Document Title Link
FAQs
Document Title Link
How to Configure the RADIUS Based Login for RUGGEDCOM WIN https://support.industry.siemens.com/cs/ww/en/view/103153206
Base Stations?
How to Configure the RADIUS Based Login for RUGGEDCOM WIN https://support.industry.siemens.com/cs/ww/en/view/103153206
Base Stations?
Installation Guides
Document Title Link
System Requirements
Each workstation used to connect to the RUGGEDCOM WIN user interface must meet the following system
requirements:
• Must have Windows XP, Windows 7 or Windows 8 installed.
• Must have the ability to configure an IP address and netmask on the computer’s Ethernet interface.
• Must have a Web browser installed. Although other versions of these Web browsers may work, the following
Web browsers have been tested at the time of release and verified as being compatible:
▫ Microsoft Internet Explorer 11
▫ Google Chrome 31 or 32
▫ Mozilla Firefox 25 or 26
▫ Apple Safari 5.1
▫ Opera 18
Training
Siemens offers a wide range of educational services ranging from in-house training of standard courses on
networking, Ethernet switches and routers, to on-site customized courses tailored to the customer's needs,
experience and application.
Siemens' Educational Services team thrives on providing our customers with the essential practical skills to make
sure users have the right knowledge and expertise to understand the various technologies associated with critical
communications network infrastructure technologies.
Siemens' unique mix of IT/Telecommunications expertise combined with domain knowledge in the utility,
transportation and industrial markets, allows Siemens to provide training specific to the customer's application.
For more information about training services and course availability, visit https://www.siemens.com/ruggedcom or
contact a Siemens Sales representative.
Customer Support
Customer support is available 24 hours, 7 days a week for all Siemens customers. For technical support or general
information, contact Siemens Customer Support through any of the following methods:
Online
Visit http://www.siemens.com/automation/support-request to submit a Support Request (SR) or check
on the status of an existing SR.
Telephone
Call a local hotline center to submit a Support Request (SR). To locate a local hotline center, visit http://
www.automation.siemens.com/mcms/aspa-db/en/automation-technology/Pages/default.aspx.
Mobile App
Install the Industry Online Support app by Siemens AG on any Android, Apple iOS or Windows mobile
device and be able to:
• Access Siemens' extensive library of support documentation, including FAQs and manuals
• Submit SRs or check on the status of an existing SR
• Contact a local Siemens representative from Sales, Technical Support, Training, etc.
• Ask questions or share knowledge with fellow Siemens customers and the support community
Introduction
Welcome to the RUGGEDCOM WIN v5.1 User Guide for RUGGEDCOM WIN7000 and WIN7200 series base stations.
This guide describes the wide array of features made available by the RUGGEDCOM WIN software. These features
include:
• Intuitive user interface and parameter groupings
• Dashboard display for monitoring vital parameters
• Quick Start window customized for base stations in standalone or in ASN-GW topologies
• Quality of Service profile tools for standalone configuration
• Remote software upgrade and software management
• Advanced communication monitoring and troubleshooting tools
The RUGGEDCOM WIN software configures and controls RUGGEDCOM WIN7000 and WIN7200 base stations, as
well as Quality of Service (QoS) functions for individual subscriber stations. It provides browser-based Web access
to a single RUGGEDCOM base station from any network connection.
Use the RUGGEDCOM WIN Web-based user interface to define initial communication parameters before the base
station is deployed to the field. After installation, use the RUGGEDCOM WIN Web-based user interface to access
the base station remotely to perform complete configuration, management, and monitoring functions.
CONTENTS
• Section 1.1, “Features and Benefits”
• Section 1.2, “Security Recommendations”
• Section 1.3, “Supported Modulation Techniques”
• Section 1.4, “About MIMO”
• Section 1.5, “User Permissions”
• Section 1.6, “SAS Gateway”
Section 1.1
Section 1.2
Security Recommendations
To prevent unauthorized access to the device, note the following security recommendations:
Authentication
• Replace the default passwords for all user accounts and processes (where applicable) before the device is
deployed.
• Use strong passwords. Avoid weak passwords such as password1, 123456789, abcdefgh, etc. An example of a
strong password would be a password that contains at least eight characters, including a lowercase letter, an
uppercase letter, a numeric character and a special character.
• Make sure passwords are protected and not shared with unauthorized personnel.
• Do not re-use passwords across different user names and systems, or after they expire.
• When RADIUS authentication is done remotely, make sure all communications are within the security perimeter
or on a secure channel.
2 Security Recommendations
RUGGEDCOM WIN Chapter 1
User Guide Introduction
Physical/Remote Access
• It is highly recommended to configure Brute Force Attack (BFA) protection to prevent a third-party from
obtaining unauthorized access to the device. For more information, refer to Section 6.1, “Configuring Brute
Force Attack Protection”.
• SSL and SSH keys are accessible to users who connect to the device via the serial console. Make sure to take
appropriate precautions when shipping the device beyond the boundaries of the trusted environment:
▫ Replace the SSH and SSL keys with throwaway keys prior to shipping.
▫ Take the existing SSH and SSL keys out of service. When the device returns, create and program new keys for
the device.
• Use a AAA server whenever possible.
• Control access to the serial console.
• When using SNMP (Simple Network Management Protocol):
▫ Limit the number of IP addresses that can connect to the device and change the community names.
▫ Make sure the default community strings are changed to unique values.
• Limit the number of simultaneous Web Server and SSH sessions allowed.
• Configure remote system logging to forward all logs to a central location.
• Management of the configuration file, certificates and keys is the responsibility of the device owner. Before
returning the device to Siemens for repair, make sure encryption is disabled (to create a cleartext version of the
configuration file) and replace the current certificates and keys with temporary throwaway certificates and keys
that can be destroyed upon the device's return.
Hardware/Software
• Make sure the latest firmware version is installed, including all security-related patches. For the latest
information on security patches for Siemens products, visit the Industrial Security website [http://
www.industry.siemens.com/topics/global/en/industrial-security/news-alerts/Pages/alerts.aspx] or the
ProductCERT Security Advisories website [http://www.siemens.com/innovation/en/technology-focus/
siemens-cert/cert-security-advisories.htm]. Updates to Siemens Product Security Advisories can be obtained
by subscribing to the RSS feed on the Siemens ProductCERT Security Advisories website, or by following
@ProductCert on Twitter.
• Use the latest Web browser version compatible with RUGGEDCOM WIN to make sure the most secure Transport
Layer Security (TLS) versions and ciphers available are employed. Additionally, 1/n-1 record splitting is
enabled in the latest web browser versions of Mozilla Firefox, Google Chrome and Internet Explorer, and
mitigates against attacks such as SSL/TLS Protocol Initialization Vector Implementation Information Disclosure
Vulnerability (e.g. BEAST).
Policy
• Periodically audit the device to make sure it complies with these recommendations and/or any internal security
policies.
• Review the user documentation for other Siemens products used in coordination with the device for further
security recommendations.
Section 1.3
Section 1.4
About MIMO
Multiple Input, Multiple Output (MIMO) is a wireless technique to improve the range or throughput of the overall
system. MIMO uses multiple radio transceivers transmitting and receiving at the same time and on the same
frequency.
The RUGGEDCOM WIN series of base stations support both MIMO Matrix A and MIMO Matrix B. The system uses
Link Adaptation to automatically select the optimal technique for a given subscriber, based on individual link
conditions.
MIMO Matrix A
MIMO Matrix A, also called STC (Space Time Coding), uses two antennas for transmitting and a single antenna for
receiving.
In the first symbol time slot, the base station transmits two symbols, one from each antenna. The SS receives the
symbols as a mixture (note that each symbol has a different path to the SS). In the second time slot, the base
station transmits a variation on the same two symbols. The SS uses both received signals from the first and second
time slots to derive a processed signal with an effectively boosted Signal-to-Noise Ratio (SNR).
This technique is combined with Maximum Ratio Combining (MRC), which is similar to STC but is applied to the
receiving side. MRC uses one antenna for transmitting and two antennas for receiving.
Because the wave’s path between the transmitting antenna and each receiving antennas is different (that is,
multipath), the combined signal from the receiving antennas can be processed to derive a signal with a boosted
SNR. Using this technique, the processed signal’s SNR is boosted in comparison with a Single Input, Single Output
(SISO) approach.
MIMO matrix A does not provide additional throughput over what a single antenna system would provide. Instead,
MIMO is used to extend range. However, note that by extending range and providing a better link budget, it is
possible to get better throughput at a given distance by being able to sustain a higher modulation rate.
MIMO Matrix B
MIMO Matrix B uses two antennas for transmitting and for receiving. The transmitting antennas transmit
independent symbols on each time slot. The received signals on each receiving antenna are a mixture of the
transmitted signals. The original transmitted symbols are extracted using signal processing. This technique
provides up to twice the throughput of a single antenna system.
Section 1.5
User Permissions
The following actions can be performed by users with administrator or guest privileges.
Privilege Level
Action
Administrator Guest
View statistics • •
Clear statistics • •
Configure settings •
Add/remove users •
Update/downgrade software •
Section 1.6
SAS Gateway
In accordance with Part 96 of the FCC's Code of Federal Regulations (CFR), no wireless device operating in
the United States is allowed to access the 3.5 GHz band without a Spectrum Access System (SAS) service.
As such, spectrum access for the following RUGGEDCOM WIN base stations and subscriber stations must be
managed by RUGGEDCOM SAS-GW.
• RUGGEDCOM WIN5137
• RUGGEDCOM WIN5137-V
• RUGGEDCOM WIN5137-V-GPS
• RUGGEDCOM WIN5237
• RUGGEDCOM WIN7237
RUGGEDCOM SAS-GW is a proxy for base stations (and their associated subscriber stations) that require access to
the 3.5 GHz band. It performs the following functions:
• Registation and De-Registation 3 MHz 30 MHz 300 MHz 3 GHz 30 GHz 300 GHz
RUGGEDCOM SAS-GW registers new base
stations and subscriber stations with the SAS.
Devices can then be de-registered as needed.
• Spectrum Requests
RUGGEDCOM SAS-GW submits requests for
spectrum on behalf of registered base stations
and subscriber stations. The SAS will grant
access based on the devices tier and spectrum
availability. Note that higher tiers have priority
over lower tiers.
• Relinquish Spectrum
RUGGEDCOM SAS-GW can be instructed to
release spectrum back to the SAS for select
base stations and subscriber stations. The SAS
may also request specific segments back if the
spectrum is required by a device belonging to a
higher tier.
• Heartbeat
RUGGEDCOM SAS-GW sends heartbeat (keep-
alive) messages to the SAS for every registered
base station and subscriber station.
For more information about RUGGEDCOM SAS-GW and Spectrum Access Systems (SASs), refer to the RUGGEDCOM
SAS-GW User Guide.
6 SAS Gateway
RUGGEDCOM WIN Chapter 2
User Guide Using WIN v5.1
CONTENTS
• Section 2.1, “Default User Names and Passwords”
• Section 2.2, “Logging In”
• Section 2.3, “Logging Out”
• Section 2.4, “Using the Web-Based User Interface”
Section 2.1
CAUTION!
Security hazard – risk of unauthorized access and/or exploitation. To prevent unauthorized access
to the base station, change the default passwords before commissioning the device. For more
information, refer to Section 5.3, “Managing Users and Passwords”.
Password generic
Section 2.2
Logging In
To log in to the base station, do the following:
IMPORTANT!
When accessing the device for the first time, use the factory default IP address, user name and
password to access the RUGGEDCOM WIN user interface. For more information, refer to Section 3.2.1,
“Default IP Address” and Section 2.1, “Default User Names and Passwords”.
1. Launch a Web browser and request a connection to the base station. The Authentication Required form
appears.
3 4
Section 2.3
Logging Out
To log out, do the following:
1. Navigate to Admin. The Web Logout screen appears.
2. Click Logout.
Section 2.4
8 Logging Out
RUGGEDCOM WIN Chapter 2
User Guide Using WIN v5.1
3
1
2 4
Figure 3: Management Interface
1. Toolbar 2. Menu Tree 3. Dashboard 4. Main Screen
CONTENTS
• Section 2.4.1, “Dashboard”
• Section 2.4.2, “Navigating the User Interface”
• Section 2.4.3, “Using Tables”
Section 2.4.1
Dashboard
The dashboard appears at the top-right of the user interface at all times. The dashboard displays base station
status information, including operational status, registered subscriber stations, downlink traffic, uplink traffic, and
alarm information. To view detailed status information, click on a status indicator.
1
5
2
Figure 4: Dashboard
1. Status 2. Registered 3. Downlink 4. Uplink 5. Alarms
Table: Dashboard Display
= critical
= major
= minor
Click to display the System Alarms screen. For more information, refer to Section 5.4.3,
“Viewing/Clearing Alarms”.
Section 2.4.2
Figure 5: Toolbar
Toolbar Links
Link Description
Subscribers Management of registered and provisioned subscriber stations and services (such as VLAN)
in Standalone mode.
Backbone Displays and sets the operation mode (Standalone or ASN-GW), and configures base station
and gateway IP addresses.
For Standalone mode, defines Switching parameters.
For ASN-GW mode, defines ASN-GW parameters.
Quick Start Displays and sets initial system setup parameters. Also provides controls to start and stop the
base station service and to reboot the base station.
Statistics Displays Base Station and Subscriber Station statistics, including Ethernet Counters, Traffic
Statistics, and Subscriber Station statistics.
Section 2.4.3
Using Tables
This section describes features common to most tables in the user interface.
1 2 3
4 5
To filter the contents of a table, click the filtering icon ( ). A new row appears above the table with a box or list in
each cell.
• Lists filter the table based on the values available in a specific column. Click the list to display the full list and
then select the desired text. Only rows that contain that text in that column appear.
• Boxes filter the table based on a search string. The string can be a full or partial text string. The table will be
filtered based on cells in that column that match the text string.
Select operators can also be used to further refine the filtering results. Click the Help icon (?) to display the
following list of operators.
Operator Description Operator Description
<X Less than a specified value X/Y Starts with and ends with
12 Using Tables
RUGGEDCOM WIN Chapter 3
User Guide Getting Started
Getting Started
This section describes startup tasks to be performed during the initial commissioning of the base station.
CONTENTS
• Section 3.1, “Basic Configuration”
• Section 3.2, “Connecting to the Base Station”
• Section 3.3, “Configuring the Base Station's IP Interface”
Section 3.1
Basic Configuration
This section describes the basic steps required to connect the base station to the network. Once these steps are
completed, additional features can be enabled and configured either directly through the RUGGEDCOM WIN user
interface or remotely via RUGGEDCOM NMS.
NOTE
For more information about RUGGEDCOM NMS, refer to the RUGGEDCOM NMS User Guide [https://
support.industry.siemens.com/cs/ww/en/ps/15399/man].
To configure the initial settings for the base station, do the following:
WARNING!
Radiation hazard – risk of Radio Frequency (RF) exposue. The GPS receiver is enabled by default. While
emitted radiation is minimal, to avoid exposure, stand at least 3.6 m (11.8 ft) from the base station at
all times.
If operating the base station in an enclosed environment, such as a lab, make sure the GPS receiver
is disabled as soon as possible after powering on the device. When ready to enable the GPS receiver,
make sure the base station is first moved to an area where personnel can stand at least 3.6 m (11.8 ft)
from it at all times.
1. Establish a direct connection to the base station. For more information, refer to Section 3.2.2, “Connecting
Directly”.
2. Log in to the base station using the default user name and password. For more information, refer to
Section 2.2, “Logging In”.
3. If operating in an enclosed environment, such as a lab, disable the GPS receiver. This is done by setting
Configured GPS Hardware Support Mode to OFF. For more information, refer to Section 7.2.1,
“Configuring the GPS Time Source”.
NOTE
A system reboot is required after changing the operating mode.
4. Set the operating mode. The base station can be configurd to run in either Standalone or ASN-GW mode. For
more information, refer to Section 5.1, “Setting the Operating Mode”.
5. Navigate to Quick Start » Quick Start Menu. The Quick Start Settings screen appears.
1
2
3
4
5
6
7
8
10
11
12
13
14 Basic Configuration
RUGGEDCOM WIN Chapter 3
User Guide Getting Started
Parameter Description
The IP address of the default gateway.
If the base station is directly connected to the ASN gateway, specify the ASN gateway’s
IP address. If the base station reaches the ASN gateway through a router, specify the
router’s IP address.
7. Click Apply.
8. Reboot the base station. For more information, refer to Section 4.1, “Rebooting the Device”.
9. Replace the default certificate and private key. For more information, refer to Section 6.3.1, “Updating the
Certificate and Private Key”.
10. Replace the default SSH keys. For more information, refer to Section 6.3.3, “Generating SSH Keys”.
11. Configure and register subscriber stations with the base station. Registered subscriber stations are listed on
the Registered SS screen. For more information, refer to Section 8.11, “Monitoring Registered Subscriber
Stations”.
12. Remotely verify the device is operational. This can be done by monitoring traversal of data packets through
the base station. For more information, refer to Section 4.5.3, “Viewing and Clearing Traffic Statistics”.
13. [Optional] If the base station is to be remotely managed by a Network Management System (NMS), such as
RUGGEDCOM NMS, create an SNMP trap destination for the associated workstation. For more information,
refer to Section 10.1.4.4, “Configuring SNMP Trap Destinations”.
14. Further configure the base station as needed.
15. If disabled previously, enable the GPS receiver. This is done by setting Configured GPS Hardware
Support Mode to ON. For more information, refer to Section 7.2.1, “Configuring the GPS Time Source”.
Section 3.2
• Remote Connections
Establish a remote connection to the base station using a Web browser or Telnet/SSH terminal. A network
connection and workstation are required.
CONTENTS
• Section 3.2.1, “Default IP Address”
• Section 3.2.2, “Connecting Directly”
• Section 3.2.3, “Connecting Remotely”
Section 3.2.1
Default IP Address
The default IP address for the base station is 192.168.100.100/24.
This is referred to as the LAN IP address.
Section 3.2.2
Connecting Directly
RUGGEDCOM WIN can be accessed through a direct RS-232 serial console or Ethernet connection for management
and troubleshooting purposes. A console connection provides access to the console interface. An Ethernet
connection provides access to the Web user interface.
Data Bits 8
Stop Bit 1
Parity None
Terminal ID VT100
3. Connect to the base station. Once the connection is established, the login form appears. For more
information about logging in to the base station, refer to Section 2.2, “Logging In”.
16 Default IP Address
RUGGEDCOM WIN Chapter 3
User Guide Getting Started
1. On the workstation being used to access the device, configure the IP address range and subnet mask for an
Ethernet port. The range is typically the IP address for the base station plus one, ending at *.*.*.254.
For example, if the base station's IP address is 192.168.100.100, configure the workstation's Ethernet port
with an IPv4 address in the range of 192.168.100.99/24 to 192.168.100.254/24.
2. Connect an Ethernet cable between the workstation and the DC/ETH port on the base station.
3. Launch a Web browser. For a list of compatible Web browsers, refer to “System Requirements”.
4. If using a proxy server, make sure the IP address and subnet for the device are included in the list of
exceptions.
5. In the address bar, enter the base station's IP address and then press Enter.
IMPORTANT!
Upon connecting to the device, some Web browsers may report the Web server's certificate cannot
be verified against any known certificates. This is expected behavior, and it is safe to instruct the
browser to accept the certificate. Once the certificate is accepted, all communications with the
Web server through that browser will be secure.
6. If the device's SSH key has not been cached to the workstation's registry, a confirmation message will appear
asking if the host is trusted. Confirm the connection to continue.
7. Log in to RUGGEDCOM WIN. For more information about logging in, refer to Section 2.2, “Logging In”.
Section 3.2.3
Connecting Remotely
The base station can be accessed over the network either through a Web browser, terminal or a workstation
running terminal emulation software.
IMPORTANT!
Upon connecting to the device, some Web browsers may report the Web server's certificate cannot
be verified against any known certificates. This is expected behavior, and it is safe to instruct the
browser to accept the certificate. Once the certificate is accepted, all communications with the
Web server through that browser will be secure.
6. If the device's SSH key has not been cached to the workstation's registry, a confirmation message will appear
asking if the host is trusted. Confirm the connection to continue.
7. Log in to RUGGEDCOM WIN. For more information about logging in, refer to Section 2.2, “Logging In”.
Port 22
login as:
4. Log in to RUGGEDCOM WIN. For more information, refer to Section 2.2, “Logging In”.
Section 3.3
1
2
3
4
5
6
NOTE
These same parameters are configurable under Quick Start » Quick Start Menu » Quick Start
Settings.
Parameter Description
Device Management
This chapter describes how to configure and manage the device and its components, such as device hardware,
logs, files and more.
CONTENTS
• Section 4.1, “Rebooting the Device”
• Section 4.2, “Displaying the Current Status”
• Section 4.3, “Displaying Device Information”
• Section 4.4, “Configuring Installation Details”
• Section 4.5, “Viewing Statistics”
• Section 4.6, “Managing Logs”
• Section 4.7, “Managing System Files”
• Section 4.8, “Managing Software”
• Section 4.9, “Configuring the Maximum Transmission Unit (MTU)”
• Section 4.10, “Managing Redundant Base Stations”
Section 4.1
1
2
3
4
5
6
7
10
11
12
Section 4.2
1
2
3
4
5
6
7
Current Frequency The current frequency measured in kilohertz (kHz) on which the base station is operating.
GPS Time The current UTC date and time from the base station’s built-in GPS receiver.
Uptime The time, in hours, minutes, and seconds, since the last system restart.
Section 4.3
1
2
3
4
5
6
7
Product Type The four-digit product type. Numbers in the 7000 range indicate a Compact base tation.
Numbers in the 7200 range indicate a Pico base station.
The last two digits indicate the frequency band. For example, 7235 represents a 3.5 GHz Pico
base station.
MAC Address The MAC address associated with the base station.
Device Serial Number The serial number for the base station.
Boot Version Displays the base station boot loader software version.
Section 4.4
1
2
3
4
5
6
7
8
Street Address The street address or physical location of the base station.
Serial Baudrate Synopsis: { 115200, 57600, 38400, 28800, 19200, 14400, 9600 }
The serial baud rate of the UART port.
3. Click Apply.
Section 4.5
Viewing Statistics
RUGGEDCOM WIN records statistics on all uplink and downlink communications, including UL and DL signal
strengths and carrier to interference plus noise ratios. Packet counters list UL and DL channels, bytes and packets
transmitted and dropped, and packet rates.
This section describes how to view and control the statistics collected.
CONTENTS
• Section 4.5.1, “Enabling/Disabling Select Statistics”
• Section 4.5.2, “Viewing and Clearing Ethernet Statistics”
• Section 4.5.3, “Viewing and Clearing Traffic Statistics”
• Section 4.5.4, “Viewing and Clearing Subscriber Station Statistics”
• Section 4.5.5, “Viewing Subscriber Station Connection Statistics”
Section 4.5.1
1
2
3
4
5
6
7
26 Viewing Statistics
RUGGEDCOM WIN Chapter 4
User Guide Device Management
Parameter Description
• False – Enables all statistics collection
3. Click Apply.
Section 4.5.2
1
2
3
4
5
6
7
10
Traffic Statistics
The Traffic Statistics table provides the following statistics related to the overall traffic flow:
Parameter Description
Rate (kbits/sec) The traffic flow rate in kilobits per second (kbits/s).
Rate (packets/sec) The traffic flow rate in packets per second (packets/s).
Parameter Description
Packets by Size
The following information details the size of packets sent and received:
Parameter Description
64 Bytes Packets The number of packets received and sent measuring less than 64 bytes.
64-127 Bytes Packets The number of packets received and sent measuring between 64 and 127 bytes.
128-255 Bytes Packets The number of packets received and sent measuring between 128 and 255 bytes.
256-511 Bytes Packets The number of packets received and sent measuring between 256 and 511 bytes.
512-1023 Bytes Packets The number of packets received and sent measuring between 512 and 1023 bytes.
1024-1518 Bytes Packets The number of packets received and sent measuring between 1024 and 1518 bytes.
1519-1522 Bytes Packets The number of packets received and sent measuring between 1519 and 1522 bytes.
Dropped Packets
The Drop Statistics table provides the following statistics on dropped packets:
Parameter Description
Runts The total number of packets that are undersized (i.e. smaller than 64 bytes).
Grunts The total number of packets that are oversized (i.e. greater than 64 bytes). These are also
referred to as giants.
Alignment Error The total number of packets whose size is not divisible by eight.
FCS Error The total number of Frame Check Sequence (FCS) errors generated by packets that include
error-detecting code.
Collision The total number of packet collisions. These occur when a packet is sent at the same time
by two or more base stations. The packets are returned to their associated base station and
then retransmitted in a timed sequence.
Full Buffer Dropped The total number of packets dropped due to a full buffer.
Section 4.5.3
RF The total number of packets originating from registered subscriber stations and sent in the
given direction.
Network The total number of packets originating from the LAN behind the base station and sent in
the given direction.
Local The total number of packets originating from the base station itself and sent in the given
direction.
Section 4.5.4
The SS Sync Table details the following information for each registered subscriber station:
Column Description
Column Description
NOTE
The name will only appear if the subscriber station is authenticated by a AAA
server.
Operation Time The up time of the subscriber station in days, hours, minutes and seconds (i.e.
DD:HH:MM:SS).
DL RSSI The downlink received signal strength indication for the subscriber station in decibels/minute
(dBm). Includes minimum, maximum, and current values.
DL CINR The downlink carrier to interference plus noise ratio for the subscriber station in decibels
(dB). Includes minimum, maximum, and current values.
DL MCS Downlink Modulation Coding Scheme (MCS) information, including the minimum,
maximum, and current modulation.
DL HARQ MCS Downlink Hybrid Automatic Repeat Request (HARQ) Modulation Coding Scheme (MCS)
information, including the minimum, maximum, and current modulation.
UL CINR The uplink carrier to interference plus noise ratio for the subscriber station in decibels (dB).
Includes minimum, maximum, and current values.
UL HARQ MCS Uplink Hybrid Automatic Repeat Request (HARQ) Modulation Coding Scheme (MCS)
information, including the minimum, maximum, and current modulation.
UL Channels Number The number of uplink channels, including the minimum, maximum, and current number of
channels.
DL Total Downlink data statistics for the subscriber station, including total bytes, packets, dropped
packets, and rate in kilobits per second.
DL Ucast Downlink unicast statistics for the subscriber station, including total bytes, packets, dropped
packets, and rate in kilobits per second.
UL Total Uplink data statistics for the subscriber station, including total bytes, packets, dropped
packets, and rate in kilobits per second.
MIMO Mode The current Multiple Input Multiple Output mode. Possible values include: MIMO A or MIMO
B.
GPS Location The latitude and longitude broadcast by the subscriber station. Only available for subscriber
stations that have GPS equipped and enabled.
Parameter Description
Section 4.5.5
Figure 17: Registered SS Screen
1. Number of Registered SS 2. Registered Subscriber Stations 3. Connections Button 4. Capabilities Button 5. Deregister Button
6. Reboot Button
2. Select a subscriber station and then click Connections. The SS Connections screen appears.
3. Select a connection and then click Show Counters. The SS Connection Counters screen appears.
1
2
3
4
5
6
Parameter Description
SS ID The Set Service Identifier (SSID) assigned to the associated subscriber station.
Section 4.6
Managing Logs
RUGGEDCOM WIN maintains the following logs to record information about important events:
Log File Description
security.log Records information related to security events, such as login information, configuration changes, etc.
sw_upgrade.log Records information related to each software upgrade applied to the device.
{time stamp}.log Records information related to general events not associated with security. The file name of each log
indicates the time at which the events occurred.
Activity Log Records all warnings generated by the SQN (Sequance) code.
When Syslog is enabled, files are forwarded automatically to a remote Syslog server when an event occurs.
Remote Syslog, defined in RFC 3164 [http://tools.ietf.org/html/rfc3164], is a UDP/IP-based transport protocol that
enables a device to send event notification messages across IP networks to event message collectors (Syslog
servers). The protocol is designed to simply transport these event messages from the generating device to the
collector.
Users also have the option of manually sending these files to the remote Syslog server as needed.
CONTENTS
• Section 4.6.1, “Configuring Syslog”
• Section 4.6.2, “Enabling/Disabling Logs”
• Section 4.6.3, “Limiting the Size of Log Files”
• Section 4.6.4, “Manually Uploading Log Files”
Section 4.6.1
Configuring Syslog
For redundancy, RUGGEDCOM WIN supports up to two remote Syslog server connections. The server defined
under Server IP is considered the primary Syslog server. The server defined under Second Server IP is the
secondary server. Should the connection with the primary server be lost, the Syslog service will automatically
switch to the secondary server.
To configure the System log (Syslog), do the following:
1. Navigate to Admin » Logs Management. The Syslog Configuration screen appears.
4. Click Apply.
Section 4.6.2
Enabling/Disabling Logs
All logs are enabled by default. However, select logs can be disabled to improve performance. This is useful when
the base station is heavily utilized with subscribers and data.
36 Configuring Syslog
RUGGEDCOM WIN Chapter 4
User Guide Device Management
IMPORTANT!
Disabling logs removes important information that may be useful during troubleshooting. Only disable
logs when necessary. For assistance determining if this step is required, contact Siemens Customer
Support.
NOTE
For information about the different log types, refer to Section 4.6, “Managing Logs”.
1
2
3
4
Figure 21: Performance Screen
1. Security Log List 2. Activity Log List 3. Terminal Logs List 4. Terminal Warnings List 5. Apply Button
3. Click Apply.
Section 4.6.3
2. Under File Size, enter the maximum file size for all log files.
3. Click Apply.
Section 4.6.4
2. Select one or more log files to send to the remote Syslog server.
3. Click Upload File. The selected files are forwarded to the remote Syslog server.
Section 4.7
CONTENTS
• Section 4.7.1, “Enabling/Disabling SFTP Sessions”
• Section 4.7.2, “Configuring the FTP Service”
• Section 4.7.3, “Uploading Files to the FTP Server”
• Section 4.7.4, “Downloading a File from the FTP Server”
• Section 4.7.5, “Copying Files from the Primary Memory Bank to the Secondary Memory Bank”
• Section 4.7.6, “Deleting Files from the Secondary Memory Bank”
• Section 4.7.7, “Viewing/Cancelling File Transfers”
Section 4.7.1
3. Click Apply.
Section 4.7.2
1
2
3
4
Directory The path on the FTP server to where software updates for the device are locate, and
where device configuration files can be uploaded.
User Name The user name required to log into the FTP server.
3. Click Apply.
If the connection is successful, files can be uploaded to or downloaded from the specified directory on the FTP
server. For more information, refer to either Section 4.7.3, “Uploading Files to the FTP Server” or Section 4.7.4,
“Downloading a File from the FTP Server”.
Section 4.7.3
NOTE
Files are only available on the Secondary Components screen if a software version has been
downloaded to the secondary memory bank.
NOTE
File transfers can be viewed and, if needed, cancelled under Admin » SW Upgrade » File Status.
For more information, refer to Section 4.7.7, “Viewing/Cancelling File Transfers”.
2. Select one or more files and then click Upload File. The selected file(s) is uploaded to the FTP server. The
location on the FTP server is defined under Admin » SW Upgrade » FTP Server.
Section 4.7.4
NOTE
All files downloaded from the FTP server are saved on the secondary memory bank so as to protect the
current running configuration.
NOTE
RUGGEDCOM NMS can be configured to download files from the FTP server to the base station at a
specific time and date. For more information, refer to the RUGGEDCOM NMS User Guide.
1. Make sure the FTP service is configured. For more information, refer to Section 4.7.2, “Configuring the FTP
Service”.
2. Navigate to Admin » SW Upgrade » Downloads. The Downloads screen appears.
Figure 27: Downloads Screen
1. File Type List 2. File Name Box 3. Download Button
3. Under File Type, select the type of file to be downloaded from the FTP server. Options include: Package,
VxWorks, Web Resource, CDC and UV.
4. Under File Name, enter the full name of the file to download.
NOTE
File transfers can be viewed and, if needed, cancelled under Admin » SW Upgrade » File Status.
For more information, refer to Section 4.7.7, “Viewing/Cancelling File Transfers”.
Section 4.7.5
NOTE
File transfers can be viewed and, if needed, cancelled under Admin » SW Upgrade » File Status.
For more information, refer to Section 4.7.7, “Viewing/Cancelling File Transfers”.
3. Select one or more files and then click Copy File. The selected file(s) is copied to the secondary memory
bank.
Alternatively, click Copy Directory to copy all files to the secondary memory bank.
Section 4.7.6
2. Select one or more files and then click Delete File. The selected file(s) is deleted from the secondary memory
bank.
Alternatively, click Delete Directory to delete all files from the secondary memory bank.
Section 4.7.7
2. Under File Operation Status, select an operation state. Any files that match that state appear in the table
below. Options include:
• Finished – Displays all files that were successfully downloaded
• Not Started – Displays all files that are waiting to be downloaded
• In Process – Displays all files that are currently being downloaded
• Failure – Displays all files that were not successfully downloaded
Section 4.8
Managing Software
This section describes how to manage the verson of RUGGEDCOM WIN running on the base station.
CONTENTS
• Section 4.8.1, “Updating RUGGEDCOM WIN”
• Section 4.8.2, “Changing the Active Software Version”
• Section 4.8.3, “Restoring Factory Defaults”
Section 4.8.1
46 Managing Software
RUGGEDCOM WIN Chapter 4
User Guide Device Management
Section 4.8.2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
2. Click Run Secondary. The device reboots with the secondary memory bank loaded.
3. Click Set As Primary. The current memory bank is now the primary memory bank. When the base station
reboots, this memory bank will be loaded automatically.
Section 4.8.3
NOTE
The device is rebooted following each factory reset.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Section 4.9
The maximum size of a data unit is 1530 bytes. However, with mini-jumbo frames enabled, the maximum size is
increased to 1599 bytes.
IMPORTANT!
When jumbo frames are enabled, the whole network must have the same MTU setting.
2. Under Mini-Jumbo Frames Support, select Enable to enable mini-jumbo frames, or Disable to disable
mini-jumbo frames.
3. Under Maximum Ethernet Size, enter the maximum MTU size in bytes.
4. Click Apply.
5. If Mini-Jumbo Frames Support was set to Enabled, reboot the base stattion.
Section 4.10
CONTENTS
• Section 4.10.1, “Understanding Redundancy”
• Section 4.10.2, “Configuring Base Station Redundancy”
• Section 4.10.3, “Viewing the Status of Base Station Redundancy”
Section 4.10.1
Understanding Redundancy
Base station redundancy allows two neighboring RUGGEDCOM base stations to act as backups for one another.
If one base station fails, the redundant base station will take over, maintaining continuity of service. The
redundancy feature must be enabled and configured on both base stations.
1 1
2 2 2
3 4 3 4
5 6 5 6
7 7
8 8
CONTENTS
• Section 4.10.1.1, “Master vs. Slave”
• Section 4.10.1.2, “States”
• Section 4.10.1.3, “Faults”
• Section 4.10.1.4, “Reachability”
Section 4.10.1.1
Master vs. Slave
The primary goal of the base station and its neighboring base station is to become the Master. As a Master, the
base station can start normal operation and begin transmitting on behalf of its registered subscriber stations. The
other base station remains in a Slave state until the Master loses its status.
50 Understanding Redundancy
RUGGEDCOM WIN Chapter 4
User Guide Device Management
Requirements
Before the base station is eligible to become the Master, it must meet the following conditions:
• The base station has been granted spectrum by the SAS Gateway. Applies only to the RUGGEDCOM WIN7237.
• The base station is sychronized with a GPS or PTP time source.
• Redundancy is configured and the base station is in Master state.
• Radio transmissions from the base station are enabled.
If the base station does not meet this criteria at any point, radio transmissions are disabled and the base station
relinquishes the Master status to the neighboring base station.
Standby Disabled The neighboring base station must not be the Master.
Section 4.10.1.2
States
The base station and its neighbor can be in any one of the following states during operation: Standby, Backoff,
Master or Fault.
To change the state, the status of the neighboring base station must change or a critical fault in the base station
must occur.
The following details each state and what action is taken by the base station:
Neighbor
Local State Fault Description Action
State
Standby Master 0 The neighboring base station is the Master. Remain as Slave.
Standby Else 0 The neighboring base station has lost the Master Move to the Backoff state.
status.
Backoff Master 0 The neighboring base station has become the Move to the Standby state.
Master.
Backoff Else The Wait for the timeout period to expire and then Move to the Master state.
neighboring claim Master state.
base station is
not the Master.
Master Master 0 Both base stations have won the Master status. Move to the Backoff state.
Master Else 0 The neighboring base station is the Slave. Remain in the Master state.
Backoff/ Unknown 0 The neighboring base station or network is Move to the Master state.
Standby unreachable.
Neighbor
Local State Fault Description Action
State
Fault — Any A critical fault has occured. Remain in the Fault state until
the fault(s) has been cleared.
Fault — 0 The critical fault(s) has been cleared. Move to the Standby state.
Section 4.10.1.3
Faults
The base station enters the Fault state whenever a critical fault occurs. Each fault is reported as an event.
ID Type Description
9 Network Unreachable The network is unreachable. For more information, refer to Section 4.10.1.4,
“Reachability”.
10 Neighbor Unreachable The neighboring base station is unreachable. For more information, refer to
Section 4.10.1.4, “Reachability”.
NOTE
This fault only affects the base station when it is not the Master.
Section 4.10.1.4
Reachability
Since it is impossible to determine if the neighboring base station is unreachable or if a network cable has
been disconnected, RUGGEDCOM WIN requires the IP address of up to two additional devices on the network.
These devices will be pinged at regular intervals so that if the neighboring base station becomes unreachable,
RUGGEDCOM WIN can test the connection to these other devices to determine if the issue is with the neighboring
base station or the network itself.
The following describes the actions taken based on the reachability status of the neighboring base station and
network.
52 Faults
RUGGEDCOM WIN Chapter 4
User Guide Device Management
Status
Action
Neighboring
Network
Base Station
ü ü No action required.
Section 4.10.2
1
2
3
4
5
6
7
8
Neighbor BS IP The IP address of the neighboring base station used for redundancy.
Parameter Description
The IP address of another device on the network. If the neighboring base station
becomes unreachable, WIN will test the LAN connection to this device to confirm if the
problem is with the neighboring base station or the network itself.
3. Make sure the base station is synchronized with either a GPS or PTP time source. For more information, refer
to Section 7.2, “Managing GPS” or Section 7.3, “Managing Precision Time Protocol (PTP)”.
4. Click Apply and then restart the base station.
5. Navigate to Admin » Redundancy and confirm the value of Neighbor BS Status is not Unreachable. For
more information, refer to Section 4.10.3, “Viewing the Status of Base Station Redundancy”.
6. Configure the same settings on the neighboring base station.
Section 4.10.3
1
2
3
4
5
6
7
8
The following parameters display the status of the base station redundancy feature:
Parameter Description
Current Redundancy Support Displays the current state of the redundancy feature.
BS Status Displays the status of the current base station. Possible values include: Init,
ElectionBackoff, ElectionQuerySent, MasterOk, MasterNotOk, SlaveReady or
SlaveNotReady.
Neighbor BS Status Displays the status of the neighboring redundant base station. Possible values include:
MasterOk, MasterNotOk, SlaveReady, SlaveNotReady, SlaveGoingToMaster.
Parameter Description
NOTE
Test Network Reachability IP1 and/or Test Network
Reachability IP2 must be defined. For more information, refer to
Section 4.10.2, “Configuring Base Station Redundancy”.
System Administration
This chapter describes how to perform various administrative tasks related to device identification, user
permissions, alarm configuration, certificates and keys, and more.
CONTENTS
• Section 5.1, “Setting the Operating Mode”
• Section 5.2, “Enabling/Disabling SSH Sessions”
• Section 5.3, “Managing Users and Passwords”
• Section 5.4, “Managing Alarms”
• Section 5.5, “Displaying the Current Switching Mode”
Section 5.1
NOTE
The current operating mode is displayed under Current Operation Mode.
Section 5.2
Parameter Description
Default: Disable
Enables or disables remote access via SSH.
3. Click Apply.
Section 5.3
NOTE
Only users with administrator level access can manage user profiles and passwords.
CONTENTS
• Section 5.3.1, “Adding Users”
• Section 5.3.2, “Removing Users”
• Section 5.3.3, “Changing User Passwords”
Section 5.3.1
Adding Users
To add a user profile, do the following:
1. Navigate to Admin » Security. The Device Access Permissions screen appears.
NOTE
The user name admin is reserved for the root administrator profile.
4. Under Retype Password, enter the user's password again the same as it was written under Password.
5. Click Apply.
60 Adding Users
RUGGEDCOM WIN Chapter 5
User Guide System Administration
Section 5.3.2
Removing Users
To remove a user profile, do the following:
1. Navigate to Admin » Security. The Device Access Permissions screen appears.
2. Select a user profile and then click . The selected profile is removed.
3. Click Apply.
Section 5.3.3
2. Under Password, enter a new password for the desired user. A strong password that meets the following
criteria is recommended:
• One lower case character
• One upper case character
• One number
• One special character (i.e. !@#$%^&*()_+-={}[];:',<>/?\|`~)
3. Under Retype Password, enter the new password again the same as it was written under Password.
4. Click Apply.
Section 5.4
Managing Alarms
The alarm system in RUGGEDCOM WIN notifies users when events of interest occur. The system includes an
extensive list of predefined alarms that can be enabled/disabled as needed.
When an event triggers an alarm, the Alarms counter on the dashboard increments by one.
62 Managing Alarms
RUGGEDCOM WIN Chapter 5
User Guide System Administration
1
5
2
Figure 42: Dashboard
1. Status 2. Registered 3. Downlink 4. Uplink 5. Alarms
Users are then encouraged to navigate to Admin » Alarms and Traps to view more details about the alarm.
CONTENTS
• Section 5.4.1, “Alarm Categories and Severities”
• Section 5.4.2, “Available Alarms”
• Section 5.4.3, “Viewing/Clearing Alarms”
Section 5.4.1
Categories
Category Description
Communication Alarms related to the base station's ability to communicate with the Local Area Network (LAN) and external
sources, such as AAA servers, master clock, etc.
Other Alarms related to the general operational state of the base station
Severity Levels
Severity Level Description
Clear Clear alarms are notifications that a previous condition has been cleared.
Critical Critical alarms represent events that disable all radio transmissions.
Major Warning alarms represent events that may disable all radio transmissions and/or affect traffic
flows.
Warning Warning alarms represent events that only affect traffic flows.
Section 5.4.2
Available Alarms
RUGGEDCOM WIN features the following predefined alarms:
Alarm ID Category
Restart 0 Other
Hardware 1 HW
Temperature 2 Other
Antenna 4 Radio
Interference 27 Radio
64 Available Alarms
RUGGEDCOM WIN Chapter 5
User Guide System Administration
Alarm ID Category
All alarms are listed under Admin » Alarms and Traps. For more information about viewing alarms, refer to
Section 5.4.3, “Viewing/Clearing Alarms”.
Section 5.4.3
Viewing/Clearing Alarms
Active system alarms are displayed in the user interface and can be cleared once resolved.
Viewing Alarms
To view the list of all predefined alarms, navigate to Admin » Alarms and Traps. The System Alarms screen
appears.
1
2
3
The Number of Critical Alarms, Number of Major Alarms and Number of Warning Alarms boxes indicate the
number of active alarms based on their severity. This information is also displayed on the dashboard. For more
information, refer to Section 2.4.1, “Dashboard”.
The Alarms Table provides additional information about each alarm:
Column Description
Name The alarm type. For information about each alarm type, refer to Section 5.4.2, “Available
Alarms”.
66 Viewing/Clearing Alarms
RUGGEDCOM WIN Chapter 5
User Guide System Administration
Column Description
The severity of the alarm.
Last Update Time The date and time when the alarm was last activated.
Clearing Alarms
To clear alarms that have been resolved, do the following:
1. Navigate to Admin » Alarms and Traps. The System Alarms screen appears.
1
2
3
Section 5.5
1
2
3
4
Security
This chapter describes how to configure and manage the security-related features of RUGGEDCOM WIN.
CONTENTS
• Section 6.1, “Configuring Brute Force Attack Protection”
• Section 6.2, “Enabling Ethernet Port Shutdown Mode”
• Section 6.3, “Managing Certificates and Keys”
• Section 6.4, “Configuring RADIUS Authentication”
• Section 6.5, “Managing Wireless Authentication”
Section 6.1
IMPORTANT!
BFA protection is not applicable to SNMP. Folow proper security practices for configuring SNMP. For
example:
• Do not use SNMP over the Internet
• Use a firewall to limit access to SNMP
• Do not use SNMPv1
Login Retries Before Trap Synopsis: { Never Send Trap, 1 Attempt, 3 Attempts, 10 Attempts }
Default: 10 Attempts
The maximum number of times a host can attempt to login to the Base Station before an
SNMP trap is triggered. Options include:
• Never Send Trap – disabled Brute Force Attack (BFA) protection
• 1 Attempt – hosts have only one chance to successfully login to the Base Station
• 3 Attempts – hosts have three chances to successfully login to the Base Station
• 10 Attempts – hosts have 10 chances to successfully login to the Base Station
3. Click Apply.
Section 6.2
BS Ethernet Port Shutdown Determines if the subscriber station can receive Ethernet port shutdown messages from
the serving base station. Set this parameter to Enable.
Ethernet Interface Blink Duration The time in seconds (s) to wait after the serving base station advertises that its physical
Ethernet connection has been disconnected. No packets will be sent during this time.
If no messages are received from the serving base station before this timer expires,
the subscriber station assumes the physical connection has been restored and resumes
sending packets.
Start Fast NE When BS Port is Down Determines if the subscriber station will connect to a different base station when the
serving base station's physical Ethernet connection has been disconnected.
For more information about these parameters, refer to the RUGGEDCOM WIN User Guide for the subscriber
stations.
Section 6.3
NOTE
Only admin users can read/write certificates and keys on the device.
CONTENTS
• Section 6.3.1, “Updating the Certificate and Private Key”
• Section 6.3.2, “Setting the Private Key Passphrase”
• Section 6.3.3, “Generating SSH Keys”
Section 6.3.1
NOTE
Replacement certificates and private keys must meet the following requirements:
Certificate Requirements Key Requirements
• Format: PEM • Format: PEM
• File Name: httpscert.pem • File Name: httpskey.pem
• Maximum Size: 20 kb • Maximum Size: 4 kb
• Password: 1 to 16 characters long
1. Navigate to Admin » HTTPS Certificate. The Load HTTPS Certificates screen appears.
4
3
2. Select the certificate or private key, and then click Browse. A dialog box appears.
3. Use the dialog box to locate and select the new certificate or private key.
4. Click Load File. If the file is loaded successfully, Success appears in the Certificate Transfer Status column.
Section 6.3.2
4
3
Section 6.3.3
CAUTION!
Security hazard – risk of unauthorized access and/or exploitation. It is important to generate new SSH
keys when commissioning the base station to prevent unauthorized access by users using the default
SSH keys.
NOTE
Key generation can take up to 5 minutes to complete.
1. Navigate to Admin » Security » SSH Keys. The SSH Keys screen appears.
2. Click Generate SSH Keys. The device reboots and generates new SSH keys.
Section 6.4
1
2
3
4
5
6
Parameter Description
Default: Disable
Enables or disables RADIUS Authentication mode.
Login AAA Port The port on the RADIUS server used for remote authentication.
Login AAA Secret The secrete key shared between the base station and RADIUS server. This is used to
encrypt passwords and exchange responses.
NAS ID The Network Access Server (NAS) ID. This ID is used by the RADIUS server to determine
the correct policy to use for the authentication request. The value can be an FQDN of the
NAS or any unique string to identify the NAS.
3. Click Apply.
Section 6.5
CONTENTS
• Section 6.5.1, “Configuring Wireless Authentication”
• Section 6.5.2, “Enabling Wireless Authentication”
• Section 6.5.3, “Configuring AAA Server Settings”
• Section 6.5.4, “Enabling/Disabling a AAA Server”
• Section 6.5.5, “Selecting the Active AAA Server”
• Section 6.5.6, “Viewing the Status of AAA Servers”
Section 6.5.1
Section 6.5.2
4
5
6
7
8
9
10
11
12
13
14
NOTE
The current setting is displayed under Current Authentication Mode.
Section 6.5.3
1. Navigate to Wireless » Wireless Security » Authentication. The Authentication Settings screen appears.
4
5
6
7
8
9
10
11
12
13
14
Parameter Description
AK Lifetime The maximum life time of authentication key in days. A value of zero (0) means the
authentication key does not expire.
4. Click Apply.
5. Select the primary AAA server. For more information, refer to Section 6.5.5, “Selecting the Active AAA Server”.
Section 6.5.4
4
5
6
7
8
9
10
11
12
13
14
2. Select the desired AAA server and then click either Enabled or Disabled.
Section 6.5.5
4
5
6
7
8
9
10
11
12
13
14
2. If Server In Use indicates Disabled for the desired AAA server, enable the server. For more information, refer
to Section 6.5.4, “Enabling/Disabling a AAA Server”.
3. Select the AAA server and then click Switch Server.
Section 6.5.6
4
5
6
7
8
9
10
11
12
13
14
The status of each AAA server is displayed by the AAA Configuration Table under the following columns:
Column Description
Column Description
• Inuse – The AAA server is being used currently for wireless authentication
• Disabled – The AAA server is not in use by the base station
Time Synchronization
This chapter describes how to synchronize the date and time with an external source.
CONTENTS
• Section 7.1, “Configuring Time Synchronization”
• Section 7.2, “Managing GPS”
• Section 7.3, “Managing Precision Time Protocol (PTP)”
Section 7.1
IMPORTANT!
Time synchronization can take up to one minute, depending on the accuracy of the time source.
1
2
3
4
5
6
Configured Time Synchronization Mode Synopsis: { GPS, IEEE1588, NONE, IEEE1588 and GPS fallback }
Default: GPS
The time source. Options include:
• GPS – Time is synchronized with a GPS source
• IEEE1588 – Time is synchronized with an IEEE 1588 source
• NONE – Time is not synchronized with an external source
• IEEE1588 and GPS fallback – Time is synchronized with an IEEE 1588 source.
However, should that source stop providing updates, the base station will switch to
the GPS source.
Section 7.2
Managing GPS
The base station is configured to use GPS by default. This section describes how to view GPS settings and
information, and how to disable and enable the GPS received for testing and troubleshooting.
CONTENTS
• Section 7.2.1, “Configuring the GPS Time Source”
• Section 7.2.2, “Viewing GPS Time Source Information”
• Section 7.2.3, “Viewing Detected GPS Satellites”
Section 7.2.1
1
2
3
4
5
6
7
8
10
Figure 58: GPS Screen
1. Current GPS Hardware Support Mode 2. Configured GPS Hardware Support Mode Box 3. Current Loop Filter BW
4. Synchronization State 5. Latitude 6. Longitude 7. Height 8. Time Advertisdement Enabled 9. Detected Satellites 10. Apply
Button
Parameter Description
When enabled, the time received by the GPS is advertised to the subscriber stations.
Options include:
• True – Enables time advertisement
• False – Disables time advertisement
Section 7.2.2
1
2
3
4
5
6
7
8
10
Figure 59: GPS Screen
1. Current GPS Hardware Support Mode 2. Configured GPS Hardware Support Mode Box 3. Current Loop Filter BW 4. Synchronization
State 5. Latitude 6. Longitude 7. Height 8. Time Advertisdement Enabled 9. Detected Satellites 10. Apply Button
Synchronization State Synopsis: { Search HW, Init, Operational, Holdover, Sync Loss, Disabled }
The synchronization state of the GPS subsystem. Possible values include: Search HW, Init,
Operational, Holdover, Sync Loss, Disabled.
Latitude The terrestrial latitude in degrees (°), as received from the GPS time source.
Longitude The terrestrial longitude in degrees (°), as received from the GPS time source.
Height The height above sea level in meters (m), as received from the GPS time source.
Section 7.2.3
1
2
3
4
5
6
7
8
10
Figure 60: GPS Screen
1. Current GPS Hardware Support Mode 2. Configured GPS Hardware Support Mode Box 3. Current Loop Filter BW 4. Synchronization
State 5. Latitude 6. Longitude 7. Height 8. Time Advertisdement Enabled 9. Detected Satellites 10. Apply Button
The Satellite Table details the following information for each GPS satellite that is in view:
Parameter Description
Section 7.3
CONTENTS
• Section 7.3.1, “Understanding Precision Time Protocol (PTP)”
• Section 7.3.2, “Configuring the Precisition Time Protocol (PTP)”
• Section 7.3.3, “Viewing the Status of the Precision Time Protcol (PTP)”
Section 7.3.1
Section 7.3.2
1
2
3
4
5
6
Figure 61: IEEE1588 Screen
1. Current Status 2. Current Master Clock ID 3. Current GM ID 4. Subdomain Router 5. Primary Configuration GM ID Box
6. Redundant Configured GM ID Box 7. Apply Button
Redundant Configured GM ID The Grandmaster (GM) ID of the secondary IEEE 1588 time source. The base station will
not synchronize with the time source if the default value is retained.
3. Click Apply.
Section 7.3.3
1
2
3
4
5
6
Figure 62: IEEE1588 Screen
1. Current Status 2. Current Master Clock ID 3. Current GM ID 4. Subdomain Router 5. Primary Configuration GM ID Box
6. Redundant Configured GM ID Box 7. Apply Button
Current Master Clock ID The ID of the IEEE 1588 time source the base station is currently listening to.
Current GM ID The ID of the IEEE 1588 Grandmaster clock source the base station is currently listening to.
Subdomain Number The IEEE 1588 subdomain the base station is currently listening to.
Subscriber Stations
This section describes how to manage registered subscriber stations via the base station.
CONTENTS
• Section 8.1, “Adding a Pre-Provisioned Subscriber Station”
• Section 8.2, “Configuring Uplink and Downlink Settings”
• Section 8.3, “Resetting the Password for a Subscriber Station”
• Section 8.4, “Rebooting a Subscriber Station”
• Section 8.5, “Deregistering Subscriber Stations”
• Section 8.6, “Listing the IP Addresses for Registered Subscriber Stations ”
• Section 8.7, “Accessing the Management Interface for Registered Subscriber Stations”
• Section 8.8, “Managing Router Adjacency”
• Section 8.9, “Managing Ethernet Traffic”
• Section 8.10, “Managing Handover”
• Section 8.11, “Monitoring Registered Subscriber Stations”
• Section 8.12, “Listing Subscriber Station Connections”
• Section 8.13, “Listing Subscriber Station Capabilities”
Section 8.1
NOTE
Subscriber stations added by the user are referred to as pre-provisioned, as opposed to a self-learned
subscriber station that is discovered dynamically by RUGGEDCOM WIN.
Figure 63: Pre-Provisioned SS Screen
1. Pre-Provisioned Subscriber Stations 2. Apply Button 3. SS Configuration Button 4. Service Profile Button 5. VLAN Button
Section 8.2
CAUTION!
Configuration error – risk of reduced performance. The configuration of individual subscriber stations
is recommended only for advanced users. Do not change the default settings unless instructed to by a
Siemens Customer Support representative.
1. Make sure Current DL Link Adaptation Mode for Link Adaptation is set to manual. For more information,
refer to Section 12.2.4.1, “Configuring Link Adaptation”.
2. Navigate to Subscribers » Subscriber Management » Pre-Provisioned SS. The Pre-Provisioned SS screen
appears.
Figure 64: Pre-Provisioned SS Screen
1. Pre-Provisioned Subscriber Stations 2. Apply Button 3. SS Configuration Button 4. Service Profile Button 5. VLAN Button
3. Select the desired subscriber station from the list and then click SS Configuration. The SS Configuration
screen appears.
1
2
3
4
5
6
7
8
9
10
11
12
Parameter Description
6. Click Apply.
Section 8.3
2. Select the desired subscriber station and then click Reset Password. A confirmation message appears.
3. Click OK.
Section 8.4
2. Select the desired subscriber station and then click Reboot. A confirmation message appears.
3. Click OK.
Section 8.5
Figure 68: Registered SS Screen
1. Number of Registered SS 2. Registered Subscriber Stations 3. Connections Button 4. Capabilities Button 5. Deregister Button
6. Reboot Button
Section 8.6
Figure 69: Registered SS IP Adresses
1. Registered Subscriber Stations 2. Get SS IP Button 3. Open SS GUI Button
The IP address for each subscriber station is listed under IP Address in the table.
If the IP address of a subscriber station is suspected of being incorrect, select the subscriber station from the list
and then click Get SS IP. The selected subscriber station is queried for its current IP address.
Section 8.7
Figure 70: Registered SS IP Adresses
1. Registered Subscriber Stations 2. Get SS IP Button 3. Open SS GUI Button
2. Select the desired subscriber station and then click Open SS GUI. The management interface appears in a
new browser window or tab.
Section 8.8
CONTENTS
• Section 8.8.1, “Understanding Router Adjacency”
• Section 8.8.2, “Enabling/Disabling Broadcasts Between Subscriber Stations”
Section 8.8.1
Section 8.8.2
1
2
3
4
2. Under Block Broadcast Between CPEs, select one of the following options:
NOTE
The current setting is displayed under Current Mode of Block Broadcast Between CPEs.
• Disable – Non-VLAN tagged broadcast/multicast frames are forwarded over-the-air from one subscriber
station to another
• Enable – Non-VLAN tagged broadast/multicast frames are not forwarded over-the-air from one subscriber
station to another
3. Click Apply and then restart the base station.
Section 8.9
CONTENTS
• Section 8.9.1, “Unlocking Ethernet Traffic”
• Section 8.9.2, “Viewing/Clearing Subscriber Station Traffic Data”
Section 8.9.1
2. Select the desired subscriber station and then click Unlock Ethernet Traffic. A confirmation message
appears.
3. Click OK.
Section 8.9.2
1. Navigate to Subscribers » Subscriber Management » Registered SS. The Registered SS screen appears.
Figure 73: Registered SS Screen
1. Number of Registered SS 2. Registered Subscriber Stations 3. Connections Button 4. Capabilities Button 5. Deregister Button
6. Reboot Button
2. Select a subscriber station and then click Connections. The SS Connections screen appears.
1
2
3
4
5
6
Parameter Description
Packets Dropped The number of packets dropped by the base station or subscriber station.
Packets Sent The number of packets received from or sent to the subscriber station.
Bytes Sent The total size of all packets (in bytes) successfully received from or sent to the subscriber
station.
Section 8.10
Managing Handover
This section describes how to manage the seamless handover of subscriber stations to neighboring base stations.
IMPORTANT!
Handover must be permitted by each participating subscriber station. For RUGGEDCOM WIN subscriber
stations, this is done by enabling the Failover BS and Allow NBR Scanning parameters.
IMPORTANT!
Handover features are only available when the base station is in Standalone mode. For more
information about Standalone mode, refer to Section 5.1, “Setting the Operating Mode”.
CONTENTS
• Section 8.10.1, “Understanding Handover”
• Section 8.10.2, “Configuring Handover”
• Section 8.10.3, “Managing Neighboring Base Stations”
• Section 8.10.4, “Configuring DCD Triggers”
• Section 8.10.5, “Verifying the Handover Configuration”
• Section 8.10.6, “Manually Handing Over Subscriber Stations”
Section 8.10.1
Understanding Handover
Handover is a technique for making sure each subscriber station is served by the base station with the best signal
strength and quality. It makes sure that when a subscriber station needs to transition from its current Serving Base
Station (SBS) to a Target Base Station (TBS) it is able to do so with as little disruption to the wireless service as
possible.
Handover is necessary when the signal strength (RSSI) is weak, the signal quality (CINR) is poor, or the time
between respones (RTD) is too long. Specific thresholds for each can be defined using Downlink Channel
Descriptor (DCD) triggers, which can initiate the handover process automatically. Specific subscriber stations can
also be handed over manually when needed to another base station, referred to as a neighboring base station.
There are different handover techniques:
• Controlled Handover
Consists of an action phase and prepration phase.
• Uncontrolled Handover
Consists of an action phase and a limited prepration phase.
• Unpredictive Handover
Consists of an action phase only.
RUGGEDCOM WIN allows for handover to take place between base stations with different central frequencies
(referred to as Inter-Frequncy Handover) using the Unpredictive Handover technique.
1
3
4 5
CONTENTS
• Section 8.10.1.1, “Neighboring Base Stations”
• Section 8.10.1.2, “DCD Triggers”
• Section 8.10.1.3, “Handover in Standalone Mode”
Section 8.10.1.1
Neighboring Base Stations
To accelerate the handover process, base stations in sight of the current base station can be added to a list of
possible handover targets. These are referred to as neighboring base stations.
Subscriber stations looking to migrate to another base station can refer to this advertised list, rather than perform
timely scanning.
Up to 32 base stations can be added to the neighboring base station list.
Section 8.10.1.2
DCD Triggers
Downlink Channel Descriptor (DCD) triggers allow for the automatic handover of subscriber stations. Each trigger
monitors one or more metrics and performs actions if those metrics exceed the defined thresholds.
The following is an example of a DCD trigger definition:
Index Metric Duration Value Function Action
In this example, subscriber stations are told to scan for a new serving base station when the base station's CINR
falls below 22 dB. The handover process is started automatically when a neighboring base station's CINR is 3 dB
greater than the current base station's CINR reading.
NOTE
It is considered best practice in deployed networks to configure at least one DCD trigger with a
scanning action. This will prevent subscriber stations from constantly scanning for neighboring base
stations.
Section 8.10.1.3
Handover in Standalone Mode
Configuration of the handover function is the same when the base station is in either Standalone or ASN-GW
mode. The handover process is also the same from the perspective of registered subscriber stations. However,
some characteristics of the handover process on the base station side are important to understand.
Latency (Handover Ttime) Backbone latency can cause long HO time Lower HO time – Only BS to BS communication
needed , normally the BS’s are collocated or physically
close.
Security AK (shared secret) sent unencrypted between ASN-GW More secure ,NO AK keys are sent , the Master session
and BS (assumes secured network) keys sent encrypted between AAA and the BS
Scalability Unlimited number of base stations and subscriber Number of base stations and subscriber stations is
stations limited
Section 8.10.2
Configuring Handover
To configure the handover feature, do the following:
1. Configure Downlink Channel Descriptor (DCD) triggers to control when handover occurs. For more
information, refer to Section 8.10.4, “Configuring DCD Triggers”.
IMPORTANT!
For successful handovers, each base station selected as a valid handover candidate must share the
same configuration as the current base station (e.g. service flows, VLANs, DUIC, UIUC, etc.).
2. Add one or more neighboring base stations to the list of potential target base stations. This can be done
manually or by using auto discovery to automatically find local base stations. For more information, refer to
Section 8.10.3.1, “Adding a Neighbor”.
3. Configure the Media Access Control (MAC) layer settings for DCDs. For more information, refer to
Section 12.2.2, “Configuring the MAC Layer Settings”.
4. Make sure one or more subscriber stations are configured to participate in the handover process. For more
information, refer to the RUGGEDCOM WIN User Guide for the subscriber stations.
Section 8.10.3
CONTENTS
• Section 8.10.3.1, “Adding a Neighbor”
• Section 8.10.3.2, “Verifying the Configuration of a Neighbor”
Section 8.10.3.1
Adding a Neighbor
Neighboring base stations can be added through auto discovery or added manually.
NOTE
If no base stations are listed, either the current base station has no neighbors or the BSID and/or
IP Address need to be updated.
5. Select one or more base stations from the list and then click Use. The selected base stations are added to the
list of neighboring base stations.
IMPORTANT!
For successful handovers, each base station selected as a valid handover candidate must share the
same configuration as the current base station (e.g. service flows, VLANs, DUIC, UIUC, etc.), with
the exception of the Operational Mode setting. Operational Mode must be set to Auto for
each handover candidate.
6. View the configuration of each selected base station and confirm which are valid neighbors (i.e. have the
same conifiguration as the current base station). For more information, refer to Section 8.10.3.2, “Verifying
the Configuration of a Neighbor”.
Parameter Description
For RUGGEDCOM WIN base stations, the frequency is listed under Wireless » Radio and
Frame » Radio Settings.
6. Click Apply.
7. View the configuration of the base station and confirm if the base station is a valid neighbor (i.e. has the
same conifiguration as the current base station). For more information, refer to Section 8.10.3.2, “Verifying
the Configuration of a Neighbor”.
Section 8.10.3.2
Verifying the Configuration of a Neighbor
To successfully handover a subscriber station to a neighboring base station, the neighboring (target) base station
and the current (service) base station must be identical (e.g. service flows, VLANs, DUIC, UIUC, etc.).
To view the configuration of a neighboring base station, do the following:
1. Navigate to Wireless » MAC » Neighbor BS. The Neighbor Settings screen appears.
2. Select a base station and then click Verify Configuration. The NBR Configuration Verification Screen
appears.
3. [Optional] Under Update Delay, set the number of seconds (s) to wait before updating the configuration and
then click Update.
4. Not any differences reported. If the differences are indicated, consider removing the base station as a
handover candidate.
Section 8.10.4
NOTE
For information about DCD triggers, refer to Section 8.10.1.2, “DCD Triggers”.
1. Navigate to Wireless » MAC » DCD Triggers. The DCD Triggers screen appears.
1
3
4 5 6 7 8
NOTE
An index number is assigned automatically to the DCD trigger under Index once the configuration
is applied.
Function Synopsis: { Nbs greater abs value, Nbs less abs value, Nbs greater rel value, Nbs less rel
value, Sbs greater abs value, Sbs less abs value }
Default: Sbs greater abs value
The metric function. Options include:
• Nbs greater abs value – The metric (e.g. CINR, RSSI or RTD) measured at the
target (neighboring) base station is greater than the absolute value specified
Parameter Description
• Nbs less abs value – The metric (e.g. CINR, RSSI or RTD) measured at the target
(neighboring) base station is less than the absolute value specified
• Nbs greater rel value – The metric (e.g. CINR, RSSI or RTD) measured at the
target (neighboring) base station is greater than the relative value measured at the
current serving base station
• Nbs less rel value – The metric (e.g. CINR, RSSI or RTD) measured at the target
(neighboring) base station is less than the relative value measured at the current
serving base station
• Sbs greater abs value – The metric (e.g. CINR, RSSI or RTD) measured at the
current serving base station is greater than the absolute value specified
• Sbs less abs value – The metric (e.g. CINR, RSSI or RTD) measured at the current
serving base station is less than the absolute value specified
4. Click Apply.
Section 8.10.5
NOTE
For the following test, a subscriber station must be registered with the base station and a neighboring
base station must be defined. The subscriber station must be able to access the network where the
neighboring base station resides.
1. Make sure bi-directional traffic can be run between the subscriber station and current base station.
2. Either physically move the subscriber station (if in a lab environment) or adjust the antennae to activate the
DCD trigger. The handover process should begin, taking from 80 to 200 milliseconds (ms).
Following a successful handover, bi-directional traffic will begin flowing between the subscriber station and
the neighboring base station.
Section 8.10.6
IMPORTANT!
For a successful handover, select a neighbor that shares the same configuration as the current
base station (e.g. service flows, VLANs, DUIC, UIUC, etc.).
2. Select a base station from the Neighbor BS Table or click Auto Discovery to select one of the base stations
found on the network.
3. Click Move CPE to Neighbor. The Registered SS for HO screen appears.
4. Select one or more subscriber stations to hand over the selected base station neighbor and then click Perform
HO.
Section 8.11
Figure 86: Registered SS Screen
1. Number of Registered SS 2. SS Table 3. Connections Button 4. Capabilities Button
The total number of registered subscriber stations is listed under Number of Registered SS.
Details about each registered subscriber station are provided in the SS Table. This table displays the following
information:
Column Description
SS ID The Service Set Identifier (SSID) associated with the subscriber station.
Connections The number of downlink and uplink connections to and from the subscriber station.
State The operating state of the subscriber station. Possible values include:
• Init – Initial state.
• DL Synchronization – MS seeks a valid preamble and DL MAPS
• Ranging – Subscriber station is in ranging state. Power, frequency and timing correction are sent to
MS by the base station
• Handover ranging – Subscriber station has started the handover process
• Capabilities negotiation – Subscriber station and base station are exchanging capability
parameters (authentication support, number of service flows supported, different modulations
supported, and other parameters)
• Authorization – Subscriber station is being authorized
• Registration – Service Flows are being created
• Operational – Subscriber station has completed its entry to the network
Operation Time The time elapsed since the subscriber station registered with the base station.
Column Description
Basic CID The basic Connection Identifier (CID) associated with the subscriber station.
Authentication Mode Indicates if the subscriber station has been authenticated. Possible values include:
• PKMv2.0 – The subscriber station has been authenticated
• Null authentication – The subscriber station has not been authenticated
Active Service Profile The current service profile name assigned to the subscriber station.
AK Lifetime The Authorization Key Lifetime (AKL). This value indicates the long the subscriber station's Authorization
Key (AK) is valid.
Next Re-Authentication The time until the subscriber station must be re-authenticated by the base station.
For more information about individual subscriber stations, refer to Section 8.12, “Listing Subscriber Station
Connections” or Section 8.13, “Listing Subscriber Station Capabilities”.
Section 8.12
Figure 87: Registered SS Screen
1. Number of Registered SS 2. Registered Subscriber Stations 3. Connections Button 4. Capabilities Button 5. Deregister Button
6. Reboot Button
2. Select a subscriber station and then click Connections. The SS Connections screen appears.
SS ID displays the Set Service Identifier (SSID) assigned to the subscriber station.
SS Name displays the name assigned to the subscriber station.
The Connections Table details the following information about each of the subscriber station's connections:
Column Description
Scheduling Service The type of scheduling service used. For information about scheduling services, refer to Section 9.3.1.3,
“Scheduling Types”.
Min Rate The minimum data rate in kilobits per second (kbits/s).
Max Rate The maximum data rate in kilobits per second (kbits/s).
SF Type The type of data delivery service. For information about data delivery services, refer to Section 9.3.1.4,
“Data Delivery Services”.
Column Description
Latency The time in milliseconds (ms) in which packets can be received. If the time to receive a packet exceeds
this time, the packet is dropped.
HARQ Max Retries The maximum number of Hybrid Automatic Repeat Request (HARQ) attempts.
For more details about a specific connection – including the connection direction, how many packets have been
dropped, how many packets have been sent, and how many bytes have been sent – refer to Section 4.5.5,
“Viewing Subscriber Station Connection Statistics”.
Section 8.13
Figure 89: Registered SS Screen
1. Number of Registered SS 2. Registered Subscriber Stations 3. Connections Button 4. Capabilities Button 5. Deregister Button
6. Reboot Button
2. Select a subscriber station and then click Capabilities. The SS Connections screen appears.
SS ID displays the Set Service Identifier (SSID) assigned to the subscriber station.
SS Name displays the name assigned to the subscriber station.
The capabilities of the subscriber station are detailed under SBC Capabilities.
Traffic Control
This chapter describes how to configure and manage features that control incoming and outgoing traffic.
CONTENTS
• Section 9.1, “Enabling/Disabling Priority Tagging Pass-Through”
• Section 9.2, “Managing VLANs”
• Section 9.3, “Managing Service Profiles and Flows”
Section 9.1
NOTE
Priority tagging pass-through is disabled by default.
3. Under Priority Tagging Pass-Through Support, select either True to enable priority tagging pass-through or
False to disable priority tagging pass-through.
4. Click Apply.
Section 9.2
Managing VLANs
This section describes how to configure and manage Virtual Local Area Networks (VLANs).
CONTENTS
• Section 9.2.1, “Configuring a VLAN”
• Section 9.2.2, “Enabling/Disabling Transparent VLANs”
• Section 9.2.3, “Configuring a VLAN Subscription”
• Section 9.2.4, “Configuring the Management VLAN”
• Section 9.2.5, “Listing Current VLANs”
Section 9.2.1
Configuring a VLAN
To configure a VLAN, do the following:
1. Navigate to Subscribers » Services » Configured VLANs. The Configured VLAN Services screen appears.
2 3 4 5 6
4. Click Apply.
5. Reboot the base station to activate the new VLAN. For more information, refer to Section 4.1, “Rebooting the
Device”.
VLANs are listed on the Current VLAN Services screen. For more information, refer to Section 9.2.5, “Listing
Current VLANs”.
Section 9.2.2
IMPORTANT!
When enabled, all VLANs are converted to transparent VLANs.
Section 9.2.3
Figure 94: Pre-Provisioned SS Screen
1. Pre-Provisioned Subscriber Stations 2. Apply Button 3. SS Configuration Button 4. Service Profile Button 5. VLAN Button
2. Select the desird subscriber station and then click VLAN. The VLAN Subscription screen appears.
3. Select one or more VLANs and then click either Subscriber or Unsubscriber.
Section 9.2.4
3. Click Apply.
Section 9.2.5
The Current VLAN Table details the following for each VLAN:
Column Description
Applicable Base The subscriber station association with the VLAN multicast connection. Possible values
include:
• All Users – The VLAN is associated with all registered subscriber stations
• Registration Base – The VLAN is associated with a single subscriber station
Broadcast Max Rate The maximum data rate in kilobits per second (kbits/sec) for VLAN-tagged broadcast traffic.
Broadcast Traffic Priority The priority tag assigned to broadcast traffic. This is required for Quality of Service (QoS).
Section 9.3
CONTENTS
• Section 9.3.1, “Understanding Service Profiles and Flows”
• Section 9.3.2, “Configuring Service Profiles and Service Flows”
• Section 9.3.3, “Managing Service Profiles”
• Section 9.3.4, “Managing Service Flows”
• Section 9.3.5, “Example: Configuring a Service Profile for Multicast Traffic”
Section 9.3.1
CONTENTS
• Section 9.3.1.1, “Service Profiles”
• Section 9.3.1.2, “Service Flows”
• Section 9.3.1.3, “Scheduling Types”
• Section 9.3.1.4, “Data Delivery Services”
• Section 9.3.1.5, “Traffic Classes”
• Section 9.3.1.6, “Traffic Priority”
• Section 9.3.1.7, “Traffic Shaping”
• Section 9.3.1.8, “Fairness”
Section 9.3.1.1
Service Profiles
A service profile is a set of service flows assigned to a subscriber station. Each service profile corresponds to the
Quality of Service (QoS) requirements of the subscriber station.
For example, a service profile can consist of the following service flows: one flow matching VoIP needs, a second
flow matching video conferencing needs, and a third flow matching web browsing needs.
RUGGEDCOM WIN features a default service profile named default. This profile is assigned to all registered
subscriber stations. It includes two service flows that apply Best Effort (BE) scheduling to uplink and downlink
traffic.
Section 9.3.1.2
Service Flows
Service flows are a key feature of the IEEE 802.16e standard. A service flow represents a unidirectional data flow
having separate Quality of Service (QoS) settings for uplink and downlink. Service flows provide the ability to set
up multiple connections to each subscriber in a sector.
Separate service flows can be established for uplink and downlink traffic, where each service flow is assigned
a unique service level category and separate QoS settings. This feature allows segregation of high-speed/high-
priority traffic from less time-critical flows.
Scheduling
The serving base station enforces QoS settings for each service flow by controlling all uplink and downlink traffic
scheduling. This provides a non-contention based traffic model with predictable transmission characteristics. By
analyzing the total of all requests from all subscribers, the base station makes sure uplink and downlink traffic
conforms to the current Service Level Agreements (SLAs). Centralized scheduling increases predictability of traffic,
eliminates contention, and provides the maximum opportunity for reducing overhead.
A regular period is scheduled for subscribers to register with the base station. These subscribers may be newly
commissioned or have been deregistered due to service outage or interference on the wireless interface. This is
the only opportunity for multiple subscribers to transmit simultaneously.
Section 9.3.1.3
Scheduling Types
One of the following scheduling types can be deployed by the base station:
• Best Effort (BE)
The serving base station schedules transmit opportunities for the subscriber to send traffic based on unused
bandwidth after all higher level traffic scheduling requirements are serviced. Typical applications include
Internet access and email. Best effort service flows can be assigned a priority of 0 to 7.
• Non-Real-Time Polling Service (nrt-PS)
The serving base station schedules regular transmit opportunities for the subscriber to send variable size data
packets. Typical applications include high bandwidth FTP. The polling period is typically be one second or less,
even during periods of network congestion.
• Real-Time Polling Service (rt-PS)
The serving base station schedules a continuous series of transmit opportunities for the subscriber to send
variable size data packets. The grant size is based on the current data transfer requirement. Typical applications
include streaming MPEG video or VoIP with silence suppression. This is efficient for applications that have a real-
time component and continuously changing bandwidth requirements.
• Extended Real-Time Polling Service (ert-PS)
The serving base station schedules a continuous series of transmit opportunities for the subscriber to send
variable size data packets. This schedule supports real-time applications including VoIP with silence suppression.
The dynamically scheduled grants guarantee reserved bandwidth and reduce latency introduced by repetitive
grant requests. The service flow will not transmit packets larger than the nominal grant interval.
• Unsolicited Grant Service (UGS)
The serving base station schedules a continuous series of transmit opportunities for the subscriber to send fixed
size data packets. This schedule supports real-time applications, including VoIP or TDM transport. The UGS pre-
scheduled grants guarantee reserved bandwidth and reduce latency introduced by repetitive grant requests.
The service flow will not transmit packets larger than the nominal grant interval.
Section 9.3.1.4
Data Delivery Services
Data delivery services refer to specific sets of base station Quality-of-Service (QoS) settings for downlink and
uplink service flows.
The following lists the different types of delivery services and their corresponding system behavior for downlink
traffic.
Delivery Service Description Application Example Scheduling Type
Best Effort (BE) Intended for applications with no rate or delay Web browsing, data transfer BE
requirements.
Non Real-Time Intended for applications that require a guaranteed data File Transfer Protocol (FTP) nrt-PS
Variable Rate (nrt- rate, but that are insensitive to delays.
VR)
Real-Time Intended for real-time data applications with variable bit Streaming audio and video, MPEG rt-PS
Variable Rate (rt- rates and guaranteed data rate and delay. encoded
VR)
Extended Real- Intended for real-time applications with variable data rates VoIP with silence suppression ert-PS
Time Variable and guaranteed data and delay. For example: VoIP with
Rate (ert-VR) silence suppression.
Unsolicited Grant Intended for real-time applications generating fixed-rate Voice-over-IP (VoIP) without silence UGS
Service (UGS) data. Data can be provided as either fixed- or variable- suppression
length PDUs.
Section 9.3.1.5
Traffic Classes
The following describes the classes assigned to service flow traffic.
Base Station
All service flow traffic in the base station is divided into two traffic classes:
• Below CIR
A guaranteed traffic class, wherein the actual traffic rate of the service flow is under or equal to the Committed
Information Rate (CIR). This class is further divided into two sub-classes:
▫ Maximum Latency Non-Null
▫ Maximum Latency Null (i.e. maximum latency is not configured)
• Above CIR
A best effort class, wherein the actual traffic rate of the service flow is over the Committed Information Rate
(CIR). In terms of prioritization between the traffic classes, there is a strict priority hierarchy as follows (the order
is from the highest priority to lowest):
1. IEEE 802.16e MAC messages (exchanged between the subscriber station and base station)
2. Guaranteed traffic class with non-null maximum latency
3. Guaranteed traffic class with null maximum latency
4. Best effort class (all the Above CIR traffic)
Subscriber Station
All service flow traffic in the subscriber is divided into two traffic classes:
• Below CIR
A guaranteed traffic class, wherein the actual traffic rate of the service flow is under or equal to the Committed
Information Rate (CIR).
• Above CIR
A best effort class, wherein the actual traffic rate of the service flow is over the Committed Information Rate
(CIR). In terms of prioritization between the traffic classes, there is a strict priority hierarchy as follows (the order
is from the highest priority to lowest):
1. IEEE 802.16e MAC messages (exchanged between the subscriber station and base station)
2. UGS and ertPS traffic
3. All other service flow traffic:
a. A service flow that requested bandwidth and received an allocation will be scheduled before a service
that hasn not asked for bandwidth yet.
b. A guaranteed traffic class will be treated before a best effort class (all the Above CIR traffic)
Section 9.3.1.6
Traffic Priority
The following describes the priority assigned to traffic within each traffic class.
Base Station
Within the traffic class, the traffic is prioritized in one of the following ways:
• Strict Priority
Each service flow is assigned a traffic priority. The service flow with the higher traffic priority is served first.
If two service flows have the same traffic priority, they are served in round-robin fashion.
• Weighted-Fair Scheduling
Each service flow is assigned a traffic priority and each priority is assigned a weight. The bandwidth is shared
relatively according to the weights given.
For example, If service flow A has a weight of 2 and service flow B has a weight of 1, service flow A is granted
2/3 of the available bandwidth and service flow B is granted 1/3.
Service flows with the same traffic priority are assigned the wieght and will be granted to the same bandwidth
allocation.
Subscriber Station
Within the traffic class, the traffic is assigned a traffic priority. The service flow with the higher traffic priority is
served first.
If two service flows have the same traffic priority, they are served in round-robin fashion.
Section 9.3.1.7
Traffic Shaping
Traffic shaping (or packet shaping) is performed by the base station in downlink communications and by the
subscriber station in uplink communications.
Shaping is a technique for improving latency and increasing usable bandwidth by controlling the volume of traffic.
It occurs automatically when traffic (either upstream or downstream) exceeds the maximum flow rate defined for
the associated service flow.
When shaping occurs, service flow traffic is stored in a First-In First -Out (FIFO) buffer until it conforms to the
current Service Level Agreements (SLAs). It is then retransmitted on a scheduled basis so as not to exceed the
maximum flow rate. If the traffic flow exceeds the maximum flow rate again, it is dropped.
Section 9.3.1.8
Fairness
RUGGEDCOM WIN applies the fairness algorithm multiple subscriber stations are connected to the base station
under different RF conditions. To illustrate, consider the following scenario:
• The base station is the serving base station to Subscriber A and Subscriber B.
• Subscriber A is close the base station and experiences good RF conditions that lead to a high Modulation and
Coding Scheme (MCS).
• Subscriber B is far from the base station and experiences significantly worse RF conditions than that of
Subscriber A.
• Both subscriber stations are configured to receive 300 kbit/sec of UGS traffic
To make sure both subscriber stations receive their required bitrate, the base station can employ one of the
following solutions:
• Byte Fairness
Both subscriber stations will receive the required bitrate, but for Subscriber B, which is the furthest away, it will
cost more frame resources than for Subscriber A.
• Resource Fairness
Both subscriber stations will get an equal part of the frame.
• Combined Fairness
The Byte Fairness and Resource Fairness approaches are mixed according to a certain percentage (for example,
50% resource and 50% byte fairness).
Each approach can be applied per traffic class. RUGGEDCOM WIN applies the Byte Fairness approach for both
below and above Committed Information Rate (CIR) traffic classes.
Section 9.3.2
Section 9.3.3
CONTENTS
• Section 9.3.3.1, “Configuring Service Profiles”
• Section 9.3.3.2, “Updating Service Profile”
• Section 9.3.3.3, “Configuring IP-CS Mode”
• Section 9.3.3.4, “Enabling/Disabling a Service Profile”
• Section 9.3.3.5, “Assigning a Service Profile to a Subscriber Station”
• Section 9.3.3.6, “Listing Associated Subscriber Stations”
Section 9.3.3.1
Configuring Service Profiles
To configure a service profile, do the following:
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
IMPORTANT!
IP-CS mode must be enabled if convergence sublayer mode is set to IP-CS.
For more information, refer to Section 9.3.3.3, “Configuring IP-CS Mode”.
4. Click Apply.
5. Add a pool of service flows to the new service profile. For more information, refer to Section 9.3.4.1,
“Configuring Service Flows”.
6. Click Set Activation On/Off. The status under Profile Status changes from Inactive to Active.
7. Asssign the new service profile to one or more subscriber stations. For more information, refer to
Section 9.3.3.5, “Assigning a Service Profile to a Subscriber Station”.
Section 9.3.3.2
Updating Service Profile
To update a service profile and apply it to the registered subscriber stations for which it is assigned, do the
following:
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
2. Update the desired service profile. For more information, refer to Section 9.3.3.1, “Configuring Service
Profiles”.
3. Update the following parameters for the desired service profile as required:
Parameter Description
Parameter Description
IMPORTANT!
IP-CS mode must be enabled if convergence sublayer mode is set to IP-CS.
For more information, refer to Section 9.3.3.3, “Configuring IP-CS Mode”.
4. Click Apply.
5. Select the updated service profile and then click Update Profile. The selected service profile is applied to all
registered subscriber stations for which the service profile has been assigned.
Section 9.3.3.3
Configuring IP-CS Mode
IP-CS (Internet Protocol Convergence Sublayer) mode allows the base station to respond to DHCP requests with
the MAC and IP addresses of the hosts behind the subscriber stations.
To configure IP-CS mode, do the following:
1. Navigate to Backbone » Backbone Admin » CS Config. The CS Configuration screen appears.
1
2
3
4
2. Under Configured IP CS in SA mode, select Enable to enable IP-CS mode, or Disable to disable IP-CS mode.
Refer to Current IP CS in SA Mode for the current state.
3. Configure the following parameters:
Parameter Description
7. [Optional] Add a classifier for each service flow. For more information, refer to Section 9.3.4.2, “Configuring
Traffic Classifiers”.
8. Assign the service flows to one or more subscriber stations. For more information, refer to Section 9.3.3.5,
“Assigning a Service Profile to a Subscriber Station”.
Alternatively, if a AAA server is used, subscriber stations can be subscribed to a service profile using the
callback ID in the AAA user configuration.
Section 9.3.3.4
Enabling/Disabling a Service Profile
To enable or disable a service profile, do the following:
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
2. Select the desired service profile and then click Set Activation On/Off. The status of the service profile
changes under Profile Status to either Active or Inactive.
3. Click Update Profile. The updated status of the profile is communicated to the associated subscriber stations.
This action also deregisters the relevant subscriber stations.
Section 9.3.3.5
Assigning a Service Profile to a Subscriber Station
After defining the pool of service flows, individual service profiles can then be assigned to specific subscriber
stations according to QoS requirements.
To assign a service profile to a subscriber station, do the following:
1. Navigate to Subscribers » Subscriber Management » Pre-Provisioned SS. The Pre-Provisioned SS screen
appears.
Figure 102: Pre-Provisioned SS Screen
1. Pre-Provisioned Subscriber Stations 2. Apply Button 3. SS Configuration Button 4. Service Profile Button 5. VLAN Button
2. Select the SSID for the desired subscriber station and then click Service Profile. The Service Profile
Subscription screen appears.
3. Select a service flow and then click Subscribe. The status under Subscription Status changes from
Unsubscribed to Subscribed.
Alternatively, a service flow can be unassigned by clicking Unsubscribe.
4. Re-register the subscriber station with the base station. For more information, refer to Section 8.5,
“Deregistering Subscriber Stations”.
Section 9.3.3.6
Listing Associated Subscriber Stations
To list the subscriber stations associated with a service profile, do the following:
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
2. Select the desired service profile and then click Subscribers. The Service Profile Subscribers screen appears.
Section 9.3.4
CONTENTS
• Section 9.3.4.1, “Configuring Service Flows”
• Section 9.3.4.2, “Configuring Traffic Classifiers”
Section 9.3.4.1
Configuring Service Flows
To configure service flows for a service profile, do the following:
NOTE
A maximum of eight service flows can be configured per service profile.
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
2. Select a service profile and then click Add/Edit Service Flows. The Unicast Service Flows screen appears.
ID Synopsis: An integer
A unique, numeric ID for the service flow.
NOTE
This parameter is related to the classifier lookup mechanism, but is not
related to traffic scheduling itself.
Parameter Description
The direction in which the service flow is assigned. Options include:
• DL – Downlink
• UL – Uplink
NOTE
Configure this parameter only when Scheduling Service is set to nRT,
RT, eRT or UGS.
NOTE
Configure this parameter only when Scheduling Service is set to BE,
nRT, RT or eRT.
Service Default
BE 0
NRT 1
RT 5
UGS 7
Parameter Description
Service Default
ERT 7
NOTE
Configure this parameter when Direction is set to UL and Scheduling
Service is set to eRT.
NOTE
Configure this parameter when Direction is set to UL and Scheduling
Service is set to either nRT, RT, eRT or UGS.
A value of default applies the following default value based on the data delivery
service:
NRT 1000
RT 20
ERT 1000
UGS 1000
Service Default
BE 3
NRT 3
RT 0
UGS 0
ERT 0
Service Default
BE 0
NRT 0
Parameter Description
Service Default
RT 30
UGS 30
ERT 30
For more information about latency, refer to the FAQ Understanding Latency Between
the RUGGEDCOM WIN Base Station (BS) and the RUGGEDCOM WIN Subscriber Station
(SS) [https://support.industry.siemens.com/cs/ww/en/view/103948900].
5. Click Apply.
6. [Optional] Define what type(s) of traffic can be mapped to the new service flow. For more information, refer
to Section 9.3.4.2, “Configuring Traffic Classifiers”.
Section 9.3.4.2
Configuring Traffic Classifiers
A traffic classifer maps a specific type of traffic to a specific traffic flow. Traffic can be defined according to the
traffic source, traffic type, or combination of traffic source and type. For example, traffic can be defined by DSCP
range, port range, IP address source or destination, and other parameters. The base station performs a logical OR
when considering traffic types.
Up to four traffic classifers can be defined for each service flow.
Data packets are analyzed according to each classifier assigned to a service flow until a match is found.
RUGGEDCOM WIN performs a logical OR when applying each classifier.
Each classifer can consist of up to two filters. If a classifier has two filters, RUGGEDCOM WIN performs a logical
AND between the filters when applying the classifier.
To configure a traffic classifier for a service flow, do the following:
1. Navigate to Subscribers » Services » Service Profiles. The Service Profiles screen appears.
2. Select the desired service profile and then click Add/Edit Service Flows. The Unicast Service Flows screen
appears.
3. Select the desired service flow and then click Classifiers. The Unicast SF Classifiers screen appears.
Classifier Value The value on which to filter for the selected traffic characteristic. The following are
examples of possible values.
Parameter Description
Bits 0, 1, 2
IP precedence bits value: 0 to 7
indicate datagram importance.
Default = 0; higher is better.
Bits 3,4,5
Values: D,T,R requesting: low
delay, high throughput, high
reliability
6. Click Apply.
Section 9.3.5
1. Add a VLAN specifically for multicast traffic. For more information, refer to Section 9.2.1, “Configuring a
VLAN”.
2. Review the available VLANs and make sure the new VLAN is displayed. For more information, refer to
Section 9.2.5, “Listing Current VLANs”.
3. Assign the VLAN ID to a pre-provisioned subscriber station. For more information, refer to Section 9.3.3.5,
“Assigning a Service Profile to a Subscriber Station”.
4. Define a service profile. For more information, refer to Section 9.3.3.1, “Configuring Service Profiles”.
5. Define a service flow for the service profile. For more information, refer to Section 9.3.4.1, “Configuring
Service Flows”.
6. Add a traffic classifer with the following minimum configuration:
Classifer Type 1 VLAN
CONTENTS
• Section 10.1, “Managing SNMP”
• Section 10.2, “Managing MAC Addresses”
Section 10.1
Managing SNMP
The Simple Network Management Protocol (SNMP) is used by network management systems and the devices they
manage. It is used to report alarm conditions and other events that occur on the devices it manages.
RUGGEDCOM WIN supports SNMPv2 and SNMPv3, which offer the following features:
• Provides the ability to send a notification of an event via traps. Traps are unacknowledged UDP messages and
may be lost in transit.
• Provides the ability to notify via informs. Informs simply add acknowledgment to the trap process, resending the
trap if it is not acknowledged in a timely fashion.
• Encrypts all data transmitted by scrambling the contents of each packet to prevent it from being seen by an
unauthorized source. The AES CFB 128 and DES3 encryption protocols are supported.
• Authenticates all messages to verify they are from a valid source.
• Verifies the integrity of each message by making sure each packet has not been tampered with in-transit.
SNMPv3 also provides security models and security levels. A security model is an authentication strategy that is
set up for a user and the group in which the user resides. A security level is a permitted level of security within a
security model. A combination of a security model and security level will determine which security mechanism is
employed when handling an SNMP packet.
Before configuring SNMP, note the following:
• Each user belongs to a group
• A group defines the access policy for a set of users
• An access policy defines what SNMP objects can be accessed for: reading, writing and creating notifications
• A group determines the list of notifications its users can receive
• A group defines the security model and security level for its users
CONTENTS
• Section 10.1.1, “Configuring SNMP”
Section 10.1.1
Configuring SNMP
To configure SNMP, do the following:
1. Enable and configure either SNMPv2 or SNMPv3. For more information, refer to either Section 10.1.2,
“Configuring SNMPv2” or Section 10.1.3, “Configuring SNMPv3”.
2. Enable the required SNMP traps. For more information, refer to Section 10.1.4.2, “Enabling/Disabling SNMP
Traps”.
3. Configure one or more trap destinations (up to a maximum of five). For more Information, refer to
Section 10.1.4.4, “Configuring SNMP Trap Destinations”.
4. Configure the system contact and location information for the base station. For more Information, refer to
Section 10.1.6, “Configuring the SNMP System Group”.
Section 10.1.2
Configuring SNMPv2
To configure the SNMPv2c parameters, do the following:
1. Navigate to Admin » SNMP. The SNMP General Settings screen appears.
1
2
3
1
2
3
4
IMPORTANT!
The SNMP Read Community and SNMP Write Community values must be unique.
Parameter Description
5. Click Apply.
Section 10.1.3
Configuring SNMPv3
To configure the SNMPv3 parameters, do the following:
1. Navigate to Admin » SNMP. The SNMP General Settings screen appears.
1
2
3
3. Configure one or more SNMP users. For more information, refer to Section 10.1.5, “Configuring Users for
SNMPv3”.
4. Click Apply.
Section 10.1.4
CONTENTS
• Section 10.1.4.1, “Available SNMP Traps”
• Section 10.1.4.2, “Enabling/Disabling SNMP Traps”
• Section 10.1.4.3, “Sending SNMP Traps”
• Section 10.1.4.4, “Configuring SNMP Trap Destinations”
Section 10.1.4.1
Available SNMP Traps
NOTE
The WIMAX-BS-TRAPS.mib file in the software release folder contains a full list of traps.
Restart Trap
Trap Description
Severity Warning
Default Enabled
Alarm ID 0
Action None
RestartFailure Description BS init failure. This event shall report all causes of
initialization errors.
Severity Major
Trap Description
Default Enabled
Alarm ID 0
Communication Traps
Trap Description
TimingUnLock Description Lost synchronization with GPS time. Value indicates time
source.
Severity Major
Default Enabled
Alarm ID 4
Action None
Severity Clear
Default Enabled
Alarm ID 4
Severity Critical
Default Enabled
Alarm ID 7
Action None
Trap Description
Severity Critical
Default Enabled
Alarm ID 8
Action None
FirstAAAReachable Description First AAA is alive. The trap is sent when the AAA server is back
after being unreachable.
Severity Clear
Default Enabled
Alarm ID None
Action None
SecondAAAReachable Description Second AAA is alive. The trap is sent when the AAA server is
back after being unreachable.
Severity Clear
Default Enabled
Alarm ID 23
Action None
Value Range —
Severity Info
Default —
Alarm ID 12
Action None
Text —
RF Traps
Trap Description
Condition When the average return loss is lower than 6db for 5 seconds.
This means that channel i antenna is disconnected and radio
powered is on.
Severity Critical
Default Enabled
Alarm ID 5
Action Tx off
Value Range —
Severity Clear
Default Enabled
Alarm ID 0
Action None
TransmissionStop Description BS SW is performing radio off value represent the initiator for
the action.
Severity Info
Default Disabled
Alarm ID 0
Action None
TransmissionStart Description BS SW is turning on radio value represent the initiator for the
action.
Severity Info
Default Disabled
Alarm ID 0
Action None
Trap Description
Text Radio is on
Hardware Trap
Trap Description
Value Range —
Severity Critical
Default Enabled
Alarm ID 6
Action TX off
Text HW Failure
Security Traps
Trap Description
Login Description Every login to one of the BS local management interfaces; this
allows WiNMS user to be updated.
Severity Warning
Default Enabled
Alarm ID 0
Action None
Login Description Every login to one of the BS local management interfaces; this
allows WiNMS user to be updated.
Severity Warning
Default Enabled
Alarm ID 0
Action None
Login Description This event should assist operator to recognize hackers trying
to enter the network.
Trap Description
Value Range —
Severity Major
Default Enabled
Alarm ID 0
Action None
Environmental Traps
Trap Description
Value Range —
Severity Major
Default Enabled
Alarm ID —
Value Range —
Severity Critical
Default Enabled
Alarm ID —
Action Stop Tx
Value Range —
Severity Clear
Default Enabled
Alarm ID —
Trap Description
Redundancy Traps
Trap Description
Value Range —
Default Enabled
Alarm ID —
Action None
Text —
Value Range —
Severity Info
Default Enabled
Alarm ID —
Action None
Text —
Condition BS has become slave ready due to slave not ready that
became capable of doing redundancy or election
Value Range —
Default Enabled
Alarm ID —
Action None
Text —
Value Range —
Severity Critical
Default Enabled
Trap Description
Alarm ID 8
Action None
Text —
Severity Critical
Default Enabled
Alarm ID 9
Text —
Severity Clear
Default Enabled
Alarm ID —
Action None
Text —
DuplicateMasterDetected Description Indicates that there are 2 master BSs on the network.
Severity Critical
Default Enabled
Alarm ID 10
Text —
Value Range —
Trap Description
Severity Critical
Default Enabled
Alarm ID 13
Text —
Value Range —
Default Enabled
Alarm ID 14
Text —
Services Traps
Trap Description
SF not established for CPE Description SF establishment failure. CPE de-registration will occur.
Condition After network entry, the CPE is Operational and ISF fails to
establish.
Severity Major
Default Enabled
Alarm ID —
Text —
Value Range CPE MSID = “fill in the MSID” + “fill in the SF name” service
cannot be provided to the CPE.
Severity Major
Default Enabled
Alarm ID —
Action None
Text —
LinkUp Description CPE is operational. Clears the LinkDown and LinkFlap traps.
Value Range —
Severity Info
Default Enabled
Alarm ID —
Action —
Text —
Severity Major
Default Enabled
Alarm ID —
Action —
Text —
Severity —
Default —
Alarm ID —
Action —
Text —
Condition —
Value Range —
Severity —
Default —
Alarm ID —
Action —
Trap Description
Text —
Section 10.1.4.2
Enabling/Disabling SNMP Traps
To enable or disable an SNMP trap, do the following:
1. Navigate to Admin » Alarms and Traps » Traps. The SNMP Trap Settings screen appears.
2
3
2. Under Activation Mode for the selected SNMP trap, select True to enable the trap or False to disable the
trap.
3. Click Apply.
Section 10.1.4.3
Sending SNMP Traps
For testing purposes, selected SNMP traps can be sent on demand.
To send SNMP traps, do the following:
1. Navigate to Admin » Alarms and Traps » Traps. The SNMP Trap Settings screen appears.
2
3
IMPORTANT!
Only SNMP traps that have been enabled can be sent on demand.
Section 10.1.4.4
Configuring SNMP Trap Destinations
Trap destinations represent SNMP trap receivers configured to receive SNMP traps and inform messages from a
device. RUGGEDCOM WIN supports up to five trap destinations.
To configure a destination for SNMP traps, do the following:
1. Navigate to Admin » SNMP. The SNMP General Settings screen appears.
1
2
3
2. Under the Managers Table, click the + button. A new row is added to the table.
3. In the Destination IP Address column, enter the IP address of an SNMP server.
4. Click Apply.
Section 10.1.5
1
2
3
3. Under the Users Table, click the + button. A new row is added to the table.
4. Configure the following parameters:
NOTE
It is recommended to use strong passphrases that meet the following criteria:
• One lower case character
• One upper case character
• One number
• One special character (i.e. !@#$%^&*()_+-={}[];:',<>/?\|`~)
Parameter Description
Privacy Passphrase The passphrase used to decrypt communications with the SNMP trap receiver.
Parameter Description
Access Group The SNMPv3 access group associated with the user name. For more information about
available access groups, refer to Section 10.1.7, “Viewing SNMPv3 Access Groups”.
5. Click Apply.
6. Verify the new user by generating and sending a trap. For more information about sending a trap manually,
refer to Section 10.1.4.3, “Sending SNMP Traps”.
Section 10.1.6
1
2
3
4
5
6
7
3. Click Apply.
Section 10.1.7
NMS Access Group Users can view and read all MIBs User can create, modify and Users can view and read all
delete MIBs notification MIBs
Traps Only Users cannot view or read MIBs User cannot create, modify or Users can view and read all
delete MIBs notification MIBs
For convenience, these access group definitions are included in the user interface.
To view the available SNMPv3 access groups, do the following:
1. Navigate to Admin » SNMP. The SNMP General Settings screen appears.
1
2
3
3. Click Access Groups. The SNMPv3 Access Groups Configuration screen appears.
Section 10.2
CONTENTS
• Section 10.2.1, “Viewing/Clearing the MAC Address Table”
• Section 10.2.2, “Viewing/Clearing the ARP Table”
• Section 10.2.3, “Configuring the Age Out Period for MAC Addresses”
Section 10.2.1
SS ID Displays the subscriber station ID, if applicable, from which the MAC address was learned.
SS Name Displays the name of the subscriber station ID, if applicable, from which the MAC address
was learned.
VLAN ID Displays the identifier for the Virtual LAN on which the node is active.
Aging Time Displays the time (in seconds) until the entry will be removed from the table.
Interface Displays the interface from which the base station learned the MAC address. Possible values
include:
• Network – the base station acquired the address from the Ethernet network interface
• RF – the base station acquired the address from the RF interface
• Local – indicates the MAC address of the base station itself
Section 10.2.2
Number of Entries displays the total number of entries in the ARP table.
The ARP table details the following information about each entry:
Parameter Description
Aging Time The time in seconds (s) until the entry is removed from the table.
Section 10.2.3
1
2
3
4
2. Under MAC Address Table Aging Time, enter the age out period in seconds. The value can between 300 and
1800 seconds. The default value is 900 seconds.
3. Click Apply.
Remote Management
This section describes how to configure the base station to be managed by a remote host.
CONTENTS
• Section 11.1, “Configuring Management via a Backhaul Subscriber Station”
Section 11.1
Managed By CPE The MAC address of the primary subscriber station used to manage the base station.
Backup CPE The MAC address of the secondary subscriber station used to manage the base station.
This subscriber station will take over if the primary subscriber station is offline.
3. Click Apply.
Wireless
This section describes how to configure and manage the base station's wireless features.
CONTENTS
• Section 12.1, “Starting/Stopping Transmissions”
• Section 12.2, “Managing Wireless Settings”
• Section 12.3, “Managing ASN Gateways”
Section 12.1
Starting/Stopping Transmissions
When necessary (i.e. to deregister subscriber stations), radio transmissions can be disabled by stopping the radio
service.
To start or stop radio transmissions, do the following:
NOTE
For devices operating on the 3.5 GHz band, radio transmissions may be temporarily stopped by
RUGGEDCOM SAS-GW due to a lack of available spectrum. Transmissions will be reenabled once
spectrum is available.
1
2
3
4
5
6
7
8
10
11
12
13
2. Click Start Service to start transmitting, or click Stop Service to stop all transmissions.
Section 12.2
CONTENTS
• Section 12.2.1, “Configuring the Base Station Name and ID”
• Section 12.2.2, “Configuring the MAC Layer Settings”
• Section 12.2.3, “Managing the WiMAX Radio”
• Section 12.2.4, “Managing Link Adaptation”
Section 12.2.1
1
2
3
4
5
3. Click Apply.
4. If you changed the value in the Configured Base Station ID or Configured Operator ID fields, reboot the
base station:
a. Click Quick Start. The Quick Start Settings pane appears.
b. Click Reboot.
Section 12.2.2
1
2
3
4
3. Click Apply.
Section 12.2.3
CONTENTS
• Section 12.2.3.1, “Viewing a Summary of WiMAX Radio Capabilities”
• Section 12.2.3.2, “Configuring the WiMAX Radio”
• Section 12.2.3.3, “Configuring the Structure of Frames”
Section 12.2.3.1
Viewing a Summary of WiMAX Radio Capabilities
To view a summary of the base station's WiMAX radio capabilities, navigate to Wireless » Radio and Frame »
Radio Capabilities. The Radio Capabilities screen appears.
1
2
3
4
5
6
7
Min Supported Frequency The minimum transmission frequency in kilohertz (kHz) supported by the radio.
Max Supported Frequency The maximum transmission frequency in kilohertz (kHz) supported by the radio.
Supported BW The bandwidths supported by the radio. Multiple bandwidths are separated by forward
slashes (/).
For example, 3.5/5/7/10 indicates support for 3.5 MHz, 5 MHz, 7 MHz, and 10 MHz
bandwidths.
Supported MIMO Schemes The Multiple-Input Multiple-Output (MIMO) schemes supported by the radio. Multiple
schemes are separated by forward slashes (/).
For example, MATRIX-A/MATRIX-B indicates both MIMO Matrix A and MIMO Matrix B are
supported.
Parameter Description
Min Supported Transmit Power The minimum amount of Radio Frequency (RF) power in dBm output by the radio.
Max Supported Transmit Power The maximum amount of Radio Frequency (RF) power in dBm output by the radio.
Number of RF Channels The number of Radio Frequency (RF) transmission channels used by the radio.
Section 12.2.3.2
Configuring the WiMAX Radio
To configure the WiMAX radio, do the following:
1. Navigate to Wireless » Radio and Frame » Radio Settings. The Radio Settings screen appears.
1
2
3
4
5
6
7
8
9
10
11
Current Frequency [kHz] Displays the current base station radio frequency, in kilohertz.
Configured Frequency [kHz] The radio frequency transmitted by the base station. The value must be within the range
defined by Min Supported Frequency and Max Supported Frequency.
Changes to this parameter will only take effect after a system reboot.
Parameter Description
Tx power [dBm] The amount of Radio Frequency (RF) power in dBm output by the radio. The value must
be within the range defined by Min Supported Transmit Power and Max Supported
Transmit Power.
3. Click Apply.
4. If parameters marked with * were configured, restart the base station service. For more information, refer to
Section 12.1, “Starting/Stopping Transmissions”.
Section 12.2.3.3
Configuring the Structure of Frames
To configure the structure of each frame distributed by the base station, do the following:
1. Navigate to Wireless » Radio and Frame » Frame Settings. The Frame Settings screen appears.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
NOTE
The TDD split values listed provide the same uplink throughput as values
from previous versions of RUGGEDCOM WIN, but with better download
throughput due to more download symbols available from the same
number of uplink symbols.
Configured Split
Actual Split (%)
Recommended
Channel
Split (%)
Split (%)
(%)
(%)
5/10 MHz 30 to 34 32 36 30 to 31 29 33
35 to 38 36 36 32 to 35 33 33
39 to 42 40 40 36 to 39 38 38
43 to 46 45 49 40 to 44 42 47
47 to 51 49 49 45 to 48 47 47
52 to 55 53 53 49 to 53 51 51
56 to 59 57 62 54 to 57 56 60
60 to 63 62 62 58 to 62 60 60
64 to 68 66 66 63 to 66 64 64
69 to 73 70 74 67 to 71 69 73
74 to 75 74 74 72 to 75 73 73
a
3.5 /7 30 27 27 30 to 31 28 34
MHz
31 to 36 33 33 32 to 37 34 34
37 to 42 39 45 38 to 43 41 41
43 to 48 45 45 44 to 49 47 53
49 to 54 52 52 50 to 56 53 53
Parameter Description
Configured Split
Configured Split
Actual Split (%)
Recommended
Channel
Split (%)
Split (%)
(%)
(%)
55 to 60 58 64 57 to 62 59 59
61 to 66 64 64 63 to 68 66 72
67 to 72 70 70 69 to 74 72 72
73 to 75 76 76 75 78 78
a
Configuration begins at 53% configured.
NOTE
The TDD split in the uplink is as follows:
• 3.5 MHz is supported up to 47% in the uplink
• 5 MHz, 7 MHz and 10 MHz is supported up to 70% in the uplink
Subscriber Line of
Extended Cell Range
Channel Bandwidth Site Distance from
Configuration
the Base Station (Km)
5/10 MHz +8 km On
Configured Subchannel Bitmap Synopsis: { All Subchannels, PUSC1 1/3, PUSC2 1/3, PUSC3 1/3, PUSC1 1/2, PUSC2 1/2 }
Default: All Subchannels
The subchannel used in the first downlink Partially Used Subchannel (PUSC) zone. The
current setting is displayed under Current Subchannel Bitmap.
For information about PUSC zones, refer to the FAQ Understanding Partially Used
Subchannels (PUSC) [https://support.industry.siemens.com/cs/ww/en/view/104466301].
3. Click Apply.
4. If parameters marked with ** were configured, reboot the base station. For more information, refer to
Section 4.1, “Rebooting the Device”.
Otherwise, restart the base station service. For more information, refer to Section 12.1, “Starting/Stopping
Transmissions”.
Section 12.2.4
CONTENTS
• Section 12.2.4.1, “Configuring Link Adaptation”
• Section 12.2.4.2, “Configuring DIUCs for Burst Profiles”
• Section 12.2.4.3, “Configuring UIUCs for Burst Profiles”
• Section 12.2.4.4, “Configuring the Interference Detection Threshold”
Section 12.2.4.1
Configuring Link Adaptation
To configure link adaptation, do the following:
1. Navigate to Wireless » Radio and Frame » Link Adaptation. The Link Adaptation Settings screen appears.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Parameter Description
• MIMO A – Independent data streams are sent over each antenna
3. Click Apply.
4. If parameters marked with ** were configured, reboot the base station. For more information, refer to
Section 4.1, “Rebooting the Device”.
5. Configure a DIUC for each downlink burst profile. For more information, refer to Section 12.2.4.2,
“Configuring DIUCs for Burst Profiles”.
6. Configure a UIUC for each uplink burst profile. For more information, refer to Section 12.2.4.3, “Configuring
UIUCs for Burst Profiles”.
7. Configure the interference detection threshold. For more information, refer to Section 12.2.4.4, “Configuring
the Interference Detection Threshold”.
Section 12.2.4.2
Configuring DIUCs for Burst Profiles
A DIUC (Downlink Interval Usage Code) represents a burst profile (e.g. modulation, encoding, usage conditions,
etc.) for a downlink burst. It consists of the following:
• An index number, which is associated with a specific burst profile
• A modulation and Forward Error Correction (FEC) code
By default, a DIUC is defined for each supported modulation technique.
To change the modulation technique assigned to a DIUC, do the following:
1. Navigate to Wireless » Radio and Frame » DL Modulation. The DL Coding and Modulation Settings screen
appears.
2. If adding a new DIUC, click the . A new row appears in the Access List Table.
3. Under Modulation and FEC Code, select one of the following options:
• Auto – The modulation technique is selected automatically based on the current RF conditions.
• { modulation technique } – A specific modulation technique to be used for the DIUC index. The same
technique can be assigned to multiple DIUC indexes. For information about the available modulation
techniques, refer to Section 1.3, “Supported Modulation Techniques”.
4. Click Apply.
Section 12.2.4.3
Configuring UIUCs for Burst Profiles
A UIUC (Uplink Interval Usage Code) represents a burst profile (e.g. modulation, encoding, usage conditions, etc.)
for a uplink burst. It consists of the following:
• An index number, which is associated with a specific burst profile
• A modulation and Forward Error Correction (FEC) code
By default, a UIUC is defined for each supported modulation technique.
To change the modulation technique assigned to a UIUC, do the following:
1. Navigate to Wireless » Radio and Frame » DL Modulation. The DL Coding and Modulation Settings screen
appears.
2. If adding a new UIUC, click the . A new row appears in the Access List Table.
3. Under Modulation and FEC Code, select one of the following options:
• Auto – The modulation technique is selected automatically based on the current RF conditions.
• { modulation technique } – A specific modulation technique to be used for the UIUC index. The same
technique can be assigned to multiple DIUC indexes. For information about the available modulation
techniques, refer to Section 1.3, “Supported Modulation Techniques”.
4. Click Apply.
Section 12.2.4.4
Configuring the Interference Detection Threshold
RUGGEDCOM WIN base stations actively monitor Air Quality (AQ) for interference that may disrupt
communications. The interference may be persistent (intermittent and repeatable) or spontaeous (random). When
the interference level exceeds a user-defined threshold, the base station will automatically generate an alarm,
analyze the available spectrum and select a different channel. The complete process can take up to 30 seconds.
To set the threshold for excessive interference, do the following:
1. Navigate to Wireless » Radio and Frame » Interference Detection. The Interference Detection Settings
screen appears.
3. Click Apply.
Section 12.3
CONTENTS
• Section 12.3.1, “Configuring the ASN Gateway Connection”
• Section 12.3.2, “Configuring the IP Address for an ASN Gateway”
• Section 12.3.3, “Configuring Keep Alive Settings”
• Section 12.3.4, “Determining the R6 Signaling Protocol In Use”
Section 12.3.1
Section 12.3.2
1
2
3
2. Under Configured ASN-GW IP Address, enter the IPv4 address for the ASN gateway.
3. Click Apply and then restart the base station.
Following the reboot, the R6 signal protocol used between the ASN gateway and the base station should be
displayed under Current R6 Flavor. This indicates a successful connection to the ASN gateway.
Section 12.3.3
1
2
3
4
4. Click Apply.
5. If Keep Alive Activation Mode was enabled or disabled, reboot the base station.
Section 12.3.4
1
2
3
The R6 signal protocol used between the ASN gateway and the base station is displayed under Current R6 Flavor.
Troubleshooting
This chapter describes troubleshooting steps for common issues that may be encountered when using
RUGGEDCOM WIN.
CONTENTS
• Section 13.1, “Troubleshooting Resources”
• Section 13.2, “Frequently Asked Questions”
Section 13.1
Troubleshooting Resources
This section describes the various troubleshooting resources available within RUGGEDCOM WIN.
CONTENTS
• Section 13.1.1, “Pinging an IPv4 Address or Host”
• Section 13.1.2, “Tracing a Route to an IPv4 Host”
• Section 13.1.3, “Viewing/Clearing Aggregate Throughput Statistics”
• Section 13.1.4, “Accessing Developer Mode”
• Section 13.1.5, “Using the Spectrum Analyizer Tool”
Section 13.1.1
1
2
3
4
5
6
Figure 140: Ping Screen
1. Destination IP Address Box 2. Packet Length Box 3. Number of Packets Box 4. Timeout Box 5. Don't Fracture Bit Box
6. Result 7. Ping Button
Packet Length The size of each individual packet (in bytes) sent by the ping request.
Timeout Time in milliseconds (ms) RUGGEDCOM WIN will wait for a reply after sending a ping
request. If the time period is exceeded, the IP address or host is deemed unreachable.
Don't Fracture Bit Controls when the Don't Fragment flag is set. Options include:
• Enable – The Don't Fragment flag is set
• False – The Don't Fragment flag is not set
Section 13.1.2
1
2
3
4
5
6
Timeout Time in seconds (s) RUGGEDCOM WIN will wait for the trace route to complete.
Don't Perform DNS Lookup Select a value to enable or disable DNS lookup. When set to True, DNS lookup is
performed as part of the trace route operation. When set to False, DNS lookup is not
performed as part of the trace route operation. The default is False.
Controls if DNS look up is performed as part of the trace route operation. Options
include:
• Enable – DNS lookup is performed
• False – DNS lookup is not performed
4. Click Trace Route. The result of the trace is displayed under Result.
Section 13.1.3
1
2
3
4
5
6
7
8
9
10
11
Aggregate DL Packets The total number of downlink packets since statistics were last cleared.
Aggregate UL Packets The total number of uplink packets since statistics were last cleared.
Aggregate UL Bytes The total number of uplink bytes since statistics were last cleared.
Aggregate DL Bytes The total number of downlink bytes since statistics were last cleared.
Aggregate UL CRC Failures The total number of uplink CRC (Cyclic Redundancy Check) failures since statistics were last
cleared.
Aggregate UL CRC OK The total number of CRC (Cyclic Redundancy Check) successes since statistics were last
cleared.
Section 13.1.4
NOTE
• Developer mode is only available to developers for advanced troubleshooting purposes.
• Developers cannot access the device without logging into the system first.
IMPORTANT!
The developer mode password is provided by Siemens. To obtain a password, contact Siemens
Customer Support.
Section 13.1.5
• Setting the Spectrum Analyzer to operate and accumulate data within a specified span
• Viewing a frozen or held signal for comparison with continuing incoming signals
• Other basic measurement tools and functions
CONTENTS
• Section 13.1.5.1, “Configuring the Spectrum Analyzer Tool”
• Section 13.1.5.2, “Starting/Stopping the Spectrum Analyzer Tool”
• Section 13.1.5.3, “Plotting the Spectrum”
• Section 13.1.5.4, “Freezing the Current Signal”
• Section 13.1.5.5, “Enabling Max Hold”
• Section 13.1.5.6, “Placing a Marker”
• Section 13.1.5.7, “Selecting/Unselecting a Signal”
• Section 13.1.5.8, “Setting the Span of a Spectrum Analysis”
• Section 13.1.5.9, “Enabling Hold”
• Section 13.1.5.10, “Saving the Spectrum Plot”
• Section 13.1.5.11, “Clearing the Spectrum Plot”
Section 13.1.5.1
Configuring the Spectrum Analyzer Tool
To configure the Spectrum Analyzer tool, do the following:
1. Start the Spectrum Analyzer tool. For more information, refer to Section 13.1.5.2, “Starting/Stopping the
Spectrum Analyzer Tool”.
2. Navigate to Admin » Spectrum Analyzer. The Spectrum Configuration screen appears.
1
2
3
4
5
6
7
10
Central Frequency The central frequency measured in kilohertz (kHz) between the upper and lower cutoff
frequencies.
Frequency Span The range measured in megahertz (MHz) between the start and stop frequencies.
Number of Sweeps to Average The number of sweeps to perform for trace averaging.
Input Antenna The input antenna. Spectrum calculations will be based on the signals received by this
antenna.
Gain Shift The receiver (Rx) gain correction used to avoid compression of the input signals.
4. Click Apply. The spectrum plot now conforms to the new settings.
For more information about viewing the spectrum plot, refer to Section 13.1.5.3, “Plotting the Spectrum”.
Section 13.1.5.2
Starting/Stopping the Spectrum Analyzer Tool
NOTE
Starting the Spectrum Analyzer requires the base station to restart in Spectrum Analyzer mode. Service
is interrupted until the Spectrum Analyzer Tool is stopped.
2. Click Start Spectrum. A confirmation message appears requesting to restart the base station in Spectrum
Analyzer mode.
3. Click OK. The base station reboots in Spectrum Analyzer mode.
4. Configure the Spectrum Analyzer tool. For more information, refer to Section 13.1.5.1, “Configuring the
Spectrum Analyzer Tool”.
1
2
3
4
5
6
7
10
2. Click Stop Spectrum. The base station reboots into normal operation mode.
Section 13.1.5.3
Plotting the Spectrum
To view the spectrum analysis plot, navigate to Admin » Spectrum Analyzer » Spectrum Plot. The Spectrum Plot
screen appears.
The table above the spectrum graph details the status of the spectrum analysis. The following information is
displayed:
Column Description
Max Hold The status of the Max Hold function. Possible values include: ON and OFF.
Peak The frequency and power of the peak signal level within the spectrum.
Hold Freezes the current signal and displays it in blue. Real-time signals are then displayed in
yellow next to the frozen signal. Use this to compare signal changes over time.
For more information about freezing the current signal, refer to Section 13.1.5.4, “Freezing
the Current Signal”.
Button Description
Max Hold Displays only the highest point detected for each frequency range during the test. This is
analogous to the Max Hold function on a standard spectrum analyzer.
For more information about this function, refer to Section 13.1.5.5, “Enabling Max Hold”.
Set Span Sets the span of the spectrum analyzer to the frequency band of the selected part of the
frozen signal.
For more information about using this function, refer to Section 13.1.5.8, “Setting the Span
of a Spectrum Analysis”.
Section 13.1.5.4
Freezing the Current Signal
During spectrum analysis, signal readings move from left to right on the spectrum graph. Click Freeze to stop the
spectrum analysis and display the signal in its current state.
Section 13.1.5.5
Enabling Max Hold
The Max Hold function places a dot on the spectrum graph at the highest point detected for each frequency range
during the spectrum analysis.
In the following example, a dot is placed where the mechanical power output (Pmax) reach -77 dBm and the
frequency (F) is 3557.6 MHz.
To enable this function, click Max Hold. The cell under Max Hold in the table above the spectrum graph changes
from Off to On.
To disable this function, click Max Hold again.
Section 13.1.5.6
Placing a Marker
Markers display frequency (Fcur) and power (Pcur and Pheld) information for the area where they are placed. This
information appears in the Marker column in the table above the spectrum graph.
To place a marker, simply left-click the desired area on the spectrum graph. A red vertical line appears on the
graph.
Figure 149: Marker
NOTE
Markers can only be placed one at a time.
Section 13.1.5.7
Selecting/Unselecting a Signal
To zoom in on an area of the spectrum graph for greater detail, left-click and drag a box around the desired area
on the graph and then click Select. The selected area will expand to fill the spectrum graph window.
To zoom out, click Unselect.
Section 13.1.5.8
Setting the Span of a Spectrum Analysis
The spectrum analysis can be adjusted to acquire signals from a specific bandwidth region.
To set the span to which the analysis will focus, do the following:
1. Left-click and drag a box around the desired area and then click Set Span. A confirmation message appears to
confirm the action.
2. Click Yes.
The frequency range and power recorded in the selected region are displayed in the Power Over BW column in
the table above the spectrum graph.
Section 13.1.5.9
Enabling Hold
The Hold function freezes the current signal and changes its color to blue, while the continuous real-time signal
appears behind it in yellow.
Figure 150: Hold Enabled
Section 13.1.5.10
Saving the Spectrum Plot
Data from the spectrum analysis can be saved locally to a Comma-Separated Value (CSV) file for future reference.
To save the spectrum plot, click Save to File and follow the on-screen instructions to save the file.
Section 13.1.5.11
Clearing the Spectrum Plot
Click Clear to clear all data collected since the spectrum analysis began. The spectrum plot will display signals
acquired from that point forward.
Section 13.2
Q: Why is there no connectivity between the base station and RUGGEDCOM NMS?
A: The base station is either powered down, not connected to the network, or using a different RF IP address
than what is configured in RUGGEDCOM NMS. Do the following to identify the problem:
1. First, make sure the workstation running RUGGEDCOM NMS is setup as an SNMP trap destination. For
more information, refer to Section 10.1.4.4, “Configuring SNMP Trap Destinations”.
2. If the workstation is an SNMP trap destination, ping the base station at its RF IP address from the
workstation running RUGGEDCOM NMS.
3. If there is no response, make sure the base station is powered and connected to the network.
4. If the base station is powered and connected, verify the RF IP address assigned to the device.
a. Connect directly to the device. For more information, refer to Section 3.2.2, “Connecting Directly”.
b. Establish an SSH connection using the device's LAN IP address.
c. Enter showipaddr. The RF IP address for the device is displayed.
If the LAN IP address is unknown, do the following:
a. Start a packet analyzer, such as Wireshark, on the workstation connected directly to the base
station.
b. Reboot the base station.
c. In the packet analyzer, open the gratuitous ARP message from the device and look for the RF IP
address defined within.
5. From the workstation running RUGGEDCOM NMS, ping the IP address assigned to the base station.
6. If there is still no response from the base station, contact Siemens Customer Support.
Q: Why is there no serial connection, even though a serial cable is connected to the base station?
A: If there is no serial connection when using the serial cable, perform the following:
1. Ping the base station's RF IP address.
2. If the RF IP address is unreachable, verify the power connections.
3. If power is connected, but there is still no serial connection or IP connectivity, contact Siemens
Customer Support.
Q: Why is the base station inaccessible or slow to access via HTTPS and/or SSH?
A: The base station may be experiencing a memory leak issue. Try disabling one or more logs to free up
memory. For more information, refer to Section 4.6.2, “Enabling/Disabling Logs”.