topic Cisco Ace Failed to boot in Application Networking

Cisco Ace Failed to boot

Dmashlah11 — Tue, 24 Sep 2013 11:20:14 GMT

Dears,

i have a Cisco Ace Module,

when i tried to creat new context i got disk0: read error, i formated the disk0, after the format finished the modulte rebooted to ROMMON mode,

System Bootstrap, Version 12.2[123],

Slot 1 : Running DEFAULT rommon image ...

.ACE platform with 1048576 Kbytes of main memory

.Loading disk0:c6ace-t1k9-mz.A2_3_3.bin. Please wait ....

file(disk0:c6ace-t1k9-mz.A2_3_3.bin) open error

loadprog: error - on file open

boot: cannot load "disk0:c6ace-t1k9-mz.A2_3_3.bin"

rommon 1 > dev

Devices in device table:

id name

bootflash: boot flash

disk0: ATA disk 0

eprom: eprom

rommon 3 > dir disk0:

Directory of disk0:

rommon 4 >

---------------------------

when i tried to boot the module from Cisco 6500 SW

6509(config)#boot device module 1 sup-bootdisk:c6ace-t1k9-mz.A2_3_3.bin

Failed to set boot device module 1

Failed to set boot device.

Cisco Ace Failed to boot

Santhosh S — Thu, 26 Sep 2013 09:23:50 GMT

Darwish,

From the output I can see disk0: is empty, so there is no image for the module to boot from.

And on 65K: "Failed to set boot device module 1"

This error usually occurs due to communication failure between the module and the chassis backplane.

Couple of things you can try if you haven’t already –

Reseat the module.
Try the module in a different slot.

Hope that helps

~Santhosh

Cisco Ace Failed to boot

Jorge Bejarano — Tue, 08 Oct 2013 04:44:30 GMT

Darwish,

You may open a case with TAC to try to load the image from the switch since it looks it does not have any image currently

Jorge

Hi. Sorry for my english.The

Gabriel Santini — Wed, 24 Sep 2014 15:27:23 GMT

Hi. Sorry for my english.

The problem wit this is that MUST be disk0: not a sup-bootdisk o anything...

My problem was the same:

Router(config)#boot device module 2 sup-bootdisk:c6ace-t1k9-mz.A2_3_5.bin
Failed to set boot device module 2
Failed to set boot device.

Then, I was installed a PCMCIA card, copied the software and:

Router(config)#boot device module 2 disk0:c6ace-t1k9-mz.A2_3_5.bin
Device BOOT variable = disk0:c6ace-t1k9-mz.A2_3_5.bin

Then, into the ACE:

rommon 2 > boot eobc:
.Probing SUP for RP number...
Received SUP RP number via PF DB: 1
boot string configured on SUP is "disk0:c6ace-t1k9-mz.A2_3_5.bin"
.
Download Start
!!!!!!!!!!!!!!!!!

And so on...

Brgds

http://www.cisco.com/c/en/us/td/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/administration/guide/admgd/upgrade.html#wp1051170

Hi Brgds,Did module reload

Kanwaljeet Singh — Wed, 24 Sep 2014 15:54:40 GMT

Hi Brgds,

Did module reload with image fine now and you still need any assistance? And yes it should be disk0 but this is disk0 for sup.

Regards,

Kanwal

Note: Please mark answers if they are helpful.

Hi,If you are using Nexus

pukumar2 — Mon, 29 Sep 2014 07:46:26 GMT

Hi,

If you are using Nexus family product, then You might want to check out this new product called ITD.

Simple and faster solution:

ITD provides :

ASIC based multi-terabit/s L3/L4 load-balancing at line-rate
No service module or external L3/L4 load-balancer needed. Every N7k port can be used as load-balancer.
Redirect line-rate traffic to any devices, for example web cache engines, Web Accelerator Engines (WAE), video-caches, etc.
Capability to create clusters of devices, for example, Firewalls, Intrusion Prevention System (IPS), or Web Application Firewall (WAF), Hadoop cluster
IP-stickiness
Resilient (like resilient ECMP)
VIP based L4 load-balancing
NAT (available for EFT/PoC). Allows non-DSR deployments.
Weighted load-balancing
Load-balances to large number of devices/servers
ACL along with redirection and load balancing simultaneously.
Bi-directional flow-coherency. Traffic from A-->B and B-->A goes to same node.
Order of magnitude OPEX savings : reduction in configuration, and ease of deployment
Order of magnitude CAPEX savings : Wiring, Power, Rackspace and Cost savings
The servers/appliances don’t have to be directly connected to N7k
Monitoring the health of servers/appliances.
N + M redundancy.
Automatic failure handling of servers/appliances.
VRF support, vPC support, VDC support
Supported on both Nexus 7000 and Nexus 7700 series.
Supports both IPv4 and IPv6
N5k / N6k support : coming soon

Blog

At a glance

ITD config guide

Email Query or feedback:ask-itd@external.cisco.com