Switch provisioning & DHCP suboptions on OS6900-X72
Posted: 21 Feb 2024 18:43
I’m currently working on setting up switch provisioning in OmniVista, and one of the required steps is as follows:
DHCP/DNS Configuration
To enable switches to contact the OmniVista Server and receive the Provisioning configuration, you must first set up your DHCP Server to point to the local OmniVista Server as the Activation Server for provisioning. You must also setup DNS to resolve to point to your local OmniVista Server.
DHCP Configuration
Option 43
Sub-Option 1 - Vendor ID. Validate the DHCP response (must be set with the value alenterprise). This sub-option is only required if you specify any of the sub-options listed below, or any devices on your network are running AOS 6.7.2 R03.
Sub-Option 128 - Activation Server FQDN. Set to as-lite.myovcloud.net.
Sub-Option 134 - Activation Server Port. The port number on the Activation Server to which the switches should communicate. By default, the switches communicate to Activation Server port 443. This sub-option is only supported on AOS 6.7.2R07 (and higher) and AOS 8.6R2 (and higher).
DNS Configuration
Configure your DNS server to resolve as-lite.myovcloud.net to point to your local OmniVista Server.
My question is how do I configure DHCP sub-options for option 43? I have:
subnet 192.168.1.0 netmask 255.255.255.0 {
dynamic-dhcp range 192.168.1.200 192.168.1.210 {
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.24.10;
option dhcp-lease-time 900;
option 43 ????????;
}
}
I found on post on here suggesting I add:
#Sub-Option 1 “alenterprise” in Hex = 010c616c656e7465727072697365
0x01 = number of suboption
0x0c is the length o the following entry (alenterprise) => Length 12=0x0c
#Sub-Option 128 “as-lite.myovcloud.net” in Hex = 801561732d6c6974652e6d796f76636c6f75642e6e6574
subopt. 128 = 0x80
Length 21=0x15
So would my final result be:
subnet 192.168.1.0 netmask 255.255.255.0 {
dynamic-dhcp range 192.168.1.200 192.168.1.210 {
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.24.10;
option dhcp-lease-time 900;
option 43 192.168.0.11;
option vivso 80:15:61:73:2d:6c:69:74:65:2e:6d:79:6f:76:63:6c:6f:75:64:2e:6e:65:74;
option vivso 01:0c:61:6c:65:6e:74:65:72:70:72:69:73:65;
}
}
Any help is greatly appreciated.
DHCP/DNS Configuration
To enable switches to contact the OmniVista Server and receive the Provisioning configuration, you must first set up your DHCP Server to point to the local OmniVista Server as the Activation Server for provisioning. You must also setup DNS to resolve to point to your local OmniVista Server.
DHCP Configuration
Option 43
Sub-Option 1 - Vendor ID. Validate the DHCP response (must be set with the value alenterprise). This sub-option is only required if you specify any of the sub-options listed below, or any devices on your network are running AOS 6.7.2 R03.
Sub-Option 128 - Activation Server FQDN. Set to as-lite.myovcloud.net.
Sub-Option 134 - Activation Server Port. The port number on the Activation Server to which the switches should communicate. By default, the switches communicate to Activation Server port 443. This sub-option is only supported on AOS 6.7.2R07 (and higher) and AOS 8.6R2 (and higher).
DNS Configuration
Configure your DNS server to resolve as-lite.myovcloud.net to point to your local OmniVista Server.
My question is how do I configure DHCP sub-options for option 43? I have:
subnet 192.168.1.0 netmask 255.255.255.0 {
dynamic-dhcp range 192.168.1.200 192.168.1.210 {
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.24.10;
option dhcp-lease-time 900;
option 43 ????????;
}
}
I found on post on here suggesting I add:
#Sub-Option 1 “alenterprise” in Hex = 010c616c656e7465727072697365
0x01 = number of suboption
0x0c is the length o the following entry (alenterprise) => Length 12=0x0c
#Sub-Option 128 “as-lite.myovcloud.net” in Hex = 801561732d6c6974652e6d796f76636c6f75642e6e6574
subopt. 128 = 0x80
Length 21=0x15
So would my final result be:
subnet 192.168.1.0 netmask 255.255.255.0 {
dynamic-dhcp range 192.168.1.200 192.168.1.210 {
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option domain-name-servers 192.168.24.10;
option dhcp-lease-time 900;
option 43 192.168.0.11;
option vivso 80:15:61:73:2d:6c:69:74:65:2e:6d:79:6f:76:63:6c:6f:75:64:2e:6e:65:74;
option vivso 01:0c:61:6c:65:6e:74:65:72:70:72:69:73:65;
}
}
Any help is greatly appreciated.