Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"h3cFCoEStaticVfcTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"H3cFCoEStaticVfcEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an association. The binding does not need to be specified when the row for a VFC is created, but may be specified later.\"",
"::=",
"{",
"h3cFCoEConfig",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"H3cFCoEStaticVfcEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This table facilitates the creation and deletion of static VFC interfaces. While VFCs can be dynamically created based on FIP FLOGI/ELP requests, operators may want to associate certain pre-configured policy for a particular ENode or a remote-FCF. In such cases static VFC creation becomes necessary. In addition to being creating, a static VFC also needs to be associated to an ENode or remote-FCF. The VFC binding provides such an association. The binding does not need to be specified when the row for a VFC is created, but may be specified later."
],
null,
null,
null,
null
]
}