E3Switch WAN Monitor Owner's manual

DS3/E3 WAN Monitor with
Ethernet Output for HDLC/PPP
Applications V .4
September 14th, 2011
Operating Information

Legal Preface:
COPYRIGHT & TRADEMARKS
Copyright © 2011 E3Swit h LLC. All Rights Reserved.
All other produ t names mentioned in this manual may be trademarks or registered trademarks of their
respe tive ompanies.
LIMITED WARRANTY
E3Swit h LLC (E3Swit h) guarantees that every unit is free from physi al defe ts in material and
workmanship under normal use for one year from the date of pur hase, when used within the limits set forth
in the Spe ifi ations se tion of this User Guide. If the produ t proves defe tive during the warranty period,
onta t E3Swit h Te hni al Support in order to obtain a return authorization number. When returning a
produ t from outside of the United States of Ameri a, learly state “NOT A SALE. RETURNED FOR
REPAIR” on the ommer ial invoi e; and failing to do so, the ustomer will be responsible for imposed
duties and taxes. All ustomers are responsible for shipping and handling harges for returned items.
IN NO EVENT SHALL E3SWITCH'S LIABILITY EXCEED THE PRICE PAID FOR THE PRODUCT
FROM DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) RESULTING FROM THE
USE OF THE PRODUCT OR ITS DOCUMENTATION, EVEN IF E3SWITCH HAS BEEN ADVISED
OF, KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. E3Swit h
makes no warranty or representation, expressed, implied, or statutory, with respe t to its produ ts or the
ontents or use of this do umentation and spe ifi ally dis laims its quality, performan e, mer hantability, or
fitness for any parti ular purpose. E3Swit h reserves the right to revise or update its produ ts or
do umentation without obligation to notify any individual or entity. Please dire t all inquiries to:
E3Switch LLC
80 Coronado Ave
San Carlos, CA 94070
U.S.A.
http://www.ds3switch.com, support@ds3switch.com
TEL: +1-650-241-9941
FCC STATEMENT
This devi e omplies with Part 15 of the FCC Rules. Operation is subje t to the following two onditions:
1. This devi e may not ause harmful interferen e.
2. This devi e must a ept any interferen e re eived, in luding interferen e that may ause
undesired operation.
Note: This equipment has been tested and found to omply with the limits for a Class A digital devi e,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable prote tion against
harmful interferen e when the equipment is operated in a ommer ial environment. This equipment
generates, uses, and an radiate radio frequen y energy, and if it is not installed and used in a ordan e with
the instru tion manual, it may ause harmful interferen e to radio ommuni ations. Operation of this
equipment in a residential area is likely to ause harmful interferen e, in whi h ase the user will be
required to orre t the interferen e at his own expense.
INDUSTRY CANADA NOTICE
This digital apparatus does not ex eed the Class A limits for radio noise emissions from digital apparatus
set out in the Radio Interferen e Regulations of the Canadian Department of Communi ations.
Le present appareil numerique n'emet pas de bruits radioele triques depassant les limites appli ables aux
appareils numeriques de la lass A pres rites dans le Reglement sur le brouillage radioele trique edi te par
le ministere des Communi ations du Canada
EUROPEAN UNION (EU) STATEMENT
This produ t is in onformity with the prote tion requirements of EU Coun il Dire tive 89/336/EEC on the
approximation of the laws of the Member States relating to ele tromagneti ompatibility. The
manufa turer annot a ept responsibility for any failure to satisfy the prote tion requirements resulting
from a non-re ommended modifi ation of the produ t.
2

This produ t has been tested and found to omply with the limits for Class A Information Te hnology
Equipment a ording to CISPR 22/European Standard EN 55022. The limits for Class A equipment were
derived for ommer ial and industrial environments to provide reasonable prote tion against interferen e
with li ensed ommuni ation equipment.
Attention:
This is a Class A produ t. In a domesti environment this produ t may ause radio interferen e in whi h
ase the user may be required to take adequate measures.
International Ele trote hni al Commission (IEC) Statement
3

TABLE OF CONTENTS
CHAPTER 1: DESCRIPTION AND REQUIREMENTS ..................................................................................................... 6
CHAPTER 2: QUICK SET-UP ................................................................................................................................. 6
CHAPTER 3: FRONT PANEL .................................................................................................................................. 8
FRONT PANEL INDICATORS ...............................................................................................................................8
CHAPTER 4: REMOTE MANAGEMENT HTTP AND SNMP ..................................................................................... 8
UNIT'S IP/MAC ADDRESS ...............................................................................................................................8
Automati Link-Lo al IP Address.........................................................................................................9
Initial Numeri IP Address....................................................................................................................9
Unknown IP Address Re overy............................................................................................................9
MANAGEMENT PASSWORDS ...............................................................................................................................9
SECURITY .....................................................................................................................................................10
HTTP Interfa e Se urity.....................................................................................................................10
SNMP Se urity....................................................................................................................................10
HTTP MANAGEMENT ..................................................................................................................................10
Event Log File.....................................................................................................................................11
Resetting..............................................................................................................................................11
SNMP ........................................................................................................................................................11
UPGRADING FIRMWARE ..................................................................................................................................11
FEATURE ACTIVATION/UPGRADE .....................................................................................................................11
CHAPTER : OPERATING MODES AND CONFIGURATION ........................................................................................ 12
TELECOM .....................................................................................................................................................12
Cir uit Clo k Speed............................................................................................................................12
DS3 Cir uit ID PMDL........................................................................................................................12
PORT TO PORT PACKET FLOW .........................................................................................................................12
LAN-to-LAN.......................................................................................................................................12
Loopba k.............................................................................................................................................12
LAN PORT SETTINGS ....................................................................................................................................12
LAN Port Speed..................................................................................................................................13
Autonegotiation Problems...................................................................................................................13
SFP Se ond LAN Port........................................................................................................................13
Dedi ated Management/Data LAN Ports............................................................................................13
VLAN ........................................................................................................................................................14
CHAPTER 6: INTEROPERABILITY ......................................................................................................................... 14
LAN ..........................................................................................................................................................14
Autonegotiation problems...................................................................................................................14
SFP LAN Port 1..................................................................................................................................14
Pause Frames.......................................................................................................................................14
TELECOM .....................................................................................................................................................14
CHAPTER 7: TELECOM CONNECTIONS ................................................................................................................. 1
FRAMING AND PHYSICAL LINK ........................................................................................................................15
TELECOM CABLING ........................................................................................................................................15
CHAPTER 8: LAN CONNECTIONS AND PERFORMANCE ......................................................................................... 1
LAN PORTS ................................................................................................................................................15
AUTONEGOTIATION ........................................................................................................................................15
LAN CABLING .............................................................................................................................................16
CHAPTER 9: LAN PACKET FORMAT FOR WAN DATA ENCAPSULATION .............................................................. 16
HEADER FORMAT FOR WAN DATA ENCAPSULATION .........................................................................................16
MTU ..........................................................................................................................................................16
TRANSPORT LAYER ........................................................................................................................................16
CHAPTER 10: TROUBLESHOOTING ....................................................................................................................... 16
GENERAL .....................................................................................................................................................16
4

PERFORMANCE ..............................................................................................................................................17
INTEROPERABILITY .........................................................................................................................................17
PINGING .......................................................................................................................................................17
STEP-BY-STEP DIAGNOSIS ..............................................................................................................................17
CHAPTER 11: THIRD PARTY COPYRIGHT NOTICES .............................................................................................. 18
ECOS LICENSE ..............................................................................................................................................18
THE FREEBSD COPYRIGHT ...........................................................................................................................18
THE NET-SNMP COPYRIGHT ........................................................................................................................18
THE APACHE LICENSE ...................................................................................................................................20
THE SHA2 COPYRIGHT .................................................................................................................................21
THE BZIP2 LICENSE ....................................................................................................................................21
THE ATHTTPD LICENSE ..............................................................................................................................21
CHAPTER 12: TECHNICAL SPECIFICATIONS AND STANDARDS ................................................................................. 22
5

Chapter 1: Des ription and Requirements
Chapter 1: Description and Re uirements
The E3Swit h WAN Monitor des ribed herein allows HDLC/PPP pa kets on a T3/DS3/E3 WAN to be
easily monitored/re orded via output to an Ethernet port. Inline apability alleviates the ne essity for
additional WAN tap-hardware. Dual WAN inputs allow monitoring of WAN traffi in ea h dire tion.
Fanless operation and extremely low part- ount design allows use with greater reliability and in harsh
environments. All units are ra k mountable. NEBS Level 3 multi ard hassis with redundant power are
available.
Single or dual LAN output is available in a variety of RJ45 or SFP opper or opti al formats at either
100Mbit or GbE/GigE rates depending upon software options pur hased. Jumbo 9600-byte frame size is
available. If pur hased, the se ond LAN port is available for out-of-band management. An appropriate
SFP trans eiver must be supplied if the se ond SFP LAN port is to be used.
Management fun tions in lude both omprehensive SNMP statisti s with link up/down and DS3 FEAC
notifi ations as well as one- li k HTTP, user-friendly, olor- oded monitoring of link operational status and
bit-error rate. Both HTTP and SNMP management of the Monitor is possible either in-band through the
same LAN port as data being re orded or out-of-band if the software option to enable the se ond LAN port
has been pur hased.
The WAN ir uit being monitored may ontain CRC-16/32 or no CRC en oding. The WAN ir uit may be
framed or unframed, but must ontain no T1/E1 hannels (un hannelized). X43 s ramble de oding is
available..
LAN output is typi ally sent to a re ording devi e. LAN pa ket format is spe ified by the user at the layer-
2 level. MAC header, VLAN, Ethertype, MPLS and pseudowire ontrol word are all manually spe ified in
the unit's onfiguration settings.
For ease of installation, the Monitor does not require a onfiguration setup and will typi ally work
immediately upon onne tion of LAN and tele om ables. Some modifi ation of default IP management
addresses or header output for data re ording would typi ally be desired.
The hot-swappable Monitor ard may be pur hased in standalone or multi- ard hassis and draws a minimal
6 watts of power. Standalone, single units ship in high-reliability, fan-free 1U hassis with ra kmount
bra kets and are available in a 100-240VAC or a ±35-75 volt DC models. NEBS-III, redundant-power
multi ard hassis are available in 6-slot/1U and 20-slot/3U versions.
Chapter 2: Quick Set-up
Atta h the WAN Monitor to a power sour e. The front panel lights should illuminate. Green is normal;
orange indi ates an error.
Depending upon the LAN options pur hased, HTTP/SNMP management of the unit may be through either
RJ-45 LAN Port 2 or through the SFP LAN port. Likewise, WAN data to be re orded may be output
through either LAN port. These LAN port assignments are found in the HTTP settings web s reen of the
unit. Typi ally, the default onfiguration has the RJ-45 port assigned to the data re ording devi e and the
management interfa e through the SFP port if pur hased or the same RJ-45 port if not.
Atta h an Ethernet UTP5 able from your LAN equipment to the desired LAN port. The Monitor an
perform automati MDIX ross-over vs. straight-through able adaptation. The monitor's LAN light will
hange from orange to green if a properly negotiated link has been established. The network equipment
attached to the LAN port of the Monitor should be set for autonegotiation mode in order to allow the
Monitor to negotiate a 100Mbit full-duplex connection. Disabling autonegotiation or using old LAN
6

Chapter 2: Qui k Set-up
equipment may result in the atta hed LAN equipment onfiguring to half-duplex mode, resulting in CRC
errors and pa ket loss. Refer to the interoperability se tion of this do ument for more information
Use only 75-ohm oaxial ables to atta h the WAN Monitor to the DS3/E3 ir uit. The monitor is atta hed
either inline with ea h WAN ir uit able or, alternatively, to a WAN tap. For inline use, the WAN able
in one dire tion should be atta hed to the “In” WAN Port 1 and ontinues to the remote lo ation via the
“Out” WAN Port 1. The other ir uit dire tion omes to the “In” WAN Port 2 from the remote lo ation,
and pro eeds via the “Out” WAN Port 2 to the the lo al equipment. For use with a WAN tap, the “Out”
ports are not utilized and may be left open.
On e the monitor is re eiving a valid TDM signal without alarms, the DS3/E3 Port LED will hange from
orange to green.
Refer to the management hapter of this manual if HTTP or SNMP operating statisti s are desired or to
hange the default administrator password or administrative onta t/lo ation information.
Further HTTP management of the monitor via LAN is required in the following situations:
●if using long (>68m) DS3 oaxial ables
●to set CRC and s rambling to mat h the WAN ir uit being monitored
●to hange the default administrator password. This is suggested, as onfiguration annot be
modified after 5 minutes of any power y le if the default password has not been hanged
●to hange the management IP address of the unit
●to set detailed LAN pa ket header format for pa kets from the WAN
There is no further onfiguration or setup required for the Monitor.
7

Chapter 3: Front Panel
Chapter 3: Front Panel
Front Panel Indicators
All Indicators: Green indicates normal operation.
Orange indicates an error condition.
Black indicates a disabled port.
DS3/E3 1/2: Green if the unit is receiving a valid WAN signal with no alarm conditions.
Flashes black each time a packet is received on this port
Orange steady indicates loss of the incoming WAN AMI signal.
Flashes orange/green if incoming signal exists, but an alarm condition is being received.
BER: Green if OK.
Orange flash for each BPV bit error.
Orange steady for absence of DS3/E3 receive signal, loss of frame lock onto receive bit-stream,
drive-level fault on transmit cable, or excessive receive bit errors.
Note: In a dual DS3/E3 unit, the BER will reflect the status of the operational link if one fails.
LAN1/2: Green when a properly negotiated 100/1000BaseTX Full-Duplex or SFP LAN connection exists.
Flashes black each time a packet is received on this port.
Orange indicates no valid connection.
Chapter 4: Remote Management HTTP and SNMP
Monitors ontain both an HTTP management interfa e, whi h may be a essed via a web browser, and an
SNMPv2 agent through either LAN port (if se ond SFP LAN port has been pur hased/enabled)
Unit's IP/MAC Address
The sour e Ethernet MAC address of E3Swit h Monitors is 00:50:C2:6F:xx:xx. The Monitor's urrent IP
and MAC addresses are always both shown at the HTTP management s reen.
The Monitor's management interfa e an be initially onta ted at either its automati link-lo al IP address
e3swit h.lo al as des ribed below or at its initial numeri IP address des ribed below. Note that after initial
setup, an operator may have hanged the onta t IP address to a new value and the initial addresses below
may not work. Prior to operator re onfiguration the unit will respond to HTTP, SNMP and ping requests to
its initial IP address.
For initial ommuni ation with the Monitor, it may be ne essary to set the network address of the host port
ommuni ating with the Monitor to 169.254.xxx.xxx with subnet mask 255.255.0.0. Se urity proto ols
advise routers not to forward pa kets with these link-lo al IP addresses, so a dire t onne tion is advised.
On e initial onta t has been established with the HTTP management interfa e of the Monitor, the
Monitor's IP address an be set to a new, stati value if desired.
If a unit's operator- onfigured IP address is lost or forgotten, it an be re overed as des ribed later in this
hapter.
8

Chapter 4: Remote Management HTTP and SNMP
Other than the e3swit h.lo al addresses des ribed below, all IP addresses used within the Monitor's
management interfa e must be in xxx.xxx.xxx.xxx numeri format rather than a human-readable DNS-
resolvable hostname.
Automatic Link-Local IP Address
E3Swit h produ ts are shipped with an initial IP address that onforms to re ent zero- onfiguration link-
lo al standards. This allows multiple E3Swit h Monitors on the same IP network to initialize with unique
IP addresses without onfli t and allows simple ping/HTTP/SNMP a ess to the Monitors using hostnames
e3swit h.lo al or e3swit h-2.lo al,... provided that, free, ZeroConf mDNS software has been installed on
the ma hine attempting to ommuni ate with the Monitor. Do not prefix www. prior to e3swit h.lo al.
www.e3swit h.lo al will not work.
If multiple WAN Monitors are powered-up on a onne ted LAN, they will negotiate between themselves to
determine whi h is assigned name e3swit h.lo al and whi h re eives e3swit h-2.lo al and so on. Sin e the
assigned name will not ne essarily be fixed to a parti ular unit after power y les, the system manager will
probably want to use/set the monitor's numeri IP address sometime during or after initial installation.
Web des riptions are available for ZeroConf mDNS and Link-lo al IPV4LL ip addresses. Free ZeroConf
software su h as Bonjour for Windows or Avahi is available for Windows/Linux/Unix ma hines.
Initial Numeric IP Address
The Monitor an also be onta ted at its initial default IP numeri address whi h always takes the form
169.254.aa.bbb. Units typi ally have the initial IP address listed on top of the hassis or an be initially
onta ted at the IP address above where aa.bbb mat hes the serial number listed on the front label.
●
The Monitor's urrent IP and MAC addresses are both shown at the HTTP management s reen.
Unknown IP Address Recovery
The following methods may be used to determine a Monitor's IP address if lost or forgotten. Note that on e
determined, management ommuni ation with the unit may only be possible from a host onfigured to the
same IP subnet address if the unit's default router address is invalid.
To manually dis over a unit's IP address, unplug all LAN and BNC ables from the Monitor and power
y le the unit. 30 se onds after powerup, the Monitor will begin blinking out its IP address on the leftmost
LED. Ea h digit is ounted up as an orange blink with a pause between digits and a short blink for a 0. A
de imal in the IP address is indi ated with a green blink. For example, <orange><orange><pause><short-
orange><pause><green>... would be an IP address that begins “20.”
For those with a ess to pa ket sniffers, upon power-up, the Monitor will broad ast several gratuitous ARP
pa kets on its network ports whi h an be examined with a sniffer or pa ket monitoring software to
determine a unit's IP address. The sour e Ethernet MAC address of su h pa kets and E3Swit h Monitors is
00:50:C2:6F:xx:xx. T pdump or Wireshark are two readily available software pa kages to examine
network pa kets.
Additionally, examination of the MAC address table of an atta hed LAN swit h or router may provide the
IP address if the E3Swit h MAC address prefix (00:50:C2:6F:xx:xx) an be lo ated.
Management Passwords
The HTTP management statisti s page is initially a essible without a password. The HTTP settings page
is initially modifiable within the first several minutes after powerup with username admin and no password.
If the unit has not had its default password hanged, after several minutes the settings page will be lo ked
for se urity reasons. It is desirable to hange the default password of the unit. For se urity reasons,
hanging the default password of the unit must be done within the first several minutes of any powerup. If
9

Chapter 4: Remote Management HTTP and SNMP
the HTTP management password is lost or forgotten, it may be reset by a essing the HTTP management
settings within the first minute after powerup and with no BNC ables atta hed to the unit.
SNMP statisti s may initially be a essed using the read-only ommunity name public. Write- ommunity
names and variable a ess authorization may be set through the HTTP management interfa e.
Security
Please also refer to the password se tion above.
HTTP Interface Security
A ess to the HTTP management interfa e statisti s and settings pages an be sele tively limited to users
knowing the HTTP management password, whi h is transmitted se urely on the network using MD5
en oding. New values of management settings, or modifi ations of the administrator password are not
en rypted and are visible to users monitoring network pa kets, as is statisti al data requested by an MD5
authorized user or any information visible on a HTTP page.
When logging out from any secure webpage, the browser window should always be closed! Browsers
typi ally ontinue to send administrator redentials ontinuously even after apparent logout.
SNMP Security
The Monitor implements SNMPv2 , whi h is inherently an inse ure proto ol; however, the Monitor
enhan es se urity by implementing view-based a ess management (VACM), whi h an restri t read or
write a ess to spe ifi management settings and statisti s. When shipped, the Monitor allows read a ess
to “safe” SNMP statisti s and prohibits read and write a ess to statisti s and settings whi h ould allow
determination of network topology or interfere with normal link traffi . The VACM onfiguration an be
updated through the HTTP management interfa e to meet the user's needs, and most SNMP variables an
also be set through the HTTP management interfa e in a more se ure manner than SNMP allows.
– SNMP VACM Se urity Warning –
As shipped, the default “safe_ro_view” is se ure but not private.
View based a ess model VACM for SNMPv2 provides good restri tion
of a ess to only spe ified statisti s but no data priva y and
minimal user authenti ation. When a spe ifi variable is enabled
for reading or writing, from a se urity perspe tive it should
be onsidered either publi for reading or publi for writing.
Alternatively, most onfiguration parameters an be set through
the HTTP password-prote ted interfa e whi h is se ure.
Viewing snmpd. onf exposes it and ommunity names to visibility by
3rd party network sniffers. All SNMPv2 data on the network
is visible. All ommunity names an be "guessed" and, when used,
be ome visible to sniffers. Sour e IP addresses of requests
an be forged. Enabling a write ommunity should be onsidered
inse ure with respe t to the spe ifi view variables enabled.
Variables in the groups: interfa e, ds3, dot3 & mau, ontrol the
link datapath; allowing write a ess allows disabling the link.
Spe ifi variables disabled for all write users are se ure.
Spe ifi statisti s disabled for all read users are invisible
and se ure.
HTTP Management
The Monitor ontains a omprehensive, user-friendly HTTP management interfa e whi h allows a manager
to monitor bit-error-rates on the DS3/E3 link, lost pa kets, and user-friendly status messages at a single,
10

Chapter 4: Remote Management HTTP and SNMP
olor- oded HTTP s reen. A s reenshot is available at www.e3swit h. om. Most settings that an be
modified via SNMP an also be set through the HTTP interfa e in a more user-friendly manner.
Refer to the onfiguration se tion of this do ument for guidan e on spe ifi settings.
vent Log File
A timestamped log of operating status and events may be a essed at the HTTP management administration
page.
Resetting
Two options for resetting the Monitor may be a omplished at the HTTP management administration page.
A management software reset will reset ounters, statisti s, MIB variables, and management software of the
Monitor without interrupting data flow on the WAN. A hardware reset will temporarily interrupt WAN
data flow as if the Monitor had experien ed a power y le. If upgrading firmware, for new fun tionality to
take effe t a hardware reset is required after the upgrade but need not be initiated immediately. A software
reset is not appropriate after upgrading firmware, as only the management CPU would be reset while the
WAN pa ket transfer CPU would be operating with the older, in ompatible version of firmware.
SNMP
The Monitor ontains an SNMP agent whi h an respond to version 1 and version 2 requests for network
statisti s from remote SNMP lients. The agent an also generate notifi ations of important network events
su h as when network ports go up/down or experien e high error rates. These trap notifi ations an be sent
to multiple hosts if desired, and using free or ommer ial software, the re eiving hosts an log the
notifi ations or even generate email or pager messages for network managers.
SNMPv2 is inherently an inse ure proto ol, so the Monitor implements VACM to restri t a ess to “safe”
statisti s and settings. Please refer to the se urity dis ussion se tion of this do ument.
SNMP onfiguration of various parameters su h as ommunity names and trap destinations is a essed
through the HTTP management interfa e and is implemented as a onfiguration file having an snmpd. onf
stru ture. Snmpd. onf is des ribed by third parties in publi ly available do uments.
Statisti s and settings a essible via SNMP are alled MIB-variables and are organized in a hierar hi al
tree topology. The MIB variable trees implemented by the Monitor in lude re ent versions of the DS3/E3,
interfa e, MAU, dot3, and many of the typi al IP-network MIB trees. The full list of MIB trees available is
listed by viewing the system.sysORTable of the Monitor. As mentioned earlier, a ess to ertain trees or
variables is initially disabled for se urity reasons, but an be set as the user wishes through the VACM
settings. The Monitor an typi ally return 1000 MIB variables per se ond in bulk requests and support
SNMP response message sizes up to 5000 bytes.
Upgrading Firmware
For a tivation of additional apabilities of the Monitor, see the “Feature A tivation” se tion. Feature
upgrades do not ne essarily require a firmware upgrade.
Firmware upgrades may be transferred to the Monitor via the LAN port. A hardware reset, whi h will
interrupt link data flow for several se onds, will be required at some point after the transfer in order to
begin using the new firmware. Instru tions for performing the TFTP transfer are in luded with all firmware
shipments. The most ommon sour e of problems when performing upgrades is attempting a TFTP transfer
in ASCII or text mode rather than binary or image mode.
Feature Acti ation/Upgrade
For a tivation of additional apabilities of the Monitor after initial pur hase, supply the fa tory with the
serial number from the front of your Monitor (also shown at the HTTP management page for re ent
11

Chapter 4: Remote Management HTTP and SNMP
firmware) and pur hase an alphanumeri “fa tory upgrade key” whi h is entered at the HTTP management
s reen.
Chapter 5: Operating Modes and Configuration
Telecom
There are several, low-level onfiguration settings for TDM ports; though, typi ally, the default settings are
appropriate:
●E3 vs DS3
●able length (for long DS3 runs only)
●unframed or M13 or C-Bit (for DS3 only)
●CRC length (none/16/32)
●s rambling on/off
●fra tional or full-rate utilization
Use a “DS3” onfiguration setting for North Ameri a, Japan, and South Korea; otherwise, “E3” speed.
The able length setting will transmit a slightly stronger signal on long DS3 oax runs.
Circuit Clock Speed
In the event of in oming lo k loss when the monitor is insert inline with the WAN ir uit, the transmit
lo k will automati ally swit h to a lo ally generated DS3/E3 lo k sour e.
The re eive lo k speeds are shown at the bottom of the unit's HTTP management statisti s page to assist
timing diagnosis.
DS3 Circuit ID PMDL
DS3 Path Maintenan e Data Link (PMDL) identifi ation messages asso iated with C-Bit framed DS3 links
may be re eived. Cir uit ID messages onvey human-readable, onfigurable, physi al lo ation information
of the DS3 sour e equipment. PMDL Cir uit ID messages fa ilitate onfirmation of the data sour e when
presented with a pair of unlabeled BNC ables.
Port to Port Packet Flow
LAN-to-LAN
Full LAN-to-LAN pa ket flow an be enabled on a unit, if desired. This might be useful if it was desirable
for in oming SFP management pa kets to exit the opper LAN Port 2 of the unit, along with the pa kets
arrying TDM data, in order to be re orded. LAN-to-LAN unidire tional flow for monitoring may also be
onfigured if desired.
LAN-to-LAN should be used cautiously to avoid overloading bandwidth limitations of the unit.
Loopback
C-Bit T3 T M ports will not respond to FEAC loopback requests.
LAN Port Settings
The hardware for two LAN ports exist on all Monitors shipped; however, entry-level models ship with only
100Base-TX mode on LAN Port 2 enabled. See upgrades se tion of this manual to enable these additional
features if required:.
12

Chapter 5: Operating Modes and Configuration
●GbE, GigE 1000Base-T for the RJ-45 LAN Port 2
●SFP LAN Port 1 whi h an a ept opti al or opper (100/1000) SFP trans eivers.
●If SFP port has been enabled, either LAN port an be onfigured as a dedi ated out-of-band
management port if desired.
●jumbo frames (9600 bytes)
See the “Interoperability” se tion of this manual for information on pa ket lengths and detailed port
onne tion/autonegotiation dis ussion.
The autonegotiation mode of the Monitor must match the autonegotiation mode of attached LAN
equipment. If autonegotiation is enabled on the Monitor it must be enabled on the atta hed equipment. If
disabled on the Monitor, it must be disabled on the atta hed equipment. This requirement is ne essary to
fulfill 802.3 standards whi h mandate a fallba k to half-duplex operation if an autonegotiation mismat h
exists. The Monitors require full duplex LAN onne tions to operate.
LAN Port Speed
1000Mbit/s LAN speeds are only available via the SFP port or if GbE LAN has been pur hased.
100Mbit/s is generally preferred over 1000Mbit/s, whi h generates signifi antly more power-requirements,
heat, and radiated noise even in the absen e of pa ket flow.
1000Mbit/s LAN port speed may be desireable when one LAN port is onfigured to monitor the other LAN
port in addition to re eiving in oming DS3/E3 data. In su h a ase, the data rate that the LAN port is
expe ted to transmit (the sum of all ports that ould be a data sour e for the LAN port) may be greater than
100Mbit/s. The HTTP management statisti s s reen will show overflow errors if a port's data rates are
ex eeded.
Setting more than one LAN port to 1000Mbit/s is not recommended and may result in
underflow/overflow errors in certain high packet load, memory-intensive cases.
Autonegotiation Problems
There are rare ases with older LAN equipment in whi h it may be ne essary to disable autonegotiation. If
CRC-errors or short pa ket errors are seen in the management statisti s of the LAN port, the atta hed LAN
equipment has probably onfigured itself to half-duplex mode and olliding pa kets are being lost. In su h
a ase, autonegotiation should be disabled on both the Monitor and the atta hed LAN equipment, with both
for ed to 100BaseTX full-duplex. Autonegotiation interoperability and standards were not well understood
by the industry at the in eption of 100BaseTX, resulting in some older LAN equipment not understanding
the Monitor's autonegotiation advertisement of stri tly full-duplex apability.
SFP Second LAN Port
The SFP LAN Port 1 hardware exists on all Monitors shipped and may be enabled as pur hased or enabled
by pur hasing an upgrade password. This upgrade allows an SFP trans eiver to enable out-of-band
management or data transfer through either LAN port, or enable fiber-opti LAN onne tions of 10km or
more. Refer to interoperability se tion of this do ument for ompatible SFP trans eivers.
Dedicated Management/Data LAN Ports
If the SFP Se ond LAN Port is in use, then either LAN port may be onfigured to pass TDM data pa kets
or, sele tively, to pass only management or only TDM data pa kets when su h an be determined.
If a LAN port is onfigured for TDM data-only pa kets, the unit will drop in oming management pa kets
on that LAN port. On a “data-only” LAN port, these management uni ast pa kets and management
broad ast/multi ast pa kets may not be forwarded to the se ond LAN even if LAN-to-LAN traffi flow is
onfigured.
13

Chapter 5: Operating Modes and Configuration
VLAN
In some firmware versions it is possible to onfigure a VLAN ID for pa kets ontaining TDM data.
VLAN onfiguration settings shown at the HTTP management page may also be set for ommuni ation
with the Monitor's management entity.
As shipped, the unit will a ept management pa kets with any VLAN tags and attempt to respond to the
same. For more robust performan e, spe ifi VLAN tag settings an be onfigured.
Chapter 6: Interoperability
LAN
The LAN ports of the Monitor support, at a minimum, all 100BaseTX Full-Duplex Ethernet onne tions up
to maximum line lengths and are set to auto-MDI/MDIX to automati ally dete t/ orre t rossover vs
straight LAN able and autonegotiate for full-duplex and pause frame modes with the atta hed LAN
equipment. Passwords may be pur hased to upgrade to enhan ed LAN port modes as des ribed elsewhere
in this manual.
The management agent a epts and responds with pa kets having MTU of 1350 bytes in order to
automati ally allow room for se urity proto ol overheads.
HDLC WAN frames an be longer than Ethernet standards. WAN frames longer than MTU setting
onfiguration will be trun ated to the MTU of the LAN.
Autonegotiation problems
There are rare ases with older LAN equipment in whi h it may be ne essary to disable autonegotiation. If
CRC-errors or short pa ket errors are seen in the management statisti s of the LAN port, the atta hed LAN
equipment has probably onfigured itself to half-duplex mode and olliding pa kets are being lost. In su h
a ase, autonegotiation should be disabled on both the Monitor and the atta hed LAN equipment with both
for ed to 100BaseTX full-duplex. Autonegotiation interoperability and standards were not well understood
by the industry at the in eption of 100BaseTX, resulting in some older LAN equipment not understanding
the Monitor's autonegotiation advertisement of stri tly full-duplex apability.
It is highly desirable to leave autonegotiation enabled so that hanging atta hed LAN equipment does not
result in the new equipment defaulting to half-duplex if set to autonegotiate.
SFP LAN Port 1
This port is designed to be ompatible with inexpensive, high-quality, opper or fiber-opti , SFP
trans eivers from Finisar, whi h allows LAN onne tions of 10km or more. Most other industry-standard
SFP trans eivers will work as well; however, fiber-opti features su h as temperature and opti al
transmit/re eive power and alarms will only be available if using Finisar trans eivers. Non-Finisar opper,
RJ45 SFP trans eivers may only operate in 1000Base-T mode, while re ommended trans eivers from
Finisar, and possibly Avago or 3Com will operate in 100Base-TX mode as well.
Pause Frames
The Monitor generates no pause frames and ignores pause ommand frames sent to it.
Telecom
Monitoring is possible for a variety of E3 or T3/DS3 links (with appropriate media Monitors) su h as fiber
opti , mi rowave radio, laser, opper, satellite, or a ombination; however, the atta hment interfa e is
always via 75-ohm opper oaxial rather than opti al. The TDM ir uit may be either framed or unframed
and supports both M13, M23, lear- hannel, C-Bit, and G.751 framing. C-Bit framing is suggested for DS3
links.
14

Chapter 6: Interoperability
Chapter 7: Telecom Connections
Framing and Physical Link
The unit an monitor a variety of E3, T3/DS3 links (with the appropriate media Monitor) su h as fiber
opti , mi rowave radio, laser, opper, satellite, or a ombination. The Monitor may be used with a standard
(i.e., M13, M23, lear- hannel, C-Bit or G.751) framed or unframed, full-rate E3 or T3/DS3 link with AMI
and HDB3 or B3ZS en oding. C-Bit framing is re ommended for DS3 links. The Monitor will report
PMDL Cir uit ID present on C-Bit links.
Ea h Monitor regenerates the timing lo k of the re eived TDM bit-stream, within E3 and T3/DS3
standards. High-a ura y re eive lo k rates are displayed at the unit's HTTP management page.
Telecom Cabling
For the E3 or T3/DS3 onne tion, 75-ohm oaxial ables with BNC onne tors are required. It is important
that 75-ohm able be used and not 50-ohm able. For long onne tions or in ele tri ally noisy
environments it may be important to use a high-quality 75-ohm able whi h will have more onsistent
shielding and ondu tion. The maximum length of ea h able shall be 440 meters for E3 or 300 meters for
T3/DS3, but the a eptable able lengths of equipment atta hed to the Monitor must be met as well. For
lengths over 135 meters, testing in field should be used to determine whether bit error rates are a eptable.
Long able lengths also require areful sele tion of able type and attention to sour es of external noise.
Third-party fiber to opper media Monitors an be used with the E3Swit h Monitor to implement fiber-
opti DS3/E3 links; however, refer to the interoperability se tion of this do ument for vendors to avoid.***
Chapter 8: LAN Connections and Performance
LAN Ports
Ea h LAN port implements the following features to maximize LAN ompatibility and link utilization and
minimize pa ket loss:
•autosense/auto onfiguration/autonegotiation with the atta hed LAN.
•100Mbit/se data rates (1000Mbit/s via SFP or if GbE upgrade pur hased).
•full-duplex LAN onne tion.
•1650-byte pa ket a eptan e (1350 for mgmt and 9600 for jumbo).
These features and their ramifi ations are dis ussed below in more detail.
Autonegotiation
The network equipment attached to the LAN port of the Monitor should be set for autonegotiation
mode in order to allow the Monitor to negotiate a 100Mbit full-duplex connection.
There are rare ases with older LAN equipment in whi h it may be ne essary to disable autonegotiation. If
CRC-errors or short pa ket errors are seen in the management statisti s of the LAN port, the atta hed LAN
equipment has probably onfigured itself to half-duplex mode and olliding pa kets are being lost. In su h
a ase, autonegotiation should be disabled on both the Monitor and the atta hed LAN equipment, with both
for ed to 100BaseTX full-duplex. Autonegotiation interoperability and standards were not well understood
by the industry at the in eption of 100BaseTX, resulting in some older LAN equipment not understanding
the Monitor's autonegotiation advertisement of stri tly full-duplex apability.
15

Chapter 8: LAN Conne tions and Performan e
It is highly desirable to leave autonegotiation enabled so that hanging atta hed LAN equipment does not
result in the new equipment defaulting to half-duplex if set to autonegotiate. Autonegotiation must always
be enabled for 1000Mbit/s links.
LAN Cabling
It is important to use the orre t abling for proper operation. Use UTP Category 5 network able with RJ-
45 onne tors for the LAN ports, and do not ex eed 100 meters (328 feet) in length. Either a straight-
through or rossover able may be used.
Chapter 9: LAN Packet Format for WAN Data Encapsulation
Header Format for WAN Data Encapsulation
Either raw WAN HDLC bytes may be pla ed on the LAN with no MAC header prepended, or layer 2
headers may be onfigured for the LAN pa kets that en apsulate the WAN data. If desired, a MAC header
is manually spe ified at the Monitor's HTTP administration s reen and onsists of:
- Destination MAC address (ffffffffffff suggested)
- Sour e MAC address (0050 26f3001 suggested)
- add VLAN if not blank (81000064 suggested)
- add EtherType if not blank (8847 suggested)
- add MPLS if not blank (ff0001ff suggested)
- add Pseudowire Control Word to MPLS
MTU
WAN HDLC pa kets that are longer than the LAN MTU onfigured at the Monitor's HTTP administration
s reen will be trun ated to fit within the spe ified LAN MTU. 9600-byte jumbo MTU apability may be
pur hased as an option.
Transport Layer
LAN pa kets are onfigured with simple MAC Layer 2 addressing whi h may in lude a simple, fixed
MPLS header. IP Layer 3 addressing is not supported.
Chapter 10: Troubleshooting
General
A great deal of diagnosti information is available by a essing the HTTP management interfa e of the
Monitor. Refer to the management se tion of this do ument for additional information.
The Monitor's front panel lights can provide useful information but are often under-utilized. They are
simple to read and an indi ate where a data onne tion is being lost. It an be very helpful to learn their
meaning and monitor flashes as a pa ket is re eived at ea h port.
Incoming Circuit I is shown at the top of the Monitor's HTTP management page for C-Bit S3 links,
facilitating confirmation of the remote data transmitter when presented with a pair of unlabeled BNC
cables.
The Ethernet networks to whi h the Monitor onne ts are omplex and may ontain thousands of devi es,
ea h of whi h requires proper onfiguration and performan e. As su h, network onfiguration and
topology issues dominate when problems arise. When troubleshooting, solutions an be rea hed more
rapidly by remembering that the most frequent cause of problems arises from improper network
configurations.
16
ffffffffffff
0050c26f3000
81000064
8847
ff0001ff

Chapter 10: Troubleshooting
The next most frequent sour e of problems generally arises from faulty cabling or connectors or in orre t
able type. Cabling must be UTP5 or better for LAN and 75-Ohm rather than 50-Ohm for TDM. If long
TDM able runs or an ele tri ally noisy environment exists, high-quality oaxial able will be required.
The least frequent ause of problems will be the hardware of the Monitor itself. This statement is not due to
a nar issisti point of view, but rather to the simpli ity of onfiguration features on the Monitor and the
low- omponent ount. A mi rowave radio link, for example, has waveguides that an fill with water,
antennas that an be ome misaligned, foreign obje ts that an blo k the path. From a failure point of view,
the Monitor is a simpler devi e.
Performance
Performan e issues are addressed in the prior hapters.
Interoperability
The interoperability se tion of this manual should be reviewed to ensure that appropriate equipment is
onne ted to the Monitor. Conne ted LAN equipment should adhere to 802.3 standards.
Pinging
Ping is not reliable. The proto ol whi h ping programs use does not guarantee delivery of the data
pa kets. Ping programs from major software and hardware corporations are known to contain bugs,
both in packet content and function. Generally, however, nearly all of the ping pa kets on a test network
that is not over-loaded should get through; if fewer are re eived, there is probably a problem.
The ping program is a useful, simple test for a TCP/IP Ethernet network. It is a program that sends a data
pa ket from a sour e ma hine to a destination ma hine, whi h then returns a response pa ket. There is a
plethora of information about ping and the free publi -domain ping utilities available. Ping is often
supplied as a standard operating system utility, and often the ommand “ping” followed by the destination
ma hine's IP address or hostname is all that is required to be typed at the sour e ma hine's ommand line.
The default ping generates approximately one 64-byte pa ket per se ond. This is not a robust test. If
onvenient, lo ate a ping program or set ommand line parameters to generate perhaps 50 pings per se ond
and try both small pa kets and large 1400-byte pa kets. Be aware that pa kets larger than 1400 bytes
sometimes un over bugs in the software of ping programs.
Step-by-Step Diagnosis
This se tion assumes that ommuni ation between two ma hines at opposite ends of the E3, T3/DS3 link
(herein the link) is failing. If this is a test in the laboratory or without a TDM ir uit present, be sure to read
the previous “Laboratory Testing” se tion first.
1. If a ess to the HTTP management interfa e of the Monitor is possible, many useful status messages
will be displayed. Typi ally, any message highlighted in orange should be of on ern. Error ounters
are of lesser on ern if they are not in rementing, and some link errors would be normal as link ables
are initially onne ted.
The S3/E3 BER light of the Monitor should be illuminated and green. This indi ates that a valid,
DS3/E3 waveshape is being re eived without bit errors and with proper framing. Refer to the front
panel se tion of this do ument for other light olors.
The S3/E3 port light of the Monitor should be illuminated and green. This indi ates that a valid,
arrier signal is being re eived on the WAN. Refer to the front panel se tion of this do ument for other
light olors.
17

Chapter 10: Troubleshooting
2. Ensure a proper LAN cable is being used. Straight-through or rossover abling is a eptable. The
LAN light of the Monitor port to whi h any LAN is atta hed should be illuminated and green. If not,
ensure that the atta hed equipment is set for autonegotiation and an a ept 100BaseTX Full-Duplex
links. Refer to front panel se tion of this do ument for other LAN light olors.
3. The network equipment atta hed to the LAN port of the Monitor should be set for autonegotiation
mode in order to allow the Monitor to negotiate a 100Mbit full-duplex onne tion. For ing either the
Monitor's or atta hed equipment's LAN port to 100Mbit full-duplex may not allow the proper
autonegotiation and LAN onne tion to o ur. There are rare ases with older LAN equipment in
whi h it may be ne essary to disable autonegotiation. If CRC-errors or short packet errors are seen
in the management statistics of the LAN port, the attached LAN equipment has probably
configured itself to half-duplex mode and colliding packets are being lost. In su h a ase,
autonegotiation should be disabled on both the Monitor and the atta hed LAN equipment with both
for ed to 100BaseTX full-duplex. Autonegotiation interoperability and standards were not well
understood by the industry at the in eption of 100BaseTX, resulting in some older LAN equipment not
understanding the Monitor's autonegotiation advertisement of stri tly full-duplex apability.
4. Monitor lights during pa ket transmission:
•With LANs atta hed, verify, perhaps using pings, that data pa kets generated by a lo al ma hine
ause the Monitor's light of the onne ted LAN port to blink. If not, determine if there is an
intermediate router or pie e of equipment that is not properly forwarding the data pa kets to the
Monitor. Examine the Link/A tivity light on the sour e ma hine and any intermediate ma hines to
ensure they behave properly (usually fli ker) as well.
5. Enlist the aid of a sniffer program to view at the sour e and destination ma hines exa tly what data
pa kets are being sent and re eived. Free publi -domain programs su h as Wireshark are readily
available.
Chapter 11: Third Party Copyright Notices
E3Swit h is grateful for and ontributes to open sour e software development whi h may be prote ted by
the following opyright noti es and li ense terms:
eCos License
E3Swit h gratefully a knowledges the ontributions of the eCos developers and ommunity. Current eCos sour e files are available at http://e os.sour eware.org/ E3Swit h
implementation-spe ifi modifi ations to those files are available by onta ting E3Swit h LLC.
The FreeBSD Copyright
Copyright 1994-2006 The FreeBSD Proje t. All rights reserved.
Redistribution and use in sour e and binary forms, with or without modifi ation, are permitted provided that the following onditions are met:
1. Redistributions of sour e ode must retain the above opyright noti e, this list of onditions and the following dis laimer.
2. Redistributions in binary form must reprodu e the above opyright noti e, this list of onditions and the following dis laimer in the do umentation and/or other materials
provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE FREEBSD PROJECT ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD
PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The views and on lusions ontained in the software and do umentation are those of the authors and should not be interpreted as representing offi ial poli ies, either expressed or
implied, of the FreeBSD Proje t.
The Net-SNMP Copyright
---- Part 1: CMU/UCD opyright noti e: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California
18

Chapter 11: Third Party Copyright Noti es
All Rights Reserved
Permission to use, opy, modify and distribute this software and its
do umentation for any purpose and without fee is hereby granted,
provided that the above opyright noti e appears in all opies and
that both that opyright noti e and this permission noti e appear in
supporting do umentation, and that the name of CMU and The Regents of
the University of California not be used in advertising or publi ity
pertaining to distribution of the software without spe ifi written
permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL
WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR
THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF
CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN
CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
---- Part 2: Networks Asso iates Te hnology, In opyright noti e (BSD) -----
Copyright ( ) 2001-2003, Networks Asso iates Te hnology, In
All rights reserved.
Redistribution and use in sour e and binary forms, with or without
modifi ation, are permitted provided that the following onditions are met:
* Redistributions of sour e ode must retain the above opyright noti e,
this list of onditions and the following dis laimer.
* Redistributions in binary form must reprodu e the above opyright
noti e, this list of onditions and the following dis laimer in the
do umentation and/or other materials provided with the distribution.
* Neither the name of the Networks Asso iates Te hnology, In nor the
names of its ontributors may be used to endorse or promote
produ ts derived from this software without spe ifi prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS
IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 3: Cambridge Broadband Ltd. opyright noti e (BSD) -----
Portions of this ode are opyright ( ) 2001-2003, Cambridge Broadband Ltd.
All rights reserved.
Redistribution and use in sour e and binary forms, with or without
modifi ation, are permitted provided that the following onditions are met:
* Redistributions of sour e ode must retain the above opyright noti e,
this list of onditions and the following dis laimer.
* Redistributions in binary form must reprodu e the above opyright
noti e, this list of onditions and the following dis laimer in the
do umentation and/or other materials provided with the distribution.
* The name of Cambridge Broadband Ltd. may not be used to endorse or
promote produ ts derived from this software without spe ifi prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 4: Sun Mi rosystems, In . opyright noti e (BSD) -----
Copyright © 2003 Sun Mi rosystems, In ., 4150 Network Cir le, Santa Clara,
California 95054, U.S.A. All rights reserved.
Use is subje t to li ense terms below.
This distribution may in lude materials developed by third parties.
19

Chapter 11: Third Party Copyright Noti es
Sun, Sun Mi rosystems, the Sun logo and Solaris are trademarks or registered
trademarks of Sun Mi rosystems, In . in the U.S. and other ountries.
Redistribution and use in sour e and binary forms, with or without
modifi ation, are permitted provided that the following onditions are met:
* Redistributions of sour e ode must retain the above opyright noti e,
this list of onditions and the following dis laimer.
* Redistributions in binary form must reprodu e the above opyright
noti e, this list of onditions and the following dis laimer in the
do umentation and/or other materials provided with the distribution.
* Neither the name of the Sun Mi rosystems, In . nor the
names of its ontributors may be used to endorse or promote
produ ts derived from this software without spe ifi prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS
IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Apache License
1. Definitions.
"Li ense" shall mean the terms and onditions for use, reprodu tion, and distribution as defined by Se tions 1 through 9 of this do ument.
"Li ensor" shall mean the opyright owner or entity authorized by the opyright owner that is granting the Li ense.
"Legal Entity" shall mean the union of the a ting entity and all other entities that ontrol, are ontrolled by, or are under ommon ontrol with that entity. For the purposes of this
definition, " ontrol" means (i) the power, dire t or indire t, to ause the dire tion or management of su h entity, whether by ontra t or otherwise, or (ii) ownership of fifty per ent
(50%) or more of the outstanding shares, or (iii) benefi ial ownership of su h entity.
"You" (or "Your") shall mean an individual or Legal Entity exer ising permissions granted by this Li ense.
"Sour e" form shall mean the preferred form for making modifi ations, in luding but not limited to software sour e ode, do umentation sour e, and onfiguration files.
"Obje t" form shall mean any form resulting from me hani al transformation or translation of a Sour e form, in luding but not limited to ompiled obje t ode, generated
do umentation, and onversions to other media types.
"Work" shall mean the work of authorship, whether in Sour e or Obje t form, made available under the Li ense, as indi ated by a opyright noti e that is in luded in or atta hed to
the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Sour e or Obje t form, that is based on (or derived from) the Work and for whi h the editorial revisions, annotations,
elaborations, or other modifi ations represent, as a whole, an original work of authorship. For the purposes of this Li ense, Derivative Works shall not in lude works that remain
separable from, or merely link (or bind by name) to the interfa es of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, in luding the original version of the Work and any modifi ations or additions to that Work or Derivative Works thereof, that is
intentionally submitted to Li ensor for in lusion in the Work by the opyright owner or by an individual or Legal Entity authorized to submit on behalf of the opyright owner. For
the purposes of this definition, "submitted" means any form of ele troni , verbal, or written ommuni ation sent to the Li ensor or its representatives, in luding but not limited to
ommuni ation on ele troni mailing lists, sour e ode ontrol systems, and issue tra king systems that are managed by, or on behalf of, the Li ensor for the purpose of dis ussing
and improving the Work, but ex luding ommuni ation that is onspi uously marked or otherwise designated in writing by the opyright owner as "Not a Contribution."
"Contributor" shall mean Li ensor and any individual or Legal Entity on behalf of whom a Contribution has been re eived by Li ensor and subsequently in orporated within the
Work.
2. Grant of Copyright Li ense. Subje t to the terms and onditions of this Li ense, ea h Contributor hereby grants to You a perpetual, worldwide, non-ex lusive, no- harge, royalty-
free, irrevo able opyright li ense to reprodu e, prepare Derivative Works of, publi ly display, publi ly perform, subli ense, and distribute the Work and su h Derivative Works in
Sour e or Obje t form.
3. Grant of Patent Li ense. Subje t to the terms and onditions of this Li ense, ea h Contributor hereby grants to You a perpetual, worldwide, non-ex lusive, no- harge, royalty-
free, irrevo able (ex ept as stated in this se tion) patent li ense to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where su h li ense applies only
to those patent laims li ensable by su h Contributor that are ne essarily infringed by their Contribution(s) alone or by ombination of their Contribution(s) with the Work to whi h
su h Contribution(s) was submitted. If You institute patent litigation against any entity (in luding a ross- laim or ounter laim in a lawsuit) alleging that the Work or a Contribution
in orporated within the Work onstitutes dire t or ontributory patent infringement, then any patent li enses granted to You under this Li ense for that Work shall terminate as of
the date su h litigation is filed.
4. Redistribution. You may reprodu e and distribute opies of the Work or Derivative Works thereof in any medium, with or without modifi ations, and in Sour e or Obje t form,
provided that You meet the following onditions:
1. You must give any other re ipients of the Work or Derivative Works a opy of this Li ense; and
2. You must ause any modified files to arry prominent noti es stating that You hanged the files; and
3. You must retain, in the Sour e form of any Derivative Works that You distribute, all opyright, patent, trademark, and attribution noti es from the Sour e form of the Work,
ex luding those noti es that do not pertain to any part of the Derivative Works; and
4. If the Work in ludes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must in lude a readable opy of the attribution noti es
ontained within su h NOTICE file, ex luding those noti es that do not pertain to any part of the Derivative Works, in at least one of the following pla es: within a NOTICE text
file distributed as part of the Derivative Works; within the Sour e form or do umentation, if provided along with the Derivative Works; or, within a display generated by the
Derivative Works, if and wherever su h third-party noti es normally appear. The ontents of the NOTICE file are for informational purposes only and do not modify the Li ense.
You may add Your own attribution noti es within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that su h
additional attribution noti es annot be onstrued as modifying the Li ense.
20
Table of contents