The physical infrastructure provider’s dashboard provides an overview of the inventory at a glance. To view it, first navigate to Compute → Physical Infrastructure → Providers page from the main navigation on the left, then click your {intersight-provider}.
|
Note
|
The {intersight-provider} does not support targeted refreshing of the inventory. To make sure that the latest information is visible, please perform Configuration → Refresh Relationships and Power States. The statuses should be up-to-date after a few seconds. |
On the main dashboard of {intersight-provider} we can examine lists of:
-
Chassis
-
Servers
-
Switches
Racks and Storages are currently not supported by the {intersight-provider}.
To view a list of the resources discovered through the inventory, click on the respective row of the Relationships table.
To view a list of Chassis provided by the {intersight} system, navigate to the list of Chassis on the main menu of the {intersight-provider}. On the detailed view of Chassis we can examine:
-
Properties (Chassis name, Product Name, Serial Number, Health state,…)
-
Relationships (list of servers and storages associated with the chassis)
-
Management Networks
-
More details about the Chassis Slot
By clicking on the Physical Servers on the {intersight-provider} dashboard row will take you to the list of physical servers:
By clicking on Servers section user is presented with the list of all servers in the {intersight-provider}. By clicking on a specific server, view with detailed information of the server is shown. Set of different information can be examined:
-
Properties (Server name, Model, Product Name, Total memory, CPU total cores, Network Devices,…)
-
Management Networks (list of networks associated with the server)
-
Relationships (details on the host, link to the Physical Infrastructure Provider)
-
Power Management (Power State and health)
-
Firmwares
-
Asset Details (Description, Location)
-
Server Profiles (Assigned and Associated server profiles)
To view a list of Fabric Interconnects provided by the {intersight} system, navigate to the list of Switches on the main menu of the {intersight-provider}.
By clicking on an item on the list of all physical switches (Fabric Interconnects) user is navigated to the details view of the specific network device. Associated networking data can be inspected through this view:
-
Number of ports
-
Health status
-
Description
-
Associated physical servers
-
Details of the management networks
Physical servers may be remotely powered off, powered on or restarted through {product-gui} using {intersight-provider}.
To power off a particular physical server, we first navigate to Compute → Physical Infrastructure → Servers from the navigation on the left. On the server list, we click on the server’s name. This takes us to the server’s summary page, which provides the Power menu and displays the server’s current power state:
We can see that the server is currently powered on. To have it powered off, we click on Power → Power Off. We get a prompt to confirm the selected action. After we click Ok, we will see the status showing the success of sending the request:
The server should be powered off within a few seconds. To see the updated status in the {product-gui}, use the Configuration → Refresh Relationships and Power States, wait a few seconds, then refresh the page in the browser.
Please refer to the [ReleaseNotesIntersight] section for further information about the power management actions and statuses.
To view a list of the alerts and notifications obtained through the {intersight}'s API, first navigate to the specific provider. By clicking on Monitoring → Timelines it will take you to a view of Timelines for Physical Infrastructure Provider. Under Options you should specify options as given in the figure below and should provide a time period you are interested in.
Currently, there are two groups of events supported by the {intersight} provider: Updates (notifications) and General Activity (alarms). By clicking on a specific element in the timeline under section Data more details are given for the specific element (alert, notification).
User can decommission a server with an action from the Lifecycle menu on the provider. Selected server can be decommissioned as depicted in the figure below.
User can commission a server with an action from the Lifecycle menu on the provider. This way selected servers that have been already decommissioned can be commissioned and therefore made available to a user for further use.
|
Note
|
As soon as the server is recommissioned it takes some time for {intersight} to aggregates all the data from the server (discovery process needs to finish). |
User can assign a server profile with an action from the Intersight menu in the server’s details view in the provider.
By clicking on Intersight → Assign Server Profile user is presented with a list of available server profiles.
Modal window has a drop-down menu that allows user to specify a server profile to be used for the assignment.
After selecting the profile and clicking Assign assignment process is triggered on the {intersight}.
|
Note
|
This process can take couple of minutes due to the process on the {intersight}. Moreover, the {intersight-provider} does not support targeted refreshing of the inventory. To make sure that the latest information is visible, please perform Configuration → Refresh Relationships and Power States. The statuses should be up-to-date after a few seconds. |
After the assignment process is triggered, notification is displayed.
As soon as the assignment process on the {intersight} is finished and the provider refreshes the inventory, the new state is reflected on the list of servers on the {intersight-provider} under Assigned Profile column.
As soon as the assignment process on the {intersight} is finished and the provider refreshes the inventory, the new state is reflected under Server Profile view on the server details view of the {intersight-provider}.
Please refer to the [ReleaseNotesIntersight] section for further information about the server profiles actions and statuses.
User can trigger deployment of a server profile on a server which is already assigned with a server profile. Deployment process can be done on the server details view of the {intersight-provider}.
Just after the deployment process is triggered, notification is displayed.
As soon as the deployment process on the {intersight} is finished and the provider refreshes the inventory, the new state is reflected on the list of servers on the {intersight-provider} under Associated Profile column. This indicated that the server profile has been assigned and deployed.
|
Note
|
This process can take couple of minutes due to the process on the {intersight}. Moreover, the {intersight-provider} does not support targeted refreshing of the inventory. To make sure that the latest information is visible, please perform Configuration → Refresh Relationships and Power States. The statuses should be up-to-date after a few seconds. |
As soon as the deployment process on the {intersight} is finished and the provider refreshes the inventory, the new state is reflected under Server Profile view on the server details view of the {intersight-provider}.
Please refer to the [ReleaseNotesIntersight] section for further information about the server profiles actions and statuses.
User can trigger unassignment of a server profile on a server which has been already deployed using a server profile. Unassigning process can be done on the server details view of the {intersight-provider} by clicking on a menu Intersight → Unassign Server Profile.
Modal window with a server list is displayed with default selection of a server on which user wants to trigger the unassignment process. The process is triggered by clicking on Unassign button on the model window.
Just after the unassignment process is triggered, notification is displayed.
As soon as the unassignment process on the {intersight} is finished and the provider refreshes the inventory, the new state is reflected under Server Profile view on the server details view of the {intersight-provider}.
|
Note
|
This process can take couple of minutes due to the process on the {intersight}. Moreover, the {intersight-provider} does not support targeted refreshing of the inventory. To make sure that the latest information is visible, please perform Configuration → Refresh Relationships and Power States. The statuses should be up-to-date after a few seconds. |
Please refer to the [ReleaseNotesIntersight] section for further information about the server profiles actions and statuses.