Details of Logo 02-C-001868

TOP > 02-C-001868

CN-2-C-20180816-000552

Management   Application Form   Extended Test Categories
Logo ID 02-C-001868
Approved Date 2019/03/11
Application ID CN-2-C-20180816-000552
Applied Date 2018/08/16
Usage Agreement Agreed
OEM Licensor's Logo ID -
Note -
Management   Application Form   Extended Test Categories
Target Information
Test Category Core Protocols
Vendor Name New H3C Techonlogies Co., Ltd
Country CN
Product Name CR16000-F Series(CR16006-F,CR16010-F,CR16010H-F,CR16014-F,CR16018-F)
Product Version Comware V7.1
Product Classification Router
Product Description H3C CR16000-F Series Core Router
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, only the switch capacity is different:
1. These products follow the same standards: such as RFCs, IETF etc.
2. The location in the telecommunication network are the same.
3. The system architecture and module are the same:
a)The same distribute forwarding architecture: the main control board are responsible for routing protocol and device management, the three layer packet forwarding is completed on each interface board.
b)The same HA mechanism, there product have two main control boards which providing NSR, NSF feature.
d)The same packet forwarding mechanism, using the longest prefix matching mode by packet forwarding, can provide stable forwarding performance in network environment.
e)The same features are based on Comware software platform providing routing protocol, MSTP, VLAN aggregation, port aggregation, QoS priority queue, MPLS VPN etc.
f)The same network management features can be managed by H3C network management.

4.These product have different port density for different interface boards:
CR16006-F have 4 interface boards,
CR16010-F have 8 interface boards,
CR16010H-F have 8 interface boards,
CR16014-F have 12 interface boards,
CR16018-F have 16 interface boards.
Management   Application Form   Extended Test Categories
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(Passive Node)
- Configuring Multicast Packet Size
o Multicast Routing(Router Only)
- RFC 4191 Type C Host(Host Only)
- Duplicate Overlapping Fragments
- Beyond Scope of Source Address(Router Only)
- Tracking Connections for ICMPv6
- Router Advertisement DNS (Host Only)