Port pattern attributes
The following attributes provide information about a port category pattern.
These attributes can be included in the request body for the POST /patterns method and the response body for the GET /patterns/{id}/includeSettings method.
For more information about port patterns, see Defining port settings.
Attributes | Type | Description | |||
---|---|---|---|---|---|
template_type | String | Type of category pattern. This value is always Port. | |||
template | Object | Information about the system-information category pattern | |||
adapterType | String | Type of adapter to which this port pattern applies | |||
applyToSwitch | Boolean | Indicates whether to apply corresponding settings to the chassis switch internal ports, where applicable. This can be one of the following values.
| |||
chipset | String | Chipset of the adapter that is associated with this pattern | |||
description | String | Category-pattern description | |||
extendedPortTemplateId | String | Pattern IDs of a referenced extended-port category pattern that are used to configure additional port settings that are learned from the server | |||
id | String | Category pattern ID | |||
inUse | Boolean | Identifies whether the category pattern is applied to one or more servers. This can be one of the following values.
| |||
name | String | Category-pattern name | |||
portCfgMode | String | Target port operational mode. This can be one of the following values.
| |||
portCfgOptionCode | String | Protocols that are enabled for this port, This can be one of the following values.
| |||
referencedBy | Array of strings | List of pattern IDs for server patterns that reference this category pattern | |||
type | String | Type of category pattern. This value is always Port. | |||
userDefined | String | Identifies whether the category pattern is user define or learned. This can be one of the following values.
| |||
vendor | String | Vendor of the adapter that is associated with this pattern | |||
vports | Array of strings | Settings for each of the vports, when port virtualization is enabled, for example
|
Example
{
"template_type" : "Port",
"template" : {
"adapterType" : "adapter:16",
"applyToSwitch" : false,
"chipset" : "Skyhawk",
"description" : "Pattern created from server: Lenovo x240 M5\n
Learned on: Jul 28, 2015 11:42:09 AM",
"extendedPortTemplateId" : "*NONE",
"id" : "portVirtualizationPattern:55",
"inUse" : false,
"name" : "Learned-Port-1.1.1",
"portCfgMode" : "",
"portCfgOptionCode" : "*NONE",
"referencedBy" : [],
"type" : "PortVirtualization",
"userDefined" : true,
"vendor" : "Emulex",
"vports" : [
"{id:'portVirtualizationPattern:55:vport:1',portNumber:1,enabled:true,
maxSpeed:0,minSpeed:0,networkMode:'TRUNK',protocol:'ethOnly',vlanId:'0'}",
"{id:'portVirtualizationPattern:55:vport:2',portNumber:2,enabled:true,
maxSpeed:0,minSpeed:0,networkMode:'TRUNK',protocol:'',vlanId:'0'}",
"{id:'portVirtualizationPattern:55:vport:3',portNumber:3,enabled:true,
maxSpeed:0,minSpeed:0,networkMode:'TRUNK',protocol:'ethOnly',vlanId:'0'}",
"{id:'portVirtualizationPattern:55:vport:4',portNumber:4,enabled:true,
maxSpeed:0,minSpeed:0,networkMode:'TRUNK',protocol:'ethOnly',vlanId:'0'}"
]
}
}
Give documentation feedback