For the router-id selection (if no router-id is defined using the router id command line) Huawei routers select the first loopback interface (interface loopback 1) on the router to be the router-id. The distribute-list feature does not support filtering of outgoing routing update. Only incoming routing update can be filtered. No information about the OSPF type of route is indicated in the display of the show ip route command.
Results Summary Table Total Pass Fail 3.1.4 Detailed Results
3.1.4.1 Router ID Objective: Verify that the router ID is assigned correctly. Test ID OSPF-RTR-ID_1 Task Description Check that a 32-bit number can be assigned to the router as a router ID. Results Passed
3.1.4.2 Network Topology Objective: Verify OSPF functionality. Test ID OSPF-NET_1 Task Description Configure DUT as an internal router in Area 0. Verify that the DUT can discover neighbours and form adjacencies with its neighbours. Verify the DUT establishes adjacencies with all of its neighbours on broadcast multi-access network. Verify the router with the highest priority becomes the DR. If a tie, the router with the numerically highest Router ID becomes the DR. Verify the router not claiming to be the DR with the highest priority greater than 0 becomes the BDR. If a tie, the router with the numerically highest Router ID becomes the BDR. Verify support for VLSM by making sure all routes are associated with a mask. Verify the administrative distance hierarchy. Verify interfaces onto broadcast and non-broadcast networks have a default router priority of 1. Verify DUT and other routers in Area 0 have the same Link State Database. Results Passed

OSPF-NET_2

Passed

OSPF-NET_3

OSPF-NET_4
OSPF-NET_5 OSPF-NET_6 OSPF-NET_7 OSPF-NET_8
Passed Passed Passed Passed

OSPF-NET_9

Configure DUT as Internal Router in an Area different than the backbone. Verify DUT and other routers in the same Area have the same Link State Database. Configure DUT as Area Border Router. Verify DUT has the same Link State Database for Area 0 and the other area(s) when configured as ABR. Define the type of media for the interface used in OSPF (nonbroadcast). Configure the DUT as ABR for a Stub Area. Configure the DUT as ABR connected to area 0 via virtual-link. Configure the DUT as ABR for a Not So Stubby Area.

OSPF-NET_10 OSPF-NET_11

Passed Passed
OSPF-NET_12 OSPF-NET_13 OSPF-NET_14 OSPF-NET_15
3.1.4.3 Metrics Objective: Verify that path selection is influenced by OSPF metrics. Test ID OSPF-MET_1 Task Description Verify proper default metrics based on bandwidth (10 EXP8 /bandwidth in bps). Configure manually an OSPF cost to an interface. Verify new cost changes and proper route selection by selecting the lower cost preferred path. Results Passed

3.3.4.5 General Display Objective: Assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Test number Test description Results

RIP_GD_1

Show ip rip displays global RIP information
3.3.4.6 Debugging Objective: Verify the level of debugging available on the DUT is sufficient to troubleshoot problems. Test number RIP_DG_1 RIP_DG_2 RIP_DG_3 Test description Debug ip rip packet display message about all RIP packets Debug ip rip recv display message about RIP packets received Debug ip rip send display message about RIP packets sent Results Passed Passed Passed
3.4.1 Key Test Items The following functionalities of the IPX RIP routing protocol have been configured and tested. Initial testing verify the main IPX RIP features. Metrics verify the proper implementation of metrics and how they influence path selection in IPX RIP. Timers verify the proper implementation of timers and how they influence rapid convergence and reliable operation of IPX RIP. Route control verify that routing updates within the IPX RIP routing domain can be controlled. Interoperability verify that the IPX RIP functionality interoperates with Cisco equipment. General display verify that the IPX RIP status on the Huawei routers can be displayed in a correct, complete and properly formatted manner. Debugging verify that the debugging capability of the Huawei routers are sufficient to troubleshoot IPX RIP problems.
3.4.2 Network Topology The following network topology was used to test the IPX RIP routing protocol functionalities on the Huawei routers.
Figure 5: IPX RIP Network Topology 3.4.3 Results Summary The IPX RIP protocol implementation on the Huawei routers has passed the most important tests. However some features such as metrics and timers were not implemented at the time of testing. Results Summary Table Total Pass Fail 3.4.4 Detailed Results
3.4.4.1 Initial Testing Objective: Verify IPX RIP functionality. Test number IPX RIP_INI_1 Test description Enable IPX routing on the DUT. Results Passed
3.4.4.2 Timers Objective: Configure and verify several timers that determine such variables as the frequency of routing updates. Test number IPX RIP_TIM_1 IPX RIP_TIM_2 Test description Configure the interval at which a network or server IPX RIP entry ages out. Adjust the RIP update timer. Results Passed Passed
3.4.4.3 Route Control Objective: Verify the route control in the DUT IPX RIP routing table. Test number IPX RIP_RC_1 Test description Advertise only the default route via the specified network RIP default route. Results Passed.

3.4.4.4 General Display Objective: Assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Test number IPX RIP_GD_1 IPX RIP_GD_2 IPX RIP_GD_3 IPX RIP_GD_4 Test description Show ipx route default display default route. Show ipx route <1- FFFFFFFE> display IPX network number. Show ipx route static display static route. Show ipx route detailed comprehensive display. Results Passed Passed Passed Passed
3.4.4.5 Debugging Objective: Verify the level of debugging available on the DUT is sufficient to troubleshoot problems. Test number Test description Results
IPX RIP_DEB_1 3.5 Static Routing
Debug ipx routing display IPX RIP routing information.
3.5.1 Key Test Items The following functionalities of static routing were configured and tested. Initial testing verify the main static routing functionality. Metrics verify the proper implementation of metrics and how they influence the static route selection. General display verify that the static route status on the Huawei routers can be displayed in a correct, complete and properly formatted manner.
3.5.2 Network Topology The following network topology was used to test the static routing functionalities on the Huawei routers.
Figure 6: Static Route Network Topology 3.5.3 Results Summary Huawei routers passed all the tests performed and static routing operated as expected. Results Summary Table Total Pass Fail 3.5.4 Detailed Results
3.5.4.1 Initial Testing Objective: Verify Static Route functionality Test number STAT_1 STAT_2 STAT_3 Test description Configure static routes Configure default route Remove static route Results Passed Passed Passed

STAT_4 STAT_5 STAT_6

Remove default route Assign a host name to an ip address Check ip connectivity with ping command
3.5.4.2 Metrics Objective: Verify the administrative distance metric. Test number STAT_MED_1 STAT_MED _2 Test description Verify administrative distance is 1 Configure static routes with a different administrative distance Results Passed Passed
3.5.4.3 General Display Objective: Assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Test number STAT_SH_1 STAT_SH_2 Test description Show ip route static - displays global static route information Show ip route display abstract routing information Results Passed Passed

Tunnelling Protocols

The following tests were designed to investigate the tunnelling protocol implementation on the Huawei routers. 4.1 GRE (Generic Routing Encapsulation) The following functionality of GRE protocol was configured and tested. 4.1.1 Key Test Items The following features of the GRE protocol were tested to ensure that GRE was functioning correctly: 4.1.2 IP verify that IP tunnels can be configured and that they work correctly. IPX verify that IPX tunnels can be configured and that they work as expected. Interoperability verify that both IP and IPX tunnels work correctly when configured between the Huawei routers and Cisco equipment. General Display verify that the applicable show commands display correct and relevant information. Debugging verify that the GRE debug features of the Huawei router are useful and would be of use for troubleshooting network problems. Network Topology

6.3.4.4 General display Objective: Assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Test number IPS-GD-1 Test description Use show commands to verify that IPsec/IKE is functioning correctly. Results Passed
6.3.4.5 Debugging Objective: Verify the level of debugging available on the DUT is sufficient to troubleshoot problems. Test number IPS-DB-1 6.4 Test description Use debug commands to verify IPsec/IKE operation and verify output is useful in a troubleshooting scenario. Results Passed
6.4.1 Key Test Items Due to the shortage of useable IPv4 addresses and the speed of deployment of IPv6, NAT plays an increasingly important role in network deployment. The following are the main tested items: Static NAT verify the operation of Static NAT Dynamic NAT verify the operation of Dynamic NAT NAT Overloading verify the operation of NAT Overloading NAT Overlapping verify the operation of NAT Overlapping Port Redirection verify the Port Redirection functionality General Display assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Debugging verify the level of debugging available on the DUT is sufficient to troubleshoot problems.
6.4.2 Network Topology Variations of the following diagram were used to test all Huawei routers.
Figure 13: NAT Network Topology 6.4.3 Results Summary One point of note is that the show nat command was the only show command for NAT. The command will show what IP addresses are in the pool but do not change to reflect that these addresses are in use or show what port numbers are in use, where applicable. Results Summary Table Total Pass Fail 1 6.4.4 Detailed Results The details of the individual tests are below: 6.4.4.1 Static NAT Objective: Verify the operation of Static NAT. Test number NAT-ST-1 Test description Verify translation uses correct static IP address Results Passed
6.4.4.2 Dynamic NAT Objective: Verify the operation of Dynamic NAT. Test number NAT-DY-1 NAT-DY-2 Test description Verify dynamic NAT operation Verify translated IP addresses are assigned dynamically from NAT pool Results Passed Passed

6.4.4.3 NAT Overloading Objective: Verify the operation of Overloading NAT. Test number NAT-OVRL-1 Test description Verify NAT overloading capabilities Results Passed

NAT-OVRL-2 NAT-OVRL-3

Verify that only one IP address is used in translation Verify that port numbers are used to differentiate source hosts
6.4.4.4 Port Redirection Objective: Verify that port redirection works. Test number NAT-PR-1 NAT-PR-2 Verify port redirection Verify traffic is redirected to stated port number Test description Results Passed Passed
6.4.4.5 General Display Objective: Assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Test number IPS-GD-1 Test description Use show commands to verify that NAT is functioning correctly and that the level of detail in the commands are sufficient to give a clear understanding of the NAT operation. Results Failed
6.4.4.6 Debugging Objective: Verify the level of debugging available on the DUT is sufficient to troubleshoot problems. Test number IPS-DB-1 Test description Use debug commands to verify NAT operation and verify output is useful in a troubleshooting scenario. Results Passed

Network layer

During the test period IP, IPX and DHCP protocol implementations were evaluated on the Huawei routers as part of the network layer tests. Absolute conformance testing was not performed, but a thorough investigation of the network layer was done. The following paragraphs show the results obtained during the testing. 7.1 IP Tests
7.1.1 Key Test Items The following IP tests were performed on the Huawei routers. IP header tests verify how the router handles IP packets when various fields of the IP header are modified. IP ICMP tests verify how the router handles IP ICMP generation/messages. IP ARP tests verify how the router handles IP ARP generation/messages. IP Misc tests verify the router supports miscellaneous IP commands. General display verify that the range of display commands on the Huawei routers can display information in a correct, complete and properly formatted manner. Debugging verify that the debugging capability of the Huawei routers are sufficient to troubleshoot network layer problems.
7.1.2 Network Topology The following network diagram was used to perform the investigation of the IP layer on the Huawei routers.

Results Summary Table Total Pass Fail 8.1.4 Detailed Results The following tables contain the detailed results for Frame Relay testing. 8.1.4.1 Encapsulation and LMI conformity Objective: To configure the different frame relay encapsulations and LMI types including auto negotiation of LMI. Test number Test description Results Passed Passed Passed Passed Passed
FR_EN_LMI_1 Configure the routers serial interface and frame relay switch for IETF encapsulation and an ANSI LMI, ensure the line is up FR_EN_LMI_2 Configure the routers serial interface and frame relay switch for IETF encapsulation and an ITU-T LMI, ensure the line is up FR_EN_LMI_3 Configure the routers serial interface and frame relay switch for IETF encapsulation and an Cisco LMI (if supported), ensure the line is up FR_EN_LMI_4 Configure the routers serial interface and frame relay switch for Cisco encapsulation (if supported) and an Cisco LMI, ensure the line is up FR_EN_LMI_5 Configure the routers serial interface and frame relay switch for Cisco
encapsulation (if supported) and an ANSI LMI, ensure the line is up FR_EN_LMI_6 Configure the routers serial interface and frame relay switch for Cisco encapsulation (if supported) and an ITU-T LMI, ensure the line is up FR_EN_LMI_7 Investigate outcome of changing the timers at the DTE (T391, N391), error thresholds (N393, N393). Passed Passed
8.1.4.2 Creating sub-interfaces Objective: Create multiple sub-interfaces on the serial interface to create a fully functional and stable routing table. Test number Test description Results Passed Passed
FR_SUBINT_1 Create multiple sub interfaces on one router and map different dlcis to different routers/ip addresses, ensure connectivity to far ends. FR_SUBINT_2 Configure a routing protocol at each router and ensure that routes are learnt on one remote router for the other remote routers that are not connected by pvcs and are learnt via the router with the sub interfaces.
8.1.4.3 Protocol Mapping/PVC Objective: To configure and test the mapping of layer 3 protocols (IP and IPX) to Frame Relay layer 2 addresses (DLCI). Test number Test description Results Passed Passed Passed
FR_PROTMAP_1 Configure the serial interface on two routers for IP on a point-to-point PVC and create a map statement to the far end and ensure connectivity. FR_PROTMAP_2 Configure the same serial interface on the two routers for IPX and ensure connectivity. FR_PROTMAP_3 Using sub-interfaces configure different DLCIs/PVCs to the same destination but only let IP over one DLCI and IPX over the second DLCI and ensure connectivity. This then segregates different protocol traffic down different PVCs. 8.1.4.4 Traffic Shaping Objective: To configure traffic shaping on the router. Test number FR_TS_1 FR_TS_2 Test description Limit the amount of traffic that may be sent using frame relay maps out of any PVC, using CIR, average rates and burst rates. Configure bandwidth for IP on a PVC using frame relay maps and a queuing policy (custom or priority).

8.2.2 Network Topology Variations of the following diagram were used to test all Huawei routers and to test interoperability with a Cisco router.
Figure 19: X25 Test Topology 8.2.3 Results Summary All X25 tests were passed with no problems found. Results Summary Table Total Pass Fail 8.2.4 Detailed Results
8.2.4.1 Initial Setup Objective: To enable X25 on the router and test IETF encapsulation and Cisco encapsulation if supported. Other encapsulation types could be tested if required i.e. bfe and ddn. Test number X25_INI_1 Test description Connect the router to the x25 switch, ensure the modulo, timers, virtual circuit ranges, input and output packet size and window sizes are identical either end. Enable X25 on the router, on the serial link make the interface a dte and ietf encapsulation and assign an X25 address. Ensure interface is up and all controls report the right conditions. Connect the router to the x25 switch, ensure the modulo, timers, virtual circuit ranges input and output packet size, and window sizes are identical either end. Enable X25 on the router, on the serial link make the interface a dte and Cisco encapsulation and assign an X25 address. Ensure interface is up and all controls report the right conditions Results Passed

X25_INI_2

8.2.4.2 SVC Setup Objective: To create SVCs over an x25 network, test using IP and IPX other protocols may be tested if required. Test number X25_SVC_1 X25_SVC_2 X25_INI_3 Test description Set up multiple routers into the X25 network (switch), add ip addresses to the interfaces and create SVCs to each other (using map statements). Ensure connectivity between all routers that are mapped. Set up multiple routers into the X25 network (switch), add ipx addresses to the interfaces and create SVCs to each other (using map statements). Ensure connectivity between all routers that are mapped. This is to prove that multi-protocols will run over the same virtual circuit. Set up multiple routers into the X25 network (switch), add ip and ipx addresses to the interfaces and create SVCs to each other (using map statements). Ensure connectivity between all routers that are mapped for each protocol configured. Results Passed Passed Passed
8.2.4.3 PVC Setup Objective: To configure and test the mapping of layer 3 protocols (IP and IPX) to X25 address over a PVC. Test number X25_PVC_1 Test description Alter the virtual circuit channels so that VCIs are allocated to PVCs, this must be done both ends of the links and be identical i.e. change lic, hic, ltc, htc, loc, hoc channel allocation. Using routers connected to the x25 switch/network, configure PVCs to each router creating a full mesh using ip addresses to x25 addresses. Ensure connectivity. NB: PVC number must be in the range as allocated in the virtual channel ranges. As above but using IPX addresses Results Passed

X25_PVC_2

8.2.4.4 X25 Parameter changes Objective: To ensure any parameter changes take effect and function correctly. Test number X25_PARA_1 X25_PARA_2 X25_PARA_3 Test description Change the modulo to 128 and ensure window sizing can be increased up to 127 from 7 for modulo 8 Alter X25 layer 3 timers (T20, T21, T22, T23) at both ends and ensure they are implemented. Alter the input/output packet size and ensure it is implemented Results Passed Passed Passed

Transparent Bridging verify the operation of Transparent bridging. Spanning Tree Protocol verify the operation of the STP build process. Concurrent Routing and Bridging verify the operation of CRB. Integrated Routing and Bridging verify the operation of IRB. Interoperability verify that the bridging functionality interoperates with Cisco equipment. General Display assess the range of display commands supported and ensure that the information presented is correct, complete and properly formatted. Debugging verify the level of debugging available on the DUT is sufficient to troubleshoot problems.
8.6.2 Network Topology Variations of the following diagram were used to test all Huawei routers and to test interoperability with a Cisco router.
Figure 23: Bridging Network Topology 8.6.3 Results Summary All the test items were completed without any queries and as such all have attained a pass grade. Results Summary Table Total Pass Fail 8.6.4 Detailed Results
8.6.4.1 Transparent Bridging Objective: Verify the operation of transparent bridging. Test number BRI-TRA-1 BRI-TRA-2 BRI-TRA-3 BRI-TRA-4 BRI-TRA-5 BRI-TRA-6 BRI-TRA-7 BRI-TRA-8 Test description Verify that MAC addresses are learned from the source MAC addresses received by the bridge. Verify that all broadcasts, multicast and unicasts not in the bridge table are forwarded by the bridge. Verify that transparent bridging works across DDR. Verify that transparent bridging works across Frame Relay. Verify that transparent bridging works across X.25 Verify that transparent bridging works across LAPB Verify that transparent bridging works across 802.1Q Verify that transparent bridging works across PPP Results Passed Passed Passed Passed Passed Passed Passed Passed

BRI-TRA-9 BRI-TRA-10

Verify that transparent bridging works across HDLC Set and verify filters at the MAC layer.
8.6.4.2 Spanning Tree Protocol (STP) Objective: Verify the operation of the spanning tree protocol. Test number BRI-STP-1 BRI-STP-2 Test description Verify the initial STP build process. Verify that the CBPDU (Configuration Bridge Protocol Data Units) contains the relevant information. This information should be; Root Bridges bridge ID, an administratively set priority, the cost and the bridge ID of the sender of the CBPDU. Verify that the selection of the root bridge has been completed. Once this has been completed the CBPDUs that are sent out of the bridges should contain the MAC address of the root bridge, ID and the cost from the root bridge. Verify that the non-root ports are set to either forwarding or blocking. Verify that update notices are sent correctly and contain the relevant fields. Relevant fields are: bridge ID, priority, cost and the root bridge ID. The CBPDU created by the root also contain some timers; Hello time, MaxAge, Forward Delay. Verify that if a bridge whose MaxAge parameter expires is also not receiving any CBPDUs on ports that are not the root port, that bridge reacts by claiming to be the root bridge and begins sending CBPDUs describing itself. Verify that the bridge whose interface is set to blocking, changes to forwarding due to the lack of CBPDUs. Verify that the following STP parameters can be adjusted and that the process still works correctly; bridge priority, path costs and CBPDU intervals. Results Passed Passed

2FXS 732510 - 1

4FXS 732530 - 3

R3680 R1760

Catalyst 1900
Frame Relay 4FXS 732520 - 2

FXO (01473) 621625 PSTN

E1 (01473) 732500-99

FXO (01473) 621392

621625

IP (01473 ) 620109

Ext. 1000
CallManger & IP Phones
Figure 24: Packet Voice Network Topology 9.1.3 Results Summary All three routers under test worked well as IP Voice routers, both over a captive Ethernet and Frame Relay network, and the additional phone features performed as expected. The voice quality sounded good and delay did not appear any more noticeable than is expected over an IP Telephony networks. No measurements were taken for voice quality these were perceived voice quality only. From a UK users perspective the tone generation needs to be addressed as ring tone was not as expected for the UK market, though Huawei do support busy tone detect feature for the FXO interfaces. Fax transmission over the IP network was successfully demonstrated without any noticeable degradation of picture quality beyond that expected from a normal Fax transmission. IP Precedence may be configured in the dial-peer to set the priority level written in the layer 3 Type of Service field. The default value is 0 but can be set to any value between 0 and 7 although 5 is usual for IP Voice packets. Results Summary Table Total Pass Fail -
9.1.4.1 Router Configuration Objective: To configure the routers to operate with the other routers on the captive network as an FXS/FXO interface, IP interface for VoIP signalling and E1 interface. Test number VoIP_SET_1 VoIP_SET_2 VoIP_SET_3 VoIP_SET_4 VoIP_SET_5 Test description Configure Dial-Peers Set IP Precedence to 5 Configure Dial Terminator Configure Abbreviated Dialling Configure Voice Port Configure Global Number Match policy Result Passed Passed Passed Passed Passed
9.1.4.2 Basic Call Objective: To confirm basic call set-up, voice transmission and call clear down on a number of routes. Test number VoIP_CALL_1 VoIP_CALL_2 VoIP_CALL_3 VoIP_CALL_4 VoIP_CALL_5 VoIP_CALL_6 VoIP_CALL_7 VoIP_CALL_8 VoIP_CALL_9 VoIP_CALL_10 VoIP_CALL_11 VoIP_CALL_12 VoIP_CALL_13 VoIP_CALL_14 Test description Calls established from analogue phone (FXS port) to another analogue phone (FXS port) on same router Calls established from analogue phone (FXS port) to another analogue phone (FXS port) on other routers Calls received at analogue phone (FXS port) established from another analogue phone (FXS port) on other routers Calls established from analogue phone (FXS port) to PSTN via own FXO port Calls received at analogue phone (FXS port) established from PSTN via own FXO port Calls established from analogue phone (FXS port) to PSTN via FXO ports on other routers Calls received at analogue phone (FXS port) established from PSTN via FXO ports on other routers Calls established from analogue phone (FXS port) to digital phone extension via own E1 port Calls received at analogue phone (FXS port) established from digital phone extension via own E1 port Calls established from analogue phone (FXS port) to digital phone extension via E1 ports on other routers Calls received at analogue phone (FXS port) established from digital phone extension via E1 ports on other routers Calls established from analogue phone (FXS port) to IP phone on AVVID network Calls received at analogue phone (FXS port) established from IP phone on AVVID network Call busy received when call placed to phone already in use. Result Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed

Passed Passed Passed Passed Passed Passed Passed
include details of neighbour changes, changes to forwarding state, expired timers plus information on periodic updates.
11 Interface Standards Conformance
During the test period all supported interfaces were evaluated on the Huawei routers. Absolute conformance testing was not performed, but a through investigation of these interfaces was undertaken. 11.1 Ethernet, Fast Ethernet, Serial, E1, cE1, Voice E1VI, FXO, FXS & ISDN BRI Note that only Ethernet, BRI and Serial interfaces are supported on the 1600 series 11.1.1 Key Test Items The following functionality of the interfaces has been configured and tested: Ethernet/Fast Ethernet verify configuration and operation of Ethernet/Fast Ethernet. Serial verify configuration and operation of Serial interfaces. E1/cE1 verify configuration and operation if E1/cE1 interfaces. Voice E1VI verify configuration and operation of E1VI interfaces. FXO & FXS verify configuration and operation of FXS & FXS interfaces. ISDN BRI verify configuration and operation of ISDN BRI interfaces. Interoperability verify that the interfaces interoperate with Cisco equipment.
11.1.2 Network Topology All supported interfaces were configured during the testing in various configurations and hence there is no network topology diagram. 11.1.3 Results Summary Throughout the test period the different type of interfaces available on the Huawei routers were tested. All interfaces passed the majority of tests and are considered compliant for data/voice networks, the only problems noted were: Ring tone was not as expected for the UK market
Results Summary Table Total Pass Fail 11.1.4 Detailed Results
11.1.4.and 100 Ethernet Objective: Configure and verify 10/100 Ethernet interfaces. Test number INT_ETH_1 INT_ETH_2 INT_ETH_3 INT_ETH_4 INT_ETH_5 Test description Configure a loopback interface. Specify an Ethernet or a Fast Ethernet interface. Specify the Ethernet encapsulation method. Adjust the maximum packet size transmission unit (MTU) size. Configure the operating mode on an interface using speed & duplex commands. Results Passed Passed Passed Passed Passed
11.1.4.2 Serial Objective: Configure and verify serial interface. Test number Test description Results

Performance\Quidway 2620\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2620\100mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2621\10mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2621\10mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2621\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2621\100mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2630\10mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2630\10mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2630\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2630\100mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2631\10mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2631\10mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 2631\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 2631\100mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 3640\10mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 3640\10mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 3640\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 3640\100mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 3680\10mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 3680\10mb Full Duplex\Latency\Latency_Detail.csv Performance\Quidway 3680\100mb Half Duplex\Latency\Latency_Detail.csv Performance\Quidway 3680\100mb Full Duplex\Latency\Latency_Detail.csv

13 Monitoring/Debugging

During the test period this section evaluated the routers ability to report information regarding monitoring and debugging features. In addition to this the routers were connected to an HP OpenView workstation to evaluate the routers ability to integrate into an existing Network Management system. 13.1 MIB review, SNMP, RMON & SYSLOG Note that the 1603 only supports SNMPv1. 13.1.1 Key Test Items The following functionality has been configured and tested.

13.1.2

Private MIB support evaluate support of private MIBs. SNMP verify support for SNMP v1, v2 & v3. RMON verify support for RMON. SYSLOG verify configuration and operation of syslog with syslog server. Interoperability verify that monitoring and debugging functionality interoperates with HP OpenView. Network Topology

15.1.4

15.1.4.1 Configuration Objective: Evaluate configuration tasks. Test number CONF_1 CONF_2 CONF_3 CONF_4 CONF_5 CONF_6 CONF_7 CONF_8 CONF_9 CONF_10 CONF_11 CONF_12 Test description Configure router using console port Configure router using telnet port (not available on 1600 series) Configure router using reverse telnet Configure router using direct setup Upgrade router image using tftp (not available on 1600 series) Upgrade router image using ftp Download configuration to terminal Upgrade router image using ftp/tftp client Upload/download router configuration to ftp/tftp server Test ping command Test tracert command Check return to unprivileged user mode when time out Results Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Passed Default 10 Min
15.1.4.2 Authentication Objective: evaluate password handling. Test number Test description Results Passed Passed
CONF_PASS_1 Check passwords can be encrypted CONF_PASS_2 Check password authentication methods

16 Conclusion

The conclusion of the tests conducted on the Huawei routers is that the Quidway IP router series performed extremely well on the wide variety of different tests they were submitted to. In fact a total of six hundred and seventy eighty (678) tests were performed on each router, and in total only four (4) failed (i.e. 99% pass rate). The main points from the test results are as follows: Support for both IP and IPX protocols. Support for a wide range of routing protocols (OSPF, BGP). Wide range of data interfaces supported. Integrated support for voice interfaces and voice over IP. Ease of management Inter-working with Cisco equipment

17 Appendix

17.1 Supported RFC and Private MIBs for the Huawei Quidway Series Routers: Module Name MIB II SNMP MIB File RFC1213.MIB gentrap.mib Framework.mib Mpd.mib Notofication.mib Target.mib Usm.mib Vacm.mib M8040.mib Mixinfo.mib Rmon.mib Performance.mib Hw_ip.mib Hw_icmp.mib Ppp.mib Eth.mib Fr.mib Lapb.mib X25.mib Qos.mib Ospf.mib Rip.mib Bgp.mib Ndec.mib Dlsw.mib Terminal.mib Table 2: Supported MIBs RFC RFC1213 RFC1907 RFC2271 RFC2272 RFC2273 RFC2273 RFC2274 RFC2275 private private RFC1757 private private private RFC1472,RFC1473,RFC1474, RFC1661,RFC1332,RFC1334 RFC1643 RFC1315,RFC2115 RFC1381 RFC1382 private RFC1253 RFC1389 RFC1657 private RFC2024,private private
Device RMON Extention for RMON Extention for IP Extention for ICMP PPP Ethernet FR LAPB X.25 QoS OSPF RIP BGP NDec DLSw Terminal Server
17.2 PPP Performance Results All results are for 20% utilisation, 30 second duration. IP Protocol, 1024 byte length frame, 10M Ethernet 2M serial 10M Ethernet. 3600 -> 2600 Bytes Out (3600) Without compression With compression 2600 -> 3600 Without compression With compression 1760 -> 3600 Without compression With compression Bytes Out (1760) Bytes In (3600) Table 3: PPP Compression Results 17.3 Router and test equipment software versions CPU Usage (1760) 9% 50% CPU Usage (3600) 3% 4% Bytes Out (2600) Bytes In (3600) CPU Usage (2600) 8% 48% CPU Usage (3600) 3% 4% Bytes In (2600) CPU Usage (3600) 4% 27% CPU Usage (2600) 9% 17%

Spirent Smartbits

SmartFlow Version 1.30.020 Controller SMB-2000, Firmware Revision 6.Cards SmartMetrices 10/100Mb Ethernet TP (ML-7710), Firmware Revision 2.20.011 SmartWindow Version 7.30.24 Controller SMB-6000B, Firmware Revision 1.20.004.00 Module 2 Port 1000Mb GBIC Terametrics, Version 1.06.030, Linux RAM size 256Mb
17.4 List of tables Table 1: Throughput Results Summary Table 2: Supported MIBs
Table 3: PPP Compression Results
17.5 List of figures Figure 1: OSPF Network Topology... 8 Figure 3: BGP Network Topology.... 13 Figure 4: BGP Route Reflector Network Topology.. 14 Figure 5: RIP Network Topology.... 19 Figure 6: IPX RIP Network Topology... 22 Figure 7: Static Route Network Topology... 23 Figure 8: GRE Network Topology... 25 Figure 9: L2TP Network Topology... 27 Figure 10: QoS Test Topology... 29 Figure 11: Access Lists Test Topology... 33 Figure 12: AAA Test Topology.... 35 Figure 13: IPSec/IKE Test Topology.... 38 Figure 14: NAT Network Topology.... 40 Figure 15: Network Layer Test Topology.... 42 Figure 16: IPX Network Topology... 45 Figure 17: DHCP Relay Network Topology... 47 Figure 18: DHCP Server Network Topology.... 48 Figure 19: Frame Relay Test Topology... 51 Figure 20: X25 Test Topology.... 54 Figure 21: PPP Test Topology... 57 Figure 22: HDLC Test Topology... 59 Figure 23: DDR Test Topology... 61 Figure 24: Bridging Network Topology... 64 Figure 25: Packet Voice Network Topology... 67 Figure 26: Multicast Test Topology... 70 Figure 27: Interface Performance Test Topology... 76 Figure 28: Router Series Throughput at 100Mb/s Full Duplex.. 77 Figure 29: Quidway Router Series Latency at 100Mb/s Full Duplex.. 78 Figure 31: Monitoring & Debugging Network Topology.. 81 Figure 32: General Handling Network Topology... 84 17.6 AAA ACL AS BGP CAR CLI DDR DHCP EBGP FIFO GRE HDLC IGMP IKE IP L2TP LAC LNS Acronyms Authentication, Authorisation And Accounting Access Control List Autonomous System Border Gateway Protocol Committed Access Rate Command Line Interface Dial-on-Demand Routing Dynamic Host Configuration Protocol Exterior Border Gateway Protocol First In First Out Generic Routing Encapsulation High-level Data-Link Control Interior Group Management Protocol Internet Key Exchange Internet Protocol Layer 2 Tunnelling Protocol L2TP Access Concentrator L2TP Network Server