Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
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
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
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.