Hi team,
We wanted to share our experience in our first VCS Starter Pack deployment, where some routing problems arose.
The scenario is the following:
- LAN1 is directly connected to Internet, with a public IP configured. This is intended for external connections.
- LAN2 is connected to LAN. This is intended for internal connections.
We configured the default gateway towards WAN (LAN1), and added a few static routes pointing to LAN2 so that the VCS could reach the corporate remote sites via VPN , next hop being a VPN router located in LAN2 network.
The routes were added via CLI using the command "xconf ip route ...", we verified they were inserted in the routing table correctly.
Jabber video and SX20 worked ok in LAN. We then tested with a Jabber Video client on a remote site, verified ping and DNS worked ok against the internal IP of the VCS, but the client didn´t register. The error was "Could not provision on time", but the VCS log did show the user as provisioned OK. Additional troubleshooting (sniffers) showed that the VCS was not routing all the traffic correctly through LAN2 on VCS, the initial request was responded ok but the second packet was never going out through LAN2 interface. It was like the static route was not being used 100% of the time on VCS.
We then changed the gateway configured and pointed it to the VPN router, via LAN2. After a reboot, the remote site Jabber registered without a problem. We rolled back and placed the original WAN gateway again, leaving the static routes for the VPN sites. We rebooted again, and still the remote Jabber registered OK.
Customer is now concerned whether this internal routing problem may appear again after a reboot. We can´t reproduce it in production, it would be great to know is anyone has experienced such routing issues, or perhaps a caveat is identified.
