Build Test Environment Setup in Colo, document connectivity, and test

[owendelong]

Description

We are in the process of building a test environment in Owen's cabinet in HE FMT2. The test environment will terminate the show IPv6 Tunnel except during the show and will provide a limited, but fairly complete simulation of the show network. It's using an SRX-300 router that Owen has lent to the project as well as the 3rd Lenovo server contributed by Bala. One of our ex4200-48p switches is installed there to simulate an IDF switch. One AP is installed and connected to the IDF switch and will provide our standard WiFi networks in a small area near the cabinet.

Acceptance Criteria

The full scope of the configuration, the capabilities and limitations of the simulation, DHCP, DNS, and other services must be configured, documented, and tested.

Currently, the router is believed to be fully configured.
The switch is about 90% configured (AP is attached, and it has uplink capabilities).
There is configuration left to do on Owen's MX-240 to enable the additional VLANs to be trunked through the MX240 to Owen's switch and there may be some minor configuration work left to do on Owen's switch.

This issue will contain notes that can hopefully be eventually turned into more complete documentation.

[owendelong]

General structure of the network:

Trunks will carry all SCaLE simulant VLANs between the SCaLE switch, Owen's MX-240, Owen's Switch, and the SRX-300.

The SRX-300 is attached to Owen's switch with 4 1Gbe Lines organized into a ~4Gbps LACP trunk. Owen's switch has a 20Gbps (2x10Ge) LACP trunk to Owen's MX-240 which has an additional 20Gbps (2x10Ge) LACP trunk to the SCaLE switch.

The SCaLE server will eventually have a 4x1Gbe trunk to the SCaLE switch to carry the various SCaLE and external management VLANs (except the OOB network to the IPMI card which is a separated dedicated link to the MX-240).

Current TODO:

• 1. Finish configuring the MX-240 to support all the needed VLANs on the ae1 (Owen's Switch) and ae6 (SCaLE switch)

• 2. Configure the dev server to support the LACP (802.3ad) trunk (802.1q) on 3 of the 4 interfaces (leaving the current active interface operational)

• 3. Connect, configure, and test the server trunk on 3 of the 4 interfaces on the SCaLE switch

  • Configure Trunk on switch
  • Cable 3 interfaces
  • Configure Trunk on server
  • Test

• 4. Disconnect the original interface and migrate the IP addresses on it to the appropriate sub interface of the new trunk.

• 5. Add the original interface into the LACP bundle of the trunk.

• 6. Test general network reachability from the server to the outside world via the SRX

• 7. Enable DHCP, DNS, NTP, and any other show-critical services on the appropriate VLANs to make the WAP work.

• 8. Test the WAP in general.

Once these steps are complete, we should be able to test the intended modifications for addressing Google's PMTU issues on IPv6.