If you consider to use a new IPv4 private subnet for your own work, please talk to Frank to get a unique and documented address prefix (e.g., 10.x.0.0/16).

VLANs

To be prepared for cases in which VLANs may span multiple floors of our building or even a wider range, VLAN-IDs have to be unique. Therefore, the VLAN ID namespace is managed by the GITZ. The following table lists the VLAN which are currently assigned to IBR:

ibr-core

136

core services; attachments are restricted to the server room and to hosts which are maintained only by IBR admins

ibr-cip

137

pools (rooms G40 and 359)

ibr-lab

138

Lab VLAN (currently not is use, 2016-04)

ibr-misc

139

major VLAN to which any hosts may connect; almost all ports in IBR rooms are in this VLAN

ibr-mgmt

140

management VLAN (switches, BMCs, iDRACs)

ibr-roce

141

VLAN for RDMA over Converged Ethernet (RoCE) which is used by the DS group

ibr-ds

142

a VLAN to interconnect some servers of the DS group

ibr-san

143

a VLAN to interconnect iSCSI devices in room 104, 10G-only

IPv6 Routing

Don't worry, if you see multiple IPv6 default routes. As of 2017-02 we really have two routers: The Linux firewall and gateway router advertises itself with "low" priority, while the Mellanox switch/router advertises itself with "high" priority, because it is able to route much faster between the IBR subnets. Just in case, the Mellanox router fails, well behaved IPv6 clients should use the Linux router.