Problem on Cisco VSMS Gateway

[Arie --]

Hello,

I'm implementing VSMS and already added to VSOM. Every time I change the setting of the VSMS, via VSOM or via Management Console, the Gateway of VSMS always disappear and need to re-set the Gateway IP. The VSMS and VSOM are not co-located.

How do to solve the problem?

Thank you.

[Scott Olsen]

What version of VSM are you running on each respective server?  Also, what OS platform?

When you mention 'reset the Gateway IP', how are you actually doing this?

[Arie --]

Hello Scott,

The VSM version is 7.6.0 both on VSOM and VSMS. The OS Platform is RedHat Enterprise Linux Server release 6.4 (Santiago). I mean that the Gateway IP always disappear when I change the VSMS config, i.e. when change the Name of VSMS via VSOM. So, I must console the VSMS and set the Gateway IP then reset the network adapter to apply config.

Thank you.

[Scott Olsen]

Are you applying the gateway configuration via the VSMC console page on the VSMS server?  i.e. - You're *not* using the actual OS to set the gateway or default route are you?

[Arie --]

Hello Scott,

I'm applying the gateway via Linux Network Configuration Setup, not from VSMC Console.

Every time I change configuration via VSMC Console like change the name of Media Server, the gateway IP is disappear. So, I must log on into Linux Network Configuration Setup and set the gateway IP again.

Do you think it's a bug?

Thank you

[Scott Olsen]

No.  You absolutely have to use the VSMC console to configure all of these settings as per the Cisco documentation.  You cannot use the underlying OS.

On the VSMC page, do you have the 'Default Gateway' populated similar to the attached screenshot?  

[Arie --]

Hello Scott,

I got what you meant. Actually the initial config was did by my end customer, but I believe that they certainly filled the default IP gateway from VSMC console.

And I have checked the network configuration via VSMC Console after initial setup and everything looks fine, especially the gateway IP address has been filled.

But, they have been enable eth1 as DHCP with the same gateway with eth0. Do you think that has caused this problem?

[Scott Olsen · Accepted solution]

More than likely, yes.  Having the second adapter (eth1) set as DHCP is probably overriding the static gateway that is attempting to be configured on eth0.  I don't believe this is even a supported configuration.  I would definitely try either setting eth1 to disabled or if it has a legitimate use that requires it's configuration, static with no default gateway configured.  At least as an initial test.

[jsah]

Hello Arie,

My name is Jayesh from Physical security team, as the default gateway is removed after apply config. You can only configured one of the NIC port on the server either Eth0 or Eth1.

One of the Eth port you need disable it.

Here, is the snapshot from the release notes of the VSM 7.6.0.

Hope this help you.

Thanks & Regards,

Jayesh

reg

[Arie --]

Hello Jayesh,

I will try to disable the eth1 and see the result after that. Thank you for your advice.

[jsah]

Glad to hear that. Pleasure assisting you here. :)

Cheers,

Jayesh

[Arie --]

Hello Scott,

I will disable the eth1 and see the result after that. Thank you for your advice, Scott.