Greetings,
I am running the SMP 5.0.45 on a Windows 2003 server. In Logs>General I am getting the following error message: "Invalid base servers in set command." Under the Information heading it lists the external address of the SMP as server 1 and 0.0.0.0 for server 2. I am getting the error message every 10 minutes and was wondering what I need to do to make it go away.

Rich

Hi,

This error message appears when a gateway cannot connect to the SMP server.
It usually happens when the SMP server is behind NAT.
Please make sure it's possible to ping the SMP server IP address from the this gateway, for example.

Regarding the 0.0.0.0 for server 2 - it happens when a secondary base server was not defined on the SMP.

Yael

Yael,

Thanks for the quick reply. I'll go through the logs and see if I have any boxes out there that can't connect. Does this also include safe@ boxes that were once getting services from the SMP but have been subsequently deleted from the SMP? When they try to check in will they generate this message or is this only regestered boxes that can't connect for some reason?



Rich

Hi,

This specific log does not include safe@ boxes that were deleted from the SMP. These are registered boxes that cannot connect.
If you can't locate those gateways then I suggest sending the problem description to the sofaware support team swservice@sofaware.com for further assistance.

Regards,
Yael

How could i configure secondary base server on management R60 HFA01

It will be configured automatically when setting a standby SmartCenter in management HA mode.

BR,
Eyal

We get this in the following scenario:
The SMP is behind a VPN-1 Edge box using NAT. We have another VPN-1 Edge with a dynamic, public IP address "out there"...

If we configure the SMP to "know" that it's using NAT (in settings for the server in the the group), then the external VPN-1 Edge is able to connect without errors, but the one protecting the SMP generates the error. This is because it is receiving the NAT address (which is actually configured on one of its direct interfaces), and thus interprets the info it receives from the SMP as invalid.

If I do not tell the SMP that it is behind NAT, then everything is inverted; now the external VPN-1 Edge gets info from the SMP telling it to connect to a private address (10.x.x.x) which it interprets as invalid, but the VPN-1 Edge protecting the SMP gives no errors.

I believe the only way to fix this is to add a secondary SMP with the private address for the directly connected VPN-1 Edge, and the other for the external gateways (thus, one configured as "behind NAT" and the other without selecting the option).

Therefore, this error happens when a box is subscribed to the SMP, but the SMP gives it an IP address that the box can't get to (usually different to the one that the box was subscribed to using the web ui).