cannot ping CUE from network

[dhislop]

New installation of CUE into existing CME; can ping CUE from CME, but not from network. Troubleshoot docs say to make sure the default-gateway of the CUE is the CME, which it is. What could I be missing?

Here's my relevant config (CME is 192.168.1.27 and CUE to be 192.168.1.28):

CME

Cisco IOS Software, C2600 Software (C2600-SPSERVICESK9-M), Version 2.3(8)T3, RELEASE SOFTWARE (fc1)

interface FastEthernet0/0

description connected to Corporate Network

ip address 192.168.1.27 255.255.255.0

no ip proxy-arp

no ip mroute-cache

duplex auto

speed auto

h323-gateway voip interface

h323-gateway voip id zonename ipaddr 192.168.1.20 1719

h323-gateway voip h323-id cme

h323-gateway voip tech-prefix 2

!

interface Service-Engine0/0

ip unnumbered FastEthernet0/0

service-module ip address 192.168.1.28 255.255.255.0

service-module ip default-gateway 192.168.1.27

ip classless

ip route 0.0.0.0 0.0.0.0 192.168.1.10

ip route 192.168.1.28 255.255.255.255 Service-Engine0/0

[Markus Schneider]

Looks OK. Is CUE actually booted up? If you enter 'serv serv 0/0 status' does the module show up in a steady state? If not, you might want to do a 'serv serv 0/0 session' to get to CUE. Then I would probably issue a reload command without saving, since this is a new install. It could be that something happened and it didn't detect the ip address change. Once it's rebooted, you can do a 'show interface' on the CUE to see if it gets the IP address.

[dhislop]

Thanks. What happens when I do the serv serv 0/0 session is that it immediately says it needs a DNS server and is not satisfied with any of my answers. I assume this is because it has no IP connectivity to my DNS Server. Ideas here?

[dhislop]

We got past the problem by assigning the CUE an IP address on a different subnet than the CME. Even though some of the docs say it should be on the same subnet, many examples show it on different subnets. It also returns a warning when you specify an IP address (instead of ip unnumbered) that is on the same subnet.

[Markus Schneider · Accepted solution]

I think resetting would have done it too. Using a different subnet or the same (with IP unnumbered) as another interface is both supported. It almost seems like maybe the fastethernet interface was not up or something while CUE was booting. The DNS question are during the post-install script. It does need to be reachable, unless you tell it not to use DNS.

[dhislop]

In case anyone else is having this problem: it was the

no ip proxy-arp

on the fastethernet interface that kept 192.168.1.27 from proxying for 192.68.1.28, thus no one could reach it. We removed this statement and were able to address the CUE on the same subnet as CME and have it work!