IOS upgradation on 6513 switch

hi everyone! plz help me to upgrade the IOS of 6513 swich. Recent IOS version is 12.2(18)SXF7. I have two sup engines 720 series.

I am sure no one here will recommend that you upgrade to a specific IOS unless you really need to. Even more, no one will also recommend an upgrade without testing the firmware in a test environment.
I will not be able to answer your question but I will urge you to take it upon yourself to test the firmware and/or read the release notes for any potential pitfalls you might encounter.
You can also do some research through Cisco's Software Advisory and Bug Traq.

Similar Messages

No valid license found after IOS upgrade on C3750x switch

HI,
Two switches below are working fine as a stack with IOS c3750e-universalk9-mz.122-55.SE5.bin & ipbase license.
Switch#1 (Master, WS-C3750X-24P-S)
Switch#2 (Member, WS-C3750X-24P-S)
After IOS Upgrade to c3750e-universalk9-mz.150-2.SE7.bin, The stack was broken. Switch#2 didn’t recognise valid ipbase license with new IOS and came up with lanbase license instead. Therefore stack cannot be composed due to license mismatch between Switch#1 (ipbase) and switch#2(lanbase).
I’m wondering why Switch#2 didn’t recognise ipbase license with new IOS even though IPASE is running well with previous IOS.
Here is excerpt from “show version” with 15.x image on Switch#2.
License Level: lanbase
License Type: Default. No valid license found.
Next reload license Level: lanbase
Here is excerpt from “show version” with 12.x image on Switch Stack.
License Level: ipbase
License Type: Permanent
Next reload license Level: ipbase
Thanks
Jeong

Thanks guys,
I have fixed the issue by configuring 'license boot level ipbase' on the member switch#2. The switch recognised IPBASE license well and joined the stack successfully.

How can i upgrade system IOS images of routers, switches and firewalls

Hi,
I am very much surprised and less of understanding yet how Cisco's licensing program or IOS upgrades are done. I have many routers, switches & ASA's of whom i wan to upgrade the IOS's but i cannot do so. How ever i can download those images from internet but i want to know how can i do this from Cisco as i don't want to trust those IOS's available over internet.
As per my study what i have found that i need to have Cisco Service Contract number for that devices so that i can download updated IOS Images for them.
Someone kindly explain what are the best methods for the above requirements.
Regards
@Mohammed

You're correct regarding a service contract. Cisco calls this Smartnet support. It includes both hardware support (i.e. returns for failed hardware), software support (including right to download and upgrade your software) and technical assistance (via the Cisco TAC). Smartnet is charged separately for each covered device. Once you have it, your cisco.com userid needs to be associated with your service contract number. Doing that will then allow you to download the software from cisco.com. (There are some very limited cases in which you don't have to have a support contract - mostly when there is a security advisory (PSIRT) indicating the Cisco software was flawed as it was initially released.)
Every product (or product family) has a product support page on cisco.com. That page includes release notes, configuration guide, users guides, and a link to software downloads for that product. Start by reading the release notes and determining which (if any) upgrade is appropriate for your product. Then you can download and upgrade the software as necessary.

Switch stack IOS upgrade

Hi,
I am planning on upgrading a 3750x switch stack to a slightly newer version.
My question is, would I have to load the new image onto each switch in the stack or just the master?
Thanks,
Waqas

I am planning on upgrading a 3750x switch stack to a slightly newer version
Specify the IOS so we can determine if you are going to a bad IOS version.
My question is, would I have to load the new image onto each switch in the stack or just the master?
1. Download the IOS file with the TAR filename from the Cisco website.
2. Compare the MD5 hash value of this file against the one in the Cisco website. The MD5 hash value must match.
3. Use the command to upgrade your IOS: archive download-sw /destination N tftp:///IOS.tar
NOTE: /destination N - The "N" means the switch members in a stack. If you have three switches in a stack then you use /destination 1 /destination 2 /destination 3.

Cisco switch ios upgradation

how can I upgrade cisco 2960s switch's ios.
what commands will be used for it

Hello Anupam,
1. You need to copy the IOS from CCO.
2. The same IOS needs to copied on to the flash.
#copy tftp : flash
#tftp ip address <x.x.x.x>
3. I would suggest before upgrading the IOS. Please verify the MD5 checksum and confirm with CCO that it matches. This confirms that while copying the image didnt get corrupt.
#verify /md5 Flash:<IOSimage>.bin
4. Once you see the IOS in flash. Please configure below.
boot-start-marker
boot system flash <IOS image name>.bin
boot-end-marker
5. Save the confguration.
#wr
6. reload the router. Post reload you can run " show version" to check if device has come up with new IOS.
HTH,
Nikhil

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.

WS-X6816-GBIC became PwrDown when IOS upgrade to 12.2(18)SXD7

When IOS upgraded from 12.1(13)E8 to 12.2(18)SXD7, one of WS-X6816-GBIC module (in slot5) become PwrDown in show module output but another one (in slot 4) is ok. The only difference I can find is DFC hardware version. Is there any limitation about this ?
IOS 12.2(18)SXD7
------------------ show module ------------------
Mod Ports Card Type Model Serial No.
1 2 Catalyst 6000 supervisor 2 (Active) WS-X6K-SUP2-2GE SAL0752RJBZ
4 16 Pure SFM-mode 16 port 1000mb GBIC WS-X6816-GBIC SAD05050HGC
5 16 Pure SFM-mode 16 port 1000mb GBIC WS-X6816-GBIC SAL08186B80
6 0 Switching Fabric Module-136 (Active) WS-X6500-SFM2 SAL0708DF8W
8 0 2 port adapter FlexWAN WS-X6182-2PA SAD073900JL
Mod MAC addresses Hw Fw Sw Status
1 0009.1246.eba8 to 0009.1246.eba9 5.0 7.1(1) 12.2(18)SXD7 Ok
4 0030.f271.1972 to 0030.f271.1981 1.7 12.1(11r)E2 12.2(18)SXD7 Ok
5 000f.f780.2420 to 000f.f780.242f 1.7 Unknown Unknown PwrDown
6 0001.0002.0003 to 0001.0002.0003 1.4 6.1(3) 8.3(0.156)RO Ok
8 000d.650a.15c0 to 000d.650a.15ff 1.6 12.2(18)SXD7 12.2(18)SXD7 Ok
Mod Sub-Module Model Serial Hw Status
1 Policy Feature Card 2 WS-F6K-PFC2 SAL0752RKWF 3.4 Ok
1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0752RB28 2.6 Ok
4 Distributed Forwarding Card WS-F6K-DFC SAL08249SUD 2.5 Ok
5 Distributed Forwarding Card WS-F6K-DFC SAL081971W0 2.7 PwrDown
Mod Online Diag Status
1 Pass
4 Pass
5 Unknown
6 Pass
8 Pass
The early show module output;
IOS 12.1(13)E8
TANET_PTC_R6K#sh module
Mod Ports Card Type Model Serial No.
1 2 Catalyst 6000 supervisor 2 (Active) WS-X6K-SUP2-2GE SAL0752RJBZ
4 16 Pure SFM-mode 16 port 1000mb GBIC WS-X6816-GBIC SAD05050HGC
5 16 Pure SFM-mode 16 port 1000mb GBIC WS-X6816-GBIC SAL08186B80
6 0 Switching Fabric Module-136 (Active) WS-X6500-SFM2 SAL0708DF8W
8 0 2 port adapter FlexWAN WS-X6182-2PA SAD073900JL
Mod MAC addresses Hw Fw Sw Status
1 0009.1246.eba8 to 0009.1246.eba9 5.0 6.1(3) 7.5(0.6)HUB1 Ok
4 0030.f271.1972 to 0030.f271.1981 1.7 12.1(11r)E2 12.1(13)E8, Ok
5 000f.f780.2420 to 000f.f780.242f 1.7 12.1(11r)E2 12.1(13)E8, Ok
6 0001.0002.0003 to 0001.0002.0003 1.4 6.1(3) 7.5(0.6)HUB1 Ok
8 000d.650a.15c0 to 000d.650a.15ff 1.6 12.1(13)E8 12.1(13)E8 Other
Mod Sub-Module Model Serial Hw Status
1 Policy Feature Card 2 WS-F6K-PFC2 SAL0752RKWF 3.4 Ok
1 Cat6k MSFC 2 daughterboard WS-F6K-MSFC2 SAL0752RB28 2.6 Ok
4 Distributed Forwarding Card WS-F6K-DFC SAL08249SUD 2.5 Ok
5 Distributed Forwarding Card WS-F6K-DFC SAL081971W0 2.7 Ok

Watch the logs as it boots up , my guess there is a problem with the board . We had a brand new card for a 6500 with a problem and the box will power it off if it see's a problem. Ended up RMA'ing the card . Does it show anything when you do a "show diagnostic result all" command ?

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.

Multiple IOS upgrade

Hello Cisco Gurus,
We are currently buying Cisco equipment in bulk. It's all used, so the IOS is slightly out of date (12.1 for the routers) and needs to be updated. I was wondering if there is a way to upgrade multiple routers/switches at the same time. The only way that I know how to do an upgrade is through the console cable using something like Hyperterminal which only does one at a time and takes about 3 hours each.
Any help offered is much appreciated.
Gary

You can deploy devices in your network and so use TFTP procedure to upgrade IOS:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1828/prod_release_note09186a00800810f3.html
You can also use the command boot tftp://ip_address/file_image.bin:
boot
To boot the router manually, use the boot ROM monitor command. The syntax of this command varies according to the platform and ROM monitor version.
boot
boot file-url
boot filename [tftp-ip-address]
boot flash [flash-fs:][partition-number:][filename]
Cisco 7000 Series, 7200 Series, 7500 Series Routers
boot flash-fs:[filename]
Cisco 1600 and Cisco 3600 Series Routers
boot [flash-fs:][partition-number:][filename]
Syntax Description
file-url
URL of the image to boot (for example, boot tftp://172.16.15.112/routertest).
filename
When used in conjunction with the ip-address argument, the filename argument is the name of the system image file to boot from a network server. The filename is case sensitive.
When used in conjunction with the flash keyword, the filename argument is the name of the system image file to boot from Flash memory.
On all platforms except the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family routers, the system obtains the image file from internal Flash memory.
On the Cisco 1600 series, Cisco 3600 series and Cisco 7000 family routers, the flash-fs: argument specifies the Flash memory device from which to obtain the system image. (See the flash-fs: argument later in this table for valid device values.) The filename is case sensitive. Without the filename argument, the first valid file in Flash memory is loaded.
tftp-ip-address
(optional) IP address of the TFTP server on which the system image resides. If omitted, this value defaults to the IP broadcast address of 255.255.255.255.
flash
Boots the router from Flash memory. Note that this keyword is required in some boot images.
flash-fs:
(Optional) Specifying the Flash file system is optional for all platforms except the Cisco 7500 series routers. Possible file systems are:
•flash:—Internal Flash memory on the Cisco 1600 series routers and Cisco 3600 series routers. This is the only valid Flash file system for the Cisco 1600 series routers.
•bootflash:—Internal Flash memory on the Cisco 7000 family.
•slot0:—Flash memory card in the first PCMCIA slot on the Cisco 7000 family and Cisco 3600 series routers.
•slot1:—Flash memory card in the second PCMCIA slot on the Cisco 7000 family and Cisco 3600 series routers.
partition-number:
(Optional) Specifies the partition number of the file system the file should be loaded from. This argument is not available on all platforms.
In latest releases there is an IOS auto upgrade function but requires 12.4 IOS alredy installed.

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?

Ios upgrade stopped my external hard drives and keep changing my laptop keyboards

Latest ios upgrade stopped my computers from contacting and saving in my external hard drives and keeps changing my laptop keyboards everytime I turn it on. Please Apple solve this because I know that many people suffer from this. If you do not I will stop my almost 30 year old use of Apples.

iOS has nothing to do with devices connected to your computer. It also has nothing to do with your keyboard. What have you done and when?
Barry

IOS upgradation on 6513 switch

Similar Messages

Maybe you are looking for