|
|
This appendix contains detailed information about the command line interface (CLI) commands that you can use to manage and monitor the device provisioning engine (DPE). They have been grouped into these associations:
This section describes the system commands that affect the entire Broadband Provisioning Registrar (BPR). These commands include:
Usage Guidelines
Use the disable command only when the DPE shell is already enabled. Once the disable mode is activated, only those commands that allow viewing the system configuration are available.
Examples
This is an example of how to use the disable command:
Usage Guidelines
Use the enable command to enable the current connection to the DPE shell. Viewing system configuration does not require the enabled mode. However, the enabled mode is required to change data.
Examples
This is an example of how to use the enable command:
 |
Note Refer to the "password" section C-13 for information on setting the password. |
Usage Guidelines
This command closes a TELNET or console connection to the DPE.
Examples
This is an example of how to use the exit command:
Usage Guidelines
This command displays a help screen to assist you in using the DPE interface. If you need help on a particular command, or to list all available commands, enter either ? or system commands respectively.
Command Types
Two types of help are provided:
1. Full help is available when you are ready to enter a command argument, such as show ?, and describes each possible argument.
2. Partial help is provided when you enter an abbreviated argument and want to know what arguments match the input. For example, show stat?.
Examples
This is an example of how to use the help command:
Usage Guidelines
This command turns the DPE power off. It removes all current users from the system and shuts the DPE down cleanly. Prior to executing this command, you should verify that there has been no hard drive activity for approximately 30 seconds.
 |
Caution Using the power switch on the device can potentially cause partial corruption of the DPE cache. This could result in the DPE needing more time to rebuild its cache the next time it is powered up. |
This is an example of how to use the poweroff command:
Usage Guidelines
This command reboots the DPE, removing all current users from the system.
|
Caution Using the power switch on the device can potentially cause partial corruption of the DPE cache. This could result in the DPE needing more time to rebuild its cache the next time it is powered up. |
Examples
This is an example of how to use the reload command:
Usage Guidelines
This command displays all DPE commands available for use by the administrator. The output from this command might differ somewhat depending on which state the DPE is in; enabled or disabled.
Examples
This is an example of how to use the show commands command:
Usage Guidelines
This command displays the current configuration of the DPE.
All of the configuration options are displayed using the actual commands to set the options. If you copy this output, you can paste it back into the configurations for other DPEs modifications. In this way, you can quickly create the configurations for multiple devices needing identical configurations.
To do this, refer to the Broadband Provisioning Registrar Installation Guide.
Examples
This is an example of how to use the show running-config command:
Usage Guidelines
This command identifies how long the system has been operational. This information is useful when determining how frequently the device is rebooted. It is also helpful when checking the reliability of the DPE when it is in a stable condition.
Examples
This is an example of how to use the uptime command:
This section describes the commands that you can use to monitor BPR system resources. These commands include:
Usage Guidelines
This command identifies how much of the CPU is being used to perform those BPR activities that are currently running.
Examples
This is an example of how to use the show cpu command:
Usage Guidelines
This command identifies how much of the current disk the DPE is using.
Examples
This is an example of how to use the show disk command:
Usage Guidelines
This command identifies how much current memory and swap usage the DPE is using.
Examples
This is an example of how to use the show memory command:
This section describes those commands that are used in network or system configuration. These commands include:
Usage Guidelines
This command sets the current time, using the 24-hour format, and date used by the DPE. The new time takes effect immediately. The DPE use GMT to keep time. When setting the time you must use GMT to prevent the incorrect time from being returned by the time server.
Syntax Description
When entering the clock set command, you must use this syntax:
Examples
This is an example of how to use the clock set command:
Usage Guidelines
This command is used to change the access password for entering into an enabled state on the DPE. You can only change the enable password when you are in the enabled mode. Once the password is changed, all users who, from that point forward, attempt to enter into an enabled mode, will be required to use the new password.
Syntax Description
When entering the enable password command, you must use this syntax:
Examples
These are examples of how to use the enable password command:
These results occur when the password is changed successfully.
These results occur when the password is not entered consistently.
These results occur when the password is changed (using an approach easier for scripting).
Usage Guidelines
This command is used to set the DPE hostname. The hostname is used primarily for display in the DPE and should correspond to the DNS name for the DPEs IP address. If you change the hostname, you must run the reload command for the changes to take effect.
Syntax Description
When entering the hostname command, you must use this syntax:
Examples
This is an example of how to use the hostname command:
Usage Guidelines
This command sets the IP address of the Ethernet interface being used by the DPE. This IP address must be kept current with a valid gateway. If the gateway is invalid, rebooting could occur and this might cause the DPE to become unavailable on the network. If the IP address is configured incorrectly, use the DPE console port to reconfigure the device with a valid IP.
|
Note IP changes do not take effect until the device is restarted. |
Syntax Description
When entering the interface ethernet / ip address command, you must use this syntax:
Examples
This is an example of how to use the interface ethernet / ip address command:
Usage Guidelines
This command controls whether or not the Ethernet interface is configured to support IP communications. If both interfaces are disabled, the device will have no network connectivity. Typically, both interfaces are enabled and connected to the network, to provide either redundancy or to use split-networking.
Syntax Description
When entering the interface ethernet / IP address command, you must use this syntax:
Examples
This is an example of how to use the interface ethernet / ip enabled command:
Usage Guidelines
This command controls whether or not the Ethernet interface(s) is used for provisioning operations. If they are, it is possible to use split-networking techniques to isolate device faced communication from provisioning system communications. Only ports that have provisioning enabled will be used for communication with the DHCP server. If both ports are enabled for provisioning, the DHCP server will send requests to both ports when processing requests from network devices.
Another technique, disabling provisioning on both interfaces, prevents the DPE from communicating with other devices. Doing this can improve performance when the DPE is undertaking a significant cache synchronization with the RDU.
Syntax Description
When entering the interface ethernet / provisioning enabled command, you must use this syntax:
Examples
This is an example of how to use the interface ethernet / provisioning enabled command:
Usage Guidelines
This command configures a default gateway onto the DPE. This default gateway must be directly accessible by one of the DPE interfaces otherwise the DPE becomes unavailable.
You must verify this setting before attempting to reboot the DPE. If an incorrect value is configured, it may become necessary to physically connect to the DPEs console port; long distances may make this impractical.
Syntax Description
When entering the ip default-gateway command, you must use this syntax:
Examples
This is an example of how to use the ip default-gateway command:
Usage Guidelines
This command clears DPEs default gateway. If a default gateway is not specified, the DPE is only available with direct network connectivity or through the console port on the DPE.
Examples
This is an example of how to use the ip default-gateway command:
Usage Guidelines
This command configures the DPE domain name for use when resolving names for communication operations, such as connecting to the RDU, or using the ping and traceroute commands. The domain name is also associated with the DPE.
Syntax Description
When entering the ip domain-name command, you must use this syntax:
Examples
This is an example of how to use the ip domain-name command:
Usage Guidelines
This command clears the DPEs domain name. If a domain name is not specified, all remote hostnames must be specified using the fully qualified domain names.
Examples
This is an example of how to use the no ip domain-name command:
Usage Guidelines
This command configures the IP name servers for use on the DPE. These servers are used to resolve hostnames into IP addresses for communication. If an FQDN is used to specify the RDU, you must specify a valid name server for successful communication with the RDU.
Syntax Description
When entering the ip name-server command, you must use this syntax:
Examples
This is an example of how to use the ip name-server command:
Usage Guidelines
This command clears the DPE name servers. When no name servers are configured, all communication must be performed using explicit IP addresses.
Examples
This is an example of how to use the no ip name-server command:
Usage Guidelines
This command configures a custom route on the DPE. Three parameters are required, as shown in the following syntax description.
Syntax Description
When entering the ip route command, you must use this syntax:
Examples
This is an example of how to use the ip route command:
Usage Guidelines
This command clears the specified custom route, but the default route cannot be removed this way. Use the ip default-gateway command to change the default route.
|
Note The changes you introduce through this command take effect immediately. |
Syntax Description
When entering the no ip route command, you must use this syntax:
The no ip route command must be entered using this syntax:
Examples
This is an example of how to use the no ip route command:
Usage Guidelines
This command changes the current system password. The password is changed automatically for future log ins and for FTP access using the administrator account.
|
Note The changes you introduce through this command take effect immediately and users who are current logged on are not disconnected. |
Syntax Description
When entering the password command, you must use this syntax:
Examples
This is an example of how to use the password command:
These results occur when the password is changed successfully.
These results occur when the password is not entered consistently.
These results occur when the password is changed (using an approach easier for scripting).
Usage Guidelines
This command shows the current system time and date.
Examples
This is an example of how to use the show clock command:
Usage Guidelines
This command show the DPEs hostname.
Examples
This is an example of how to use the show hostname command:
Usage Guidelines
This command shows the configuration for the Ethernet interface. These are the settings that are used when the DPE is rebooted. Use the show interface / stats command to identify the currently configured IP address.
Syntax Description
When entering the show interface ethernet / config command, you must use this syntax:
Examples
This is an example of how to use the show interface ethernet / config command:
Usage Guidelines
This command shows statistics on the DPE's Ethernet interface.
Syntax Description
When entering the show interface ethernet / stats command, you must use this syntax:
Examples
This is an example of how to use the show interface ethernet / stats command:
Usage Guidelines
This command shows the DPEs current general IP settings. For specific interface specific settings, use the show interface commands. These are the settings used when the DPE is rebooted.
Examples
This is an example of how to use the show ip command:
Usage Guidelines
This command shows the DPEs IP routing table, including any custom routes. The default gateway is indicated by the G flag in the flags column.
Examples
This is an example of how to use the show ip route command:
This section describes those CLI commands that assist in supporting and troubleshooting the operation of BPR. These CLI commands include:
Usage Guidelines
This command clears any existing archived bundles on the DPE. These bundles are created using the support bundles commands and normally contain archived logs and archived state information of use to the Cisco TAC. You must ensure that all bundles are retrieved before using this command because the archived state is lost.
Examples
This is an example of how to use the clear bundles command:
Usage Guidelines
The host (DNS) command looks up the IP address of a DPE host using DNS. You can use this command to verify that the RDU's IP address can be successfully resolved. If a system domain name is specified, the host command will automatically attempt searching that domain as well when resolving host names.
Syntax Description
When entering the host (DNS) command, you must use this syntax:
Examples
This is an example of how to use the host (DNS) command:
Usage Guidelines
The host (IP) command looks up the hostname for the specified IP address, and is used to verify that an IP address is correctly reverse-mapped in DNS. The IP address is reverse looked up on each of the configured name servers until the IP address is found.
Syntax Description
When entering the host (IP) command, you must use this syntax:
Examples
This is an example of how to use the host (IP) command:
Usage Guidelines
The ping (domain) command pings the specified host, using the host and domain name. Press the Enter key to stop the process. The ping command is useful in diagnosing network connectivity problems.
Syntax Description
When entering the ping (domain) command, you must use this syntax:
Examples
This is an example of how to use the ping (domain) command:
Usage Guidelines
The ping (IP) command pings the specified host, using the hosts IP address. Press the Enter key to stop the process. Ping is useful in diagnosing network connectivity problems.
Syntax Description
When entering the ping (IP) command, you must use this syntax:
Examples
This is an example of how to use the ping (IP) command:
Usage Guidelines
This command shows all bundles currently available in the outgoing directory. These bundles are created using the support bundle commands and are accessible from the DPEs FTP server.
Examples
This is an example of how to use the show bundles command:
These results occur when there are bundles currently archived.
These results occur when no bundles are currently archived.
Usage Guidelines
This command bundles the current DPE cache. This is useful when archiving the cache for delivery to Cisco Technical Assistance Center. Once created, the bundle is available from the FTP server's outgoing directory.
Examples
This is an example of how to use the support bundle cache command:
Usage Guidelines
This command bundles the current DPE state. This is useful when archiving configuration and log files for the DPE for delivery to Cisco Technical Assistance Center. Once created, the bundle is available from the FTP server's outgoing directory.
|
Note The state bundle is the first bundle you should send to Cisco when the DPE is not operating correctly. |
Examples
This is an example of how to use the support bundle state command:
|
Note In addition to the support bundle state command available on the DPE, there is a script in the client/bin directory on the RDU. This script, called bundleState.sh is used to bundle the system state, including logs, when sending information to the TAC. |
This command enters the DPE into a support shell mode, where low-level access to the device is possible. Most BPR users do not have low-level access to the system and, without the user's password, Cisco TAC cannot access the user's system to perform diagnostics. Consequently, the access password is a derivative of the system password. This affords security to the user while allowing the Technical Assistance Center to provide sufficient technical support.
Usage Guidelines
This command identifies the route, using the host and domain names, to a specified host including each hop between the DPE and the destination host. This command is useful when verifying communication and determining if gateways and routes are correctly configured.
Syntax Description
When entering the traceroute (domain) command, you must use this syntax:
Examples
This is an example of how to use the traceroute (domain) command:
Usage Guidelines
This command identifies the route, using the hosts IP address, to a specified host including each hop between the DPE and the destination host. This command is useful when verifying communication and determining if gateways and routes are correctly configured.
Syntax Description
When entering the traceroute (IP) command, you must use this syntax:
Examples
This is an example of how to use the traceroute (IP) command:
This section describes the configuration commands that affect Broadband Provisioning Registrar. These commands include:
Usage Guidelines
This command erases the entire DPE cache and resets the server back to a clean state. When the DPE is restarted, it will connect to the RDU and rebuild the cache from the information stored in the RDU's database. You should only clear the cache when the DPE is having a major problem, such as when having the DPE rebuild its cache, a process which may take an extended amount of time to complete.
Examples
This is an example of how to use the clear cache command:
These results occur when the cache is successfully cleared.
These results occur when the cache has not yet been stopped.
These results occur when cache has already been cleared.
Usage Guidelines
This command sets the port number that the DPE will use to communicate with the Network Registrar extension points. Normally, you can leave this port number intact unless there is a need to change it for firewall reasons.
|
Note The changes you introduce through this command do not take effect until the DPE is restarted. |
Syntax Description
When entering the dpe port command, you must use this syntax:
Examples
This is an example of how to use the dpe port command:
Usage Guidelines
This command sets the primary provisioning group(s) that the DPE server will use. Most DPEs are configured with one primary provisioning group, however, selecting multiple provisioning groups might allow multiple DHCP servers to use this DPE.
When assigning new provisioning groups that have a high number of devices, restarting the DPE can take an extensive amount of time. This is due to the fact that the cache for each provisioning group has to be synchronized or, for new provisioning groups, completely rebuilt.
Under normal situations, provisioning groups should only be changed when the DPE is first deployed on the network.
Syntax Description
When entering the dpe provisioning-group primary command, you must use this syntax:
Examples
This is an example of how to use the dpe provisioning-group primary command:
Usage Guidelines
This command sets the secondary provisioning group(s) to be used by the DPE server. Most DPEs are configured with one primary provisioning group, however, selecting multiple provisioning groups might allow multiple DHCP servers to use this DPE. Secondary provisioning groups are used for provisioning only when the primary provisioning groups are not available or are overloaded.
When assigning new provisioning groups that have a high number of devices, restarting the DPE can take an extensive amount of time. This is due to the fact that the cache for each provisioning group has to be synchronized or, for new provisioning groups, completely rebuilt.
Under normal situations, provisioning groups should only be changed when the device is first deployed on the network.
Syntax Description
When entering the dpe provisioning-group secondary command, you must use this syntax:
Examples
This is an example of how to use the dpe provisioning-group secondary command:
Usage Guidelines
This command identifies the RDU to connect this DPE to. The FQDN specifies the associated port. Normally, you configure the RDU on the default port but, for security reasons, you could configure it to run on a nonstandard port.
Syntax Description
When entering the dpe rdu-server command, you must use this syntax:
Examples
This is an example of how to use the dpe rdu-server command:
Usage Guidelines
This command assigns the RDU to connect this DPE to. Specify this as the IP address or FQDN with the associated port. Normally, the RDU resides on the default port, but for security reasons the port might be configured to something non-standard. This command will not take effect until the next time the DPE is restarted.
This command identifies the RDU to connect this DPE to. Specify this as the IP address of the associated port.
Syntax Description
When entering the dpe rdu-server command, you must use this syntax:
Examples
This is an example of how to use the dpe rdu-server command:
Usage Guidelines
This command restarts the DPE, which must already be operating before performing the reload operation. If the DPE has not stopped within 60 seconds, the DPE agent forces the DPE to stop and an alert message, indicating this has occurred, is displayed. After that message appears the DPE is restarted.
Examples
This is an example of how to use the dpe reload command:
These results occur when the DPE is restarted successfully.
These results occur when the DPE is not currently running.
Usage Guidelines
This command sets the shared secret used for communications with the RDU. Communications will fail if the shared secret, between the two servers, is not the same.
Syntax Description
When entering the dpe shared-secret command, you must use this syntax:
Examples
This is an example of how to use the dpe shared-secret command:
Usage Guidelines
This command starts the DPE, and you can only use it when the DPE is not running. Having the DPE start successfully does not guarantee that the DPE will run successfully. Check the DPE log to ensure that the DPE has started correctly. In addition, check the log again periodically to make sure no additional errors have occurred.
Examples
This is an example of how to use the dpe start command:
These results occur when the DPE starts successfully.
These results occur when the DPE is already running.
Usage Guidelines
This command stops the DPR and can only be performed when the DPE is running. If the DPE has not stopped within 60 seconds, the DPE agent forces the DPE to stop and an alert message, indicating this has occurred, is displayed.
Examples
This is an example of how to use the dpe stop command:
These results occur when the DPE stops successfully.
These results occur when the DPE is already stopped.
Usage Guidelines
This command clears configured primary provisioning groups. If primary provisioning groups are not available, you can use the DPE as either a backup for other provisioning groups or as a TFTP file cache.
Examples
This is an example of how to use the no dpe provisioning-group primary command:
Usage Guidelines
This command clears configured secondary provisioning groups. If secondary provisioning groups are not available, the DPE can be used as a primary in other provisioning groups.
Examples
This is an example of how to use the no dpe provisioning-group secondary command:
Usage Guidelines
This command identifies the current state of the DPE process. It checks to see if the DPE is running and displays the state of the process. It does not indicate if the DPE is running successfully, only that the process itself is currently executing.
Examples
These examples show how to use the show dpe command:
These results occur when the DPE is not running.
These results occur when the DPE is running.
Usage Guidelines
This command shows the current DPE settings used when it is restarted. It is used to verify that all executed commands have been executed successfully.
|
Note The shared secret is protected data that is not normally displayed on the screen and as such, it is not displayed when the configuration information appears. |
Examples
This is an example of how to use the show dpe config command:
Usage Guidelines
This command is used whenever the DPE requires a new software upgrade, using uploaded upgrade files. These files, which end in the file extension .bpr, should be FTP'd into the incoming directory. The upgrade process scans all available updates and determines which ones are required. It separates the files into these categories:
Examples
This is an example of how to use the upgrade command:
This section describes the system commands that affect how you can manage Broadband Provisioning Registrar logs. These commands include:
Usage Guidelines
This command remove historic (out of date) log files that exist on the system. These files include:
Over time, historic log files accumulate within the DPE. The support bundle state command is used to bundle these logs. Cisco recommends that you create a bundle before clearing logs. This will ensure that no necessary files are accidently lost.
Examples
This is an example of how to use the clear logs command:
Usage Guidelines
This command clears the settings assigned to the syslog server. When the syslog mode is set to either both or remote, clearing the syslog log server results in the log mode being automatically set back to local until a new log server is configured.
Examples
This is an example of how to use the no syslog log-server command:
Usage Guidelines
This command shows all recent log entries for the DPE. These logs contain general DPE process information, including logging all system errors or severe problems. Check this log, when the system is experiencing difficulties. If the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Syntax Description
When entering the show log command, you must use this syntax:
Examples
This is an example of how to use the show log command:
Usage Guidelines
This command shows the specified number of recent log entries for the DPE appliance. Check this log, when the system is experiencing difficulties and, if the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Syntax Description
When entering the show log last command, you must use this syntax:
Examples
This is an example of how to use the show log last command:
Usage Guidelines
This command displays the running DPE log, which starts showing all messages logged to the DPE log. The command continues to run until you press Enter. Check this log when the system is experiencing difficulties. If the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Examples
This is an example of how to use the show log run command:
Usage Guidelines
This command shows all recent DPE syslog entries. The syslog file contains information about the general DPE system, including alerts from various processes related to the DPE. Check this log when the system is experiencing difficulties. If the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Examples
This is an example of how to use the show syslog command:
Usage Guidelines
This command shows the specified number of recent DPE syslog entries, including information about the general DPE system including alerts from various processes related to the DPE. Check this log when the system is experiencing difficulties. If the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Syntax Description
When entering the show syslog command, you must use this syntax:
Examples
This is an example of how to use the show syslog last command:
Usage Guidelines
This command shows the running syslog, which starts showing all messages logged to the syslog. The command continues to run until you press Enter. The syslog contains information about the general DPE system including alerts from various processes related to the DPE. Check this log when the system is experiencing difficulties. If the log contains insufficient information, enable the trace logging function and experiment with the different categories related to the problem.
Examples
This is an example of how to use the show syslog run command:
Usage Guidelines
This command configures the log-server to send syslog messages whenever the syslog mode is set to either both or remote. When the mode is set to local changing this setting has no effect.
Under major failure conditions, syslog messages would normally be sent to a remote server since it may be impossible to connect to the DPE or to logon to the local syslog file.
Syntax Description
When entering the syslog log-server command, and you must use this syntax:
Examples
This is an example of how to use the syslog log-server command:
Usage Guidelines
Configure the mode to log syslog messages. Syslog messages are normally configured to go to a remote server. The available modes are:
If one setting results in remote messages is chosen, but without a log-server configured, messages continue to be logged locally.
Syntax Description
When entering the syslog mode command, you must use this syntax:
Examples
This is an example of how to use the syslog mode command:
Usage Guidelines
This command enables the debug function which can be helpful when troubleshooting possible system problems.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debug function.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the DPE cache debug logging, which involves messages pertaining to the DPE cache including:
Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables DPE cache debug logging.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the debugging of the DPE connection, which logs communication subsystem status and error messages. This is useful for finding communication problems between the DPE and the RDU. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of the DPE connection.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables debugging of the DPE server, which involves logging messages about the overall status and issues of the DPE server. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables debugging of the DPE server.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables debugging of the DPE event manager, which involves logging messages and conditions showing the state of the event manager. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables debugging of the DPE event manager.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the debugging of DPE events, which involves logging details about all events passing through the system. Enabling this command might result in an extensive amount of data being logged, especially during times of high cache volatility. Debugging is typically enabled for certain categories of calls to ensure the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of DPE events.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables or disables the debugging of DPE exceptions, which involves logging full stack traces for exceptions occurring during system operation. When unusual situations occur, where the system is apparently corrupt or behaving very badly, running this command can reveal very valuable information for Cisco TAC support. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of DPE exceptions.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the debugging of the DPE framework, which involves logging information about the DPE server's underlying framework. This underlying infrastructure provides for all of the various servers in BPR. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with excessive trace messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of the DPE framework.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the debugging of DPE messaging, which involves logging details about the DPEs messaging subsystem. This subsystem is used primarily for communication between the DPE and the RDU. Debugging is typically enabled for certain categories of calls to ensure that the system is not overloaded with an excessive number of messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of DPE messaging.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command enables the debugging of TFTP messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Usage Guidelines
This command disables the debugging of TFTP messages.
Examples
This command requires no special syntax, and you enter it as shown in this example:
Posted: Wed Apr 23 16:33:39 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.