DHCP Option 82 Feature Testing Plan: Confidential

Confidential
DHCP Option 82 Feature Testing Plan

Confidential
Table of Contents
Verify that the Relay Agent Info can be enabled and

DHCP_Option82_Conf_001 disabled
Modify Relay Agent Info from default and verify that the
DHCP_Option82_Flash_001 diff shows correct information
Modify Relay Agent Info from default and verify that
DHCP_Option82_Flash_002 revert will clear the pending configuration
DHCP_Option82_Flash_003 applying will modify all items in the running configuration
Modify Relay Agent Info from default, apply and verify
that revert apply will set all items to the saved
DHCP_Option82_Flash_004 configuration
DHCP_Option82_Flash_005 saving will modify all items in the saved configuration
Modify Relay Agent Info from default, save, and verify
DHCP_Option82_Flash_006 that the information is retained through a hot-remove/insert
Modify Relay Agent Info from default, save, and verify
DHCP_Option82_Flash_007 that the information is retained through a soft reset
Verify that the current configuration can be displayed
DHCP_Option82_Info_001 correctly in the bootp menu
Verify that the Layer 3 information menu displays correct
DHCP_Option82_Info_002 information about the running state of the feature
Verify that Relay Agent Info becomes active when enabled
DHCP_Option82_Functional_001 in the configuration
Verify that Relay Agent Info becomes inactive when
DHCP_Option82_Functional_002 disabled in the configuration
Verify that Relay Agent Info-enabled DHCP packets are
DHCP_Option82_Functional_003 modified correctly by the DUT
Verify that DHCP requests are relayed with the correct
DHCP_Option82_Functional_004 Relay Agent Info to the primary server
Verify that DHCP requests are relayed with the correct
DHCP_Option82_Functional_005 Relay Agent Info to the secondary server
Verify that DHCP requests are relayed to the primary
DHCP_Option82_Functional_006 server with Relay Agent Info disabled
Verify that DHCP requests are relayed to the secondary
DHCP_Option82_Functional_007 server with Relay Agent Info disabled
Verify that Relay Agent Info is correct when requests are
DHCP_Option82_Functional_008 relayed from external ports
Verify that Relay Agent Info is correct when relaying
DHCP_Option82_Functional_009 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
Verify that Relay Agent Info is correct when Chassis S/N
DHCP_Option82_Functional_011 is changed after initial lease
DHCP_Option82_Compat_001 Verify that DHCPD sees the chassis ID as agent.circuit-id
Verify that DHCPD sees the port number as agent.remote-
DHCP_Option82_Compat_002 id
Verify that the Windows DHCP service sees the chassis ID
DHCP_Option82_Compat_003 as agent.circuit-id
Verify that the Windows DHCP service sees the port
DHCP_Option82_Compat_004 number as agent.remote-id
Verify that Option 82 information is inserted when
DHCP_Option82_Compat_005 relaying requests from Windows DHCP clients
Verify that Option 82 information is inserted when
DHCP_Option82_Compat_006 relaying requests from Linux DHCP clients
Section A – Repeat tests using AOS / ISCLI / BBI / SNMP
Case ID DHCP_Option82_Conf_001
Purpose Verify that the Relay Agent Info can be enabled and disabled.
Supports
Assertion
Procedure  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.
Tips
Expected Time
Tools Needed 1xDUT, 1xClient
Case ID DHCP_Option82_Flash_001
Purpose Modify Relay Agent Info from default and verify that the diff
shows correct information.
Supports
Assertion
Procedure  Connect to the DUT using AOS, BBI, or SNMP
 Locate the DHCP relay agent commands.
3
Confidential
 Enable Relay Agent Info without applying

 Use the diff command to see pending changes.
Expected Results All configuration changes should be listed as pending.
Tips N/A for ISCLI
Expected Time
Purpose Modify Relay Agent Info from default and verify that revert will
clear the pending configuration.
Supports
Assertion
Procedure  Connect to the DUT using AOS, BBI, or SNMP
 Enable Relay Agent Info without applying
 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 ISCLI
Expected Time
Purpose Modify Relay Agent Info from default and verify that applying will
modify items in the running configuration.
Supports
Assertion
 Apply
 Check config to see last changes took affect.
Expected Results All configurations should be applied in the config and diff should
be clear.
Tips
Expected Time
4
Confidential
Purpose Modify Relay Agent Info from default, apply and verify that revert
apply will set all items to the saved configuration.
Supports
Assertion
 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.
Tips
Expected Time
Purpose Modify Relay Agent Info from default and verify that saving will
modify all items in the saved configuration.
Supports
Assertion
 Apply
 Save
 Check config to see changes are saved.
Expected Results All configuration changes should be saved with no errors.
Tips
Expected Time
Purpose Modify Relay Agent Info from default, save, and verify that the
5
Confidential
information is retained through a hot-remove/insert.

Supports
Assertion
 Apply
 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.
Tips
Expected Time
Purpose Modify Relay Agent Info from default, save, and verify that the
information is retained through a soft reset.
Supports
Assertion
 Apply
 Save
 Reset the switch
 After booting is complete, check config.
Expected Results All configuration changes should be saved and running.
Tips
Expected Time
Case ID DHCP_Option82_Info_001
Purpose Verify that the current configuration can be displayed correctly in
the bootp menu.
6
Confidential
Supports
Assertion
 Apply
 While in the bootp menu, type ‘cur’.
Expected Results All current values should be displayed and accurate.
Tips
Expected Time
Case ID DHCP_Option82_Info_002
Purpose Verify that the Layer 3 information menu displays correct
information about the running state of the feature.
Supports
Assertion
 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.
Tips
Expected Time
Section B - Perform each test once
Case ID DHCP_Option82_Functional_001
Purpose Verify that Relay Agent Info becomes active when enabled in the
configuration.
Supports
Assertion
 Apply
 Use a sniffer to capture packets.
7
Confidential
 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.
Tips
Expected Time
Purpose Verify that Relay Agent Info becomes inactive when disabled in the
configuration.
Supports
Assertion
 Disable Relay Agent Info.
 Apply
 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.
Tips
Expected Time
Purpose Verify that Relay Agent Info-enabled DHCP packets are modified
correctly by the DUT.
Supports
Assertion
 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.
8
Confidential
Tips
Expected Time
Purpose Verify that DHCP requests are relayed with the correct Relay Agent
Info to the primary server.
Supports
Assertion
 Modify the information for the relay agent including an IP
address for the primary server.
 Apply
 Check packets for relay information.
 Verify that packets have correct information and a
destination address of the primary server
Expected Results Packets should contain the relay agent information and have the IP
destination of the primary server.
Tips
Expected Time
Purpose Verify that DHCP requests are relayed with the correct Relay Agent
Info to the secondary server.
Supports
Assertion
address for the primary and secondary servers.
 Apply
 Remove connectivity from the primary server.
 Check packets for relay information.
 Verify that packets have correct information and a
destination address of the secondary server.
9
Confidential
Expected Results Packets should contain the relay agent information and have the IP
destination of the secondary server.
Tips
Expected Time
Purpose Verify that DHCP requests are relayed to the primary server with
Relay Agent Info disabled.
Supports
Assertion
 Apply
 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 information
Expected Results DHCP request should be sent to the primary server with no agent
info added.
Tips
Expected Time
Purpose Verify that DHCP requests are relayed to the secondary server with
Relay Agent Info disabled.
Supports
Assertion
 Apply
 Remove connectivity from primary server.
 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 information
Expected Results DHCP request should be sent to the secondary server with no agent
info added.
10
Confidential
Tips
Expected Time
Purpose Verify that Relay Agent Info is correct when requests are relayed
from external ports
Supports
Assertion
 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
Tips
Expected Time
Tools Needed 1xDUT, 1xClient, 1xProtocol Analyzer
Purpose Verify that Relay Agent Info is correct when relaying multiple
client requests from ports on both GEA units
Supports
Assertion
information enabled
 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 added
Expected Results DHCP requests should have correct info on each port
11
Confidential
Tips
Expected Time
Purpose 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 ports
Supports
Assertion
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)
 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
Tips
Expected Time
Purpose Verify that Relay Agent Info is correct when Chassis S/N is
changed after initial lease
Supports
Assertion
information enabled
 Connect a DHCP client to the DUT
 Verify that the initial DHCP request has the correct Option
82 information added
 Change the Chassis S/N over a serial connection to the
12
Confidential
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
Tips
Expected Time
Case ID DHCP_Option82_Compat_001
Purpose Verify that DHCPD sees the chassis ID as agent.circuit-id.
Supports
Assertion
 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 Time
Tools Needed 1xDUT, 1xClient, 1xDHCPD Server, 1xBlade Server
Purpose Verify that DHCPD sees the port number as agent.remote-id.
Supports
Assertion
 Insert the Blade Server in the chassis so that it links up to
port 1 of the DUT
13
Confidential
 Apply
 Configure an address on the DHCPD server to match if
option agent.remote-id = 0:0:0:01
the address
Expected Results DHCPD on the server should see the port number in agent.remote-
id format.
Expected Time
Tools Needed 1xDUT, 1xClient, 1xDHCPD Server, 1xBlade Server
Purpose Verify that the Windows DHCP service sees the chassis ID as
agent.circuit-id
Supports
Assertion
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
the address
Expected Results The DHCP service on the server should see the port number in
agent.remote-id format.
Tips
Expected Time
Tools Needed 1xDUT, 1xClient, 1xWindows DHCP Server, 1xBlade Server
Purpose Verify that the Windows DHCP service sees the port number as
agent.remote-id.
Supports
Assertion
14
Confidential

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
the address
Expected Results The DHCP service on the server should see the port number in
agent.remote-id format.
Expected Time
Tools Needed 1xDUT, 1xClient, 1xWindows DHCP Server, 1xBlade Server
Purpose Verify that Option 82 information is inserted when relaying
requests from Windows DHCP clients
Supports
Assertion
 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
the address
Expected Results Option 82 information should be correctly inserted into requests
from Windows clients
Tips
Expected Time
Tools Needed 1xDUT, 1xClient, 1xDHCP Server, 1xBlade Server
Purpose Verify that Option 82 information is inserted when relaying
requests from Linux DHCP clients
15
Confidential
Supports
Assertion
 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
the address
Expected Results Option 82 information should be correctly inserted into requests
from Linux clients
Tips
Expected Time
Tools Needed 1xDUT, 1xClient, 1xDHCP Server, 1xBlade Server
16

DHCP Option 82 Feature Testing Plan: Confidential

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DHCP Option 82 Feature Testing Plan: Confidential

Uploaded by

Copyright:

Available Formats

Confidential

DHCP Option 82 Feature Testing Plan

Verify that the Relay Agent Info can be enabled and

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

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

 Enable Relay Agent Info without applying

information is retained through a hot-remove/insert.

Section B - Perform each test once

 Verify that DHCP Opt 82 Info is present in DHCP requests

 Modify the information for the relay agent including an IP

You might also like