# FD.io CSIT Testbed Specifications 1. [Purpose](#purpose) 1. [Testbeds Overview](#testbeds-overview) 1. [Summary List](#summary-list) 1. [1-Node-Skylake Xeon Intel (1n-skx)](#1-node-skylake-xeon-intel-1n-skx) 1. [1-Node-ThunderX2 Arm Marvell (1n-tx2)](#1-node-thunderx2-arm-marvell-1n-tx2) 1. [1-Node-Cascadelake Xeon Intel (1n-clx)](#1-node-cascadelake-xeon-intel-1n-clx) 1. [2-Node-Skylake Xeon Intel (2n-skx)](#2-node-skylake-xeon-intel-2n-skx) 1. [2-Node-Denverton Atom Intel (2n-dnv)](#2-node-denverton-atom-intel-2n-dnv) 1. [2-Node-IxiaPS1L47 Ixia PSOne L47 (2n-ps1)](#2-node-ixiaps1l47-ixia-psone-l47-2n-ps1) 1. [2-Node-Cascadelake Xeon Intel (2n-clx)](#2-node-cascadelake-xeon-intel-2n-clx) 1. [3-Node-Haswell Xeon Intel (3n-skx)](#3-node-haswell-xeon-intel-3n-skx) 1. [3-Node-Skylake Xeon Intel (3n-skx)](#3-node-skylake-xeon-intel-3n-skx) 1. [3-Node-TaiShan Arm Huawei (3n-tsh)](#3-node-taishan-arm-huawei-3n-tsh) 1. [3-Node-MACCHIATObin Arm Marvell](#3-node-macchiatobin-arm-marvell) 1. [3-Node-Rangeley Atom Testbeds](#3-node-rangeley-atom-testbeds) 1. [Server Management](#server-management) 1. [Requirements](#requirements) 1. [Addressing](#addressing) 1. [LOM (IPMI) VLAN IP Addresses](#lom-ipmi-vlan-ip-addresses) 1. [Management VLAN IP Addresses](#management-vlan-ip-addresses) 1. [Server Specifications](#server-specifications) 1. [Server Types](#server-types) 1. [Naming Convention](#naming-convention) 1. [Testbeds Configuration](#testbeds-configuration) 1. [Per Testbed Server Allocation and Naming](#per-testbed-server-allocation-and-naming) 1. [1-Node-Skylake Servers (1n-skx) PROD](#1-node-skylake-servers-1n-skx-prod) 1. [1-Node-Thunderx2 Servers (1n-tx2) WIP](#1-node-thunderx2-servers-1n-tx2-wip) 1. [1-Node-Cascadelake Servers (1n-clx) SETUP](#1-node-cascadelake-servers-1n-clx-setup) 1. [2-Node-Skylake Servers (2n-skx) PROD](#2-node-skylake-servers-2n-skx-prod) 1. [2-Node-Denverton Servers (2n-dnv) TODO](#2-node-denverton-servers-2n-dnv-todo) 1. [2-Node-IxiaPS1L47 Servers (2n-ps1) VERIFY](#2-node-ixiaps1l47-servers-2n-ps1-verify) 1. [2-Node-Cascadelake Servers (2n-clx) SETUP](#2-node-cascadelake-servers-2n-clx-setup) 1. [3-Node-Haswell Servers (3n-hsw) PROD](#3-node-haswell-servers-3n-hsw-prod) 1. [3-Node-Skylake Servers (3n-skx) PROD](#3-node-skylake-servers-3n-skx-prod) 1. [3-Node-Rangeley Servers (3n-rng) VERIFY](#3-node-rangeley-servers-3n-rng-verify) 1. [3-Node-Taishan Servers (3n-tsh) WIP](#3-node-taishan-servers-3n-tsh-wip) 1. [3-Node-Mcbin Servers (3n-mcb) TODO](#3-node-mcbin-servers-3n-mcb-todo) 1. [Per Testbed Wiring](#per-testbed-wiring) 1. [1-Node-Skylake Wiring (1n-skx) PROD](#1-node-skylake-wiring-1n-skx-prod) 1. [1-Node-Thunderx2 Wiring (1n-tx2) WIP](#1-node-thunderx2-wiring-1n-tx2-wip) 1. [1-Node-Cascadelake Wiring (1n-clx) SETUP](#1-node-cascadelake-wiring-1n-clx-setup) 1. [2-Node-Skylake Wiring (2n-skx) PROD](#2-node-skylake-wiring-2n-skx-prod) 1. [2-Node-Denverton Wiring (2n-dnv) TODO](#2-node-denverton-wiring-2n-dnv-todo) 1. [2-Node-IxiaPS1L47 Wiring (2n-ps1) VERIFY](#2-node-ixiaps1l47-wiring-2n-ps1-verify) 1. [2-Node-Cascadelake Wiring (2n-clx) SETUP](#2-node-cascadelake-wiring-2n-clx-setup) 1. [3-Node-Haswell Wiring (3n-hsw) PROD](#3-node-haswell-wiring-3n-hsw-prod) 1. [3-Node-Skylake Wiring (3n-skx) PROD](#3-node-skylake-wiring-3n-skx-prod) 1. [3-Node-Rangeley Wiring (3n-rng) TODO](#3-node-rangeley-wiring-3n-rng-todo) 1. [3-Node-Taishan Wiring (3n-tsh) WIP](#3-node-taishan-wiring-3n-tsh-wip) 1. [3-Node-Mcbin Wiring (3n-mcb) WIP](#3-node-mcbin-wiring-3n-mcb-wip) 1. [Inventory](#inventory) 1. [Appliances](#appliances) 1. [Arm Servers](#arm-servers) 1. [Xeon and Atom Servers](#xeon-and-atom-servers) 1. [Network Interface Cards](#network-interface-cards) 1. [Pluggables and Cables](#pluggables-and-cables) 1. [Other Parts](#other-parts) ## Purpose This note includes specification of the physical testbed infrastructure hosted by LFN FD.io CSIT project. ## Testbeds Overview ### Summary List ``` #. CSIT_tb Purpose SUT TG #TB #SUT #TG #hsw #skx #ps1 #rng #dnv #tx2 #tsh #mcb 1. 1-Node-VIRL dev hsw --- 3 3 0 3 0 0 0 0 0 0 0 2. 1-Node-Skylake dev skx na 2 2 0 0 2 0 0 0 0 0 0 3. 1-Node-Thunderx2 dev tx2 na 1 1 0 0 0 0 0 0 1 0 0 4. 1-Node-Cascadelake dev clx lcx 1 1 0 0 0 0 0 0 0 0 0 5. 2-Node-Skylake perf skx skx 4 4 4 0 8 0 0 0 0 0 0 6. 2-Node-Denverton perf dnv skx 1 1 1 0 .5 0 0 1 0 0 0 7. 2-Node-IxiaPS1L47 tcp skx ps1 1 1 1 0 1 1 0 0 0 0 0 8. 2-Node-Cascadelake perf clx clx 3 3 3 0 0 0 0 0 0 0 0 9. 3-Node-Haswell perf hsw hsw 3 6 3 9 0 0 0 0 0 0 0 10. 3-Node-Skylake perf skx skx 2 4 2 0 6 0 0 0 0 0 0 11. 3-Node-Rangeley perf rng skx 1 3 1 0 0 0 2 0 0 0 0 12. 3-Node-Taishan perf tsh skx 1 2 1 0 .5 0 0 0 0 2 0 13. 3-Node-Mcbin perf mcb skx 1 2 1 0 .5 0 0 0 0 0 2 14. 3-Node-Denverton perf dnv skx 1 2 1 0 .5 0 0 2 0 0 0 Totals: 22 35 18 12 19 1 2 3 1 2 2 ``` ### 1-Node-Skylake Xeon Intel (1n-skx) Each 1-Node-Skylake testbed includes one SUT (Server-Type-B6) with NIC ports connected back-to-back ([Server Types](#server-types)). Used for FD.io VPP_Device functional driver tests. ### 1-Node-ThunderX2 Arm Marvell (1n-tx2) Each 1-Node-ThunderX2 testbed includes one SUT (Server-Type-B9) with NIC ports connected back-to-back ([Server Types](#server-types)). Used for FD.io VPP_Device functional driver tests. ### 1-Node-Cascadelake Xeon Intel (1n-clx) Each 1-Node-Cascadelake testbed includes one SUT (Server-Type-C1) with NIC ports connected back-to-back ([Server Types](#server-types)). Used for FD.io VPP_Device functional driver tests. ### 2-Node-Skylake Xeon Intel (2n-skx) Each 2-Node-Skylake testbed includes one SUT (Server-Type-B1) and one TG (Server-Type-B2) connected in a 2-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 2-Node-Denverton Atom Intel (2n-dnv) Each 2-Node-Skylake testbed includes one SUT (Server-Type-B10) and one TG (Server-Type-B2) connected in a 2-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 2-Node-IxiaPS1L47 Ixia PSOne L47 (2n-ps1) Each 2-Node-IxiaPS1L47 testbed includes one SUT (Server-Type-B1) and one TG (Ixia PSOne appliance) with 10GE interfaces connected in a 2-node circular topology ([Server Types](#server-types)). Used for FD.io TCP/IP and HTTP performance tests. ### 2-Node-Cascadelake Xeon Intel (2n-clx) Each 2-Node-Cascadelake testbed includes one SUT (Server-Type-C2) and one TG (Server-Type-C3) connected in a 2-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 3-Node-Haswell Xeon Intel (3n-hsw) Each 3-Node-Haswell testbed includes two SUTs (Server-Type-A1) and one TG (Server-Type-A2) connected in a 3-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 3-Node-Skylake Xeon Intel (3n-skx) Each 3-Node-Skylake testbed includes two SUTs (Server-Type-B1) and one TG (Server-Type-B2) connected in a 3-node circular topology. Used for FD.io performance tests. ### 3-Node-TaiShan Arm Huawei (3n-tsh) Each 3-Node-TaiShan testbed includes two SUTs (Server-Type-B3) and one TG (Server-Type-B2) connected in a 3-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 3-Node-MACCHIATObin Arm Marvell Each 3-Node-MACCHIATObin testbed includes two SUTs (Server-Type-B4) and one TG (Server-Type-B2) connected in a 3-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ### 3-Node-Rangeley Atom Testbeds Each 3-Node-Rangeley testbed includes two SUTs (Server-Type-B5) and one TG (Server-Type-2) connected in a 3-node circular topology ([Server Types](#server-types)). Used for FD.io performance tests. ## Server Management ### Requirements For management purposes, each server must have following two ports connected to the management network: ``` - 1GE IPMI port - IPMI - Intelligent Platform Management Interface. - Required for access to embedded server management with WebUI, CLI, SNMPv3, IPMIv2.0, for firmware (BIOS) and OS updates. - 1GE/10GE/40GE management port - hostOS management port for general system management. ``` ### Addressing Each server has a LOM (Lights-Out-Management e.g. SM IPMI) and a Management port, which are connected to two different VLANs. ``` 1. LOM (IPMI) VLAN: - Subnet: 10.30.50.0/24 - Gateway: 10.30.50.1 - Broadcast: 10.30.50.255 - DNS1: 199.204.44.24 - DNS2: 199.204.47.54 2. Management Vlan: - Subnet: 10.30.51.0/24 - Gateway: 10.30.51.1 - Broadcast: 10.30.51.255 - DNS1: 199.204.44.24 - DNS2: 199.204.47.54 ``` To access these hosts, VPN connection is required. ### LOM (IPMI) VLAN IP Addresses Name | Comment ------------ | ------- 10.30.50.0 | network 10.30.51.1 | Router 10.30.50.2 | LF Reserved 10.30.50.3 | LF Reserved 10.30.50.4 | LF Reserved 10.30.50.5 | LF Reserved 10.30.50.6 | LF Reserved 10.30.50.7 | LF Reserved 10.30.50.8 | LF Reserved 10.30.50.9 | LF Reserved 10.30.50.10 | LF Reserved 10.30.50.11 | LF Reserved 10.30.50.12 | LF Reserved 10.30.50.13 | LF Reserved 10.30.50.14 | LF Reserved 10.30.50.15 | LF Reserved 10.30.50.16 | t1-tg1 10.30.50.17 | t1-sut1 10.30.50.18 | t1-sut2 10.30.50.20 | t2-tg1 10.30.50.21 | t2-sut1 10.30.50.22 | t2-sut2 10.30.50.24 | t3-tg1 10.30.50.25 | t3-sut1 10.30.50.26 | t3-sut-2 10.30.50.28 | t4-sut1 10.30.50.29 | t4-sut2 10.30.50.30 | t4-sut3 10.30.50.36 | s17-t33-sut1 10.30.50.37 | s18-t33-sut2 10.30.50.41 | s3-t21-sut1 10.30.50.42 | s4-t21-tg1 10.30.50.43 | s11-t31-sut1 10.30.50.44 | s12-t31-sut2 10.30.50.45 | s13-t31-tg1 10.30.50.46 | s19-t33t34-tg1 10.30.50.47 | s1-t11-sut1 10.30.50.48 | s2-t12-sut1 10.30.50.49 | s5-t22-sut1 10.30.50.50 | s6-t22-tg1 10.30.50.51 | s7-t23-sut1 10.30.50.52 | s8-t23-tg1 10.30.50.53 | s9-t24-sut1 10.30.50.54 | s10-t24-tg1 10.30.50.55 | s14-t32-sut1 10.30.50.56 | s15-t32-sut2 10.30.50.57 | s16-t32-tg1 10.30.50.58 | s25-t25-sut1 10.30.50.59 | s26-t25-tg1 10.30.50.69 | s27-t13-sut n/a | s20-t34-sut1 n/a | s21-t34-sut2 10.30.51.29 | s22-t35-sut1 screen -r /dev/ttyUSB0 10.30.51.30 | s23-t35-sut2 screen -r /dev/ttyUSB1 10.30.51.30 | s24-t35-sut3 screen -r /dev/ttyUSB2 10.30.55.10 | s28-t26t35-tg1 10.30.55.11 | s29-t26-sut1 10.30.55.12 | s30-t35-sut1 10.30.55.13 | s31-t35-sut2 10.30.50.255 | Broadcast 10.30.55.17 | s32-t14-sut1 10.30.55.18 | s33-t27-sut1 10.30.55.19 | s34-t27-tg1 10.30.55.20 | s35-t28-sut1 10.30.55.21 | s36-t28-tg1 10.30.55.22 | s37-t29-sut1 10.30.55.23 | s38-t29-tg1 ### Management VLAN IP Addresses Name | Comment ------------------------- | ------- 10.30.51.0 | network 10.30.51.1 | Router 10.30.51.2 | LF Reserved 10.30.51.3 | LF Reserved 10.30.51.4 | LF Reserved 10.30.51.5 | LF Reserved 10.30.51.6 | LF Reserved 10.30.51.7 | LF Reserved 10.30.51.8 | LF Reserved 10.30.51.9 | s22-t35-sut1 (netgate-1) 10.30.51.10 | s23-t35-sut2 (netgate-2) 10.30.51.11 | s24-t35-sut3 (netgate-3) 10.30.51.12 | softiron-1 10.30.51.13 | softiron-2 10.30.51.14 | softiron-3 10.30.51.15 | LF Reserved 10.30.51.16 | t1-tg1 10.30.51.17 | t1-sut1 10.30.51.18 | t1-sut2 10.30.51.20 | t2-tg1 10.30.51.21 | t2-sut1 10.30.51.22 | t2-sut2 10.30.51.24 | t3-tg1 10.30.51.25 | t3-sut1 10.30.51.26 | t3-sut-2 10.30.51.28 | t4-sut1 10.30.51.29 | t4-sut2 10.30.51.29 | s22-t35-sut1 screen -r /dev/ttyUSB0, TO BE VERIFIED 10.30.51.30 | t4-sut3 10.30.51.30 | s23-t35-sut2 screen -r /dev/ttyUSB1, TO BE VERIFIED 10.30.51.30 | s24-t35-sut3 screen -r /dev/ttyUSB2, TO BE VERIFIED 10.30.51.36 | s17-t33-sut1 10.30.51.37 | s18-t33-sut2 10.30.51.41 | s20-t34-sut1 10.30.51.42 | s21-t34-sut2 10.30.51.44 | s3-t21-sut1 10.30.51.45 | s4-t21-tg1 10.30.51.46 | s11-t31-sut1 10.30.51.47 | s12-t31-sut2 10.30.51.48 | s13-t31-tg1 10.30.51.49 | s19-t33t34-tg1 10.30.51.50 | s1-t11-sut1 10.30.51.51 | s2-t12-sut1 10.30.51.52 | s5-t22-sut1 10.30.51.53 | s6-t22-tg1 10.30.51.54 | s7-t23-sut1 10.30.51.55 | s8-t23-tg1 10.30.51.56 | s9-t24-sut1 10.30.51.57 | s10-t24-tg1 10.30.51.58 | s14-t32-sut1 10.30.51.59 | s15-t32-sut2 10.30.51.60 | s16-t32-tg1 10.30.51.61 | s25-t25-sut1 10.30.51.62 | s26-t25-tg1 10.30.51.69 | s27-t13-sut1 10.30.51.70-10.30.51.105 | VIRL1 TO BE VERIFIED 10.30.51.106-10.30.51.180 | VIRL2 10.30.51.181-10.30.51.254 | VIRL3 10.30.51.255 | Broadcast 10.32.8.10 | s28-t26t35-tg1 10.32.8.11 | s29-t26-sut1 10.32.8.12 | s30-t35-sut1 10.32.8.13 | s31-t35-sut2 10.32.8.17 | s32-t14-sut1 10.32.8.18 | s33-t27-sut1 10.32.8.19 | s34-t27-tg1 10.32.8.20 | s35-t28-sut1 10.32.8.21 | s36-t28-tg1 10.32.8.22 | s37-t29-sut1 10.32.8.23 | s38-t29-tg1 ## Server Specifications ### Server Types FD.io CSIT lab contains following server types: ``` 1. Server-Type-A1: Purpose - Haswell Xeon SUT (Systems Under Test) for FD.io performance testing. - Quantity: 6 servers. - Physical connectivity: - CIMC and host management ports. - NIC ports connected in 3-node topologies. - Main HW configuration: - Chassis: UCSC-C240-M4SX with 6 PCIe3.0 slots. - Processors: 2* E5-2699v3 2.3 GHz. - RAM Memory: 16* 32GB DDR4-2133MHz. - Disks: 2* 2TB 12G SAS 7.2K RPM SFF HDD. - NICs configuration: - Numa0: Right PCIe Riser Board (Riser 1) (x8, x8, x8 PCIe3.0 lanes) - PCIe Slot1: Cisco VIC 1385 2p40GE. - PCIe Slot2: Intel NIC x520 2p10GE. - PCIe Slot3: empty. - Numa1: Left PCIe Riser Board (Riser 2) (x8, x16, x8 PCIe3.0 lanes) - PCIe Slot4: Intel NIC xl710 2p40GE. - PCIe Slot5: Intel NIC x710 2p10GE. - PCIe Slot6: Intel QAT 8950 50G (Walnut Hill) - MLOM slot: Cisco VIC 1227 2p10GE (x8 PCIe2.0 lanes). 2. Server-Type-A2: Purpose - Haswell Xeon TG (Traffic Generators) for FD.io performance testing. - Quantity: 3 servers. - Physical connectivity: - CIMC and host management ports. - NIC ports connected in 3-node topologies. - Main HW configuration: - Chassis: UCSC-C240-M4SX with 6 PCIe3.0 slots. - Processors: 2* E5-2699v3 2.3 GHz. - RAM Memory: 16* 32GB DDR4-2133MHz. - Disks: 2* 2TB 12G SAS 7.2K RPM SFF HDD. - NICs configuration: - Numa0: Right PCIe Riser Board (Riser 1) (x8, x8, x8 lanes) - PCIe Slot1: Intel NIC xl710 2p40GE. - PCIe Slot2: Intel NIC x710 2p10GE. - PCIe Slot3: Intel NIC x710 2p10GE. - Numa1: Left PCIe Riser Board (Riser 2) (x8, x16, x8 lanes) - PCIe Slot4: Intel NIC xl710 2p40GE. - PCIe Slot5: Intel NIC x710 2p10GE. - PCIe Slot6: Intel NIC x710 2p10GE. - MLOM slot: empty. 3. Server-Type-A3: Purpose - Haswell Xeon VIRL hosts for FD.io functional testing. - Quantity: 3 servers. - Physical connectivity: - CIMC and host management ports. - no NIC ports, standalone setup. - Main HW configuration: - Chassis: UCSC-C240-M4SX with 6 PCIe3.0 slots. - Processors: 2* E5-2699v3 2.3 GHz. - RAM Memory: 16* 32GB DDR4-2133MHz. - Disks: 2* 480 GB 2.5inch 6G SATA SSD. - NICs configuration: - Numa0: Right PCIe Riser Board (Riser 1) (x8, x8, x8 lanes) - no cards. - Numa1: Left PCIe Riser Board (Riser 2) (x8, x16, x8 lanes) - no cards. - MLOM slot: empty. 4. Server-Type-B1: Purpose - Skylake Xeon SUT for FD.io performance testing. - Quantity: --- - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 2-node and 3-node topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8180 2.5 GHz. - RAM Memory: 16* 16GB DDR4-2666MHz. - Disks: 2* 1.6TB 6G SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: xxv710-DA2-2p25GE Intel. - PCIe Slot9 5e:00.xx: empty. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 5. Server-Type-B2: Purpose - Skylake Xeon TG for FD.io performance testing. - Quantity: --- - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 2-node and 3-node topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8180 2.5 GHz. - RAM Memory: 16* 16GB DDR4-2666MHz. - Disks: 2* 1.6TB 6G SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: xxv710-DA2 2p25GE Intel. - PCIe Slot9 5e:00.xx: empty. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: x710-4p10GE Intel. 6. Server-Type-B3: Purpose - TaiShan Arm Huawei SUT for FD.io performance testing. - Quantity: 2 - Physical connectivity: - IPMI(?) and host management ports. - NIC ports connected into 3-node topology. - Main HW configuration: - Chassis: Huawei TaiShan 2280. - Processors: 1* hip07-d05 ~ 64* Arm Cortex-A72 - RAM Memory: 8* 16GB DDR4-2400MT/s - Disks: 1* 4TB SATA HDD - NICs configuration: - PCIe Slot4 e9:00.xx: connectx4-2p25GE Mellanox. - PCIe Slot6 11:00.xx: x520-2p10GE Intel. 7. Server-Type-B4: Purpose - MACCHIATObin Arm Marvell SUT for FD.io performance testing. - Quantity: 3 - Physical connectivity: - Host management ports. - NIC ports connected into 2-node and 3-node topologies. - Main HW configuration: - Chassis: MACCHIATObin. - Processors: 1* Armada 8040 ~ 4* Arm Cortex-A72 - RAM Memory: 1* 16GB DDR4 - Disks: 1* 128GB(?) SATA SDD - NICs configuration: - pp2-2p10GE Marvell (on-chip Ethernet ports ; marvell plugin in VPP) 8. Server-Type-B5: Purpose - Rangeley Atom SUT for FD.io performance testing. - Quantity: TBD based on testbed allocation. - Physical connectivity: - Management: serial Port (usb) for console - NIC ports connected into 2-node. - Main HW configuration: - Chassis: Netgate XG-2758-1u - Processors: 1* Rangeley (Atom) C2758 2.4 GHz - RAM Memory: 16GB ECC - Disks: 150 GB - NICs configuration: - 2x 10Gb Intel 82599ES - 4x 1GB Intel I354 9. Server-Type-B6: Purpose - Skylake Xeon SUT for FD.io VPP_Device functional tests. - Quantity: 2. - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 2-node and 3-node topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8180 2.5 GHz. - RAM Memory: 16* 16GB DDR4-2666MHz. - Disks: 2* 1.6TB 6G SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: x710-4p10GE Intel. - PCIe Slot9 5e:00.xx: empty. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 10. Server-Type-B7: Purpose - Ixia PerfectStorm One Appliance TG for FD.io TCP/IP performance tests. - Quantity: 1. - Physical connectivity: - Host management interface: 10/100/1000-BaseT. - 8-port 10GE SFP+ integrated NIC. - Main HW configuration: - Chassis: PS10GE4NG. - Motherboard: SuperMicro X11DPG-QT. - Processors: Quad-Core, Intel Processor. - HW accelerators: FPGA offload. - RAM Memory: 64GB. - Disks: 1 * 1 TB, Enterprise Class, High MTBF. - Physical Interfaces: 4 * 10GE SFP+. - Operating System: Native IxOS. - Interface configuration: - Port-1: 10GE SFP+. - Port-2: 10GE SFP+. - Port-3: 10GE SFP+. - Port-4: 10GE SFP+. 11. Server-Type-B8: Purpose - Skylake Xeon SUT for TCP/IP host stack tests. - Quantity: 1. - Physical connectivity: - IPMI and host management ports. - NIC ports. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8180 2.5 GHz. - RAM Memory: 16* 16GB DDR4-2666MHz. - Disks: 2* 1.6TB 6G SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: empty. - PCIe Slot9 5e:00.xx: empty. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 12. Server-Type-B9: Purpose - ThunderX2 Arm Marvell SUT for FD.io VPP_Device functional tests. - Quantity: 1 - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 1-node topologies. - Main HW configuration: - Chassis: Gigabyte R181-T90 1U - Motheboard: MT91-FS1 - Processors: 1* ThunderX2 ARMv8 CN9975 2.0 GHz - RAM Memory: 4* 32GB RDIMM - Disks: 1* 480GB SSD Micron, 1* 1000GB HDD Seagate_25 - NICs configuration: - Numa0: - PCIe Slot1 05:00.xx: XL710-QDA2. - PCIe Slot3 08:00.xx: XL710-QDA2. - Numa1: - PCIe Slot6 85:00.xx: XL710-QDA2. 13. Server-Type-B10: Purpose - Denverton Atom SUT for FD.io performance testing. - Quantity: 4 - Physical connectivity: - IPMI and host management ports. - NIC ports. - Main HW configuration: - Chassis: SuperMicro SYS-E300-9A - Processors: 1* Intel(R) Atom(TM) CPU C3858 @ 2.00GHz - RAM Memory: 32GB ECC - Disks: 480 GB - NICs configuration: - 2x 10Gb Intel x553 fiber ports - 2x 10Gb Intel x553 copper ports - 4x 1GB Intel I350 ports 14. Server-Type-C1: Purpose - Cascadelake Xeon SUT for FD.io VPP_Device functional tests. - Quantity: 1. - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 1-node testbed topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8280 2.7 GHz. - RAM Memory: 12* 16GB DDR4-2933. - Disks: 2* 1.92TB SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: x710-4p10GE Intel. - PCIe Slot9 5e:00.xx: empty. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 15. Server-Type-C2: Purpose - Cascadelake Xeon SUT for FD.io performance testing. - Quantity: 3 - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 2-node testbed topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Gold 6252N 2.3 GHz. - RAM Memory: 12* 16GB DDR4-2933. - Disks: 2* 1.92TB SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: xxv710-DA2-2p25GE Intel. - PCIe Slot9 5e:00.xx: ConnectX5-2p100GE Mellanox. - Only 4 of mcx556a-edat ConnectX5-2p100GE NICs are in the lab, so only two out of three 2-node testbeds are equipped with them. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 16. Server-Type-C3: Purpose - Cascadelake Xeon TG for FD.io performance testing. - Quantity: 3. - Physical connectivity: - IPMI and host management ports. - NIC ports connected into 2-node testbed topologies. - Main HW configuration: - Chassis: SuperMicro SYS-7049GP-TRT. - Motherboard: SuperMicro X11DPG-QT. - Processors: 2* Intel Platinum 8280 2.7 GHz. - RAM Memory: 12* 16GB DDR4-2933. - Disks: 2* 1.92TB SATA SSD. - NICs configuration: - Numa0: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot2 18:00.xx: x710-4p10GE Intel. - PCIe Slot4 3b:00.xx: xxv710-DA2 2p25GE Intel. - PCIe Slot9 5e:00.xx: ConnectX5-2p100GE Mellanox. - Only 4 of mcx556a-edat ConnectX5-2p100GE NICs are in the lab, so only two out of three 2-node testbeds are equipped with them. - Numa1: (x16, x16, x16 PCIe3.0 lanes) - PCIe Slot6 86:00.xx: empty. - PCIe Slot8 af:00.xx: empty. - PCIe Slot10 d8:00.xx: empty. 17. Server-Type-C4: Purpose - Cascadelake Xeon Backend hosts for FD.io builds and data processing. - Quantity: 3. - Physical connectivity: - CIMC and host management ports. - no NIC ports, standalone setup. - Main HW configuration: - Chassis: SuperMicro 1029P-WTRT. - Motherboard: SuperMicro X11DDW-NT. - Processors: 2* Intel Platinum 8280 2.7 GHz. - RAM Memory: 12* 16GB DDR4-2933. - Disks: 4* 1.92TB SATA SSD. - NICs configuration: - Numa0: - no cards. - Numa1: - no cards. ``` ### Naming Convention Following naming convention is used within this page to specify physical connectivity and wiring across defined CSIT testbeds: ``` - testbedname: testbedN. - hostname: - traffic-generator: tN-tgW. - system-under-testX: tN-sutX. - portnames: - tN-tgW-cY/pZ. - tN-sutX-cY/pZ. - where: - N - testbed number. - tgW - server acts as traffic-generator with W index. - sutX - server acts as system-under-test with X index. - Y - PCIe slot number denoting a NIC card number within the host. - Z - port number on the NIC card. ``` ## Testbeds Configuration ### Per Testbed Server Allocation and Naming #### 1-Node-Skylake Servers (1n-skx) PROD ``` - SUT [Server-Type-B6]: - testbedname: testbed11. - hostname: s1-t11-sut1. - IPMI IP: 10.30.50.47 - Host IP: 10.30.51.50 - portnames: - s1-t11-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s1-t11-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s1-t11-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s1-t11-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s1-t11-sut1-c4/p1 - 10GE-port1 x710-4p10GE. - s1-t11-sut1-c4/p2 - 10GE-port2 x710-4p10GE. - s1-t11-sut1-c4/p3 - 10GE-port3 x710-4p10GE. - s1-t11-sut1-c4/p4 - 10GE-port4 x710-4p10GE. - SUT [Server-Type-B6]: - testbedname: testbed12. - hostname: s2-t12-sut1. - IPMI IP: 10.30.50.48 - Host IP: 10.30.51.51 - portnames: - s2-t12-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s2-t12-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s2-t12-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s2-t12-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s2-t12-sut1-c4/p1 - 10GE-port1 x710-4p10GE. - s2-t12-sut1-c4/p2 - 10GE-port2 x710-4p10GE. - s2-t12-sut1-c4/p3 - 10GE-port3 x710-4p10GE. - s2-t12-sut1-c4/p4 - 10GE-port4 x710-4p10GE. ``` #### 1-Node-Thunderx2 Servers (1n-tx2) WIP ``` - SUT [Server-Type-B9]: - testbedname: testbed13. - hostname: s27-t13-sut1. - IPMI IP: 10.30.50.69 - Host IP: 10.30.51.69 - portnames: - s27-t13-sut1-c1/p1 - 40GE-port1 XL710-QDA2-2p40GE. - s27-t13-sut1-c1/p2 - 40GE-port2 XL710-QDA2-2p40GE. - s27-t13-sut1-c3/p1 - 40GE-port1 XL710-QDA2-2p40GE. - s27-t13-sut1-c3/p2 - 40GE-port2 XL710-QDA2-2p40GE. - s27-t13-sut1-c6/p1 - 40GE-port1 XL710-QDA2-2p40GE. - s27-t13-sut1-c6/p2 - 40GE-port2 XL710-QDA2-2p40GE. ``` #### 1-Node-Cascadelake Servers (1n-clx) SETUP ``` - SUT [Server-Type-C1]: - testbedname: testbed11. - hostname: s32-t14-sut1. - IPMI IP: 10.30.55.17 - Host IP: 10.32.8.17 - portnames: - s32-t14-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s32-t14-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s32-t14-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s32-t14-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s32-t14-sut1-c4/p1 - 10GE-port1 x710-4p10GE. - s32-t14-sut1-c4/p2 - 10GE-port2 x710-4p10GE. - s32-t14-sut1-c4/p3 - 10GE-port3 x710-4p10GE. - s32-t14-sut1-c4/p4 - 10GE-port4 x710-4p10GE. ``` #### 2-Node-Skylake Servers (2n-skx) PROD ``` - SUT [Server-Type-B1]: - testbedname: testbed21. - hostname: s3-t21-sut1. - IPMI IP: 10.30.50.41 - Host IP: 10.30.51.44 - portnames: - s3-t21-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s3-t21-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s3-t21-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s3-t21-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s3-t21-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s3-t21-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - TG [Server-Type-B2]: - testbedname: testbed21. - hostname: s4-t21-tg1. - IPMI IP: 10.30.50.42 - Host IP: 10.30.51.45 - portnames: - s4-t21-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s4-t21-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s4-t21-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s4-t21-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s4-t21-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s4-t21-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - SUT [Server-Type-B1]: - testbedname: testbed22. - hostname: s5-t22-sut1. - IPMI IP: 10.30.50.49 - Host IP: 10.30.51.52 - portnames: - s5-t22-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s5-t22-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s5-t22-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s5-t22-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s5-t22-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s5-t22-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - TG [Server-Type-B2]: - testbedname: testbed22. - hostname: s6-t22-tg1. - IPMI IP: 10.30.50.50 - Host IP: 10.30.51.53 - portnames: - s6-t22-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s6-t22-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s6-t22-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s6-t22-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s6-t22-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s6-t22-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - SUT [Server-Type-B1]: - testbedname: testbed23. - hostname: s7-t23-sut1. - IPMI IP: 10.30.50.51 - Host IP: 10.30.51.54 - portnames: - s7-t23-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s7-t23-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s7-t23-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s7-t23-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s7-t23-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s7-t23-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - TG [Server-Type-B2]: - testbedname: testbed23. - hostname: s8-t23-tg1. - IPMI IP: 10.30.50.52 - Host IP: 10.30.51.55 - portnames: - s8-t23-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s8-t23-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s8-t23-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s8-t23-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s8-t23-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s8-t23-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - SUT [Server-Type-B1]: - testbedname: testbed24. - hostname: s9-t24-sut1. - IPMI IP: 10.30.50.53 - Host IP: 10.30.51.56 - portnames: - s9-t24-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s9-t24-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s9-t24-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s9-t24-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s9-t24-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s9-t24-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - TG [Server-Type-B2]: - testbedname: testbed24. - hostname: s10-t24-tg1. - IPMI IP: 10.30.50.54 - Host IP: 10.30.51.57 - portnames: - s10-t24-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s10-t24-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s10-t24-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s10-t24-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s10-t24-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s10-t24-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. ``` #### 2-Node-Denverton Servers (2n-dnv) WIP Note: ServerB28 (TG) is shared between testbed26 & testbed35 ``` - TG [Server-Type-B2]: - testbednames: testbed26 and testbed35. - hostname: s28-t26t35-tg1. - IPMI IP: 10.30.55.10 - Host IP: 10.32.8.10 - portnames: - s28-t26t35-tg1-c2/p1 - 10GE-port1 x710da2-2p10GE. - s28-t26t35-tg1-c2/p2 - 10GE-port2 x710da2-2p10GE. - s28-t26t35-tg1-c4/p1 - 10GE-port1 x550t2-2p10GE. - s28-t26t35-tg1-c4/p2 - 10GE-port2 x550t2-2p10GE. - s28-t26t35-tg1-c9/p1 - 10GE-port1 x550t2-2p10GE. - s28-t26t35-tg1-c9/p2 - 10GE-port2 x550t2-2p10GE. - s28-t26t35-tg1-c6/p1 - 10GE-port1 x710da2-2p10GE. - s28-t26t35-tg1-c6/p2 - 10GE-port2 x710da2-2p10GE. - s28-t26t35-tg1-c8/p1 - 10GE-port1 x550t2-2p10GE. - s28-t26t35-tg1-c8/p2 - 10GE-port2 x550t2-2p10GE. - s28-t26t35-tg1-c10/p1 - 10GE-port1 x550t2-2p10GE. - s28-t26t35-tg1-c10/p2 - 10GE-port2 x550t2-2p10GE. - SUT [Server-Type-B10]: - testbednames: testbed26. - hostname: s29-t26-sut1. - IPMI IP: 10.30.55.11 - Host IP: 10.32.8.11 - portnames: - s29-t26-sut1-p1 - 10GE-port1 x553 copper port. - s29-t26-sut1-p2 - 10GE-port2 x553 copper port. - s29-t26-sut1-p3 - 10GE-port3 x553 fiber port. - s29-t26-sut1-p4 - 10GE-port4 x553 fiber port. ``` #### 2-Node-IxiaPS1L47 Servers (2n-ps1) VERIFY ``` - SUT [Server-Type-B8]: - testbedname: testbed25. - hostname: s25-t25-sut1. - IPMI IP: 10.30.50.58 - Host IP: 10.30.51.61 - portnames: - s25-t25-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s25-t25-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s25-t25-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s25-t25-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - TG [Server-Type-B7]: - testbedname: testbed25. - hostname: s26-t25-tg1. - IPMI IP: 10.30.50.59 - Host IP: 10.30.51.62 - portnames: - s26-t25-tg1-p1 - 10GE-port1. - s26-t25-tg1-p2 - 10GE-port2. - s26-t25-tg1-p3 - 10GE-port3. - s26-t25-tg1-p4 - 10GE-port4. ``` #### 2-Node-Cascadelake Servers (2n-clx) SETUP ``` - SUT [Server-Type-C2]: - testbedname: testbed27. - hostname: s33-t27-sut1. - IPMI IP: 10.30.55.18 - Host IP: 10.32.8.18 - portnames: - s33-t27-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s33-t27-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s33-t27-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s33-t27-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s33-t27-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s33-t27-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s33-t27-sut1-c9/p1 - 100GE-port1 ConnectX5-2p100GE. - s33-t27-sut1-c9/p2 - 100GE-port2 ConnectX5-2p100GE. - TG [Server-Type-C3]: - testbedname: testbed27. - hostname: s34-t27-tg1. - IPMI IP: 10.30.55.19 - Host IP: 10.32.8.19 - portnames: - s34-t27-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s34-t27-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s34-t27-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s34-t27-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s34-t27-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s34-t27-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s34-t27-tg1-c9/p1 - 100GE-port1 ConnectX5-2p100GE. - s34-t27-tg1-c9/p2 - 100GE-port2 ConnectX5-2p100GE. - SUT [Server-Type-C2]: - testbedname: testbed28. - hostname: s35-t28-sut1. - IPMI IP: 10.30.55.20 - Host IP: 10.32.8.20 - portnames: - s35-t28-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s35-t28-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s35-t28-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s35-t28-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s35-t28-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s35-t28-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s35-t28-sut1-c9/p1 - 100GE-port1 ConnectX5-2p100GE. - s35-t28-sut1-c9/p2 - 100GE-port2 ConnectX5-2p100GE. - TG [Server-Type-C3]: - testbedname: testbed28. - hostname: s36-t28-tg1. - IPMI IP: 10.30.55.21 - Host IP: 10.32.8.21 - portnames: - s36-t28-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s36-t28-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s36-t28-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s36-t28-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s36-t28-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s36-t28-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s36-t28-tg1-c9/p1 - 100GE-port1 ConnectX5-2p100GE. - s36-t28-tg1-c9/p2 - 100GE-port2 ConnectX5-2p100GE. - SUT [Server-Type-C2]: - testbedname: testbed29. - hostname: s37-t29-sut1. - IPMI IP: 10.30.55.22 - Host IP: 10.32.8.22 - portnames: - s37-t29-sut1-c2/p1 - 10GE-port1 x710-4p10GE. - s37-t29-sut1-c2/p2 - 10GE-port2 x710-4p10GE. - s37-t29-sut1-c2/p3 - 10GE-port3 x710-4p10GE. - s37-t29-sut1-c2/p4 - 10GE-port4 x710-4p10GE. - s37-t29-sut1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s37-t29-sut1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s37-t29-sut1-c9/p1 - FUTURE 100GE-port1 ConnectX5-2p100GE. - s37-t29-sut1-c9/p2 - FUTURE 100GE-port2 ConnectX5-2p100GE. - TG [Server-Type-C3]: - testbedname: testbed29. - hostname: s38-t29-tg1. - IPMI IP: 10.30.55.23 - Host IP: 10.32.8.23 - portnames: - s38-t29-tg1-c2/p1 - 10GE-port1 x710-4p10GE. - s38-t29-tg1-c2/p2 - 10GE-port2 x710-4p10GE. - s38-t29-tg1-c2/p3 - 10GE-port3 x710-4p10GE. - s38-t29-tg1-c2/p4 - 10GE-port4 x710-4p10GE. - s38-t29-tg1-c4/p1 - 25GE-port1 xxv710-DA2-2p25GE. - s38-t29-tg1-c4/p2 - 25GE-port2 xxv710-DA2-2p25GE. - s38-t29-tg1-c9/p1 - FUTURE 100GE-port1 ConnectX5-2p100GE. - s38-t29-tg1-c9/p2 - FUTURE 100GE-port2 ConnectX5-2p100GE. ``` #### 3-Node-Haswell Servers (3n-hsw) PROD ``` 1. SUT [Server-Type-A1]: - testbedname: testbed1. - hostname: t1-sut1. - CIMC IP: 10.30.50.17 - Host IP: 10.30.51.17 - portnames: - t1-sut1-c1/p1 - 10GE port1 on Intel NIC x520 2p10GE. - t1-sut1-c1/p2 - 10GE port2 on Intel NIC x520 2p10GE. - t1-sut1-c2/p1 - 40GE port1 on Cisco VIC 1385 2p40GE. - t1-sut1-c2/p2 - 40GE port2 on Cisco VIC 1385 2p40GE. - t1-sut1-c4/p1 - 40GE port1 on Intel NIC xl710 2p40GE. - t1-sut1-c4/p2 - 40GE port2 on Intel NIC xl710 2p40GE. - t1-sut1-c5/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-sut1-c5/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t1-sut1-cm/p1 - 10GE port1 on Cisco VIC 1227 2p10GE. - t1-sut1-cm/p2 - 10GE port2 on Cisco VIC 1227 2p10GE. 2. SUT [Server-Type-A1]: - testbedname: testbed1. - hostname: t1-sut2. - CIMC IP: 10.30.50.18 - Host IP: 10.30.51.18 - portnames: - t1-sut2-c1/p1 - 10GE port1 on Intel NIC x520 2p10GE. - t1-sut2-c1/p2 - 10GE port2 on Intel NIC x520 2p10GE. - t1-sut2-c2/p1 - 40GE port1 on Cisco VIC 1385 2p40GE. - t1-sut2-c2/p2 - 40GE port2 on Cisco VIC 1385 2p40GE. - t1-sut2-c4/p1 - 40GE port1 on Intel NIC xl710 2p40GE. - t1-sut2-c4/p2 - 40GE port2 on Intel NIC xl710 2p40GE. - t1-sut2-c5/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-sut2-c5/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t1-sut2-cm/p1 - 10GE port1 on Cisco VIC 1227 2p10GE. - t1-sut2-cm/p2 - 10GE port2 on Cisco VIC 1227 2p10GE. 3. TG [Server-Type-A2]: - testbedname: testbed1. - hostname: t1-tg1. - CIMC IP: 10.30.50.16 - Host IP: 10.30.51.16 - portnames: - t1-tg1-c1/p1 - 40GE port1 on Intel NIC xl710 2p40GE. - t1-tg1-c1/p2 - 40GE port2 on Intel NIC xl710 2p40GE. - t1-tg1-c2/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-tg1-c2/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t1-tg1-c3/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-tg1-c3/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t1-tg1-c4/p1 - 40GE port1 on Intel NIC xl710 2p40GE. - t1-tg1-c4/p2 - 40GE port2 on Intel NIC xl710 2p40GE. - t1-tg1-c5/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-tg1-c5/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t1-tg1-c6/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t1-tg1-c6/p2 - 10GE port2 on Intel NIC x710 2p10GE. 4. SUT [Server-Type-A1]: - testbedname: testbed2. - hostname: t2-sut1. - CIMC IP: 10.30.50.21 - Host IP: 10.30.51.21 - portnames: - t2-sut1-c1/p1 - 10GE port1 on Intel NIC x520 2p10GE. - t2-sut1-c1/p2 - 10GE port2 on Intel NIC x520 2p10GE. - t2-sut1-c2/p1 - 40GE port1 on Cisco VIC 1385 2p40GE. - t2-sut1-c2/p2 - 40GE port2 on Cisco VIC 1385 2p40GE. - t2-sut1-c4/p1 - 40GE port1 on Intel NIC xl710 2p40GE. - t2-sut1-c4/p2 - 40GE port2 on Intel NIC xl710 2p40GE. - t2-sut1-c5/p1 - 10GE port1 on Intel NIC x710 2p10GE. - t2-sut1-c5/p2 - 10GE port2 on Intel NIC x710 2p10GE. - t2-sut1-cm/p1 - 10GE port1 on Cisco VIC 1227 2p10GE. - t2-s
# Copyright (c) 2018 Cisco and/or its affiliates.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at:
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
"""Algorithms to generate tables.
"""
import logging
import csv
import prettytable
import pandas as pd
from string import replace
from collections import OrderedDict
from numpy import nan, isnan
from xml.etree import ElementTree as ET
from errors import PresentationError
from utils import mean, stdev, relative_change, classify_anomalies
def generate_tables(spec, data):
"""Generate all tables specified in the specification file.
:param spec: Specification read from the specification file.
:param data: Data to process.
:type spec: Specification
:type data: InputData
"""
logging.info("Generating the tables ...")
for table in spec.tables:
try:
eval(table["algorithm"])(table, data)
except NameError as err:
logging.error("Probably algorithm '{alg}' is not defined: {err}".
format(alg=table["algorithm"], err=repr(err)))
logging.info("Done.")
def table_details(table, input_data):
"""Generate the table(s) with algorithm: table_detailed_test_results
specified in the specification file.
:param table: Table to generate.
:param input_data: Data to process.
:type table: pandas.Series
:type input_data: InputData
"""
logging.info(" Generating the table {0} ...".
format(table.get("title", "")))
# Transform the data
logging.info(" Creating the data set for the {0} '{1}'.".
format(table.get("type", ""), table.get("title", "")))
data = input_data.filter_data(table)
# Prepare the header of the tables
header = list()
for column in table["columns"]:
header.append('"{0}"'.format(str(column["title"]).replace('"', '""')))
# Generate the data for the table according to the model in the table
# specification
job = table["data"].keys()[0]
build = str(table["data"][job][0])
try:
suites = input_data.suites(job, build)
except KeyError:
logging.error(" No data available. The table will not be generated.")
return
for suite_longname, suite in suites.iteritems():
# Generate data
suite_name = suite["name"]
table_lst = list()
for test in data[job][build].keys():
if data[job][build][test]["parent"] in suite_name:
row_lst = list()
for column in table["columns"]:
try:
col_data = str(data[job][build][test][column["data"].
split(" ")[1]]).replace('"', '""')
if column["data"].split(" ")[1] in ("vat-history",
"show-run"):
col_data = replace(col_data, " |br| ", "",
maxreplace=1)
col_data = " |prein| {0} |preout| ".\
format(col_data[:-5])
row_lst.append('"{0}"'.format(col_data))
except KeyError:
row_lst.append("No data")
table_lst.append(row_lst)
# Write the data to file
if table_lst:
file_name = "{0}_{1}{2}".format(table["output-file"], suite_name,
table["output-file-ext"])
logging.info(" Writing file: '{}'".format(file_name))
with open(file_name, "w") as file_handler:
file_handler.write(",".join(header) + "\n")
for item in table_lst:
file_handler.write(",".join(item) + "\n")
logging.info(" Done.")
def table_merged_details(table, input_data):
"""Generate the table(s) with algorithm: table_merged_details
specified in the specification file.
:param table: Table to generate.
:param input_data: Data to process.
:type table: pandas.Series
:type input_data: InputData
"""
logging.info(" Generating the table {0} ...".
format(table.get("title", "")))
# Transform the data
logging.info(" Creating the data set for the {0} '{1}'.".
format(table.get(