Configuring a Working Mode for an APS Group

A working mode can be configured for an APS group. The NE40E-X3  ME60    supports APS working modes, including automatic APS switching, and delayed switchback with the wait to restore (WTR) time configured. An APS working mode must be configured on a protect interface.

Run:

system-view

The system view is displayed.

Run:

interface interface-type interface-number

Or, run:

controller cpos cpos-number

The interface view is displayed.

Run:

aps mode { one2one bidirection | one-plus-one { bidirection | unidirection } }

A working mode is configured for the APS group. The configuration of an APS working mode takes effect after the shutdown and undo shutdown commands are run on the protect interface.

Run:

system-view

The system view is displayed.

Run:

interface interface-type interface-number

Or, run:

controller cpos cpos-number

The protect interface view of the APS group is displayed.

Run:

aps revert wtr-time

The WTR time is set for the APS group.

NOTE:

If two different switchback delays are set on two protect interfaces in APS groups on two ends of a link, the effective switchback delay depends on one of the following situations:

If one-plus-one unidirection is configured, the switckback delays of both protect interfaces take effect after the working interfaces recover.

If one2one bidirection or one-plus-one bidirection is configured, the switchback delay of the protect interface on the device with the working interface recovering later than the other working interface takes effect on both protect interfaces.

Configuring a VTY User Interface

Step 1 Configure LS-S5328C-EI-24S   the maximum number of concurrent VTY user interfaces.

<HUAWEI> system-view

[HUAWEI] user-interface maximum-vty 8

Step 2 Configure restrictions on call-in and call-out permissions on the VTY user interface.

[HUAWEI] acl 2000

[HUAWEI-acl-basic-2000] rule deny source 10.1.1.1 0

[HUAWEI-acl-basic-2000] rule permit source any

[HUAWEI-acl-basic-2000] quit

[HUAWEI] user-interface vty 0 7

[HUAWEI-ui-vty0-7] acl 2000 inbound

Step 3 Configure terminal attributes on the VTY user interface.

[HUAWEI-ui-vty0-7] shell

[HUAWEI-ui-vty0-7] idle-timeout 30

[HUAWEI-ui-vty0-7] screen-length 30

[HUAWEI-ui-vty0-7] history-command max-size 20

Step 4 Configure the user level on the VTY user interface.

[HUAWEI-ui-vty0-7] user privilege level 15

Step 5 Configure the authentication mode and password of the VTY user interface.

[HUAWEI-ui-vty0-7] authentication-mode password

[HUAWEI-ui-console0] set authentication password cipher huawei2012

[HUAWEI-ui-vty0-7] quit

After the VTY user interface is configured, users can log in to the device in the password

authentication mode using Telnet to maintain the device locally or remotely. For details on how

to log in to the device see Logging In to the Device Through Telnet.

Step 6 Verify the configuration.

# Run the quit command to disconnect the terminal from the device, connect the terminal to the

device using Telnet, and verify that the new password is valid.

# Use 10.1.1.1 to log in to the device using Telnet. The login fails.

# Run the user-interface vty 0 7 command to enter the VTY interface view, and run the display

this command to check the configurations on the VTY interface.

[HUAWEI] user-interface vty 0 7

[HUAWEI-ui-console0] display this

#

user-interface maximum-vty 8

user-interface vty 0 7

acl 2000 inbound

authentication-mode password

user privilege level 15

set authentication password cipher %%$%$RdF~Z+6N|0d^a3%v5`W~3.%ymjpAD#$u

[T'e#e32hd8G~4+&%$%$

history-command max-size 20

idle-timeout 30 0

screen-length LS-S5352C-EI  30

#

Configuring the Association Between BFD Status and Sub-Interface Status

Perform the following procedure on the ME60/NE40E-X3  that needs to rapidly detect the link fault:

Run:

system-view

The system view is displayed.

Run:

bfd cfg-name

The BFD session view is displayed.

Run:

process-interface-status sub-if

The association between the BFD status and the sub-interface status is configured.

Run:

commit

The configuration is committed.

NOTE:

When the process-interface-status command and the commit command are run in succession, the BFD session may not be set up or the BFD session does not go Up through negotiation. Therefore, the BFD session does not notify the interface of the BFD status immediately, avoiding that the BFD session notifies the interface of incorrect status information that results in incorrect interface status change. After the configuration is committed, the BFD sessions can notify the interface of the BFD status change. In this manner, the BFD session status is associated with the interface status.

If the networking requires that the BFD status must be synchronized with the interface status, you can run the shutdown and undo shudown commands to change the status of the BFD session. When the undo shutdown command is run, a timer to test the BFD session status is started. If the BFD session goes Up through negotiation before the timer expires, the BFD session notifies the interface of the Up state. Otherwise, the BFD session regards the link as failed and notifies the interface of the Down state after the timer expires. In this manner, the BFD session status and the interface status are in real-time synchronization.

If the process-interface-status command is saved in the configuration file, the BFD session that is bound to the interface notifies the interface that the BFD session is Down when the NE80E/40E is restarted, in view of the initial status of an interface being Down.

Before BFD status is associated with interface status, the BFD configurations on the two NE80E/40Es must be correct and symmetrical. If the BFD status on the local interface goes Down, check whether the BFD configuration on the peer is correct or whether the BFD session has been shut down.

Configuring the GE/FE Optical/Electrical Interface on Huawei NE40E

Generally, the Huawei ME60/Huawei NE40E   sets an Ethernet interface to an optical or electrical interface based on the interface module's type. If the NE80E/40E cannot identify an interface module, you need to manually set the interface to the optical or electrical mode.

Run:

system-view

The system view is displayed.

Run:

interface { ethernet | gigabitethernet } interface-number

The Ethernet interface view is displayed.

Run:

port-type { copper | fiber-100 | fiber-1000 }

The interface type is set.

Once the SFP module is identified, the system can automatically set the interface type according to the type of the SFP module. No configuration is required.

If the SFP module that cannot be identified works well, you need to forcibly set the interface type.

 NOTE:

When an SFP module is being replaced, the configurations such as the loopback test, interface speed, auto-negotiation mode, and duplex mode on the interface are all restored to default ones. You need to reconfigure them on the interface.

After the port-type command is run, the configurations such as the loopback test, interface speed, auto-negotiation mode, and duplex mode on the interface are all restored to default ones. You need to reconfigure them on the interface.

The parameter copper can be configured in the port-type command only when an optical/electrical SFP module is installed.

Configuring CAR on a Layer 2 Port

The Huawei ME60 /40E supports configuration of traffic policing in both inbound and outbound directions on Layer 2 interfaces.

You can configure traffic policing for the NE80E/40E only on the physical GE and Ethernet interfaces.

Run:

system-view

The system view is displayed.

Run:

interface { ethernet | gigabitethernet } interface-number

The interface view is displayed.

Run:

portswitch

The Layer 2 interface view is displayed.

Run:

port default vlan vlan-id

A Layer 2 interface is added to a specified VLAN.

NOTE:

Please confirm the specified VLAN has been created before running this command.

Run:

port trunk allow-pass vlan { { vlan-id1 [ to vlan-id2 ] } & <1-10> | all }

The IDs of the VLANs allowed by the current interface are specified.

Run:

qos car { cir cir-value [ pir pir-value] } [ cbs cbs-value pbs pbs-value ] [ green { discard | pass [ service-class class color color ] } | yellow { discard | pass [ service-class class color color ] } | red { discard | pass [ service-class class color color ] } ]* { inbound | outbound } [ vlan { vlan-id1 [ to vlan-id2 ] &<1-10> } ]

 NOTE:

CAR is configured on an interface. The parameter [ vlan { vlan-id1 [ to vlan-id2 ] &<1-10> } ] takes effect only on layer 2 interfaces, and VLAN ID must be configured. When this command is configured  ME60 on a layer 3 interface, however, VLAN ID cannot be configured.

Configuration file of ME60 A

 sysname Huawei ME60A

#

 set board-type slot 5 tunnel

#

interface GigabitEthernet2/0/0

 undo shutdown

 ip address 10.1.1.2 255.255.255.0

#

interface Pos1/0/0

 undo shutdown

 link-protocol ppp

 ip address 20.1.1.1 255.255.255.0

#

interface LoopBack1

 ip address 1.1.1.9 255.255.255.255

target-board 5

binding tunnel gre

#

interface Tunnel5/0/1

 tunnel-protocol gre

 ip address 40.1.1.1 255.255.255.0

 source LoopBack1

 destination 2.2.2.9

#

ospf 1

 area 0.0.0.0

  network 20.1.1.0 0.0.0.255

  network 1.1.1.9 0.0.0.0

#

ip route-static 10.2.1.0 255.255.255.0 Tunnel5/0/1

#

return

Configuration file of ME60 B

#

 sysname ME60B

#

interface Pos1/0/0

 undo shutdown

 link-protocol ppp

 ip address 20.1.1.2 255.255.255.0

#

interface Pos2/0/0

 undo shutdown

 link-protocol ppp

 ip address 30.1.1.1 255.255.255.0

#

ospf 1

 area 0.0.0.0

  network 20.1.1.0 0.0.0.255

  network 30.1.1.0 0.0.0.255

#

return

Configuration file of ME60 C

#

 sysname ME60C

#

 set board-type slot 5 tunnel

#

interface GigabitEthernet2/0/0

 undo shutdown

 ip address 10.2.1.2 255.255.255.0

#

interface Pos1/0/0

 undo shutdown

 link-protocol ppp

 ip address 30.1.1.2 255.255.255.0

#

interface LoopBack1

ip address 2.2.2.9 255.255.255.255

target-board 5

binding tunnel gre

#

interface Tunnel5/0/1

 tunnel-protocol gre

 ip address 40.1.1.2 255.255.255.0

 source LoopBack1

 destination 1.1.1.9

#

ospf 1

 area 0.0.0.0

  network 30.1.1.0 0.0.0.255

  network 2.2.2.9 0.0.0.0

#

ip route-static 10.1.1.0 255.255.255.0 Tunnel5/0/1

#

ME60 Return

Configuring a Tunnel Interface on Huawei AR3260

AR3260 Series routers are designed to provide secure unified voice and data communication with exceptional performance and scalability to meet the demands of today’s enterprise requirements.

Run:

system-view

The system view is displayed.

Run:

interface tunnel interface-number

A tunnel interface is created and the tunnel interface view is displayed.

Run:

tunnel-protocol gre

The tunnel encapsulation mode is set to GRE.

Run:

source { source-ip-address | interface-type interface-number }

The source address or source interface is configured for the tunnel interface.

Run:

destination [ vpn-instance vpn-instance-name ] dest-ip-address

The destination address is configured for the tunnel interface.

Run:

mtu mtu

The MTU of the interface is set.

Run:

description text

The description of the current tunnel interface is set.

Run:

ip address ip-address { mask | mask-length } [ sub ]

An IP address is configured for the interface.

Run:

ip address unnumbered interface interface-type interface-number

The tunnel interface is configured as an IP unnumbered interface.

The Huawei AR3260  routers integrate routing, switching, 3G, voice, and security functions. It utilizes a multi-core CPU and non-blocking switching structure providing industry-leading system performance and extensibility, supporting evolving service development requirements.

Configuring a Single RRPP Ring the ME60

Create an RRPP domain and its control VLAN.

# Configure the domain of ME60A, the master node of ring 1, to be 1, and the ID of the major control VLAN to be 20.

<ME60A> system-view

[ME60A] rrpp domain 1

[ME60A-rrpp-domain-region1] control-vlan 20

[ME60A-rrpp-domain-region1] quit

# Configure the domain of ME60B, a transit node of ring 1, to be 1, and the ID of the major control VLAN to be 20.

<ME60B> system-view

[ME60B] rrpp domain 1

[ME60B-rrpp-domain-region1] control-vlan 20

[ME60B-rrpp-domain-region1] quit

# Configure the domain of ME60C, a transit node of ring 1, to be 1, and the ID of the major control VLAN to be 20.

<ME60C> system-view

[ME60C] rrpp domain 1

[ME60C-rrpp-domain-region1] control-vlan 20

[ME60C-rrpp-domain-region1] quit

Disable the STP function on the interfaces to be added to the RRPP ring.

# Disable the STP function on the interfaces to be added to the RRPP ring on ME60A.

<ME60A> system-view

[ME60A] interface gigabitethernet 2/0/1

[ME60A-GigabitEthernet2/0/1] undo shutdown

[ME60A-GigabitEthernet2/0/1] portswitch

[ME60A-GigabitEthernet2/0/1] stp disable

[ME60A-GigabitEthernet2/0/1] quit

[ME60A] interface gigabitethernet 2/0/2

[ME60A-GigabitEthernet2/0/2] undo shutdown

[ME60A-GigabitEthernet2/0/2] portswitch

[ME60A-GigabitEthernet2/0/2] stp disable

[ME60A-GigabitEthernet2/0/2] quit

# Disable the STP function on the interfaces to be added to the RRPP ring on ME60B.

<ME60B> system-view

[ME60B] interface gigabitethernet 2/0/1

[ME60B-GigabitEthernet2/0/1] undo shutdown

[ME60B-GigabitEthernet2/0/1] portswitch

[ME60B-GigabitEthernet2/0/1] stp disable

[ME60B-GigabitEthernet2/0/1] quit

[ME60B] interface gigabitethernet 2/0/2

[ME60B-GigabitEthernet2/0/2] undo shutdown

[ME60B-GigabitEthernet2/0/2] portswitch

[ME60B-GigabitEthernet2/0/2] stp disable

[ME60B-GigabitEthernet2/0/2] quit

# Disable the STP function on the interfaces to be added to the RRPP ring on ME60C.

<ME60C> system-view

[ME60C] interface gigabitethernet 2/0/1

[ME60C-GigabitEthernet2/0/1] undo shutdown

[ME60C-GigabitEthernet2/0/1] portswitch

[ME60C-GigabitEthernet2/0/1] stp disable

[ME60C-GigabitEthernet2/0/1] quit

[ME60C] interface gigabitethernet 2/0/2

[ME60C-GigabitEthernet2/0/2] undo shutdown

[ME60C-GigabitEthernet2/0/2] portswitch

[ME60C-GigabitEthernet2/0/2] stp disable

[Huawei ME60C-GigabitEthernet2/0/2] quit

Obtaining Upgrade AR3260 Software

The system software of AR3260 V200R002C02SPC200 is AR3260-V200R002C02SPC200.cc.

Run the display version command in the user view to check the current system software version and ensure that it meets the upgrade requirement.

<Huawei>display version                                                         

Huawei Versatile Routing Platform Software                                     

VRP (R) software, Version 5.90 (AR3200 V200R002C02SPC100)                      

Copyright (C) 2011 HUAWEI TECH CO., LTD                                         

Huawei AR3260 Router uptime is 0 week, 0 day, 0 hour, 1 minute                 

BKP 0 version information:                                                     

1. PCB      Version  : AR01BAK3A VER.B                                         

2. If Supporting PoE : No                                                      

3. Board    Type     : AR3260                                                  

4. MPU Slot Quantity : 2                                                       

5. LPU Slot Quantity : 10                                                      

                                                                               

MPU 15(Master) : uptime is 0 week, 0 day, 0 hour, 1 minute                     

SDRAM Memory Size    : 2048    M bytes                                         

Flash Memory Size    : 16      M bytes                                         

NVRAM Memory Size    : 512     K bytes                                         

SD Card0 Memory Size : 1882    M bytes                                          

MPU version information :                                                      

1. PCB      Version  : AR01SRU3A VER.B                                         

2. MAB      Version  : 0                                                        

3. Board    Type     : SRU80                                                   

4. CPLD0    Version  : 104                                                     

5. CPLD1    Version  : 104                                                      

6. FPGA     Version  : 111                                                     

7. BootROM  Version  : 236                                                     

                                                                               

LPU 2 : uptime is 0 week, 0 day, 0 hour, 0 minute                              

SDRAM Memory Size    : 256     M bytes                                         

Flash Memory Size    : 16      M bytes                                         

LPU version information :                                                      

1. PCB      Version  : AR01SDCE2A VER.B                                        

2. MAB      Version  : 0                                                       

3. Board    Type     : 1E1/T1-M                                                

4. CPLD0    Version  : 100                                                     

5. BootROM  Version  : 203                                                     

                                                                                

FAN version information :                                                      

1. PCB      Version  : AR01DF05A VER.A                                         

2. Board    Type     : FAN                                                      

3. Software Version  : 104

In the preceding output, AR3260 V200R002C02SPC100 indicates the system software version currently running on the ME60. If this is the target version, no upgrade is necessary.

UATool NE40E Usage Scenario

The UATool must be used to upgrade the  Huawei NE40E. The UATool can be used in three upgrade scenarios. Huawei recommends the first two scenarios. The third scenario, on-site upgrade, can be used if necessary. The three scenarios are described below:

  Remote upgrade with nearby support

Software commissioning engineers remotely upgrade the NE40E-X1/X2 from the network management center. Spare part provisioners wait near the site and are ready to deliver spare parts to the site quickly. Huawei recommends this scenario in the following situations:

−    The project is at the site deployment stage, and there are no stringent time requirements for replacing spare parts.

−    The spare part provisioning site is close to the upgrade site with favorable traffic and road conditions so that spare parts can be installed within the required time frame.

−    There are backup planes or links on the customer's network, and customer requirements allow enough time to install spare parts.

  Remote upgrade with on-site support

Software commissioning engineers remotely upgrade the NE40E-X1/X2 from the network management center. Spare part provisioners wait on site. Huawei recommends this scenario if spare parts cannot be delivered to the site within the required time frame.

  On-site upgrade

Software commissioning engineers upgrade the NE40E-X1/X2 on site. Spare parts are also available on site. This scenario can be used when only one site is being upgraded.

Huawei recommends that the upgrade is performed using the UATool. The UATool can automatically compare pre-upgrade services and post-upgrade services. This prevents operator errors during the upgrade and decreases upgrade risks.

In all the three scenarios, software commissioning engineers must be Huawei engineers with a good command of the NE40E-X1/X2 upgrade procedures. The personnel providing and replacing parts (who can be engineers from Huawei partners or customer staff) must be able to correctly identify product models and replace boards.

The three scenarios described above are examples of typical upgrade situations. Engineers can flexibly determine the way the upgrade is performed based on the real-world situation.

The NE40E-X1/X2 plays an important role on a network. Ensure that spare parts are available when using the UATool to upgrade the NE40E

How to Configuring IPoEoA Mapping on PVCs Huawei AR3200

Huawei AR3260 Series routers are designed to provide secure unified voice and data communication with exceptional performance and scalability to meet the demands of today’s enterprise requirements.

Run:

system-view

The system view is displayed.

Run:

interface virtual-ethernet interface-number

A VE interface is created and the VE interface view is displayed.

Run:

quit

The system view is displayed.

Run:

interface atm interface-number [.subinterface ]

The ATM interface or sub-interface view is displayed.

Run:

pvc { pvc-name [ vpi/vci ] | vpi/vci }

A PVC is created and the PVC view is displayed.

Run:

encapsulation { aal5snap | aal5mux }

The AAL5 encapsulation type is specified for the PVC.

The AAL5 encapsulation type can be aal5snap or aal5mux. The default value is aal5snap.

Run:

map bridge virtual-ethernet interface-number

IPoEoA mapping is AR3260 configured.

Configuring a Static Route

The management network interface does not participate in dynamic route calculation. Thus, in the scenario where the device to be commissioned is connected to the NMS through the management network interface, and the IP address of the management network interface and the IP address of the NMS are not on the same network segment, you can configure static routes to enable the Layer 3 communication between the device and the NMS.

the Huawei ME60-X3 to be commissioned is connected to the NMS through the management network interface GE 0/0/0. The IP address of the management network interface and the IP address of the NMS are not on the same network segment.

The management network interface does not participate in dynamic route calculation. Thus, you need to configure static routes to enable the Layer 3 communication between the ME60 and the NMS.

# After the configuration is complete, run the display ip routing-table command on ME60 to check whether there is a static route in the routing table.

<HUAWEI> display ip routing-table

Route Flags: R - relay, D - download to fib

------------------------------------------------------------------------------

Routing Tables: Public

        Destinations : 9        Routes : 9

Destination/Mask    Proto  Pre  Cost        Flags NextHop         Interface

        1.1.1.1/32  Direct 0    0             D  127.0.0.1       InLoopBack0

    192.168.1.0/24  Direct 0    0             D  192.168.1.1     GigabitEthernet0/0/0

    100.1.1.200/32  Direct 0    0             D  127.0.0.1       InLoopBack0

    100.1.1.255/32  Direct 0    0             D  127.0.0.1       InLoopBack0

      127.0.0.0/8   Direct 0    0             D  127.0.0.1       InLoopBack0

      127.0.0.1/32  Direct 0    0             D  127.0.0.1       InLoopBack0

127.255.255.255/32  Direct 0    0             D  127.0.0.1       InLoopBack0

      192.167.1.0/24  Static 60   0             D  192.168.1.2     GigabitEthernet0/0/0

255.255.255.255/32  Direct 0    0             D  127.0.0.1       InLoopBack0

# Run the ping command on Huawei ME60-X8  to verify the connectivity.

<HUAWEI> ping 192.167.1.10

PING 192.167.1.10: 56  data bytes, press CTRL_C to break

    Reply from 192.167.1.10: bytes=56 Sequence=1 ttl=254 time=60 ms

    Reply from 192.167.1.10: bytes=56 Sequence=2 ttl=254 time=65 ms

    Reply from 192.167.1.10: bytes=56 Sequence=3 ttl=254 time=36 ms

    Reply from 192.167.1.10: bytes=56 Sequence=4 ttl=254 time=93 ms

    Reply from 192.167.1.10: bytes=56 Sequence=5 ttl=254 time=23 ms

  --- 192.167.1.10 ping statistics ---

    5 packet(s) transmitted

    5 packet(s) received

    0.00% packet loss

round-trip min/avg/max = 23/55/93 ms