<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Upgrading remote site APS through RFDM AP in ExtremeWireless (WiNG)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83209#M7743</link>
    <description>&lt;P&gt;Aviv,&lt;/P&gt;&lt;P&gt;Are you saying that your initial test here with 7.2 involved an initial adoption scenario where all of the APs needed to be upgraded?&amp;nbsp; If that’s the case, then it is *expected/known* that the 1st upgrade for a remote site WILL require that each AP be upgraded individually by the controller (each AP using its initial level-2 MINT link).&amp;nbsp; Like you mentioned, in this *initial deployment* scenario, the APs are not yet adopted….so they don’t yet have their config...and they don’t have their config yet because they first have to have a matching WiNG firmware version.&amp;nbsp; Once the firmware match requirement is met, they get their config, and then the tear-down from level-2 MINT links to level-1 MINT links (for the non-RFDM APs) is performed and the RFDM is elected.&amp;nbsp; Then going forward, the firmware updates are performed by the RFDM AP.&lt;/P&gt;&lt;P&gt;Trying to circumvent this though by relaxing the version matching requirements is not something you should be doing in a production environment...unless you first thoroughly test the specific setup and accept the responsibility of anything going wrong.&lt;/P&gt;&lt;P&gt;In some cases, doing this might not cause any problems. &amp;nbsp; But doing this can have unexpected results.&amp;nbsp; Using the ability to have non-matching WiNG firmware on the APs should only be used in special cases, and is meant to be a *short-term temporary* solution.&lt;/P&gt;&lt;P&gt;What you are suggesting may in fact work.&amp;nbsp; But if you run into any problems while doing this, it won’t be supported and will not be considered a bug.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 24 Oct 2019 21:19:21 GMT</pubDate>
    <dc:creator>ckelly</dc:creator>
    <dc:date>2019-10-24T21:19:21Z</dc:date>
    <item>
      <title>Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83190#M7724</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;&lt;P&gt;In my lab I can’t make working the upgrading remote site APS through RFDM AP.&lt;/P&gt;&lt;P&gt;My upgrades are successful, but through VX9000 and not through the RFDM AP.&lt;/P&gt;&lt;P&gt;The test is very simple, VX9000 + 2 pieces of AP7532 in the same vlan.&lt;/P&gt;&lt;P&gt;VX running config:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;!### show running-config&lt;BR /&gt;!&lt;BR /&gt;! Configuration of VX9000 version 7.2.1.1-006R&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;version 2.7&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;client-identity-group default&lt;BR /&gt; load default-fingerprints&lt;BR /&gt;!&lt;BR /&gt;ip access-list BROADCAST-MULTICAST-CONTROL&lt;BR /&gt; permit tcp any any rule-precedence 10 rule-description "permit all TCP traffic"&lt;BR /&gt; permit udp any eq 67 any eq dhcpc rule-precedence 11 rule-description "permit DHCP replies"&lt;BR /&gt; deny udp any range 137 138 any range 137 138 rule-precedence 20 rule-description "deny windows netbios"&lt;BR /&gt; deny ip any 224.0.0.0/4 rule-precedence 21 rule-description "deny IP multicast"&lt;BR /&gt; deny ip any host 255.255.255.255 rule-precedence 22 rule-description "deny IP local broadcast"&lt;BR /&gt; permit ip any any rule-precedence 100 rule-description "permit all IP traffic"&lt;BR /&gt;!&lt;BR /&gt;mac access-list PERMIT-ARP-AND-IPv4&lt;BR /&gt; permit any any type ip rule-precedence 10 rule-description "permit all IPv4 traffic"&lt;BR /&gt; permit any any type arp rule-precedence 20 rule-description "permit all ARP traffic"&lt;BR /&gt;!&lt;BR /&gt;ip snmp-access-list default&lt;BR /&gt; permit any&lt;BR /&gt;!&lt;BR /&gt;firewall-policy default&lt;BR /&gt; no ip dos tcp-sequence-past-window&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;mint-policy global-default&lt;BR /&gt;!&lt;BR /&gt;meshpoint-qos-policy default&lt;BR /&gt;!&lt;BR /&gt;wlan-qos-policy default&lt;BR /&gt; qos trust dscp&lt;BR /&gt; qos trust wmm&lt;BR /&gt;!&lt;BR /&gt;radio-qos-policy default&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;management-policy default&lt;BR /&gt; no telnet&lt;BR /&gt; no http server&lt;BR /&gt; https server&lt;BR /&gt; rest-server&lt;BR /&gt; ssh&lt;BR /&gt; user admin password 1 b3c4e90173bd1f030e821f04ee833f17e78b4133788ffb40f12928bfabba10c8 role superuser access all&lt;BR /&gt; snmp-server community 0 private rw&lt;BR /&gt; snmp-server community 0 public ro&lt;BR /&gt; snmp-server user snmptrap v3 encrypted des auth md5 0 admin123&lt;BR /&gt; snmp-server user snmpmanager v3 encrypted des auth md5 0 admin123&lt;BR /&gt; t5 snmp-server community public ro 192.168.0.1&lt;BR /&gt; t5 snmp-server community private rw 192.168.0.1&lt;BR /&gt;!&lt;BR /&gt;ex3500-management-policy default&lt;BR /&gt; snmp-server community public ro&lt;BR /&gt; snmp-server community private rw&lt;BR /&gt; snmp-server notify-filter 1 remote 127.0.0.1&lt;BR /&gt; snmp-server view defaultview 1 included&lt;BR /&gt;!&lt;BR /&gt;ex3500-qos-class-map-policy default&lt;BR /&gt;!&lt;BR /&gt;ex3500-qos-policy-map default&lt;BR /&gt;!&lt;BR /&gt;database-policy default&lt;BR /&gt;!&lt;BR /&gt;profile vx9000 default-vx9000&lt;BR /&gt; no autoinstall configuration&lt;BR /&gt; no autoinstall firmware&lt;BR /&gt; no device-upgrade auto&lt;BR /&gt; crypto ikev1 policy ikev1-default &lt;BR /&gt;  isakmp-proposal default encryption aes-256 group 2 hash sha &lt;BR /&gt; crypto ikev2 policy ikev2-default &lt;BR /&gt;  isakmp-proposal default encryption aes-256 group 2 hash sha &lt;BR /&gt; crypto ipsec transform-set default esp-aes-256 esp-sha-hmac&lt;BR /&gt; crypto ikev1 remote-vpn&lt;BR /&gt; crypto ikev2 remote-vpn&lt;BR /&gt; crypto auto-ipsec-secure&lt;BR /&gt; crypto load-management&lt;BR /&gt; crypto remote-vpn-client&lt;BR /&gt; interface xge1&lt;BR /&gt; interface xge2&lt;BR /&gt; interface xge3&lt;BR /&gt; interface xge4&lt;BR /&gt; interface ge1&lt;BR /&gt; interface ge2&lt;BR /&gt; use firewall-policy default&lt;BR /&gt; logging on&lt;BR /&gt; service pm sys-restart&lt;BR /&gt; router bgp&lt;BR /&gt; adoption-mode controller&lt;BR /&gt;!&lt;BR /&gt;profile ap7532 default-ap7532&lt;BR /&gt; autoinstall configuration&lt;BR /&gt; autoinstall firmware&lt;BR /&gt; crypto ikev1 policy ikev1-default &lt;BR /&gt;  isakmp-proposal default encryption aes-256 group 2 hash sha &lt;BR /&gt; crypto ikev2 policy ikev2-default &lt;BR /&gt;  isakmp-proposal default encryption aes-256 group 2 hash sha &lt;BR /&gt; crypto ipsec transform-set default esp-aes-256 esp-sha-hmac&lt;BR /&gt; crypto ikev1 remote-vpn&lt;BR /&gt; crypto ikev2 remote-vpn&lt;BR /&gt; crypto auto-ipsec-secure&lt;BR /&gt; crypto load-management&lt;BR /&gt; crypto remote-vpn-client&lt;BR /&gt; interface radio1&lt;BR /&gt; interface radio2&lt;BR /&gt; interface ge1&lt;BR /&gt; interface vlan1&lt;BR /&gt;  ip address dhcp&lt;BR /&gt;  ip address zeroconf secondary&lt;BR /&gt;  ip dhcp client request options all&lt;BR /&gt; interface pppoe1&lt;BR /&gt; use firewall-policy default&lt;BR /&gt; use client-identity-group default&lt;BR /&gt; logging on&lt;BR /&gt; controller host 172.17.8.3 pool 1 level 2&lt;BR /&gt; service pm sys-restart&lt;BR /&gt; router ospf&lt;BR /&gt; adoption-mode controller&lt;BR /&gt;!&lt;BR /&gt;rf-domain VXtest&lt;BR /&gt; country-code il&lt;BR /&gt;!&lt;BR /&gt;rf-domain default&lt;BR /&gt; no country-code&lt;BR /&gt; control-vlan 1&lt;BR /&gt;!&lt;BR /&gt;vx9000 08-00-27-1D-96-AB&lt;BR /&gt; use profile default-vx9000&lt;BR /&gt; use rf-domain VXtest&lt;BR /&gt; hostname vx9000-1D96AB&lt;BR /&gt; license AAP VX-DEMO-16AAP-LICENSE&lt;BR /&gt; license ADSEC DEFAULT-ADV-SEC-LICENSE&lt;BR /&gt; no mint mlcp vlan&lt;BR /&gt; autoinstall firmware&lt;BR /&gt; interface ge1&lt;BR /&gt; interface ge2&lt;BR /&gt; interface vlan1&lt;BR /&gt;  ip address dhcp&lt;BR /&gt;!&lt;BR /&gt;ap7532 B8-50-01-71-C0-D4&lt;BR /&gt; use profile default-ap7532&lt;BR /&gt; use rf-domain default&lt;BR /&gt; hostname ap7532-71C0D4&lt;BR /&gt;!&lt;BR /&gt;ap7532 B8-50-01-74-3E-6C&lt;BR /&gt; use profile default-ap7532&lt;BR /&gt; use rf-domain default&lt;BR /&gt; hostname ap7532-743E6C&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;end&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Info from VX:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;vx9000-1D96AB#show mint ne&lt;BR /&gt;1 mint neighbors of 12.1D.96.AB:&lt;BR /&gt;1B.71.C0.D4 (ap7532-71C0D4) at level 2, best adjacency ip-172.17.8.4:24576&lt;BR /&gt;&lt;BR /&gt;vx9000-1D96AB#show global domain managers &lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;                      RF-DOMAIN                              MANAGER          HOST-NAME  APS  CLIENTS&lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;                         VXtest                    08-00-27-1D-96-AB      vx9000-1D96AB    0        0&lt;BR /&gt;                        default                    B8-50-01-71-C0-D4      ap7532-71C0D4    2        0&lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;Total number of RF-domain displayed: 2&lt;BR /&gt;&lt;BR /&gt;vx9000-1D96AB#show device-upgrade history &lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;BR /&gt;            Device      RESULT                 TIME  RETRIES        UPGRADED-BY LAST-UPDATE-ERROR&lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;     ap7532-743E6C        done  2019-10-22 09:23:31        0      vx9000-1D96AB -&lt;BR /&gt;&lt;BR /&gt;     ap7532-71C0D4        done  2019-10-22 09:24:42        0      vx9000-1D96AB -&lt;BR /&gt;&lt;BR /&gt;Total number of entries displayed: 2&lt;BR /&gt;&lt;BR /&gt;vx9000-1D96AB#show mint neighbors on ap7532-71C0D4&lt;BR /&gt;2 mint neighbors of 1B.71.C0.D4:&lt;BR /&gt;1B.74.3E.6C (ap7532-743E6C) at level 1, best adjacency vlan-1&lt;BR /&gt;12.1D.96.AB (vx9000-1D96AB) at level 2, best adjacency ip-172.17.8.3:24576&lt;BR /&gt;&lt;BR /&gt;vx9000-1D96AB#show mint neighbors on ap7532-743E6C&lt;BR /&gt;1 mint neighbors of 1B.74.3E.6C:&lt;BR /&gt;1B.71.C0.D4 (ap7532-71C0D4) at level 1, best adjacency vlan-1&lt;BR /&gt;&lt;BR /&gt;vx9000-1D96AB#show mint links &lt;BR /&gt;1 mint links on 12.1D.96.AB:&lt;BR /&gt;link ip-172.17.8.4:24576 at level 2, 1 adjacencies, (used)&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;What is wrong with my configuration?&lt;/P&gt;&lt;P&gt;Why I can’t make the upgrades working through RFDM AP?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 18:26:11 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83190#M7724</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-22T18:26:11Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83191#M7725</link>
      <description>&lt;P&gt;Hi Avi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Everything looks good. And how the upgrade process looks like? You can monitor it with "watch 4 sh device-upgrade status". Also the devices can skip the update while already running requested release and without "force" option in upgrade command..&lt;/P&gt;&lt;P&gt;Misha&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 19:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83191#M7725</guid>
      <dc:creator>vanelm</dc:creator>
      <dc:date>2019-10-22T19:52:00Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83192#M7726</link>
      <description>&lt;P&gt;Hello Misha,&lt;/P&gt;&lt;P&gt;Upgrade process is looking OK, but I expecting to see from &lt;CODE&gt;show device-upgrade history &lt;/CODE&gt;&lt;/P&gt;&lt;PRE&gt;something like: UPGRADED-BY - ap7532-743E6C, but I don’t see that.&lt;/PRE&gt;&lt;P&gt;Also I don’t see any temp firmware file stored on the&amp;nbsp;flash of the RFDM AP, as expected.&lt;/P&gt;&lt;P&gt;So, I think the upgrade is accomplished through VX9000 without RFDM AP, so the file is transferred twice.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 21:35:23 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83192#M7726</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-22T21:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83193#M7727</link>
      <description>&lt;P&gt;Hello Aviv,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; Please use the attached when upgrading VX9 and adopted remote APs.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 22:12:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83193#M7727</guid>
      <dc:creator>Christopher_Fra</dc:creator>
      <dc:date>2019-10-22T22:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83194#M7728</link>
      <description>&lt;P&gt;The results of the MINT links and neighbors looks correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you run the device upgrade history command directly on the AP’s themselves?&lt;/P&gt;&lt;P&gt;Specifically interested in the output from the non-RFDM AP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Oct 2019 22:20:08 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83194#M7728</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-22T22:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83195#M7729</link>
      <description>&lt;P&gt;Hello Aviv,&lt;/P&gt;&lt;P&gt;&amp;nbsp; Please note that&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Upgrade always happens with RFDM unless you specify “from-controlled” explicitly&lt;/LI&gt;	&lt;LI&gt;UPGRADED-BY shows device, who is actually handle&amp;nbsp;the upgrade i.e. control the process, hosts the AP image etc&lt;/LI&gt;	&lt;LI&gt;In case you upgrading many RFD from active-active (not recommended) VX cluster - perhaps you will have these upgrading activities shared between nodes&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;CODE&gt;vx9000-5566BE#device-upgrade rf-domain TEST all ?&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; force &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Force upgrade of devices in the rf-domain&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; from-controller &amp;nbsp; Upgrade devices from the adopted device&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; no-reboot &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; No reboot (manually reboot after the upgrade)&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; reboot-time &amp;nbsp; &amp;nbsp; &amp;nbsp; Schedule a reboot time&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; staggered-reboot &amp;nbsp;Reboot one at a time without network being hit&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; upgrade-time &amp;nbsp; &amp;nbsp; &amp;nbsp;Schedule an upgrade time&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp; &amp;lt;cr&amp;gt;&lt;/CODE&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Misha&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2019 14:29:36 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83195#M7729</guid>
      <dc:creator>vanelm</dc:creator>
      <dc:date>2019-10-23T14:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83196#M7730</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;&lt;P&gt;Logs from VX when device-upgrade rf-domain default all force executed :&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;vx9000-1D96AB#device-upgrade all force &lt;BR /&gt;In progress ....&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;       CONTROLLER         STATUS                     MESSAGE                    &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;  08-00-27-1D-96-AB     Success     Number of devices added for upgrade: 2      &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;Are you sure you want to proceed with the upgrade? (y/n): y&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;           CONTROLLER                              MESSAGE                      &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;  08-00-27-1D-96-AB             Successfully started device upgrade             &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;vx9000-1D96AB#show device-upgrade status &lt;BR /&gt;Number of devices currently being upgraded : 2&lt;BR /&gt;Number of devices waiting in queue to be upgraded : 0&lt;BR /&gt;Number of devices currently being rebooted : 0&lt;BR /&gt;Number of devices waiting in queue to be rebooted : 0&lt;BR /&gt;Number of devices failed upgrade : 0&lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;      DEVICE         STATE     UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR    UPGRADED BY     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;  ap7532-71C0D4   downloading   immediate    immediate   8        0       -                 vx9000-1D96AB     &lt;BR /&gt;  ap7532-743E6C   downloading   immediate    immediate   8        0       -                 vx9000-1D96AB     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;vx9000-1D96AB#show gl domain managers &lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;                      RF-DOMAIN                              MANAGER          HOST-NAME  APS  CLIENTS&lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;                         VXtest                    08-00-27-1D-96-AB      vx9000-1D96AB    0        0&lt;BR /&gt;                        default                    B8-50-01-71-C0-D4      ap7532-71C0D4    2        0&lt;BR /&gt;-----------------------------------------------------------------------------------------------------&lt;BR /&gt;Total number of RF-domain displayed: 2&lt;BR /&gt;vx9000-1D96AB#show device-upgrade status &lt;BR /&gt;Number of devices currently being upgraded : 2&lt;BR /&gt;Number of devices waiting in queue to be upgraded : 0&lt;BR /&gt;Number of devices currently being rebooted : 0&lt;BR /&gt;Number of devices waiting in queue to be rebooted : 0&lt;BR /&gt;Number of devices failed upgrade : 0&lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;      DEVICE         STATE     UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR    UPGRADED BY     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;  ap7532-71C0D4   downloading   immediate    immediate   49       0       -                 vx9000-1D96AB     &lt;BR /&gt;  ap7532-743E6C   downloading   immediate    immediate   49       0       -                 vx9000-1D96AB     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;vx9000-1D96AB#&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;logs from ap7532-71C0D4&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;2019-10-23 11:16:26     ap7532-71C0D4  SYSTEM     CONFIG_REVISION      Configuration revision updated to 4 from 3&lt;BR /&gt;2019-10-23 11:14:25     ap7532-71C0D4  SYSTEM     WARM_START_RECOVER   Warm Start Recover. Reason: Upgrade done, reloading... (user: system @ vx9000-1D96AB) Timestamp: Oct 23 11:11:57 2019&lt;BR /&gt;2019-10-23 11:14:23     ap7532-71C0D4  SYSTEM     CONFIG_REVISION      Configuration revision updated to 3 from 3&lt;BR /&gt;2019-10-23 11:14:23     ap7532-71C0D4  SYSTEM     CONFIG_COMMIT        Configuration commit by user 'cfgd' (update own config) from '127.0.0.1'&lt;BR /&gt;2019-10-23 11:14:27     ap7532-71C0D4  SYSTEM     CLOCK_RESET          System clock reset, Time: 2019-10-23 11:14:23&lt;BR /&gt;2019-10-23 11:14:26     ap7532-71C0D4  DEVICE     ADOPTED_TO_CONTROLLER Joined successfully with controller 'vx9000-1D96AB'(12.1D.96.AB)&lt;BR /&gt;2019-10-23 11:14:26     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message adopted-event from module cfgd&lt;BR /&gt;2019-10-23 11:13:55     ap7532-71C0D4  NSM        DHCPIP               Interface vlan1 acquired IP address 172.17.8.4/24 via DHCP&lt;BR /&gt;2019-10-23 11:13:55     ap7532-71C0D4  NSM        DHCPDEFRT            Default route with gateway 172.17.8.254 learnt via DHCP&lt;BR /&gt;2019-10-23 11:12:54     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R2' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R2' changing state from 'Off' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R1' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R1' changing state from 'Off' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R2' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R2' changing state from 'Unconfigured' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R1' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-71C0D4:R1' changing state from 'Unconfigured' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  MESH       MESHPOINT_LOOP_PREVENT_OFF Meshpoint loop prevention off (port ALL), all wired traffic is allowed&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message AP_LEDS_ON from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message LED_NO_COUNTRY_CODE_SET from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-71C0D4  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.71.c0.d4 sitemgr_mint_id 1b.71.c0.d4&lt;BR /&gt;2019-10-23 11:12:52     ap7532-71C0D4  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.71.c0.d4 sitemgr_mint_id 00.00.00.00&lt;BR /&gt;2019-10-23 11:12:52     ap7532-71C0D4  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.71.c0.d4 sitemgr_mint_id 1b.71.c0.d4&lt;BR /&gt;2019-10-23 11:12:52     ap7532-71C0D4  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.71.c0.d4 sitemgr_mint_id 00.00.00.00&lt;BR /&gt;2019-10-23 11:12:52     ap7532-71C0D4  DIAG       NEW_LED_STATE        LED state message LED_LOCATIONING_OFF from module cfgd&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;log from ap7532-743E6C&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;2019-10-23 11:16:27     ap7532-743E6C  SYSTEM     CONFIG_REVISION      Configuration revision updated to 4 from 3&lt;BR /&gt;2019-10-23 11:14:27     ap7532-743E6C  SYSTEM     WARM_START_RECOVER   Warm Start Recover. Reason: Upgrade done, reloading... (user: system @ vx9000-1D96AB) Timestamp: Oct 23 11:11:58 2019&lt;BR /&gt;2019-10-23 11:14:26     ap7532-743E6C  SYSTEM     CONFIG_REVISION      Configuration revision updated to 3 from 3&lt;BR /&gt;2019-10-23 11:14:26     ap7532-743E6C  SYSTEM     CONFIG_COMMIT        Configuration commit by user 'cfgd' (update own config) from '127.0.0.1'&lt;BR /&gt;2019-10-23 11:14:29     ap7532-743E6C  SYSTEM     CLOCK_RESET          System clock reset, Time: 2019-10-23 11:14:26&lt;BR /&gt;2019-10-23 11:14:29     ap7532-743E6C  DEVICE     ADOPTED_TO_CONTROLLER Joined successfully with controller 'vx9000-1D96AB'(12.1D.96.AB)&lt;BR /&gt;2019-10-23 11:14:29     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message adopted-event from module cfgd&lt;BR /&gt;2019-10-23 11:14:02     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 1b.71.c0.d4&lt;BR /&gt;2019-10-23 11:14:01     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 1b.74.3e.6c&lt;BR /&gt;2019-10-23 11:13:56     ap7532-743E6C  NSM        DHCPIP               Interface vlan1 acquired IP address 172.17.8.30/24 via DHCP&lt;BR /&gt;2019-10-23 11:13:56     ap7532-743E6C  NSM        DHCPDEFRT            Default route with gateway 172.17.8.254 learnt via DHCP&lt;BR /&gt;2019-10-23 11:13:00     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 1b.71.c0.d4&lt;BR /&gt;2019-10-23 11:12:55     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:55     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R2' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:55     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:55     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R2' changing state from 'Off' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R1' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R1' changing state from 'Off' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R2' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_1_52G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R2' changing state from 'Unconfigured' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R1' changing state from 'Initializing' to 'Off(no country-code)' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message WIOS_LED_NO_COUNTRY_0_24G from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  RADIO      RADIO_STATE_CHANGE   Radio 'ap7532-743E6C:R1' changing state from 'Unconfigured' to 'Initializing' &lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  MESH       MESHPOINT_LOOP_PREVENT_OFF Meshpoint loop prevention off (port ALL), all wired traffic is allowed&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message AP_LEDS_ON from module DOT11&lt;BR /&gt;2019-10-23 11:12:54     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message LED_NO_COUNTRY_CODE_SET from module DOT11&lt;BR /&gt;2019-10-23 11:12:53     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 1b.74.3e.6c&lt;BR /&gt;2019-10-23 11:12:53     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 00.00.00.00&lt;BR /&gt;2019-10-23 11:12:53     ap7532-743E6C  MINT       RFDM_MGR_UPDATE      own_mint_id 1b.74.3e.6c sitemgr_mint_id 00.00.00.00&lt;BR /&gt;2019-10-23 11:12:53     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message LED_LOCATIONING_OFF from module cfgd&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  MGMT       LOG_HTTP_START       lighttpd started in external mode&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  SYSTEM     SYSTEM_AUTOUP_ENABLE Autoupgrade enabled for ap7562&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message LED_LOCAL_LICENSE from module CFGD&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  SYSTEM     SYSTEM_AUTOUP_ENABLE Autoupgrade enabled for ap7522&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  DIAG       NEW_LED_STATE        LED state message LED_LOCAL_LICENSE from module CFGD&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  SYSTEM     SYSTEM_AUTOUP_ENABLE Autoupgrade enabled for ap7532&lt;BR /&gt;2019-10-23 11:12:51     ap7532-743E6C  LICMGR     LIC_INSTALL_DEFAULT  AP default license installed, count: 64&lt;BR /&gt;2019-10-23 11:12:51       MGMT       LOG_HTTP_START       lighttpd started in external mode&lt;BR /&gt;2019-10-23 11:12:51       MGMT       LOG_HTTP_START       lighttpd started in external mode&lt;BR /&gt;2019-10-23 11:12:51       DHCPSVR    DHCPSVR_STOP         DHCP server is stopped&lt;BR /&gt;2019-10-23 11:12:53       NSM        IFUP                 Interface ge1 is up&lt;BR /&gt;2019-10-23 11:12:50       SYSTEM     CONFIG_REVISION      Configuration revision updated to 3 from 2&lt;BR /&gt;2019-10-23 11:12:50       SYSTEM     CONFIG_REVISION      Configuration revision updated to 2 from 1&lt;BR /&gt;2019-10-23 11:12:51       NSM        IFDOWN               Interface ge1 is down&lt;BR /&gt;2019-10-23 11:12:50       SYSTEM     CONFIG_COMMIT        Configuration commit by user 'cfgd' (read startup-config) from '127.0.0.1'&lt;BR /&gt;2019-10-23 11:12:51       NSM        IFUP                 Interface vlan1 is up&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;show upgrade from AP:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;ap7532-71C0D4#show upgrade?&lt;BR /&gt;  upgrade-status  Display last image upgrade status&lt;BR /&gt;&lt;BR /&gt;ap7532-71C0D4#show upgrade&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2019 21:25:09 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83196#M7730</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-23T21:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83197#M7731</link>
      <description>&lt;P&gt;Log from VX when executed device-upgrade rf-domain default all force from-controller&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;vx9000-1D96AB#device-upgrade rf-domain default all force from-controller &lt;BR /&gt;In progress ....&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;       CONTROLLER         STATUS                     MESSAGE                    &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;  08-00-27-1D-96-AB     Success     Number of devices added for upgrade: 2      &lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;vx9000-1D96AB#show device-upgrade status &lt;BR /&gt;Number of devices currently being upgraded : 2&lt;BR /&gt;Number of devices waiting in queue to be upgraded : 0&lt;BR /&gt;Number of devices currently being rebooted : 0&lt;BR /&gt;Number of devices waiting in queue to be rebooted : 0&lt;BR /&gt;Number of devices failed upgrade : 0&lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;      DEVICE         STATE     UPGRADE TIME REBOOT TIME PROGRESS RETRIES LAST UPDATE ERROR    UPGRADED BY     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;  ap7532-71C0D4   downloading   immediate    immediate   30       0       -                 vx9000-1D96AB     &lt;BR /&gt;  ap7532-743E6C   downloading   immediate    immediate   30       0       -                 vx9000-1D96AB     &lt;BR /&gt;--------------------------------------------------------------------------------------------------------------&lt;BR /&gt;vx9000-1D96AB#&lt;BR /&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Its looks like the same procedure, the image is uploaded from VX to the APS simultaneously, without the RFDM AP &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2019 21:27:42 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83197#M7731</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-23T21:27:42Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83198#M7732</link>
      <description>&lt;P&gt;Aviv, please see my previous request.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2019 22:11:11 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83198#M7732</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-23T22:11:11Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83199#M7733</link>
      <description>&lt;PRE&gt;&lt;CODE&gt;ap7532-71C0D4#show upgrade?&lt;BR /&gt;  upgrade-status  Display last image upgrade status&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Upgrade history of the APS is &lt;U&gt;&lt;STRONG&gt;clear &lt;/STRONG&gt;&lt;/U&gt;on these APS.&lt;/P&gt;&lt;P&gt;Please look into event-histories attached in my previous message.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 00:56:13 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83199#M7733</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T00:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83200#M7734</link>
      <description>&lt;P&gt;The command I’m wanting to see the results of are:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show device-upgrade status&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 00:58:44 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83200#M7734</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-24T00:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83201#M7735</link>
      <description>&lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1a2a931a17a8481fb89bab61b12e3db2_47d77fd5-387f-4ba7-83ef-44505e48dea6.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/5708i7B9BBB36D7ED8FAF/image-size/large?v=v2&amp;amp;px=999" role="button" title="1a2a931a17a8481fb89bab61b12e3db2_47d77fd5-387f-4ba7-83ef-44505e48dea6.jpg" alt="1a2a931a17a8481fb89bab61b12e3db2_47d77fd5-387f-4ba7-83ef-44505e48dea6.jpg" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 01:12:10 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83201#M7735</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T01:12:10Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83202#M7736</link>
      <description>&lt;FIGURE&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="566069ae55e94804afd2054287b017e8_b9bbfdd2-99c3-4aaf-99fe-d2beb3159acf.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/617i72A05A5739D2928E/image-size/large?v=v2&amp;amp;px=999" role="button" title="566069ae55e94804afd2054287b017e8_b9bbfdd2-99c3-4aaf-99fe-d2beb3159acf.jpg" alt="566069ae55e94804afd2054287b017e8_b9bbfdd2-99c3-4aaf-99fe-d2beb3159acf.jpg" /&gt;&lt;/span&gt;&lt;/FIGURE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 01:14:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83202#M7736</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T01:14:06Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83203#M7737</link>
      <description>&lt;P&gt;My fault on the command - as you correctly replied with, I was looking for the command ‘history’.&lt;/P&gt;&lt;P&gt;But yeah...something’s not right here.&amp;nbsp; Not sure what though.&lt;/P&gt;&lt;P&gt;Wondering if something in WiNG-7 changed with this RFDM-AP distributed firmware upgrade process.&lt;/P&gt;&lt;P&gt;As seen in your earlier MINT link outputs, the RFDM AP has its level-2 MINT link and the non-RFDM AP just has its single level-1 MINT link with the RFDM AP. &amp;nbsp; That’s exactly as it should be. &amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In my lab on a WiNG-5 distributed setup, I clearly see the RFDM AP and non-RFDM APs both showing device-upgrade history info….. and the non-RFDM AP indicates that it was upgraded by the RFDM AP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In addition, you can run this command on the controller and it will also (should) tell you the APs that were upgrade and *which* RFDM AP performed it.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;show device-upgrade history on &amp;lt;RFD&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 01:18:20 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83203#M7737</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-24T01:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83204#M7738</link>
      <description>&lt;P&gt;Chris,&lt;/P&gt;&lt;P&gt;Can you please share the correct output from the controller ?&lt;/P&gt;&lt;P&gt;In the near past tried to make this feature to work with ALL the same topology, but with WING 5.9.3.3 and RFS4000, but with no luck.&lt;/P&gt;&lt;P&gt;So, maybe, we are talking about some very old bug ?&lt;/P&gt;&lt;P&gt;I need this feature working, for our customer with VX and have about 400 branches, so this feature is very important, since WAN links are&amp;nbsp; pretty slow.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 01:36:27 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83204#M7738</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T01:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83205#M7739</link>
      <description>&lt;P&gt;I can certainly testify that this works perfectly in WiNG-5.&amp;nbsp; (Can’t imagine how it would’ve gotten messed up in WiNG-7 though).&amp;nbsp; This topology is used for a HUGE number of deployments.&amp;nbsp; If something was fundamentally broken in this regard, we’d have heard about it long before now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the &lt;STRONG&gt;controller,&lt;/STRONG&gt; my output looks like this:&lt;/P&gt;&lt;P&gt;NX(config)#sh device-upgrade history on LAB&lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Device &amp;nbsp; &amp;nbsp; &amp;nbsp;RESULT &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; TIME &amp;nbsp;RETRIES &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;UPGRADED-BY LAST-UPDATE-ERROR&lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;LAB-MCX &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp; done &amp;nbsp;2019-03-13 13:15:37 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 8533-Floor-2 &amp;nbsp; &amp;nbsp;&amp;nbsp; done &amp;nbsp;2019-03-13 13:14:39 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; 8533-Floor-2 &amp;nbsp; &amp;nbsp;&amp;nbsp; done &amp;nbsp;2018-11-09 12:39:30 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;BR /&gt;Total number of entries displayed: 3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;On the &lt;STRONG&gt;RFDM AP,&lt;/STRONG&gt; the output shows this (the non-RFDM AP output is empty)&lt;/P&gt;&lt;P&gt;(You can see in the first column (Device) the listing of non-RFDM APs that this RFDM AP had upgraded.&lt;/P&gt;&lt;P&gt;8533-Floor-1#sh device-upgrade history&lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;BR /&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Device &amp;nbsp; &amp;nbsp; &amp;nbsp;RESULT &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; TIME &amp;nbsp;RETRIES &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;UPGRADED-BY LAST-UPDATE-ERROR&lt;BR /&gt;-------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;P&gt;&amp;nbsp; 8533-Floor-2 &amp;nbsp; &amp;nbsp; &amp;nbsp; done &amp;nbsp;2019-03-13 13:14:39 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;/P&gt;&lt;P&gt;&amp;nbsp; LAB-MCX &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; done &amp;nbsp;2019-03-13 13:15:37 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;/P&gt;&lt;P&gt;&amp;nbsp; 8533-Floor-2 &amp;nbsp; &amp;nbsp; &amp;nbsp; done &amp;nbsp;2018-11-09 12:39:30 &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;0 &amp;nbsp; &amp;nbsp; &amp;nbsp; 8533-Floor-1 &amp;nbsp; &amp;nbsp;&amp;nbsp; -&lt;BR /&gt;Total number of entries displayed: 3&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 01:53:52 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83205#M7739</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-24T01:53:52Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83206#M7740</link>
      <description>&lt;P&gt;Chris,&lt;/P&gt;&lt;P&gt;I will test also it with 5.9.4.1+ and update you.&lt;/P&gt;&lt;P&gt;RFD without country code and ap profile without rf domain manager capable… I’ll check it...&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 04:05:39 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83206#M7740</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T04:05:39Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83207#M7741</link>
      <description>&lt;P&gt;The AP profile needs to have the RFDM-capable option enabled for this Distributed setup.&amp;nbsp; Otherwise, none of the APs in the ‘remote’ RFD will be able to be elected...and the test won’t work.&lt;/P&gt;&lt;P&gt;From what I can tell, your configuration looks correct, based on the MINT queries you’ve supplied.&amp;nbsp; So you just would want to re-test this again but with 5.9.x&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also….if it still doesn’t work as expected with 5.9.x, try setting the county-code for the “default” RFD.&amp;nbsp; It shouldn’t be necessary, but it’s also very unusual to have an RFD for APs where it isn’t configured.&amp;nbsp; Just want to make sure that this isn’t some sort of weird bug/restriction.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 20:06:11 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83207#M7741</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-24T20:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83208#M7742</link>
      <description>&lt;P&gt;Hello Chris,&lt;/P&gt;&lt;P&gt;Just validated with 5.9.4.1 and working well with the same configuration, so I suggest to test it in your LAB and open case about WING 7.2.1.1 bug. I continue tests with WING5.&lt;/P&gt;&lt;P&gt;But It's important to consider that the first adoption of APS with different OS version from controller requires an upgrade from VX because the aps firstly are without control vlan.&lt;/P&gt;&lt;P&gt;But I think, I can workaround it:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;I can set an enforce-version adoption none +&amp;nbsp; device-upgrade auto on VX.&lt;/LI&gt;&lt;/OL&gt;&lt;OL&gt;&lt;LI&gt;after 1 AP at remote site adopted and configured manually with high RFDM priority, all other APS at the remote site receive the L3 adoption site from dhcp option and VX add to the APS a control vlan. Than VX should upgrade and configure the other APS through RFDM automatically.&lt;BR /&gt;	&amp;nbsp;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I right?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Aviv&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 21:02:19 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83208#M7742</guid>
      <dc:creator>Aviv_Kedem</dc:creator>
      <dc:date>2019-10-24T21:02:19Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading remote site APS through RFDM AP</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83209#M7743</link>
      <description>&lt;P&gt;Aviv,&lt;/P&gt;&lt;P&gt;Are you saying that your initial test here with 7.2 involved an initial adoption scenario where all of the APs needed to be upgraded?&amp;nbsp; If that’s the case, then it is *expected/known* that the 1st upgrade for a remote site WILL require that each AP be upgraded individually by the controller (each AP using its initial level-2 MINT link).&amp;nbsp; Like you mentioned, in this *initial deployment* scenario, the APs are not yet adopted….so they don’t yet have their config...and they don’t have their config yet because they first have to have a matching WiNG firmware version.&amp;nbsp; Once the firmware match requirement is met, they get their config, and then the tear-down from level-2 MINT links to level-1 MINT links (for the non-RFDM APs) is performed and the RFDM is elected.&amp;nbsp; Then going forward, the firmware updates are performed by the RFDM AP.&lt;/P&gt;&lt;P&gt;Trying to circumvent this though by relaxing the version matching requirements is not something you should be doing in a production environment...unless you first thoroughly test the specific setup and accept the responsibility of anything going wrong.&lt;/P&gt;&lt;P&gt;In some cases, doing this might not cause any problems. &amp;nbsp; But doing this can have unexpected results.&amp;nbsp; Using the ability to have non-matching WiNG firmware on the APs should only be used in special cases, and is meant to be a *short-term temporary* solution.&lt;/P&gt;&lt;P&gt;What you are suggesting may in fact work.&amp;nbsp; But if you run into any problems while doing this, it won’t be supported and will not be considered a bug.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Oct 2019 21:19:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-wing/upgrading-remote-site-aps-through-rfdm-ap/m-p/83209#M7743</guid>
      <dc:creator>ckelly</dc:creator>
      <dc:date>2019-10-24T21:19:21Z</dc:date>
    </item>
  </channel>
</rss>

