Symantec™ Security Gateways Reference Guide - Sawmill

150 Log messagesInformational messages (100-199)120 - Shared key is not defined for userDescription: This is a configuration error. An attempt to connect to the tunnel has failed as the shared key is notconfigured on the security gateway.120 - Some adapter IP address has changed, will reconfigure VPN servicesDescription: The IP address of the remote user who connects to a private network using the Symantec Client VPN haschanged. The VPN service is reconfigured when there is a change in the IP address.120 - Spawning new processDescription: A process is starting a new instance.120 - Stale rule cache host-to-address mapping detected. Reloading rule cacheDescription: If the variable gwcontrol.rule_cache_reload_timer is set, periodic reloading of the cache ensures that ahost entity which is defined with a fully-qualified domain name in a rule, but whose address is assigned byDHCP, is still found in the rule. Without rule cache reloading, the old address persists in the cache, evenafter DHCP has assigned a new address.120 - StartingDescription: Individual proxy sessions are starting.120 - Successfully logged into the ISAKMP engine with a customized profile with certificatesupportDescription: The Symantec Client VPN has successfully logged into the ISAKMP engine. The administrator has createdthe Entrust certificate profile for the user, enabling the VPN Client to use the digital certificate method forauthentication.120 - Successfully logged into the ISAKMP engine with a default profile which has no certificatesupportDescription: This is a standard operational feature. The Symantec Client VPN has successfully logged into the ISAKMPengine with a default profile, and operates without using the Digital Certificate method of authentication.120 - Switched to lite mode, cannot access CA directoryDescription: This is a standard operational feature. The Symantec Client VPN is switched to lite mode, so it operateswithout using the Digital Certificate method of authentication.120 - Symantec Client VPN does not respond to Phase 1 requestsDescription: The Symantec Client VPN does not respond to Phase 1 negotiation.120 - Symantec Client VPN has exitedDescription: This message notifies that the Symantec Client VPN has exited.120 - Symantec Client VPN has startedDescription: This message notifies that the Symantec Client VPN has started.