Professional Documents
Culture Documents
Basic Participant
Basic Participant
Basic Participant
A P2 00
NETWORKS
Et hereal PC
sni ff Configured AP
Destination
L2 MAC address
L3 I P address
162 Basic Installation and Configuration of a Meru Network
Capturing Packets
Wireshark
The GUI-based Wireshark (formerly Ethereal) has far more advanced filtering
capabilities than the command-line version, so its usually better to capture a bit more
data than we need and use the GUI to filter it further.
21 2009 Meru Networks Inc All rights reserved
Wireshark
Help
1. Click on the
Expression
button to create
a filter.
2. Create the filter,
click OK
3. Click on the
Apply button.
Capturing Packets
Troubleshooting 163
Saving Captures
Because the controller only has 10MB of space reserved for captures, we can use the
ISDS system to route packets directly to Wireshark running on a computer.
Dont forget to disable the IDS once youre done.
Note: This technique shows only what is received by the AP!
22 2009 Meru Networks, Inc. All rights reserved.
Saving Captures with Wireshark
Synchronize clocks with Controller and
Wireshark PC
Set up IDS
Point to Wireshark PCs IP address
Use port 9177
Specify index number(s) of L3-connected APs
Set up and activate Wireshark
Set up Capture Options...
When youre done, restore IDS to original
state
164 Basic Installation and Configuration of a Meru Network
diagnostics Command
diagnostics Command
The diagnostics command is only run at the request of Support, typically only for
very involved problems. No tools are provided to use the data collected.
23 2009 Meru Networks, Inc. All rights reserved.
diagnostics Command
When you need to capture the entire system
state, use the command diagnostics
Takes snapshot of system state
Essential for reporting problems
Does not affect operation
Need to copy off the controller
If you run it again, it will overwrite the previous
copy
Lab Preview
Troubleshooting 165
Lab Preview
24 2009 Meru Networks, Inc. All rights reserved.
Lab Preview
Examine station logs
Capture and examine packets
SIP
RADIUS
166 Basic Installation and Configuration of a Meru Network
Lab Exercises
Lab Exercises
In this lab exercise, you will:
Examine the station logs to track a stations connection.
Capture packets from the system.
Filter for certain packets after you have captured them.
Station Diagnostics
Filtered View
1. Set up station diagnostics to record the events of your station.
2. Connect your station to your test network.
3. Looking at the station log and one of the connection stages diagrams, trace the
progress of your connection.
4. Connect your station to your network that uses 802.1x authentication.
5. Looking at the station log and one of the connection stages diagrams, trace the
progress of your connection.
Filtered View
1. Set up station diagnostics your controller to capture DHCP events.
2. Connect your station to your test network.
3. Display the messages that indicate IP address assignment.
Capture Packets
From a controller
1. Open a terminal session to your controller.
Check: Have your instructor check off your progress at this point.
Lab Exercises
Troubleshooting 167
2. Change the default number of lines that the command line displays using the
command: terminal length 0.
3. Capture packets from the controller.
What command did you use? ________________________________________
4. Observe the packets flowing by.
5. Stop the capture by pressing Control-C.
From an AP using IDS and Wireshark
In this section reminds youll practice capturing packets using the IDS facility and
Wireshark.
1. Close the web browser currently running the Web interface.
2. Launch Wireshark and configure it to collect information from the Ethernet
interface of the station on which it is running.
3. Disconnect from all wireless networks.
4. Open an SSH terminal session to your controller.
5. Identify the IP address of your recording system.
6. Open the IDS configuration page in the Web interface (Configuration > IDS
[under the Wireless IDS/IPS heading]).
7. Enter the number 9177 in the Server Port text box.
8. Enter the index numbers of both your APs, separated by a comma, in the AP
selection box.
You can capture packets from a single AP by entering its index number only in
the AP selection box.
Note: Note: the AP from which you want to record must be configured for L3
access.
9. Click on the OK button.
Data should begin streaming to the Wireshark application from the AP.
10. Have your partner connect to your wireless network.
11. Collect data while your partner authenticates, then stop the capture.
12. Disable the IDS facility.
168 Basic Installation and Configuration of a Meru Network
Lab Exercises
13. Filter the data display so you can see only the packets from your partners station.
What filter term (or terms) did you use?
________________________________
________________________________
________________________________
14. Close Wireshark.
Capture a SIP Session
During a SIP Call
1. Capture packet traces for a SIP session on the controller. Use the command:
controller# capture-packets -R sip
You will see something like:
There should be a symmetry of communication between the two devices.
11.391697 192.168.10.131 -> 10.6.6.103 SIP Request: REGISTER sip:10.6.6.103
12.067072 10.6.6.103 -> 192.168.10.131 SIP Status: 200 OK (1 bindings)
17.190306 192.168.10.130 -> 10.6.6.103 SIP Request: REGISTER sip:10.6.6.103
17.717009 10.6.6.103 -> 192.168.10.130 SIP Status: 200 OK (1 bindings)
41.081454 192.168.10.130 -> 10.6.6.103 SIP/SDP Request: INVITE
sip:303@10.6.6.103, with session description
41.084611 10.6.6.103 -> 192.168.10.131 SIP/SDP Request: INVITE
sip:303@192.168.10.131, with session description
41.237828 192.168.10.131 -> 10.6.6.103 SIP Status: 180 Ringing
41.240878 10.6.6.103 -> 192.168.10.130 SIP Status: 180 Ringing
42.276537 192.168.10.131 -> 10.6.6.103 SIP/SDP Status: 200 OK, with session
description
42.278801 10.6.6.103 -> 192.168.10.130 SIP/SDP Status: 200 OK, with session
description
42.520909 192.168.10.130 -> 10.6.6.103 SIP Request: ACK sip:303@10.6.6.103:5060
42.524012 10.6.6.103 -> 192.168.10.131 SIP Request: ACK sip:303@192.168.10.131
Call Setup
Phone registration
on powerup
192.168.10.130 initiates a call
Lab Exercises
Troubleshooting 169
2. Capture packet traces for a SIP session on the AP to which the phone is
associated. You can use either the IDS method or the capture-packets
command:
controller# capture-packets -i apId -R sip
In this command, substitute the number of the AP you want to capture from
for the term apId.
3. Show your instructor the traces you have captured.
Capture a WPA Session
In this section you will use the troubleshooting techniques you have learned and the
references you have to construct a troubleshooting command for a WPA
authentication session.
1. Create an appropriate packet capture command.
What command did you use?
________________________________________
2. Run the command, then attempt authentication through the WPA2PSK-secured
ESS you constructed earlier.
Capture a RADIUS Session
Capture a Wired RADIUS Flow using Wireshark
The next two steps involve capturing packets for analysis. Either the IDS method or
the capture-packets command can be used.
1. Capture packets destined for the RADIUS server coming from the controller into
a file (in this example: filename.cap). For a file capture, use a command like:
controller# capture-packets -R radius -w filename.cap
or, to filter on the IP address of the RADIUS server (172.17.17.7, in this example),
use:
controller# capture-packets -R ip.addr==172.17.17.7 -w filename.cap
Check: Have your instructor check off your progress at this point.
170 Basic Installation and Configuration of a Meru Network
Lab Exercises
Youll see something like:
2. Verify that Access Accept is returned.
Capture a Wireless EAPOL Flow
3. Capture packet traces for the session from a specific AP. Use the command:
controller# capture-packets -i apId -R eapol
a. Verify that Access Accept is returned.
Capture a Complete RADIUS Transaction
4. Capture packets from the RADIUS transactions into a file (in this example:
filename.cap). For file capture, use a command like:
controller# capture-packets -R radius -w filename.cap
a. Verify that the entire RADIUS transaction can be seen by reviewing the
capture.
See the illustration RADIUS Protocol Example on page 109 for an example
of the required information exchanges.
b. Verify that Access Accept is returned.
Troubleshoot a RADIUS Session
Your instructor will borrow your system and put a typical problem in it. Your job is
to locate the problem using the troubleshooting techniques you have learned.
1. Ask you instructor to configure your system.
2. Once configured, use the techniques you have learned to isolate the problem.
yoyodyne-wifi# capture-packets -R "radius"
9
Fan Tray
Power Supply Bay
Shelf Manager MC5000 Controller Blade Slots
5
4
3
1
Grounding Plug
Fan Tray
2
0
0
2
1
3
Power Port
Input A
Grounding Screws
Input A
Power Switch
Input B
Power Switch and Port
Controllers
Hardware Reference 203
MC4100 Features
The MC4100 controller supports medium and large-scale deployments with Ethernet
network connectivity up to 4 Gbps line rate supporting as many as 300 Access Points
and 3000 clients.
Figure 3: MC4100 Chassis (Front view)
Use the ports marked G1 through G4 for management, control, and data. At this time,
you cannot place a management address for out of band management on the X1 or
X2 ports. These ports are for future use.
Port bonding is configured using the command bonding single (for all ports into a
single logical port of 4G) or bonding dual (for 2 ports each with 2G where G1-G2
are bonded together and G3-G4 are bonded together). Logically, after bonding the
ports are the same as the current MC1000/MC3000 where there are either 1 or 2
Etherports for N+1.
The USB port is used for recovery purposes.
When power is on, the LCD screen and LCD buttons glow blue. Use the four LCD
buttons to navigate through the LCD functions illustrated below in Figure 4.
00
2
2
0
0
2
2
0
G1 G2 G3 G4
Power USB
LCD
1G Ethernet
LED
Link
Indicator
Indicator
Link
Indicator Indicator
Activity
Activity
Ports (X1, X2)
future use
Power
indicator
Port
DB9
Serial
Console
Port
204 Basic Installation and Configuration of a Meru Network
Controllers
Figure 4: LCD Navigation Tree
The first time that MC4100 is turned on, you must turn on the two back power
switches shown below before powering on with the power button on the front panel.
Figure 5: MC4100 Back
4 Fans - 2 per power supply
2 Power
2 On/Off Power
Connectors Switches
0
0
2
2
Controllers
Hardware Reference 205
MC3000 Features
The MC3000 wireless LAN controller is designed for large-scale enterprise
deployments and provides comprehensive security, gigabit scalability in its Ethernet
interface, service flexibility, and reliable performance. The MC3000 can support up
to 150 APs.
Figure 6 and Figure 7 show the front and the back of the MC3000, respectively.
Figure 6: MC3000 Controller Front Panel
Figure 7: MC3000 Controller Back Panel
0
0
0
2
0
LCD Informational Panel
Navigational
Keys
10/100/1000
Ethernet Port
G1
Ethernet Port
10/100/1000
Serial Port
G1 Speed
Power/Status
LEDs
G2 (reserved)
Up Arrow
Left Arrow
Down Arrow
Right
Arrow
Activity/Link LEDs
G2 Speed Activity/Link LEDs
(reserved)
Power
inlet
Power
switch
Air Outlets
206 Basic Installation and Configuration of a Meru Network
Controllers
MC1500 Features
The MC1500 is designed for small to medium-scale site deployments, such as small
offices or remote branch sites. It supports customers requiring Layer 1-4 security,
Fast Ethernet, and affordable performance. The MC1500 can support up to 30 APs.
The MC1500 measures 16.7x1.1x10.6 inches. The front and back of the MC1500 are
shown below.
Figure 8: MC1500 Front Panel
Figure 9: MC1500 Rear Panel
0
0
2
2
8
USB
Ethernet
LEDs:
Activity
Indicators Indicators
Link
Ports
Power
Status (not used)
Ports
Console
Port
hard disk drive (not used)
0
0
2
2
9
Power
Switch
Power
Connector
Fans
Controllers
Hardware Reference 207
MC1000 Features
The MC1000 controller was optimized for medium-scale enterprises and education
customers providing Layer 1-4 security, gigabit Ethernet interface scalability, and
affordable performance. At this writing the MC1000 is not available for purchase.
The MC1000 controller supports up to 30 APs.
The front and back of the MC1000 are shown in Figures 10 and 11.
Figure 10: MC1000 Controller Front Panel
Figure 11: MC1000 Controller Back Panel
10/100/1000
LINK/ACT
LCD Informational Panel
Navigational
Keys
10/100/1000
Ethernet Port
G2 (reserved)
Ethernet Port
10/100/1000
Serial Port
G1 Speed
Power/Status
LEDs
G1
Up Arrow
Left Arrow
Down Arrow
Right
Arrow
Link/Activity LEDs
G2 Speed
Link/Activity LEDs
(reserved)
Power
inlet
Power
switch
Air Outlets
208 Basic Installation and Configuration of a Meru Network
Controllers
MC500 Features
The MC500 controller was designed for small-scale site deployments, such as small
offices or Remote branch sites. It supports customers requiring Layer 1-4 security,
Fast Ethernet, and affordable performance. The MC500 controller can support up to
5 APs. At this writing the MC500 is not available for purchase.
The MC500s small footprint is 1.3" H by 9.5" W by 5.8" D and it is powered by an
external power brick. The front and back of the MC500 are shown in FIgures 12 and
13.
Figure 12: MC500 Controller Front Panel
Figure 13: MC500 Controller Rear Panel
Comparison of Controller Features
A comparison of the features for the various controllers is provided in Table 1.
0
0
Power LED
Power On/Off Button
LAN1 Speed/Activity LED
LAN2 Speed/Activity LED
(reserved)
0
0
Power Inlet
Serial Port
LAN1 10/100 Ethernet Port
LAN2 10/100 Ethernet Port
(reserved)
Reset Button
Controllers
Hardware Reference 209
SA1000 Features
The SA1000 appliance is used to run the E(z)RF Network Manager and E(z)RF
Location Manager products.
Figure 14: SA1000 Chassis (Front view)
Use the pors marked X1 for management, control, and data. At this time, you cannot
place a management address for out of band management on the X1 or X2 ports.
These ports are for future use.
Port bonding is configured using the command bonding single (for all ports into a
single logical port of 4G) or bonding dual (for 2 ports each with 2G where G1-G2
are bonded together and G3-G4 are bonded together). Logically, after bonding the
ports are the same as the current MC1000/MC3000 where there are either 1 or 2
Etherports for N+1.
The USB port is used for recovery purposes.
Table 1: Controller Feature Comparison
Controller Model Number of Ethernet
Connections
Number of Supported
APs
MC500 1 (supporting 10/100 Mbps) Up to 5
MC1000/MC1500
1 (supporting 10/100/1000
Mbps)
Up to 30
MC3000
1 (supporting 10/100/1000
Mbps)
Up to 150
000
2
0
0
2
2
2
Power USB
LCD
1G Ethernet
LED
Link
Indicator
Indicator
Activity
Ports (X1, X2)
Power
indicator
Port
DB9
Serial
Console
Port
210 Basic Installation and Configuration of a Meru Network
Controllers
When power is on, the LCD screen and LCD buttons glow blue. Use the four LCD
buttons to navigate through the LCD functions illustrated in the following tree.
Figure 15: LCD Navigation Tree
The first time that the SA1000 appliance is turned on, you must turn on the two back
power switches shown below before powering on with the power button on the front
panel.
Figure 16: SA1000 Back
4 Fans - 2 per power supply
2 Power
2 On/Off Power
Connectors Switches
0
0
2
2
Access Points
Hardware Reference 211
Access Points
AP150 Connectors
Figure 17: AP150 Connector Panel
AP150 Status LEDs
The following illustrations depict the AP 150 access point.
Four LEDs on the face of the AP150 indicate status, as shown below.
.
Figure 18: AP150 Status LEDs
ANT1 ANT2
LAN
DC 5V
CONSOLE
RESET RELOAD
0
0
Power Ethernet
connection
Console
port Reset
button
Reload
Antenna 1 Antenna 2
(reserved) (reserved)
PWR
LAN
RADIO2
RADIO1
Status LEDs
0
0
214 Basic Installation and Configuration of a Meru Network
Access Points
Table 3: AP180 LED Description
AP201/208 Connectors
Figure 21: AP201/208 Connector Panel
Note: DC input is only available on Rev 1 AP200s.
LEDs Function
Power When power is applied to the system this LED initially turns
amber, then blinks green when the system power check is
applied, and then is a steady green when power is on.
The Ethernet Link LED blinks green when a link has been
detected and is in use.
The 11bg connection LED blinks amber when radio packets
are being transmitted and when the radio is beaconing. If
there is traffic over the air on this radio, the blinking rate
increases.
Ethernet Link
Radio 1 11bg
Radio 2 11a
The 11a connection LED blinks green when radio packets are
being transmitted and when the radio is beaconing. If there
is traffic over the air on this radio, the blinking rate
increases.
CONSOLE
ANT 1 ANT 2
3.3 VDC ETHERNET
0
0
0
8
100/1000
Ethernet
(Reserved)
Console
port
Antenna 1 Antenna 2 Power
inlet
Reset
(Push to restore
default settings)
(Currently
unsupported)
Access Points
Hardware Reference 215
AP201/208 Status LEDs
Four LEDs on the face of the AP201/208 indicate status, as shown below.
..
Figure 22: AP200 Status LEDs
The functions of the status LEDs are described in the table below.
When the AP200 is first connected to the controller and any time the access point is
rebooted thereafter, the AP initializes with and then is programmed by the controller.
When the AP is first powered up, all LEDs are green. Thereafter, the Status LED (see
the figure above) color reflects the various operating states (see the table below).
AP200
RF2
RF1
STATUS
POWER
0
0
P
W
R
S
T
A
T
L
A
N
R
F
1
R
F
2
220 Basic Installation and Configuration of a Meru Network
Access Points
Table 6: AP300 LED Descriptions
LED Function
Power
offno power
greenpresence of power
Status
offno power
greenbooting stage 1
blinking green and offbooting stage 2
blinking green and whitediscovering the controller
blinking green and bluedownloading a configuration from the controller
blinking blue and offAP is online and enabled, working state
blinking red and yellowfailure; consult controller for alarm state
LAN
offno power, or no link
greenlink status OK (at any speed)
green/blinkingactivity (at any speed)
redauto negotiation failure
Radio 1
Radio 2
offno radio present
greenradio enabled
green blinkingdata activity
yellowdisabled or in scanning mode
redfailure
Access Points
Hardware Reference 221
RS4000 Connectors
Figure 25: RS4000 with Antenna Attached
RS4000 Status LEDs
LEDs on the face of the RS4000 indicate status, as shown below.
.
Figure 26: RS4000 Status LEDs
K
0
0
1
8
2
ANT1 ANT2
ETH1
ETH2
ANT1
ANT2
(Meru logo is upside down)
POWER
RADIO I
RADIO II
ETHERNET
POWER
RADIO I
RADIO II
ETHERNET
0
0
1
8
5
Status LEDs
222 Basic Installation and Configuration of a Meru Network
Installing the MC5000 Controller Chassis
The RS4000 uses 4 LEDs. The functions of the status LEDs are described the table
below.
Table 7: RS4000 LED Descriptions
Installing the MC5000 Controller Chassis
Perform the procedures in the following sections to install and configure the
MC5000 Controller Chassis.
The MC5000 Controller Chassis can be set on a flat surface or rack-mounted in a
standard 19 telco rack.
The MC5000 Controller blades and Chassis frame are packaged separately. For the
initial installation, use the following procedure:
LED Function
Power The Power status LED status is as follows:
offpower is off
solid redwhen power is applied, system initializes for 40 seconds and then
the LED turns amber; after discovering the controller the LED turns green.
Otherwise, the system is in an abnormal state (notify Customer Support).
solid amberat any time, if this LED state persists longer than 40 seconds,
notify Customer Support
solid greensystem is fully operational
Radio I The Radio I LED is lit when radio packets are being transmitted and when the
radio is beaconing.
Radio II The Radio II LED is lit when radio packets are being transmitted and when the
radio is beaconing.
Ethernet The Ethernet LED status is as follows:
offno link
solid green100Mbps connection
blinking greentransmit or receive activity at 100Mbps
solid amber10Mbps connection
blinking ambertransmit or receive activity at 10Mbps
Installing the MC5000 Controller Chassis
Hardware Reference 223
1. Unpack the shipping containers and verify the following items are included:
Chassis frame with installed Shelf Manager card(s), 2 fans, and power supply
Chassis power cord
Number of blades ordered
Release 3.4 documentation CD
2. Install the chassis in a 19 standard rack, if so desired. The following must be
considered when installing the chassis in a rack:
Elevated Operating Ambient TemperatureIf installed in a closed or multi-unit rack
assembly, the operating ambient temperature of the rack environment may be greater than
room ambient. Therefore, consideration should be given to installing the equipment in an
environment compatible with the manufacturer's maximum rated ambient temperature (Tmra)
of 40
o
C (104
o
F).
Reduced Air FlowInstallation of the equipment in a rack should be such that the amount of
air flow required for safe operation of the equipment is not compromised.
Mechanical LoadingMounting of the equipment in the rack should be such that a hazardous
condition is not created due to uneven mechanical loading.
Circuit OverloadingConsideration should be given to the connection of the equipment to the
supply circuit and the effect that overloading circuits might have on overcurrent protection and
supply wiring. Appropriate consideration of equipment nameplate ratings should be used
when addressing this concern.
Reliable EarthingReliable earthing of rack mounted equipment should be maintained.
Particular attention should be given to supply connections other than direct connections to the
branch circuit (such as using a power strip and so forth).
a. To install MC5000 chassis in rack:
Move the MC5000 chassis to the rack or cabinet where it will be installed.
Remove any packing materials from the chassis.
b. Lift the MC5000 into position and attach the chassis to the rack rails. Ensure
that all mounting screws (both sides) are installed to secure the MC5000 to the
mounting rails.
3. Attach a ground wire to the chassis and to a grounded location.
4. To install an MC5000 blade:
a. To properly ground yourself, attach a grounding strap to the grounding plug on
the front (top left corner) of the MC5000 chassis.
b. Slots are numbered starting with 1 on the bottom and 5 on top, below the Shelf
Manager. For the slot where the MC5000 blade will installed, remove the filler
panel. Store the filler panel in a safe place.
Warning!
Installing an MC5000 chassis is a 2-person task. The base chassis with filler
panels weighs 50 pounds, and a fully loaded chassis weighs up to 75
pounds. At least 2 installers are required to do this task safely.
224 Basic Installation and Configuration of a Meru Network
Installing the MC5000 Controller Chassis
c. Insert the MC5000 blade by following the directions MC5000 Blade Insertion
and Removal.
5. Connect the first Ethernet cable to the primary Ethernet port (the left-most
Ethernet port) on the front of the MC5000 blade and to a switch, as described in
the Installation and Quick Start Guide.
Figure 27: Primary and Secondary Ethernet Ports
If a secondary Ethernet connection is required, connect it to the Ethernet port indicated in Figure 1.
The MC5000 blades can be configured to the same subnet or different subnets, depending on the type
of network configured that is required.
6. Connect the power cord to the Input A receptacle on back of the chassis and to
the wall AC power source. (Input B is used if the optional power supply has been
purchased.)
7. Power up the chassis by flipping the On/Off switch on the back of the chassis to
On. Ensure that the fans are running, and cool air is flowing through the chassis.
8. Perform controller configuration as described in the Installation and Quick Start
Guide.
Caution!
Electrostatic DischargeThe blades contain ESD-sensitive devices, and
can be damaged if not handled in accordance with approved ESD
guidelines. Do not remove any blade from its ESD packaging until you are
ready to install it in the MC5000 chassis.
Caution! Seating this blade properly can be tricky. Be sure to look at the directions.
primary
primary
secondary
Installing the MC5000 Controller Chassis
Hardware Reference 225
About the Shelf Manager
The shelf manager monitors the power, cooling and operation of the chassis. Status
is visible via the LEDs located on the shelf manager blade and on the Shelf Alarm
Panel, located in the center of the Shelf Manager blade.
The Shelf Manager LED location and status are shown in the following figure. The
green LED, shown in location 9 in the following figure, displays with normal
operation.
Figure 28: Shelf Manager Status LED Location and Description
226 Basic Installation and Configuration of a Meru Network
Installing the MC5000 Controller Chassis
Checking the Shelf Manager Alarm Panel LEDs
The LEDs on the Shelf Manager Alarm Panel convey status about chassis alarms.
The following shows the location of the LEDs and the serial ports on the Shelf
Manager Alarm Panel:
Figure 29: Shelf Manager Alarm Panel LEDs
Serial and Alarm Card Relays
The incoming signals for the alarm board are SELV and are not more than 30V dc/1A
the rating for the contact.
MC5000 Blade Insertion and Removal
To install a card in a chassis:
1. Remove the filler panel of the slot.
2. Ensure the board is configured properly.
3. Carefully align the PCB edges in the bottom and top card guide.
4. Insert the board in the system until it makes contact with the backplane
connectors.
5. Using both ejector handles, engage the board in the backplane connectors until
both ejectors are locked.
6. Fasten screws at the top and bottom of the faceplate.
To remove an MC5000 blade:
1. Unscrew the top and the bottom screw of the front panel.
2. Unlock the lower handle latch. This may initiate a clean shutdown off the
operating system.
3. Wait until the blue LED is fully ON; this means that the hot swap sequence is
ready for board removal.
Caution!
Electrostatic DischargeThe blades contain ESD-sensitive devices, and
can be damaged if not handled in accordance with approved ESD
guidelines. Do not remove any blade from its ESD packaging until you are
ready to install it in the MC5000 chassis.
Controller Installation
Hardware Reference 227
4. Use both ejectors to disengage the board from the backplane.
5. Pull the board out of the chassis.
Controller Installation
The form factor for the MC3000 and MC1000 controllers are 1U chassis that have
been designed for a 19" rack. The MC4100 has a 2 U chassis. Airflow enters from
the front chassis and exits through the back. Care should be taken to ensure that there
are no obstructions around the controller chassis that could reduce or block airflow.
The MC500 is a mini-desktop unit that may be placed in a convenient location in a
small office or data center. The MC500 is powered by a separate power adapter.
To install the controller:
1. If you opt to install the controller in a rack, choose a location in the rack that
accepts the clearance for a 1U high chassis.
2. Insert the chassis into the chosen rack location and mount the unit.
3. Make the ground connection.
4. Ensuring proper ground should always be the first connection to the controller
during installation.
5. Connect the power cord to the chassis and a wall outlet.
Note: The power cord(s) provided with the Meru controllers is for use only with
that Meru Networks product. It is not for use with any other Meru Networks product
or other brands of equipment.
6. Press the power switch to the On position for the MC500, MC1000 and MC3000.
For the MC4100, first turn on both power supplies on the back of the chassis (see
Figure 5:), then press the power button on the front left of the unit.If the MC4100
beeps continuously, you have not turned on all 3 switches.
For the MC1000 and MC3000, the Power On System Test runs and completes
with one of the following codes, depending on the system status.
Table 8: MC1000 and MC3000 POST Results
Beep Code Description
1 Short beep Normal POST, controller status is normal
228 Basic Installation and Configuration of a Meru Network
Powering Off the Controller
The hardware installation is now complete.
Powering Off the Controller
Should it become necessary to power off the controller, it is recommended you use
the CLI command poweroff controller before switching the controller off with the
Power On/Off switch. The command gracefully brings the controller down to a state
where power can safely be removed using the power switch.
LED Status Indicators
Monitor the status of the controller and the Ethernet connection using the various
LED status indicators, located on the front of the chassis.
2 Short beeps CMOS error
One long and one short beep DRAM error
One long and two short beeps Video (Mono/CGA Display Circuitry) issue
One long and three short
beeps
Keyboard/Keyboard card error
One long and nine short
beeps
ROM error
Continuous long beep DRAM problem
Repeating short beeps There are some problem with the Power source.
Table 8: MC1000 and MC3000 POST Results
Caution! Failure to use the poweroff controller command before removing power from the
controller can cause Flash card corruption and result in the controller becoming non-operational.
LED Status Indicators
Hardware Reference 229
Controller LED Status Indicators
The controller status indicator LEDs are located on the front of the chassis, as shown
in the figures in the previous chapter. The description of the LED states are shown in
the following tables.
Table 9: MC4100 LED Status Information
Each of the MC4100 G1-G4 ports has a link LED on the right of the port and an
activity LED on the left of the port. There is also a solid green light to the right of all
four ports that indicates the power of the network accelerator (this should always be
solid green).
LED Color Description
Power
Unlit
Green solid
Red solid
Unit is off
Unit is on, power good
Unit is on, but one of the dual-redundant power
supplies has a failure and needs to be replaced.
230 Basic Installation and Configuration of a Meru Network
LED Status Indicators
Table 10: MC1000 and MC3000 LED Status Information
Table 11: MC500 LED Status Information
Ethernet LED Status Indicators
The RJ-45 connector provides information about the Ethernet connection.
LED Color Description
Power
Amber Solid
Unlit
Powered on
Powered off
Status
Unlit
Green
Unimplemented
Unimplemented
G1
10/100/1000
Unlit
Green solid
Amber solid
LAN Speed 10 Mbps
LAN Speed 100 Mbps
LAN Speed 1000 Mbps
Link/Act
Unlit
Green solid
Green blinking
Link Down/ No Activity
Link Up
Rx/Tx Activity
LED Color Description
Power
Green blinking
Green solid
Unlit
Powered on
While booting or after shutdown
Powered off
100
Unlit
Red solid
100 Mbps Link Down
100 Mbps Link Up
10
Unlit
Red solid
10 Mbps Link Down
10 Mbps Link Up
Act
Unlit
Amber blinking
No Activity
Rx/Tx Activity
LED Status Indicators
Hardware Reference 231
Figure 30: RJ-45 Status Indicators
Table 12: Ethernet Status Information
Navigating the Status Panel Information
The MC1000, MC3000, and MC4100 LCD status panels on the front of the chassis
displays information about the system and the network. The following diagrams
show the structural organization of the information. Use the up and down
navigational buttons to move from one level to the next and the left and right buttons
to move through items on the same level.
LED Activity Description
Network Status
Green solid Network connection
Green blinking Network activity
Port Speed
Off 10 MB/second
Green 100 MB/second
Yellow 1000 MB/second
Ethernet activity
Link present
0
0
2
9
Note: The layout of the navigational buttons are not intuitive. For example, the
button pointing up moves left and the button pointing down moves up; the button
pointing right moves down and the button pointing left moves right. Refer to Figures
31 and 32 for a description of these buttons.
232 Basic Installation and Configuration of a Meru Network
LED Status Indicators
Figure 31: Navigating the MC1000 and MC3000 Status Panel Information
Figure 32: Navigating the MC4100 Status Panel Information
System ID
Serial
Number
Software
Version
Physical
Address
Default
Gateway
Host Name IP Address
Network Menu
Running System
Menu
Controller Information
Meru Networks, Inc.
MC1000 or MC3000
Date and Time
U
p
A
r
r
o
w
K
e
y
D
o
w
n
A
r
r
o
w
K
e
y
Left or Right Arrow Key
0
0