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#1345 — FS#5346 — vss-1/2/3/4

Attached to Project— Network
Maintenance
Whole Network
CLOSED
100%
In anticipation of the introduction of vss-1b/2b/3b new routers which will help us to get a redundant routing of "first hop", we pass the gateways of each vlan on HSRP.
No expected impact on traffic.
Date:  Friday, 22 April 2011, 07:09AM
Reason for closing:  Done
Comment by OVH - Thursday, 14 April 2011, 14:06PM

The vlans routed by vss-1 were switched.


Comment by OVH - Tuesday, 19 April 2011, 12:17PM

We intervene on the vss-2-6k.


Comment by OVH - Tuesday, 19 April 2011, 13:12PM

Now we intervene on vss-3-6k.


Comment by OVH - Tuesday, 19 April 2011, 15:26PM

We move to vss-4-6k.


Comment by OVH - Thursday, 21 April 2011, 17:31PM

The vss-1b/2b/3b are connected on all vlans routed by vss-1/2/3/4. We configure routing this morning to enable them to resume the traffic in case of interruption of the primary routing. To do this, we need to temporarily freeze the configuration of IP fail-over successively on vss-1/2/3 (between 30min and 1h by router)


Comment by OVH - Thursday, 21 April 2011, 17:31PM

We freeze updates of IPs FO on vss-1-6k.


Comment by OVH - Thursday, 21 April 2011, 17:33PM

Following activation of routing on vss-1b, a part of the internal traffic was impacted from/to networks 94.23.0 57. Randomly, some ips were no longer reachable from other networks in intra ovh.


Comment by OVH - Thursday, 21 April 2011, 17:34PM

We activate the routing on vss-2b/3b/4b.