5508 WLC Upgrade steps

Single 5508 WLC with 8 x 1142 APs.
5508 is running FUS 1.3, software version 7.0.116.0, field recovery image 6.0.182.0.
I need to bring the software version up to at least 7.2.115 to support 2 new 2602 AP i need to install.
Question is; do I install FUS 1.9 then update my controller to 7.6.120 or do I need to do any intermediate steps?
This is my first time upgrading a WLC so I'm fresh and this is a production WLC.
Cheers

Hi Fisher.
Normally It doesn't matter as long as you get it done but make sure that you reboot the WLC before doing the next. 
Here is the procedure for FUS upgrade:
http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/fus_rn_OL-31390-01.html
WLC Software upgrade Procedure:
http://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/68835-wlc-upgrade.html
Regards
Dont forget to rate helpful posts

Similar Messages

  • 5508 WLC upgrade

    Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
    We are currently running an older code  6.0.196.0
    Are there any issues that I need to worry about with this upgrade ?
    Do I need to upgrade the AP's at the same time ?
    Any help would be appreciated.
    Cheers
    Dave

    Looking to upgrade our 5508 WLC to the newest code AIR-CT5500-K9-7-2-103-0-FUS
    Is the WLC going to be used in RUSSIA?  That's what this code is for.  If not, use the "AIR-CT5500-K9-7-2-103-0.aes" file instead.
    Do I need to upgrade the AP's at the same time ?
    The WLC will do it for you.

  • 5508 WLC Upgrade from 7.0.116 to 7.2.111.3

    I am planing to upgrade 2 of my 5508 series WLC from 7.0.116 to version 7.2.111.3.  I understand that legacy AP's are no longer supported.  Is there any other issues I should be aware of that others have experienced?  Is the upgrade straight-forward just like other code upgrades?  Thank you.

    Thanks so much for all the information.  Afterr reading throught this, it makes sense now.  I do have one more question. After doing a show sysinfo on these controllers, it does look like the FUS does need to be updated.  Should I perform this before I upgrade to version 7.2 code, or after I have peformed the upgrade to 7.2, or does it matter?
    (Cisco Controller) >show sysinfo
    Manufacturer's Name.............................. Cisco Systems Inc.
    Product Name..................................... Cisco Controller
    Product Version.................................. 7.0.116.0
    Bootloader Version............................... 1.0.1
    Field Recovery Image Version..................... 6.0.182.0
    Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
    Build Type....................................... DATA + WPS

  • WLC 5508 Fus upgrade

    Hi,
    I have few 5508 controlers with 7.0.116.0 version and i decided to upgrade to 7.4. I did an upgrade of software and FUS (
    AIR-CT5500-K9-1-7-0-0-FUS.aes) on three of them without any problems. But on the last one i cannot upgrade fus image.. I dowload code from tftp server, wlc checks image and ask for reload for changes to take effects. After reboot it still has old fus installed :/ I have no access to console to see if there are any errors during the reboot. Is there any way of troubleshooting?
    Thanks

    Hi Ad,
    same exact image is being used for all WLCs upgrade? or this is a different one (downloaded separately)?
    Rating useful replies is more useful than saying "Thank you"

  • How to Upgrade (legacy setup) 5508 wlc in HA

    How to Upgrade 5508 wlc in HA (both the WLC with permanant AP license only, i.e, without HA license).
    As per 
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/7-5/High_Availability_DG.pdf
    Both the WLCs have a valid AP Count license
    • The CLI should be used to configure one WLC as the Standby WLC (as mentioned in the
    configuration section) provided it satisfies the requirement of minimum permanent license count.
    This condition is only valid for the 5500 WLC, where a minimum of 50 AP Permanent licenses are
    needed to be converted to Standby. There is no restriction for other WLCs such as the WiSM2, 7500,
    and 8500.
    • AP-count license information will be pushed from Active to Standby.
    • In the event of a switchover, the new Active WLC will operate with the license count of the previous
       Active WLC and will start the 90-day countdown.
    • The WLC configured as Secondary will not use its own installed license, and only the inherited
       license from the active will be utilized.
    • After 90-days, it starts nagging messages. It will not disconnect connected APs.
    • With the new WLC coming up, HA SKU at the time of paring will get the AP Count:
    – If the new WLC has a higher AP count than the previous, the 90-day counter is reset.
    – If the new WLC has a lower AP count than the previous, the 90-day counter is not reset.
    – After switchover to a lower AP count, the WLC offset timer will continue and nagging messages 
       will be displayed after time expiry.
    My query is:
    How can we upgrade the WLC version in this scenatio (where both the WLC have only permanent
    AP License and not the HA license), Is it the same as done with HA controller or some othe procedure?
    Pls comment.

    Thanks Freerk for the comments, 
    But my query is, What would be the procedure for image upgradation after configuring HA between both the controllers (Primary-Secondary).
    Will it be same as with the Primary-HA controller, or do i've to upgrade them individually and
    re-configure HA again.

  • 5508 WLC license upgrade ?

    Looks like my 5508 WLC came with base license of 25 ap's and I need to exceed that.
    Is this something I can purchase thru Cisco indirectly thru a vendor ?
    Do I need a license to exceed the 25 ap's ?
    Cheers
    Dave

    The part number for the adder license can be found in this doc.
    http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps10315/data_sheet_c78-521631.html
    Thanks,
    Scott Fella
    Sent from my iPhone

  • Cisco ACS 5.5 with 5508 WLC.

    Our current environment consists of 5508 WLCs authenticating to ACS 4.2.
    I'm in a process of doing a clean build of ACS 5.5 (vmware) to replace the 4.2 installations. I do not want to migrate.
    I have basic administration & Lobby Ambassador logins working. I now want to configure Layer 3 web auth for wireless access off Windows Domain accounts. I've found a document that discusses this, step by step, but it's for ACS 4.2 (which I know how to build), but nothing seems handy for ACS 5.5. Can anyone point me in that direction?
    Thanks.

    Are you using plain vanilla 5.0 or have any patches installed?
    ACS 5.1 has new TACACS related functionaity including support for custom services and attributes. If these are needed for WLC support yo would need ti upgrade.
    There may also have been relevant patch fixes since 5.0 timeframe but I can't find any specific relevant CDETS at this point

  • Clients unable to connect and get DHCP - LAP1142N AP and 5508 WLC

    Hi,
    I have 19 locations, each with 1 or more LAP1142N AP's in FlexConnect mode, AP's are primed using CAPWAP to my 5508 WLC at the datacenter. The AP's join the WLC without issue every time. I have two WLAN's, one guest and one staff, the guest network is open and obtains DHCP from a WatchGuard XTM33 firewall at each of the remote locations. The staff side is WPA2/RADIUS and DHCP is assigned from the WLC. Each AP is assigned a static IP that is not in the DHCP scope. For example: DHCP scope on the branch firewall is 192.168.1.10-250 the AP will be assigned static IP of 192.168.1.1.. The AP's are connected to a HP procurve switch that has a untagged VLAN, the firewall is using the native vlan 1 and so is the AP.
    I have been running this network for over a year and it has not had a single issue until the last two weeks. Nothing on the network has changed or has been upgraded.
    Now for the issue: The issue I am seeing is that clients are no longer able to connect to the AP and do not get DHCP assigned to them. I am able to get it working, if I remove the static IP from the AP, the AP will reboot, join the controller, then begin working, users can connect and DHCP is assigned from the firewall as it should. However, If the AP then reboots, the AP will join back to the controller but no clients can connect nor do they get a DHCP address. So, I then reassign a static IP to the AP again and it reboots, connects to the controller and clients then can connect and get DHCP.
    Attached is a running config from one of the APs
    I've found several posts on this topic, in fact the patch of unassigning or reassigning static IP is one that I found. However, I wanted to post this to see if there is any further assistance I can get on this. I am also waiting on my SmartNet to start up and will be contacting Cisco support as well.
    Thanks for any help.

    Alright, so I finally figured out the issue with this. I had a Mobility Anchor set on the guest WLAN and once I removed that all started working again.
    What is Mobility Anchor?
    A. Mobility Anchor, also referred to as Guest tunneling or Auto Anchor Mobility, is a feature where all the client traffic that belongs to a WLAN (Specially Guest WLAN) is tunneled to a predefined WLC or set of controllers that are configured as Anchor for that specific WLAN. This feature helps to restrict clients to a specific subnet and have more control over the user traffic. Refer to the Configuring Auto-Anchor Mobility section of Cisco Wireless LAN Controller Configuration Guide, Release 7.0 for more information on this feature.

  • AIR-CAP3702I booting up in mesh mode and not joining our 5508 WLC

    I have a batch of 30+ AIR-CAP3702I-A-K9 APs that I need to setup but none of them are joining to the 5508 WLC and when I connect a console cable and view the output from the AP it shows that it is trying to initiate in mesh mode. I have read other forums that are showing that I need to put in the APs MAC address to a filter list on the WLC for it to show up and then I will be able to change it from mesh mode to local mode. The only issue I'm having with that solution is not knowing how it will affect my current production environment off of that 5508 WLC. I have 69 active production APs with clients working off them and there are no MAC filters currently in place on the WLC. By adding a MAC filter entry for the new APs would the WLC create an implicit deny for all other clients that don't have their MAC addresses entered?? If so is there another work around? Can the mode be changed via the CLI on the AP itself to make it local instead of mesh? 

    sh capwap client rcb
    AdminState                  :  ADMIN_ENABLED
    SwVer                       :  7.6.1.118
    NumFilledSlots              :  2
    Name                        :  AP88f0.4290.7184
    Location                    :  default location
    MwarName                    :  xxxxx
    MwarApMgrIp                 :  x.x.x.x !<it has the correct name and IP of the WLC>
    MwarHwVer                   :  0.0.0.0
    ApMode                      :  Bridge
    ApSubMode                   :  Not Configured
    OperationState              :  JOIN
    CAPWAP Path MTU             :  576
    LinkAuditing                :  disabled
    ApRole                      :  MeshAP
    ApBackhaul                  :  802.11a
    ApBackhaulChannel           :  0
    ApBackhaulSlot              :  2
    ApBackhaul11gEnabled        :  0
    ApBackhaulTxRate            :  24000
    Ethernet Bridging State     :  0
    Public Safety State         :  disabled
    AP Rogue Detection Mode     :  Enabled
    AP Tcp Mss Adjust           :  Disabled
    AP IPv6 TCP MSS Adjust      :  Disabled
    Predownload Status          :  None
    Auto Immune Status          :  Disabled
    RA Guard Status             :  Disabled
    Efficient Upgrade State     :  Disabled
    Efficient Upgrade Role      :  None
    TFTP Server                 :  Disabled
    Antenna Band Mode           :  Unknown
    802.11bg(0) Radio
    ADMIN  State =  ENABLE [1]
    OPER   State =    DOWN [1]
    CONFIG State =      UP [2]
    HW     State =      UP [4]
      Radio Mode                : Bridge
      GPR Period                : 0
      Beacon Period             : 0
      DTIM Period               : 0
      World Mode                : 1
      VoceraFix                 : 0
      Dfs peakdetect            : 1
      Fragmentation Threshold   : 2346
      Current Tx Power Level    : 0
      Current Channel           : 11
      Current Bandwidth         : 20
    802.11a(1) Radio
    ADMIN  State =  ENABLE [1]
    OPER   State =    DOWN [1]
    CONFIG State =      UP [2]
    HW     State =      UP [4]
      Radio Mode                : Bridge
      GPR Period                : 0
      Beacon Period             : 0
      DTIM Period               : 0
      World Mode                : 1
      VoceraFix                 : 0
      Dfs peakdetect            : 1
      Fragmentation Threshold   : 2346
      Current Tx Power Level    : 1
      Current Channel           : 165
      Current Bandwidth         : 20
    It is showing the following error on our WLC in the log file:
    Tue Jul 15 14:01:26 2014
    AAA Authentication Failure for UserName:88f042907184 User Type: WLAN USER
    And here are some of the errors it's showing on the AP after bootup:
    *Jul 15 17:47:30.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
    *Jul 15 17:47:31.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jul 15 17:47:31.031: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jul 15 17:47:31.039: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Jul 15 17:47:31.047: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Jul 15 17:47:32.067: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jul 15 17:47:33.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Jul 15 17:47:35.471: %CAPWAP-5-SENDJOIN: sending Join Request to x.x.x.x
    *Jul 15 17:47:35.471: %DTLS-5-ALERT: Received WARNING : Close notify alert from x.x.x.x
    *Jul 15 17:47:35.475: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to down
    *Jul 15 17:47:35.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Jul 15 17:47:36.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Jul 15 17:47:36.503: %LINK-6-UPDOWN: Interface Dot11Radio0, changed state to up
    *Jul 15 17:47:37.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
    *Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Jul 15 17:48:15.007: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Jul 15 17:48:15.007: %MESH-6-LINK_UPDOWN: Mesh station 88f0.4290.7184 link Down
    *Jul 15 17:48:17.007: %LINK-6-UPDOWN: Interface BVI1, changed state to down
    *Jul 15 17:48:22.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to down
    *Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: Invalid event 31 & state 4 combination
    *Jul 15 17:59:10.099: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 31, state 4

  • 5508 WLC HA pair - change management interface settings

    Hi,
    We have a pair of 5508 WLC's in a HA configuration that is working well at the moment, however I have noticed that the management interface is configured as untagged. I would like to change this to tagged and change the attached switch to trunk for these devices but if I try and edit the management interface through the GUI the VLAN and IP address section is greyed out and cannot be changed. While I could attempt it through the CLI and am comfortable doing that, the fact that it cannot be changed through the GUI implies that this should not be changed and so I am after further information. I don't have any lab equipment other than the HA pair in production so I cannot try changing it through the CLI at the moment. 
    The WLC's are in LAG mode if that makes any difference. I realise there may be downtime required for making this change but I am trying to work out the steps to get this done without having to drastically reconfigure things. 
    Any assistance would be appreciated. 

    Introduction of New Interfaces for HA Interaction
    Redundancy Management Interface
    The IP address on this interface should be configured in the same subnet as the management interface. This interface will check the health of the Active WLC via network infrastructure once the Active WLC does not respond to Keepalive messages on the Redundant Port. This provides an additional health check of the network and Active WLC, and confirms if switchover should or should not be executed. Also, the Standby WLC uses this interface in order to source ICMP ping packets to check gateway reachability. This interface is also used in order to send notifications from the Active WLC to the Standby WLC in the event of Box failure or Manual Reset. The Standby WLC will use this interface in order to communicate to Syslog, the NTP server, and the TFTP server for any configuration upload.
    Redundancy Port
    This interface has a very important role in the new HA architecture. Bulk configuration during boot up and incremental configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure, the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).

  • WLC Upgrade - FUS Upgrade

    Greetings,
    I am planning on upgrading our redundant 5508 WLC’s from v.7.3.112.0 to v.7.4.110.0 this weekend. One thing I noticed in the release notes of 7.4 is the guideline to update the Field Upgrade Software to v. 1.7.0.0-FUS.
    My question is should this FUS be upgraded before or after I upgrade the WLC to 7.4? On the release notes it does state a FPGA error on the does occur on the 5500 series controllers.
    http://www.cisco.com/en/US/docs/wireless/controller/release/notes/fus_rn_1_7_0_0.html#wp45499
    On a Cisco 5500 Series Controller, it is observed that the controller sporadically reboots (due to a defect CSCtr39523) and displays the following FPGA error message:
    fpga: Lost heartbeat from Environment controller, system will reboot in 5 seconds!!!
    A crash file is not created to debug or troubleshoot the error.
    You can resolve this issue by installing the FUS image. Please see Resolved Caveats for more details.
    Thanks,
    Robert

    Honestly, it doesn't really matter the ordr you upgrade in.
    Though, I tend to update the FUS before the image.
    HTH,
    Steve
    Please remember to rate useful posts, and mark questions as answered

  • WLC upgrade due to Advisory

    Hi,
    We have a 5508 WLC running 7.2.110.0 and need to upgrade according to the advisory released today.
    It seems we have three upgrade choices:
    7.2.110.0 to 7.2.111.3
    7.2.110.0 to 7.3.110.0
    7.2.110.0 to 7.4.x
    I've not upgraded one of these 5508's before, but if they are anything like ASAs then I need to be careful.
    Can anyone advise if upgrading from our current version to 7.4 requires planning. Same for 7.3.
    How will the WLC upgrades affect the APs (3502i) ?
    How does one recover from a failed upgrade on these WLCs?
    Thanks.

    WLC version 7.4.100 will need Prime Infrastructure Version 1.3 to be managed, but Version 1.3 is not yet available to download at this time.
    Huh? What is Prime Infrastructure and why do I need it?

  • 4500 R+E with sup 8 vs. (3850 stack + 5508 WLC)

    I got into discussion about upgrade our 3750 stack, 4404 WLC, less than 50 APs (APs spread out over MPLS WAN). I'm planning to get 4510 R+ E with 2 sup 8, but another opinion talked me down to 3850 stack with 5508 WLC. Basically, his argument is 3850 stack can do everything 4500 R+E can do, plus it's not hulky as 4500. My argument is I like unify access since sup 8 built in WLC and we don't have to get 5508. I know there're more 4500 R+E and respect his argument. Does anyone has input on these setup giving pricing is not much different between setup.
    Thanks
    Kevin

    In my honest opinion, if you are posted this solution here, you are smelling something is off.  I hate to be a bearer of bad news.  It is.  
    We went through the same exercise 2 years ago.  We wanted to upgrade our legacy 3750/3750G to 3750X and we found out that if we were to get a stack of four (or more ) 3750X, it is cheaper (much, much cheaper) to get a 4510R+E bundle (with Sup7E included) and associated line cards on top.  Just to note, the 3750X and 3850 have the same price.  The Sup7E and Sup8E have the same price.  
    Don't ask me why your consultant wanted you to get 3850.  I am refraining myself putting two theories in here.

  • ASU-process POST Upgrade Step on SQL database

    Hi All,
    To check this message in the right format kindly click on reply first then click on quote original icon ("").
    I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
    This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
    Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
    IS-OIL Application Test 600                                                 Optional          
    KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
    CGPL: Entries are blank after upgrade                                                Obligatory          
    Error handling of task group execution                                Optional          
    Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
    Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
    Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Convert customizing for warehouse funds ctr scenarios     Optional          
    Various problems classification commitment items (class type     Obligatory          
    Unauthorized error messages udring fiscal year change/reassi     Obligatory          
    RFFMUDX1 migrates incomplete budgeting tables                          Obligatory          
    Non-7bit-ASCII character used for BCS key figures             Obligatory          
    Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory          
    BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory          
    BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory          
    Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory          
    Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
    Activating VMC for the Internet Pricing and Configurator     Obligatory          
    Customer specific BSEG-fields not transferred                  Optional          
    Conversion of report headers in drilldown-reporting            Optional                                   600
    IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
    ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
    Conversion of CO-Total-Tables                                              Obligatory     46C                      500
    Conversion of CO-line-item table COEP                                Obligatory     46C                       600
    New General Ledger, problems in CO-documents                 Obligatory                               500
    No receivers found in allocations                                          Obligatory     46C                        470
    Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
    Migration of process parameters in recipe management     Optional     110                        600
    FAQ new depreciation calculation                                        Optional                                600
    Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
    Reloading Table T512W                                                        Optional          
    Converting Short Texts                                                         Obligatory          
    Migrating Data                                                                         Optional     4.7     
    Activating SAP ECC Extensions                                          Optional          
    I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
    Please suggest me, how to proceed and what to do. please guide if i skip this step now and later  on I apply latest SP than still I need to do all this.
    Regards
    Vinay

    Hi All,
    I also faced a similar issue during upgrade. Some useful findings.
    1. Only super user can access this /n/ASU/START
    2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
    3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
    4.  Execute all the checks /n/ASU/UPGRADE
    5. This surely can be skipped, but not advisable.
    regards,
    Amit

  • Upgrade step ASU-process post upgrade step

    Hi All,
    To check this message in the right format kindly click on reply first then click on quote original icon ("").
    I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
    This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
    Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
    IS-OIL Application Test 600                                                 Optional          
    KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
    CGPL: Entries are blank after upgrade                                                Obligatory          
    Error handling of task group execution                                Optional          
    Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
    Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
    Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Convert customizing for warehouse funds ctr scenarios     Optional          
    Various problems classification commitment items (class type     Obligatory          
    Unauthorized error messages udring fiscal year change/reassi     Obligatory          
    RFFMUDX1 migrates incomplete budgeting tables                          Obligatory          
    Non-7bit-ASCII character used for BCS key figures             Obligatory          
    Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory          
    BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory          
    BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory          
    Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory          
    Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory          
    Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
    Activating VMC for the Internet Pricing and Configurator     Obligatory          
    Customer specific BSEG-fields not transferred                  Optional          
    Conversion of report headers in drilldown-reporting            Optional                                   600
    IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
    ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
    Conversion of CO-Total-Tables                                              Obligatory     46C                      500
    Conversion of CO-line-item table COEP                                Obligatory     46C                       600
    New General Ledger, problems in CO-documents                 Obligatory                               500
    No receivers found in allocations                                          Obligatory     46C                        470
    Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
    Migration of process parameters in recipe management     Optional     110                        600
    FAQ new depreciation calculation                                        Optional                                600
    Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
    Reloading Table T512W                                                        Optional          
    Converting Short Texts                                                         Obligatory          
    Migrating Data                                                                         Optional     4.7     
    Activating SAP ECC Extensions                                          Optional          
    I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
    Please suggest me, how to proceed and what to do. please guide if i skip this step now and later  on I apply latest SP than still I need to do all this.
    Regards
    Vinay
    Edited by: Vinay Paul on Sep 11, 2009 10:11 PM

    Hi All,
    I also faced a similar issue during upgrade. Some useful findings.
    1. Only super user can access this /n/ASU/START
    2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
    3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
    4.  Execute all the checks /n/ASU/UPGRADE
    5. This surely can be skipped, but not advisable.
    regards,
    Amit

Maybe you are looking for