Compare commits
No commits in common. "b9eb69bfcf419b600369c38568d8fb49d5e14462" and "41ea3314c97248546f86d8fbc5d5b7b094336266" have entirely different histories.
b9eb69bfcf
...
41ea3314c9
2 changed files with 5 additions and 8 deletions
|
|
@ -92,14 +92,15 @@ The MAC address is only used in some playbooks to set the interface name.
|
||||||
|
|
||||||
#### L1 setup
|
#### L1 setup
|
||||||
|
|
||||||
To break out a port, create the appropriately named interfaces and delete the original interface, e.g. for swp14:
|
To break out a port, create the appropriately named interfaces and disable the original interface:
|
||||||
|
|
||||||
|
{ "name": "swp14", "enabled": false },
|
||||||
{ "name": "swp14s0", "type": { "value": "25gbase-x-sfp28" } },
|
{ "name": "swp14s0", "type": { "value": "25gbase-x-sfp28" } },
|
||||||
{ "name": "swp14s1", "type": { "value": "25gbase-x-sfp28" } },
|
{ "name": "swp14s1", "type": { "value": "25gbase-x-sfp28" } },
|
||||||
{ "name": "swp14s2", "type": { "value": "25gbase-x-sfp28" } },
|
{ "name": "swp14s2", "type": { "value": "25gbase-x-sfp28" } },
|
||||||
{ "name": "swp14s3", "type": { "value": "25gbase-x-sfp28" } }
|
{ "name": "swp14s3", "type": { "value": "25gbase-x-sfp28" } }
|
||||||
|
|
||||||
Note that for SN2700 switches only odd‐numbered ports may be broken out; besides deleting the original interface the next even‐numbered interface must be disabled as well. The new ports can then be used normally in further configuration.
|
Note that for SN2700 switches only odd‐numbered ports may be broken out; the next even‐numbered port must be disabled as well as the original port in this case. The new ports can be used normally in further configuration.
|
||||||
|
|
||||||
#### L3 setup
|
#### L3 setup
|
||||||
|
|
||||||
|
|
@ -224,8 +225,8 @@ The setup consists of two [firewall nodes](https://netbox.fri.uni-lj.si/search/?
|
||||||
|
|
||||||
For the firewall nodes, configure `mgmt0` and `lo` as usual for L3 devices. Additionally, the firewall nodes should define the following interfaces:
|
For the firewall nodes, configure `mgmt0` and `lo` as usual for L3 devices. Additionally, the firewall nodes should define the following interfaces:
|
||||||
|
|
||||||
{ "name": "lan0", "mac_address": "12:34:56:ab:cd:e0" },
|
{ "name": "lan0" },
|
||||||
{ "name": "lan1", "mac_address": "12:34:56:ab:cd:e1" },
|
{ "name": "lan1" },
|
||||||
{ "name": "mgmt1", "ip_addresses": [{ "address": "fe80::1/64" }] },
|
{ "name": "mgmt1", "ip_addresses": [{ "address": "fe80::1/64" }] },
|
||||||
|
|
||||||
The MAC address should be defined for each interface, as they are renamed by the OS. The `mgmt1` interface is used for synchronizing connection-tracking information and should use the `fe80::1/64` and `fe80::2/64` addresses for the first and second firewall node, respectively.
|
The MAC address should be defined for each interface, as they are renamed by the OS. The `mgmt1` interface is used for synchronizing connection-tracking information and should use the `fe80::1/64` and `fe80::2/64` addresses for the first and second firewall node, respectively.
|
||||||
|
|
|
||||||
|
|
@ -14,7 +14,3 @@ query_filters:
|
||||||
- role: 'firewall'
|
- role: 'firewall'
|
||||||
- role: 'switch'
|
- role: 'switch'
|
||||||
- role: 'server'
|
- role: 'server'
|
||||||
- status: 'active' # everything except 'inventory' and 'failed'
|
|
||||||
- status: 'offline'
|
|
||||||
- status: 'planned'
|
|
||||||
- status: 'staged'
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue