Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Firmware to be upgraded from v6.10 build 405, needs assistance.

How do i upgrade the firmware from v6.10.

4 REPLIES
New Member

Re: Firmware to be upgraded from v6.10 build 405, needs assistan

Hi,

I have CSS 11050 running V6.10 build 405

sometime content switch getting hunged.

which causing impact.Please let me know whats the latest firmware recommended release that i can upgrade and also please provide me the link of it aswell.

Thanks in advance

Cisco Employee

Re: Firmware to be upgraded from v6.10 build 405, needs assistan

There is no need to upgradeom from 6.10.

You need to contact the TAC to have your hung state troubleshooted.

It requires forcing a core dump when in a bad state.

This is a complex procedure that can't be given in a forum.

What do you do to recover from the hung state ?

Is the CSS still switching traffic during that time ?

Do you have some kind of access through console or telnet when css hanging ?

Gilles.

New Member

Re: Firmware to be upgraded from v6.10 build 405, needs assistan

Hi Gilles,

Thanks for reply

we have 2 HA redundant CSS's acting as master and slave -one-01 and -one-02

Both devices have 3 VLANS setup with each VLAN having the same critical service configured.

The live incident is out of 3 vlans 2 of these VLANS failing over to one-02, leaving the remaining VLAN active on one-01.

This is what caused the service impact. We do not know the reason why this happened.

Please advise as to what changes can be made to the configuration to prevent the incident having a reoccurance.

Thanks for your time.

New Member

Re: Firmware to be upgraded from v6.10 build 405, needs assistan

Hi Giles,

I had a problem with a CSS11503 where an app configured to use a VIP on the CSS stopped working after new confg was applied

The problem was that the content rule for the catchall was using the wrong port. Once that was changed the app worked fine

We are however confused as to how it ever worked as this has been running for months ?

Any suggestion on this would be greatly appricated..

140
Views
4
Helpful
4
Replies
CreatePlease login to create content