Status in source: current.
Names: fsMIIpv6IfScopeZoneMapTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIIpv6IfScopeZoneMapTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"FsMIIpv6IfScopeZoneMapEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"A zone index identifies an instance of a specific scope uniquely within the system.The zone index is used to associate unambiguously an IPv6 address to a specific zone. Following are the changes that has been done in fsMIIpv6IfScopeZoneMapTable 1) The Zone-Index which is of type InetZoneIndex in stdipvx.mib is changed to DisplayString for user convenience.As the user is aware of the zones by the scope-zone name rather than the index (i.e Linklocal1 or sitelocal1,scope61,scope71) it has been changed to DisplayString. But the index associated with the scope-zone is displayed by ipv6ScopeZoneIndexTable. 2) The InetZoneIndex definition in INET-ADDRESS-MIB says that the zone-index will typically be the interface index for link-local address, but as per the Aricent design the Zone-Index is taken as a free flowing number starting from the value 1, hence the value of ipv6ScopeZoneIndexLinkLocal shall not be complaint with InetZoneIndex definition. 3) It is also mentioned that the zone-index value of 0 refers to the default zone. But the Aricent design implements the default scope-zone index for every scope by the fsipv6ScopeMemberEntry mib table. Hence the default-zone index of value 0 is also not supported 4) The scope-zone index that are not configured on an interface shall take a alpha numeric value of invalid in FsMIIpv6IfScopeZoneMapEntry and -1 for the index value in ipv6ScopeZoneIndexTable. \"",
"REFERENCE",
"\"Section 2.7 of RFC 4291\"",
"::=",
"{",
"fsMIipv6",
"13",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"FsMIIpv6IfScopeZoneMapEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A zone index identifies an instance of a specific scope uniquely within the system.The zone index is used to associate unambiguously an IPv6 address to a specific zone. Following are the changes that has been done in fsMIIpv6IfScopeZoneMapTable 1) The Zone-Index which is of type InetZoneIndex in stdipvx.mib is changed to DisplayString for user convenience.As the user is aware of the zones by the scope-zone name rather than the index (i.e Linklocal1 or sitelocal1,scope61,scope71) it has been changed to DisplayString. But the index associated with the scope-zone is displayed by ipv6ScopeZoneIndexTable. 2) The InetZoneIndex definition in INET-ADDRESS-MIB says that the zone-index will typically be the interface index for link-local address, but as per the Aricent design the Zone-Index is taken as a free flowing number starting from the value 1, hence the value of ipv6ScopeZoneIndexLinkLocal shall not be complaint with InetZoneIndex definition. 3) It is also mentioned that the zone-index value of 0 refers to the default zone. But the Aricent design implements the default scope-zone index for every scope by the fsipv6ScopeMemberEntry mib table. Hence the default-zone index of value 0 is also not supported 4) The scope-zone index that are not configured on an interface shall take a alpha numeric value of invalid in FsMIIpv6IfScopeZoneMapEntry and -1 for the index value in ipv6ScopeZoneIndexTable."
],
[
"REFERENCE",
"Section 2.7 of RFC 4291"
],
null,
null,
null
]
}