(1) Gigabit Ethernet interface 4—SFP optical interface
(2) 1000 Mbps LED of gigabit Ethernet interface 4
(3) 10/100 Mbps LED of gigabit Ethernet interface 4
(4) 10/100/1000 Base-T auto-sensing Ethernet electrical interface 4
(5) Gigabit Ethernet interface 3—SFP optical interface
(6) 1000 Mbps LED of gigabit Ethernet interface 3
(7) 10/100 Mbps LED of gigabit Ethernet interface 3
(8) 10/100/1000 Base-T auto-sensing Ethernet electrical interface 3
(9) Gigabit Ethernet interface 2—SFP optical interface
(10) 1000 Mbps LED of gigabit Ethernet interface 2
(11) 10/100 Mbps LED of gigabit Ethernet interface 2
(12) 10/100/1000 Base-T auto-sensing Ethernet electrical interface 2
(13) Gigabit Ethernet interface 1—SFP optical interface
(14) 1000 Mbps LED of gigabit Ethernet interface 1
(15) 10/100 Mbps LED of gigabit Ethernet interface 1
(16) 10/100/1000 Base-T auto-sensing Ethernet electrical interface 1
(17) Console port	(18) System LED
(19) LED of the expansion card	(20) LED of power supply 1
(21) LED of power supply 2

Rear Panel

The WX5004 provides two power supply module slots and one expansion card slot, as shown in Figure 1-3.

Figure 1-3 Rear panel of the WX5004

(1) PSU 1 (AC/DC)	(2) Handle of PSU 1
(3) OPEN BOOK sign	(4) Power cord retainer for PSU 1
(5) AC power socket of PSU 1	(6) PSU 2 (AC/DC)
(7) Handle of PSU 2	(8) OPEN BOOK sign
(9) Power cord retainer for PSU 2	(10) AC power socket of PSU 2
(11) Expansion card slot	(12) OPEN BOOK sign
(13) Grounding screw

OPEN BOOK and CAUTION signs: Refer to related sections when performing the following operations:

Table 1-1 OPEN BOOK sign description

Operation	Related section
Connect the power cord	Connecting the AC Power Cord
Ground the device	Connecting the Ground Wire

Specifications

Processor and Storages

Table 1-2 Processor and storages of the WX5004

Item	Description
Processor	XLR716 (800 MHz)
CF card	Built in, 256 MB
Memory type and capacity	Memory: DDR2 SDRAM Capacity: 2048 MB

Dimensions and Weight

Table 1-3 Dimensions and weight

Item	Description
Dimensions (H × W × D)	43.6 × 440 × 430 mm (1.72 × 17.32 × 16.93 in.)
Weight	7.4 kg (16.31 lb.) (with two PSUs installed)

Fixed Interfaces and Slots

Table 1-4 Fixed interfaces and slots

Item	Description
Console port	1 console port, 9600 bps (the default) to 115200 bps.
Ethernet interfaces	4 × 10/100/1000 Base-T autosensing Layer 2 Ethernet interfaces; support MDI/MDIX
SFP interfaces	4 × 1000 Base-X SFP optical interfaces, forming Combo ports together with the corresponding Ethernet electrical interfaces
Slots	l 1 expansion card slot l 2 PSU slots

Power Input

The WX5004 uses two AC/DC PSUs, which provide 1+1 redundancy backup for the WX5004 to enhance the system reliability.

Table 1-5 AC/DC power input

Item	Description
Rated voltage range	For AC power input: 100 VAC to 240 VAC, 50 Hz or 60 Hz For DC power input: –48 VDC to –60 VDC
Max input voltage range	For AC power input: 90 VAC to 264 VAC, 47 Hz to 63 Hz For DC power input: –36 VDC to –72 VDC
Power consumption	53.4 W to 67.7 W

l You are not recommended to use an AC power module with a DC power module on the device.

l No AC or DC power module is provided with the access controller. You need to prepare them yourself.

Components

LEDs

The WX5004 provides LEDs on the front panel, as shown in Figure 1-4.

Figure 1-4 LEDs of the WX5004

(1) 1000 Mbps LED of gigabit Ethernet interface (1000M)
(2) System status LED (SYS)	(3) Status LED of PSU 1 (PWR1)
(4) 10/100 Mbps LED of gigabit Ethernet interface (10/100M)
(5) LED of the expansion card (MOD)	(6) Status LED of PSU 2 (PWR2)

Table 1-6 Description of LEDs

LEDs	Silkscreen	Status	Description
LED of PSU 1 (green/yellow)	PWR1	Solid green	PSU 1 supplies power to the system normally.
		Solid yellow	PSU 1 is faulty.
		Off	No PSU is installed in the slot.
LED of PSU 2 (green/yellow)	PWR2	Solid green	PSU 2 supplies power to the system normally.
		Solid yellow	PSU 2 is faulty.
		Off	No PSU is installed in the slot.
System LED (green/yellow)	SYS	Solid green	The system is performing POST or downloading software.
		Green, slow blinking (1 Hz)	The system works normally.
		Solid yellow	The POST has failed or another fatal error has been detected in the system.
		Off	No power input
LED of the expansion card (green)	MOD	Solid green	The expansion card is present in the slot.
LED of the expansion card (green)	MOD	Off	The expansion card is not present in the slot
Gigabit Combo port LED	1000M	Solid green	The interface is connected at 1000 Mbps.
		Blinking green (6 Hz)	The port is receiving or sending data at 1000 Mbps
		Off	The interface is not connected at 1000 Mbps.
	10/100M	Solid yellow	The interface is connected at 10/100 Mbps.
		Blinking yellow (6 Hz)	The interface is receiving or sending data at 10/100 Mbps.
		Off	The interface is not connected at 10/100 Mbps.

Fixed Interfaces

Console port

The WX5004 provides an RS232 asynchronous serial port (console port) that can be connected to a computer for system debugging, configuration, maintenance, management, and host software loading.

The console cable is an 8-core cable. One end of the cable is a crimped RJ-45 connector and is connected to the console port of the WX5004. The other end is a DB-9 female connector and is connected to the 9-pin serial port on the configuration terminal. Figure 1-5 illustrates a console cable:

Figure 1-5 Console cable

Table 1-7 Console cable pinouts

RJ-45	Signal	Direction	DB-9
1	RTS	←	7
2	DTR	←	4
3	TXD	←	3
4	CD	→	1
5	GND	—	5
6	RXD	→	2
7	DSR	→	6
8	CTS	→	8

Ethernet interfaces

1) Introduction

The WX5004 provides four 10/100/1000 Base-T autosensing Ethernet electrical interfaces and four 1000 Base-X SFP optical interfaces. One electrical interface and one optical interface form a Combo port, which is marked in a white box on the front panel. Only one interface (either electrical or optical) of a Combo port can be used at a time.

l Ethernet electrical interfaces support 10/100/1000 Mbps autosensing. Table 1-8 describes the working mode of the interfaces in each speed.

Table 1-8 Speed and working mode of an electrical Ethernet interface

Speed	Working mode
10 Mbps (autosensing)	Half/full duplex, auto-negotiation
100 Mbps (autosensing)	Half/full duplex, auto-negotiation
1000 Mbps (autosensing)	Full duplex, auto-negotiation

l Ethernet optical interfaces support 1000 Mbps full duplex. The optical interface and the electrical interface of a Combo port share the same LED.

l A Combo port can work in either the electrical interface mode or the optical interface mode, that is, either the electrical interface or the optical interface of a Combo port can be used at a time.

l A Combo port supports optical-electrical automatic switching, however, when both the optical and electrical interfaces are connected, the electrical interface will be used in precedence.

2) SFP interface modules

The WX5004 provides four SFP GE optical interfaces. The following SFP modules are available:

l 1000 Base-SX SFP module

l 1000 Base-LX SFP module

Table 1-9 Technical specifications for the GE optical interface modules

Item		Description
Item		Short-haul multimode (850 nm) SFP module	Medium-haul single-mode (1310 nm) SFP module	Long-haul single-mode (1310 nm) SFP module	Long-haul single-mode (1550 nm) SFP module		Ultra-long-haul single-mode (1550 nm) SFP module
Connector		SFP/LC
Optical fiber		62.5 μm/125 μm multimode	9 μm /125 μm single-mode	9 μm /125 μm single-mode	9 μm /125 μm single-mode	9 μm /125 μm single-mode
Max. transmission distance		0.55 km (0.34 mi)	10 km (6.21 mi)	40 km (24.86 mi)	40 km (24.86 mi)	70 km (43.50 mi)
Central wavelength		850 nm	1310 nm	1310 nm	1550 nm	1550 nm
Optical transmit power	Min.	-9.5 dBm	-9 dBm	-2 dBm	-4 dBm	-4 dBm
Optical transmit power	Max.	0 dBm	-3 dBm	5 dBm	1 dBm	2 dBm
Receive sensitivity		-17 dBm	-20 dBm	-23 dBm	-21 dBm	-22 dBm
Working mode		1000 Mbps Full duplex

No SFP module is shipped with the WX5004. You need to purchase SFP modules as needed and are recommended to use H3C SFP modules.

3) RJ-45 connector

The 10/100/1000 Mbps electrical Ethernet interfaces of the WX5004 use RJ-45 connectors to connect with the category 5 twisted pair cables. Figure 1-6 shows the appearance of an RJ-45 connector.

Figure 1-6 RJ-45 connector

4) LC connector

Optical fiber connectors are indispensable passive components in optical fiber communication systems. Their application enables the removable connection between optical channels, which makes the optical system debugging and maintenance more convenient and the transit dispatching of the system more flexible.

The Ethernet optical interfaces of the WX5004 support LC connectors only.

Figure 1-7 LC connector

l Before using an optical fiber to connect a network device, make sure that the optical fiber connector matches the optical module.

l Before connecting the fiber, make sure that the receiving-end optical power does not exceed the upper threshold of the receiving optical power. Excessive receiving optical power is very likely to burn the optical module. For optical power values of the optical modules, refer to Table 1-9.

5) Ethernet electrical interface cables

Usually, you can use a category-5 twisted pair cable to connect an electrical interface to an Ethernet. Figure 1-8 shows an Ethernet cable.

Figure 1-8 Ethernet cable

Ethernet cables fall into the following two categories:

l Standard cable: Also called straight-through cable. At both ends of a standard cable, wires are crimped in the RJ-45 connectors in the same sequence. A straight-through cable is used to connect a terminal (for example, PC or router) to a Hub or LAN Switch.

l Crossover cable: At both ends of a crossover cable, wires are crimped in the RJ-45 connectors in different sequences. A crossover cable is used to connect a terminal (for example, a PC or router) to another terminal. You can make crossover cables by yourself as needed.

Table 1-10 Straight-through cable pinouts

RJ-45	Signal	Category-5 twisted pair	Signal direction	RJ-45
1	TX+	White (Orange)	à	1
2	TX-	Orange	à	2
3	RX+	White (Green)	ß	3
4	—	Blue	—	4
5	—	White (Blue)	—	5
6	RX-	Green	ß	6
7	—	White (Brown)	—	7
8	—	Brown	—	8

Table 1-11 Crossover cable pinouts

RJ-45	Signal	Category-5 twisted pair	Signal direction	RJ-45
1	TX+	White (Orange)	à	3
2	TX-	Orange	à	6
3	RX+	White (Green)	ß	1
4	—	Blue	—	4
5	—	White (Blue)	—	5
6	RX-	Green	ß	2
7	—	White (Brown)	—	7
8	—	Brown	—	8

l You can refer to the table above when distinguishing between or preparing these two types of Ethernet cables.

l When preparing Ethernet cables, please follow the chromatogram given in the table to arrange the wires. Otherwise communication quality will be affected even if the devices at both ends are connected.

Fans

The WX5004 is equipped with five fans: three fans for heat dissipation of the main board and two fans for heat dissipation of the expansion card. If no expansion card is installed, these two fans do not work.

Interface Numbering

The WX5004 provides four fixed GE interfaces numbered GigabitEthernet 1/0/1 through GigabitEthernet 1/0/4, with the last part of the port numbers indicated on the front panel

2 Installation Preparation

Safety Precautions

Installation and removal of the unit and its accessories must be carried out by qualified personnel. You must read all of the Safety Instructions supplied with your device before installation and operation.

Installation und Ausbau der Anlage und ihrer Zubehörteile müssen von qualifiziertem Personal realisiert werden. Sie müssen vor der Installation oder Bedienung allen beiliegenden Sicherheitshinweise lesen.

负责安装和日常维护本设备的人员必须具备安全操作基本技能。在操作本设备前，请务必认真阅读和执行产品手册规定的安全规范。

To avoid any device impairment and bodily injury caused by improper use, observe these rules:

l Pull the power plug(s) out of the access controller before cleaning it. Do not clean the access controller using wet cloth or liquid.

l Keep the access controller away from water or dampness. Prevent water or moisture from entering the chassis of the access controller.

l Do not place the access controller on an unstable case or desk. The access controller might be damaged severely in case of a fall.

l Ensure proper ventilation of the equipment room and keep the ventilation vents of the access controller free of obstruction.

l Make sure that the operating voltage is the same one labeled on the access controller.

l Do not open the chassis when the access controller is operating or when electrical hazards are present to avoid electrical shocks.

l When replacing interface modules, wear the ESD-preventive wrist strap to avoid damaging the interface modules.

Installation Site Checking

The WX5004 must be used indoors. You can mount the WX5004 in a cabinet or on a workbench, but make sure that:

l Adequate clearance is reserved at the air inlet/exhaust vents for heat dissipation.

l The cabinet or workbench is in the environment that has a good ventilation system.

l The cabinet is sturdy enough to support the access controller and its accessories.

l The cabinet or workbench is well earthed.

To ensure normal operation and long service life of your access controller, install it in an environment that meets the requirements described in the following subsections.

Requirements on Temperature and Humidity

To ensure the normal operation and service lifetime of the access controller, proper temperature and humidity should be maintained in the equipment room.

l A long term of high humidity may lead to bad insulation, electricity leakage, mechanical property changes, and metal components corrosion.

l If the relative humidity is too low, captive screws may become loose as a result of contraction of insulation washers and static electricity may be produced in a dry environment to endanger the circuits on the access controller.

l A high temperature is the most undesirable condition, because it accelerates the aging of insulation materials and thus significantly lowers the reliability and service life of the access controller.

The following table lists temperature and humidity requirements for the WX5004.

Table 2-1 Operating environment

Item	Description
Operating temperature	0°C to 45°C (32°F to 113°F)
Relative humidity (noncondensing)	5% to 95%

Requirements on Cleanness

Dust is a hazard to the operating safety of the access controller. The dust accumulated on the chassis can be adsorbed by static electricity and result in poor contact of metal connectors or metal contact points. Especially, when the relative indoor humidity is low, electrostatic adsorption is more likely to happen. This can not only shorten the service life of the access controller but also cause communications failures. The following table lists the dust concentration limit.

Table 2-2 Dust concentration limit in the equipment room

Physical active substance	Concentration limit (particles/m³)
Dust	≤ 3 × 10⁴(No visible dust on the tabletop over three days)
Note: The dust particle diameter is ≥ 5 μm

Besides the dust specifications, the equipment room of the access controller also needs to strictly meet the requirements on the concentration of salt, acid and sulfide. These harmful gases can accelerate the metallic corrosion and the aging process of some parts. The specific limits of the harmful gases such as are given in the following table.

Table 2-3 Limit on harmful gases in the equipment room

Gas	Maximum concentration (mg/m³)
SO₂	0.2
H₂S	0.006
NH₃	0.05
Cl₂	0.01

Anti-Static Requirements

Generation and damage of static electricity

In the communication network to which the WX5004 is connected, static induction of the access controller mainly comes from the following sources:

l External electric fields, such as outdoor high-voltage transmission lines or thunderbolts.

l Internal environment like flooring materials or the structure of the overall system.

Although the WX5004 is designed to be Electrostatic Discharge (ESD) preventive, excessive static electricity may enormously damage the card circuits or even the whole device.

Protection measures

To prevent electrostatic damage, observe the following:

l Ensure that the access controller and the floor is well grounded.

l Keep the equipment room clean.

l Maintain suitable temperature and humidity;

l Wear ESD-preventive gloves or an ESD-preventive wrist strap and uniform when handling the circuit board.

l Hold the interface module only by its edge when installing, observing or removing it. Do not touch the components on it.

l Place the removed interface module on an ESD-preventive workbench with the component-side facing upward or place it in an antistatic bag.

Wearing ESD-Preventive Wrist Strap

No ESD-preventive wrist strap is shipped with the access controller. You need to purchase one if needed.

Follow these steps to use an ESD-preventive wrist strap:

1) Put on the ESD-preventive wrist strap.

2) Fasten the ESD-preventive wrist strap and verify that it makes good skin contact.

3) Lock the terminal of the alligator clip to the ESD-preventive wrist strap.

4) Attach the alligator clip to the rack where the access controller is installed.

5) Make sure that the rack has been well-grounded.

Figure 2-1 Use ESD-preventive wrist strap

(1) ESD-preventive wrist strap

(2) Locker

(3) Alligator clip

Electromagnetic Environment Requirements

The operation of your access controller may be affected by external interferences, such as capacitance coupling, inductance coupling, electromagnetic wave radiation, common impedance (including the grounding system) coupling, and the conducted interference of leads (power cords, signaling cables and output wires). To eliminate the interferences,

l Use the TN power system as the AC power supply system. A TN power system is called zero connection protection system. It is a power distribution system with one point connected directly to earth (ground). The exposed conductive parts and the neutral metal parts of the installation are connected to that point by protective earth conductors. Use a single-phase three-wire power socket with a protection earth (PE) to effectively filter interference from the power grid.

l Keep the access controller far from high-power radio transmitters, radars, and high-frequency heavy-current devices.

l Use electromagnetic shielding measures when necessary. For example, use shielded interface cables.

l Route interface cables only indoors to prevent signal ports from getting damaged by over-voltage or over-current caused by lightning strikes.

Laser Safety

The WX5004 is a Class 1 laser device.

When the optional optical ports on the WX5004 are operating, avoid staring into the optical interfaces because the high-energy laser beam emitted from the optical fiber may hurt your retina.

Do not stare the laser beam of an optical fiber. Otherwise, your eyes may be hurt.

Installation Tools

l Flat-blade screwdriver

l Phillips screwdriver: P2-150mm

l ESD-preventive wrist strap

No installation tool or ESD-preventive wrist strap is provided with the access controller. You need to prepare them yourself.

3 Installation

When you ask your sales agent to maintain your access controller, you must ensure that the dismantlement-preventive seal on a mounting screw of the access controller chassis is intact. If you want to open the chassis, you should contact the agent for permission. Otherwise, you will bear any consequence resulting from your actions.

Installation Procedure

Figure 3-1 Installation procedure

The WX5004 can be installed in either a standard 19-inch rack or a workbench as needed.

Installing the Access Controller onto a 19-Inch Rack

The access controller can be installed onto a 19-inch standard rack in one of the following approaches:

l Installing the access controller with front and rear mounting brackets

l Installing the access controller with front mounting brackets and a tray

l Installing the access controller with front mounting brackets and slide rails

Installing the Access Controller with Front and Rear Mounting Brackets

Mounting bracket structure

1) Appearance of a front mounting bracket

Figure 3-2 Front mounting bracket appearance

(1) Screw hole for fixing the front mounting bracket to the rack (use M6 screws)

(2) Screw hole for fixing the front mounting bracket to the access controller

2) Appearance of a rear mounting bracket

Figure 3-3 Rear mounting bracket appearance

(1) Screw hole for fixing the rear mounting bracket to the rack (use M6 screws)

(2) Heat dissipation hole

Installation procedure

1) Put on the EAD-preventive wrist strap and check that the rack is sturdy and properly earthed.

2) Take out the screws, which are packaged with the front mounting brackets. Attach the front mounting brackets to the access controller with the screws, as shown in Figure 3-4.

Figure 3-4 Install front mounting brackets to both sides of the access controller

3) Take out the bearing screws, which are packaged with rear mounting brackets. Attach a bearing screw into the proper installation hole on the rear, upper right and left sides of the access controller respectively, as shown in Figure 3-5.

Figure 3-5 Install bearing screws into the access controller

(1) Three installation holes for bearing screws (choose one as needed)

(2) Bearing screw

There are three screw holes on both the right and left sides of the rear, and upper part of the access controller for installing the bearing screws. You need to choose a proper hole to install a bearing screw to each side. The rear mounting brackets can support the weight of the access controller through firm contact with the bearing screws.

4) Determine the position for installing the access controller on the rack. Use screws and the corresponding cage nuts to fix the rear mounting brackets to the rear square-hole rack rails, as shown in Figure 3-6.

Figure 3-6 Install rear mounting brackets to the rack

(1) Rear square-hole rack rails

5) Support the bottom of your access controller with one hand and hold the front part of the access controller with the other hand, and then gently push the access controller into the rack, as shown in Figure 3-7.

Figure 3-7 Installation with front and rear mounting brackets

(1) Front mounting bracket	(2) Front square-hole rack rail	(3) Bearing screw
(4) Screw for fixing the rear mounting bracket to the rear square-hole rack rail
(5) Rear mounting bracket	(6) Rear square-hole rack rail

6) After the access controller is pushed in, make sure that the upper side of the rear mounting brackets and the bearing screws are closely touched, as shown in Figure 3-8.

Figure 3-8 Installation with front and rear mounting brackets

(1) Rear square-hole rack rail	(2) Bearing screw
(3) Rear mounting bracket

7) Use screws and the corresponding cage nuts to fix the front mounting brackets to the front square-hole rack rails, so that the front and rear mounting brackets can fix the access controller on the rack horizontally and steadily, as shown in Figure 3-9.

Figure 3-9 Installation with front and rear mounting brackets

(1) Front square-hole rack rail

(2) Front mounting bracket

Installing the Access Controller with Front Mounting Brackets and a Tray

The tray is an optional component, which needs to be separately ordered if needed.

Installation procedure with front mounting brackets and a tray:

1) Put on the EAD-preventive wrist strap and check that the rack is sturdy and properly earthed.

2) Take out the screws, which are packaged with the front mounting brackets. Attach the front mounting brackets to the access controller with the screws, as shown in Figure 3-4.

3) Fix the tray horizontally to a proper poison on the rack, as shown in Figure 3-10. (This figure is just for your reference. The installation may differ on a different rack.)

Figure 3-10 Install a tray

4) Place the access controller on the tray horizontally, gently push the access controller into the rack along the tray, and then use screws and the corresponding cage nuts to fix the front mounting brackets to the front square-hole rack rails of the rack, as shown in Figure 3-11.

Figure 3-11 Installation with front mounting brackets and a tray

Installing the Access Controller with Mounting Brackets and Slide Rails

l Slide rails are optional components, which need to be separately ordered if needed.

l H3C slide rails are suitable for only the H3C standard racks with a depth of 1000 mm (39.37 in.). If the depth of your rack is different, substitute other supports for the slide rails.

Slide rail appearance

Figure 3-12 Appearance of a slide rail

(1) Slotted hole, a screw hole for fixing the slide rail to the rear round-hole rack rail of the rack. You can adjust the screw position within the screw hole according to the device position.

(2) Heat dissipation hole. It is for heat dissipation between the device and rack.

(3) Slotted hole, a screw hole for fixing the slide rail to the front round-hole rack rail of the rack.

Installation procedure

1) Put on the EAD-preventive wrist strap and check that the rack is sturdy and properly earthed.

2) Take out the screws, which are packaged with the front mounting brackets. Attach one end of the front mounting brackets to the access controller with the screws, as shown in Figure 3-4.

3) Install the slide rails to the round-hole rack rails at both sides of the rack using M5 tapping screws, as shown in Figure 3-13. (This figure is just for your reference. The installation may differ on a different rack.)

Figure 3-13 Install slide rails

4) Hold the two sides of the access controller with both hands, and then slightly slide the access controller into a proper position of the rack, as shown in Figure 3-14. Make sure that the bottom of the access controller is closely touched with the slide rails.

Figure 3-14 Installation with front mounting brackets and slide rails

5) Use M6 screws and cage nuts to fix the front mounting brackets to the front square-hole rack rails, so that the front mounting brackets and the slide rails can fix the access controller on the rack steadily, as shown in Figure 3-15.

Figure 3-15 Installation with front mounting brackets and slide rails (diagram 2)

Make sure that there is at least 1 U (44.45 mm, 1.75 in.) height away from neighbor devices for heat dissipation.

Installing the Access Controller on a Workbench

In case the standard 19-inch rack is not available, you can install the access controller on a clean workbench. When installing the access controller on a workbench,

l Make sure that the workbench is flat, sturdy and well earthed.

l Keep the environment well ventilated and reserve a clearance of 10 cm (3.9 in.) around the chassis for heat dissipation.

l Place no heavy objects on the access controller.

l Keep at least a vertical distance of 1.5 cm (0.59 in.) between access controllers when they are placed one above the other.

Connecting the Ground Wire

The correct connection of the protection ground (PGND) wire of the access controller is an essential safeguard against lightning strokes and electromagnetic susceptibility (EMS) interference. You must first correctly connect the PGND wire when installing the access controller.

The power input end of the access controller is connected with a noise filter, whose central ground is directly connected to the chassis, forming the chassis ground (also known as PGND). This chassis ground must be securely grounded so that induced and leaked electricity can be safely discharged to the ground, enhancing the anti-EMS capability of the access controller. Ground the access controller as follows:

When a grounding strip is available

1) Remove the grounding terminal screw located at the right back of the chassis, as shown in Figure 3-16.

2) Fasten the wiring terminal of the yellow-green PGND wire of the access controller to the grounding terminal screw you removed in step 1.

3) Put the grounding terminal screw back to the grounding hole on the chassis and fasten it.

4) Fasten the other end of the yellow-green PGND wire to the grounding stud for the access controller on the grounding strip.

5) On the grounding strip, use a nut to fasten the grounding stud that is attached with the PGND wire.

Figure 3-16 Ground the access controller through a grounding strip

(1) AC power socket	(2) Grounding terminal
(3) PGND wire	(4) Grounding strip

The fire main and lightning rod of a building are not good grounding options. The ground wire of the access controller should be connected to the grounding system in the equipment room.

When a grounding strip is unavailable

1) If earth is available nearby and allows a grounding body to be buried

Hammer an angle steel or steel pipe longer than 0.5 m (1.64 ft) into the earth. In this case, weld the yellow-green PGND wire of the access controller onto the angle steel or steel pipe, and treat the joint for corrosion protection.

Figure 3-17 Ground the access controller through a grounding body

(1) AC power socket	(2) Grounding terminal	(3) PGND wire
(4) Earth	(5) Angle steel

2) If no grounding body is allowed to be buried

This method applies to the device using AC power input.

If the access controller is AC powered, you can ground the access controller through a PE wire of the AC power supply. In this case, make sure the PE wire is well connected to the ground in the power distribution room or on the AC transformer side.

Figure 3-18 Ground the access controller through an AC PE wire

(1) Power transformer	(2) AC power socket	(3) Grounding terminal
(4) Three-core AC power cord	(5) PE wire

Connecting the Power Cord

Make sure that the ground wire is properly connected before powering on the access controller.

If the device is AC-powered, connect the device with an external AC power system through an AC power cord; if the device is DC-powered, connect the device with an external DC power system through a DC power cord.

Connecting the AC Power Cord

Follow the steps below to connect the AC power cord:

1) Make sure that the PGND of the access controller is correctly connected.

2) Install the AC power cord retainer to the access controller, and turn the retainer left.

3) Connect one end of the power cord to either power socket on the rear panel of the chassis, and the other end to the AC power supply.

4) Turn the power cord retainer right to lock the power cord plug.

Figure 3-19 Install the AC power cord retainer

(1) Rear panel	(2) Power cord retainer slot
(3) AC power cord retainer	(4) AC power cord

5) Check the corresponding PWR LED on the front panel of the access controller. If the LED is solid green, the AC power input is normal.

l The AC power cord retainer can prevent the AC power cord from accidentally falling off.

l Whether a power cord retainer is needed depends on the power supply system of the country.

Connecting the DC Power Cord

Follow the steps below to connect the DC power cord:

1) Make sure that the PGND of the access controller is correctly connected.

2) Insert the DC connector with upside on top into the DC power receptacle of the power module, as shown in callout 1 of Figure 3-20. (If the connector is inserted with the upside down, the insertion is not smooth due to the specific design of the receptacle and connector.)

3) Fix the screws on the two sides of the DC connector using a flat-blade screwdriver until the connector is secured to the DC power receptacle, as shown in callout 2 of Figure 3-20.

4) Connect the other end of the power cord to the external DC power supply.

5) Check the corresponding PWR LED on the front panel of the access controller. If the LED is solid green, the DC power input is normal.

Figure 3-20 Connect the DC power cord

Connecting Interface Cables

Connecting the Console Cable

1) Select a terminal for configuration.

The terminal can be a character terminal with a standard RS232 serial port or a PC. A PC is used in this example.

2) Connect the console cable

Power off the access controller, connect the DB-9 female connector of the console cable to the serial interface of the PC, and connect the RJ-45 connector of the console cable to the console port of the access controller.

Pay attention to the interface mark and plug the connector to the right interface.

Figure 3-21 Connect the console cable

(1) RJ-45 connector	(2) Console port	(3) DB-9 (female) connector
(4) Serial interface of the configuration terminal		(5) Console cable

For a powered-on access controller:

l When connecting a PC to the access controller, you are recommended to first connect the DB-9 connector of the console cable to the PC, and then the RJ-45 connector to the console port of the access controller.

l When disconnecting a PC from the access controller, you are recommended to first disconnect the RJ-45 connector, and then the DB-9 connector.

Connecting the Ethernet Cable

To an the Ethernet electrical interface

1) Connect one end of the Ethernet cable to an Ethernet electrical interface of the access controller and the other end to an Ethernet interface of the peer device.

2) After powering on the access controller, check the LED of the Ethernet electrical interface. For description on the LED status, refer to section “LEDs” on page 1-4.

To an the Ethernet optical interface

To connect a 1000 Mbps optical interface, follow these steps:

1) Align the end without handle of an SFP module with an SFP interface and insert the SFP module into the SFP interface carefully.

Figure 3-22 Insert an SFP module

2) Distinguish between the Rx and Tx interfaces on the SFP module. Connect the LC connector at one end of an optical fiber to the Rx interface of the access controller and the LC connector at the other end of the optical fiber to the Tx interface of the peer device. Use another fiber to connect the access controller and the peer device in the opposite way.

Figure 3-23 Plug LC connectors

3) Power on the access controller and check the SFP interface LEDs. For description on SFP LED status, refer to section “LEDs” on page 1-4.

When connecting optical fibers, make sure that:

l The curvature radius of fibers is no less than 10 cm (3.9 in.).

l The Tx and Rx connectors are correctly connected.

l The fiber ends are clean.

Checking the Installation

After installation, make sure that:

l The correct power supply is used.

l The ground wire is properly connected.

l Both the console cable and power cord are correctly connected.

l All interface cables are routed indoors. If there are cables outdoors, check that lightning arresters for the AC power strip and network interfaces have been correctly connected. For how to connect the lightning arresters for the AC power supply and network interfaces, refer to Appendix A and B.

4 Initial Startup

Setting up the Configuration Environment

Connecting a Configuration Terminal to the Access Controller

For how to connect a configuration terminal to the access controller, refer to section “Connecting Interface Cables” on page 3-13.

Setting Terminal Parameters

Step1 Start the PC and run the terminal emulation program such as the Terminal of Windows 3.1 or the HyperTerminal of Windows 95/98/NT/2000/XP.

Step2 Select Start > Program > Accessories > Communications > HyperTerminal. On the Connection Description interface, type the name of the new connection and click OK, as shown in Figure 4-1.

Figure 4-1 Connection description interface

Step3 The system displays the Connect To interface, as shown in Figure 4-2. From the Connect using drop-down list, select the serial interface to be used. (Be sure to select the serial interface to which the console cable is actually connected.)

Figure 4-2 Select the serial interface used for HyperTerminal connection

Step4 Click OK and the system displays the following interface, as shown in Figure 4-3. On the interface, set Bits per second to 9600, Data bits to 8, Parity to None, Stop bits to 1, and Flow control to None.

Figure 4-3 Set serial port parameters

To use the default settings, click Restore Defaults.

Step5 Click OK and the system displays the HyperTerminal interface.

Figure 4-4 HyperTerminal window

Step6 Set HyperTerminal properties. Select File > Properties > Settings in the HyperTerminal to enter the properties setting window, as shown in Figure 4-5. Select VT100 as the terminal emulation, and click OK.

Figure 4-5 Set terminal emulation

Powering On the Access Controller

Checking Before Power-On

Before powering on the access controller, verify that:

l The power cord and the ground wire are properly connected.

l The power supply voltage is within the range that required by the access controller.

l The console cable is properly connected; the terminal (for example, a PC) used for configuration has been started; the configuration parameters have been set.

Powering on the Access Controller

After the access controller is powered on, the system first initializes memory. After the initiation, the system runs the extended BootWare, and the following information is displayed on the terminal:

System is starting...

Booting Normal Extend BootWare....

The Extend BootWare is self-decompressing..................

Done!

**************************************************************************

* *

* H3C WX5004 BootWare, Version 1.06 *

* *

**************************************************************************

Compiled Date : Nov 9 2009

CPU Type : XLR716

CPU L1 Cache : 32KB

CPU Clock Speed : 800MHz

Memory Type : DDR2 SDRAM

Memory Size : 2048MB

Memory Speed : 533MHz

BootWare Size : 512KB

Flash Size : 4MB

cfa0 Size : 261MB

CPLD Version : 008

PCB Version : Ver.A

BootWare Validating...

Press Ctrl+B to enter extended boot menu...

Press Ctrl+B to enter the extended boot menu; otherwise, the system will start loading and decompressing the application file.

l You must press Ctrl+B in four seconds when “Press Ctrl+B to enter extended boot menu” appears. Otherwise, the system will not enter the extended boot menu but start loading and decompressing the application file.

l You need to reboot the access controller if you want to enter the extended boot menu after the application file is decompressed.

l The extended BootWare menu is referred to as the BootWare main menu in this manual unless otherwise specified.

Starting to get the main application file--cfa0:/main.bin!...............................

.........................................

The main application file is self-decompressing.........................................

........................................................................................

.................................................

Done!

System is starting...

Startup configuration file does not exist.

User interface con0 is available.

Press ENTER to get started.

Press Enter. The following prompt is displayed:

<H3C>

The prompt indicates that the system has entered user view and you can configure the access controller now.

5 Software Maintenance

Overview

Files Managed by the Access Controller

The WX5004 manages the following three types of files:

l BootWare program file

l Application file

l Configuration file

BootWare Program File

The BootWare program file is used to boot the applications when the access controller is started up. The complete BootWare program file consists of two segments: basic and extended.

l Basic BootWare implements the basic system initialization.

l Extended BootWare provides abundant human-computer interaction (HCI) functions. It is used for interface initialization for upgrading applications and booting the system.

l The full BootWare refers to the combination of the two segments. After the basic BootWare is booted, you can load or upgrade the extended BootWare on the menu of the basic BootWare.

Do not power off or restart the access controller during BootWare upgrade process; otherwise, the BootWare program may be damaged and the access controller may fail to operate normally.

Application Files

The WX5004 supports the Dual Image function. By default, three application files are defined for system boot:

l Main application file (main file)

l Backup application file (backup file)

l Secure application file (secure file)

These files are stored on the built-in CF card, with the extension .bin.

Typically, the default application file is written into the built-in CF card of an access controller before it is delivered.

If you have loaded the three application files to the CF card, the system uses these three files to boot the access controller in the sequence of main.bin, backup.bin, and secure.bin. For how to set the application file types, refer to section “Maintaining Application and Configuration Files” on page 5-22.

The default names and types of the application files and their loading priorities for booting are as follows.

l Main application file. The default name is main.bin, and the file type is M. It is the default application file used for booting.

l Backup application file. The default name is backup.bin, and the file type is B. When the boot using the main application file fails, the system boots using the backup application file.

l Secure application file. The default name is secure.bin, and the file type is S. When boot using the backup application file fails, the system tries the secure application file. If the boot using the secure application file fails, the system prompts a boot failure.

Note that:

l The application files for system boot can be type M, B and S, but not type N/A.

l After the application program is loaded, you can rename the application files through the command line interface (CLI) or change the file type (M, B or N/A) through the BootWare menu or the CLI. However, you cannot change the file type of the S-type application file.

l As the secure application file is the last resort for system boot, you cannot change the type of the secure application file, or change other types of files to the secure application file. You can only download it by selecting the “Update Secure Application File” option on the BootWare menu.

l Only one file of the same type (M, B, or S) can exist on the CF card. For instance, if an application file of type M+B exists on the CF card, another file of type M or B cannot exist. If the type of another file is changed to B, the existing type M+B file changes to a file of type M.

Configuration Files

Configuration files store configuration information of the access controller, with the extension of .cfg. Typically, the access controller has no configuration file when it is delivered.

The configuration files generated by users are saved in the built-in CF card, with the default name startup.cfg.

l The length of a configuration file name must no exceed 64 characters (including the drive name and the string terminator). For example, if the drive name is cfa0:/, the maximum length of a file name is [64–1–6] = 57 characters.

l If the length of a file name exceeds 57 characters, error will occur in file operations on that file. Generally, it is recommended to keep the file name within 16 characters.

l There is a limitation on the length of file name that can be displayed in BootWare. If a file name is shorter than 30 characters, all the characters of the file name can be displayed; if a file name has or exceeds 30 characters, only the first 26 characters of the file name can be displayed, followed by a tilde (~) and a serial number. The serial number identifies position in sequence of the file. For example, if three files, file A, file B and file C, have a file name longer than 30 characters, the name of file A will appear as the first 26 characters plus ~001, that of file B will appear as the first 26 characters plus ~002, and that of file C will appear as the first 26 characters plus ~003.

Approaches for Software Maintenance

You can maintain the access controller in one of the following three ways:

l Upgrade BootWare and application files using the XMODEM protocol through a serial interface.

l Upgrade application files using TFTP/FTP through an Ethernet interface on the BootWare menu.

l Upload/download application files and configuration files using TFTP/FTP through command lines.

l The BootWare program is upgraded together with the host software program version. That is, the system automatically upgrades the BootWare program when you upgrade the host software program.

l Before upgrading the software of your access controller, check the current BootWare version and application program version to make sure that the correct file is used for the upgrade. For the association between the host software version and the BootWare version, refer to the version compatibility matrix in Release Notes.

BootWare and Application File Upgrade Flow

Figure 5-1 BootWare and application file upgrade flow

BootWare Menus

BootWare Main Menu

When a device is powered on or restated, the terminal first displays the following information:

System is starting...

Then, the system displays the following:

Booting Normal Extend BootWare....

The Extend BootWare is self-decompressing..................

Done!

****************************************************************************

* *

* H3C WX5004 BootWare, Version 1.06 *

* *

****************************************************************************

Compiled Date : Nov 9 2009

CPU Type : XLR716

CPU L1 Cache : 32KB

CPU Clock Speed : 800MHz

Memory Type : DDR2 SDRAM

Memory Size : 2048MB

Memory Speed : 533MHz

BootWare Size : 512KB

Flash Size : 4MB

cfa0 Size : 261MB

CPLD Version : 008

PCB Version : Ver.A

BootWare Validating...

Press Ctrl+B to enter extended boot menu...

The extended boot menu is referred to as the BootWare main menu in this manual unless otherwise specified.

Press Ctrl + B when the system prompts “Press Ctrl+B to enter extended boot menu”. Then, the system prompts you to enter the BootWare password:

Please input BootWare password:

You have three chances to enter the BootWare password (the initial password is null). If you fail to enter the correct password three times in a row, the system will be halted and you can only restart the system. After you provide the correct password, the system enters the BootWare main menu:

Note: The current operating device is cfa0

Enter < Storage Device Operation > to select device.

=============================<EXTEND-BOOTWARE MENU>=============================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Modify BootWare Password |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Clear Super Password |

|<9> Storage Device Operation |

|<0> Reboot |

================================================================================

Enter your choice(0-9):

BootWare Submenus

Serial submenu

You can upgrade application files, change the serial interface baud rate, and so on through the serial submenu.

Enter 2 on the BootWare main menu to enter the serial submenu. The system displays:

=============================<Enter Serial SubMenu>=============================

|Note:the operating device is cfa0 |

|<1> Download Application Program To SDRAM And Run |

|<2> Update Main Application File |

|<3> Update Backup Application File |

|<4> Update Secure Application File |

|<5> Modify Serial Interface Parameter |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-5):

Ethernet submenu

Enter 3 on the BootWare main menu to enter the Ethernet submenu. The system displays:

============================<Enter Ethernet SubMenu>============================

|Note:the operating device is cfa0 |

|<1> Download Application Program To SDRAM And Run |

|<2> Update Main Application File |

|<3> Update Backup Application File |

|<4> Update Secure Application File |

|<5> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

|<Ensure The Parameter Be Modified Before Downloading!> |

================================================================================

Enter your choice(0-5):

Items in this submenu are described in the following table.

File control submenu

Enter 4 on the BootWare main menu to enter the file control submenu. The following information is displayed:

=================================<File CONTROL>=================================

|Note:the operating device is cfa0 |

|<1> Display All File(s) |

|<2> Set Application File type |

|<3> Delete File |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-3):

BootWare operation submenu

Enter 7 on the BootWare main menu to enter the BootWare operation submenu. The system displays:

===========================<BootWare Operation Menu>============================

|Note:the operating device is cfa0 |

|<1> Backup Full BootWare |

|<2> Restore Full BootWare |

|<3> Update BootWare By Serial |

|<4> Update BootWare By Ethernet |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-4):

Storage device operation submenu

Enter 9 on the BootWare main menu to enter the storage device operation submenu. The system displays:

================================<DEVICE CONTROL>================================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-3):

Upgrading the BootWare Through a Ethernet/Serial Interface

To upgrade the BootWare through a serial interface, use the XMODEM protocol.

XMODEM is a file transfer protocol that is widely used due to its simplicity and good performance. XMODEM transfers files through serial interfaces. It supports two types of data packets (128 bytes and 1 KB), two check methods (checksum and CRC), and error packet retransmission mechanism (generally the maximum number of retransmission attempts is ten).

The XMODEM transmission procedure is completed by the cooperation of a receiving program and a sending program. The receiving program sends a negotiation character to negotiate a packet check method. After the negotiation, the sending program starts to send data packets. Upon receiving a complete packet, the receiving program checks the packet using the agreed check method.

l If the check succeeds, the receiving program sends an acknowledgement character and the sending program proceeds to send another packet.

l If the check fails, the receiving program sends a negative acknowledgement character and then the sending program retransmits the packet.

l The BootWare program is upgraded together with the Comware application. When you upgrade the Comware application program, the system automatically checks whether the current BootWare version is compliant with that included the updated Comware application and upgrades the current BootWare if needed.

l Before upgrading the software of your access controller, check the current BootWare version and Comware application version to make sure that the correct file is used for the upgrade. For the association between the Comware application version and the BootWare version, refer to the version compatibility matrix in Release Notes.

Modifying Serial Interface Parameters

Sometimes, we need a high serial interface baud rate to save the update time, or a low baud rate to ensure transmission reliability. This section introduces how to adjust the serial interface baud rate.

Enter the BootWare main menu and enter 2 to go to the serial submenu, and then enter 5 on the submenu to modify the baud rate. The system displays the following:

=================================<BAUDRATE SET>=============================

|Note:'*'indicates the current baudrate |

| Change The HyperTerminal's Baudrate Accordingly |

|---------------------------<Baudrate Available>------------------------- |

|<1> 9600(Default)* |

|<2> 19200 |

|<3> 38400 |

|<4> 57600 |

|<5> 115200 |

|<0> Exit |

============================================================================

Enter your choice(0-5):

Select a proper baud rate. For example, enter 5 for a baud rate of 115200 bps and the system displays the following information:

Baudrate has been changed to 115200 bps.

Please change the terminal's baudrate to 115200 bps, press ENTER when ready.

At this time, the serial interface baud rate of the access controller is modified to 115200 bps, while that of the terminal is still 9600 bps. The access controller and the terminal cannot communicate with each other. Change the baud rate to 115200 bps on the terminal.

Perform the following operations on the terminal:

Figure 5-2 Disconnect the terminal

Select File > Properties, In the Properties dialog box, click Configure… and then Set the Bits per second to 115200.

Figure 5-3 Modify the baud rate

Select Call > Call to establish a new connection.

Figure 5-4 Re-establish a call connection

Then, press the Enter key, and the system will prompt the current baud rate.

The current baudrate is 115200 bps

==============================<BAUDRATE SET>=============================

|Note:'*'indicates the current baudrate |

| Change The HyperTerminal's Baudrate Accordingly |

|---------------------------<Baudrate Available>-------------------------|

|<1> 9600(Default) |

|<2> 19200 |

|<3> 38400 |

|<4> 57600 |

|<5> 115200* |

|<0> Exit |

==========================================================================

Enter your choice(0-5):

After downloading files with a changed baud rate, timely change the baud rate back to 9,600 bps in HyperTerminal to ensure the normal display on the console screen when the system boots or reboots.

Upgrading the BootWare Through an Ethernet Interface

Enter the BootWare main menu (refer to section “BootWare Main Menu” on page 5-4). On the BootWare main menu, enter 7. The system will enter the BootWare operation submenu, where you can perform all BootWare operations. For details about this menu, refer to section “BootWare operation submenu” on page 5-7.

Enter 4 on the BootWare operation submenu to enter the BootWare operation Ethernet submenu:

=====================<BOOTWARE OPERATION ETHERNET SUB-MENU>=====================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-4):

Enter 4 on the BootWare operation Ethernet submenu. The system prompts you to modify the network parameters.

============================<ETHERNET PARAMETER SET>============================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

================================================================================

Protocol (FTP or TFTP) :tftp

Load File Name :host

:main.bin

Target File Name :target

:main.bin

Server IP Address :192.168.0.1

Local IP Address :192.168.0.10

Gateway IP Address :0.0.0.0

The load file name and the target file name must not exceed 50 bytes.

After modification of the parameters, the system display returns to the BootWare operation Ethernet submenu.

=====================<BOOTWARE OPERATION ETHERNET SUB-MENU>=====================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-4):

Enter 1 on the BootWare operation Ethernet submenu.

The system displays:

Loading...................................................................

..........................................................................

.........................................................Done!

20710792 bytes downloaded!

Updating Basic BootWare? [Y/N]Y

Updating Basic BootWare................Done!

Updating Extend BootWare? [Y/N]Y

Updating Extend BootWare..............Done!

After download of the BootWare program file, the system display returns to the BootWare operation Ethernet submenu.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

Enter 0 on this menu to return to the BootWare operation submenu:

=========================<BootWare Operation Menu>==========================

|Note:the operating device is cfa0 |

|<1> Backup Full BootWare |

|<2> Restore Full BootWare |

|<3> Update BootWare By Serial |

|<4> Update BootWare By Ethernet |

|<0> Exit To Main Menu |

===========================================================================

Enter your choice(0-4):

Enter 0 on the BootWare operation submenu to return to the BootWare main menu:

===========================<EXTEND-BOOTWARE MENU>===========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Modify BootWare Password |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Clear Super Password |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Enter your choice(0-9): 0

Enter 0 on the BootWare main menu to reboot the access controller.

Upgrading the BootWare Through a Serial Interface

Enter the BootWare main menu (refer to section “BootWare Main Menu” on page 5-4). On the BootWare main menu, enter 7. The system will enter the BootWare operation submenu, where you can perform all BootWare operations. For detail description on this submenu, refer to section “BootWare operation submenu” on page 5-7.

Enter 3 on the BootWare operation submenu to enter the BootWare operation serial submenu:

======================<BOOTWARE OPERATION SERIAL SUB-MENU>======================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Serial Interface Parameter |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-4):

Enter 4 on the BootWare operation serial submenu. The system prompts you to modify the baud rate:

=================================<BAUDRATE SET>=================================

|Note:'*'indicates the current baudrate |

| Change The HyperTerminal's Baudrate Accordingly |

|-----------------------------<Baudrate Available>-----------------------------|

|<1> 9600(Default)* |

|<2> 19200 |

|<3> 38400 |

|<4> 57600 |

|<5> 115200 |

|<0> Exit |

================================================================================

Enter your choice(0-5):

Change the communication baud rate. For the detailed modification procedure, refer to section “Modifying Serial Interface Parameters” on page 5-8. After the modification, the system displays the following information:

Baudrate has been changed to 115200 bps.

Please change the terminal's baudrate to 115200 bps, press ENTER when ready.

The current baudrate is 115200 bps

=================================<BAUDRATE SET>=============================

|Note:'*'indicates the current baudrate |

| Change The HyperTerminal's Baudrate Accordingly |

|---------------------------<Baudrate Available>---------------------------|

|<1> 9600(Default) |

|<2> 19200 |

|<3> 38400 |

|<4> 57600 |

|<5> 115200* |

|<0> Exit |

============================================================================

Enter your choice(0-5):

Enter 0 to return to the BootWare operation serial submenu.

======================<BOOTWARE OPERATION SERIAL SUB-MENU>======================

|<1> Update Full BootWare |

|<2> Update Extend BootWare |

|<3> Update Basic BootWare |

|<4> Modify Serial Interface Parameter |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-4):

Enter 1 on the BootWare operation serial submenu. The system displays the following information:

Please Start To Transfer File, Press <Ctrl+C> To Exit.

Waiting ...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC

Select Transfer > Send file… on the terminal window. The following dialog box appears:

Figure 5-5 Send File dialog box

Click Browse… to select the application file to be downloaded, and select Xmodem from the Protocol drop-down list. Then click Send. The following dialog box appears:

Figure 5-6 Sending file dialog box

Upon successful download, the system displays the following information:

Download successfully!

10323456 bytes downloaded!

Updating Basic BootWare? [Y/N]Y

Updating Basic BootWare.................Done!

Updating Extend BootWare? [Y/N]Y

Updating Extend BootWare...........Done!

Change the baud rate on the configuration terminal from 115200 bps to 9600 bps, and then reboot the access controller.

l The actual file name, size and path may differ from what are shown in the figure above. Before upgrading the software of your access controller, check the current BootWare version and the application program version to ensure that the correct file is used for the upgrade.

l After you download files with a changed baud rate, timely change the baud rate in the HyperTerminal to 9600 bps to ensure the normal display on the console screen when the system boots or reboots.

Upgrading Applications Through a Serial Interface on the BootWare Menu

The application file upgrade through a serial port is implemented on the serial submenu. Enter 2 on the BootWare main menu to enter the serial submenu. For detailed description on this submenu, refer to section “Serial submenu” on page 5-6.

The following example shows how to upgrade the main application file.

To improve the upgrading speed, you can modify the serial interface baud rate before upgrading the file. (refer to section “Modifying Serial Interface Parameters” on page 5-8). Enter 2 on the serial submenu. The system displays the following information:

Please Start To Transfer File, Press <Ctrl+C> To Exit.

Waiting ...CCCCCCCCCC

Select and send the application file. The procedure for upgrading an application file through a serial interface is the same as upgrading the BootWare. For details, refer to section “Upgrading the BootWare Through a Ethernet/Serial Interface” on page 5-7.

The size of an application program is typically over 10 MB. Even at the maximum baud rate of 115200 bps, the upgrade will also take a long time. Therefore, it is not recommended to upgrade application files through a serial interface but through an Ethernet interface.

Upgrading Applications Through an Ethernet Interface on the BootWare Menu

Enter 3 on the BootWare main menu to enter the Ethernet submenu. For details, refer to section “Ethernet submenu” on page 5-6.

Configuring Ethernet Interface Parameters

Before upgrading an application program through an Ethernet interface, you need to configure the Ethernet interface of the access controller, as follows:

Enter 3 on the BootWare main menu to enter the Ethernet submenu. Then, enter 5 on the submenu to enter the Ethernet interface configuration interface:

============================<ETHERNET PARAMETER SET>============================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

================================================================================

Protocol (FTP or TFTP) :tftp

Load File Name :host

:main.bin

Target File Name :target

:main.bin

Server IP Address :192.168.0.1

Local IP Address :192.168.0.10

Gateway IP Address :0.0.0.0

l When configuring a parameter, you can enter a new value directly, or press Enter to accept the default value, which is after the colon. Type a dot (.) to clear the input, a hyphen (-) to return to the previous parameter field, and a combination of ^D (namely, Ctrl+D) to exit the parameter configuration interface.

l The WX5004 supports only GigabitEthernet 1/0/1 for application upgrade.

Upgrading Applications Through an Ethernet Interface

The Trivial File Transfer Protocol (TFTP) is a TCP/IP protocol used for file transfer between client and server. It provides a simple and low-cost file transfer service. TFTP provides unreliable data transfer over UDP and does not provide any access authorization and authentication mechanism. It employs the timeout retransmission method to implement best-effort delivery of data. Compared with FTP, TFTP has a much smaller software size.

Follow these steps to upgrade an application file through the management Ethernet interface (10/100 Base-TX):

Step1 Set up a software upgrade environment.

Figure 5-7 Set up a software upgrade environment

Connect GigabitEthernet 1/0/1 to a PC with an Ethernet cable. Run TFTP Server on the PC, and set the path of the application file to be downloaded.

The TFTP Server software is not provided with the WX5004. You need to prepare it yourself.

Step2 Modify the Ethernet interface parameters. For details, refer to section “Configuring Ethernet Interface Parameters” on page 5-15.

Step3 Enter 3 on the BootWare main menu to enter the Ethernet submenu. The following example shows how to upgrade the main application file. Enter 2 on the Ethernet submenu. The following information appears:

Loading.................................................................................

........................................................................................

.............................Done!

10323352 bytes downloaded!

Updating File cfa0:/main.bin

The file is exist,will you overwrite it? [Y/N]Y..............................................

........................................................................................

............................................................. ... ..........................Done!

Step4 Enter 0 to return to the BootWare main menu. Enter 1 on the BootWare main menu to reboot the access controller.

l If the downloaded file has the same name with an existing file on the CF card, the system prompts The file is exist, will you overwrite it? [Y/N]. If you choose Y, the existing file will be overwritten.

l Make sure that sufficient space is available on the CF card. In case of insufficient space, the system will give a prompt.

l The new application file directly replaces the existing file of the same type. In this example, the downloaded file main.bin replaces the existing application file of type M and becomes the only main application file.

l For details about the application file types, refer to section “Application Files” on page 5-1.

Maintaining the Application and Configuration Files Through the CLI

After the access controller is normally started, you can back up and restore the application and configuration files through the CLI.

Maintaining the Access Controller Through TFTP

Use the WX5004 as a TFTP client and a file server as the TFTP server. You can use commands on the configuration terminal, which can be the same file server, to upload the application and configuration files from the access controller to the file server or download the files from the file server to the access controller.

Setting up a configuration environment

Set up a network environment (for the procedure, refer to section “Upgrading Applications Through an Ethernet Interface” on page 5-16). Run the TFTP Server on the file server and set the file path.

Figure 5-8 Network diagram for software maintenance through the CLI

Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the TFTP server to 192.168.0.1, and that of the access controller’s management interface to 192.168.0.2. Then use ping to verify the network connectivity.

Backing up and restoring application and configuration files

After setting up the environment, perform the following operations on the PC:

View the files in the current file system with the dir command.

<H3C>dir

Directory of cfa0:/

0 -rw- 10295948 Sep 11 2053 02:17:14 main.bin

1 -rw- 33 Aug 20 2008 09:58:44 system.xml

2 -rw- 802 Aug 20 2008 09:58:44 startup.cfg

3 -rw- 76960 Aug 15 2008 15:58:02 vmetest.vme

253950 KB total (243028 KB free)

File system type of cfa0: FAT32

<H3C>

For example, to back up the file startup.cfg on the access controller and save it as config.bak on the TFTP server, use the following command:

<H3C>tftp 192.168.0.1 put startup.cfg config.bak

File will be transferred in binary mode

Sending file to remote TFTP server. Please wait... \

TFTP: 802 bytes sent in 10 second(s).

File uploaded successfully.

To download config.cfg from the TFTP server to the access controller, use the following command:

<H3C>tftp 192.168.0.1 get config.bak startup.cfg

File will be transferred in binary mode

Downloading file from remote TFTP server, please wait...

TFTP: 842 bytes received in 1 second(s)

File downloaded successfully.

If a file with the same name already exists on the access controller, the system will ask you whether to replace the existing file. Enter Y to replace it, or N to abort.

l When you back up a file to the server and if a file with the same name already exists on the server, the existing file will be overwritten without a prompt.

l The above-mentioned operations are performed in user view.

l The backup configuration file can be modified by using a text editor. To update the system configuration of the access controller, you can modify the backup configuration file on the file server, and then download the modified configuration file to the access controller. Your update takes effect on the access controller after it is restarted. Likewise, you can download a new application file to the access controller to overwrite the existing main application file to update the application.

Maintaining the Access Controller Through FTP

The access controller as the FTP server

The File Transfer Protocol (FTP) is an application layer protocol in the TCP/IP suite. It is mainly used for file transfer between remote hosts. FTP provides a reliable, connection-oriented data transfer service over TCP.

The access controller can serve as the FTP server. In this case, you can use your PC as an FTP client to log in to the access controller for file operations.

Before using FTP, you need to install the FTP client application on your PC. The FTP client software is not provided with the access controller. You must prepare it yourself. In the following example, the FTP client program is the one that comes with Microsoft Windows XP.

Follow these steps to maintain the software of your access controller through FTP with the access controller as the FTP server:

1) Set up a network environment as follows:

Figure 5-9 Set up a software maintenance environment (the access controller as the FTP server)

Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the FTP client (PC) to 192.168.0.1, while that of the access controller’s Ethernet interface to 192.168.0.2. Then use the ping command to verify the network connectivity.

2) Enable the FTP service.

Configure FTP server authentication and authorization and enable FTP. The FTP server supports multi-client access. When a remote FTP client sends a request to the FTP server, the FTP server executes an action accordingly and returns the execution result to the client. Use the following command to enable the FTP service.

[H3C]ftp server enable

% Start FTP server

Add an authorized FTP username and password:

[H3C]local-user guest //Create user account guest.

[H3C-luser-guest]service-type ftp //Set user type to FTP.

[H3C-luser-guest]password simple 123456 //Set password to 123456 for the user.

[H3C-luser-guest]authorization-attribute level 3 //Set the user level to 3.

3) Maintain the access controller.

After enabling the FTP service and configuring the username and password, start the FTP client program on the PC.

Open a DOS window, and enter ftp at the DOS prompt:

C:\Documents and Settings\Administrator>ftp

ftp> //The system prompt changed to ftp>.

ftp> open 192.168.0.2 //Connect to the access controller.

Connected to 192.168.0.2.

220 FTP service ready.

User (192.168.0.2:(none)): guest //Enter the user name guest.

331 Password required for guest

Password: //Enter the password 123456.

230 User logged in. //Successfully connected to the server.

Now, use the following commands to maintain the access controller: To back up main.bin on the access controller to the PC, do the following:

ftp> binary //Specify the transfer mode as binary.

200 Type set to I.

ftp> lcd c:\temp //Change the local path.

Local directory now C:\temp.

ftp> get main.bin main.bin //Back up the file to the PC.

200 Port command okay.

150 Opening BINARY mode data connection for /main.bin.

226 Transfer complete.

ftp: 14323376 bytes received in 16.81Seconds 851.87Kbytes/sec.

To restore the backup file to the access controller, do the following:

ftp> put main.bin main.bin //Download the backup file to the access controller.

200 Port command okay.

150 Opening BINARY mode data connection for /main.bin.

226 Transfer complete.

ftp: 14323376 bytes sent in 8.29Seconds 1727.37Kbytes/sec.

ftp> quit //Quit FTP.

221 Server closing.

The access controller as an FTP client

You can also maintain the file system of your access controller through FTP with the access controller as an FTP client.

1) Set up a maintenance environment.

Figure 5-10 Set up a software maintenance environment (access controller as an FTP client)

Run the FTP server program on the PC, set the file path, and set the username and password for the access controller.

Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP address of the FTP server (PC) to 192.168.0.1, while that of the access controller’s Ethernet interface to 192.168.0.2. Then use ping to verify the network connectivity.

2) Maintain the access controller using the terminal connected to the console port of the access controller.

<H3C>ftp 192.168.0.1

Trying 192.168.0.1 ...

Press CTRL+K to abort

Connected to 192.168.0.1.

220 3Com 3CDaemon FTP Server Version 2.0

User(192.168.0.1:(none)):guest //Enter the username set on the server.

331 User name ok, need password

Password: //Enter the password.

230 User logged in //Connection succeeded.

[ftp]

Use the following commands to maintain the access controller.

Download and back up files using the get and put commands.

[ftp]get main.bin main.bin //Download the file from the server to the access controller.

cfa0:/main.bin has been existing. Overwrite it?[Y/N]:y //Overwrite the existing file or not?

227 Entering passive mode (192,168,0,1,5,60)

125 Using existing data connection

226 Closing data connection; File transfer successful.

FTP: 10323352 byte(s) received in 13.234 second(s), 780.00K byte(s)/sec.

[ftp]put main.bin main.bin //Back up the file on the access controller to the server.

227 Entering passive mode (192,168,0,1,5,90)

125 Using existing data connection

226 Closing data connection; File transfer successful.

FTP: 10323352 byte(s) sent in 7.342 second(s), 1406.00Kbyte(s)/sec.

[ftp]quit //Quit FTP.

221 Service closing control connection

Maintaining Application and Configuration Files

You can modify and display file types by using the file control submenu or the CLI.

Enter 4 on the BootWare main menu to enter the file control submenu. The system displays the following:

=================================<File CONTROL>=================================

|Note:the operating device is cfa0 |

|<1> Display All File(s) |

|<2> Set Application File type |

|<3> Delete File |

|<0> Exit To Main Menu |

================================================================================

Enter your choice(0-3):

Displaying All Files

Displaying all files on BootWare menu

Enter 1 on the file control submenu, and the system displays the following information:

Display all file(s) in cfa0:

'M' = MAIN 'B' = BACKUP 'S' = SECURE 'N/A' = NOT ASSIGNED

==========================================================================

|NO. Size(B) Time Type Name |

|1 10323352 Aug/20/2008 10:42:42 M cfa0:/main.bin |

|2 33 Aug/20/2008 10:06:24 N/A cfa0:/system.xml |

|3 842 Aug/20/2008 10:23:56 N/A cfa0:/startup.cfg |

|4 76960 Aug/15/2008 15:58:02 N/A cfa0:/vmetest.vme |

==========================================================================

Displaying all files on the CLI

<H3C>dir

Directory of cfa0:/

0 -rw- 10323352 Sep 11 2053 02:17:14 main.bin

1 -rw- 33 Aug 28 2008 10:22:50 system.xml

2 -rw- 802 Aug 28 2008 10:22:50 startup.cfg

3 -rw- 76960 Aug 15 2008 15:58:02 vmetest.vme

253950 KB total (242996 KB free)

File system type of cfa0: FAT32

Setting an Application File Type

Using the BootWare menu

Enter 2 on the file control submenu, and the system displays the following information:

'M' = MAIN 'B' = BACKUP 'S' = SECURE 'N/A' = NOT ASSIGNED

==========================================================================

|NO. Size(B) Time Type Name |

|1 10323352 Aug/20/2008 10:42:42 M cfa0:/main.bin |

|0 Exit |

==========================================================================

Enter file No:

Enter the file sequence number at the prompt above. In this example, type 1 for file main.bin and press Enter. The system prompts you to modify the file type:

Modify the file attribute:

================================================================================

|<1> +Main |

|<2> -Main |

|<3> +Backup |

|<4> -Backup |

|<0> Exit |

================================================================================

Enter your choice(0-4)

Enter 1 for +Main (set to type M), 2 for –Main (remove the M type), 3 for +Backup (set to type B), or 4 for –Backup (remove the B type). For details about the file types, refer to section “Application Files” on page xx.

Using the CLI

# Change the type of file main.bin from type B to type M+B.

<H3C> boot-loader file main.bin main

This command will set the boot file. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on slot 1!

Now, the type of file main.bin is modified as M+B, and the file is specified as the main boot file to be used at the next startup of the access controller. If a file of type M already exists on the access controller, the type of the file will automatically change to N/A.

Specifying a Startup Configuration File

Using the CLI

You can use the startup saved-configuration cfgfile command to specify the configure file to be used for the next startup of the access controller. cfgfile represents the name of the configuration file to be specified.

# Specify the configuration file to be used for the next startup of the access controller.

<H3C> startup saved-configuration startup.cfg

Please wait ...

... Done!

# Display the configuration file used for the current startup and that to be used for the next startup of the access controller.

<H3C>display startup

Current startup saved-configuration file: cfa0:/startup.cfg

Next startup saved-configuration file: cfa0:/startup.cfg

# Cancel the configuration file specified for the next startup of the access controller.

<H3C>undo startup saved-configuration

Please wait ...... Done!

<H3C>display startup

Current startup saved-configuration file: cfa0:/startup.cfg

Next startup saved-configuration file: NULL

Delete a File

Using the BootWare menu

Enter 3 on the file control submenu, and the system displays the following information:

Deleting the file in cfa0:

'M' = MAIN 'B' = BACKUP 'S' = SECURE 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 10323352 Aug/20/2008 10:42:42 M cfa0:/main.bin |

|2 33 Aug/20/2008 10:06:24 N/A cfa0:/system.xml |

|3 842 Aug/20/2008 10:23:56 N/A cfa0:/startup.cfg |

|4 76960 Aug/15/2008 15:58:02 N/A cfa0:/vmetest.vme |

|0 Exit |

============================================================================

Enter file No:

Type a file sequence number and press Enter. The system asks you to confirm your operation:

The file you selected is cfa0:/startup.cfg,Delete it? [Y/N]

Enter Y for confirmation. The following message appears, indicating the file was successfully deleted.

Deleting..........Done!

Using the CLI

Execute the delete [ /unreserved ] file-url command in user view to delete a file, where:

l /unreserved: Permanently deletes the specified file, and the deleted file can never be restored.

l file-url: Name of the file to be deleted.

# Delete file test.txt in the root directory.

<H3C> delete test.txt

Delete cfa0:/test.txt?[Y/N]:y

%Delete file cfa0:/test.txt...Done.

At this time, file test.txt is removed to the recycle bin. If you want restore the file, you can use the undelete command.

# Restore file test.txt from the recycle bin.

<H3C> undelete test.txt

Undelete cfa0:/test.txt? [Y/N]:y

% Undeleted file cfa0:/test.txt.

Dealing With Password Loss

This section describes how to deal with password loss.

User Password Loss

Your login will be refused if you have forgotten the user password. In this case, set a new user password by following the steps below:

1) Enter the BootWare main menu, and enter 6 to bypass the current configuration in system startup.

The system prompts the following information, which indicates that your setting succeeds.

Flag Set Success.

2) When the BootWare main menu appears again, enter 0 to reboot the system.

System starts booting ...

3) Set a new password in system view.

[H3C]user-interface console 0

[H3C-ui-console0]authentication-mode password

[H3C-ui-console0]set authentication password simple 123456

The above output information indicates that password authentication is used for console port login, the password is set to 123456 in plain text.

l After reboot, the system runs with the default configuration, while the original configuration file is still kept on the CF card. To restore the original configuration, use the display saved-configuration command to locate the configuration file, and then copy and run it.

l If the password is stored in plain text, you can use the display current-configuration command to view the password in the current configuration. If you use the set authentication password cipher 123456 command to set your password, the password will be stored in cipher text.

4) Save the new password.

[H3C] save

After modifying the user password, use the save command to save it.

BootWare Password Loss

Contact your local dealer if you forget the BootWare password. The technical support staff will help you log in to the access controller and set a new password.

To change the BootWare password, enter the BootWare main menu.

Enter 5 on the BootWare main menu, and follow the prompts:

please input old password:

Please input new password:

Please input new password again:

Password Set Successfully.

l Once you enter a wrong old password or different new passwords, the password modification operation will fail and the system will exit this operation.

l The BootWare password can consist of a maximum of 32 printable characters, such as letters, numerals, and punctuations.

Super Password Loss

The super password enables you to switch between four super levels. Without a super password, you cannot perform higher privilege operations.

Enter 8 from the BootWare main menu to clear the super password. Then, reboot the access controller. You will directly enter system view after the access controller restarts.

This setting works only once. When the access controller is restarted for a second time, the super password is restored.

Backing Up and Restoring the BootWare

Using the BootWare Menu

You can back up and restore the BootWare on the BootWare operation submenu. After the BootWare is backed up on a storage device, if the normal BootWare is lost, you can restore it using the backup BootWare to boot the device. Enter 7 on the BootWare main menu to enter the BootWare operation submenu. For details of this submenu, refer to section “BootWare operation submenu” on page 5-7.

To back up the basic and extended BootWare to the CF card, enter 1 on the BootWare operation submenu and follow the prompts:

Will you backup the Basic BootWare? [Y/N]Y

Begin to backup the Basic BootWare...................Done!

Will you backup the Extend BootWare? [Y/N]Y

Begin to backup the Extend BootWare...................Done!

To restore the backup BootWare from the CF card, enter 2 on the BootWare operation submenu and follow the prompts:

Will you restore the Basic BootWare? [Y/N]Y

Begin to restore Normal Basic BootWare...Done!

Will you restore the Extend BootWare? [Y/N]Y

Begin to restore Normal Extend BootWare....Done!

Using the CLI

You can also use bootrom commands to back up and restore the BootWare.

Backing up the BootWare

l Back up the complete BootWare to the Flash:

<H3C>bootrom backup all

Now backuping bootrom, please wait...

Backup bootrom completed!

l Back up the extended BootWare to the Flash:

<H3C>bootrom backup part

Now backuping bootrom, please wait...

Backup bootrom completed!

Restoring the BootWare

l Restore the complete BootWare backed up on the Flash to the system:

<H3C>bootrom restore all

This command will restore bootrom file, Continue? [Y/N]:y

Now restoring bootrom, please wait...

Restore bootrom completed!

l Restore the extended BootWare backed up on the Flash card to the system:

<H3C>bootrom restore part

This command will restore bootrom file, Continue? [Y/N]:y

Now restoring bootrom, please wait...

Restore bootrom completed!

6 Troubleshooting

Software Loading Failure

If software loading fails, the system runs the old version of the software. The following information appears:

=========================<Enter Ethernet SubMenu>===========================

|Note:the operating device is cfa0 |

|<1> Download Application Program To SDRAM And Run |

|<2> Update Main Application File |

|<3> Update Backup Application File |

|<4> Update Secure Application File |

|<5> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

|<Ensure The Parameter Be Modified Before Downloading!> |

============================================================================

Enter your choice(0-5): 2

Loading...Failed!

In this case, check whether the physical interfaces are properly connected.

l If the interfaces are not properly connected, reconnect them correctly and restart the loading process.

l If the interfaces are properly connected, check the loading process information displayed on the configuration terminal for input errors. In case of any input error, restart the loading process with correct inputs.

Input errors include:

l A baud rate other than 9600 bps selected for BootWare loading using XMODEM

l An improper baud rate setting in HyperTerminal

l A wrong IP address, file name, or TFTP Server work path specified for software loading using TFTP

l A wrong IP address, file name, username, or password specified for software loading using FTP

If the cause cannot be located, contact your local agent for help.

Power Supply Failure

You can check whether the power system of the access controller works normally by observing the PWR LED on the front panel. The PWR LED is solid green when the power system works normally. When the PWR LED is off, check whether:

l The power cord of the access controller is properly connected.

l The voltage of the power input is correct.

Configuration System Failure

If the access controller is operational upon power-on, the configuration terminal displays the boot information; otherwise, you may see nothing or illegible characters on the configuration terminal.

No Display on the Terminal

If there is no information display on the configuration terminal after the access controller is powered on, please check:

l Whether the power LED is solid green.

l Whether all LEDs are off or blinking. If so, the main control board is abnormal.

l Whether the console cable is connected to the console port of the main control board.

If the cause cannot be located in the steps above, the possible reasons are as follows:

l The serial interface to which the console cable is connected is not the one specified in the terminal emulation program.

l Terminal settings are incorrect. The required settings are as follows: 9600 bits per second, 8 data bits, no parity check, 1 stop bit, no flow control, and VT100 for terminal emulation type.

l The console cable is not in good condition.

Illegible Characters on the Terminal

l If illegible characters are displayed, check whether the connection of the console cable is loose.

H3C WX5004 Access Controller Installation Manual-6PW101

Console port

Ethernet interfaces

Fans

Generation and damage of static electricity

Protection measures

Wearing ESD-Preventive Wrist Strap

3 Installation

Mounting bracket structure

Installation procedure

Installation procedure

When a grounding strip is available

When a grounding strip is unavailable

To an the Ethernet electrical interface

To an the Ethernet optical interface

Checking the Installation

5 Software Maintenance

Setting up a configuration environment

Backing up and restoring application and configuration files

The access controller as the FTP server

The access controller as an FTP client

Displaying all files on BootWare menu

Displaying all files on the CLI

Using the BootWare menu

Using the CLI

Using the CLI

Using the BootWare menu

Using the CLI

Backing up the BootWare

Restoring the BootWare

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us