[Starlingx-discuss] STX networking

Wed May 11 19:25:21 UTC 2022

replying to answer your questions from email below,
see in-lined below,
Greg.

-----Original Message-----
From: Outback Dingo <outbackdingo at gmail.com>
Sent: Wednesday, May 11, 2022 12:00 AM
To: starlingx-discuss at lists.starlingx.io
Subject: [Starlingx-discuss] STX networking

[Please note: This e-mail is from an EXTERNAL e-mail address]

scenario...

i have a host say controller-0

prior to any ansible run
[Greg] I assume you mean the bootstrap ansible playbook

i need to create a bond, and bridges and vlans
[Greg] You do need an interface to the outside world ... e.g. in order to download container images from docker hub.
[Greg] Why can you not simply create a single interface (one link of bond) with a vlan ?

sure....
Add a bond device as root:

ip link add bond0 type bond
ip link set bond0 type bond miimon 100 mode 80211.ad ip link set enp33s0 down ip link set snp33s0 master bond0 ip link set enp44s0 down ip link set enp44s0 master bond0 ip link set bond0 up

Set VLAN on the bond device:

ip link add link bond0 name bond0.1648 type vlan id 1648 ip link set bond0.1648 up ip link add link bond0 name bond0.1664 type vlan id 1664 ip link set bond0.1664 up ip link add link bond0 name bond0.1680 type vlan id 1680 ip link set bond0.1680 up

Add the bridge device and attach VLAN to it:
ip link add br0 type bridge
ip link set bond0.1648 master br0
ip link set bond0.1664 master br0
ip link set bond0.1680 master br0
ip link set br0 up

so i see where in starlingx
[Greg] the following commands are only possible AFTER bootstrap

system host-if-add -c platform -a 802.3ad -x layer2 controller-0 bond0 ae enp33s0 enp49s0
system host-if-modify controller-0 $OAM_IF -c platform system interface-network-assign controller-0 $OAM_IF oam
system host-if-add controller-0 -V 1648 -c platform bond0.1648 vlan bond0
system host-if-add controller-0 -V 1664 -c platform bond0.1664 vlan bond0
system host-if-add controller-0 -V 1680 -c platform bond0.1680 vlan bond0

does allow for me to create the bond0 and the vlans? but I dont see any documentation for bridges anywhere ? Do I even need the bridge.
[Greg] No ... there is no requirement for a bridge with StarlingX.

where i want to set example, since each needs its own interface can i set OAM_IF=bond0, and say MGMT_IF=bond0.1664
[Greg] Yes ... i.e. OAM on port-based/untagged-vlan of bond and MGMT on vlan-tag=1664 on bond
( BUT here is where you need the pxeboot network because your MGMT network is vlan-tagged ... and you can't pxe boot over that )

OAM_IF=bond0
system host-if-modify controller-0 $OAM_IF -c platform system interface-network-assign controller-0 $OAM_IF oam
system host-if-add controller-0 -V 1648 -c platform bond0.1648 vlan bond0
system host-if-add controller-0 -V 1664 -c platform bond0.1664 vlan bond0
system host-if-add controller-0 -V 1680 -c platform bond0.1680 vlan bond0
system host-if-add controller-0 -V 1672 -c platform bond0.1672 vlan bond0
MGMT_IF=bond0.1664
system host-if-modify controller-0 lo -c none IFNET_UUIDS=$(system interface-network-list controller-0 | awk '{if
($6=="lo") print $4;}')
for UUID in $IFNET_UUIDS; do
    system interface-network-remove ${UUID}
done
system host-if-modify controller-0 $MGMT_IF -c platform   [Greg] don't think you actually need this command
system interface-network-assign controller-0 $MGMT_IF mgmt
system interface-network-assign controller-0 $MGMT_IF cluster-host

the reason for this being our switches are

# MGMT
interface vlan1648
  address 10.16.48.2/24
  address-virtual 44:38:39:FF:00:02 10.16.48.1
  vlan-id 1648
  vlan-raw-device bridge

interface vlan1672
  address 10.16.72.2/24
  address-virtual 44:38:39:FF:00:03 10.16.72.1
  vlan-id 1672
  vlan-raw-device bridge

interface vlan1680
  address 10.16.80.2/24
  address-virtual 44:38:39:FF:00:03 10.16.80.1
  vlan-id 1680
  vlan-raw-device bridge

interface vlan1696
  address 10.16.96.2/24
  address-virtual 44:38:39:FF:00:03 10.16.96.1
  vlan-id 1696
  vlan-raw-device bridge

interface vlan1664
  address 10.16.64.2/24
  address-virtual 44:38:39:FF:00:07 10.16.64.1
  vlan-id 1664
  vlan-raw-device bridge

and further down DATAIF_0=bond0.1680

the reason being we are trying to have starlingx conform to our networks topology I also noted: in
https://docs.starlingx.io/deploy_install_guides/r6_release/ansible_bootstrap_configs.html#install-time-only-params-r6
...

Network Properties I listed at the bottom

can i modify these addresses to conform to our networks, as our switches wount pass the traffic you set as defaults, as seen in my first attempt at the bottom. Though i dont believe still dhcp/pxe will work on a vlan interface.

Network Properties
pxeboot_subnet
pxeboot_start_address
pxeboot_end_address
management_subnet
management_start_address
management_end_address
cluster_host_subnet
cluster_host_start_address
cluster_host_end_address
cluster_pod_subnet
cluster_pod_start_addres
cluster_pod_end_address
cluster_service_subnet
cluster_service_start_address
cluster_service_end_address
management_multicast_subnet
management_multicast_start_address
management_multicast_end_address

7: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000
    link/ether b8:59:9f:12:34:f0 brd ff:ff:ff:ff:ff:ff
    inet 10.16.48.112/24 brd 10.16.48.255 scope global bond0
       valid_lft forever preferred_lft forever
    inet 10.16.48.114/24 scope global secondary bond0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba59:9fff:fe12:34f0/64 scope link
       valid_lft forever preferred_lft forever
8: vlan1664 at bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb state UP group default qlen 1000
    link/ether b8:59:9f:12:34:f0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.204.2/24 brd 192.168.204.255 scope global vlan1664
       valid_lft forever preferred_lft forever
    inet 192.168.206.2/24 brd 192.168.206.255 scope global vlan1664:12
       valid_lft forever preferred_lft forever
    inet 169.254.202.1/24 scope global vlan1664
       valid_lft forever preferred_lft forever
    inet 192.168.206.1/24 scope global secondary vlan1664
       valid_lft forever preferred_lft forever
    inet 192.168.204.1/24 scope global secondary vlan1664
       valid_lft forever preferred_lft forever
    inet 192.168.204.4/24 brd 192.168.204.255 scope global secondary vlan1664
       valid_lft forever preferred_lft forever
    inet6 fe80::ba59:9fff:fe12:34f0/64 scope link
       valid_lft forever preferred_lft forever
9: vlan1672 at bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b8:59:9f:12:34:f0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ba59:9fff:fe12:34f0/64 scope link
       valid_lft forever preferred_lft forever
10: vlan1648 at bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b8:59:9f:12:34:f0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ba59:9fff:fe12:34f0/64 scope link
       valid_lft forever preferred_lft forever
11: vlan1680 at bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b8:59:9f:12:34:f0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::ba59:9fff:fe12:34f0/64 scope link
       valid_lft forever preferred_lft forever

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20220511/d30a6915/attachment-0001.htm>