ATDHCP-MIB

File: ATDHCP-MIB.mib (9563 bytes)

Imported modules

RFC1155-SMI RFC1213-MIB RFC-1215
RFC-1212 ATSWTCH2-MIB

Imported symbols

enterprises Counter IpAddress
TimeTicks DisplayString TRAP-TYPE
OBJECT-TYPE alliedTelesyn atiProduct
mibObject atswitchMib

Defined Types

MacAddress  
OCTET STRING Size(6)    

BridgeId  
OCTET STRING Size(8)    

Timeout  
INTEGER    

Defined Values

atswitchDHCPGroup 1.3.6.1.4.1.207.8.10.11
OBJECT IDENTIFIER    

atswitchDHCPSysGroup 1.3.6.1.4.1.207.8.10.11.1
OBJECT IDENTIFIER    

atswitchDHCPTimerGroup 1.3.6.1.4.1.207.8.10.11.2
OBJECT IDENTIFIER    

atswitchDHCPCurrentDHCPClientAddress 1.3.6.1.4.1.207.8.10.11.1.1
Current IP address of the client. To start with,it might be null . This is filled by the server when sending a DHCPOFFER and the client uses the most comfortable offer from offers sent by different DHCP servers. A DHCPREQUEST packet is sent with the Client address agreed upon to the selected server ( Broadcast). Server Acks back this packet which is where Client/Server moves to the Bound state. Once reached into Bound state, the client address is made the official address on the client.
OBJECT-TYPE    
  IpAddress  

atswitchDHCPSubnetMask 1.3.6.1.4.1.207.8.10.11.1.2
When the client/server reaches the BOUND state, this is one of the parameters set by the server.
OBJECT-TYPE    
  IpAddress  

atswitchDHCPCurrentRelayAgentAddress 1.3.6.1.4.1.207.8.10.11.1.3
The IP address of the DHCP relay Agent on the same subnet. Normally there will be no DHCP server on each of the subnet and this Relay Agent will act in sending server accross the subnets. There might not be any relay agent. This depends on the network Toplogy like where is the DHCP server and DHCP client.
OBJECT-TYPE    
  IpAddress  

atswitchDHCPNextDHCPServerAddress 1.3.6.1.4.1.207.8.10.11.1.4
The IP address of the next DHCP server to be used during bootstrap. This address is sent by the DHCP server in the messages DHCPOFFER, DHCPACK,DHCPNACK.
OBJECT-TYPE    
  IpAddress  

atswitchDHCPLeaseTimer 1.3.6.1.4.1.207.8.10.11.2.1
When the client/server reaches the BOUND state, this is one of the parameters set by the server. The lease time period in seconds for the DHCP client for using IP address on lease from the server. At the end of 50% of this timer a renewal request is sent by the client . This is the next Object atswitchDHCPRenewalTimer.
OBJECT-TYPE    
  TimeTicks  

atswitchDHCPReacquisitionTimer 1.3.6.1.4.1.207.8.10.11.2.2
When the client/server reaches the BOUND state, this is one of the parameters set by the server. Mentioned in RFC2131 4.4.5 as T1, this renewal time period in secs for the DHCP client is for using IP address on lease from the server Once the Reacquisition Timer period in secs afetr the lease period is reached, the client sends a DHCPREQUEST to the DHCP server reque- -sting for renewal of the lease. Default would be 50% of the Lease timer which is represeneted by the above object. The client moves from BOUND to RENEW state once the DHCPREQUEST is sent after time T1 secs is passed from the start of to release time. T1 is always less than T2 ( see below for 'T2') which is lesss than the lease Timer period.
OBJECT-TYPE    
  TimeTicks  

atswitchDHCPExpirationTimer 1.3.6.1.4.1.207.8.10.11.2.3
When the client/server reaches the BOUND state, this is one of the parameters set by the server. Mentioned in RFC2131 4.4.5 as T2,this Expiration time period in secs is the time period in secs during which DHCP has gone through the BOUND->RENEWAL state. After T1 secs and when the state machine reaches T2 secs, ( T1 < T2 < lease period), DHCP client sends another DHCPREQUEST to the server asking the server to renew the lease for the IP parameters. By default it would be 87.5% of the Lease timer .If there is DHCPACK then the DHCP client moves from REBIND to BOUND. Else it moves to INIT state where it starts all over again sending a request for DHCPDISCOVER.
OBJECT-TYPE    
  TimeTicks