DHCP services can be configured on many platforms. So here we will mainly explain how to use option 43 on the Linux DHCP server to implement the H3C AP to automatically contact the AC for registration. The original DHCP Server was deployed on the switch, but the DHCP Server should be migrated because it is ready to change the network topology recently. The operating system uses RHEL5.3 and DHCP version 3.05.
Call H3C 800. The second-line engineer said that the DHCP configuration in Linux has not been used. I want to see the document, which contains the configuration instances for dhcp server and windows dhcp server, I also sent an example of how to issue option 43 to cisco AP in Linux. I want to compare and modify it,
Cisco Configuration
Option serverip code 43 = ip-address; then define option serverip x. x in subnet; but the test fails.
No way. Read the document and find that the H3C document uses hexadecimal data. It is completely different from the configuration document provided by the second-line technical support that is defined as an IP address. The following is the H3C configuration on the built-in DHCP of the switch.
Hex indicates the hexadecimal format, 80 indicates the option Type, and 0B indicates the option length. It indicates the length of the subsequent content, 0000 indicates the Server Type, fixed as the limit, and 02 indicates the number of IP addresses of the following AC, 12010701 and 12010702 are the hexadecimal IP addresses of the Two AC respectively, that is, you only need to set your own AC address X. x. x. convert X to hexadecimal format and replace it.
Next, check the document on the Linux DHCP server and find
- option new-name code new-code = string ;
-
- An option whose type is a data string is essentially just a collection
- of bytes, and can be specified either as quoted text, like the text
- type, or as a list of hexadecimal contents separated by colons whose
- values must be between 0 and FF. For example:
-
- option sql-identification-token code 195 = string;
- option sql-identification-token 17:23:19:a6:42:ea:99:7c:22;
Modify the configuration in dhcpd. conf.
- option serverip code 43 = string;
-
- #office,wireless AP
- subnet 10.20.3.0 netmask 255.255.255.0 {
- option routers 10.20.3.1;
- option subnet-mask 255.255.255.0;
- option serverip 80:0B:00:00:01:0B:45:13:01:0B:45:14;
- pool {
- failover peer "dhcp-failover";
- range 10.20.3.120 10.20.3.254;
- deny dynamic bootp clients;
- }
- }
After testing, the AP in the Linux DHCP server can be successfully registered on the AC. In case of problems, you have to carefully check the configuration and documentation. The problem will still be solved as long as you find the direction.