Table Of Contents
Disable VPDN Logging for Normal Session Termination
vpdn history failure cause normal
Disable VPDN Logging for Normal Session Termination
This document introduces two new commands—no vpdn logging cause normal and no vpdn history failure cause normal—that can be used to disable virtual private dialup network (VPDN) message logging when a session is terminated normally.
Feature History
Contents
Additional References
The following sections provide references related to this feature.
Related Documents
VPDN and VPDN commands
•
Virtual Templates, Profiles, and Networks part in the Cisco IOS Dial Technologies Configuration Guide, Release 12.3
•
Syslog message logging and syslog message logging commands
•
•
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Command Reference
This section documents the following new commands:
•
vpdn history failure cause normal
To prevent the message "The remote server closed the session" from overwriting useful messages in the virtual private dialup network (VPDN) connection failure log, use the no vpdn history failure cause normal command in global configuration mode. To reenable logging of the message (the default), use the vpdn history failure cause normal command.
vpdn history failure cause normal
no vpdn history failure cause normal
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled when the VPDN failure log is enabled, but it will not appear in the configuration of a Layer 2 access controller (LAC) or Layer 2 network server (LNS) when the running configuration is listed. When the no form of this command is configured, it will be listed in the running configuration. See the "Usage Guidelines" section for more information.
Command Modes
Global configuration
Command History
Usage Guidelines
When users are declared as unauthenticated, their termination is recorded in the VPDN failure log. One method for determining why a subscriber cannot establish a PPP session is for the network operator to check the VPDN failure log for connection failure messages. The router can determine and log specific reasons for session termination, such as authentication failure, exceeding the session limit, timer expiration, and so on. However, a peer LAC or LNS will send the message "VPDN-6-CLOSED" to the router for any type of session termination. All other messages at the console and in the failure log will come under abnormal termination at that router, and the message "The remote server closed the session" is also logged in the VPDN connection failure log. So the failure log, which has maximum of 50 messages, gets filled with messages. Once the maximum message length is reached, new messages begin replacing old messages and information about the unauthenticated users is lost.
The no vpdn logging cause normal command disables all system logging (syslog) messages with the prefix "VPDN-6-CLOSED." The no vpdn history failure cause normal command is used to prevent the message "The remote server closed the session" from being added to the connection failure log.
Both commands are independent, so that configuring the no vpdn logging cause normal command does not prevent the message "The remote server closed the session" from being logged. And conversely, configuring the no vpdn history failure cause normal command does not prevent the syslog message "VPDN-6-CLOSED" from appearing.
By default, the vpdn logging cause normal command is enabled only when VPDN logging is enabled, and will not show up when the show running configuration command is used to display the configuration. When configured, the command no vpdn logging cause normal is listed in the output of the show running configuration command only when VPDN logging is enabled.
By default, the vpdn history failure cause normal command is enabled only when the VPDN failure log is enabled, and it will not show up when the show running configuration command is used to display the configuration. When configured, the command no vpdn history failure cause normal shows up only when the VPDN history log is enabled.
Regardless of whether the no vpdn logging cause normal and no vpdn history failure cause normal commands are configured, all other syslog messages except those with prefix "VPDN-6-CLOSED" should appear on the console, and the failure table should log all messages except "The remote server closed the session."
Examples
The default behavior of this command enables logging of the message "The remote server closed the session." The following example shows how to disable both the "The remote server closed the session" and "VPDN-6-CLOSED" messages so that the VPDN connection failure log maintains useful messages about session termination:
no vpdn logging cause normalno vpdn history failure cause normalRelated Commands
vpdn logging cause normal
Prevents the message "VPDN-6-CLOSED" from overwriting useful messages in the VPDN connection failure log.
vpdn logging cause normal
To prevent display of the syslog message "VPDN-6-CLOSED" on the router console, use the no vpdn logging cause normal command in global configuration mode. To reenable display of the message (the default), use the vpdn logging cause normal command.
vpdn logging cause normal
no vpdn logging cause normal
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled when VPDN logging is enabled, but it will not appear in the configuration of a Layer 2 access controller (LAC) or Layer 2 network server (LNS) when the running configuration is listed. When the no form of this commands is configured, it will be listed in the running configuration. See the "Usage Guidelines" section for more information.
Command Modes
Global configuration
Command History
Usage Guidelines
When users are declared as unauthenticated, their termination is recorded in the VPDN failure log. One method for determining why a subscriber cannot establish a PPP session is for the network operator to check the VPDN failure log for connection failure messages. The router can determine and log specific reasons for session termination, such as authentication failure, exceeding the session limit, timer expiration, and so on. However, a peer LAC or LNS will send the message "VPDN-6-CLOSED" to the router for any type of session termination. All other messages at the console and in the failure log will come under abnormal termination at that router, and the message "The remote server closed the session" is also logged in the VPDN connection failure log. So the failure log, which has maximum of 50 messages, gets filled with messages. Once the maximum message length is reached, new messages begin replacing old messages and information about the unauthenticated users is lost.
The no vpdn logging cause normal command disables all system logging (syslog) messages with the prefix "VPDN-6-CLOSED." The no vpdn history failure cause normal command is used to prevent the message "The remote server closed the session" from being added to the connection failure log.
Both commands are independent, so that configuring the no vpdn logging cause normal command does not prevent the message "The remote server closed the session" from being logged. And conversely, configuring the no vpdn history failure cause normal command does not prevent the syslog message "VPDN-6-CLOSED" from appearing.
By default, the vpdn logging cause normal command is enabled only when VPDN logging is enabled, and will not show up when the show running configuration command is used to display the configuration. When configured, the command no vpdn logging cause normal is listed in the output of the show running configuration command only when VPDN logging is enabled.
By default, the vpdn history failure cause normal command is enabled only when the VPDN failure log is enabled, and it will not show up when the show running configuration command is used to display the configuration. When configured, the command no vpdn history failure cause normal shows up only when the VPDN history log is enabled.
Regardless of whether the no vpdn logging cause normal and no vpdn history failure cause normal commands are configured, all other syslog messages except those with prefix "VPDN-6-CLOSED" should appear on the console, and the failure table should log all messages except "The remote server closed the session."
Examples
The default behavior of this command enables display of the syslog message "VPDN-6-CLOSED." The following example shows how to disable both the "VPDN-6-CLOSED" and "The remote server closed the session" messages so that the VPDN connection failure log maintains useful messages about session termination:
no vpdn logging cause normalno vpdn history failure cause normalRelated Commands
vpdn history failure cause normal
Prevents the message "The remote server closed the session" from overwriting useful messages in the VPDN connection failure log.
Copyright © 2004 Cisco Systems, Inc. All rights reserved.
Guest
