Hello everyone. My name is Laura and I am a domain engineer specializing in modular systems including the MX 7000 chassis.
Today, we are going to cover how to define V lands to your smart fabric network and associate the VL to a server template to put them into use through open manage enterprise modular or OM For short, this action does require logging into an account with chassis administrator privileges. First, we will navigate to configuration V lands and then quick to find to specify the V land. We wish to use name the VLA as desired and give it a description if you wish select your VA ID or input a range of VA I DS separated by a single dash with no space between currently using commas to separate and add multiple V lands is not supported.
If we need to add multiple V lands to a smarter fabric and they are non sequential, then multiple entries will be required in order to create them. Also, please note that VL 4001 through VA 4020 are reserved for inter chassis communications as well as smart fabric communications. Last select your Q OS to the desired configuration. If more description is needed. Regarding the Q OS levels, you can click the question mark in the upper right corner to open the embedded user manual. This information can also be found in the online user guide for open manage, enterprise modular in the section, smart fabric V LA management, and automated Q OS select finish. And in a few seconds, you'll see that your V land is defined in the VL section. Let's now pivot over to the templates page.
For our next step here, we will associate our newly created va to a server template. This tutorial assumes that we already have a template created. So we will only be editing an existing template. First, select your template, you desire to assign the VA to and then click edit network. The first section is on IO pool assignment which we will cover in another tutorial. Then the second section is for configuring bandwidth settings when using Nick partitioning or N par. The third section which is the one we are concerned with is for V lands, we see a drop down for un tagged networks in which we can select a single, un tagged network, V land and a tagged network where we can assign multiple V lands at once. Click select V land on either option to define the network as desired.
Scroll through the list on the left and select the V lands that you wish to assign to the template. And click the Chevron to move them from the available V lands to the selected V lands. Click finish. In some cases, we will encounter a warning pop up with some om versions regarding virtual identities from assigned IO pools. If we are uncertain in any way, what was altered, select no and go back through the process again to double check that IO pools were not assigned or unassigned. When the template edit is completed, we'll see a pop up in the right corner telling us the network details updated successfully.
Now, the last step is to deploy the template either to a server profile or to a chassis slot profile if it has not been deployed. This topic is covered in another tutorial. Also note that editing V lands from within the fabric section of OME will not save these configurations to the server template and profile for more information. There is another KB article 209969 regarding this topic that completes our tutorial on a, how to define V lands and associate them with a server template. I hope you found this informative and please review the other available tutorials for more information on the MX 7000 operational procedures.
Thank you.
