Memes symptomes à PA-3, assez réguliers en fait :

Jan 24 13:58:52: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 13:58:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 24 14:05:16: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 24 14:05:17: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 24 14:06:49: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 14:06:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 24 14:08:08: %LINK-5-CHANGED: Interface GigabitEthernet2/0/4, changed state 
to administratively down
Jan 24 14:08:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 24 14:08:12: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 14:08:13: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 24 14:18:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 24 14:18:37: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 24 14:19:25: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 14:19:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 24 14:33:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 24 14:33:36: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 24 14:37:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 14:37:05: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 24 18:21:02: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Jan 24 18:21:02: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Jan 24 18:21:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 24 18:21:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 24 18:21:32: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Jan 24 18:21:34: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 24 18:21:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 25 04:41:19: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Jan 25 04:41:19: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Jan 25 04:41:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 25 04:41:21: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 25 04:41:49: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Jan 25 04:41:51: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 25 04:41:52: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 25 12:38:09: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Jan 25 12:38:09: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Jan 25 12:38:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 25 12:38:11: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 25 12:38:39: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Jan 25 12:38:41: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 25 12:38:42: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 26 12:17:52: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Jan 26 12:17:52: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Jan 26 12:17:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 26 12:17:54: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 26 12:18:22: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Jan 26 12:18:24: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 26 12:18:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Jan 29 06:41:58: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Jan 29 06:41:58: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Jan 29 06:41:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Jan 29 06:42:00: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Jan 29 06:42:28: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Jan 29 06:42:30: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Jan 29 06:42:31: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  1 21:31:11: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  1 21:31:11: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  1 21:31:12: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  1 21:31:13: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  1 21:31:41: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  1 21:31:43: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  1 21:31:44: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  2 12:26:57: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  2 12:26:57: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  2 12:26:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  2 12:26:59: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  2 12:27:27: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  2 12:27:29: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  2 12:27:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  3 01:15:53: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  3 01:15:53: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  3 01:15:54: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  3 01:15:55: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  3 01:16:23: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  3 01:16:25: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  3 01:16:26: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  3 03:05:36: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  3 03:05:36: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  3 03:05:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  3 03:05:38: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  3 03:06:06: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  3 03:06:08: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  3 03:06:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  3 11:49:03: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  3 11:49:03: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  3 11:49:04: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  3 11:49:05: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  3 11:49:33: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  3 11:49:35: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  3 11:49:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  3 15:21:08: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  3 15:21:08: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  3 15:21:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  3 15:21:10: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  3 15:21:38: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  3 15:21:40: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  3 15:21:41: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  4 07:21:52: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  4 07:21:52: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  4 07:21:53: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  4 07:21:54: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  4 07:22:22: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  4 07:22:24: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  4 07:22:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  5 03:03:05: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  5 03:03:05: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  5 03:03:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  5 03:03:07: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  5 03:03:35: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  5 03:03:37: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  5 03:03:38: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
Feb  6 09:30:02: %UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gi2/0/4, 
aggressive mode failure detected
Feb  6 09:30:02: %PM-4-ERR_DISABLE: udld error detected on Gi2/0/4, putting 
Gi2/0/4 in err-disable state
Feb  6 09:30:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to down
Feb  6 09:30:04: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to down
Feb  6 09:30:32: %PM-4-ERR_RECOVER: Attempting to recover from udld err-disable 
state on Gi2/0/4
Feb  6 09:30:34: %LINK-3-UPDOWN: Interface GigabitEthernet2/0/4, changed state 
to up
Feb  6 09:30:35: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
GigabitEthernet2/0/4, changed state to up
-----Message d'origine-----
De : frnog-requ...@frnog.org [mailto:frnog-requ...@frnog.org] De la part de 
Jean-Philippe Castanet
Envoyé : mardi 6 février 2018 10:32
À : 'Raphael Maunier' <raph...@maunier.net>; 'David Ponzone' 
<david.ponz...@gmail.com>
Cc : 'frnog-al...@frnog.org' <frnog-al...@frnog.org>
Objet : RE: [FRnOG] [ALERT] Equinix-IX : Plouf

Bonjour Raphael,

Comme tu l'as évoqué dans ton message initial, c'est probablement du a un souci 
de connectique (Panneau de brassage, jarretière défaillante, XFP , etc ...) sur 
le lien te donnant accès au service IX, à ma connaissance aucun autre port 
n'est affecté.

Peux-tu ouvrir également un incident auprès de notre NOC.


Merci.

-----Original Message-----
From: frnog-requ...@frnog.org [mailto:frnog-requ...@frnog.org] On Behalf Of 
Raphael Maunier
Sent: 06 February 2018 10:13
To: David Ponzone
Cc: frnog-al...@frnog.org
Subject: Re: [FRnOG] [ALERT] Equinix-IX : Plouf

j’ai reçu des messages en privé,

il y a eu des soucis sur plusieurs ports ( et pas que depuis ce matin) , mais 
pas toute la fabric

Bref, j’ai shut et j’attends un retour du support

Raphael


> On 6 Feb 2018, at 10:06, David Ponzone <david.ponz...@gmail.com> wrote:
>
> Pareil, rien ici sur PA3.
> J'ai même toujours le trafic unknown unicast, donc tout est normal :)
>
>
>
> Le 6 févr. 2018 à 10:04, Cédric Bassaget a écrit :
>
>> Pas de problème sur PA3 de mon côté
>>
>> Le 6 février 2018 à 09:58, Raphael Maunier <raph...@maunier.net 
>> <mailto:raph...@maunier.net>> a écrit :
>>
>>> PA2, ça vient de reflaper bien gentillement.
>>>
>>> Encore un soucis sur la mmr. Et ce qui est top, c’est que ça flappe 
>>> rapidement et que ça revient, juste le temps de faire des drops bien 
>>> sympathique
>>>
>>> Raphael
>>>
>>>
>>>> On 6 Feb 2018, at 09:50, VAHE Thomas <tv...@fltechno.scc.com 
>>>> <mailto:tv...@fltechno.scc.com>> wrote:
>>>>
>>>> Bonjour,
>>>>
>>>> Rien à PA2 et PA6.
>>>>
>>>> Cdt,
>>>>
>>>>
>>>> Thomas VAHE •
>>>>
>>>>
>>>>
>>>>
>>>> -----Message d'origine-----
>>>> De : frnog-requ...@frnog.org <mailto:frnog-requ...@frnog.org> 
>>>> [mailto:frnog-requ...@frnog.org] De la
>>> part de Raphael Maunier
>>>> Envoyé : mardi 6 février 2018 09:44 À : frnog-al...@frnog.org 
>>>> <mailto:frnog-al...@frnog.org> Objet : [FRnOG] [ALERT] Equinix-IX :
>>>> Plouf
>>>>
>>>> Hello,
>>>>
>>>> Visiblement c’est un début d’année bien chargé. J’ai un gros plouf 
>>>> sur
>>> le trafic Equinix-IX. Drop du trafic puis port down ( le temps de 
>>> faire des dégats avant que les sessions ne tombent )
>>>>
>>>> Vous avez eu la meme , vers 09h23 ?
>>>>
>>>> Raphael
>>>>
>>>>
>>>> ---------------------------
>>>> Liste de diffusion du FRnOG
>>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&;
>>>> d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6s
>>>> lz_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx
>>>> 8_pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9a
>>>> Jut-bZpyI5kQ&e=
>>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_
>>>> &d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6
>>>> slz_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACt
>>>> x8_pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9
>>>> aJut-bZpyI5kQ&e=>
>>>>
>>>> ___________________________________________________________________
>>>> ___ Ce message contient des informations dont le contenu est 
>>>> susceptible
>>> d'etre confidentiel.
>>>> Il est destine au(x) destinataire(s) indique(s) exclusivement.
>>>>
>>>> A moins que vous ne fassiez partie de la liste des destinataires, 
>>>> ou que
>>> vous soyez habilite a recevoir le mail a leur place, il vous est 
>>> interdit de le copier, de l'utiliser ou de devoiler son contenu a un tiers.
>>>>
>>>> Si vous avez recu cet email par erreur, merci de prendre contact 
>>>> avec
>>> l'emetteur.
>>>>
>>>> Les opinions exprimees dans cet e-mail sont celles de l'emetteur et 
>>>> ne
>>> refletent pas necessairement celles de l'entreprise.
>>>>
>>>> Ce e-mail peut contenir des pieces jointes dont certaines 
>>>> pourraient
>>> contenir des virus qui pourraient endommager votre systeme informatique.
>>>>
>>>> La compagnie a pris toutes dispositions afin de minimiser ce risque 
>>>> et
>>> decline toute responsabilite pour toute perte ou dommage resultant 
>>> directement ou indirectement de l'utilisation de cet email ou de son 
>>> contenu.
>>>>
>>>> Il vous appartient d'effectuer vos propres controles anti-virus 
>>>> avant
>>> d'ouvrir la ou les pieces jointes.
>>>> ___________________________________________________________________
>>>> ___
>>>>
>>>> ---------------------------
>>>> Liste de diffusion du FRnOG
>>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&;
>>>> d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6s
>>>> lz_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx
>>>> 8_pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9a
>>>> Jut-bZpyI5kQ&e=
>>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_
>>>> &d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6
>>>> slz_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACt
>>>> x8_pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9
>>>> aJut-bZpyI5kQ&e=>
>>>
>>>
>>> ---------------------------
>>> Liste de diffusion du FRnOG
>>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&d
>>> =DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6slz
>>> _nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx8_p
>>> nYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9aJut-
>>> bZpyI5kQ&e=
>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&;
>>> d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6sl
>>> z_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx8_
>>> pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9aJut
>>> -bZpyI5kQ&e=>
>>>
>>
>> ---------------------------
>> Liste de diffusion du FRnOG
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&d=
>> DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6slz_n
>> ZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx8_pnYK
>> 1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9aJut-bZpy
>> I5kQ&e=
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&d
>> =DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6slz_
>> nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx8_pnY
>> K1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9aJut-bZp
>> yI5kQ&e=>
>


---------------------------
Liste de diffusion du FRnOG
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.frnog.org_&d=DwIFaQ&c=gxW9PgscCAGwFImBgfkGkoANogu61GVPNv0sglxAtik&r=IXI2Y2KJ6slz_nZhUqGTJeYFpdy_zsEvdIEeOYoISRnLqDCSUEx3SKc8R1-MsCKj&m=1NCAqAACtx8_pnYK1Y1kPul7Li8XV3jlylwsHWVFROk&s=8oKD3H2aNnCmnEPr8AEYRsjG-CPtl9aJut-bZpyI5kQ&e=
This email is from Equinix (EMEA) B.V. or one of its associated companies in 
the territory from where this email has been sent. This email, and any files 
transmitted with it, contains information which is confidential, is solely for 
the use of the intended recipient and may be legally privileged. If you have 
received this email in error, please notify the sender and delete this email 
immediately. Equinix (EMEA) B.V.. Registered Office: Amstelplein 1, 1096 HA 
Amsterdam, The Netherlands. Registered in The Netherlands No. 57577889.

---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/

---------------------------
Liste de diffusion du FRnOG
http://www.frnog.org/

Répondre à