Granted Patent B2

US 7,466,698 · App. 10/454,283 · Granted Dec 16, 2008

Abstract

Claims (41)

1. A network node having a plurality of communication ports, the network node comprising:

an interface configuration mechanism operable to receive user commands, the user commands comprising:

an interface class configuration command that configures at least in part a Layer 3 (L3) interface class in terms of an L3 interface class identifier and one or more packet forwarding rules;

a first interface configuration command that configures at least in part a first L3 interface for a specified one of the plurality of communication ports and non-exclusively assigns the L3 interface class identifier to the first L3 interface;

a second interface configuration command that configures at least in part a second L3 interface for a specified one of the plurality of communication ports and non-exclusively assigns the L3 interface class identifier to the second L3 interface;

wherein the first and second L3 interfaces specify a port identifier, a media type, an IP address, and an IP subnet mask;

a packet forwarding mechanism operable to apply the one or more packet forwarding rules, which are associated with the L3 interface class identifier, to packets arriving at the first and second L3 interfaces, the packet forwarding mechanism comprising a first hardware lookup table having a plurality of entries, some of said entries corresponding to interface class configuration commands and being identified by L3 interface class identifiers (IDs) and other of said entries corresponding to interface configuration commands and being identified by L3 interface IDs, wherein said entries in the first hardware lookup table include the respective L3 interface class IDs and L3 interface IDs and data representative of their respective packet forwarding rules; and

a second hardware lookup table having a plurality of entries, each entry corresponding to an interface configuration command and operable to store an L3 interface class identifier in association with at least a VLAN ID.

2. The network node of claim 1 , wherein the packet forwarding mechanism is operable to apply the one or more packet forwarding rules to packets arriving at the first L3 interface and packets arriving at the second L3 interface.

3. The network node of claim 1 , wherein the interface configuration mechanism comprises a Command Line Interface (CLI).

4. The network node of claim 1 , wherein the user commands further comprise a third interface configuration command that configures at least in part a third L3 interface for a third specified one of the communication ports in terms of at least one or more packet forwarding rules, wherein the third L3 interface specifies a port identifier, a media type, an IP address, and an IP subnet mask.

5. The network node of claim 4 , wherein the interface configuration mechanism generates an L3 interface identifier for the third L3 interface when the interface configuration command does not specify an L3 interface class identifier.

6. A method for managing a network node, comprising:

identifying Layer 3 (L3) interface classes;

associating one or more packet forwarding rules with each one of the L3 interface classes;

assigning L3 interface class identifiers (IDs) to the L3 interface classes;

establishing L3 interfaces in terms of a port identifier, a media type, an IP address, an IP subnet mask;

associating one or more packet forwarding rules with each one of the L3 interfaces;

assigning L3 interface IDs to the L3 interfaces;

storing the L3 interface class IDs and the L3 interface IDs in the same hardware lookup table in association with data representative of their respective packet forwarding rules;

using the hardware lookup table to retrieve packet forwarding rules based on an L3 interface class ID or based on an L3 interface ID;

establishing at least two L3 interfaces in terms of a port identifier, a media type, an IP address, an IP subnet mask, and a first L3 interface class of the L3 interface classes;

receiving a first packet via a first one of the at least two L3 interfaces;

applying the one or more packet forwarding rules, which are associated with the first L3 interface class, to the first packet;

receiving a second packet via a second one of the at least two L3 interfaces; and

applying the one or more packet forwarding rules, which are associated with the first L3 interface class, to the second packet;

wherein the maximum number of IDs supported in the hardware lookup table is fixed to a limited ID space and wherein a maximum number of L3 interface classes is specified as a subset of the limited ID space such that IDs from the limited ID space are assigned to L3 interface classes up to the maximum number of L3 interface classes and IDs from the limited ID space outside the maximum number of L3 interfaces classes are assigned to L3 interfaces.

7. The method of claim 6 , wherein the identifying step comprises limiting a maximum number of class identifiers to a predetermined value.

8. The method of claim 6 , wherein the one or more packet forwarding rules comprise a rule for establishing an access control list (ACL).

9. The method of claim 6 , wherein the one or more packet forwarding rules comprise a rule for establishing Quality of Service (QoS) guarantees.

10. The method of claim 6 , wherein the one or more packet forwarding rules comprise a rule for establishing policy routing.

11. The method of claim 6 , wherein the establishing step comprises providing the class identifier, an IP address, and a subnet mask for a selected physical port of the network node to define a first Layer 3 Interface.

12. The method of claim 11 , wherein the establishing step comprises providing the class identifier, an IP address, and a subnet mask for a selected physical port of the network node to define a second Layer 3 Interface.

13. The method of claim 6 , wherein the identifying step comprises assigning a class identifier to the L3 interface class and further comprising:

receiving a first packet via a first one of the at least two L3 interfaces;

performing a hardware lookup using the class identifier as a key to identify the one or more packet forwarding rules;

applying the one or more packet forwarding rules, which are identified through the hardware lookup, to the first packet;

receiving a second packet via a second one of the at least two L3 interfaces;

performing a hardware lookup using the class identifier as a key to identify the one or more packet forwarding rules;

applying the one or more packet forwarding rules, which are identified through the hardware lookup, to the second packet.

14. The network node of claim 1 wherein the maximum number of IDs supported in the first hardware lookup table is fixed to a limited ID space and wherein a maximum number of L3 interface classes is specified as a subset of the limited ID space such that IDs from the limited ID space are assigned to L3 interface classes up to the maximum number of L3 interface classes and IDs from the limited ID space outside the maximum number of L3 interfaces classes are assigned to L3 interfaces.

Assignments (10)