Holemans Wim wrote:
We are setting up a testbed for IP SLA monitoring and I wanted to
include our core 6500 switches into the test. For 2 of them this went
without problem, on two others this doesn't work : I get the following
error (after putting on debug) :
RTR unable to set SO_STRICT_ADDR_BIND option
I searched the Cisco website and also did a google search but this
didn't give any results. Anyone an idea of what is going wrong here ?
Both not-working routers have a SUP32, the working ones a SUP2
supervisor.
Router1 s3223_rp-IPBASEK9-VM Version 12.2(18)SXF6
WS-SUP32-GE-3B : rtr responder not working
Router2 s222_rp-IPSERVICESK9-M Version 12.2(18)SXF6
WS-X6K-SUP2-2GE : rtr responder working
Router3 s3223_rp-IPBASEK9-VM Version 12.2(18)SXF6
WS-SUP32-GE-3B : rtr responder not working
Router4 s222_rp-IPSERVICESK9-M Version 12.2(18)SXF6
WS-X6K-SUP2-2GE : rtr responder working
Is it possible I need the ipservices version to do this ? Anyone a clue
on what the error means ? The rtr responder command is accepted in all
versions.
I think you need ipservices.
Also, IIRC RTR has crash-bugs under SXF, and you are advised to not use
it at all :o(
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
