Details of Logo 02-C-001849

TOP > 02-C-001849

CN-2-C-20180820-000557

Logo ID 02-C-001849
Approved Date 2019/02/08
Application ID CN-2-C-20180820-000557
Applied Date 2018/08/20
Usage Agreement Agreed
OEM Licensor's Logo ID -
Note -
Target Information Application Phase Phase-2
Test Category Core Protocols
Vendor Name New H3C Techonlogies Co., Ltd
Country CN
Product Name SR8800-X Series(SR8804-X, SR8808-X, SR8808H-X, SR8812-X, SR8816-X)
Product Version Comware V7.1
Product Classification Router
Product Description H3C SR8800-X Series Core Routers
Vendor's Note
    Note 1:
##About ROUTER.NetBSD and HOST.OpenBSD##
When NetBSD or OpenBSD act as the target, and receive ICMPv6 Echo Requests with 1500 bytes,
they response and fragment ICMPv6 Echo Replies within MTU 1280 bytes.

Note 2:
##About 1.6.A.OpenBSD##
For the reason mentioned in Note 1, we exchange the direction of ping in 1.6.A.OpenBSD.
That is ping from OpenBSD(TAR-Host1) to REF-Host2(FreeBSD). We use the command "ping6 -mm" to force OpenBSD sending ICMPv6 Echo Requests without fragmenting.

Note 3:
##About 1.6.B.NetBSD##
We exchange the direction of ping in 1.6.B.NetBSD step 13.That is ping from NetBSD(TAR-Router2) to REF-Host1. We use the command "ping6 -mm" to force NetBSD sending ICMPv6 Echo Requests without fragmenting.

Note 4:
##About 1.6.D.OpenBSD##
We exchange the order of ping in 1.6.D.OpenBSD. That is first ping from OpenBSD(TAR-Host1) to our device(TAR-Router1),then ping from our device to OpenBSD,in this way we can observe the Packet Too Big message for our device and for OpenBSD. We use the command "ping6 -mm" to force OpenBSD sending ICMPv6 Echo Requests without fragmenting.
Test Information Test Specification 4.0.7
Interoperability Test Scneario 4.0.4
Information for Series of Product
These products have the same software and hardware architecture but different capacity.
1. Compliance with the same standards, such as RFCs, IETF etc.
2. Same location in the telecommunication network.
3. Same system architecture and modules:
a) Same distribute forwarding architecture: The main control board is responsible for routing protocol and device management, and the three-layer packet forwarding is performed on each interface board.
b) Same HA mechanism: Each product has two main control boards which providing NSR and NSF feature.
d) Same packet forwarding mechanism that uses the longest prefix matching mode for packet forwarding to provide stable forwarding performance.
e) Same features based on the Comware software platform that provides support for routing protocols, MSTP, VLAN aggregation, port aggregation, QoS priority queue, MPLS VPN etc.
f) Same network management powered by H3C.
4. The number of interface modules supported by each product is shown as follows:
SR8804-X has four interface boards,
SR8808-X has eight interface boards,
SR8808H-X has eight interface boards,
SR8812-X has twelve interface boards,
SR8816-X has sixteen interface boards.
Interoperable
Devices
Router
1 Vendor Name FreeBSD
Device Name FreeBSD
Version 7.0-Release
2 Vendor Name NetBSD
Device Name NetBSD
Version 4.0.1-Release
Host
1 Vendor Name Fedora9
Device Name Fedora9
Version 2.6.25-14.fc9.i686
2 Vendor Name OpenBSD
Device Name OpenBSD
Version 4.3 Generic#698 i386
Target supporting
Advanced Functions:
o Transmitting Echo Requests and configuring packet size
o Multicast Routing
o MTU Configuration
o Multiple physical network interfaces