Brocade Unified IP MIB Reference (Supporting FastIron Release 07.5.00) - Manual (Page 430)

402 Unified IP MIB Reference
53-1002549-02
Layer 2 ACL binding configuration table
Layer 2 ACL binding configuration table
The Layer 2 ACL binding configuration table lists the Layer 2 ACLs that have been bound to a port.
fdryL2AclMirrorPackets
brcdIp.1.2.2.15.7.1.13
Syntax: TruthVal Read-write This object is optional. It is applicable only for the ACLs with a
permit clause.
When you bind a Layer 2 ACL to a port, you can configure the
port to mirror the packets to another port using the
acl-mirror-port CLI command. Then the packets permitted on this
port (as a result of the bound ACL) will be mirrored on the other
port.
Default: “false”
fdryL2AclLogEnable
brcdIp.1.2.2.15.7.1.14
Syntax: TruthVal Read-write The optional parameter to enable logging only when a deny
clause is specified. Note that the traffic denied by the implicit
deny mechanism is not subject to logging. The implicit deny
occurs when traffic does not match any of the clauses and there
is no permit any any clause specified at the end of the Layer 2
ACL.
Default: “false”
fdryL2AclRowStatus
brcdIp.1.2.2.15.7.1.15
Syntax: RowStatus Read-write The row status variable is used according to installation and
removal conventions for conceptual rows. Setting this object to
active(1) or createAndGo(4) results in the addition of a Layer 2
ACL filter in the router. Duplicate entries will be rejected during
row creation.
As part of the row creation, entries are appended to this table.
Row insertion may not be supported.
Setting this object to destroy(6) removes the associated filter
from the router. Other values in the enumeration are not used.
Name, OID, and syntax Access Description
Name, OID, and syntax Access Description
fdryL2AclIfBindTable
brcdIp.1.2.2.15.8 None The table of Layer 2 ACL binding to a port.
Layer 2 ACLs and Layer 3 ACLs cannot be bound to the same port.
However, you can configure a port to use Layer 2 ACLs, and another
port on the same device to use Layer 3 ACLs.
In general:
•
Layer 2 ACLs cannot be bound to virtual interfaces, unlike
Layer 3 ACLs.
•
You cannot modify an existing Layer 2 ACL clause. You must
first unbind the Layer 2 ACL, delete it, and then create a new
clause.
fdryL2AclIfBindDirection
brcdIp.1.2.2.15.8.1.1
Syntax: Direction None Indicates if Layer 2 ACLs are bound to incoming or outgoing ports:
•
inbound(0)
•
outbound(1))