<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PING LOSS on a specific VLAN in Switching</title>
    <link>https://community.cisco.com/t5/switching/ping-loss-on-a-specific-vlan/m-p/3709534#M448808</link>
    <description>&lt;P&gt;Hello Every one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I've had a unique incident handling over the last four days.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Customer has encountered communication problems with wrong band.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Windows Server ) vlan 21&amp;nbsp; Cluster IP 172.17.21.11&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; |&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( BackBone ) VLAN21&amp;nbsp; ( Nexus 7010 , Catalyst 6509E )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 3750X-24S-S * 2EA)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 2960CX)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Fortinet Firewall )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 2960S Switch )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Server ) 172.29.3.0 /&amp;nbsp; 25&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;consist in this way&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Ping loss has recently occurred in communicating with each server.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Various checks were made to resolve the cause.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;The problem we found and solved today was Catalyst equipment.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;The Nexus 7010 was clean without a PING LOSS.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&lt;SPAN&gt;Only the Catalyst Backbone Switch caused a communication interruption up to the PING LOSS and VLANs on other servers.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&lt;SPAN&gt;Nexus 7010 HSRP Active&amp;nbsp; &amp;amp; Catalyst 6509E HSRP Standby equipment.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;The introduction also caused problems for servers that serve VLAN21 services.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;&lt;SPAN&gt;I wonder if there could be a compatibility issue between the two devices. (&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;Install 3 years ago )&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Please advise.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nexus.JPG" style="width: 399px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/18862i07AF95FB4AFACFC6/image-size/medium?v=v2&amp;amp;px=400" role="button" title="nexus.JPG" alt="nexus.JPG" /&gt;&lt;/span&gt;&lt;SPAN style="font-family: inherit;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="6509" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/18864iAFE0ACED96C78A9F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="6509.JPG" alt="6509" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;6509&lt;/span&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Mar 2019 00:12:04 GMT</pubDate>
    <dc:creator>Yun-Ho KIM</dc:creator>
    <dc:date>2019-03-09T00:12:04Z</dc:date>
    <item>
      <title>PING LOSS on a specific VLAN</title>
      <link>https://community.cisco.com/t5/switching/ping-loss-on-a-specific-vlan/m-p/3709534#M448808</link>
      <description>&lt;P&gt;Hello Every one.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I've had a unique incident handling over the last four days.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Customer has encountered communication problems with wrong band.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Windows Server ) vlan 21&amp;nbsp; Cluster IP 172.17.21.11&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; |&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( BackBone ) VLAN21&amp;nbsp; ( Nexus 7010 , Catalyst 6509E )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&amp;nbsp; &amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 3750X-24S-S * 2EA)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 2960CX)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Fortinet Firewall )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( 2960S Switch )&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;|&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;( Server ) 172.29.3.0 /&amp;nbsp; 25&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;consist in this way&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Ping loss has recently occurred in communicating with each server.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Various checks were made to resolve the cause.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;The problem we found and solved today was Catalyst equipment.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;The Nexus 7010 was clean without a PING LOSS.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&lt;SPAN&gt;Only the Catalyst Backbone Switch caused a communication interruption up to the PING LOSS and VLANs on other servers.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&lt;SPAN&gt;Nexus 7010 HSRP Active&amp;nbsp; &amp;amp; Catalyst 6509E HSRP Standby equipment.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step4__3vbxw"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;The introduction also caused problems for servers that serve VLAN21 services.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&lt;SPAN&gt;&lt;SPAN&gt;I wonder if there could be a compatibility issue between the two devices. (&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;Install 3 years ago )&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="edit_box__1KtZ3 active__3VPGL font_step3__3--df"&gt;
&lt;DIV id="txtTarget" class="edit_box__1KtZ3 active__3VPGL"&gt;&lt;SPAN&gt;Please advise.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="nexus.JPG" style="width: 399px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/18862i07AF95FB4AFACFC6/image-size/medium?v=v2&amp;amp;px=400" role="button" title="nexus.JPG" alt="nexus.JPG" /&gt;&lt;/span&gt;&lt;SPAN style="font-family: inherit;"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-left" image-alt="6509" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/18864iAFE0ACED96C78A9F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="6509.JPG" alt="6509" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;6509&lt;/span&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Mar 2019 00:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/ping-loss-on-a-specific-vlan/m-p/3709534#M448808</guid>
      <dc:creator>Yun-Ho KIM</dc:creator>
      <dc:date>2019-03-09T00:12:04Z</dc:date>
    </item>
  </channel>
</rss>

