VCS Expressway - IP address change

[asobryan01]

Our VCS Expressway was installed by a Cisco partner.

We now want to change the internally facing network interface IP address but cant figure out how to.

The external internet facing address can be changed on the web interface on the VCS-E for NIC 2

But the internal network facing address can be changed but it's default gateway can't.

Without a default gateway, it of course will not work.

I had a look at the command line and think i found where to change the default gateway but on the command line

i cant figure out how to change the IP address of NIC2 and the Subnet.

Can anyone help guide me on how to do this simple change?

[awinter2]

Andy,

the VCS can only have one default gateway, and that gateway should normally be a router/firewall in the subnet of the externally-facing VCS interface.

You should be able to change both the interface address/subnet mask as well as the default gateway address from the System > IP page in the VCS's web interface.

[Tomonori Taniguchi]

As Andreas mention, VCS only support “one” default gateway configuration even enable 2^nd Ethernet port.

The default gateway can be set to either of 1^st or 2^nd Ethernet port.

If you need to configure additional network path for non-default-gateway interface, you can add static route by “xconfig ip route” CLI command.

===================================================================================

*h xConfiguration IP Route [1..50] Address: < 0="">

"Specifies an IP address used in conjunction with the prefix length to determine the network to which this route applies."

*h xConfiguration IP Route [1..50] PrefixLength: <1..128>

"Specifies the number of bits of the IP address which must match when determining the network to which this route applies. Default: 32"

*h xConfiguration IP Route [1..50] Gateway: < 0="">

"Specifies the IP address of the gateway for this route."

*h xConfiguration IP Route [1..50] Interface:

"Specifies the LAN interface to use for this route. Auto: the VCS will select the most appropriate interface to use. Default: Auto"

===================================================================================

For example, assume …

• VCS-E deploy with dual interfaces connection.
• 1^st Ethernet (NIC1) connect to Office network router (172.16.1.1/24)
• 2^nd Ethernet (NIC2) connect to public network via FW (200.1.1.1/28).
• Office network has 172.16.2.0/24 till 172.16.9.0/24 network routable from office network router (172.16.1.1)

Then,

• Configure NIC2 as public facing interface
• Configure 200.1.1.1 as default gateway
• Add static route 172.16.0.0/16 via 172.16.1.1 (xconfig ip route 1 address: 172.16.0.0 prefix:16 gateway:172.16.1.1 interface:lan1)

By this configuration VCS-E know default gateway is 200.1.1.1 but also reachable 172.16.0.0/16 network via 172.16.1.1 (VCS-E know 172.16.1.1 as direct connect network from NIC1).

[Tomonori Taniguchi · Accepted solution]

You able to review static route configured on VCS by executing “xconfig ip route”.

For example,

==================================================

xconfig ip route

*c xConfiguration IP Route 1 Address: "172.16.0.0"

*c xConfiguration IP Route 1 PrefixLength: 16

*c xConfiguration IP Route 1 Gateway: "172.16.1.1"

*c xConfiguration IP Route 1 Interface: LAN1

==================================================

For adding static route, “xcommand routeadd” is available as well.

For removing static route, “xcommand routedelete routeid:” command will be used.

For example removing above static route, then “xcommand routedelete routeid:1” will be command for it.

[asobryan01]

Thank you.

Made the changes, it now works.

Would be nice to be able to change interface NIC 2 using the web browser or even the front panel of the VCS.

Also would be nice if the other two NIC interfaces were used. That way i could provision a management connection to the box. Rather than having to go in serially.

[Tomonori Taniguchi]

> Also would be nice if the other two NIC interfaces were used.

> That way i could provision a management connection to the box. Rather than having to go in serially.

We are continue to investigating/studying how to use 2 additional LAN port (or at least 1 additional port), but yet have conclusion nor timeframe for making enhancement of this.

And yes we have received number of request for enabling additional port for management purpose.

Please note firewall feature on X7.2 may works for traffic control and use one port for management purpose only by disable call protocol although you will able to use 1 port for all call handling.

[gubadman]

There are also requests to use the 3rd and 4th LAN ports as redundant links (bonded adapters) for the 1st and 2nd LAN ports. So I guess we need to see if both can be done or which is the best solution. This would help with router/switch upgrades as it wouldn't isolate the VCS from the network, its traffic could just take a different path instead.

As Tomo says this is still being investigated.

[Martin Koch]

And then somebody accidentally unplugs the only power connection of the vcs instead of the router he wanted to replace and the network is down ;-)

I guess the real high available vcs could be hosted on ESXi or it would need some hardware improvements.

But sure it would be nice to haven an option like:

* bridging/mirroring/bonding/failover (interface 1&3, 2&4 become mirrored)

* define role of port: voip, management, clustering, combined

[gusaguillon]

You can use the command:

xConfiguration Ethernet 1 IP V4 Address: yourIpAddress

xConfiguration Ethernet 1 IP V4 Subnetmask: yourNetMask