US 6,539,019 B1Grant

Methods and apparatus for automatically connecting a dynamic host configuration protocol (DHCP) client network device to a virtual local area network (VLAN)

Issue Date:2003-03-25

•19 Claims

•2 Drawing Sheets

Abstract

A method for automatically connecting a DHCP endpoint to a VLAN in an ATM network having a switch operative to provide LAN emulation for a plurality of non-ATM endpoints, the method including the steps of maintaining a LEC for the VLAN in the absence of any request by any of the endpoints to communicate via the VLAN, the LEC having been previously established for the VLAN, connecting the DHCP endpoint to a port on the switch, determining a predefined association between the VLAN and either the address of the port or the network address of the DHCP endpoint, and mapping either the network address of the DHCP endpoint or the address of the port to the LEC for communication via the VLAN.

Metadata

Assignee

3Com Corporation

Inventors

Ariel Noy
Sharon Barkai
Zeev Vax

Application Information

Application Number:US 09/317,786

Filing Date:1999-05-24

Priority Date:1999-05-24

Art Unit:7

Classifications

IPC:

H04L 1256

Field of Search:

37035237039513703952370395337039553703955237039553370395543703956370401370465

Patent Drawings (2 sheets)

Description

Field of the Invention

[0002] The present invention relates to computer networks in general, and more particularly relates to methods and apparatus for automatically connecting a Dynamic Host Configuration Protocol (DHCP) client network device to a Virtual Local Area Network (VLAN).

Background of the Invention

[0003] With the proliferation of local area networks (LANs), the need has developed for more powerful tools to manage LANs as they increase in complexity and size. One technique used for managing large networks involves defining one or more virtual local area networks (VLANs), allowing end-user network devices, also referred to herein as “endpoints,” to be logically grouped together and communicate as if they are on a common LAN, whether or not they reside on the same physical LAN segment. Some VLAN implementations allow for network switches to automatically identify an endpoint as it is physically attached to a switch port and assign it to a VLAN, either according to a default policy or in accordance with a predefined relationship between the endpoint address and a particular VLAN. In this manner an endpoint may be moved from one physical LAN segment to another while preserving its association with a particular VLAN.

[0004] VLANs may be implemented in various types of networks, including Asynchronous Transfer Mode (ATM) networks. Where non-ATM-based networks communicate via ATM networks, LAN Emulation (LANE) may be employed to provide address resolution between ATM and non-ATM addresses, such as Media Access Control (MAC) addresses. Where VLANs and LANE are both used in an ATM network, a network switch to which a non-ATM endpoint is attached may establish a LAN Emulation Client (LEC) to support communications between the non-ATM endpoint and another non-ATM endpoint in a given VLAN. A switch may simultaneously support multiple LECs for multiple VLANs, adding a LEC as communication via a VLAN is requested by one or more endpoints that belong to the VLAN, and removing the LEC when communications over the VLAN are concluded or idle for a period of time.

[0005] Further complicating the management of a VLAN/ATM/LANE environment is the need to support endpoints which dynamically request the assignment of their network addresses in accordance with the Dynamic Host Configuration Protocol (DHCP). When a DHCP endpoint is attached to a network it attempts to find a DHCP server which offers the endpoint an address for its use. A DHCP endpoint that does not find a DHCP server within a predefined period will “time out” and cease its attempt to find a DHCP server. Unfortunately, this timeout period is usually much shorter than the time it takes to map a DHCP endpoint upon being connected to a switch port to its VLAN and establish a LEC for the VLAN, thus virtually guaranteeing a DHCP timeout.

Summary of the Present Invention

[0006] The present invention seeks to provide methods and apparatus for automatically connecting a Dynamic Host Configuration Protocol (DHCP) client network device to a Virtual Local Area Network (VLAN) that overcome disadvantages related to the prior art.

[0007] There is thus provided in accordance with a preferred embodiment of the present invention a method for automatically connecting a DHCP endpoint to a VLAN in an ATM network having a switch operative to provide LAN emulation for a plurality of non-ATM endpoints, the method including the steps of maintaining a LEC for the VLAN in the absence of any request by any of the endpoints to communicate via the VLAN, the LEC has been previously-established for the VLAN, connecting the DHCP endpoint to a port of the switch, determining a predefined association between the VLAN and either of the address of the port and the network address of the DHCP endpoint, and mapping either of the network address of the DHCP endpoint and the address of the port to the LEC for communication via the VLAN.

[0008] Further in accordance with a preferred embodiment of the present invention any of the maintaining, determining, and mapping steps are performed by the switch.

[0009] Still further in accordance with a preferred embodiment of the present invention the determining step is performed by a network management station and the method further includes the steps of requesting the network address of the DHCP endpoint from the DHCP endpoint via the switch, and communicating the determination of the predefined association between the VLAN and either of the address of the port and the network address of the DHCP endpoint to the switch.

[0010] Additionally in accordance with a preferred embodiment of the present invention the network address of the DHCP endpoint is a MAC address.

[0011] Moreover in accordance with a preferred embodiment of the present invention the method further includes the steps of maintaining a plurality of LECs for a plurality of VLANs in the absence of any request by any of the endpoints to communicate via any of the plurality of VLANs, the plurality of LECs have been previously-established for the i of VLANs, and discontinuing maintenance of a least-recently used one of the plurality of LECs.

Brief Description of the Drawings

[0012] The present invention will be understood and appreciated more fully from the following detailed description taken in conjunction with the appended drawings in which:

[0013] FIG. 1 is a simplified flow diagram illustration of a system in which a Dynamic Host Configuration Protocol (DHCP) client network device is automatically connected to a Virtual Local Area Network (VLAN), constructed and operative in accordance with a preferred embodiment of the present invention; and

[0014] FIG. 2 is a simplified flowchart illustration of a method for automatically connecting a Dynamic Host Configuration Protocol (DHCP) client network device to a Virtual Local Area Network (VLAN) useful in understanding the system of FIG. 1, operative in accordance with a preferred embodiment of the present invention.

Detailed Description of the Present Invention

[0015] Reference is now made to FIG. 1 which is a simplified flow diagram illustration of a system in which a Dynamic Host Configuration Protocol (DHCP) client network device is automatically connected to a Virtual Local Area Network (VLAN), constructed and operative in accordance with a preferred embodiment of the present invention. FIG. 2 is a simplified flowchart illustration of a method for automatically connecting a Dynamic Host Configuration Protocol (DHCP) client network device to a Virtual Local Area Network (VLAN) intended to aid in understanding the system of FIG. 1, operative in accordance with a preferred embodiment of the present invention.

[0016] In the system of FIG. 1, a computer 10 is shown connected to a port 12 of an ATM switch 14. As shown in FIG. 1, computer 10 is a DHCP client. Switch 14 is in communication with a network management system (NMS) 16 to which switch 14 reports that computer 10 has connected to switch 14. Switch 14 may be triggered to report to NMS 16 either as the result of a simple network management protocol (SNMP) trap being set to detect new connections to ports on switch 14 or switch 14 may otherwise be periodically polled by NMS 16 for new connections. If the address of computer 10, such as a MAC address, and/or the port address of switch 14 to which computer 10 has been connected, have not yet been reported to NMS 16, NMS 16 then requests one or both addresses from switch 14, which switch 14 then provides to NMS 16.

[0017] A table 18 is preferably provided mapping endpoint or switch addresses to VLANs in accordance with specific, predetermined mappings or otherwise in accordance with a default address-to-VLAN mapping policy where no specific address-to-VLAN mapping exists. NMS 16 preferably queries table 18 to determine the VLAN to which computer 10 is to be assigned based on computer 10's MAC address and/or the address of port 12. NMS 16 then reports to switch 14 the VLAN to which computer 10 is to be assigned.

[0018] Switch 14 preferably maintains a table 20 mapping LECs to VLANs. Upon receiving computer 10's VLAN assignment from NMS 16, switch 14 queries table 20 to determine the LEC that is currently assigned to the VLAN designated for computer 10. If a LEC exists for the VLAN, switch 14 connects computer 10 to its designated VLAN. If no LEC exists, switch 14 must establish an LEC in order to support communications via the VLAN.

[0019] It is a particular feature of the invention that once switch 14 establishes a LEC for a VLAN it maintains the LEC even when it is no longer needed, such as in the absence of any request by any ATM endpoints to communicate via the VLAN. Thus, in the example shown, should computer 10 be assigned to VLAN 6 for which a LEC 3 was previously established but which is no longer active, such as is shown in table 20 at reference numeral 22, computer 10 may nonetheless be connected to VLAN 6 and serviced by LEC 3, as long as LEC 3 has been maintained by switch 14. Switch 14 may maintain any number of LECs for inactive VLANs, being limited only by its memory and processing capacity. Where such capacity would be exceeded, switch 14 preferably discontinues maintenance of the LEC which was least-recently used.

[0020] Once computer 10 connects to port 12 of switch 14, it attempts to find a DHCP server 24 which may offer computer 10 an address for its use. If switch 14 has not maintained a LEC for the VLAN to which computer 10 is assigned, computer 10 will typically not find DHCP server 24 within the timeout period and will stop searching for DHCP server 24, since this timeout period is typically much shorter than the time it takes to map computer 10 upon being connected to port 12 to its VLAN and establish a LEC for the VLAN. By maintaining a LEC for the VLAN, even while the VLAN is inactive, computer 10 finds DHCP server 24 within the timeout period and receives an address.

[0021] (New) A flow chart illustrating the method of the present invention for automatically connecting a DHCP client network device to a VLAN is shown in FIG. 2. The method is performed on the switch within the ATM network. The first step in the method is to establish a LEC for each VLAN to be supported (step 30). The switch then checks if a DHCP client (endpoint) gets connected to the switch (step 32). If no DHCP client is detected, the switch continuously maintains LECs for associated VLANs (step 34).

[0022] (New) Once the switch detects a DHCP endpoint connected to it, it reports the endpoint MAC address or switch port (depending on the configuration) to the NMS (step 36). The NMS functions to determine a VLAN assignment for the endpoint (or switch port) from the NMS mapping table (step 38). The switch receives instructions to assign the endpoint to a particular VLAN (step 40).

[0023] (New) If the VLAN currently does not have a LEC (step 42), the method continues with step 30 wherein a LEC is established for the VLAN. If the VLAN does have a LEC associated with it (step 42), the switch assigns the endpoint to the VLAN (step 44).

[0024] The methods and apparatus disclosed herein have been described without reference to specific hardware or software. Rather, the methods and apparatus have been described in a manner sufficient to enable persons of ordinary skill in the art to readily adapt commercially available hardware and software as may be needed to reduce any of the embodiments of the present invention to practice without undue experimentation and using conventional techniques.

[0025] While the present invention has been described with reference to a few specific embodiments, the description is intended to be illustrative of the invention as a whole and is not to be construed as limiting the invention to the embodiments shown. It is appreciated that various modifications may occur to those skilled in the art that, while not specifically shown herein, are nevertheless within the true spirit and scope of the invention.

Claims

What is claimed is:

1. A method of automatically connecting a Dynamic Host Configuration Protocol (DHCP) endpoint to a Virtual Local Area Network (VLAN) in an Asynchronous Transfer Mode (ATM) network having a switch operative to provide Local Area Network (LAN) emulation for a plurality of non-ATM endpoints, the method comprising the steps of:

maintaining a LAN Emulation Client (LEC) for said VLAN in an absence of a request by any of said endpoints to communicate via said VLAN, wherein said LEC has been previously established for said VLAN;

determining a predefined association between said VLAN and said DHCP endpoint upon connection of said DHCP endpoint to said switch; and

mapping said DHCP endpoint to said LEC for communication via said VLAN.

2. A method according to claim 1 wherein any of said maintaining, determining, and mapping steps are performed by said switch.

3. A method according to claim 1 wherein said determining step is performed by a network management station and further comprises the steps of:

requesting a network address of said DHCP endpoint from said DHCP endpoint via said switch; and

communicating said determination of said predefined association between said VLAN and either of an address of a port and the network address of said DHCP endpoint to said switch.

4. A method according to claim 1 wherein a network address of said DHCP endpoint is a Media Access Control (MAC) address.

5. A method according to claim 1 and further comprising the steps of:

maintaining a plurality of LECs for a plurality of VLANs in the absence of the request by any of said endpoints to communicate via any of said plurality of VLANs, wherein said plurality of LECs have been previously established for said plurality of VLANs; and

discontinuing maintenance of a least-recently used one of said plurality of LECs.

6. The method according to claim 1, wherein said step of determining a predefined association comprises making an association between said VLAN and an address of a port.

7. The method according to claim 1, wherein said step of determining a predefined association comprises making an association between said VLAN and a Media Access Control (MAC) address of said DHCP endpoint.

8. The method according to claim 1, wherein said step of mapping comprises mapping an address of a port to said LEC.

9. The method according to claim 1, wherein said step of mapping comprises mapping a Media Access Control (MAC) address of said DHCP endpoint to said LEC.

10. A method for automatically connecting a Dynamic Host Configuration Protocol (DHCP) endpoint to a Virtual Local Area Network (VLAN) upon connection of said DHCP endpoint to an Asynchronous Transfer Mode (ATM) network switch, said ATM network switch adapted to provide LAN emulation services for a plurality of DHCP endpoints, the method comprising the steps of:

creating predefined associations between each VLAN to be supported by said switch and one or more DHCP endpoints;

establishing a plurality of LAN Emulation Clients (LECs), each LEC associated with a different VLAN, wherein said plurality of LECs are continuously maintained in said switch even in an absence of a request by a DHCP endpoint to connect to a VLAN during which time a VLAN is inactive;

upon connection of a DHCP endpoint to said switch, searching for a VLAN associated with said connected DHCP endpoint;

determining a first LEC associated with said VLAN; and

assigning said connected DHCP endpoint to said first LEC so as to enable communications via said VLAN.

11. The method according to claim 10, wherein said step of creating predefined associations comprises making associations between each VLAN and a port address.

12. The method according to claim 10, wherein said step of creating predefined associations comprises making associations between each VLAN and a DHCP endpoint Media Access Control (MAC) address.

13. The method according to claim 10, wherein said step of searching comprises searching for a VLAN associated with a port address said DHCP endpoint is connected to.

14. The method according to claim 10, wherein said step of searching comprises searching for a VLAN associated with a Media Access Control (MAC) address of said connected DHCP endpoint.

15. An Asynchronous Transfer Mode (ATM) network switch for automatically connecting a Dynamic Host Configuration Protocol (DHCP) endpoint to a Virtual Local Area Network (VLAN) upon connection of said DHCP endpoint to said switch, said switch adapted to provide LAN emulation services for a plurality of DHCP endpoints, comprising:

means for creating predefined associations between each VLAN to be supported by said switch and one or more DHCP endpoints;

means for establishing a plurality of LAN Emulation Clients (LECs), each LEC associated with a different VLAN, wherein said plurality of LECs are continuously maintained in said switch even in an absence of a request by a DHCP endpoint to connect to a VLAN during which time a VLAN is inactive;

means for upon connection of a DHCP endpoint to said switch, searching for a VLAN associated with said connected DHCP endpoint;

means for determining a first LEC associated with said VLAN; and

means for assigning said connected DHCP endpoint to said first LEC so as to enable communications via said VLAN.

16. The switch according to claim 15, wherein said means for creating predefined associations comprises means for making associations between each VLAN and a port address.

17. The switch according to claim 15, wherein said means for creating predefined associations comprises means for making associations between each VLAN and a DHCP endpoint Media Access Control (MAC) address.

18. The switch according to claim 15, wherein said means for searching comprises means for searching for a VLAN associated with a port address said DHCP endpoint is connected to.

19. The switch according to claim 15, wherein said means for searching comprises means for searching for a VLAN associated with a Media Access Control (MAC) address of said connected DHCP endpoint.

Patent Citations (38)

Patent	Date	Inventor	Cited By
US4823338(A)	1989-04-01	Chan et al.	Applicant
US4975906(A)	1990-12-01	Takiyasu et al.	Applicant
US5214646(A)	1993-05-01	Yacoby	Applicant
US5280476(A)	1994-01-01	Kojima et al.	Applicant
US5280481(A)	1994-01-01	Chang et al.	Applicant
US5315582(A)	1994-05-01	Morizono et al.	Applicant
US5321693(A)	1994-06-01	Perlman	Applicant
US5321694(A)	1994-06-01	Chang et al.	Applicant
US5329527(A)	1994-07-01	Ujihashi et al.	Applicant
US5329619(A)	1994-07-01	Page et al.	Applicant
US5345558(A)	1994-09-01	Opher et al.	Applicant
US5390184(A)	1995-02-01	Morris	Applicant
US5394402(A)	1995-02-01	Ross	Applicant
US5408469(A)	1995-04-01	Opher et al.	Applicant
US5444702(A)	1995-08-01	Burnett et al.	Applicant
US5483536(A)	1996-01-01	Gunji et al.	Applicant
US5519704(A)	1996-05-01	Farinacci et al.	Applicant
US5548646(A)	1996-08-01	Aziz et al.	Applicant
US5548723(A)	1996-08-01	Pettus	Applicant
US5550816(A)	1996-08-01	Hardwick et al.	Applicant
US5550818(A)	1996-08-01	Brackett et al.	Applicant
US5566014(A)	1996-10-01	Glance	Applicant
US5583865(A)	1996-12-01	Esaki et al.	Applicant
US5600644(A)	1997-02-01	Chang et al.	Applicant
US5633869(A)	1997-05-01	Burnett et al.	Applicant
US5659542(A)	1997-08-01	Bell et al.	Applicant
US5666487(A)	1997-09-01	Goodman et al.	Applicant
US5812552(A)	1998-09-01	Arora et al.	Examiner
US5920699(A)	1999-07-01	Bare	Examiner
US5949783(A)	1999-09-01	Husak et al.	Examiner
US5968126(A)	1999-10-01	Ekstrom et al.	Examiner
US6047325(A)	2000-04-01	Jain et al.	Examiner
US6167052(A)	2000-12-01	McNeill et al.	Examiner
US6269076(B1)	2001-07-01	Shamir et al.	Examiner
US6286038(B1)	2001-09-01	Reichmeyer et al.	Examiner
US6289017(B1)	2001-09-01	Shani et al.	Examiner
WO97/04386	1997-06-01		Applicant
WO98/02821	1998-01-01		Applicant

Non-Patent Literature (17)

Rajaravivarma, V. “Virtual Local Area Network Technology and Applications” System Theory, 1997, pp. 49-52, Mar. 9-11, 1997.Applicant
Simpson, W., “IP in IP Tunneling”, Request for Comments #153, Oct. 1995, 9 pages.Applicant
Swallow, G., “Frame Relay PVC Multicast Service and Protocol Description”, FRF.7, Frame Relay Forum Implementation Agreement, Oct. 21, 1994, printed from internet site www.frforum.com, 17 pages.Applicant
Cisco—“Packet Services”, printed from website http://www.cisco.com/warp/public/732/Tech/pksrv_tc.html, 32 pages, Dec. 1995.Applicant
Deering, S., “Host Extensions for IP Multicasting”, Request for Comments (RFC) 1112, Stanford University, 16 pages, Aug. 1989.Applicant
Egevang, K. et al., “The IP Network Address Translator (NAT)”, Request for Comments (RFC) 1631, Cray Communications, 12 pages, May 1994.Applicant
“All About . . . Multicast Wide Area Network Services”, printed from website http://www.starburstcom.com/ mcast.html, 11 pages, Feb. 1997.Applicant
Ellington, B. (Ed.), LAN Emulation SWG Drafting Group, “LAN Emulation Over ATM Specification—Version 1.0”, ATM Forum, pp. 1-139, (1995).Applicant
Novell NetWare Network Computing Products 3.12, “NetWare 3.12 Concepts”, Novell, Inc., USA, Part No.: 100-001715-001, Jul. 1993, pp. 158-163.Applicant
Novell NetWare Network Computing Products 3.12, “TCP/IP Transport Supervisor's Guide”, Novell, Inc., USA, Part No. 100-001866-001, May 1993, pp. B-15-B-22.Applicant
Parker, T. et al., “TCP/IP Unleashed”, SAMS Publishing (1996), pp. 418-429.Applicant
Perlman, R., “Interconnections: Bridges and Routers”, Addison-Wesley Publishing, Section 9.2.4, Chapter 9, pp. 205-264 (1992).Applicant
Sedgewick, R., “Algorithms”, Second Edition, Addison-Wesley Publishing, Chapter 17, pp. 245-257 (1988).Applicant
Doeringer, W. et al., “Routing on Longest-Matching Prefixes”, IEEE/ACM Transactions on Networking, vol. 4, No. 1, Feb. 1996, pp. 86-97.Applicant
Williams, K. A., “A Distributed ATM Network Based on an Optical Passive Star”, printed from website http://williams.cs.ncat.edu/ATMStar.htm, 2 pages, (1998).Applicant
“All-optical ATM-Switch based on Self Electro-optic Effect Devices (SEED's)”, printed from website http://www.stw.nl/projecten/T/tel3997.html, 2 pages, Feb. 2, 1997.Applicant
“VLAN Information”, printed from website http://net21.ucdavis.edu/newvlan.htm, Oct. 29, 1998, 13 pages.Applicant

Abstract