PEERDNS=yes
IPV6INIT=no
ifcfg-br0
DEVICE=br0
TYPE=Bridge
ONBOOT=yes
NM_CONTROLLED=no
MTU=1500
BOOTPROTO=none
IPADDR=10.142.0.145
NETMASK=255.255.0.0
About Bridge Port 1 (Operational Network)
br1
does not exist by default when Urika-GX tenant management software is installed. The administrator can
create a bare-bones network configuration for
br1
or produce a fully functioning bridge configuration associated
with network port 1's configuration.
An example of a bare-bones
br1
configuration is shown below:
/etc/sysconfig/network-scripts/ifcfg-br1
DEVICE=br1
TYPE=Bridge
ONBOOT=yes
NM_CONTROLLED=no
MTU=1500
BOOTPROTO=none
About the
utm-host-net
Command
The
utm-host-net
command can be used to modify
the
/etc/sysconfig/network-scripts/ifcfg-
br1
|enp
X
s0f1
files, which are required for setting up
br1
's configuration. The syntax of the command is:
utm-host-net [--opns-enable-force] [--opns-enable-dryrun] [--opns-enable]
ip_addr
,
hwaddr-not-used
,\
netmask
,
default_gateway
,
dns1_server_ip
,
dns2_server_ip
,
domain
NOTE: Comma separated arguments should be passed to the
utm-host-net
command in exactly the
same order as shown in the preceding command syntax.
Procedure
1. Log on to the node that the tenant VM needs to be created on.
2. Identify the Ethernet device.
This can be
eth1
or a variation of
enp
X
s0f1
, where
X
equals {7, 8, ...}.
enp7s0f1
is used as an example in
this procedure.
#
ip addr
...
enp7s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
inet xxx.xx.xx.xx/20 brd 172.30.63.255 scope global enp7s0f1T
The values listed in
ifcfg-enp7s0f1
can be used to auto-generate new files required by the Urika-GX
tenant management process.
Security
S3016
186
