General - Revision history

Support at 19:37, 9 May 2017

2017-05-09T19:37:55Z

Support at 19:36, 9 May 2017

2017-05-09T19:36:04Z

Show changes

Support: Support moved page Network to General without leaving a redirect

2017-05-09T19:26:23Z

Support moved page Network to General without leaving a redirect

Support at 02:07, 9 May 2017

2017-05-09T02:07:19Z

Support at 23:24, 8 May 2017

2017-05-08T23:24:12Z

Support: /* Quick Reference */

2017-05-08T23:18:45Z

‎Quick Reference

Support: /* Quick Reference */

2017-05-08T23:17:32Z

‎Quick Reference

Support at 23:16, 8 May 2017

2017-05-08T23:16:38Z

Support at 23:15, 8 May 2017

2017-05-08T23:15:40Z

Support at 23:12, 8 May 2017

2017-05-08T23:12:59Z

@@ Line 3: / Line 3: @@
 ===  Network Setup (ent 7) ===
-. determine interface and connection name setup for the subsequent nmcli commands, use what it shows for the Connection name (Device and Connection name are normally the same, but not always the same - this needs to be checked to verify what to use).
+. determine interface and connection name setup for the subsequent nmcli commands, use what it shows for the Connection name (Device and Connection name are normally the same, but not always the same - this needs to be checked to verify what to use).<br>
 Note: "show" is a default argument in most cases, and does not need to be specified, unless other "show" arguments/details are needed (as in: nmcli dev show eno16777728)
   # nmcli dev
@@ Line 30: / Line 30: @@
   NETMASK=255.255.255.0
-b. configure the default gateway and disable the dynamic link-local (DHCP network) address in /etc/sysconfig/network
+b. configure the default gateway and disable the dynamic link-local (DHCP network) address in /etc/sysconfig/network<br>
 Note: ent 6 defaults to/prefers quotes around the params, i.e. GATEWAY="172.100.130.1"
   GATEWAY=172.100.130.1
@@ Line 56: / Line 56: @@
 ===  Changing the IP (ent 7) ===
-. set the new IP and netmask
+. set the new IP and netmask<br>
 Note: if the IP is not getting set, please check or go through the Network Setup steps (above), specifically see the note on the default setting with DHCP/manual mode
   # nmcli con mod eno16777728 ipv4.addresses 172.100.200.140/24 ipv4.gateway 172.100.200.1
@@ Line 63: / Line 63: @@
   # nmcli con mod eno16777728 ipv4.gateway 172.100.200.1
-. restart networking
+. restart networking<br>
 Note: this has worked remotely over ssh, as long as the two commands are entered together as per this example, otherwise doing the single down command will cause you to lose your connection and require console access to resolve/fix
   # nmcli con down eno16777728 ; nmcli con up eno16777728
 ===  Changing the IP (before ent 7) ===
-. set the new IP and netmask in the ifcfg-interface file (usually ifcfg-eth0) under /etc/sysconfig/network-scripts/
+. set the new IP and netmask in the ifcfg-interface file (usually ifcfg-eth0) under /etc/sysconfig/network-scripts/<br>
 Note: ent 6 defaults to/prefers quotes around the params, i.e. NETMASK="255.255.255.0", ent 6 also introduced CIDR notation, ex; PREFIX="24" to replace the old/longer netmask convention (NETMASK="255.255.255.0")
   IPADDR=172.200.110.140
   NETMASK=255.255.255.0
-. set the new default gateway in /etc/sysconfig/network
+. set the new default gateway in /etc/sysconfig/network<br>
 Note: ent 6 defaults to/prefers quotes around the params, i.e. GATEWAY="172.100.130.1"
   GATEWAY=172.100.130.1
@@ Line 80: / Line 80: @@
 .100.200.140   ks-c7a.lab.example.com ks-c7a
-. restart networking
+. restart networking<br>
 Note: recommended to use "&" when connected remotely so the command will continue after the network gets disconnected (your session is normally not lost in this case, and you would normally stay connected)
   # service network restart &
@@ Line 88: / Line 88: @@
   # nmcli con mod eno16777728 +ipv4.addresses 172.100.200.140/24
-. restart networking
+. restart networking<br>
 Note: this has worked remotely over ssh, as long as the two commands are entered together as per this example, otherwise doing the single down command will cause you to lose your connection and require console access to resolve/fix
   # nmcli con down eno16777728 ; nmcli con up eno16777728
@@ Line 99: / Line 99: @@
   ONPARENT="yes"
-. restart networking
+. restart networking<br>
 Note: recommended to use & when connected remotely so the command will continue after the network gets disconnected (your session is normally not lost in this case, and you would normally stay connected)
   # service network restart &

@@ Line 3: / Line 3: @@
 ===  Network Setup (ent 7) ===
-. determine interface and connection name setup, for the subsequent nmcli commands, use what it shows for the Connection name (Device and Connection name are normally the same, but not always the same, this needs to be checked to verify what to use).
+. determine interface and connection name setup for the subsequent nmcli commands, use what it shows for the Connection name (Device and Connection name are normally the same, but not always the same - this needs to be checked to verify what to use).
   # nmcli dev
 . configure the interface, IP, and gateway (defaults to "automatic" (DHCP), change to "manual" to be able to configure static parameters - settings saved in an ifcfg-interface file in /etc/sysconfig/network-scripts/, in this example; ifcfg-eno16777728)
   # nmcli con mod eno16777728 ipv4.method manual ipv4.addresses 172.100.200.140/24 ipv4.gateway 172.100.200.1
-. configure hostname (saved in /etc/hostname) and domain (saved in an ifcfg-interface file in /etc/sysconfig/network-scripts/)
+. configure hostname (saved in /etc/hostname) and domain (saved in an ifcfg-interface file in /etc/sysconfig/network-scripts/ and in /etc/resolv.conf)
   # nmcli gen hostname ks-c7a.lab.example.com
   # nmcli con mod eno16777728 ipv4.dns-search lab.example.com
-. configure DNS servers (see Data Center Services page for the DNS servers to use for each data center - saved in an ifcfg-interface file in /etc/sysconfig/network-scripts/)
+. configure DNS servers ((use DNS servers appropriate for your internet provider, for your own internal network, or for your local data center - saved in an ifcfg-interface file in /etc/sysconfig/network-scripts/ and in /etc/resolv.conf)
   # nmcli con mod eno16777728 ipv4.dns 172.100.170.90,172.100.130.90
@@ Line 44: / Line 44: @@
 c. set the IP and hostname info in /etc/hosts (required for 'hostname -s' and other types of resolution)
-.100.200.140   ks-c7a ks-c7a.lab.example.com
+.100.200.140   ks-c7a.lab.example.com ks-c7a
-. configure the DNS servers in /etc/resolv.conf (see Data Center Services page for the DNS servers to use for each data center)
+. configure the DNS servers in /etc/resolv.conf (use DNS servers appropriate for your internet provider, for your own internal network, or for your local data center)
   nameserver 172.100.170.90
   nameserver 172.100.130.90
@@ Line 93: / Line 93: @@
 . restart networking
-Note: this has worked remotely over ssh, and long as the two commands are entered together as per this example, otherwise doing the single down command will cause you to lose your connection and require console access to resolve/fix
+Note: this has worked remotely over ssh, as long as the two commands are entered together as per this example, otherwise doing the single down command will cause you to lose your connection and require console access to resolve/fix
   # nmcli con down eno16777728 ; nmcli con up eno16777728
@@ Line 110: / Line 110: @@
 ===  Adding Static Routes (ent 7) ===
-Set the address range and gateway address (saved in an route-interface file in /etc/sysconfig/network-scripts/, in this example; route-eno16777728)
+Set the address range and gateway address (saved in a route-interface file in /etc/sysconfig/network-scripts/, in this example; route-eno16777728)
   # nmcli con mod eno16777728 ipv4.routes "172.200.210.0/24 172.200.210.120"
@@ Line 128: / Line 128: @@
 ===  Multi-NIC Routing (before ent 7) ===
-Before Enterprise 7, since we could not have a gateway (that works) per interface (even though it lets you set a gateway in every interface config file: which it uses to overwrite the default gateway), we have to set the default gateway to the outside or customer facing network (since we cannot possibly know all IP's/networks these connections would be coming from), and then set static routes to every possible network and host it needs access to for our inside network. These are examples for /etc/sysconfig/network-scripts/route-eth1 (where the eth0/default is the primary/outside/customer network, and eth1 in the secondary/internal/private network).
+Before Enterprise 7, since we could not have a gateway (that works) per interface (even though it lets you set a gateway in every interface config file: which it uses to overwrite the default gateway), we have to set the default gateway to the outside or customer facing network (since we cannot possibly know all IP's/networks these connections would be coming from), and then set static routes to every possible network and host it needs access to for our inside network. Here is an example for /etc/sysconfig/network-scripts/route-eth1 (where the eth0/default is the primary/outside/customer network, and eth1 is the secondary/internal/private network).
 Static list for NOTEL (example, the NOTEL data center no longer exists)

@@ Line 130: / Line 130: @@
 Before Enterprise 7, since we could not have a gateway (that works) per interface (even though it lets you set a gateway in every interface config file: which it uses to overwrite the default gateway), we have to set the default gateway to the outside or customer facing network (since we cannot possibly know all IP's/networks these connections would be coming from), and then set static routes to every possible network and host it needs access to for our inside network. These are examples for /etc/sysconfig/network-scripts/route-eth1 (where the eth0/default is the primary/outside/customer network, and eth1 in the secondary/internal/private network).
-Static list for TEL (example, the TEL data center no longer exists)
+Static list for NOTEL (example, the NOTEL data center no longer exists)
   # default network (set this for your specific env/stack)
   ADDRESS0=172.200.200.0

@@ Line 300: / Line 300: @@
   # cat /etc/sysconfig/network /etc/sysconfig/network-scripts/ifcfg-e*
-Show IP Configuration (ent 7)
+Show IP Configuration (ent 7)<br>
 Note: run 'nmcli dev' to find the device name
   # nmcli dev

@@ Line 308: / Line 308: @@
   # nmcli con show ens32
-Show Listening Ports (only)
+Show Listening Ports (only)<br>
 Note: the : in the output normally denotes a listening port
   # lsof -nP | grep ":"

← Older revision	Revision as of 19:26, 9 May 2017
(No difference)

← Older revision		Revision as of 23:16, 8 May 2017
Line 124:		Line 124:
	The multi-NIC routing scenario has not yet been tried/tested on Enterprise 7. Things may work correctly based on (possibly) proper gateway settings per NIC (if this works correctly under ent 7). If not, we know how to add static routes on ent 7, and can replicate the configuration for pre-ent 7 envs via Network Manager (nmcli).		The multi-NIC routing scenario has not yet been tried/tested on Enterprise 7. Things may work correctly based on (possibly) proper gateway settings per NIC (if this works correctly under ent 7). If not, we know how to add static routes on ent 7, and can replicate the configuration for pre-ent 7 envs via Network Manager (nmcli).

−	There was some testing done here, we ended up doing the ~~source~~ based ~~routing~~.	+	There was some testing done here, we ended up doing the Source-based Routing (below).

← Older revision		Revision as of 23:15, 8 May 2017
Line 257:		Line 257:

	Reboot when done to properly pick up all the udev/network config changes/etc		Reboot when done to properly pick up all the udev/network config changes/etc
		+
		+
		+	=== Source-based Routing (ent 7) ===
		+	Note: using NetworkManager
		+
		+	In this scenario, the system is using the gateway on the primary NIC. Any incoming packets on the 2nd interface end up going out the primary interface, and packets are not returning to devices on the 2nd network.
		+
		+	Note: table '2' was chosen since this is the 2nd NIC. Names can be used if the proper mapping is set in /etc/iproute2/rt_tables
		+
		+	1. Add policy routing to NetworkManager
		+	# yum install NetworkManager-dispatcher-routing-rules
		+	# systemctl enable NetworkManager-dispatcher.service
		+	# systemctl start NetworkManager-dispatcher.service
		+
		+	2. Add policy rule
		+	Note: ens33 is the 2nd NIC, 10.60.130.250 is the NIC IP
		+	# vi /etc/sysconfig/network-scripts/rule-ens33
		+	iif ens33 table 2
		+	from 10.60.130.250 table 2
		+
		+	3. Add static routes using policy rules (may be able to do this w/nmcli)
		+	Note: 10.60.130.0/24 is the subnet/cidr of the 2nd network, 10.60.130.1 is the gateway
		+	# vi /etc/sysconfig/network-scripts/route-ens33
		+	10.60.130.0/24 dev ens33 table 2
		+	default via 10.60.130.1 dev ens33 table 2
		+
		+	4. Load the new/changed config files
		+	# nmcli connection reload
		+	# nmcli connection down ens33 ; nmcli connection up ens33

@@ Line 1: / Line 1: @@
-===  Enterprise 7 Note
+===  Enterprise 7 Note ===
 Networking drastically changed under Enterprise 7, which now has Network Manager fully integrated (which was recommended to be uninstalled in previous releases when used on a server/static configuration). On 7, the convention is now not to modify any config files (which may be auto-generated, and/or will get overwritten by updates), but to use command-line utilities to modify any of the configuration settings/parameters (which normally does not modify the primary config file, but creates an override config file usually in a separate location).
-===  Network Setup (ent 7)
+===  Network Setup (ent 7) ===
 . determine interface and connection name setup, for the subsequent nmcli commands, use what it shows for the Connection name (Device and Connection name are normally the same, but not always the same, this needs to be checked to verify what to use).
   # nmcli dev
@@ Line 21: / Line 21: @@
-===  Network Setup (before ent 7)
+===  Network Setup (before ent 7) ===
 most of this is common knowledge, but some of these additional steps have been added (moreso) as a comparison to the new ent 7 listing/steps (above)
@@ Line 57: / Line 57: @@
-===  Changing the IP (ent 7)
+===  Changing the IP (ent 7) ===
 . set the new IP and netmask
 Note: if the IP is not getting set, please check or go through the Network Setup steps (above), specifically see the note on the default setting with DHCP/manual mode
@@ Line 70: / Line 70: @@
-===  Changing the IP (before ent 7)
+===  Changing the IP (before ent 7) ===
 . set the new IP and netmask in the ifcfg-interface file (usually ifcfg-eth0) under /etc/sysconfig/network-scripts/
 Note: ent 6 defaults to/prefers quotes around the params, i.e. NETMASK="255.255.255.0", ent 6 also introduced CIDR notation, ex; PREFIX="24" to replace the old/longer netmask convention (NETMASK="255.255.255.0")
@@ Line 88: / Line 88: @@
-===  Adding Additional IP's/Aliases (ent 7)
+===  Adding Additional IP's/Aliases (ent 7) ===
 . add the additional IP
   # nmcli con mod eno16777728 +ipv4.addresses 172.100.200.140/24
@@ Line 97: / Line 97: @@
-===  Adding Additional IP's/Aliases (before ent 7)
+===  Adding Additional IP's/Aliases (before ent 7) ===
 . create an ifcfg-interface:aliasnumber file in /etc/sysconfig/network-scripts/ (ifcfg-eth0:0 for this example), with the following contents
   DEVICE="eth0:0"
@@ Line 109: / Line 109: @@
-===  Adding Static Routes (ent 7)
+===  Adding Static Routes (ent 7) ===
 Set the address range and gateway address (saved in an route-interface file in /etc/sysconfig/network-scripts/, in this example; route-eno16777728)
   # nmcli con mod eno16777728 ipv4.routes "172.200.210.0/24 172.200.210.120"
-===  Adding Static Routes (before ent 7)
+===  Adding Static Routes (before ent 7) ===
 Create a route-interface file (for IPv4), example /etc/sysconfig/network-scripts/route-eth0 (or route-bond0 for a bonding interface);
   ADDRESS0=172.200.210.0
@@ Line 121: / Line 121: @@
-===  Multi-NIC Routing (ent 7)
+===  Multi-NIC Routing (ent 7) ===
 The multi-NIC routing scenario has not yet been tried/tested on Enterprise 7. Things may work correctly based on (possibly) proper gateway settings per NIC (if this works correctly under ent 7). If not, we know how to add static routes on ent 7, and can replicate the configuration for pre-ent 7 envs via Network Manager (nmcli).
@@ Line 127: / Line 127: @@
-===  Multi-NIC Routing (before ent 7)
+===  Multi-NIC Routing (before ent 7) ===
 Before Enterprise 7, since we could not have a gateway (that works) per interface (even though it lets you set a gateway in every interface config file: which it uses to overwrite the default gateway), we have to set the default gateway to the outside or customer facing network (since we cannot possibly know all IP's/networks these connections would be coming from), and then set static routes to every possible network and host it needs access to for our inside network. These are examples for /etc/sysconfig/network-scripts/route-eth1 (where the eth0/default is the primary/outside/customer network, and eth1 in the secondary/internal/private network).
@@ Line 157: / Line 157: @@
-===  Teaming (ent 7)
+===  Teaming (ent 7) ===
 . add the teaming inferface
   # nmcli con add type team con-name team0 ifname team0 config '{"runner": {"name": "loadbalance"}}'
@@ Line 171: / Line 171: @@
-===  Bonding (before ent 7)
+===  Bonding (before ent 7) ===
 Before Enterprise 7, interface Bonding was configured via various config files in /etc/sysconfig/network-scripts/ (this has been rewritten in ent 7 and is now called Teaming), example setup;
@@ Line 237: / Line 237: @@
-===  Renumbering Ports (ent 6)
+===  Renumbering Ports (ent 6) ===
 Example is from a R630 system used as an appliance with 4 ports on the motherboard that had 2 coppper & 2 fiber. For this appliance they wanted the 2 copper ports to be eth0/1 and the fiber be eth2/3, but a recently built system had them designated in reverse. The renaming/mapping went as follows;
   eth0 (fiber)  -> eth2
@@ Line 259: / Line 259: @@
-===  Quick Reference
+===  Quick Reference ===
 past what is shown above, here are a few additional/helpful commands