Hi, everyone. My name is Mark McBride and I'm a customer success expert.00:11And in this video, we'll go over how to configure port roles for server discovery within an Intersight managed mode domain. In today's session, we'll cover the following topics. We'll start with a brief overview of Intersight and the value that it brings.00:15We'll subsequently go over the different types of port roles that can be configured within a port policy, and subsequently we'll demonstrate how to configure a port policy and establish server port roles to be able to discover a UCSX blade chassis. So what is Cisco Intersight?00:31Cisco Intersight is our platform designed to deliver unified intelligent management for your Cisco UCS compute infrastructure. Whether your operations are housed in data centers, co location facilities or even distributed edge environments.00:49Intersight is built to help you manage at scale and securely. By leveraging policy driven automation, it ensures consistent operations across your entire global footprint worldwide. We focus on three fundamental pillars to help you simplify your infrastructure life cycle and liberate your IT resources so you can focus more eff.01:05On driving strategic business value.01:25Starting with simplicity, Intersight provides policy driven management across your global infrastructure enabling you to govern complex environments with ease. It also provides clear comprehensive visibility into your operations. You gain real time health and performance insights.01:30Empowering you to diligently monitor your systems with confidence. And in addition, we help you streamline IT operations by automating time consuming tasks such as initial server provisioning, firmware updates, and ongoing life cycle management. Ultimately, Cisco Intersight provides the flexible deployment options and.01:49Seamless ecosystem integration that you need to keep your infrastructure operating smoothly and efficiently.02:09Consequently, when you create a port policy, you establish the port role for the Fabric interconnect. And below is a comprehensive and detailed list of the different port role types that can be configured. Be sure to check the docs for any more information when you are setting your port roles.02:16Today we'll be focusing our own attention on the server ports that are used for either C series standalone servers or B series blade chassis that are connected to each fabric interconnect.02:37Before we jump into the demo, let's take a careful look at our surroundings and the hardware that we'll be configuring to help orient us for the hands on portion of this walkthrough. In our demo, we'll be configuring a pair of 6536 fabric interconnects where we.02:52We have FEA and FFB.03:08Within the FIA module, we intend to allocate and configure ports 17 and 18 so that they operate in the role of server ports. Port 17 will establish a connection to IFM one-one and port 18 will establish a connection to IFM one-two.03:13We'll also apply the exact same configuration to Fabric Interconnect B ensuring that port 17 will connect to IFM two-one and port 18 will connect to IFM two-two. Now let's review step by step how this can be configured within Intersight for verification.03:31We are now logged into Intersight, and we will begin by going to system and targets to view what has currently been claimed within our intersight portal. And here we can see we have an Intersight managed domain that has been claimed for our.03:56Records at this time.04:10If we access this inter site managed domain, we can clearly see that we have FIA and FAB for each of our fabric interconnects that have already been claimed within inter site. From here we can go to operate and then under the Fabric interconnects, we can see that we indeed have.04:15Have each fabric interconnect FIA and FAB.04:33We can select FIA to obtain additional more detailed information about our fabric interconnects specifically. Presently, at this moment we observed clearly that there is only a single port configured to operate as an ethernet uplink. Port 17 and port 18 remain unconfigured, and both are currently in the administrative.04:37Down state for clarity now.04:57If we compare to another port that lacks a transceiver, Intersight will indicate that the other port currently has NO transceiver installed. This confirms that ports 17 and 18 in our system presently include a transceiver.05:04And are wired up and prepared for configuration. For right now, we'll head on over to our policies page and begin revising the currently active port policy and we'll open actions then edit.05:18Here we can view the initial information that was used to construct the port, including the port's policy name, any additional tags that were configured and a description. We can also observe that this policy is being applied to Fabric Interconnect A and Fabric Interconnect.05:41B Consequently, this single policy is applied to each fabric interconnect.05:57In our practical example, we'll have matching ports, so we can utilize the exact same policy to map them to each of the fabric interconnect profiles as described above. If for any reason your ports are not going to match, you could also create a separate port policy, one for FIA and one for.06:04Fib respectively.06:23But now in this demonstration since we're using the same ports, we can apply a single policy for each fabric interconnect. Here we see options for unified ports. If you want to configure ports that could be used for a fiber channel.06:24Let's choose next. And now if you plan to use any kind of breakout ports, you may configure your breakout port options. In this demonstration, we are not using any breakout ports at all for this setup. And then moving on to the main topic of this session, this is the place where you can configure the various kinds of port roles.06:44For your network configuration today.07:04In this section, we will select port number 17 and port number 18, and then select configure to proceed. After that, we will change the role from an unconfigured state to the server role. Leave auto negotiation at the default and will keep manual chassis server numbering disabled today.07:06Should you find it necessary to indicate the chassis identification, you may enable this setting in order to designate the chassis numbering. After that, we will choose the save action to store the port role configuration, and then we will click save a second time to securely apply the policy.07:27At this current stage, we have implemented the changes to the policy, yet we have not yet applied those changes to the Fabric Interconnect today. We can accomplish this by navigating to the profile section where you can see that for the domain profile in question, there is a status indicating that changes have not yet been deployed.07:45You can also obtain further information by opening that domain profile.08:05Or you may choose to view the changes or to view the changes that would be applied when you deploy this profile. Here we can observe that we are transitioning from an unconfigured state to a server roll port designation for port 17 and port 18.08:09So from here we will navigate to the actions menu after which we will select deploy, and this will implement the updated port policy across every fabric interconnect in the system. We'll proceed to deploy.08:26We get a successful message that the deployment has begun, and here we can go to the request page, and now we can carefully monitor the progress to help assure that the deployment of the domain profile succeeds in the system.08:41So this will take a few minutes as the profile is applied to each fabric interconnect.09:01Here we can clearly observe that the deployed domain profile has completed its deployment successfully at this stage today as well. We've also completed chassis inventory, and now we are continuing blade discovery for blades inserted into the UCSX blade chassis within.09:12In this system.09:28While the blade discovery continues to run in the background, let's proceed to review our inventory by pressing into the operate menu and then selecting chassis. And now we can clearly see that we've successfully discovered a UCSX chassis.09:36We can select our chassis, and we can see that it is now beginning to populate the blades that it's going through the blade discovery process in this system today. We can also access the inventory section to review further information about the devices connected to the chassis, including the intelligence.09:51Fabric modules, which are the elements currently used to establish the connection from the chassis up to the fabric interconnects that we configured for the ports serving the server roles as described above.10:11If you navigate to the topology tab, you will also be able to view a graphical representation that clearly shows how every component is wired and interconnected throughout the system, giving you a visual sense of the overall layout and how the pieces relate to one another within the setup. In this view you.10:29You can observe that ports 17 and 18 are connected to IFM ports one/one and one/two for Fabric Interconnect A, and the exact same wiring arrangement applies to Fabric Interconnect B.10:46Port 17 and 18 are cabled up as our server ports to IFM two/one and IFM two/two. That completes our demonstration in which we observed how we are able to configure network ports in order to enable discovery of a UCX blue.11:00Aid chassis. Thanks for watching and hope to see you on the next video.11:19
