Abstract:
An network controller provides both network controller and management controller functionality. Accordingly, the system host sees, in a single device, both network functionality as well as management functionality. The integration may reduce chip count and provide a more cost effective as well as power efficient platform solution for the network and management functions in a larger system, such as a server with multiple network controllers and multiple network ports.
Abstract:
Aspects of a method and system for matching and repairing network configuration are provided. In this regard, one or more circuits and/or processors may be operable to determine a configuration of one or more parameters in a plurality of devices along a network path, and detect whether any of the one or more parameters are configured such that communication between the plurality of devices is disabled and/or suboptimal. The devices may comprise at least one server and one or more of a network switch, a network bridge, and a router. In instances that one or more parameters are incompatibly or sub-optimally configured, a notification of the incompatibility may be communicated to a network management entity and/or one or more messages may be generated to reconfigure the one or more parameters in one or more of the plurality of devices. The determining and/or detecting may be performed automatically in response to various events.
Abstract:
Certain aspects of a method and system for managing network power policy and configuration of data center bridging may include a network domain that comprises a single logical point of management (LPM) that coordinates operation of one or more devices, such as network interface controllers (NICs), switches, and/or servers in the network domain: The single LPM may be operable to manage one or both of a network power policy and/or a data center bridging (DCB) configuration policy for the network domain.
Abstract:
Distributed Management Task Force (DMTF) management profiles, based on the Common Information Model (CIM) protocol, may be utilized to perform access authentication during opaque management data profile operations based on DMTF/CIM Role Based Authorization (RBA) profile and/or Simple Identity Management (SIM) profiles. Instances of CIM_Identity class may be utilized to enable validation of ownership and/or access rights, via instances of CIM_Role class and/or instances of CIM_Privilege class for a plurality of common users and/or applications. Quota related operations may be performed via “QuotaAffectsElement” associations between instances of CIM_Identity class and instances of the CIM_OpaqueManagementDataService class. The “QuotaAffectsElement” association may comprise “AllocationQuota” and/or “AllocatedBytes” properties to enable tracking and/or validating of quota related information within the opaque management data profile.
Abstract:
Certain aspects of a method and system for managing network power policy and configuration of data center bridging may include a network domain that comprises a single logical point of management (LPM) that coordinates operation of one or more devices, such as network interface controllers (NICs), switches, and/or servers in the network domain: The single LPM may be operable to manage one or both of a network power policy and/or a data center bridging (DCB) configuration policy for the network domain.
Abstract:
Distributed Management Task Force (DMTF) management profiles, based on the Common Information Model (CIM) protocol, may be utilized to perform access authentication during opaque management data profile operations based on DMTF/CIM Role Based Authorization (RBA) profile and/or Simple Identity Management (SIM) profiles. Instances of CIM_Identity class may be utilized to enable validation of ownership and/or access rights, via instances of CIM_Role class and/or instances of CIM_Privilege class for a plurality of common users and/or applications. Quota related operations may be performed via “QuotaAffectsElement” associations between instances of CIM_Identity class and instances of the CIM_OpaqueManagementDataService class. The “QuotaAffectsElement” association may comprise “AllocationQuota” and/or “AllocatedBytes” properties to enable tracking and/or validating of quota related information within the opaque management data profile.
Abstract:
Various embodiments for hyper-channel management are disclosed. One such method is implemented by a network interface controller (NIC) residing in a server. This method involves determining a network component that is operable to create, modify, terminate, or any combination thereof, a hyper-channel. The hyper-channel corresponds to a logical abstraction of network resources associated with the server. The method also involves using the determined network component to manage the hyper-channel.
Abstract:
Various embodiments for hyper-channel management are disclosed. One such method is implemented by a network interface controller (NIC) residing in a server. This method involves determining a network component that is operable to create, modify, terminate, or any combination thereof, a hyper-channel. The hyper-channel corresponds to a logical abstraction of network resources associated with the server. The method also involves using the determined network component to manage the hyper-channel.
Abstract:
Disclosed are various embodiments for configuring a virtual machine. A template for a virtual machine may be generated. The template may include metadata that references data for port profiles for the virtual machine. The template for the virtual machine may be stored in a template repository, and the data for the port profiles may be stored in a port profile database that is separate from the template.
Abstract:
For a platform level data model for indications based event control and data transfer, a management controller may enable performing indications based management operations that may be based on a management service utilizing CIM Indications model. The management controller may enable communication of indications based messaging and/or data. The indications may be triggered based on events generated and/or triggered in a plurality of managed entities. The events generation may be performed dynamically within the plurality of managed entities, or may be initiated via the management controller. The management controller may enable processing of partially generated indications, via the plurality of managed entities, and/or as pass-through router for full indications processed via the plurality of managed entities. The indications based management operations may also comprise subscription related operations wherein the management controller may enable performing processing of subscription requests, modifications, and/or deletions to facilitate external access via the device.