Cisco IP SLA monitor failure on tcpConnect but the host can be telneted from routerCisco SNMP OID for...

Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?

A faster way to compute the largest prime factor

Negative Resistance

How to not starve gigantic beasts

A Paper Record is What I Hamper

Complex numbers z=-3-4i polar form

How exactly does Hawking radiation decrease the mass of black holes?

Double-nominative constructions and “von”

Philosophical question on logistic regression: why isn't the optimal threshold value trained?

Why doesn't the standard consider a template constructor as a copy constructor?

How to keep bees out of canned beverages?

What does "function" actually mean in music?

Why is the underscore command _ useful?

Drawing a german abacus as in the books of Adam Ries

What is the most expensive material in the world that could be used to create Pun-Pun's lute?

Where was the County of Thurn und Taxis located?

Unknown code in script

Island of Knights, Knaves and Spies

What is the unit of time_lock_delta in LND?

Can a stored procedure reference the database in which it is stored?

How can I practically buy stocks?

How much of a wave function must reside inside event horizon for it to be consumed by the black hole?

Why did C use the -> operator instead of reusing the . operator?

Why did Rep. Omar conclude her criticism of US troops with the phrase "NotTodaySatan"?



Cisco IP SLA monitor failure on tcpConnect but the host can be telneted from router


Cisco SNMP OID for track/SLA monitorCan I tail the log on a Cisco Router?Cisco 1800 Router, dual ISP but one firewallHow can I simulate a Cisco router LAN card failure?cisco 6500 crash enabling netflowUnexplained 0.1% packets time out when pinging from routerConfiguring Dialout with the Cisco 2500 routerDual ISP Inbound NAT — Asymmetric routingCannot ping wan gateway from cisco routerLoad balancing and Fail-over at the same time on Cisco Router






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I want to configure a failover link to my cache server with Cisco policy routing.
So I attempted to create an ip sla monitor. here is the syntax in the cisco router (there is possibility of being wrong words in parameters but here I just wanted to show the styles):



R1(config)# ip sla monitor 1
type tcpConnect destip 10.10.10.2 destport 1010
timeOut 30
frequency 30
R1(config)# ip sla monitor 1 schedule life forever starttime now


and then created a track watching for that monitor and use it on routing. But every time I check out the ip sla monitor 1 statistics like this it fails. While I can telnet the 10.10.10.2:1010 with router!



R1# sh ip sla monitor statistics 1

<some stuff here>

last operation return code: No connection
number of success: 0
number of failures: 66


and the track return me the link is down.



Any ideas?










share|improve this question
















bumped to the homepage by Community 11 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






migrated from stackoverflow.com Nov 24 '11 at 15:38


This question came from our site for professional and enthusiast programmers.

























    1















    I want to configure a failover link to my cache server with Cisco policy routing.
    So I attempted to create an ip sla monitor. here is the syntax in the cisco router (there is possibility of being wrong words in parameters but here I just wanted to show the styles):



    R1(config)# ip sla monitor 1
    type tcpConnect destip 10.10.10.2 destport 1010
    timeOut 30
    frequency 30
    R1(config)# ip sla monitor 1 schedule life forever starttime now


    and then created a track watching for that monitor and use it on routing. But every time I check out the ip sla monitor 1 statistics like this it fails. While I can telnet the 10.10.10.2:1010 with router!



    R1# sh ip sla monitor statistics 1

    <some stuff here>

    last operation return code: No connection
    number of success: 0
    number of failures: 66


    and the track return me the link is down.



    Any ideas?










    share|improve this question
















    bumped to the homepage by Community 11 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






    migrated from stackoverflow.com Nov 24 '11 at 15:38


    This question came from our site for professional and enthusiast programmers.





















      1












      1








      1








      I want to configure a failover link to my cache server with Cisco policy routing.
      So I attempted to create an ip sla monitor. here is the syntax in the cisco router (there is possibility of being wrong words in parameters but here I just wanted to show the styles):



      R1(config)# ip sla monitor 1
      type tcpConnect destip 10.10.10.2 destport 1010
      timeOut 30
      frequency 30
      R1(config)# ip sla monitor 1 schedule life forever starttime now


      and then created a track watching for that monitor and use it on routing. But every time I check out the ip sla monitor 1 statistics like this it fails. While I can telnet the 10.10.10.2:1010 with router!



      R1# sh ip sla monitor statistics 1

      <some stuff here>

      last operation return code: No connection
      number of success: 0
      number of failures: 66


      and the track return me the link is down.



      Any ideas?










      share|improve this question
















      I want to configure a failover link to my cache server with Cisco policy routing.
      So I attempted to create an ip sla monitor. here is the syntax in the cisco router (there is possibility of being wrong words in parameters but here I just wanted to show the styles):



      R1(config)# ip sla monitor 1
      type tcpConnect destip 10.10.10.2 destport 1010
      timeOut 30
      frequency 30
      R1(config)# ip sla monitor 1 schedule life forever starttime now


      and then created a track watching for that monitor and use it on routing. But every time I check out the ip sla monitor 1 statistics like this it fails. While I can telnet the 10.10.10.2:1010 with router!



      R1# sh ip sla monitor statistics 1

      <some stuff here>

      last operation return code: No connection
      number of success: 0
      number of failures: 66


      and the track return me the link is down.



      Any ideas?







      networking router failover cisco






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 24 '11 at 15:44









      duenni

      2,6351532




      2,6351532










      asked Nov 24 '11 at 15:26







      user1025749












      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 11 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






      migrated from stackoverflow.com Nov 24 '11 at 15:38


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com Nov 24 '11 at 15:38


      This question came from our site for professional and enthusiast programmers.
























          1 Answer
          1






          active

          oldest

          votes


















          0














          You don't need to use control protocol.



          type tcpConnect destip 10.10.10.2 destport 1010 control disable



          IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily. This action allows the Responder to reply to the TCP Connect operation. In this example, because the target is not a router and a well-known TCP port is used, there is no need to send the control message.
          http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hstcpc.html







          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "2"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f334518%2fcisco-ip-sla-monitor-failure-on-tcpconnect-but-the-host-can-be-telneted-from-rou%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown
























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You don't need to use control protocol.



            type tcpConnect destip 10.10.10.2 destport 1010 control disable



            IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily. This action allows the Responder to reply to the TCP Connect operation. In this example, because the target is not a router and a well-known TCP port is used, there is no need to send the control message.
            http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hstcpc.html







            share|improve this answer




























              0














              You don't need to use control protocol.



              type tcpConnect destip 10.10.10.2 destport 1010 control disable



              IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily. This action allows the Responder to reply to the TCP Connect operation. In this example, because the target is not a router and a well-known TCP port is used, there is no need to send the control message.
              http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hstcpc.html







              share|improve this answer


























                0












                0








                0







                You don't need to use control protocol.



                type tcpConnect destip 10.10.10.2 destport 1010 control disable



                IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily. This action allows the Responder to reply to the TCP Connect operation. In this example, because the target is not a router and a well-known TCP port is used, there is no need to send the control message.
                http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hstcpc.html







                share|improve this answer













                You don't need to use control protocol.



                type tcpConnect destip 10.10.10.2 destport 1010 control disable



                IP SLAs uses the control protocol to notify the IP SLAs Responder to enable the target port temporarily. This action allows the Responder to reply to the TCP Connect operation. In this example, because the target is not a router and a well-known TCP port is used, there is no need to send the control message.
                http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hstcpc.html








                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 24 '11 at 22:19









                Sergii ShevchykSergii Shevchyk

                1012




                1012






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f334518%2fcisco-ip-sla-monitor-failure-on-tcpconnect-but-the-host-can-be-telneted-from-rou%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Фонтен-ла-Гаярд Зміст Демографія | Економіка | Посилання |...

                    Список ссавців Італії Природоохоронні статуси | Список |...

                    Маріан Котлеба Зміст Життєпис | Політичні погляди |...