Este documento explica o procedimento para promover o software do sistema do Cisco Unity Express da liberação 1.1.x para liberar 2.0 ou 2.1. Os destaques importantes discutidos neste documento são:
Um upgrade de software do Cisco Unity Express apaga a configuração existente e os dados. Execute um apoio na configuração atual e dados no Cisco Unity Express se os dados existentes precisam de ser restaurados após a elevação.
No Cisco Unity Express libere 2.0 e o 2.1, licenças separadas é exigido para o CallManager da Cisco e o CallManager da Cisco expressos.
Você pode promover da liberação 2.0 do Cisco Unity Express ao 2.1 (ou da liberação 2.0/2.1 do Cisco Unity Express a uma versão mais atrasada). Contudo, os suportes de software um método novo que permita que a transferência ocorra quando o sistema ainda se operar.
Uma elevação da liberação 1.0.2 do Cisco Unity Express diretamente para liberar 2.0 foi testada. As instruções são as mesmas, salvo que as necessidades da imagem do Boot Loader primeiramente ser promovido a 1.0.17. Refira o upgrade de software expresso do Unity da liberação 1.0.2 a 1.1.1 para mais informação.
Um FTP e um servidor TFTP devem ser disponíveis e alcançáveis pelo Cisco Unity Express. O servidor FTP deve apoiar o FTP passivo (PASV). O servidor TFTP deve apoiar os tamanhos do arquivo maiores do que o 16 MB (alguns servidores TFTP mais velhos apoiam somente tamanhos do arquivo até o 16 MB).
Embora todo o servidor FTP que cumprir estas exigências seja esperado se operar corretamente, há algum Produtos específico que Cisco usou com sucesso:
Para o sistema operacional de Microsoft Windows:
Servidor FTP de FileZilla
GuildFTPd
Servidor FTP serviço-U
Servidor FTP de Microsoft IIS
Para o sistema operacional de Linux:
Servidor ProFTPD
PureFTPd
WU-FTPD
Note: Cisco não endossa nem apoia qualquer um Produtos do servidor FTP. Esta é somente uma lista de algum do software Cisco usou-se no passado que provou bem sucedido.
O módulo do Cisco Unity Express precisa de estar na liberação 1.1.1 ou 1.1.2. Especificamente, a versão do Boot Loader deve estar na liberação 1.0.17 (das saídas de versão da mostra do Cisco Unity Express).
Se você recebe este erro quando você incorpora o comando limpo do pkgfilename do download do software a fim promover o Cisco Unity Express, é porque a versão não apoia um download do software nem o instala:
NameError: global name 'nativeSysdbException' is not defined[15261 refs]
Nesta encenação, você precisa de usar o bootloader a fim promover.
A informação neste documento é baseada no produto do Cisco Unity Express que é promovido.
A informação neste documento foi criada dos dispositivos em um ambiente de laboratório específico com o Cisco Unity Express 2.0. Para o 2.1 do Cisco Unity Express (liberado uma vez), os números de versão no instalador e alterações de sistema. Contudo, o processo permanece o mesmo. Todos os dispositivos utilizados neste documento foram iniciados com uma configuração (padrão) inicial. Se a sua rede estiver ativa, certifique-se de que entende o impacto potencial de qualquer comando.
Consulte as Convenções de Dicas Técnicas da Cisco para obter mais informações sobre convenções de documentos.
O FTP e os servidores TFTP devem estabelecer-se para o download do software. Certifique-se que você nota o endereço IP de Um ou Mais Servidores Cisco ICM NT de cada um destes server. O servidor FTP deve apoiar o FTP passivo (PASV). O servidor TFTP deve apoiar os tamanhos do arquivo maiores do que o 16 MB (alguns servidores TFTP mais velhos apoiam somente tamanhos do arquivo até o 16 MB).
Assegure-se de que seja possível sibilar o módulo do Cisco Unity Express do TFTP e dos servidores FTP.
Um server do Domain Name System (DNS) é opcional para a iniciação. Se o DNS é desejado, instale e ative um servidor DNS no PC ou no server antes que você continue.
O upgrade de software da liberação 1.1.1 do Cisco Unity Express envolve três atividades de carga do software:
Carregue o Boot Loader novo.
Carregue a licença nova apropriada.
Carregue o software do Cisco Unity Express.
Conclua estes passos:
Transfira o software da liberação 2.0 do Cisco Unity Express e a licença apropriada do cisco.com.
Note: O CallManager da Cisco e o CallManager da Cisco expressos exigem licenças diferentes.
Coloque o arquivo de instalação cue-installer.2.0.1 (ou cue-installer.2.1.1) no servidor TFTP.
Coloque estes arquivos no servidor FTP:
cue-vm.2.0.1.pkg (o arquivo de aplicativo principal)
cue-vm-full.2.0.1.prt1
cue-vm-lang-pack.2.0.1.pkg
Um destes arquivos de idioma (baseados em que língua você quer ter como o idioma de sistema):
cue-vm-en_US-lang-pack.2.0.1.prt1 (inglês dos EUA)
cue-vm-de_DE-lang-pack.2.0.1.prt1 (alemão)
cue-vm-es_ES-lang-pack.2.0.1.prt1 (espanhol da europa)
cue-vm-fr_FR-lang-pack.2.0.1.prt1 (Francês Europeu)
Cue-vm-installer.2.0.1.prt1 (opcional) - este arquivo é o instalador on-line que pode ser usado aos arquivos da licença de upgrade e imagens da transferência o software 2.0 é carregada uma vez. Você não precisa este arquivo a fim promover o Cisco Unity Express para liberar 2.0/2.1. Contudo, pode ser útil para as elevações futuras. Se você planeia usar este mesmo servidor FTP, põe-no sobre o server.
(Opcional) armazene o arquivo de licença apropriado no servidor FTP. Se o sistema já tem o arquivo de licença correto na versão anterior, não precisa de ser aplicado outra vez. Se a licença é promovida, a seguir o arquivo novo precisa de ser colocado no servidor FTP assim que pode ser promovido mais tarde. É sempre uma boa prática ter o arquivo de licença correto no servidor FTP para propósitos de backup. Isto é caso que o módulo inteiro do Cisco Unity Express precisa de ser substituído a dada altura do tempo. Os arquivos de licença possíveis são:
Note: Não todos estes arquivos são apropriados para cada plataforma de hardware do Cisco Unity Express.
cue-vm-license_100mbx_ccm_2.0.1.pkg
cue-vm-license_100mbx_cme_2.0.1.pkg
cue-vm-license_12mbx_ccm_2.0.1.pkg
cue-vm-license_12mbx_cme_2.0.1.pkg
cue-vm-license_25mbx_ccm_2.0.1.pkg
cue-vm-license_25mbx_cme_2.0.1.pkg
cue-vm-license_50mbx_ccm_2.0.1.pkg
cue-vm-license_50mbx_cme_2.0.1.pkg
Assegure-se de que o TFTP e os servidores FTP estejam em serviço. No caso de um PC, assegure-se de que os programas TFTP e FTP no PC estejam ativados.
Use o ferramenta comando-linha do cliente de TFTP de Microsoft Windows a fim testar o servidor TFTP. Por exemplo:
O servidor FTP pode ser testado similarmente. Em um navegador que apoie FTP (internet explorer, Firefox, e assim por diante), põe na URL que você planeia usar junto com o nome de usuário e senha. Por exemplo, ftp://user:password@14.80.227.128/2.0.1/. Isto significa que você está tentando alcançar o host 14.80.227.128 no diretório 2.0.1 usando o username “usuário” com senha “senha”. Todos os arquivos necessários na listagem de diretórios podem ser vistos e você pode transferir cada um. Isto não testa todos os aspectos do processo FTP, mas testa para os problemas mais comuns.
Estabeleça uma conexão (através do telnet ou diretamente através do console) ao roteador do Cisco IOS que contém o módulo do Cisco Unity Express. De, conecta ao módulo do Cisco Unity Express emitindo o comando service-module service-engine <slot/0> session. Para o Cisco Unity Express AIM, o número de slot é 0. por exemplo:
[user1-mac:~] root% telnet 14.80.227.140 Trying 14.80.227.140... Connected to 14.80.227.140. Escape character is '^]'. vnt-3660-41c>enable Password: vnt-3660-41c#show ip interface brief Interface IP-Address OK? Method Status Protocol FastEthernet0/0 14.80.227.140 YES NVRAM up up Service-Engine5/0 14.80.227.140 YES TFTP up up vnt-3660-41c#service-module service-Engine 5/0 session Trying 14.80.227.140, 2161 ... % Connection refused by remote host vnt-3660-41c#clear line 161 [confirm] [OK] vnt-3660-41c#service-module service-Engine 5/0 session Trying 14.80.227.140, 2161 ... cue-3660-41c>
Certifique-se que você nota o endereço IP de Um ou Mais Servidores Cisco ICM NT, a máscara de sub-rede, e o gateway padrão do Cisco Unity Express. Obtenha isto do CLI com os comandos show interfaces e show ip route.
cue-3660-41c>show interfaces FastEthernet 1 is up, line protocol is up Internet address is 14.80.227.141 mask 255.255.255.0 !--- Configured on router. Broadcast address is 14.255.255.255 176 input, 18507 bytes 0 input errors 172 output, 16756 bytes 0 output errors IDE hd0 is up, line protocol is up 3385 reads, 39324672 bytes 0 read errors 2393 write, 23195648 bytes 0 write errors cue-3660-41c>show ip route DEST GATE MASK IFACE 14.80.227.0 0.0.0.0 255.255.255.0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 lo 0.0.0.0 14.80.227.140 0.0.0.0 eth1
Suporte seus dados.
Consulte para executar alternativo e a restauração do Cisco Unity Express com o servidor FTP de Microsoft para obter mais informações sobre de alternativo e da restauração. Você pode igualmente referir os guias alternativos e da restauração na documentação regular do Cisco Unity Express, tal como a suportação e a restauração de dados.
Depois que o backup terminou com sucesso, recarregue o Cisco Unity Express NM emitindo o comando reload.
Quando você é alertado satisfazer incorpore o “***” para mudar a configuração de inicialização, incorporam o ***.
Isto permite que o Cisco Unity Express entre no modo Boot Loader.
Incorpore a configuração na alerta do loader> da bota do Mecanismo de serviços.
Incorpore estes detalhes para as várias alertas mostradas na saída da configuração.
O endereço IP de Um ou Mais Servidores Cisco ICM NT do Cisco Unity Express
A máscara de sub-rede do Cisco Unity Express
Endereço de servidor de TFTP
O gateway padrão do Cisco Unity Express
A interface Ethernet é interna. Para a imagem do auxiliar do padrão, incorpore cue-installer.2.0.1. Assegure-se de que a bota do padrão seja sempre disco, o Boot Loader do padrão está sempre preliminar, e a interface Ethernet está ajustada sempre a interno.
ServicesEngine boot-loader>config IP Address [14.80.227.141] > 14.80.227.141 Subnet mask [255.255.255.0] > 255.255.255.0 TFTP server [14.80.227.128] > 14.80.227.128 Gateway [14.80.227.140] > 14.80.227.140 Default Helper-file [cue-installer.2.0.1] > cue-installer.2.0.1 Ethernet interface [internal] > internal Default Boot [disk] > disk Default bootloader [primary|secondary] [primary] > primary Updating flash with bootloader configuration
O sistema redige a informação no flash, e a alerta do loader> da bota do Mecanismo de serviços aparece outra vez.
Conclua estes passos:
Inscreva o auxiliar de boot da alerta do loader> da bota do Mecanismo de serviços.
O Cisco Unity Express carreg a imagem do auxiliar do servidor TFTP.
O sistema carrega agora o pacote do instalador do servidor TFTP e botas dele.
No fim do processo de boot, este menu é apresentado:
Welcome to Cisco Systems Service Engine Helper Software Please select from the following 1 Install software 2 Reload module (Type '?' at any time for help)
Incorpore 1 a fim instalar o software novo.
O nome do pacote, o server URL, e o nome de usuário de FTP/senha são exigidos seguiram por uma confirmação:
Package name: cue-vm.2.0.1.pkg Server url: ftp://14.80.227.128/2.0.1 Username: jdoe Password: WARNING:: Software installation will clear disk contents Continue [n]? y Downloading cue-vm.2.0.1.pkg Bytes downloaded : 1448 Validating package signature ... done Downloading cue-vm-lang-pack.2.0.1.pkg Bytes downloaded : 147456 Validating package signature ... done
Note: Nestas saídas de exemplo, o sistema FTP a 14.80.227.128, entra como o usuário “jdoe” com a senha especificada, manobras ao diretório 2.0.1, e recupera o arquivo "cue-vm.2.0.1.pkg". Deste mesmo diretório, o arquivo "cue-vm-lang-pack.2.0.1.pkg" é recuperado igualmente. Se esta etapa falha por qualquer razão, certifique-se de que estes arquivos ambos existem no trajeto especificado e de que o usuário especificado FTP tem as permissões correta transferir aqueles arquivos.
Um menu de idioma é apresentado. Neste exemplo, 4 (inglês dos EUA) são selecionados. Somente uma língua é possível. Depois que a língua está selecionada (notável pelo * ao lado dele), pressione x a fim terminar.
Language Selection Menu: # Selected SKU Language Name ----------------------------------------------------------------- 1 FRA CUE Voicemail European French (2.0.1) 2 ESP CUE Voicemail European Spanish (2.0.1) 3 DEU CUE Voicemail German (2.0.1) 4 ENG CUE Voicemail US English (2.0.1) Available commands are: # - enter the number for the language to select one r # - remove the language for given # i # - more information about the language for given # x - Done with language selection > 4 Language Selection Menu: # Selected SKU Language Name ----------------------------------------------------------------- 1 FRA CUE Voicemail European French (2.0.1) 2 ESP CUE Voicemail European Spanish (2.0.1) 3 DEU CUE Voicemail German (2.0.1) 4 * ENG CUE Voicemail US English (2.0.1) Available commands are: # - enter the number for the language to select one r # - remove the language for given # i # - more information about the language for given # x - Done with language selection > x
Note: Do mesmos diretório de FTP e trajeto, os arquivos chamados cue-vm-full.2.0.1.prt1, e o cue-vm-en_US-lang-pack.2.0.1.prt1 são transferidos agora. O cue-vm-en_US-lang-pack.2.0.1.prt1 é transferido somente se o inglês dos EUA é selecionado nesta etapa. Outras línguas têm blocos diferentes da língua.
O sistema termina a instalação, repartições (não pressione a combinação do *** neste tempo), e as corridas do script de instalação do cargo.
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)? y Are you sure (y,n)? y
Escolha mesmo se restaurar a configuração existente.
Esta não é uma opção se uma configuração nunca salvar no sistema. Na maioria dos casos, quando uma elevação é feita, o objetivo é ter a configuração e os dados o mesmos como era antes da elevação. Neste caso, é levemente mais rápido restaurar a configuração salva. Esta configuração salva é somente a configuração running (visível do comando show run) em um sistema. Não inclui nenhuns cumprimentos, nomes falados, mensagens, e assim por diante. Aqueles ainda têm que ser restaurados. Contudo, contém o servidor DNS, o servidor de NTP, e a informação da zona de hora (fuso horário) que de outra maneira necessidades de ser entrado manualmente.
IMPORTANT:: IMPORTANT:: A Cisco Unity Express configuration has been found in flash. IMPORTANT:: You can choose to restore this configuration into the IMPORTANT:: current image. IMPORTANT:: IMPORTANT:: A stored configuration contains some of the data from a IMPORTANT:: previous installation, but not as much as a backup. For IMPORTANT:: example: voice messages, user passwords, user PINs, and IMPORTANT:: auto attendant scripts are included in a backup, but are IMPORTANT:: not saved with the configuration. 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 are going to restore a backup from a previous IMPORTANT:: installation, you should not 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) y Are you sure (y,n)? y
Se “n” é selecionado na etapa 7, você está alertado para o servidor DNS, o servidor de NTP, e a zona de hora (fuso horário). Uma vez que terminado, o sistema termina o cargo instala começando acima de todos seus aplicativos. Isso pode demorar vários minutos. Na extremidade, o usuário é alertado criar um usuário do administrador - identificação e senha:
Configuring the system. Please wait... Changing owners and file permissions. Change owners and permissions complete. INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal STARTED: cli_server.sh STARTED: ntp_startup.sh STARTED: LDAP_startup.sh STARTED: superthread_startup.sh STARTED: SQL_startup.sh STARTED: HTTP_startup.sh STARTED: ${ROOT}/usr/wfavvid/run STARTED: probe STARTED: dwnldr_startup.sh waiting 160 ... IMPORTANT:: IMPORTANT:: Administrator Account Creation IMPORTANT:: IMPORTANT:: Create an administrator account. With this account, IMPORTANT:: you can log in to the Cisco Unity Express GUI and IMPORTANT:: run the initialization wizard. IMPORTANT:: Enter administrator user ID: (user ID): administrator Enter password for administrator: (password): Confirm password for administrator by reentering it: (password): cue-3660-41c>
Importante: Para os sistemas que são integrados com CallManager da Cisco, o sistema tenta agora registrar-se com o CallManager da Cisco.
Com Cisco Unity Express 2.0 e mais atrasado, se durante o processo de registro o Cisco Unity Express detecta uma versão de JTAPI a não ser o que está executando atualmente, instala bibliotecas JTAPI compatível e repartições. Por exemplo, o 2.1 da liberação do Cisco Unity Express envia com as bibliotecas JTAPI compatíveis com CallManager da Cisco 4.1. A primeira vez que um sistema do 2.1 do Cisco Unity Express se registra com um CallManager da Cisco a não ser os 4.1 que apoia (como 4.0 ou 3.3), carrega as bibliotecas novas e recarrega-as automaticamente. Se o CallManager da Cisco é promovido de uma versão à outro, a mesma coisa acontece. Isso é normal. Reveja os Release Note para assegurar a compatibilidade apropriada do Cisco Unity Express e do CallManager da Cisco. O Cisco Unity Express 2.0 (por exemplo) não apoia o CallManager da Cisco 4.1. Consequentemente, não trabalha.
Inscreva o comando show software versions a fim verificar o software do sistema:
cue-3660-41c>show software versions Installed Packages: - Bootloader (Primary) 1.0.17 - Global 2.0.1 - Voice Mail 2.0.1 - Bootloader (Secondary) 2.0.1 - Core 2.0.1 - Installer 2.0.1 - Auto Attendant 2.0.1 Installed Languages: - US English 2.0.1
Note: Você não tem que ser referido sobre a diferença nas versões preliminares e secundárias do Boot Loader. Isso é normal.
Verifique a licença do software aplicada. Especificamente, o tipo de integração (CallManager da Cisco expresso ou CallManager da Cisco) e o número de portas e de caixas postais:
cue-3660-41c>show software licenses Core: - application mode: CCME - total usable system ports: 4 Voicemail/Auto Attendant: - max system mailbox capacity time: 6000 - max general delivery mailboxes: 5 - max personal mailboxes: 12 Languages: - max installed languages: 1 - max enabled languages: 1 cue-3660-41c>
Execute a restauração. Se você não restaurou a configuração precedente (ou algo mudada) então você precisa possivelmente de mudar a informação do servidor de backup. Por exemplo:
cue-3660-41c>offline !!!WARNING!!!: Putting the system offline will terminate all active calls. Do you wish to continue[n]? : y cue-3660-41c(offline)>restore id 1 category all Restore progress: 417227 bytes Restore Complete. Check Restore history for detailed information. cue-3660-41c(offline)>show backup history #Start Operation Category: Configuration Backup Server: ftp://172.18.106.10/cue/41c Operation: Restore Backupid: 1 Restoreid: 1 Date: Mon Jan 10 15:01:02 EST 2005 Result: Success Reason: #End Operation #Start Operation Category: Data Backup Server: ftp://172.18.106.10/cue/41c Operation: Restore Backupid: 1 Restoreid: 1 Date: Mon Jan 10 15:01:04 EST 2005 Result: Success Reason: #End Operationcue-3660-41c(offline)>reload cue-3660-41c(offline)> MONITOR SHUTDOWN...
Note: A restauração real ID (1 neste exemplo) é específica a seu grupo do backup. Examine o arquivo de history.log a fim obter o ID o mais recente.
Consulte para executar alternativo e a restauração do Cisco Unity Express com o servidor FTP de Microsoft para obter mais informações sobre de alternativo e da restauração. Você pode igualmente referir os guias alternativos e da restauração na documentação regular, tal como a suportação e a restauração de dados.
Aponte seu navegador da Web a http:// < ao endereço IP de Um ou Mais Servidores Cisco ICM NT do CUE>/a fim registrar no página da web do Cisco Unity Express. Entre com a conta de administrador criada em etapa 8. Se uma restauração foi feita previamente, você não precisa de mudar nenhuma informação. Na extremidade do assistente, você é registrado para fora.
Este é o resultado completo para promover um Módulo de rede Cisco Unity Express da liberação 1.1.2 do Cisco Unity Express à liberação 2.0.1 do Cisco Unity Express:
cue-3660-41c>reload Are you sure you want to reload? Doing a reload will cause any unsaved configuration data to be lost. Continue[y]? : y cue-3660-41c> MONITOR SHUTDOWN... EXITED: probe exit status 0 EXITED: LDAP_startup.sh exit status 0 EXITED: HTTP_startup.sh exit status 0 MONITOR EXIT... INIT: Sending processes the TERM signal Remounting device 03:01 ... OK Done. Restarting system. Initializing memory. Please wait. 256 MB SDRAM detected BIOS Version: SM 02.00 BIOS Build date: 09/17/02 System Now Booting ... Booting from flash..., please wait. [BOOT-ASM] 7Found Intel 82371AB at 0x00000000 ROM address 0x00000000 Please enter '***' to change boot configuration: ***Probing...[EEPRO100]Found I ntel EtherExpressPro100 at 0x00000000 ROM address 0x00000000 Found Intel EtherExpressPro100 at 0x00000000 ROM address 0x00000000 Ethernet addr: 00:11:20:F2:04:AF equalizer val: 16 ServicesEngine Bootloader Version : 1.0.17 ServicesEngine boot-loader>config IP Address [14.80.227.141] > Subnet mask [255.255.255.0] > TFTP server [14.80.227.128] > Gateway [14.80.227.140] > Default Helper-file [cue-installer.2.0.1] > Ethernet interface [internal] > Default Boot [disk] > Default bootloader [primary|secondary] [primary] > ServicesEngine boot-loader> ServicesEngine boot-loader> boot helper Probing...[EEPRO100]Found Intel EtherExpressPro100 at 0x00000000 ROM address 0x 00000000 Found Intel EtherExpressPro100 at 0x00000000 ROM address 0x00000000 Ethernet addr: 00:11:20:F2:04:AF equalizer val: 16 Me: 14.80.227.141, Server: 14.80.227.128, Gateway: 14.80.227.140 Loading cue-installer.2.0.1 Dbg: Final image size: 8692059 Debug: bl_sz: 115296 reading key: 0 reading key: 1 reading key: 2 reading key: 3 reading key: 4 reading key: 5 in verifysignature_md5, MD5 hash generated now, str format:hexmd5:a133f91b2adf8 818ce5f26ad0cf49594 Verifying signature now... calling RSA decrypt now mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1 316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188 RSA decrypt returned:33 verifysignature_md5, Orig MD5 hash generated during encryption:a133f91b2adf8818 ce5f26ad0cf49594 Image signature verified successfully Aesop Helper: system image header: v=2, b=942206, i=7747337 Network boot: moving 3072 code bytes to 0x90000 .... Network boot: invoking kernel now [BOOT-PHASE2]: booting kernel Linux version 2.4.24 (bld_adm@bld-system) (gcc version 2.95.3 20010315 (release)) #1 Wed Dec 1 10:15:11 PST 2004 Platform: nm setup.c: handling flash window at [15MB..16MB] setup.c: handling kernel log buf at [245.5MB] setup.c: handling trace buf at [246MB] BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0800 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000000f00000 (usable) BIOS-e820: 0000000000f00000 - 0000000001000000 (reserved) BIOS-e820: 0000000001000000 - 000000000f580000 (usable) BIOS-e820: 000000000f580000 - 000000000f600000 (reserved) BIOS-e820: 000000000f600000 - 0000000010000000 (reserved) BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) 245MB LOWMEM available. On node 0 totalpages: 62848 zone(0): 4096 pages. zone(1): 58752 pages. zone(2): 0 pages. DMI not present. Kernel command line: root=/dev/ram ramdisk_size=200000 ramdisk_start=0x6000000 console=ttyS0,9600n8 plat=nm Initializing CPU#0 Detected 498.680 MHz processor. Calibrating delay loop... 996.14 BogoMIPS Memory: 237488k/251392k available (1207k kernel code, 12492k reserved, 690k data, 92k init, 0k highmem) kdb version 4.3 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved in atrace_init log_head: h: 0, t: 10069583, l: 0, w: 0, s: 10484672 Using existing trace log log_head: h: 0, t: 10069583, l: 0, w: 0, s: 10484672 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU serial number disabled. CPU: Intel Pentium III (Coppermine) stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xeab9c, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd kinoded started VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: devfs_debug: 0x0 devfs: boot_options: 0x1 Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Cisco ContentEngine Flash Driver Version 0.02 RAMDISK driver initialized: 16 RAM disks of 200000K size 1024 blocksize eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others eth0: PCI device 8086:1229, 00:11:20:F2:04:AE, IRQ 9. Receiver lock-up bug exists -- enabling work-around. Board assembly 668081-002, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Receiver lock-up workaround activated. eth1: PCI device 8086:1229, 00:11:20:F2:04:AF, IRQ 10. Receiver lock-up bug exists -- enabling work-around. Board assembly 668081-002, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Receiver lock-up workaround activated. Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX4: IDE controller at PCI slot 00:07.1 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio hda: C/H/S=50127/232/176 from BIOS ignored hdb: C/H/S=0/0/0 from BIOS ignored hda: IC25N020ATMR04-0, ATA DISK drive blk: queue c031e040, I/O limit 4095Mb (mask 0xffffffff) ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: attached ide-disk driver. hda: host protected area => 1 hda: 39070080 sectors (20004 MB) w/1740KiB Cache, CHS=2432/255/63, UDMA(33) init unit number == 0 Partition check: /dev/ide/host0/bus0/target0/lun0: p1 device capacity not supported Flash capacity == 39070080 init unit number == 1 IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 16384) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 100663296 Freeing initrd memory: 7565k freed VFS: Mounted root (ext2 filesystem) readonly. Mounted devfs on /dev Init drive control Freeing unused kernel memory: 92k freed INIT: version 2.84 booting Started device management daemon v1.3.25 for /dev /dev/root: clean, 924/5984 files, 21644/28248 blocks FILESYSTEM CLEAN Remounting the root filesystem read-write... kernel.sem = 28672 32000 32 128 Welcome to Cisco Service Engine Wed Jan 1 00:00:00 UTC 2003 ********** rc.aesop **************** ==> eth1 exists, we must be running on a Network Module ==> eth1 exists, we must be running on a Network Module Router communications servers initializing...complete. IOS IP Address Registration complete. Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 14.80.227.0 * 255.255.255.0 U 0 0 0 eth1 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 14.80.227.140 0.0.0.0 UG 0 0 0 eth1 Size of buff is: 65536 65536 bytes written Reading License... /tmp/license/voicemail_lic.sig done [13311 refs] Reading Limits... Processing: /lib/python2.3/startup/limits.xml done [9662 refs] ModuleType = nm INIT: Entering runlevel: 2 ********** rc.post_install **************** Changing owners and file permissions. Change owners and permissions complete. INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal STARTED: dwnldr_startup.sh Welcome to Cisco Systems Service Engine Helper Software Please select from the following 1 Install software 2 Reload module (Type '?' at any time for help) Choice: 1 Package name: cue-vm.2.0.1.pkg Server url: ftp://14.80.227.128/2.0.1 Username: cse Password: WARNING:: Software installation will clear disk contents Continue [n]? y Downloading cue-vm.2.0.1.pkg Bytes downloaded : 1448 Validating package signature ... done Downloading cue-vm-lang-pack.2.0.1.pkg Bytes downloaded : 147456 Validating package signature ... done Language Selection Menu: # Selected SKU Language Name ----------------------------------------------------------------- 1 FRA CUE Voicemail European French (2.0.1) 2 ESP CUE Voicemail European Spanish (2.0.1) 3 DEU CUE Voicemail German (2.0.1) 4 ENG CUE Voicemail US English (2.0.1) Available commands are: # - enter the number for the language to select one r # - remove the language for given # i # - more information about the language for given # x - Done with language selection > 4 Language Selection Menu: # Selected SKU Language Name ----------------------------------------------------------------- 1 FRA CUE Voicemail European French (2.0.1) 2 ESP CUE Voicemail European Spanish (2.0.1) 3 DEU CUE Voicemail German (2.0.1) 4 * ENG CUE Voicemail US English (2.0.1) Available commands are: # - enter the number for the language to select one r # - remove the language for given # i # - more information about the language for given # x - Done with language selection > x type: bootloader cleaning fs prepfs.sh: nm reiser /mnt clean umount: /dev/hda1: not mounted check_partition_count: 0 check_partition_flag: 1 The number of cylinders for this disk is set to 2432. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): Partition number (1-4): Command (m for help): Command action e extended p primary partition (1-4) Partition number (1-4): First cylinder (1-2432, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-2432, default 2432): Using default value 2432 Command (m for help): The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. <-------------mkreiserfs, 2003-------------> reiserfsprogs 3.6.8 mkreiserfs: Guessing about desired format.. mkreiserfs: Kernel 2.4.24 is running. Initializing journal - 0%....20%....40%....60%....80%....100% Starting payload download File : cue-vm-en_US-lang-pack.2.0.1.prt1 Bytes : 18612224 Validating payloads match registered checksums... - cue-vm-full.2.0.1.prt1 ...................................verified - cue-vm-en_US-lang-pack.2.0.1.prt1 ...................verified No installed manifests found. Clearing previous downgrade files ... complete. Performing Hot install ...starting_phase: install-files.sh /mnt/dwnld/.hot_work_order install_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 0 __CUE_PRIMARY_BOOTLOADER__ gz add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 2 /mnt sw/installed/manifest/bootloader_prim_manifest.sig none install_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 1 __CUE_SECONDARY_BOOTLOADER__ gz add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 3 /mnt sw/installed/manifest/bootloader_sec_manifest.sig none complete. wo_path /mnt/dwnld/.work_order sc /bin/installer_shutdown.sh /mnt/dwnld/.work_order Shutting down processes ... Please wait . . [20219 refs] Process shutdown complete. starting_phase: install-files.sh /mnt/dwnld/.work_order Fri Dec 3 19:40:02 UTC 2004 Remove /mnt// root directory removing install_tmp removing sw add_file /mnt/dwnld/pkgdata/cue-vm-en_US-lang-pack.2.0.1.prt1 1 /mnt tgz add_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 5 /mnt tgz add_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 7 /mnt tgz add_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 9 /mnt tgz add_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 11 /mnt tgz extract_mv_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 3 /mnt lib tgz extract_mv_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 3 /mnt bin tgz extract_mv_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 3 /mnt etc tgz extract_mv_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 3 /mnt sbin tgz install_file P1x9waI0kGGBGZbTCw/mKEgwSbrtCvlAKujkzbIOKj6Xfsvb5HfXn9LHJe8uQU nZXAWch= __BZ_SIGNATURE__ bzsig ldbl -m nm -t bzsig P1x9waI0kGGBGZbTCw/mKEgwSbrtCvlAKujkzbIOKj6XLdvHK+ 7PdNpMNYD8w= add_file /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 3 /mnt bzImage tgz add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 2 /mnt sw/installed/manifest/bootloader_prim_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 6 /mnt sw/installed/manifest/infrastructure_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 1 /mnt sw/installed/manifest/global_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 7 /mnt sw/installed/manifest/telephony_infrastructure_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 8 /mnt sw/installed/manifest/voicemail_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 3 /mnt sw/installed/manifest/bootloader_sec_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 9 /mnt sw/installed/manifest/installer_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 4 /mnt sw/installed/manifest/oscore_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg 5 /mnt sw/installed/manifest/gpl_infrastructure_manifest.sig none add_file /mnt/dwnld/pkgdata/cue-vm-lang-pack.2.0.1.pkg 1 /mnt sw/installed/manifest/en_US_lang_manifest.sig none Remove /mnt/dwnld/pkgdata/cue-vm.2.0.1.pkg Remove /mnt/dwnld/pkgdata/cue-vm-lang-pack.2.0.1.pkg Remove /mnt/dwnld/pkgdata/cue-vm-full.2.0.1.prt1 Remove /mnt/dwnld/pkgdata/cue-vm-en_US-lang-pack.2.0.1.prt1 Performing final moves mnt_dir: /mnt INIT: Sending processes the TERM signal Remounting device 03:01 ... OK Remounting device 01:00 ... OK Done. Restarting system. Initializing memory. Please wait. 256 MB SDRAM detected BIOS Version: SM 02.00 BIOS Build date: 09/17/02 System Now Booting ... Booting from flash..., please wait. [BOOT-ASM] 7Found Intel 82371AB at 0x00000000 ROM address 0x00000000 Please enter '***' to change boot configuration: Filesystem type is reiserfs, partition type 0x83 kf: a1 : (hd0,0)/bzImage root=/dev/hda1 ro plat=nm kf: a2 : (hd0,0)/bzImage root=/dev/hda1 ro plat=nm in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=nm in grub_open1: /bzImage root=/dev/hda1 ro plat=nm in grub_open2: /bzImage root=/dev/hda1 ro plat=nm in grub_open3: /bzImage root=/dev/hda1 ro plat=nm 1 in grub_open: (hd0,0)/bzImage root=/dev/hda1 ro plat=nm in grub_open1: /bzImage root=/dev/hda1 ro plat=nm in grub_open2: /bzImage root=/dev/hda1 ro plat=nm in grub_open3: /bzImage root=/dev/hda1 ro plat=nm 1 In verify_kernel_sig Chksum: final image size: 910364 plat: 1 Debug: bl_sz: 115296 After: buf_len: 2048 After KEY_InitMem reading key: 0 reading key: 1 reading key: 2 reading key: 3 reading key: 4 reading key: 5 After karr After 2: buf_len: 2048 sig len : 172 in verifysignature_md5, MD5 hash generated now, str format:hexmd5:ba809dd8cdb3d 54429a98c2b5b2f7c7e Verifying signature now... calling RSA decrypt now mem ptr: 0 704 832 968 1040 1172 1184 1196 1208 1220 1228 1244 1268 1284 1300 1 316 1332 1344 1360 1384 1400 1664 1804 2080 2224 2364 2880 3396 3660 3924 4188 RSA decrypt returned:33 verifysignature_md5, Orig MD5 hash generated during encryption:ba809dd8cdb3d544 29a98c2b5b2f7c7e Kernel signature verified successfully In load_imagea1 In load_imagea2 Dbg ********* filemax/data_len/SECSIZ: 910364/2560/512 [Linux-bzImage, setup=0xa00, size=0xdd81c] kernel_func: kt: 3 in boot func: kt: 3 Linux version 2.4.24 (bld_adm@bld-system) (gcc version 2.95.3 20010315 (release)) #1 Tue Nov 30 23:07:21 PST 2004 Platform: nm setup.c: handling flash window at [15MB..16MB] setup.c: handling kernel log buf at [245.5MB] setup.c: handling trace buf at [246MB] BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0800 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000000f00000 (usable) BIOS-e820: 0000000000f00000 - 0000000001000000 (reserved) BIOS-e820: 0000000001000000 - 000000000f580000 (usable) BIOS-e820: 000000000f580000 - 000000000f600000 (reserved) BIOS-e820: 000000000f600000 - 0000000010000000 (reserved) BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) 245MB LOWMEM available. On node 0 totalpages: 62848 zone(0): 4096 pages. zone(1): 58752 pages. zone(2): 0 pages. DMI not present. Kernel command line: root=/dev/hda1 ro plat=nm Initializing CPU#0 Detected 498.675 MHz processor. Calibrating delay loop... 996.14 BogoMIPS Memory: 245128k/251392k available (1164k kernel code, 4852k reserved, 667k data, 88k init, 0k highmem) kdb version 4.3 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved in atrace_init log_head: h: 0, t: 10069583, l: 0, w: 0, s: 10484672 Using existing trace log log_head: h: 0, t: 10069583, l: 0, w: 0, s: 10484672 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode cache hash table entries: 16384 (order: 5, 131072 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 6, 262144 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K CPU serial number disabled. CPU: Intel Pentium III (Coppermine) stepping 0a Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xeab9c, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd kinoded started VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: devfs_debug: 0x0 devfs: boot_options: 0x1 Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Cisco ContentEngine Flash Driver Version 0.02 eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others eth0: PCI device 8086:1229, 00:11:20:F2:04:AE, IRQ 9. Receiver lock-up bug exists -- enabling work-around. Board assembly 668081-002, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Receiver lock-up workaround activated. eth1: PCI device 8086:1229, 00:11:20:F2:04:AF, IRQ 10. Receiver lock-up bug exists -- enabling work-around. Board assembly 668081-002, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). Receiver lock-up workaround activated. Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX4: IDE controller at PCI slot 00:07.1 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio hda: C/H/S=50127/232/176 from BIOS ignored hdb: C/H/S=0/0/0 from BIOS ignored hda: IC25N020ATMR04-0, ATA DISK drive blk: queue c030c160, I/O limit 4095Mb (mask 0xffffffff) ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: attached ide-disk driver. hda: host protected area => 1 hda: 39070080 sectors (20004 MB) w/1740KiB Cache, CHS=2432/255/63, UDMA(33) init unit number == 0 Partition check: /dev/ide/host0/bus0/target0/lun0: p1 device capacity not supported Flash capacity == 39070080 init unit number == 1 IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 16384) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. reiserfs: found format "3.6" with standard journal reiserfs: using ordered data mode reiserfs: checking transaction log (device ide0(3,1)) ... for (ide0(3,1)) ide0(3,1):Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Mounted devfs on /dev Init drive control Freeing unused kernel memory: 88k freed INIT: version 2.84 booting Started device management daemon v1.3.25 for /dev reiser root fs ... Reiserfs super block in block 16 on 0x301 of format 3.6 with standard journal Blocks (total/free): 4883752/4837151 by 4096 bytes Filesystem is cleanly umounted Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree..finished FILESYSTEM CLEAN Remounting the root filesystem read-write... kernel.sem = 28672 32000 32 128 Welcome to Cisco Service Engine Fri Dec 3 19:40:51 UTC 2004 ********** rc.aesop **************** ==> eth1 exists, we must be running on a Network Module ==> eth1 exists, we must be running on a Network Module Router communications servers initializing...complete. IOS IP Address Registration complete. Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 14.80.227.0 * 255.255.255.0 U 0 0 0 eth1 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 14.80.227.140 0.0.0.0 UG 0 0 0 eth1 Size of buff is: 65536 65536 bytes written Reading License... /tmp/license/voicemail_lic.sig done [13311 refs] Processing: /sw/installed/manifest/gpl_infrastructure_manifest.sig Processing: /sw/installed/manifest/installer_manifest.sig Processing: /sw/installed/manifest/en_US_lang_manifest.sig Processing: /sw/installed/manifest/oscore_manifest.sig Processing: /sw/installed/manifest/telephony_infrastructure_manifest.sig Processing: /sw/installed/manifest/bootloader_prim_manifest.sig Processing: /sw/installed/manifest/bootloader_sec_manifest.sig Processing: /sw/installed/manifest/global_manifest.sig Processing: /sw/installed/manifest/infrastructure_manifest.sig Processing: /sw/installed/manifest/voicemail_manifest.sig Populating internal database ................... complete. [16589 refs] Reading Limits... Processing: /lib/python2.3/startup/limits.xml done [9662 refs] ModuleType = nm INIT: Entering runlevel: 2 ********** rc.post_install **************** 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)? y Are you sure (y,n)? y IMPORTANT:: IMPORTANT:: A Cisco Unity Express configuration has been found in flash. IMPORTANT:: You can choose to restore this configuration into the IMPORTANT:: current image. IMPORTANT:: IMPORTANT:: A stored configuration contains some of the data from a IMPORTANT:: previous installation, but not as much as a backup. For IMPORTANT:: example: voice messages, user passwords, user PINs, and IMPORTANT:: auto attendant scripts are included in a backup, but are IMPORTANT:: not saved with the configuration. 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 are going to restore a backup from a previous IMPORTANT:: installation, you should not 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) y Are you sure (y,n)? y Configuring the system. Please wait... Changing owners and file permissions. Change owners and permissions complete. INIT: Switching to runlevel: 4 INIT: Sending processes the TERM signal STARTED: cli_server.sh STARTED: ntp_startup.sh STARTED: LDAP_startup.sh STARTED: superthread_startup.sh STARTED: SQL_startup.sh STARTED: HTTP_startup.sh STARTED: ${ROOT}/usr/wfavvid/run STARTED: probe STARTED: dwnldr_startup.sh waiting 160 ... IMPORTANT:: IMPORTANT:: Administrator Account Creation IMPORTANT:: IMPORTANT:: Create an administrator account. With this account, IMPORTANT:: you can log in to the Cisco Unity Express GUI and IMPORTANT:: run the initialization wizard. IMPORTANT:: Enter administrator user ID: (user ID): administrator Enter password for administrator: (password): Confirm password for administrator by reentering it: (password): cue-3660-41c>