HUAWEI-USERLOG-MIB

File: HUAWEI-USERLOG-MIB.mib (33650 bytes)

Imported modules

SNMPv2-CONF SNMPv2-SMI HUAWEI-MIB

Imported symbols

OBJECT-GROUP MODULE-COMPLIANCE IpAddress
Integer32 Counter32 OBJECT-TYPE
MODULE-IDENTITY hwDatacomm

Defined Types

HwUserlogNatSlotCfgInfoEntry  
SEQUENCE    
  hwUserlogNatCfgSlotNumber Integer32
  hwUserlogNatEnable Integer32
  hwUserlogNatAclNumber Integer32
  hwUserlogNatHostAddress IpAddress
  hwUserlogNatUdpPort Integer32

HwUserlogNatSlotRunInfoEntry  
SEQUENCE    
  hwUserlogNatRunSlotNumber Integer32
  hwUserlogNatTotalEntries Counter32
  hwUserlogNatTotalPackets Counter32
  hwUserlogNatFailedEntries Counter32
  hwUserlogNatFailedPackets Counter32
  hwUserlogNatClearRunStat Integer32

HwUserlogFlowSlotCfgInfoEntry  
SEQUENCE    
  hwUserlogFlowCfgSlotNumber Integer32
  hwUserlogFlowEnable Integer32
  hwUserlogFlowAclNumber Integer32
  hwUserlogFlowHostAddress IpAddress
  hwUserlogFlowUdpPort Integer32

HwUserlogFlowSlotRunInfoEntry  
SEQUENCE    
  hwUserlogFlowRunSlotNumber Integer32
  hwUserlogFlowTotalEntries Counter32
  hwUserlogFlowTotalPackets Counter32
  hwUserlogFlowFailedEntries Counter32
  hwUserlogFlowFailedPackets Counter32
  hwUserlogFlowClearRunStat Integer32

HwUserlogAccessSlotCfgInfoEntry  
SEQUENCE    
  hwUserlogAccessCfgSlotNumber Integer32
  hwUserlogAccessEnable Integer32
  hwUserlogAccessHostAddress IpAddress
  hwUserlogAccessUdpPort Integer32

HwUserlogAccessSlotRunInfoEntry  
SEQUENCE    
  hwUserlogAccessRunSlotNumber Integer32
  hwUserlogAccessTotalEntries Counter32
  hwUserlogAccessTotalPackets Counter32
  hwUserlogAccessFailedEntries Counter32
  hwUserlogAccessFailedPackets Counter32
  hwUserlogAccessClearRunStat Integer32

Defined Values

hwUserLogMIB 1.3.6.1.4.1.2011.5.25.18
The HUAWEI-USERLOG-MIB contains objects to manage configuration and monitor running state for userlog feature. For users who access network through NAT and BAS equipments, their IP addresses are generally unfixed, and so it is hard to exactly locate which host a certain access comes from and which user initiates it. This decreases the network security. User log is designed to solve the problem. User log can record Network Address Translation (NAT) flow information, and login/ logout information and flow information of Broadband Access Server (BAS) user, thus enabling the administrator know address information before NAT, access record of BAS user, etc. Then, network activities and operations can be queried and tracked, and network availability and security are improved accordingly.
MODULE-IDENTITY    

hwUserlogObjects 1.3.6.1.4.1.2011.5.25.18.1
OBJECT IDENTIFIER    

hwUserlogNatObjects 1.3.6.1.4.1.2011.5.25.18.1.1
OBJECT IDENTIFIER    

hwUserlogNatVersion 1.3.6.1.4.1.2011.5.25.18.1.1.1
NAT LOG version. Currently only version 1 is developed.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwUserlogNatSyslog 1.3.6.1.4.1.2011.5.25.18.1.1.2
NAT LOG format. If 1, LOG format is sysLog. If 0, LOG format is UDP packet. UDP packet is the default format and is recommended. Syslog can be used in the case that log amount is not too large.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNatSourceIP 1.3.6.1.4.1.2011.5.25.18.1.1.3
The Source IP address of NAT LOG UDP packet. By default, the source IP address of the UDP packet is the IP address of the interface through which the router outputs the user log packet. On the user log server side, the source of log information can be located rapidly through identifying the source IP address of the log. You are recommended to configure a loopback address or router ID to function as the source IP address of the UDP packet.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogNatFlowBegin 1.3.6.1.4.1.2011.5.25.18.1.1.4
Log the NAT flow when it is created. If 1, this function is enabled. If 0, this function is disabled. This function will be used when real-time monitor is required. The default value 0 means this function is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNatActiveTime 1.3.6.1.4.1.2011.5.25.18.1.1.5
The active time for long-time existed NAT flow. Unit: minute. Range: 10 minutes ~ 120 minutes. When setting it, NAT flow can be logged after an interval of active time. This function will be used when real-time monitor is required. The default value 0 means real-time monitor function is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNatSlotCfgInfoTable 1.3.6.1.4.1.2011.5.25.18.1.1.6
A table of NAT LOG configuration information for the specified slot. By default, user log function is disabled on the interface board. Only after user log function is enabled, the other configurations related to user log take effect.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogNatSlotCfgInfoEntry

hwUserlogNatSlotCfgInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.1.6.1
NAT LOG configuration information entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogNatSlotCfgInfoEntry  

hwUserlogNatCfgSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.1.6.1.1
Slot number. The object specifies which slot is configured with NAT LOG. For NAT LOG, it is the slot of the egress interface configured with NAT.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogNatEnable 1.3.6.1.4.1.2011.5.25.18.1.1.6.1.2
The NAT LOG feature status. If 1, NAT LOG is enabled. If 0, NAT LOG is disabled. The default value 0 means NAT LOG is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNatAclNumber 1.3.6.1.4.1.2011.5.25.18.1.1.6.1.3
Access-list number. Its range is 2000 ~ 3999. The value 0 means no ACL is specified. Only when NAT LOG is enabled, and ACL is configured. Only NAT flow which match the ACL will be logged.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNatHostAddress 1.3.6.1.4.1.2011.5.25.18.1.1.6.1.4
The IP address of NAT LOG server. If user log is output in UDP packet mode, user log server must be configured and user log server address must be specified correctly. Otherwise, user log function cannot work normally. The address of the destination server must be a valid unicast address rather than a loop address or multicast address. In principle, it should be the address of the user log server that can communicate normally.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogNatUdpPort 1.3.6.1.4.1.2011.5.25.18.1.1.6.1.5
The UDP Port Number of NAT LOG server. Its range is 1 ~ 65535. In order to avoid confliction with general UDP port numbers, you are recommended to use the UDP port number above 1024.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 0..65535  

hwUserlogNatSlotRunInfoTable 1.3.6.1.4.1.2011.5.25.18.1.1.7
A table of NAT LOG running information for the specified slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogNatSlotRunInfoEntry

hwUserlogNatSlotRunInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.1.7.1
NAT LOG running information entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogNatSlotRunInfoEntry  

hwUserlogNatRunSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.1
Slot number. The object specifies on which slot the NAT LOG statistics are calculated.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogNatTotalEntries 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.2
The total number of NAT flow entries which are logged.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogNatTotalPackets 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.3
The total number of NAT LOG UDP packets generated by the device.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogNatFailedEntries 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.4
The total number of NAT flow entries failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogNatFailedPackets 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.5
The total number of NAT LOG UDP packets failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogNatClearRunStat 1.3.6.1.4.1.2011.5.25.18.1.1.7.1.6
Clears the running statistics for NAT LOG. Its access is write-only. If 1, the running statistics for NAT LOG is resetted. Other value is invalid.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowObjects 1.3.6.1.4.1.2011.5.25.18.1.2
OBJECT IDENTIFIER    

hwUserlogFlowVersion 1.3.6.1.4.1.2011.5.25.18.1.2.1
BAS FLOW LOG version. Currently only version 1 is developed.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwUserlogFlowSyslog 1.3.6.1.4.1.2011.5.25.18.1.2.2
BAS FLOW LOG format. If 1, LOG format is sysLog. If 0, LOG format is UDP packet. UDP packet is the default format, and is recommended. Syslog can be used in the case that log amount is not too large.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowSourceIP 1.3.6.1.4.1.2011.5.25.18.1.2.3
The Source IP address of BAS FLOW LOG UDP packet. By default, the source IP address of the UDP packet is the IP address of the interface through which the router outputs the user log packet. On the user log server side, the source of log information can be located rapidly through identifying the source IP address of the log. You are recommended to configure a loopback address or router ID to function as the source IP address of the UDP packet.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogFlowFlowBegin 1.3.6.1.4.1.2011.5.25.18.1.2.4
Log the BAS flow when it is created. If 1, this function is enabled. If 0, this function is disabled. This function will be used when real-time monitor is required. The default value 0 means this function is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowActiveTime 1.3.6.1.4.1.2011.5.25.18.1.2.5
The active time for long-time existed BAS flow. Its unit is minute. Its range is 10 minutes ~ 120 minutes. When setting it, BAS flow can be logged after an internal of active time. This function will be used when real-time monitor is required. The default value 0 means real-time monitor function is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowSlotCfgInfoTable 1.3.6.1.4.1.2011.5.25.18.1.2.6
A table of BAS FLOW LOG configuration information for the specified slot. By default, user log function is disabled on the interface board. Only after user log function is enabled, the other configurations related to user log take effect.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogFlowSlotCfgInfoEntry

hwUserlogFlowSlotCfgInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.2.6.1
BAS FLOW LOG configuration information entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogFlowSlotCfgInfoEntry  

hwUserlogFlowCfgSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.2.6.1.1
Slot number. The ojects specifies which slot is configured with BAS FLOW LOG.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogFlowEnable 1.3.6.1.4.1.2011.5.25.18.1.2.6.1.2
The BAS FLOW LOG feature status. If 1, BAS FLOW LOG is enabled. If 0, BAS FLOW LOG is disabled. The default value 0 means BAS FLOW LOG is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowAclNumber 1.3.6.1.4.1.2011.5.25.18.1.2.6.1.3
Access-list number. Its range is 2000 ~ 3999. The value 0 means no ACL is specified. Only when BAS FLOW LOG is enabled, the ACL be configured. Only BAS flow which match the ACL will be logged.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogFlowHostAddress 1.3.6.1.4.1.2011.5.25.18.1.2.6.1.4
The IP address of BAS FLOW LOG server. If user log is output in UDP packet mode, user log server must be configured and user log server address must be specified correctly. Otherwise, user log function cannot work normally. The address of the destination server must be a valid unicast address rather than a loop address or multicast address. In principle, it should be the address of the user log server that can communicate normally.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogFlowUdpPort 1.3.6.1.4.1.2011.5.25.18.1.2.6.1.5
The UDP Port Number of BAS FLOW LOG server. Its range is 1 ~ 65535. In order to avoid confliction with general UDP port numbers, you are recommended to use the UDP port number above 1024.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 0..65535  

hwUserlogFlowSlotRunInfoTable 1.3.6.1.4.1.2011.5.25.18.1.2.7
A table of BAS FLOW LOG running information for the specified slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogFlowSlotRunInfoEntry

hwUserlogFlowSlotRunInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.2.7.1
Running Information Entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogFlowSlotRunInfoEntry  

hwUserlogFlowRunSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.1
Slot number. The object specifies on which slot the BAS FLOW LOG statistics are calculated.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogFlowTotalEntries 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.2
The total number of BAS FLOW Entries which are logged.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogFlowTotalPackets 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.3
The total number of FLOW LOG UDP packet generated by the device.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogFlowFailedEntries 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.4
The total number of BAS FLOW entries failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogFlowFailedPackets 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.5
The total number of BAS FLOW LOG UDP packet failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogFlowClearRunStat 1.3.6.1.4.1.2011.5.25.18.1.2.7.1.6
Clears the running statistics for FLOW LOG. Its access is write-only. If 1, the running statistics for FLOW LOG is resetted. Other value is invalid.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogAccessObjects 1.3.6.1.4.1.2011.5.25.18.1.3
OBJECT IDENTIFIER    

hwUserlogAccessVersion 1.3.6.1.4.1.2011.5.25.18.1.3.1
BAS ACCESS LOG version. Currently only version 1 is developed.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32  

hwUserlogAccessSyslog 1.3.6.1.4.1.2011.5.25.18.1.3.2
BAS ACCESS LOG format. If 1, LOG format is sysLog; If 0, LOG format is UDP packet. UDP packet is the default format, and is recommended. Syslog can be used in the case that log amount is not too large.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogAccessSourceIP 1.3.6.1.4.1.2011.5.25.18.1.3.3
The Source IP address of BAS ACCESS LOG UDP packet. By default, the source IP address of the UDP packet is the IP address of the interface through which the router outputs the user log packet. On the user log server side, the source of log information can be located rapidly through identifying the source IP address of the log. You are recommended to configure a loopback address or router ID to function as the source IP address of the UDP packet.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogAccessSlotCfgInfoTable 1.3.6.1.4.1.2011.5.25.18.1.3.4
A table of BAS ACCESS LOG configuration information for the specified slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogAccessSlotCfgInfoEntry

hwUserlogAccessSlotCfgInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.3.4.1
BAS ACCESS LOG configuration information entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogAccessSlotCfgInfoEntry  

hwUserlogAccessCfgSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.3.4.1.1
Slot number. The object specifies which slot is configured with BAS ACCESS LOG.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogAccessEnable 1.3.6.1.4.1.2011.5.25.18.1.3.4.1.2
The BAS ACCESS LOG feature status. If 1, BAS ACCESS LOG is enabled. If 0, BAS ACCESS LOG is disabled. The default value 0 means BAS ACCESS LOG is disabled.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogAccessHostAddress 1.3.6.1.4.1.2011.5.25.18.1.3.4.1.3
The IP address of BAS ACCESS LOG server. If user log is output in UDP packet mode, user log server must be configured and user log server address must be specified correctly. Otherwise, user log function cannot work normally. The address of the destination server must be a valid unicast address rather than a loop address or multicast address. In principle, it should be the address of the user log server that can communicate normally.
Status: current Access: read-write
OBJECT-TYPE    
  IpAddress  

hwUserlogAccessUdpPort 1.3.6.1.4.1.2011.5.25.18.1.3.4.1.4
The UDP Port Number of BAS ACCESS LOG server. Its range is 1 ~ 65535. In order to avoid confliction with general UDP port numbers, you are recommended to use the UDP port number above 1024.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32 0..65535  

hwUserlogAccessSlotRunInfoTable 1.3.6.1.4.1.2011.5.25.18.1.3.5
A table of BAS ACCESS LOG running information for the specified slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    HwUserlogAccessSlotRunInfoEntry

hwUserlogAccessSlotRunInfoEntry 1.3.6.1.4.1.2011.5.25.18.1.3.5.1
Running Information Entry for a slot.
Status: current Access: not-accessible
OBJECT-TYPE    
  HwUserlogAccessSlotRunInfoEntry  

hwUserlogAccessRunSlotNumber 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.1
Slot number. The object specifies on which slot the BAS ACCESS LOG statistics are calculated.
Status: current Access: read-only
OBJECT-TYPE    
  Integer32 0..15  

hwUserlogAccessTotalEntries 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.2
The total number of BAS ACCESS records which are logged.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogAccessTotalPackets 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.3
The total number of ACCESS LOG UDP packet generated by the router.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogAccessFailedEntries 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.4
The total number of BAS ACCESS entries failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogAccessFailedPackets 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.5
The total number of BAS ACCESS LOG UDP packet failed in outputting.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

hwUserlogAccessClearRunStat 1.3.6.1.4.1.2011.5.25.18.1.3.5.1.6
Clear the running statistics for ACCESS LOG. Its access is write-only. If 1, the running statistics for ACCESS LOG is resetted, the other value is invalid.
Status: current Access: read-write
OBJECT-TYPE    
  Integer32  

hwUserlogNotifications 1.3.6.1.4.1.2011.5.25.18.2
OBJECT IDENTIFIER    

hwUserlogConformance 1.3.6.1.4.1.2011.5.25.18.3
OBJECT IDENTIFIER    

hwUserlogCompliances 1.3.6.1.4.1.2011.5.25.18.3.1
OBJECT IDENTIFIER    

hwUserlogCompliance 1.3.6.1.4.1.2011.5.25.18.3.1.1
The compliance statement for entities which implement the Huawei Userlog mib.
Status: current Access: read-write
MODULE-COMPLIANCE    

hwUserlogGroups 1.3.6.1.4.1.2011.5.25.18.3.2
OBJECT IDENTIFIER    

hwUserlogMandatoryGroup 1.3.6.1.4.1.2011.5.25.18.3.2.1
A collection of objects providing mandatory Userlog information.
Status: current Access: read-write
OBJECT-GROUP    

hwUserlogConfigGroup 1.3.6.1.4.1.2011.5.25.18.3.2.2
All configurable parameters of Userlog feature.
Status: current Access: read-write
OBJECT-GROUP    

hwUserlogInfoGroup 1.3.6.1.4.1.2011.5.25.18.3.2.3
All running information of Userlog feature.
Status: current Access: read-write
OBJECT-GROUP