Installation Guide for Cisco Unified SIP Proxy Release 8.5
Installing Cisco Unified SIP Proxy Release 8.5
Downloads: This chapterpdf (PDF - 289.0KB) The complete bookPDF (PDF - 0.97MB) | Feedback

Installing Cisco Unified SIP Proxy Release 8.5

Table Of Contents

Installing Cisco Unified SIP Proxy Release 8.5

About Installing Cisco Unified SIP Proxy Release 8.5

About Installing on a Network Module

About Installing on a Service Module

Restrictions for Installing Cisco Unified SIP Proxy Release 8.5

Configuration

Hardware

System Functionality

Prerequisites for Installing Cisco Unified SIP Proxy Release 8.5

Loading the Correct IOS Image on the ISR

Activating IP Connectivity to Cisco Unified SIP Proxy

Prerequisites

Summary Steps

Detailed Steps

Examples of IP Connectivity

Opening and Closing a Session with the Module

Summary Steps

Detailed Steps

Preparing the FTP and TFTP Servers

Booting Up Cisco Unified SIP Proxy for the First Time

How to Download and Install the Software

Using the Clean Install Command

About Using the Clean Install Command

Prerequisites for Using the Clean Install Command

Downloading and Installing the Clean Install Command Software Files

Example of Installing the Software Using the Clean Install Software Command

How to Install the Software on a Service Module

Installing the Software

Example of Installation on a Service Module

Using the Postinstallation Configuration Tool


Installing Cisco Unified SIP Proxy Release 8.5


Last updated: September 12, 2012

Caution If you are upgrading to Cisco Unified SIP Proxy Release 8.5 from a Release 1.x image, you must install the software by using a helper. For information about migrating from a Release 1.x system to a Release 8.5 system, see Migrating from Cisco Unified SIP Proxy Release 1.x to Release 8.5. Do not follow the procedures in this chapter.

About Installing Cisco Unified SIP Proxy Release 8.5

Restrictions for Installing Cisco Unified SIP Proxy Release 8.5

Prerequisites for Installing Cisco Unified SIP Proxy Release 8.5

How to Download and Install the Software

About Installing Cisco Unified SIP Proxy Release 8.5

There are two hardware platforms on which you can install Cisco Unified SIP Proxy Release 8.5:

network module, such as the NME-CUSP-522

service module, such as the SM-SRE-700 and SM-SRE-900

About Installing on a Network Module

Use this process if you are using a network module. You can also use this process if you are using a service module but only if the software has already been loaded.


Caution You cannot use this process with a blank service module.

If you are upgrading to Cisco Unified SIP Proxy Release 8.5 from a Release 1.x image, you must install the software by using a helper. If a Cisco Unified SIP Proxy Release 8.5 image already exists on the router, then you can perform a clean installation.

For information about migrating from a Release 1.x system to a Release 8.5 system, see Migrating from Cisco Unified SIP Proxy Release 1.x to Release 8.5. Do not follow the procedures in this chapter.

Follow these steps:

1. Read the restrictions. See Restrictions for Installing Cisco Unified SIP Proxy Release 8.5.

2. Perform the prerequisites. See Prerequisites for Installing Cisco Unified SIP Proxy Release 8.5.

3. Install the software. See either How to Install the Software on a Service Module.

4. Use the Postinstallation Configuration Tool. See Using the Postinstallation Configuration Tool.

About Installing on a Service Module


Note For information about migrating from a Release 1.x system to a Release 8.5 system, see Migrating from Cisco Unified SIP Proxy Release 1.x to Release 8.5. Do not follow the procedures in this chapter.


Use this process if you are using a service module. The service module can be blank or have the software already loaded on it.


Caution This process does not work with network modules.

Follow these steps:

1. Read the restrictions. See Restrictions for Installing Cisco Unified SIP Proxy Release 8.5.

2. Perform the prerequisites. See Prerequisites for Installing Cisco Unified SIP Proxy Release 8.5.

3. Install the software. See Using the Clean Install Command.

4. Use the Postinstallation Configuration Tool. See Using the Postinstallation Configuration Tool.

Restrictions for Installing Cisco Unified SIP Proxy Release 8.5

Configuration

Hardware

System Functionality

Configuration

You can only configure the module software by using a console that connects to a single serial console port on the host router. From the console, you use the router's Cisco IOS software CLI to reach the module.

Hardware

You cannot replace the hard disk on the module. If the module's hard disk crashes, you must replace the module.

The module's front panel Gigabit Ethernet 0 port is not used by Cisco Unified SIP Proxy and is disabled. The Gigabit Ethernet on the backplane connects the Cisco Unified SIP Proxy module to the router and is the only active Gigabit Ethernet port on the module.

System Functionality

Cisco Unified SIP Proxy does not support CiscoWorks Configmaker.

Prerequisites for Installing Cisco Unified SIP Proxy Release 8.5

Loading the Correct IOS Image on the ISR

Activating IP Connectivity to Cisco Unified SIP Proxy

Opening and Closing a Session with the Module

Preparing the FTP and TFTP Servers

Booting Up Cisco Unified SIP Proxy for the First Time

Loading the Correct IOS Image on the ISR

Cisco Unified SIP Proxy Release 8.5 requires that the host ISR be running a K9 IOS image. Follow these steps to load the correct IOS image onto the ISR.

Procedure


Step 1 Download the K9 version of this image from Cisco.com.

The file is called c<xxxx>-ipbasek9-<IOS_release_number>, where <xxxx> is the ISR model number and <IOS_release_number> is the release number for your Cisco IOS system. For example, the file is called c3845-ipbasek9-mz.150-1.M3 for a 3845 router that uses Cisco IOS release 15.0(1)M3. For an ISR G2, such as the 3925 or 3945, an example IOS image file is c3900-universalk9-mz.SPA.150-1.M3

To find the file, do the following:

a. Go to Cisco.com.

b. Click Support.

c. On the right, in the box that says Option 2: Select a Task, click Download Software.

d. In the left box, click Products.

e. In the middle box, click Cisco IOS and NX-OS Software.

f. In the right box, click your release of Cisco IOS, such as Cisco IOS.

g. In the right box, click your release of Cisco IOS, such as Cisco IOS Software Release 15M&T.

h. In the right box, click your release of Cisco IOS, such as Cisco IOS Software Release 15M.

i. In the right box, scroll down and click Routers.

j. In the right box, scroll down and click Branch Routers.

k. Click the name of your router model.

l. Under Select a Software Type, click IOS Software.

m. Click the software version that corresponds to the IOS version installed on your system.

n. Scroll down until you find the file.

o. Click Download Now.

p. Log in if you are prompted.

q. Proceed with the download.

Step 2 Physically connect the console to the router.

Step 3 Log in to the machine using SSH or Telnet.

Step 4 Copy the image that you downloaded in Step 1 to the flash directory.

Step 5 Ensure that the config register is set to 0x2102 so that the router can boot from flash.

Step 6 Configure the ISR to automatically load this Cisco IOS image after a reboot by entering these commands:

boot-start-marker
boot system flash:<file_name>
boot-end-marker

Activating IP Connectivity to Cisco Unified SIP Proxy

After you physically install the module in the router, you need to activate the IP communication link between the host router and the Cisco Unified SIP Proxy application.

Prerequisites

Summary Steps

Detailed Steps

Examples of IP Connectivity

Prerequisites

Gather the following information before activating the software:

Slot and port numbers of the module on the Cisco router that hosts Cisco Unified SIP Proxy.

IP address and subnet mask of the Cisco router that hosts Cisco Unified SIP Proxy or the unnumbered interface type and number.

IP address of the module. This IP address must be on the same subnet as the Cisco router that hosts Cisco Unified SIP Proxy.

IP address of the default gateway of the host router. This IP address must be the same IP address as the Cisco router that hosts Cisco Unified SIP Proxy.

Figure 1 Router and Module Interfaces

Summary Steps

1. Depending on your module type, do one of the following:

For a network module:

interface integrated-Service-Engine slot/port

For a service module:

interface sm slot/0

2. ip address router-ip-addr subnet-mask

or

ip unnumbered type number

3. service-module ip address cusp-side-ip-addr subnet-mask

4. service-module ip default-gateway gw-ip-addr

5. no shutdown

6. exit

7. ip route cusp-side-ip-addr subnet-mask integrated-Service-Engine slot/port

Detailed Steps

 
Command or Action
Purpose

Step 1 

Depending on your module type, do one of the following:

 
interface integrated-service-engine slot/port
Example:
Router(config)# interface interface-service-engine 
2/0

Enters interface configuration mode on the enhanced network module (NME).

 
interface sm slot/0
Example:
Router(config)# interface sm 2/0

Enters interface configuration mode on the Service Module (SM) SRE module.

Step 2 

Enter one of the following:

 
ip address router-ip-addr subnet-mask 
Example:
Router(config-if)# ip address 172.18.12.28 
255.255.255.0
 
        

Specifies the IP address and subnet mask of the Cisco IOS router hosting Cisco Unified SIP Proxy.

 
ip unnumbered type number
Example:
Router(config-if)# ip unnumbered GigabitEthernet 0/0

Specifies the interface type and number for the Cisco IOS router hosting Cisco Unified SIP Proxy.

Step 3 

service-module ip address cusp-side-ip-addr subnet-mask

Example:

Router(config-if)# service-module ip address 172.18.12.26 255.255.255.0

Specifies the IP address of the Cisco Unified SIP Proxy module interface. This IP address must be on the same subnet as the Cisco router that hosts Cisco Unified SIP Proxy.

Step 4 

service-module ip default-gateway gw-ip-addr

Example:

Router(config-if)# service-module ip default-gateway 172.18.12.1

Specifies the default gateway for Cisco Unified SIP Proxy.

Step 5 

no shutdown
Example:

Router(config-if)# no shutdown

Enables actual IP connectivity to the blade.

Step 6 

exit
Example:

Router(config-if)# exit

Exits interface configuration mode.

Step 7 

ip route cusp-side-ip-addr subnet-mask integrated-Service-Engine slot/port

Example:

Router(config-if)# ip route 172.18.12.26 255.255.255.0 integrated-Service-Engine 2/0

Specifies the IP route on the Cisco Unified SIP Proxy side.

Examples of IP Connectivity

The following partial outputs from the show running-config command shows how the interfaces are configured.

With IP Address

Router(config)# interface integrated-Service-engine 1/0
Router(config-if)# ip address 10.0.0.20 255.255.255.0
Router(config-if)# service-module ip address 172.18.12.28 255.255.255.0
Router(config-if)# service-module ip address default-gateway 172.18.12.26
Router(config-if)# ip route 172.18.12.26 255.255.255.0 integrated-Service-Engine 2/0

With IP Unnumbered

Router(config)# interface integrated-Service-Engine 2/0
Router(config-if)# ip unnumbered GigabitEthernet 0/0
Router(config-if)# service-module ip address 172.18.12.26 255.255.255.0
Router(config-if)# service-module ip default-gateway 172.18.12.1
Router(config-if)# ip route 172.18.12.26 255.255.255.0 integrated-Service-Engine 2/0

Opening and Closing a Session with the Module

After you set up the module interfaces, you can open and close a session on the Cisco Unified SIP Proxy. The first time that you access the Cisco Unified SIP Proxy module, its hostname will be the factory default, probably SE-Module.

Summary Steps

Detailed Steps

Summary Steps

From the Host Router CLI

1. enable

2. Depending on your module type, do one of the following:

For a network module:

service-module integrated-Service-Engine slot/port status

For a service module:

service-module Service-Module slot/port status

3. Depending on your module type, do one of the following:

For a network module:

service-module integrated-Service-Engine slot/port session

For a service module:

service-module Service-Module slot/port session

4. Enter your credentials.

From the Module CLI

5. Do configuration or other procedures.

The first time that you open a session, the system launches the postinstallation configuration tool. See the "Using the Postinstallation Configuration Tool" section.

To see which other configurations are available, see the CLI Configuration Guide for Cisco Unified SIP Proxy Release 8.5.

6. Control-Shift-6 x or exit

From the Host Router CLI

7. Depending on your module type, do one of the following:

For a network module:

service-module integrated-Service-Engine slot/port session clear

For a service module:

service-module Service-Module slot/port session clear

Detailed Steps

 
Command or Action
Purpose
 
From the Host-Router CLI

Step 1 

enable

Example:

Router> enable

Enters privileged EXEC mode on the host router. Enter your password if prompted.

Step 2 

Depending on your module type, do one of the following:

 

service-module integrated-service-engine slot/port status

Example:

Router# service-module integrated-service-engine 2/0 status

Displays the status of the specified module, so that you can ensure that the module is running (that is, in steady state).

Note If the module is not running, start it with one of the startup commands listed in the CLI Command Reference for Cisco Unified SIP Proxy Release 8.5.

 

service-module Service-Module slot/port status

Example:

Router# service-module Service-Module 2/0 status

Displays the status of the specified module, so that you can ensure that the module is running (that is, in steady state).

Note If the module is not running, start it with one of the startup commands listed in the CLI Command Reference for Cisco Unified SIP Proxy Release 8.5.

Step 3 

Depending on your module type, do one of the following:

 

service-module integrated-service-engine slot/port session

Example:

Router# service-module integrated-service-engine 1/0 session

Begins a session on the specified module. Do one of the following:

To interrupt the autoboot sequence and access the bootloader, quickly type ***.

To start a configuration session, press Enter.

 

service-module Service-Module slot/port session

Example:

Router# service-module Service-Module 2/0 session

Begins a session on the specified module. Do one of the following:

To interrupt the autoboot sequence and access the bootloader, quickly type ***.

To start a configuration session, press Enter.

Step 4 

Enter your credentials.

 
From the Service-Module Interface

Step 5 

Example:

SE-Module> configure terminal

SE-Module(config)>

.

SE-Module(config)> exit

SE-Module> write

Enter configuration commands on the module as needed.

Configuration command choices are similar to those that are available on the router. Access global configuration mode by using the configure terminal command. Enter configuration commands. Then exit global configuration mode with the exit command and save your new configuration with the write command.

Step 6 

Press Control-Shift-6 x.

Closes the service-module session and returns to the router CLI.

Note The service-module session stays up until you clear it in the next step. While it remains up, you can return to it from the router CLI by pressing Enter.

Step 7 

Depending on your module type, do one of the following:

 

service-module integrated-service-engine slot/port session clear

Example:

Router# service-module integrated-service-engine 1/0 session clear

Clears the service-module session for the specified module. When prompted to confirm this command, press Enter.

 

service-module Service-Module slot/port session clear

Example:

Router# service-module Service-Module 2/0 session clear

Clears the service-module session for the specified module. When prompted to confirm this command, press Enter.

Preparing the FTP and TFTP Servers

Verify that your download FTP and TFTP servers are accessible. You will need the FTP server for installations, backups, and restores, and the TFTP file server (on the FTP-file-server machine) for boothelper operations to recover if the installation fails.


Note The FTP server that communicates with Cisco Unified SIP Proxy must support passive FTP requests.


For more information, see your FTP server documentation.

Booting Up Cisco Unified SIP Proxy for the First Time

The first time Cisco Unified SIP Proxy is booted up, you are prompted for information about your Cisco Unified SIP Proxy. When you are asked if you want to configure the module, answer yes. Answer the questions that follow which include questions about time zone, NTP servers, and other details about your configuration.

How to Download and Install the Software

Using the Clean Install Command

How to Install the Software on a Service Module

Using the Postinstallation Configuration Tool


Tip If you lose power or connection during any of the following procedures, the system usually detects the interruption and tries to recover. If it fails to recover, reinstall the system using the boot helper.


Using the Clean Install Command

About Using the Clean Install Command

Prerequisites for Using the Clean Install Command

Downloading and Installing the Clean Install Command Software Files

Example of Installing the Software Using the Clean Install Software Command

About Using the Clean Install Command

The system is offline while you are using this clean installation process. The clean installation erases the disk before loading the new files on the disk.

However, your previous module configuration, if any, is usually saved to the flash memory. After the new files are loaded, the system offers to restore the configuration it finds in flash, if any. You can choose to restore this configuration into the new image. A stored configuration contains some of the data from a previous installation, but not as much as a backup.

If you are recovering from a disaster and do not have a backup, you can restore the saved configuration.
If you choose not to restore the saved configuration, it is erased from flash.

Prerequisites for Using the Clean Install Command

The blade on which you are installing the software must have a Cisco Unified SIP Proxy Release 8.5 image on it. If it does not, you must use the boot helper process, described in Migrating from Cisco Unified SIP Proxy Release 1.x to Release 8.5.

Gather the following information:

FTP server hostname or IP address. If the Cisco Unified SIP Proxy is configured to use DNS, use the hostname. If the Cisco Unified SIP Proxy is not configured to use DNS, use the IP address.

FTP server username

FTP server password

Software package name

Ensure that the FTP server is configured and active.

Ensure that you can ping the module from the FTP server.

Downloading and Installing the Clean Install Command Software Files

Procedure


Step 1 Log in to Cisco.com and go to the Cisco Unified SIP Proxy software download page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=282713225.

Step 2 Download all the Cisco Unified SIP Proxy Release 8.5 software files. For a complete list of all the files, see the Release Notes for Cisco Unified SIP Proxy Release 8.5.

Step 3 Copy the files to the FTP server.

Step 4 Starting from Cisco Unified SIP Proxy EXEC mode, enter the following:

ping <ftp_server_ip_address>

Step 5 Install the software by entering the following:

software install clean url ftp://<ftp_server_ip_address>/cusp-k9.nmx.8.5.1.pkg

Step 6 Enter y to confirm installation.

Step 7 Enter boot disk.

Step 8 Enter y to begin postinstallation configuration immediately.

Step 9 Enter y to confirm immediate configuration.

Step 10 Enter y to restore the configuration saved in memory or n to use your backup to restore your configuration.

Step 11 If you entered y in step 10 enter y again to confirm restoration of the saved configuration.

Step 12 Use the show software versions command to verify the reinstallation.


Related Topics

Refer to the CLI Command Reference for Cisco Unified SIP Proxy Release 8.5 for information about the CLI commands.

Example of Installing the Software Using the Clean Install Software Command

The following output illustrates the online installation process, from ensuring the FTP server is reachable, to configuration using the data found in memory and finally, verifying the version.

se-10-50-30-125#software install clean url ftp://10.50.10.25/dir/cusp-k9.nmx.8.5.1.pkg 
 
   
 
   
WARNING:: This command will install the necessary software to 
WARNING:: complete a clean install.  It is recommended that a backup be done 
WARNING:: before installing software. 
 
   
Would you like to continue?[confirm]
 
   
Downloading ftp cusp-k9.nmx.8.5.1.pkg
Bytes downloaded :  147082 
 
   
Validating package signature ... done
 - Parsing package manifest files... complete.
Validating installed manifests ........complete.
 - Checking Package dependencies... complete.
 - Checking Manifest dependencies for subsystems in the install candidate list...
complete
Starting payload download
Starting payload download 
File : cusp-full-k9.nmx.8.5.1.prt1 Bytes : 83865859 
Downloading payload(s) complete
Validating payloads match registered checksums...
 - cusp-full-k9.nmx.8.5.1.prt1 
................................................................................verified
Validating installed manifests ........complete.
Clearing previous downgrade files ... complete.
Performing Hot install ...starting_phase:
install_files.sh /dwnld/.hot_work_order
install_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 0 __PRIMARY_BOOTLOADER__ gz
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 1 / 
/sw/installed/manifest/bootloader_prim_manifest.sig none
install_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 5 __SECONDARY_BOOTLOADER__ gz
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 4 / 
/sw/installed/manifest/bootloader_sec_manifest.sig none
WARNING sysdb util exit (Protocol error) Probable leak of evtsrc @b704f1b0 by: python 
InstMain.py
. 
superthread:    INFO superthread server output END
 
   
starting_phase:
install_files.sh /dwnld/.work_order
Mon Apr  5 18:20:48 UTC 2010
Remove: ///
root directory
removing INSTALLER_WORK_ORDER
removing INSTALL_COMPLETE
removing application
removing data
removing database
removing home
removing ldap
removing name(s)
removing opt
removing scratch
removing sw
clearing ////tmp/
removing usr
add_file /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 4 / tgz
add_file /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 7 / tgz
add_file /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 9 / tgz
cdp:    INFO cdp server output WARNING sysdb evt provider (Operation canceled) event 
handler is dead: event=get, attr=/sw/dns/host/name, sender=1554'/bin/cdpd', state=0, 
deadline=11:28:24=+450, provider=dns@1634'?'
 
   
cdp:    INFO cdp server output WARNING sysdb evt provider (Operation canceled) event 
handler is dead: event=get, attr=/sw/dns/host/domain, sender=1554'/bin/cdpd', state=0, 
deadline=18:28:24=+450, provider=dns@1634'?'
 
   
extract_mv_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 2 / lib tgz
extract_mv_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 2 / bin tgz
extract_mv_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 2 / etc tgz
extract_mv_file: /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 2 / sbin tgz
install_file: 
n/KpXrE2b444jrkSlT6Kcu3co1adzDK+EGgoG/EwPX5rIY20ST+kRKYH5ulF28p7AIESITDsyssW3XBa6kI3wgeCEN
EL8x5mEtKWGoDL4HzlyK7j3q5Gr7G9P81JGRPA0b77iuFj1QPBWiv931EOA3teCPfg6ZLnSlhFA3s2hmQ= 
__BZ_SIGNATURE__
bzsig ldbl -m bryce -t bzsig 
n/KpXrE2b444jrkSlT6Kcu3co1adzDK+EGgoG/EwPX5rIY20ST+kRKYH5ulF28p7AIESITDsyssW3XBa6kI3wgeCEN
EL8x5mEtKWGoDL4HzlyK7j3q5Gr7G9P81JGRPA0b77iuFj1QPBWiv931EOA3teCPfg6ZLnSlhFA3s2hmQ=
add_file /dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1 2 / bzImage tgz
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 3 / 
sw/installed/manifest/cusp_infrastructure_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 1 / 
sw/installed/manifest/bootloader_prim_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 7 / 
sw/installed/manifest/infrastructure_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 8 / 
sw/installed/manifest/global_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 4 / 
sw/installed/manifest/bootloader_sec_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 6 / 
sw/installed/manifest/installer_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 2 / 
sw/installed/manifest/oscore_manifest.sig none
add_file /dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg 5 / 
sw/installed/manifest/gpl_infrastructure_manifest.sig none
Remove: //dwnld/pkgdata/cusp-k9.nmx.8.5.1.pkg
Remove: //dwnld/pkgdata/cusp-full-k9.nmx.8.5.1.prt1
Creating new nodes.
Performing final moves mnt_dir: /
INIT: fndn_udins_wrapper:    INFO fndn_udins_wrapper server output END
 
   
cdp:    INFO cdp server output END
 
   
 
   
Rebooting ...
 
   
shutdown: sending all processes the TERM signal...
rbcp:    INFO rbcp daemon output END
 
   
platform.config:    INFO platform.config server output END
 
   
trace:    INFO trace daemon output END
 
   
shutdown: sending all processes the KILL signal.
shutdown: turning off swap
shutdown: unmounting all file systems
Please stand by while rebooting the system.
Restarting system.
Nmi Npx0 Dly P92 Sha0 Kbd0 Cmos Pci Dma0 PrtB Tim Exp Rfsh Geom 
 
   
Initializing memory.  Please wait. Mem0 Mem1 Ebda Sha1 CacheE Admgr1 Memmgr1 AdmgrEbda 
Media LowBios Brd2 
 
   
Swap to secondary BIOS ... Mem1 Ebda Sha1 CacheE Admgr1 Memmgr1 AdmgrEbda Media LowBios 
Brd2 Cache0 Driver PostDrv Dma1 Irq1 Vec Brd4 Time0 Kbd1 Speed Com Vid0 Par PciEnum Vid1 
Redir Brd6 Com KbdBuf SMM 
General Software Firmbase[r] SMM Kernel 1.3.2 Feb 11 2005 11:51:07
Intel(R) E7320 Performance Development Platform
 
   
EIST: Enhanced Intel Speedstep Driver, V3.0.
EIST: Copyright (C) 2003-2006 General Software, Inc.
EIST: Built Mar  3 2006, 14:49:27
UsbHid Pwd Msg0 Msg1 Cache1 Mem2 Prot Cache2 Flg Siz0 Msg2 Ata Dsk Npx1 Apm Err Dbg Enb 
App MemReduce MemSync1 Ext MemSync2 PciRom MemSync3 Setup Time1 Mfg Brd8 Com Admgr2 Cfg 
Brd10 
DDR2 Memory 2047 MB with ECC detected
Intel(R) Celeron(R) M processor         1.00GHz
BIOS ISE 5.00, Build date: 05/05/06
System Now Booting ...
 
   
704 832 968 1040 1172 1184 1196 1208 1220 1228 1240 1260 1276 1288 1304 1320 1332 1348 
1368 1380 1644 1784 2060 2204 2344 2860 3376 3640 3904 4168 RSA decrypt returned:33
a434d0dc915ae14f5477ff3cf44c7d22
 
   
Booting from Secure secondary boot loader..., please wait.
 
   
[BOOT-ASM]
 
   
Updating flash with bootloader configuration: 1
Please wait ...
.............done.
 
   
Please enter '***' to change boot configuration: 
Loading disk:/bzImage ... Verifying ... done.
Starting Kernel.
 
   
Platform: nmx
 
   
Cisco init
INIT: version 2.86 booting
mounting proc fs ...
mounting sys fs ...
mounting /dev/shm tmpfs ...
reiser root fs ...
Reiserfs super block in block 16 on 0x801 of format 3.6 with standard journal
Blocks (total/free): 19537040/19481910 by 4096 bytes
Filesystem is clean
Filesystem seems mounted read-only. Skipping journal replay.
Checking internal tree..finished
 
   
FILESYSTEM CLEAN
Remounting the root filesystem read-write...
 
   
kernel.sem = 1900 4000 32 100
vm.overcommit_memory = 1
 
   
Welcome to Cisco Service Engine
 
   
Power button monitor started
Setting the system time from hardware clock
 
   
********** rc.aesop ****************
Populating resource values from /etc/bryce_rsrc_file
attribute ios_rbcp/app_cookie_id exists
Populating resource values from /etc/default_rsrc_file
Populating resource values from /etc/products/umg/default_rsrc_file
Processing manifests . . . . . . . . complete
==> Management interface is eth0
==> Management interface is eth0
 
   
Serial Number: FOC11424VUM
INIT: Entering runlevel: 2
********** rc.post_install ****************

How to Install the Software on a Service Module

Use this process only if you are starting with a service module. Otherwise, use the process described in the "Using the Clean Install Command" section.

Installing the Software

Example of Installation on a Service Module

Related Topics

Cisco SRE Service Module Configuration and Installation Guide

Installing the Software

Procedure


Step 1 Log in to Cisco.com and go to the Cisco Unified SIP Proxy software download page at http://tools.cisco.com/support/downloads/pub/Redirect.x?mdfid=282713225.

Step 2 Download all the Cisco Unified SIP Proxy Release 8.5 software files. For a complete list of all the files, see the Release Notes for Cisco Unified SIP Proxy Release 8.5.

Step 3 Copy the files to the FTP server.

Step 4 Starting from router EXEC mode, enter the following:

ping <ftp_server_ip_address>

Step 5 Install the software by entering the following:

service-module Service-Module 1/0 install url ftp://<ftp_server_ip_address>/cusp-k9.sme.8.5.1.pkg

Step 6 Enter y to confirm installation.

Step 7 Enter Cisco Unified SIP Proxy SM to monitor and complete the installation.


Example of Installation on a Service Module

Router# service-module sm 1/0 install url 
ftp://<ftp_server_ip_address>/cusp-k9.sme.8.5.1.pkg
Delete the installed Cisco Unified SIP Proxy (CUSP) and proceed with new installation? 
[no]: yes
Loading 8.5.0.168/sme/cusp-k9.sme.8.5.1.pkg.install.sre !
[OK - 1850/4096 bytes]
cur_cpu:  1862
cur_disk:  953880
cur_mem:  4135616
cur_pkg_name: cusp-k9.sme.8.5.1.pkg
cur_ios_version: 15.1(2.19)T0.3,
cur_image_name: c2951-universalk9-mz
cur_pid: SM-SRE-900-K9
bl_str: 
inst_str: 
app_str: 
key_filename: cusp-k9.sme.8.5.1.key
helper_filename: cusp-helper.sme.8.5.1
Resource check passed...
 
   
Router#

Related Topics

See the CLI Command Reference for Cisco Unified SIP Proxy Release 8.5 for information about the CLI commands.

Using the Postinstallation Configuration Tool

When you open the first session, the system launches the post installation configuration tool, and asks you if you want to start configuration immediately.

Enter the appropriate response, y or n. If you enter n, the system will halt. If you enter y, the system will ask you to confirm, then begin the interactive postinstallation configuration process.

The following is an example:

IMPORTANT::
IMPORTANT::    Welcome to Cisco Systems Service Engine 
IMPORTANT::     post installation configuration tool. 
IMPORTANT::
IMPORTANT:: This is a one time process which will guide 
IMPORTANT:: you through initial setup of your Service Engine.
IMPORTANT:: Once run, this process will have configured 
IMPORTANT:: the system for your location.
IMPORTANT::
IMPORTANT:: If you do not wish to continue, the system will be halted 
IMPORTANT:: so it can be safely removed from the router.
IMPORTANT::
 
   
Do you wish to start configuration now (y,n)? yes
Are you sure (y,n)? yes
 
   
IMPORTANT:: 
IMPORTANT:: A configuration has been found in flash.  You can choose 
IMPORTANT:: to restore this configuration into the current image.
IMPORTANT:: 
IMPORTANT:: A stored configuration contains some of the data from a 
IMPORTANT:: previous installation, but not as much as a backup.
IMPORTANT::
IMPORTANT:: If you are recovering from a disaster and do not have a
IMPORTANT:: backup, you can restore the saved configuration.
IMPORTANT::
IMPORTANT:: If you choose not to restore the saved configuration, it 
IMPORTANT:: will be erased from flash.
IMPORTANT::
 
   
Would you like to restore the saved configuration? (y,n) n
 
   
Erasing old configuration...done.
 
   
IMPORTANT::
IMPORTANT:: The old configuration has been erased.
IMPORTANT:: As soon as you finish configuring the system please use the
IMPORTANT:: "write memory" command to save the new configuration to flash.
IMPORTANT::
 
   
Enter Hostname
 (my-hostname, or enter to use se-10-50-30-125): 
Using se-10-50-30-125 as default
 
   
Enter Domain Name
 (mydomain.com, or enter to use localdomain): cusp
 
   
IMPORTANT:: DNS Configuration:
IMPORTANT:: 
IMPORTANT:: This allows the entry of hostnames, for example foo.cisco.com, instead 
IMPORTANT:: of IP addresses like 1.100.10.205 for application configuration.  In order 
IMPORTANT:: to set up DNS you must know the IP address of at least one of your
IMPORTANT:: DNS Servers.  
 
   
Would you like to use DNS (y,n)?y
 
   
Enter IP Address of the Primary DNS Server
  (IP address): 180.180.180.50
Found server 180.180.180.50
 
   
Enter IP Address of the Secondary DNS Server (other than Primary)
  (IP address, or enter to bypass): 
 
   
E
 
   
Enter Fully Qualified Domain Name(FQDN: e.g. myhost.mydomain.com) 
or IP address of the Primary NTP server
  (FQDN or IP address, or enter for 10.50.30.1): 10.50.10.1
Found server 10.50.10.1
 
   
Enter Fully Qualified Domain Name(FQDN: e.g. myhost.mydomain.com) 
or IP address of the Secondary NTP Server
  (FQDN or IP address, or enter to bypass): 
 
   
Please identify a location so that time zone rules can be set correctly.
Please select a continent or ocean.
1) Africa            4) Arctic Ocean     7) Australia       10) Pacific Ocean
2) Americas          5) Asia             8) Europe
3) Antarctica        6) Atlantic Ocean   9) Indian Ocean
#? 2
Please select a country.
 1) Anguilla                 27) Honduras
 2) Antigua & Barbuda        28) Jamaica
 3) Argentina                29) Martinique
 4) Aruba                    30) Mexico
 5) Bahamas                  31) Montserrat
 6) Barbados                 32) Netherlands Antilles
 7) Belize                   33) Nicaragua
 8) Bolivia                  34) Panama
 9) Brazil                   35) Paraguay
10) Canada                   36) Peru
11) Cayman Islands           37) Puerto Rico
12) Chile                    38) St Barthelemy
13) Colombia                 39) St Kitts & Nevis
14) Costa Rica               40) St Lucia
15) Cuba                     41) St Martin (French part)
16) Dominica                 42) St Pierre & Miquelon
17) Dominican Republic       43) St Vincent
18) Ecuador                  44) Suriname
19) El Salvador              45) Trinidad & Tobago
20) French Guiana            46) Turks & Caicos Is
21) Greenland                47) United States
22) Grenada                  48) Uruguay
23) Guadeloupe               49) Venezuela
24) Guatemala                50) Virgin Islands (UK)
25) Guyana                   51) Virgin Islands (US)
26) Haiti
#? 47
Please select one of the following time zone regions.
 1) Eastern Time
 2) Eastern Time - Michigan - most locations
 3) Eastern Time - Kentucky - Louisville area
 4) Eastern Time - Kentucky - Wayne County
 5) Eastern Time - Indiana - most locations
 6) Eastern Time - Indiana - Daviess, Dubois, Knox & Martin Counties
 7) Eastern Time - Indiana - Pulaski County
 8) Eastern Time - Indiana - Crawford County
 9) Eastern Time - Indiana - Pike County
10) Eastern Time - Indiana - Switzerland County
11) Central Time
12) Central Time - Indiana - Perry County
13) Central Time - Indiana - Starke County
14) Central Time - Michigan - Dickinson, Gogebic, Iron & Menominee Counties
15) Central Time - North Dakota - Oliver County
16) Central Time - North Dakota - Morton County (except Mandan area)
17) Mountain Time
18) Mountain Time - south Idaho & east Oregon
19) Mountain Time - Navajo
20) Mountain Standard Time - Arizona
21) Pacific Time
22) Alaska Time
23) Alaska Time - Alaska panhandle
24) Alaska Time - Alaska panhandle neck
25) Alaska Time - west Alaska
26) Aleutian Islands
27) Hawaii
#? 21
 
   
The following information has been given:
 
   
        United States
        Pacific Time
 
   
Therefore TZ='America/Los_Angeles' will be used.
Is the above information OK?
1) Yes
2) No
#? 1
 
   
Local time is now:      Mon Apr  5 11:20:17 PDT 2010.
Universal Time is now:  Mon Apr  5 18:20:17 UTC 2010.
executing app post_install
executing app post_install done
Configuring the system. Please wait...
Changing owners and file permissions.
Tightening file permissions ...
Change owners and permissions complete.
Creating Postgres database .... done.
INIT: Switching to runlevel: 4
INIT: Sending processes the TERM signal
==> Starting CDP
STARTED: cli_server.sh
STARTED: ntp_startup.sh
STARTED: LDAP_startup.sh
STARTED: SQL_startup.sh
STARTED: dwnldr_startup.sh
STARTED: HTTP_startup.sh
STARTED: probe
STARTED: fndn_udins_wrapper
STARTED: superthread_startup.sh
STARTED: /bin/products/umg/umg_startup.sh
 
   
 Waiting 49 ...
 
   
IMPORTANT::                                                     
IMPORTANT::        Administrator Account Creation               
IMPORTANT::                                                     
IMPORTANT:: Create an administrator account.                    
IMPORTANT:: With this account, you can log in to the            
IMPORTANT:: Cisco Unified SIP Proxy
IMPORTANT:: GUI and run the initialization wizard.              
IMPORTANT::                                                     
 
   
Enter administrator user ID:
  (user ID): test
tesEnter password for test:
  (password): 
Confirm password for test by reentering it:
  (password): 
 
   
SYSTEM ONLINE
 
   
se-10-50-30-125# show software versions 
Cisco Unified SIP Proxy version (8.5.1)
Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2010 by Cisco 
Systems, Inc.
 
   
se-10-50-30-125# show sof
se-10-50-30-125# show software p
se-10-50-30-125# show software packages 
 
   
Installed Packages:
 
   
 - Installer (Installer application) (8.5.1)
 - CUSP (Cisco Unified SIP Proxy) (8.5.1)
 - Bootloader (Primary) (Service Engine Bootloader) (2.1.23)
 - Infrastructure (Service Engine Infrastructure) (2.3.2.2)
 - Global (Global manifest) (8.5.1)
 - Bootloader (Secondary) (Service Engine Bootloader) (2.1.23.0)
 - Core (Service Engine OS Core) (2.4.0.4)
 - GPL Infrastructure (Service Engine GPL Infrastructure) (2.2.1.1)
SE-Module>