Vecima Networks EUM3004 Wireless LAN end-users modem User Manual LMS4000 900 MHz Guide

Vecima Networks Inc. Wireless LAN end-users modem LMS4000 900 MHz Guide

Contents

User Manual LMS4000 900 MHz Part 2

Download: Vecima Networks EUM3004 Wireless LAN end-users modem User Manual LMS4000 900 MHz Guide
Mirror Download [FCC.gov]Vecima Networks EUM3004 Wireless LAN end-users modem User Manual LMS4000 900 MHz Guide
Document ID372626
Application ID69cS2s1SioSnWbj9syBU3A==
Document DescriptionUser Manual LMS4000 900 MHz Part 2
Short Term ConfidentialNo
Permanent ConfidentialNo
SupercedeNo
Document TypeUser Manual
Display FormatAdobe Acrobat PDF - pdf
Filesize100.04kB (1250550 bits)
Date Submitted2003-11-11 00:00:00
Date Available2003-11-11 00:00:00
Creation Date2003-11-11 11:16:37
Producing SoftwareAcrobat Distiller 5.0.5 (Windows)
Document Lastmod2003-11-11 11:17:01
Document TitleLMS4000_900_MHz_Guide.book
Document CreatorFrameMaker 6.0
Document Author: Administrator

9: Installing the EUM
9.4.9 Obtaining Valid IP Addresses for the End-user’s PC
To obtain IP addresses for the end-user’s PC, including the PC IP address, Gateway IP
address, and DNS server address, the PC must request an update from the DHCP server.
This procedure varies depending on which operating system is running on the end-user’s PC,
but a general method is outlined as follows.
NOTE: The subscriber PC may obtain a dynamic IP through DHCP, or it
may use a static IP and DNS server.
To Obtain a Valid IP Address for the End-user’s PC (Windows XP)
1. Open a command prompt window.
2. At the prompt, type ipconfig/release and press Enter.
3. Type ipconfig/renew and press Enter.
4. If no error messages are returned, the WISP network has successfully provided an IP
address to the end-user’s PC.
9.4.10 Testing the Data Link
The fact that the IP address was successfully obtained indicates that the data link from the PC
to the WISP's network is functioning properly. WaveRider recommends more thorough testing
of the EUM-to-CCU data link, as outlined below. These tests can also be used to troubleshoot
simple problems if DHCP access is not available.
There are several tools available for testing the quality of the link between the end-user PC
and the WISP network. The most important tool is the “file get” test, which tests the quality of
the data link. You can also use the ping command to progressively test presence of the data
link. The procedures for running the “file get” throughput tests and “ping” data link tests are
described below.
To Run a “File Get” Throughput Test From the EUM
1. Open the EUM console, as described in Access Interface on page 221.
2. At the prompt, type file get , and press Enter.
WaveRider Communications, Inc. LMS3000
Password:
60:ff:fe> file get 192.168.1.21
Enter password:
file transfer started (press 'qqq' to abort)...
bytes processed:
2097152 at
829 kbps
file transfer complete
Transfered "/tffs0/null" Okay.
60:ff:fe>
To Run a “File Get” Throughput Test From the CCU
1. Establish a Telnet connection to the CCU.
2. At the prompt, type file get , and press Enter.
156
APCD-LM043-8.0 (DRAFT C)
9: Installing the EUM
WaveRider Communications, Inc. LMS3000
Password:
60:03:3a> file get 192.168.10.250
Enter password:
file transfer started (press 'qqq' to abort)...
by
2097152 at
183 kbps24 at
201 kbps
file transfer complete
Transfered "/tffs0/null" Okay.
60:03:3a>
The following three tests use the “ping” command to progressively test the data link.
To Test the Data Link from the End-user’s PC to the EUM
1. Ping the EUM’s IP address from the end-user’s PC, as follows:
•
•
Open a DOS window in the end-user’s PC.
At the command prompt, type ping , where
 is the IP address of the EUM and press Enter.
2. If there is no response, check the following:
•
•
PC IP address settings.
Ethernet crossover cable between the EUM and the end-user’s PC, to ensure
that the pins have not been damaged.
3. If there is a response, but with errors, check the Ethernet crossover cable.
To illustrate data link testing between the PC and the EUM, consider the sample configuration
shown in Figure 60.
Internet
Gateway Router
Ethernet crossover
cable
Radio
Link
End-user's PC
IP Address 172.16.6.1
Net Mask
22
Gateway IP 172.16.4.1
EUM3000
IP Address
Net Mask
Gateway IP
CCU3000
Radio IP Address
172.16.4.1
Net Mask
22
172.16.4.2
22
172.16.4.1
EUM Antenna
End-user's Premises
Figure 60
APCD-LM043-8.0 (DRAFT C)
Sample Configuration — Testing the Data Link
157
9: Installing the EUM
Using the sample configuration shown in Figure 60, confirm the connection between the enduser’s PC and the EUM as demonstrated below:
This is what successful ping from the end-user’s PC to the EUM looks like:
C:\>ping 172.16.6.1
Pinging 172.16.6.1 with 32 bytes of data:
Reply
Reply
Reply
Reply
from
from
from
from
172.16.6.1:
172.16.6.1:
172.16.6.1:
172.16.6.1:
bytes=32
bytes=32
bytes=32
bytes=32
time<10ms
time<10ms
time<10ms
time<10ms
TTL=64
TTL=64
TTL=64
TTL=64
Ping statistics for 172.16.6.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
This is what an unsuccessful ping from the end-user’s PC to the EUM looks like:
C:\>ping 172.16.10.1
Pinging 172.16.10.1 with 32 bytes of data:
Request
Request
Request
Request
timed
timed
timed
timed
out.
out.
out.
out.
Ping statistics for 172.16.10.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
Testing the Data Link from the End-user’s PC to the Network
Once the connection from the PC to the EUM is confirmed, ping the EUM gateway address
from a PC DOS window. Ping with short packets first to confirm function, and then with long
packets (1472 byte packets) to confirm performance. Errors observed on pings with long
packets indicate a high error rate on the channel, caused by low signal levels or interference.
To Ping a CCU with the Maximum Packet Size
1. Open a DOS window.
2. At the command prompt, type ping  -t -L 1472, where
 is the CCU radio IP address and press Enter.
3. Press Ctrl+c to end the test.
NOTE: If this test fails, but pinging the CCU with the default packet size
succeeds, then the connection is working but is not operating at
maximum capacity, possibly due to poor antenna placement or
orientation.
158
APCD-LM043-8.0 (DRAFT C)
9: Installing the EUM
This following example uses the sample configuration shown in Figure 60:
Pinging the CCU from the end-user’s PC (with maximum packet size):
C:\>ping 172.16.4.1 -t -l 1472
Pinging 172.16.4.1 with 1472 bytes of data:
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
from
from
from
from
from
from
from
from
172.16.4.1:
172.16.4.1:
172.16.4.1:
172.16.4.1:
172.16.4.1:
172.16.4.1:
172.16.4.1:
172.16.4.1:
bytes=1472
bytes=1472
bytes=1472
bytes=1472
bytes=1472
bytes=1472
bytes=1472
bytes=1472
time=40ms TTL=64
time=81ms TTL=64
time=80ms TTL=64
time=40ms TTL=64
time=60ms TTL=64
time=80ms TTL=64
time=40ms TTL=64
time=110ms TTL=64
Ping statistics for 172.16.4.1:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 110ms, Average = 66ms
Control-C
^C
C:\>
Testing the Data Link from the End-user’s PC to the Internet
Use the following test to determine whether the end-user’s PC can communicate with the
Internet.
Pinging an Internet site from the PC using the site’s IP address:
C:\>ping 207.23.175.75
Pinging 207.23.175.75 with 32 bytes of data:
Reply
Reply
Reply
Reply
from
from
from
from
207.23.175.75:
207.23.175.75:
207.23.175.75:
207.23.175.75:
bytes=32
bytes=32
bytes=32
bytes=32
time=90ms
time=80ms
time=80ms
time=70ms
TTL=113
TTL=113
TTL=113
TTL=113
Ping statistics for 207.23.175.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 90ms, Average = 80ms
C:\>
Use the following test to verify that the DNS server IP address is correctly configured in the
end-user’s PC and is operating properly:
Pinging an Internet site from the PC, using the site’s domain name:
C:\>ping www.waverider.com
Pinging waverider.com [207.23.175.75] with 32 bytes of data:
Reply from 207.23.175.75: bytes=32 time=70ms TTL=113
Reply from 207.23.175.75: bytes=32 time=90ms TTL=113
Reply from 207.23.175.75: bytes=32 time=60ms TTL=113
APCD-LM043-8.0 (DRAFT C)
159
9: Installing the EUM
Reply from 207.23.175.75: bytes=32 time=50ms TTL=113
Ping statistics for 207.23.175.75:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 90ms, Average = 67ms
C:\>
9.4.11 Configuring the Browser Application
Follow the manufacturer's instructions for configuring the end-user’s browser, so that it
correctly uses the PC Ethernet interface. Once you have done this:
1. Launch the browser
2. Confirm access to sites of interest.
9.4.12 Completing the Installation
1. Configure the remaining PC applications, as required.
2. Re-activate the end-user’s cordless phones, and any other 900MHz ISM-band
equipment that was turned off at the beginning of the installation. Note the following
points:
•
•
•
Cordless phones operating in the 900MHz ISM band can disrupt service to
the EUM if precautions are not taken.
Run an FTP throughput test, and turn on the cordless phones in sequence,
while monitoring the downlink throughput. Since there is naturally a wide
variation in the downlink speed, for reasons more associated with the network
than with the performance of the LMS4000 wireless service, repeat the tests
several times to confirm whether or not the end user’s cordless phones are
going to affect the EUM performance.
If the cordless phones do affect the performance of the EUM, move the
cordless phone base station to a location as far from the antenna as possible.
Instruct the end user to avoid using the cordless handset in the proximity of
the antenna, particularly when the EUM is being used.
9.4.13 Baselining the Installation
Once you have completed the installation, WaveRider recommends recording the following
information:
•
EUM IP addresses
•
EUM radio settings
•
RSSI readings
•
Tx retry rate readings (displayed with the RSSI readings)
•
SQ, RNA, and RNB (displayed with the RSSI readings)
If you have problems with the EUM at a later date, you can compare the latest site settings
and RSSI readings with the original settings in the site installation record.
160
APCD-LM043-8.0 (DRAFT C)
9: Installing the EUM
You can record and save this information in several ways:
•
using the EUM Configuration Utility. Through the EUM Configuration Utility, you can
also upload and store the EUM’s complete configuration file.
•
through the EUM command-line interface locally, using a Telnet session, through the
EUM Ethernet connection.
•
through a Telnet session over the wireless link between the network and the EUM.
Record the information from the following session, and store it to a file.
60:02:04>
60:02:04> ip
IP Address: 172.16.4.2 / 22
IP Subnet : 10.5.0.0 ( 255.255.0.0 )
Gateway IP Address: 172.16.4.1
60:02:04>
60:02:04> radio
RF Power: HIGH
Radio Frequency: 9170
60:02:04>
60:02:04> rad rssi
Press any key to stop
RSSI[dBm]
RSSI: -36
RSSI: -36
RSSI: -36
RSSI: -36
RSSI: -37
RSSI: -37
RSSI: -36
RX; TX; R1; R2; R3;
0;
0;
0;
0;
0;
887;
2;
0;
0;
0;
899;
2;
0;
0;
0;
899;
3;
0;
0;
0;
898;
2;
0;
0;
0;
898;
2;
0;
0;
0;
899;
2;
0;
0;
0;
F;Retry%; SQ; RNA; RNB
0;
0;
7; 71; 71
0;
0;
5; 72; 71
0;
0;
8; 73; 72
0;
0;
6; 73; 72
0;
0;
5; 72; 72
0;
0;
6; 71; 71
0;
0;
5; 72; 72
You should also run the “file get” command from both the CCU and EUM to baseline the
installation.
To Run a “File Get” Throughput Test From the EUM
1. Open the EUM console, as described in Access Interface on page 221.
2. At the prompt, type file get , and press Enter.
WaveRider Communications, Inc. LMS3000
Password:
60:ff:fe> file get 192.168.1.21
Enter password:
file transfer started (press 'qqq' to abort)...
bytes processed:
2097152 at
829 kbps
file transfer complete
Transfered "/tffs0/null" Okay.
60:ff:fe>
To Run a “File Get” Throughput Test From the CCU
1. Establish a Telnet connection to the CCU.
2. At the prompt, type file get , and press Enter.
WaveRider Communications, Inc. LMS3000
Password:
APCD-LM043-8.0 (DRAFT C)
161
9: Installing the EUM
60:03:3a> file get 192.168.10.250
Enter password:
file transfer started (press 'qqq' to abort)...
by
2097152 at
183 kbps24 at
201 kbps
file transfer complete
Transfered "/tffs0/null" Okay.
60:03:3a>
162
APCD-LM043-8.0 (DRAFT C)
10
Maintaining the Network
The LMS4000 900MHz radio network requires virtually no maintenance. This chapter
describes what you need to do to maintain the CCU and EUM operating environments.
The CCU and EUM must be kept in a temperature-controlled and dust-free environment, as
described under the following headings:
•
Maintaining Temperature and Humidity on page 163
•
Cleaning the Equipment on page 164
•
Checking the CCU Shelf Cooling Fans on page 164
Maintaining Temperature and Humidity
Make sure the CCU and EUM sites meet the environmental requirements outlined in Table 27.
Table 27 Temperature and Humidity Requirements
Equipment
Operating
Temperature
Non-condensing
Relative Humidity
Storage
Temperature
CCU3000
0° to +50°C
5% to 95%
-40° to +70°C
EUM3000
10° to +40°C
5% to 95%
-40° to +70°C
EUM3003
0° to +40°C
5% to 95%
-40° to +70°C
APCD-LM043-8.0 (DRAFT C)
163
10: Maintaining the Network
Cleaning the Equipment
WARNING!
Make sure you follow ESD precautions when you touch and
clean CCU and EUM components.
When cleaning CCU and EUM components:
•
Use dry, static-free cloths to wipe dust from the devices.
•
Make sure you do not disconnect any cables or wires when cleaning.
Checking the CCU Shelf Cooling Fans
WARNING!
Exercise caution when you are in close proximity to the CCU
Shelf cooling fans. Disconnect AC power to the fans prior to
handling.
Verify that the cooling fans in the CCU Shelf are rotating freely and at a high speed when
connected to the power supply to ensure proper cooling of the CCUs.
164
APCD-LM043-8.0 (DRAFT C)
11
Monitoring the Network
Although there are a large number of detailed statistics available for the various data handling
applications in the CCU (refer to Appendix J on page 277 for a complete list), there are only a
few that are key for monitoring system performance on an on-going basis. These statistics are
described in detail on the following pages.
11.1
•
CCU Transmit Statistics on page 165
•
CCU Receive Statistics on page 169
•
EUM Transmit Statistics on page 171
•
EUM Receive Statistics on page 172
•
User Data on page 173
•
Logging CCU or EUM Statistics on page 173
•
CCU Air Table Statistics on page 174
•
CCU Radio Meter on page 175
CCU Transmit Statistics
As described in CCU–EUM Interface MAC Layer (Polling MAC) on page 40, the MAC
continuously transmits polls to the EUMs. These polls can contain specific user payloads
directed to the EUM or the PC connected to the EUM, control payloads directed to the EUM,
broadcast payloads directed to all EUMs, or empty polls, which contain no payload.
In an ideal system, all data transmitted would be received error free by the EUMs, and no retransmissions would be required. In the real world, unfortunately, RF noise, low signal
conditions, interferers, system engineering problems, and equipment malfunction can result in
the need to retransmit data over the radio link. These retransmissions, which are key to
maintaining data integrity for the end user, come with the trade-off of reduced network
capacity.
APCD-LM043-8.0 (DRAFT C)
165
11: Monitoring the Network
Statistics reported by the CCU can assist in identifying when retransmissions are occurring
and at what rate they are occurring. They can also be used to troubleshoot the cause of
retransmissions.
The statistic txPayloads gives the total number of transmitted payloads, consisting of
•
user data received by the CCU Ethernet port, and transmitted over the radio network,
•
user data received from an EUM, that is “switched” to the CCU radio port for
transmission to another EUM,
•
MAC control data,
•
broadcast data, and
•
data retransmitted because it was not acknowledged by an EUM and is assumed lost.
Examining this statistic in more detail, txPayloads includes
•
Tx Data Payloads which, in turn, includes
•
•
•
•
data originated by the CCU application and sent to the radio port,
data coming from the Ethernet port of the CCU (either end-user data or
operator monitoring [SNMP] data),
data coming from EUM-originated data payloads that have been “switched” to
the CCU radio port (for transmission to other EUMs), and
broadcast data to all EUMs(TxPayloadsBCast).
•
Tx Ctrl Payloads — Control data generated in the CCU, and used to configure, or
request status from, the EUMs. Tx Ctrl Payloads are transmitted during specific EUM
poll periods.
•
Retransmitted data — Data that is not acknowledged after a transmission and is
assumed to be lost or corrupted.
Understanding the relationship between these values helps you monitor the integrity of a CCU
radio environment.
All non-broadcast payloads (hence, “directed” payloads) are explicitly acknowledged by the
EUMs. For these payloads, the result of a transmission during an EUM poll cycle will be one of
the following:
Table 28 Possible Transmission Outcomes
Result of Transmission
166
Reported Statistic
Payload is delivered to an EUM and
acknowledged on the first poll.
txPayloads10k
Payload is transmitted twice, after which an
acknowledgement is received.
txPayloads20k
Payload is transmitted three times, after
which an acknowledgement is received.
txPayloads30k
Payload is transmitted four times, after
which an acknowledgement is received.
txPayloads40k
APCD-LM043-8.0 (DRAFT C)
11: Monitoring the Network
Result of Transmission
Reported Statistic
No acknowledgement received after four
transmissions, and the payload is
discarded.
txPayloadsFailRetry
Payload is not transmitted at all.
txPayloadsFailAssocDeleted
Total number of payloads returned to host
because they are malformed.
txPayloadsFailBadParam
Total number of payloads returned to host
because the virtual net was not active.
txPayloadsFailVnetInactive
Total number of empty payloads received
and returned to host.
txPayloadsEmpty
Total number of payloads returned to the
host because an association could not be
created.
txPayloadsFailAssocFail
Total number of payloads returned to the
host because of timeout.
txPayloadsFailTimeout
txPayloadsFailQueueTooLong
To put these values in perspective, the following samples have been taken from a live CCU,
using the  CLI command:
Table 29 Typical CCU Transmit Statistics
Statistic
Sample
txPayloadsBCast
txPayloads10k
66,001
txPayloads20k
1,761
txPayloads30k
281
txPayloads40k
91
txPayloadsFailRetry
102
txPayloadsFailAssocDeleted
11
txPayloadsFailBadParam
txPayloadsFailVnetInactive
txPayloadsEmpty
txPayloadsFailAssocFail
txPayloadsFailTimeout
txPayloadsFailQueueTooLong
APCD-LM043-8.0 (DRAFT C)
445
167
11: Monitoring the Network
The objective of the first level analysis of this data is to determine the relative amount of radio
traffic resulting from retransmissions. Ideally, the percentage would be 0. In practice, local
engineering limitations result in a certain normal level. Once this normal level is established,
the statistics can be used to monitor changes.
Since not all of these CCU transmit statistics are independent, you have to be careful when
interpreting and using results which are based on these statistics. For example, since
broadcast payloads are not acknowledged, the retry data is not relevant to these payloads,
and they have to be subtracted from the total. In addition, the txPayloadsFailAssocDeleted
and the following payloads are never transmitted and should be subtracted from the total. The
calculations to do this are shown below:
Net Payloads sent through directed polls (see note) = B + C + D + E + F = 68,236
NOTE: Due to real-time issues (at any given time, some packets are
being processed or queued), the numbers often differ by the
small number of packets that are in queues.
The percentage of directed payloads that are delivered on the first transmission
= 66,001 / 68,236 = 97%
Similarly, the percentage of directed payloads not delivered on the first transmission, but
delivered on the second transmission
= 1,761 / (68,236 - 66,001) = 79%
It is generally a good indication if most payloads that fail on the first try are then successful
with only one retry.
The percentage of directed payloads that are not able to be delivered
= 102 / 68,681 = 0.15%
A very low undeliverable payload rate implies that user service has a high level of integrity,
and that the radio link is not significantly impacting higher-level TCP/IP applications.
The impact of the retransmission can be calculated by looking at the total number of
transmissions requiring acknowledgments:
= 1xB + 2xC + 3xD + 4xE + 4xF = 71,138.
Adding to this value the non-acknowledged broadcast payloads (txPayloadsBCast = 445)
results in total txPayloads - 71,583.
A simple metric of overall sector link quality is the effective utilization of the channel, which can
be readily calculated as desired payloads transmitted/actual payloads transmitted, or:
(B + C + D + E +F) / (71,138 - G + H + I + J + K + L)
= 68,236 / 71,127 = 96%
168
APCD-LM043-8.0 (DRAFT C)
11: Monitoring the Network
which suggests that 4% of the radio traffic is used to retransmit packets, which is referred to in
this document as the Retransmission Rate.
From an operational point of view, it is important to keep the number of retransmissions to a
minimum since they reduce the total air time available and the total network throughput.
These calculations may appear tedious, but since all of the referenced statistics are available
through MIBs, SNMP management tools, such as SNMPc, can directly collect the statistics,
calculate the above metric, and track and report its value over time.
NOTE: The “stats summary” command displays similar calculations.
You can also monitor the MAC statistic “txPayloadsFailQueueTooLong” at the CCU to give an
indication of packet discards due to queue overrun. The MAC statistic
“lastQueueTooLongEUM” at the CCU indicates for which EUM the last packet was discarded.
That EUM can then be “watched” to determine how often discards occur and whether it is a
problem. Some discards may occur simply due to multiple concurrent downloads combined
with heavy system loading. If more than one EUM is having problems, the
“lastQueueTooLongEUM” statistic will change as discards occur.
11.2
CCU Receive Statistics
Similar to the case for CCU transmit statistics, there are several key CCU receive statistics
that you can use to monitor on-going performance of the CCU radio network. When the CCU
sends a directed poll to an EUM, it expects to get an acknowledgement. The following results
have been taken from a live CCU using the  command:
Table 30 Typical CCU Receive Statistic
Statistic
rxPktsDirected
APCD-LM043-8.0 (DRAFT C)
Description
The number of packets received
correctly from all EUMs. These may
contain an ack.
Sample
409,730
169
11: Monitoring the Network
Statistic
Description
Sample
rxPktsHCRCFail
Packet received with a corrupted
header.
rxPktsFCS Fail
Packet received from an EUM, with a
corrupted payload.
192
replyOrRssiTimeouts
No reply or EUM HCRC errors and
missed packets. Does not include FCS
(frame check sequence) errors.
22,688
2,464
Note: This statistic also includes EUM
receive errors, by virtue of the fact that
if an EUM does not receive a poll from
the CCU, for any reason, then it will
not reply to the CCU.
From these statistics:
Total number of replies expected = A + B + D = 434,882
and the receive packet error rate which, as noted in Table 30, includes EUM receive errors
and errors associated with random access attempts, is given by
RxPER = (B + C + D) / (A + B + D) = (2,464 + 192 + 22,688) / 434,882 = 5.8%
One other receive statistic that is important in multi-CAP environments where frequency reuse is implemented is rxPktsNoMatch. A high value of rxPktsNoMatch indicates that the two
CCU radio environments are interfering with each other.
The statistic rxPktsDuplicate measures the number of times the EUM sends the same packet
of information more than once. A high value of rxPktsDuplicate indicates that the
acknowledgements from the CCU are not being properly received at the EUM.
11.3
Watch Statistics
CCU statistics monitor the aggregate traffic to all EUMs connected to that CCU. The CCU
“watch” command is available for monitoring a single EUM, which is a very useful tool for
troubleshooting individual links. These statistics have the same meaning as the “stats mac”
statistics of the same name, but apply to a single EUM, rather than all EUMs. This command is
described in detail in CCU Watch Statistics on page 298.
170
APCD-LM043-8.0 (DRAFT C)
11: Monitoring the Network
11.4
EUM Transmit Statistics
In general, the statistics collected at the EUM are the same as those collected at the CCU;
however, there are some differences in meaning (see Appendix H). More significantly, of
course, is that the EUM statistics are unique to the EUM, as opposed to the CCU statistics,
which are a collective of the CCU and all EUM interactions.
The relationships of the key EUM statistics are the same as those for the CCU. In the case of
the EUM, however, no broadcast packets are transmitted, and the value of
txPayloadsFailAssocDeleted will always be 0. The key EUM transmit statistics, with sample
values, are shown below.
Table 31 EUM Transmit Statistics
Statistic
Description
Sample
Total
Payload
Total
Packets
txPayloads
Number of payloads transmitted.
49,101
Tx Data Payloads
Number of data payloads to be
transmitted (user data)
45,879
Tx Control Payloads
Number of control payloads to
be transmitted.
txPayloads10k
Payload is delivered to the EUM
and acknowledged on the first
poll.
43,153
43,153
x1
43,153
txPayloads20k
Payload is transmitted twice,
then acknowledge received.
2,306
2,306
x2
44,612
txPayloads30k
Payload is transmitted three
times, then acknowledge
received.
344
344
x3
1,032
txPayloads40k
Payload is transmitted four
times, then acknowledge
received.
47
47
x4
188
txPayloadsFailRetry
No acknowledge received after
four transmissions, packet
discarded.
29
29
x4
116
txPayloadsFailTime
out
Total number of payloads
returned to host because of
timeout.
Sum
45,879
49,101
The same combinations used for the CCU case are also included in the table for clarity.
APCD-LM043-8.0 (DRAFT C)
171
11: Monitoring the Network
As with the CCU transmit statistics, the following sample calculations can be made using the
sample data from Table 31:
Total number of desired payloads = B + C = 45,879 + 2 = 45,881
This is also equal to:
(D + E + F + G + H + I) = (43,153 + 2,306 + 344 + 47 + 29 + 0) = 45,879
NOTE: Due to real-time issues (the fact that at any given time, some
packets are being processed or queued), the numbers frequently
differ by the number of packets that are in queues.
NOTE: In the case of the EUM, most payloads are sent in response to
directed polls; however, a small number of payloads are sent in
response to random access polls.
The percentage of payloads that are delivered on the first transmission
= txPayloads10k / (B + C) = 43,153 / 45,879 = 94.1%
Similarly, the percentage of payloads that are not delivered on the first transmission but are
delivered on the second transmission
= txPayloads20k / (45,879 - 43,153) = 2,306 / 2,726 = 84.6%
The percentage of payloads that are not able to be delivered
= 29 /45,879 = 0.06%
Since there are no broadcast or control payloads, the calculation of the Retransmission Rate
is fairly straightforward:
Retransmission Rate
= (1 - desired payloads/actual payloads) x 100
= (1 - tx Data Payloads / txPayloads) x 100
= (1 - 44,153 / 49,101) x 100
= 10.1%
These calculations are displayed by the “stats summary” command.
11.5
EUM Receive Statistics
Perhaps the most important receive statistic is the Receive Signal Strength Indicator (RSSI),
which provides an indication of the receive signal strength in dBm.
NOTE: Since the EUM can receive packets that are destined for other
EUMs, the EUM receive statistics are not as useful as the CCU
receive statistics. They are useful when the EUM is the only EUM
172
APCD-LM043-8.0 (DRAFT C)
11: Monitoring the Network
that is active, which is seldom the case after more than one EUM
have been activated.
The statistic rxPktsDuplicate measures the number of times the CCU sends the same packet
of information more than one time. A high value of rxPktsDuplicate indicates that the
acknowledgements from the EUM are not being properly received at the CCU.
11.6
User Data
The total user data is recorded by the statistics Rx Data Payloads, Tx Data Payloads, Rx Data
Octets, and Tx Data Octets. These statistics could be viewed as billable data and allow you to
monitor total usage at the EUM level.
11.7
Logging CCU or EUM Statistics
The system log is an extremely powerful tool since it has accurate absolute time stamps and
can be downloaded very quickly using FTP. The system log has two roles:
•
To assist in troubleshooting unit and network problems. The MAC statistics for the
CCU and EUM are recorded hourly and are very useful, especially when an absolute
time reference is entered to coordinate the logs.
•
To monitor individual unit traffic after the fact, which is useful if any unit is in trouble. It
can also be helpful with billing information. By recording information to the log, events
of interest are less likely to be missed, as can happen with real-time monitoring.
The system log records every command you enter, either through the serial console port or
through a Telnet session, which can be useful when troubleshooting problems. The system log
also saves the statistics defined below at each recording period. Each statistic line is preceded
by the date/time stamp and the “statN” label, where “N” is the line number. If the statistics are
recorded every 15 minutes, then the system log can hold at least 36 hours worth of data.
Since not all counters are large numbers, the log can typically contain information for the last
2-3 days. The system logs can be downloaded during quiet hours to avoid affecting system
performance during peak periods. Downloading the logs every 2 days should ensure that all
statistics are retrieved for each unit.
To control system logging, connect to the device with Telnet and use the following commands:
•
stats log .  is the time interval in minutes between each
data sample to log. You may set the interval to any number of minutes between 1 and
65535. After entering this command, the CCU or EUM will begin logging statistics at
the specified interval. The default interval is 15 minutes.
•
stats log off stops logging statistics.
•
stats log now records the current statistics in the log without affecting the
statistics period or whether it is on or off.
•
stats log shows the logging interval.
APCD-LM043-8.0 (DRAFT C)
173
11: Monitoring the Network
•
sys log  [] displays a portion of the system log file.
NOTE: If statistics logging is enabled and you use the “statistics clear”
command, the current values are logged before the statistics are
cleared.
To Retrieve the System Log File
1. Connect to the unit with FTP.
2. Use the bin command to switch to binary image mode.
3. Use the get log  command to transfer the file.
NOTE: The  is a filename you assign to identify the file on
your computer. WaveRider recommends including the date and
time in the filename. If you do not specify any filename, the
received file will be named “log”.
4. Use the quit command to close the FTP session.
C:\TEMP>ftp 10.0.2.253
Connected to 10.0.2.253.
220 FTP server ready
User (10.0.2.253:(none)):
331 Password required
Password:
230 User logged in
ftp> bin
200 Type set to I, binary mode
ftp> get log 020808
200 Port set okay
150 Opening BINARY mode data connection
226 Transfer complete
ftp: 169939 bytes received in 0.28Seconds 606.92Kbytes/sec.
ftp> quit
221 Bye...see you later
C:\TEMP>
For more information about CCU and EUM statistics logging, refer to CCU and EUM System
Log Statistics on page 302.
11.8
CCU Air Table Statistics
The air table statistics are a useful tool for monitoring Tx/Rx data transfer rates on a particular
EUM. You can use it to isolate EUMs that may be using an unreasonably large portion of the
network. You can also use the air table statistics to generate usage billing reports for each
EUM.
The air table statistics:
174
APCD-LM043-8.0 (DRAFT C)
11: Monitoring the Network
11.9
•
provide accumulated octet/packet counts for each registered EUM. The Rx- and Txdirections are from the perspective of the CCU. In other words, Rx-Octets and RxPackets refers to data received by the CCU from the EUM; Tx-Octets and Tx-Packets
refers to data transmitted from the CCU to the EUM,
•
may be cleared by CCU reset or using the air flush command,
•
sorts entries by EUM IDs, and
•
if RADIUS accounting is enabled, the CCU RADIUS client—periodically and on
special events—sends RADIUS accounting packets to a RADIUS server for each
EUM authorized through RADIUS. (For example, this event occurs when an EUM is
removed from the registration table.)
CCU Radio Meter
The CCU radio meter is a very useful CLI tool for determining the system load. In addition, it
assists in monitoring grade of service violations. The radio meter displays the running average
of per second traffic and polling statistics for each grade of service.
The CCU radio meter
•
displays only the active grade of service levels since last CCU reset (for example, if
the CCU has Silver and BE grades of service, the radio meter displays entries only for
Silver Active/Inactive and BE Active/Inactive),
•
can specify the interval (in seconds) over which the average is made,
•
can generate graphs of Rx/Tx packets for the CCU channel,
•
provides broadcast rates for both forward traffic (such as CCU to EUM Tx traffic) and
reverse traffic.
Keep the following points in mind when using the CCU radio meter:
•
The Tx broadcasts should not exceed 10% of the total Tx traffic.
•
The reverse packet rate should be less than 15% of the total poll rate for the
broadcast traffic.
•
The Max IPS Violation monitoring indicates the number of “missed polls” within the
inter-poll space defined by the EUM's grade of service.
•
The Ideal IPS Violation indicates “below GOS” EUMs (in other words, the number of
times a particular grade of service has not been achieved).
APCD-LM043-8.0 (DRAFT C)
175
— This page is intentionally left blank —
12
Specialized Applications
The advanced capabilities of the LMS4000 900 MHz radio network modems can support a
variety of special applications.
12.1
EUM Thin Route
The EUM Thin Route configuration, in Figure 61, shows how to use an EUM as a thin route to
extend the reach of the LMS4000 900 MHz radio network to a small number of outlying EUMs.
End-user PC
Radio
Channel "A"
Standard
EUM
Radio
Channel "B"
Standard
EUM
End-user PC
Antenna
Antenna
CCU1
CAP1
Thin Route
EUM
Hub
CCU2
CAP2
Standard
EUM
End-user PC
End-user PC
Figure 61
Using an EUM for Thin Route
NOTE: This EUM Thin Route example uses Routed mode. You can also
use Switched Ethernet mode.
APCD-LM043-8.0 (DRAFT C)
177
12: Specialized Applications
In the above configuration, a backhaul is created between the local CCU1 (CAP1) and the
remote CCU2 (CAP2) by deploying an EUM (Thin Route EUM) from CAP1 in CAP2. The Thin
Route EUM will operate at the frequency of CCU1 and have CCU1 as its gateway.
CCU2 may be connected to the Ethernet port of the EUM either directly or through a switch.
Additional subscriber EUMs may then be deployed off CCU2.
To correctly route the traffic between CAP1 and CAP2, routes need to be added to the CAP1
router and CAP1 CCU1. The latter route is required to route the traffic to CCU2.
Traffic traversing from the CAP2 subscribers’ radio network will place additional load on CAP1
CCU1, reducing its available throughput. In order to improve the overall backhaul
performance, a special grade of service (Thin Route GOS) should be provisioned in CAP1
CCU1 and assigned to the Thin Route EUM.
12.2
EUM Backhaul
In some cases, it may be cost-effective to use an EUM as the backhaul link as an alternative to
a separate wired or wireless link to the CCU, as is illustrated in Figure 62.
Data path from end-user
modem to network
EUM
Antenna
EUM
Backhaul EUM
Figure 62
CCU3000
Using an EUM for Backhaul
The above configuration has one CCU located at a remote location and one EUM (Backhaul)
installed at a NAP or CAP. The CCU’s Ethernet port is unused and may be left unconnected,
or with appropriate routing it may be used for a co-located user PC. The Backhaul EUM’s
Ethernet would typically be connected to a router, switch, or a hub. The subscriber EUMs are
setup as normal.
The Backhaul EUM scenario creates an extended bridged network with Backhaul EUM, CCU,
and subscribers EUMs following the same IP scheme as the rest of the existing network.
The Max Customers setting in the Backhaul EUM applies to the number of hosts on the
Ethernet side of the Backhaul EUM, not to the number of customers served by the CCU.
WaveRider recommends setting Max Customers to 50.
To have a good backhaul performance it is important that the Backhaul EUM is positioned for
optimum RF reception (for example, on a tower).
178
APCD-LM043-8.0 (DRAFT C)
12: Specialized Applications
Traffic traversing from subscriber computers to the Backhaul EUM will use the radio link twice,
placing additional load on the Backhaul EUM. To alleviate potential performance bottlenecks,
a special grade of service (EUM Backhaul GOS) should be provisioned in the CCU used for
the backhaul configuration and assigned to the Backhaul EUM.
Traffic load considerations in the EUM Backhaul configuration imply that the CCU should
support approximately half the usual number of subscribers, with approximately the same
throughput as usual.
APCD-LM043-8.0 (DRAFT C)
179
— This page is intentionally left blank —
Appendix A
Specifications
This appendix lists the following specifications for the LMS4000 900 MHz Radio Network,
specifically the technical specifications for the CCU and EUM, configured for operation in the
FCC/IC RF regulatory domain:
•
Radio Specifications on page 181
•
Ethernet Interface Specifications on page 182
•
Power Supply Specifications on page 182
•
Environmental Specifications on page 182
Table 32 Radio Specifications
Maximum Number of Operational CCUs and
Orthogonal Channels
Maximum Number of EUMs per CCU
300
Maximum Address Table Size (CCU)
1051
Maximum Bridge Table Size
256
Minimum Channel Center Frequency
905 MHz
Maximum Channel Center Frequency
925 MHz
Channel Bandwidth
5.5 MHz
Center Frequency Spacing Increment
0.2 MHz (101 channels possible)
Minimum Separation Between Co-located
Channels
6.6 MHz
Maximum Co-located Channels
APCD-LM043-8.0 (DRAFT C)
181
Appendix A: Specifications
Co-located Channel Set Center
Frequencies (standard)
905 MHz, 911.6 MHz, 918.4 MHz, and 925
MHz
Note: Other frequencies can be used,
depending on site-specific considerations.
Contact WaveRider for more information.
Modulation Scheme
Based on DSSS (Direct-Sequence Spread
Spectrum) signals, modulated with CCK
(Complementary Code Keying), and Barkercoded BPSK (Binary Phase Shift Keying)
and QPSK (Quaternary Phase Shift Keying)
Receiver Sensitivity for BER < 10-5
Better than -86 dBm
Maximum Over-the-Air, Raw Data Rate
2.75 Mbps
Maximum Output Power
+26 dBm
Table 33 Ethernet Interface Specifications
CCU Physical Interface
10BaseT (Ethernet)
EUM Physical Interface
10BaseT (Ethernet)
Table 34 Power Supply Specifications
AC Input
110/230 ± 15% VAC, single phase
AC Input Frequency
50/60 ± 3 Hz
Maximum Input Current
0.2 A
Table 35 Environmental Specifications
182
Operating Temperature
0°C to +50°C, CCU
10°C to +40°C, EUM3000
0°C to +40°C, EUM3003
(10%-80% RH non-condensing)
Storage Temperature
-40°C to +70°C
APCD-LM043-8.0 (DRAFT C)
Appendix B
Factory Configuration
This appendix identifies the factory configuration settings for the CCU and EUM.
Table 36 CCU Factory Configuration
Parameter
Default Configuration
Console Prompt
The default console prompt is the station
(CCU) ID.
Deregistration Count
DHCP Relay
Disabled
Ethernet IP Address
192.168.10.250
Ethernet Netmask
24
255.255.255.0
ffffff00
Gateway IP Address
192.168.10.1
GOS Definitions
BE (0 - 384 kbps)
Bronze (0 - 1024 kbps)
Silver (128 - 256 kbps)
Gold (256 - 512 kbps)
Denied (0 kbps)
Note: The above data rates are based on
FTP transfers from a single EUM, using
maximum-sized packets.
GOS Default (Authorization Table)
BE (Best Effort)
Maximum Associations
75
Maximum Registered EUMs
300
Password
By default, the CCU has no password.
Press Enter at the password prompt to
enter a null password.
APCD-LM043-8.0 (DRAFT C)
183
Appendix B: Factory Configuration
Table 36 CCU Factory Configuration
Parameter
184
Default Configuration
Port Filters
137 (both)
138 (both)
139 (both)
445 (both)
1512 (both)
Protocol
Switched Ethernet Mode (“Switched”)
Radio
Enabled
Radio Frequency
9050 (905.0MHz)
Radio Power
+26 dBm (High)
RADIUS Period
60 (minutes)
SNMP Contact
WaveRider Communications Inc.
SNMP Location
www.waverider.com
SNMP Read Communities
public
SNMP Write Communities
private
SNMP Traps
None entered
SNTP Client Enabled
No
SNTP Client Resynchronization Period
3600 seconds
SNTP Client Retry Period
30 seconds
SNTP Relay Enabled
Yes
SNTP Relay Send Time on Boot
Yes
SNTP Relay Send Time on EUM
Registration
Yes
SNTP Servers
132.246.168.148 (time.nrc.ca)
140.162.8.3 (ntp.cmr.gov)
136.159.2.1 (ntp.cpsc.ucalgary.ca)
192.5.5.250 (clock.isc.org)
Statistics Log Interval
15 minutes
APCD-LM043-8.0 (DRAFT C)
Appendix B: Factory Configuration
To reset the CCU to factory default
60:03:3a> fi dir
Directory listing:
SA1110.EXE
475764
BASIC.CFG
1992
PORT.CFG
6240
SNTP.CFG
156
ROUTE.CFG
2896
AUTHDB.CFG
3496
DHCP.CFG
896
SA1110.BAK
475764
60:03:3a> fil del
file deleted
60:03:3a> fil del
file deleted
60:03:3a> fil del
file deleted
60:03:3a> fil del
file deleted
60:03:3a> fil del
file deleted
60:03:3a> fil del
file deleted
60:03:3a> reset
basic.cfg
port.cfg
sntp.cfg
route.cfg
authdb.cfg
dhcp.cfg
rebooting CCU ...
(... Power On Self Test ...)
WaveRider Communications, Inc. LMS3000
Password:
60:03:3a> port add 137 both
60:03:3a> port add 138 both
60:03:3a> port add 139 both
60:03:3a> port add 445 both
60:03:3a> port add 1512 both
60:03:3a>
60:03:3a> save
Basic Config saved
Port Filter Config saved
sntp cfg file saved
Route Config saved
Authorization Database saved
DHCP Server Config saved
60:03:3a>
60:03:3a> port
PORT FILTERS
Port
Filter
--------------------------------445
both
137
both
138
both
139
both
1512
both
---------------------------------60:03:3a>
APCD-LM043-8.0 (DRAFT C)
185
Appendix B: Factory Configuration
Table 37 EUM Factory Configuration
Parameter
186
Default Configuration
Console Prompt
The default console prompt is the station
(EUM) ID.
Ethernet IP Address
192.168.10.250
Ethernet Netmask
24
255.255.255.0
ffffff00
Gateway IP Address
192.168.10.1
Maximum Number of Customers
Password
By default, the EUM has no password.
Press Enter at the password prompt to
enter a null password.
Port Filters
137 (both)
138 (both)
139 (both)
445 (both)
1512 (both)
Radio
Enabled
Radio Frequency
9050 (905.0MHz)
Radio Power
+26 dBm (High)
SNMP Contact
WaveRider Communications Ltd.
SNMP Location
www.waverider.com
SNMP Read Communities
public
SNMP Write Communities
private
SNMP Traps
None entered
SNTP Client (listen only) Enabled
Yes
APCD-LM043-8.0 (DRAFT C)
Appendix B: Factory Configuration
To reset the EUM to factory default
60:ff:fe> fil dir
Directory listing:
BASIC.CFG
1992
SNTP.CFG
156
SA1110.EXE
475764
PORT.CFG
6240
SA1110.BAK
475764
60:ff:fe> fil del basic.cfg
file deleted
60:ff:fe> fil del sntp.cfg
file deleted
60:ff:fe> fil del port.cfg
file deleted
60:ff:fe> reset
rebooting EUM ...
(... Power On Self Test ...)
WaveRider Communications, Inc. LMS3000
Password:
60:ff:fe> port add 137 both
60:ff:fe> port add 138 both
60:ff:fe> port add 139 both
60:ff:fe> port add 445 both
60:ff:fe> port add 1512 both
60:ff:fe>
60:ff:fe> save
Basic Config saved
Port Filter Config saved
sntp cfg file saved
60:ff:fe>
60:ff:fe> port
PORT FILTERS
Port
Filter
--------------------------------445
both
137
both
138
both
139
both
1512
both
---------------------------------60:03:3a>
APCD-LM043-8.0 (DRAFT C)
187
— This page is intentionally left blank —
Appendix C
Command-Line Syntax
This appendix describes the various LMS4000 commands and syntax, and consists of the
following sections:
•
Command-line Syntax Conventions and Shortcuts on page 189
•
CCU Command-line Syntax on page 191
•
EUM Command-line Syntax on page 204
NOTE: The help command on the CCU or EUM may display additional
commands that are not listed in the following tables. WaveRider
recommends that you use only commands listed in this Appendix.
All commands typed at the command-line interface are recorded verbatim in the system log.
For instructions on accessing the command-line interface, refer to Access Interface on page
221.
Command-line Syntax Conventions and Shortcuts
Table 38 shows the typographical conventions used to represent command-line syntax. Table
39 provides a list of shortcuts and methods to get help on commands. To execute a command,
type the command and press Enter.
Table 38 Command-Line Syntax Conventions
Convention
monospaced
font
Use
Indicates that you must type the text.
APCD-LM043-8.0 (DRAFT C)
Examples
ip route
189
Appendix C: Command-Line Syntax
Convention
Use
Examples
Enter
Bold face type indicates a keyboard key
press. A plus sign (+) indicates key
combinations. For example, for Ctrl+U,
press and hold down the Ctrl key, then
press the U key.
Enter
Esc
Ctrl+U

Specifies a variable name or other
information that you must replace with a
real name or value.
ip address ethernet

bold
characters
Indicates the shortcut characters for a
command.
ip ethernet can also be
typed as i e
Separates two mutually exclusive choices
in a command. Type one choice and do
not type the vertical bar.
exit|quit
Encloses a range of values from which
you can choose a value.
ip ethernet

(0-32)
( )
Table 39 Command-Line Shortcuts and Getting Help
Type
190
To do this...
↑↓
Scroll up and down through last 10 commands.
To display the names of the root commands.
 ?
To display the syntax for a command.
help
To display all the commands, their subcommands and
the parameters and options for each command.
help 
To display the parameters and options for the
command.
ESC
To cancel the command you are typing.
APCD-LM043-8.0 (DRAFT C)
Appendix C: Command-Line Syntax
CCU Command-line Syntax
Table 40 CCU Command-Line Syntax
NOTE: In Table 40, commands that are noted with a √ in the right-hand
column will not take effect until you have rebooted the CCU.
Command Syntax (CCU)
Command Description
address
Displays the Address Table.
address delete|remove 
Removes an EUM ID from the Address
Table.
•  is the EUM ID, in the form
XX:XX:XX.
address flush
Removes all entries from the Address
Table.
air
Displays the EUM Registration Table.
air associations
Displays the maximum association count.
air associations 
Changes the maximum number of
associations.
•  must be between 1 and 75.
air delete 
Deletes an EUM from the Registration
Table.
•  is the EUM ID, formatted in
hexadecimal XX:XX:XX.
air dereg
Displays the deregistration count.
air dereg 
Changes the deregistration count.
•  is the deregistration count,
from 1 to 254.
air fdereg 
Forces deregistration of an EUM.
•  is the EUM ID, in the form
XX:XX:XX.
air flush
Removes all entries from the EUM
Registration Table.
arp
Displays the ARP Table.
APCD-LM043-8.0 (DRAFT C)
191
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
arp add 
 [flags]
Adds an entry to the ARP Table.
•  is the IP
address of the new entry.
•  is the MAC
address, in hexadecimal format.
• [flags] is always set to 4, meaning
the entry is permanent and does not
time out, as long as the CCU or EUM is
ON.
arp delete 
Deletes an entry from the ARP Table:
•  is the IP
address of the entry being deleted.
arp flush
Removes all entries from the ARP Table.
arp map
Displays the ARP Map Table.
arp map
|
Maps an IP address  to a
MAC address, EUM ID, grade of service,
etc.
•  is the IP
address of the host to display.
•  is the EUMID of the EUM to
display.
auth
Displays the EUM Authorization Table.
auth add | edit  
Adds an EUM to the Authorization Table.
•  is the EUM ID, in the form
XX:XX:XX.
•  is the EUM grade of service.
Available GOSs are gold, silver, bronze, be
(best effort), and denied.
auth default 
Sets the default GOS, which is the GOS
assigned to an EUM upon registration.
•  is the default grade of service.
Available GOSs are gold, silver, bronze, be
(best effort), and denied.
NOTE: After changing the default GOS,
execute the “air flush” and “arp
flush” commands for the default
GOS to apply to EUMs that are
already registered.
auth delete 
192
The EUM will receive the default grade of
service.
•  is the EUM ID, in the form
XX:XX:XX.
APCD-LM043-8.0 (DRAFT C)
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
auth gos 
Displays the GOS definitions.
•  is the default grade of service.
Available GOSs are gold, silver, bronze, be
(best effort), and broadcast.
auth radius
Displays the RADIUS client configuration.
auth radius accounting enable
Enable RADIUS accounting.
NOTE: RADIUS authorization must be
enabled before you can enable RADIUS
accounting.
auth radius accounting disable
Disable RADIUS accounting.
auth radius disable
Disables RADIUS authorization and
accounting.
auth radius enable
Enables RADIUS authorization.
auth radius period 
Sets the period between RADIUS requests
for each EUM.
•  is the number of minutes
between RADIUS requests. The period
must be between 5 and 20000 minutes.
auth radius primary
|none
Sets the primary RADIUS server IP address
and password. The CCU prompts for
password entry.
•  is the primary
RADIUS server IP address.
auth radius secondary
|none
Sets the secondary RADIUS server IP
address and password. The CCU prompts
for password entry.
•  is the secondary
RADIUS server IP address.
bcf
Displays the basic configuration file (BCF).
bridge | customer
Displays the bridge table.
bridge | customer flush
Removes all entries from the bridge table.
bridge | customer maximum 
Sets the maximum number of customers.
•  is the maximum, which must be
from 1 to 50.
dhcp
Displays status of CCU DHCP Relay, either
enabled or disable.
dhcp disable
Disables DHCP relay.
dhcp enable
Enables DHCP relay.
APCD-LM043-8.0 (DRAFT C)
193
Appendix C: Command-Line Syntax
Command Syntax (CCU)
194
Command Description
dhcp relay
Displays the CCU DHCP relay status and
contents of the DHCP Server Table.
dhcp relay add 

Adds the DHCP server IP address.
•  is the IP
address of the DHCP server.
•  is the subnet mask of the
DHCP server (0-32).
dhcp relay delete
 
Deletes the DHCP server IP address.
•  is the IP
address of the DHCP server.
•  is the subnet mask of the
DHCP server (0-32).
dhcp relay flush
Removes all DHCP server IP addresses.
exit|quit
Exits the current console session and
returns to the password prompt.
file copy | cp 

Copies a file.
•  is the name of the source
file.
•  is the name of the
destination file.
file delete 
Deletes a file.
•  is the name of the file you
want to delete.
file dir | ls
Lists the name, size, and cyclic redundancy
check (CRC) for each file.
APCD-LM043-8.0 (DRAFT C)
Appendix C: Command-Line Syntax
Command Syntax (CCU)
file get
|
 [|_]
 
Command Description
NOTE: If you enter only the IP address or
EUM ID, then  defaults to
“buywavc”,  defaults to “null”, and
 defaults to “null”—the link
speed test.
Retrieves a file from a remote location.
•  is the IP
address of the computer from which
you are retrieving the file.
NOTE: You can use  in
place of the IP address for EUMs or
CCUs.
•  is the user name required
to log on to the remote computer.
Defaults to “buywavc” if left blank.
•  is the password to log on
to the remote computer. If you omit the
password argument, you will be
prompted for the password, which will
be asterisked out and not recorded in
the system log. Use _ when the
password is blank.
•  is the path and filename of
the file that is being retrieved from the
remote computer. Defaults to “null” if
left blank.
•  is the path and
filename to which the file will be copied.
Defaults to “null” if left blank.
file mkboot | makeboot

Makes a new boot file. Use this command
with caution.
•  is the name of the new
boot file.
file rename | rn  
Renames a file.
•  is the old file name.
•  is the new file name.
help
Displays the console command structure.
ip
Displays the CCU IP address assignments.
ip ethernet
Displays the Ethernet IP address of the
CCU.
NOTE: If the CCU is in Switched Ethernet
mode or Through Only mode, this command
displays the CCU IP address.
APCD-LM043-8.0 (DRAFT C)
195
Appendix C: Command-Line Syntax
Command Syntax (CCU)
196
Command Description
ip ethernet 

Changes the Ethernet IP address of the
CCU.
•  is the new
Ethernet IP address of the CCU.
•  is the subnet mask of the
CCU Ethernet address (0-32).
NOTE: If the CCU is in Switched Ethernet
mode or Through Only mode, this command
sets the CCU IP address.
ip gateway
Displays the IP address of the router
through which the CCU connects to the
Internet.
ip gateway 
Defines the router through which the CCU
connects to the Internet.
•  is the new
Ethernet IP address of the router.
ip radio
Displays the radio IP address of the CCU.
NOTE: If the CCU is in Switched Ethernet
mode or Through Only mode, this command
displays the CCU IP address.
ip radio 

Changes the radio IP address of the CCU.
•  is the new IP
address of the CCU radio.
•  is the subnet mask of the
CCU radio address (0-32).
NOTE: If the CCU is in Switched Ethernet
mode or Through Only mode, this command
sets the CCU IP address.
password
Initiates the process for changing the
system password.
pcf
Displays the permanent configuration file
(PCF).
APCD-LM043-8.0 (DRAFT C)
√
√
√
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
ping |
 
Sends ICMP echo requests to a remote
host.
•  is the IP
address of the remote host.
•  is the EUMID (in the form
XX:XX:XX) of an EUM or CCU to ping.
•  is an optional parameter
defining the ping packet size in bytes.
The default length is 64 bytes, and the
maximum length is 1460 bytes.
•  is an optional parameter
defining the number of milliseconds
between pings. The interval may be
from 100 to 4000 milliseconds, and the
default is 490 milliseconds.
Press any key to halt.
port
Displays the TCP/UDP port filters.
port add 
tcp|udp|both
Adds or modifies a port filter.
•  is the number of the
port to be filtered.
• One of tcp, udp, or both is selected
to filter TCP or UDP messages, or both.
port delete 
Deletes a port filter.
•  is the port to be
deleted.
port flush
Deletes all port filters.
protocol
Displays the protocol mode.
protocol routed|switched|through
Changes the protocol mode.
radio
Displays the radio attributes of the CCU.
APCD-LM043-8.0 (DRAFT C)
√
197
Appendix C: Command-Line Syntax
Command Syntax (CCU)
198
Command Description
radio analyse 
  
Starts a spectral analysis.
•  is the number of RSSI and
noise floor samples taken at each
frequency. The default value is 200.
•  is the step size between
sample points. The default is 2
(200kHz), which is also the minimum
step size allowed. The maximum
interval is 200 (20MHz).
•  is the lowest frequency
sampled, in 100’s of kHz. The default is
9000 (900.0MHz), which is also the
minimum allowed.
•  is the upper boundary on
frequencies sampled, in 100’s of kHz.
The default is 9300 (930.0MHz), which
is also the maximum allowed.
radio analyse last
This command will redisplay the results of
the last spectral analysis that was
performed.
radio comment 
Adds a comment to both the tabular and the
graphical versions of the spectral analysis
output. The character string that you enter in
 will be displayed below the date
and time line. Up to 50 characters are
allowed.
radio disable
Disables the radio transmitter/receiver. The
radio is re-enabled automatically after
rebooting the unit.
NOTE: When using this command, ensure
that an Ethernet or serial port connection to
the CCU is available; otherwise, you will be
unable to re-enable the radio.
radio enable
Enables the radio transmitter/receiver.
radio frequency
Displays the CCU radio frequency in tenths
of a MHz; for example, 905.0 MHz is
displayed as 9050.
radio frequency 
Changes the CCU radio frequency.
•  is the new radio
frequency, in tenths of a MHz. (For
example, 905.0 MHz is entered as
9050.) The radio frequency must be
within the range of 9050 to 9250. The
frequency may use only 0.2 MHz
increments and may use even values
only.
APCD-LM043-8.0 (DRAFT C)
√
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
radio meter
Displays traffic statistics and polling
statistics totals for each grade of service.
radio meter 
Displays running average per second traffic
and polling statistics for each grade of
service.
•  in seconds is the time
over which the average is made. Press
any key to halt.
radio rf high|low|
Displays or sets the power of the CCU radio,
where programming the value to:
•
high will set the transmit power
output to +26 dBm,
•
low will set the transmit power to
+15 dBm, and
•
, where , an
integer between 15 and 26
inclusive, will set the transmit power
to + dBm.
NOTE: The CCU RF level should normally
be set to high.
radio rssi
Displays continuous RSSI readings. Press
any key to halt.
rcf
Displays the contents of the route
configuration file (RCF).
reset|reboot
Reboots the CCU.
route
Displays the routing table of the CCU.
route add 
 
Adds a static route to the routing table.
•  is the Ethernet
IP address of the network being added
to the routing table.
•  is the Ethernet
IP address of the gateway through
which the destination is reached.
•  is the subnet mask of the
destination network(0-32).
APCD-LM043-8.0 (DRAFT C)
199
Appendix C: Command-Line Syntax
Command Syntax (CCU)
200
Command Description
route delete 
 
Deletes a route from the routing table.
•  is the Ethernet
IP address of the network being
removed from the routing table.
•  is the Ethernet
IP address of the gateway through
which the destination device can be
reached.
•  is the subnet mask for the
destination network (0-32).
route stats
Displays the routing statistics.
save | commit
Saves configuration changes.
snmp
Displays the CCU SNMP information.
snmp community
Displays the SNMP communities.
snmp community add 

Adds an SNMP community.
•  is the name of the
SNMP community being added, from 131 characters in length.
• Enter  or  to indicate
the type of the community being added.
snmp community delete

Deletes an SNMP community.
•  is the name of the
SNMP community being deleted.
snmp contact
Displays the SNMP system contact.
snmp contact 
Changes the SNMP system contact.
•  is the name of the contact
(WISP, for example), from 1-80
characters in length.
snmp interface
Displays the SNMP interface MIBs.
snmp location
Displays the SNMP system location.
snmp location 
Changes the SNMP system location.
•  is the location of the
CCU, from 1-80 characters in length.
snmp trap
Displays the SNMP Trap Server Table.
snmp trap add 

Adds a trap server community.
•  is the Ethernet
IP address of the trap server.
•  is the community name
for the trap server, from 1-63
characters in length.
APCD-LM043-8.0 (DRAFT C)
√
√
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
snmp trap delete
 
Deletes a trap server community.
•  is the Ethernet
IP address of the trap server.
•  is the community name
for the trap server being deleted, from
1-63 characters in length.
stats
Displays the statistics for all drivers and
network protocols.
stats auth
Displays authorization/RADIUS statistics.
stats clear
Clears the statistics for all drivers.
stats ethernet
Displays Ethernet statistics.
stats log |OFF|NOW
Displays or sets statistics logging interval in
minutes.
•  is the time interval in minutes
of statistics logging, from 1 to 65535
minutes; setting the interval also turns
logging on.
• OFF turns statistics logging off.
• NOW prints the current statistics to the
log without affecting the period or
turning logging on or off.
stats mac
Displays MAC driver statistics.
stats net
Displays network protocol statistics.
stats net icmp
Displays ICMP statistics.
stats net ip
Displays IP statistics.
stats net tcp
Displays TCP statistics.
stats net udp
Displays UDP statistics.
stats radio
Displays radio driver statistics.
stats rp | routing
Displays routing protocol statistics.
stats summary
Displays a summary of the Atmel MAC
statistics.
sys log  
Displays the modem log file.
•  is the number of characters
to print from the log file.
•  is the character offset;
default is 0.
sys mac
Displays the Atmel MAC log.
sys memory
Displays memory allocation information.
APCD-LM043-8.0 (DRAFT C)
201
Appendix C: Command-Line Syntax
Command Syntax (CCU)
202
Command Description
sys prompt 
Changes the system prompt.
•  is the new prompt,
from 1-20 characters in length.
You cannot use the “>” character. It will be
appended to the prompt automatically.
sys ss
Displays the system status file, which
includes POST results, file status, I/O
connections, and system statistics.
sys tasks
Displays the task list.
sys uptime
Displays the length of time the system has
been running.
NOTE: It rolls over to zero after about 8
days.
sys version
Displays software version information.
sys wlog 
Writes text to the log file. This command is
useful for adding information to the log for
subsequent analysis:
•  may be from 1-246 characters
in length.
telnet
|
Begins a telnet session to a destination
address.
•  is the IP address of
a host, such as an EUM, accessible
from this CCU, in the format
aaa.bbb.ccc.ddd.
•  is the EUMID (in the form
XX:XX:XX) of an EUM or CCU to
connect to.
time
Displays the system calendar clock time.
time client
Manages the SNTP client and displays a list
of NTP servers.
time client disable
Disables the SNTP client.
time client enable
Enables the SNTP client.
time print
Prints the SNTP configuration and NTP
server list.
time relay destination
[broadcast|]
Relays NTP messages to an EUM network
or to an individual EUM.
•  is the multicast
address, SNTP client network address,
EUM IP address.
APCD-LM043-8.0 (DRAFT C)
Appendix C: Command-Line Syntax
Command Syntax (CCU)
Command Description
time relay disable
Disables SNTP relay over the radio
interface.
time relay disable boot
Disables CCU time updates when the CCU
boots.
time relay disable registration
Disables EUM time updates when an EUM
registers with a CCU.
time relay enable
Enables SNTP relay over the radio
interface.
time relay period 
Sets the time relay resynchronization
period, in seconds.
• Time period may be from 0 to 100000
seconds.
• Enter 0 to force immediate
resynchronization.
The default time relay period is 3600
seconds.
time server
Manages NTP servers.
time server add

Adds or modifies an NTP server.
time server default
Restores default NTP servers.
time server delete

Deletes an NTP server.
time server flush
Deletes all NTP servers.
time set
Source Exif Data: 
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Modify Date                     : 2003:11:11 11:17:01-05:00
Create Date                     : 2003:11:11 11:16:37-05:00
Title                           : LMS4000_900_MHz_Guide.book
Author                          : Administrator
Creator                         : FrameMaker 6.0
Producer                        : Acrobat Distiller 5.0.5 (Windows)
Page Count                      : 185
Mod Date                        : 2003:11:11 11:17:01-05:00
Creation Date                   : 2003:11:11 11:16:37-05:00
Metadata Date                   : 2003:11:11 11:17:01-05:00
EXIF Metadata provided by EXIF.tools
FCC ID Filing: OOX-EUM3004

Navigation menu