Talk:Network Environment

From BCCD 3.0

(Difference between revisions)
Jump to: navigation, search
(Stage descriptions)
Line 13: Line 13:
### If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
### If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
## Diskless boot: Upon user request, start DHCP server that will answer requests from diskless BCCD systems on '''only''' a given interface
## Diskless boot: Upon user request, start DHCP server that will answer requests from diskless BCCD systems on '''only''' a given interface
 +
 +
Open questions:
 +
 +
# Should we continue using <code>bccd-identifier</code> or switch to using the standard [https://www.isc.org/wp-content/uploads/2017/08/dhcp41options.html <code>vendor-class-identifier]</code> that can be provided via <code>[https://www.freedesktop.org/software/systemd/man/systemd.network.html#VendorClassIdentifier= systemd.network]</code>?
= Troubleshooting =
= Troubleshooting =

Revision as of 23:50, 11 May 2019

Stage descriptions

BCCD goes through the following network configuration stages:

  1. Live mode
    1. Initial boot:
      1. Try to obtain an IP address from a BCCD DHCP server
      2. If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
    2. Head node: Upon user request, start DHCP server that will answer requests only from other BCCD systems
  2. Liberated mode
    1. Initial boot:
      1. Try to obtain an IP address from a BCCD DHCP server
      2. If no BCCD DHCP servers are available, obtain an IP address from any DHCP server
    2. Diskless boot: Upon user request, start DHCP server that will answer requests from diskless BCCD systems on only a given interface

Open questions:

  1. Should we continue using bccd-identifier or switch to using the standard vendor-class-identifier that can be provided via systemd.network?

Troubleshooting

RTNETLINK answers: File exists

If you get an error like this:

RTNETLINK answers: File exists
Failed to bring up eth1.

Try flushing that interface and replumbing it:

$ sudo ip addr flush dev eth1
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox