Status in source: mandatory.
Names: vSwitchTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vSwitchTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"VSwitchEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"A Table of information specific to vSwitches within the PAN. vSwitches establish connectivity between pServers and external networks or between pServers. Internal Connectivity - LPAN Administrators can create Eths for pBlade-to-pBlade communication using any vSwitch they have permission to access. If two pServers connect to the same vSwitch, the two pServers can communicate via IP. External Connectivity - BladeFrame architecture only supports external network communication through a Redundant Ethernet (rEth) configuration. PAN or BladeFrame Administrators can only create vSwitches for external connectivity using an uplink configured with the 'reth' command. \"",
"::=",
"{",
"vSwitches",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"VSwitchEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"A Table of information specific to vSwitches within the PAN. vSwitches establish connectivity between pServers and external networks or between pServers. Internal Connectivity - LPAN Administrators can create Eths for pBlade-to-pBlade communication using any vSwitch they have permission to access. If two pServers connect to the same vSwitch, the two pServers can communicate via IP. External Connectivity - BladeFrame architecture only supports external network communication through a Redundant Ethernet (rEth) configuration. PAN or BladeFrame Administrators can only create vSwitches for external connectivity using an uplink configured with the 'reth' command."
],
null,
null,
null,
null
]
}