MOC Public Network Providers¶
This document describes what external networks the MOC utilizes for public connectivity and who to contact for support.
There are 4 networks we use from CSAIL. For help, we should contact email@example.com
We used this for infrastructure in engage1 but we have to use CSAIL’s DHCP since they like to control this network, which makes this less desirable. As of 8/12/2021, the DHCP range on this network is 126.96.36.199/25.
Our brocade switches in BU cages 2 and 4 connect to the CSAIL switch to access this network.
We used this for engage1. Our brocade switches in BU cages 2 and 4 connect to the CSAIL switch to access this network.
For Kaizen openstack floating IPs. We don’t have a direct connection to CSAIL switch, but instead it’s via NEU->MeetMe->MIT->CSAIL.
This is used for MaaS services and hosts, and some infrastructure VMs. Our Cisco switch in Kumo (Row 4 Pod A Cage) connects to a BU switch which carries this VLAN in addition to BU’s public network (VLAN 105, 188.8.131.52/24).
We have no servers racked in MIT space. The cluster we call enage1 at MOC is racked in BU cages 2 and 4 (Row 4 Pod A). We have 4 brocade switches racked in those cages and they are part of a brocade fabric where the rest of the brocade switches (5) are racked in MIT cages. We should figure who gets dibs on those switches. The brocade switches that connect to CSAIL are in our cages so that’s good.
We can open a ticket with (BU IS&T)[https://www.bu.edu/tech/contact/] for support.
Used for all our openshift clusters. We get this from the BU switch in kumo which also gets us VLAN 3803 from CSAIL.
We can email firstname.lastname@example.org for help.
Used for all our infrastructure needs like openstack services, monitoring, DNS, radosgw etc.