Details of Logo 02-C-001767

TOP > 02-C-001767

CN-2-C-20180619-000521

Management   Application Form   Extended Test Categories
Logo ID 02-C-001767
Approved Date 2018/09/12
Application ID CN-2-C-20180619-000521
Applied Date 2018/06/19
Usage Agreement Agreed
OEM Licensor's Logo ID -
Note -
Management   Application Form   Extended Test Categories
Target Information Application Phase Phase-2
Test Category Core Protocols
Vendor Name New H3C Techonlogies Co., Ltd
Country CN
Product Name S6520 series(S6520XE-54QC-HI,S6520X-30QC-EI,S6520X-54QC-EI,S6520X-30QC-HI,S6520X-54QC-HI,S6520X-30HC-EI,S6520X-54HC-EI,S6520X-30HC-HI,S6520X-54HC-HI,S6520-16S-SI,S6520-24S-SI,S6520X-18C-SI,S6520X-26C-SI,S6520X-16ST-SI,S6520X-26ST-SI,S6520X-26MC-SI,S6520X-26MC-UPWR-SI)
Product Version Comware V7.1
Product Classification Router
Product Description S6520 series switch provides ultra large switching capacity, high density 10GE/40GE wire speed forwarding port, dual plug in power supply, and has rich three layer characteristics. The H3C S6520 series is located in the next generation core / converged high density Gigabit switch. It includes the following 17 kinds of deliveries: S6520XE-54QC-HI,S6520X-30QC-EI,S6520X-54QC-EI,S6520X-30QC-HI,S6520X-54QC-HI,S6520X-30HC-EI,S6520X-54HC-EI,S6520X-30HC-HI,S6520X-54HC-HI,S6520-16S-SI,S6520-24S-SI,S6520X-18C-SI,S6520X-26C-SI,S6520X-16ST-SI,S6520X-26ST-SI,S6520X-26MC-SI,S6520X-26MC-UPWR-SI.Their difference lies in the number and type of physical ports.
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
Management   Application Form   Extended Test Categories
Interoperable
Devices		 Router
1 Vendor Name FreeBSD
Device Name FreeBSD
Version 7.0-Release
2 Vendor Name OpenBSD
Device Name OpenBSD
Version 4.3 Generic#698 i386
Host
1 Vendor Name NetBSD
Device Name NetBSD
Version 4.0.1-Release
2 Vendor Name Fedora9
Device Name Fedora9
Version 2.6.25-14.fc9.i686
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)