Network resource management system utilizing physical network identification for converging operations
Summary by NHIP
Converging IHS with PNet ID grouping
The converging information handling system receives a hardware configuration management database containing physical network identifier entries and logical partition access information. A tool groups physical adapters by these identifiers to form a converged adapter enabling remote direct memory access communications.
Claim Score by NHIP
Abstract
The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration information, including physical network identifications (PNet IDs), in an HCM database and share the HCM database with the administered IHSs. The administered IHS may be a remote direct memory access (RDMA) enabled network interface controller (RNIC) converging IHS. An RNIC converging tool may extract hardware configuration information, including PNet IDs, from the HCM database. The RNIC converging tool may utilize the hardware configuration information, including PNet IDs, to enable the RNIC converging IHS to communicate over a network with RDMA protocols.
Term
Projected expiry 18 May 2034.
- Priority and filed
- Granted
- Today
- Projected expiry
18 claims: 2 independent, 16 dependent
- 1Broadest claimClaim Score 18, narrow(NHIP)A converging information handling system (IHS) comprising:a processor, and a memory coupled to the processor, the memory including a hypervisor that is configured to: receive from another IHS, via a network, a hardware configuration management (HCM) database that includes configuration information including physical network identifier (PNet IDs) entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries;transmit the HCM database to a remote direct memory access network interface controller (RNIC) converging tool in the memory;wherein the RNIC converging tool extracts configuration information from the HCM database, the configuration information including PNet IDs entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries, thus providing extracted RNIC converging configuration information;wherein the RNIC converging tool groups on a per PNet ID basis particular physical adapter types from the extracted RNIC converging configuration information to form a converged RNIC adapter comprising a first physical adapter having an RNIC adapter type and a second physical adapter, wherein the first physical adapter and the second physical adapter connect to a same physical network and wherein the first physical adapter and the second physical adapter function together to perform RDMA communications over the same physical network;and wherein the RNIC converging tool determines if the converging IHS and the another IHS include the particular physical adapter types to initiate an RDMA communication, and wherein the RNIC converging tool initiates an RDMA connection between the converging IHS and the another IHS if it is determined that the converging IHS and the another IHS include the particular physical adapter types to initiate an RDMA communication.
- 10A computer program product comprising a non-transitory computer readable storage medium having a computer readable program stored therein, wherein the computer readable program, when executed on a converging information handling system (IHS), causes the converging IHS to:receive from another IHS, via a network, a hardware configuration management (HCM) database that includes configuration information including physical network identifier (PNet IDs) entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries;transmit the HCM database to a remote direct memory access network interface controller (RNIC) converging tool in the memory;wherein the RNIC converging tool extracts configuration information from the HCM database, the configuration information including PNet IDs entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries, thus providing extracted RNIC converging configuration information;wherein the RNIC converging tool groups on a per PNet ID basis particular physical adapter types from the extracted RNIC converging configuration information to form a converged RNIC adapter comprising a first physical adapter having an RNIC adapter type and a second physical adapter, wherein the first physical adapter and the second physical adapter connect to a same physical network and wherein the first physical adapter and the second physical adapter function together to perform RDMA communications over the same physical network;and wherein the RNIC converging tool determines if the converging IHS and the another IHS include the particular physical adapter types to initiate an RDMA communication, and wherein the RNIC converging tool initiates an RDMA connection between the converging IHS and the another IHS if it is determined that the converging IHS and the another IHS include the particular physical adapter types to initiate an RDMA communication.
Independent claims2
440 paragraphs in 4 sections, as filed
BACKGROUND
0001The disclosures herein relate generally to information handling systems (IHSs), and more specifically, to IHSs that communicate with other particular IHSs. Multiple IHSs may be connected together via a communication network. Multiple IHSs may also be connected together via multiple communication networks. A hardware configuration management system on a first IHS may share information about the hardware configuration of a second IHS via a communication network.
BRIEF SUMMARY
0002In one embodiment, a method for converging operations in an information handling system (IHS) is provided. The method includes receiving, by a hypervisor of a first IHS, an HCM database that includes configuration information including physical network identifier (PNet IDs) entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries. The method also includes transmitting, by the hypervisor of the first IHS, the HCM database to a remote direct memory access network interface controller (RNIC) converging tool. The method further includes extracting, by the RNIC converging tool, configuration information from the HCM database, the configuration information including PNet IDs entries and respective associated physical adapter type entries and respective associated logical partition (LPAR) access information entries, thus providing extracted RNIC converging configuration information. The method still further includes grouping on a per PNet ID basis, by the RNIC converging tool, particular physical adapter types from the extracted RNIC converging configuration information.
BRIEF DESCRIPTION OF THE DRAWINGS
0003The appended drawings illustrate only exemplary embodiments of the invention and therefore do not limit its scope because the inventive concepts lend themselves to other equally effective embodiments.
0004<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram showing one embodiment of the disclosed hardware configuration management (HCM) system utilizing physical network identifiers (PNet IDs).
0005<figref idref="DRAWINGS">FIG. 2</figref> depicts one embodiment of an HCM database that may be used in the disclosed HCM system.
0006<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram showing another embodiment of the disclosed HCM system utilizing PNet IDs.
0007<figref idref="DRAWINGS">FIG. 4</figref> depicts one embodiment of the HCM database that may be used in the disclosed HCM system.
0008<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of an HCM information handling system (IHS) that may be used in the disclosed HCM system.
0009<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart that shows a representative process flow of an HCM tool that may be used in the disclosed HCM system.
0010<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram showing one embodiment of the disclosed remote direct memory access (RDMA) enabled network adapter controller (RNIC) converging system utilizing PNet IDs.
0011<figref idref="DRAWINGS">FIG. 8</figref> depicts one embodiment of an HCM database that may be used in the disclosed RNIC converging system.
0012<figref idref="DRAWINGS">FIG. 9</figref> is a block diagram showing another embodiment of the disclosed RNIC converging system utilizing PNet IDs.
0013<figref idref="DRAWINGS">FIG. 10</figref> depicts one embodiment of the HCM database that may be used in the disclosed RNIC converging system.
0014<figref idref="DRAWINGS">FIG. 11</figref> is a block diagram of an RNIC converging IHS that may be used in the disclosed RNIC converging system.
0015<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart that shows a representative process flow of an RNIC converging tool that may be used in the disclosed RNIC converging system.
0016<figref idref="DRAWINGS">FIG. 13</figref> is a block diagram showing one embodiment of the disclosed bridging system utilizing PNet IDs.
0017<figref idref="DRAWINGS">FIG. 14</figref> depicts one embodiment of a HCM database that may be used in the disclosed bridging system.
0018<figref idref="DRAWINGS">FIG. 15</figref> is a block diagram showing another embodiment of the disclosed bridging system utilizing PNet IDs.
0019<figref idref="DRAWINGS">FIG. 16</figref> depicts one embodiment of the HCM database that may be used in the disclosed bridging system.
0020<figref idref="DRAWINGS">FIG. 17</figref> is a block diagram of a bridging IHS that may be used in the disclosed bridging system.
0021<figref idref="DRAWINGS">FIG. 18</figref> is a flowchart that shows a representative process flow of a bridging tool that may be used in the disclosed bridging system.
0022<figref idref="DRAWINGS">FIG. 19</figref> is a block diagram showing one embodiment of the disclosed load balancing system utilizing PNet IDs.
0023<figref idref="DRAWINGS">FIG. 20</figref> depicts one embodiment of a HCM database that may be used in the disclosed load balancing system.
0024<figref idref="DRAWINGS">FIG. 21</figref> is a block diagram showing another embodiment of the disclosed load balancing system utilizing PNet IDs.
0025<figref idref="DRAWINGS">FIG. 22</figref> depicts one embodiment of the HCM database that may be used in the disclosed load balancing system.
0026<figref idref="DRAWINGS">FIG. 23</figref> is a block diagram of a load balancing IHS that may be used in the disclosed load balancing system.
0027<figref idref="DRAWINGS">FIG. 24</figref> is a flowchart that shows a representative process flow of a load balancing tool that may be used in the disclosed load balancing system.
0028<figref idref="DRAWINGS">FIGS. 25A and 25B</figref> are block diagrams showing one embodiment of the disclosed privileged network access (PNA) system utilizing PNet IDs.
0029<figref idref="DRAWINGS">FIG. 26</figref> depicts one embodiment of a HCM database that may be used in the disclosed privileged network access (PNA) system.
0030<figref idref="DRAWINGS">FIG. 27</figref> depicts one embodiment of a privileged network access management (PNAM) database that may be used in the disclosed privileged network access system.
0031<figref idref="DRAWINGS">FIGS. 28A and 28B</figref> are block diagrams showing another embodiment of the disclosed privileged network access (PNA) system utilizing PNet IDs.
0032<figref idref="DRAWINGS">FIG. 29</figref> depicts one embodiment of the HCM database that may be used in the disclosed privileged network access (PNA) system.
0033<figref idref="DRAWINGS">FIG. 30</figref> depicts one embodiment of the PNAM database that may be used in the disclosed privileged network access (PNA) system.
0034<figref idref="DRAWINGS">FIG. 31</figref> is a block diagram of a privileged network access IHS that may be used in the disclosed privileged network access (PNA) system.
0035<figref idref="DRAWINGS">FIG. 32</figref> is a block diagram of a privileged network access management (PNAM) IHS that may be used in the disclosed privileged network access system.
0036<figref idref="DRAWINGS">FIG. 33</figref> is a flowchart that shows a representative process flow of a privileged network access tool (PNA) that may be used in the disclosed privileged network access system.
0037<figref idref="DRAWINGS">FIG. 34</figref> is a flowchart that shows a representative process flow of a privileged network access management (PNAM) tool that may be used in the disclosed privileged network access system.
DETAILED DESCRIPTION
0038The disclosed network resource management system employs a hardware configuration management (HCM) information handling system (IHS) that may couple to a single administered IHS or to multiple administered IHSs via an administrative network. An HCM tool in the HCM IHS may generate, modify and store hardware configuration management information in an HCM database in the HCM IHS. The HCM database stores hardware configuration information that may include, but is not limited to, machine serial numbers (MSNs), physical identifications (PIDs), logical identifications (LIDs), types, logical partition (LPAR) access lists and physical network identifications (PNet IDs). A PNet ID is an identifier that informs an IHS with respect to a particular network to which an adapter of the IHS connects, as explained in more detail below.
0039In one embodiment, the HCM tool may transmit the HCM database to a hypervisor agent of an administered IHS via the administrative network. In another embodiment, the HCM tool may transmit the HCM database to a hypervisor agent of an administered IHS via a serial connection. The hypervisor agent of the administered IHS may receive the HCM database and allow the hypervisor of the administered IHS to access the HCM database.
0040In one embodiment, the administered IHS may be a remote direct memory access (RDMA) enabled network interface controller (RNIC) converging IHS. RDMA is remote direct memory access, a technology that enables an IHS to exchange information with another IHS without involving the processor, cache or operating system. The hypervisor of the RNIC converging IHS may transmit the HCM database to an RNIC converging tool in the RNIC converging IHS. The RNIC converging tool may extract hardware configuration information from the HCM database. The RNIC converging tool may utilize the hardware configuration information to enable the RNIC converging IHS to communicate over a network with RDMA protocols, as discussed in more detail below.
0041In another embodiment, the administered IHS may be a bridging IHS. The hypervisor of the bridging IHS may transmit the HCM database to a bridging tool in the bridging IHS. The bridging tool may extract hardware configuration information from the HCM database. The bridging tool may utilize the hardware configuration information to enable the bridging IHS to bridge networks internal to the bridging IHS with networks external to the bridging IHS, as discussed in more detail below.
0042In another embodiment, the administered IHS may be a load balancing IHS. The hypervisor of the load balancing IHS may transmit the HCM database to a load balancing tool in the load balancing IHS. The load balancing tool may extract hardware configuration information from the HCM database. The load balancing tool may utilize the hardware configuration information to enable the load balancing IHS to balance adapter loads in the load balancing IHS. The load balancing tool may also utilize the hardware configuration information to enable the load balancing IHS to failover from a failing adapter to other adapters in the load balancing IHS, as discussed in more detail below.
0043In another embodiment, the administered IHS may be a privileged network access (PNA) IHS. The hypervisor agent of the PNA IHS may receive a privileged network access management (PNAM) database from a PNAM tool in a PNAM IHS via the administrative network. The hypervisor agent of the PNA IHS may allow the hypervisor of the PNA IHS to access the PNAM database. The hypervisor of the PNA IHS may transmit the HCM database and the PNAM database to a PNA tool in the PNA IHS. The PNA tool may extract hardware configuration information from the HCM database and privileged network access information from the PNAM database. The PNA tool may utilize the hardware configuration information and privileged network access information to enable the PNA IHS to limit access to privileged networks, as discussed in more detail below.
0000I. HCM System
0044<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram showing one embodiment of the disclosed hardware configuration management (HCM) system <b>100</b> utilizing physical network identifiers (PNet IDs). HCM system <b>100</b> may utilize network adapter <b>101</b>, administrative network <b>102</b> and network adapter <b>103</b> to couple HCM IHS <b>500</b> to administered IHS <b>104</b>. HCM system <b>100</b> may utilize network adapter <b>101</b>, administrative network <b>102</b> and network adapter <b>105</b> to couple HCM IHS <b>500</b> to administered IHS <b>106</b>. HCM system <b>100</b> may utilize network adapter <b>101</b>, administrative network <b>102</b> and network adapter <b>107</b> to couple HCM IHS <b>500</b> to administered IHS <b>108</b>. HCM system <b>100</b> may utilize network adapter <b>101</b>, administrative network <b>102</b> and network adapter <b>109</b> to couple HCM IHS <b>500</b> to administered IHS <b>110</b>. Administered IHSs <b>104</b>, <b>106</b>, <b>108</b> and <b>110</b> couple via administrative network <b>102</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>200</b> with HCM tool <b>600</b> to the administered IHSs.
0045HCM system <b>100</b> may utilize network adapter <b>111</b> and/or network adapter <b>112</b> via NETWORK A <b>113</b> via network adapter <b>114</b> and/or network adapter <b>115</b> to couple administered IHS <b>104</b> to administered IHS <b>106</b>. HCM system <b>100</b> may utilize network adapter <b>116</b> and/or network adapter <b>117</b> via NETWORK B <b>118</b> via network adapter <b>119</b> and/or network adapter <b>120</b> to couple administered IHS <b>104</b> to administered IHS <b>108</b>. HCM system <b>100</b> may utilize network adapter <b>121</b> and/or network adapter <b>122</b> via NETWORK C <b>123</b> via network adapter <b>124</b> and/or network adapter <b>125</b> to couple administered IHS <b>104</b> to administered IHS <b>108</b>. HCM system <b>100</b> may utilize network adapter <b>121</b> and/or network adapter <b>122</b> via NETWORK C <b>123</b> via network adapter <b>126</b> and/or network adapter <b>127</b> to couple administered IHS <b>104</b> to administered IHS <b>110</b>.
0046In one embodiment, network adapter <b>101</b>, <b>103</b>, <b>105</b>, <b>107</b> and <b>109</b> may be Ethernet (ETH) adapters. Network adapters <b>111</b>, <b>114</b>, <b>116</b>, <b>119</b>, <b>121</b>, <b>124</b> and <b>126</b> may be open system adapters (OSAs). Network adapters <b>112</b>, <b>115</b>, <b>117</b>, <b>120</b>, <b>122</b>, <b>125</b> and network adapter <b>127</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>102</b>, NETWORK A <b>113</b>, NETWORK B <b>118</b> and NETWORK C <b>123</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0047Administered IHS <b>104</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>128</b>-<b>1</b>, LPAR <b>128</b>-<b>2</b>, LPAR <b>128</b>-<b>3</b>, LPAR <b>128</b>-<b>4</b>, LPAR <b>128</b>-<b>5</b>, LPAR <b>128</b>-<b>6</b> and LPAR <b>128</b>-<b>7</b> in administered IHS <b>104</b>. LPAR <b>128</b>-<b>1</b>, LPAR <b>128</b>-<b>2</b>, LPAR <b>128</b>-<b>3</b>, LPAR <b>128</b>-<b>4</b>, LPAR <b>128</b>-<b>5</b>, LPAR <b>128</b>-<b>6</b> and LPAR <b>128</b>-<b>7</b> may respectively include virtual internal network adapter <b>129</b>-<b>1</b>, virtual internal network adapter <b>129</b>-<b>2</b>, virtual internal network adapter <b>129</b>-<b>3</b>, virtual internal network adapter <b>129</b>-<b>4</b>, virtual internal network adapter <b>129</b>-<b>5</b>, virtual internal network adapter <b>129</b>-<b>6</b> and virtual internal network adapter <b>129</b>-<b>7</b>. Virtual internal network adapter <b>129</b>-<b>1</b>, <b>129</b>-<b>2</b>, <b>129</b>-<b>3</b>, <b>129</b>-<b>4</b>, <b>129</b>-<b>5</b>, <b>129</b>-<b>6</b> and <b>129</b>-<b>7</b> may be internal queued direct (IQD) communication adapters and couple to one another via administered IHS <b>104</b> IQD network <b>130</b>. Administered IHS <b>104</b> IQD network <b>130</b> may be a channel, i.e., a bus.
0048LPAR <b>128</b>-<b>1</b>, LPAR <b>128</b>-<b>2</b> and LPAR <b>128</b>-<b>3</b> may include virtual network adapter <b>131</b>-<b>1</b>, virtual network adapter <b>131</b>-<b>2</b> and virtual network adapter <b>131</b>-<b>3</b>, respectively. Virtual network adapter <b>131</b>-<b>1</b>, virtual network adapter <b>131</b>-<b>2</b> and virtual network adapter <b>131</b>-<b>3</b> may couple to network adapter <b>111</b> via a channel. LPAR <b>128</b>-<b>4</b> and LPAR <b>128</b>-<b>5</b> may include virtual network adapter <b>131</b>-<b>4</b> and virtual network adapter <b>131</b>-<b>5</b>, respectively. Virtual network adapter <b>131</b>-<b>4</b> and virtual network adapter <b>131</b>-<b>5</b> may couple to network adapter <b>116</b> via a channel. LPAR <b>128</b>-<b>6</b> and LPAR <b>128</b>-<b>7</b> may include virtual network adapter <b>131</b>-<b>6</b> and virtual network adapter <b>131</b>-<b>7</b>, respectively. Virtual network adapter <b>131</b>-<b>6</b> and virtual network adapter <b>131</b>-<b>7</b> may couple to network adapter <b>121</b> via a channel.
0049LPAR <b>128</b>-<b>1</b>, LPAR <b>128</b>-<b>2</b> and LPAR <b>128</b>-<b>3</b> may include virtual network adapter <b>132</b>-<b>1</b>, virtual network adapter <b>132</b>-<b>2</b> and virtual network adapter <b>132</b>-<b>3</b>, respectively. Virtual network adapter <b>132</b>-<b>1</b>, virtual network adapter <b>132</b>-<b>2</b> and virtual network adapter <b>132</b>-<b>3</b> may couple to network adapter <b>112</b> via a channel. LPAR <b>128</b>-<b>4</b> and LPAR <b>128</b>-<b>5</b> may include virtual network adapter <b>132</b>-<b>4</b> and virtual network adapter <b>132</b>-<b>5</b>, respectively. Virtual network adapter <b>132</b>-<b>4</b> and virtual network adapter <b>132</b>-<b>5</b> may couple to network adapter <b>117</b> via a channel. LPAR <b>128</b>-<b>6</b> and LPAR <b>128</b>-<b>7</b> may include virtual network adapter <b>132</b>-<b>6</b> and virtual network adapter <b>132</b>-<b>7</b>, respectively. Virtual network adapter <b>132</b>-<b>6</b> and virtual network adapter <b>132</b>-<b>7</b> may couple to network adapter <b>122</b> via a channel.
0050<figref idref="DRAWINGS">FIG. 2</figref> depicts one embodiment of HCM database <b>200</b> in the disclosed HCM system <b>100</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>200</b> on a per adapter basis. In one embodiment, for each network adapter in HCM system <b>100</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) for a first port of the network adapter, and the PNet ID for the second port of the network adapter.
0051In one embodiment, the machine serial number (MSN) may be a four byte hex value that identifies the IHS of the adapter. In one embodiment, the physical identification (PID) may be a physical channel ID (PCHID), i.e., the physical card slot in an I/O drawer of an IHS. In another embodiment, the PID may be a virtual channel identification (VCHID), a virtual ID given because internal adapters do not have a physical card slot in an IHS. In one embodiment, the logical identification (LID) may be a logical channel identification (CHPID). In another embodiment, the LID may be a function identification (FID), i.e. logical identification.
0052In one embodiment, the adapter type may be a two byte hex value that identifies the type of adapter. For example, OSA, RNIC and IQD adapters may be 0087, 0008, and 008D, respectively. In one embodiment, the logical partition (LPAR) access list may include eight one byte hex values that represent which LPARs in the IHS may access the particular adapter. In one embodiment, PNet ID 1 may include a four-character string identifying the physical network coupled to the first port of the adapter. PNet ID 2 may include a four-character string identifying the physical network coupled to the second port of the adapter.
0053As shown in HCM database <b>200</b>, the hardware configuration information of adapter <b>111</b> includes MSN of 0000880B, PID of 0008, LID of 00F0, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>111</b> is located in physical channel 0008 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 00F0. Adapter <b>111</b> is a physical OSA network adapter and couples to NETWORK A <b>113</b> on both ports 1 and 2. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b> and <b>128</b>-<b>3</b> of administered IHS <b>104</b> may access adapter <b>111</b> to communicate via NETWORK A <b>113</b>.
0054The hardware configuration information of adapter <b>112</b> includes MSN of 0000880B, PID of 0020, LID of 0200, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>112</b> is located in physical channel 0020 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 0200. Adapter <b>112</b> is a physical RNIC network adapter and couples to NETWORK A <b>113</b> on both ports 1 and 2. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b> and <b>128</b>-<b>3</b> of administered IHS <b>104</b> may access adapter <b>112</b> to communicate via NETWORK A <b>113</b>.
0055The hardware configuration information of adapter <b>116</b> includes MSN of 0000880B, PID of 0009, LID of 00F4, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>116</b> is located in physical channel 0009 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 00F4. Adapter <b>116</b> is a physical OSA network adapter and couples to NETWORK B <b>118</b> on both ports 1 and 2. LPAR <b>128</b>-<b>4</b> and <b>128</b>-<b>5</b> of administered IHS <b>104</b> may access adapter <b>116</b> to communicate via NETWORK B <b>118</b>.
0056The hardware configuration information of adapter <b>117</b> includes MSN of 0000880B, PID of 0021, LID of 0204, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>117</b> is located in physical channel 0021 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 0204. Adapter <b>117</b> is a physical RNIC network adapter and couples to NETWORK B <b>118</b> on both ports 1 and 2. LPAR <b>128</b>-<b>4</b> and <b>128</b>-<b>5</b> of administered IHS <b>104</b> may access adapter <b>117</b> to communicate via NETWORK B <b>118</b>.
0057The hardware configuration information of adapter <b>121</b> includes MSN of 0000880B, PID of 020A, LID of 00F7, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>121</b> is located in physical channel 020A in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 00F7. Adapter <b>121</b> is a physical OSA network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. LPAR <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>121</b> to communicate via NETWORK C <b>123</b>.
0058The hardware configuration information of adapter <b>122</b> includes MSN of 0000880B, PID of 0222, LID of 0207, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>122</b> is located in physical channel 0222 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 0207. Adapter <b>122</b> is a physical RNIC network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. LPAR <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>121</b> to communicate via NETWORK C <b>123</b>.
0059The hardware configuration information of adapter <b>129</b>-<b>1</b> includes MSN of 0000880B, PID of 0111, LID of 04CO<sub>3 </sub>type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>1</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C0. Adapter <b>129</b>-<b>1</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>1</b> to communicate via IQD network <b>130</b>.
0060The hardware configuration information of adapter <b>129</b>-<b>2</b> includes MSN of 0000880B, PID of 0111, LID of 04C1, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>2</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C1. Adapter <b>129</b>-<b>2</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>2</b> to communicate via IQD network <b>130</b>.
0061The hardware configuration information of adapter <b>129</b>-<b>3</b> includes MSN of 0000880B, PID of 0111, LID of 04C2, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>3</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C2. Adapter <b>129</b>-<b>3</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>3</b> to communicate via IQD network <b>130</b>.
0062The hardware configuration information of adapter <b>129</b>-<b>4</b> includes MSN of 0000880B, PID of 0111, LID of 04C3, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>4</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C3. Adapter <b>129</b>-<b>4</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>4</b> to communicate via IQD network <b>130</b>.
0063The hardware configuration information of adapter <b>129</b>-<b>5</b> includes MSN of 0000880B, PID of 0111, LID of 04C4, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>5</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C4. Adapter <b>129</b>-<b>5</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>5</b> to communicate via IQD network <b>130</b>.
0064The hardware configuration information of adapter <b>129</b>-<b>6</b> includes MSN of 0000880B, PID of 0111, LID of 04C5, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>6</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C5. Adapter <b>129</b>-<b>6</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>6</b> to communicate via IQD network <b>130</b>.
0065The hardware configuration information of adapter <b>129</b>-<b>7</b> includes MSN of 0000880B, PID of 0111, LID of 04C6, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>129</b>-<b>7</b> is a virtual adapter with a virtual channel 0111 in administered IHS <b>104</b> and may be identified logically by administered IHS <b>104</b> as 04C6. Adapter <b>129</b>-<b>7</b> is an IQD virtual network adapter and couples to IQD network <b>130</b> on virtual channel 0111. LPAR <b>128</b>-<b>1</b>, <b>128</b>-<b>2</b>, <b>128</b>-<b>3</b>, <b>128</b>-<b>4</b>, <b>128</b>-<b>5</b>, <b>128</b>-<b>6</b> and <b>128</b>-<b>7</b> of administered IHS <b>104</b> may access adapter <b>129</b>-<b>7</b> to communicate via IQD network <b>130</b>.
0066The hardware configuration information of adapter <b>114</b> includes MSN of 8A0024FC, PID of 0007, LID of 0061, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>114</b> is located in physical channel 0007 in administered IHS <b>106</b> and may be identified logically by administered IHS <b>106</b> as 0061. Adapter <b>114</b> is a physical OSA network adapter and couples to NETWORK A <b>113</b> on both ports 1 and 2. Administered IHS <b>106</b> may access adapter <b>114</b> to communicate via NETWORK A <b>113</b>.
0067The hardware configuration information of adapter <b>115</b> includes MSN of 8A0024FC, PID of 0012, LID of 0006, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>115</b> is located in physical channel 0012 in administered IHS <b>106</b> and may be identified logically by administered IHS <b>106</b> as 0006. Adapter <b>115</b> is a physical RNIC network adapter and couples to NETWORK A <b>113</b> on both ports 1 and 2. Administered IHS <b>106</b> may access adapter <b>115</b> to communicate via NETWORK A <b>113</b>.
0068The hardware configuration information of adapter <b>119</b> includes MSN of 578A7CE6, PID of 005A, LID of 0200, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>119</b> is located in physical channel 005A in administered IHS <b>108</b> and may be identified logically by administered IHS <b>108</b> as 0200. Adapter <b>119</b> is a physical OSA network adapter and couples to NETWORK B <b>118</b> on both ports 1 and 2. Administered IHS <b>108</b> may access adapter <b>119</b> to communicate via NETWORK B <b>118</b>.
0069The hardware configuration information of adapter <b>120</b> includes MSN of 578A7CE6, PID of 0402, LID of 001C, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>120</b> is located in physical channel 0402 in administered IHS <b>108</b> and may be identified logically by administered IHS <b>108</b> as 001C. Adapter <b>120</b> is a physical RNIC network adapter and couples to NETWORK B <b>118</b> on both ports 1 and 2. Administered IHS <b>108</b> may access adapter <b>115</b> to communicate via NETWORK B <b>118</b>.
0070The hardware configuration information of adapter <b>124</b> includes MSN of 578A7CE6, PID of 005B, LID of 0201, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>124</b> is located in physical channel 005B in administered IHS <b>108</b> and may be identified logically by administered IHS <b>108</b> as 0201. Adapter <b>124</b> is a physical OSA network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. Administered IHS <b>108</b> may access adapter <b>124</b> to communicate via NETWORK C <b>123</b>.
0071The hardware configuration information of adapter <b>125</b> includes MSN of 578A7CE6, PID of 0444, LID of 001 D, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>125</b> is located in physical channel 0444 in administered IHS <b>108</b> and may be identified logically by administered IHS <b>108</b> as 001D. Adapter <b>125</b> is a physical RNIC network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. Administered IHS <b>108</b> may access adapter <b>125</b> to communicate via NETWORK C <b>123</b>.
0072The hardware configuration information of adapter <b>126</b> includes MSN of A453E85C, PID of 0002, LID of 0105, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>126</b> is located in physical channel 0002 in administered IHS <b>110</b> and may be identified logically by administered IHS <b>110</b> as 0105. Adapter <b>126</b> is a physical OSA network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. Administered IHS <b>110</b> may access adapter <b>126</b> to communicate via NETWORK C <b>123</b>.
0073The hardware configuration information of adapter <b>127</b> includes MSN of A453E85C, PID of 0005, LID of 00A2, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>127</b> is located in physical channel 0005 in administered IHS <b>110</b> and may be identified logically by administered IHS <b>110</b> as 00A2. Adapter <b>127</b> is a physical RNIC network adapter and couples to NETWORK C <b>123</b> on both ports 1 and 2. Administered IHS <b>110</b> may access adapter <b>127</b> to communicate via NETWORK C <b>123</b>.
0074In one embodiment, HCM tool <b>600</b> in HCM IHS <b>500</b> may transmit the HCM database to a hypervisor agent of administered IHS <b>104</b>, <b>106</b>, <b>108</b> and/or <b>110</b> via administrative network <b>102</b>. For example, the hypervisor agent of administered IHS <b>104</b> may receive HCM database <b>200</b> and allow the hypervisor of administered IHS <b>104</b> to extract hardware configuration information from HCM database <b>200</b>. The hypervisor of administered IHS <b>104</b> may configure administered IHS <b>104</b> as shown in HCM database <b>200</b>.
0075In one embodiment, a user may assign PNet ID, “NETA” to NETWORK A <b>113</b>, “NETB” to NETWORK B <b>118</b>, and “NETC” to NETWORK C <b>123</b>, with HCM tool <b>600</b>. A user may use HCM tool <b>600</b> to provision adapters <b>111</b>, <b>112</b> for network A by assigning a PNet ID of “NETA” therewith. If more adapters are required due to bandwidth limitations between administered IHS <b>104</b> and NETWORK A <b>113</b>, additional adapters may easily be provisioned by assigning a PNet ID of “NETA” to the adapter, with HCM tool <b>600</b>.
0076<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram showing one embodiment of the disclosed hardware configuration management (HCM) system <b>300</b> utilizing physical network identifiers (PNet IDs). HCM system <b>300</b> may utilize network adapter <b>301</b>, administrative network <b>302</b> and network adapter <b>303</b> to couple HCM IHS <b>500</b> to administered IHS <b>304</b>. HCM system <b>300</b> may utilize network adapter <b>301</b>, administrative network <b>302</b> and network adapter <b>305</b> to couple HCM IHS <b>500</b> to administered IHS <b>306</b>. HCM system <b>300</b> may utilize network adapter <b>301</b>, administrative network <b>302</b> and network adapter <b>307</b> to couple HCM IHS <b>500</b> to administered IHS <b>308</b>. HCM system <b>300</b> may utilize network adapter <b>301</b>, administrative network <b>302</b> and network adapter <b>309</b> to couple HCM IHS <b>500</b> to administered IHS <b>310</b>. Administered IHSs <b>304</b>, <b>306</b>, <b>308</b> and <b>310</b> couple via administrative network <b>302</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>400</b> with HCM tool <b>600</b> to the administered IHSs.
0077HCM system <b>300</b> may utilize network adapter <b>311</b> and/or network adapter <b>312</b> and/or network adapter <b>313</b> and/or network adapter <b>314</b> via NETWORK A <b>315</b> via network adapter <b>316</b> and/or network adapter <b>317</b> to couple administered IHS <b>304</b> to administered IHS <b>306</b>. HCM system <b>300</b> may utilize network adapter <b>318</b> and/or network adapter <b>319</b> and/or network adapter <b>320</b> and/or network adapter <b>321</b> via NETWORK B <b>322</b> via network adapter <b>323</b> and/or network adapter <b>324</b> to couple administered IHS <b>304</b> to administered IHS <b>306</b>. HCM system <b>300</b> may utilize network adapter <b>318</b> and/or network adapter <b>319</b> and/or network adapter <b>320</b> and/or network adapter <b>321</b> via NETWORK B <b>322</b> via network adapter <b>325</b> and/or network adapter <b>326</b> to couple administered IHS <b>304</b> to administered IHS <b>308</b>. HCM system <b>300</b> may utilize network adapter <b>327</b> and/or network adapter <b>328</b> and/or network adapter <b>329</b> and/or network adapter <b>330</b> via NETWORK C <b>331</b> via network adapter <b>332</b> and/or network adapter <b>333</b> to couple administered IHS <b>304</b> to administered IHS <b>308</b>. HCM system <b>300</b> may utilize network adapter <b>327</b> and/or network adapter <b>328</b> and/or network adapter <b>329</b> and/or network adapter <b>330</b> via NETWORK C <b>331</b> via network adapter <b>334</b> and/or network adapter <b>335</b> and/or network adapter <b>336</b> and/or network adapter <b>337</b> to couple administered IHS <b>304</b> to administered IHS <b>310</b>.
0078In one embodiment, network adapter <b>301</b>, <b>303</b>, <b>305</b>, <b>307</b> and <b>309</b> may be Ethernet (ETH) adapters. Network adapters <b>311</b>, <b>312</b>, <b>316</b>, <b>318</b>, <b>319</b>, <b>323</b>, <b>325</b>, <b>327</b>, <b>328</b>, <b>334</b> and <b>336</b> may be open system adapters (OSAs). Network adapters <b>313</b>, <b>314</b>, <b>317</b>, <b>320</b>, <b>321</b>, <b>326</b>, <b>329</b>, <b>330</b>, <b>333</b>, <b>335</b> and <b>337</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>302</b>, NETWORK A <b>315</b>, NETWORK B <b>322</b> and NETWORK C <b>331</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0079Administered IHS <b>304</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>338</b>-<b>1</b>, LPAR <b>338</b>-<b>2</b>, LPAR <b>338</b>-<b>3</b>, LPAR <b>338</b>-<b>4</b>, LPAR <b>338</b>-<b>5</b>, LPAR <b>338</b>-<b>6</b> and LPAR <b>338</b>-<b>7</b> in administered IHS <b>304</b>. LPAR <b>338</b>-<b>1</b>, LPAR <b>338</b>-<b>2</b>, LPAR <b>338</b>-<b>3</b>, LPAR <b>338</b>-<b>4</b>, LPAR <b>338</b>-<b>5</b>, LPAR <b>338</b>-<b>6</b> and LPAR <b>338</b>-<b>7</b> may respectively include virtual internal network adapter <b>339</b>-<b>1</b>, virtual internal network adapter <b>339</b>-<b>2</b>, virtual internal network adapter <b>339</b>-<b>3</b>, virtual internal network adapter <b>339</b>-<b>4</b>, virtual internal network adapter <b>339</b>-<b>5</b>, virtual internal network adapter <b>339</b>-<b>6</b> and virtual internal network adapter <b>339</b>-<b>7</b>. Virtual internal network adapter <b>339</b>-<b>1</b>, <b>339</b>-<b>2</b>, <b>339</b>-<b>3</b>, <b>339</b>-<b>4</b>, <b>339</b>-<b>5</b>, <b>339</b>-<b>6</b> and <b>339</b>-<b>7</b> may be internal queued direct (IQD) communication adapters and couple to one another via administered IHS <b>304</b> IQD network <b>340</b>. Administered IHS <b>304</b> IQD network <b>340</b> may be a channel, i.e., a bus.
0080LPAR <b>338</b>-<b>1</b>, LPAR <b>338</b>-<b>2</b> and LPAR <b>338</b>-<b>3</b> may include virtual network adapter <b>341</b>-<b>1</b>, virtual network adapter <b>341</b>-<b>2</b> and virtual network adapter <b>341</b>-<b>3</b>, respectively. Virtual network adapter <b>341</b>-<b>1</b>, virtual network adapter <b>341</b>-<b>2</b> and virtual network adapter <b>341</b>-<b>3</b> may couple to network adapter <b>311</b> and network adapter <b>312</b> via a channel. LPAR <b>338</b>-<b>4</b> and LPAR <b>338</b>-<b>5</b> may include virtual network adapter <b>341</b>-<b>4</b> and virtual network adapter <b>341</b>-<b>5</b>, respectively. Virtual network adapter <b>341</b>-<b>4</b> and virtual network adapter <b>341</b>-<b>5</b> may couple to network adapter <b>318</b> and network adapter <b>319</b> via a channel. LPAR <b>338</b>-<b>6</b> and LPAR <b>338</b>-<b>7</b> may include virtual network adapter <b>341</b>-<b>6</b> and virtual network adapter <b>341</b>-<b>7</b>, respectively. Virtual network adapter <b>341</b>-<b>6</b> and virtual network adapter <b>341</b>-<b>7</b> may couple to network adapter <b>327</b> and network adapter <b>328</b> via a channel.
0081LPAR <b>338</b>-<b>1</b>, LPAR <b>338</b>-<b>2</b> and LPAR <b>338</b>-<b>3</b> may include virtual network adapter <b>342</b>-<b>1</b>, virtual network adapter <b>342</b>-<b>2</b> and virtual network adapter <b>342</b>-<b>3</b>, respectively. Virtual network adapter <b>342</b>-<b>1</b>, virtual network adapter <b>342</b>-<b>2</b> and virtual network adapter <b>342</b>-<b>3</b> may couple to network adapter <b>313</b> and network adapter <b>314</b> via a channel. LPAR <b>338</b>-<b>4</b> and LPAR <b>338</b>-<b>5</b> may include virtual network adapter <b>342</b>-<b>4</b> and virtual network adapter <b>342</b>-<b>5</b>, respectively. Virtual network adapter <b>342</b>-<b>4</b> and virtual network adapter <b>342</b>-<b>5</b> may couple to network adapter <b>320</b> and network adapter <b>321</b> via a channel. LPAR <b>338</b>-<b>6</b> and LPAR <b>338</b>-<b>7</b> may include virtual network adapter <b>342</b>-<b>6</b> and virtual network adapter <b>342</b>-<b>7</b>, respectively. Virtual network adapter <b>342</b>-<b>6</b> and virtual network adapter <b>342</b>-<b>7</b> may couple to network adapter <b>329</b> and network adapter <b>330</b> via a channel.
0082<figref idref="DRAWINGS">FIG. 4</figref> depicts one embodiment of HCM database <b>400</b> in the disclosed HCM system <b>300</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>400</b> on a per adapter basis. In one embodiment, for each network adapter in HCM system <b>300</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) for a first port of the network adapter, and the PNet ID for the second port of the network adapter.
0083As shown in HCM database <b>400</b>, the hardware configuration information of adapter <b>311</b> includes MSN of 000F880A, PID of 0008, LID of 00F0, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>311</b> is located in physical channel 0008 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00F0. Adapter <b>311</b> is a physical OSA network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b> and <b>338</b>-<b>3</b> of administered IHS <b>304</b> may access adapter <b>311</b> to communicate via NETWORK A <b>315</b>.
0084The hardware configuration information of adapter <b>312</b> includes MSN of 000F880A, PID of 0009, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>312</b> is located in physical channel 0009 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00F1. Adapter <b>312</b> is a physical OSA network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b> and <b>338</b>-<b>3</b> of administered IHS <b>304</b> may access adapter <b>312</b> to communicate via NETWORK A <b>315</b>.
0085The hardware configuration information of adapter <b>313</b> includes MSN of 000F880A, PID of 020A, LID of 0010, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>313</b> is located in physical channel 020A in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0010. Adapter <b>313</b> is a physical RNIC network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b> and <b>338</b>-<b>3</b> of administered IHS <b>304</b> may access adapter <b>313</b> to communicate via NETWORK A <b>315</b>.
0086The hardware configuration information of adapter <b>314</b> includes MSN of 000F880A, PID of 020B, LID of 0011, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>314</b> is located in physical channel 020B in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0011. Adapter <b>314</b> is a physical RNIC network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b> and <b>338</b>-<b>3</b> of administered IHS <b>304</b> may access adapter <b>314</b> to communicate via NETWORK A <b>315</b>.
0087The hardware configuration information of adapter <b>318</b> includes MSN of 000F880A, PID of 0330, LID of 00F5, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>318</b> is located in physical channel 0330 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00F5. Adapter <b>318</b> is a physical OSA network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. LPAR <b>338</b>-<b>4</b> and <b>338</b>-<b>5</b> of administered IHS <b>304</b> may access adapter <b>318</b> to communicate via NETWORK B <b>322</b>.
0088The hardware configuration information of adapter <b>319</b> includes MSN of 000F880A, PID of 0331, LID of 00F6, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>319</b> is located in physical channel 0331 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00F6. Adapter <b>319</b> is a physical OSA network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. LPAR <b>338</b>-<b>4</b> and <b>338</b>-<b>5</b> of administered IHS <b>304</b> may access adapter <b>319</b> to communicate via NETWORK B <b>322</b>.
0089The hardware configuration information of adapter <b>320</b> includes MSN of 000F880A, PID of 020C, LID of 0015, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>320</b> is located in physical channel 020C in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0015. Adapter <b>320</b> is a physical RNIC network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. LPAR <b>338</b>-<b>4</b> and <b>338</b>-<b>5</b> of administered IHS <b>304</b> may access adapter <b>320</b> to communicate via NETWORK B <b>322</b>.
0090The hardware configuration information of adapter <b>321</b> includes MSN of 000F880A, PID of 020D, LID of 0016, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>321</b> is located in physical channel 020D in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0016. Adapter <b>321</b> is a physical RNIC network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. LPAR <b>338</b>-<b>4</b> and <b>338</b>-<b>5</b> of administered IHS <b>304</b> may access adapter <b>321</b> to communicate via NETWORK B <b>322</b>.
0091The hardware configuration information of adapter <b>327</b> includes MSN of 000F880A, PID of 0111, LID of 00F9, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>327</b> is located in physical channel 0111 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00F9. Adapter <b>327</b> is a physical OSA network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. LPAR <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>327</b> to communicate via NETWORK C <b>331</b>.
0092The hardware configuration information of adapter <b>328</b> includes MSN of 000F880A, PID of 0112, LID of 00FA, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>328</b> is located in physical channel 0112 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 00FA. Adapter <b>328</b> is a physical OSA network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. LPAR <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>328</b> to communicate via NETWORK C <b>331</b>.
0093The hardware configuration information of adapter <b>329</b> includes MSN of 000F880A, PID of 020E, LID of 0019, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>329</b> is located in physical channel 020E in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0019. Adapter <b>329</b> is a physical RNIC network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. LPAR <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>329</b> to communicate via NETWORK C <b>331</b>.
0094The hardware configuration information of adapter <b>330</b> includes MSN of 000F880A, PID of 020F, LID of 0020, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>330</b> is located in physical channel 020F in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 0020. Adapter <b>330</b> is a physical RNIC network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. LPAR <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>330</b> to communicate via NETWORK C <b>331</b>.
0095The hardware configuration information of adapter <b>339</b>-<b>1</b> includes MSN of 000F880A, PID of 0222, LID of 06D0, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>1</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D0. Adapter <b>339</b>-<b>1</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>1</b> to communicate via IQD network <b>340</b>.
0096The hardware configuration information of adapter <b>339</b>-<b>2</b> includes MSN of 000F880A, PID of 0222, LID of 06D1, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>2</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D1. Adapter <b>339</b>-<b>2</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>2</b> to communicate via IQD network <b>340</b>.
0097The hardware configuration information of adapter <b>339</b>-<b>3</b> includes MSN of 000F880A, PID of 0222, LID of 06D2, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>3</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D2. Adapter <b>339</b>-<b>3</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>3</b> to communicate via IQD network <b>340</b>.
0098The hardware configuration information of adapter <b>339</b>-<b>4</b> includes MSN of 000F880A, PID of 0222, LID of 06D3, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>4</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D3. Adapter <b>339</b>-<b>4</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>4</b> to communicate via IQD network <b>340</b>.
0099The hardware configuration information of adapter <b>339</b>-<b>5</b> includes MSN of 000F880A, PID of 0222, LID of 06D4, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>5</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D4. Adapter <b>339</b>-<b>5</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>5</b> to communicate via IQD network <b>340</b>.
0100The hardware configuration information of adapter <b>339</b>-<b>6</b> includes MSN of 000F880A, PID of 0222, LID of 06D5, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>6</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D5. Adapter <b>339</b>-<b>6</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>6</b> to communicate via IQD network <b>340</b>.
0101The hardware configuration information of adapter <b>339</b>-<b>7</b> includes MSN of 000F880A, PID of 0222, LID of 06D6, type of 008D, LPAR access list of 01, 02, 03, 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 with no entries. In other words, adapter <b>339</b>-<b>7</b> is a virtual adapter with a virtual channel 0222 in administered IHS <b>304</b> and may be identified logically by administered IHS <b>304</b> as 06D6. Adapter <b>339</b>-<b>7</b> is an IQD virtual network adapter and couples to IQD network <b>340</b> on virtual channel 0222. LPAR <b>338</b>-<b>1</b>, <b>338</b>-<b>2</b>, <b>338</b>-<b>3</b>, <b>338</b>-<b>4</b>, <b>338</b>-<b>5</b>, <b>338</b>-<b>6</b> and <b>338</b>-<b>7</b> of administered IHS <b>304</b> may access adapter <b>339</b>-<b>7</b> to communicate via IQD network <b>340</b>.
0102The hardware configuration information of adapter <b>316</b> includes MSN of A467E85D, PID of 0005, LID of 00D1, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>316</b> is located in physical channel 0005 in administered IHS <b>306</b> and may be identified logically by administered IHS <b>306</b> as 00D1. Adapter <b>316</b> is a physical OSA network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. Administered IHS <b>306</b> may access adapter <b>316</b> to communicate via NETWORK A <b>315</b>.
0103The hardware configuration information of adapter <b>317</b> includes MSN of A467E85D, PID of 0016, LID of 0CB1, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>317</b> is located in physical channel 0016 in administered IHS <b>306</b> and may be identified logically by administered IHS <b>306</b> as 0CB1. Adapter <b>317</b> is a physical RNIC network adapter and couples to NETWORK A <b>315</b> on both ports 1 and 2. Administered IHS <b>306</b> may access adapter <b>317</b> to communicate via NETWORK A <b>315</b>.
0104The hardware configuration information of adapter <b>323</b> includes MSN of A467E85D, PID of 0006, LID of 00D2, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>323</b> is located in physical channel 0006 in administered IHS <b>306</b> and may be identified logically by administered IHS <b>306</b> as 00D2. Adapter <b>323</b> is a physical OSA network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. Administered IHS <b>306</b> may access adapter <b>323</b> to communicate via NETWORK B <b>322</b>.
0105The hardware configuration information of adapter <b>324</b> includes MSN of A467E85D, PID of 0017, LID of 0CB2, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>324</b> is located in physical channel 0017 in administered IHS <b>306</b> and may be identified logically by administered IHS <b>306</b> as 0CB2. Adapter <b>324</b> is a physical RNIC network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. Administered IHS <b>306</b> may access adapter <b>324</b> to communicate via NETWORK B <b>322</b>.
0106The hardware configuration information of adapter <b>325</b> includes MSN of 007A0052, PID of 00A1, LID of 00F0, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>325</b> is located in physical channel 00A1 in administered IHS <b>308</b> and may be identified logically by administered IHS <b>308</b> as 00F0. Adapter <b>325</b> is a physical OSA network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. Administered IHS <b>308</b> may access adapter <b>325</b> to communicate via NETWORK B <b>322</b>.
0107The hardware configuration information of adapter <b>326</b> includes MSN of 007A0052, PID of 00D1, LID of 00F1, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>326</b> is located in physical channel 00D1 in administered IHS <b>308</b> and may be identified logically by administered IHS <b>308</b> as 00F1. Adapter <b>326</b> is a physical RNIC network adapter and couples to NETWORK B <b>322</b> on both ports 1 and 2. Administered IHS <b>308</b> may access adapter <b>326</b> to communicate via NETWORK B <b>322</b>.
0108The hardware configuration information of adapter <b>332</b> includes MSN of 007A0052, PID of 00A2, LID of 00F2, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>332</b> is located in physical channel 00A2 in administered IHS <b>308</b> and may be identified logically by administered IHS <b>308</b> as 00F2. Adapter <b>332</b> is a physical OSA network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>308</b> may access adapter <b>332</b> to communicate via NETWORK C <b>331</b>.
0109The hardware configuration information of adapter <b>333</b> includes MSN of 007A0052, PID of 00D2, LID of 00F3, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>333</b> is located in physical channel 00D2 in administered IHS <b>308</b> and may be identified logically by administered IHS <b>308</b> as 00F3. Adapter <b>333</b> is a physical RNIC network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>308</b> may access adapter <b>333</b> to communicate via NETWORK C <b>331</b>.
0110The hardware configuration information of adapter <b>334</b> includes MSN of C6200070, PID of 0016, LID of 00CA, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>334</b> is located in physical channel 0016 in administered IHS <b>310</b> and may be identified logically by administered IHS <b>310</b> as 00CA. Adapter <b>334</b> is a physical OSA network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>310</b> may access adapter <b>334</b> to communicate via NETWORK C <b>331</b>.
0111The hardware configuration information of adapter <b>335</b> includes MSN of C6200070, PID of 0032, LID of 00CB, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>335</b> is located in physical channel 0032 in administered IHS <b>310</b> and may be identified logically by administered IHS <b>310</b> as 00CB. Adapter <b>335</b> is a physical RNIC network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>310</b> may access adapter <b>335</b> to communicate via NETWORK C <b>331</b>.
0112The hardware configuration information of adapter <b>336</b> includes MSN of C6200070, PID of 0022, LID of 00CC, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>336</b> is located in physical channel 0022 in administered IHS <b>310</b> and may be identified logically by administered IHS <b>310</b> as 00CC. Adapter <b>336</b> is a physical OSA network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>310</b> may access adapter <b>336</b> to communicate via NETWORK C <b>331</b>.
0113The hardware configuration information of adapter <b>337</b> includes MSN of C6200070, PID of 000A, LID of 00CD, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>337</b> is located in physical channel 000A in administered IHS <b>310</b> and may be identified logically by administered IHS <b>310</b> as 00CD. Adapter <b>337</b> is a physical RNIC network adapter and couples to NETWORK C <b>331</b> on both ports 1 and 2. Administered IHS <b>310</b> may access adapter <b>337</b> to communicate via NETWORK C <b>331</b>.
0114In one embodiment, HCM tool <b>600</b> in HCM IHS <b>500</b> may transmit the HCM database to a hypervisor agent of administered IHS <b>104</b>, <b>106</b>, <b>108</b> and/or <b>110</b> via administrative network <b>102</b>. For example, the hypervisor agent of administered IHS <b>104</b> may receive HCM database <b>200</b> and allow the hypervisor of administered IHS <b>104</b> to extract hardware configuration information from HCM database <b>400</b>. The hypervisor of administered IHS <b>104</b> may configure administered IHS <b>104</b> as shown in HCM database <b>400</b>.
0115<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram of an HCM information handling system (IHS) <b>500</b> that may be used in the disclosed HCM system. HCM IHS <b>500</b> includes a processor <b>505</b> that may include multiple cores. HCM IHS <b>500</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. HCM IHS <b>500</b> includes a bus <b>510</b> that couples processor <b>505</b> to memory <b>515</b> via a memory controller <b>520</b> and memory bus <b>525</b>. System memory <b>515</b> may also be referred to as main memory. System memory <b>515</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>505</b> may also include local memory such as L1, L2 and L3 caches. A video graphics controller <b>530</b> couples display <b>535</b> to bus <b>510</b>. Nonvolatile storage <b>540</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>510</b> to provide HCM IHS <b>500</b> with permanent storage of information. System memory <b>515</b> and nonvolatile storage <b>540</b> are both forms of memory stores. Nonvolatile storage <b>540</b> stores an operating system <b>545</b> (OPERATING SYS) that governs operation of HCM IHS <b>500</b>. I/O devices <b>550</b>, such as speakers, a keyboard and a pointing device, couple to bus <b>510</b> via I/O controller <b>555</b> and I/O bus <b>560</b>.
0116One or more expansion busses <b>565</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, couple to bus <b>510</b> to facilitate the connection of peripherals and devices to HCM IHS <b>500</b>. A network interface controller (NIC) <b>570</b> couples to bus <b>510</b> to enable HCM IHS <b>500</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>570</b> may also be called a network communication adapter, network interface adapter, network adapter, network interface or an adapter. NIC <b>570</b> may take many forms. For example, NIC <b>570</b> may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0117While <figref idref="DRAWINGS">FIG. 5</figref> shows one IHS that employs processor <b>505</b>, the IHS may take many forms. For example, HCM IHS <b>500</b> may take the form of a desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. HCM IHS <b>500</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0118HCM IHS <b>500</b> includes a hardware configuration management (HCM) tool computer program product <b>600</b> on digital media <b>575</b> such as a CD, DVD or other media. For simplicity, the term HCM tool will be used below. HCM IHS <b>500</b> may store HCM tool <b>600</b> in nonvolatile storage <b>540</b> as HCM tool <b>600</b>′. HCM IHS <b>500</b> may also store operating system <b>545</b> (OPERATING SYS) and HCM database <b>580</b> in nonvolatile storage <b>540</b>. When HCM IHS <b>500</b> initializes, the IHS loads operating system <b>545</b> into system memory <b>515</b> for execution as operating system <b>545</b>′. HCM IHS <b>500</b> also loads HCM database <b>580</b> and HCM tool <b>600</b>′ into system memory <b>515</b> for execution as HCM database <b>580</b>′ and HCM tool <b>600</b>″, respectively.
0119<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart that shows a representative process flow of an HCM tool <b>600</b> that may be used in the disclosed HCM system. Process flow commences when HCM tool <b>600</b> in HCM IHS <b>500</b> initializes, as per block <b>605</b>. The HCM tool <b>600</b> may determine if HCM database <b>580</b> exists in HCM IHS <b>500</b>, as per block <b>610</b>. If HCM database <b>580</b> exists in HCM IHS <b>500</b>, HCM tool <b>600</b> opens HCM database <b>580</b> for modification, as per block <b>615</b>. However, if HCM database <b>580</b> does not exist in HCM IHS <b>500</b>, HCM tool <b>600</b> generates a blank HCM database <b>580</b> in HCM IHS <b>500</b> and opens the HCM database <b>580</b> for modification, as per block <b>620</b>.
0120HCM database <b>580</b> may store entries on a per adapter basis, i.e., each row in HCM database <b>580</b> may contain information that pertains to a specific network adapter. Process flow continues as HCM tool <b>600</b> checks the entries in HCM database <b>580</b> and determines if rows in HCM database <b>580</b> are assigned physical network identifications (PNet IDs), as per block <b>625</b>. If HCM tool <b>600</b> determines that rows of HCM database <b>580</b> have not been assigned PNet IDs, HCM tool <b>600</b> may generate a PNet ID and assign the particular PNet ID to a particular physical network and store the generated PNet IDs in HCM database <b>580</b>, as per block <b>630</b>. For example, HCM tool <b>600</b> may generate a PNet ID of “NETA” for NETWORK A <b>113</b>, “NETB” for NETWORK B <b>118</b>, and/or “NETC” for NETWORK C <b>123</b>. In one embodiment, a user may input PNet IDs to the HCM tool <b>600</b> and the user may assign particular PNet IDs to particular physical networks with HCM tool <b>600</b>.
0121HCM tool <b>600</b> may provision the network adapters of each administered IHS in the HCM system. HCM tool <b>600</b> may modify rows of HCM database <b>580</b> to include logical partition (LPAR) designations of LPARs in the particular administered IHS that may access each particular network adapter, as per block <b>635</b>. For example, HCM tool <b>600</b> may provision LPARs 01, 02, and 03 of administered IHS <b>104</b> to utilize network adapter <b>111</b>, as shown in the first row of HCM database <b>200</b> in <figref idref="DRAWINGS">FIG. 2</figref>, i.e., the hardware configuration information related to network adapter <b>111</b>. In one embodiment, a user may utilize the HCM tool <b>600</b> to provision the network adapters of each administered IHS in the HCM system. The user may input LPAR designations of LPARs in the particular administered IHS that may access each particular network adapter, to the HCM tool <b>600</b>. The HCM tool <b>600</b> may modify the rows of HCM database <b>580</b> to include the LPAR designations of LPARs in the particular administered IHS that may access each particular network adapter.
0122HCM tool <b>600</b> may then assign PNet IDs to the network adapters of each administered IHS in the HCM system. HCM tool <b>600</b> may modify rows of HCM database <b>580</b> to include PNet IDs of the physical networks to which the particular network adapters connect, as per block <b>640</b>. For example, as shown in <figref idref="DRAWINGS">FIG. 1</figref>, since both ports of network adapter <b>111</b> physically connect to NETWORK A <b>113</b>, HCM tool <b>600</b> may assign PNet ID “NETA” to both ports of network adapter <b>111</b>, by storing, “NETA” in the first row, “PNET ID1” column of HCM database <b>200</b> and by storing, “NETA” in the first row, “PNET ID2” column of HCM database <b>200</b>. In one embodiment, a user may utilize the HCM tool <b>600</b> to assign PNet IDs to network adapters of each administered IHS in the HCM system. The user may input and/or select PNet IDs with HCM tool <b>600</b> and assign the PNet IDs to particular network adapters with HCM tool <b>600</b>. The HCM tool <b>600</b> may then modify the rows of HCM database <b>580</b> to include the assigned PNet IDs with the particular network adapter.
0123If HCM tool <b>600</b> determines that rows of HCM database <b>580</b> have been assigned PNet IDs, as per block <b>625</b>, process flow continues at block <b>645</b>. HCM tool <b>600</b> inspects the configuration of the HCM system that may include the machine serial number (MSN), physical identification (PID), logical identification (LID), type, LPAR access list, PNet ID1 and PNet ID2 on a per adapter basis, as per block <b>645</b>. HCM tool <b>600</b> may also inspect the hardware configuration information of each network adapter in HCM database <b>580</b>.
0124If HCM tool <b>600</b> determines that the HCM system configuration does not match HCM database <b>580</b>, as per block <b>650</b>, HCM tool <b>600</b> updates the information stored in HCM database <b>580</b> with the inspected configuration of the HCM system, as per block <b>655</b>. In one embodiment, a user may view HCM database <b>580</b> with HCM tool <b>600</b> and determine if HCM database <b>580</b> matches the HCM system configuration. If HCM database <b>580</b> does not match the HCM system configuration, the user may input the HCM system configuration to the HCM tool <b>600</b>. HCM tool <b>600</b> may then store the HCM system configuration input by the user to HCM database <b>580</b>.
0125If HCM tool <b>600</b> determines that the HCM system configuration does match HCM database <b>580</b>, as per block <b>650</b>, process flow continues at block <b>660</b>. If HCM tool <b>600</b> determines that HCM database <b>580</b> has been modified and/or generated, as per block <b>660</b>, HCM tool <b>600</b> may transmit HCM database <b>580</b> to any or all administered IHSs, as per block <b>665</b>. For example, as shown in <figref idref="DRAWINGS">FIG. 1</figref>, HCM tool <b>600</b> may transmit HCM database <b>200</b> to administered IHS <b>104</b>, <b>106</b>, <b>108</b> and/or <b>110</b> via administrative network <b>102</b>. In one embodiment, a user may input or select a transmit command in HCM tool <b>600</b>, causing HCM tool <b>600</b> to transmit HCM database <b>580</b> to any or all administered IHSs. In another embodiment HCM tool <b>600</b> may transmit HCM database <b>580</b> to any or all administered IHSs at a user specified time interval. If HCM tool <b>600</b> determines that the HCM database <b>580</b> has not been modified and/or generated, as per block <b>660</b>, process flow continues at block <b>670</b>. Process flow terminates at end block <b>670</b>. Alternatively, process flow may continue at start block <b>605</b>.
0000II. RNIC Converging System
0126<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram showing one embodiment of the disclosed remote direct memory access (RDMA) enabled network adapter controller (RNIC) converging system <b>700</b> utilizing PNet IDs. RNIC converging system <b>700</b> may utilize network adapter <b>701</b>, administrative network <b>702</b> and network adapter <b>703</b> to couple HCM IHS <b>500</b> to administered IHS <b>704</b>. Administered IHS <b>704</b> may also be referred to as RNIC converging IHS <b>704</b>. RNIC converging system <b>700</b> may utilize network adapter <b>701</b>, administrative network <b>702</b> and network adapter <b>705</b> to couple HCM IHS <b>500</b> to administered IHS <b>706</b>. RNIC converging system <b>700</b> may utilize network adapter <b>701</b>, administrative network <b>702</b> and network adapter <b>707</b> to couple HCM IHS <b>500</b> to administered IHS <b>708</b>. RNIC converging system <b>700</b> may utilize network adapter <b>701</b>, administrative network <b>702</b> and network adapter <b>709</b> to couple HCM IHS <b>500</b> to administered IHS <b>710</b>. Administered IHSs <b>704</b>, <b>706</b>, <b>708</b> and <b>710</b> couple via administrative network <b>702</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>800</b> with HCM tool <b>600</b> to the administered IHSs.
0127RNIC converging system <b>700</b> may utilize network adapter <b>711</b> and/or network adapter <b>712</b> via NETWORK A <b>713</b> via network adapter <b>714</b> and/or network adapter <b>715</b> to couple RNIC converging IHS <b>704</b> to administered IHS <b>706</b>. RNIC converging system <b>700</b> may utilize network adapter <b>716</b> and/or network adapter <b>717</b> via NETWORK B <b>718</b> via network adapter <b>719</b> and/or network adapter <b>720</b> to couple RNIC converging IHS <b>704</b> to administered IHS <b>708</b>. RNIC converging system <b>700</b> may utilize network adapter <b>721</b> and/or network adapter <b>722</b> via NETWORK C <b>723</b> via network adapter <b>724</b> and/or network adapter <b>725</b> to couple RNIC converging IHS <b>704</b> to administered IHS <b>708</b>. RNIC converging system <b>700</b> may utilize network adapter <b>721</b> and/or network adapter <b>722</b> via NETWORK C <b>723</b> via network adapter <b>726</b> to couple RNIC converging IHS <b>704</b> to administered IHS <b>710</b>.
0128In one embodiment, network adapter <b>701</b>, <b>703</b>, <b>705</b>, <b>707</b> and <b>709</b> may be Ethernet (ETH) adapters. Network adapters <b>711</b>, <b>714</b>, <b>716</b>, <b>719</b>, <b>721</b>, <b>724</b> and <b>726</b> may be open system adapters (OSAs). Network adapters <b>712</b>, <b>715</b>, <b>717</b>, <b>720</b>, <b>722</b> and <b>725</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>702</b>, NETWORK A <b>713</b>, NETWORK B <b>718</b> and NETWORK C <b>723</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0129RNIC converging IHS <b>704</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>727</b>-<b>1</b>, LPAR <b>727</b>-<b>2</b>, LPAR <b>727</b>-<b>3</b>, LPAR <b>727</b>-<b>4</b>, LPAR <b>727</b>-<b>5</b>, LPAR <b>727</b>-<b>6</b> and LPAR <b>727</b>-<b>7</b> in RNIC converging IHS <b>704</b>. LPAR <b>727</b>-<b>1</b>, LPAR <b>727</b>-<b>2</b> and LPAR <b>727</b>-<b>3</b> may include virtual network adapter <b>728</b>-<b>1</b>, virtual network adapter <b>728</b>-<b>2</b> and virtual network adapter <b>728</b>-<b>3</b>, respectively. Virtual network adapter <b>728</b>-<b>1</b>, virtual network adapter <b>728</b>-<b>2</b> and virtual network adapter <b>728</b>-<b>3</b> may couple to network adapter <b>711</b> via a channel, i.e., a bus. LPAR <b>727</b>-<b>4</b> and LPAR <b>727</b>-<b>5</b> may include virtual network adapter <b>728</b>-<b>4</b> and virtual network adapter <b>728</b>-<b>5</b>, respectively. Virtual network adapter <b>728</b>-<b>4</b> and virtual network adapter <b>728</b>-<b>5</b> may couple to network adapter <b>716</b> via a channel. LPAR <b>727</b>-<b>6</b> and LPAR <b>727</b>-<b>7</b> may include virtual network adapter <b>728</b>-<b>6</b> and virtual network adapter <b>728</b>-<b>7</b>, respectively. Virtual network adapter <b>728</b>-<b>6</b> and virtual network adapter <b>728</b>-<b>7</b> may couple to network adapter <b>721</b> via a channel.
0130LPAR <b>727</b>-<b>1</b>, LPAR <b>727</b>-<b>2</b> and LPAR <b>727</b>-<b>3</b> may include virtual network adapter <b>729</b>-<b>1</b>, virtual network adapter <b>729</b>-<b>2</b> and virtual network adapter <b>729</b>-<b>3</b>, respectively. Virtual network adapter <b>729</b>-<b>1</b>, virtual network adapter <b>729</b>-<b>2</b> and virtual network adapter <b>729</b>-<b>3</b> may couple to network adapter <b>712</b> via a channel. LPAR <b>727</b>-<b>4</b> and LPAR <b>727</b>-<b>5</b> may include virtual network adapter <b>729</b>-<b>4</b> and virtual network adapter <b>729</b>-<b>5</b>, respectively. Virtual network adapter <b>729</b>-<b>4</b> and virtual network adapter <b>729</b>-<b>5</b> may couple to network adapter <b>717</b> via a channel. LPAR <b>727</b>-<b>6</b> and LPAR <b>727</b>-<b>7</b> may include virtual network adapter <b>729</b>-<b>6</b> and virtual network adapter <b>729</b>-<b>7</b>, respectively. Virtual network adapter <b>729</b>-<b>6</b> and virtual network adapter <b>729</b>-<b>7</b> may couple to network adapter <b>722</b> via a channel.
0131<figref idref="DRAWINGS">FIG. 8</figref> depicts one embodiment of HCM database <b>800</b> in the disclosed RNIC converging system <b>700</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>800</b> on a per adapter basis. In one embodiment, for each network adapter in RNIC converging system <b>700</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) for a first port of the network adapter, and the PNet ID for the second port of the network adapter.
0132As shown in HCM database <b>800</b>, the hardware configuration information of adapter <b>711</b> includes MSN of 00D5380C, PID of 0008, LID of 00F0, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>711</b> is located in physical channel 0008 in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 00F0. Adapter <b>711</b> is a physical OSA network adapter and couples to NETWORK A <b>713</b> on both ports 1 and 2. LPAR <b>727</b>-<b>1</b>, <b>727</b>-<b>2</b> and <b>727</b>-<b>3</b> of RNIC converging IHS <b>704</b> may access adapter <b>711</b> to communicate via NETWORK A <b>713</b>.
0133The hardware configuration information of adapter <b>712</b> includes MSN of 00D5380C, PID of 0009, LID of 02F0, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>712</b> is located in physical channel 0009 in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 02F0. Adapter <b>712</b> is a physical RNIC network adapter and couples to NETWORK A <b>713</b> on both ports 1 and 2. LPAR <b>727</b>-<b>1</b>, <b>727</b>-<b>2</b> and <b>727</b>-<b>3</b> of RNIC converging IHS <b>704</b> may access adapter <b>712</b> to communicate via NETWORK A <b>713</b>.
0134The hardware configuration information of adapter <b>716</b> includes MSN of 00D5380C, PID of 020A, LID of 00F4, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>716</b> is located in physical channel 020A in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 00F4. Adapter <b>716</b> is a physical OSA network adapter and couples to NETWORK B <b>718</b> on both ports 1 and 2. LPAR <b>727</b>-<b>4</b> and <b>727</b>-<b>5</b> of RNIC converging IHS <b>704</b> may access adapter <b>716</b> to communicate via NETWORK B <b>718</b>.
0135The hardware configuration information of adapter <b>717</b> includes MSN of 00D5380C, PID of 020B, LID of 02F4, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>717</b> is located in physical channel 020B in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 02F4. Adapter <b>717</b> is a physical RNIC network adapter and couples to NETWORK B <b>718</b> on both ports 1 and 2. LPAR <b>727</b>-<b>4</b> and <b>727</b>-<b>5</b> of RNIC converging IHS <b>704</b> may access adapter <b>717</b> to communicate via NETWORK B <b>718</b>.
0136The hardware configuration information of adapter <b>721</b> includes MSN of 00D5380C, PID of 0330, LID of 00F7, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>721</b> is located in physical channel 0330 in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 00F7. Adapter <b>721</b> is a physical OSA network adapter and couples to NETWORK C <b>723</b> on both ports 1 and 2. LPAR <b>727</b>-<b>6</b> and <b>727</b>-<b>7</b> of RNIC converging IHS <b>704</b> may access adapter <b>721</b> to communicate via NETWORK C <b>723</b>.
0137The hardware configuration information of adapter <b>722</b> includes MSN of 00D5380C, PID of 0331, LID of 02F7, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>722</b> is located in physical channel 0331 in RNIC converging IHS <b>704</b> and may be identified logically by RNIC converging IHS <b>704</b> as 02F7. Adapter <b>722</b> is a physical RNIC network adapter and couples to NETWORK C <b>723</b> on both ports 1 and 2. LPAR <b>727</b>-<b>6</b> and <b>727</b>-<b>7</b> of RNIC converging IHS <b>704</b> may access adapter <b>722</b> to communicate via NETWORK C <b>723</b>.
0138The hardware configuration information of adapter <b>714</b> includes MSN of 0007880A, PID of 020C, LID of 0022, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>714</b> is located in physical channel 020C in administered IHS <b>706</b> and may be identified logically by administered IHS <b>706</b> as 0022. Adapter <b>714</b> is a physical OSA network adapter and couples to NETWORK A <b>713</b> on both ports 1 and 2. Administered IHS <b>706</b> may access adapter <b>714</b> to communicate via NETWORK A <b>713</b>.
0139The hardware configuration information of adapter <b>715</b> includes MSN of 0007880A, PID of 020D, LID of 0023, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>715</b> is located in physical channel 020D in administered IHS <b>706</b> and may be identified logically by administered IHS <b>706</b> as 0023. Adapter <b>715</b> is a physical RNIC network adapter and couples to NETWORK A <b>713</b> on both ports 1 and 2. Administered IHS <b>706</b> may access adapter <b>715</b> to communicate via NETWORK A <b>713</b>.
0140The hardware configuration information of adapter <b>719</b> includes MSN of 003F230A, PID of 0111, LID of 0DA1, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>719</b> is located in physical channel 0111 in administered IHS <b>708</b> and may be identified logically by administered IHS <b>708</b> as 0DA1. Adapter <b>719</b> is a physical OSA network adapter and couples to NETWORK B <b>718</b> on both ports 1 and 2. Administered IHS <b>708</b> may access adapter <b>719</b> to communicate via NETWORK B <b>718</b>.
0141The hardware configuration information of adapter <b>720</b> includes MSN of 003F230A, PID of 0112, LID of 0DA2, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>720</b> is located in physical channel 0112 in administered IHS <b>708</b> and may be identified logically by administered IHS <b>708</b> as 0DA2. Adapter <b>720</b> is a physical RNIC network adapter and couples to NETWORK B <b>718</b> on both ports 1 and 2. Administered IHS <b>708</b> may access adapter <b>720</b> to communicate via NETWORK B <b>718</b>.
0142The hardware configuration information of adapter <b>724</b> includes MSN of 003F230A, PID of 020E, LID of 0024, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>724</b> is located in physical channel 020E in administered IHS <b>708</b> and may be identified logically by administered IHS <b>708</b> as 0024. Adapter <b>724</b> is a physical OSA network adapter and couples to NETWORK C <b>723</b> on both ports 1 and 2. Administered IHS <b>708</b> may access adapter <b>724</b> to communicate via NETWORK C <b>723</b>.
0143The hardware configuration information of adapter <b>725</b> includes MSN of 003F230A, PID of 020F, LID of 0025, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>725</b> is located in physical channel 020F in administered IHS <b>708</b> and may be identified logically by administered IHS <b>708</b> as 0025. Adapter <b>725</b> is a physical RNIC network adapter and couples to NETWORK C <b>723</b> on both ports 1 and 2. Administered IHS <b>708</b> may access adapter <b>725</b> to communicate via NETWORK C <b>723</b>.
0144The hardware configuration information of adapter <b>726</b> includes MSN of 668A2B01, PID of 0117, LID of 06D0, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>726</b> is located in physical channel 0117 in administered IHS <b>710</b> and may be identified logically by administered IHS <b>710</b> as 06D0. Adapter <b>726</b> is a physical OSA network adapter and couples to NETWORK C <b>723</b> on both ports 1 and 2. Administered IHS <b>710</b> may access adapter <b>726</b> to communicate via NETWORK C <b>723</b>.
0145As illustrated in <figref idref="DRAWINGS">FIG. 7</figref>, RNIC converging tool <b>1200</b> may group OSA adapter <b>711</b> with RNIC adapter <b>712</b>. RNIC converging tool <b>1200</b> may sort the adapters by PNet IDs and by type to group OSA and RNIC type adapters together. RNIC converging tool <b>1200</b> may group OSA adapter <b>711</b> with RNIC adapter <b>712</b>, allowing the adapters to function together on NETWORK A <b>713</b>. These grouped adapters, i.e. RNIC converged adapters, allow LPARs to easily utilize the adapters for RDMA communications. RDMA is remote direct memory access, a technology that enables an IHS to exchange information with another IHS without involving the processor, cache or operating system.
0146<figref idref="DRAWINGS">FIG. 9</figref> is a block diagram showing one embodiment of the disclosed remote RNIC converging system <b>900</b> utilizing PNet IDs. RNIC converging system <b>900</b> may utilize network adapter <b>901</b>, administrative network <b>902</b> and network adapter <b>903</b> to couple HCM IHS <b>500</b> to administered IHS <b>904</b>. Administered IHS <b>904</b> may also be referred to as RNIC converging IHS <b>904</b>. RNIC converging system <b>900</b> may utilize network adapter <b>901</b>, administrative network <b>902</b> and network adapter <b>905</b> to couple HCM IHS <b>500</b> to administered IHS <b>906</b>. RNIC converging system <b>900</b> may utilize network adapter <b>901</b>, administrative network <b>902</b> and network adapter <b>907</b> to couple HCM IHS <b>500</b> to administered IHS <b>908</b>. Administered IHSs <b>904</b>, <b>906</b> and <b>908</b> couple via administrative network <b>902</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>1000</b> with HCM tool <b>600</b> to the administered IHSs.
0147RNIC converging system <b>900</b> may utilize network adapter <b>909</b> and/or network adapter <b>910</b> and/or network adapter <b>912</b> and/or network adapter <b>913</b> and/or network adapter <b>914</b> and/or network adapter <b>915</b> and/or network adapter <b>916</b> and/or network adapter <b>917</b> and/or network adapter <b>918</b> and/or network adapter <b>919</b> via NETWORK A <b>920</b> via network adapter <b>921</b> and/or network adapter <b>922</b> and/or network adapter <b>923</b> and/or network adapter <b>924</b> to couple RNIC converging IHS <b>904</b> to administered IHS <b>906</b>. RNIC converging system <b>900</b> may utilize network adapter <b>925</b> and/or network adapter <b>926</b> and/or network adapter <b>927</b> and/or network adapter <b>928</b> and/or network adapter <b>929</b> and/or network adapter <b>930</b> and/or network adapter <b>931</b> and/or network adapter <b>932</b> and/or network adapter <b>933</b> and/or network adapter <b>934</b> via NETWORK B <b>935</b> via network adapter <b>936</b> and/or network adapter <b>937</b> and/or network adapter <b>938</b> and/or network adapter <b>939</b> to couple RNIC converging IHS <b>904</b> to administered IHS <b>908</b>.
0148In one embodiment, network adapter <b>901</b>, <b>903</b>, <b>905</b> and <b>907</b> may be Ethernet (ETH) adapters. Network adapters <b>909</b>, <b>911</b>, <b>913</b>, <b>915</b>, <b>917</b>, <b>918</b>, <b>919</b>, <b>921</b>, <b>923</b>, <b>925</b>, <b>927</b> and <b>929</b> may be open system adapters (OSAs). Network adapters <b>910</b>, <b>912</b>, <b>914</b>, <b>916</b>, <b>922</b>, <b>924</b>, <b>926</b>, <b>928</b>, <b>930</b>, <b>931</b>, <b>932</b>, <b>933</b> and <b>934</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>902</b>, NETWORK A <b>920</b> and NETWORK B <b>935</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0149RNIC converging IHS <b>904</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> in RNIC converging IHS <b>904</b>. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may include virtual network adapters. In one embodiment, the virtual network adapters may be ETH, OSA or RNIC type virtual network adapters.
0150Referring to the HCM database <b>1000</b> of <figref idref="DRAWINGS">FIG. 10</figref> in conjunction with the RNIC converging system <b>900</b> of <figref idref="DRAWINGS">FIG. 9</figref>, LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>909</b> via a channel, i.e., a bus. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>910</b> via a channel.
0151LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b> and LPAR <b>940</b>-<b>7</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b> and LPAR <b>940</b>-<b>7</b> may couple to network adapter <b>911</b> via a channel. LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b> and LPAR <b>940</b>-<b>7</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b> and LPAR <b>940</b>-<b>7</b> may couple to network adapter <b>912</b> via a channel.
0152LPAR <b>940</b>-<b>3</b> may include an OSA type virtual network adapter. The OSA type virtual network adapter of LPAR <b>940</b>-<b>3</b> may couple to network adapter <b>913</b> via a channel. LPAR <b>940</b>-<b>3</b> may include an RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>3</b> may couple to network adapter <b>914</b> via a channel.
0153LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>8</b> and LPAR <b>940</b>-<b>10</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>4</b>, <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>8</b> and LPAR <b>940</b>-<b>10</b> may couple to network adapter <b>915</b> via a channel. LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>8</b> and LPAR <b>940</b>-<b>10</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>4</b>, <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>8</b> and LPAR <b>940</b>-<b>10</b> may couple to network adapter <b>916</b> via a channel.
0154LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may couple to network adapter <b>917</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>918</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>8</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>919</b> via a channel.
0155LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may couple to network adapter <b>925</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may couple to network adapter <b>926</b> via a channel.
0156LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>927</b> via a channel. LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>928</b> via a channel.
0157LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>5</b> and LPAR <b>940</b>-<b>7</b> may each include a respective OSA type virtual network adapter. The OSA type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>5</b> and LPAR <b>940</b>-<b>7</b> may couple to network adapter <b>929</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>5</b> and LPAR <b>940</b>-<b>7</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>5</b> and LPAR <b>940</b>-<b>7</b> may couple to network adapter <b>930</b> via a channel.
0158LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may couple to network adapter <b>931</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>932</b> via a channel.
0159LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>5</b>, LPAR <b>940</b>-<b>6</b>, LPAR <b>940</b>-<b>7</b> and LPAR <b>940</b>-<b>8</b> may couple to network adapter <b>933</b> via a channel. LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, LPAR <b>940</b>-<b>3</b>, LPAR <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may each include a respective RNIC type virtual network adapter. The RNIC type virtual network adapters of LPAR <b>940</b>-<b>1</b>, LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, LPAR <b>940</b>-<b>7</b>, LPAR <b>940</b>-<b>9</b>, LPAR <b>940</b>-<b>10</b> and LPAR <b>940</b>-<b>11</b> may couple to network adapter <b>934</b> via a channel.
0160<figref idref="DRAWINGS">FIG. 10</figref> depicts one embodiment of HCM database <b>1000</b> in the disclosed RNIC converging system <b>900</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>1000</b> on a per adapter basis. In one embodiment, for each network adapter in RNIC converging system <b>900</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) for a first port of the network adapter, and the PNet ID for the second port of the network adapter.
0161As shown in HCM database <b>1000</b>, the hardware configuration information of adapter <b>909</b> includes MSN of 000F3801, PID of 0011, LID of 00F0, type of 0087, LPAR access list of 01, 02, 03, 04, 08, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>909</b> is located in physical channel 0011 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 00F0. Adapter <b>909</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>8</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>909</b> to communicate via NETWORK A <b>920</b>.
0162The hardware configuration information of adapter <b>910</b> includes MSN of 000F3801, PID of 0020, LID of 05C0, type of 0008, LPAR access list of 01, 02, 03, 04, 08, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>910</b> is located in physical channel 0020 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 05C0. Adapter <b>910</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>8</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>910</b> to communicate via NETWORK A <b>920</b>.
0163The hardware configuration information of adapter <b>911</b> includes MSN of 000F3801, PID of 0012, LID of 00F9, type of 0087, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>911</b> is located in physical channel 0012 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 00F9. Adapter <b>911</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b> and <b>940</b>-<b>7</b> of RNIC converging IHS <b>904</b> may access adapter <b>911</b> to communicate via NETWORK A <b>920</b>.
0164The hardware configuration information of adapter <b>912</b> includes MSN of 000F3801, PID of 0021, LID of 05C9, type of 0008, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>912</b> is located in physical channel 0021 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 05C9. Adapter <b>912</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b> and <b>940</b>-<b>7</b> of RNIC converging IHS <b>904</b> may access adapter <b>912</b> to communicate via NETWORK A <b>920</b>.
0165The hardware configuration information of adapter <b>913</b> includes MSN of 000F3801, PID of 0013, LID of 00FE, type of 0087, LPAR access list of 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>913</b> is located in physical channel 0013 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 00FE. Adapter <b>913</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>3</b> of RNIC converging IHS <b>904</b> may access adapter <b>913</b> to communicate via NETWORK A <b>920</b>.
0166The hardware configuration information of adapter <b>914</b> includes MSN of 000F3801, PID of 0022, LID of 05CE, type of 0008, LPAR access list of 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>914</b> is located in physical channel 0022 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 05CE. Adapter <b>914</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>3</b> of RNIC converging IHS <b>904</b> may access adapter <b>914</b> to communicate via NETWORK A <b>920</b>.
0167The hardware configuration information of adapter <b>915</b> includes MSN of 000F3801, PID of 0014, LID of 0100, type of 0087, LPAR access list of 02, 04, 06, 08 and 0A, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>915</b> is located in physical channel 0014 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0100. Adapter <b>915</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>8</b> and <b>940</b>-<b>10</b> of RNIC converging IHS <b>904</b> may access adapter <b>915</b> to communicate via NETWORK A <b>920</b>.
0168The hardware configuration information of adapter <b>916</b> includes MSN of 000F3801, PID of 0023, LID of 0600, type of 0008, LPAR access list of 02, 04, 06, 08 and 0A, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>916</b> is located in physical channel 0023 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0600. Adapter <b>916</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>2</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>8</b> and <b>940</b>-<b>10</b> of RNIC converging IHS <b>904</b> may access adapter <b>916</b> to communicate via NETWORK A <b>920</b>.
0169The hardware configuration information of adapter <b>917</b> includes MSN of 000F3801, PID of 0015, LID of 0106, type of 0087, LPAR access list of 01, 02, 03, 04, 05, 06, 07 and 08, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>917</b> is located in physical channel 0015 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0106. Adapter <b>917</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>7</b> and <b>940</b>-<b>8</b> of RNIC converging IHS <b>904</b> may access adapter <b>917</b> to communicate via NETWORK A <b>920</b>.
0170The hardware configuration information of adapter <b>918</b> includes MSN of 000F3801, PID of 0016, LID of 010F, type of 0087, LPAR access list of 01, 02, 03, 04, 07, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>918</b> is located in physical channel 0016 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 010F. Adapter <b>918</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>7</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>918</b> to communicate via NETWORK A <b>920</b>.
0171The hardware configuration information of adapter <b>919</b> includes MSN of 000F3801, PID of 0017, LID of 0118, type of 0087, LPAR access list of 01, 03, 05, 07, 08, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>919</b> is located in physical channel 0017 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0118. Adapter <b>919</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>7</b>, <b>940</b>-<b>8</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>919</b> to communicate via NETWORK A <b>920</b>.
0172The hardware configuration information of adapter <b>925</b> includes MSN of 000F3801, PID of 0018, LID of 0120, type of 0087, LPAR access list of 01, 02, 03, 04, 05, 06, 07 and 08, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>925</b> is located in physical channel 0018 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0120. Adapter <b>925</b> is a physical OSA network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>7</b> and <b>940</b>-<b>8</b> of RNIC converging IHS <b>904</b> may access adapter <b>925</b> to communicate via NETWORK B <b>935</b>.
0173The hardware configuration information of adapter <b>926</b> includes MSN of 000F3801, PID of 0024, LID of 0606, type of 0008, LPAR access list of 01, 02, 03, 04, 05, 06, 07 and 08, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>926</b> is located in physical channel 0024 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0606. Adapter <b>926</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>7</b> and <b>940</b>-<b>8</b> of RNIC converging IHS <b>904</b> may access adapter <b>926</b> to communicate via NETWORK B <b>935</b>.
0174The hardware configuration information of adapter <b>927</b> includes MSN of 000F3801, PID of 0019, LID of 0129, type of 0087, LPAR access list of 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>927</b> is located in physical channel 0019 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0129. Adapter <b>927</b> is a physical OSA network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>927</b> to communicate via NETWORK B <b>935</b>.
0175The hardware configuration information of adapter <b>928</b> includes MSN of 000F3801, PID of 0025, LID of 060F, type of 0008, LPAR access list of 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>928</b> is located in physical channel 0025 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 060F. Adapter <b>928</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>928</b> to communicate via NETWORK B <b>935</b>.
0176The hardware configuration information of adapter <b>929</b> includes MSN of 000F3801, PID of 001A, LID of 012D, type of 0087, LPAR access list of 01, 03, 05 and 07, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>929</b> is located in physical channel 001A in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 012D. Adapter <b>929</b> is a physical OSA network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>5</b> and <b>940</b>-<b>7</b> of RNIC converging IHS <b>904</b> may access adapter <b>929</b> to communicate via NETWORK B <b>935</b>.
0177The hardware configuration information of adapter <b>930</b> includes MSN of 000F3801, PID of 0026, LID of 0613, type of 0008, LPAR access list of 01, 03, 05 and 07, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>930</b> is located in physical channel 0026 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0613. Adapter <b>930</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>5</b> and <b>940</b>-<b>7</b> of RNIC converging IHS <b>904</b> may access adapter <b>930</b> to communicate via NETWORK B <b>935</b>.
0178The hardware configuration information of adapter <b>931</b> includes MSN of 000F3801, PID of 0027, LID of 0618, type of 0008, LPAR access list of 01, 02, 03, 04, 05, 06, 07 and 08, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>931</b> is located in physical channel 0027 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0618. Adapter <b>931</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>7</b> and <b>940</b>-<b>8</b> of RNIC converging IHS <b>904</b> may access adapter <b>931</b> to communicate via NETWORK B <b>935</b>.
0179The hardware configuration information of adapter <b>932</b> includes MSN of 000F3801, PID of 0028, LID of 0621, type of 0008, LPAR access list of 01, 02, 03, 04, 07, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>932</b> is located in physical channel 0028 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0621. Adapter <b>932</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>7</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>932</b> to communicate via NETWORK B <b>935</b>.
0180The hardware configuration information of adapter <b>933</b> includes MSN of 000F3801, PID of 0029, LID of 062A, type of 0008, LPAR access list of 01, 02, 03, 04, 05, 06, 07 and 08, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>933</b> is located in physical channel 0029 in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 062A. Adapter <b>933</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>5</b>, <b>940</b>-<b>6</b>, <b>940</b>-<b>7</b> and <b>940</b>-<b>8</b> of RNIC converging IHS <b>904</b> may access adapter <b>933</b> to communicate via NETWORK B <b>935</b>.
0181The hardware configuration information of adapter <b>934</b> includes MSN of 000F3801, PID of 002A, LID of 0633, type of 0008, LPAR access list of 01, 02, 03, 04, 07, 09, 0A and 0B, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>934</b> is located in physical channel 002A in RNIC converging IHS <b>904</b> and may be identified logically by RNIC converging IHS <b>904</b> as 0633. Adapter <b>934</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. LPAR <b>940</b>-<b>1</b>, <b>940</b>-<b>2</b>, <b>940</b>-<b>3</b>, <b>940</b>-<b>4</b>, <b>940</b>-<b>7</b>, <b>940</b>-<b>9</b>, <b>940</b>-<b>10</b> and <b>940</b>-<b>11</b> of RNIC converging IHS <b>904</b> may access adapter <b>934</b> to communicate via NETWORK B <b>935</b>.
0182The hardware configuration information of adapter <b>921</b> includes MSN of 03006FF7, PID of 0101, LID of 0F01, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>921</b> is located in physical channel 0101 in administered IHS <b>906</b> and may be identified logically by administered IHS <b>906</b> as 0F01. Adapter <b>921</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. Administered IHS <b>906</b> may access adapter <b>921</b> to communicate via NETWORK A <b>920</b>.
0183The hardware configuration information of adapter <b>922</b> includes MSN of 03006FF7, PID of 0201, LID of 0F02, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>922</b> is located in physical channel 0201 in administered IHS <b>906</b> and may be identified logically by administered IHS <b>906</b> as 0F02. Adapter <b>922</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. Administered IHS <b>906</b> may access adapter <b>922</b> to communicate via NETWORK A <b>920</b>.
0184The hardware configuration information of adapter <b>923</b> includes MSN of 03006FF7, PID of 0102, LID of 0F03, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>923</b> is located in physical channel 0102 in administered IHS <b>906</b> and may be identified logically by administered IHS <b>906</b> as 0F03. Adapter <b>923</b> is a physical OSA network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. Administered IHS <b>906</b> may access adapter <b>923</b> to communicate via NETWORK A <b>920</b>.
0185The hardware configuration information of adapter <b>924</b> includes MSN of 03006FF7, PID of 0202, LID of 0F04, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>924</b> is located in physical channel 0202 in administered IHS <b>906</b> and may be identified logically by administered IHS <b>906</b> as 0F04. Adapter <b>924</b> is a physical RNIC network adapter and couples to NETWORK A <b>920</b> on both ports 1 and 2. Administered IHS <b>906</b> may access adapter <b>924</b> to communicate via NETWORK A <b>920</b>.
0186The hardware configuration information of adapter <b>936</b> includes MSN of D832900A, PID of 0055, LID of DD06, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>936</b> is located in physical channel 0055 in administered IHS <b>908</b> and may be identified logically by administered IHS <b>908</b> as DD06. Adapter <b>936</b> is a physical OSA network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. Administered IHS <b>908</b> may access adapter <b>936</b> to communicate via NETWORK B <b>935</b>.
0187The hardware configuration information of adapter <b>937</b> includes MSN of D832900A, PID of 0057, LID of DD07, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>937</b> is located in physical channel 0057 in administered IHS <b>908</b> and may be identified logically by administered IHS <b>908</b> as DD07. Adapter <b>937</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. Administered IHS <b>908</b> may access adapter <b>937</b> to communicate via NETWORK B <b>935</b>.
0188The hardware configuration information of adapter <b>938</b> includes MSN of D832900A, PID of 0056, LID of DD08, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>938</b> is located in physical channel 0056 in administered IHS <b>908</b> and may be identified logically by administered IHS <b>908</b> as DD08. Adapter <b>938</b> is a physical OSA network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. Administered IHS <b>908</b> may access adapter <b>938</b> to communicate via NETWORK B <b>935</b>.
0189The hardware configuration information of adapter <b>939</b> includes MSN of D832900A, PID of 0058, LID of DD09, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>939</b> is located in physical channel 0058 in administered IHS <b>908</b> and may be identified logically by administered IHS <b>908</b> as DD09. Adapter <b>939</b> is a physical RNIC network adapter and couples to NETWORK B <b>935</b> on both ports 1 and 2. Administered IHS <b>908</b> may access adapter <b>939</b> to communicate via NETWORK B <b>935</b>.
0190As illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, RNIC converging tool <b>1200</b> may group many OSA adapters with RNIC adapters, thus creating RNIC converged adapters. To create RNIC converged adapters, RNIC converging tool <b>1200</b> may sort the adapters by PNet IDs and adapter types. In one embodiment, RNIC converged adapters should be on the same network to function. Without PNet IDs and adapter types, RNIC converging tool <b>1200</b> would not be able to create RNIC converged adapters on the same network.
0191RNIC converged adapters allow OSA adapter <b>909</b> to initiate TCP/IP communications. When converged with RNIC adapter <b>910</b>, RDMA communications may be more readily initiated and conducted. RNIC converged adapters allow LPARs to easily utilize the RNIC converging adapters for RDMA communications. RDMA communications may exhibit lower latency than TCP/IP communications. RDMA is remote direct memory access, a technology that enables an IHS to exchange information with another IHS without involving the processor, cache or operating system.
0192With respect to an RNIC converging IHS, the disclosed methodology logically causes two unlike adapters, such as OSA and RNIC adapters, that are connected to or associated with the same physical network to function together, i.e to converge, as if the two adapters were a single adapter (i.e. using standard TCP/IP protocol over the OSA and RDMA protocols over the RNIC.
0193<figref idref="DRAWINGS">FIG. 11</figref> is a block diagram of an RNIC converging information handling system (IHS) <b>1100</b> that may be used in the disclosed RNIC converging system. RNIC converging IHS <b>1100</b> includes a processor <b>1105</b> that may include multiple cores. RNIC converging IHS <b>1100</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. In one embodiment, RNIC converging IHS <b>1100</b> includes a bus <b>1110</b>, i.e. channel <b>1110</b>. In another embodiment, bus <b>1110</b> may be multiple busses, i.e., multiple channels. Bus <b>1110</b> may couple processor <b>1105</b> to memory <b>1115</b> via a memory controller <b>1120</b> and memory bus <b>1125</b>. System memory <b>1115</b> may also be referred to as main memory. System memory <b>1115</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>1105</b> may also include local memory such as L1, L2 and L3 caches.
0194In one embodiment, a video graphics controller <b>1130</b> couples display <b>1135</b> to bus <b>1110</b>. In another embodiment, RNIC converging IHS <b>1100</b> may operate without display <b>1135</b> and/or video graphics controller <b>1130</b>. Nonvolatile storage <b>1140</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>1110</b> to provide RNIC converging IHS <b>1100</b> with permanent storage of information. System memory <b>1115</b> and nonvolatile storage <b>1140</b> are both forms of memory stores. In one embodiment, nonvolatile storage <b>1140</b> stores a hypervisor <b>1145</b> (HYPERVISOR) that governs operation of RNIC converging IHS <b>1100</b>. In another embodiment, nonvolatile storage <b>1140</b> may store an operating system (not shown) that governs operation of RNIC converging IHS <b>1100</b>. In another embodiment, nonvolatile storage <b>1140</b> may store an operating system (not shown) that governs operation of RNIC converging IHS <b>1100</b>, where the operating system includes a hypervisor (not shown).
0195I/O devices <b>1150</b>, such as speakers, a keyboard and a pointing device, may couple to bus <b>1110</b> via I/O controller <b>1155</b> and I/O bus <b>1160</b>. One or more expansion busses <b>1165</b>, i.e. channels <b>1165</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, i.e. channels, couple to bus <b>1110</b> to facilitate the connection of peripherals and devices to RNIC converging IHS <b>1100</b>. Network interface controllers (NICs), for example, NIC <b>1170</b>-<b>1</b>, NIC <b>1170</b>-<b>2</b>, . . . , NIC <b>1170</b>-N, wherein N is the number of NICs, may couple to bus <b>1110</b> to enable RNIC converging IHS <b>1100</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>1170</b>-<b>1</b>, NIC <b>1170</b>-<b>2</b>, . . . , NIC <b>1170</b>-N may also be called a network communication adapter, network interface adapter, network adapter, network interface and/or an adapter. NIC <b>1170</b>-<b>1</b>, NIC <b>1170</b>-<b>2</b>, . . . , NIC <b>1170</b>-N may take many forms. For example, NIC <b>1170</b>-<b>1</b>, NIC <b>1170</b>-<b>2</b>, . . . , NIC <b>1170</b>-N may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0196While <figref idref="DRAWINGS">FIG. 11</figref> shows one IHS that employs processor <b>1105</b>, the IHS may take many forms. For example, RNIC converging IHS <b>1100</b> may take the form of a mainframe, server, central processor complex (CPC), desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. RNIC converging IHS <b>1100</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0197RNIC converging IHS <b>1100</b> includes a RNIC converging tool computer program product <b>1200</b> on digital media <b>1175</b> such as a CD, DVD or other media. For simplicity, the term RNIC converging tool will be used below. RNIC converging IHS <b>1100</b> may store RNIC converging tool <b>1200</b> in nonvolatile storage <b>1140</b> as RNIC converging tool <b>1200</b>′. RNIC converging IHS <b>1100</b> may also store hypervisor <b>1145</b> (HYPERVISOR) and logical partition (LPAR) <b>1180</b>-<b>1</b>, LPAR <b>1180</b>-<b>2</b>, . . . , LPAR <b>1180</b>-M, wherein M is the number of LPARs, in nonvolatile storage <b>1140</b>.
0198In another embodiment, RNIC converging tool <b>1200</b>′ may be part of the hypervisor <b>1145</b> (not shown). In another embodiment, RNIC converging tool <b>1200</b>′ may be in LPAR <b>1180</b>-<b>1</b>, LPAR <b>1180</b>-<b>2</b>, . . . , LPAR <b>1180</b>-M. In another embodiment, RNIC converging IHS <b>1100</b> may store an operating system (not shown) that governs operation of RNIC converging IHS <b>1100</b>, where the operating system includes a hypervisor (not shown) and where the operating system includes LPAR <b>1180</b>-<b>1</b>, LPAR <b>1180</b>-<b>2</b>, . . . , LPAR <b>1180</b>-M as virtual machines (not shown). When RNIC converging IHS <b>1100</b> initializes, the IHS loads hypervisor <b>1145</b> into system memory <b>1115</b> for execution as hypervisor <b>1145</b>′. RNIC converging IHS <b>1100</b> also loads RNIC converging tool <b>1200</b>′ into system memory <b>1115</b> for execution as RNIC converging tool <b>1200</b>″. RNIC converging IHS <b>1100</b> may also load LPAR <b>1180</b>-<b>1</b>, LPAR <b>1180</b>-<b>2</b>, . . . , LPAR <b>1180</b>-M into system memory <b>1115</b> for execution as LPAR <b>1180</b>-<b>1</b>′, LPAR <b>1180</b>-<b>2</b>′, . . . , LPAR <b>1180</b>-M′, respectively.
0199In another embodiment, when RNIC converging IHS <b>1100</b> initializes, the IHS may load an operating system (not shown) into system memory <b>1115</b> for execution. In another embodiment, when RNIC converging IHS <b>1100</b> initializes, the IHS may load an operating system (not shown) that includes a hypervisor (not shown) and includes LPAR <b>1180</b>-<b>1</b>, LPAR <b>1180</b>-<b>2</b>, . . . , LPAR <b>1180</b>-M as virtual machines (not shown) into system memory <b>1115</b> for execution.
0200<figref idref="DRAWINGS">FIG. 12</figref> is a flowchart that shows a representative process flow of an RNIC converging tool <b>1200</b> that may be used in the disclosed RNIC converging system. Process flow commences when RNIC converging tool <b>1200</b> in RNIC converging IHS <b>1100</b> initializes, as per block <b>1205</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does not transmit HCM database <b>580</b>, as per block <b>1210</b>, process flow continues at block <b>1210</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does transmit HCM database <b>580</b>, as per block <b>1210</b>, a hypervisor agent in RNIC converging IHS <b>1100</b> may receive HCM database <b>580</b>, as per block <b>1215</b>. In one embodiment, the hypervisor agent in the RNIC converging IHS <b>1100</b> is included in hypervisor <b>1145</b>.
0201The hypervisor agent may allow hypervisor <b>1145</b> to access HCM database <b>580</b>. Hypervisor <b>1145</b> may transmit HCM database <b>580</b> to RNIC converging tool <b>1200</b>, as per block <b>1220</b>. RNIC converging tool <b>1200</b> may extract the hardware configuration information of RNIC converging IHS <b>1100</b> from the HCM database <b>580</b>, as per block <b>1225</b>. In one embodiment, the hardware configuration information of RNIC converging IHS <b>1100</b> from HCM database <b>580</b> may include, but is not limited to, on a per adapter basis, machine serial numbers (MSNs), physical identifications (PIDs), logical identifications (LIDs), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) of the first port of the adapter and the PNet ID of the second port of the adapter. In one embodiment, the adapter type “0087” may be an OSA adapter and the adapter type “0008” may be an RNIC adapter.
0202In one embodiment, the RNIC converging tool <b>1200</b> may share the extracted hardware configuration information of RNIC converging IHS <b>1100</b> with hypervisor <b>1145</b>. Hypervisor <b>1145</b> may update the hardware configuration of RNIC converging IHS <b>1100</b> with the extracted hardware configuration information of RNIC converging IHS <b>1100</b>. In another embodiment, the RNIC converging tool <b>1200</b> may share the extracted hardware configuration information of RNIC converging IHS <b>1100</b> with LPARs <b>1180</b>-<b>1</b>, <b>1180</b>-<b>2</b>, . . . , <b>1180</b>-M, where M is the number of LPARs in RNIC converging IHS <b>1100</b>. LPARs <b>1180</b>-<b>1</b>, <b>1180</b>-<b>2</b>, . . . , <b>1180</b>-M may update their respective hardware configuration with the extracted hardware configuration information of RNIC converging IHS <b>1100</b>.
0203RNIC converging tool <b>1200</b> may sort the extracted hardware configuration information by PNet IDs, as per block <b>1230</b>. For example, the RNIC converging tool <b>1200</b> may list all adapters with the PNet ID of “NETA” first, followed by all adapters with the PNet ID of “NETB”. RNIC converging tool <b>1200</b> may further sort the extracted configuration information by adapter type, as per block <b>1235</b>. For example, the RNIC converging tool <b>1200</b> may list all adapters with the type “0087” and the PNet ID “NETA” first, followed by the adapters with the type “0008” and the PNet ID of “NETA”, further followed by the adapters with the type “0087” and the PNet ID of “NETB”.
0204In one embodiment, RNIC converging tool <b>1200</b> may group OSA adapters and RNIC adapters with matching PNet IDs, as per block <b>1240</b>. For example, as shown in <figref idref="DRAWINGS">FIGS. 7 and 8</figref>, RNIC converging tool <b>1200</b> may group network adapter <b>711</b> and network adapter <b>712</b> together because adapter <b>711</b> is the type “0087”, i.e. OSA, and adapter <b>712</b> is the type “0008”, i.e. RNIC, and both adapters <b>711</b> and <b>712</b> have a PNet ID of “NETA”. The RNIC converging tool <b>1200</b> may allow an LPAR with access to utilize the grouped adapters to communicate using RDMA, which may require both an OSA and RNIC adapter, as per block <b>1245</b>. Process flow terminates at end block <b>1250</b>. Alternatively, process flow may continue at start block <b>605</b>.
0000III. Bridging System
0205<figref idref="DRAWINGS">FIG. 13</figref> is a block diagram showing one embodiment of the disclosed bridging system <b>1300</b> utilizing PNet IDs. Bridging system <b>1300</b> may utilize network adapter <b>1301</b>, administrative network <b>1302</b> and network adapter <b>1303</b> to couple HCM IHS <b>500</b> to administered IHS <b>1304</b>. Administered IHS <b>1304</b> may be referred to as bridging IHS <b>1304</b>. Bridging system <b>1300</b> may utilize network adapter <b>1301</b>, administrative network <b>1302</b> and network adapter <b>1305</b> to couple HCM IHS <b>500</b> to administered IHS <b>1306</b>. Bridging system <b>1300</b> may utilize network adapter <b>1301</b>, administrative network <b>1302</b> and network adapter <b>1307</b> to couple HCM IHS <b>500</b> to administered IHS <b>1308</b>. Bridging system <b>1300</b> may utilize network adapter <b>1301</b>, administrative network <b>1302</b> and network adapter <b>1309</b> to couple HCM IHS <b>500</b> to administered IHS <b>1310</b>. Administered IHSs <b>1304</b>, <b>1306</b>, <b>1308</b> and <b>1310</b> couple via administrative network <b>1302</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>1400</b> with HCM tool <b>600</b> to the administered IHSs.
0206Bridging system <b>1300</b> may utilize network adapter <b>1311</b> via NETWORK A <b>1312</b> via network adapter <b>1313</b> to couple bridging IHS <b>1304</b> to administered IHS <b>1306</b>. Bridging system <b>1300</b> may utilize network adapter <b>1314</b> via NETWORK B <b>1315</b> via network adapter <b>1316</b> to couple bridging IHS <b>1304</b> to administered IHS <b>1308</b>. Bridging system <b>1300</b> may utilize network adapter <b>1317</b> via NETWORK C <b>1318</b> via network adapter <b>1319</b> to couple bridging IHS <b>1304</b> to administered IHS <b>1310</b>.
0207In one embodiment, network adapters <b>1301</b>, <b>1303</b>, <b>1305</b>, <b>1307</b> and <b>1309</b> may be Ethernet (ETH) adapters. Network adapters <b>1311</b>, <b>1313</b>, <b>1314</b>, <b>1316</b>, <b>1317</b> and <b>1319</b> may be open system adapters (OSAs). In one embodiment, administrative network <b>1302</b>, NETWORK A <b>1312</b>, NETWORK B <b>1315</b> and NETWORK C <b>1318</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0208Bridging IHS <b>1304</b> may include a hypervisor <b>1745</b> that may create logical partition (LPAR) <b>1320</b>-<b>1</b>, LPAR <b>1320</b>-<b>2</b>, LPAR <b>1320</b>-<b>3</b>, LPAR <b>1320</b>-<b>4</b>, LPAR <b>1320</b>-<b>5</b>, LPAR <b>1320</b>-<b>6</b> and LPAR <b>1320</b>-<b>7</b> in bridging IHS <b>1304</b>. LPAR <b>1320</b>-<b>1</b>, LPAR <b>1320</b>-<b>2</b> and LPAR <b>1320</b>-<b>3</b> may include virtual internal network adapter <b>1321</b>-<b>1</b>, virtual internal network adapter <b>1321</b>-<b>2</b> and virtual internal network adapter <b>1321</b>-<b>3</b>, respectively. Virtual internal network adapter <b>1321</b>-<b>1</b> and/or virtual internal network adapter <b>1321</b>-<b>2</b> and/or virtual internal network adapter <b>1321</b>-<b>3</b> may couple via channel <b>1322</b> to virtual internal network adapter <b>1323</b>. Virtual internal network adapter <b>1323</b> may be referred to as bridge port <b>1323</b>.
0209LPAR <b>1320</b>-<b>4</b> and LPAR <b>1320</b>-<b>5</b> may include virtual internal network adapter <b>1321</b>-<b>4</b> and virtual internal network adapter <b>1321</b>-<b>5</b>, respectively. Virtual internal network adapter <b>1321</b>-<b>4</b> and/or virtual internal network adapter <b>1321</b>-<b>5</b> may couple via channel <b>1324</b> to virtual internal network adapter <b>1325</b>. Virtual internal network adapter <b>1325</b> may be referred to as bridge port <b>1325</b>.
0210LPAR <b>1320</b>-<b>6</b> and LPAR <b>1320</b>-<b>7</b> may include virtual internal network adapter <b>1321</b>-<b>6</b> and virtual internal network adapter <b>1321</b>-<b>7</b>, respectively. Virtual internal network adapter <b>1321</b>-<b>6</b> and/or virtual internal network adapter <b>1321</b>-<b>7</b> may couple via channel <b>1326</b> to virtual internal network adapter <b>1327</b>. Virtual internal network adapter <b>1327</b> may be referred to as bridge port <b>1327</b>.
0211In one embodiment, virtual internal network adapters <b>1321</b>-<b>1</b>, <b>1321</b>-<b>2</b>, <b>1321</b>-<b>3</b>, <b>1321</b>-<b>4</b>, <b>1321</b>-<b>5</b>, <b>1321</b>-<b>6</b>, <b>1321</b>-<b>7</b>, <b>1323</b>, <b>1325</b> and <b>1327</b> may be internal queued direct (IQD) communication adapters. Channel <b>1322</b>, channel <b>1324</b> and channel <b>1326</b> may be respective IQD communication networks internal to bridging IHS <b>1304</b>.
0212Hypervisor <b>1745</b> may create virtual switch (VSWITCH) <b>1328</b>, VSWITCH <b>1329</b> and VSWITCH <b>1330</b> in bridging IHS <b>1304</b>. In one embodiment, VSWITCH <b>1328</b>, <b>1329</b> and <b>1330</b> are each specialized LPARs. VSWITCH <b>1328</b> may include virtual internal network adapter <b>1323</b> and network adapter <b>1311</b>. VSWITCH <b>1329</b> may include virtual internal network adapter <b>1325</b> and network adapter <b>1314</b>. VSWITCH <b>1330</b> may include virtual internal network adapter <b>1327</b> and network adapter <b>1317</b>.
0213<figref idref="DRAWINGS">FIG. 14</figref> depicts one embodiment of HCM database <b>1400</b> in the disclosed bridging system <b>1300</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>1400</b> on a per adapter basis. In one embodiment, for each network adapter in bridging system <b>1300</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0214As shown in HCM database <b>1400</b>, the hardware configuration information of adapter <b>1311</b> includes MSN of 0A0A0B11, PID of 0006, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1311</b> is located in physical channel 0006 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 00F1. Adapter <b>1311</b> is a physical OSA network adapter and couples to NETWORK A <b>1312</b> on both ports 1 and 2. LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> of bridging IHS <b>1304</b> may access adapter <b>1311</b> to communicate via NETWORK A <b>1312</b>.
0215The hardware configuration information of adapter <b>1314</b> includes MSN of 0A0A0B11, PID of 0007, LID of 00F5, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1314</b> is located in physical channel 0007 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 00F5. Adapter <b>1314</b> is a physical OSA network adapter and couples to NETWORK B <b>1315</b> on both ports 1 and 2. LPAR <b>1320</b>-<b>4</b> and <b>1320</b>-<b>5</b> of bridging IHS <b>1304</b> may access adapter <b>1314</b> to communicate via NETWORK B <b>1315</b>.
0216The hardware configuration information of adapter <b>1317</b> includes MSN of 0A0A0B11, PID of 0008, LID of 00F8, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1317</b> is located in physical channel 0008 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 00F8. Adapter <b>1317</b> is a physical OSA network adapter and couples to NETWORK C <b>1318</b> on both ports 1 and 2. LPAR <b>1320</b>-<b>6</b> and <b>1320</b>-<b>7</b> of bridging IHS <b>1304</b> may access adapter <b>1317</b> to communicate via NETWORK C <b>1318</b>.
0217The hardware configuration information of adapter <b>1321</b>-<b>1</b> includes MSN of 0A0A0B11, PID of 0112, LID of 04C1, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1321</b>-<b>1</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>1</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C1. Adapter <b>1321</b>-<b>1</b> is an IQD virtual network adapter and couples to IQD network <b>1322</b> on virtual channel 0112. LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>1</b> to communicate via IQD network <b>1322</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>1</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> to access adapter <b>1311</b> to communicate via NETWORK A <b>1312</b>.
0218The hardware configuration information of adapter <b>1321</b>-<b>2</b> includes MSN of 0A0A0B11, PID of 0112, LID of 04C2, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1321</b>-<b>2</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>2</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C2. Adapter <b>1321</b>-<b>2</b> is an IQD virtual network adapter and couples to IQD network <b>1322</b> on virtual channel 0112. LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>2</b> to communicate via IQD network <b>1322</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>2</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> to access adapter <b>1311</b> to communicate via NETWORK A <b>1312</b>.
0219The hardware configuration information of adapter <b>1321</b>-<b>3</b> includes MSN of 0A0A0B11, PID of 0112, LID of 04C3, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1321</b>-<b>3</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>3</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C3. Adapter <b>1321</b>-<b>3</b> is an IQD virtual network adapter and couples to IQD network <b>1322</b> on virtual channel 0112. LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>3</b> to communicate via IQD network <b>1322</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>3</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>1</b>, <b>1320</b>-<b>2</b> and <b>1320</b>-<b>3</b> to access adapter <b>1311</b> to communicate via NETWORK A <b>1312</b>.
0220The hardware configuration information of adapter <b>1321</b>-<b>4</b> includes MSN of 0A0A0B11, PID of 0113, LID of 04C5, type of 008D, LPAR access list of 04 and 05, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1321</b>-<b>4</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>4</b> is a virtual adapter with a virtual channel 0113 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C5. Adapter <b>1321</b>-<b>4</b> is an IQD virtual network adapter and couples to IQD network <b>1324</b> on virtual channel 0113. LPAR <b>1320</b>-<b>4</b> and <b>1320</b>-<b>5</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>4</b> to communicate via IQD network <b>1324</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>4</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>4</b> and <b>1320</b>-<b>5</b> to access adapter <b>1314</b> to communicate via NETWORK B <b>1315</b>.
0221The hardware configuration information of adapter <b>1321</b>-<b>5</b> includes MSN of 0A0A0B11, PID of 0113, LID of 04C6, type of 008D, LPAR access list of 04 and 05, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1321</b>-<b>5</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>5</b> is a virtual adapter with a virtual channel 0113 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C6. Adapter <b>1321</b>-<b>5</b> is an IQD virtual network adapter and couples to IQD network <b>1324</b> on virtual channel 0113. LPAR <b>1320</b>-<b>4</b> and <b>1320</b>-<b>5</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>5</b> to communicate via IQD network <b>1324</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>5</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>4</b> and <b>1320</b>-<b>5</b> to access adapter <b>1314</b> to communicate via NETWORK B <b>1315</b>.
0222The hardware configuration information of adapter <b>1321</b>-<b>6</b> includes MSN of 0A0A0B11, PID of 0114, LID of 04C8, type of 008D, LPAR access list of 06 and 07, and PNet ID 1 of NETC and PNet ID 2 with no entry because adapter <b>1321</b>-<b>6</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>6</b> is a virtual adapter with a virtual channel 0114 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C8. Adapter <b>1321</b>-<b>6</b> is an IQD virtual network adapter and couples to IQD network <b>1326</b> on virtual channel 0114. LPAR <b>1320</b>-<b>6</b> and <b>1320</b>-<b>7</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>6</b> to communicate via IQD network <b>1326</b>. PNet ID 1 of NETC indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>6</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>6</b> and <b>1320</b>-<b>7</b> to access adapter <b>1317</b> to communicate via NETWORK C <b>1318</b>.
0223The hardware configuration information of adapter <b>1321</b>-<b>7</b> includes MSN of 0A0A0B11, PID of 0114, LID of 04C9, type of 008D, LPAR access list of 06 and 07, and PNet ID 1 of NETC and PNet ID 2 with no entry because adapter <b>1321</b>-<b>7</b> is virtual and does not have a second port. In other words, adapter <b>1321</b>-<b>7</b> is a virtual adapter with a virtual channel 0114 in bridging IHS <b>1304</b> and may be identified logically by bridging IHS <b>1304</b> as 04C9. Adapter <b>1321</b>-<b>7</b> is an IQD virtual network adapter and couples to IQD network <b>1326</b> on virtual channel 0114. LPAR <b>1320</b>-<b>6</b> and <b>1320</b>-<b>7</b> of bridging IHS <b>1304</b> may access adapter <b>1321</b>-<b>7</b> to communicate via IQD network <b>1326</b>. PNet ID 1 of NETC indicates that a bridging tool <b>1800</b> may bridge adapter <b>1321</b>-<b>7</b> with adapter <b>1311</b> to allow LPAR <b>1320</b>-<b>6</b> and <b>1320</b>-<b>7</b> to access adapter <b>1317</b> to communicate via NETWORK C <b>1318</b>.
0224The hardware configuration information of adapter <b>1313</b> includes MSN of 0000F12A, PID of 0022, LID of 0DA1, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1313</b> is located in physical channel 0022 in administered IHS <b>1306</b> and may be identified logically by administered IHS <b>1306</b> as 0DA1. Adapter <b>1313</b> is a physical OSA network adapter and couples to NETWORK A <b>1312</b> on both ports 1 and 2. Administered IHS <b>1306</b> may access adapter <b>1313</b> to communicate via NETWORK A <b>1312</b>.
0225The hardware configuration information of adapter <b>1316</b> includes MSN of DDD32AA, PID of 0054, LID of 00C1, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1316</b> is located in physical channel 0054 in administered IHS <b>1308</b> and may be identified logically by administered IHS <b>1308</b> as 00C1. Adapter <b>1316</b> is a physical OSA network adapter and couples to NETWORK B <b>1315</b> on both ports 1 and 2. Administered IHS <b>1308</b> may access adapter <b>1316</b> to communicate via NETWORK B <b>1315</b>.
0226The hardware configuration information of adapter <b>1319</b> includes MSN of 000000B2, PID of 0001, LID of 0DD4, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1319</b> is located in physical channel 0001 in administered IHS <b>1310</b> and may be identified logically by administered IHS <b>1310</b> as 0DD4. Adapter <b>1319</b> is a physical OSA network adapter and couples to NETWORK C <b>1318</b> on both ports 1 and 2. Administered IHS <b>1310</b> may access adapter <b>1319</b> to communicate via NETWORK C <b>1318</b>.
0227As illustrated in <figref idref="DRAWINGS">FIG. 13</figref>, in the HCM database <b>1400</b> of <figref idref="DRAWINGS">FIG. 14</figref> IQD adapters <b>1321</b>-<b>6</b> and <b>1321</b>-<b>7</b> exhibit a PNet ID of NETC. This indicates to bridging tool <b>1800</b> (not shown in <figref idref="DRAWINGS">FIG. 13</figref>, but shown in <figref idref="DRAWINGS">FIG. 18</figref>) that the internal network IQD <b>1326</b> should be bridged to an external network (NETWORK C) that exhibits the same PNet ID as internal network IQD <b>1326</b>. More particularly, bridging tool <b>1800</b> may bridge internal networks, i.e. networks internal to bridging IHS <b>1304</b>, to external networks with a matching PNet ID. In one embodiment, an internal network (e.g. IQD <b>1426</b>) is not assigned a PNet ID in the HCM database <b>1400</b> unless the internal network should be bridged to an external network, such as OSA <b>1317</b> that exhibits a matching PNet ID. In this particular example, OSA <b>1317</b> exhibits a PNet ID of NETC and IQD internal network IQD <b>1326</b> also exhibits the same PNet ID of NETC. In response to this match of PNet IDs, bridging tool <b>1800</b> may bridge the connection between IQD <b>1326</b> and OSA <b>1317</b>, thus providing IQD <b>1326</b> with access to external NETWORK C. Without this bridge, provided by bridge port <b>1327</b> and (VSWITCH) <b>1330</b>, IQD channels are only internal and not externally connected, in one embodiment. In one embodiment, an internal network such as IQD <b>1326</b> is not provided with a PNet ID unless that internal network is to be bridged with an external network.
0228<figref idref="DRAWINGS">FIG. 15</figref> is a block diagram showing one embodiment of the disclosed bridging system <b>1500</b> utilizing PNet IDs. Bridging system <b>1500</b> may utilize network adapter <b>1501</b>, administrative network <b>1502</b> and network adapter <b>1503</b> to couple HCM IHS <b>500</b> to administered IHS <b>1504</b>. Administered IHS <b>1504</b> may be referred to as bridging IHS <b>1504</b>. Bridging system <b>1500</b> may utilize network adapter <b>1501</b>, administrative network <b>1502</b> and network adapter <b>1505</b> to couple HCM IHS <b>500</b> to administered IHS <b>1506</b>. Bridging system <b>1500</b> may utilize network adapter <b>1501</b>, administrative network <b>1502</b> and network adapter <b>1507</b> to couple HCM IHS <b>500</b> to administered IHS <b>1508</b>. Administered IHSs <b>1504</b>, <b>1506</b> and <b>1508</b> couple via administrative network <b>1502</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>1600</b> with HCM tool <b>600</b> to the administered IHSs.
0229Bridging system <b>1500</b> may utilize network adapter <b>1509</b> via NETWORK A <b>1510</b> via network adapter <b>1511</b> to couple bridging IHS <b>1504</b> to administered IHS <b>1506</b>. Bridging system <b>1500</b> may utilize network adapter <b>1512</b> via NETWORK B <b>1513</b> via network adapter <b>1514</b> to couple bridging IHS <b>1504</b> to administered IHS <b>1508</b>.
0230In one embodiment, network adapters <b>1501</b>, <b>1503</b>, <b>1505</b> and <b>1507</b> may be Ethernet (ETH) adapters. Network adapters <b>1509</b>, <b>1511</b>, <b>1512</b> and <b>1514</b> may be open system adapters (OSAs). In one embodiment, administrative network <b>1502</b>, NETWORK A <b>1510</b> and NETWORK B <b>1513</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0231Bridging IHS <b>1504</b> may include a hypervisor <b>1745</b> that may create logical partition (LPAR) <b>1515</b>-<b>1</b>, LPAR <b>1515</b>-<b>2</b>, LPAR <b>1515</b>-<b>3</b>, LPAR <b>1515</b>-<b>4</b>, LPAR <b>1515</b>-<b>5</b>, LPAR <b>1515</b>-<b>6</b> and LPAR <b>1515</b>-<b>7</b> in bridging IHS <b>1504</b>. LPAR <b>1515</b>-<b>1</b>, LPAR <b>1515</b>-<b>2</b> and LPAR <b>1515</b>-<b>3</b> may include virtual internal network adapter <b>1516</b>-<b>1</b>, virtual internal network adapter <b>1516</b>-<b>2</b> and virtual internal network adapter <b>1516</b>-<b>3</b>, respectively. Virtual internal network adapter <b>1516</b>-<b>1</b> and/or virtual internal network adapter <b>1516</b>-<b>2</b> and/or virtual internal network adapter <b>1516</b>-<b>3</b> may couple via channel <b>1517</b> to virtual internal network adapter <b>1518</b>. Virtual internal network adapter <b>1518</b> may be referred to as bridge port <b>1518</b>.
0232LPAR <b>1515</b>-<b>4</b>, LPAR <b>1515</b>-<b>5</b>, LPAR <b>1515</b>-<b>6</b> and LPAR <b>1515</b>-<b>7</b> may include virtual internal network adapter <b>1516</b>-<b>4</b>, virtual internal network adapter <b>1516</b>-<b>5</b>, virtual internal network adapter <b>1516</b>-<b>6</b> and virtual internal network adapter <b>1516</b>-<b>7</b>, respectively. Virtual internal network adapter <b>1516</b>-<b>4</b> and/or virtual internal network adapter <b>1516</b>-<b>5</b> and/or virtual internal network adapter <b>1516</b>-<b>6</b> and/or virtual internal network adapter <b>1516</b>-<b>7</b> may couple via channel <b>1519</b> to virtual internal network adapter <b>1520</b>. Virtual internal network adapter <b>1520</b> may be referred to as bridge port <b>1520</b>.
0233In one embodiment, virtual internal network adapters <b>1516</b>-<b>1</b>, <b>1516</b>-<b>2</b>, <b>1516</b>-<b>3</b>, <b>1516</b>-<b>4</b>, <b>1516</b>-<b>5</b>, <b>1516</b>-<b>6</b>, <b>1516</b>-<b>7</b>, <b>1518</b> and <b>1519</b> may be internal queued direct (IQD) communication adapters. Channel <b>1517</b> and channel <b>1519</b> may be respective IQD communication networks internal to bridging IHS <b>1504</b>.
0234Hypervisor <b>1745</b> in bridging IHS <b>1504</b> may create virtual switch (VSWITCH) <b>1521</b> and VSWITCH <b>1522</b> in bridging IHS <b>1504</b>. In one embodiment, VSWITCH <b>1521</b> and <b>1522</b> are each specialized LPARs. VSWITCH <b>1521</b> may include virtual internal network adapter <b>1518</b> and network adapter <b>1509</b>. VSWITCH <b>1522</b> may include virtual internal network adapter <b>1520</b> and network adapter <b>1512</b>.
0235In one embodiment, administered IHS <b>1508</b> may be a bridging IHS. Administered IHS <b>1508</b> may include a hypervisor <b>1745</b> that may create LPAR <b>1523</b>-<b>1</b> and LPAR <b>1523</b>-<b>2</b> in administered IHS <b>1508</b>. LPAR <b>1523</b>-<b>1</b> and LPAR <b>1523</b>-<b>2</b> may include virtual internal network adapter <b>1524</b>-<b>1</b> and virtual internal network adapter <b>1524</b>-<b>2</b>, respectively. Virtual internal network adapter <b>1524</b>-<b>1</b> and/or virtual internal network adapter <b>1524</b>-<b>2</b> may couple via channel <b>1525</b> to virtual internal network adapter <b>1526</b>. Virtual internal network adapter <b>1526</b> may be referred to as bridge port <b>1526</b>.
0236In one embodiment, virtual internal network adapters <b>1524</b>-<b>1</b> and <b>1524</b>-<b>2</b> may be internal queued direct (IQD) communication adapters. Channel <b>1525</b> may be an IQD communication network internal to administered IHS <b>1508</b>. Hypervisor <b>1745</b> in administered IHS <b>1508</b> may create virtual switch (VSWITCH) <b>1527</b> in administered IHS <b>1508</b>. In one embodiment, VSWITCH <b>1527</b> may be a specialized LPAR. VSWITCH <b>1527</b> may include virtual internal network adapter <b>1526</b> and network adapter <b>1514</b>.
0237<figref idref="DRAWINGS">FIG. 16</figref> depicts one embodiment of HCM database <b>1600</b> in the disclosed bridging system <b>1500</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>1600</b> on a per adapter basis. In one embodiment, for each network adapter in bridging system <b>1500</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0238As shown in HCM database <b>1600</b>, the hardware configuration information of adapter <b>1509</b> includes MSN of 03F00A21, PID of 0006, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1509</b> is located in physical channel 0006 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 00F1. Adapter <b>1509</b> is a physical OSA network adapter and couples to NETWORK A <b>1510</b> on both ports 1 and 2. LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> of bridging IHS <b>1504</b> may access adapter <b>1509</b> to communicate via NETWORK A <b>1510</b>.
0239The hardware configuration information of adapter <b>1512</b> includes MSN of 03F00A21, PID of 0007, LID of 00F5, type of 0087, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1512</b> is located in physical channel 0007 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 00F5. Adapter <b>1512</b> is a physical OSA network adapter and couples to NETWORK B <b>1513</b> on both ports 1 and 2. LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> of bridging IHS <b>1504</b> may access adapter <b>1512</b> to communicate via NETWORK B <b>1513</b>.
0240The hardware configuration information of adapter <b>1516</b>-<b>1</b> includes MSN of 03F00A21, PID of 0111, LID of 04C0, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1516</b>-<b>1</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>1</b> is a virtual adapter with a virtual channel 0111 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C0. Adapter <b>1516</b>-<b>1</b> is an IQD virtual network adapter and couples to IQD network <b>1517</b> on virtual channel 0111. LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>1</b> to communicate via IQD network <b>1517</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>1</b> with adapter <b>1509</b> to allow LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> to access adapter <b>1509</b> to communicate via NETWORK A <b>1510</b>.
0241The hardware configuration information of adapter <b>1516</b>-<b>2</b> includes MSN of 03F00A21, PID of 0111, LID of 04C1, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1516</b>-<b>2</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>2</b> is a virtual adapter with a virtual channel 0111 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C1. Adapter <b>1516</b>-<b>2</b> is an IQD virtual network adapter and couples to IQD network <b>1517</b> on virtual channel 0111. LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>2</b> to communicate via IQD network <b>1517</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>2</b> with adapter <b>1509</b> to allow LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> to access adapter <b>1509</b> to communicate via NETWORK A <b>1510</b>.
0242The hardware configuration information of adapter <b>1516</b>-<b>3</b> includes MSN of 03F00A21, PID of 0111, LID of 04C2, type of 008D, LPAR access list of 01, 02 and 03, and PNet ID 1 of NETA and PNet ID 2 with no entry because adapter <b>1516</b>-<b>3</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>3</b> is a virtual adapter with a virtual channel 0111 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C2. Adapter <b>1516</b>-<b>3</b> is an IQD virtual network adapter and couples to IQD network <b>1517</b> on virtual channel 0111. LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>3</b> to communicate via IQD network <b>1517</b>. PNet ID 1 of NETA indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>3</b> with adapter <b>1509</b> to allow LPAR <b>1515</b>-<b>1</b>, <b>1515</b>-<b>2</b> and <b>1515</b>-<b>3</b> to access adapter <b>1509</b> to communicate via NETWORK A <b>1510</b>.
0243The hardware configuration information of adapter <b>1516</b>-<b>4</b> includes MSN of 03F00A21, PID of 0112, LID of 04C4, type of 008D, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1516</b>-<b>4</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>4</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C4. Adapter <b>1516</b>-<b>4</b> is an IQD virtual network adapter and couples to IQD network <b>1519</b> on virtual channel 0112. LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>4</b> to communicate via IQD network <b>1519</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>4</b> with adapter <b>1512</b> to allow LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> to access adapter <b>1512</b> to communicate via NETWORK B <b>1513</b>.
0244The hardware configuration information of adapter <b>1516</b>-<b>5</b> includes MSN of 03F00A21, PID of 0112, LID of 04C5, type of 008D, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1516</b>-<b>5</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>5</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C5. Adapter <b>1516</b>-<b>5</b> is an IQD virtual network adapter and couples to IQD network <b>1519</b> on virtual channel 0112. LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>5</b> to communicate via IQD network <b>1519</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>5</b> with adapter <b>1512</b> to allow LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> to access adapter <b>1512</b> to communicate via NETWORK B <b>1513</b>.
0245The hardware configuration information of adapter <b>1516</b>-<b>6</b> includes MSN of 03F00A21, PID of 0112, LID of 04C6, type of 008D, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1516</b>-<b>6</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>6</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C6. Adapter <b>1516</b>-<b>6</b> is an IQD virtual network adapter and couples to IQD network <b>1519</b> on virtual channel 0112. LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>6</b> to communicate via IQD network <b>1519</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>6</b> with adapter <b>1512</b> to allow LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> to access adapter <b>1512</b> to communicate via NETWORK B <b>1513</b>.
0246The hardware configuration information of adapter <b>1516</b>-<b>7</b> includes MSN of 03F00A21, PID of 0112, LID of 04C7, type of 008D, LPAR access list of 04, 05, 06 and 07, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1516</b>-<b>7</b> is virtual and does not have a second port. In other words, adapter <b>1516</b>-<b>7</b> is a virtual adapter with a virtual channel 0112 in bridging IHS <b>1504</b> and may be identified logically by bridging IHS <b>1504</b> as 04C7. Adapter <b>1516</b>-<b>7</b> is an IQD virtual network adapter and couples to IQD network <b>1519</b> on virtual channel 0112. LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> of bridging IHS <b>1504</b> may access adapter <b>1516</b>-<b>7</b> to communicate via IQD network <b>1519</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1516</b>-<b>7</b> with adapter <b>1512</b> to allow LPAR <b>1515</b>-<b>4</b>, <b>1515</b>-<b>5</b>, <b>1515</b>-<b>6</b> and <b>1515</b>-<b>7</b> to access adapter <b>1512</b> to communicate via NETWORK B <b>1513</b>.
0247The hardware configuration information of adapter <b>1511</b> includes MSN of 2338282D, PID of 0031, LID of 00F3, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1511</b> is located in physical channel 0031 in administered IHS <b>1506</b> and may be identified logically by administered IHS <b>1506</b> as 00F3. Adapter <b>1511</b> is a physical OSA network adapter and couples to NETWORK A <b>1510</b> on both ports 1 and 2. Administered IHS <b>1506</b> may access adapter <b>1511</b> to communicate via NETWORK A <b>1510</b>.
0248The hardware configuration information of adapter <b>1514</b> includes MSN of 2338282D, PID of 0022, LID of 0DA1, type of 0087, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1514</b> is located in physical channel 0022 in bridging IHS <b>1508</b> and may be identified logically by bridging IHS <b>1508</b> as 0DA1. Adapter <b>1514</b> is a physical OSA network adapter and couples to NETWORK B <b>1513</b> on both ports 1 and 2. LPAR <b>1515</b>-<b>1</b> and <b>1515</b>-<b>2</b> of bridging IHS <b>1508</b> may access adapter <b>1514</b> to communicate via NETWORK B <b>1513</b>.
0249The hardware configuration information of adapter <b>1524</b>-<b>1</b> includes MSN of 2338282D, PID of 0200, LID of 06D1, type of 008D, LPAR access list of 01 and 02, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1524</b>-<b>1</b> is virtual and does not have a second port. In other words, adapter <b>1524</b>-<b>1</b> is a virtual adapter with a virtual channel 0200 in bridging IHS <b>1508</b> and may be identified logically by bridging IHS <b>1508</b> as 06D1. Adapter <b>1524</b>-<b>1</b> is an IQD virtual network adapter and couples to IQD network <b>1525</b> on virtual channel 0200. LPAR <b>1523</b>-<b>1</b> and <b>1523</b>-<b>2</b> of bridging IHS <b>1508</b> may access adapter <b>1524</b>-<b>1</b> to communicate via IQD network <b>1525</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1524</b>-<b>1</b> with adapter <b>1514</b> to allow LPAR <b>1523</b>-<b>1</b> and <b>1523</b>-<b>2</b> to access adapter <b>1514</b> to communicate via NETWORK B <b>1513</b>.
0250The hardware configuration information of adapter <b>1524</b>-<b>2</b> includes MSN of 2338282D, PID of 0200, LID of 06D2, type of 008D, LPAR access list of 01 and 02, and PNet ID 1 of NETB and PNet ID 2 with no entry because adapter <b>1524</b>-<b>2</b> is virtual and does not have a second port. In other words, adapter <b>1524</b>-<b>2</b> is a virtual adapter with a virtual channel 0200 in bridging IHS <b>1508</b> and may be identified logically by bridging IHS <b>1508</b> as 06D2. Adapter <b>1524</b>-<b>2</b> is an IQD virtual network adapter and couples to IQD network <b>1525</b> on virtual channel 0200. LPAR <b>1523</b>-<b>1</b> and <b>1523</b>-<b>2</b> of bridging IHS <b>1508</b> may access adapter <b>1524</b>-<b>2</b> to communicate via IQD network <b>1525</b>. PNet ID 1 of NETB indicates that a bridging tool <b>1800</b> may bridge adapter <b>1524</b>-<b>2</b> with adapter <b>1514</b> to allow LPAR <b>1523</b>-<b>1</b> and <b>1523</b>-<b>2</b> to access adapter <b>1514</b> to communicate via NETWORK B <b>1513</b>.
0251<figref idref="DRAWINGS">FIG. 17</figref> is a block diagram of a bridging information handling system (IHS) <b>1700</b> that may be used in the disclosed bridging system. With respect to <figref idref="DRAWINGS">FIG. 11</figref>, like numbers indicate like elements. Bridging IHS <b>1700</b> includes a processor <b>1705</b> that may include multiple cores. RNIC converging IHS <b>1700</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. In one embodiment, bridging IHS <b>1700</b> includes a bus <b>1710</b>, i.e. channel <b>1710</b>. In another embodiment, bus <b>1710</b> may be multiple busses, i.e., multiple channels. Bus <b>1710</b> may couple processor <b>1705</b> to memory <b>1715</b> via a memory controller <b>1720</b> and memory bus <b>1725</b>. System memory <b>1715</b> may also be referred to as main memory. System memory <b>1715</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>1705</b> may also include local memory such as L1, L2 and L3 caches.
0252In one embodiment, a video graphics controller <b>1730</b> couples display <b>1735</b> to bus <b>1710</b>. In another embodiment, bridging IHS <b>1700</b> may operate without display <b>1735</b> and/or video graphics controller <b>1730</b>. Nonvolatile storage <b>1740</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>1710</b> to provide bridging IHS <b>1700</b> with permanent storage of information. System memory <b>1715</b> and nonvolatile storage <b>1740</b> are both forms of memory stores. In one embodiment, nonvolatile storage <b>1740</b> stores a hypervisor <b>1745</b> (HYPERVISOR) that governs operation of bridging IHS <b>1700</b>. In another embodiment, nonvolatile storage <b>1740</b> may store an operating system (not shown) that governs operation of bridging IHS <b>1700</b>. In another embodiment, nonvolatile storage <b>1740</b> may store an operating system (not shown) that governs operation of bridging IHS <b>1700</b>, where the operating system includes a hypervisor (not shown).
0253I/O devices <b>1750</b>, such as speakers, a keyboard and a pointing device, may couple to bus <b>1710</b> via I/O controller <b>1755</b> and I/O bus <b>1760</b>. One or more expansion busses <b>1765</b>, i.e. channels <b>1765</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, i.e. channels, couple to bus <b>1710</b> to facilitate the connection of peripherals and devices to bridging IHS <b>1700</b>. Network interface controllers (NICs), for example, NIC <b>1770</b>-<b>1</b>, NIC <b>1770</b>-<b>2</b>, . . . , NIC <b>1770</b>-L, wherein L is the number of NICs, may couple to bus <b>1710</b> to enable bridging IHS <b>1700</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>1770</b>-<b>1</b>, NIC <b>1770</b>-<b>2</b>, . . . , NIC <b>1770</b>-L may also be called a network communication adapter, network interface adapter, network adapter, network interface or an adapter. NIC <b>1770</b>-<b>1</b>, NIC <b>1770</b>-<b>2</b>, . . . , NIC <b>1770</b>-L may take many forms. For example, NIC <b>1770</b>-<b>1</b>, NIC <b>1770</b>-<b>2</b>, . . . , NIC <b>1770</b>-L may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0254While <figref idref="DRAWINGS">FIG. 17</figref> shows one IHS that employs processor <b>1705</b>, the IHS may take many forms. For example, bridging IHS <b>1700</b> may take the form of a mainframe, server, central processor complex (CPC), desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. Bridging IHS <b>1700</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0255Bridging IHS <b>1700</b> includes a bridging tool computer program product <b>1800</b> on digital media <b>1775</b> such as a CD, DVD or other media. For simplicity, the term bridging tool will be used below. Bridging IHS <b>1700</b> may store bridging tool <b>1800</b> in nonvolatile storage <b>1740</b> as bridging tool <b>1800</b>′. Bridging IHS <b>1700</b> may also store hypervisor <b>1745</b> (HYPERVISOR) and logical partition (LPAR) <b>1780</b>-<b>1</b>, LPAR <b>1780</b>-<b>2</b>, . . . , LPAR <b>1780</b>-K, wherein K is the number of LPARs, in nonvolatile storage <b>1740</b>.
0256In another embodiment, bridging tool <b>1800</b>′ may be part of the hypervisor <b>1745</b> (not shown). In another embodiment, bridging tool <b>1800</b>′ may be in LPAR <b>1780</b>-<b>1</b>, LPAR <b>1780</b>-<b>2</b>, . . . , LPAR <b>1780</b>-K. In another embodiment, bridging IHS <b>1700</b> may store an operating system (not shown) that governs operation of bridging IHS <b>1700</b>, where the operating system includes a hypervisor (not shown) and where the operating system includes LPAR <b>1780</b>-<b>1</b>, LPAR <b>1780</b>-<b>2</b>, . . . , LPAR <b>1780</b>-K as virtual machines (not shown). When bridging IHS <b>1700</b> initializes, the IHS loads hypervisor <b>1745</b> into system memory <b>1715</b> for execution as hypervisor <b>1745</b>′. Bridging IHS <b>1700</b> also loads bridging tool <b>1800</b>′ into system memory <b>1715</b> for execution as bridging tool <b>1800</b>″. Bridging IHS <b>1700</b> may also load LPAR <b>1780</b>-<b>1</b>, LPAR <b>1780</b>-<b>2</b>, . . . , LPAR <b>1780</b>-K into system memory <b>1715</b> for execution as LPAR <b>1780</b>-<b>1</b>′, LPAR <b>1780</b>-<b>2</b>′, . . . , LPAR <b>1780</b>-K′, respectively.
0257In another embodiment, when bridging IHS <b>1700</b> initializes, the IHS may load an operating system (not shown) into system memory <b>1715</b> for execution. In another embodiment, when bridging IHS <b>1700</b> initializes, the IHS may load an operating system (not shown) that includes a hypervisor (not shown) and includes LPAR <b>1780</b>-<b>1</b>, LPAR <b>1780</b>-<b>2</b>, . . . , LPAR <b>1780</b>-K as virtual machines (not shown) into system memory <b>1715</b> for execution.
0258<figref idref="DRAWINGS">FIG. 18</figref> is a flowchart that shows a representative process flow of a bridging tool <b>1800</b> that may be used in the disclosed bridging system. Process flow commences when bridging tool <b>1800</b> in bridging IHS <b>1700</b> initializes, as per block <b>1805</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does not transmit HCM database <b>580</b>, as per decision block <b>1810</b>, process flow continues at decision block <b>1810</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does transmit HCM database <b>580</b>, as per decision block <b>1810</b>, a hypervisor agent in bridging IHS <b>1700</b> may receive HCM database <b>580</b>, as per block <b>1815</b>. In one embodiment, the hypervisor agent in the bridging IHS <b>1700</b> is included in hypervisor <b>1745</b>.
0259The hypervisor agent may allow hypervisor <b>1745</b> to access HCM database <b>580</b>. Hypervisor <b>1745</b> may transmit HCM database <b>580</b> to bridging tool <b>1800</b>, as per block <b>1820</b>. Bridging tool <b>1800</b> may extract the hardware configuration information of bridging IHS <b>1700</b> from the HCM database <b>580</b>, as per block <b>1825</b>. In one embodiment, the hardware configuration information of bridging IHS <b>1700</b> from HCM database <b>580</b> may include, but is not limited to, on a per adapter basis, machine serial numbers (MSNs), physical identifications (PIDs), logical identifications (LIDs), adapter types, a logical partition (LPAR) access list, a physical network identification (PNet ID) of the first port of the adapter and a PNet ID of the second port of the adapter. In one embodiment, the adapter type “0087” may be an OSA adapter and the adapter type “008D” may be an internal queued direct (IQD) communication adapter.
0260In one embodiment, the bridging tool <b>1800</b> may share the extracted hardware configuration information of bridging IHS <b>1700</b> with hypervisor <b>1745</b>. Hypervisor <b>1745</b> may update the hardware configuration of bridging IHS <b>1700</b> with the extracted hardware configuration information of bridging IHS <b>1700</b>. In another embodiment, the bridging tool <b>1800</b> may share the extracted hardware configuration information of bridging IHS <b>1700</b> with LPARs <b>1780</b>-<b>1</b>, <b>1780</b>-<b>2</b>, . . . , <b>1780</b>-K, where K is the number of LPARs in bridging IHS <b>1700</b>. LPARs <b>1780</b>-<b>1</b>, <b>1780</b>-<b>2</b>, . . . , <b>1780</b>-K may update their respective hardware configuration with the extracted hardware configuration information of bridging IHS <b>1700</b>.
0261Bridging tool <b>1800</b> may sort the extracted hardware configuration information by PNet IDs, as per block <b>1830</b>. For example, the bridging tool <b>1800</b> may list all adapters with the PNet ID of “NETA” first, followed by all adapters with the PNet ID of “NETB”. Bridging tool <b>1800</b> may further sort the extracted configuration information by adapter type, as per block <b>1835</b>. For example, the bridging tool <b>1800</b> may list all adapters with the type “0087” and the PNet ID “NETA” first, followed by the adapters with the type “008D” and the PNet ID of “NETA”, further followed by the adapters with the type “0087” and the PNet ID of “NETB”.
0262Bridging tool <b>1800</b> may determine if any adapters may be bridged, as per decision block <b>1840</b>. In one embodiment, bridging tool <b>1800</b> may bridge adapters with the type “008D”, i.e. IQD, with adapters of the type “0087”, i.e. OSA, if the IQD adapter's PNet ID matches the OSA's PNet ID. If bridging tool <b>1800</b> determines that bridging IHS <b>1700</b> contains bridgeable adapters, as per block <b>1840</b>, bridging tool <b>1800</b> may bridge communications between IQD adapters and OSAs that have matching PNet IDs, as per block <b>1845</b>. For example, as shown in <figref idref="DRAWINGS">FIGS. 13 and 14</figref>, virtual internal network adapter <b>1321</b>-<b>7</b> is of type “008D”, i.e. IQD, and has a PNet ID of “NETC”. Network adapter <b>1317</b> is of type “007”, i.e. OSA, and has a PNet ID of “NETC”.
0263Bridging tool <b>1800</b> may bridge communications between virtual internal network adapter <b>1321</b>-<b>7</b> and network adapter <b>1317</b>. In one embodiment, virtual internal network adapter <b>1321</b>-<b>7</b> and bridge port <b>1327</b> are coupled. To bridge communications between virtual internal network adapter <b>1321</b>-<b>7</b> and network adapter <b>1317</b>, bridging tool <b>1800</b> may bridge communications from bridge port <b>1327</b>, through VSWITCH <b>1330</b>, to network adapter <b>1327</b>. In one embodiment, LPAR <b>1320</b>-<b>7</b> may then communicate over the bridge between virtual internal network adapter <b>1321</b>-<b>7</b> and network adapter <b>1317</b> to any IHS on NETWORK C <b>1318</b>, as per block <b>1850</b>.
0264Process flow terminates at end block <b>1855</b>. If bridging tool <b>1800</b> determines that no adapters on bridging IHS <b>1700</b> may be bridged, as per decision block <b>1840</b>, process flow terminates at end block <b>1855</b>. Alternatively, process flow may continue at start block <b>1805</b>.
0000IV. Load Balancing System
0265<figref idref="DRAWINGS">FIG. 19</figref> is a block diagram showing one embodiment of the disclosed load balancing system <b>1900</b> utilizing PNet IDs. Load balancing system <b>1900</b> may utilize network adapter <b>1901</b>, administrative network <b>1902</b> and network adapter <b>1903</b> to couple HCM IHS <b>500</b> to administered IHS <b>1904</b>. Administered IHS <b>1904</b> may also be referred to as load balancing IHS <b>1904</b>. Load balancing system <b>1900</b> may utilize network adapter <b>1901</b>, administrative network <b>1902</b> and network adapter <b>1905</b> to couple HCM IHS <b>500</b> to administered IHS <b>1906</b>. Load balancing system <b>1900</b> may utilize network adapter <b>1901</b>, administrative network <b>1902</b> and network adapter <b>1907</b> to couple HCM IHS <b>500</b> to administered IHS <b>1908</b>. Load balancing system <b>1900</b> may utilize network adapter <b>1901</b>, administrative network <b>1902</b> and network adapter <b>1909</b> to couple HCM IHS <b>500</b> to administered IHS <b>1910</b>. Administered IHSs <b>1904</b>, <b>1906</b>, <b>1908</b> and <b>1910</b> couple via administrative network <b>1902</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>2000</b> with HCM tool <b>600</b> to the administered IHSs.
0266Load balancing system <b>1900</b> may utilize network adapter <b>1911</b> and/or network adapter <b>1912</b> and/or network adapter <b>1913</b> and/or network adapter <b>1914</b> via NETWORK A <b>1915</b> via network adapter <b>1916</b> and/or network adapter <b>1917</b> and/or network adapter <b>1918</b> and/or network adapter <b>1919</b> to couple load balancing IHS <b>1904</b> to administered IHS <b>1906</b>. Load balancing system <b>1900</b> may utilize network adapter <b>1920</b> and/or network adapter <b>1921</b> and/or network adapter <b>1922</b> and/or network adapter <b>1923</b> via NETWORK B <b>1924</b> via network adapter <b>1925</b> and/or network adapter <b>1926</b> and/or network adapter <b>1927</b> and/or network adapter <b>1928</b> to couple load balancing IHS <b>1904</b> to administered IHS <b>1906</b>. Load balancing system <b>1900</b> may utilize network adapter <b>1929</b> and/or network adapter <b>1930</b> and/or network adapter <b>1931</b> and/or network adapter <b>1932</b> via NETWORK C <b>1933</b> via network adapter <b>1934</b> and/or network adapter <b>1935</b> and/or network adapter <b>1936</b> and/or network adapter <b>1937</b> to couple load balancing IHS <b>1904</b> to administered IHS <b>1910</b>.
0267In one embodiment, network adapter <b>1901</b>, <b>1903</b>, <b>1905</b>, <b>1907</b> and <b>1909</b> may be Ethernet (ETH) adapters. Network adapters <b>1911</b>, <b>1912</b>, <b>1916</b>, <b>1918</b>, <b>1920</b>, <b>1921</b>, <b>1925</b>, <b>1927</b>, <b>1929</b>, <b>1930</b>, <b>1934</b> and <b>1936</b> may be open system adapters (OSAs). Network adapters <b>1913</b>, <b>1914</b>, <b>1917</b>, <b>1919</b>, <b>1922</b>, <b>1923</b>, <b>1926</b>, <b>1928</b>, <b>1931</b>, <b>1933</b>, <b>1935</b> and <b>1937</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>1902</b>, NETWORK A <b>1915</b>, NETWORK B <b>1924</b> and NETWORK C <b>1933</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0268Load balancing IHS <b>1904</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>1938</b>-<b>1</b>, LPAR <b>1938</b>-<b>2</b>, LPAR <b>1938</b>-<b>3</b>, LPAR <b>1938</b>-<b>4</b>, LPAR <b>1938</b>-<b>5</b>, LPAR <b>1938</b>-<b>6</b> and LPAR <b>1938</b>-<b>7</b> in load balancing IHS <b>1904</b>. LPAR <b>1938</b>-<b>1</b>, LPAR <b>1938</b>-<b>2</b> and LPAR <b>1938</b>-<b>3</b> may include virtual network adapter <b>1939</b>-<b>1</b>, virtual network adapter <b>1939</b>-<b>2</b> and virtual network adapter <b>1939</b>-<b>3</b>, respectively. Virtual network adapter <b>1939</b>-<b>1</b>, virtual network adapter <b>1939</b>-<b>2</b> and virtual network adapter <b>1939</b>-<b>3</b> may couple to network adapter <b>1911</b> and network adapter <b>1912</b> via a channel, i.e., a bus. LPAR <b>1938</b>-<b>4</b> and LPAR <b>1938</b>-<b>5</b> may include virtual network adapter <b>1939</b>-<b>4</b> and virtual network adapter <b>1939</b>-<b>5</b>, respectively. Virtual network adapter <b>1939</b>-<b>4</b> and virtual network adapter <b>1939</b>-<b>5</b> may couple to network adapter <b>1920</b> and network adapter <b>1921</b> via a channel. LPAR <b>1938</b>-<b>6</b> and LPAR <b>1938</b>-<b>7</b> may include virtual network adapter <b>1939</b>-<b>6</b> and virtual network adapter <b>1939</b>-<b>7</b>, respectively. Virtual network adapter <b>1939</b>-<b>6</b> and virtual network adapter <b>1939</b>-<b>7</b> may couple to network adapter <b>1929</b> and network adapter <b>1930</b> via a channel.
0269LPAR <b>1938</b>-<b>1</b>, LPAR <b>1938</b>-<b>2</b> and LPAR <b>1938</b>-<b>3</b> may include virtual network adapter <b>1940</b>-<b>1</b>, virtual network adapter <b>1940</b>-<b>2</b> and virtual network adapter <b>1940</b>-<b>3</b>, respectively. Virtual network adapter <b>1940</b>-<b>1</b>, virtual network adapter <b>1940</b>-<b>2</b> and virtual network adapter <b>1940</b>-<b>3</b> may couple to network adapter <b>1913</b> and network adapter <b>1914</b> via a channel. LPAR <b>1938</b>-<b>4</b> and LPAR <b>1938</b>-<b>5</b> may include virtual network adapter <b>1940</b>-<b>4</b> and virtual network adapter <b>1940</b>-<b>5</b>, respectively. Virtual network adapter <b>1940</b>-<b>4</b> and virtual network adapter <b>1940</b>-<b>5</b> may couple to network adapter <b>1922</b> and network adapter <b>1923</b> via a channel. LPAR <b>1938</b>-<b>6</b> and LPAR <b>1938</b>-<b>7</b> may include virtual network adapter <b>1940</b>-<b>6</b> and virtual network adapter <b>1940</b>-<b>7</b>, respectively. Virtual network adapter <b>1940</b>-<b>6</b> and virtual network adapter <b>1940</b>-<b>7</b> may couple to network adapter <b>1931</b> and network adapter <b>1932</b> via a channel.
0270<figref idref="DRAWINGS">FIG. 20</figref> depicts one embodiment of HCM database <b>2000</b> in the disclosed load balancing system <b>1900</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>2000</b> on a per adapter basis. In one embodiment, for each network adapter in load balancing system <b>1900</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0271As shown in HCM database <b>2000</b>, the hardware configuration information of adapter <b>1911</b> includes MSN of 0000FFA1, PID of 0006, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1911</b> is located in physical channel 0006 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 00F1. Adapter <b>1911</b> is a physical OSA network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> of load balancing IHS <b>1904</b> may access adapter <b>1911</b> to communicate via NETWORK A <b>1915</b>.
0272The hardware configuration information of adapter <b>1912</b> includes MSN of 0000FFA1, PID of 0007, LID of 00F5, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1912</b> is located in physical channel 0007 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 00F5. Adapter <b>1912</b> is a physical OSA network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> of load balancing IHS <b>1904</b> may access adapter <b>1912</b> to communicate via NETWORK A <b>1915</b>.
0273The hardware configuration information of adapter <b>1913</b> includes MSN of 0000FFA1, PID of 0111, LID of 04CO<sub>3 </sub>type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1913</b> is located in physical channel 0111 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04C0. Adapter <b>1913</b> is a physical RNIC network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> of load balancing IHS <b>1904</b> may access adapter <b>1913</b> to communicate via NETWORK A <b>1915</b>.
0274The hardware configuration information of adapter <b>1914</b> includes MSN of 0000FFA1, PID of 0112, LID of 04C4, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1914</b> is located in physical channel 0112 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04C4. Adapter <b>1914</b> is a physical RNIC network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> of load balancing IHS <b>1904</b> may access adapter <b>1914</b> to communicate via NETWORK A <b>1915</b>.
0275The hardware configuration information of adapter <b>1920</b> includes MSN of 0000FFA1, PID of 0008, LID of 00F9, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1920</b> is located in physical channel 0008 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 00F9. Adapter <b>1920</b> is a physical OSA network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>4</b> and <b>1938</b>-<b>5</b> of load balancing IHS <b>1904</b> may access adapter <b>1920</b> to communicate via NETWORK B <b>1924</b>.
0276The hardware configuration information of adapter <b>1921</b> includes MSN of 0000FFA1, PID of 0009, LID of 00FC, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1921</b> is located in physical channel 0009 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 00FC. Adapter <b>1921</b> is a physical OSA network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>4</b> and <b>1938</b>-<b>5</b> of load balancing IHS <b>1904</b> may access adapter <b>1921</b> to communicate via NETWORK B <b>1924</b>.
0277The hardware configuration information of adapter <b>1922</b> includes MSN of 0000FFA1, PID of 0113, LID of 04C8, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1922</b> is located in physical channel 0113 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04C8. Adapter <b>1922</b> is a physical RNIC network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>4</b> and <b>1938</b>-<b>5</b> of load balancing IHS <b>1904</b> may access adapter <b>1922</b> to communicate via NETWORK B <b>1924</b>.
0278The hardware configuration information of adapter <b>1923</b> includes MSN of 0000FFA1, PID of 0114, LID of 04CB, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1923</b> is located in physical channel 0114 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04CB. Adapter <b>1923</b> is a physical RNIC network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>4</b> and <b>1938</b>-<b>5</b> of load balancing IHS <b>1904</b> may access adapter <b>1923</b> to communicate via NETWORK B <b>1924</b>.
0279The hardware configuration information of adapter <b>1929</b> includes MSN of 0000FFA1, PID of 000A, LID of 00FF, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1929</b> is located in physical channel 000A in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 00FF. Adapter <b>1929</b> is a physical OSA network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>6</b> and <b>1938</b>-<b>7</b> of load balancing IHS <b>1904</b> may access adapter <b>1929</b> to communicate via NETWORK C <b>1933</b>.
0280The hardware configuration information of adapter <b>1930</b> includes MSN of 0000FFA1, PID of 000B, LID of 0102, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1930</b> is located in physical channel 000B in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 0102. Adapter <b>1930</b> is a physical OSA network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>6</b> and <b>1938</b>-<b>7</b> of load balancing IHS <b>1904</b> may access adapter <b>1930</b> to communicate via NETWORK C <b>1933</b>.
0281The hardware configuration information of adapter <b>1931</b> includes MSN of 0000FFA1, PID of 0115, LID of 04CE, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1931</b> is located in physical channel 0115 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04CE. Adapter <b>1931</b> is a physical RNIC network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>6</b> and <b>1938</b>-<b>7</b> of load balancing IHS <b>1904</b> may access adapter <b>1931</b> to communicate via NETWORK C <b>1933</b>.
0282The hardware configuration information of adapter <b>1932</b> includes MSN of 0000FFA1, PID of 0116, LID of 04D1, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1932</b> is located in physical channel 0116 in load balancing IHS <b>1904</b> and may be identified logically by load balancing IHS <b>1904</b> as 04D1. Adapter <b>1932</b> is a physical RNIC network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. LPAR <b>1938</b>-<b>6</b> and <b>1938</b>-<b>7</b> of load balancing IHS <b>1904</b> may access adapter <b>1932</b> to communicate via NETWORK C <b>1933</b>.
0283The hardware configuration information of adapter <b>1916</b> includes MSN of 00DDA254, PID of 0001, LID of 00A3, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1916</b> is located in physical channel 0001 in administered IHS <b>1906</b> and may be identified logically by administered IHS <b>1906</b> as 00A3. Adapter <b>1916</b> is a physical OSA network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. Administered IHS <b>1906</b> may access adapter <b>1916</b> to communicate via NETWORK A <b>1915</b>.
0284The hardware configuration information of adapter <b>1917</b> includes MSN of 00DDA254, PID of 0003, LID of 00B1, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1917</b> is located in physical channel 0003 in administered IHS <b>1906</b> and may be identified logically by administered IHS <b>1906</b> as 00B1. Adapter <b>1917</b> is a physical RNIC network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. Administered IHS <b>1906</b> may access adapter <b>1917</b> to communicate via NETWORK A <b>1915</b>.
0285The hardware configuration information of adapter <b>1918</b> includes MSN of 00DDA254, PID of 0002, LID of 00A4, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1918</b> is located in physical channel 0002 in administered IHS <b>1906</b> and may be identified logically by administered IHS <b>1906</b> as 00A4. Adapter <b>1918</b> is a physical OSA network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. Administered IHS <b>1906</b> may access adapter <b>1918</b> to communicate via NETWORK A <b>1915</b>.
0286The hardware configuration information of adapter <b>1919</b> includes MSN of 00DDA254, PID of 0004, LID of 00B2, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>1919</b> is located in physical channel 0004 in administered IHS <b>1906</b> and may be identified logically by administered IHS <b>1906</b> as 00B2. Adapter <b>1919</b> is a physical RNIC network adapter and couples to NETWORK A <b>1915</b> on both ports 1 and 2. Administered IHS <b>1906</b> may access adapter <b>1919</b> to communicate via NETWORK A <b>1915</b>.
0287The hardware configuration information of adapter <b>1925</b> includes MSN of FAF33922, PID of 0023, LID of 00F6, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1925</b> is located in physical channel 0023 in administered IHS <b>1908</b> and may be identified logically by administered IHS <b>1908</b> as 00F6. Adapter <b>1925</b> is a physical OSA network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. Administered IHS <b>1908</b> may access adapter <b>1925</b> to communicate via NETWORK B <b>1924</b>.
0288The hardware configuration information of adapter <b>1926</b> includes MSN of FAF33922, PID of 0032, LID of 00FF, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1926</b> is located in physical channel 0032 in administered IHS <b>1908</b> and may be identified logically by administered IHS <b>1908</b> as 00FF. Adapter <b>1926</b> is a physical RNIC network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. Administered IHS <b>1908</b> may access adapter <b>1926</b> to communicate via NETWORK B <b>1924</b>.
0289The hardware configuration information of adapter <b>1927</b> includes MSN of FAF33922, PID of 0024, LID of 00F7, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1927</b> is located in physical channel 0024 in administered IHS <b>1908</b> and may be identified logically by administered IHS <b>1908</b> as 00F7. Adapter <b>1927</b> is a physical OSA network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. Administered IHS <b>1908</b> may access adapter <b>1927</b> to communicate via NETWORK B <b>1924</b>.
0290The hardware configuration information of adapter <b>1928</b> includes MSN of FAF33922, PID of 0033, LID of 0100, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>1928</b> is located in physical channel 0033 in administered IHS <b>1908</b> and may be identified logically by administered IHS <b>1908</b> as 0100. Adapter <b>1928</b> is a physical RNIC network adapter and couples to NETWORK B <b>1924</b> on both ports 1 and 2. Administered IHS <b>1908</b> may access adapter <b>1928</b> to communicate via NETWORK B <b>1924</b>.
0291The hardware configuration information of adapter <b>1934</b> includes MSN of 363B77A2, PID of 0011, LID of 00C2, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1934</b> is located in physical channel 0011 in administered IHS <b>1910</b> and may be identified logically by administered IHS <b>1910</b> as 00C2. Adapter <b>1934</b> is a physical OSA network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. Administered IHS <b>1910</b> may access adapter <b>1934</b> to communicate via NETWORK C <b>1933</b>.
0292The hardware configuration information of adapter <b>1935</b> includes MSN of 363B77A2, PID of 0002, LID of 0D01, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1935</b> is located in physical channel 0002 in administered IHS <b>1910</b> and may be identified logically by administered IHS <b>1910</b> as 0D01. Adapter <b>1935</b> is a physical RNIC network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. Administered IHS <b>1910</b> may access adapter <b>1935</b> to communicate via NETWORK C <b>1933</b>.
0293The hardware configuration information of adapter <b>1936</b> includes MSN of 363B77A2, PID of 0012, LID of 00C3, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1936</b> is located in physical channel 0012 in administered IHS <b>1910</b> and may be identified logically by administered IHS <b>1910</b> as 00C3. Adapter <b>1936</b> is a physical OSA network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. Administered IHS <b>1910</b> may access adapter <b>1936</b> to communicate via NETWORK C <b>1933</b>.
0294The hardware configuration information of adapter <b>1937</b> includes MSN of 363B77A2, PID of 0003, LID of 0D02, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>1937</b> is located in physical channel 0003 in administered IHS <b>1910</b> and may be identified logically by administered IHS <b>1910</b> as 0D02. Adapter <b>1937</b> is a physical RNIC network adapter and couples to NETWORK C <b>1933</b> on both ports 1 and 2. Administered IHS <b>1910</b> may access adapter <b>1937</b> to communicate via NETWORK C <b>1933</b>.
0295<figref idref="DRAWINGS">FIG. 21</figref> is a block diagram showing one embodiment of the disclosed load balancing system <b>2100</b> utilizing PNet IDs. Load balancing system <b>2100</b> may utilize network adapter <b>2101</b>, administrative network <b>2102</b> and network adapter <b>2103</b> to couple HCM IHS <b>500</b> to administered IHS <b>2104</b>. Administered IHS <b>2104</b> may also be referred to as load balancing IHS <b>2104</b>. Load balancing system <b>2100</b> may utilize network adapter <b>2101</b>, administrative network <b>2102</b> and network adapter <b>2105</b> to couple HCM IHS <b>500</b> to administered IHS <b>2106</b>. Load balancing system <b>2100</b> may utilize network adapter <b>2101</b>, administrative network <b>2102</b> and network adapter <b>2107</b> to couple HCM IHS <b>500</b> to administered IHS <b>2108</b>. Administered IHSs <b>2104</b>, <b>2106</b> and <b>2108</b> couple via administrative network <b>2102</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>2200</b> with HCM tool <b>600</b> to the administered IHSs.
0296Load balancing system <b>2100</b> may utilize network adapter <b>2109</b> and/or network adapter <b>2110</b> and/or network adapter <b>2111</b> and/or network adapter <b>2112</b> and/or network adapter <b>2113</b> and/or network adapter <b>2114</b> via NETWORK A <b>2115</b> via network adapter <b>2116</b> and/or network adapter <b>2117</b> and/or network adapter <b>2118</b> and/or network adapter <b>2119</b> to couple load balancing IHS <b>2104</b> to administered IHS <b>2106</b>. Load balancing system <b>2100</b> may utilize network adapter <b>2120</b> and/or network adapter <b>2121</b> and/or network adapter <b>2122</b> and/or network adapter <b>2123</b> and/or network adapter <b>2124</b> and/or network adapter <b>2125</b> via NETWORK B <b>2126</b> via network adapter <b>2127</b> and/or network adapter <b>2128</b> and/or network adapter <b>2129</b> and/or network adapter <b>2130</b> to couple load balancing IHS <b>2104</b> to administered IHS <b>2106</b>.
0297In one embodiment, network adapter <b>2101</b>, <b>2103</b>, <b>2105</b> and <b>2107</b> may be Ethernet (ETH) adapters. Network adapters <b>2109</b>, <b>2110</b>, <b>2113</b>, <b>2116</b>, <b>2118</b>, <b>2120</b>, <b>2122</b>, <b>2123</b>, <b>2127</b> and <b>2128</b> may be open system adapters (OSAs). Network adapters <b>2111</b>, <b>2112</b>, <b>2114</b>, <b>2117</b>, <b>2119</b>, <b>2121</b>, <b>2124</b>, <b>2125</b>, <b>2129</b> and <b>2130</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>2102</b>, NETWORK A <b>2115</b> and NETWORK B <b>2126</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0298Load balancing IHS <b>2104</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>2131</b>-<b>1</b>, LPAR <b>2131</b>-<b>2</b>, LPAR <b>2131</b>-<b>3</b>, LPAR <b>2131</b>-<b>4</b> and LPAR <b>2131</b>-<b>5</b> in load balancing IHS <b>2104</b>. LPAR <b>2131</b>-<b>1</b>, LPAR <b>2131</b>-<b>2</b> and LPAR <b>2131</b>-<b>3</b> may include virtual network adapter <b>2132</b>-<b>1</b>, virtual network adapter <b>2132</b>-<b>2</b> and virtual network adapter <b>2132</b>-<b>3</b>, respectively. Virtual network adapter <b>2132</b>-<b>1</b>, virtual network adapter <b>2132</b>-<b>2</b> and virtual network adapter <b>2132</b>-<b>3</b> may couple to network adapter <b>2109</b>, network adapter <b>2110</b> and network adapter <b>2113</b> via a channel, i.e., a bus. LPAR <b>2131</b>-<b>4</b> and LPAR <b>2131</b>-<b>5</b> may include virtual network adapter <b>2132</b>-<b>4</b> and virtual network adapter <b>2132</b>-<b>5</b>, respectively. Virtual network adapter <b>2132</b>-<b>4</b> and virtual network adapter <b>2132</b>-<b>5</b> may couple to network adapter <b>2120</b>, network adapter <b>2121</b> and network adapter <b>2123</b> via a channel.
0299LPAR <b>2131</b>-<b>1</b>, LPAR <b>2131</b>-<b>2</b> and LPAR <b>2131</b>-<b>3</b> may include virtual network adapter <b>2133</b>-<b>1</b>, virtual network adapter <b>2133</b>-<b>2</b> and virtual network adapter <b>2133</b>-<b>3</b>, respectively. Virtual network adapter <b>2133</b>-<b>1</b>, virtual network adapter <b>2133</b>-<b>2</b> and virtual network adapter <b>2133</b>-<b>3</b> may couple to network adapter <b>2111</b>, network adapter <b>2112</b> and network adapter <b>2114</b> via a channel. LPAR <b>2131</b>-<b>4</b> and LPAR <b>2131</b>-<b>5</b> may include virtual network adapter <b>2133</b>-<b>4</b> and virtual network adapter <b>2133</b>-<b>5</b>, respectively. Virtual network adapter <b>2133</b>-<b>4</b> and virtual network adapter <b>2133</b>-<b>5</b> may couple to network adapter <b>2121</b>, network adapter <b>2124</b> and network adapter <b>2125</b> via a channel.
0300In one embodiment, administered IHS <b>2108</b> may be a load balancing IHS. Administered IHS <b>2108</b> may include a hypervisor (not shown) that may create LPAR <b>2134</b>-<b>1</b> and LPAR <b>2134</b>-<b>2</b>. LPAR <b>2134</b>-<b>1</b> and LPAR <b>2134</b>-<b>2</b> may include virtual network adapter <b>2135</b>-<b>1</b> and virtual network adapter <b>2135</b>-<b>2</b>, respectively. Virtual network adapter <b>2135</b>-<b>1</b> and virtual network adapter <b>2135</b>-<b>2</b> may couple to network adapter <b>2127</b> and network adapter <b>2128</b> via a channel. LPAR <b>2134</b>-<b>1</b> and LPAR <b>2134</b>-<b>2</b> may include virtual network adapter <b>2136</b>-<b>1</b> and virtual network adapter <b>2136</b>-<b>2</b>, respectively. Virtual network adapter <b>2136</b>-<b>1</b> and virtual network adapter <b>2136</b>-<b>2</b> may couple to network adapter <b>2129</b> and network adapter <b>2130</b> via a channel.
0301<figref idref="DRAWINGS">FIG. 22</figref> depicts one embodiment of HCM database <b>2200</b> in the disclosed load balancing system <b>2100</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>2200</b> on a per adapter basis. In one embodiment, for each network adapter in load balancing system <b>2100</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0302As shown in HCM database <b>2200</b>, the hardware configuration information of adapter <b>2109</b> includes MSN of 0DC0FFB2, PID of 0001, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2109</b> is located in physical channel 0001 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 00F1. Adapter <b>2109</b> is a physical OSA network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2109</b> to communicate via NETWORK A <b>2115</b>.
0303The hardware configuration information of adapter <b>2110</b> includes MSN of 0DC0FFB2, PID of 0002, LID of 00F5, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2110</b> is located in physical channel 0002 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 00F5. Adapter <b>2110</b> is a physical OSA network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2110</b> to communicate via NETWORK A <b>2115</b>.
0304The hardware configuration information of adapter <b>2111</b> includes MSN of 0DC0FFB2, PID of 0111, LID of 0FF1, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2111</b> is located in physical channel 0111 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0FF1. Adapter <b>2111</b> is a physical RNIC network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2111</b> to communicate via NETWORK A <b>2115</b>.
0305The hardware configuration information of adapter <b>2112</b> includes MSN of 0DC0FFB2, PID of 0112, LID of 0FF5, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2112</b> is located in physical channel 0112 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0FF5. Adapter <b>2112</b> is a physical RNIC network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2112</b> to communicate via NETWORK A <b>2115</b>.
0306The hardware configuration information of adapter <b>2113</b> includes MSN of 0DC0FFB2, PID of 0003, LID of 00F9, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2113</b> is located in physical channel 0003 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 00F9. Adapter <b>2113</b> is a physical OSA network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2113</b> to communicate via NETWORK A <b>2115</b>.
0307The hardware configuration information of adapter <b>2114</b> includes MSN of 0DC0FFB2, PID of 0113, LID of 0FF9, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2114</b> is located in physical channel 0113 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0FF9. Adapter <b>2114</b> is a physical RNIC network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>1</b>, <b>2131</b>-<b>2</b> and <b>2131</b>-<b>3</b> of load balancing IHS <b>2104</b> may access adapter <b>2114</b> to communicate via NETWORK A <b>2115</b>.
0308The hardware configuration information of adapter <b>2120</b> includes MSN of 0DC0FFB2, PID of 0004, LID of 00FD, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2120</b> is located in physical channel 0004 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 00FD. Adapter <b>2120</b> is a physical OSA network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2120</b> to communicate via NETWORK B <b>2126</b>.
0309The hardware configuration information of adapter <b>2121</b> includes MSN of 0DC0FFB2, PID of 0114, LID of 0FFD, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2121</b> is located in physical channel 0114 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0FFD. Adapter <b>2121</b> is a physical RNIC network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2121</b> to communicate via NETWORK B <b>2126</b>.
0310The hardware configuration information of adapter <b>2122</b> includes MSN of 0DC0FFB2, PID of 0005, LID of 0100, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2122</b> is located in physical channel 0005 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0100. Adapter <b>2122</b> is a physical OSA network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2122</b> to communicate via NETWORK B <b>2126</b>.
0311The hardware configuration information of adapter <b>2123</b> includes MSN of 0DC0FFB2, PID of 0006, LID of 0103, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2123</b> is located in physical channel 0006 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 0103. Adapter <b>2123</b> is a physical OSA network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2123</b> to communicate via NETWORK B <b>2126</b>.
0312The hardware configuration information of adapter <b>2124</b> includes MSN of 0DC0FFB2, PID of 0115, LID of 1000, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2124</b> is located in physical channel 0115 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 1000. Adapter <b>2124</b> is a physical RNIC network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2124</b> to communicate via NETWORK B <b>2126</b>.
0313The hardware configuration information of adapter <b>2125</b> includes MSN of 0DC0FFB2, PID of 0116, LID of 1003, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2125</b> is located in physical channel 0116 in load balancing IHS <b>2104</b> and may be identified logically by load balancing IHS <b>2104</b> as 1003. Adapter <b>2125</b> is a physical RNIC network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2131</b>-<b>4</b> and <b>2131</b>-<b>5</b> of load balancing IHS <b>2104</b> may access adapter <b>2125</b> to communicate via NETWORK B <b>2126</b>.
0314The hardware configuration information of adapter <b>2116</b> includes MSN of 0000D100, PID of 0033, LID of 0D01, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2116</b> is located in physical channel 0033 in administered IHS <b>2106</b> and may be identified logically by administered IHS <b>2106</b> as 0D01. Adapter <b>2116</b> is a physical OSA network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. Administered IHS <b>2106</b> may access adapter <b>2116</b> to communicate via NETWORK A <b>2115</b>.
0315The hardware configuration information of adapter <b>2117</b> includes MSN of 0000D100, PID of 0025, LID of 0D03, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2117</b> is located in physical channel 0025 in administered IHS <b>2106</b> and may be identified logically by administered IHS <b>2106</b> as 0D03. Adapter <b>2117</b> is a physical RNIC network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. Administered IHS <b>2106</b> may access adapter <b>2117</b> to communicate via NETWORK A <b>2115</b>.
0316The hardware configuration information of adapter <b>2118</b> includes MSN of 0000D100, PID of 0034, LID of 0D02, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2118</b> is located in physical channel 0034 in administered IHS <b>2106</b> and may be identified logically by administered IHS <b>2106</b> as 0D02. Adapter <b>2118</b> is a physical OSA network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. Administered IHS <b>2106</b> may access adapter <b>2118</b> to communicate via NETWORK A <b>2115</b>.
0317The hardware configuration information of adapter <b>2119</b> includes MSN of 0000D100, PID of 0026, LID of 0D04, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2119</b> is located in physical channel 0026 in administered IHS <b>2106</b> and may be identified logically by administered IHS <b>2106</b> as 0D04. Adapter <b>2119</b> is a physical RNIC network adapter and couples to NETWORK A <b>2115</b> on both ports 1 and 2. Administered IHS <b>2106</b> may access adapter <b>2119</b> to communicate via NETWORK A <b>2115</b>.
0318The hardware configuration information of adapter <b>2127</b> includes MSN of FFFFA200, PID of 0011, LID of 000A, type of 0087, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2127</b> is located in physical channel 0011 in load balancing IHS <b>2108</b> and may be identified logically by load balancing IHS <b>2108</b> as 000A. Adapter <b>2127</b> is a physical OSA network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2134</b>-<b>1</b> and <b>2134</b>-<b>2</b> of load balancing IHS <b>2108</b> may access adapter <b>2127</b> to communicate via NETWORK B <b>2126</b>.
0319The hardware configuration information of adapter <b>2128</b> includes MSN of FFFFA200, PID of 0012, LID of 000B, type of 0087, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2128</b> is located in physical channel 0012 in load balancing IHS <b>2108</b> and may be identified logically by load balancing IHS <b>2108</b> as 000B. Adapter <b>2128</b> is a physical OSA network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2134</b>-<b>1</b> and <b>2134</b>-<b>2</b> of load balancing IHS <b>2108</b> may access adapter <b>2128</b> to communicate via NETWORK B <b>2126</b>.
0320The hardware configuration information of adapter <b>2129</b> includes MSN of FFFFA200, PID of 0021, LID of 0F01, type of 0008, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2129</b> is located in physical channel 0021 in load balancing IHS <b>2108</b> and may be identified logically by load balancing IHS <b>2108</b> as 0F01. Adapter <b>2129</b> is a physical RNIC network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2134</b>-<b>1</b> and <b>2134</b>-<b>2</b> of load balancing IHS <b>2108</b> may access adapter <b>2129</b> to communicate via NETWORK B <b>2126</b>.
0321The hardware configuration information of adapter <b>2130</b> includes MSN of FFFFA200, PID of 0022, LID of 0F02, type of 0008, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2130</b> is located in physical channel 0022 in load balancing IHS <b>2108</b> and may be identified logically by load balancing IHS <b>2108</b> as 0F02. Adapter <b>2130</b> is a physical RNIC network adapter and couples to NETWORK B <b>2126</b> on both ports 1 and 2. LPAR <b>2134</b>-<b>1</b> and <b>2134</b>-<b>2</b> of load balancing IHS <b>2108</b> may access adapter <b>2130</b> to communicate via NETWORK B <b>2126</b>.
0322<figref idref="DRAWINGS">FIG. 23</figref> is a block diagram of a load balancing information handling system (IHS) <b>2300</b> that may be used in the disclosed load balancing system. With respect to <figref idref="DRAWINGS">FIG. 11</figref>, like numbers indicate like elements. Load balancing IHS <b>2300</b> includes a processor <b>2305</b> that may include multiple cores. RNIC converging IHS <b>2300</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. In one embodiment, load balancing IHS <b>2300</b> includes a bus <b>2310</b>, i.e. channel <b>2310</b>. In another embodiment, bus <b>2310</b> may be multiple busses, i.e., multiple channels. Bus <b>2310</b> may couple processor <b>2305</b> to memory <b>2315</b> via a memory controller <b>2320</b> and memory bus <b>2325</b>. System memory <b>2315</b> may also be referred to as main memory. System memory <b>2315</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>2305</b> may also include local memory such as L1, L2 and L3 caches.
0323In one embodiment, a video graphics controller <b>2330</b> couples display <b>2335</b> to bus <b>2310</b>. In another embodiment, load balancing IHS <b>2300</b> may operate without display <b>2335</b> and/or video graphics controller <b>2330</b>. Nonvolatile storage <b>2340</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>2310</b> to provide load balancing IHS <b>2300</b> with permanent storage of information. System memory <b>2315</b> and nonvolatile storage <b>2340</b> are both forms of memory stores. In one embodiment, nonvolatile storage <b>2340</b> stores a hypervisor <b>2345</b> (HYPERVISOR) that governs operation of load balancing IHS <b>2300</b>. In another embodiment, nonvolatile storage <b>2340</b> may store an operating system (not shown) that governs operation of load balancing IHS <b>2300</b>. In another embodiment, nonvolatile storage <b>2340</b> may store an operating system (not shown) that governs operation of load balancing IHS <b>2300</b>, where the operating system includes a hypervisor (not shown).
0324I/O devices <b>2350</b>, such as speakers, a keyboard and a pointing device, may couple to bus <b>2310</b> via I/O controller <b>2355</b> and I/O bus <b>2360</b>. One or more expansion busses <b>2365</b>, i.e. channels <b>2365</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, i.e. channels, couple to bus <b>2310</b> to facilitate the connection of peripherals and devices to load balancing IHS <b>2300</b>. Network interface controllers (NICs), for example, NIC <b>2370</b>-<b>1</b>, NIC <b>2370</b>-<b>2</b>, . . . , NIC <b>2370</b>-J, wherein J is the number of NICs, may couple to bus <b>2310</b> to enable load balancing IHS <b>2300</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>2370</b>-<b>1</b>, NIC <b>2370</b>-<b>2</b>, . . . , NIC <b>2370</b>-J may also be called a network communication adapter, network interface adapter, network adapter, network interface or an adapter. NIC <b>2370</b>-<b>1</b>, NIC <b>2370</b>-<b>2</b>, . . . , NIC <b>2370</b>-J may take many forms. For example, NIC <b>2370</b>-<b>1</b>, NIC <b>2370</b>-<b>2</b>, . . . , NIC <b>2370</b>-J may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0325While <figref idref="DRAWINGS">FIG. 23</figref> shows one IHS that employs processor <b>2305</b>, the IHS may take many forms. For example, load balancing IHS <b>2300</b> may take the form of a mainframe, server, central processor complex (CPC), desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. Load balancing IHS <b>2300</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0326Load balancing IHS <b>2300</b> includes a load balancing tool computer program product <b>2400</b> on digital media <b>2375</b> such as a CD, DVD or other media. For simplicity, the term load balancing tool will be used below. Load balancing IHS <b>2300</b> may store load balancing tool <b>2400</b> in nonvolatile storage <b>2340</b> as load balancing tool <b>2400</b>′. Load balancing IHS <b>2300</b> may also store hypervisor <b>2345</b> (HYPERVISOR) and logical partition (LPAR) <b>2380</b>-<b>1</b>, LPAR <b>2380</b>-<b>2</b>, . . . , LPAR <b>2380</b>-H, wherein H is the number of LPARs, in nonvolatile storage <b>2340</b>.
0327In another embodiment, load balancing tool <b>2400</b>′ may be part of the hypervisor <b>2345</b> (not shown). In another embodiment, load balancing tool <b>2400</b>′ may be in LPAR <b>2380</b>-<b>1</b>, LPAR <b>2380</b>-<b>2</b>, . . . , LPAR <b>2380</b>-H. In another embodiment, load balancing IHS <b>2300</b> may store an operating system (not shown) that governs operation of load balancing IHS <b>2300</b>, where the operating system includes a hypervisor (not shown) and where the operating system includes LPAR <b>2380</b>-<b>1</b>, LPAR <b>2380</b>-<b>2</b>, . . . , LPAR <b>2380</b>-H as virtual machines (not shown). When load balancing IHS <b>2300</b> initializes, the IHS loads hypervisor <b>2345</b> into system memory <b>2315</b> for execution as hypervisor <b>2345</b>′. Load balancing IHS <b>2300</b> also loads load balancing tool <b>2400</b>′ into system memory <b>2315</b> for execution as load balancing tool <b>2400</b>″. Load balancing IHS <b>2300</b> may also load LPAR <b>2380</b>-<b>1</b>, LPAR <b>2380</b>-<b>2</b>, . . . , LPAR <b>2380</b>-H into system memory <b>2315</b> for execution as LPAR <b>2380</b>-<b>1</b>′, LPAR <b>2380</b>-<b>2</b>′, . . . , LPAR <b>2380</b>-H′, respectively.
0328In another embodiment, when load balancing IHS <b>2300</b> initializes, the IHS may load an operating system (not shown) into system memory <b>2315</b> for execution. In another embodiment, when load balancing IHS <b>2300</b> initializes, the IHS may load an operating system (not shown) that includes a hypervisor (not shown) and includes LPAR <b>2380</b>-<b>1</b>, LPAR <b>2380</b>-<b>2</b>, . . . , LPAR <b>2380</b>-H as virtual machines (not shown) into system memory <b>2315</b> for execution.
0329<figref idref="DRAWINGS">FIG. 24</figref> is a flowchart that shows a representative process flow of a load balancing tool <b>2400</b> that may be used in the disclosed load balancing system. Process flow commences when load balancing tool <b>2400</b> in load balancing IHS <b>2300</b> initializes, as per block <b>2405</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does transmit HCM database <b>580</b>, as per decision block <b>2410</b>, a hypervisor agent in load balancing IHS <b>2300</b> may receive HCM database <b>580</b>, as per block <b>2415</b>. In one embodiment, the hypervisor agent in the load balancing IHS <b>2300</b> is included in hypervisor <b>2345</b>.
0330The hypervisor agent may allow hypervisor <b>2345</b> to access HCM database <b>580</b>. Hypervisor <b>2345</b> may transmit HCM database <b>580</b> to load balancing tool <b>2400</b>, as per block <b>2420</b>. Load balancing tool <b>2400</b> may extract the hardware configuration information of load balancing IHS <b>2300</b> from the HCM database <b>580</b>, as per block <b>2425</b>. In one embodiment, the hardware configuration information of load balancing IHS <b>2300</b> from HCM database <b>580</b> may include, but is not limited to, on a per adapter basis, machine serial numbers (MSNs), physical identifications (PIDs), logical identifications (LIDs), adapter types, a logical partition (LPAR) access list, a physical network identification (PNet ID) of the first port of the adapter and a PNet ID of the second port of the adapter. In one embodiment, the adapter type “0087” may be an OSA network adapter and the adapter type “0008” may be an RNIC network adapter.
0331In one embodiment, the load balancing tool <b>2400</b> may share the extracted hardware configuration information of load balancing IHS <b>2300</b> with hypervisor <b>2345</b>. Hypervisor <b>2345</b> may update the hardware configuration of load balancing IHS <b>2300</b> with the extracted hardware configuration information of load balancing IHS <b>2300</b>. In another embodiment, the load balancing tool <b>2400</b> may share the extracted hardware configuration information of load balancing IHS <b>2300</b> with LPARs <b>2380</b>-<b>1</b>, <b>2380</b>-<b>2</b>, . . . , <b>2380</b>-H, where H is the number of LPARs in load balancing IHS <b>2300</b>. LPARs <b>2380</b>-<b>1</b>, <b>2380</b>-<b>2</b>, . . . , <b>2380</b>-H may update their respective hardware configuration with the extracted hardware configuration information of load balancing IHS <b>2300</b>.
0332Load balancing tool <b>2400</b> may sort the extracted hardware configuration information by PNet IDs, as per block <b>2430</b>. For example, the load balancing tool <b>2400</b> may list all adapters with the PNet ID of “NETA” first, followed by all adapters with the PNet ID of “NETB”. Load balancing tool <b>2400</b> may further sort the extracted configuration information by adapter type, as per block <b>2435</b>.
0333Load balancing tool <b>2400</b> may group adapters by adapter type on a PNet ID basis, as per block <b>2440</b>. For example, the load balancing tool <b>2400</b> may group all adapters with the type “0087” and the PNet ID “NETA” first, followed by the adapters with the type “0008” and the PNet ID of “NETA”, further followed by the adapters with the type “0087” and the PNet ID of “NETB”. Referring back to decision block <b>2410</b>, if HCM tool <b>600</b> in HCM IHS <b>500</b> does not transmit HCM database <b>580</b>, as per block <b>2410</b>, process flow continues at decision block <b>2445</b>.
0334Load balancing tool <b>2400</b> may decide if the adapter loads on load balancing IHS <b>2300</b> are balanced, as per decision block <b>2445</b>. If the adapter loads are not balanced, load balancing tool <b>2400</b> may balance the loads between like adapters with matching PNet IDs, as per block <b>2450</b>. For example, OSA network adapter <b>1911</b> and OSA network adapter <b>1912</b> may both have a PNet ID of “NETA”. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b>, <b>1938</b>-<b>3</b> may access OSA network adapter <b>1911</b> and <b>1912</b>. In one embodiment, LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> may be utilizing OSA network adapter <b>1911</b> for communication to NETWORK A <b>1915</b>. Load balancing tool <b>2400</b> may balance the load of LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> through OSA network adapter <b>1911</b> by denying LPAR <b>1938</b>-<b>2</b> and LPAR <b>1938</b>-<b>3</b> access to OSA adapter <b>1911</b>. In response, LPAR <b>1938</b>-<b>2</b> and LPAR <b>1938</b>-<b>3</b> may utilize OSA adapter <b>1912</b> for communication to NETWORK A <b>1915</b>, thereby balancing the load between OSA network adapter <b>1911</b> and <b>1912</b>. Process flow continues at block <b>2455</b>.
0335If load balancing tool <b>2400</b> determines that the adapter load is in balancer, as per decision block <b>2445</b>, process flow continues at block <b>2455</b>. Load balancing tool <b>2400</b> may decide if an adapter on load balancing IHS <b>2300</b> has failed, as per decision block <b>2455</b>. If load balancing tool <b>2400</b> determines that an adapter has not failed, as per decision block <b>2455</b>, process flow continues at decision block <b>2410</b>. If load balancing tool <b>2400</b> determines that an adapter on load balancing IHS <b>2300</b> has failed, as per decision block <b>2455</b>, load balancing tool <b>2400</b> may failover the adapter to a like adapter with matching PNet IDs, as per block <b>2460</b>.
0336For example, OSA network adapter <b>1911</b> and OSA network adapter <b>1912</b> may both have a PNet ID of “NETA”. LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b>, <b>1938</b>-<b>3</b> may access OSA network adapter <b>1911</b> and <b>1912</b>. In one embodiment, LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> may be utilizing OSA network adapter <b>1911</b> for communication to NETWORK A <b>1915</b>. Load balancing tool <b>2400</b> may determine that OSA adapter <b>1911</b> is experiencing failure. Load balancing tool <b>2400</b> may failover OSA adapter <b>1911</b> to OSA adapter <b>1912</b> by denying LPAR <b>1938</b>-<b>1</b>, <b>1938</b>-<b>2</b> and <b>1938</b>-<b>3</b> access to network adapter <b>1911</b>. In response, LPAR <b>1938</b>-<b>1</b>, LPAR <b>1938</b>-<b>2</b> and LPAR <b>1938</b>-<b>3</b> may utilize OSA adapter <b>1912</b> for communication to NETWORK A <b>1915</b>, thereby the communications utilizing OSA network adapter <b>1911</b> failover to OSA network adapter <b>1912</b>. Process flow terminates at end block <b>2465</b>. Alternatively, process flow may continue at start block <b>2405</b>.
0000V. Privileged Network Access System
0337<figref idref="DRAWINGS">FIGS. 25A and 25B</figref> are block diagrams showing one embodiment of the disclosed privileged network access (PNA) system <b>2500</b> utilizing PNet IDs. PNA system <b>2500</b> may utilize network adapter <b>2501</b>, administrative network <b>2502</b> and network adapter <b>2503</b> to couple HCM IHS <b>500</b> to administered IHS <b>2504</b>. Administered IHS <b>2504</b> may also be referred to as PNA IHS <b>2504</b>. PNA system <b>2500</b> may utilize network adapter <b>2501</b>, administrative network <b>2502</b> and network adapter <b>2505</b> to couple HCM IHS <b>500</b> to privileged network access management (PNAM) IHS <b>3200</b>. PNA system <b>2500</b> may utilize network adapter <b>2501</b>, administrative network <b>2502</b> and network adapter <b>2506</b> to couple HCM IHS <b>500</b> to administered IHS <b>2507</b>. PNA system <b>2500</b> may utilize network adapter <b>2501</b>, administrative network <b>2502</b> and network adapter <b>2508</b> to couple HCM IHS <b>500</b> to administered IHS <b>2509</b>. PNA system <b>2500</b> may utilize network adapter <b>2501</b>, administrative network <b>2502</b> and network adapter <b>2510</b> to couple HCM IHS <b>500</b> to administered IHS <b>2511</b>. Administered IHSs <b>2504</b>, <b>2507</b>, <b>2509</b> and <b>2511</b> couple via administrative network <b>2502</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>2600</b> with HCM tool <b>600</b> to the administered IHSs. Administered IHSs <b>2504</b>, <b>2507</b>, <b>2509</b> and <b>2511</b> couple via administrative network <b>2502</b> to PNAM IHS <b>3200</b> to enable PNAM IHS <b>3200</b> to administer PNAM database <b>2700</b> with PNAM tool <b>3400</b> to the administered IHSs.
0338PNA system <b>2500</b> may utilize network adapter <b>2512</b> and/or network adapter <b>2513</b> via NETWORK A <b>2514</b> via network adapter <b>2515</b> and/or network adapter <b>2516</b> to couple PNA IHS <b>2504</b> to administered IHS <b>2507</b>. PNA system <b>2500</b> may utilize network adapter <b>2517</b> and/or network adapter <b>2518</b> via NETWORK B <b>2519</b> via network adapter <b>2520</b> and/or network adapter <b>2521</b> to couple PNA IHS <b>2504</b> to administered IHS <b>2509</b>. PNA system <b>2500</b> may utilize network adapter <b>2522</b> and/or network adapter <b>2523</b> via NETWORK C <b>2524</b> via network adapter <b>2525</b> and/or network adapter <b>2526</b> to couple PNA IHS <b>2504</b> to administered IHS <b>2509</b>. PNA system <b>2500</b> may utilize network adapter <b>2522</b> and/or network adapter <b>2523</b> via NETWORK C <b>2524</b> via network adapter <b>2527</b> and/or network adapter <b>2528</b> to couple PNA IHS <b>2504</b> to administered IHS <b>2511</b>.
0339In one embodiment, network adapters <b>2501</b>, <b>2503</b>, <b>2505</b>, <b>2506</b>, <b>2508</b> and <b>2510</b> may be Ethernet (ETH) adapters. Network adapters <b>2512</b>, <b>2515</b>, <b>2517</b>, <b>2520</b>, <b>2522</b>, <b>2525</b> and <b>2527</b> may be open system adapters (OSAs). Network adapters <b>2513</b>, <b>2516</b>, <b>2518</b>, <b>2521</b>, <b>2523</b>, <b>2526</b> and <b>2528</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>2502</b>, NETWORK A <b>2514</b>, NETWORK B <b>2519</b> and NETWORK C <b>2524</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0340PNA IHS <b>2504</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>2529</b>-<b>1</b>, LPAR <b>2529</b>-<b>2</b>, LPAR <b>2529</b>-<b>3</b>, LPAR <b>2529</b>-<b>4</b>, LPAR <b>2529</b>-<b>5</b>, LPAR <b>2529</b>-<b>6</b> and LPAR <b>2529</b>-<b>7</b> in PNA IHS <b>2504</b>. LPAR <b>2529</b>-<b>1</b>, LPAR <b>2529</b>-<b>2</b> and LPAR <b>2529</b>-<b>3</b> may include virtual network adapter <b>2530</b>-<b>1</b>, virtual network adapter <b>2530</b>-<b>2</b> and virtual network adapter <b>2530</b>-<b>3</b>, respectively. Virtual network adapter <b>2530</b>-<b>1</b>, virtual network adapter <b>2530</b>-<b>2</b> and virtual network adapter <b>2530</b>-<b>3</b> may couple to network adapter <b>2512</b> via a channel, i.e., a bus. LPAR <b>2529</b>-<b>4</b> and LPAR <b>2529</b>-<b>5</b> may include virtual network adapter <b>2530</b>-<b>4</b> and virtual network adapter <b>2530</b>-<b>5</b>, respectively. Virtual network adapter <b>2530</b>-<b>4</b> and virtual network adapter <b>2530</b>-<b>5</b> may couple to network adapter <b>2517</b> via a channel. LPAR <b>2529</b>-<b>6</b> and LPAR <b>2529</b>-<b>7</b> may include virtual network adapter <b>2530</b>-<b>6</b> and virtual network adapter <b>2530</b>-<b>7</b>, respectively. Virtual network adapter <b>2530</b>-<b>6</b> and virtual network adapter <b>2530</b>-<b>7</b> may couple to network adapter <b>2522</b> via a channel.
0341LPAR <b>2529</b>-<b>1</b>, LPAR <b>2529</b>-<b>2</b> and LPAR <b>2529</b>-<b>3</b> may include virtual network adapter <b>2531</b>-<b>1</b>, virtual network adapter <b>2531</b>-<b>2</b> and virtual network adapter <b>2531</b>-<b>3</b>, respectively. Virtual network adapter <b>2531</b>-<b>1</b>, virtual network adapter <b>2531</b>-<b>2</b> and virtual network adapter <b>2531</b>-<b>3</b> may couple to network adapter <b>2513</b> via a channel. LPAR <b>2529</b>-<b>4</b> and LPAR <b>2529</b>-<b>5</b> may include virtual network adapter <b>2531</b>-<b>4</b> and virtual network adapter <b>2531</b>-<b>5</b>, respectively. Virtual network adapter <b>2531</b>-<b>4</b> and virtual network adapter <b>2531</b>-<b>5</b> may couple to network adapter <b>2518</b> via a channel. LPAR <b>2529</b>-<b>6</b> and LPAR <b>2529</b>-<b>7</b> may include virtual network adapter <b>2531</b>-<b>6</b> and virtual network adapter <b>2531</b>-<b>7</b>, respectively. Virtual network adapter <b>2531</b>-<b>6</b> and virtual network adapter <b>2531</b>-<b>7</b> may couple to network adapter <b>2523</b> via a channel.
0342<figref idref="DRAWINGS">FIG. 26</figref> depicts one embodiment of HCM database <b>2600</b> in the disclosed privileged network access (PNA) system <b>2500</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>2600</b> on a per adapter basis. In one embodiment, for each network adapter in PNA system <b>2500</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0343As shown in HCM database <b>2600</b>, the hardware configuration information of adapter <b>2512</b> includes MSN of 00CCC0AB2, PID of 0001, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2512</b> is located in physical channel 0001 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00F1. Adapter <b>2512</b> is a physical OSA network adapter and couples to NETWORK A <b>2514</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>1</b>, <b>2529</b>-<b>2</b> and <b>2529</b>-<b>3</b> of PNA IHS <b>2504</b> may access adapter <b>2512</b> to communicate via NETWORK A <b>2514</b>.
0344The hardware configuration information of adapter <b>2513</b> includes MSN of 00CCC0AB2, PID of 0111, LID of 00A1, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2513</b> is located in physical channel 0111 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00A1. Adapter <b>2513</b> is a physical RNIC network adapter and couples to NETWORK A <b>2514</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>1</b>, <b>2529</b>-<b>2</b> and <b>2529</b>-<b>3</b> of PNA IHS <b>2504</b> may access adapter <b>2513</b> to communicate via NETWORK A <b>2514</b>.
0345The hardware configuration information of adapter <b>2517</b> includes MSN of 00CCC0AB2, PID of 0002, LID of 00F5, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2517</b> is located in physical channel 0002 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00F5. Adapter <b>2517</b> is a physical OSA network adapter and couples to NETWORK B <b>2519</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>4</b> and <b>2529</b>-<b>5</b> of PNA IHS <b>2504</b> may access adapter <b>2517</b> to communicate via NETWORK B <b>2519</b>.
0346The hardware configuration information of adapter <b>2518</b> includes MSN of 00CCC0AB2, PID of 0112, LID of 00A5, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2518</b> is located in physical channel 0112 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00A5. Adapter <b>2518</b> is a physical RNIC network adapter and couples to NETWORK B <b>2519</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>4</b> and <b>2529</b>-<b>5</b> of PNA IHS <b>2504</b> may access adapter <b>2518</b> to communicate via NETWORK B <b>2519</b>.
0347The hardware configuration information of adapter <b>2522</b> includes MSN of 00CCC0AB2, PID of 0003, LID of 00F8, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2522</b> is located in physical channel 0003 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00F8. Adapter <b>2522</b> is a physical OSA network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>6</b> and <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> may access adapter <b>2522</b> to communicate via NETWORK C <b>2524</b>.
0348The hardware configuration information of adapter <b>2523</b> includes MSN of 00CCC0AB2, PID of 0113, LID of 00A8, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2523</b> is located in physical channel 0113 in PNA IHS <b>2504</b> and may be identified logically by PNA IHS <b>2504</b> as 00A8. Adapter <b>2523</b> is a physical RNIC network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. LPAR <b>2529</b>-<b>6</b> and <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> may access adapter <b>2523</b> to communicate via NETWORK C <b>2524</b>.
0349The hardware configuration information of adapter <b>2515</b> includes MSN of DFA22601, PID of 0001, LID of 00F4, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2515</b> is located in physical channel 0001 in administered IHS <b>2507</b> and may be identified logically by administered IHS <b>2507</b> as 00F4. Adapter <b>2515</b> is a physical OSA network adapter and couples to NETWORK A <b>2514</b> on both ports 1 and 2. Administered IHS <b>2507</b> may access adapter <b>2515</b> to communicate via NETWORK A <b>2514</b>.
0350The hardware configuration information of adapter <b>2516</b> includes MSN of DFA22601, PID of 0002, LID of 00A4, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2516</b> is located in physical channel 0002 in administered IHS <b>2507</b> and may be identified logically by administered IHS <b>2507</b> as 00A4. Adapter <b>2516</b> is a physical RNIC network adapter and couples to NETWORK A <b>2514</b> on both ports 1 and 2. Administered IHS <b>2507</b> may access adapter <b>2516</b> to communicate via NETWORK A <b>2514</b>.
0351The hardware configuration information of adapter <b>2520</b> includes MSN of 33300FB8, PID of 0001, LID of 00F5, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2520</b> is located in physical channel 0001 in administered IHS <b>2509</b> and may be identified logically by administered IHS <b>2509</b> as 00F5. Adapter <b>2520</b> is a physical OSA network adapter and couples to NETWORK B <b>2519</b> on both ports 1 and 2. Administered IHS <b>2509</b> may access adapter <b>2520</b> to communicate via NETWORK B <b>2519</b>.
0352The hardware configuration information of adapter <b>2521</b> includes MSN of 33300FB8, PID of 0011, LID of 00F6, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2521</b> is located in physical channel 0011 in administered IHS <b>2509</b> and may be identified logically by administered IHS <b>2509</b> as 00F6. Adapter <b>2521</b> is a physical RNIC network adapter and couples to NETWORK B <b>2519</b> on both ports 1 and 2. Administered IHS <b>2509</b> may access adapter <b>2521</b> to communicate via NETWORK B <b>2519</b>.
0353The hardware configuration information of adapter <b>2525</b> includes MSN of 33300FB8, PID of 0002, LID of 00A5, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2525</b> is located in physical channel 0002 in administered IHS <b>2509</b> and may be identified logically by administered IHS <b>2509</b> as 00A5. Adapter <b>2525</b> is a physical OSA network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. Administered IHS <b>2509</b> may access adapter <b>2525</b> to communicate via NETWORK C <b>2524</b>.
0354The hardware configuration information of adapter <b>2526</b> includes MSN of 33300FB8, PID of 0012, LID of 00A6, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2526</b> is located in physical channel 0012 in administered IHS <b>2509</b> and may be identified logically by administered IHS <b>2509</b> as 00A6. Adapter <b>2526</b> is a physical RNIC network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. Administered IHS <b>2509</b> may access adapter <b>2526</b> to communicate via NETWORK C <b>2524</b>.
0355The hardware configuration information of adapter <b>2527</b> includes MSN of 0000FC32, PID of 0031, LID of 0D01, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2527</b> is located in physical channel 0031 in administered IHS <b>2511</b> and may be identified logically by administered IHS <b>2511</b> as 0D01. Adapter <b>2527</b> is a physical OSA network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. Administered IHS <b>2511</b> may access adapter <b>2527</b> to communicate via NETWORK C <b>2524</b>.
0356The hardware configuration information of adapter <b>2528</b> includes MSN of 0000FC32, PID of 0033, LID of 0D03, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2528</b> is located in physical channel 0033 in administered IHS <b>2511</b> and may be identified logically by administered IHS <b>2511</b> as 0D03. Adapter <b>2528</b> is a physical RNIC network adapter and couples to NETWORK C <b>2524</b> on both ports 1 and 2. Administered IHS <b>2511</b> may access adapter <b>2528</b> to communicate via NETWORK C <b>2524</b>.
0357<figref idref="DRAWINGS">FIG. 27</figref> depicts one embodiment of privileged network access management (PNAM) database <b>2700</b> in the disclosed PNA system <b>2500</b>. PNAM tool <b>3400</b> may store the privileged network access information in PNAM database <b>2700</b> on a per PNet ID, per IHS basis. In one embodiment, for each network adapter in PNA system <b>2500</b>, PNAM tool <b>3400</b> may store, from the leftmost column to the rightmost column, the physical network identification (PNet ID), the machine serial number (MSN) and the logical partition (LPAR) access list.
0358As shown in PNAM database <b>2700</b>, the privileged network access information in the first row of PNAM database <b>2700</b> may include a PNet ID of NETB, MSN of 00CCC0AB2 and LPAR access list of 04 and 05. In other words, NETWORK B <b>2519</b> is a privileged network. A PNA tool <b>3300</b> may grant LPARs <b>2529</b>-<b>4</b> and <b>2529</b>-<b>5</b> in PNA IHS <b>2504</b> access to privileged NETWORK B <b>2519</b>.
0359The privileged network access information in the second row of PNAM database <b>2700</b> may include a PNet ID of NETB, MSN of 33300FB8 and LPAR access list with no entries. In other words, NETWORK B <b>2519</b> is a privileged network. In one embodiment, a PNA tool <b>3300</b> may grant administered IHS <b>2509</b> access to privileged NETWORK B <b>2519</b>.
0360The privileged network access information in the third row of PNAM database <b>2700</b> may include a PNet ID of NETC, MSN of 00CCC0AB2 and LPAR access list of 07. In other words, NETWORK C <b>2524</b> is a privileged network. A PNA tool <b>3300</b> may grant LPAR <b>2529</b>-<b>7</b> in PNA IHS <b>2504</b> access to privileged NETWORK C <b>2524</b>. A PNA tool <b>330</b> may deny LPAR <b>2529</b>-<b>6</b> in PNA IHS <b>2504</b> access to privileged NETWORK C <b>2524</b>, even though LPAR <b>2529</b>-<b>6</b> is coupled to NETWORK C <b>2524</b> via network adapters <b>2522</b> and <b>2523</b>.
0361The privileged network access information in the fourth row of PNAM database <b>2700</b> may include a PNet ID of NETC, MSN of 33300FB8 and LPAR access list with no entries. In other words, NETWORK C <b>2524</b> is a privileged network. In one embodiment, a PNA tool <b>3300</b> may grant administered IHS <b>2509</b> access to privileged NETWORK C <b>2524</b>.
0362The privileged network access information in the fifth row of PNAM database <b>2700</b> may include a PNet ID of NETC, MSN of 0000FC32 and LPAR access list with no entries. In other words, NETWORK C <b>2524</b> is a privileged network. In one embodiment, a PNA tool <b>3300</b> may grant administered IHS <b>2511</b> access to privileged NETWORK C <b>2524</b>.
0363<figref idref="DRAWINGS">FIGS. 28A and 28B</figref> are block diagrams showing one embodiment of the disclosed PNA system <b>2800</b> utilizing PNet IDs. PNA system <b>2800</b> may utilize network adapter <b>2801</b>, administrative network <b>2802</b> and network adapter <b>2803</b> to couple HCM IHS <b>500</b> to administered IHS <b>2804</b>. Administered IHS <b>2804</b> may also be referred to as PNA IHS <b>2804</b>. PNA system <b>2800</b> may utilize network adapter <b>2801</b>, administrative network <b>2802</b> and network adapter <b>2805</b> to couple HCM IHS <b>500</b> to privileged network access management (PNAM) IHS <b>3200</b>. PNA system <b>2800</b> may utilize network adapter <b>2801</b>, administrative network <b>2802</b> and network adapter <b>2806</b> to couple HCM IHS <b>500</b> to administered IHS <b>2807</b>. PNA system <b>2800</b> may utilize network adapter <b>2801</b>, administrative network <b>2802</b> and network adapter <b>2808</b> to couple HCM IHS <b>500</b> to administered IHS <b>2809</b>. PNA system <b>2800</b> may utilize network adapter <b>2801</b>, administrative network <b>2802</b> and network adapter <b>2810</b> to couple HCM IHS <b>500</b> to administered IHS <b>2811</b>. Administered IHSs <b>2804</b>, <b>2807</b>, <b>2809</b> and <b>2811</b> couple via administrative network <b>2802</b> to HCM IHS <b>500</b> to enable HCM IHS <b>500</b> to administer HCM database <b>2900</b> with HCM tool <b>600</b> to the administered IHSs. Administered IHSs <b>2804</b>, <b>2807</b>, <b>2809</b> and <b>2811</b> couple via administrative network <b>2802</b> to PNAM IHS <b>3200</b> to enable PNAM IHS <b>3200</b> to administer PNAM database <b>3000</b> with PNAM tool <b>3400</b> to the administered IHSs.
0364PNA system <b>2800</b> may utilize network adapter <b>2812</b> and/or network adapter <b>2813</b> and/or network adapter <b>2814</b> and/or network adapter <b>2815</b> via NETWORK A <b>2816</b> via network adapter <b>2817</b> and/or network adapter <b>2818</b> to couple PNA IHS <b>2804</b> to administered IHS <b>2807</b>. PNA system <b>2800</b> may utilize network adapter <b>2819</b> and/or network adapter <b>2820</b> and/or network adapter <b>2821</b> and/or network adapter <b>2822</b> via NETWORK B <b>2823</b> via network adapter <b>2824</b> and/or network adapter <b>2825</b> to couple PNA IHS <b>2804</b> to administered IHS <b>2807</b>. PNA system <b>2800</b> may utilize network adapter <b>2819</b> and/or network adapter <b>2820</b> and/or network adapter <b>2821</b> and/or network adapter <b>2822</b> via NETWORK B <b>2823</b> via network adapter <b>2826</b> and/or network adapter <b>2827</b> and/or network adapter <b>2828</b> and/or network adapter <b>2829</b> to couple PNA IHS <b>2804</b> to administered IHS <b>2809</b>. PNA system <b>2800</b> may utilize network adapter <b>2830</b> and/or network adapter <b>2831</b> and/or network adapter <b>2832</b> and/or network adapter <b>2833</b> via NETWORK C <b>2834</b> via network adapter <b>2835</b> and/or network adapter <b>2836</b> and/or network adapter <b>2837</b> and/or network adapter <b>2838</b> to couple PNA IHS <b>2804</b> to administered IHS <b>2811</b>.
0365In one embodiment, network adapters <b>2801</b>, <b>2803</b>, <b>2805</b>, <b>2806</b>, <b>2808</b> and <b>2810</b> may be Ethernet (ETH) adapters. Network adapters <b>2812</b>, <b>2813</b>, <b>2817</b>, <b>2819</b>, <b>2820</b>, <b>2824</b>, <b>2826</b>, <b>2828</b>, <b>2830</b>, <b>2831</b>, <b>2835</b> and <b>2836</b> may be open system adapters (OSAs). Network adapters <b>2814</b>, <b>2815</b>, <b>2818</b>, <b>2821</b>, <b>2822</b>, <b>2824</b>, <b>2827</b>, <b>2829</b>, <b>2832</b>, <b>2833</b>, <b>2837</b> and <b>2838</b> may be remote direct memory access (RDMA) enabled network adapter controllers (RNICs). In one embodiment, administrative network <b>2802</b>, NETWORK A <b>2816</b>, NETWORK B <b>2823</b> and NETWORK C <b>2834</b> may provide local area network (LAN) communications and/or wide area network (WAN) communications and/or virtual LAN communications and/or intranet communications and/or Internet communications to structures that couple thereto.
0366PNA IHS <b>2804</b> may include a hypervisor (not shown) that may create logical partition (LPAR) <b>2839</b>-<b>1</b>, LPAR <b>2839</b>-<b>2</b>, LPAR <b>2839</b>-<b>3</b>, LPAR <b>2839</b>-<b>4</b>, LPAR <b>2839</b>-<b>5</b>, LPAR <b>2839</b>-<b>6</b> and LPAR <b>2839</b>-<b>7</b> in PNA IHS <b>2804</b>. LPAR <b>2839</b>-<b>1</b>, LPAR <b>2839</b>-<b>2</b> and LPAR <b>2839</b>-<b>3</b> may include virtual network adapter <b>2840</b>-<b>1</b>, virtual network adapter <b>2840</b>-<b>2</b> and virtual network adapter <b>2840</b>-<b>3</b>, respectively. Virtual network adapter <b>2840</b>-<b>1</b>, virtual network adapter <b>2840</b>-<b>2</b> and virtual network adapter <b>2840</b>-<b>3</b> may couple to network adapter <b>2812</b> and network adapter <b>2813</b> via a channel, i.e., a bus. LPAR <b>2839</b>-<b>4</b> and LPAR <b>2839</b>-<b>5</b> may include virtual network adapter <b>2840</b>-<b>4</b> and virtual network adapter <b>2840</b>-<b>5</b>, respectively. Virtual network adapter <b>2840</b>-<b>4</b> and virtual network adapter <b>2840</b>-<b>5</b> may couple to network adapter <b>2819</b> and network adapter <b>2820</b> via a channel. LPAR <b>2839</b>-<b>6</b> and LPAR <b>2839</b>-<b>7</b> may include virtual network adapter <b>2840</b>-<b>6</b> and virtual network adapter <b>2840</b>-<b>7</b>, respectively. Virtual network adapter <b>2840</b>-<b>6</b> and virtual network adapter <b>2840</b>-<b>7</b> may couple to network adapter <b>2830</b> and network adapter <b>2831</b> via a channel.
0367LPAR <b>2839</b>-<b>1</b>, LPAR <b>2839</b>-<b>2</b> and LPAR <b>2839</b>-<b>3</b> may include virtual network adapter <b>2841</b>-<b>1</b>, virtual network adapter <b>2841</b>-<b>2</b> and virtual network adapter <b>2841</b>-<b>3</b>, respectively. Virtual network adapter <b>2841</b>-<b>1</b>, virtual network adapter <b>2841</b>-<b>2</b> and virtual network adapter <b>2841</b>-<b>3</b> may couple to network adapter <b>2814</b> and network adapter <b>2815</b> via a channel. LPAR <b>2839</b>-<b>4</b> and LPAR <b>2839</b>-<b>5</b> may include virtual network adapter <b>2841</b>-<b>4</b> and virtual network adapter <b>2841</b>-<b>5</b>, respectively. Virtual network adapter <b>2841</b>-<b>4</b> and virtual network adapter <b>2841</b>-<b>5</b> may couple to network adapter <b>2821</b> and network adapter <b>2822</b> via a channel. LPAR <b>2839</b>-<b>6</b> and LPAR <b>2839</b>-<b>7</b> may include virtual network adapter <b>2841</b>-<b>6</b> and virtual network adapter <b>2841</b>-<b>7</b>, respectively. Virtual network adapter <b>2841</b>-<b>6</b> and virtual network adapter <b>2841</b>-<b>7</b> may couple to network adapter <b>2832</b> and network adapter <b>2833</b> via a channel.
0368In one embodiment, administered IHS <b>2811</b> may be a PNA IHS. Administered IHS <b>2811</b> may include a hypervisor (not shown) that may create LPAR <b>2842</b>-<b>1</b> and LPAR <b>2842</b>-<b>2</b>. LPAR <b>2842</b>-<b>1</b> and LPAR <b>2842</b>-<b>2</b> may include virtual network adapter <b>2843</b>-<b>1</b> and virtual network adapter <b>2843</b>-<b>2</b>, respectively. Virtual network adapter <b>2843</b>-<b>1</b> and virtual network adapter <b>2843</b>-<b>2</b> may couple to network adapter <b>2835</b> and network adapter <b>2836</b> via a channel. LPAR <b>2842</b>-<b>1</b> and LPAR <b>2842</b>-<b>2</b> may include virtual network adapter <b>2844</b>-<b>1</b> and virtual network adapter <b>2844</b>-<b>2</b>, respectively. Virtual network adapter <b>2844</b>-<b>1</b> and virtual network adapter <b>2844</b>-<b>2</b> may couple to network adapter <b>2837</b> and network adapter <b>2838</b> via a channel.
0369<figref idref="DRAWINGS">FIG. 29</figref> depicts one embodiment of HCM database <b>2900</b> in the disclosed privileged network access (PNA) system <b>2800</b>. HCM tool <b>600</b> may store the hardware configuration information in HCM database <b>2900</b> on a per adapter basis. In one embodiment, for each network adapter in PNA system <b>2800</b>, HCM tool <b>600</b> may store, from the leftmost column to the rightmost column, the machine serial number (MSN), physical identification (PID), logical identification (LID), adapter type, logical partition (LPAR) access list, physical network identification (PNet ID) network adapter.
0370As shown in HCM database <b>2900</b>, the hardware configuration information of adapter <b>2812</b> includes MSN of 000AFA11, PID of 0001, LID of 00F1, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2812</b> is located in physical channel 0001 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00F1. Adapter <b>2812</b> is a physical OSA network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>1</b>, <b>2839</b>-<b>2</b> and <b>2839</b>-<b>3</b> of PNA IHS <b>2804</b> may access adapter <b>2812</b> to communicate via NETWORK A <b>2816</b>.
0371The hardware configuration information of adapter <b>2813</b> includes MSN of 000AFA11, PID of 0002, LID of 00F5, type of 0087, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2813</b> is located in physical channel 0002 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00F5. Adapter <b>2813</b> is a physical OSA network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>1</b>, <b>2839</b>-<b>2</b> and <b>2839</b>-<b>3</b> of PNA IHS <b>2804</b> may access adapter <b>2813</b> to communicate via NETWORK A <b>2816</b>.
0372The hardware configuration information of adapter <b>2814</b> includes MSN of 000AFA11, PID of 0011, LID of 00A1, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2814</b> is located in physical channel 0011 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00A1. Adapter <b>2814</b> is a physical RNIC network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>1</b>, <b>2839</b>-<b>2</b> and <b>2839</b>-<b>3</b> of PNA IHS <b>2804</b> may access adapter <b>2814</b> to communicate via NETWORK A <b>2816</b>.
0373The hardware configuration information of adapter <b>2815</b> includes MSN of 000AFA11, PID of 0012, LID of 00A5, type of 0008, LPAR access list of 01, 02 and 03, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2815</b> is located in physical channel 0012 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00A5. Adapter <b>2815</b> is a physical RNIC network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>1</b>, <b>2839</b>-<b>2</b> and <b>2839</b>-<b>3</b> of PNA IHS <b>2804</b> may access adapter <b>2815</b> to communicate via NETWORK A <b>2816</b>.
0374The hardware configuration information of adapter <b>2819</b> includes MSN of 000AFA11, PID of 0003, LID of 00F9, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2819</b> is located in physical channel 0003 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00F9. Adapter <b>2819</b> is a physical OSA network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>4</b> and <b>2839</b>-<b>5</b> of PNA IHS <b>2804</b> may access adapter <b>2819</b> to communicate via NETWORK B <b>2823</b>.
0375The hardware configuration information of adapter <b>2820</b> includes MSN of 000AFA11, PID of 0004, LID of 00FC, type of 0087, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2820</b> is located in physical channel 0004 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00FC. Adapter <b>2820</b> is a physical OSA network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>4</b> and <b>2839</b>-<b>5</b> of PNA IHS <b>2804</b> may access adapter <b>2820</b> to communicate via NETWORK B <b>2823</b>.
0376The hardware configuration information of adapter <b>2821</b> includes MSN of 000AFA11, PID of 0013, LID of 00A9, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2821</b> is located in physical channel 0013 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00A9. Adapter <b>2821</b> is a physical RNIC network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>4</b> and <b>2839</b>-<b>5</b> of PNA IHS <b>2804</b> may access adapter <b>2821</b> to communicate via NETWORK B <b>2823</b>.
0377The hardware configuration information of adapter <b>2822</b> includes MSN of 000AFA11, PID of 0014, LID of 00AC, type of 0008, LPAR access list of 04 and 05, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2822</b> is located in physical channel 0014 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00AC. Adapter <b>2822</b> is a physical RNIC network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>4</b> and <b>2839</b>-<b>5</b> of PNA IHS <b>2804</b> may access adapter <b>2822</b> to communicate via NETWORK B <b>2823</b>.
0378The hardware configuration information of adapter <b>2830</b> includes MSN of 000AFA11, PID of 0005, LID of 00FF, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2830</b> is located in physical channel 0005 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00FF. Adapter <b>2830</b> is a physical OSA network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>6</b> and <b>2839</b>-<b>7</b> of PNA IHS <b>2804</b> may access adapter <b>2830</b> to communicate via NETWORK C <b>2834</b>.
0379The hardware configuration information of adapter <b>2831</b> includes MSN of 000AFA11, PID of 0006, LID of 0102, type of 0087, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2831</b> is located in physical channel 0006 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 0102. Adapter <b>2831</b> is a physical OSA network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>6</b> and <b>2839</b>-<b>7</b> of PNA IHS <b>2804</b> may access adapter <b>2831</b> to communicate via NETWORK C <b>2834</b>.
0380The hardware configuration information of adapter <b>2832</b> includes MSN of 000AFA11, PID of 0015, LID of 00AF, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2832</b> is located in physical channel 0015 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00AF. Adapter <b>2832</b> is a physical RNIC network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>6</b> and <b>2839</b>-<b>7</b> of PNA IHS <b>2804</b> may access adapter <b>2832</b> to communicate via NETWORK C <b>2834</b>.
0381The hardware configuration information of adapter <b>2833</b> includes MSN of 000B2A11, PID of 0016, LID of 00B2, type of 0008, LPAR access list of 06 and 07, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2833</b> is located in physical channel 0016 in PNA IHS <b>2804</b> and may be identified logically by PNA IHS <b>2804</b> as 00B2. Adapter <b>2833</b> is a physical RNIC network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2839</b>-<b>6</b> and <b>2839</b>-<b>7</b> of PNA IHS <b>2804</b> may access adapter <b>2833</b> to communicate via NETWORK C <b>2834</b>.
0382The hardware configuration information of adapter <b>2817</b> includes MSN of 0000FC32, PID of 0001, LID of 0D01, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2817</b> is located in physical channel 0001 in administered IHS <b>2807</b> and may be identified logically by administered IHS <b>2807</b> as 0D01. Adapter <b>2817</b> is a physical OSA network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. Administered IHS <b>2807</b> may access adapter <b>2817</b> to communicate via NETWORK A <b>2816</b>.
0383The hardware configuration information of adapter <b>2818</b> includes MSN of 0000FC32, PID of 0021, LID of 0D03, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETA. In other words, adapter <b>2818</b> is located in physical channel 0021 in administered IHS <b>2807</b> and may be identified logically by administered IHS <b>2807</b> as 0D03. Adapter <b>2818</b> is a physical RNIC network adapter and couples to NETWORK A <b>2816</b> on both ports 1 and 2. Administered IHS <b>2807</b> may access adapter <b>2818</b> to communicate via NETWORK A <b>2816</b>.
0384The hardware configuration information of adapter <b>2824</b> includes MSN of 0000FC32, PID of 0002, LID of 0D02, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2824</b> is located in physical channel 0002 in administered IHS <b>2807</b> and may be identified logically by administered IHS <b>2807</b> as 0D02. Adapter <b>2824</b> is a physical OSA network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2807</b> may access adapter <b>2824</b> to communicate via NETWORK B <b>2823</b>.
0385The hardware configuration information of adapter <b>2825</b> includes MSN of 0000FC32, PID of 0022, LID of 0D04, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2825</b> is located in physical channel 0022 in administered IHS <b>2807</b> and may be identified logically by administered IHS <b>2807</b> as 0D04. Adapter <b>2825</b> is a physical RNIC network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2807</b> may access adapter <b>2825</b> to communicate via NETWORK B <b>2823</b>.
0386The hardware configuration information of adapter <b>2826</b> includes MSN of DDDD00AB, PID of 0001, LID of 0001, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2826</b> is located in physical channel 0001 in administered IHS <b>2809</b> and may be identified logically by administered IHS <b>2809</b> as 0001. Adapter <b>2826</b> is a physical OSA network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2809</b> may access adapter <b>2826</b> to communicate via NETWORK B <b>2823</b>.
0387The hardware configuration information of adapter <b>2827</b> includes MSN of DDDD00AB, PID of 0011, LID of 0003, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2827</b> is located in physical channel 0011 in administered IHS <b>2809</b> and may be identified logically by administered IHS <b>2809</b> as 0003. Adapter <b>2827</b> is a physical RNIC network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2809</b> may access adapter <b>2827</b> to communicate via NETWORK B <b>2823</b>.
0388The hardware configuration information of adapter <b>2828</b> includes MSN of DDDD00AB, PID of 0002, LID of 0002, type of 0087, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2828</b> is located in physical channel 0002 in administered IHS <b>2809</b> and may be identified logically by administered IHS <b>2809</b> as 0002. Adapter <b>2828</b> is a physical OSA network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2809</b> may access adapter <b>2828</b> to communicate via NETWORK B <b>2823</b>.
0389The hardware configuration information of adapter <b>2829</b> includes MSN of DDDD00AB, PID of 0022, LID of 0004, type of 0008, LPAR access list with no entries, and PNet ID 1 and PNet ID 2 of NETB. In other words, adapter <b>2829</b> is located in physical channel 0022 in administered IHS <b>2809</b> and may be identified logically by administered IHS <b>2809</b> as 0004. Adapter <b>2829</b> is a physical RNIC network adapter and couples to NETWORK B <b>2823</b> on both ports 1 and 2. Administered IHS <b>2809</b> may access adapter <b>2829</b> to communicate via NETWORK B <b>2823</b>.
0390The hardware configuration information of adapter <b>2835</b> includes MSN of ACA000F1, PID of 0001, LID of 0081, type of 0087, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2835</b> is located in physical channel 0001 in PNA IHS <b>2811</b> and may be identified logically by PNA IHS <b>2811</b> as 0061. Adapter <b>2835</b> is a physical OSA network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2842</b>-<b>1</b> and <b>2842</b>-<b>2</b> of PNA IHS <b>2811</b> may access adapter <b>2835</b> to communicate via NETWORK C <b>2834</b>.
0391The hardware configuration information of adapter <b>2836</b> includes MSN of ACA000F1, PID of 0002, LID of 00B4, type of 0087, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2836</b> is located in physical channel 0002 in PNA IHS <b>2811</b> and may be identified logically by PNA IHS <b>2811</b> as 00B4. Adapter <b>2836</b> is a physical OSA network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2842</b>-<b>1</b> and <b>2842</b>-<b>2</b> of PNA IHS <b>2811</b> may access adapter <b>2836</b> to communicate via NETWORK C <b>2834</b>.
0392The hardware configuration information of adapter <b>2837</b> includes MSN of ACA000F1, PID of 0021, LID of 00C1, type of 0008, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2837</b> is located in physical channel 0021 in PNA IHS <b>2811</b> and may be identified logically by PNA IHS <b>2811</b> as 00C1. Adapter <b>2837</b> is a physical RNIC network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2842</b>-<b>1</b> and <b>2842</b>-<b>2</b> of PNA IHS <b>2811</b> may access adapter <b>2837</b> to communicate via NETWORK C <b>2834</b>.
0393The hardware configuration information of adapter <b>2838</b> includes MSN of ACA000F1, PID of 0022, LID of 00C4, type of 0008, LPAR access list of 01 and 02, and PNet ID 1 and PNet ID 2 of NETC. In other words, adapter <b>2838</b> is located in physical channel 0022 in PNA IHS <b>2811</b> and may be identified logically by PNA IHS <b>2811</b> as 00C4. Adapter <b>2838</b> is a physical RNIC network adapter and couples to NETWORK C <b>2834</b> on both ports 1 and 2. LPAR <b>2842</b>-<b>1</b> and <b>2842</b>-<b>2</b> of PNA IHS <b>2811</b> may access adapter <b>2838</b> to communicate via NETWORK C <b>2834</b>.
0394<figref idref="DRAWINGS">FIG. 30</figref> depicts one embodiment of privileged network access management (PNAM) database <b>3000</b> in the disclosed PNA system <b>2800</b>. PNAM tool <b>3400</b> may store the privileged network access information in PNAM database <b>2900</b> on a per PNet ID, per IHS basis. In one embodiment, for each network adapter in PNA system <b>2800</b>, PNAM tool <b>3400</b> may store, from the leftmost column to the rightmost column, the physical network identification (PNet ID), the machine serial number (MSN) and the logical partition (LPAR) access list.
0395As shown in PNAM database <b>3000</b>, the privileged network access information in the first row of PNAM database <b>3000</b> may include a PNet ID of NETB, MSN of 000AFA11 and LPAR access list of 04 and 05. In other words, NETWORK B <b>2823</b> is a privileged network. PNA tool <b>3300</b> may grant LPARs <b>2839</b>-<b>4</b> and <b>2839</b>-<b>5</b> in PNA IHS <b>2804</b> access to privileged NETWORK B <b>2823</b>.
0396The privileged network access information in the second row of PNAM database <b>3000</b> may include a PNet ID of NETB, MSN of 0000FC32 and LPAR access list with no entries. In other words, NETWORK B <b>2823</b> is a privileged network. In one embodiment, PNA tool <b>3300</b> may grant administered IHS <b>2807</b> access to privileged NETWORK B <b>2823</b>.
0397The privileged network access information in the third row of PNAM database <b>3000</b> may include a PNet ID of NETB, MSN of DDDD00AB and LPAR access list with no entries. In other words, NETWORK B <b>2823</b> is a privileged network. In one embodiment, PNA tool <b>3300</b> may grant administered IHS <b>2809</b> access to privileged NETWORK B <b>2823</b>.
0398The privileged network access information in the fourth row of PNAM database <b>3000</b> may include a PNet ID of NETC, MSN of 000AFA11 and LPAR access list of 07. In other words, NETWORK C <b>2823</b> is a privileged network. PNA tool <b>3300</b> may grant LPAR <b>2839</b>-<b>7</b> in PNA IHS <b>2804</b> access to privileged NETWORK C <b>2834</b>. PNA tool <b>330</b> may deny LPAR <b>2839</b>-<b>6</b> in PNA IHS <b>2804</b> access to privileged NETWORK C <b>2834</b>, even though LPAR <b>2839</b>-<b>6</b> is coupled to NETWORK C <b>2834</b> via network adapters <b>2830</b>, <b>2831</b>, <b>2832</b> and <b>2833</b>.
0399The privileged network access information in the fifth row of PNAM database <b>3000</b> may include a PNet ID of NETC, MSN of ACA000F1 and LPAR access list of 02. In other words, NETWORK C <b>2823</b> is a privileged network. PNA tool <b>3300</b> may grant LPAR <b>2842</b>-<b>2</b> in PNA IHS <b>2811</b> access to privileged NETWORK C <b>2834</b>. PNA tool <b>330</b> may deny LPAR <b>2842</b>-<b>1</b> in PNA IHS <b>2811</b> access to privileged NETWORK C <b>2834</b>, even though LPAR <b>2842</b>-<b>1</b> is coupled to NETWORK C <b>2834</b> via network adapters <b>2835</b>, <b>2836</b>, <b>2837</b> and <b>2838</b>.
0400<figref idref="DRAWINGS">FIG. 31</figref> is a block diagram of a privileged network access (PNA) information handling system (IHS) <b>3100</b> that may be used in the disclosed PNA system. With respect to <figref idref="DRAWINGS">FIG. 11</figref>, like numbers indicate like elements. PNA IHS <b>3100</b> includes a processor <b>3105</b> that may include multiple cores. RNIC converging IHS <b>3100</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. In one embodiment, PNA IHS <b>3100</b> includes a bus <b>3110</b>, i.e. channel <b>3110</b>. In another embodiment, bus <b>3110</b> may be multiple busses, i.e., multiple channels. Bus <b>3110</b> may couple processor <b>3105</b> to memory <b>3115</b> via a memory controller <b>3120</b> and memory bus <b>3125</b>. System memory <b>3115</b> may also be referred to as main memory. System memory <b>3115</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>3105</b> may also include local memory such as L1, L2 and L3 caches.
0401In one embodiment, a video graphics controller <b>3130</b> couples display <b>3135</b> to bus <b>3110</b>. In another embodiment, PNA IHS <b>3100</b> may operate without display <b>3135</b> and/or video graphics controller <b>3130</b>. Nonvolatile storage <b>3140</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>3110</b> to provide PNA IHS <b>3100</b> with permanent storage of information. System memory <b>3115</b> and nonvolatile storage <b>3140</b> are both forms of memory stores. In one embodiment, nonvolatile storage <b>3140</b> stores a hypervisor <b>3145</b> (HYPERVISOR) that governs operation of PNA IHS <b>3100</b>. In another embodiment, nonvolatile storage <b>3140</b> may store an operating system (not shown) that governs operation of PNA IHS <b>3100</b>. In another embodiment, nonvolatile storage <b>3140</b> may store an operating system (not shown) that governs operation of PNA IHS <b>3100</b>, where the operating system includes a hypervisor (not shown).
0402I/O devices <b>3150</b>, such as speakers, a keyboard and a pointing device, may couple to bus <b>3110</b> via I/O controller <b>3155</b> and I/O bus <b>3160</b>. One or more expansion busses <b>3165</b>, i.e. channels <b>3165</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, i.e. channels, couple to bus <b>3110</b> to facilitate the connection of peripherals and devices to PNA IHS <b>3100</b>. Network interface controllers (NICs), for example, NIC <b>3170</b>-<b>1</b>, NIC <b>3170</b>-<b>2</b>, . . . , NIC <b>3170</b>-G, wherein G is the number of NICs, may couple to bus <b>3110</b> to enable PNA IHS <b>3100</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>3170</b>-<b>1</b>, NIC <b>3170</b>-<b>2</b>, . . . , NIC <b>3170</b>-G may also be called a network communication adapter, network interface adapter, network adapter, network interface or an adapter. NIC <b>3170</b>-<b>1</b>, NIC <b>3170</b>-<b>2</b>, . . . , NIC <b>3170</b>-G may take many forms. For example, NIC <b>3170</b>-<b>1</b>, NIC <b>3170</b>-<b>2</b>, . . . , NIC <b>3170</b>-G may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0403While <figref idref="DRAWINGS">FIG. 31</figref> shows one IHS that employs processor <b>3105</b>, the IHS may take many forms. For example, PNA IHS <b>3100</b> may take the form of a mainframe, server, central processor complex (CPC), desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. PNA IHS <b>3100</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0404PNA IHS <b>3100</b> includes a PNA tool computer program product <b>3300</b> on digital media <b>3175</b> such as a CD, DVD or other media. For simplicity, the term PNA tool will be used below. PNA IHS <b>3100</b> may store PNA tool <b>3300</b> in nonvolatile storage <b>3140</b> as PNA tool <b>3300</b>′. PNA IHS <b>3100</b> may also store hypervisor <b>3145</b> (HYPERVISOR) and logical partition (LPAR) <b>3180</b>-<b>1</b>, LPAR <b>3180</b>-<b>2</b>, . . . , LPAR <b>3180</b>-F, wherein F is the number of LPARs, in nonvolatile storage <b>3140</b>.
0405In another embodiment, PNA tool <b>3300</b>′ may be part of the hypervisor <b>3145</b> (not shown). In another embodiment, PNA tool <b>3300</b>′ may be in LPAR <b>3180</b>-<b>1</b>, LPAR <b>3180</b>-<b>2</b>, . . . , LPAR <b>3180</b>-F. In another embodiment, PNA IHS <b>3100</b> may store an operating system (not shown) that governs operation of PNA IHS <b>3100</b>, where the operating system includes a hypervisor (not shown) and where the operating system includes LPAR <b>3180</b>-<b>1</b>, LPAR <b>3180</b>-<b>2</b>, . . . , LPAR <b>3180</b>-F as virtual machines (not shown). When PNA IHS <b>3100</b> initializes, the IHS loads hypervisor <b>3145</b> into system memory <b>3115</b> for execution as hypervisor <b>3145</b>′. PNA IHS <b>3100</b> also loads PNA tool <b>3300</b>′ into system memory <b>3115</b> for execution as PNA tool <b>3300</b>″. PNA IHS <b>3100</b> may also load LPAR <b>3180</b>-<b>1</b>, LPAR <b>3180</b>-<b>2</b>, . . . , LPAR <b>3180</b>-F into system memory <b>3115</b> for execution as LPAR <b>3180</b>-<b>1</b>′, LPAR <b>3180</b>-<b>2</b>′, . . . , LPAR <b>3180</b>-F′, respectively.
0406In another embodiment, when PNA IHS <b>3100</b> initializes, the IHS may load an operating system (not shown) into system memory <b>3115</b> for execution. In another embodiment, when PNA IHS <b>3100</b> initializes, the IHS may load an operating system (not shown) that includes a hypervisor (not shown) and includes LPAR <b>3180</b>-<b>1</b>, LPAR <b>3180</b>-<b>2</b>, . . . , LPAR <b>3180</b>-F as virtual machines (not shown) into system memory <b>3115</b> for execution.
0407<figref idref="DRAWINGS">FIG. 32</figref> is a block diagram of a privileged network access management (PNAM) IHS <b>3200</b> that may be used in the disclosed privileged network access system. Like numbers indicate like elements with respect to <figref idref="DRAWINGS">FIG. 5</figref>. PNAM IHS <b>3200</b> includes a processor <b>3205</b> that may include multiple cores. PNAM IHS <b>3200</b> processes, transfers, communicates, modifies, stores or otherwise handles information in digital form, analog form or other form. PNAM IHS <b>3200</b> includes a bus <b>3210</b> that couples processor <b>3205</b> to memory <b>3215</b> via a memory controller <b>3220</b> and memory bus <b>3225</b>. System memory <b>3215</b> may also be referred to as main memory. System memory <b>3215</b> may be a static random access memory (SRAM) array or a dynamic random access memory (DRAM) array. Processor <b>3205</b> may also include local memory such as L1, L2 and L3 caches. A video graphics controller <b>3230</b> couples display <b>3235</b> to bus <b>3210</b>. Nonvolatile storage <b>3240</b>, such as a hard disk drive, solid-state drive (SSD), CD drive, DVD drive, or other nonvolatile storage couples to bus <b>3210</b> to provide PNAM IHS <b>3200</b> with permanent storage of information. System memory <b>3215</b> and nonvolatile storage <b>3240</b> are both forms of memory stores. Nonvolatile storage <b>3240</b> stores an operating system <b>3245</b> (OPERATING SYS) that governs operation of PNAM IHS <b>3200</b>. I/O devices <b>3250</b>, such as speakers, a keyboard and a pointing device, couple to bus <b>3210</b> via I/O controller <b>3255</b> and I/O bus <b>3260</b>.
0408One or more expansion busses <b>3265</b>, such as USB, IEEE 1394 bus, ATA, SATA, PCI, PCIE, DVI, HDMI and other busses, couple to bus <b>3210</b> to facilitate the connection of peripherals and devices to PNAM IHS <b>3200</b>. A network interface controller (NIC) <b>3270</b> couples to bus <b>3210</b> to enable PNAM IHS <b>3200</b> to connect by wire or wirelessly to a network and other information handling systems. NIC <b>3270</b> may also be called a network communication adapter, network interface adapter, network adapter, network interface or an adapter. NIC <b>3270</b> may take many forms. For example, NIC <b>3270</b> may take the form of an Ethernet (ETH) adapter, open systems adapter (OSA), RDMA enabled network interface controller (RNIC) or other network communication adapter.
0409While <figref idref="DRAWINGS">FIG. 32</figref> shows one IHS that employs processor <b>3205</b>, the IHS may take many forms. For example, PNAM IHS <b>3200</b> may take the form of a desktop, portable, laptop, notebook, tablet or other form factor computer or data processing system. PNAM IHS <b>3200</b> may take other form factors such as a gaming device, a personal digital assistant (PDA), a portable telephone device, a communication device or other devices that include a processor and memory.
0410PNAM IHS <b>3200</b> includes a privileged network access management (PNAM) tool computer program product <b>3400</b> on digital media <b>3275</b> such as a CD, DVD or other media. For simplicity, the term PNAM tool will be used below. PNAM IHS <b>3200</b> may store PNAM tool <b>3400</b> in nonvolatile storage <b>3240</b> as PNAM tool <b>3400</b>′. PNAM IHS <b>3200</b> may also store operating system <b>3245</b> (OPERATING SYS) and PNAM database <b>3280</b> in nonvolatile storage <b>3240</b>. When PNAM IHS <b>3200</b> initializes, the IHS loads operating system <b>3245</b> into system memory <b>3215</b> for execution as operating system <b>3245</b>′. PNAM IHS <b>3200</b> also loads PNAM database <b>3280</b> and PNAM tool <b>3400</b>′ into system memory <b>3215</b> for execution as PNAM database <b>3280</b>′ and PNAM tool <b>3400</b>″, respectively.
0411<figref idref="DRAWINGS">FIG. 33</figref> is a flowchart that shows a representative process flow of a privileged network access (PNA) tool <b>3300</b> that may be used in the disclosed privileged network access system. Process flow commences when PNA tool <b>3300</b> in PNA IHS <b>3100</b> initializes, as per block <b>3305</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does not transmit HCM database <b>580</b>, as per decision block <b>3310</b>, process flow continues at decision block <b>3310</b>. If HCM tool <b>600</b> in HCM IHS <b>500</b> does transmit HCM database <b>580</b>, as per decision block <b>3310</b>, a hypervisor agent in PNA IHS <b>3100</b> may receive HCM database <b>580</b>, as per block <b>3315</b>. In one embodiment, the hypervisor agent in the PNA IHS <b>3100</b> is included in hypervisor <b>3145</b>.
0412The hypervisor agent may allow hypervisor <b>3145</b> to access HCM database <b>580</b>. Hypervisor <b>3145</b> may transmit HCM database <b>580</b> to PNA tool <b>3300</b>, as per block <b>3320</b>. PNA tool <b>3300</b> may extract the hardware configuration information of PNA IHS <b>3100</b> from the HCM database <b>580</b>, as per block <b>3325</b>. In one embodiment, the hardware configuration information of PNA IHS <b>3100</b> from HCM database <b>580</b> may include, but is not limited to, on a per adapter basis, machine serial numbers (MSNs), physical identifications (PIDs), logical identifications (LIDs), adapter types, a logical partition (LPAR) access list, a physical network identification (PNet ID) of the first port of the adapter and a PNet ID of the second port of the adapter. In one embodiment, the adapter type “0087” may be an OSA network adapter and the adapter type “0008” may be an RNIC network adapter.
0413In one embodiment, the PNA tool <b>3300</b> may share the extracted hardware configuration information of PNA IHS <b>3100</b> with hypervisor <b>3145</b>. Hypervisor <b>3145</b> may update the hardware configuration of PNA IHS <b>3100</b> with the extracted hardware configuration information of PNA IHS <b>3100</b>. In another embodiment, the PNA tool <b>3300</b> may share the extracted hardware configuration information of PNA IHS <b>3100</b> with LPARs <b>3180</b>-<b>1</b>, <b>3180</b>-<b>2</b>, . . . , <b>3180</b>-F, where F is the number of LPARs in PNA IHS <b>3100</b>. LPARs <b>3180</b>-<b>1</b>, <b>3180</b>-<b>2</b>, . . . , <b>3180</b>-F may update their respective hardware configuration with the extracted hardware configuration information of PNA IHS <b>3100</b>.
0414If PNAM tool <b>3400</b> in privileged network access management (PNAM) IHS <b>3200</b> does not transmit PNAM database <b>3280</b>, as per decision block <b>3330</b>, process flow continues at decision block <b>3330</b>. If PNAM tool <b>3400</b> in PNAM IHS <b>3200</b> does transmit PNAM database <b>3280</b>, as per decision block <b>3330</b>, a hypervisor agent in PNA IHS <b>3100</b> may receive PNAM database <b>3280</b>, as per block <b>3335</b>.
0415The hypervisor agent may allow hypervisor <b>3145</b> to access PNAM database <b>3280</b>. Hypervisor <b>3145</b> may transmit PNAM database <b>3280</b> to PNA tool <b>3300</b>, as per block <b>3340</b>. PNA tool <b>3300</b> may extract the privileged network access information of PNA IHS <b>3100</b> from the PNAM database <b>3280</b>, as per block <b>3345</b>. In one embodiment, the privileged network access information of PNA IHS <b>3100</b> from PNAM database <b>3280</b> may include, but is not limited to, on a per PNet ID, per IHS basis, PNet IDs, MSNs and logical partition (LPAR) access lists.
0416In one embodiment, the PNA tool <b>3300</b> may share the extracted privileged network access information of PNA IHS <b>3100</b> with hypervisor <b>3145</b>. Hypervisor <b>3145</b> may update the privileged network access information of PNA IHS <b>3100</b> with the extracted privileged network access information of PNA IHS <b>3100</b>. In another embodiment, the PNA tool <b>3300</b> may share the extracted privileged network access information of PNA IHS <b>3100</b> with LPARs <b>3180</b>-<b>1</b>, <b>3180</b>-<b>2</b>, . . . , <b>3180</b>-F, where F is the number of LPARs in PNA IHS <b>3100</b>. LPARs <b>3180</b>-<b>1</b>, <b>3180</b>-<b>2</b>, . . . , <b>3180</b>-F may update their respective privileged network access information with the extracted privileged network access information of PNA IHS <b>3100</b>.
0417Utilizing the extracted hardware configuration information and the extracted privileged network access information, PNA tool <b>3300</b> may determine if a particular LPAR is allowed to access a particular privileged network, as per decision block <b>3350</b>. PNA tool <b>3300</b> may determine that a particular LPAR is allowed to access a particular privileged network, as per decision block <b>3350</b>. PNA tool <b>3300</b> may grant the particular LPAR access to the particular privileged network, as per block <b>3355</b>.
0418For example, as shown in <figref idref="DRAWINGS">FIGS. 25A, 25B and 26</figref>, LPAR <b>2529</b>-<b>7</b> in PNA IHS <b>2504</b> may attempt to access privileged NETWORK C <b>2524</b>. PNA tool <b>3300</b> may determine from the extracted hardware configuration information from HCM database <b>2600</b> that LPAR <b>2529</b>-<b>7</b> has access to network adapters <b>2522</b> and <b>2523</b> that both have a PNet ID of “NETC”. PNA tool <b>330</b> may determine from the extracted privileged network access information from PNAM database <b>2700</b> that PNet IDs “NETB” and “NETC” are the PNet IDs of privileged NETWORK B <b>2519</b> and privileged NETWORK C <b>2524</b>. PNA tool <b>300</b> may determine from the extracted privileged network access information from PNAM database <b>2700</b> that LPAR <b>2529</b>-<b>4</b> and LPAR <b>2529</b>-<b>5</b> of PNA IHS <b>2504</b>, i.e. MSN 00CCC0AB2 are allowed to access privileged networks with a PNet ID of “NETB” and that LPAR <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> is allowed to access privileged networks with a PNet ID of “NETC”. PNA tool <b>3300</b> may grant LPAR <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> access to privileged NETWORK C <b>2524</b>. Process flow terminates at end block <b>3365</b>.
0419PNA tool <b>3300</b> may determine that a particular LPAR is not allowed to access a particular privileged network, as per decision block <b>3350</b>. PNA tool <b>3300</b> may deny the particular LPAR access to the particular privileged network, as per block <b>3360</b>. For example, as shown in <figref idref="DRAWINGS">FIGS. 25A, 25B and 26</figref>, LPAR <b>2529</b>-<b>7</b> in PNA IHS <b>2504</b> may attempt to access privileged NETWORK C <b>2524</b>. PNA tool <b>3300</b> may determine from the extracted hardware configuration information from HCM database <b>2600</b> that LPAR <b>2529</b>-<b>7</b> has access to network adapters <b>2522</b> and <b>2523</b> that both have a PNet ID of “NETC”. PNA tool <b>330</b> may determine from the extracted privileged network access information from PNAM database <b>2700</b> that PNet IDs “NETB” and “NETC” are the PNet IDs of privileged NETWORK B <b>2519</b> and privileged NETWORK C <b>2524</b>.
0420PNA tool <b>300</b> may determine from the extracted privileged network access information from PNAM database <b>2700</b> that LPAR <b>2529</b>-<b>4</b> and LPAR <b>2529</b>-<b>5</b> of PNA IHS <b>2504</b>, i.e. MSN 00CCC0AB2 are allowed to access privileged networks with a PNet ID of “NETB” and that LPAR <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> is allowed to access privileged networks with a PNet ID of “NETC”. PNA tool <b>3300</b> may grant LPAR <b>2529</b>-<b>7</b> of PNA IHS <b>2504</b> access to privileged NETWORK C <b>2524</b>. Process flow terminates at end block <b>3365</b>. Process flow terminates at end block <b>3365</b>. Alternatively, process flow may continue at start block <b>3305</b>.
0421<figref idref="DRAWINGS">FIG. 34</figref> is a flowchart that shows a representative process flow of a privileged network access management (PNAM) tool <b>3400</b> that may be used in the disclosed privileged network access system. Process flow commences when PNAM tool <b>3400</b> in PNAM IHS <b>3200</b> is initialized, as per block <b>3405</b>. PNAM tool <b>3400</b> may determine if PNAM database <b>3280</b> exists in PNAM IHS <b>3200</b>, as per block <b>3410</b>. If PNAM database <b>3280</b> exists in PNAM IHS <b>3200</b>, PNAM tool <b>3400</b> opens PNAM database <b>3280</b> for modification, as per block <b>3415</b>. However, if PNAM database <b>3280</b> does not exist in PNAM IHS <b>3200</b>, PNAM tool <b>3400</b> generates a blank PNAM database <b>3280</b> in PNAM IHS <b>3200</b> and opens the PNAM database <b>3280</b> for modification, as per block <b>3420</b>.
0422PNAM database <b>3280</b> may store entries on a per privileged network, per PNA IHS basis, i.e., each row in PNAM database <b>3280</b> may contain information that pertains to the PNet ID of a particular privileged access network that couples to a particular PNA IHS, to which the particular PNA IHS may have access. Process flow continues as PNAM tool <b>3400</b> checks the PNA system for IHSs with access to privileged networks, as per block <b>3425</b>. If PNAM tool <b>3400</b> determines that the PNA system does not include PNA IHSs with access to privileged access networks, as per block <b>3425</b>, process flow terminates at end block <b>3460</b>.
0423If PNAM tool <b>3400</b> determines that the PNA system includes PNA IHSs with access to privileged access networks, PNAM tool <b>3400</b> may add the PNet IDs of the privileged access networks to which the PNA IHSs have privileged access, to PNAM database <b>3280</b>, as per block <b>3430</b>. For example, PNAM tool <b>3400</b> may add the PNet ID of “NETB” to PNAM database <b>3280</b> for privileged NETWORK B <b>2519</b>, to which PNA IHS <b>2504</b> has privileged access. In one embodiment, a user may input PNet IDs of physical networks to the PNAM tool <b>3400</b>. PNAM tool <b>3400</b> may then store the input PNet IDs of the physical networks in PNAM database <b>3280</b>, thereby listing the PNet IDs and respective physical networks as privileged access networks.
0424PNAM tool <b>3400</b> may modify rows of PNAM database <b>3280</b> to include the PNA IHSs and/or logical partition (LPAR) designations of LPARs in the particular PNA IHS that may access each particular network adapter, as per block <b>3435</b>. For example, as shown in <figref idref="DRAWINGS">FIGS. 25A, 25B and 27</figref>, PNAM tool <b>3400</b> may modify the first row of PNAM database <b>2700</b>, that has a “PNET ID” of “NET B” to include the “MSN” of PNA IHS <b>2504</b>, “0CCC0AB2” and the “LPAR ACCESS LIST” to include LPARs “04” and “05”, thereby listing that LPAR <b>2529</b>-<b>4</b> and LPAR <b>2529</b>-<b>5</b> in PNA IHS <b>2504</b> may access privileged NETWORK B <b>2519</b>. In one embodiment, a user may input LPAR designations of LPARs in particular PNA IHSs that may access particular privileged networks, to the PNAM tool <b>3400</b>. The PNAM tool <b>3400</b> may then modify the rows of PNAM database <b>3280</b> to include the LPAR designations of LPARs in particular PNA IHSs that may access the particular privileged networks.
0425PNAM tool <b>3400</b> inspects the configuration of the PNA system that may include the PNet ID, MSN and LPAR access list on a per privileged network, per PNA IHS basis, as per block <b>3440</b>. If PNAM tool <b>3400</b> determines that the PNA system configuration does not match PNAM database <b>3280</b>, as per block <b>3440</b>, PNAM tool <b>3400</b> updates the information stored in PNAM database <b>3280</b> with the inspected configuration of the PNA system, as per block <b>3445</b>. In one embodiment, a user may view PNAM database <b>3280</b> with PNAM tool <b>3400</b> and determine if PNAM database <b>3280</b> matches the PNA system configuration. If PNAM database <b>3280</b> does not match the PNA system configuration, the user may input the PNA system configuration to the PNAM tool <b>3400</b>. PNAM tool <b>3400</b> may store the PNA system configuration input by the user to PNAM database <b>3280</b>.
0426If PNAM tool <b>3400</b> determines that the PNA system configuration does match PNAM database <b>3280</b>, as per block <b>3440</b>, process flow continues at block <b>3450</b>. If PNAM tool <b>3400</b> determines that PNAM database <b>3280</b> has been modified and/or generated, as per block <b>3450</b>, PNAM tool <b>3400</b> may transmit PNAM database <b>3280</b> to any or all PNA IHSs, as per block <b>3455</b>. For example, as shown in <figref idref="DRAWINGS">FIGS. 25A and 25B</figref>, PNAM tool <b>3400</b> may transmit PNAM database <b>2700</b> to PNA IHS <b>2504</b>, <b>2507</b>, <b>2509</b> and/or <b>2511</b> via administrative network <b>2502</b>. In one embodiment, a user may input or select a transmit command in PNAM tool <b>3400</b>, causing PNAM tool <b>3400</b> to transmit PNAM database <b>3280</b> to any or all PNA IHSs. In another embodiment PNAM tool <b>3400</b> may transmit PNAM database <b>3280</b> to any or all PNA IHSs at a user specified time interval. If PNAM tool <b>3400</b> determines that the PNAM database <b>3280</b> has not been modified and/or generated, as per block <b>3450</b>, process flow continues at block <b>3460</b>. Process flow terminates at end block <b>3470</b>. Alternatively, process flow may continue at start block <b>3405</b>.
0427As will be appreciated by one skilled in the art, aspects of the disclosed methodology may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
0428Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
0429Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
0430Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref> flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart of <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref> and/or block diagram block or blocks.
0431These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
0432The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart of <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref> described above.
0433The flowchart of <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref> illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products that perform analysis in accordance with various embodiments of the present invention. In this regard, each block in the flowcharts of <figref idref="DRAWINGS">FIGS. 7 and 8</figref> may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref>. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of <figref idref="DRAWINGS">FIGS. 6, 12, 18, 24, 33 and 34</figref> and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
0434The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
0435The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Contents4
36 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32 Sheet 33 Sheet 34 Sheet 35 Sheet 36
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10659320B2 | Cited by | United States of America | Search report |
| US2017288985A1 | Cited by | United States of America | Search report |
| US9736037B2 | Cited by | United States of America | Search report |
| US2015215153A1 | Cited by | United States of America | Pre-grant |
| US2002059427A1 | Cites | United States of America | Applicant |
| US2006282529A1 | Cites | United States of America | Applicant |
| US2007002738A1 | Cites | United States of America | Applicant |
| US2011085563A1 | Cites | United States of America | Applicant |
| US2011093849A1 | Cites | United States of America | Search report |
| US2011216669A1 | Cites | United States of America | Applicant |
| US2012317289A1 | Cites | United States of America | Search report |
| US2013290541A1 | Cites | United States of America | Search report |
| US2014010109A1 | Cites | United States of America | Search report |
| US2014213177A1 | Cites | United States of America | Applicant |
| US2015012606A1 | Cites | United States of America | Search report |
| US2015026313A1 | Cites | United States of America | Search report |
| US2015026314A1 | Cites | United States of America | Applicant |
| US2015026339A1 | Cites | United States of America | Applicant |
| US2015026677A1 | Cites | United States of America | Applicant |
| US2015339151A1 | Cites | United States of America | Applicant |
| US2015339161A1 | Cites | United States of America | Applicant |
| US2015339251A1 | Cites | United States of America | Applicant |
| US2015341354A1 | Cites | United States of America | Applicant |
| US5257379A | Cites | United States of America | Applicant |
| US7275175B2 | Cites | United States of America | Applicant |
| US7940706B2 | Cites | United States of America | Applicant |
| US8036229B2 | Cites | United States of America | Applicant |
| US20020059427A1 | Cites | United States of America | Applicant |
| US20060282529A1 | Cites | United States of America | Applicant |
| US20070002738A1 | Cites | United States of America | Applicant |
| US20110085563A1 | Cites | United States of America | Applicant |
| US20110093849A1 | Cites | United States of America | Search report |
| US20110216669A1 | Cites | United States of America | Applicant |
| US20120317289A1 | Cites | United States of America | Search report |
| US20130290541A1 | Cites | United States of America | Search report |
| US20140010109A1 | Cites | United States of America | Search report |
| US20140213177A1 | Cites | United States of America | Applicant |
| US20150012606A1 | Cites | United States of America | Search report |
| US20150026313A1 | Cites | United States of America | Search report |
| US20150026314A1 | Cites | United States of America | Applicant |
| US20150026339A1 | Cites | United States of America | Applicant |
| US20150026677A1 | Cites | United States of America | Applicant |
| US20150339151A1 | Cites | United States of America | Applicant |
| US20150339161A1 | Cites | United States of America | Applicant |
| US20150339251A1 | Cites | United States of America | Applicant |
| US20150341354A1 | Cites | United States of America | Applicant |
| Buonadonna, “Queue-Pair IP: A Hybrid Architecture for System Area Networks”; Intel Research Berkeley; Mar. 2002; pp. 1-12. | Non-patent | – | Applicant |
| Challa, “Comparative Study of Axial Flux Permanent Magnet Brushless DC Motor Operating With the Winding Connected in Single-Phase and Two-Phase System”; A Thesis Submitted to the Graduate Faculty of the Louisiana State University and Agricultural and Mechanical College in the Department of Electrical Engineering; Aug. 2006; pp. 1-8. | Non-patent | – | Applicant |
| Ching, “Link Aggregation”; Thecus Blog; Jan. 14, 2013; pp. 1-5. | Non-patent | – | Applicant |
| Dante, “Get Ready for a New Dimension in Computing.”; System z Technical Education; IBM Advanced Technical Skills in Gaithersburg, Maryland; 2011; pp. 1-144. | Non-patent | – | Applicant |
| Deek, The Impact of Channel Bonding on 802.11n Network Management; ACM CoNEXT 2011, Dec. 6-9, 2011, Tokyo, Japan; pp. 1-12. | Non-patent | – | Applicant |
| Feldman, “RoCE: An Ethernet-InfiniBand Love Story”; HPCwire, Apr. 22, 2010; pp. 1-11. | Non-patent | – | Applicant |
| Filliater, “InfiniBand Technology and Usage Update”; Mellanox Technologies; SDC Storage Developer Conference, SNIA, Santa Clara; 2012; pp. 1-48. | Non-patent | – | Applicant |
| Fischer, “Link Aggregation”; ADMIN Network & Security; © 2013 Linux New Media USA, LLC; pp. 1-4. | Non-patent | – | Applicant |
| Fuller, “Sub-microsecond interconnects for processor connectivity—The opportunity”; EDN Networks, May 22, 2013; pp. 1-10. | Non-patent | – | Applicant |
| Guijarro; “Experience and Lessons learnt from running High Availability Databases on Network Attached Storage”; International Conference on Computing in High Energy and Nuclear Physics (CHEP'07); Journal of Physics: Conference Series 119; 2008, IOP Publishing Ltd; pp. 1-10. | Non-patent | – | Applicant |
| Hendel, Link Aggregation Trunking; Sun Microsystems IEEE 802—Tutorial Session Nov. 11, 1997; pp. 1-9. | Non-patent | – | Applicant |
| Intel, “PCI-SIG SR-IOV Primer”; An Introduction to SR-IOV Technology; Jan. 2011; pp. 1-28. | Non-patent | – | Applicant |
| Lowe, “What is SR-IOV?”; The weblog of an IT pro specializing in virtualization, storage, and servers; blog.scottlowe.org; Dec. 2, 2009; pp. 1-5. | Non-patent | – | Applicant |
| Mellanox1, “RoCE vs. iWARP Competitive Analysis Brief”; Whitepaper; © Copyright 2010; Mellanox Technologies; www.mellanox.com; Nov. 2010; pp. 1-3. | Non-patent | – | Applicant |
| Mellanox2, “InfiniBand Architecture Overview Back to Basic”; www.mellanox.com; © 2009 Mellanox Technologies; pp. 1-38. | Non-patent | – | Applicant |
| Microsoft1, Overview of Single Root I/O Virtualization (SR-IOV); © 2013 Microsoft, Build date Jun. 19, 2013; p. 1. | Non-patent | – | Applicant |
| Microsoft2, “SR-IOV Architecture”; © 2013 Microsoft. Build date Jun. 19, 2013; pp. 1-3. | Non-patent | – | Applicant |
| Microsoft3, “Overview of SR-IOV Data Paths”; © 2013 Microsoft; Build date Jun. 19, 2013; pp. 1-2. | Non-patent | – | Applicant |
| QLogic, “NIC Partitioning and SR-IOV”; Technology Brief; 2012; pp. 1-4. | Non-patent | – | Applicant |
| Recio, “RDMA enabled NIC (RNIC) Verbs Overview”; dated Apr. 29, 2003; available from http://www.rdmaconsortium.org/home/RNIC<sub>—</sub>Verbs<sub>—</sub>Overview2.pdf, pp. 1-28. | Non-patent | – | Applicant |
| Rouse, “PCI Express (PCIe or PCI-E)”; SearchDataCenter.com; Mar. 28, 2008; p. 1. | Non-patent | – | Applicant |
| Singh, “I/O Configuration Using z/OS HCD and HCM”; ibm.com/redbooks; Apr. 2010; pp. 1-462. | Non-patent | – | Applicant |
| Stevens, “Network Virtualization, Management, and Security”; IBM zEnterprise System; © 2010 IBM Corporation; pp. 1-40. | Non-patent | – | Applicant |
| Torres, “Everything You Need to Know About the PCI Express”; Hardware Secrets; Jul. 12, 2012; pp. 1-8. | Non-patent | – | Applicant |
| Wiki, “RDMA over Converged Ethernet”; From Wikipedia; http://en.wikipedia.org/w/index.php? title=RDMA<sub>—</sub>over<sub>—</sub>Converged<sub>—</sub>Ethernet&oldid=564939508; last modified on Jul. 19, 2013; pp. 1-3. | Non-patent | – | Applicant |
| Woodruff, “Introduction to the InfiniBand Core Software”; Proceedings of the Linux Symposium, vol. Two; Ottawa, Ontario Canada; Jul. 20-23, 2005; pp. 1-14. | Non-patent | – | Applicant |
| ZCopy, “Quick Concepts Part 1—Introduction to RDMA”; Education and Sample Code for RDMA Programming; Powered by WordPress.com; Posted on Oct. 8, 2010; pp. 1-6. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/948,157. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/948,161. | Non-patent | – | Applicant |
| U.S. Appl. No. 13/948,163. | Non-patent | – | Applicant |
| U.S. Appl. No. 14/814,874. | Non-patent | – | Applicant |
| U.S. Appl. No. 14/814,949. | Non-patent | – | Applicant |
| U.S. Appl. No. 14/815,096. | Non-patent | – | Applicant |
| U.S. Appl. No. 14/815,191. | Non-patent | – | Applicant |
| Buonadonna, "Queue-Pair IP: A Hybrid Architecture for System Area Networks"; Intel Research Berkeley; Mar. 2002; pp. 1-12. | Non-patent | – | Applicant |
| Challa, "Comparative Study of Axial Flux Permanent Magnet Brushless DC Motor Operating With the Winding Connected in Single-Phase and Two-Phase System"; A Thesis Submitted to the Graduate Faculty of the Louisiana State University and Agricultural and Mechanical College in the Department of Electrical Engineering; Aug. 2006; pp. 1-8. | Non-patent | – | Applicant |
| Ching, "Link Aggregation"; Thecus Blog; Jan. 14, 2013; pp. 1-5. | Non-patent | – | Applicant |
| Dante, "Get Ready for a New Dimension in Computing."; System z Technical Education; IBM Advanced Technical Skills in Gaithersburg, Maryland; 2011; pp. 1-144. | Non-patent | – | Applicant |
| Deek, The Impact of Channel Bonding on 802.11n Network Management; ACM CoNEXT 2011, Dec. 6-9, 2011, Tokyo, Japan; pp. 1-12. | Non-patent | – | Applicant |
| Feldman, "RoCE: An Ethernet-InfiniBand Love Story"; HPCwire, Apr. 22, 2010; pp. 1-11. | Non-patent | – | Applicant |
| Filliater, "InfiniBand Technology and Usage Update"; Mellanox Technologies; SDC Storage Developer Conference, SNIA, Santa Clara; 2012; pp. 1-48. | Non-patent | – | Applicant |
| Fischer, "Link Aggregation"; ADMIN Network & Security; © 2013 Linux New Media USA, LLC; pp. 1-4. | Non-patent | – | Applicant |
| Fuller, "Sub-microsecond interconnects for processor connectivity-The opportunity"; EDN Networks, May 22, 2013; pp. 1-10. | Non-patent | – | Applicant |
| Guijarro; "Experience and Lessons learnt from running High Availability Databases on Network Attached Storage"; International Conference on Computing in High Energy and Nuclear Physics (CHEP'07); Journal of Physics: Conference Series 119; 2008, IOP Publishing Ltd; pp. 1-10. | Non-patent | – | Applicant |
| Hendel, Link Aggregation Trunking; Sun Microsystems IEEE 802-Tutorial Session Nov. 11, 1997; pp. 1-9. | Non-patent | – | Applicant |
| Intel, "PCI-SIG SR-IOV Primer"; An Introduction to SR-IOV Technology; Jan. 2011; pp. 1-28. | Non-patent | – | Applicant |
| Lowe, "What is SR-IOV?"; The weblog of an IT pro specializing in virtualization, storage, and servers; blog.scottlowe.org; Dec. 2, 2009; pp. 1-5. | Non-patent | – | Applicant |
| Mellanox1, "RoCE vs. iWARP Competitive Analysis Brief"; Whitepaper; © Copyright 2010; Mellanox Technologies; www.mellanox.com; Nov. 2010; pp. 1-3. | Non-patent | – | Applicant |
| Mellanox2, "InfiniBand Architecture Overview Back to Basic"; www.mellanox.com; © 2009 Mellanox Technologies; pp. 1-38. | Non-patent | – | Applicant |
| Microsoft1, Overview of Single Root I/O Virtualization (SR-IOV); © 2013 Microsoft, Build date Jun. 19, 2013; p. 1. | Non-patent | – | Applicant |
| Microsoft2, "SR-IOV Architecture"; © 2013 Microsoft. Build date Jun. 19, 2013; pp. 1-3. | Non-patent | – | Applicant |
| Microsoft3, "Overview of SR-IOV Data Paths"; © 2013 Microsoft; Build date Jun. 19, 2013; pp. 1-2. | Non-patent | – | Applicant |
| QLogic, "NIC Partitioning and SR-IOV"; Technology Brief; 2012; pp. 1-4. | Non-patent | – | Applicant |
| Recio, "RDMA enabled NIC (RNIC) Verbs Overview"; dated Apr. 29, 2003; available from http://www.rdmaconsortium.org/home/RNIC-Verbs-Overview2.pdf, pp. 1-28. | Non-patent | – | Applicant |
4 members in 1 office; this record represents the family
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2015026287A1 | United States of America | A1 | |
| US2015339161A1 | United States of America | A1 | |
| US9348649B2This record | United States of America | B2 | |
| US9495212B2 | United States of America | B2 |
66 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Correspondence Address ChangeC.AD | C.AD | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Letter Accepting Permission for Search Results Access by Foreign IPOSB69ACPR | SB69ACPR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| PTO/SB/69-Authorize EPO Access to Search ResultsSREXR141 | SREXR141 | |
| Letter Accepting Correction of Inventorship Under Rule 1.48R48ACLT | R48ACLT | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Preliminary AmendmentA.PE | A.PE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 9348649
- Application
- 13948151
Titles
- English
- Network resource management system utilizing physical network identification for converging operations
Patent term adjustment
- A delay
- +354 daysthe office missed an examination deadline
- Applicant delay
- −54 days
- Net adjustment
- 300 days
Classification
- CPC, 8
- G06F9/50
- G06F9/45533
- G06F9/5077
- G06F16/20
- G06F15/167
- H04L47/70
- G06F17/30286
- G06F2009/45595
- IPC, 11
- G06F15 167
- G06F15 177
- G06F15 173
- G06F12 00
- G06F13 00
- G06F13 28
- G06F9 50
- G06F17 30
- G06F9 455
- H04L12 911
- H04L47 70