Automatic configuration using HTTP server and Tcl script
Network requirements
As shown in Figure 51, Router B does not have a configuration file.
Configure the servers so Router B can obtain a Tcl script to complete the following configuration tasks:
Enable the administrator to Telnet to Router B to manage Router B.
Require the administrator to enter the correct username and password at login.
Figure 52: Network diagram
Configuration procedure
Configure the DHCP server:
# Enable DHCP.
<RouterA> system-view [RouterA] dhcp enable
# Configure the address pool 1 to assign IP addresses on the subnet 192.168.1.0/24 to clients.
[RouterA] dhcp server ip-pool 1 [RouterA-dhcp-pool-1] network 192.168.1.0 24
# Specify the URL of the script file for the clients.
[RouterA-dhcp-pool-1] bootfile-name http://192.168.1.40/device.tcl
Configure the HTTP server:
# Create the configuration file device.tcl on the HTTP server.
return system-view telnet server enable local-user user password simple abcabc service-type telnet quit user-interface vty 0 4 authentication-mode scheme user-role network-admin quit interface gigabitethernet 1/0/1 port link-mode route ip address dhcp-alloc return
# Start HTTP service software and enable HTTP service. (Details not shown.)
Verifying the configuration
Power on Router B.
After Router B starts up, display assigned IP addresses on Router A.
<RouterA> display dhcp server ip-in-use IP address Client identifier/ Lease expiration Type Hardware address 192.168.1.2 0030-3030-632e-3239- May 12 17:41:15 2016 Auto(C) 3035-2e36-3736-622d- 4574-6830-2f30-2f32
Telnet to 192.168.1.2 from Router A.
<RouterA> telnet 192.168.1.2
Enter the username user and password abcabc as prompted. (Details not shown.)
You are logged in to Router B.