Attestations_20190613_v1 - Attestation (DFS Master Declaration) rev

FCC ID: Q9DAPEX0387

Attestation Statements

Download: PDF
FCCID_4317323

DFS device channel plan and software operational declaration Date: 2019-06-11 We, Hewlett Packard Enterprise Company, declare that the device, FCC ID: Q9DAPEX0387 Model Name: APEX0387, does not have Ad Hoc on “non-US frequencies” and/or on“ DFS frequencies“. Also, the client software and associated drivers will not initiate any transmission on DFS frequencies without initiation by a master. This includes restriction on transmissions for beacons and support for ad-hoc peer-to-peer modes. Below is the channel / frequency plan for the device: 5G band 1 CH 36 38 40 42 44 46 48 Frequency (MHz) 5180 5190 5200 5210 5220 5230 5240 Scan Type Active Active Active Active Active Active Active 5G band 2 CH 52 54 56 58 60 62 64 Frequency (MHz) 5260 5270 5280 5290 5300 5310 5320 Active Active Active Active Active Active Active Scan Type Passive Passive Passive Passive Passive Passive Passive 5G band 3 CH 100 102 104 106 108 110 112 116 118 120 122 Frequency (MHz) 5500 5510 5520 5530 5540 5550 5560 5580 5590 5600 5610 Active Active Active Active Active Active Active Active Active Active Active Scan Type Passive Passive Passive Passive Passive Passive Passive Passive Passive Passive Passive CH 124 126 128 132 134 136 138 140 142 144 Frequency (MHz) 5620 5630 5640 5660 5670 5680 5690 5700 5710 5720 Active Active Active Active Active Active Active Active Active Active Scan Type Passive Passive Passive Passive Passive Passive Passive Passive Passive Passive 5G band 4 CH 149 151 153 155 157 159 161 165 Frequency (MHz) 5745 5755 5765 5775 5785 5795 5805 5825 Scan Type Active Active Active Active Active Active Active Active Also, on DFS channels, the WLAN driver in the device operates under the control of an AP at all times, except when in ad-hoc mode on US non-DFS channels. The device passively scans DFS frequencies until a master device is detected. The control of this functionality is not accessible to anyone under any conditions. Furthermore, the firmware is protected by a special signature and CRC checksum. Signature and CRC checksum will be calculated and verified before firmware upgrade. Unauthorized modification to firmware will lead to the failure of verification and thus firmware upgrade will not be allowed. Sincerely yours, ----------------------------------------------- Robert Hastings / Compliance Manager Tel: 6502369611 Fax: 4802274550 E-mail: rob.hastings@hpe.com


Document Created: 0400-06-21 00:00:00
Document Modified: 0400-06-21 00:00:00
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC