Troubleshooting Installation Problems

When you install a Cisco UE module, problems might occur in downloading the software package. These problems might be caused by network connectivity or package issues. This section discusses some common problems that might occur during software installation of Cisco UE and ways to troubleshoot them.

Network Connectivity Issues

If the Cisco UE module is unable to establish contact with the FTP server where the software load resides, the error shown in Example 19-13 occurs when you attempt to install the software.

Example 19-13. Installation Failed

cueinstaller#>software install package url ftp://username:password@1.3.61.61/
 cue-vm.1.1.0.6.pkg
RAMDisk mounted
Connecting to host...
curl: (7) Connect failed 
ERROR: Host did not respond. 
Please check the host ip and try again.
RAMDisk unmounted

First ensure that the IP address of the FTP server is correct. Verify all the parameters given in the install command. If you are sure these are all correct, verify the IP connectivity from the Cisco UE module to the router. Reboot the Cisco UE module, as shown in Example 19-14, and press *** at the first prompt. This action takes you to the bootloader prompt.

Example 19-14. Checking IP Connectivity Between Cisco UE and the FTP Server

cueinstaller#>reboot
WARNING: This will reboot the Service Engine!
Do you wish to continue (y,n) [n] y

The bootloader has a ping command, as shown in Example 19-15.

Example 19-15. Checking IP Connectivity from the Bootloader

ServicesEngine boot-loader> ping 1.3.61.61
Sending 5, 32 byte ICMP Echos to 1.3.61.61:
.....
Success rate is 0% (0/5)

ServicesEngine boot-loader> ping 1.3.61.16
Sending 5, 32 byte ICMP Echos to 1.3.61.16:
!!!!!
Success rate is 100% (5/5)

If the Cisco UE system cannot ping the FTP server, you might have the wrong configuration of IP parameters in the bootloader. Example 19-16 shows how to check the bootloader configuration. If you see anything wrong, you can use the bootloader config command to make modifications.

Example 19-16. Checking the Bootloader Configuration

ServicesEngine boot-loader>show config
IP addr: 1.4.13.90
Netmask: 255.255.0.0
TFTP server : 1.4.53.1
GW IP addr: 1.4.13.190
Default boot: disk
Bootloader Version: 1.0.17
Default Helper-file: cue-installer.1.1.1
Default BIOS: primary
Default bootloader: primary
Default cpu throttle: 50%

Another reason why the ping command might not be successful is the routing configuration on the Cisco IOS router. With an ip unnumbered configuration for the service-engine interface, you can verify the routing as follows:

• Ping the FTP host from the Cisco IOS router to ensure that the host can be reached. If this fails, examine the Cisco IOS routing configuration.
• If the FTP host can be reached from the router, verify the Cisco UE module's connectivity, as shown in Example 19-17.

Example 19-17. Verifying Routing Table Information for Cisco UE Connectivity

router#show ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
 D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
 E1 - OSPF external type 1, E2 - OSPF external type 2
 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
 ia - IS-IS inter area, * - candidate default, U - per-user static route
 o - ODR, P - periodic downloaded static route
Gateway of last resort is 1.3.0.1 to network 0.0.0.0
 1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 1.3.0.0/16 is directly connected, FastEthernet0/0
S 1.3.6.129/32 is directly connected, Service-Engine1/0
 20.0.0.0/24 is subnetted, 1 subnets
S 20.20.20.0 [1/0] via 1.3.6.26
 10.0.0.0/24 is subnetted, 1 subnets
C 10.10.10.0 is directly connected, FastEthernet0/1
 41.0.0.0/24 is subnetted, 1 subnets
S 41.41.41.0 [1/0] via 1.3.6.28
S* 0.0.0.0/0 [1/0] via 1.3.0.1

When the show ip route command is executed, a host route similar to the one highlighted in Example 19-17 should be displayed (where 1.3.6.129 is the IP address of your Cisco UE module and Service-Engine 1/0 is the Cisco UE module seated in NM slot 1 of the router). If such a route does not show in your routing table, use the following command to add it:

router(config)#ip route 1.3.6.129 255.255.255.255 Service-Engine 1/0

 

Software Package Issues

Sometimes a problem might occur in downloading the software, such as if binary mode was not used in the FTP command. This causes a problem when installing the software, such as the error shown in Example 19-18.

Example 19-18. Failed Installation Caused by Corrupted Files

cueinstaller#>software install package ftp://username:password@1.3.61.16/pkg/
cue-vm.1.1.0.6.pkg
RAMDisk mounted
Connecting to host...
 % Total % Received % Xferd Average Speed Time Curr.
 Dload Upload Total Current Left Speed
100 92785 100 92785 0 0 221k 0 0:00:00 0:00:00 0:00:00 2623k
RAMDisk unmounted
ERROR:: Security Header Validation Failed. 

The error shown in Example 19-19 indicates that not all the files needed for installation are present on the FTP server.

Example 19-19. Failed Installation Caused by a Missing File

cueinstaller#>software install package ftp ://username :password@1.3.61.16/
cue-vm.1.1.1pkg
Created RAMDisk.
File System Type = reiser
RAMDisk mounted
Connecting to host...
 % Total % Received % Xferd Average Speed Time Curr.
 Dload Upload Total Current Left Speed
100 92811 100 92811 0 0 361k 0 0:00:00 0:00:00 0:00:00 8822k
Core File List is Signed
Retrieving cue-vm.1.1.1.manifest from 1.3.61.16
Retrieve manifest from server failed.
RAMDisk unmounted
Connecting to host...
curl: (19) cue-vm.1.1.1.manifest: No such file or directory 
ERROR: The requested file does not exist on host.
Please check the package name and try again.

To recover from these software package installation errors, again download the software to the FTP server. Ensure that three types of files are present on the FTP server:

• .pkg
• .prt1
• .manifest (this file no longer exists separately in Cisco UE releases after 2.0)

Along with the available software image packages, a bootloader package is available. All Cisco UE software versions have a minimum bootloader version requirement. The manifest does not check that the minimum bootloader version is present in the system. Refer to the Cisco UE documentation to identify the bootloader version that is compatible with the Cisco UE software version you're trying to install. The exact files that comprise the installation might also vary from release to release. The examples in this section pertain to Cisco UE 1.1.1.

Troubleshooting Cisco UE Startup