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#5352 — FS#9274 — vac2-10-tms

Attached to Project— Anti-DDoS
Incident
Paris DC1
CLOSED
100%
We had a problem on the Arbor
TMS 4000 box of VAC2 last week.
One of the mitigation cards
is dead and we are waiting for
the replacement:
http://status.ovh.co.uk/?do=details&id=5335

The 2 remaining cards are visibly not in the
best condition. We have just shut down VAC2.

TMS Fault
Appliance: vac2-10-tms
Subhost 'apm-0-0' is 'Inactive'
We are looking into the problem with Arbor but
card 0 seems dead as well as the 2nd...
Date:  Wednesday, 11 September 2013, 00:28AM
Reason for closing:  Done
Comment by OVH - Monday, 09 September 2013, 10:26AM

apm-0-0- has refused to recover with gentler measures.
..
The latest attempt to restart apm-0-0 appears to have succeeded.
..
apm-0-0 crashed again after restart.
..
Looks like the appliance reboot was able to recover this TMS 4000.
All appears to be functioning correctly at this time.


Comment by OVH - Monday, 09 September 2013, 10:27AM

We are seeing how to reinstall the profiles on the TMS
that rebooted without doing a STOP START on them.


Comment by OVH - Monday, 09 September 2013, 10:28AM

We have put VAC2 back in production.


Comment by OVH - Monday, 09 September 2013, 10:29AM

The box crashed again.

TMS Fault
Appliance: vac2-10-tms
Subhost 'apm-0-1' is 'Inactive'


Comment by OVH - Monday, 09 September 2013, 10:30AM

The APM-E blade is failing to boot correctly.
We will request an RMA of the APM-E blade.


Comment by OVH - Monday, 09 September 2013, 15:42PM

We rebooted the chassis with an APM card
that we received as an RMA.


Comment by OVH - Tuesday, 10 September 2013, 10:03AM

TMS Fault
Appliance: vac2-10-tms
Subhost 'apm-0-1' is 'Inactive'

The new APM card crashed. It will be the chassis ..


Comment by OVH - Tuesday, 10 September 2013, 10:10AM

We have found a bug in the in the naming of cards
between the chassis, the Arbor documentation and the
SHELL commands output.

We've just replaced the cards again.

We have restored the traffic.


Comment by OVH - Tuesday, 10 September 2013, 10:16AM

The tracking of card n° written on the chassis and
in the system is not the same. When the card in
slot 3 (CLI) must be changed, the card is slot 2
(phsyical) must be withdrawn.
Totally illogical. We will put labels on the
chassis so that tracking is the same between the
CLI and the physical.

==================

The mapping of Slot Number (physical labeling) and that shown by CLI commands for TMS-4000 series is as below:

Slot Number Physical Labeling
Shelf Manager
0 MCM
1 PSM
2 APM
3 APM
4 APM
5 APM

Slot Number CLI (/ system hardware)
0 Shelf Manager
1 MCM
2 PSM
3 APM
4 APM
5 APM
6 APM


Comment by OVH - Tuesday, 10 September 2013, 17:11PM

The chassis seems stable.

We will add the 3rd card. We are shutting down VAC2.


Comment by OVH - Wednesday, 11 September 2013, 00:27AM

We have reset the box. It is stable.