Contents

Using automatic configuration· 1

About automatic configuration· 1

Using URL-based automatic configuration· 1

About URL-based automatic configuration· 1

How URL-based automatic configuration works· 1

Procedure· 4

Configuration file· 5

Public cloud-based automatic configuration· 7

About this task· 7

Restrictions and guidelines· 7

 

Using automatic configuration

About automatic configuration

With the automatic configuration feature, the device can automatically obtain a set of configuration settings at startup. You only need to save the configuration file on a specific storage medium. This feature simplifies network configuration and maintenance.

The device supports only URL-based automatic configuration. URL-based automatic configuration applies to scenarios where the devices to be configured are geographically distributed.

Using URL-based automatic configuration

About URL-based automatic configuration

URL-based automatic configuration uses a customizable configuration file saved on the device by default to implement basic device configuration after the device starts up. The configuration file contains the basic network configuration command lines. This feature requires you to construct a URL to indicate the values for the parameters in the command lines. The URL can be in either of the following forms:

·     Plaintext form—The user directly configures the plaintext URL. Parameters in the URL are configured and transmitted in plaintext form.

·     Encrypted form—The administrator generates the encrypted URL and an authentication password for the URL by using the controller. Within the validity of the URL, a user can enter the authentication password as prompted to use the URL to perform URL-based automatic configuration.

How URL-based automatic configuration works

The basic device configuration defines how the device connects to the network. By default, the following connection modes are available: PPPoE mode, static IP address mode, and DHCP mode. The customizable configuration file contains the command lines for the connection modes. The required URL varies by connection mode.

PPPoE mode

Table 1 lists the parameters required or optional in the URL in PPPoE mode. The following is the format of the URL in PPPoE mode:

http://Device IP address/urlcfg?sys_name=Device name&link_mode=Link mode&dialer_if=Dialer interface name&ntp_server=NTP server (optional)&link_if=WAN interface&ac_host=Server IP address&ac_port=Server port&ac_password=Server password&pap_user=PPPoE PAP authentication password&pap_password=PPPoE PAP authentication password&chap_user=PPPoE CHAP authentication username&chap_password=PPPoE CHAP authentication password

Table 1 Parameters required for PPPoE mode

Item	Parameter	Value type	Value range	Corresponding command	Required
Device address	Device IP address	IP address	N/A	N/A	Yes
Device name	sys_name	String	1 to 64	sysname sysname	Yes
Server address	ac_host	IP address	N/A	cloud-management server domain ip-address	Yes
Server port	ac_port	Integer	1 to 65535	cloud-management server port port-number	Yes
Server password	ac_password	String	1 to 63	cloud-management server password simple password	Yes
NTP server	ntp_server	IP address	N/A	ntp-service unicast-server ip-address	No
WAN interface	link_if	Interface type and number	N/A	interface interface-type interface-number	Yes
PPPoE connection mode	link_mode	String	PPPoE	N/A	Yes
PPPoE dialer interface	dialer_if	String	N/A	interface dialer number	Yes
PPPoE PAP authentication username	pap_user	String	1 to 80	ppp pap local-user user-name password simple password	Yes
PPPoE PAP authentication password	pap_password	String	1 to 255	ppp pap local-user user-name password simple password	Yes
PPPoE CHAP authentication username	chap_user	String	1 to 80	ppp chap user user-name	Yes
PPPoE CHAP authentication password	chap_password	String	1 to 255	ppp chap password simple password	Yes

 

Static IP address mode

Table 2 lists the parameters required or optional in static IP address mode. The following is the format of the URL in static IP address mode:

http://Device IP address/urlcfg?sys_name=Device name&link_mode=Link mode&ntp_server=NTP server (optional)&dest_ip=Destination IP address&dest_mask=Destination IP mask&next_hop=IP address of the next hop&link_if=WAN interface&static_ip=Static IP address&static_mask=Static IP mask&ac_host=Server address&ac_port=Server port&ac_password=Server password

Table 2 Parameters required for static IP address mode

Item	Parameter	Value type	Value range	Corresponding command	Required
Device address	Device IP address	IP address	N/A	N/A	Yes
Device name	sys_name	String	1 to 64	sysname sysname	Yes
Server address	ac_host	IP address	N/A	cloud-management server domain ip-address	Yes
Server port	ac_port	Integer	1 to 65535	cloud-management server port port-number	Yes
Server password	ac_password	String	1 to 63	cloud-management server password simple password	Yes
NTP server	ntp_server	IP address	N/A	ntp-service unicast-server ip-address	No
Destination IP address	dest_ip	IP address	N/A	ip route-static dest-address mask next-hop-address	Yes
Destination IP mask	dest_mask	IP mask	N/A	ip route-static dest-address mask next-hop-address	Yes
IP address of the next hop	next_hop	IP address	N/A	ip route-static dest-address mask next-hop-address	Yes
WAN interface	link_if	Interface type and number	N/A	interface interface-type interface-number	Yes
Static IP address connection mode	link_mode	String	STATIC	N/A	Yes
Static IP address	static_ip	IP address	N/A	ip address ip-address mask	Yes
Static IP mask	static_mask	IP mask	N/A	ip address ip-address mask	Yes
Static default gateway	gateway	IP address	N/A	ip route-static 0.0.0.0 0.0.0.0 next-hop-address	Yes

 

DHCP mode

Table 3 lists the parameters required or optional in DHCP mode. The following is the format of the URL in DHCP mode:

http://Device IP address/urlcfg?sys_name=Device name&link_mode=Link mode&ntp_server=NTP server (optional)&link_if=WAN interface&ac_host=Server address&ac_port=Server port&ac_password=Server password

Table 3 Parameters required for DHCP mode

Item	Parameter	Value type	Value range	Corresponding command	Required
Device address	Device IP address	IP address	N/A	N/A	Yes
Device name	sys_name	String	1 to 64	sysname sysname	Yes
Server address	ac_host	IP address	N/A	cloud-management server domain ip-address	Yes
Server port	ac_port	Integer	1 to 65535	cloud-management server port port-number	Yes
Server password	ac_password	String	1 to 63	cloud-management server password simple password	Yes
NTP server	ntp_server	IP address	N/A	ntp-service unicast-server ip-address	No
WAN interface	link_if	Interface type and number	N/A	interface interface-type interface-number	Yes
DHCP connection mode	link_mode	String	DHCP	N/A	Yes

 

Procedure

1.     Power on the device.

2.     Enable URL-based automatic configuration.

a.     Enter system view.

system-view

b.     Enable URL-based automatic configuration.

autodeploy url enable

By default, URL-based automatic configuration is enabled the state.

c.     Save the current configuration.

save

If URL-based automatic configuration is disabled on a device, you must execute this command, save the configuration, and reboot the device to make this feature take effect.

3.     On the configuration terminal, launch a Web browser and enter the default IP address of the device in the address bar. Then, enter the default username and password as prompted to log in to the device.

You can change the default IP address, username, and password on the device. The IP address and username are the device address and device name required in the URL.

4.     Construct a URL as describe in "How URL-based automatic configuration works."

5.     Enter the URL in the address bar and enter the username and password as prompted.

The device will use the parameters and values in the URL and the customizable configuration file to reconstruct a configuration file, and then execute the file to complete automatic configuration.

Configuration file

IMPORTANT: The contents of the configuration file might vary by device model.

 

PPPoE mode section

{link_mode = PPPoE}

#

 system-view

#

 sysname [sys_name]

#

 dialer-group 1 rule ip permit

#

interface Dialer1

 1:ppp chap password simple [chap_password]

 1:ppp chap user [chap_user]

 ppp ipcp dns admit-any

 ppp ipcp dns request

 1:ppp pap local-user [pap_user] password simple [pap_password]

 dialer bundle enable

 dialer-group 1

 dialer timer idle 0

 dialer timer autodial 5

 ip address ppp-negotiate

 tcp mss 1024

 nat outbound

#

 quit

#

interface [link_if]

 port link-mode route

 pppoe-client dial-bundle-number 1

#

 quit

#

 1:ntp-service unicast-server [ntp_server]

#

 cloud-management server domain [ac_host]

 cloud-management server port [ac_port]

 cloud-management server password simple [ac_password]

#

 ip route-static 0.0.0.0 0 Dialer1

#

Static IP address mode section

{link_mode = STATIC}

#

 system-view

#

 sysname [sys_name]

#

interface [link_if]

 port link-mode route

 ip address [static_ip] [static_mask]

 nat outbound

#

 qu

#

 1:ntp-service unicast-server [ntp_server]

#

 cloud-management server domain [ac_host]

 cloud-management server port [ac_port]

 cloud-management server password simple [ac_password]

#

 ip route-static 0.0.0.0 0.0.0.0 [gateway]

#

DHCP mode section

{link_mode = DHCP}

#

 system-view

#

 sysname [sys_name]

#

interface [link_if]

 port link-mode route

 ip address dhcp-alloc

 nat outbound

#

 qu

#

 1:ntp-service unicast-server [ntp_server]

#

 cloud-management server domain [ac_host]

 cloud-management server port [ac_port]

 cloud-management server password simple [ac_password]

#

Public cloud-based automatic configuration

About this task

VSRs use the mature Comware platform, and run on standard server VMs and bare-metal servers. VSRs provide the same experience as physical routers, and provide features such as routing, firewall, VPN, QoS, and configuration management. VSRs help an enterprise to build a secure, unified, expandable intelligent branch, and also reduce the number of branch infrastructures and the investments.

Traditionally, you must configure VSRs one by one or bulk configure VSRs through a script. In the public cloud scenario, this configuration method is inconvenient and slow. This feature allows the system to bulk configure VSRs through a public cloud. The administrator only needs to select related parameters on related Web pages of the public cloud.

Restrictions and guidelines

The public clouds that can automatically configure VSRs depend on the VSR compatibility.