{"id":11,"date":"2010-09-02T11:13:18","date_gmt":"2010-09-02T09:13:18","guid":{"rendered":"http:\/\/www.zed-network.fr\/blog\/?p=11"},"modified":"2010-09-05T13:34:34","modified_gmt":"2010-09-05T11:34:34","slug":"cisco-link-state-traking","status":"publish","type":"post","link":"https:\/\/zed-network.fr\/?p=11","title":{"rendered":"Cisco Link State Tracking"},"content":{"rendered":"<p>Link State Tracking est tr\u00e8s utile pour les architectures en haute disponibilit\u00e9. En effet lorsque l&#8217;on connecte un serveur en teaming sur deux switchs diff\u00e9rents pour la redondance, si l&#8217;uplink est down alors le port de downstream reste up. Cela peut occasionner un vrai dysfonctionnement au niveau de l&#8217;accessibilit\u00e9 des serveurs.<\/p>\n<p>La premi\u00e8re solution consiste \u00e0 mettre un lien entre les deux switchs d&#8217;acc\u00e8s mais ca devient rapidement compliqu\u00e9 et dangereux niveau Spanning-Tree.<\/p>\n<p>Seconde solution et certainement bien meilleur : la feature Link-State Tracking.<\/p>\n<p>Consid\u00e9rons une architecture avec X serveurs double attach\u00e9s sur deux switchs d&#8217;acces eux m\u00eame avec un double attachement sur la partie distribution.<\/p>\n<p>Si la partie Upstream est down alors la partie downstream passe en err-disabled.<\/p>\n<p>Cons\u00e9quence : Lorsque le port primaire du teaming est down le teaming effectue sont failover sur le second lien.<\/p>\n<p>&#8212;<\/p>\n<p>Exemple : Uplink interface Gi0\/21 et 22 et port serveur Gi0\/1, Gi0\/3, Gi0\/5<\/p>\n<div>\n<pre>Switch# <strong>configure terminal<\/strong>\r\n<\/pre>\n<\/div>\n<pre><a name=\"wp1285367\"><\/a><\/pre>\n<div>\n<pre>Switch(config)# <strong>link state track 1\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285368\"><\/a><\/pre>\n<div>\n<pre>Switch(config)# <strong>interface range gigabitethernet0\/21 -22<\/strong>\r\n<\/pre>\n<\/div>\n<pre><a name=\"wp1285369\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>link state group 1 upstream\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285370\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>interface gigabitethernet0\/1\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285371\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>link state group 1 downstream\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285372\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>interface gigabitethernet0\/3\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285373\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>link state group 1 downstream\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285374\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>interface gigabitethernet0\/5\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285375\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>link state group 1 downstream\r\n<\/strong><\/pre>\n<\/div>\n<pre><a name=\"wp1285376\"><\/a><\/pre>\n<div>\n<pre>Switch(config-if)# <strong>end\r\n<\/strong><\/pre>\n<\/div>\n<p><a href=\"http:\/\/www.cisco.com\/en\/US\/docs\/switches\/lan\/catalyst2960\/software\/release\/12.2_25_see\/configuration\/guide\/swethchl.html#wp1285238\" target=\"_blank\">Lien cisco de la documentation<\/a><\/p>\n<address>\n<\/address>\n","protected":false},"excerpt":{"rendered":"<p>Link State Tracking est tr\u00e8s utile pour les architectures en haute disponibilit\u00e9. En effet lorsque l&#8217;on connecte un serveur en teaming sur deux switchs diff\u00e9rents pour la redondance, si l&#8217;uplink est down alors le port de downstream reste up. Cela peut occasionner un vrai dysfonctionnement au niveau de l&#8217;accessibilit\u00e9 des serveurs. La premi\u00e8re solution consiste [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"footnotes":""},"categories":[4],"tags":[20,6,5],"class_list":["post-11","post","type-post","status-publish","format-standard","hentry","category-cisco","tag-cisco","tag-link-state","tag-redondance"],"_links":{"self":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/11","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=11"}],"version-history":[{"count":7,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/11\/revisions"}],"predecessor-version":[{"id":31,"href":"https:\/\/zed-network.fr\/index.php?rest_route=\/wp\/v2\/posts\/11\/revisions\/31"}],"wp:attachment":[{"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=11"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=11"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zed-network.fr\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=11"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}