Sup2T IOS Upgrade to Support WS-X6904-40G

Hi All,
We are currently running "s2t54-adventerprisek9_npe-mz.SPA.150-1.SY.bin" image on our Sup2T (single Supervisor in each chassis). We want to upgrade two of our core 6K to support WS-X6904-40G line card.
I am going through below release note thinking about upgrading it to "s2t54-adventerprisek9-mz.SPA.151-2.SY.bin"
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.1SY/release_notes.html#wp4833604
There are few code options available to me (see below), What version do you guys suggest me based on your experience with this line card.
In that I found this EFSU compatibility matrix which I could not understand properly. Should I go by this compatibility matrix & make a decision?
Upgrade to Release15.0(1)SY1 or later before installing WS-X6904-40G (see the "EFSU Compatibility" section).
TIA
Rasika

Every major IOS release, the amount of stacked 6800IA increases. How many currently, I've lost touch.
The problem nowadays is some SEs don't seem to know how to sell them or they're not listening to their clients. It's like they are selling them to get "points".
You have to be one good network engineer to say "no" due to specific technical reasons.

Similar Messages

C6509E/SUP2T/X6904-40G/FOURX Converter will not recognize 1G Optic Transceiver

We have a C6509E with dual VS-SUP2T-10G running 15.0(1)SY6. A WS-X6904-40G-2T module is in slot1 and 2. They have CVR-CFP-4SFP10G converters in the slots. The GLC-SX-MMD 1Gbps optical transceivers are not recognized, even though they are on the supported list.

A simple solution... upgrade to 15.1(2)SY2! Now they are recognized.

WS-X6904-40G-2T Instant Access query

Hello
I'm having a look at Instant Access with the WS-X6904-40G-2T linecard. Instant Access can currently support 1000 ports with a maximum of 12 stacks. The document below seems to state that only 6 ports on a WS-X6904-40G-2T linecard can be used for IA parent-client links. Does this mean that a WS-X6904-40G-2T can only support 6 IA stacks? If so, is this number increase set to increase?
Thanks
Andy
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/15-1SY/config_guide/sup2T/15_1_sy_swcg_2T/instant_access.pdf
The IA parent-client connection is supported on links between WS-X6904-40G-2T switching
module 10GE ports and Catalyst 6800ia access switch 10GE ports.
– You can use up to 6 IA client 10GE ports in the IA parent-client link. See this document for
information about WS-X6904-40G-2T switching module port configuration:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/white_paper_c11-696669.html

Every major IOS release, the amount of stacked 6800IA increases. How many currently, I've lost touch.
The problem nowadays is some SEs don't seem to know how to sell them or they're not listening to their clients. It's like they are selling them to get "points".
You have to be one good network engineer to say "no" due to specific technical reasons.

Since an ios upgrade on my ipod, my device no longer appears in itunes or my computer

Since a recent ios upgrade, I can not locate my Ipod touch 5th generation in iTunes nor in My Computer. I am working with Windows 7. I have uninstalled and reinstalled itunes, quicktime and Apple Mobile Device Support software programs. I have also gone through the on line Apple Trouble shooting support for this problem with no success.
I did have WiFi syncing turned on before the upgrade and now when I go into settings on my iPod, the sync now option is greyed out.
Any other ideas please...

OK, never mind. After all that, a restart of the iPhone fixed it. That should have been the first thing I tried, of course, before posting. Sorry about that!

I bought a Sandisk Connect Media Drive, downloaded the app from iTunes. Before iOS 8, movies played fine. After iOS upgrade I can no longer play movies downloaded from iTunes to the media drive. Anyone else have a similar issue?

I bought a Sandisk Connect Media Drive, downloaded the app from iTunes. Before iOS 8, movies played fine. After iOS upgrade I can no longer play movies downloaded from iTunes to the media drive. Anyone else have a similar issue?

I checked with SanDisk's own online support and they indicate that they have notified Apple of the issue.
According to SanDisk, the problem lies with Apple not having the iOS 8 version of the Safari browser having DRM decoding enabled that the Media Drive relies upon to decode and play iTunes DRM titles. Non DRM encoded videos will play in the browser.
DRM audio is not effected as this is handled by the native iOS music app.
As of the date of this post SanDisk have not been given a timeframe by Apple for this issue to be resolved.
I hope that Apple resolves this issue quickly as I have a large collection of DRM video titles on a 128Mb memory card installed in the Media Drive that I am unable to view.

POE 3560 Issue after IOS upgrade

Hello,
I having issue where 6 WLAN AP's not coming back uo after reboot and IOS upgrade of 3560 POE swtiches - . Prior to changes here most if not all ALL the 23 Aps were mainly on one switch, Now after these changes they are now spread over three switches ( 3560's) - with 17 coming back on line
I am sure its not the power limitation of the switch(s) as the one switch I am TS at present had a fairly large allocation of the aps attached prior to ios upgrade and reload. and the available power value now showing is applicable.for 8 AP's
I have tried various TS steps to try and bring them back up - A couple of things I would like to try but I am restricted to do so is to check the APS physically or downgrade the ios!
Any input on this matter would be truly appreciated.- (attached is the log buffer debug)
res
Paul

c3560-ipbase-mz.122-25.SEE2.bin
You upgraded the IOS to the switch? I shudder at the thought of what old version did you upgrade FROM.
Available:370.0(w) Used:110.4(w) Remaining:259.6(w)
You've got more than enough PoE left.
Only two things comes to my mind:
1. Cable issue - Unfortunately, the 3560 is a non-GigabitEthernet and this particular sub-model does NOT support TDR.
2. Hardware failure - Read THIS.

IOS upgrade - can no longer resize pictures for messaging or email

Hi before the recent iOS upgrade, if I wanted to send a photo from my iPhone by either MMS or email I had the option to choose the file size of the photo before I sent the message. This option now seems to have disappeared. Does anyone know if this option has been removed, or is it now hidden away in the settings somewhere?

Hi AntonioC,
The forums wouldn't let me login as CFTrock so I had to register a new User ID (CFTagain).
Thanks for your response and for you'r suggestion.
I actually have contacted Verizon and here's what's been happening...
I thought it was the GB update but I can't be sure. I remember that the Facebook app notified me of an update which I downloaded around the same time of the GB update.
I can't be sure if it was the GB update or the facebook app update which has caused the photo upload error.
I did call Verizon tech support and after spending time doing some of their suggested actions (uploading the picture with 3G or WiFi, uninstalling, reinstalling
the facebook app, taking and trying to upload lower quality pictures, etc.). The Verizon tech put me on hold as he attempted to get in touch with Samsung.
When he got back to me he told me the only option/solution which Samsung and the Verizon engineers could come up with was a Factory Reset.
The Factory Reset has NOT helped. I had to lose all of my Angry Birds data (saved progress), I had to loose text messages because the SMS backup/restore
app I was recommended didn't do a good job, and my phone seems to be more sluggish since the Factory Reset. I suspect its the facebook app update
and NOT the GB update.
I have found a mediocre work around. If you want to upload a picture I would recommend you open up your phone's browser and type in facebook.com.
Hit the "Photo" tab, the next screen will provide you with a "Choose file" button. Click that and you'll be set.
Please DO NOT Factory Reset your phone. I really wish I had not. My phone
hasn't been right since that Factory Reset.
I really do believe its the fb app that is causing this particular problem.
Hopefully fb will release an updated app soon.
Anyone else have this problem or have suggestions?

Lost iTunes purchased music after latest IOS upgrade

After the automatic IOS upgrade for the Apple Watch my iTunes account lost several purchased albums. I have tried to re-download the purchased music but not successfully, I'm only able to download four of the songs and they are still not showing up in my iTunes library.

For info these are user-to-user forums, you are not talking to Apple nor iTunes Support.
If they don't show in the Purchased tab in the iTunes Store app on your iPhone and iPad then check to see if they are hidden : iTunes Store: Hiding and unhiding purchases.
If you've moved countries since buying them, or if the rights-holder has removed them from the store, then you won't be able to redownload them. Also if the rights-holder has removed an album and replaced it with a different version then it be treated as a different album/purchase.

I have the original Ipad. How do I download the latest iOS upgrade on my original Ipad?

How do I upgrade to the latest iOS with my original IPad?

See
iOS 5: Updating your device to iOS 5
http://support.apple.com/kb/HT4972
iOS: How to update your iPhone, iPad, or iPod touch
http://support.apple.com/kb/HT4623
If you are currently running an iOS lower than 5.0, connect to your computer & click on the "Update your device using iTunes".
Tip - You may need to disable your firewall and anitvirus software temporarily. Then download and install the iOS update. After you update to iOS 5.x, the next update can be installed via wifi (i.e., not connected to your computer).
 Cheers, Tom

IDSM2 on 6500-IOS inline mode support?

Hi,
I have an IDSM-2 running IPS5.1(1d) software (recently upgraded from 4.x) that is sitting on a 6500 IOS.
The IPS device manager shows gi0/7 and gi0/8 as both in Promiscuous mode. There is no option to change the mode to inline and pair them.
Is it so that IDSM-2 currently supports only Promiscuous mode?
If so, then this module is still acting as an IDS despite running IPS5.1. Isn't it? What is the advantage that I get after upgrading it from 4.x to 5.1?
-- Vasanth

There are 2 pieces to the puzzle.
There is the IDSM-2 version and what it supports, but also the Cat 6K Native IOS version and what it supports.
IDSM-2 v5.1(1d) supports
a) Promiscuous mode,
b) InLine Interface Pair mode (2 interfaces are paired for inline monitoring), and also
c) InLine Vlan Pair mode (2 vlans on a single interface are paired for inline monitoring, you will also see it called inline-on-a-stick)
But for these features to be used, the switch code must also support configuring the switch side of the IDSM-2 for each of these 3 features.
Native IOS Versions prior to 12.2(18)SXE will support only Promiscuous mode on the IDSM-2.
12.2(18)SXE and later versions will support InLine Interface Pair mode on the IDSM-2.
No Native IOS versions currently support InLine Vlan Pair mode on the IDSM-2 (a new Native IOS versions with this support is currently in development).
So to get Inline (IPS) functionality you need to be running a Native IOS version 12.2(18)SXE or later, and on the IDSM-2 run IPS versions 5.1 (or even the older 5.0).
(NOTE: Cat OS 8.5(1) does support all 3 modes of the IDSM-2. So if you are using Cat OS instead of Native IOS, then run version 8.5(1) to have access to all of the features of IPS 5.1(1) on the IDSM-2)
If you are running a Native IOS version prior to 12.2(18)SXE then the IDSM-2 can only be operated in Promiscuous mode even if 5.1(1) is loaded on the IDSM-2.
However, even in promiscuous mode the IPS 5.1(1) software does have a few advantages.
There are several engines, and engine parameters that are only supported in the 5.1 version and not the 4.0 version. So there are several signatures that are either a) not even created for 4.x sensors, or b) the 4.x signature is not as precise as the 5.x signature in the new engines.
(These new engines have proved invaluable in writing signatures to detect some of the new attacks that have come out over the past year.)
There are of course other advantages as well:
For example:
1) Risk Rating to better aid in prioritization of alerts.
2) More flexible fitlering mechanism for alerts that allows for fitlering individual actions
The 2 features above are just 2 of the new features that have been added in 5.0 and 5.1 that apply to both promiscuous and inline modes.

Cisco 4500X IOS upgrade through ISSU

Hi,
I am having 2 number of cisco 4500x switch and configured with VSS
so one switch is active and another switch is standby.
I am panning to upgrade IOS through ISSU
i read in document that it required auto boot enable in switch.
My switch current Configuration register = 0x2101
do i need to change config register or this will ok. If need to change then what will be auto boot and after IOS upgrade do i need to change it again.
Please help....

Hello Tarun,
Please find below the steps to perform the ISSU:
ISSU Prerequisites
Before one can perform an ISSU, there are a few prerequisites one must verify for a successful ISSU. The following list explains what is initially required.
• Must be using a redundant Cisco Catalyst 4500 switch with symmetric hardware (that is, supervisors, memory, rommon, NFL daughter card, and so on).
• Both new and old Cisco IOS Software images must be preloaded to the file system on both supervisors.
• SSO must be configured and working properly.
• Config register must be configured to autoboot (that is, the value should have a "2" in the lowest byte).
45010R-203# sh bootvar | i register
Configuration register is 0x2102
Standby Configuration register is 0x2102
Several commands are available to verify if SSO is enabled:
4510R-203# sh module | b Redundancy
Mod  Redundancy role     Operating mode      Redundancy status
----+-------------------+-------------------+-------------------
1   Standby Supervisor   SSO                  Standby hot
2   Active Supervisor    SSO                 Active
45010R-203# sh redundancy states
       my state = 13 -ACTIVE
     peer state = 8   -STANDBY HOT
           Mode = Duplex
           Unit = Secondary
        Unit ID = 2
Redundancy Mode (Operational) =  Stateful Switchover
Redundancy Mode (Configured)  =  Stateful Switchover
Redundancy State              =  Stateful Switchover
             <snip>
4507R-ISSU# sh run | b redundancy
redundancy
mode  sso
As a step prior to the beginning of the ISSU process, the new version of the Cisco IOS Software image needs to be loaded into both the active and standby supervisors' file systems. Both active and standby supervisor need to contain both the new and old images in the file system. In order to store both new and old images, the supervisors should be upgraded to contain sufficient amounts of flash memory prior to the ISSU process.
The new images can be downloaded into both supervisors using commands such as:
copy tftp: bootflash:
copy tftp: slavebootflash:
The example below illustrates this verification:
4510R-203#dir
Directory of bootflash:/
1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
4510R-203#dir slavebootflash:
Directory of slavebootflash:/
1  -rwx 13636500 Sep 6 2006 03:18:58 -08:00 cat4500-entservices-mz.122-31.SGA
2  -rwx 13747611 Sep 9 2006 03:19:58 -08:00 cat4500-entservices-mz.122-31.SGA1
Once this check is verified, one can now proceed with the ISSU process.
The ISSU process is started by typing the "issu loadversion" command on the active supervisor. This command directs the active supervisor to begin the ISSU process. The active supervisor, through intersupervisor communications, checks that the requested image has been downloaded into both the active and standby supervisors' file systems. If the required images are not present, the command is rejected, and an appropriate warning is generated.
If the "issu loadversion" command is successful, the switch transitions into the "Load Version" ISSU state. The standby supervisor will reset and boot with the new version of the Cisco IOS Software image loaded into the file system.
The following actions take place when the command is implemented:
1. The standby supervisor (B) is reset.
2. The standby supervisor (B) is booted with the new Cisco IOS Software image: Release 12.2(31)SGA1.
3. If both Cisco IOS Software images are declared as compatible, the standby supervisor moves into SSO mode and is fully stateful for all compatible clients and applications. Compatibility allows for in-service software upgrade or downgrade between two versions to succeed with minimal service effect.
4. If both Cisco IOS Software images are incompatible, the system moves into RPR mode, and the ISSU process is terminated with an appropriate message to the user. Images are declared incompatible when "required" clients or applications are not interoperable between two Cisco IOS Software releases.
5. Standby "B" reaches the standby HOT state.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
7. The "issu loadversion" command also supports a "forced" option that allows the operator to force the system into entering RPR mode when incompatibility is detected.
Note: When performing an ISSU, disable manual switchovers. Performing manual switchovers during the issu process is strongly discouraged. The current implementation does not prevent it, but it does display a warning to the user.
An example of the CLI for implementing the issu loadversion command is displayed below.
On the active supervisor, one would issue the following command:
4510R-203#issu loadversion 1 bootflash:cat4500-entservices-mz.122-31.SGA1 2 slavebootflash: cat4500-entservices-mz.122-31.SGA1
Syntax - issu loadversion active-slot active-image-new standby-slot standby-image-new
The second step of the ISSU process is to perform the issu runversion CLI.
The user can issue the " issu runversion" command when:
1. The ISSU state is "Load Version"; this can be verified with the "show issu state detail" CLI.
2. The standby supervisor is running the new version of the software.
3. The standby supervisor has moved into the "Standby Hot " state.
The following actions take place when the " issu runversion" command is executed:
1. A switchover occurs; that is, the standby (B) becomes the new active, and the old active (A) is rebooted and comes up as a standby.
2. A timer called "Rollback Timer" is started with a previously configured value.
3. Move both supervisors to "Run Version" state.
4. If the command "issu acceptversion" is not issued before the "Rollback timer" fires, then the entire ISSU process is aborted via the automatic rollback.
5. If the active supervisor console connectivity is established and the "issu acceptversion" command is issued, then the rollback timer is stopped.
6. The user has an option to abort the ISSU process by issuing the "issu abortversion" command.
An example of the CLI for implementing the issu runversion command is displayed below:
On the active supervisor, one would issue the following command:
4510R-203#issu runversion 2 slavebootflash:cat4500-entservices-mz.122-31.SGA1
Syntax - issu runversion standby-slot [standby-image-new]
Prior to issuing the `issu acceptversion' command the system will be counting down the rollback timer. If `issu acceptversion' is not completed before rollback timer expires an automatic abort will occur. This command stops the "Rollback Timer." This command serves as a feedback mechanism. This is an optional command and can be skipped in the ISSU process with the "issu commitversion" CLI.
If this command is not issued within 45 minutes (default) from the time the standby supervisor moves into the "Standby Hot" state, it is assumed that the new active supervisor is not reachable and the entire ISSU process is rolled back to the previous version of the software. The acceptversion is not intended for long-term network operation. It is also important to note that none of the features available on the new version will work yet.
The following actions take place when the command is implemented:
1. The "Rollback Timer" is terminated. This means that the rollback timer is not looked at anymore. Therefore, the system can run in this state for an extended period.
2. The user has an option to abort the ISSU process by issuing the command "issu abortversion."
Aborting the ISSU process now causes the newly active supervisor (B) to fail over to the standby supervisor (A) running the old image and will also cause the rebooting supervisor (B) to load the original image. The issu acceptversion halts the rollback timer and helps ensure the ISSU process is not automatically aborted during the process.
An example of the CLI for implementing the issu acceptversion command is displayed below:
On the "New" active supervisor, one would issue the following command:
4510R-203#issu acceptversion 2
% Rollback timer stopped. Please issue the commitversion command.
Syntax - issu acceptversion active-slot-number
This is the last stage of the ISSU procedure. Once the user is satisfied with the new version of software, this must be committed by issuing the "issu commitversion" command. This command resets the standby supervisor and boots it with a new version of the software (same as the active supervisor). This concludes the ISSU process, and the new version of software is permanently committed on both supervisors. Since this is the conclusion of the ISSU process, the system can not be reverted back to the previous version of the software from this point onward as a part of this upgrade cycle. However, if for any reason users wish to go back to the previous version of the software, they can do so by starting a new upgrade/downgrade process.
The following actions take place if the command is implemented:
1. The standby supervisor (A) is reset and booted with the new version of Cisco IOS Software image.
2. The standby supervisor (A) moves into the "Standby Hot" state in SSO mode and is fully stateful for all clients/applications that are compatible.
3. Both supervisors are moved into "Final State," which is the same as "Initial State."
4. Users can initiate switchovers from this point onward.
An example of the CLI for implementing the issu commitversion command is displayed below:
4510R-203#issu commitversion 1
Syntax - issu commitversion standby-slot-number
ISSU Process: issu abortversion
One can abort the ISSU process at any stage manually (prior to issuing the issu commitversion command) by issuing the exec-level issu abortversion command. The ISSU process also aborts on its own if the software detects a failure.
If a user aborts the process after issuing the issu loadversion command, then the standby supervisor engine is reset and reloaded with the original software.
If the process is aborted after a user enters either the issu runversion or issu acceptversion command, then a second switchover is performed to the new standby supervisor engine that is still running the original software version.
The supervisor engine that had been running the new software is reset and reloaded with the original software version. The command is accepted only in "Load Version" or "Run Version" states. In "Load Version" state, the active supervisor is running an old image and the standby supervisor is running new image.
Syntax - issu abortversion active-slot [active-image-new]
Let me know if you have any questions.

Cisco 6500 Sup2 IOS with SLB support

Hello
A have two questions about SLB funcionality on Cisco 6500 SUP2/MSFC2
1) Is IP LAN ONLY ios support SLB ? If yes, does it have any restrictions ?
2) How heavy IOS SLB for processor ? (i mean in dispatched mode).

Are sup-bootflash: and sup-bootdisk: the same thing ?
No, they are not. sup-bootflash: is located inside but the sup-bootdisk: is located OUTSIDE and is physically accessible. If you look at the line card, you'll see a CF slot marked "Disk0:" or "Slot0". This is the sup-bootdisk:. It is also known as "disk0:". Confusing, I know.
Can I make use of the disk0 of both chassis to perform ios upgrade ?
Of course you can. I perform VSS upgrade just using one of the disk0: and push the IOS from the disk0: to the two supervisor cards.
By setting the boot path to disk0
You can too. The sup-bootflash: and the sup-bootdisk:/disk0: are the same physical format.
A word of caution: I cannot stop reiterating the importance of checking the MD5 hash value of the IOS file in the sup-bootdisk: or sup-bootflash: BEFORE rebooting the chassis for an IOS upgrade. Make sure the MD5 hash value match exactly to the MD5 hash value found in the Cisco website. Once they are match, check the boot variable string, the config-registry and you're off to the next step.

Internet Don't work after the last IOS Upgrade. What can I do?

Internet Don't work after the last IOS Upgrade. What can I do?

Can you give us more details?
Is Wi-Fi working, i.e. not greyed out in Settings/Wi-Fi?
Can you go online by using the Mobile Network?
Any error messages given?
Problem with your router?
See these articles for help with Wi-Fi issues:
Issues with Wi-Fi networks and connection
Wi-Fi or Bluetooth settings grayed our or dim
If you see No Service in the status bar of your iPhone or iPad - Apple Support
iOS and OS X: Recommended settings for Wi-Fi routers and access points

HT4972 Where can I get an iOS upgrade for my I pad 2 with iOS ?

I have looked in settings and on the iTunes store for an upgrade to iOS 5, does anyone know where to get this?

The option to update without the computer (Over the air) was made available with iOS 5. If your iDevice is using a version of iOS lower than 5, you will need to use iTunes on your syncing computer to perform the upgrade. Use the Apple link below as a guide for the upgrade.
http://support.apple.com/kb/HT4972
Also read the instructions from the section entitled "Update your device using iTunes" at the link below.
http://support.apple.com/kb/HT4623
Information regarding transferring purchases from your iDevice to iTunes on your syncing computer can be found at the link below.
http://support.apple.com/kb/ht1848

Apple iPad 3. BT email not working. Cannot send emails from btconnect SMTP after iOS upgrade. This is the only difference I am aware of. Can anyone help me please.

BT email not working. Cannot send emails from btconnect SMTP after iOS upgrade. This is the only difference I am aware of. Apple iPad 3. Can anyone help me please.

All resolved at last
Deleted the SMTP setting
Recreated the SMTP using the same settings
Able to send emails now
No logic - as usual - just a bug!

Sup2T IOS Upgrade to Support WS-X6904-40G

Similar Messages

Maybe you are looking for