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

Asset tags are written on the following format: HNL00001S26

Breakdown:

• HNL: Tenant/Owner scope
  • HNL: Hackeriet NettLaug (Network Infrastructure)
  • HCK: Other Hackeriet devices
  • MBR: Member device (Nettlaug tenant)
• 00001: Sequence number
• S: Tag type - Rough namespacing of various assets
  • B: Backbone cables (uplinks/downlinks)
  • S: Switches
  • T: Tenant-destined cables (i.e. from Hackeriet/Nettlaug to non-Hackeriet/Nettlaug people)
• 26: Installation year (Optional) - For quick “vibecheck” of e.g. cables or common infra

Labels should include a QR code leading to the Netbox search page: https://ip.hackeriet.no/search/?q=TAG

A full run of labels (00001-00009, 00010-00019, etc.) should be printed whenever a new series is needed.

The NEXT START of a given series, as of 2026-11-07:

• HNL000010S26
• HNL000010T26

Switches should be marked with two tags:

• Facing reader (e.g. front of device when in a rack)
• An alternative side (e.g. top/side) in case primary label gets lost

Cables should be marked with at least three-four tags:

• One in each end, close to the connector
• In strategic locations along its run, e.g. in the middle or after “important” walls

We keep our infra inventory in Netbox, which can be accessed by everyone who's onboarded into Hula by utilizing Hacker-ID.

• 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

• 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.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 a prefix in this list and use the following parameters:
  • Prefix: 2a02:ed06::N:0/112 (where N is the next available prefix)
    • N can anything you want between 0001 and ffff (not 0000)
  • Status: Container
  • Role: Nettlaug-member hosts
  • Is a pool: -on-
  • Mark utilized: -on-
  • Scope type: DCIM > Site
  • Site: Hausmania
  • VLAN: NETT-SRV (130)
  • Tenant group: Nettlaug members
  • Tenant: <your tenant>

• 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.

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