[Atlas-anchors-pilot] Network configuration details

[Romeo Zwart]

Hi all,
Tore, congrats. :)

On 12/10/30 09:46 , Tore Anderson wrote:
> Hi,
> 
> Just got my purchase order approved, so I'll be ordering the box later
> today. I was wondering about how its network configuration should look
> like, such as:

During the first phase of the pilot we will work with a simplified
network setup.

> - Host name and desired PTR DNS records?

We will publish a naming-scheme soon.

> - Will both or only one of the LAN ports be used?

Only one port will be used during the pilot phase. The second port may
be used later in an aggregated set up, as has been mentioned here too.
However, we're also considering using the second port to split off
particular services.

> - If both ports are to be used, how should the network be configured?
> (LACP, static LAG, VRRP, same VLAN, as independent layer-3 ports, or
> something else?)

Not yet applicable.

> - Desired prefix lengths for IPv4 and IPv6? (If shorter than /31 for
> IPv4, could you provide a filled in ripe-488 form?)

Not sure I understand your question. I think that the assumption here
has been that addresses used will be part of your (aggregated) address
space.

> - Address configuration (DHCPv4, IPv6 ND/RA, DHCPv6, SLAAC, static, ..)?

static

> - Any routing requirements to be aware of? I assume BGP will be used for
> the K-root instance?

No routing requirements for the pilot. BGP for a K-root instance is
beyond the scope of the Atlas Anchor pilot. We are considering some
alternatives for the K-root setup that may or may not use BGP, but as
said, that's out of scope for this pilot.

> - Is IPv4 a requirement for the iDRAC port, or is IPv6-only fine? (I try
> to save on IPv4 addresses where I can...)

A desire that we sympathize with. :) Let me get back to you on this one.

Regards,
Romeo