SUPERMICRO-DHCPv6-SERVER-MIB Table View

The Configuration Pool Table. Each row in the table represents a 
different Configured Pool. The DHCPv6 server can provide those configuration
parameters that do not require the server to maintain any dynamic state for
individual clients, such as DNS server addresses and domain search list
options. 
          
A DHCPv6 configuration information pool is a named entity that includes
information about available configuration parameters and policies that control
assignment of the parameters to clients from the pool. A pool is configured
independently of the DHCPv6 service. 
          
Each Row of the fsDhcp6SrvOptionTable contains the configuration 
information configured by user. 
Rows of the fsDhcp6SrvOptionTable are  mapped using fsDhcp6SrvPoolIndex.
          
Each configuration pool Row can be mapped to either Interface table or the
client table.

This table contains the list of link prefixes which are to be used by
the server to map an information-request/relay-forward message to a pool. 
          
When an address on the incoming interface or a link-address in the
packet matches the specified IPv6-prefix, the server uses the
configuration information pool.

This table contains the global  options that are
to be used by the server to respond to a DHCP
information-request message.
Following are valid options user can configure:- 
1 Vendor-specific Information with type fsDhcp6SrvOptionType 17
2 SIP server domain name list with type fsDhcp6SrvOptionType 21
3 SIP server IPV6 address list with type fsDhcp6SrvOptionType 22
4 DNS recursive name server with type fsDhcp6SrvOptionType 23
5 Domain search list with type fsDhcp6SrvOptionType 24
6 Information refresh timer fsDhcp6SrvOptionType 32
option table row can not be created until row status of pool table with
same fsDhcp6SrvPoolIndex becomes active.
                 
Row status with ffsDhcp6SrvPoolIndex becomes not in service when row 
status of fsDhcp6SrvPoolTable with the same index becomes 
Not in service.

This table contains the vendor specific options which the server
will reply in response to a information-request or relay-forward
message.
This table will contain the various sub-option associated with
a specific option

This table contains the statistics of DHCPv6 Server on each 
interface. It will give the Number of Information Request messages, Relay
Forward messages received on the interface and Number of Relay reply,
reply messages transmitted from the interface.
          
This table also contains the per interface configuration column 
fsDhcp6SrvIfPool contains the pool id associated with the interface.

Server authenticate the received information request with 
HMAC MD5 algorithm when received message contains the 
Authentication option tlv .Realms are container for 
authentication information. For the Authentication key id is required.
Keys are assigned to clients. This table is used to create 
the Realm Row and the fsDhcp6SrvRealmIndex index is also used
by the fsDhcp6SrvAuthClntTable. Following is an example
of a server authentication hierarchy:
          
realm testrealm01.private.com 
{
   key 1 TESTREALMKEY01
   key 2 TESTREALMKEY02
}
realm testrealm02.private.com 
{
   key 1 TESTREALMKEY01
}

The server and client have a shared key. When one wants to send a
message to another, the source creates a digest value by using the
shared key and the message contents as inputs to a keyed hashing
function (MD5 by default). The source then includes the digest value in
the authentication option. When the message arrives at the destination,
the destination searches for the shared key and generates the digest
value itself. If the digest value in the authentication option of the
message matches the digest value generated by the destination, then the
message is secure and comes from a trusted source.
          
This table is used to define containers for keys to be used for a 
single client.

This table is used to define the various keys used for authentication 
the information-request.