Skip to end of metadata
Go to start of metadata
| Create bridge on Proxmox |
|
|---|
| vmnet0: wan1 for mgmt-Broanband ( default ) vmnet2: wan2 for MPLS vmnet3: future use vmnet4: lan1 in DC1-subnet1 10.1.4.0/24 ( 10.dc_number.4.0/24) vmnet5: lan2 in DC1-subnet2 10.1.5.0/24 ( 10.dc_number.5.0/24) vmnet11: lan1 branch1-subnet1 10.11.11.0/24 ( 10.1branch_number.11.0/24) vmnet12: lan2 branch1-subnet2 10.11.12.0/24 ( 10.1branch_number.12.0/24)
|
| troubleshoot second interface down vi /etc/network/interfaces and add the new vmbr2 and vmbr3
root@hp8300:~# more /etc/network/interfaces
. . .
auto lo
iface lo inet loopback
iface eno1 inet manual
iface enp2s0 inet manual
auto vmbr0
iface vmbr0 inet static
address 192.168.0.9/24
gateway 192.168.0.1
bridge-ports eno1
bridge-stp off
bridge-fd 0
auto vmbr1
iface vmbr1 inet dhcp
bridge-ports enp2s0
bridge-stp off
bridge-fd 0
#to SRX320
auto vmbr2
iface vmbr2 inet static
address 192.168.92.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#wan1 MPLS for 128T
auto vmbr3
iface vmbr3 inet static
address 192.168.93.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#wan2 Broadband for 128T
auto vmbr4
iface vmbr4 inet static
address 10.1.4.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#lan1 service1 for 128T
auto vmbr5
iface vmbr5 inet static
address 10.1.5.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#lan2 server2 for 128T
auto vmbr11
iface vmbr11 inet static
address 10.10.11.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#lan1 branch1 for 128T
auto vmbr12
iface vmbr12 inet static
address 10.10.12.1/24
bridge-ports none
bridge-stp off
bridge-fd 0
#lan1 branch2 for 128T
root@hp8300:~#
|
| bring the bridge up | brctl show >>> after creation the bridge are down ( look screenshot above ) ifup vmbr4 ifup vmbr5 ifup vmbr11 ifup vmbr12
root@hp8300:~# brctl show
bridge name bridge id STP enabled interfaces
fwbr104i0 8000.de1d18b636d8 no fwln104i0
tap104i0
fwbr104i1 8000.5a2334bb6246 no fwln104i1
tap104i1
fwbr105i0 8000.725c16ef867f no fwln105i0
tap105i0
fwbr105i1 8000.82028c6a1620 no fwln105i1
tap105i1
fwbr105i2 8000.9e193329f381 no fwln105i2
tap105i2
fwbr107i0 8000.a24bf9f3c51c no fwln107i0
tap107i0
fwbr107i1 8000.363654ec5fa0 no fwln107i1
tap107i1
fwbr107i2 8000.5e55831c4beb no fwln107i2
tap107i2
fwbr107i3 8000.7e3ccd070384 no fwln107i3
tap107i3
vmbr0 8000.6c3be5389335 no eno1
fwpr104p0
fwpr105p0
fwpr107p0
fwpr107p3
vmbr1 8000.6805ca16086f no enp2s0
vmbr11 8000.000000000000 no
vmbr12 8000.000000000000 no
vmbr2 8000.62aeb72ced89 no fwpr104p1
fwpr105p1
fwpr107p1
vmbr3 8000.4eb40554a69a no fwpr105p2
fwpr107p2
vmbr4 8000.000000000000 no
vmbr5 8000.000000000000 no
|
| |
| |
| Create Conductor VM |
|
|---|
| KVM Proxmox | enable NUMA >>> may be not require!!!! numa: 1 ( 0 disable ) Info / explain Link doc: Link |
| Create Router VMs |
|
|---|
| DC | Interface naming convention ( E1000 driver ) nmtui 
or in command line more /etc/sysconfig/network-scripts/ifcfg-ens20
|
| nmcli nmcli connection
[t128@routerdc1_node1 ~]$ nmcli
ens18: connected to wan1_ens18
"Intel 82540EM"
ethernet (e1000), C6:E8:52:33:32:2C, hw, mtu 1500
ip4 default
inet4 192.168.0.217/24
route4 0.0.0.0/0
route4 192.168.0.0/24
inet6 fe80::f63:1ec3:3e1a:8a5d/64
route6 fe80::/64
route6 ff00::/8
ens19: disconnected
"Intel 82540EM"
1 connection available
ethernet (e1000), D6:D8:E9:6E:DE:3F, hw, mtu 1500
ens20: disconnected
"Intel 82540EM"
1 connection available
ethernet (e1000), 5A:FE:25:3E:CD:0B, hw, mtu 1500
ens21: disconnected
"Intel 82540EM"
1 connection available
ethernet (e1000), C6:23:C7:9B:85:B7, hw, mtu 1500
lo: unmanaged
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.0.1
domains: Home
interface: ens18
Use "nmcli device show" to get complete information about known devices and
"nmcli connection show" to get an overview on active connection profiles.
Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage details.
[t128@routerdc1_node1 ~]$ nmcli connection
NAME UUID TYPE DEVICE
wan1_ens18 c49eb85a-7809-309a-811d-ee5e86e904bd ethernet ens18
lan1_ens20 0f27d46f-5483-365a-ab4f-51633ed667b9 ethernet --
lan2_ens21 6ea0d133-50b9-3426-a853-67f7d5f93b66 ethernet --
wan2_ens19 73d89cc8-c202-3213-82de-3cc613b9322c ethernet --
|
| PCIe ID | lshw -c network -businfo
|
| Install 128t |
|
|---|
| t128 / 128tRoutes sudo ip link set dev eth0 up sudo dhclient ip addr |
| systemctl start 128T >> ISSUE |
| https://192.168.0.212 https://192.168.0.212/quick-start |
| Onboard Router |
|
|---|
| on conductor | Create a Router: 1- new Router ( GPS coordinates + conductor IP@ + Inter-node Security Policy= "internal" ) 2- New node: node1 or node2 ( Combo + No need for "Associated Asset ID", will be done automatically with quick-start file ) 3- Device interface ( with PCI address or VMbus on Azure ) 4- Network interface ( IP@ or DHCP, Security Policy: "Internal" + Neighborhoods= "wan1" + Hub ( DC ) or Spoke ( branch) ) 5- Validate and Commit 6- Under Operation get the quick-start file and password
|
| On the router | 7-drag the quick-file file and copy the password in the router: https://x.x.x.x/quick-start |
