rssLink RSS for all categories
 
icon_red
icon_green
icon_red
icon_red
icon_blue
icon_green
icon_green
icon_red
icon_red
icon_red
icon_orange
icon_green
icon_green
icon_green
icon_green
icon_blue
icon_green
icon_orange
icon_red
icon_green
icon_red
icon_red
icon_green
icon_red
icon_red
icon_red
icon_red
icon_orange
icon_green
 

FS#1116 — FS#5127 — iSCSI network of RPS

Attached to Project— Network
Maintenance
Whole Network
CLOSED
100%
We will update the network equipment of the rps iSCSI
storage network. Usually the procedure of
update does not cause any interruption in the service.
But given the sensitive nature of iSCSI it
may be possible to have problems. We'll be there
to fix.


Date:  Wednesday, 16 February 2011, 17:43PM
Reason for closing:  Done
Comment by OVH - Thursday, 10 February 2011, 09:48AM

We interrupt the B side.


Comment by OVH - Thursday, 10 February 2011, 09:49AM

It's done.


Comment by OVH - Thursday, 10 February 2011, 09:49AM

we update the A side which assure all routing.


Comment by OVH - Thursday, 10 February 2011, 09:50AM

A problem.


Comment by OVH - Thursday, 10 February 2011, 09:50AM

A problem.

Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
100 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!
103 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
104 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
105 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
106 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!
107 yes disruptive reset STP ISSU preupgrade check failed - Upgrade needs to be disruptive!


Comment by OVH - Thursday, 10 February 2011, 09:51AM

We cancel. We will open a TAC to understand the problem.


Comment by OVH - Thursday, 10 February 2011, 18:26PM

rps-1a-n5(config)# no spanning-tree vlan 1-3967,4048-4093

ouch


Comment by OVH - Thursday, 10 February 2011, 18:27PM

rps-1b-n5(config)# no spanning-tree vlan 1-3967,4048-4093

up


Comment by OVH - Thursday, 10 February 2011, 19:07PM

So, it was that ...


Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
100 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



Images will be upgraded according to following table:
Module Image Running-Version New-Version
Upg-Required
------ ---------- ---------------------- ----------------------
------------
1 system 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 kickstart 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 bios v1.3.0(09/08/09) v1.3.0(09/08/09)
no
100 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
102 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
103 fexth 4.2(1)N1(1) 5.0(2)N2(1)
yes
104 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
105 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
106 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
107 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 power-seq v1.2 v1.2
no


We are going to do the update one morning.


Comment by OVH - Wednesday, 16 February 2011, 17:17PM

Here we go.


Comment by OVH - Wednesday, 16 February 2011, 17:22PM

The side B is cut.

We are updating the side A with the switches in the racks.
Everything must be done in emergency.


Comment by OVH - Wednesday, 16 February 2011, 17:22PM

Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
100 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



Images will be upgraded according to following table:
Module Image Running-Version New-Version
Upg-Required
------ ---------- ---------------------- ----------------------
------------
1 system 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 kickstart 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 bios v1.3.0(09/08/09) v1.3.0(09/08/09)
no
100 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
102 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
103 fexth 4.2(1)N1(1) 5.0(2)N2(1)
yes
104 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
105 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
106 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
107 fex 4.2(1)N1(1) 5.0(2)N2(1)
yes
1 power-seq v1.2 v1.2
no


Comment by OVH - Wednesday, 16 February 2011, 17:25PM

The side A is up again. 0 packets lost.

We still have the FEX to do.

rps-1a-n5# sh fex detail
FEX: 100 Description: fex100|salle00|00E06 state: Online
FEX version: 4.2(1)N1(1) [Switch version: 5.0(2)N2(1)]
FEX Interim version: 4.2(1)N1(1)
Switch Interim version: 5.0(2)N2(1)


Comment by OVH - Wednesday, 16 February 2011, 17:26PM

rps-1a-n5# sh fex detail
FEX: 100 Description: fex100|salle00|00E06 state: Online
FEX version: 5.0(2)N2(1) [Switch version: 5.0(2)N2(1)]
FEX Interim version: 5.0(2)N2(1)
Switch Interim version: 5.0(2)N2(1)

2011 Feb 16 16:50:03 rps-1b-n5 %VPC-2-VPC_ISSU_START: Peer vPC switch
ISSU start, locking configuration
2011 Feb 16 17:10:37 rps-1b-n5 %VPC-2-VPC_ISSU_END: Peer vPC switch
ISSU end, unlocking configuration


Comment by OVH - Wednesday, 16 February 2011, 17:27PM

We are updating the side B now.


Comment by OVH - Wednesday, 16 February 2011, 17:28PM

2011 Feb 16 17:15:30 rps-1a-n5 %VPC-2-VPC_ISSU_START: Peer vPC switch
ISSU start, locking configuration
2011 Feb 16 17:18:00 rps-1a-n5 %VPC-2-VPC_ISSU_END: Peer vPC switch
ISSU end, unlocking configuration

Done.

We still have the side B to reactivate.


Comment by OVH - Wednesday, 16 February 2011, 17:42PM

Up.

0 packets lost. When it runs well, we have to tell it too.