<?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 Re: Probe on CSM ??? in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491060#M9274</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is what it looks like.&lt;/P&gt;&lt;P&gt;Are you using Gig module ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Aug 2005 06:16:30 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2005-08-29T06:16:30Z</dc:date>
    <item>
      <title>Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491051#M9265</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have one CSM in two 6500 switches in active-passive configuration, in CSM inline mode. ( so the L3 inter-server communications go through the CSM with predictor forward)&lt;/P&gt;&lt;P&gt;Here the details:&lt;/P&gt;&lt;P&gt;- one CSM (4.1.5) in one C6509 switch with SUP2/MSFC2 using IOS 12.1(19)EA1, which is active&lt;/P&gt;&lt;P&gt;- and one CSM(4.1.5) in one C6513 switch with SUP720 using IOS 12.2(18)SXD3, which is passive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have defined two probes: one L4 and one L7. These two probes are attached to the serverfarm. A vserver is also defined.&lt;/P&gt;&lt;P&gt;When i test the first server with shut the service, the active CSM remove the failed server from the serverfarm but also desactivates the real server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i try on the backup CSM, it works very well: the csm remove only the failed server but not desactivate the real.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where is the problem? any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Silvere&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2005 17:30:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491051#M9265</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-16T17:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491052#M9266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Silvere,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you please clarify what you mean by desactivate the real ??&lt;/P&gt;&lt;P&gt;Could you capture the following commands :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sho mod csm X probe det&lt;/P&gt;&lt;P&gt;sho mod csm x real&lt;/P&gt;&lt;P&gt;sho mod csm x probe&lt;/P&gt;&lt;P&gt;sho mod csm x vserver&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2005 07:37:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491052#M9266</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-17T07:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491053#M9267</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here in copy the log you requested. In addition, i have put in a ping test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i say the CSM desactivate the real, i mean that the real is not reachable on the active CSM - on MSFC2 with 12.1(19)EA1-. ping failed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i move to the backup CSM it works - on Sup-720 with 12.2(18)SXD3- .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Aug 2005 08:38:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491053#M9267</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-17T08:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491054#M9268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this info does not show any problem.&lt;/P&gt;&lt;P&gt;So, the concern is that you can't ping from MSFC to real.&lt;/P&gt;&lt;P&gt;How is the MSFC reaching the real ?&lt;/P&gt;&lt;P&gt;Does it have a static route pointing to the CSM ?&lt;/P&gt;&lt;P&gt;Is the CSM configured in bridge mode ?&lt;/P&gt;&lt;P&gt;Can you ping the real from the CSM or from the other real ? [ to ping from the CSM use the command -ping mod csm X x.x.x.x]&lt;/P&gt;&lt;P&gt;Can we see your config ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Aug 2005 08:19:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491054#M9268</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-18T08:19:37Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491055#M9269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gilles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the HTTP probes failed, the "ping mod csm" works&lt;/P&gt;&lt;P&gt;but from the MSFC, it failed. &lt;/P&gt;&lt;P&gt;on the csm  to msfc, a default route  on the vlan client 0.0.0.0 0.0.0 gateway hsrp msfc&lt;/P&gt;&lt;P&gt;on the MSFC, a static route 10.190.6.0 255.255.255.0 alias CSM is also here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2005 12:33:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491055#M9269</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-25T12:33:37Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491056#M9270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;to allow traffic to pass from client to server, a vserver must be configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try to configure something like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;serverfarm route&lt;/P&gt;&lt;P&gt;  predictor forward&lt;/P&gt;&lt;P&gt;  no nat server&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;vserver vlan190&lt;/P&gt;&lt;P&gt;  vip 10.190.6.0/24&lt;/P&gt;&lt;P&gt;  serverfarm route&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if that solves the ping from the MSFC.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you can, I appreciate ratings for my answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2005 13:11:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491056#M9270</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-25T13:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491057#M9271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vserver is also configured: here the configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vlan 51 client&lt;/P&gt;&lt;P&gt;  ip address 10.190.8.37 255.255.255.240&lt;/P&gt;&lt;P&gt;  route 0.0.0.0 0.0.0.0 gateway 10.190.8.33&lt;/P&gt;&lt;P&gt;  alias 10.190.8.36 255.255.255.240&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; serverfarm R-ROUTING51-40&lt;/P&gt;&lt;P&gt;  no nat server &lt;/P&gt;&lt;P&gt;  no nat client&lt;/P&gt;&lt;P&gt;  predictor forward &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt; vserver VR-ROUTING51-40&lt;/P&gt;&lt;P&gt;  virtual 10.190.6.0 255.255.255.128 any&lt;/P&gt;&lt;P&gt;  vlan 51&lt;/P&gt;&lt;P&gt;  serverfarm R-ROUTING51-40&lt;/P&gt;&lt;P&gt;  replicate csrp sticky&lt;/P&gt;&lt;P&gt;  replicate csrp connection&lt;/P&gt;&lt;P&gt;  no persistent rebalance&lt;/P&gt;&lt;P&gt;  inservice&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Vlan51&lt;/P&gt;&lt;P&gt; ip address 10.190.8.34 255.255.255.240&lt;/P&gt;&lt;P&gt; no ip redirects&lt;/P&gt;&lt;P&gt; standby 51 ip 10.190.8.33&lt;/P&gt;&lt;P&gt; standby 51 priority 110&lt;/P&gt;&lt;P&gt; standby 51 preempt&lt;/P&gt;&lt;P&gt; standby 51 track Port-channel1 10&lt;/P&gt;&lt;P&gt; standby 51 track Port-channel2 &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip route 10.190.6.0 255.255.255.0 10.190.8.36&lt;/P&gt;&lt;P&gt;ip route 10.190.7.0 255.255.255.0 10.190.8.36&lt;/P&gt;&lt;P&gt;ip route 10.190.8.0 255.255.255.224 10.190.8.36&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#sh ip route static &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S       10.190.6.0/24 [1/0] via 10.190.8.36&lt;/P&gt;&lt;P&gt;S       10.190.7.0/24 [1/0] via 10.190.8.36&lt;/P&gt;&lt;P&gt;S       10.190.8.4/32 [1/0] via 10.190.8.36, Vlan51&lt;/P&gt;&lt;P&gt;S       10.190.8.5/32 [1/0] via 10.190.8.36, Vlan51&lt;/P&gt;&lt;P&gt;S       10.190.8.6/32 [1/0] via 10.190.8.36, Vlan51&lt;/P&gt;&lt;P&gt;S       10.190.8.7/32 [1/0] via 10.190.8.36, Vlan51&lt;/P&gt;&lt;P&gt;S       10.190.8.0/27 [1/0] via 10.190.8.36&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;#ping mod csm 9 10.190.6.11&lt;/P&gt;&lt;P&gt;IP address       Reachable&lt;/P&gt;&lt;P&gt;--------------------------&lt;/P&gt;&lt;P&gt;10.190.6.11      Yes&lt;/P&gt;&lt;P&gt;#ping mod csm 9 10.190.6.12&lt;/P&gt;&lt;P&gt;IP address       Reachable&lt;/P&gt;&lt;P&gt;--------------------------&lt;/P&gt;&lt;P&gt;10.190.6.12      Yes&lt;/P&gt;&lt;P&gt;#ping 10.190.6.11          &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type escape sequence to abort.&lt;/P&gt;&lt;P&gt;Sending 5, 100-byte ICMP Echos to 10.190.6.11, timeout is 2 seconds:&lt;/P&gt;&lt;P&gt;!!!!!&lt;/P&gt;&lt;P&gt;Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms&lt;/P&gt;&lt;P&gt;#ping 10.190.6.12&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Type escape sequence to abort.&lt;/P&gt;&lt;P&gt;Sending 5, 100-byte ICMP Echos to 10.190.6.12, timeout is 2 seconds:&lt;/P&gt;&lt;P&gt;.....&lt;/P&gt;&lt;P&gt;Success rate is 0 percent (0/5)&lt;/P&gt;&lt;P&gt;#&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2005 13:57:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491057#M9271</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-25T13:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491058#M9272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok - this looks good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you get a 'sho mod csm X conn vser VR-ROUTING51-40' and a 'sho mod csm x vser name VR-ROUTING51-40 det' before and after the ping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the server, could you sniff the traffic to see if something is getting there, and if there is a response to which mac address is it sent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, can we get a 'sho mod csm x arp' after the test.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2005 14:48:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491058#M9272</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-25T14:48:02Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491059#M9273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gilles, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is very strange. I did many trace. I have sniffed the vlan client (between the MSFC and CSM) and the vlan server . When i ping the server, i see the ICMP echo request across the vlan client and vlan server. but no reply across the vlan server. On the server, the ICMP echo request don't received. So i sniff the port and the ICMP echo request is not sent through the port. &lt;/P&gt;&lt;P&gt;When i desactivate the probe, all works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So as L2port-MSFC-CSM-L2port architecture, the problem is the ICMP packet echo request go out the CSM vlan client but do not enter on L2 port via the IOS.&lt;/P&gt;&lt;P&gt;So the bug is the IOS version  of the switch which is bugged. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2005 14:19:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491059#M9273</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-26T14:19:47Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491060#M9274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this is what it looks like.&lt;/P&gt;&lt;P&gt;Are you using Gig module ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 06:16:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491060#M9274</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-29T06:16:30Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491061#M9275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, configured in 100 Full duplex. Here below the reference:&lt;/P&gt;&lt;P&gt;SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 06:50:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491061#M9275</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-29T06:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491062#M9276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;this could be this well-known issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www-tac.cisco.com/Support_Library/field_alerts/fn26096.html" target="_blank"&gt;http://www-tac.cisco.com/Support_Library/field_alerts/fn26096.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have a FE module, try to use it to confirm the problem is the Gig module.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 11:26:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491062#M9276</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-29T11:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491063#M9277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hum, i can't access to this url...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 13:10:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491063#M9277</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-08-29T13:10:06Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491064#M9278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sorry - that was the internal link.&lt;/P&gt;&lt;P&gt;Try this one&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/switches/ps700/products_field_notice09186a0080228f16.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/switches/ps700/products_field_notice09186a0080228f16.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Aug 2005 13:36:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491064#M9278</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-08-29T13:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491065#M9279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gilles, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have open a case (TAC Cisco). After analyzing our problem, it reveals that CSM 4.2(2) and 4.1(5) has a bug. I 'm witing the return from Cisco Engineer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for your help, i have learnt a little more on  CSM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Sep 2005 19:40:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491065#M9279</guid>
      <dc:creator>edaguet</dc:creator>
      <dc:date>2005-09-06T19:40:48Z</dc:date>
    </item>
    <item>
      <title>Re: Probe on CSM ???</title>
      <link>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491066#M9280</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the update.&lt;/P&gt;&lt;P&gt;I was actually aware of the case as the TAC engineer came to us for an explanation &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;G.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Sep 2005 06:11:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/probe-on-csm/m-p/491066#M9280</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-09-07T06:11:16Z</dc:date>
    </item>
  </channel>
</rss>

