Patent Document

CROSS-REFERENCES 
       [0001]    This is a continuation application of U.S. Ser. No. 11/487,347, filed Jul. 17, 2006, the entire disclosure of which is hereby incorporated by reference. 
       CLAIM OF PRIORITY 
       [0002]    The present application claims priority from Japanese patent application serial no. 2006-040644, filed on Feb. 17, 2006, the content of which is hereby incorporated by reference into this application. 
     
    
     BACKGROUND OF THE INVENTION 
       [0003]    This invention relates to a network apparatus and method for forwarding a packet, and relates to a network apparatus and method for forwarding a packet for providing layer 2 VPN functions. 
         [0004]    The VPWS (Virtual Private Wire Service) function using MPLS (Multi Protocol Label Switching) switching is one method for constructing a Layer 2 Virtual Private Network. In VPWS operation, the network apparatus functioning via Ethernet on subscriber lines receives only flow control packets defined by IEEE 802.3x, and relays all other packets. In other words, in VPWS operation the network apparatus provides layer 2 VPN service by relaying all packets other than flow control packets. 
         [0005]    Ethernet line redundancy on the other hand is regulated by IEEE 802.3ad standard. This standard achieves line redundancy by transmitting and receiving link aggregation control packets. 
         [0006]    The following Document 1 (in particular, 3.2.1 “PAUSE Frames”) is described in the IEEE 802.3x standard. The subsequent Document 2 is described in the IEEE 802.3ad standard. The subsequent Document 3 and Document 4 are described in the RFC (Request For Comments) of the IETF (Internet Engineering Task Force) relating to VPWS. 
         [0007]    VPWS, as might be assumed from the title of wire service, is a service lending cable lines to carriers. VPWS therefore gives no consideration to link aggregation. 
         [0008]    Document 1: “TechFest Ethernet Technical Summary”, the Internet&lt;http://www.techfest.com/networking/lan/ethernet.h tm&gt; 
         [0009]    Document 2: “Link Aggregation according to IEEE 802.3ad”, the 
         [0000]    Internet&lt;http://www.triumf.ca/canarie/amsterdam-test/References/wp-lag-c.pdf&gt; 
         [0010]    Document 3: L. Martini, and three others, “Pseudowire Setup and Maintenance using the Label Distribution Protocol”, the Internet&lt;URL:http//www.ietf.org/rfc/rfc4447.txt&gt; 
         [0011]    Document 4: L. Martini, and three others, “Encapsulation Methods for Transport of Ethernet Over MPLS Networks”, the 
         [0000]    Internet&lt;URL:http//www.ietf.org/rfc/rfc4448.txt&gt; 
       SUMMARY OF THE INVENTION 
       [0012]    As described above, attempting to apply IEEE 802.3ad link aggregations to subscriber Ethernet lines adapted to VPWS causes the link aggregation control packets to be relayed. Applying a link aggregation between two customer edge apparatuses via an MPLS network is possible. However, link aggregations cannot be applied to subscriber lines between customer edge apparatuses and provider edge apparatuses. The object of this invention is to provide a high-reliability network device for VPWS subscribers on Ethernet lines with redundancy capability and capable of seamless band additions. 
         [0013]    The network apparatus of this invention receives an IEEE802.3ad link aggregation control packet and also receives an IEEE802.3x flow control packet. The network apparatus transmits link aggregation control packets. The network apparatus also relays other layer 2 control protocol packets without receiving them, and does not transmit other layer 2 control protocol packets. 
         [0014]    A network apparatus connecting an MPLS network and a subscriber line for providing layer 2 VPN between the MPLS network and the subscriber line, is characterized in that the subscriber line forms a link aggregate with other subscriber lines. 
         [0015]    A network apparatus connecting an MPLS network and a subscriber line for providing layer 2 VPN between the MPLS network and the subscriber line, is characterized in executing a flow control process when a flow control packet is received from the subscriber line, and executing a link aggregate process or withdraw process with other subscriber lines when a link aggregation control packet is received from the subscriber line. 
         [0016]    A network apparatus connecting an MPLS network and a subscriber line for providing layer 2 VPN between the MPLS network and the subscriber line, is characterized in discarding a link aggregation control packet when the link aggregation control packet attached with a label is received from the MPLS network. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0017]    Preferred embodiments of the present invention will now be described in conjunction with the accompanying drawings, in which; 
           [0018]      FIG. 1  is a block diagram showing the structure of the network apparatus; 
           [0019]      FIG. 2  is a block diagram of the network; 
           [0020]      FIG. 3  is a drawing for describing the structural information of the provider edge apparatus; 
           [0021]      FIG. 4  is a flowchart for describing the process when the provider edge apparatus receives a packet from the customer edge apparatus; 
           [0022]      FIG. 5  is a flowchart for describing the process when the provider edge apparatus receives a packet from another provider edge apparatus; and 
           [0023]      FIG. 6  is a drawing showing the table held by the provider edge apparatus. 
       
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS 
       [0024]    The embodiment of this invention is hereafter described while referring to the drawings in  FIG. 1  through  FIG. 6 . Here,  FIG. 1  is a block diagram showing the structure of the network apparatus.  FIG. 2  is a block diagram of the network.  FIG. 3  is a drawing for describing structural information on the provider edge apparatus.  FIG. 4  is a flowchart for describing the process when the provider edge apparatus receives a packet from the customer edge apparatus.  FIG. 5  is a flowchart for describing the process when the provider edge apparatus receives a packet from another provider edge apparatus.  FIG. 6  is a drawing showing the table held by the provider edge apparatus. 
         [0025]    A network apparatus  100  includes a control unit  110  and a communication unit  120  as shown in  FIG. 1 . This control unit  110  contains a memory  114  and a CPU  112 . The CPU  112  processes control packets and controls the entire device by executing programs stored within the memory  114 . The communication unit  120  contains two network interfaces  122  and relays packets between a third layer (network layer) and a second layer (data link layer) of an OSI (Open Systems Interconnection) reference model. The communication unit  120  also relays packets on the MPLS layer. Each network interface  122  is connected to a respective line (twisted pair cable, optical fiber, etc.) such as the Ethernet. 
         [0026]    The network where the network apparatus is utilized, is described while referring to  FIG. 2 . A network  1000  in  FIG. 2  is made up of a customer edge apparatus (shown in the figure as CE: Customer Edge)  400 - 1 , and a provider edge apparatus (shown in the figure as PE: Provider Edge)  100 - 1 , a provider edge apparatus  100 - 2 , and a customer edge apparatus  400 - 2 . The provider edge apparatus  100 - 1  and the customer edge apparatus  400 - 1  are connected via lined  1  and  2 . The lines  1  and  2  of the provider edge apparatus  100 - 1  and the customer edge apparatus  400 - 1  are concentrated by a link aggregation defined in IEEE 802.3ad. The provider edge apparatus  100 - 2  and the customer edge apparatus  400 - 2  however are connected by a line  6 . In other words, there is no link aggregation between the provider edge apparatus  100 - 2  and the customer edge apparatus  400 - 2 . 
         [0027]    The provider edge apparatus and the customer edge apparatus are both network apparatuses. The customer edge apparatus may utilize the structure in  FIG. 1 . 
         [0028]    The configuration information of  FIG. 3  is placed in the memory  114  of  FIG. 1 . The first line of  FIG. 3  specifies the Ethernet network interface to which the Ethernet line  1  is connected. The second line specifies the network interface shown in line  1  as a layer 2 VPN subscriber line. The third line specifies the Ethernet network interface to which the Ethernet line  2  is connected. The fourth line specifies that the network interface shown in the third line is a layer 2 VPN subscriber line. The fifth line specifies the IEEE 802.3ad link aggregation and specifies the control ID as  10 . The sixth line specifies the interfaces defined in the first and third lines as network interfaces belonging to the IEEE 802.3ad link aggregation specified in the fifth line. The seventh line and onward define structural information for the MPLS function. The eighth line specifies layer 2 VPN. The IEEE 802.3ad link aggregation defined in the fifth and sixth line is specified for the layer 2 VPN subscriber line, and the control ID is defined as  20 . The ninth line specifies the provider edge apparatus  100 - 2  as the exit edge router for this layer 2 VPN. Based on these structures, the provider edge apparatus  100 - 1  establishes an IEEE 802.3ad link aggregation with the customer edge apparatus  400 - 1  and establishes the VC required for 2 layer VPN with the provider edge apparatus  100 - 2 . 
         [0029]      FIG. 4  is a flowchart of the process when the provider edge apparatus  100 - 1  has received a packet from the customer edge apparatus  400 - 1 . The provider edge apparatus  100 - 1  first of all decides whether the received packet is for flow control as specified in IEEE 802.3x (S 11 ). If the decision is “YES” then the flow control process is executed (S 12 ). 
         [0030]    If the decision in step  11  is “NO”, then a decision is made whether the received packet is for link aggregation as specified in IEEE 802.3ad (S 13 ). If the decision is “YES”, then the control unit  110  executes the link aggregation process, and controls the aggregation and withdraw recovery of the line  1  and the line  2  (S 14 ). If the decision in step  13  is “NO” then the provider edge apparatus  100 - 1  relays the packet to the VPWS (S 15 ) and the process ends. 
         [0031]      FIG. 5  is a flowchart for the processing when the provider edge apparatus  100 - 1  has received a packet from the provider edge apparatus  100 - 2 . The provider edge apparatus  100 - 1  stores the MPLS label value attached to the received packet (S 21 ). The provider edge apparatus  100 - 1  next removes the MPLS label from the received packet (S 22 ). This step  22  is required because the provider edge apparatus  100 - 2  encapsulates the packet sent from the customer edge apparatus  400 - 2  by utilizing the MPLS label. In order to implement layer 2 VPN, the MPLS label must be removed before the provider edge apparatus  100 - 1  sends (the packet) to the customer edge apparatus  400 - 1 . The provider edge apparatus  100 - 1  next decides whether the packet whose MPLS label is removed is a link aggregation control packet as specified in IEEE 802.3ad (S 23 ). If the decision is “YES”, then that received packet is discarded (S 24 ). If the decision in step  23  is “NO”, then the VPWS relay process is executed (S 25 ) and the process ends. 
         [0032]    The necessity for step  24  (discarding the link aggregation control packet) is described here. If the provider edge apparatus  100 - 2  carries out the processing shown in step S 14  in the sequence of  FIG. 4  when a link aggregation control packet is sent from the customer edge apparatus  400 - 2 , then the provider edge apparatus  100 - 2  processes the packet so that packet is not sent to the provider edge apparatus  100 - 1 . On the other hand, when the processing shown in step S 14  in  FIG. 4  is not performed, then the provider edge apparatus  100 - 2  sends a link aggregation control packet from the customer edge apparatus  400 - 2 , and this packet reaches the provider edge apparatus  100 - 1  via the provider edge apparatus  100 - 2 . The link aggregation control packet sent from the customer edge apparatus  400 - 2  does not arrive at the customer edge apparatus  400 - 1  since the provider edge apparatus  100 - 1  carries out the processing in step S 24 . This step S 24  as related previously is a step required for making link aggregation function correctly on the line  1  and the line  2  connecting the customer edge apparatus  400 - 1  and the provider edge apparatus  100 - 1 . 
         [0033]      FIG. 6  is an output line select table used when selecting an output line on which to send a packet to the customer edge apparatus  400 - 1  when the provider edge apparatus  100 - 1  has received a packet from the provider edge apparatus  100 - 2 . The output line select table  60  is stored in the database  121  of the communication unit  120  of the provider edge apparatus  100 . The output line select table  60  contains an input label value  61  and an output interface type  62  and output line  63  and output line selection method  64 . 
         [0034]    The provider edge apparatus  100 - 1  must identify the output network interface for sending the received packet, from the MPLS label value that is stored in step S 21  of  FIG. 5 . If the input label value attached to the packet received by the provider edge apparatus  100 - 1  is “ 16 ”, then the provider edge apparatus  100 - 1  refers to the output line select table  60 , and sets the network interface for outputting the packet is a link aggregation where line  1  and line  2  are concentrated. One of either the first line or the second line is then assumed to be selected as the output line. However the selection method used here is random so that either the first line or the second line is selected at random and the packet is then sent. 
         [0035]    However, if the input label value attached to the packet received by the provider edge apparatus  100 - 1  is “ 18 ”, then the provider edge apparatus  100 - 1  refers to the output line select table  60 , and sets the network interface for outputting the packet as a link aggregation where line  4  (not shown in  FIG. 1 ) and line  5  (not shown in drawing) are concentrated as a link aggregation. Here, the selection method selects the output line via the L 2  header so after analyzing the packet L 2  header in a state where the MPLS label was removed from the received packet, one output line is selected from line  4  or a line  5  based on predetermined rules, and that packet is then sent. 
         [0036]    Further, if the input label value attached to the packet received by the provider edge apparatus  100 - 1  is “ 17 ”, then the provider edge apparatus  100 - 1  refers to the output line select table  60 , and sends the packet on the line  3  (not shown in  FIG. 1 ) as the network interface for output where there is no link aggregation. 
         [0037]    The reason for using  16  through  18  as input label values is that these values can be used freely. These values are defined along with the presence or absence of a link aggregation, and the output line selection method using  FIG. 6 . Therefore other values or combinations of values may also be used. 
         [0038]    In the above embodiment, the link aggregation is implemented by the provider edge apparatus  100 - 1  and the customer edge apparatus  400 - 1  mutually sending and receiving link aggregation control packets. However, this embodiment is not limited to this means, and rather than sending and receiving link aggregation control packets, lines may be concentrated or withdrawn by utilizing structural information by applying a so-called static mode. 
         [0039]    The above embodiment utilized MPLS as the method for implementing layer 2 VPN, however this method may also be applied when functions such as VLAN are used and the invention is not limited to these methods. 
         [0040]    The layer 2 VPN device of this embodiment applied link aggregation to the subscriber lines so that there was no stoppage of subscriber communication even if a problem occurred on one of the lines in the line concentration at the link aggregation. Moreover, even if there is insufficient bandwidth for a line, the effect on communications can be eliminated, and bandwidth can be easily increased by adding lines concentrated by the link aggregation. Moreover seamless increases to the band (width) can be made.

Technology Category: 5