How to save configuration locally on an AR router

27

There are two methods to export configuration locally on an AR router: web NMS and command lines.

1. Web NMS (example):
Log in to the web NMS, and choose System Management > Upgrade and Maintenance > Restart Device. Click Export Configuration File to back up the current configuration file to a local PC.

2. Command lines (example):
Use the router as an FTP server, and enable the FTP service.  
Enable the FTP server on the router, and create an FTP user with the user name huawei and password Helloworld@6789. Authorize the user to access the directory sd1:.
<Huawei> system-view
[Huawei] ftp server enable
Info: Succeeded in starting the FTP server.
[Huawei] aaa
[Huawei-aaa] local-user huawei password irreversible-cipher Helloworld@6789
[Huawei-aaa] local-user huawei ftp-directory sd1:
[Huawei-aaa] local-user huawei service-type ftp
[Huawei-aaa] local-user huawei privilege level 15

Initiate an FTP connection from a maintenance PC to the router.  
On the PC, create an FTP connection to the router through the FTP client (for example, the IP address of the router is 10.110.24.254).
C:\Documents and Setting\Administrator> ftp 10.110.24.254
Connected to 10.110.24.254.
220 FTP service ready.
User (10.110.24.254:(none)): huawei
331 Password required for huawei.
Password:
230 User logged in.

Set transmission parameters.  
After the FTP user passes the authentication, the FTP client displays the prompt "ftp>". Enter binary (binary transmission mode) under the prompt ftp>, and set a directory on the FTP client for storing uploaded files.
ftp> binary
200 Type set to I.
ftp> lcd c:\temp
Local directory now C:\temp.

Transmit the configuration file.  
On the PC, run the get command to download the configuration file to a locally specified directory, and name the file backup.cfg.
ftp> get sd1:/config.cfg backup.cfg

Other related questions:
How to configure local traffic mirroring on AR series routers
By configuring local traffic mirroring, you can replicate specific packets transmitted through an interface to local monitoring devices for analysis and surveillance. Prerequisites Before configuring local traffic mirroring, ensure that the link protocol state of the interface is Up. 1. Configure the local observing interface. Background In local traffic mirroring, monitoring devices are directly connected to the observing interface. It is recommended that other configurations should not be performed on an interface that is configured as the observing interface to prevent its mirroring function from being affected: - If not only the mirroring packets but also the packets of other services are transmitted through the observing interface, the source of the packets cannot be distinguished. - If traffic congests on the observing interface, mirroring packets may be discarded because the priority of the mirroring packets is lower. Procedure Run the system-view command to enter the system view. Run the observe-port interface interface-type interface-number command to configure the local observing interface. 2. Configure traffic mirroring. Background In traffic mirroring, the mirroring interface applies a traffic policy that includes traffic mirroring behavior. Packets that are transmitted through the interface and match the traffic classification rules are replicated to the observing interface. Procedure a. Configure the traffic classifier. Run the system-view command to enter the system view. Run the traffic classifier classifier-name [ operator { and | or } ] command to create a traffic classifier and enter the view of the traffic classifier. Run the if-match command to configure the matching rule of the traffic classifier based on actual requirements. Run the quit command to quit the view of the traffic classifier. b. Configure the traffic behavior. Run the traffic behavior behavior-name command to create traffic behavior and enter the view of the traffic behavior. Run the mirror to observe-port command to mirror traffic that matches the rule to the specified observing interface. Run the quit command to quit the view of the traffic behavior. Run the quit command to quit the system view. c. Configure the traffic policy. Run the system-view command to enter the system view. Run the traffic policy policy-name command to create a traffic policy and enter the view of the traffic policy, or directly enter the view of an existing traffic policy. Run the classifier classifier-name behavior behavior-name command to configure the traffic behavior of specified traffic classifiers in the traffic policy, that is, bind the traffic behavior to the specified traffic classifier. Run the quit command to quit the view of the traffic policy. Run the quit command to quit the system view. d. Apply the traffic policy. Run the system-view command to enter the system view. Run the interface interface-type interface-number [.subinterface-number ] command to enter the interface view. Run the traffic-policy policy-name { inbound | outbound } to apply the traffic policy in the inbound or outbound direction of the interface.

How to configure local interface mirroring on AR series routers
By configuring local interface mirroring, you can replicate the packets transmitted through the interface to local monitoring devices for analysis and surveillance. Before configuring local interface mirroring, ensure that the link protocol state of the interface is Up. 1. Configure the local observing interface. Background In local interface mirroring, monitoring devices are directly connected to the observing interface. It is recommended that other configurations should not be performed on an interface that is configured as the observing interface to prevent its mirroring function from being affected: - If not only the mirroring packets but also the packets of other services are transmitted through the observing interface, the source of the packets cannot be distinguished. - If traffic congests on the observing interface, mirroring packets may be discarded because the priority of the mirroring packets is lower. Procedure Run the system-view command to enter the system view. Run the observe-port interface interface-type interface-number command to configure the local observing interface. 2. Configure the local mirroring interface. Background An interface of any type can be configured as a mirroring interface. If an Eth-trunk interface is configured as a mirroring interface, a member interface of the Eth-trunk interface cannot be configured as a mirroring interface separately. If you want to configure a member interface of the Eth-trunk as a mirroring interface, you must unbind the member interface from the Eth-trunk interface. If a member interface of an Eth-trunk is configured as a mirroring interface, the Eth-trunk interface cannot be configured as a mirroring interface. If you want to configure the Eth-trunk interface as a mirroring interface, you must unbind the member interface that is configured as the mirroring interface from the Eth-trunk interface. Procedure Run the system-view command to enter the system view. Run the interface interface-type interface-number command to enter the interface view. Run the mirror to observe-port { both | inbound | outbound } [ exclude-link-head ] command to configure the local mirroring interface.

How to upload a web file on an AR router
How to upload a web file on an AR router?
Upload a web file through FTP to a router.
1.  Use the router as an FTP server, and enable the FTP service.  
Enable the FTP server on the router, and create an FTP user with the user name huawei and password Helloworld@6789. Authorize the user to access the directory sd1:.
[Huawei] ftp server enable
Info: Succeeded in starting the FTP server.
[Huawei] aaa
[Huawei-aaa] local-user huawei password irreversible-cipher Helloworld@6789  //Create an FTP user with the user name huawei and password Helloworld@6789.
[Huawei-aaa] local-user huawei ftp-directory sd1:    //Authorize the user to access the directory sd1:.
[Huawei-aaa] local-user huawei service-type ftp      //Set the service type of the user to FTP.  
[Huawei-aaa] local-user huawei privilege level 15     //Set the user level to 15. The larger the value, the higher the level.
[Huawei-aaa] return    //Return the user view.
<Huawei> save //Save the current configuration file.

2.  Initiate an FTP connection from a maintenance PC to the router.  
On the PC, create an FTP connection to the router through the FTP client (for example, the IP address of the router is 10.110.24.254).
C:\Documents and Setting\Administrator> ftp 10.110.24.254
Connected to 10.110.24.254.
220 FTP service ready.
User (10.110.24.254:(none)): huawei
331 Password required for huawei.
Password:
230 User logged in.

3.  Upload the web software to the router.
ftp> put Web.zip
200 Port command okay.
150 Opening BINARY mode data connection for devicesoft.cc
226 Transfer complete.
ftp:  Send  76556  bytes within  3.35 seconds   at the rate 560.79 Kbytes per second.

4.  View the files and sub-directories under the current directory.
<Huawei> dir
Directory of sd1:/
  Idx  Attr     Size(Byte)  Date        Time       FileName
    0  -rw-          6,311  Feb 17 2012 14:05:04   backup.cfg
    1  -rw-         76,556  Mar 06 2012 17:20:10   Web.zip

5.  Load the web file.
<Huawei> system-view
[Huawei] http server load Web.zip      //Load the web file. If the file has been loaded, ignore this step. In later versions of the software, the web file has been integrated into the system package, and does not need loading.

Configure rules of local policy routing on an AR router
Run the system-view command to access the system view. Run the policy-based-routepolicy-name { deny | permit } nodenode-id command to create policy-based routing and policy points. If policy points have been created, access the local policy routing view. By default, no local policy routing or policy point has been created. Note: For packets that matches a rule, permit indicates a policy routing is applied; while deny indicates no policy routing is applied. Repeat the previous command to create multiple policy points for a local policy routing. The policy points are specified based on the node ID. The smaller the node ID, the higher the priority, and corresponding policy is implemented preferentially. Run the if-match aclacl-number command to set ACL rules of IP packets. The command can be implemented once or twice. By default, rules about IP addresses are not configured in local policy routing. Note: If an ACL rule is set to permit, the router implements an action for packets that match the rule. When a policy point is permit, packets that match the rule are routed based on a policy. When a policy point is deny, packets that match the rule are not routed based on a policy, and are forwarded according to the destination IP addresses. If an ACL is configured with rules, packets that do not match any rule are forwarded according to the destination IP addresses. If an ACL rule is set to deny or an ACL is not configured with rules, local policy routing that applies the ACL does not take effect. Therefore, packets are forwarded according to the destination IP addresses. Run the if-match packet-lengthmin-lengthmax-length command to set a length rule of IP packets. By default, length rules of IP packets are not configured in local policy routing.

How to change local and remote discriminators on the AR router
For static BFD sessions, when the session is created for the first time, a single-hop BFD session is bound to a local interface, while a multi-hop session is not. For dynamic BFD sessions, query the routes to determine whether a BFD session is a single-hop session or a multi-hop session. BFP for Internal Border Gateway Protocol (IBGP) sessions are multi-hop sessions.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top