I'm trying to deploy CUE 8.6 on a 2921 with a ISM-SRE-300-K9 module and CME 9.1
I can start a session to CUE and ping it from the router with no issues, but I can't reach it from LAN either via web or ping, I can ping the router's loopback IP with no problems.
When I traceroute from LAN it goes out the Internet interface since it's the default route even though I have configured a specific static route for the module, when I try the same traceroute to the router's IP it reached with no problem.
! interface Loopback1 ip address 192.168.11.1 255.255.255.252 end
interface ISM0/0 ip unnumbered Loopback1 service-module ip address 192.168.11.2 255.255.255.252 !Application: CUE Running on ISM service-module ip default-gateway 192.168.11.1 end
ip route 192.168.11.2 255.255.255.255 ISM0/0
Trace to router from LAN:
traceroute to 192.168.11.1 (192.168.11.1), 30 hops max, 60 byte packets 1 gateway (172.30.21.1) 4.947 ms 4.947 ms 5.077 ms 2 172.30.22.1 (172.30.22.1) 0.691 ms * *
Trace to module from LAN:
traceroute to 192.168.11.2 (192.168.11.2), 30 hops max, 60 byte packets 1 gateway (172.30.21.1) 2.263 ms 2.379 ms 2.594 ms 2 172.30.22.1 (172.30.22.1) 2.642 ms 2.658 ms 2.715 ms 3 188.8.131.52 (184.108.40.206) 2.053 ms 2.136 ms 2.149 ms <-- ISP Default GW
I have tried with ip unnumbered and also with explicit IP on the ism0/0 with the same results
I have also restored the module to factory settings with the same results.
Yes, I can ping 192.168.11.2 from 172.30.22.1, from LAN I can ping 192.168.11.1 but not 192.168.11.2 it sends the traffic through my default route even though I have a static route for the module:
#show run | i ip route ip route 0.0.0.0 0.0.0.0 220.127.116.11 track 20 ip route 0.0.0.0 0.0.0.0 18.104.22.168 2 ip route 192.168.11.2 255.255.255.255 ISM0/0
ping from 172.30.22.1:
#ping 192.168.11.2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.11.2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Trace to 192.168.11.2 from router:
#traceroute 192.168.11.2 Type escape sequence to abort. Tracing the route to 192.168.11.2 VRF info: (vrf in name/id, vrf out name/id) 1 192.168.11.2 0 msec 0 msec 0 msec
Trace to 192.168.11.2 from LAN:
traceroute to 192.168.11.2 (192.168.11.2), 30 hops max, 60 byte packets 1 gateway (172.30.20.1) 2.803 ms 4.368 ms 3.814 ms 2 172.30.22.1 (172.30.22.1) 3.201 ms 3.701 ms 2.734 ms 3 22.214.171.124 (126.96.36.199) 6.693 ms 5.732 ms 8.451 ms
172.30.22.1 and 192.168.11.1 are the same device, the first is the LAN address and the second is a loopback created for the CUE, basically it's just my PC directly connected to the router with the ism module, still it goes out the wan interface instead of following the static route
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...