ZxAnQosAclTrafficLimitEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclTrafficLimitRuleId |
Integer32 |
|
|
zxAnQosAclTrafficLimitCir |
INTEGER |
|
|
zxAnQosAclTrafficLimitPir |
INTEGER |
|
|
zxAnQosAclTrafficLimitCbs |
INTEGER |
|
|
zxAnQosAclTrafficLimitEbs |
INTEGER |
|
|
zxAnQosAclTrafficLimitPbs |
INTEGER |
|
|
zxAnQosAclTrafficLimitMode |
INTEGER |
|
|
zxAnQosAclTrafficRowStatus |
RowStatus |
|
ZxAnQosAclPriorityMarkEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclPriorityMarkRuleId |
Integer32 |
|
|
zxAnQosAclPriMarkDscp |
INTEGER |
|
|
zxAnQosAclPriMarkCos |
INTEGER |
|
|
zxAnQosAclPriMarkPrecedence |
INTEGER |
|
|
zxAnQosAclPriMarkTrafficClass |
Integer32 |
|
|
zxAnQosAclPriMarkRowStatus |
RowStatus |
|
ZxAnQosAclVlanMarkEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclVlanMarkRuleId |
Integer32 |
|
|
zxAnQosAclVlanMarkVid |
INTEGER |
|
|
zxAnQosAclVlanMarkRowStatus |
RowStatus |
|
ZxAnQosAclRedirectEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclRedirectRuleId |
Integer32 |
|
|
zxAnQosAclRedirectType |
INTEGER |
|
|
zxAnQosAclRedirectIf |
Integer32 |
|
|
zxAnQosAclRedirectNextHopIpType |
InetAddressType |
|
|
zxAnQosAclRedirectNextHopIp |
InetAddress |
|
|
zxAnQosAclRedirectSubIf |
ZxAnSubIfIndex |
|
|
zxAnQosAclRedirectRowStatus |
RowStatus |
|
ZxAnQosAclTrafficMirrorEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclTrafficMirrorRuleId |
Integer32 |
|
|
zxAnQosAclTrafficMirrorType |
INTEGER |
|
|
zxAnQosAclTrafficMirrorIf |
Integer32 |
|
|
zxAnQosAclTrafficMirrorVid |
Integer32 |
|
|
zxAnQosAclTrafficMirrorCos |
Integer32 |
|
|
zxAnQosAclTrafficMirrorTpid |
Integer32 |
|
|
zxAnQosAclTrafficMirrorSubIf |
ZxAnSubIfIndex |
|
|
zxAnQosAclTrafficMirrorRowStatus |
RowStatus |
|
ZxAnQosAclTrafficStatsEntry |
|
SEQUENCE |
|
|
|
|
zxAnQosAclTrafficStatsRuleId |
Integer32 |
|
|
zxAnQosAclTrafficStatsPktsHc |
Counter64 |
|
|
zxAnQosAclTrafficStatsOctetsHc |
Counter64 |
|
|
zxAnQosAclTrafficStatsPktRate |
CounterBasedGauge64 |
|
|
zxAnQosAclTrafficStatsOctetRate |
CounterBasedGauge64 |
|
|
zxAnQosAclTrafficStatsReset |
INTEGER |
|
|
zxAnQosAclTrafficStatsRowStatus |
RowStatus |
|
zxAnQosAclCapabilities |
1.3.6.1.4.1.3902.1082.50.5.1.1 |
The QoS ACL capabilities for this equipment.
The bit value 1 means the function represented by this bit is
supported.
priMarkTrafficClass(0): value 1 means supporting
zxAnQosAclPriMarkTrafficClass.
trafficLimitNotSupportColor(1): value 1 means not supporting
priMarkNotSupportPrecedence(4): value 1 means not supporting
zxAnQosAclPriMarkPrecedence.
trafficMirrorSupportSubIf(9): value 1 means supporting
zxAnQosAclTrafficMirrorSubIf.
redirectSupportSubIf(10): value 1 means supporting
zxAnQosAclRedirectSubIf.
|
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
BITS |
priMarkTrafficClass(0), trafficLimitNotSupportColor(1), priMarkNotSupportLocalPrecedence(2), priMarkNotSupportDropPrecedence(3), priMarkNotSupportPrecedence(4), redirectNotSupportNextHop(5), trafficMirrorNotSupportErspan(6), trafficStatsNotSupportPktColor(7), trafficStatsNotSupportType(8), trafficMirrorSupportSubIf(9), redirectSupportSubIf(10) |
|
zxAnQosAclTrafficLimitEntry |
1.3.6.1.4.1.3902.1082.50.5.2.2.2.1 |
Acl traffic-limit entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To create an entry, there are several cases. The mandatory
and optional variables are different in each case.
Case 1: to create an entry based on single rate three color marker
algorithm:
mandatory: zxAnQosAclTrafficLimitCir,
zxAnQosAclTrafficLimitCbs,
zxAnQosAclTrafficLimitEbs,
zxAnQosAclTrafficLimitMode
Case 2: to create an entry based on two rate three color marker
algorithm:
mandatory: zxAnQosAclTrafficLimitCir,
zxAnQosAclTrafficLimitCbs,
zxAnQosAclTrafficLimitPir,
zxAnQosAclTrafficLimitPbs
zxAnQosAclTrafficLimitMode,
After an entry is created, no variable can be modified.
If a manager tries to modify any variables in this entry,
agent will return error with SNMP error code inconsistentValue. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclTrafficLimitEntry |
|
|
zxAnQosAclPriorityMarkEntry |
1.3.6.1.4.1.3902.1082.50.5.2.2.3.1 |
Acl priority-mark entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To create an entry, a manager must follow a few rules:
1. One of these four variables(zxAnQosAclPriMarkDscp,
zxAnQosAclPriMarkPrecedence, zxAnQosAclPriMarkCos,
zxAnQosAclPriMarkTrafficClass) must be
included in one SNMP set operation.
2. zxAnQosAclPriMarkDscp is mutually exclusive. Manager can't set these two variables
at the same time.
4. zxAnQosAclPriMarkTrafficClass is mutually exclusive.
Manager can't set these two variables at the same time.
After an entry is created, no variable can be modified.
If a manager tries to modify any variables in this entry,
agent will return error with SNMP error code inconsistentValue. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclPriorityMarkEntry |
|
|
zxAnQosAclVlanMarkEntry |
1.3.6.1.4.1.3902.1082.50.5.2.2.4.1 |
Acl vlan-mark entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To create an entry of this table, all the variable are mandatory.
After an entry is created, no variable can be modified.
If a manager tries to modify any variables in this entry,
agent will return error with SNMP error code inconsistentValue. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclVlanMarkEntry |
|
|
zxAnQosAclRedirectEntry |
1.3.6.1.4.1.3902.1082.50.5.2.2.5.1 |
Acl vlan-mark entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To create an entry, there are several cases based
on the variable zxAnQosAclRedirectType. The mandatory and optional
variables are different in each case.
Case 1: to create an entry when zxAnQosAclRedirectType is
cpu(1):
mandatory: none
optional : none
Case 2: to create an entry when zxAnQosAclRedirectType is
interface(2):
mandatory: zxAnQosAclRedirectIf
optional : none
After an entry is created, no variable can be modified.
If a manager tries to modify any variables in this entry,
agent will return error with SNMP error code inconsistentValue. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclRedirectEntry |
|
|
zxAnQosAclTrafficMirrorEntry |
1.3.6.1.4.1.3902.1082.50.5.2.2.6.1 |
Acl traffic-mirror entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To create an entry, there are several cases based
on the variable zxAnQosAclTrafficMirrorType. The mandatory
and optional variables are different in each case.
Case 1: to create an entry when zxAnQosAclTrafficMirrorType is
cpu(1):
mandatory: none
optional : none
Case 2: to create an entry when zxAnQosAclTrafficMirrorType is
interface(2):
mandatory: zxAnQosAclTrafficMirrorIf
optional : none
Case 3: to create an entry when zxAnQosAclTrafficMirrorType is
rspan(3):
mandatory: zxAnQosAclTrafficMirrorIf
zxAnQosAclTrafficMirrorVid,
optional : zxAnQosAclTrafficMirrorCos,
zxAnQosAclTrafficMirrorTpid,
Case 4: to create an entry when zxAnQosAclTrafficMirrorType is
erspan(4):
mandatory: zxAnQosAclTrafficMirrorDstIpType
zxAnQosAclTrafficMirrorSrcIpAddr
optional : zxAnQosAclTrafficMirrorCos
zxAnQosAclTrafficMirrorTpid
zxAnQosAclTrafficMirrorTtl
zxAnQosAclTrafficMirrorDscp
After an entry is created, no variable can be modified.
If a manager tries to modify any variables in this entry,
agent will return error with SNMP error code inconsistentValue. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclTrafficMirrorEntry |
|
|
zxAnQosAclTrafficStatsEntry |
1.3.6.1.4.1.3902.1082.50.5.2.3.2.1 |
Acl traffic-statistics entry.
The multi-variables binding rule should be complied with when a
manager creates an entry. According to this rule, all the related
mib variables must be included in one SNMP set operation.
There are two types of variables: mandatory and optional.
All of the mandatory variables must be included in one SNMP set
operation. Optional variables may be included in one SNMP set
operation with the mandatory variables, but must not be used alone.
To reset the count, zxAnQosAclTrafficStatsReset is mandatory.
When an entry is created, modify operation is not allowed. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
ZxAnQosAclTrafficStatsEntry |
|
|