Chapter 4 Device Provisioning Engine Configuration Commands

Table Of Contents

Device Provisioning Engine Configuration Commands

Commands

aaa authentication

clear cache

docsis shared-secret

no docsis shared-secret

dpe port

dpe provisioning-group primary

no dpe provisioning-group primary

dpe provisioning-group secondary

no dpe provisioning-group secondary

dpe rdu-server (host)

dpe rdu-server (IP)

dpe reload

dpe shared-secret

dpe start

dpe stop

interface ethernet 0...1 provisioning enabled

interface ethernet 0...1 provisioning fqdn

interface ethernet <intf0|intf1> provisioning enabled

interface ethernet <intf0|intf1> provisioning fqdn <fqdn>

show device-config

show dpe

show dpe config

tftp allow-create-dirs

no tftp allow-create-dirs

tftp allow-override

no tftp allow-override

tftp allow-read-access

no tftp allow-read-access

tftp allow-write-access

no tftp allow-write-access

tftp verify-ip

no tftp verify-ip

Device Provisioning Engine Configuration Commands

This chapter contains detailed information about those command line interface (CLI) commands that you can run from both the hardware and software DPEs. These commands are used to manage and monitor the Broadband Access Center for Cable (BACC) device provisioning engine (DPE).

Note Although some CLI commands run on both hardware and software DPEs, there are several that can only run on a specific DPE type. Refer to the "Command Usage" section on page 1-2 and Table 1-1 for a list of commands and applicable DPE use.

Commands

This section describes the configuration commands that affect the DPE, including:

• aaa authentication

• clear cache

• docsis shared-secret

• no docsis shared-secret

• dpe port

• dpe provisioning-group primary

• no dpe provisioning-group primary

• dpe provisioning-group secondary

• no dpe provisioning-group secondary

• dpe rdu-server (host)

• dpe rdu-server (IP)

• dpe reload

• dpe shared-secret

• dpe start

• dpe stop

• interface ethernet 0...1 provisioning enabled

• interface ethernet 0...1 provisioning fqdn

• interface ethernet <intf0|intf1> provisioning enabled

• interface ethernet <intf0|intf1> provisioning fqdn <fqdn>

• show device-config

• show dpe

• show dpe config

• tftp allow-create-dirs

• no tftp allow-create-dirs

• tftp allow-override

• no tftp allow-override

• tftp allow-read-access

• no tftp allow-read-access

• tftp allow-write-access

• no tftp allow-write-access

• tftp verify-ip

• no tftp verify-ip

Note Output examples provided for DPE CLI commands in this appendix may differ slightly depending on whether you invoke the commands on a hardware DPE or the Solaris DPE.

aaa authentication

Usage Guidelines

You use this command to configure the CLI to perform local user (login) authentication or remote TACACS+ user authentication. This setting applies to all Telnet and console CLI interfaces.

Syntax Description

When entering the aaa authentication command, you simply enter the command as indicated below:

dpe# aaa authentication <mode>

Where <mode> specifies either:

•local—This default method of authentication has been used in all previous versions of BACC.

•tacacs— In this authentication method, the CLI attempts a TACACS+ exchange with each server found in the TACACS+ server list. The attempts continue for a specified number of retries. If the end of the server list is reached before a successful protocol exchange occurs, the local authentication mode is automatically entered. In this manner, you can gain access to the CLI even if the TACACS+ service is completely unavailable.

Note Although TACACS+ authentication prompts you to enter your username and password, local authentication prompts you for your password only. This command is used with both the hardware and Solaris DPE. On the hardware DPE, it is used only in the console mode.

Examples

This is an example of how to use the aaa authentication command to set the authentication mode to TACACS:

dpe# aaa authentication tacacs
%OK

clear cache

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 encounters a major problem. Running this command forces the DPE to rebuild or repopulate its device cache. This process may take an extended amount of time to complete.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the clear cache command, you simply enter the command as indicated below:

dpe# clear cache
Once the command is entered, the DPE cache is cleared and a prompt appears to indicated how much space was cleared as a result. If a situation exists whereby the cache could not be cleared, the reason for the failure is also displayed.

Examples

These are examples of how to use the clear cache command:

Example 1

dpe# clear cache
Clearing DPE cache...
+ 417792 bytes cleared.

Results:

These results occur when the cache is successfully cleared.

Example 2

dpe# clear cache
DPE must be stopped before clearing cache.

Results:
These results occur when the DPE has not yet been stopped.

Example 3

dpe# clear cache
Clearing DPE cache...
+ Cache already cleared.

Results:

These results occur when cache has already been cleared.

docsis shared-secret

Usage Guidelines

This command sets a DOCSIS shared secret (DSS) on the DPE, that is used to calculate the CMTS message integrity check (MIC).

Note This command is used with both the hardware and Solaris DPE. On the hardware DPE, it is used only in the console mode.

Syntax Description

When entering the docsis shared-secret command, you simply enter the command as indicated below:

dpe# docsis shared-secret (format) (secret>)
Where:

•(format)—Identifies whether the shared secret string that follows is entered in clear text or as an encrypted text string. To specify the format, enter:

–0 if a clear text string is used. This is the default setting.

–7 if an IOS encrypted shared-secret text string is being used.

•(secret)—Identifies the actual secret string.

If, after running this command, you use the show running config command, a new line will appear to identify the shared-secret and it's format.

Examples

This is an example of how to use the docsis shared-secret command:

dpe# docsis shared-secret 0 changeme
%OK (Warning: Current input accepted. Note a secure connection is recommended to set or change the docsis shared secret

no docsis shared-secret

Usage Guidelines

This command is used to disable the DSS functionality on the DPE. Using this command does not imply that DSS use is completely disabled, rather disabling DSS at the DPE results in the RDU global DSS being used in stead of local functionality.

If you enter this command, DSS is disabled immediately.

Note This command is used with both the hardware and Solaris DPE. On the hardware DPE, it is used only in the console mode.

Syntax Description

When entering the no docsis shared-secret command, you simply enter the command as indicated below:

dpe# no docsis shared-secret

Examples

This is an example of how to use the no docsis shared-secret command:

dpe# no docsis shared secret
%OK

dpe port

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 You must stop the DPE prior to running this command. If you attempt to run this command on an operational DPE, the ERROR: DPE must be stopped before changing the port number error message appears. The changes you introduce through this command do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe port command, you must use this syntax:

dpe# dpe port <port>

Where the (port) identifies the port number assigned for connecting to the DPE.

Examples

This is an example of how to use the dpe port command:

dpe# dpe port 49186
%OK

dpe provisioning-group primary

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.

Note Whenever voice technology is enabled, a DPE can only belong to one provisioning group.

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.

Note Provisioning group changes do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe provisioning-group primary command, you must use this syntax:

dpe provisioning-group primary <name>*

Where:

•(name)—identifies the assigned primary provisioning group

•*—allows the entry of multiple provisioning groups

When this command is used, you must follow it by running the dpe reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the dpe provisioning-group primary command:

dpe# dpe provisioning-group primary PrimaryProvGroup
%OK (Requires DPE restart "> dpe reload")

no dpe provisioning-group primary

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.

Note Changes do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the no dpe provisioning-group primary command, you simply enter the command as indicated below:

dpe# no dpe provisioning-group primary
Once the command is entered, all configured primary provisioning groups are cleared. When this command is used, you must follow it by running the dpe reload command to restart the DPE and make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the no dpe provisioning-group primary command:

dpe# no dpe provisioning-group primary
%OK (Requires DPE restart "> dpe reload")

dpe provisioning-group secondary

Usage Guidelines

This command sets the secondary provisioning group(s) for the DPE server to use. 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.

Note Provisioning group changes do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe provisioning-group secondary command, you must use this syntax:

dpe provisioning-group secondary <name>*

Where:

•(name)—identifies the assigned secondary provisioning group

•*—allows the entry of multiple provisioning groups

When this command is used, you must follow it by running the dpe reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the dpe provisioning-group secondary command:

dpe# dpe provisioning-group secondary SecondaryProvGroup
%OK (Requires DPE restart "> dpe reload")

no dpe provisioning-group secondary

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.

Note Changes introduced through this command do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the no dpe provisioning-group secondary command, you simply enter the command as indicated below:

dpe# no dpe provisioning-group secondary
Once the command is entered, all configured secondary provisioning groups are cleared. When this command is used, you must follow it by running the dpe reload command to restart the DPE and make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the no dpe provisioning-group secondary command:

dpe# no dpe provisioning-group secondary
%OK (Requires DPE restart "> dpe reload")

dpe rdu-server (host)

Usage Guidelines

This command identifies the RDU to connect this DPE to. Normally, you configure the RDU on the default port but, for security reasons, you could configure it to run on a nonstandard port.

Note Changes do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe rdu-server command, you must use this syntax:

dpe rdu-server <host> <port>

Where:

•<host>—identifies the host on which the RDU is running

•<port>—identifies the port number on which RDU is listening for DPE connections (normally 49187)

When this command is used, you must follow it by running the dpe reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the dpe rdu-server command:

dpe# dpe rdu-server rdu.cisco.com 49187
%OK (Requires DPE restart "> dpe reload")

dpe rdu-server (IP)

Usage Guidelines

This command assigns the RDU to connect this DPE to. Specify this as the IP address 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.

Note Changes do not take effect until you restart the DPE.

This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe rdu-server command, you must use this syntax:

dpe rdu-server <x.x.x.x> <port>

Where:

•<x.x.x.x>—identifies the IP address of the RDU

•<port>—identifies the port on which RDU is listening for DPE connections (normally 49187)

When this command is used, you must follow it by running the dpe reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the dpe rdu-server command:

dpe# dpe rdu-server 10.10.20.1 49187
%OK (Requires DPE restart "> dpe reload")

dpe reload

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 BACC agent forces the DPE to stop and an alert message, indicating this has occurred, is displayed. After that message appears, the DPE restarts.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe reload command, you simply enter the command as indicated below:

dpe# dpe reload
Once the command is entered, a prompt indicating that the DPE was restarted is displayed.

Examples

This is an example of how to use the dpe reload command:

dpe# dpe reload
dpe has been restarted

dpe shared-secret

Usage Guidelines

This command sets the shared secret used for communications with the RDU. Communications will fail if the shared secret, set on the two servers, is not the same. For security reasons, this command is only available through a console connection. It can not be accessed through a Telnet connection.

Note This command is used with both the hardware and Solaris DPE. On the hardware DPE, it is used only in the console mode. Changes do not take effect until you restart the DPE

Syntax Description

When entering the dpe shared-secret command, you must use this syntax:

dpe shared-secret <secret>

Where the <secret> identifies the RDU shared secret. This may appear as encrypted text when the command is run through the console mode or, if being run through a Telnet session, may simply indicate that the shared secret has been set.

When this command is used, you must follow it by running the dpe reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the dpe shared-secret command:

dpe# dpe shared-secret private
%OK (Requires DPE restart "> dpe reload")

dpe start

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.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe start command, you simply enter the command as indicated below:

dpe# dpe start
Once the command is entered, the DPE is started.

Examples

This is an example of how to use the dpe start command:

dpe# dpe start
dpe has been started

dpe stop

Usage Guidelines

This command stops the DPE 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.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the dpe stop command, you simply enter the command as indicated below:

dpe# dpe stop
Once the command is entered, the DPE is stopped.

Examples

This is an example of how to use the dpe stop command:

dpe# dpe stop
dpe has been stopped

interface ethernet 0...1 provisioning enabled

Usage Guidelines

This command controls whether or not the Ethernet interface(s) is used for provisioning operations. This command allows the use of split-networking techniques to isolate device facing communication from provisioning system side communications. Only ports that have provisioning enabled will be used for communication with the DHCP server.

Note This command is only used in conjunction with a hardware DPE.

Syntax Description

When entering the interface ethernet <0...1> provisioning enabled command, you must use this syntax:

interface ethernet <0...1> provisioning enabled <true/false>

Where:

•<0...1>—identifies the Ethernet interface

•<true/false>—indicates whether or not provisioning has been enabled for this interface

When this command is used, you must follow it by running the reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the interface ethernet <0...1> provisioning enabled command:

dpe# interface ethernet 0 provisioning enabled true
%OK (Requires DPE restart "> dpe reload")

interface ethernet 0...1 provisioning fqdn

Usage Guidelines

This command sets the fully qualified domain name for a specific interface. The provisioning FQDN is the FQDN that is given to devices in order to contact the specific DPE interface. It is only used when provisioning is enabled on that interface.

Note This command is only used in conjunction with a hardware DPE.

Syntax Description

When entering the interface ethernet <0...1> provisioning fqdn command, you must use this syntax:

interface ethernet <0...1> provisioning fqdn <fqdn>

Where:

•<0...1>—identifies the Ethernet interface

•<fqdn>—identifies the fully qualified domain name being set on the specified interface

Note Enabling both DPE appliance interface IPs, and setting the provisioning FQDNs to identical names has no effect on PacketCable since this voice technology always uses the IP address of the first interface.

When this command is used, you must follow it by running the reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the interface ethernet <0...1> provisioning fqdn command:

dpe# interface ethernet 0 provisioning fqdn dpe.cisco.com
%OK (Requires DPE restart "> dpe reload")

interface ethernet <intf0|intf1> provisioning enabled

Usage Guidelines

This command performs the same functions as those described in the "interface ethernet 0...1 provisioning enabled" section with the single exception that this command can only be invoked on a Solaris DPE. The provisioning FQDN is the FQDN that is given to devices in order to contact the specific DPE interface. It is only used when provisioning is enabled on that interface.

Note This command is only used in conjunction with a Solaris DPE.

Syntax Description

When using the interface ethernet [intf0/intf1] provisioning enabled command, you must use this syntax:

interface ethernet <intf0/intf1> provisioning enabled <true/false>

Where:

•<intf0/intf1>—identifies the Ethernet interface

•<true>—indicates that provisioning has been enabled

•<false>—indicates that provisioning has been disabled

When this command is used, you must follow it by running the reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the interface ethernet [intf0/intf1] provisioning enabled command:

dpe# interface ethernet hme0 provisioning enabled true
% OK (Requires DPE restart "> dpe reload")

interface ethernet <intf0|intf1> provisioning fqdn <fqdn>

Usage Guidelines

This command sets the fully qualified domain name for a specific interface. This is the FQDN that is sent as the SNMPEntity in DHCP option 177, sub-option -3.

Note This command is only used in conjunction with a Solaris DPE.

Syntax Description

When entering the interface ethernet [intf0/intf1] provisioning fqdn command, you must use this syntax:

interface ethernet [intf0/intf1] provisioning fqdn <fqdn>

Where:

•<intf0/intf1>—identifies the Ethernet interface

•<fqdn>—identifies the fully qualified domain name being set on the specified interface

When this command is used, you must follow it by running the reload command to make the changes take effect. See the "dpe reload" section for additional information.

Examples

This is an example of how to use the interface ethernet [intf0/intf1] provisioning fqdn command:

dpe# interface ethernet hme0 provisioning fqdn cisco.com
% OK (Requires DPE restart "> dpe reload")

show device-config

Usage Guidelines

This command shows the configuration of the device configuration

If you run this command on an unlicensed DPE, a message similar to this one appears:

This DPE is not licensed. Your request cannot be serviced. Please check with your system administrator for DPE licenses.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the show device-config command, you must use this syntax:

show device-config <mac>

Where <mac> specifies the MAC address of any device. The accepted MAC address formats are: type,len,addr. For example:

•1,6,00:01:02:03:04:05, or

•9,10,43:43:31:32:33:34:35:36:2d:41

Also, the exact size octets, such as 000102030405 or 00:01:02:03:04:05 (assuming that the mac address header is 1,6) could be used.

Examples

This is an example of how to use the show device-config command. For the purpose of this example assume that the DPE MAC address is 1,6,00:00:00:00:00:03.

dpe# dpe show device-config 00:00:00:00:00:03

Retrieved the following configuration from DPE.

DHCP Configuration for device 1,6,00:00:00:00:00:03 in default provisioning-group
. . . . . . . . . . . . . . . . . . . . . .

Note The output of this command has been trimmed for demonstration purposes.

show dpe

Usage Guidelines

This command checks to see if the DPE is running and displays the state of the process and, if running, its operational statistics. It does not indicate if the DPE is running successfully, only that the process itself is currently executing. However, DPE statistics that this command prints when the DPE is running, can be used to determine if the DPE is successfully servicing requests.

If you run this command on an unlicensed DPE, a message similar to this one appears:

This DPE is not licensed. Your request cannot be serviced. Please check with your system administrator for DPE licenses.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the show dpe command, you simply enter the command as indicated below:

dpe# show dpe
Once the command is entered, operating information for the selected DPE is displayed.

Examples

These examples show how to use the show dpe command:

Example 1

dpe# show dpe
CSRC BPR Device Provisioning Engine is not running

Results:

These results occur when the DPE is not running.

Example 2

dpe# show dpe
BPR Agent is running
dpe is running

Version BPR 2.7 (cbpr_27_L_000000000000).
Caching 0 device configs and 0 external files.
Received 0 cache hits and 0 misses.
Received 0 lease updates.
Connection status is Disconnected.
Sent 0 SNMP informs and 0 SNMP sets.
Received 0 MTA provisioning successful SNMP informs.
Received 0 MTA provisioning failed SNMP informs.
Running for 6 days 41 mins 35 secs.

Results:

These results occur when the DPE is running.

show dpe config

Usage Guidelines

This command shows the current DPE settings.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the show dpe config command, you simply enter the command as indicated below:

dpe# show dpe config
Once the command is entered, the DPE configuration is displayed.

Examples

This is an example of how to use the show dpe config command:

dpe# show dpe config
dpe port = 49186
rdu host = host.cisco.com
rdu port = 49187
primary groups = Default
secondary groups = [no value]

tftp allow-create-dirs

Usage Guidelines

This command allows a TFTP write request to create directories.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# tftp allow-create-dirs
Examples

This is an example of how to use the tftp allow-create-dirs command:

dpe# tftp allow-create-dirs
%OK

Note During a TFTP read operation, the TFTP server only looks in its cache although, if the tftp allow-read-access CLI command has been run, the TFTP server first looks at the local file system before looking in the cache. If the required file exists in the local file system, it is read from there. Otherwise, the TFTP server looks in the cache and, if the file is there it uses it. Should the file not exist in the cache, the TFTP server sends a request to the RDU for the file.

TFTP writes are not made to the DPE cache; only to the local file system. When the tftp allow-write-access DPE CLI command, you can write to the TFTP home directory. By default you are not allowed to create directories or override files, but this can be changed using either the tftp allow-create-dirs or the tftp allow-override commands.

no tftp allow-create-dirs

Usage Guidelines

This command is used to disable the creation of directories by TFTP write requests.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# no tftp allow-create-dirs
Examples

This is an example of how to use the no tftp allow-create-dir command:

dpe# no tftp allow-create-dirs
%OK

tftp allow-override

Usage Guidelines

This command allows the override of existing files using a TFTP write request.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# tftp allow-override
Examples

This is an example of how to use the tftp allow-override command:

dpe# tftp allow-override
%OK

no tftp allow-override

Usage Guidelines

This command disables the overriding of existing files by TFTP write requests.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# no tftp allow-override
Examples

This is an example of how to use the no tftp allow-override command:

dpe# no tftp allow-override
%OK

tftp allow-read-access

Usage Guidelines

This command enables TFTP read requests from the file system. When this command is enabled, and a DPE does not find the required file in the local directory, the DPE cache is searched.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# tftp allow-read-access
Examples

This is an example of how to use the tftp allow-read-access command:

dpe# tftp allow-read-access
%OK

no tftp allow-read-access

Usage Guidelines

This command disables TFTP read requests from the file system.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering this command, you simply enter the command as indicated below:

dpe# no tftp allow-read-access
Examples

This is an example of how to use the no tftp read-access command:

dpe# no tftp allow-read-access
%OK

tftp allow-write-access

Usage Guidelines

This command is used to support of TFTP write requests to the local file system.

Note This command is used with both the hardware and Solaris DPEs.

Examples

This is an example of how to use the tftp write-access command:

dpe# tftp allow-write-access
%OK

no tftp allow-write-access

Usage Guidelines

This command disables TFTP write requests to the file system.

Note This command is used with both the hardware and Solaris DPEs.

Examples

This is an example of how to use the no tftp write-access command:

dpe# no tftp allow-write-access
%OK

tftp verify-ip

Usage Guidelines

This command enables the verification of requestor IP addresses on dynamic configuration TFTP requests.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the tftp verify-ip command, you simply enter the command as indicated below:

dpe# tftp verify-ip
Examples

This is an example of how to use the tftp verify-ip command:

dpe# tftp verify-ip
%OK

no tftp verify-ip

Usage Guidelines

This command disables the verification of requestor IP addresses on dynamic configuration TFTP requests.

Note This command is used with both the hardware and Solaris DPEs.

Syntax Description

When entering the no tftp verify-ip command, you must use this syntax:

dpe# no tftp verify-ip
Examples

This is an example of how to use the no tftp verify-ip command:

dpe# no tftp verify-ip
%OK