Aruba Instant AP Advisory (v8.5)

Got this overnight at work.

Who in their right mind thought it would be a good idea to ship a version update that shifts the default interface off the first one? I get one version being an oops, too, but 3? Holy cow.

Hopefully none of you have made the jump yet. I will be holding our ten 375s off for a few months but that's only because we open our gates in 4 days for our big event of the year.

​

Default Uplink Change in Instant 8.5.0.0

Confidentiality Level: Aruba Customers & Partners only | Rev-2 (August 15, 2019)

AFFECTED PRODUCTS

· AP-318, AP-374, AP-375, AP-377 when upgraded from Instant 8.3.x or 8.4.x to Instant 8.5.0.0, 8.5.0.1, or 8.5.0.2

SUMMARY

In Aruba Instant versions prior to 8.5.0.0, the default uplink port for all Instant APs is eth0 (copper interface). Starting from Instant version 8.5.0.0, the default uplink port for AP-318 and 370 series Access Points was changed to eth1 (fiber interface).

Therefore, when an Instant AP network with AP-318 and AP-370 series Access Points using port eth0 for uplink connection,

Is upgraded from Instant 8.3.x.x/8.4.x.x to Instant 8.5.0.0/8.5.0.1/8.5.0.2, OR

Has the IAP configuration reset to factory defaults on Instant 8.5.0.0, 8.5.0.1 or 8.5.0.2,

Then, only the AP-318 and AP-370 series Access Points will get disconnected from the network because their default active uplink port configuration will change from eth0 to eth1.

The disconnected APs can be reconnected to the network by changing the preferred-uplink port configuration from the CLI through the AP’s console.

DESCRIPTION OF THE LIMITATIONS

In troubleshooting this issue, it was found that the original workaround developed would only address the Master AP in an Instant cluster, or an Instant AP in standalone mode. APs that were cluster members (slave or non-master) will not inherit the workaround change, and as a result will be disconnected from the network.

As a result, in an abundance of caution and to ensure we minimize as much as possible the potential impact and downtime of the AP-318/370 series APs, Aruba has removed the firmware image for these AP platforms (named ‘Hercules’) from Support site, Central, and Activate until the firmware with the fix for this issue is released (8.5.0.3). Further, 8.5.0.2 firmware for these AP platforms will be on a ‘controlled release’ until 8.5.0.3 is published. Because the AP-31x and AP-32x APs share and use the same ‘Hercules’ firmware image, the removal of ‘Hercules’ from support sites will also temporarily limit customers using AP-31x and AP-32x seeking to upgrade to 8.5.x.x.

While the AP-31x and AP-32x Access Points are not impacted by the bug, because the ‘Hercules’ firmware is being temporarily removed to protect any impact to customers, customers needing 8.5.0.x for the AP-31x and AP-32x APs will simply need to follow the procedures below pursuant to their deployment to be able to access the firmware. These procedures will not be needed after 8.5.0.3 is released.

RECOMMENDATIONS AND CONDITIONS

The general recommendation for customers who would like to upgrade to Instant 8.5.0.x and have any of IAP-314/315, IAP-324/325, AP-318 and AP-374/375/377/387 in their network is to wait until 8.5.0.3 releases.Confidentiality Level: Aruba Customers & Partners only | Rev-2 (August 15, 2019)

AFFECTED PRODUCTS

· AP-318, AP-374, AP-375, AP-377 when upgraded from Instant 8.3.x or 8.4.x to Instant 8.5.0.0, 8.5.0.1, or 8.5.0.2

SUMMARY

In Aruba Instant versions prior to 8.5.0.0, the default uplink port for all Instant APs is eth0 (copper interface). Starting from Instant version 8.5.0.0, the default uplink port for AP-318 and 370 series Access Points was changed to eth1 (fiber interface).

Therefore, when an Instant AP network with AP-318 and AP-370 series Access Points using port eth0 for uplink connection,

Is upgraded from Instant 8.3.x.x/8.4.x.x to Instant 8.5.0.0/8.5.0.1/8.5.0.2, OR

Has the IAP configuration reset to factory defaults on Instant 8.5.0.0, 8.5.0.1 or 8.5.0.2,

Then, only the AP-318 and AP-370 series Access Points will get disconnected from the network because their default active uplink port configuration will change from eth0 to eth1.

The disconnected APs can be reconnected to the network by changing the preferred-uplink port configuration from the CLI through the AP’s console.

DESCRIPTION OF THE LIMITATIONS

In troubleshooting this issue, it was found that the original workaround developed would only address the Master AP in an Instant cluster, or an Instant AP in standalone mode. APs that were cluster members (slave or non-master) will not inherit the workaround change, and as a result will be disconnected from the network.

As a result, in an abundance of caution and to ensure we minimize as much as possible the potential impact and downtime of the AP-318/370 series APs, Aruba has removed the firmware image for these AP platforms (named ‘Hercules’) from Support site, Central, and Activate until the firmware with the fix for this issue is released (8.5.0.3). Further, 8.5.0.2 firmware for these AP platforms will be on a ‘controlled release’ until 8.5.0.3 is published. Because the AP-31x and AP-32x APs share and use the same ‘Hercules’ firmware image, the removal of ‘Hercules’ from support sites will also temporarily limit customers using AP-31x and AP-32x seeking to upgrade to 8.5.x.x.

While the AP-31x and AP-32x Access Points are not impacted by the bug, because the ‘Hercules’ firmware is being temporarily removed to protect any impact to customers, customers needing 8.5.0.x for the AP-31x and AP-32x APs will simply need to follow the procedures below pursuant to their deployment to be able to access the firmware. These procedures will not be needed after 8.5.0.3 is released.

RECOMMENDATIONS AND CONDITIONS

The general recommendation for customers who would like to upgrade to Instant 8.5.0.x and have any of IAP-314/315, IAP-324/325, AP-318 and AP-374/375/377/387 in their network is to wait until 8.5.0.3 releases.