cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1549
Views
0
Helpful
7
Replies

Cannot access cue on a UC520-16U-4FXO-K9

themizzz21
Level 1
Level 1

Hello,

I had to replace a working UC520W-8U-2BRI-K9 with a new UC520-16U-4FXO-K9.

I backed up cue from old uc and tried to restore it to the new one.

The restoration procedure did not completed successfully.

The system returned something like(i cannot remember exactly):

RESTORE FAILED

RESTORE SCRIPT FAILURE

So i reloaded cue using "service-module integrated-Service-Engine 0/0 reload "

From then on i cannot access cue

I have the following message which never stops:

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

 

UC520W-8U-2BRI-K9:

Cisco UC520W-8U-2BRI-K9 (MPC8358) processor (revision 0x202) with 249856K/12288K bytes of memory.
Processor board ID FCZ121760QR
MPC8358 CPU Rev: Part Number 0x804A, Revision ID 0x20
14 User Licenses
10 FastEthernet interfaces
2 ISDN Basic Rate interfaces
2 terminal lines
4 Voice FXO interfaces
4 Voice FXS interfaces
1 Voice MoH interface
1 802.11 Radio
1 cisco service engine(s)
128K bytes of non-volatile configuration memory.
125440K bytes of ATA CompactFlash (Read/Write)

UC520#service-module integrated-Service-Engine 0/0 status
Service Module is Cisco Integrated-Service-Engine0/0
Service Module supports session via TTY line 2
Service Module is in Steady state
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..
 
Cisco Unity Express 3.0.3
CUE running on UC500


===========================================

UC520-16U-4FXO-K9:

Cisco UC520-16U-4FXO-K9 (MPC8358) processor (revision 0x202) with 235520K/26624K bytes of memory.
Processor board ID FHK114155J3
MPC8358 CPU Rev: Part Number 0x804A, Revision ID 0x20
22 User Licenses
10 FastEthernet interfaces
2 ISDN Basic Rate interfaces
2 terminal lines
1 Virtual Private Network (VPN) Module
4 Voice FXO interfaces
4 Voice FXS interfaces
1 Voice MoH interface
1 cisco service engine(s)
128K bytes of non-volatile configuration memory.
125440K bytes of ATA CompactFlash (Read/Write)

 

UC520#service-module integrated-Service-Engine 0/0 status
Service Module is Cisco Integrated-Service-Engine0/0
Service Module supports session via TTY line 2
Service Module is in Steady state
Service Module heartbeat-reset is enabled
Getting status from the Service Module, please wait..
 
Cisco Unity Express 2.3.4.1
CUE running on UC500

 

 

Thank you.

 

 

 

1 Accepted Solution

Accepted Solutions

Manish Gogna
Cisco Employee
Cisco Employee

Hi,

Can you try the following

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity_exp/rel3_1/installation/guide/install31/boothelp31.html

HTH

Manish

View solution in original post

7 Replies 7

Manish Gogna
Cisco Employee
Cisco Employee

Hi,

Can you try the following

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity_exp/rel3_1/installation/guide/install31/boothelp31.html

HTH

Manish

Hello Manish and thank you for your reply.

In the procedure described,

Step 1 Type reload to restart the system.

Step 2 Type "***" to enter the boot loader mode.

do you know where to enter the "reload" command and when to type *** ?

 

Thanks again.

Themis.

Hi Themis,


The reload command needs to be given from CUE itself.

Once the command is given, after some time you are prompted to Please enter '***' to change boot configuration, enter ***.

This allows Cisco Unity Express to go into boot loader mode.

Enter config at the ServicesEngine boot loader> prompt.

Enter these details for the various prompts shown in the config output:

    The Cisco Unity Express IP address

    The Cisco Unity Express subnet mask

    The TFTP server address

    The Cisco Unity Express default gateway

The Ethernet interface is internal. Enter cue-installer image name for the default helper image. Ensure that the default boot is always disk, the default boot loader is always primary, and the Ethernet interface is always set to internal.

Example

    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

The system writes the information onto the Flash, and the ServicesEngine boot loader> prompt appears again.

Good day Manish,

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

The problem is that i cannot access CUE.

Trying to open session, i have the following:


UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

 

This counting never stops thus, i cannot issue any command from within CUE.

Thank you,

Themis.

 

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

UC520#service-module integrated-Service-Engine 0/0 session
Trying 10.1.10.2, 2002 ... Open


User Access Verification

Username: cisco
Password:
 waiting 299 ...

 waiting 300 ...


 waiting 302 ...

 waiting 707 ...

 waiting 708 ...
 waiting 709 ...

- See more at: https://supportforums.cisco.com/discussion/12519701/cannot-access-cue-uc520-16u-4fxo-k9#sthash.XK7JQ08e.dpuf

Hi,

Thanks for the details, i would suggest involving TAC in that case.

Manish

You were right at first place. I was doing something wrong during the boothelper procedure. It's OK now.

 

Thank you very much.

Themis.

Hi,

 

In case its still not working.

 

CUE Telnet access is configured for access authorization. So at this prompt ,we should enter user credential for hosting device, itself. If you have an enable password set for this box, please do try the same. If that do not works, then try giving credential for old box as well.

 

\Amit

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: