Cisco CISCO2921/K9 IOS Upgrade

Hi Everyone,
I've been asked to upgrade the IOS Image on our 2921 Router. We currently have IOS version 15.2(3)T1 and a CME version 9.0 running using SIP and Skynny protocols.
I have to upgrade it to CME version 10.0 which I understand is embedded in IOS version 15.3(3)M, right?
So I was hoping if you can shed some light on this procedure since it's my first time executing this task. Do I need to upgrade the phones firmware as well? I have been looking around the internet but still I'm not quite sure how to go about it.
Thanks!

You are correct that CME 10 is embedded in that IOS version. Depending on the phones and firmware they should be ok. Make sure to copy the config before you do anything!

Similar Messages

Help Setting Up A Cisco Lab For IOS Upgrade?

Hi.
I've collected quite a few routers and switches over the past few months that have what seems to be corrupted or no IOS. I have a small lab set up to test parts, and I was wondering how I can network them in such a way where I have an active functional network (for testing purposes, not for actual internet use), that I can connect routers or switches to and upgrade or change the IOS version.
I have all the hardware and cabling needed, and I have the Cisco IOS software for the routers I need, I've just never upgraded or changed an IOS on a router or switch before.
I have:
a Cisco 7505 with an RSP4+, 256MB RAM, 16MB Flash, and it's full of the modules that hold the PA cards (I forget what it's called, but I just use it to throw PA cards in to test 8 at a time).
A Cisco 3450 (I believe, 3400 series anyhow) that I believe is 64/16, that again I use for testing.
Two Cisco 2621 64/16, for testing WIC's, VWIC's and NM's.
Two Cisco 2950 series switches, one I'd like to use to actually connect to my LAN already implimented seperatly, and one to connect to this mini lab LAN.
So again, I'm wondering how I can set these up on a small LAN just for testing purposes and so I can just connect a device and upgrade it's IOS. I also need information about the TFTP server and all of that as I haven't been able to find out much info on it.
Thanks in advance for any help :).

Hi
First of all make sure that the flash is enough for IOS you are loading.Here is guide for loading IOS.
(1)Download and install tftp server from www.solarwinds.net
(2)Give IP on ethernet port of router
(3)Give IP on computer which should be in same subnet that of router
(4)Follow the following steps:
Router#copy tftp: flash:
Address or name of remote host []? 192.168.1.67
Source filename []? c1700-k9o3sy7-mz.122-15.T9.bin
Destination filename [c1700-k9o3sy7-mz.122-15.T9.bin]?
Accessing tftp://192.168.1.67/c1700-k9o3sy7-mz.122-15.T9.bin...
Erase flash: before copying? [confirm]
Erasing the flash filesystem will remove all files! Continue? [confirm]
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased
Erase of flash: complete
Loading c1700-k9o3sy7-mz.122-15.T9.bin from 192.168.1.67 (via FastEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 9190488/18380800 bytes]
Verifying checksum... OK (0xF7C5)
9190488 bytes copied in 129.664 secs (71244 bytes/sec)
(5)Reboot and your new IOS is ready.
Regards
JD

Cisco 4402 WLC IOS Upgradation using CLI and Web Interface

Hi,
I would like to know how to upgrade IOS of Cisco 4402 WireLess LAN Controller using CLI and Web interface ?
Can any one help me regarding the same.
Please answer as soon as possible.
Thanks in advance.

Here are the instructions for upgrading the controllers via GUI:
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn52.html#wp472449
Instructions via cli:
Cisco recommends that a direct CLI console port connection is used to update the controller software.
1. Make sure a TFTP server is available for the Operating System (OS) software download. Also, keep these guidelines in mind when the TFTP server is set up:
If a download is performed through the service port, the TFTP server must be on the same subnet as the service port because the service port is not routable.
If a download is performed through the Distribution System (DS) network port, the TFTP server can be on the same or a different subnet because the DS port is routable.
The TFTP server cannot run on the same computer as the Cisco Wireless Control System (WCS) because WCS and the TFTP server use the same communication port.
2. Download the desired OS software update file from the Cisco website to the default directory on the TFTP server.
3. Log into the WLC CLI.
4. Issue the ping server-ip-address command to verify that the WLC can contact the TFTP server.
5. Issue the transfer download start command and answer n when prompted to view the current download settings.
This example shows the command output:
transfer download start
Mode........................................... TFTP
Data Type...................................... Code
TFTP Server IP.................................
xxx.xxx.xxx.xxx
6. TFTP Path...................................... TFTP Filename.................................. AS_2000_3_0_x_x.aes --OR-- AS_4100_3_0_x_x.aes --OR-- AS_4400_3_0_x_x.aes Are you sure you want to start? (y/n) n Transfer Canceled Issue these commands to change the download settings:
* transfer download mode tftp
* transfer download datatype code
* transfer download serverip tftp-server-ip-address
* transfer download filename filename
* transfer download path absolute-tftp-server-path-to-file
Note: All TFTP servers require the full pathname. For example, in Windows, the path is C:\TFTP-Root. (In UNIX forward slashes (/) are required.)
7. Issue the transfer download start command to view the updated settings, and answer y when prompted to confirm the current download settings and start the OS code download.
This example shows the download command output:
transfer download start
Mode........................................... TFTP
Data Type...................................... Code
TFTP Server IP.................................
xxx.xxx.xxx.xxx
TFTP Path......................................
path>
TFTP Filename..................................
AS_2000_3_0_x_x.aes --OR--
AS_4100_3_0_x_x.aes --OR--
AS_4400_3_0_x_x.aes
Are you sure you want to start? (y/n) y
TFTP Code transfer starting.
TFTP receive complete... extracting components.
Writing new bootloader to flash.
Making backup copy of RTOS.
Writing new RTOS to flash.
Making backup copy of Code.
Writing new Code to flash.
TFTP File transfer operation completed successfully. Please
restart the switch (reset system) for update to complete.
8. The WLC now has the code update in active volatile RAM, but the reset system command must be issued to save the code update to non-volatile RAM (NVRAM) and reboot the WLC.
This is a sample output:
The system has unsaved changes.
Would you like to save them now? (y/n) y
The controller completes the bootup proce

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.

Wlc 5508 ios upgrade in ha mode

I am having 2 wlc 5508 in HA mode, and want to upgrade ios from 7.5 to 7.6
Current IOS file status in primary and secondary.
Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
HA WLC ios upgrade procedure is when we upgrade ios in primary wlc it will push to standby wlc and if earlier ios version match it will accept it.
ISSUE : If you check in wlc status detail I have given upper both has same ios version but IOS file are different and currently in HA mode and working.
Now I am trying to upgrade IOS it is not allow me to upgrade it.
Giving below error :
TFTP receive complete... extracting components.
Checking Version Built.
Image version check passed.
Informing the standby to start the transfer download process
Waiting for the Transfer & Validation result from Standby.
Standby - Standby receive complete... extracting components.
Standby - Checking Version Built.
Standby - Image version check passed.
Standby - Transfer failure : Upgrade from non LDPE to LDPE software is not allowed.
Please download AIR-CT5500-K9-x-x-x-x.aes image instead.
Transfer & Validation on Standby failed.
Transfer download failed both on Active & Standby, Please retry download
(Cisco Controller) >
Please suggest how I can upgrade IOS in HA mode.

Primary WLC IOS : AIR-CT5500-K9-7-5-102-0.aes
Standby WLC IOS : AIR-CT5500-LDPE-K9-7-5-102-0.aes
This won't work and you'll see from the error message. Your standby WLC has a particular firmware loaded with LDPE enabled. So first, you need to answer if you need LDPE or not.
Both firmwares has to match, including LDPE. If you need LDPE, the your primary has to be loaded with LDPE before you can proceed. If you don't need LDPE, then you need to downgrade the secondary to non-LDPE version before you can proceed.

Cisco Modem Firmware (HWIC) upgrade Process

HI experts,
I need to upgrade firmware of my LTE ( Hwic) module for the router 2901. I am wondering if this is the part of IOS upgrade process , I mean ones I upgrade IOS to the latest version will it upgrade my modem firmware by own or I need to upgrade LTE modem separately?
can you guys please share your experience here?
any docs on this please?
Thanks!

Hi,
The LTE module is part of main Cisco IOS you load into the router. Once you upgrade the IOS, it also applies to the module.
ntegrated 4G LTE WWAN broadband: With the 4G LTE WWAN modem integrated into the router, you gain the benefits of simplified installation and management. In addition, the Cisco 4G LTE WWAN EHWICs are tightly integrated with Cisco ISRs, which run the industry-leading Cisco IOS® Software, giving access to all the advanced features of Cisco IOS Software such as quality of service (QoS), intelligent network queuing, and robust security.
Link:
http://www.cisco.com/c/en/us/products/collateral/interfaces-modules/4g-lte-wireless-wan-enhanced-high-speed-wan-interface-card/datasheet_c78-710314.html
HTH

The iOS Upgrade TSHOOT Flowchart v1.0! :-)

I am not a jailbreak user, and yet was always bugged by the various unknown error messages when upgrading iOS.
Originally were some point-form notes for my own usages only, but feel that it would be useful for the community after seeing so many people facing various types of error messages on iOS 5 release today.
The paths for iPad is quite solid (cuz I am managing 4 iPads), just need to spend somemore time to QA the iPhone paths tomorrow.
Last but not least, this is inspired by Cisco Press - Troubleshooting IP Routing Protocols
http://www.itcertnotes.com/2011/10/ios-upgrade-tshoot-flowchart.html

Self-repaired! It was appear that the quality of reception of the ATV is problem because it cannot hold a connection long enough to download the software. I took an 11n airport express which extends my airport network and plugged the ATV to in by Ethernet. Result. ATV showed up on iTunes. Upgrade to 2.2 downloaded. And since I only stream, the system seems faster and more solid, so far. Amazing.

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.

2851 IOS upgrade failed with WAE

Hello,
I have a strange situation with WAAS. I am in progress of a project to upgrade my Cisco IP telephony and as a result preferred to update my remote sites routers to 12.4.x T code in order to register DSP resources over SCCP and match closely the CMgr version as many of the sites running mainline code didn't have updated parameters for this. To make a long story short, I upgraded (for other reasons) several non-voice sites routers that have WAE 512s running 4.1.7 with the latest 12.4.xT code and didn't have an issue. All upgraded sites are running 2821's or 2811's except this one site I had an issue with. I needed T code on this particular site router and assumed since others sites reacted well with the IOS upgrade and WAAS that this site wouldn't be different but it was!
Situation: After updating this 2851 router from 12.4.25c mainline to 12.4.24T3, traffic from WAN was directing to WAE but no return. It appeared also that any LAN redirection was also working but no return from WAE. I didn't see any WCCP flow statistics incrementing but traffic was being directed to the WAE. WAE connection statistics were building but all TCP based traffic was getting dropped. I tried 3 different feature sets of same code version wondering if I've encountered a bug but none of the featured images worked. I downgraded to 12.4.24T2 and still nothing. Changed IOS back to mainline code and WAE was back operational as expected. During the testing of each IOS change, I've reset the WAE also hoping it didn't get hung up with some WCCP process from the previous IOS change in case there was some codebug occuring.
Layout:
With respect to this site, we have a 2851 with multilinked serial interfaces to MPLS; WAN interface is redirecting 62 in with an ACL that disallows a couple of hosts. LAN side of router is single Gig port (router on a stick). 5 sub-interfaces configured with DOT1Q encap. including one interface for WAAS. 2 of these user interfaces are redirecting 61 in and of course the interface servicing WAAS is redirect excluded in. The 61 WCCP group is also using ACL to oppositely match WCCP 62 group.
Why would this upgrade cause a problem especially using latest T code? Feature sets would be irrelevant. One more thing that makes this even stranger is I have one other voice site running a 2851 with 12.4.24T3 (already running) and is configured for WCCP the very same with same 512WAE and 4.1.7 code. The only difference is this router is running a "SP" feature set which I didn't try on this site that is failing.
Does this make any sense to anyone? I've seen posted from one of the WAAS experts a document listing compatible IOS version across platforms but these efforts are the latest code. Any help would be greatly appreciated! Thanks everyone.

Thanks Bhavin.
Sorry, I've been traveling a lot lately for business and I haven't had a chance to respond. And it looks like I'll be heading out again for a few days. Meanwhile, I did want to say that I looked at a lot of these things and didn't see anything apparent. Egress methods show GRE Return. When I ran "show wccp flows tcp" I didnt' see any flow counts. However I could see packets redirecting at the router with "show ip wccp". I debugged events and packets and saw "See You" packets being sent back to the caching appliance. WCCP looked fine from the router's viewpoint. WCCP communications looked good rather. But anything getting redirected to the WAE would get dropped.
I don't have a chance right now to change IOS back to one of the non-working versions to get all of the info. but I will try soon. Unfortunately, the site is where my executives reside and it's always a tough situation to do anything there most of the time.
And to answer your question about having another configuration in place working .... yes I do. I have another 2851 with 12.4(24)T3, same WAE model with WAE-4.1.7 code and everything configured the same including connections as the site that isn't working. The only difference as mentioned before is that this working site router is running SP feature set which I know shouldn't matter but I didn't try a SP feature set however I went through ADV IP, ADV ENTER, and IP VOICE and neither worked with 2 different 12.4(X)Tx versions. I was grasping at straws at this point.
I figured I was going to need to get TAC involved when I could spare some time to run one of the non-working IOS images and could afford to not have WAAS working for the site but was hoping one of you guys might have seen something like this and could offer something to try to fix the issue. It is very odd indeed. I have other 28xx routers and all of the upgrades worked that aren't 2851's.
I'll post more info. when I can.
Thanks again!
Wayne

Aironet 1300 AG IOS upgrade

could somebody give me a doc with the steps to perform an IOS upgrade for the APs
thank you

Hi Cris,
Working with Software Images
This section describes how to archive (download and upload) software image files, which contain the system software, IOS code, radio firmware, and the web management HTML files.
Cisco IOS Software Configuration Guide for Cisco Aironet 1300 Series Outdoor Access Point/Bridge 12.3(7)JA
http://www.cisco.com/en/US/docs/wireless/access_point/1300/12.3_7_JA/configuration/guide/b37mfw.html#wp1035507
Hope this helps!
Rob

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!

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.

IPAD Mini Locked after iOS upgrade, tried reset on iPAD did not work, plugged in and device not appearing in iTUNEs for reset/restore

PAD Mini Locked after iOS upgrade, tried reset on iPAD did not work, plugged in and device not appearing in iTUNEs for reset/restore. Just get an Apple Logo then a flashing blue screen as if it is caught booting up. This has happened twice before and iTunes restore fixed it. But this time device not appearing in iTunes.
Running iTunes for PC. But as stated restore has worked before! Any help greatly appreciated!!

Place the device in DFU mode and let iTunes restore the device to factory condition.

Why are the calendars on my Mac no longer syncing with my iPhone and/or my iPad since the last IOS upgrade?

Since installing the IOS upgrade, it seems impossible to sync the calendar(s) on my iMac (via the cloud OR via cable) with my iPhone 4 or my iPad (last generation).
Any thoughts?

What happens when you try to sync? Error messages?

Cisco CISCO2921/K9 IOS Upgrade

Similar Messages

Maybe you are looking for