OVHcloud Network Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#16628 — bhs4-16a/b-n56
Scheduled Maintenance Report for Network & Infrastructure
Completed
We will update this pair in Nexus release 7.1.3.N1.2
The intervention is planned for February 18, 2016 as of 8:00 am CEST (2:00 pm EST)

The aim is primarily a bug fix on 2348:
- Better interop between 2348 and intel 10GBaseT x555 / 557
- Bug counter fex2348
- Bug fix, among other vpc the mismatch speed, but also on crash pfstat, ptplc, port-channel, dry-port.

The update will happen in two phases:
- The update of the nexus NXOS and fex (non-disruptive)
- The last day of Broadcom PHY in fex2348 (Firmware low that manages eth) (breakdown)


A sh install all impact shows that will be hitless in ISSU
bhs4-16a-n56# show install all impact system n6000-uk9.7.1.3.N1.2.bin kickstart n6000-uk9-kickstart.7.1.3.N1.2.bin

Verifying image bootflash:/n6000-uk9-kickstart.7.1.3.N1.2.bin for boot variable \"kickstart\".
[####################] 100% -- SUCCESS

Verifying image bootflash:/n6000-uk9.7.1.3.N1.2.bin for boot variable \"system\".
[####################] 100% -- SUCCESS

Verifying image type.
[####################] 100% -- SUCCESS

Extracting \"system\" version from image bootflash:/n6000-uk9.7.1.3.N1.2.bin.
[####################] 100% -- SUCCESS

Extracting \"kickstart\" version from image bootflash:/n6000-uk9-kickstart.7.1.3.N1.2.bin.
[####################] 100% -- SUCCESS

Extracting \"bios\" version from image bootflash:/n6000-uk9.7.1.3.N1.2.bin.
[####################] 100% -- SUCCESS

Extracting \"fexth\" version from image bootflash:/n6000-uk9.7.1.3.N1.2.bin.
[####################] 100% -- SUCCESS

Extracting \"fex4\" version from image bootflash:/n6000-uk9.7.1.3.N1.2.bin.
[####################] 100% -- SUCCESS

Performing module support checks.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS



Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
2 yes non-disruptive rolling
100 yes non-disruptive rolling
101 yes non-disruptive rolling
102 yes non-disruptive rolling
103 yes non-disruptive rolling
104 yes non-disruptive rolling
105 yes non-disruptive rolling
106 yes non-disruptive rolling
107 yes non-disruptive rolling
108 yes non-disruptive rolling
109 yes non-disruptive rolling
110 yes non-disruptive rolling
111 yes non-disruptive rolling
112 yes non-disruptive rolling
113 yes non-disruptive rolling
114 yes non-disruptive rolling
115 yes non-disruptive rolling
116 yes non-disruptive rolling
117 yes non-disruptive rolling
118 yes non-disruptive rolling
119 yes non-disruptive rolling
120 yes non-disruptive rolling



Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------------- ---------------------- ---------------------- ------------
1 system 7.1(2)N1(1) 7.1(3)N1(2) yes
1 kickstart 7.1(2)N1(1) 7.1(3)N1(2) yes
1 bios v2.1.2(07/16/2014) v2.1.2(07/16/2014) no
1 power-seq v4.0 v4.0 no
1 fabric-power-seq v4.0 v4.0 no
2 power-seq v4.0 v4.0 no
100 fexth 7.1(2)N1(1) 7.1(3)N1(2) yes
101 fexth 7.1(2)N1(1) 7.1(3)N1(2) yes
102 fexth 7.1(2)N1(1) 7.1(3)N1(2) yes
103 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
104 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
105 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
106 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
107 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
108 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
109 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
110 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
111 fexth 7.1(2)N1(1) 7.1(3)N1(2) yes
112 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
113 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
114 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
115 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
116 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
117 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
118 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
119 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
120 fex4 7.1(2)N1(1) 7.1(3)N1(2) yes
1 microcontroller v0.0.0.15 v0.0.0.15 no

However, so that the fex can update the PHY, it is mandatory to reload the fex (it is a low level component that can not be hot maj).
We will do this fex by fex after the shift of NXOS, this implies a downtime of 2-3min per fex.
Posted Feb 16, 2016 - 15:03 UTC