Nexus 7010 upgrade path

We currently have two Nexus 7010 with 5.0(2a) as system images.
We would need to know the correct upgrade path to 6.1(1). On the release notes it reads the path is from 4.2(8), 5.0(5) or 5.1(6) to 5.2(5) then to 6.1(1).
Also if ISSU is possible or, because we may need to upgrade EPLD, if there is no upgrade path to do a non-disruptive upgrade.

You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

Similar Messages

  • Cisco Nexus 5548UP upgrade path

    Hi,
       I'm planning to upgrade Nexus 5548UP (no L3 services) from 5.2(1)N1(6)  to 7.0(5)N1(1). Is this upgrade path vaild? or is there any intermediate version; also advise if ISSU is possible.
    Regards,
    Navin RK

    Hi,
    Yes you can upgrade directly from 5.2(1)N1(6) to 7.0(5)N1(1).  ISSU is possible, provided you meet the requirements.  You can copy the kickstart and system image to bootflash, then run the "show install all impact" command to see whether or not ISSU will be possible with your configuration.
    Here is a document supporting the statements above: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5500/sw/upgrade/705_N1_1/n5500_upgrade_downgrade_700.html#pgfId-640981

  • Nexus 7010 Upgrade to 6.2(6)

    We recently discovered that due to an issue with Netflow ingress/DHCP Relay on the same interface, we are going to have to upgrade to 6.2(6)
    In the release notes, I do not see anything specific about ISSU from 6.2(2a) to 6.2(6) but I am assuming that an ISSU upgrade can be achieved.  Can someone let me know that has performed this upgrade path.

    We did exactly same upgrade from 6.2.2 to 6.2.6 with ISSU; just make sure you don’t have any 
    aclmgr inactive configurations so before ISSU run these two commands on each VDC
    sh run aclmgr inactive-if-config
    clear inactive-config acl
    Also I had one failed upgrade on my first try due MST changes so try to make this when n the network is more quite
    Hope it helps

  • Nexus 7010 Sup2 Upgrade

         I am trying to find the documentation to upgrade my nexus 7010 from SUP1 to SUP2. But I cannot seem to find it. Anyone know where it is hiding?                

    Of corse i find it 5 minutes after posting this.........
    http://www.cisco.com/en/US/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_replacing.html#wp1410535

  • Nexus 7010 fabric extender timing out

    Hello -
    We have a Nexus 7010 and we are testing out using the fabric extenders for a need.  We have a demo 2224 unit and have it connected to our M132XP-12 10G blade in the 7K but the FEX won't come online.  I would have figured a possible software incompatability but looking at the supported list for that as well as hardware everything seems to be in order.  This is what the status shows after it spends about 15 mins in the image download state.
    FEX: 111 Description: FEX0111   state: Offline
      FEX version: 4.2(1)N2(1a) [Switch version: 5.1(2)]
      FEX Interim version: 4.2(1)N2(1a)
      Switch Interim version: 5.1(2)
      Module Sw Gen: 21  [Switch Sw Gen: 21]
    pinning-mode: static    Max-links: 1
      Fabric port for control traffic: Eth2/20
      Fabric interface state:
        Po11 - Interface Up. State: Active
        Eth2/20 - Interface Up. State: Active
      Fex Port        State  Fabric Port  Primary Fabric
    This is looped in the log details until it times out:
    04/25/2011 15:31:41.986978: Module register received
    04/25/2011 15:31:41.987713: Registration response sent
    04/25/2011 15:31:41.987889: Requesting satellite to download image
    04/25/2011 15:32:00.105031: Module register received
    04/25/2011 15:32:00.105779: Registration response sent
    04/25/2011 15:32:00.105956: Requesting satellite to download image
    04/25/2011 15:32:20.191181: Module register received
    04/25/2011 15:32:20.191957: Registration response sent
    04/25/2011 15:32:20.192144: Requesting satellite to download image
    We ran a debug during this and these entries are displayed when looking for errors.
    2011 Apr 25 15:30:31.443745 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:35.472721 fex: Cardinfo: Unknown card id to get (132)
    2011 Apr 25 15:30:35.472753 fex: Reg resp: Failed to get card info for swcardid 132
    2011 Apr 25 15:30:41.495302 fex: Cardinfo: Unknown card id to get (132)
    I'm still doing some more searching which so far hasn't turned up much, wanted to see if anyone has some other insight??
    Thanks!

    Hi Jack -
    Thanks for the response.  Unfortunately, yes that is already complete.  I was hoping that would be an easy fix.  When we upgraded to 5.1(2) we did the 5.1 EPLD.  I ran the install all impact command noted below for the 5.1 EPLD just to make sure it didn't report anything else as needing upgrade.
    sho install all impact epld bootflash:n7000-s1-epld.5.1.1.img
    Compatibility check:
    Module  Type  Upgradable        Impact   Reason
         1    LC         Yes    disruptive   Module Upgradable
         2    LC         Yes    disruptive   Module Upgradable
         5   SUP         Yes    disruptive   Module Upgradable
         1  Xbar         Yes    disruptive   Module Upgradable
         2  Xbar         Yes    disruptive   Module Upgradable
         3  Xbar         Yes    disruptive   Module Upgradable
         1   FAN         Yes    disruptive   Module Upgradable
         2   FAN         Yes    disruptive   Module Upgradable
         3   FAN         Yes    disruptive   Module Upgradable
         4   FAN         Yes    disruptive   Module Upgradable
    Copy complete, now saving to disk (please wait)...
    Retrieving EPLD versions... Please wait.
    Images will be upgraded according to following table:
    Module  Type           EPLD      Running-Version   New-Version  Upg-Required
         1    LC  Power Manager              4.008       4.008           No
         1    LC  IO                         1.006       1.006           No
         1    LC  Forwarding Engine          1.006       1.006           No
         1    LC  SFP                        1.004       1.004           No
         2    LC  Power Manager              4.008       4.008           No
         2    LC  IO                         1.016       1.016           No
         2    LC  Forwarding Engine          1.006       1.006           No
         2    LC  FE Bridge(1)              186.006      186.006           No
         2    LC  FE Bridge(2)              186.006      186.006           No
         2    LC  Linksec Engine(1)          2.006       2.006           No
         2    LC  Linksec Engine(2)          2.006       2.006           No
         2    LC  Linksec Engine(3)          2.006       2.006           No
         2    LC  Linksec Engine(4)          2.006       2.006           No
         2    LC  Linksec Engine(5)          2.006       2.006           No
         2    LC  Linksec Engine(6)          2.006       2.006           No
         2    LC  Linksec Engine(7)          2.006       2.006           No
         2    LC  Linksec Engine(8)          2.006       2.006           No
         5   SUP  Power Manager              3.009       3.009           No
         5   SUP  IO                         3.028       3.028           No
         5   SUP  Inband                     1.008       1.008           No
         5   SUP  Local Bus CPLD             3.000       3.000           No
         5   SUP  CMP CPLD                   6.000       6.000           No
         1  Xbar  Power Manager              2.010       2.010           No
         2  Xbar  Power Manager              2.010       2.010           No
         3  Xbar  Power Manager              2.010       2.010           No
         1   FAN  Fan Controller (1)         0.007       0.007           No
         1   FAN  Fan Controller (2)         0.007       0.007           No
         2   FAN  Fan Controller (1)         0.007       0.007           No
         2   FAN  Fan Controller (2)         0.007       0.007           No
         3   FAN  Fan Controller (1)         0.007       0.007           No
         3   FAN  Fan Controller (2)        0.007       0.007           No
         4   FAN  Fan Controller (1)         0.007       0.007           No
         4   FAN  Fan Controller (2)         0.007       0.007           No

  • Disruptive ISSU 6.1.4a- 6.2.8 on Nexus 7010 sup1 because of LACP timers.

    Hi all.
    The problem.
    Today I updated my Nexus 7010 sup1 from 6.1.4a to 6.2.8.
    I want did it in ISSU mode, but after impact check I got this:
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1       yes  non-disruptive       rolling  
         2       yes  non-disruptive       rolling  
         3       yes  non-disruptive       rolling  
         4       yes  non-disruptive       rolling  
         5       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         6       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         7       yes  non-disruptive       rolling  
         8       yes  non-disruptive       rolling  
         9       yes  non-disruptive       rolling  
        10       yes  non-disruptive       rolling  
    Additional info for this installation:
    Service "lacp" in vdc 1: LACP: Upgrade will be disruptive as 6 switch ports and 0 fex ports are not upgrade ready!!
          Issue the "show lacp issu-impact" cli for more details.
    (modified the impact to <Hitful>  for module <6>)
    Do you want to continue with the installation (y/n)?  [n] y
    I went on with yes and update script reboot both sups after updated all modules.
    It was quite a surprise for me (yes I know I must see word "disruptive" opposite my sups 5 and 6). Because I already had done two ISSU updates on two nexuses (from 5.1.* ->5.2.7 and 5.2.7 -> 6.1.4a) and didn`t have any trouble with LACP timers. Is it a new feature of the 6.* train?
    I have another Nexus that I want to update. And it also has same problem with LACP timers.
    show install all impact give me the same disruptive result because of LACP.
    Can I somehow suppress such ISSU behavior? In case of LACP. I don`t have vPC, just ordinal PC.
    It is a way better if some LACP interfaces flap in process, than an almost 14 minutes of all 7010 chassis reboot that I had.
    Although problem with LACP timers is that they must be the same on the switch side and on the other side. And in case of switches, linux boxes or HP VCs changing LACP timers isn`t a big problem. IT is a biggg problem in case of the Windows Server.
    sh lacp interface ethernet 8/13
    Interface Ethernet8/13 is up
      Channel group is 13 port channel is Po13
    Local Port: Eth8/13   MAC Address= 40-55-39-23-1e-c1
      System Identifier=0x8000,  Port Identifier=0x8000,0x80d
      Operational key=12
      LACP_Activity=active
      LACP_Timeout=Long Timeout (30s)
    Neighbor: 0x1
      MAC Address= ac-16-2d-a4-f2-54
      System Identifier=0xffff,  Port Identifier=0xff,0x1
      Operational key=17
      LACP_Activity=active
      LACP_Timeout=short Timeout (1s)
    They must be the same and equal 30s for successful ISSU

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

  • Nexus 7010 mgmt0 useage opinion

    As a Senior Network Engineer I have entered into a bit of a debate with our Architect about the use of the mgmt0 interfaces on the nexus 7010 switch (dual-sups, M2 and F2 linecards).
    I would like to know opinion of the Cisco support network.
    I believe the mgmt0 interface should left alone for control plane traffic only and Out Of Band management access (ie ssh).  At the moment I have made a subnet for all VDCs with the mgmt0 (vrf management) sitting in a common subnet.  The physical mgmt0 interfaces from both SUPs are connected a management hand off switch.  The mgmt0s also serves as our control plane for VPCs. The VPC peer-link however is using main interfaces of the line-cards.
    The opinions;
    - The Architect thinks we should use all the mgmt0 interfaces for snmp, ntp, tacacs netflow-analysis and switch management.
    - However, I think I should use a traditional Loopback to perform these functions within the linecards.  The mgmt0 should only be used if traditional restricted switch access has failed.
    My Basis;
    the Loopback never goes down, uses multiple paths (the OOB hand off switch could fail closing switch management access completely).  The mgmt0 should be used as a last resort of management access to CMP.
    Thoughts please - Cheers

    I see your point about wanting to mitigate the impact of losing the OOB switch. I don't think the mgmt0 interface going down is considered the level of failure that will trigger a Supervisor switchover though. That's the way I read the Nexus 7000 HA whitepaper (and what I've seen based on some limited experience with taking apart a 7k pair).
    So, no the 7k can't send you an SNMP trap or syslog message if it's configured management path is offline. Mitigation of that could be via your NMS polling the devices's mgmt0 addresses. No response = trouble in paradise. Investigation step would be to log into the 7ks using the loopback IP and local authentication since your TACACS source-interface (mgmt0) is offline and going from there.
    The handful I've built (mostly 5k setups) I go for a Cat 3k switch with dual power supplies as the OOB switch. Once one of those is setup and seen not to be DOA, it's generally going to stay up until someone goes in and uplugs it or initiates a system reload.

  • Nexus 5500 upgrade

    Hi,
    I am planning to upgrade my Nexus 5596 switches and Nexus 2Ks. We are currently running an older version 5.2(1)N1(2).
    What should be the upgrade path to the latest version, or would that be just a one-step upgrade?
    Anything I should be careful about during the upgrade process?
    Thanks

    I have the following "show install impact" output. I see few places of caution. Is there anything I should be concerned about?
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1        no             n/a           n/a  Incompatible image
       101       yes      disruptive         reset  STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
       102       yes      disruptive         reset  STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
       111       yes      disruptive         reset  STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
       112       yes      disruptive         reset  STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
    Images will be upgraded according to following table:
    Module       Image         Running-Version             New-Version  Upg-Required
         1      system             5.2(1)N1(2)             7.0(5)N1(1)            no
         1   kickstart             5.2(1)N1(2)            7.0(5)N1(1a)            no
         1        bios      v3.6.0(05/09/2012)      v3.6.0(05/09/2012)            no
         1      SFP-uC                v1.0.0.0                v1.0.0.0            no
       101       fexth             5.2(1)N1(2)             7.0(5)N1(1)           yes
       102       fexth             5.2(1)N1(2)             7.0(5)N1(1)           yes
       111       fexth             5.2(1)N1(2)             7.0(5)N1(1)           yes
       112       fexth             5.2(1)N1(2)             7.0(5)N1(1)           yes
         1   power-seq                    v5.0                    v7.0           yes
         1          uC                v1.0.0.2                v1.0.0.2            no
    Additional info for this installation:
    Remove QoS & ACL config on L3 interfaces and SVIs if any
    Service "stp" : Port: port-channel20 in VLAN0001 is Designated. Topology change could occur during ISSU.
    Upgrade needs to be disruptive!!!
    Service "vpc" : STP Preupgrade Check failed on VPC peer switch

  • In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010. Part Number is N7K-MPLS1K9.

    In reviewing the Cisco Licensing Guide, there is a license part number for MPLS on the Nexus 7010.  Part Number is N7K-MPLS1K9.  Is there a corresponding part number for the Nexus 7710?

    For the benefit of others, here is what we found. The N7K was hitting the bug CSCtg95381.
    Symptom
    Nexus 7000 may punt traffic to CPU; so that the traffic may experience random delay or drop.
    Further looking, ARP is learned and FIB adjacency is in FIB adjacency table.
    Conditions
    The problem is caused by race condition. Some hosts have not responded to the ARP refresh sent by
    N7k which in turn  trigger to delete  ARP entry  due to expiry. As a result   the route delete notification is
    sent   to URIB from the process. However there is still traffic coming to   given IP address as a result  the next packet that hit glean resulting   in triggering ARP and  hope ARP is learnt from the host this time.
    Workaround
    (s):
    Clear ip route < host>.
    Not  totally explains why it was working for certain client-server  combination but yet the workaround is holding well for end-points when  implemented.
    There  would be no host route for the destination server in the adjacency  manager on N7K-01. The only thing thats there is the subnet route  pointing towards the vlan gateway address. Implementing the work-around,  a new /32 route can now be seen in the adjacency manager for the  server.
    The bug is fixed in releases starting 5.1(5). Planning to upgrade to 5.2(3a).
    Regards, Rashid.

  • Nexus 7010 and ESX Host

    Hi,
    We are currently seeing issues on a ESX Host using 10G Fibre dual connectivity to a pair of Nexus 7010's using vPC for the port channel to this ESX host which was working fine , up to this weekend. No changes had been made on the Nexus or ESX host.
    We have changed the hardware path for the believed fault on a vmnic which when part of the virtual switch cause VM's on the Host to stop pinging, although we still see a CDP neighborship with the ESX from the Nexus, but changing fibre and Nexus ports has not worked.
    As part of the testing , the vmware guy was removing this 'faulty' vmnic from the Virtual switch , which is part of an ether channel bundle his end. My first question is, how does the Nexus detect a link leaving the bundle for the ESX host , when the actual physical link is still up , and all they have done is software removed it from on the ESX, as the Nexus will still attempt to push traffic across both bundled links. I know there is the Cisco 1000V software , which can be used at an extra price, but is this the only option.
    Any help will be gladly welcome.

    Hi
    How the switch detects a link 'moving out' of the Etherchannel would depend on how you have configured it...
    If you have used 'channel-group x mode on' under the physical ports in the channel, then it will not detect the change, and you will get problems. The solution is to ensure the config of the channel on both ends (server/switch) is consistent in this case. An inconsistent config will cause you connectivity issues.
    If the switch automatically negotiates the Etherchannel (i.e. you are using LACP, and the server supports LACP) then it should detect the change.
    Regards
    Aaron
    Please rate helpful posts...

  • Nexus 7010 10G Ports

    As many 10G ports may have a nexus 7010? I read documentation who speaks in some 256 ports, but each module has a throughput of only 80G. This means that I can really only have 64 10G ports because 10G are shared by groups of 4?
    Thanks

    5596's L3 throughput is limited to 160G one way per chassis. However the N7K depends on the type of line card, number of fabric and the fabric speed, which you can said it will increase when Cisco release a newer fabric and line card. With the current M1 line card, the N7K can perfrom 80G one way per line card for L3.
    The F132 line card doesn't support L3, but it supports fabric path. The F1 will rely on the M1 to forward L3 traffic.
    HTH,
    jerry

  • Disable openssl on Nexus 7010

    I need to restrict management to ssh on Nexus 7010.
    I need to turn off or restrict ssl.
    or upgrade to a newer version of Openssl

    You can restrict access with ACL. Or turn off SSH completely. But you can't install any SSL version you want since the NX-OS is not a regular Linux box.
    HTH,
    jerry

  • Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

    Hi everybody,
    I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
    of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
    I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
    etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
    the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
    <04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
    <04-25-2014 02:06:47> ********************************************
    <04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
    minimum supported installed build version is [7804].
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Unsupported upgrade path;    Error;   
    Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
    <04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Active Replica MP;    Passed
    <04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
    <04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;   
    Parent site replication status;    Passed
    <04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
    =====
    <04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server sysadmin rights;    Passed
    <04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
    for reference site;    Passed
    <04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Site server computer account administrative rights;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server security mode;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
    <04-25-2014 02:07:09> INFO: Target computer is a Windows server.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Unsupported site server operating system version for Setup;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Domain membership;    Passed
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Pending system restart;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server version;    Passed
    <04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Edition;    Passed
    <04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
    Instance:.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    SQL Server Tcp Port;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
    <04-25-2014 02:07:09> INFO: SQL Server memory is limited.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Configuration for SQL Server memory usage;    Passed
    <04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
    <04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
    Server to reserve a minimum of 8 gigabytes (GB) of memory.
    <04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;   
    Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
    using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
    http://go.microsoft.com/fwlink/p/?LinkId=233759.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Case-insensitive collation on SQL Server;    Passed
    <04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
    <04-25-2014 02:07:09> INFO: getaddrinfo returned success.
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Validate FQDN of SQL Server Computer;    Passed
    <04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
    <04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
    <04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;   
    Primary FQDN;    Passed
    <04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
    =====
    <04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
    <04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
    been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
    <04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Failover Cluster;    Passed
    <04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
    skipped.
    <04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    Windows Deployment Tools installed;    Passed
    <04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
    installed;    Passed
    <04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;   
    SMS Provider machine has same domain as site server;    Passed
    <04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
    <04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
    <04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
    <04-25-2014 02:07:10> ***************************************************
    <04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
    <04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
    Prerequisite checking result into the registry
    <04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
    <04-25-2014 02:07:10> INFO: Setting registry values
    If you wonder whether it might be related to this error:
    -2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
    I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
    on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
    I've already tried the
    Preinst /DELSITE XXX  command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
    Finally,  the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
    the impression that it's being cached somehow.
    Any help would be highly appreciated,
    Thank you.
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

    Hello again everybody,
    I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
    primary sites.
    If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
    DELETE
    FROMServerDataWHERESiteCode='XXX'
    DELETE
    FROMSC_SiteDefinitionWHERESiteCode='XXX'
    And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
    Thank you all anyways for your answers and comments,
    Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

  • Error Message: "This upgrade path is not supported"

    Scenario
    During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
    choice.” in the Compatibility report.
    Analysis
    Step 1: Perform the scenario 1: the upgrade installation fails.
    Reproduce this error following the steps below:
    Download the Windows 10 Technical Preview ISO installation file.
    Extract the ISO installation file to C:\New folder, and now the location of the installation file is
    C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
    Click setup.exe from the installation file, and then click
    Install now.   
    Setup is starting, and then get two options Upgrade and
    Custom which is the classic setup wizard which we can see during booting from DVD.
    Click Upgrade to run upgrade installation, however, the error occurs.
    It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
    Custom to perform clean installation which cannot keep the personal setting and applications.
    However, what we want is upgrade installation, not clean installation.
    Step 2: Perform the scenario 2: the upgrade installation works fine.
    If extract the ISO installation to C:\New in the above step2, click the
    setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
    Step 3: Check the setupact.log
    file which contains information about setup actions during the installation of the two scenarios.
    Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
    2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
    2014-10-14 19:03:42, Info UI Will launch ConX setup experience
    2014-10-14 19:03:42, Info UI Launching ConX setup experience
    2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
    2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
    2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
    2014-10-14 19:03:44, Info UI No need to hide autorun
    2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
    2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
    2014-10-14 19:03:44, Info UI AppWindow has layout style 0
    2014-10-14 19:03:45, Info UI NavWindow has layout style 0
    2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
    2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
    Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
    2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
    2014-10-14 19:08:05, Info UI Will launch ConX setup experience
    2014-10-14 19:08:05, Info UI Launching ConX setup experience
    2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
    According to the two logs, we can get the following points:
    In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
    C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
    In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
    So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
    Workaround
    Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
    file, the upgrade installation would work fine.
    What’s more, we can get the meaning of the two setup models in the setupact.log:
    Legacy setup: it is same with setup from DVD boot.
    ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
    Additional Resource
    From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
    us your feedback.
    Download Windows Technical Preview
    http://windows.microsoft.com/en-us/windows/preview-iso
    Download Windows Technical Preview for Enterprise
    http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    Hello,
    I would guess that existence of a space in the folder name is what the issue is.  Try removing the space from the folder name and see if works. New_Folder for example
    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

  • I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

    I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

    yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
    When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
    I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

Maybe you are looking for

  • Address book application

    When I made a Duplicate of my address book I kept it on my desktop. I then deleted it and foolishly emptied my trash can - securely! The address book icon in the docking then showed a question mark, so I could not use it and dragged it onto my deskto

  • Importing from iPhoto into Photshop Elements

    I have never had a problem importing images from my iPhoto library into Adobe Photoshop Elements until I installed iLife 08. Now the iPhoto library is greyed out and I can not access my images. I find the image editing facilities of iPhoto good but a

  • Number of elements that can be used with 'in' Operator

    One of my SQL query having 'in' operator failed saying number of elements exceed. Is there a limit on number of elements that can be used with - 'in' operator. And if yes can it be increased?

  • Sync iphone calendar with windows 8 calendar

    Hi, I'm using windows 8 on my new PC and would like to sync my iPhone calendar with it. Is it possible? How do I do it? Thanks

  • How can I edit VOB Video files in imovie 09?

    Hi Everyone I wonder if you can help? How can I edit VOB Video files in imovie 09? Thanks