OVHcloud Network Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
CSCtr36441
Incident Report for Network & Infrastructure
Resolved
Allelouja !

Après 4 semaines de discutions et d'echange avec TAC
de Cisco, le support de Cisco a mis en evidence un
bug sur la plateforme Nexus 7000 qui nous embete
enormement.

CSCtr36441 Traffic dropped on F1 peer-link for one leg vpc after ISSU

It is not yet externally viewable. Once the release note has been
reviewed it will be published at the above link. The details of the bug
are below:

########################################################

Symptom:

When shutting down one leg of a vPC, packets redirected through the peer
link are dropped.

Conditions:

- ISSU from 5.1(2) to 5.1(3)
- peer-link on a high port-channel number (i.e., peer-link carried on
Po4096)
- All F1 modules
- shutdown/disable vPC on single chassis creating 'one leg' vPC

Workaround:

This issue is not seen when the vPC peer-link port-channel number is
lower than the port-channels carrying vPCs. Therefore, changing the
peer-link port-channel number (i.e., reconfiguring the peer-link from
Po4096 to Po1) would resolve the issue. This would also bounce the
entire vPC domain so it may not be a feasible solution for most
customers.

Reload of both N7k peers

########################################################

This bug will be resolved in 5.2(1) which has not yet been released but
is planned to be released this month. There are two ways to resolve the
issue:

1) ISSU to resolved code once released
2) Since the issue is specific to an ISSU from 5.1(2), a reload of each
N7k will resolve the current state.

Please let me know how you would like to proceed. As always, feel free
to call or email me directly with any questions or concerns.

Merci à la nouvelle équipe Cisco qui suit Ovh depuis 1 mois.
Grâce à leur soutient (morale) on a continué les echanges
pour finalement aboutir à une solution. Les bugs sont tellement
complexe et spécifique qu'il faut 1 mois pour trouver
l'origine du probleme.

On a encore 11 bugs comme ça ...

On avance !
Posted Jul 11, 2011 - 19:45 UTC