Cascading
Guide

Release 3.3.10

Copyright © 2017 Raritan, Inc.
USBcascade-1C-v3.3.10-E
June 2017
255-80-0012-00 RoHSSafety Guidelines
WARNING! Read and understand all sections in this guide before installing or operating this product.
WARNING! Connect this product to an AC power source whose voltage is within the range specified
on the product's nameplate. Operating this product outside the nameplate voltage range may resultin electric shock, fire, personal injury and death.
WARNING! Connect this product to an AC power source that is current limited by a suitably rated
fuse or circuit breaker in accordance with national and local electrical codes. Operating this productwithout proper current limiting may result in electric shock, fire, personal injury and death.
WARNING! Connect this product to a protective earth ground. Never use a "ground lift adaptor"
between the product's plug and the wall receptacle. Failure to connect to a protective earth groundmay result in electric shock, fire, personal injury and death.
WARNING! This product contains no user serviceable parts. Do not open, alter or disassemble thisproduct. All servicing must be performed by qualified personnel. Disconnect power before servicing
this product. Failure to comply with this warning may result in electric shock, personal injury anddeath.
WARNING! Use this product in a dry location. Failure to use this product in a dry location may resultin electric shock, personal injury and death.
WARNING! Do not rely on this product's receptacle lamps, receptacle relay switches or any otherreceptacle power on/off indicator to determine whether power is being supplied to a receptacle.
Unplug a device connected to this product before performing repair, maintenance or service on thedevice. Failure to unplug a device before servicing it may result in electric shock, fire, personal injury
and death.
WARNING! Only use this product to power information technology equipment that has a UL/IEC
60950-1 or equivalent rating. Attempting to power non-rated devices may result in electric shock, fire,
personal injury and death.
WARNING! Do not use a Raritan product containing outlet relays to power large inductive loads suchas motors or compressors. Attempting to power a large inductive load may result in damage to therelay.
WARNING! Do not use this product to power critical patient care equipment, fire or smoke alarmsystems. Use of this product to power such equipment may result in personal injury and death.
WARNING! If this product is a model that requires assembly of its line cord or plug, all suchassembly must be performed by a licensed electrician and the line cord or plugs used must be
suitably rated based on the product's nameplate ratings and national and local electrical codes.
Assembly by unlicensed electricians or failure to use suitably rated line cords or plugs may result inelectric shock, fire, personal injury or death.
WARNING! This product contains a chemical known to the State of California to cause cancer, birthdefects, or other reproductive harm.

Safety Instructions
1.

Installation of this product should only be performed by a person who has knowledge andexperience with electric power.

2.

Make sure the line cord is disconnected from power before physically mounting or moving thelocation of this product.

3.

This product is designed to be used within an electronic equipment rack. The metal case of thisproduct is electrically bonded to the line cord ground wire. A threaded grounding point on thecase may be used as an additional means of protectively grounding this product and the rack.

4.

Examine the branch circuit receptacle that will supply electric power to this product. Make sure
the receptacle’s power lines, neutral and protective earth ground pins are wired correctly andare the correct voltage and phase. Make sure the branch circuit receptacle is protected by asuitably rated fuse or circuit breaker.

5.

If the product is a model that contains receptacles that can be switched on/off, electric power
may still be present at a receptacle even when it is switched off.

This document contains proprietary information that is protected by copyright. All rights reserved. Nopart of this document may be photocopied, reproduced, or translated into another language without
express prior written consent of Raritan, Inc.
© Copyright 2017 Raritan, Inc. All third-party software and hardware mentioned in this document areregistered trademarks or trademarks of and are the property of their respective holders.
FCC Information

This equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a commercial installation. This equipment generates, uses, and canradiate radio frequency energy and if not installed and used in accordance with the instructions, maycause harmful interference to radio communications. Operation of this equipment in a residential
environment may cause harmful interference.
VCCI Information (Japan)

Raritan is not responsible for damage to this product resulting from accident, disaster, misuse,abuse, non-Raritan modification of the product, or other events outside of Raritan's reasonable
control or not arising under normal operating conditions.
If a power cable is included with this product, it must be used exclusively for this product.

Contents
Safety Guidelines

ii

Safety Instructionsiii

Applicable Productsix

What's New in the Cascading Guidex

Chapter 1

1

Cascading Solution's Overview

Cascading Applications .................................................................................................................... 1
Illustration.............................................................................................................................. 1
Best Practices ........................................................................................................................ 3
When to Avoid Cascading Devices.................................................................................................... 3
Cascading Procedure ....................................................................................................................... 4

Chapter 2

Cascading Modes

5

Overview of the Cascading Modes.................................................................................................... 5
Setting the Cascading Mode............................................................................................................. 7
Mode Change via Web Interface ............................................................................................ 7
Mode Change via CLI.............................................................................................................. 9

Chapter 3

Cascading Raritan Devices

11

USB Cascading ............................................................................................................................... 11
USB-Cascading Requirements............................................................................................ 12
Cascading the Raritan devices via USB ............................................................................... 13
Extended Cascading (for PX3-iX7 Only) ......................................................................................... 15
Extended-Cascading Requirements.................................................................................... 15
Cascading PX3-iX7 via Ethernet or USB .............................................................................. 16
Cascading Restrictions................................................................................................................... 18

Chapter 4

Accessing Raritan Devices

20

Finding the IP Address ................................................................................................................... 20
Local Console....................................................................................................................... 21vi

Contents

LCD Display .......................................................................................................................... 21
MAC Address........................................................................................................................ 25
HTTP/HTTPS Access ...................................................................................................................... 25
Supported Web Browsers .................................................................................................... 25
Login..................................................................................................................................... 26
SSH/Telnet Access ......................................................................................................................... 27
SNMP Management........................................................................................................................ 27
SNMP Notifications .............................................................................................................. 28
Third-Party SNMP Managers .............................................................................................. 28
Port Numbers for Port-Forwarding Devices ................................................................................. 28
Port Number Syntax ............................................................................................................ 28
Port Forwarding Examples.................................................................................................. 30

Chapter 5

Identifying Cascaded Devices

33

Using the Web Interface ................................................................................................................. 33
Using the CLI .................................................................................................................................. 36
Using the SNMP.............................................................................................................................. 38
Using the LCD Display .................................................................................................................... 40
Dot-Matrix LCD Display ....................................................................................................... 40
Character LCD Display......................................................................................................... 43

Chapter 6

Adding, Removing or Swapping Cascaded Devices

45

Chapter 7

Firmware Upgrade

47

Updating the Raritan device Firmware .......................................................................................... 47
Upgrade Sequence in an Existing Cascading Chain ...................................................................... 48

Appendix A

Unsupported Cascading Connections for Port Forwarding

50

Appendix B

Cascading Troubleshooting

53

Possible Root Causes..................................................................................................................... 53
Port-Forwarding Slave Device Events ........................................................................................... 56
The Ping Tool .................................................................................................................................. 56
Ping via the Web Interface ................................................................................................... 57
Ping via the CLI .................................................................................................................... 58

vii

Contents

Appendix C

Additional Information

60

Connecting the Raritan device to a Computer ............................................................................... 60
Making a Connection............................................................................................................ 60
Installing the USB-to-Serial Driver (Optional) .................................................................... 61
Configuring Network Settings........................................................................................................ 63
Configuration via Web Interface .......................................................................................... 63
Configuration via CLI............................................................................................................ 64
Wireless LAN Information.............................................................................................................. 70
Supported Wireless LAN Configuration .............................................................................. 70
USB Wireless LAN Adapters................................................................................................ 70

Index

viii

73

Applicable ProductsThis guide is applicable to the following Raritan products.







PX2 series power distribution units (PDUs)
PX3 series PDUs, including PX3-iX7
EMX asset management devices
PX3TS transfer switches
Branch Circuit Monitor 1 (BCM1)
Branch Circuit Monitor 2 (BCM2), including PMC modelsixWhat's New in the Cascading Guide

Warning: Firmware version 3.3.10 or later is NOT compatible withpre-3.3.10 firmware versions in terms of the cascading feature so all
devices in the cascading chain must run version 3.3.10 or later.
To upgrade an existing USB-cascading chain from a firmware version
older than 3.3.10, you must start from the last slave device and so on
until the master device. Otherwise, a networking issue occurs. See
Upgrade Sequence in an Existing Cascading Chain (on page 48).

The following sections have changed or information has been added to
the Cascading Guide based on changes and enhancements to the Raritan
software, hardware, and/or user documentation.


The following chapters, including their subtopics, have been
modified or re-organized.
Chapter 1: Cascading Solution's Overview (on page 1)
Chapter 2: Cascading Modes (on page 5)
Chapter 3: Cascading Raritan Devices (on page 11)
Chapter 7: Firmware Upgrade (on page 47)








Port Numbers for Port-Forwarding Devices (on page 28)
Port Number Syntax (on page 28)
Using the SNMP (on page 38)
Character LCD Display (on page 43)
Adding, Removing or Swapping Cascaded Devices (on page 45)
Cascading Troubleshooting (on page 53)

xChapter 1

Cascading Solution's Overview
Raritan provides a cascading solution, which enables multiple Raritan
devices to share the network connectivity by cascading them through the
USB or Ethernet interface.
You can access and administer each device in the cascading chain overthe Internet from anywhere via various protocols -- HTTP(S), SNMP, SSH,
Telnet and Modbus. Besides, each device can be upgraded respectively.
For documentation purposes, the first device in the cascading chain iscalled the 'master' device and the others are called 'slave' devices.

In This Chapter
Cascading Applications ...............................................................................1
When to Avoid Cascading Devices...............................................................3
Cascading Procedure ..................................................................................4

Cascading Applications
To reduce the number of Ethernet connections or save networking costs
in your data center, you can apply the cascading solution.
Illustration
In a cascading chain, all Raritan devices are cascaded via USB or
Ethernet, and only the master device is connected to the LAN.
The following diagrams illustrate different cascading scenarios using
Zero U PDUs. Red lines in the diagrams represent the cascading
connections, which are either USB or standard network patch cables.
Scenario 1: Cabinet 1 has four PDUs cascaded, sharing one
Ethernet connection.

1

Chapter 1: Cascading Solution's Overview

Scenario 2: Cabinet 1 and Cabinet 2 have four PDUs respectively.
The eight PDUs are cascaded, sharing one Ethernet connection.

Scenario 3: Cabinet 1 through Cabinet 4 have four PDUs
respectively.
The 16 PDUs are cascaded, sharing one Ethernet connection.

2

Chapter 1: Cascading Solution's Overview

Best Practices
One Ethernet connection per cabinet is better:
One Ethernet connection per cabinet is better than one Ethernet
connection across cabinets because of these advantages:Easier to manage or maintain one cabinet when all of the cabling andconnections are located in the same cabinet.
Reduces the cross-cabinet cabling.
When to establish a chain comprising 16 devices:A chain consisting of 16 devices saves the most Ethernet connections
and costs, and it is recommended only when:External Ethernet ports are expensive or limited.
Available IP addresses are limited.
Ethernet cascading is recommended for PX3-iX7 PDUs:

If your Raritan products are PX3-iX7 PDUs, cascading them via Ethernet
is better than via USB because the Ethernet interface offers the following
benefits.
Longer cabling distance
Lower latency
More reliable connection with RJ-45 connectors

See Extended Cascading (for PX3-iX7 Only) (on page 15).

When to Avoid Cascading Devices
There are two scenarios where the cascading solution is NOT
recommended.
High network reliability is required:
The cascading solution increases the number of network bridging
points for cascaded devices, which may result in network
unreliability. Therefore, when high network reliability is required,establish a separate network connection for each Raritan device tominimize the number of potential network failure points.

3

Chapter 1: Cascading Solution's Overview

High bandwidth is required:
The bandwidth among cascaded devices is limited by the USB or
Ethernet interface where they are connected. When high bandwidthis required, such as transmission of webcam videos, it is strongly
recommended to directly connect that Raritan device to the network
to optimize the data transfer rate.
The maximum bandwidth supported by each interface: USB: 12 or 480 Mbps, half duplex.


12 Mbps (half duplex) when both or either side supports
full-speed USB only.



480 Mbps (half duplex) when both cascaded devices are
PX3-iX7 PDUs, which support high-speed USB.

 Ethernet: 100 Mbps, full duplex.

Note: Effective throughput may be lower than the rate listed due
to protocol overhead.

Cascading Procedure
Since firmware version 3.3.10, you must follow the steps below toestablish a cascading chain.
Warning: Networking issues occur if the following steps arereversed.
Main cascading procedure:1.

Log in to each Raritan device and configure the cascading mode.
Refer to:

2.

Setting the Cascading Mode (on page 7).

Cascade all devices.
Refer to:


4

Cascading the Raritan devices via USB (on page 13)
Cascading PX3-iX7 via Ethernet or USB (on page 16)

Chapter 2

Cascading Modes
You must apply a cascading mode to a cascading chain.
The cascading mode determines how each device in the chain isaccessed.

In This Chapter
Overview of the Cascading Modes...............................................................5
Setting the Cascading Mode........................................................................7

Overview of the Cascading Modes
There are two cascading modes: Bridging and Port Forwarding.
In the following illustration, it is assumed that users enable the DHCP
networking for the cascading chain comprising four devices. In the
diagrams, "M" is the master device and "S" is the slave device.
Illustration:
"Bridging" mode:

In this mode, the DHCP server communicates with every cascaded
device respectively and assigns four different IP addresses. Eachdevice has its own IP address.
The way to remotely access each cascaded device is completely thesame as accessing a standalone device in the network.

5Chapter 2: Cascading Modes"Port Forwarding" mode:

In this mode, the DHCP server communicates with the master device
alone and assigns one IP address to the master device. All slave
devices share the same IP address as the master device.
You must specify a 5XXXX port number (where X is a number) whenremotely accessing any slave device with the shared IP address. See
Port Number Syntax (on page 28).






Comparison between cascading modes:
The Bridging mode supports the wired network only, while the Port
Forwarding mode supports both wired and wireless networks.
Both cascading modes support a maximum of 16 devices in a chain.
Both cascading modes support both DHCP and static IP addressing.
In the Bridging mode, each cascaded device has a unique IP address.
In the Port Forwarding mode, all cascaded devices share the same IP
address(es) as the master device.

In the Bridging mode, each cascaded device has only one IP address.
In the Port Forwarding mode, each cascaded device can havemultiple IP addresses as long as the master device has multiple
network interfaces enabled/configured properly.
For example:

6



If the master device is a non-PX3-iX7 product, you can enable the
ETHERNET and WIRELESS interfaces so that thePort-Forwarding chain has one wired IP address and one
wireless IP address.



If the master device is a PX3-iX7 PDU, you can enable ETH1,
ETH2 and WIRELESS interfaces so that the Port-Forwarding
chain has two wired IP addresses and one wireless IP address.

Chapter 2: Cascading Modes

Setting the Cascading Mode
The cascading mode of all devices in the chain must be the same.
Warning: If any slave device's cascading mode is different from themaster device's, a networking failure occurs on that one and thesubsequent slave devices.
The cascading mode can be configured via the web interface orcommand line interface (CLI).
Only a user with the Change Network Settings permission can configure
the cascading mode.
Mode Change via Web Interface
Repeat the following procedure for each device you want to cascade until
all devices share the same cascading mode.
To set the cascading mode via the Web interface:1.

Connect the Raritan device to the LAN and find its IP address, orconnect it to a computer.
For computer connection instructions, see Connecting theRaritan device to a Computer (on page 60).



To find the IP address, see Finding the IP Address (on page 20).

2.

Log in to its web interface. See Login (on page 26).

3.

Choose Device Settings > Network.

4.

Select the preferred mode in the Cascading Mode field.
Mode

DescriptionNone

No cascading mode is enabled. This is thedefault.

Bridging

Each device in the cascading chain isaccessed with a different IP address.

Port Forwarding

Each device in the cascading chain isaccessed with the same IP address but with adifferent port number assigned.
For details on port numbers, see Port
Number Syntax (on page 28).

Tip: If selecting Port Forwarding, the Device Information page willshow a list of port numbers for all cascaded devices. Simply choose
Maintenance > Device Information > Port Forwarding.

7

Chapter 2: Cascading Modes5.

For the Port Forwarding mode, one to two more fields have to be
configured.
Note that if either setting below is incorrectly configured, anetworking issue occurs.
Field
Role
(available on allcascaded devices)
Downstream interface(available on the maser
device only)

Description

Master or Slave.
This is to determine which device is themaster and which ones are slave
devices.

USB or Ethernet (or ETH1/ETH2).
This is to determine which port on themaster device is connected to Slave 1.
Always select 'USB' for NON-PX3-iX7
product models, but you can selecteither 'USB' or 'ETH1/ETH2' for PX3-iX7
PDUs.
If ETH1 or ETH2 is selected, make surethe selected Ethernet interface isenabled.

6.

(Optional) Configure the network settings by clicking the BRIDGE,ETHERNET (ETH1/ETH2), or WIRELESS section on the same page.
See Configuration via Web Interface (on page 63).


In the Bridging mode, each cascaded device can have different
network settings. You may need to configure each device's
network settings in the BRIDGE section.

In the Port Forwarding mode, all cascaded devices share themaster device's network settings. You only need to configure themaster device's network settings in the ETHERNET (orETH1/ETH2) and/or WIRELESS section.

Tip: You can enable/configure multiple network interfaces in the Port
Forwarding mode so that the cascading chain has multiple IP
addresses.
7.

8

Click Save.

Chapter 2: Cascading Modes

Mode Change via CLI
Repeat the following procedure for each device you want to cascade until
all devices share the same cascading mode.
To set the cascading mode via CLI:
1.

Connect the Raritan device to the LAN and find its IP address, orconnect it to a computer.

2.

Log in to its CLI.


To use the SSH or Telnet service, see SSH/Telnet Access (onpage 27).

3.

Type config and press Enter to enter the configuration mode.

4.

Type the following command to set the cascading mode.
config:#network <mode> enabled <option1>

Variables:<mode> is one of the following cascading modes.
Mode

Description

bridgeThe Bridging mode, where each cascaded
device is assigned a unique IP address.

portForwarding

The Port Forwarding mode, where every
cascaded device in the chain shares thesame IP address, with diverse port
numbers assigned.

Important: When enabling either cascading mode, you must makesure the other cascading mode is disabled, or the preferredcascading mode may not be enabled successfully.
<option1> is one of the following options:
OptionDescriptiontrue

The selected cascading mode is enabled.

false

The selected cascading mode is disabled.

9

Chapter 2: Cascading Modes

If Port Forwarding mode is enabled, you must configure twomore settings to finish the configuration:
On ALL cascaded devices, you must configure the 'role' setting one byone.
config:#network portForwarding role <option2>

On the master device, you must configure the 'downstream interface'setting.
config:#network portForwarding
masterDownstreamInterface <option3>

Variables:




10

<option2> is one of the following cascading roles:
Role

Description

master

The device is a master device.

slave

The device is a slave device.

<option3> is one of the following options:
OptionDescription

Ethernet (orETH1/ETH2)

Ethernet (or ETH1/ETH2) port is the port
where the 1st slave device is connected.

Usb

USB port is the port where the 1st slave
device is connected.

Chapter 3

Cascading Raritan Devices
There are two cascading methods.
USB cascading: All devices in the chain are cascaded via USB ports.



All Raritan products described in this guide support this cascading
method.
Extended cascading: All devices in the chain are cascaded via either
USB or Ethernet ports. Only PX3-iX7 PDUs support this cascading
method.

In This Chapter
USB Cascading...........................................................................................11
Extended Cascading (for PX3-iX7 Only).....................................................15
Cascading Restrictions..............................................................................18

USB Cascading
All Raritan devices described in this guide support full-speed USB, whichtransfers data at a maximum rate of 12 Mbps.
PX3-iX7 supports high-speed USB so it can transfer data at a rate up to
480 Mbps.
USB communication is always half duplex.
Note that the USB bandwidth between the master and the first slave
device will limit the actual data transfer rate between all USB-cascadedslave devices.

Tip: If two or more PX3-iX7 PDUs are involved in a USB-cascading chain,
you can set them as the master and the first several slave devices for
optimal data transmission.
The distance between two USB-cascaded devices CANNOT exceed 5
meters (16 feet).

11Chapter 3: Cascading Raritan Devices

USB-Cascading Requirements
The USB-cascading chain comprises either identical or diverse Raritan
products. For example, you can cascade PX2 PDUs only, or you can mix
PX2, PX3, EMX, PX3TS and BCM devices in a USB-cascading chain.









Hardware requirements:
The USB-cascading chain must consist of the following Raritan
products.
Raritan products

Number of USB-A ports

PX2 series PDUs

1

PX3 series PDUs, including PX3-iX7

2

EMX devices

1

PX3TS transfer switches

2

BCM1

1

BCM2, including PMC models

2

If wireless networking is wanted, the master device must be a
product with two USB-A ports.
Software requirements:
Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10
firmware versions in terms of the cascading feature so all devices in
the cascading chain must run version 3.3.10 or later.
You can also choose to have the chain run a firmware version older
than 3.3.10. The disadvantage is that a pre-3.3.10 firmware version
supports a maximum of 8 cascaded devices rather than 16.

Check firmware versions before cascading Raritan devices and upgrade
any device as needed.
Warning: To upgrade an existing USB-cascading chain from afirmware version older than 3.3.10, you must start from the last slave
device and so on until the master device. Otherwise, a networking
issue occurs. See Upgrade Sequence in an Existing Cascading
Chain (on page 48).

12

Chapter 3: Cascading Raritan Devices

Cascading the Raritan devices via USB
Any certified USB 2.0 cable up to 16 feet (5 meters) long can be used.
For a list of Raritan products supporting the USB-cascading feature, see
USB-Cascading Requirements (on page 12).
You must set the cascading mode before establishing the chain. See
Setting the Cascading Mode (on page 7).

Tip: If your Raritan products are PX3-iX7 PDUs, you can cascade them via
either USB or Ethernet. See Cascading PX3-iX7 via Ethernet or USB(on page 16).
The following illustrates a USB-cascading chain.

13

Chapter 3: Cascading Raritan Devices

NumberDevice role
Master device
Slave 1
Slave 2
Slave 3

To cascade Raritan devices:
1.

Make sure all Raritan devices to be cascaded are running firmware
version 3.3.10 or later.

Important: To upgrade an existing USB-cascading chain from any
pre-3.3.10 firmware version to version 3.3.10 or later, follow theUpgrade Sequence in an Existing Cascading Chain (on page 48).
2.

Make sure all devices share the same cascading mode.

3.

Choose the appropriate one as the master device.

4.

Connect the master device to the LAN, using a method below.


Bridging mode:
Use a standard network patch cable (CAT5e or higher).

Port Forwarding mode:
Use a standard network patch cable and/or a Raritan USB WIFI
wireless LAN adapter. For information on the Raritan USB WIFI
adapter, see USB Wireless LAN Adapters (on page 70).

145.

Connect the USB-A port of the master device to the USB-B port of anadditional Raritan device via a USB cable. This additional device is
Slave 1.

6.

Connect Slave 1's USB-A port to the USB-B port of an additional
Raritan device via another USB cable. The second additional device is
Slave 2.

7.

Repeat the same step to connect more slave devices. You cancascade up to 15 slave devices.

Chapter 3: Cascading Raritan Devices

Extended Cascading (for PX3-iX7 Only)
Extended cascading can be made via USB or Ethernet interfaces on the
PX3-iX7 PDUs. PX3-iX7 supports high-speed USB so it can transfer data
at a rate up to 480 Mbps.
The following is the comparison between the two interfaces of PX3-iX7.
Item

Maximum rate or distance

Data transfer rate USB: 480 Mbps (half duplex)
 Ethernet: 100 Mbps (full duplex) USB: 5 meters (16 feet)
Cabling distance between two  Ethernet: 100 meters (328 feet)cascaded devices

Extended-Cascading Requirements
The extended-cascading chain must meet these requirements.

Hardware requirements:
All cascaded devices are PX3-iX7 PDUs.
Only these PDUs support extended cascading because they have dual
USB-A ports and dual Ethernet ports -- ETH1 and ETH2.



Software requirements:
All cascaded devices must run firmware version 3.3.10 or later.
This is because 'Ethernet' cascading is supported as of release
3.3.10.

15Chapter 3: Cascading Raritan Devices

Cascading PX3-iX7 via Ethernet or USB
Though PX3-iX7 PDUs support both USB- and Ethernet-cascading
connections, Ethernet cascading is recommended because of the longer
distance, lower latency and more reliable connection it supports.
You can use either Ethernet port on PX3-iX7 for cascading.
You must set the cascading mode before establishing the chain. See
Setting the Cascading Mode (on page 7).
When establishing a Port-Forwarding chain, make sure you follow theguidelines described in the section titled Unsupported Cascading
Connections for Port Forwarding (on page 50).
Special application: You can "loop" a cascading chain to create
network communication redundancy (Bridging mode only), but only
when your network supports R/STP protocol. Make sure that yournetwork has R/STP enabled if using a cascade loop (Bridging mode)or else network loops may occur.

16

Chapter 3: Cascading Raritan Devices

You can mix Ethernet and USB cascading in a PX3-iX7 chain if preferred.
The following diagram illustrates such a chain.

NumberDevice role
Master device
Slave 1
Slave 2
Slave 3For instructions on USB cascading, see Cascading the Raritan devices

via USB (on page 13).
To cascade PX3-iX7 PDUs via Ethernet ports:
1.

Make sure all Raritan devices to be cascaded are running firmware
version 3.3.10 or later.

17

Chapter 3: Cascading Raritan Devices

2.

Make sure all devices share the same cascading mode.

3.

Choose an appropriate PX3-iX7 PDU as the master device.

4.

Connect the master device to the LAN, using a method below.


Bridging mode:
Use a standard network patch cable (CAT5e or higher).

Port Forwarding mode:
Use a standard network patch cable and/or a Raritan USB WIFI
wireless LAN adapter. For information on the Raritan USB WIFI
adapter, see USB Wireless LAN Adapters (on page 70).

5.

Connect an available Ethernet port of the master device to either
Ethernet port of another PX3-iX7 via a standard network patch cable.
This additional PX3-iX7 is Slave 1.

6.

Connect Slave 1's available Ethernet port to either Ethernet port ofanother PX3-iX7 via a standard network patch cable. The second
additional PX3-iX7 is Slave 2.

7.

Repeat the same step to connect more PX3-iX7 slave devices. You
can cascade up to 15 slave devices.

Cascading Restrictions
General:All devices in the chain must run "compatible" firmware versions.
Note that firmware version 3.3.10 or later is NOT compatible withpre-3.3.10 firmware versions in terms of the cascading function.
USB-cascading chain:
All devices must run firmware version 3.3.10 or later, or all run
any firmware version earlier than 3.3.10.



Extended-cascading chain:
All PX3-iX7 PDUs must run firmware version 3.3.10 or later.

Warning: To upgrade an existing USB-cascading chain from afirmware version older than 3.3.10, you must start from the lastslave device and so on until the master device. Otherwise, anetworking issue occurs. See Upgrade Sequence in an Existing
Cascading Chain (on page 48).

The cascading mode of all devices in the chain must be the same.
Both cascading modes support a maximum of 16 devices in a chain.
Only the master device is connected to the LAN.
Do NOT connect slave devices to the LAN via a standard network
patch cable or a USB wireless LAN adapter.

18

Chapter 3: Cascading Raritan Devices









Appropriate networking methods vary based on the cascading mode.
See Setting the Cascading Mode (on page 7).


The Bridging mode supports the wired networking only.



The Port Forwarding mode supports both the wired and wirelessnetworking.

Your network switch's port security settings must support thecascading solution. Make sure that packets forwarding is enabled forthe "external" Ethernet port where the master device is connected.
Plug-and-play is no longer supported as of release 3.3.10 so you
CANNOT add, remove or swap cascaded devices in a chain randomly.
For the appropriate procedure, see Adding, Removing or Swapping
Cascaded Devices (on page 45).
Restrictions for the Bridging mode only:
In the Bridging mode, the master device can have "only one"connection to the network. If the master device is a PX3-iX7 PDU
with two Ethernet ports, DO NOT connect both ports to the network(s)unless your network has the R/STP protocol enabled.

Note: The Port Forwarding mode does NOT have this restriction. In
this mode, you can enable one wired and one wireless network
connections for non-PX3-iX7 products, or enable two wired and one
wireless network connections for PX3-iX7.

Restrictions for the "wireless" LAN (Port Forwarding mode):
You must use the Raritan USB WIFI wireless LAN adapter instead ofother WIFI adapters for wireless network connection.
No external USB hub is used with the master device.
To establish a USB-cascading chain, the master device must be a
Raritan product with two USB-A ports. This is because it requires
one USB-A port to connect the USB wireless LAN adapter and theother to connect a slave device.

19

Chapter 4

Accessing Raritan Devices
The master device functions as the network bridge and can transmit IP
packets between the LAN and all slave devices connected to it. Therefore,
you can remotely access the master and every slave device via the Web(http or https), SNMP, SSH, or Telnet interface.

In This Chapter
Finding the IP Address .............................................................................. 20
HTTP/HTTPS Access ................................................................................. 25
SSH/Telnet Access .................................................................................... 27
SNMP Management................................................................................... 27
Port Numbers for Port-Forwarding Devices ............................................ 28

Finding the IP Address
Before you can remotely access any Raritan device, you should first findits IP address(es).
There are three IP retrieval methods:

Access the local console.
Operate the front panel LCD display if the Raritan device is a PX3,
PX3-iX7, PX3TS, BCM or EMX device.
Use the device's MAC address and common networking tools.

20Chapter 4: Accessing Raritan Devices

Local Console
The IP address of the master or slave device is available in each device's
local console, which is the command line interface (CLI).
To access the local console, first connect the Raritan device to thecomputer using a serial RS-232 cable, and then use a terminal emulation
program on the computer to access it.
You can also access a master device's local console via a USB
connection. For details, see the Quick Setup Guide, Online Help or User
Guide, which can be downloaded from Raritan website's Support page(http://www.raritan.com/support/).
You can use any terminal emulation programs for local access to thecommand line interface.
This section illustrates HyperTerminal, which is part of Windows
operating systems prior to Windows Vista.
To get the IP address using HyperTerminal:
1.

Connect your computer to the Raritan device via a local connection.

2.

Launch HyperTerminal on your computer and open a console
window. When the window first opens, it is blank.
Make sure the COM port settings use this configuration:3.



Bits per second = 115200 (115.2Kbps)



Data bits = 8

Stop bits = 1

Parity = None

Flow control = None

In the communications program, press Enter to send a carriage
return to the Raritan device. Now you should see the Raritan device's
IP address displayed in the terminal.

LCD Display
Some Raritan products have a front panel LCD display which can show
its networking information.
Depending on the Raritan product you purchased, the LCD display typevaries.
PX3, PX3-iX7, and BCM2 models have a dot-matrix LCD display.
EMX, PX3TS and BCM1 have a character LCD display.

21

Chapter 4: Accessing Raritan Devices

Dot-Matrix LCD Display

The dot-matrix LCD display can show both IPv4 and IPv6 networking
information.
Note that the diagrams illustrated in this section are for Zero U models,
and your dot-matrix LCD display may look slightly different if it is on a 1U
or 2U model.
To retrieve the IPv4 and/or IPv6 addresses:
1.

2.

If the LCD display is in the Automatic mode, exit it by pressing/ordisplayed.

/

/

or

Press
and press

3.

22

/
Press
displayed.

/. The Main Menu similar to the following is/

to select "Device Info" in the Main Menu,.
until IPv4 and/or IPv6 address(es) of the device areChapter 4: Accessing Raritan Devices

The diagram illustrates the IP address screen in the 'Bridging' mode.
For information on the Port Forwarding mode, see Dot-Matrix LCD
Display (on page 40).

NumberDescription
Current cascading mode.
In the above diagram, it shows the Bridging mode.

IPv4/IPv6 network information, including: Network configuration: DHCP (or Automatic), or Static. Static
represents Static IP.
 The device's IP address.
 IPv4 subnet mask (such as "/24"), or IPv6 prefix length.
If you do not enable IPv4 or IPv6 settings, a message is displayed toindicate IPv4 or IPv6 is disabled.

23

Chapter 4: Accessing Raritan Devices

Character LCD Display

The IP address is available in the Device mode, which is indicated by thealphabet 'd' shown at the top of the LCD display. Note that this type of
LCD display only shows the IPv4 address (if available).
Below illustrates the IP address information.

SectionExample information"d" means the LCD display has entered the Device
mode.
The LCD display is showing 192, which is one of
the four IP address octets. It will cycle throughfour octets.
"i4" indicates that the IP address shown on the
LCD display is an IPv4 address.
The word "MASTER" indicates the Raritan device
is the master device in a cascading chain.
For a slave device, it shows "SLAVE" instead.

Note: As of release 3.3.10, the "MASTER/SLAVE"
information is no longer available in the Bridging
mode, but remains available in the Port
Forwarding mode.
If you connect your Raritan device to the wireless network, a Wi-Fi icon isdisplayed at the bottom-right corner.

24

Chapter 4: Accessing Raritan Devices

To display the IPv4 address:
1.

Press the MODE button to enter the Device mode, indicated by analphabet "d" at the top left of the display.

2.

The LCD display cycles between the four octets of the IPv4 address,
indicated by "i4" at the upper right corner of the display.
For example, 192.168.84.4 cycles in this sequence:

192 --> 168 --> 84 --> 4

MAC Address
A label is affixed to the Raritan device, showing both the serial number
and MAC address.

If necessary, you can find its IP address through the MAC address byusing commonly-used network tools. Contact your LAN administrator forassistance.

HTTP/HTTPS Access
You can remotely access the web interface of any Raritan device in acascading chain by using a web browser. See Supported Web Browsers(on page 25) for a list of supported web browsers.
Supported Web Browsers
The following web browsers can be used to access a Raritan device’s
web interface. For details, see the online help or User Guide for your
Raritan device.








Internet Explorer®
Windows Edge
Firefox®
Safari®
Google® Chrome®
Android
IOS

25

Chapter 4: Accessing Raritan Devices

Login
You must enable JavaScript in the web browser for proper operation.
To log in to the web interface:
1.

Open a browser and type the IP address of the Raritan device.

Note: The address to access a slave device in the Port Forwarding
mode via non-standard ports is a combination of a protocol (http://
or https://), an IP address and a port number. See Port Forwarding
Examples (on page 30).

26

2.

If any security alert message appears, accept it.

3.

The login screen displays. Type your user name and password. User
credentials are case sensitive.

4.

(Optional) If a security agreement is displayed, accept it. Otherwise,
you cannot log in.

5.

Click Login or press Enter. The Raritan device web interface opens.

Chapter 4: Accessing Raritan Devices

SSH/Telnet Access
All devices in the cascading chain support the SSH or Telnet service.
You can remotely log in to the command line interface (CLI) using an SSH
or Telnet client, such as PuTTY.

Note: PuTTY is a free program you can download from the Internet. See
PuTTY's documentation for details on configuration.
To log in using SSH or Telnet:
1.

Ensure SSH or Telnet has been enabled.

2.

Launch an SSH or Telnet client and open a console window. A login
prompt appears.

3.

Type a name and press Enter. The name is case sensitive.

Note: If using the SSH client, the name must NOT exceed 25
characters. Otherwise, the login fails.
Then you are prompted to enter a password.

4.

Type a password and press Enter. The password is case sensitive.

5.

After properly entering the password, the # or > system prompt
appears.

Tip: The "Last Login" information, including the date and time, isalso displayed if the same user profile was used to log in to thisproduct's web interface or CLI.
6.

You are now logged in to the command line interface and can begin
administering the Raritan device.

SNMP Management
In the cascading chain, the SNMP capability of each Raritan device
remains unchanged. A cascaded device is able to send SNMP
notifications and communicate with an SNMP manager.

27

Chapter 4: Accessing Raritan Devices

SNMP Notifications
A Raritan device in the cascading chain can send out SNMP traps orinforms to an SNMP destination like a standalone Raritan device. All you
have to do is to configure the SNMP notification setting on that device.
For details, see "Configuring SNMP Settings" in the online help, which isaccessible from the application or on the Raritan website's Support
page (http://www.raritan.com/support/ ).
Third-Party SNMP Managers
A third-party SNMP manager can communicate with any Raritan device
in the cascading chain. There are no differences made to the SNMP
accessibility no matter the device is a master or slave device.
To allow a Raritan device to communicate with an SNMP manager, youmust enable the SNMP agent implemented on that device and download
the latest SNMP MIB for your SNMP manager. For details, see "Enabling
and Configuring SNMP" in the online help, which is accessible from theapplication or on the Raritan website's Support page(http://www.raritan.com/support/).

Port Numbers for Port-Forwarding Devices
All devices in a Port-Forwarding chain share the same IP address(es).
Therefore, a port number is required when accessing any device in the
chain.
Port Number Syntax
In the Port Forwarding mode, all devices in the cascading chain sharethe same IP address. To access any cascaded device, you must assign anappropriate port number to it.





28

Master device: The port number is either 5NNXX or the standard
TCP/UDP port.
Slave device: The port number is 5NNXX.
5NNXX port number syntax:
NN is a two-digit number representing the network protocol asshown below:
Protocols

NN

HTTPS

00

HTTP

01

Chapter 4: Accessing Raritan Devices

Protocols

NN

SSH

02

TELNET

03

SNMP

05

MODBUS

06

XX is a two-digit number representing the device position as shown
below.
PositionXX

Master device

00
01

Slave 1

02

Slave 203

Slave 304

Slave 405

Slave 506

Slave 607

Slave 7

Position
Slave 8
Slave 9Slave 10
Slave 11
Slave 12
Slave 13
Slave 14
Slave 15

XX
08
09
10
11
12
13
14
15

For example, to access the Slave 4 device via Modbus/TCP, the port
number is 50604. See Port Forwarding Examples (on page 30) for
further illustrations.

Tip: The full list of each cascaded device's port numbers can be retrieved
from the web interface. Choose Maintenance > Device Information > Port
Forwarding.
Standard TCP/UDP ports:
The master device can be also accessed through standard TCP/UDP
ports as listed in the following table.
Protocols

Port Numbers

HTTPS

443

HTTP

80

29

Chapter 4: Accessing Raritan Devices

Protocols

Port Numbers

SSH

22

TELNET

23

SNMP

161

MODBUS

502

In the Port Forwarding mode, the Raritan device does NOT allow you tomodify the standard TCP/UDP port configuration, including HTTP, HTTPS,
SSH, Telnet and Modbus/TCP.
Port Forwarding Examples
To access a cascaded device in the Port Forwarding mode, assign a port
number to the IP address.


Master device: Assign proper 5NNXX port numbers or standard
TCP/UDP ports. See Port Number Syntax (on page 28) for details.
Slave device: Assign proper 5NNXX port numbers.

Assumption: The Port Forwarding mode is applied to a cascading chain
comprising three Raritan devices. The IP address is 192.168.84.77.
Master device:
Position code for the master device is '00' so each port number is 5NN00
as listed below.
Protocols

Port numbers

HTTPS

50000

HTTP

50100

SSH

50200

TELNET

50300

SNMP

50500

MODBUS

50600

Examples using "5NN00" ports:
To access the master device via HTTPS, the IP address is:

To access the master device via HTTP, the IP address is:https://192.168.84.77:50000/
http://192.168.84.77:50100/

30

Chapter 4: Accessing Raritan Devices

To access the master device via SSH, the command is:ssh -p 50200 192.168.84.77
Examples using standard TCP/UDP ports:
To access the master device via HTTPS, the IP address is:https://192.168.84.77:443/
To access the master device via HTTP, the IP address is:

http://192.168.84.77:80/


To access the master device via SSH, the command is:ssh -p 22 192.168.84.77
Slave 1 device:
Position code for Slave 1 is '01' so each port number is 5NN01 as shown
below.
Protocols

Port numbers

HTTPS

50001

HTTP

50101

SSH

50201

TELNET

50301

SNMP

50501

MODBUS

50601

Examples:

To access Slave 1 via HTTPS, the IP address is:https://192.168.84.77:50001/


To access Slave 1 via HTTP, the IP address is:

http://192.168.84.77:50101/


To access Slave 1 via SSH, the command is:ssh -p 50201 192.168.84.77
Slave 2 device:
Position code for Slave 2 is '02' so each port number is 5NN02 as shown
below.
Protocols

Port numbers

HTTPS

50002

HTTP

50102

31

Chapter 4: Accessing Raritan Devices

Protocols

Port numbers

SSH

50202

TELNET

50302

SNMP

50502

MODBUS

50602

Examples:

To access Slave 2 via HTTPS, the IP address is:https://192.168.84.77:50002/


To access Slave 2 via HTTP, the IP address is:

http://192.168.84.77:50102/


To access Slave 2 via SSH, the command is:ssh -p 50202 192.168.84.77

32

Chapter 5

Identifying Cascaded Devices
You can retrieve a device's cascading status from one of theseinterfaces:Web interface: Accessible via HTTP or HTTPS.
Command line interface (CLI): Accessible via SSH, Telnet or theserial interface.
SNMP: An SNMP manager is required.
LCD display: Use the front panel LCD display if your Raritan device
has it.

Before remotely accessing a Raritan device, you need to get its IP
address. See Finding the IP Address (on page 20).

In This Chapter
Using the Web Interface............................................................................ 33
Using the CLI ............................................................................................. 36
Using the SNMP ........................................................................................ 38
Using the LCD Display............................................................................... 40

Using the Web Interface
This section explains how to identify a cascaded device through the webinterface.
The following only introduces the web interface of firmware version
3.3.10 or later, which is different from old firmware versions.
1.

Log in to the desired Raritan device using a supported web browser.
See HTTP/HTTPS Access (on page 25).

2.

Choose Maintenance > Device Information.

3.

Click the Network title bar.



If the information shown on this page does not match the latest
status, press F5 to reload it.

33

Chapter 5: Identifying Cascaded Devices



Cascading information in the Bridging mode:
The Common section contains two read-only fields for indicating thecascading status. Note that the cascading position is NOT available
in the Bridging mode.
FieldsPort Forwarding

Description
Indicates the Port Forwarding is disabled. See

Setting the Cascading Mode (on page 7).
BRIDGE section

Indicates the device is in the Bridging mode and its
IP address.

Cascading information in the Port Forwarding mode:
The Common section contains three read-only fields for indicating
the cascading status.
FieldsDescription

Port Forwarding

Indicates the Port Forwarding is enabled. See
Setting the Cascading Mode (on page 7).

Cascade Position Indicates the position of the Raritan device in the
cascading chain.
 0 (zero) represents the master device.
 A non-zero number represents a slave device. 1
is Slave 1, 2 is Slave 2, 3 is Slave 3 and so on.

34

Chapter 5: Identifying Cascaded Devices

FieldsDescription

Cascaded Device
Connected

Indicates whether a slave device is detected on the
USB-A or Ethernet port.
 yes: Connection to a slave device is detected.
 no: NO connection to a slave device is detected.

A master device shows 0 (zero) in the Cascade Position field andyes in the Cascaded Device Connected field.



A slave device in the middle position shows a non-zero number
which indicates its exact position in the Cascade Position field
and yes in the Cascaded Device Connected field.
The following diagram shows 1, indicating it is the first slave Slave 1.

35Chapter 5: Identifying Cascaded Devices



The final slave device shows a non-zero number which indicatesits position in the Cascade Position field and no in the Cascaded
Device Connected field.
The following diagram shows 2, indicating it is the second slave Slave 2. The Cascaded Device Connected field shows no,
indicating that it is the final one in the chain.

For a list of port numbers required for accessing each cascaded
device in the Port Forwarding mode, click the Port Forwarding title
bar on the same page.

Using the CLIThis section explains how to identify a cascaded device through CLI.
The following only introduces the CLI commands of firmware version
3.3.10 or later, which are different from old firmware versions.
1.

Log in to the CLI of the desired cascaded device. To use the SSH or
Telnet service, see SSH/Telnet Access (on page 27).

2.

Type the following CLI commands and press Enter.
#36

show network

Chapter 5: Identifying Cascaded Devices

In the Bridging mode:
In the Bridging mode, IP-related information is shown under the'BRIDGE' interface, similar to the following.

In the Port Forwarding mode:
In the Port Forwarding mode, the Port Forwarding status shows'Enabled'.

The 'Role' or 'Slave number' field indicates the device's position.
For a master device, the Role field shows 'Master'.

For a slave device, the Role field shows 'Slave'. The 'Slave
number' field indicates its position: 1 is the first slave device, 2 isthe second, and so on.

37

Chapter 5: Identifying Cascaded Devices

Using the SNMP
The unitConfigurationTable in MIB contains entries for cascading
information. One SNMP MIB manager, such as a MIB browser, isrequired for retrieving the SNMP data.
As of release 3.3.10, cascading information other than the cascading
mode is no longer available in the Bridging mode, but all cascading
information remains available in the Port Forwarding mode.
In the Port Forwarding mode:
1.

Launch your SNMP MIB manager and connect to the desired Raritan
device.

2.

To find whether the Raritan device is in a cascading chain, retrieve
the value of either one below:


SNMP name - pduDaisychainMemberType



SNMP object identifier (OID) - 1.3.6.1.4.1.13742.6.3.2.2.1.41

One of the following values is returned.

3.

SNMP value

Description

standalone (0)The Raritan device is not in the cascading chain.
It is a standalone device.

master (1)The Raritan device is the master device.

slave (2)The Raritan device is a slave device.

To check which cascading mode is applied, retrieve the value ofeither one below:


SNMP name - deviceCascadeType



SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.70

One of the values in the following table is returned.
SNMP value

Cascading mode0

Bridging mode

1

Port Forwarding mode

The value 1 is returned in the Port Forwarding mode.
4.

To identify the device's position in the cascading chain, retrieve thevalue of either one below:


SNMP name - deviceCascadePosition



SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.71

One of the following values is returned.

38

Chapter 5: Identifying Cascaded Devices

5.

SNMP value

Device position0

Master device

1 to 15

Slave 1 to Slave 15

To find whether the Raritan device is the final slave device, retrieve
the value of either one below:


SNMP name - cascadedDeviceConnected

SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.58

Check which value is returned. A final slave device has NO slave
device connected to its Ethernet (ETH1 or ETH2) or USB-A port.
SNMP value

Description

true (1)A slave device has been connected to either
Ethernet or USB-A port of this Raritan device.

false (2)No slave device is connected to either Ethernetor USB-A port of this Raritan device.

In the Bridging mode:
1.

Launch your SNMP MIB manager and connect to the desired Raritan
device.

2.

To check which cascading mode is applied, retrieve the value ofeither one below:


SNMP name - deviceCascadeType



SNMP OID - 1.3.6.1.4.1.13742.6.3.2.2.1.70

One of the values in the following table is returned.
SNMP value

Cascading mode0

Bridging mode

1

Port Forwarding mode

The value 0 is returned in the Bridging mode.
3.

The following cascading information is NOT available in the Bridging
mode so they always show a permanent value, which CANNOT
correctly indicate the current cascading status.
 pduDaisychainMemberType(1.3.6.1.4.1.13742.6.3.2.2.1.41) always shows'standalone (0)'
 deviceCascadePosition(1.3.6.1.4.1.13742.6.3.2.2.1.71) always shows'Master device (0)'39Chapter 5: Identifying Cascaded Devices

cascadedDeviceConnected(1.3.6.1.4.1.13742.6.3.2.2.1.58) always shows 'false(2)'

Using the LCD Display
Some Raritan products have a front panel LCD display which can show
cascading information, such as the device position.
Depending on the Raritan product you purchased, the LCD display typevaries.
PX3, PX3-iX7, and BCM2 models have a dot-matrix LCD display.
EMX and BCM1 have a character LCD display.

Dot-Matrix LCD Display
On the dot-matrix LCD display, available cascading information depends
on the cascading mode.
Note that the diagrams illustrated in this section are for Zero U models,
and your dot-matrix LCD display may look slightly different if it is on a 1U
or 2U model.
1.

2.

If the LCD display is in the Automatic mode, exit it by pressing/ordisplayed.

/

/

or

Press
and press

3.

40

Press

/
/

. The Main Menu similar to the following is/

to select "Device Info" in the Main Menu,.
until the Network Cascading page displays.

Chapter 5: Identifying Cascaded Devices

Bridging mode:
In this mode, the LCD display only indicates the Bridging mode isenabled, but the device position information is NOT available.

NumberDescription
Current cascading mode.
In the above diagram, it shows the Bridging mode.

IPv4/IPv6 network information, including: Network configuration: DHCP (or Automatic), or Static. Static
represents Static IP.
 The device's IP address.
 IPv4 subnet mask (such as "/24"), or IPv6 prefix length.
If you do not enable IPv4 or IPv6 settings, a message is displayed toindicate IPv4 or IPv6 is disabled.
Port Forwarding mode:
In this mode, the LCD display indicates the cascading mode, device
position and the presence/absence of a connected slave device.

41

Chapter 5: Identifying Cascaded Devices

42Chapter 5: Identifying Cascaded Devices

NumberDescription
Cascading mode-related information, including: Port Forwarding mode
 Maser or Slave Cascade position -- This information is available on slave
devices only.
1 represents the first slave, 2 represents the second slave,and the like.
 Slave Connected: yes indicates a downstream slave device is
detected, and no indicates no downstream slave devices aredetected.
The master device's IPv4/IPv6 address.

Character LCD Display
Note: As of release 3.3.10, the following cascading information is nolonger available in the Bridging mode, but remains available in the
Port Forwarding mode.
A cascaded device's position is available by operating the LCD display.
Below illustrates a slave device's position.

SectionExample information"d" means the LCD display has entered the Device mode.
"CA" indicates that the cascading information is being
displayed.

43

Chapter 5: Identifying Cascaded Devices

SectionExample information"SLAVE" indicates that this Raritan device is a slave
device.

Note: For a master device, it shows the word "MASTER"
instead.
The number 1 means the device position is Slave 1.
To retrieve the device's cascading position information:
1.

Press the MODE button to enter the Device mode, indicated by a 'd'in at the top left of the display.

2.

Press the FUNC button until "CA" is displayed at the top right of thedisplay.

3.

The device's position is represented by any number defined below:
Number
0
1
2
3
4
5
6
7

44

Device position
Master device
Slave 1
Slave 2
Slave 3
Slave 4
Slave 5
Slave 6
Slave 7

Number
8
9
10
11
12
13
14
15

Device position
Slave 8
Slave 9Slave 10
Slave 11
Slave 12
Slave 13
Slave 14
Slave 15

Chapter 6

Adding, Removing or Swapping
Cascaded Devices
Change the cascading mode first before adding any device to a cascading
chain, or before disconnecting a cascaded device from the chain.
If you only want to change the cascading mode of an existing chain, or
swap the master and slave device, always start from the slave device.

Note: If the following procedures are not followed, a networking issue
occurs. When a networking issue occurs, check the cascading
connection and/or software settings of all devices in the chain. See
Cascading Troubleshooting (on page 53).
To add a device to an existing chain:
1.

Connect the Raritan device to the LAN and find its IP address, orconnect it to a computer.

2.

Log in to this device and set its cascading mode to be the same as
the existing chain's cascading mode. See Setting the Cascading
Mode (on page 7).

3.

Connect it to the chain, using either USB or Ethernet cable.
To remove a device from the chain:

1.

Log in to the desired cascaded device, and change its cascading
mode to None.

Exception: If you are going to connect the removed device to anothercascading chain, set its cascading mode to be the same as thecascading mode of another chain.
2.





Now disconnect it from the cascading chain.
To swap the master and slave device:
In the Bridging mode, you can swap the master and slave devices bysimply disconnecting ALL cascading cables from them, and thenreconnecting cascading cables. No changes to software settings are
required.
In the Port Forwarding mode, you must follow the procedure below:a. Access the slave device that will replace the master device, andset its role to 'Master', and correctly set the downstream
interface.
b. Access the master device, set its role to 'Slave'.
c.

Swap the master and slave device now. You must disconnect ALL
cascading cables connected to the two devices first before
swapping them and reconnecting cascading cables.

45

Chapter 6: Adding, Removing or Swapping Cascaded Devices

To change the cascading mode applied to a chain:
1.

Access the last slave device, and change its cascading mode.
46

If the new cascading mode is 'Port Forwarding', you must also
set its role to 'Slave'.

2.

Access the second to last, third to last and so on until the first slave
device to change their cascading modes one by one.

3.

Access the master device, and change its cascading mode.

4.

If the new cascading mode is 'Port Forwarding', you must also set its
role to 'Master', and correctly select the downstream interface.

Chapter 7

Firmware Upgrade
You can upgrade each individual Raritan device in the cascading chain
through the web interface. The upgrade procedure is completely
identical to the procedure for a standalone Raritan device.
Firmware version 3.3.10 or later is NOT compatible with pre-3.3.10
firmware versions in terms of the cascading feature so all devices in the
cascading chain must run version 3.3.10 or later.
To upgrade an existing USB-cascading chain from a firmware version
older than 3.3.10, you must start from the last slave device and so on
until the master device. Otherwise, a networking issue occurs.

In This Chapter
Updating the Raritan device Firmware ..................................................... 47
Upgrade Sequence in an Existing Cascading Chain ................................. 48

Updating the Raritan device Firmware
Firmware files are available on Raritan website's Support page(http://www.raritan.com/support/).
To update the firmware:1.

Choose Maintenance > Update Firmware.

2.

Click

3.

Click Upload. A progress bar appears to indicate the upload process.

4.

Once complete, information of both installed and uploaded firmware
versions as well as compatibility and signature-checking results are
displayed.
5.

to select an appropriate firmware file.

If anything is incorrect, click Discard Upload.

To proceed with the update, click Update Firmware.

Warning: Do NOT power off the Raritan device during the update.
6.

When the update is complete, the Raritan device resets, and the
Login page re-appears.

Important: If you are using the Raritan device with an SNMP
manager, download its MIB again after the firmware update toensure your SNMP manager has the correct MIB for the latest
release you are using.

47

Chapter 7: Firmware UpgradeUpgrade Sequence in an Existing Cascading Chain
Depending on the firmware version(s) of your cascading chain, there may
or may not be limitations for the firmware upgrade sequence in the
chain.
Upgrade from any "pre-3.3.10" firmware version to version
3.3.10 or later:
You must follow the firmware upgrade sequence below to upgrade acascading chain from a firmware version older than 3.3.10 to version
3.3.10 or later. If you do not follow this upgrade sequence, you will
not be able to access some cascaded devices over the Internet.


The upgrade must start from the last slave device (S), then thesecond to last, the third to last, and so on until the master device(M).
Red numbers below represent the appropriate upgrade sequence.
'N' is the final one to upgrade.

You must upgrade ALL devices in the chain to 3.3.10 or later. If
you upgrade only some devices in the chain, networking issues
occur on some cascaded devices.

Upgrade from firmware version 3.3.10 or later to any post-3.3.10
version:
There is no upgrade sequence limitation.
Firmware version 3.3.10 is compatible with later firmware versions
so you can upgrade all devices of the chain in a random order.
Important: Raritan does not guarantee that no upgrade sequence
limitation will be required for all future firmware versions. It ishighly suggested to check the latest revision of the Cascading Guideor your product's User Guide before upgrading an existing chain
from version 3.3.10 or later to any post-3.3.10 version.

48

Chapter 7: Firmware UpgradeUpgrade from a pre-3.3.10 firmware version to any pre-3.3.10
version:
There is no upgrade sequence limitation.
Firmware versions earlier than 3.3.10 are compatible with each otherso you can upgrade all devices of the chain in a random order.

49

Appendix A Unsupported Cascading Connections
for Port Forwarding
The following guidelines must be obeyed for establishing a cascading
chain in the Port Forwarding mode.
Each cascaded device, except for the master device, must have only
one upstream device.
Each cascaded device, except for the last slave device, must have
only one downstream device.
Use only one cable to cascade two devices. That is, NO simultaneousconnection of USB and Ethernet cables between two cascaded
devices.

The following diagrams illustrate cascading connections that are NOT
supported.



UNSUPPORTED connections:
One cascaded device has two upstream devices via Ethernet cables.

50Appendix A: Unsupported Cascading Connections for Port ForwardingOne cascaded device has two upstream devices via Ethernet andUSB cables.

One cascaded device has two downstream devices.

51

Appendix A: Unsupported Cascading Connections for Port Forwarding52

One device is connected to another device via two cascading cables USB and Ethernet cables.

Appendix B Cascading Troubleshooting
Any accessibility problem occurred on one of the devices in the
cascading chain may result in failure to access all downstream slave
devices that are connected to it.

In This Chapter
Possible Root Causes................................................................................ 53
Port-Forwarding Slave Device Events ...................................................... 56
The Ping Tool............................................................................................. 56

Possible Root Causes
The following lists the network accessibility issues and possible root
causes.
You can always troubleshoot the software settings by connecting theRaritan device to a computer if network access to that Raritan device
fails. See Connecting the Raritan device to a Computer (on page 60).

53

Appendix B: Cascading Troubleshooting

Symptom

Probable cause

Failure to access the masterdevice









54

Anything below is lost on the master device:Network connection

Power supply

Anything below is disabled on the master device:The Ethernet or wireless interfaceIPv4 or IPv6 settings

In the Port Forwarding mode, related settings areincorrectly configured on the master device.
The master device's role is incorrectly set to 'Slave'.



The interface where the network is connected isincorrectly set as the downstream interface.

For the wireless networking, one of the following issues
occurs:

The USB wireless LAN adapter attached to themaster device is not the Raritan USB WIFI LAN
adapter. See USB Wireless LAN Adapters (on page70).

The wireless LAN configuration is not supported. See
Supported Wireless LAN Configuration (on page70).

The installed CA certificate chain contains any
certificate that has expired or is not valid yet.

Appendix B: Cascading Troubleshooting

Symptom

Probable cause

Failure to access a slave device One of the following issues occurs on the master device:Network connection is lost.



The Ethernet or wireless interface is disabled.

One of the following issues occurs on the slave device inquestion or any upstream device (if available):Connection of the cascading cable is loose or lost.

No power supply.

The cascading mode is set incorrectly.
For example, the master device is set to Bridging, but
the slave device in question or any upstream device is
set to Port Forwarding.

In the Bridging mode, IPv4 (or IPv6) settings are disabledon the slave device in question.
In the Port Forwarding mode, one of the following issues
occurs:

The master device's role is incorrectly set to 'Slave'.



The master device's downstream interface isincorrectly set. For example, you use a USB cable toconnect the 1st slave device, but select the Ethernet
port as the downstream interface.

The role of the slave device in question or any
upstream device is set to 'Master' instead of 'Slave'.



The port number you added to the IP address isincorrect. See Port Number Syntax (on page 28).



IPv4 (or IPv6) settings are disabled on the masterdevice.

The slave device in question or any upstream device runs
a "pre-3.3.10" firmware version while the rest of thechain runs firmware version 3.3.10 or later.

55

Appendix B: Cascading Troubleshooting

Tip: To determine which Raritan device may be the failure point of
network, you may ping each Raritan device in the cascading chain, orcheck the slave-related events in the event log of each Raritan device.
See The Ping Tool (on page 56) and Port-Forwarding Slave Device
Events (on page 56).



For a PX3-iX7 cascading chain, also check the following:
Whether the Ethernet interface (ETH1 or ETH2) where the network or
cascading cable is connected is disabled on the cascaded device inquestion or any upstream device.
Whether the connection complies with the cascading guidelines if it
is set to the Port Forwarding mode. See Unsupported Cascading
Connections for Port Forwarding (on page 50).

Port-Forwarding Slave Device Events
In the Bridging mode, events regarding connection/disconnection of adownstream slave device via USB is NOT logged.
However, in the Port Forwarding mode, whenever the connection or
disconnection of a downstream slave device via USB is detected, theRaritan device at the USB-A end of the USB cable logs it in the internallog. Note that the Raritan device at the USB-B end of the cable does NOT
log these events.
There are two slave-related events in the Port Forwarding mode:
Event

Description

Slave connected

This log entry is generated when a Raritan device
detects the presence of a slave device on its USB-A
port.

Slave
disconnected

This log entry is generated when it detects thedisconnection of a slave device from its USB-A
port.

The Ping Tool
The Raritan device provides a ping tool in the web interface and CLI so
you can ping any host or Raritan device in your data center.

56

Appendix B: Cascading Troubleshooting

Ping via the Web Interface
To log in to the web interface, see Login (on page 26).
The Ping tool is useful for checking whether a host is accessible throughthe network or Internet.
To ping a host:
1.

Choose Maintenance > Network Diagnostics.

2.

Type values in the following fields.

3.

Field

Description

Network Host

The name or IP address of the host that you want
to check.

Number ofRequests

A number up to 20.
This determines how many packets are sent forpinging the host.

Click Run Ping to ping the host. The Ping results are then displayed.

57

Appendix B: Cascading Troubleshooting

Ping via the CLI
You can access the CLI interface by connecting a computer to the Raritan
device or using SSH/Telnet. See SSH/Telnet Access (on page 27) for
details.
You must perform the ping command in the diagnostic mode. To enter
the diagnostic mode, type the following command and press Ener.
#

diag

After the diag> or diag# prompt appears, you can perform the pingcommand.
This ping command sends the ICMP ECHO_REQUEST message to a
network host for checking its network connectivity. If the output shows
the host is responding properly, the network connectivity is good. If not,either the host is shut down or it is not being properly connected to the
network.
diag>ping <host>

Variables:<host> is the host name or IP address whose networking connectivity
you want to check.

Options:

58

You can include any or all of additional options listed below in theping command.
Options

Description

count <number1>

Determines the number of messages to be
sent. <number1> is an integer number
between 1 and 100.

size <number2>

Determines the packet size. <number2> is an
integer number in bytes between 1 and
65468.

timeout <number3>

Determines the waiting period before
timeout. <number3> is an integer number inseconds ranging from 1 to 600.

Appendix B: Cascading Troubleshooting

The command looks like the following when it includes all options:diag>ping <host> count <number1> size <number2> timeout <number3>

59

Appendix C Additional Information

In This Chapter
Connecting the Raritan device to a Computer.......................................... 60
Configuring Network Settings...................................................................63
Wireless LAN Information......................................................................... 70

Connecting the Raritan device to a Computer
To change the cascading mode of any Raritan device, you can connect itto the computer via one of the following ports on the Raritan device.
USB-B port (male)ETHERNET port (female)
RS-232 serial port (model dependent -- male DB9 or female RJ-45
connector)

To use the command line interface (CLI) for configuration, establish an
RS-232 or USB connection.
To use a web browser for configuration, make a network connection to
the computer. The Raritan device is automatically configured with thefollowing link-local addressing in any network without DHCP available:https://169.254.x.x (where x is a number)
https://pdu.local

Making a Connection
Establish one of the following connections to a computer.
Serial connection for "DB9" RS-232 connector on Raritan device:1.

Connect one end of the null-modem DB9 cable to the male "DB9"RS-232 port labeled CONSOLE / MODEM on the Raritan device.

2.

Connect the other end to your computer's RS-232 port (COM).

60

Appendix C: Additional Information

Serial connection for "RJ-45" RS-232 connector on PX3-iX7:
The PX3-iX7 PDU's serial connection procedure is the same as above
except that a third party RJ-45 to "DB9 female" adapter/cable isrequired, such as the blue Cisco adapter cable. This is because the
CONSOLE / MODEM port on PX3-iX7 is a female RJ-45 connector.
USB connection:

1.

A USB-to-serial driver is required in Windows®. Install this driver
before connecting the USB cable. See Installing the USB-to-Serial
Driver (Optional) (on page 61).

2.

Connect a USB cable between the Raritan device device's USB-B
port and a computer's USB-A port.
Direct network connection:

The Ethernet port must be enabled for this connection to work properly.
Per default, the Ethernet port is enabled.
1.

Connect one end of a standard network patch cable to the
ETHERNET port of the Raritan device.


For PX3-iX7, either Ethernet port is fine.

2.

Connect the other end to a computer's Ethernet port.

3.

On the connected computer, launch a web browser to access theRaritan device, using either link-local addressing: pdu.local or
169.254.x.x.

Installing the USB-to-Serial Driver (Optional)
The Raritan device can emulate a USB-to-serial converter over a USB
connection. A USB-to-serial driver named "Dominion PX2 (or EMX)Serial
Console" is required for Microsoft® Windows® operating systems.
Download the Windows driver for USB serial console from the Raritan
website's Support page (http://www.raritan.com/support/). The
downloaded driver's name is dominion-serial-setup-<n>.exe, where <n>represents the file's version number.
There are two ways to install this driver: automatic and manual
installation. Automatic driver installation is highly recommended.
Automatic driver installation in Windows®:
1.

Make sure the Raritan device is NOT connected to the computer via a
USB cable.

2.

Run dominion-serial-setup-<n>.exe on the computer and follow
online instructions to install the driver.

61

Appendix C: Additional Information

Note: If any Windows security warning appears, accept it to continue
the installation.
3.

Connect the Raritan device to the computer via a USB cable. The
driver is automatically installed.
Manual driver installation in Windows®:

1.

Make sure the Raritan device has been connected to the computer
via a USB cable.

2.

The computer detects the new device and the "Found New Hardware
Wizard" dialog appears.
3.

If this dialog does not appear, choose Control Panel > System >Hardware > Device Manager, right-click the Dominion PX2 (orEMX)Serial Console, and choose Update Driver.

Select the option of driver installation from a specific location, andthen specify the location where both dominion-serial.inf anddominion-serial.cat are stored.

Note: If any Windows security warning appears, accept it to continue
the installation.
4.

Wait until the installation is complete.

Note: If the Raritan device enters the disaster recovery mode when the
USB serial driver is not installed yet, it may be shown as a 'GPS camera'in the Device Manager on the computer connected to it.
In Linux:
No additional drivers are required, but you must provide the name of thetty device, which can be found in the output of the "dmesg" afterconnecting the Raritan device to the computer. Usually the tty device is"/dev/ttyACM#" or "/dev/ttyUSB#," where # is an integer number.
For example, if you are using the kermit terminal program, and the tty
device is "/dev/ttyACM0," perform the following commands:> set line /dev/ttyACM0> Connect

62Appendix C: Additional Information

Configuring Network Settings
Network settings can be configured through either the web interface orcommand line interface (CLI). This appendix only shows basic operation.
For details, see the online help or User Guide for your Raritan device.
In the Bridging mode, each cascaded device can have different
network settings. You may need to configure each device's
network settings in the BRIDGE section.

In the Port Forwarding mode, all cascaded devices share themaster device's network settings. You only need to configure themaster device's network settings in the ETHERNET (orETH1/ETH2) and/or WIRELESS section.

Configuration via Web Interface
When you are able to connect to the master or slave device over Internet,
you can access its web interface to change the network settings.
Note that all slave devices share the master device's IP address(es) in
the Port-Forwarding mode. To access a Port-Forwarding slave device,
you must add a port number to the end of the IP address. See Port
Numbers for Port-Forwarding Devices (on page 28).
To change initial network settings:
1.

Launch a web browser and type the IP address of the Raritan device
in the address bar.

2.

Accept any warnings that may appear and log in to that Raritan
device using the administrator account.
User name: admin

63Appendix C: Additional Information

Password: raritan (or a new password if you have changed thedefault)

3.

If this is the first time to log in to the Raritan device, you areprompted to change the password. Type the new password.

4.

Choose Device Settings > Network.

5.

(Optional) If the current cascading mode does not meet your needs,
select an appropriate cascading mode: Bridging or Port Forwarding.


6.

7.

For the Port Forwarding mode, you must also set the role anddownstream interface correctly.

Go to the correct interface to enable IPv4, IPv6 or both protocols.
In the Bridging mode, click the BRIDGE interface.

In the Port Forwarding mode, click ETHERNET (or ETH1/ETH2)
and/or WIRELESS interface on the master device.

Depending on which IP protocol has been enabled in the above step,
configure the corresponding IP settings.

Configuration via CLI
If you want to configure a master or slave device's network settings via
CLI, you must connect that device to a computer via a serial RS-232
connection.
You can also access the master device's CLI through a USB connection.
For details, see the Quick Setup Guide, Online Help or User Guide, which
can be downloaded from Raritan website's Support page(http://www.raritan.com/support/).
To configure network settings via CLI:
1.

64

On the computer connected to the Raritan device, open a
communications program such as HyperTerminal or PuTTY.

Appendix C: Additional Information2.

Select the appropriate COM port, and set the following port settings:
Bits per second = 115200 (115.2Kbps)



Data bits = 8

Stop bits = 1

Parity = None

Flow control = None

Tip: For a USB connection, you can determine the COM port bychoosing Control Panel > System > Hardware > Device Manager, andlocating the "Dominion PX2 (or EMX)Serial Console" under the Ports
group.
3.

In the communications program, press Enter to send a carriage
return to the Raritan device.

4.

The Raritan device prompts you to log in. Both user name andpassword are case sensitive.
a. Username: adminb. Password: raritan (or a new password if you have changed it).

5.

If prompted to change the default password, change or ignore it.
To change it, follow onscreen instructions to type your new
password.

To ignore it, simply press Enter.

6.

The # prompt appears.

7.

Type config and press Enter.

8.

To configure network settings, type appropriate commands andpress Enter. Refer to the following commands list. CLI commands
are case sensitive.

9.

After finishing the network settings, type apply to save changes. To
abort, type cancel.

65Appendix C: Additional Information

Commands for wired networking:The <ipvX> variable in the following commands is either ipv4 or ipv6,
depending on the type of IP protocol you are configuring.
For all Raritan products other than PX3-iX7, replace the variable<ETH> with the word "ethernet". For PX3-iX7, replace the variable<ETH> with either 'ETH1' or 'ETH2', depending on which Ethernet port
you are configuring.
General IP settings:
To set or
enableUse this command

IPv4 or IPv6
protocolnetwork <ipvX> interface <ETH>
enabled <option><option> = true, or false

IPv4
configuration
methodnetwork ipv4 interface <ETH>
configMethod <mode>

IPv6
configuration
methodnetwork ipv6 interface <ETH>
configMethod <mode><mode> = dhcp (default) or static<mode> = automatic (default) or static

Preferred host network <ipvX> interface <ETH>
preferredHostName <name>name(optional)<name> = preferred host name
IP address
returned by
the DNS
server

network dns resolverPreference<resolver><resolver> = preferV4 or preferV6

Static IP configuration:
To setStatic IPv4 or
IPv6 address

Use this command
network <ipvX> interface <ETH>
address <ip address><ip address> = static IP address, with asyntax similar to the example below.
 Example: 192.168.7.9/24

66

Appendix C: Additional Information

To setStatic IPv4 or
IPv6 gateway

Use this command
network <ipvX> gateway <ipaddress><ip address> = gateway's IP address

IPv4 or IPv6
primary DNS
server

network dns firstServer <ip
address>

IPv4 or IPv6
secondary
DNS server

network dns secondServer <ip
address>

IPv4 or IPv6
third DNS
server

network dns thirdServer <ip
address><ip address> = DNS server's IP
address<ip address> = DNS server's IP
address<ip address> = DNS server's IP
address

Commands for wireless networking:General wireless settings:
To set or
enableUse this command

Wirelessinterface

network wireless enabled<option><option> = true, or false

SSID

network wireless SSID <ssid><ssid> = SSID string

BSSID

network wireless BSSID <bssid><bssid> = AP MAC address or none

802.11n
protocolnetwork wireless enableHT<option><option> = true, or false

67Appendix C: Additional Information

To set or
enableUse this command

Authentication network wireless authMethod<method>method<method> = psk or eap
PSK

network wireless PSK <psk><psk> = PSK string

network wireless
EAP outer
authentication eapOuterAuthentication<outer_auth><outer_auth> = PEAP
network wireless
EAP inner
authentication eapInnerAuthentication<inner_auth><inner_auth> = MSCHAPv2
EAP identity

network wireless eapIdentity<identity><identity> = your user name for EAPauthentication

EAP password network wireless eapPassword
When prompted to enter the password
for EAP authentication, type thepassword.
EAP CAcertificate

network wireless
eapCACertificate
When prompted to enter the CA
certificate, open the certificate with atext editor, copy and paste the content
into the communications program.

68Appendix C: Additional Information

The content to be copied from the CA certificate does NOT include thefirst line containing "BEGIN CERTIFICATE" and the final line containing"END CERTIFICATE." If a certificate is installed, configure the following:
Whether to
Verify thecertificate

Use this command
network wirelessenableCertVerification<option1><option1> = true or false

Accept an
expired or
not valid
certificate

network wirelessallowOffTimeRangeCerts<option2><option2> = true or false

Make theconnection
successful byignoring the"incorrect"
system time

network wirelessallowConnectionWithIncorrectC
lock <option3><option3> = true or false

Wireless IPv4 / IPv6 settings:

Commands for wireless IP settings are identical to those for wired
networking. Just replace the variable <ETH> with the word 'wireless'.
The following illustrates a few examples.
To set or
enableUse this command

IPv4
configuration
methodnetwork ipv4 interface WIRELESS
configMethod <mode>

IPv6
configuration
methodnetwork ipv6 interface WIRELESS
configMethod <mode><mode> = dhcp (default) or static<mode> = automatic (default) or static

To verify network settings:
After exiting the above configuration mode and the # prompt re-appears,
type this command to verify all network settings.
show network

69

Appendix C: Additional Information

Wireless LAN Information
The cascading chain can connect to a wired and/or wireless LAN in the
Port Forwarding mode. See Setting the Cascading Mode (on page 7).
This appendix provides information regarding wireless LAN
configuration and LAN adapters.
Supported Wireless LAN Configuration
If wireless networking is preferred, ensure that the wireless LAN
configuration of your Raritan device matches the access point. The
following is the wireless LAN configuration that the Raritan device
supports.


Network type: 802.11 A/B/G/N



Protocol: WPA2 (RSN)

Key management: WPA-PSK, or WPA-EAP with PEAP and
MSCHAPv2 authenticationEncryption: CCMP (AES)

Important: Supported 802.11 network protocols vary according to thewireless LAN adapter being used with the Raritan device. See USB
Wireless LAN Adapters (on page 70).
USB Wireless LAN Adapters
A standalone Raritan device supports the use of all USB wireless LAN
adapters below. However, the Port Forwarding mode only supports theuse of the Raritan USB WIFI LAN adapter.

70

Wi-Fi LAN adapters

Supported 802.11
protocols

SparkLAN WUBR-508N

A/B/G/N

Proxim Orinoco 8494

A/B/G

Zyxel NWD271N

B/G

Edimax EW-7722UnD

A/B/G/N

TP-Link TL-WDN3200 v1

A/B/G/N

Raritan USB WIFI

A/B/G/NAppendix C: Additional Information

Note: To use the Edimax EW-7722UnD or Raritan USB WIFI wireless LAN
adapter to connect to an 802.11n wireless network, the handshaketimeout setting must be changed to 500 or greater, or the wirelessconnection will fail.

71

IndexA

I

Accessing Raritan Devices • 20
Adding, Removing or Swapping Cascaded
Devices • x, 19, 45
Additional Information • 60
Applicable Products • ix

Identifying Cascaded Devices • 33
Illustration • 1
Installing the USB-to-Serial Driver (Optional) •61

BBest Practices • 3

CCascading Applications • 1
Cascading Modes • x, 5
Cascading Procedure • 4
Cascading PX3-iX7 via Ethernet or USB • 4, 13,
16
Cascading Raritan Devices • x, 11
Cascading Restrictions • 18
Cascading Solution's Overview • x, 1
Cascading the Raritan devices via USB • 4, 13,
17
Cascading Troubleshooting • x, 45, 53
Character LCD Display • x, 24, 43
Configuration via CLI • 64
Configuration via Web Interface • 8, 63
Configuring Network Settings • 63
Connecting the Raritan device to a Computer •7, 53, 60

DL
LCD Display • 21
Local Console • 21
Login • 7, 26, 57

M
MAC Address • 25
Making a Connection • 60
Mode Change via CLI • 9Mode Change via Web Interface • 7

OOverview of the Cascading Modes • 5

PPing via the CLI • 58
Ping via the Web Interface • 57
Port Forwarding Examples • 26, 29, 30
Port Number Syntax • x, 6, 7, 28, 30, 55
Port Numbers for Port-Forwarding Devices •x, 28, 63
Port-Forwarding Slave Device Events • 56
Possible Root Causes • 53

Dot-Matrix LCD Display • 22, 23, 40

SE

Safety Guidelines • ii
Safety Instructions • iii
Setting the Cascading Mode • 4, 7, 13, 16, 19,
34, 45, 70
SNMP Management • 27
SNMP Notifications • 28
SSH/Telnet Access • 9, 27, 36, 58
Supported Web Browsers • 25
Supported Wireless LAN Configuration • 54,
70

Extended Cascading (for PX3-iX7 Only) • 3, 15
Extended-Cascading Requirements • 15

F
Finding the IP Address • 7, 20, 33
Firmware Upgrade • x, 47

H
HTTP/HTTPS Access • 25, 33

73

IndexT
The Ping Tool • 56
Third-Party SNMP Managers • 28

U
Unsupported Cascading Connections for Port
Forwarding • 16, 50, 56
Updating the Raritan device Firmware • 47
Upgrade Sequence in an Existing Cascading
Chain • x, 12, 14, 18, 48
USB Cascading • 11
USB Wireless LAN Adapters • 14, 18, 54, 70
USB-Cascading Requirements • 12, 13
Using the CLI • 36
Using the LCD Display • 40
Using the SNMP • x, 38
Using the Web Interface • 33

W
What's New in the Cascading Guide • xWhen to Avoid Cascading Devices • 3
Wireless LAN Information • 7074