Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
Works are scheduled on Tuesday, 27/09/2011 at 11pm.
They will cause about 15 minutes of breakdown on the overall amenity \"virtual rack\".
Update(s):
Date: 2011-09-29 10:51:59 UTC The network has been switched.All is up.
Date: 2011-09-28 00:10:03 UTC A network has been connected \"not properly\" on the old infrastructure and so we forgot to move it.It is in progress.
Po108 fex108|00E04 connected 1 full 10G --
Eth1/8 HG|188.165.15_ connected trunk full 10G 10g
Date: 2011-09-28 00:05:52 UTC False alarm.A configuration problem on hard.so it's okey from the infrastructure's side.Reboot was not necessary.
We are checking some feedbacks of our customers.
Date: 2011-09-28 00:02:15 UTC We isolated the old vrack and connected directly the new one.
We have an N5 of a couple that does not ping. If we load the IP it pings. It doesn't ping on the old IP.
We will reload the N5 that doesn't ping.
Date: 2011-09-28 00:01:17 UTC The FEX of RBX-1-2-3 have been transfered on the final infrastructure.
Date: 2011-09-27 22:12:26 UTC 64 bytes from vrack-2a-n5.fr.eu : icmp_seq=84 ttl=249 time=4.25 ms
64 bytes from vrack-2a-n5.fr.eu : icmp_seq=85 ttl=249 time=4.26 ms
64 bytes from vrack-2a-n5.fr.eu : icmp_seq=86 ttl=249 time=5.99 ms
64 bytes from vrack-2a-n5.fr.eu : icmp_seq=117 ttl=249 time=4.27 ms
64 bytes from vrack-2a-n5.fr.eu : icmp_seq=118 ttl=249 time=4.16 ms
64 bytes from vrack-2a-n5.fr.eu : icmp_seq=119 ttl=249 time=4.19 ms
Done
Date: 2011-09-27 22:11:59 UTC We will reconnect the vrack of RBX4 on the vrack of RBX1/2/3.