The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to initially install and configure your Cisco 3355 Mobility Services Engine.
This chapter contains these sections:
Note For configuration details beyond initial installation, refer to the appropriate mobility services configuration guide at:
http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html
This section lists the required hardware and other information that you need to install and setup the mobility services engine.
You need this equipment to install a mobility services engine in an Electronics Industries Alliance (EIA) rack:
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.
You need this equipment to connect to the mobility services engine console:
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
Obtain these parameters from your network administrator:
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. Another approach, especially for high traffic networks, is to dedicate Ethernet-0 for communication with the Wireless LAN Controllers and use Ethernet-1 for communication with WCS and other applications.
For maximum safety and reliability, mount the mobility services engine using the following guidelines.
To reduce the risk of personal injury or damage to the mobility services engine:
Laser devices are used within the DVD of the mobility services engine. The DVD has no defined use at the customer site.
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 there is sufficient room at the back of the mobility services engine for all cables and connectors.
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 10 and 35° C (50 and 95° F), taking into account the elevated temperatures that occur when equipment is installed in a rack.
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.
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:
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
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
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.
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.
Follow these steps to unpack the mobility services engine.
Step 1 Open the shipping container and carefully remove the contents.
Step 2 Return all packing materials to the shipping container and save it.
Step 3 Ensure that all items listed in the “Package Contents” section are included in the shipment.
Step 4 Check each item for damage. If any item is damaged or missing, notify your authorized Cisco sales representative.
Each mobility services engine package contains the following items:
Warning Only trained and qualified personnel should be allowed to install, replace, or service this equipment. Statement 1030
To reduce the risk of personal injury or damage to the equipment:
The mobility services engine comes with a universal rack mount kit that can be installed in a square-hole rack, round-hole rack, or a threaded-hole rack. You can order replacement universal rack mount kits from Cisco. The replacement part PID is AIR-SRVR-URMK=.
Note You must provide the threaded-hole screws to secure the mounting rails to the rack. Threaded-hole screws are not shipped with the system.
Review the documentation that comes with the rack cabinet for safety and cabling information. Before you install the mobility services engine in a rack cabinet, review the following guidelines:
– Minimum depth of 70 mm (2.76 in.) between the front mounting flange and inside of the front door.
The following illustration shows the items that you need to install the mobility services engine in the rack cabinet. If any items are missing or damaged, contact your place of purchase.
Note Some items come with the mobility services engine, not in the rack installation kit.
Note Use cage bars with square-holed racks, clip nuts with round-holed racks, and your own screws or the screws provided in this kit with threaded-hole racks.
Note If the slide rails in your rack installation kit came with shipping thumbscrews, remove them before you begin the following installation procedure.
Step 1 Select an available 1 U or 2 U space (depending on the mobility services engine you are installing) in your rack to install your mobility services engine. If you have either a round-holed or square-holed rack, install cage bars or clip nuts in the middle and the bottom (optional for the upper) holes of the lower U on each side of the front of the rack. Then, install cage bars or clip nuts in the upper and the bottom holes of the lower U on each side of the rear of the rack.
Step 2 Use a screwdriver to install the cage bars or the clip nuts on the inside of the mounting rail, as required for your rack, into the selected holes.
Step 3 The rail depth can be adjusted from 17 in (432 mm) to 31.25 in (794 mm). To adjust the depth, you can loosen the nuts on the posts and slide the bracket until the distance between the front and rear slide rail flanges matches the distance between the front and rear EIA rails of the rack cabinet. If you need further adjustment, remove the nuts, move the bracket to the appropriate set of posts (A, B, C, and D) to obtain the appropriate slide rail depth, then reinstall and tighten the nuts.
Step 4 To remove the support bracket, remove the screw (1) and remove the bracket (2) from the rear of the slide rail.
Step 5 To remove the mounting brackets, remove the screws (1) and (3). Slide out the brackets (2) and (4) from the rear of the slide rail.
Step 6 Attach the front of the slide rail and EIA latch to the front of the rack cabinet by installing a screw in the bottom hole of the lower U; then, install another screw in the middle hole of the lower U to attach the front of the slide rail to the front of the rack cabinet.
Note When you fasten the slides to the rack, ensure the screws are engaged but the flange can move slightly. You will use a screwdriver to fully tighten them in Lift the locking levers (1) on the slide rails and push the mobility services engine (2) all the way into the rack until it clicks into place..
Note Use 12-24 screws (not hex head M6 screws) on the front mounting bracket if you are installing this system into a rack with round or square holes (i.e., not threaded holes).
Step 7 Use two screws to attach the rear of the slide rail to the rear of the rack cabinet in the upper and the bottom holes of the lower U.
Repeat The rail depth can be adjusted from 17 in (432 mm) to 31.25 in (794 mm). To adjust the depth, you can loosen the nuts on the posts and slide the bracket until the distance between the front and rear slide rail flanges matches the distance between the front and rear EIA rails of the rack cabinet. If you need further adjustment, remove the nuts, move the bracket to the appropriate set of posts (A, B, C, and D) to obtain the appropriate slide rail depth, then reinstall and tighten the nuts. through Use two screws to attach the rear of the slide rail to the rear of the rack cabinet in the upper and the bottom holes of the lower U. to install the other slide rail into the rack.
Step 8 Pull the slide rails forward (1) until they click, two times, into place. Carefully lift the mobility services engine and tilt it into position over the slide rails so that the rear nail heads (2) on the mobility services engine line up with the rear slots (3) on the slide rails. Slide the mobility services engine down until the rear nail heads slip into the two rear slots, and then slowly lower the front of the mobility services engine (4) until the other nail heads slip into the other slots on the slide rails. Make sure that the front latch (5) slides over the nail heads.
Step 9 Lift the locking levers (1) on the slide rails and push the mobility services engine (2) all the way into the rack until it clicks into place.
Slide the system in and out twice to make sure the system slides correctly. Push the system inwards to the rack as close as possible but able to access the screws with a screwdriver. Then tighten the screws with a screwdriver.
Step 10 Slide the mobility services engine into the rack until it snaps into place. To slide the mobility services engine out of the rack, press on the release latches (1).
Note When you move the rack cabinet, or if you install the rack cabinet in a vibration-prone area, insert the optional M6 screws (2) in the front of the mobility services engine.
To remove the mobility services engine from the rack, reverse these instructions. Store this information with your mobility services engine documentation for future use.
This section describes the controls and light-emitting diodes (LEDs) and how to turn the Cisco 3355 Mobility Services Engine on and off.
Figure 2-1 shows the controls, LEDs, and connectors the front panel of the Cisco 3355 Mobility Services Engine.
Figure 2-2 shows a detailed view of the operator information panel.
Figure 2-1 Cisco 3355 Mobility Services Engine Front Panel
Note The maximum video resolution is 1600 x 1200 at 75 Hz.
Figure 2-2 shows a detailed view of the controls and LEDs on the operator information panel.
Figure 2-2 Close Up of Cisco 3355 Operator Information Panel
– Off: Power is not present, or the power supply or the LED itself has failed.
– Flashing rapidly (4 times per second): The mobility services engine is turned off and is not ready to be turned on. The power-control button is disabled. This will last approximately 20 to 40 seconds.
– Flashing slowly (once per second): The mobility services engine is turned off and is ready to be turned on. You can press the power-control button to turn on the mobility services engine.
– Lit: The mobility services engine is turned on.
– Fading on and off: The mobility services engine is in a reduced-power state. To wake the mobility services engine, press the power-control button or use the IMM Web interface. See the Integrated Management Module User’s Guide for information on logging on to the IMM Web interface.
The light path diagnostics panel is on the top of the operator information panel, as shown in Figure 2-3. For additional information about the LEDs on the light path diagnostics panel, see Table 2-1 .
To access the light path diagnostics panel, slide the blue release button on the operator information panel to the left. Pull forward on the unit until the hinge of the operator panel is free of the chassis. Then pull down on the unit, so that you can view the light path diagnostics panel information.
Note When you slide the light path diagnostics panel out of the mobility services engine to check the LEDs or checkpoint codes, do not run the mobility services engine continuously with the light path diagnostics panel outside of the mobility services engine. The panel should only be outside of the mobility services engine a short time. The light path diagnostics panel must remain in the mobility services engine when it is running to ensure proper cooling.
Figure 2-3 Light Path Diagnostics Panel
Figure 2-4 shows the LEDs and controls on the light path diagnostics panel.
Figure 2-4 Light Path Diagnostics Panel Components
By placing the system-error LED indicator in Remind mode, you acknowledge that you are aware of the last failure but will not take immediate action to correct the problem. The Remind function is controlled by the IMM.
|
||
---|---|---|
|
|
|
An error occurred and cannot be isolated. The error is not represented by a path. |
||
The power supplies are using more power than their maximum rating. |
||
Check the IMM system event log and the system-error log for information about the error and then determine the next steps. If needed, contact Cisco TAC. |
||
1. Check the power supply that has a lit amber LED (see Power-supply LEDs). 2. Make sure that the power supplies are seated correctly. 3. Remove one of the power supplies to isolate the failed power supply. |
||
An error has occurred on a PCI bus or on the system board. An additional LED is lit next to a failing PCI slot. |
||
1. Shut down the system and remove the power cords from the mobility services engine; then, reconnect the mobility services engine to power and restart it. 2. If the problem does not go away, contact Cisco TAC for assistance. |
||
A fan has failed, is operating too slowly, or has been removed. The TEMP LED might also be lit. |
Contact Cisco TAC to replace your Cisco 3355 Mobility Services Engine and for further assistance. |
|
The system temperature has exceeded a threshold level. A failing fan can cause the TEMP LED to be lit. |
||
When only the MEM LED is lit, a memory error has occurred. When both the MEM and CNFG LEDs are lit, the memory configuration is invalid or the PCI Option ROM is out of resource. |
||
A nonmaskable interrupt has occurred, or the NMI button was pressed. |
||
An invalid microprocessor configuration or a microprocessor has failed (both the CPU LED and the CNFG LED might be lit). |
||
1. Check the LEDs on the hard disk drives for the drive with a lit status LED and reseat the hard disk drive. 2. If reseating the drive does not resolve the issue, then the failed hard disk drive must be replaced. Contact Cisco TAC for assistance. |
||
Figure 2-5 shows details of the rear panel for the Cisco 3355 Mobility Services Engine.
Figure 2-6 shows the Cisco 3355 Mobility Services Engine back panel LEDs.
Figure 2-5 Cisco 3355 Mobility Services Engine Rear Panel
Note Power supply 1 is the default/primary power supply. If power supply 1 fails, you must replace it immediately.
Note The maximum video resolution is 1600 x 1200 at 75 Hz.
Figure 2-6 shows the LEDs on the rear of the mobility services engine.
Figure 2-6 Cisco 3355 Mobility Services Engine Rear Panel LEDs
Figure 2-7 shows a detailed view of the LEDs on a dc power supply.
Figure 2-7 Close Up of Cisco 3355 Mobility Services Engine DC Power Supply LEDs
– Off: Power is not present, or the power supply or the LED itself has failed.
– Flashing rapidly (4 times per second): The mobility services engine is turned off and is not ready to be turned on. The power-control button is disabled. This will last approximately 20 to 40 seconds.
– Flashing slowly (once per second): The mobility services engine is turned off and is ready to be turned on. You can press the power-control button to turn on the mobility services engine.
– Lit: The mobility services engine is turned on.
– Fading on and off: The mobility services engine is in a reduced-power state. To wake the mobility services engine, press the power-control button or use the IMM Web interface. See the Integrated Management Module User’s Guide for information on logging on to the IMM Web interface.
Figure 2-8 shows the location of the power-supply LEDs on the rear of the Cisco 3355 Mobility Services Engine. See Table 2-2 for additional information about solving power-supply problems.
Figure 2-8 Location of Cisco 3355 Mobility Services Engine Power Supply LEDs
Table 2-2 describes the problems that are indicated by various combinations of the power-supply LEDs on an ac power supply and suggested actions to correct the detected problems.
Specific steps to power-on the Cisco 3355 Mobility Services Engine are provided in Powering On the Mobility Services Engine.
When the mobility services engine is connected to an ac power source but is not turned on, the operating system does not run, and all core logic except for the service processor (the Integrated Management Module) is shut down; however, the mobility services engine can respond to requests to the service processor, such as a remote request to turn on the mobility services engine. The power-on LED flashes to indicate that the mobility services engine is connected to power but is not turned on.
Approximately 5 seconds after the mobility services engine is connected to power, one or more fans might start running to provide cooling while the system is connected to power, and the power-on button LED will blink quickly. Approximately 20 to 40 seconds after the mobility services engine is connected to power, the power-control button becomes active (the power-on LED will blink slowly), and one or more fans might start running to provide cooling while the mobility services engine is connected to power. You can turn on the mobility services engine by pressing the power-control button.
If a power failure occurs while the mobility services engine is turned on, the system will restart automatically when power is restored.
When you turn off the mobility services engine and leave it connected to power, it can respond to requests to the service processor, such as a remote request to turn on the mobility services engine. While the mobility services engine remains connected to power, one or more fans might continue to run. To remove all power from the mobility services engine, you must disconnect it from the power source.
The integrated management module (IMM) can turn off the mobility services engine as an automatic response to a critical system failure.
To replace a 2.5-inch hot-swap SAS hard disk drive, complete the following steps.
You can order replacement hard disk drives from Cisco. The replacement part PID is AIR-SRVR-146GB-HD=.
Step 1 Read the safety information in General Warnings, Regulatory and Safety.
Step 2 Touch the static-protective package that contains the drive to any unpainted metal surface on the mobility services engine; then, remove the drive from the package and place it on a static-protective surface.
Step 3 Ensure that the drive you are replacing has failed before pulling it out of the drive slot. Press on the tray handle to unlock the drive. Pull on the tray handle to remove the drive.
Step 4 Install the hard disk drive in the drive bay:
a. Make sure that the tray handle is in the open (unlocked) position.
b. Align the drive assembly with the guide rails in the bay.
c. Gently push the drive assembly into the bay until the drive stops.
d. Rotate the tray handle to the closed (locked) position.
e. Check the hard disk drive status LED to verify that the hard disk drive is operating correctly. If the amber hard disk drive status LED for a drive is lit continuously, that drive is faulty and must be replaced. If the green hard disk drive activity LED is flashing, the drive is being accessed.
The following section describes the type of ac power supply that the server supports and other information that you must consider when you replace a failed power supply:
To install a hot-swap power supply, complete the following steps.
Step 1 Read the safety information in General Warnings, Regulatory and Safety.
Step 2 Touch the static-protective package that contains the hot-swap power supply to any unpainted metal surface on the mobility services engine; then, remove the power supply from the package and place it on a static-protective surface.
Step 3 Remove the failed power supply first. Grasp the handle on the rear of the power supply and slide the power supply out from the chassis.
Step 4 Grasp the handle on the rear of the power supply and slide the power supply forward into the power-supply bay until it clicks. Make sure that the power supply connects firmly into the power-supply connector.
Step 5 Route the power cord through the handle so that it does not accidentally become unplugged.
Step 6 Connect the power cord for the new power supply to the power-cord connector on the power supply.
Step 7 Connect the other end of the power cord to a properly grounded electrical outlet.
Step 8 Make sure that the ac power LED and the dc power LED on the ac power supply are lit, indicating that the power supply is operating correctly. The two green LEDs are to the right of the power-cord connector.
Figure 2-9 shows the locations of the input and output connectors on the front of the server.
Figure 2-9 Front of Cisco 3355 Mobility Services Engine
Figure 2-10 shows the locations of the input and output connectors on the rear of the server.
Figure 2-10 Rear of Cisco 3355 Mobility Services Engine
For initial system configuration, use the command-line interface (CLI) console. The CLI console connects to the mobility services engine back-panel DB9 console port. Figure 2-5 shows the console port on the back panel of the mobility services engine. Back panel components are described in Rear Panel Components.
Use these terminal emulator settings for the CLI console session:
When you apply AC power to a mobility services engine, the bootup script initializes the operating system and its stored configurations. You are prompted to enter a user ID and password and enter key configuration details.
Follow these steps to power up the mobility services engine.
Step 1 Plug an AC power cord into the back of the two power supplies (Figure 2-5). If only one power supply is connected to a power source, the system will still function correctly but the monitoring components of the mobility services engine will detect the absence of the second power supply and send an alert to WCS. Connect the other end to a grounded 100 to 240 VAC 50/60 Hz electrical outlet.
The end of the power cord that plugs into the mobility services engine conforms with the IEC 320 standard.
Step 2 Use the front-panel Power On/Standby button, located in the operator information panel, to turn the mobility services engine on (Figure 2-2).
Step 3 At the login prompt, enter the mobility services engine operating user ID and password. The default user ID is root and the default password is password.
The user ID and password are case sensitive.
You are now logged into the mobility services engine operating system.
Continue to the “Configuring the Mobility Services Engine” section.
Minimal configuration is done for the mobility services engine as part of installation using the console. All configuration beyond the initial setup using the automatic installation is done with Cisco WCS. For details on automatic installation refer to the “Automatic Installation Script” section.
Note You must change the default root password during initial configuration of the mobility services engine to ensure optimum network security.
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 re-enter 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 whether you would like to set up the initial parameters manually or via the setup wizard.
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.
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.
You can also configure a strong (Grand Unified Bootloader [GRUB]) password. A strong password must have a minimum of nine 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.
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.
You can configure the WCS Communication username and password using the mobility services engine setup.sh script file.
Scenarios that you might encounter while configuring the WCS username and password are as follows:
Note These users are API users, and they do not have corresponding OS users on the mobility services engine appliance.
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.
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.
You can configure NTP servers to set up the time and date of the mobility services engine.
Note You are automatically prompted to enable NTP and enter NTP server IP addresses as part of the automatic installation script. For more details on the automatic installation script, refer to the “Configuring the Mobility Services Engine” section.
Note If you need to add or change an NTP server installation after a mobility services engine install, rerun the automatic installation script. You can configure the NTP server without adjusting the other values by tabbing through the script. To rerun the automatic script, log in as root and run /opt/mse/setup/setup.sh.
Note For more information on the NTP configuration, consult the Linux configuration guide.
To configure a mobility services engine to automatically launch after bootup, enter:
You can verify the mobility services engine software state at any time. In the mobility services engine CLI interface, enter: /etc/init.d/msed status.
If the mobility services engine is running, the command output looks like this example:
If the mobility services engine is not running, the command output looks like this example:
The mobility services engine software automatically runs after initial configuration and after each reboot.
Follow these steps to manually stop and restart the software:
Step 1 To stop the software, enter / etc/init.d/msed stop.
Step 2 To check status, enter / etc/init.d/msed status.
Step 3 To start the software, enter / etc/init.d/msed start.
Step 1 To restart a running mobility services engine, enter /etc/init.d/msed restart.
You can update the mobility services engine using the Cisco WCS or manually download the software using a console port connected to the mobility services engine.
Note If MSE is unreachable on Prime Infrastructure soon after an upgrade, you must reboot the MSE using this command as root user on the MSE: run reboot linux.
Note For the latest Cisco WCS and mobility services engine compatibility and installation notes for a given release, refer to the appropriate release note at the following link: http://www.cisco.com/en/US/products/ps9742/tsd_products_support_series_home.html
Before downloading and updating software on the mobility services engine, note the following:
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 Services > Mobility Services (Figure 2-11).
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.
Figure 2-11 Mobility Services Window
Step 6 To download software, do one of the following:
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.
Step 7 Click Download to send the software to the /opt/installers directory on the mobility services engine.
Step 8 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 9 To run the software, enter /etc/init.d/msed start.
Step 10 To stop the software, enter /etc/init.d/msed stop and to check status enter /etc/init.d/msed status.
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:
Step 5 To uninstall the mobility services engine’s script files, enter:
If you lose or forget the root password for a mobility services engine, follow these steps below.
Note The following steps must be done via a connection over the console port, not by connecting a keyboard, mouse and monitor to the unit.
Step 1 When the GRUB screen comes up, press Esc to enter the boot menu.
If you do not see the GRUB menu on your serial console, go to Step 4.
Step 3 Navigate to the line beginning with “kernel,” and press e.
If there is no "rhgb quiet consolettys0,9600" string on the line, at the end of the line, enter a space and enter "rhgb quiet consolettyS0,9600". Then enter a space and the number one (1).
Press Enter to save this change.
Step 4 When you connect to the MSE via serial console and reboot, if the GRUB screen does not show up, complete the following steps:
a. Connect a monitor and keyboard to the MSE and reboot.
b. Once you see the GRUB screen on the attached monitor, press Esc to enter the boot menu.
d. Navigate to the line beginning with "kernel," and press e.
Enter a space and the number one (1). The modified line should appear as follows:
Press Enter to save your changes. Continue your interaction using the monitor and keyboard.
Step 5 Press b to begin boot sequence.
At the end of the boot sequence, a shell prompt appears.
Note The shell prompt does not appear if you have set up a single user mode password.
Step 6 You can change the root password by entering the passwd command.
Step 7 Enter and confirm the new password.