Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"issAclTrafficSeperationCtrl",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"systemdefault",
"(",
"1",
")",
",",
"userconfig",
"(",
"2",
")",
",",
"none",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object provides control to administrator, to have system default or user defined ACL/QoS rules to carry control traffic to CPU. system-default: ACL/QoS rules for all the control packets will be automatically installed by the ISS software at system init time.Either a 'switch-and-copy-to-cpu'filter (or) 'drop-and-copy-to-cpu' filter will be installed, as appropriate, for getting the control packets to CPU, for processing. Each ACL rule will be associated with class-map, meter and policy map with protocol ID, and CPU queue number user-config: The ACL/QoS rules for receiving all the control packets to CPU for processing, will NOT be automatically installed by the the ISS software.The administrator is expected to install required rules for the control packets as requried. none: ACL/QoS rules for all the control packets will be automatically installed by the ISS software at system init time.Either a 'switch-and-co py-to-cpu'filter (or) 'drop-and-copy-to-cpu' filter will be installed, as appropriate, for getting the control packets to CPU, for processing. Default mode is none If the configuration is changed from 'systemdefault' to 'userconfig' option, then all the default ACL/QoS rules for carrying protocol control packets to CPU are removed.Then user has to install the specific ACL/QoS rules, to carry the intended control packets to CPU for the processing. If the configuration is changed from 'userconfig' to 'systemdefault', all the default ACL/QoS rules are installed. Already existing(if any) user configured ACL rules in the system are not removed. If the configuration is changed from 'none' to 'systemdefault' option, then all the default ACL filters for carrying protocol control packets to CPU are removed and new set of filters will be installed. Each filter will be associated with Qos rules. If the configuration is changed from 'none' to 'userconfig' option, then all the default ACL filters for carrying protocol control packets to CPU are removed.Then user has to install the specific ACL/QoS rules, to carry the intended control packets to CPU for the processing. If the configuration is changed from 'userconfig' to 'none' all the default ACL filters are installed. Already existing(if any) user configured ACL rules in the system are not removed. Above three options can be configured during system runtime.\"",
"DEFVAL",
"{",
"none",
"}",
"::=",
"{",
"issAclTrafficControl",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"systemdefault",
1
],
[
"userconfig",
2
],
[
"none",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object provides control to administrator, to have system default or user defined ACL/QoS rules to carry control traffic to CPU. system-default: ACL/QoS rules for all the control packets will be automatically installed by the ISS software at system init time.Either a 'switch-and-copy-to-cpu'filter (or) 'drop-and-copy-to-cpu' filter will be installed, as appropriate, for getting the control packets to CPU, for processing. Each ACL rule will be associated with class-map, meter and policy map with protocol ID, and CPU queue number user-config: The ACL/QoS rules for receiving all the control packets to CPU for processing, will NOT be automatically installed by the the ISS software.The administrator is expected to install required rules for the control packets as requried. none: ACL/QoS rules for all the control packets will be automatically installed by the ISS software at system init time.Either a 'switch-and-co py-to-cpu'filter (or) 'drop-and-copy-to-cpu' filter will be installed, as appropriate, for getting the control packets to CPU, for processing. Default mode is none If the configuration is changed from 'systemdefault' to 'userconfig' option, then all the default ACL/QoS rules for carrying protocol control packets to CPU are removed.Then user has to install the specific ACL/QoS rules, to carry the intended control packets to CPU for the processing. If the configuration is changed from 'userconfig' to 'systemdefault', all the default ACL/QoS rules are installed. Already existing(if any) user configured ACL rules in the system are not removed. If the configuration is changed from 'none' to 'systemdefault' option, then all the default ACL filters for carrying protocol control packets to CPU are removed and new set of filters will be installed. Each filter will be associated with Qos rules. If the configuration is changed from 'none' to 'userconfig' option, then all the default ACL filters for carrying protocol control packets to CPU are removed.Then user has to install the specific ACL/QoS rules, to carry the intended control packets to CPU for the processing. If the configuration is changed from 'userconfig' to 'none' all the default ACL filters are installed. Already existing(if any) user configured ACL rules in the system are not removed. Above three options can be configured during system runtime."
],
null,
null,
null,
[
"DEFVAL",
"none"
]
]
}