Automated configuration of network device ports

• US 8,601,143 B2
• Filed: 09/27/2011
• Issued: 12/03/2013
• Est. Priority Date: 05/13/2004
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Vogel, Gary Dennis Jr., Droms, Ralph, Butaney, Vikas, Saville, Roland
• Primary Examiner(s): Burgess, Glenton B.
• Assistant Examiner(s): Nguyen, Angela
• Application Number:
  US13/246,642
• Publication Number:
  US 20120036243A1
• Time in Patent Office: 798 Days
• Field of Search: 709/204
• US Class Current: 709/228
• CPC Class Codes: G08B 13/2402 Electronic Article Surveillance [EAS], i.e. systems using tags for detecting removal of a tagged item from a secure area, e.g. tags for detecting shoplifting mechanical aspects of the tags, e.g. related to locking E05B73/0017; RFID readers G06K7/00; RFID tags G06K19/00; access control systems G07C9/00; anti-theft control in point of sale systems G07G3/003; security seals G09F3/03
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 2101/663 Transport layer addresses, e.g. aspects of transmission control protocol [TCP] or user datagram protocol [UDP] ports
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0883 Semiautomatic configuration, e.g. proposals from system
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1021 based on client or server locations
• CPC Class Codes: H04W 28/088 among core entities
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support

Abstract

Methods and devices are provided for identifying end devices and automatically configuring associated network settings. Preferred implementations of the invention do not require users to manually identify connection types (e.g., RFID, IPphone, manufacturing device, etc.) or to manually configure the network device. Accordingly, such implementations allow automatic switch configuration, even for devices that use inconsistent protocols and/or protocols that are not well known. Some methods of the invention employ DHCP options combined with traffic snooping to identify devices and automatically apply appropriate switch port configuration.

Claims

1. A method, comprising:

receiving a DHCPDISCOVER request from a device;

examining at least one DHCP option of the DHCPDISCOVER request; and

determining, based on information in the at least one DHCP option of the DHCPDISCOVER request, whether an appropriate macro is available to configure a port of a network device on which the DHCPDISCOVER request was received;

if the appropriate macro is determined to be available, causing the port of the network device to be configured by the appropriate macro such that the port of the network device on which the DHCPDISCOVER request was received is automatically configured;

wherein the macro includes a set of instructions.

2. The method of claim 1, further comprising the step of determining whether the port has already been configured in a manner appropriate for the device.

3. The method of claim 1, wherein the determining step comprises determining a device personality.

4. The method of claim 1, wherein the determining step comprises identifying the device.

5. The method of claim 1, wherein the determining step is performed by the network device on which the DHCPDISCOVER request was first received.

6. The method of claim 1, wherein the determining step is not performed by the network device on which the DHCPDISCOVER request was first received.

7. The method of claim 1, wherein the DHCPDISCOVER request is received by a switch port and wherein the determining step is performed by one of a DHCP server, an edge services management server, an authentication server or a device dedicated to port configuration.

8. The method of claim 1, wherein the at least one option includes a PreBoot Execution Environment (PXE) DHCP option.

9. An apparatus for establishing network device port settings, the apparatus comprising:

a port for receiving a DHCPDISCOVER request from a device;

a memory; and

at least one logic device configured for determining, based on information in at least one DHCP option in the DHCPDISCOVER request, whether an appropriate macro is available to configure the port of the apparatus and, if the appropriate macro is determined to be available, causing the port of the apparatus to be configured by the appropriate macro such that the port of the apparatus on which the DHCPDISCOVER request was received is automatically configured, wherein the macro includes a set of instructions.

10. The apparatus of claim 9, wherein the at least one DHCP option comprises a Preboot Execution Environment (PXE) DHCP option.

11. The apparatus of claim 9, wherein the information comprises vendor specific information, a vendor identifier, a device type, and/or a connection type.

12. The apparatus of claim 9, wherein the device is an RFID device, wherein the at least one logic device is further configured for determining, based, at least in part, on the information in the DHCPDISCOVER request, a personality of the device, and wherein determining, based on information in at least one DHCP option in the DHCPDISCOVER request, whether an appropriate macro is available to configure the port of the apparatus, comprises:

determining whether an appropriate macro for an RFID device having the personality of the device is available to configure a port of the apparatus on which the DHCPDISCOVER request was received from the device.

13. A method, comprising:

receiving a DHCPDISCOVER request from a first device;

examining at least one DHCP option of the DHCPDISCOVER request;

determining, based on information in the DHCPDISCOVER request, a personality of the first device;

determining whether an appropriate macro for a device having the personality of the first device is available to configure a port of a second device on which the DHCPDISCOVER request was received; and

causing the port of the second device to be configured by the appropriate macro such that the port of the second device on which the DHCPDISCOVER request was received is automatically configured.

14. The method of claim 13, wherein the first device is an RFID device.

15. The method of claim 13, wherein the macro comprises a set of instructions.

16. A network device, comprising:

a plurality of ports;

a storage device; and

a logic device configured to

receive a DHCPDISCOVER request from a first device via a first port of the plurality of ports of the network device,

determine, based on information in the DHCPDISCOVER request, a personality of the first device,

determine whether configuration parameters for a device having the personality of the first device are available to configure the first port of the network device on which the DHCPDISCOVER request was received and

configure the first port of the network device with the configuration parameters such that the first port of the network device on which the DHCPDISCOVER request was received is automatically configured.

17. The network device of claim 16, wherein the logic device is further configured to forward a copy of the DHCPDISCOVER request to a second device and wherein the logic device configures the first port according to instructions received from the second device.

18. The network device of claim 16, wherein the network device is a switch or router.

19. The network device of claim 16, wherein the configuration parameters comprise VLAN parameters.

20. The network device of claim 16, wherein the first device is an RFID device.

21. The network device of claim 17, wherein the second device is a device selected from the group consisting of a DHCP server, an edge services management server, an authentication server and a device dedicated to port configuration.