Deployment Guide
Error! No text of specified style in document.
19 Scaling VCF Domains Beyond a Single MX7000 Chassis | Document ID
6.3.2 Resulting Port Mappings
Though the physical compute sleds were not moved the ports to which the NICs connect will change. The A2
NIC ports on the compute sled installed in slot 1 of chassis one, before the second chassis is added are
shown in figure 9 below. Note that because both IOMs were initially installed in chassis one, that the hosts in
slots 1 and 2 are connected to Eth 1/1/1 and Eth 1/1/3 on both IOMs
Compute to IOM Ports Before Expansion
Once the second chassis is added and the IOMs are moved (as shown in figure 7 above) the network
manager will update the fabric topology. Part of that update will be to determine the FEM ports to which the
A2 NIC ports of these two compute sleds connect. Keep in mind that the FEMs just provide physical
connections back to the FSE, so ports 1/71/1 and 1/71/2 are actually ports on the FSE. These two compute
sleds were deployed using “Deploy to Device” which means that the configuration elements follow the device
and the VLAN tagging specified in the deployment template will be applied to the A2 ports now connected.
This shows the ports to which the A2 NICs are connected after the reconfiguration of the Fabric.
Compute to IOM Ports After Expansion
If the servers were deployed using the “Deploy to Device” method the OME-M will detect the location of the
device and apply the settings that are contained in the deployment template to the appropriate ports. If the
servers were deployed using the “Deploy to Slot” method the OME-M detects the ports that are now mapped
to that slot. OME-M will then apply the settings that are contained in the deployment template to any server
installed into that slot.