Making changes in the server room

This is an overview/checklist for what to do when you add hardware or make changes in the server room.

We keep our infra inventory in Netbox, which can be accessed by everyone who's part of the Github organization.

1. Make sure you're in the contact list

• Link to contact list
• A “Contact” holds information about how to get in touch with a specific contact person
• Click “Add” in the top right to add a new
  • Group: Nettlaug members
  • Fill out real name, e-mail and phone number
• We need accurate contact info for all personal devices in the server room. If someone needs to contact you (i.e in case of accidentally removed power, need to move your device or if it has an alarm), we need to be able to get in touch with you.
• Important: do NOT add personal information about other members without their consent

2. Make sure you're in the tenant list

• Link to tenants list
• A “Tenant” holds information about whom something (device, IP) is assigned to
• Click “Add” in the top right to add a new
  • Name: nick/handle (upper/lowercase as you want yourself)
  • Slug: lowercase nick/handle
  • Group: Nettlaug members
• Add yourself as contact to the tenant
  • Group: Nettlaug members
  • Contact: <your contact>
  • Role: Nettlaug member
  • Priority: Primary

3. Add or claim IP address(es) - public or private

3.1 Public IPv4 (VLAN 130)

• We have a limited number of public IPv4 addresses. You will find those in this list
• The config for this network is:
  • Network ID: 185.35.202.192/26
  • First IP: 185.35.202.193
  • Last IP: 185.35.202.254
  • Gateway: 185.35.202.193
  • Netmask: 255.255.255.192
• Set “Nettlaug members” as tenant group, and your own tenant as tenant for the address
• Fill out something descriptive (like hostname) in the Description field
• Take note of the last octet if the IP (right-most group of numbers)

3.2 Public IPv6 (VLAN 130) - single address

• Each host with a v4 address can bind a corresponding v6 address
• You'll find the IPv6 addresses in this list
• Pattern: 2a02:ed06::<IPv4 octet>
  • Example: IPv4 address is 185.35.202.193, that makes the IPv6 address 2a02:ed06::193
• The config for this network is:
  • Network ID: 2a02:ed06::/64
  • First usable IP: 20a2:ed06::1
  • Last usable IP: 2a02:ed06::ffff:ffff:ffff:fffe
  • Gateway: 20a2:ed06::1
  • Netmask: ffff:ffff:ffff:ffff:0:0:0:0
• Set Nettlaug members as tenant group, and your own tenant as tenant for the address
• Fill out something descriptive (like hostname) in the Description field

3.3 Public IPv6 (VLAN 130) - multiple addresses

• If you need more than one IPv6 address, you can assign a range of IPv6 addresses to yourself. This will not affect any routing, but just reserve those addresses in the inventory, so that we don't get collisions.
• Add an IP range in this list and use the network config in 3.2 to configure the additional addresses
  • X and Y can anything you want between 0000 and ffff
  • Z can anything you want between 0001 and ffff (not 0000)
  • BE CONSIDERATE and don't claim too many addresses
  • Start: 20a2:ed06::X:Y:Z:0/64
  • End: 20a2:ed06::X:Y:Z:ffff/64
  • Description: short description of what you'll use the addresses for
  • Tenant group: Nettlaug members
  • Tenant: <your tenant>

4. Make sure your device's model is in the list of Device types

• Make sure to add “Interface” components as well (use eth0, eth1, eth2 etc. if you don't have their numbering) for the device type. This will allow you to document where it's connected.
• Interfaces etc. are only populated on a Device from the Device Type when it is initially created. When changing the Device Type after Device creation, you need to either manually move over changes or recreate the Device.

5. Create the device from the Device list

• Device role: Member device
• Device type: <your device type>
• Site: Hausmania
• Location: Haus server room
• Tenant group: Nettlaug members
• Tenant: <your tenant>

6. Go to the device and add yourself as contact