Figure 9 Correlating physical slot and Ethernet network names
2. Create a table for your own use, similar to the example table shown below:
l
Base the table on the RHEL port definitions for the relevant server type
described in the "Server node port designations" section.
l
In the Port row, record the enXXX names that correspond with the PCI
slots.
l
Map each line in turn from step 1.a on page 57 output to the corresponding
line in step 1.b on page 58 output.
Note: In R640 (1U1N) and R740xd (2U1N) platforms, the 1 GbE port on the
right is used for management.
For example, the last column in the following table was created using the
information from the 4th line in steps 1.a on page 57 and 1.b on page 58:
VxFlex OS role
... Optional VxFlex OS Data2 2nd port
Port enp6s0f0
Slot name PCIe Slot 6 Port 0
Logical bus address 0000:05:00.0
Physical port on node PCI 10G Left
Speed 0 GB
Virtual IP Address
Virtual IP addresses can be defined for the MDM cluster.
Up to two virtual IP addresses can be defined for the MDM cluster in AMS
deployments. SDCs are then mapped to the MDM cluster's virtual IP addresses,
instead of to static MDM IP addresses. MDMs are sometimes switched during normal
operation of the cluster, and the virtual IP address will always be mapped to the active
MDM. The use of virtual IP addresses simplifies maintenance procedures on the MDM
cluster, because system components communicate via the virtual IP addresses.
Therefore, SDCs do not need to be reconfigured when a server hosting an MDM is
replaced.
Existing systems may be extended to include additional MDMs to a cluster. The new
MDMs should be mapped to the existing virtual IP addresses.
If virtual IP addresses need to be modified, you must use the CLI or the REST API, and
it must be done with extreme caution.
Architecture
Dell EMC VxFlex Ready Node AMS User Guide 59
To Next Page
Loading...
