Status in source: mandatory.
Names: rEthTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rEthTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"REthEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"A list of rEth entries containing information about each redundant Ethernet (rEth) in the PAN. A rEth is a pair of Ethernet Network Interface Cards (NICs), one on each cBlade, with the same configuration and external connectivity. A rEth provides redundant load-balancing and failover capability for BladeFrame network connectivity. Egenera rEth Naming Conventions ethx@bladeframename/cn Reference to a cBlade Network Interface Card (NIC). BladeFrame naming conventions require you to use a '/' between the BladeFrame name and cBlade number. For example eth1 on cBlade 2 on the BladeFrame named Egenera, would be referred to as 'eth1@Egenera/c2'.\"",
"::=",
"{",
"rEths",
"1",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"REthEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"A list of rEth entries containing information about each redundant Ethernet (rEth) in the PAN. A rEth is a pair of Ethernet Network Interface Cards (NICs), one on each cBlade, with the same configuration and external connectivity. A rEth provides redundant load-balancing and failover capability for BladeFrame network connectivity. Egenera rEth Naming Conventions ethx@bladeframename/cn Reference to a cBlade Network Interface Card (NIC). BladeFrame naming conventions require you to use a '/' between the BladeFrame name and cBlade number. For example eth1 on cBlade 2 on the BladeFrame named Egenera, would be referred to as 'eth1@Egenera/c2'."
],
null,
null,
null,
null
]
}