Bahamian1977
Technical User
Currently I have a G430 chassis with an S8300 and CM loaded on the hyper-visor of the S8300. The CM has been in production for well over a year now and recently the client wanted to add an H.323 trunk over the internet.
The CM 192.168.x.5 has the G430 192.168.x.7 as its default gateway(which is actually set in the hyper-visor GUI) and the G430 has its default gateway pointing to the internal Cisco router which is 192.168.x.1 on the same network as the G430 and the CM. I configured a public IP on the 10/2(WAN port) 2x.xxx.xxx.xxx and have IP route statements pointing to various sites for testing through the 10/2 gateway.
If I ping from the CLI of the G430 the pings all go through both to the internal networks and the external WAN networks and trace route shows its using the correct interface. Pinging from the CM CLI to the internal network(where my default gateway statement points) goes through and routes to the internal networks from 192.168.x.1 to 192.168.y.y and 192.168.z.z as they should. The issue occurs when sending a ping to any ip from CM through the 10/2 wan interface it stops at the G430 x.7 internal ip and trace-routes fail after that point.
I tested a simple ping from the G430 and CM CLI and monitored my offices external ip for ICMP requests and could see that there were no requests reaching us from the CM ping tests. I recently ran the ip routing command in the G430 but have not restarted and I hope I do not have to as this is a production enviroment. Anyone have any suggestions?
The CM 192.168.x.5 has the G430 192.168.x.7 as its default gateway(which is actually set in the hyper-visor GUI) and the G430 has its default gateway pointing to the internal Cisco router which is 192.168.x.1 on the same network as the G430 and the CM. I configured a public IP on the 10/2(WAN port) 2x.xxx.xxx.xxx and have IP route statements pointing to various sites for testing through the 10/2 gateway.
If I ping from the CLI of the G430 the pings all go through both to the internal networks and the external WAN networks and trace route shows its using the correct interface. Pinging from the CM CLI to the internal network(where my default gateway statement points) goes through and routes to the internal networks from 192.168.x.1 to 192.168.y.y and 192.168.z.z as they should. The issue occurs when sending a ping to any ip from CM through the 10/2 wan interface it stops at the G430 x.7 internal ip and trace-routes fail after that point.
I tested a simple ping from the G430 and CM CLI and monitored my offices external ip for ICMP requests and could see that there were no requests reaching us from the CM ping tests. I recently ran the ip routing command in the G430 but have not restarted and I hope I do not have to as this is a production enviroment. Anyone have any suggestions?