H3C-ACFP-MIB
AI MIB Summary
The H3C-ACFP-MIB module provides SNMP objects for configuring and monitoring the Access Control Firewall Policy (ACFP) features on H3C switches and routers, enabling centralized management of firewall rule enforcement and session states.
This MIB module defines a set of basic objects for configuring switches and routers to enable ACFP.
Main OID:
h3cAcfp.1.3.6.1.4.1.2011.10.2.74
75
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
75 total| Object Name |
|---|
h3cAcfpThis MIB module defines a set of basic objects for configuring switches and routers to enable ACFP. MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.74 |
h3cAcfpObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1 |
h3cAcfpOAP OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1 |
h3cAcfpServer OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1.1 |
h3cAcfpServerInfoWhen retrieved, this object returns a set of bits indicating the capabilities (or configuration) of the switch or router. The set bit is indication that a router or switch can support the action for security rule.ro Bits .1.3.6.1.4.1.2011.10.2.74.1.1.1.1 |
h3cAcfpServerMaxLifetimeWhen retrieved, this object returns the maximum lifetime in seconds, that this router or switch allows policy rules to have.ro Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.1.2 |
h3cAcfpServerPersistentRulesWhen retrieved, this object returns true(1) if the ACFP MIB implementation can store policy rules persistently. Otherwise, it returns false(2).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.1.3 |
h3cAcfpServerCurContextTypeIn some circumstances, it's necessary that packets go to ACFP client with context from ACFP server. However, the context perhaps is different. h3cAcfpServerCurContextType is used to distinguish this difference, ACFP client may process distinctively.ro Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.1.4 |
h3cAcfpClientInfo OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1.2 |
h3cAcfpClientInfoTableThis table contains the basic information about ACFP client. SEQUENCE OF H3cAcfpClientInfoEntry .1.3.6.1.4.1.2011.10.2.74.1.1.2.1 |
h3cAcfpClientInfoEntryThis list contains the basic information about ACFP client. H3cAcfpClientInfoEntry .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1 |
h3cAcfpClientIDThe identifier of ACFP client.ro Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.1 |
h3cAcfpClientDescriptionDescription of the application that is running on ACFP client, eg. IPS, VCX.rw DisplayString .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.2 |
h3cAcfpClientHwVersionThe hardware revision of ACFP client.rw DisplayString .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.3 |
h3cAcfpClientOSVersionThe operating system version running ACFP client.rw DisplayString .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.4 |
h3cAcfpClientAppVersionThe application version running on ACFP clientrw DisplayString .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.5 |
h3cAcfpClientIPIP address of ACFP client.rw IpAddress .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.6 |
h3cAcfpClientModeACFP client informs Router or switch which mode it is operating. Router or switch checks h3cAcfpServerInfo to see whether it is capable of fulfilling this function. If not, router or switch generates a trap informing ACFP client such OAP mode is not supported.rw Bits .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.7 |
h3cAcfpClientRowStatusRowStatus, supports three states: createAndGo, active, destroy. Creation Operation Restriction: Node h3cAcfpClientMode must be bound while creating a row. It is optional for other nodes. ACFP module must be enabled for the server while creating a row. The number of rows created must not exceed upper limit. Modification Operation Restriction: Nodes that do not support modification: h3cAcfpClientMode. Nodes that support modification: h3cAcfpClientDescription, h3cAcfpClientHwVersion, h3cAcfpClientOSVersion, h3cAcfpClientAppVersion and h3cAcfpClientIP. If the row to be modified does not exist, error returns directly. Deletion Operation Restriction: If the row to be deleted does not exist, success returns directly.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.2.1.1.8 |
h3cAcfpPolicy OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1.3 |
h3cAcfpPolicyTableThis table lists all current policies for ACFP client(s). Entries in this table are created or removed implicitly when entries in the h3cAcfpRuleTable are created or removed, respectively. A policy entry in this table only exists as long as there is rule of this policy in the h3cAcfpRuleTable. The table serves for listing the existing policies and their remaining lifetimes and for changing lifetimes of policies and implicitly of all policy members and all their member policy rules can be deleted by setting h3cAcfpPolicyLifetime to 0. SEQUENCE OF H3cAcfpPolicyEntry .1.3.6.1.4.1.2011.10.2.74.1.1.3.1 |
h3cAcfpPolicyEntryThe list contains basic information of ACFP Policy. H3cAcfpPolicyEntry .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1 |
h3cAcfpPolicyIndexThe identifier of the Policy of ACFP clientro Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.1 |
h3cAcfpPolicyInIfIndexPacket is received from this interface. The value of this object contains the same value of ifIndex of ifTable.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.2 |
h3cAcfpPolicyOutIfIndexPacket is sent to this interface. The value of this object contains the same value of ifIndex of ifTable.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.3 |
h3cAcfpPolicyDestIfIndexThrough this interface, packet go to ACFP client from ACFP server. The value of this object contains the same value of ifIndex of ifTable.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.4 |
h3cAcfpPolicyContextIDInternal id ACFP server allocated used to map to the interface. ACFP server may send packet with this h3cAcfpPolicyContextID to ACFP client, ACFP client can make use of this h3cAcfpPolicyContextID and find the policy.ro Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.5 |
h3cAcfpPolicyAdminStatusThe value of this object indicates the desired status of the policy.rw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.6 |
h3cAcfpPolicyLifetimeWhen retrieved, this object delivers the maximum lifetime (seconds) of all the rules of this, i.e., of all the rows in h3cAcfpRuleTable that have the same values of h3cAcfpRulePolicyIndex and h3cAcfpClientID. Successfully writing to this object modifies the lifetime of all the rules of this. Successfully writing a value of 0 terminates all the rules and implicitly deletes this as soon as all member entries are removed from the h3cAcfpRuleTable. Note that after a lifetime expired, all the corresponding entry in the h3cAcfpRuleTable will be removed and this will be deleted implicitly. Writing to this object is processed by the ACFP MIB implementation by choosing a lifetime value that is greater than or equal to zero and less than or equal to the minimum of the requested value and the value specified by object h3cAcfpServerMaxLifetime: 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum) whereas: lt_granted is the actually granted lifetime by the ACFP MIB implementation. lt_requested is the requested lifetime of the ACFP client. lt_maximum is the value of object h3cAcfpServerMaxLifetime. SNMP set requests to this object may be rejected or the value of the object after an accepted set operation may be less than the value that was contained in the SNMP set request.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.7 |
h3cAcfpPolicyTimeStartBeginning time of this policy every day. Eg. HH:MM:SSrw OCTET STRING .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.8 |
h3cAcfpPolicyTimeEndEnding time of this policy every day. Eg. HH:MM:SSrw OCTET STRING .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.9 |
h3cAcfpPolicyRowStatusRowStatus, supports three states: createAndGo, active, destroy. Creation Operation Restriction: The client corresponding to the index h3cAcfpClientID must exist while creating a row. Nodes h3cAcfpPolicyTimeStart and h3cAcfpPolicyTimeEnd are bound together, and h3cAcfpPolicyTimeEnd must be greater than h3cAcfpPolicyTimeStart. The number of rows created on an incoming/outgoing interface cannot exceed the upper limit. The number of rows created cannot exceed the upper limit for each client. A packet matches a policy in the following order: - It first matches the policy with the highest priority. - For two policies with the same priority, it matches the one with the smallest client index. - For two policies with the same client index, it matches the one with the smallest policy index. Modification Operation Restriction: Nodes that do not support modification: h3cAcfpPolicyInIfIndex, h3cAcfpPolicyOutIfIndex, h3cAcfpPolicyDestIfIndex, h3cAcfpPolicyDestIfFailAction, h3cAcfpPolicyPriority. Nodes that support modification: h3cAcfpPolicyAdminStatus, h3cAcfpPolicyLifetime, h3cAcfpPolicyTimeStart and h3cAcfpPolicyTimeEnd. While modifying a row, if the row corresponding to the index configured does not exist, error returns directly. While modifying a node, the restriction over h3cAcfpPolicyTimeStart and h3cAcfpPolicyTimeEnd is the same as creating a node. Deletion Operation Restriction: If the row to be deleted does not exist, success returns directly.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.10 |
h3cAcfpPolicyDestIfFailActionThe value of this object indicates the action of the policy when the destination interface failed.rw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.11 |
h3cAcfpPolicyPriorityThe value of this object indicates the priority of the policy. Priority8 is maximal priority. Priority1 is minimal priority.rw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.3.1.1.12 |
h3cAcfpRule OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1.4 |
h3cAcfpRuleTableThis table lists all the rules. It is indexed by h3cAcfpClientID, h3cAcfpRulePolicyIndex and h3cAcfpRuleIndex. Entries can be deleted by writing h3cAcfpPolicyLifetime to 0. SEQUENCE OF H3cAcfpRuleEntry .1.3.6.1.4.1.2011.10.2.74.1.1.4.1 |
h3cAcfpRuleEntryThe list contains basic information of the rule. H3cAcfpRuleEntry .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1 |
h3cAcfpRuleIndexThe identifier of the rules which have the same h3cAcfpPolicyIndex and h3cAcfpClientID.h3cAcfpRuleIndex indicates rule sequence in the same policy.ro Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.1 |
h3cAcfpRuleOperStatusThe value of this object indicates the status of a rule. success : Applied rule to interface successfully. fail : Failed to apply rule to interface.ro Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.2 |
h3cAcfpRuleActionThe action of this rule.rw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.3 |
h3cAcfpRuleAllThe rule match all packet or does not. true : all false : not allrw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.4 |
h3cAcfpRuleSrcMACSource MAC of this rule.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.5 |
h3cAcfpRuleDstMACDestination MAC of this rule.rw MacAddress (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.6 |
h3cAcfpRuleVlanStartStarting VLAN id of this rule. 0 : Invalid valuerw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.7 |
h3cAcfpRuleVlanEndEnding VLAN id of this rule. 0 : Invalid valuerw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.8 |
h3cAcfpRuleProtocolThe protocol-type of this rule. <0-255> Protocol number gre GRE tunneling(47) icmp Internet Control Message Protocol(1) igmp Internet Management Protocol(2) ip Any IP protocol(0) ipinip IP in IP tunneling(4) ospf OSPF routing protocol(89) tcp Transmission Control Protocol (6) udp User Datagram Protocol (17)rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.9 |
h3cAcfpRuleSrcIPSource IP address of this rule.rw IpAddress .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.10 |
h3cAcfpRuleSrcIPMaskSource IP-address wild of this rule. Eg. 0.0.0.255.rw IpAddress .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.11 |
h3cAcfpRuleSrcOpSource Port operation for this rulerw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.12 |
h3cAcfpRuleSrcStartPortStarting UDP/TCP Source Port number of this rule.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.13 |
h3cAcfpRuleSrcEndPortEnding UDP/TCP Source Port of this rule.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.14 |
h3cAcfpRuleDstIPDestination IP address of this rule.rw IpAddress .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.15 |
h3cAcfpRuleDstIPMaskDestination IP-address wild of this rule. Eg. 0.0.0.255rw IpAddress .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.16 |
h3cAcfpRuleDstOpDestination Port operation for this rulerw Enumeration .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.17 |
h3cAcfpRuleDstStartPortStarting UDP/TCP Destination Port number of this rule.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.18 |
h3cAcfpRuleDstEndPortEnding UDP/TCP Destination Port of this rule.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.19 |
h3cAcfpRulePrecedenceThe value of precedence field in IP header. <255> Invalid value <0-7> value of precedence routine(0) Routine precedence priority(1) Priority precedence immediate(2) Immediate precedence flash(3) Flash precedence flash-override(4) Flash Override precedence critical(5) Critical precedence internet(6) Network Control precedence network(7) Internetwork Control precedencerw Integer32(0..7|255) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.20 |
h3cAcfpRuleTosThe value of TOS field in IP header. <255> Invalid value <0-15> value of ToS (Type of Service) Normal(0) normal service min-monetary-cost(1) minimum monetary cost max-reliability(2) maximum reliability max-throughput(4) maximum throughput min-delay(8) minimum delayrw Integer32(0..15|255) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.21 |
h3cAcfpRuleDscpThe value of DSCP. <255> Invalid value <0-63> value of DSCP Be(0) best effort af11(10) assured forwarding 11 service af12(12) assured forwarding 12 service af13(14) assured forwarding 13 service af21(18) assured forwarding 18 service af22(20) assured forwarding 20 service af23(22) assured forwarding 22 service af31(26) assured forwarding 31 service af32(28) assured forwarding 32 service af33(30) assured forwarding 33 service af41(34) assured forwarding 41 service af42(36) assured forwarding 42 service af43(38) assured forwarding 43 service cs1(8) class selector 1 service cs2(16) class selector 2 service cs3(24) class selector 3 service cs4(32) class selector 4 service cs5(40) class selector 5 service cs6(48) class selector 6 service cs7(56) class selector 7 service ef(46) expedited forwarding servicerw Integer32(0..63|255) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.22 |
h3cAcfpRuleEstablishEstablish Flag. Matches the TCP packets with the ACK and/or RST flag, including the TCP packets of these types: SYN+ACK, ACK, FIN+ACK, RST, RST+ACK.rwdeprecated TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.23 |
h3cAcfpRuleFragmentThe flag of matching fragmented packet.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.24 |
h3cAcfpRulePacketRatePacket rate (Kbps) of this rule.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.25 |
h3cAcfpRuleRowStatusRowStatus, supports three states: createAndGo, active, destroy. Creation Operation Restriction: Node h3cAcfpRuleAction must be bound while creating a line. Nodes h3cAcfpRuleAll and h3cAcfpRuleProtocol, h3cAcfpRuleSrcIP, h3cAcfpRuleSrcIPMask, h3cAcfpRuleDstIP, h3cAcfpRuleSrcOp, h3cAcfpRuleSrcStartPort, h3cAcfpRuleSrcEndPort, h3cAcfpRuleDstIP, h3cAcfpRuleDstIPMask, h3cAcfpRuleDstOp, h3cAcfpRuleDstStartPort, h3cAcfpRuleDstEndPort, h3cAcfpRulePrecedence, h3cAcfpRuleTos, h3cAcfpRuleDscp, h3cAcfpRuleTCPFlag, h3cAcfpRuleFragment are mutually exclusive. Nodes h3cAcfpRuleSrcIP and h3cAcfpRuleSrcIPMask are bound together, otherwise, the source IP address is neglected. The restriction over h3cAcfpRuleDstIP and h3cAcfpRuleDstIPMask is the same as h3cAcfpRuleSrcIP and h3cAcfpRuleSrcIPMask. Nodes h3cAcfpRuleDscp and h3cAcfpRulePrecedence, h3cAcfpRuleTos are mutually exclusive. If the node h3cAcfpRuleSrcOp is bound to range(5), h3cAcfpRuleSrcStartPort and h3cAcfpRuleSrcEndPort must be bound together, and h3cAcfpRuleSrcEndPort must be greater than h3cAcfpRuleSrcStartPort. If the node h3cAcfpRuleSrcOp is bound to equal(1), notEqual(2), lessThan(3) or greaterThan(4), h3cAcfpRuleSrcStartPort must be bound together, and h3cAcfpRuleSrcEndPort is neglected. The restriction over h3cAcfpRuleDstOp, h3cAcfpRuleDstStartPort and h3cAcfpRuleDstEndPort is the same as h3cAcfpRuleSrcOp, h3cAcfpRuleSrcStartPort and h3cAcfpRuleSrcEndPort. If the node h3cAcfpRuleAction is bound to redirect(3) or mirror(4), the destination interfaces of the policy the rule belonging to must exist; The number of rows created cannot exceed the upper limit for each policy, each inbound interface and each outbound interface. Modification Operation Restriction: The row does not support modification. Deletion Operation Restriction If the row to be deleted does not exist, success returns directly.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.26 |
h3cAcfpRuleTCPFlagTCP Flag. <0> don't care for TCP flag to match packets <1-65535> care for TCP flag to match packets, the value is combination of next list. URG_VALID (1 << 13) URG_SET (1 << 5) ACK_VALID (1 << 12) ACK_SET (1 << 4) PSH_VALID (1 << 11) PSH_SET (1 << 3) RST_VALID (1 << 10) RST_SET (1 << 2) SYN_VALID (1 << 9) SYN_SET (1 << 1) FIN_VALID (1 << 8) FIN_SET 1 Matches the TCP packets with the URG and/or ACK and/or PSH and/or RST and/or SYN and/or FIN flag, including the TCP packets of these types: SYN+ACK, ACK, FIN+ACK, RST, RST+ACK.rw Integer32 .1.3.6.1.4.1.2011.10.2.74.1.1.4.1.1.27 |
h3cAcfpNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.74.1.1.5 |
h3cAcfpCurContextChangedThis notification is sent when router or switch changed h3cAcfpServerCurContextType. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.1 |
h3cAcfpClientRegisterThis notification is sent when the ACFP client is registered. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.2 |
h3cAcfpClientUnRegisterThis notification is sent when the ACFP client is unregistered. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.3 |
h3cAcfpClientDeadThis notification is sent when the ACFP client is not responding. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.4 |
h3cAcfpNotSupportedOAPModeThis notification is sent when router or switch cannot support OAP mode that ACFP client wants to operate on. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.5 |
h3cAcfpLifetimeChangeEventThis notification can be generated for indicating that The lifetime of all member rules of the was changed by successfully writing to object h3cAcfpPolicyLifetime. Note that this notification is only sent if the lifetime of a policy was changed by successfully writing to object h3cAcfpPolicyLifetime. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.6 |
h3cAcfpRuleCreatedEventThis notification is sent when a new rule is created. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.7 |
h3cAcfpRuleDeletedEventThis notification is sent when a rule is deleted. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.8 |
h3cAcfpRuleErrorEventThis notification is sent when rule cannot be applied. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.9 |
h3cAcfpLifetimeExpireEventThis notification is sent when the time of the policy existed exceeds its lifetime. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.74.1.1.5.10 |