Cisco 3350 Mobility Services Engine Getting Started Guide

Required Hardware

You need this equipment to install a mobility services engine in an EIA rack:

• A mobility services engine
• Network cables
• One rack unit (RU) in an EIA-standard rack
• Rack mounting kit (included in shipment)

Note If you are installing this unit in a threaded-hole rack, you must supply screws that fit the threaded-hole rack and the appropriate screwdriver or Torx driver for those screws.

CLI Console Requirements

You need this equipment to connect to the mobility services engine console:

• VT-100 terminal emulator on CLI console laptop, desktop, or palmtop

Note A null modem serial cable that provides a connection to the laptop, desktop, or palmtop is shipped with the mobility services engine.

Note Please refer to the latest Release Notes for Cisco 3300 Series Mobility Services Engine for compatibility by release between the mobility services engine and Cisco WCS and controller releases at: http://www.cisco.com/en/US/products/ps9742/prod_release_notes_list.html

System Configuration Parameters

Obtain these parameters from your network administrator:

• A host name for the mobility services engine
• An IP address for the Ethernet-0 (eth0) port (mobility services engine back panel)
• A net mask for the eth0 IP address
• An IP address for the eth0 default gateway
• An IP address for the Ethernet-1 (eth1) port (mobility services engine back panel) (installation optional)
• A net mask for the eth1 IP address (only required if eth1 is installed)
• An IP address for the eth1 default gateway (only required if eth1 is installed)

Note Either the Ethernet-0 or Ethernet-1 port can be used to transmit location updates to Cisco WCS. However, the Ethernet-0 port is generally configured to communicate with Cisco WCS and the Ethernet-1 port is generally used for out-of-band management. Both ports are configured as part of the installation script described in the “Configuring the Mobility Services Engine” section.

General Precautions

To reduce the risk of personal injury or damage to the mobility services engine:

• Place the product away from radiators, heat registers, stoves, amplifiers, or other products that produce heat.
• Never use the product in a wet location.
• Avoid inserting foreign objects through openings in the product.
• To reduce risk of injury from electric shock hazards, do not open the product enclosure.

Laser Devices

Laser devices are used within the DVD of the mobility services engine. The DVD has no defined use on the customer site.

To reduce the risk of exposure to hazardous radiation:

• Do not try to open the laser device enclosure. There are no user-serviceable components inside.
• Do not operate controls, make adjustments, or perform procedures to the laser device other than those specified herein.
• Allow only Cisco authorized service technicians to repair the laser device.

Space and Airflow Requirements

Install the mobility services engine in a EIA-standard rack. One rack unit is required for each mobility services engine.

Ensure that you can reach the mobility services engine and all cables.

• Ensure that the mobility services engine is within 328 ft (100 m) equivalent distance to any equipment connected to the 10/100/1000BASE-T ports.
• Ensure that the power cord can reach a 110 or 220 VAC grounded electrical outlet.

Ensure that there is sufficient room at the back of the mobility services engine for all cables and connectors.

• Leave a minimum clearance of 63.5 cm (25 in.) in front of the rack.
• Leave a minimum clearance of 76.2 cm (30 in.) behind the rack.
• Leave a minimum clearance of 121.9 cm (48 in.) from the back of the rack to the back of another rack or row of racks

Caution To prevent improper cooling and damage to the equipment, do not block the ventilation openings.

---

Caution Always use blanking panels to fill empty vertical spaces in the rack. This arrangement ensures proper airflow. Using a rack without blanking panels results in improper cooling that can lead to thermal damage.

---

Caution When selecting a rack to use, observe the following additional requirements to ensure adequate airflow and to prevent damage to the equipment: (1) Front and rear doors—If the 42U rack includes closing front and rear doors, you must allow 5,350 sq. cm (830 sq. in.) of holes evenly distributed from top to bottom to permit adequate airflow (equivalent to the required 64 percent open area for ventilation). (2) Side—The clearance between the installed rack component and the side panels of the rack must be a minimum of 7 cm (2.75 in.in.).

---

Temperature Requirements

To ensure continued safe and reliable equipment operation, install or position the system in a well ventilated, climate-controlled environment.

Ensure that the ambient operating temperature remains between 0 and 40° C (32 and 104° F), taking into account the elevated temperatures that occur when equipment is installed in a rack.

Caution To reduce the risk of damage to the equipment when installing third-party options: (1) Do not permit optional equipment to impede airflow around the mobility services engine or to increase the internal rack temperature beyond the maximum allowable limits. (2) Do not exceed the manufacturer’s TMRA.

---

Power Requirements

Installation of this equipment must comply with local and regional electrical regulations governing the installation of information technology equipment by licensed electricians. This equipment is designed to operate in installations covered by NFPA 70, 1999 Edition (National Electric Code) and NFPA-75, 1992 (code for Protection of Electronic Computer/Data Processing Equipment). For electrical power ratings on options, refer to the product rating label or the user documentation supplied with that option.

Caution Protect the mobility services engine from power fluctuations and temporary interruptions with a regulating uninterruptible power supply (UPS). This device protects the hardware from damage caused by power surges and voltage spikes and keeps the system in operation during a power failure.

---

When installing more than one mobility services engine, you may need to use additional power distribution devices (PDUs) to safely provide power to all devices. Observe the following guidelines:

• Balance the mobility services engine power load between available AC supply branch circuits.
• Do not allow the overall system AC current load to exceed 80 percent of the branch circuit AC current rating.
• Do not use common power outlet strips for this equipment.
• Provide a separate electrical circuit for the mobility services engine.

Power Supplies on the Mobility Services Engine

The mobility services engine has two power supplies.

Warning This unit might have more than one power supply connection. All connections must be removed to de-energize the unit. Statement 1028

Caution Verify that the external power source connected to the mobility services engine matches the type of power source indicated on the electrical ratings label. If you are not sure of the type of power source required, consult your Cisco authorized reseller or local power company.

---

Batteries

The mobility services engine might include a real-time clock battery or coin cell battery that might contain perchlorate and might require special handling when recycled or disposed of in California.

Refer to the following link for disposal information.

http://www.dtsc.ca.gov/hazardouswaste/perchlorate

Caution Do not dispose of batteries with the general household waste. Recycle them using the public collection system.

---

Electrical Grounding Requirements

The mobility services engine must be grounded properly for proper operation and safety. In the United States, you must install the equipment in accordance with NFPA 70, 1999 Edition (National Electric Code), Article 250, as well as any local and regional building codes. In Canada, you must install the equipment in accordance with Canadian Standards Association, CSA C22.1, Canadian Electrical Code. In all other countries, you must install the equipment in accordance with any regional or national electrical wiring codes, such as the International Electrotechnical Commission (IEC) Code 364, parts 1 through 7.

Furthermore, you must verify that all power distribution devices used in the installation, such as branch wiring and receptacles, are listed or certified grounding-type devices. Because of the high ground-leakage currents associated with multiple systems connected to the same power source, Cisco recommends the use of a PDU that is either permanently wired to the building’s branch circuit or includes a nondetachable cord that is wired to an industrial-style plug. NEMA locking-style plugs or those complying with IEC 60309 are considered suitable for this purpose. Using common power outlet strips for the mobility services engine is not recommended.

Rack Warnings

Warning To prevent bodily injury when mounting or servicing this unit in a rack, you must take special precautions to ensure that the system remains stable. The following guidelines are provided to ensure your safety: (1) This unit should be mounted at the bottom of the rack if it is the only unit in the rack. (2) When mounting this unit in a partially filled rack, load the rack from the bottom to the top with the heaviest component at the bottom of the rack. (3) If the rack is provided with stabilizing devices, install the stabilizers before mounting or servicing the unit in the rack. Statement 1006.

Caution To reduce the risk of personal injury or equipment damage when unloading a rack, at least two people are needed to safely unload the rack from the pallet.

---

Caution To prevent damage, ensure that water or excessive moisture cannot get into the mobility services engine.

---

Package Contents

Each mobility services engine package contains the following items:

• One Cisco 3350 Mobility Services Engine
• One rack mount kit
• Power cords
• DB9-RJ45 cable for console connection
• RJ45-DB9 adapter
• This guide, the Cisco 3350 Mobility Services Engine Getting Started Guide

Installing the Rail Kit Into a Threaded-Hole, Square-Hole or Round-Hole Rack

Step 1 Release the inner slide of the mounting rail and attach it to the side of the mobility services engine (Figure 2-1). The numbers within the illustrations indicate the order of the action.

Figure 2-1 Attach Inner Sliding Rail to Mobility Services Engine

Step 2 Attach the outside rail to the front of the rack structure where the mobility services engine is going to be installed (Figure 2-2). The numbers within the illustrations indicate the order of the action.

Figure 2-2 Attach Outer Rail to Front of Rack

Step 3 Attach the outside rail to the back of the rack structure where the mobility services engine is going to be installed (Figure 2-3). The numbers within the illustrations indicate the order of the action.

Figure 2-3 Attach Outer Rail to Back of Rack

Step 4 Attach inner slide rail with mobility service engine to the outside rail that is mounted on the rack (Figure 2-4).

Figure 2-4 Attach Inner Rail to Outer Rail

Step 5 Slide the attached inner rail and the mobility services engine to the rear of the rack (Figure 2-5). The numbers within the illustrations indicate the order of the action.

Figure 2-5 Slide System and Inner Rail to Rear of Rack

Front Panel

Figure 2-6 shows a full view of the front panel of the Cisco 3350 Mobility Services Engine.

Figure 2-7 shows a detailed section of the Cisco 3350 front panel.

Table 2-1 identifies Cisco 3350 front panel components and their function.

Figure 2-6 Cisco 3350 Front Panel

Figure 2-7 Close Up of Cisco 3350 Front Panel

Diagnostic Card

Figure 2-8 shows details of the diagnostic card found on the front panel.

Table 2-2 summarizes the internal components of the mobility services engine that are tracked by the diagnostic card. Definitions of each of the LED states for those components are also summarized.

Note This information is not currently summarized within Cisco WCS.

Figure 2-8 Diagnostic Card

Rear Panel

Figure 2-9 shows details of the rear panel for the Cisco 3350 Mobility Services Engine.

Table 2-3 identifies Cisco 3350 back panel components and their function.

Table 2-4 summarizes pin assignment for the DB9 cable.

Note Items not labeled in Figure 2-9 are not currently assigned an active role on the system.

Figure 2-9 Cisco 3350 Mobility Services Engine Rear Panel

Table 2-3 Back Panel Components

Number	Description
1	DB9 serial connector for console. See pinouts in Table 2-4 .
2	DB15 connector.
3	Mouse connector.
4	Keyboard connector.
5	NIC 1 (Ethernet-0) connector and LED. Green LED indicates link exists. Off (unlit) LED indicates no link.
6	NIC 2 (Ethernet-1) connector and LED. Green LED indicates link exists. Off (unlit) LED indicates no link.
7	NIC 2 link status LED (same function as LED for NIC 1)
8	UID button and LED. Blue means that identification is activated. Blinking blue means that the system is being managed remotely. Off (unlit) means that identification is deactivated.
9	Power Supply 2. Green means normal operation. Off means that the system is off or the power supply has failed. Warning This unit might have more than one power supply connection. All connections must be removed to de-energize the unit. Statement 1028
10	Power Supply 1. Green means normal operation. Off means that the system is off or the power supply has failed. Warning This unit might have more than one power supply connection. All connections must be removed to de-energize the unit. Statement 1028

Automatic Installation Script

Note It is highly recommended that all relevant items be configured during initial setup to ensure optimum operation of the mobility services engine in your network. The hostname and either the Ethernet-0 (eth0) or the Ethernet-1 (eth1) port MUST always be configured during the automatic installation.

Note You can rerun the automatic installation script at any time to add or change parameters. There is no need to reenter values that you do not want changed during one of these updates.

Note If you do not want to configure an item, enter skip and you are prompted for the next configuration step. Any setting skipped is retained and not modified.

The automatic installation script that displays to the screen is shown below along with descriptive text.

Example text: Indicates the installation script that displays to the console.

Body text: Provides additional information to the user about steps within the script.

Enter the login root.

Enter the password password.

Enter yes if you want to use the setup wizard or No if you want to manually set the parameters. Only experienced Linux system administrators should opt to configure the system using the setup script. The option in square brackets is the default. You can press Enter to choose that default.

When you enter Yes the following displays on the console.

The host name should be a unique name that can identify the device on the network. The hostname should start with a letter, end with a letter or number, and contain only letters, numbers, and dashes.

Enter a domain name for the network domain to which this device belongs. The domain name should start with a letter, and it should end with a valid domain name suffix such as .com. It must contain only letters, numbers, dashes, and dots.

Note A network administrator can provide you with the IP address, network mask, and default gateway address for the prompts that follow.

Enter Yes if you want to provide information for a second ethernet (eth1) interface.

Note Entry of a second ethernet interface (eth1) can be skipped by entering skip.

Enter the network mask for the IP address you specified.

Note If you entered an IP address and mask for the second interface (eth1) of this machine, you are given the opportunity to define up to two static routing entries for that interface. Static routes are typically used in lab environments to mimic out-of-band networks and are not recommended for implementation within your network unless you have extensive experience in their use.

Note If you do not want to configure any static routes, enter none at the network address prompt seen below. You will not be prompted for the network mask and gateway address.

Note If you want to configure only one route, you can enter none when you are prompted for the second network address.You will not be prompted for the network mask and gateway address for the second route.

Enter the network mask for the network address you entered above.

Enter a gateway address for the network address and network mask you provided.

Enter DNS information.

Note Communications between the mobility services engine, Cisco WCS and the controller are in universal time code (UTC). Local time zones are configured on the mobility services engine to assist network operations center personnel in locating events within logs. Configuring NTP on each system provides devices with the UTC time.

Note The mobility services engine and its associated controllers must be mapped to the same NTP server and the same Cisco WCS server. An NTP server is required to automatically synchronize time between the controller, Cisco WCS and the mobility services engine.

A login banner appears when a user logs in through the console or SSH. This example shows the default banner. You can change the text that appears in this banner in the steps below. The banner is usually used to warn users that they are entering a private system.

Enter Y in the step below to configure and enable remote root login (access) from the console.

Note If you enable remote root access, serial and SSH connections are supported. Local monitor and keyboard access is denied.

Note If you disable remote root access, then both the local monitor and keyboard work along with the serial connection. SSH access is disabled.

Enter yes (below) to allow remote login through SSH v2 (ssh root login) in addition to console login. Choose no to allow root login only from the console.

Note If you forget the ssh root login password, you can enter into single user mode and change the password. To prevent unauthorized access, a password for the single user mode can be defined.

Caution If you forget the single user mode password, you cannot login and you will need to contact TAC to arrange for an RMA.

---

Enter the desired value for each of the password parameters or hit Enter to accept the default parameter value.

Note These parameter settings apply to ALL passwords that you enable and set during the installation script.

Enter Y to enable and define a root (superuser) password. Press Enter to skip this step.

Enter a password for the superuser and confirm it by typing it again. Your typing is not visible.

You can also configure a strong (GRand Unified Bootloader (GRUB)) password. A strong password must have a minimum of 9 characters and must include: two lowercase letters, two digits and two special characters (such as $ and #). An error message displays if you enter an inadequate password.

Caution If you forget the GRUB password, you cannot login and you will need to contact TAC to arrange for an RMA.

---

Note If a strong password is not enabled, a password can be of any length.

Note Passwords defined before a strong password is set are not affected by the strong password setting. Only those passwords that are set after the strong password is set are affected. For example, strong passwords will be required for passwords set later in this script such as the Cisco WCS communication password (as noted in example below) and as passwords expire.

Enter Y to enable and define a Cisco WCS communication password.

Note This password does not define an individual user password for access to the Cisco WCS GUI. This password is used for SOAP/XML authentication between systems (such as mobility services engines) and Cisco WCS.

Enter a password for Cisco WCS communication and confirm it by typing it again. Your typing is not visible.

Note It is recommended that you set a BIOS password to prevent unauthorized BIOS access.

All of the information that was entered into the install script appears on the screen.

After the script configuration appears on the screen, you are asked to verify all the setup information you provided. You can enter Yes to proceed with the configuration, No to make more changes, or ^ to go back to the previous step.

If you enter yes, the configuration information is applied. Cisco recommends that you reboot the system when prompted to ensure that the changes are applied.

Note The message “***Configuration successful*** appears on the screen when the configuration is complete.

The next time you log in using root, only the Linux shell prompt appears and not the setup script. You can rerun the setup script at any time to change settings by logging in as root and running /opt/mse/setup/setup.sh.

The setup script generates a log file that can be found at /opt/mse/setup/setup.log .

Downloading Software Using Cisco WCS

To download software to a mobility services engine using Cisco WCS, follow these steps:

Step 1 Verify that you can ping the mobility services engine from Cisco WCS or an external FTP server, whichever you are going to use for the image download.

Step 2 In Cisco WCS, choose Mobility > Mobility Service Engines.

Note In release 6.0, the path is Services > Mobility Services.

Step 3 Click the name of the mobility services engine to which you want to download software.

Step 4 Choose Maintenance (left panel).

Step 5 Choose Download Software.

Step 6 To download software, do one of the following:

• To download software listed in the Cisco WCS directory, select Select from uploaded images to transfer into the Server. Then, choose a binary image from the drop-down menu.

Cisco WCS downloads the binary images listed in the drop-down menu into the FTP server directory you have specified during the Cisco WCS installation.

• To use downloaded software available locally or over the network, select the Browse a new software image to transfer into the Server and click Browse. Locate the file and click Open.

Step 7 Enter the time in seconds (between 1 and1800) after which software download times out.

Note This time out setting represents the total time allowed before a software download to a mobility services engine expires. It is not a FTP packet timeout setting.

Step 8 Click Download to send the software to the /opt/installers directory on the mobility services engine.

Step 9 After the image has been transferred to the mobility service engine, log in to the mobility services engine CLI and run the installer image from the /opt/installers directory by entering the ./image-name command.

Step 10 To run the software, enter /etc/init.d/msed start.

Step 11 To stop the software, enter /etc/init.d/msed stop and to check status enter /etc/init.d/msed status.

Manually Downloading Software

If you do not want to automatically update the mobility services engine software using Cisco WCS, follow these steps to upgrade the software manually using a local (console) or remote (SSH) connection.

Step 1 Transfer the new mobility services engine image onto the hard drive.

a. Log in as root, and use the binary setting to send the software image from an external FTP server root directory.

An example software image file name is CISCO-MSE-L-K9-x-x-x-x-64bit.bin.gz and it changes with each release.

Note The mobility services engine image is compressed at this point.

Note The default login name for the FTP server is ftp-user.

b. Verify that the image ( CISCO-MSE-L-K9-x-x-x-x-64bit.bin.gz) is in the mobility services engine /opt/installers directory.

c. To decompress (unzip) the image file enter:

The decompression yields a bin file.

d. Make sure that the CISCO-MSE-L-K9-x-x-x-x.bin file has execute permissions for the root user. If not, enter:

chmod 755 CISCO-MSE-L-K9-x-x-x-x.bin

Step 2 To manually stop the mobility services engine, login as root and enter:

Step 3 To install the new mobility services engine image, enter:

Step 4 To start the new mobility services software, by enter:

Caution Do not complete the next step, which uninstalls the script files, unless the system instructs you to do so. Removing the files unnecessarily erases your historical data.

---

Step 5 To uninstall the mobility services engine’s script files, enter: