Confidential

DHCP Option 82 Feature Testing Plan

Confidential

Table of Contents

DHCP_Option82_Conf_001Verify that the Relay Agent Info can be enabled and disabled

DHCP_Option82_Flash_001Modify Relay Agent Info from default and verify that the diff shows correct information

DHCP_Option82_Flash_002Modify Relay Agent Info from default and verify that revert will clear the pending configuration

DHCP_Option82_Flash_003Modify Relay Agent Info from default and verify that applying will modify all items in the running configuration

DHCP_Option82_Flash_004

Modify Relay Agent Info from default, apply and verify that revert apply will set all items to the saved configuration

DHCP_Option82_Flash_005Modify Relay Agent Info from default and verify that saving will modify all items in the saved configuration

DHCP_Option82_Flash_006Modify Relay Agent Info from default, save, and verify that the information is retained through a hot-remove/insert

DHCP_Option82_Flash_007Modify Relay Agent Info from default, save, and verify that the information is retained through a soft reset

DHCP_Option82_Info_001Verify that the current configuration can be displayed correctly in the bootp menu

DHCP_Option82_Info_002Verify that the Layer 3 information menu displays correct information about the running state of the feature

DHCP_Option82_Functional_001Verify that Relay Agent Info becomes active when enabled in the configuration

DHCP_Option82_Functional_002Verify that Relay Agent Info becomes inactive when disabled in the configuration

DHCP_Option82_Functional_003Verify that Relay Agent Info-enabled DHCP packets are modified correctly by the DUT

DHCP_Option82_Functional_004Verify that DHCP requests are relayed with the correct Relay Agent Info to the primary server

DHCP_Option82_Functional_005Verify that DHCP requests are relayed with the correct Relay Agent Info to the secondary server

DHCP_Option82_Functional_006Verify that DHCP requests are relayed to the primary server with Relay Agent Info disabled

DHCP_Option82_Functional_007Verify that DHCP requests are relayed to the secondary server with Relay Agent Info disabled

DHCP_Option82_Functional_008Verify that Relay Agent Info is correct when requests are relayed from external ports

DHCP_Option82_Functional_009Verify that Relay Agent Info is correct when relaying multiple client requests from ports on both GEA units

DHCP_Option82_Functional_010 Verify that Relay Agent Info is correct when relaying a

2

Confidential

request on one GEA unit's ports to a server on another GEA unit's ports

DHCP_Option82_Functional_011Verify that Relay Agent Info is correct when Chassis S/N is changed after initial lease

DHCP_Option82_Compat_001 Verify that DHCPD sees the chassis ID as agent.circuit-id

DHCP_Option82_Compat_002Verify that DHCPD sees the port number as agent.remote-id

DHCP_Option82_Compat_003Verify that the Windows DHCP service sees the chassis ID as agent.circuit-id

DHCP_Option82_Compat_004Verify that the Windows DHCP service sees the port number as agent.remote-id

DHCP_Option82_Compat_005Verify that Option 82 information is inserted when relaying requests from Windows DHCP clients

DHCP_Option82_Compat_006Verify that Option 82 information is inserted when relaying requests from Linux DHCP clients

Section A – Repeat tests using AOS / ISCLI / BBI / SNMP

Case ID DHCP_Option82_Conf_001Purpose Verify that the Relay Agent Info can be enabled and disabled.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent command. Enable Relay Agent Info. Apply Check config. Disable the agent.

Expected Results Command should successfully enable and disable the DHCP relay agent.

TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_001Purpose Modify Relay Agent Info from default and verify that the diff

shows correct information.SupportsAssertionProcedure Connect to the DUT using AOS, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info without applying

3

Confidential

Use the diff command to see pending changes.Expected Results All configuration changes should be listed as pending.Tips N/A for ISCLIExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_002Purpose Modify Relay Agent Info from default and verify that revert will

clear the pending configuration.SupportsAssertionProcedure Connect to the DUT using AOS, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info without applying Use the diff command to see pending changes. Revert Use the diff command to see that pending changes are

removed.Expected Results All pending configuration changes should be removed.Tips N/A for ISCLIExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_003Purpose Modify Relay Agent Info from default and verify that applying will

modify items in the running configuration.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Use the diff command to see pending changes. Apply Check config to see last changes took affect.

Expected Results All configurations should be applied in the config and diff should be clear.

TipsExpected TimeTools Needed 1xDUT, 1xClient

4

Confidential

Case ID DHCP_Option82_Flash_004Purpose Modify Relay Agent Info from default, apply and verify that revert

apply will set all items to the saved configuration.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Use the diff command to see pending changes. Apply Check config to see changes took affect. Revert apply Check config to see last changes removed.

Expected Results All changes from the last apply should be removed from the config.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_005Purpose Modify Relay Agent Info from default and verify that saving will

modify all items in the saved configuration.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Use the diff command to see pending changes. Apply Check config to see changes took affect. Save Check config to see changes are saved.

Expected Results All configuration changes should be saved with no errors.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_006Purpose Modify Relay Agent Info from default, save, and verify that the

information is retained through a hot-remove/insert.SupportsAssertion

5

Confidential

Procedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP Locate the DHCP relay agent commands. Enable Relay Agent Info. Use the diff command to see pending changes. Apply Check config to see changes took affect. Save Pull the switch module from the chassis. Insert the switch module into the chassis. After booting is complete, check config.

Expected Results All configuration changes should be saved and running.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Flash_007Purpose Modify Relay Agent Info from default, save, and verify that the

information is retained through a soft reset.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Use the diff command to see pending changes. Apply Check config to see changes took affect. Save Reset the switch After booting is complete, check config.

Expected Results All configuration changes should be saved and running.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Info_001Purpose Verify that the current configuration can be displayed correctly in

the bootp menu.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info.

6

Confidential

Apply While in the bootp menu, type ‘cur’.

Expected Results All current values should be displayed and accurate.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Info_002Purpose Verify that the Layer 3 information menu displays correct

information about the running state of the feature.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Apply Check the Layer 3 information. Assure the DHCP relay agent information is present.

Expected Results Information about the DHCP relay agent should be displayed and accurate.

TipsExpected TimeTools Needed 1xDUT, 1xClient

Section B - Perform each test once

Case ID DHCP_Option82_Functional_001Purpose Verify that Relay Agent Info becomes active when enabled in the

configuration.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Apply Use a sniffer to capture packets. Verify that DHCP Opt 82 Info is present in DHCP requests

when the feature is enabled.Expected Results Relay agent should become enabled and start modifying packets

sent to DHCP server.TipsExpected Time

7

Confidential

Tools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_002Purpose Verify that Relay Agent Info becomes inactive when disabled in the

configuration.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Disable Relay Agent Info. Apply Use a sniffer to capture packets. Verify that DHCP Opt 82 Info is not present in DHCP

requests when the feature is disabled.Expected Results Relay agent should remain enabled and stop modifying DHCP

packets.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_003Purpose Verify that Relay Agent Info-enabled DHCP packets are modified

correctly by the DUT.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent. Apply Use a sniffer to capture DHCP relayed packets. Verify that DHCP Opt 82 Info is present and correct in

DHCP requests.Expected Results Packets should contain the correct relay agent information in DHCP

packets.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_004

8

Confidential

Purpose Verify that DHCP requests are relayed with the correct Relay Agent Info to the primary server.

SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary server. Apply Use a sniffer to capture DHCP relayed packets. Check packets for relay information. Verify that packets have correct information and a

destination address of the primary serverExpected Results Packets should contain the relay agent information and have the IP

destination of the primary server.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_005Purpose Verify that DHCP requests are relayed with the correct Relay Agent

Info to the secondary server.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Apply Remove connectivity from the primary server. Use a sniffer to capture DHCP relayed packets. Check packets for relay information. Verify that packets have correct information and a

destination address of the secondary server.Expected Results Packets should contain the relay agent information and have the IP

destination of the secondary server.TipsExpected TimeTools Needed 1xDUT, 1xClient

9

Confidential

Case ID DHCP_Option82_Functional_006Purpose Verify that DHCP requests are relayed to the primary server with

Relay Agent Info disabled.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Disable Relay Agent Info. Apply Use a sniffer to capture packets. Check DHCP request packets for IP information. Verify that packets are relayed correctly to the primary

server and that they do not contain chassis/port informationExpected Results DHCP request should be sent to the primary server with no agent

info added.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_007Purpose Verify that DHCP requests are relayed to the secondary server with

Relay Agent Info disabled.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Disable Relay Agent Info. Apply Remove connectivity from primary server. Use a sniffer to capture packets. Check DHCP request packets for IP information. Verify that packets are relayed correctly to the secondary

server and that they do not contain chassis/port informationExpected Results DHCP request should be sent to the secondary server with no agent

info added.TipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_008Purpose Verify that Relay Agent Info is correct when requests are relayed

from external portsSupports

10

Confidential

AssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Configure the DUT as a BOOTP relay agent with Option 82 information enabled

Connect a DHCP server to the DUT Connect a DHCP client to an external port Using a protocol analyzer, capture packets on the network

segment that contains the DHCP server Verify that Option 82 information is inserted correctly

Expected Results Relay Agent Info should be added to DHCP requests originating from external ports

TipsExpected TimeTools Needed 1xDUT, 1xClient, 1xProtocol Analyzer

Case ID DHCP_Option82_Functional_009Purpose Verify that Relay Agent Info is correct when relaying multiple

client requests from ports on both GEA unitsSupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Configure the DUT as a BOOTP relay agent with Option 82 information enabled

Connect a DHCP server to the DUT Using /info/geaport, note which internal ports use different

GEAs Connect two or more clients to internal ports on GEA unit 0 Connect two or more clients to internal ports on GEA unit 2 Configure DHCP server with pools that will assign

addresses based on originating port Perform DHCP requests from all clients Verify that multiple client requests have the correct option

82 information addedExpected Results DHCP requests should have correct info on each portTipsExpected TimeTools Needed 1xDUT, 1xClient

Case ID DHCP_Option82_Functional_010Purpose Verify that Relay Agent Info is correct when relaying a request on

one GEA unit's ports to a server on another GEA unit's portsSupports

11

Confidential

AssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Configure the DUT as a BOOTP relay agent with Option 82 information enabled

Using /info/geaport, note which ports use different GEAs Connect a DHCP server to the DUT and note which GEA

controls the port Connect a client to a port on the other GEA unit (do not use

ports on the same GEA unit as the server) Using a protocol analyzer, capture packets on the network

segment that contains the DHCP server Verify that Option 82 information is inserted correctly

Expected Results Relay Agent Information should be added correctly when relaying requests across ports with different controlling GEA units

TipsExpected TimeTools Needed 1xDUT, 1xClient, 1xProtocol Analyzer

Case ID DHCP_Option82_Functional_011Purpose Verify that Relay Agent Info is correct when Chassis S/N is

changed after initial leaseSupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Configure the DUT as a BOOTP relay agent with Option 82 information enabled

Connect a DHCP server to the DUT Connect a DHCP client to the DUT Using a protocol analyzer, capture packets on the network

segment that contains the DHCP server Verify that the initial DHCP request has the correct Option

82 information added Change the Chassis S/N over a serial connection to the

backplane Verify that the next DHCP request uses the new information

Expected Results Relay agent info should be modified when the Chassis S/N is changed

TipsExpected TimeTools Needed 1xDUT, 1xClient, 1xProtocol Analyzer

12

Confidential

Case ID DHCP_Option82_Compat_001Purpose Verify that DHCPD sees the chassis ID as agent.circuit-id.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Configure the chassis ID to “BladeSwitching” Apply Configure an address on the DHCPD server to match if

option agent.circuit-id = 42:6C:61:64:65:53:77:69:74:63:68:69:6E:67:0:0

Verify that DHCP sees the information correctly and assigns the address

Expected Results DHCPD on the server should see the ID in agent.circuit-id format.Tips ID will be in HEX mode.Expected TimeTools Needed 1xDUT, 1xClient, 1xDHCPD Server, 1xBlade Server

Case ID DHCP_Option82_Compat_002Purpose Verify that DHCPD sees the port number as agent.remote-id.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Insert the Blade Server in the chassis so that it links up to

port 1 of the DUT Apply Configure an address on the DHCPD server to match if

option agent.remote-id = 0:0:0:01 Verify that DHCP sees the information correctly and assigns

the addressExpected Results DHCPD on the server should see the port number in agent.remote-

id format.Tips ID will be in HEX mode.Expected TimeTools Needed 1xDUT, 1xClient, 1xDHCPD Server, 1xBlade Server

13

Confidential

Case ID DHCP_Option82_Compat_003Purpose Verify that the Windows DHCP service sees the chassis ID as

agent.circuit-idSupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Insert the Blade Server in the chassis so that it links up to

port 1 of the DUT Apply Configure an address on the Windows DHCP server to

match if option agent.remote-id = 0:0:0:01 Verify that DHCP sees the information correctly and assigns

the addressExpected Results The DHCP service on the server should see the port number in

agent.remote-id format.TipsExpected TimeTools Needed 1xDUT, 1xClient, 1xWindows DHCP Server, 1xBlade Server

Case ID DHCP_Option82_Compat_004Purpose Verify that the Windows DHCP service sees the port number as

agent.remote-id.SupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Insert the Blade Server in the chassis so that it links up to

port 1 of the DUT Apply Configure an address on the Windows DHCP server to

match if option agent.remote-id = 0:0:0:01 Verify that DHCP sees the information correctly and assigns

the addressExpected Results The DHCP service on the server should see the port number in

agent.remote-id format.Tips ID will be in HEX mode.Expected Time

14

Confidential

Tools Needed 1xDUT, 1xClient, 1xWindows DHCP Server, 1xBlade Server

Case ID DHCP_Option82_Compat_005Purpose Verify that Option 82 information is inserted when relaying

requests from Windows DHCP clientsSupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Insert a Windows-based Blade Server in the chassis so that

it links up to a port on the DUT Apply Configure an address on the DHCP server to match both

Option 82 sub-options Verify that DHCP sees the information correctly and assigns

the addressExpected Results Option 82 information should be correctly inserted into requests

from Windows clientsTipsExpected TimeTools Needed 1xDUT, 1xClient, 1xDHCP Server, 1xBlade Server

Case ID DHCP_Option82_Compat_006Purpose Verify that Option 82 information is inserted when relaying

requests from Linux DHCP clientsSupportsAssertionProcedure Connect to the DUT using AOS, ISCLI, BBI, or SNMP

Locate the DHCP relay agent commands. Enable Relay Agent Info. Modify the information for the relay agent including an IP

address for the primary and secondary servers. Insert a Linux-based Blade Server in the chassis so that it

links up to a port on the DUT Apply Configure an address on the DHCP server to match both

Option 82 sub-options Verify that DHCP sees the information correctly and assigns

the address

15

Confidential

Expected Results Option 82 information should be correctly inserted into requests from Linux clients

TipsExpected TimeTools Needed 1xDUT, 1xClient, 1xDHCP Server, 1xBlade Server

16