JP6472304B2 - Network monitoring device and relay system - Google Patents

Description

  The present invention relates to a network monitoring apparatus and a relay system, for example, a relay system to which a MAC-in-MAC scheme is applied and a network monitoring apparatus used in the relay system.

  For example, Patent Document 1 extracts key information from a received packet, generates a hash value from the key information, and stores the key information and a cumulative packet length in an area having the hash value as an address. An excessive flow detector is shown.

JP 2009-27400 A

  For example, as a technique for realizing wide area Ethernet (registered trademark), an extended VLAN system, a MAC-in-MAC system, and the like are known. The extended VLAN method is standardized by IEEE802.1ad, and is a technology for expanding the number of VLANs by adding a VLAN tag for a carrier to a customer VLAN (Virtual Local Area Network) tag based on IEEE802.1Q. It is.

  The MAC-in-MAC method encapsulates a customer MAC (Media Access Control) frame with a carrier MAC frame to further expand the number of VLANs and switch (core switch) in a wide area network. This is a technique for reducing the number of MAC addresses learned in the above. As a MAC-in-MAC scheme, a PBB (Provider Backbone Bridge) standard based on IEEE 802.1ah is typically known. In the PBB standard, each customer can be identified using a 24-bit service instance identifier ISID.

  On the other hand, RMON, sFlow, NetFlow, etc. are known as techniques for monitoring the bandwidth used for each customer. For example, it is conceivable to monitor the bandwidth used by each customer by applying such a technique to the PBB network. However, unlike a general customer network in which a 12-bit customer is accommodated using a VLAN identifier, the PBB network needs to monitor a 24-bit (about 16 million) customer. Therefore, hardware and / or software resources may become excessive.

  The present invention has been made in view of such circumstances, and one of its purposes is to provide a network monitoring apparatus and a relay system that can implement bandwidth monitoring with small resources.

  The above and other objects and novel features of the present invention will be apparent from the description of this specification and the accompanying drawings.

  Of the inventions disclosed in the present application, the outline of a typical embodiment will be briefly described as follows.

  The network monitoring apparatus according to the present embodiment includes a port that receives a frame including a first identifier of a plurality of bits, a first identifier, a first bit area, and a second bit area excluding the first bit area. A bandwidth monitoring unit that divides into a plurality of bit regions and monitors a bandwidth of a frame received at the port using the plurality of bit regions. The bandwidth monitoring unit counts the size of each frame received within a predetermined period for each value of the first bit area (first process). Furthermore, when there is a count value that satisfies a predetermined condition in the first process, the bandwidth monitoring unit, based on the first value of the first bit area corresponding to the count value, the first bit area of the first identifier The value is the first value, and the size is counted for each value of the second bit area for a newly received frame within a predetermined period (second process).

  The effects obtained by the representative embodiments of the invention disclosed in the present application will be briefly described. In the network monitoring apparatus and the relay system, bandwidth monitoring with small resources can be realized.

In the relay system by one embodiment of this invention, it is the schematic which shows the structural example of the whole. FIG. 2 is a schematic diagram illustrating an example of the structure of various frames in the relay system of FIG. 1. (A) is a block diagram which shows the example of schematic structure of the principal part of a switch apparatus in the relay system of FIG. 1, (b) is the schematic which shows the structural example of FDB in (a). (A) And (b) is the schematic which shows an example of the mounting form different from Fig.3 (a) in the network monitoring apparatus by one embodiment of this invention. FIG. 4 is an explanatory diagram illustrating a schematic operation example of a bandwidth monitoring unit in the switch device of FIG. FIG. 4 is a flowchart showing an example of detailed processing contents of a bandwidth monitoring unit in the switch device of FIG. FIG. 4 is a flowchart showing an example of detailed processing contents of a bandwidth monitoring unit in the switch device of FIG. It is a figure which shows an example of the specific sequence of the process of FIG. 6 and FIG.

  In the following embodiment, when it is necessary for the sake of convenience, the description will be divided into a plurality of sections or embodiments. However, unless otherwise specified, they are not irrelevant, and one is the other. Some or all of the modifications, details, supplementary explanations, and the like are related. Further, in the following embodiments, when referring to the number of elements (including the number, numerical value, quantity, range, etc.), especially when clearly indicated and when clearly limited to a specific number in principle, etc. Except, it is not limited to the specific number, and may be more or less than the specific number.

  Further, in the following embodiments, the constituent elements (including element steps and the like) are not necessarily indispensable unless otherwise specified and apparently essential in principle. Needless to say. Similarly, in the following embodiments, when referring to the shapes, positional relationships, etc. of the components, etc., the shapes are substantially the same unless otherwise specified, or otherwise apparent in principle. And the like are included. The same applies to the above numerical values and ranges.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. Note that components having the same function are denoted by the same reference symbols throughout the drawings for describing the embodiment, and the repetitive description thereof will be omitted.

<< Overall configuration of relay system >>
FIG. 1 is a schematic diagram showing an example of the overall configuration of a relay system according to an embodiment of the present invention. The relay system shown in FIG. 1 includes a plurality (eight in this case) of customer networks 12a1 to 12a4, 12b1 to 12b4, and a plurality (here, two) of PB networks 11a and 11b that are responsible for relaying between the customer networks. And a PBB network 10 responsible for relaying between the PB networks 11a and 11b. Here, as an example, a description will be given assuming that the customer networks 12a1 to 12a4 belong to a certain customer (for example, company A) and the customer networks 12b1 to 12b4 belong to another customer (for example, company B).

  The PB network 11a is responsible for relaying between the customer networks 12a1 and 12a2 and between the customer networks 12b1 and 12b2. The PB network 11b is relaying between the customer networks 12a3 and 12a4 and between the customer networks 12b3 and 12b4. Bear. The PBB network 10 is a relay network in which relaying based on IEEE 802.1ah (that is, the PBB standard) is performed. The PB networks 11a and 11b are relay networks to which the above-described extended VLAN system is applied.

  Switches SWB1, SWB2, SWB3, and SWB4 are installed at the boundaries between the customer networks 12a1, 12b1, 12a2, and 12b2 and the PB network 11a, respectively. The customer network 12a1 includes a plurality of customer terminals TM and a network NWc1. The plurality of customer terminals TM are connected to the network NWc1 via a communication line (for example, Ethernet (registered trademark) line) 13, and are connected to the switch SWB1 via the network NWc1. The network NWc1 is configured by, for example, a switch and a communication line. Similarly, the customer network 12b1 includes a plurality of customer terminals TM and a network NWc2 that connects these to the switch SWB2. Although not shown, each of the customer networks 12a2 and 12b2 has the same configuration. .

  The switch SWB1 is responsible for relaying between the plurality of customer terminals TM in the customer network 12a1, and is also responsible for relaying between each customer terminal TM and the PB network 11a. Similarly, the switch SWB2 is responsible for relaying between a plurality of customer terminals TM in the customer network 12b1, and is also responsible for relaying between each customer terminal TM and the PB network 11a. Although not shown, the switch SWB3 , SWB4 perform the same operation.

  As in the case of the PB network 11a, switches SWB5, SWB6, SWB7, and SWB8 are installed at the boundary portions between the customer networks 12a3, 12b3, 12a4, and 12b4 and the PB network 11b, respectively. Each of the customer networks 12a3 and 12b3 includes a plurality of customer terminals TM and networks NWc5 and NWc6. The customer networks 12a4 and 12b4 also have the same configuration. Each of the switches SWB5 to SWB8 is responsible for relaying between the plurality of customer terminals TM in the corresponding customer network, and is also responsible for relaying between each customer terminal TM and the PB network 11b.

  A switch device (edge switch device) SWE1 is installed at the boundary between the PB network 11a and the PBB network 10 (in other words, at the entrance or exit of the PBB network 10). The switch device SWE1 has one or a plurality (n in this example) of lower link ports Pd [1] to Pd [n] and a single or a plurality of (single in this example) upper link ports Pu. The PB network 11a includes a network NWb1 configured by switches, communication lines, and the like.

  Each of the switches SWB1 to SWB4 is connected to the network NWb1 via the communication line 13, and any one of the plurality of lower link ports Pd [1] to Pd [n] of the switch device SWE1 is connected via the network NWb1. To be connected as appropriate. Thereby, the switching device SWE1 is responsible for relaying between the switches SWB1 and SWB3, relaying between the switches SWB2 and SWB4, and is also responsible for relaying between the switches SWB1 to SWB4 and the PBB network 10.

  As in the case of the switch device SWE1, a switch device (edge switch device) SWE2 is installed at the boundary between the PB network 11b and the PBB network 10. The switch device SWE2 includes one or more lower link ports Pd [1] to Pd [n] and one or more upper link ports Pu. The PB network 11b includes a network NWb2. The switches SWB5 to SWB8 are appropriately connected to any of the plurality of lower link ports Pd [1] to Pd [n] of the switch device SWE2 via the network NWb2. Thereby, the switch device SWE2 is responsible for relaying between the switches SWB5 and SWB7, relaying between the switches SWB6 and SWB8, and also responsible for relaying between the switches SWB5 to SWB8 and the PBB network 10.

  The PBB network 10 includes a network (core network) NWbb including a switch device (core switch device) SWC. The switch device SWC includes a plurality (four in this example) of ports P1 to P4. In this example, the ports P1 and P2 are connected to the upper link ports Pu of the switch devices (edge switch devices) SWE1 and SWE2 via the communication line 13, respectively. Similarly, ports P3 and P4 are also connected to an upper link port of an edge switch device (not shown). Thus, the edge switch devices are connected to each other via the network NWbb.

  Here, four switches SWB1 to SWB4 are installed at the boundary portion of the PB network 11a (the same applies to the PB network 11b), but more switches are actually installed. Accordingly, in addition to the four customer networks 12a1, 12a2, 12b1, and 12b2, more customer networks are accommodated in the PB network 11a (the same applies to the PB network 11b). As a result, a large number of customers (such as companies) are accommodated in the PBB network 10, and each switch device (particularly the core switch device SWC) in the PBB network 10 relays frames from the large number of customers as appropriate. In this example, one core switch device SWC is typically installed in the core network NWbb, but actually, a plurality of core switch devices are installed.

<< Frame structure in relay system >>
FIG. 2 is a schematic diagram showing an example of the structure of various frames in the relay system of FIG. Here, as an example, various frames based on the PBB standard are transferred from a customer terminal TM (referred to as TM1) in the customer network 12a1 to a customer terminal TM (referred to as TM2) in the customer network 12a3. The customer address (MAC address) CMAC of the customer terminal TM1 is “CAa1”, and the customer address CMAC of the customer terminal TM2 is “CAa3”. Further, it is assumed that the encapsulation address (MAC address) BMAC of the switch device SWE1 is “BA1”, and the encapsulation address BMAC of the switch device SWE2 is “BA2”.

  As shown in FIGS. 1 and 2, first, the customer terminal TM1 as the transmission source transmits a frame FR1 in the customer network 12a1. The frame FR1 in the customer network 12a1 is an unencapsulated frame including the customer VLAN tag 15, the source customer address CMAC (CSA), and the destination customer address CMAC (CDA). Here, the source customer address CSA is the MAC address “CAa1”, and the destination customer address CDA is the MAC address “CAa3”. The customer VLAN tag 15 includes a customer VLAN identifier CVID arbitrarily set by the customer.

  Next, as shown in FIG. 1, the switch SWB1 receives the frame FR1 and transmits the frame FR2 in the PB network 11a. The frame FR2 is an extended VLAN frame and is an unencapsulated frame in which the service VLAN tag 16 is added to the frame FR1 as shown in FIG. The service VLAN (extended VLAN) tag 16 includes a service VLAN identifier SVID arbitrarily set by a communication carrier or the like. Although not necessarily limited, the communication carrier or the like sets the service VLAN identifier SVID having the same value for the customer networks 12a1 and 12a2, and the same value different from the customer networks 12a1 and 12a2 for the customer networks 12b1 and 12b2. The service VLAN identifier SVID is set.

  The broadcast domain in the PB network 11a is determined by this service VLAN identifier SVID. The switch SWB1 adds the service VLAN tag 16 to the frame FR1 based on the above-mentioned setting of the communication carrier or the like. Note that the service VLAN tag assigning device having the function of assigning such a service VLAN tag 16 is not limited to the switch SWB1, but may be an OLT (Optical Line Termination).

  Subsequently, as illustrated in FIG. 1, the switching device SWE1 receives the frame FR2 and transmits the frame FR3 into the PBB network 10. The frame FR3 is a PBB frame and an encapsulated frame. The encapsulated frame generally has a structure in which an encapsulation address, various identifiers, and the like are added to an unencapsulated frame based on the PBB standard. Specifically, as shown in FIG. 2, the frame FR3 is obtained by changing the frame FR2 into a service instance identifier ISID, a backbone VLAN tag (B tag) 18, a source encapsulation address BMAC (BSA), and a destination encapsulation address. It has a structure encapsulated with BMAC (BDA).

  The service instance identifier ISID is included in the service instance tag (I tag) 17 including the above-mentioned source customer address CSA and destination customer address CDA. The service instance identifier ISID is an identifier for identifying a customer and has a 24-bit area. This 24-bit area allows further expansion of the 12-bit service VLAN identifier SVID.

  The service instance identifier ISID is arbitrarily set by a communication carrier or the like. A typical setting method includes a method of associating one service VLAN identifier SVID with one service instance identifier ISID, a method of associating a plurality of service VLAN identifiers SVID with one service instance identifier ISID, and the like. Although not particularly limited, the communication carrier or the like can set a service VLAN identifier SVID set in the PB network 11a for the customer networks 12a1 and 12a2 and a service VLAN identifier assigned in the PB network 11b for the customer networks 12a3 and 12a4. The same service instance identifier ISID is associated with the SVID.

  The backbone VLAN tag (B tag) 18 includes a backbone VLAN identifier BVID. The backbone VLAN identifier BVID is an identifier for frame transfer path control and has a 12-bit area. A broadcast domain within the PBB network 10 is defined by this backbone VLAN identifier BVID. The backbone VLAN identifier BVID is set by a communication carrier or the like. A typical setting method is a method of associating a plurality of service instance identifiers ISID with one backbone VLAN identifier BVID.

  As shown in the frame FR3 in FIG. 2, the switching device SWE1 sends the source encapsulation address BSA (the own device encapsulation address “BA1”), the destination encapsulation address BDA (here, the encapsulation of the switching device SWE2). Frame “FR2” is encapsulated using the address “BA2”) and various tags (17, 18). Then, the switching device SWE1 transmits the frame FR3, which is the encapsulated frame, from the upper link port Pu.

  The switching device SWC relays the frame FR3 received at the port P1 to the port P2 based on the destination encapsulation address BDA “BA2”. The switching device SWE2 receives the frame FR3 at the upper link port Pu. Since the destination encapsulation address BDA “BA2” of the frame FR3 is addressed to the switching device SWE2, the switching device SWE2 converts the encapsulated frame FR3 into the unencapsulated frame FR2, as shown in FIGS. Then, the switching device SWE2 transmits the frame FR2 from the lower link port (Pd [1] in this case) to the switch SWB5 via the PB network 11b.

  The switch SWB5 receives the frame FR2, and converts it into the frame FR1 by removing the service VLAN tag 16 from the frame FR2. Then, the switch SWB5 transmits the frame FR1 to the customer terminal TM2 having the customer address CMAC “CAa3” via the customer network 12a3.

  In the examples of FIGS. 1 and 2, the switching devices SWE1 and SWE2 receive or transmit the frame FR2 with the PB networks 11a and 11b. It is also possible to receive or transmit FR1. That is, the edge switching device can generate the frame FR3 by encapsulating the frame FR1 of FIG. 2, or can generate the frame FR1 by decapsulating the frame FR3.

  Also, here, the description has been made on the assumption that the configuration is based on the PBB standard, which is one of the MAC-in-MAC schemes. However, for the other EoE (Ethernet (registered trademark) over Ethernet) standard, Is equally applicable. The EoE frame has a slightly different format from the PBB frame (frame FR3) in FIG. 2, but has substantially the same information as the information in the PBB frame in FIG. 2, and the relay system is the same as in FIG. Configured. For example, in the EoE frame, each customer is identified using a 20-bit ES-VID (Extended Service VLAN ID) instead of the 24-bit service instance identifier ISID.

《Relay system issues》
In the relay system as shown in FIG. 1, there are cases where it is desired to monitor the bandwidth used for each customer and identify a customer whose bandwidth is excessive. In this case, for example, the size of the frame transferred by the PBB network 10 may be monitored for each service instance identifier ISID. However, unlike the 12-bit (4096) customer VLAN identifier CVID, the service instance identifier ISID has a 24-bit (about 16 million) area. In this case, for example, a process for appropriately managing the storage unit using a storage unit having an address space of 24 bits is required, and thus hardware and / or software resources may be excessive.

  On the other hand, in order to solve such a problem, for example, it is conceivable to use a method as shown in Patent Document 1. However, in this method, since the address space is compressed using a hash operation, there is a possibility that some service instance identifiers ISID (that is, customers) may be overlooked due to collision of hash values.

<< Configuration of switch device (network monitoring device) >>
3A is a block diagram illustrating a schematic configuration example of a main part of the switch device in the relay system of FIG. 1, and FIG. 3B is a schematic diagram illustrating a structure example of the FDB in FIG. 3A. FIG. FIG. 3A shows a configuration example of the core switch device SWC shown in FIG. The switch device SWC shown in FIG. 3A includes a plurality of ports P1, P2, P3,..., An interface unit 20, a relay processing unit 21, an FDB (Forwarding DataBase), and a bandwidth monitoring unit 22.

  Each of the plurality of ports P1, P2, P3,... Receives a frame (specifically, an encapsulated frame FR3) and transmits a frame. When the frame is received at any of the plurality of ports, the interface unit 20 adds the identifier of the port that has received the frame (referred to as a reception port identifier in this specification) to the frame and sends the frame to the relay processing unit 21. Send. Further, when the interface unit 20 receives from the relay processing unit 21 a frame to which a port destination identifier (referred to as a destination port identifier in this specification) is added, the interface unit 20 determines the frame based on the destination port identifier. Send to port.

  As shown in FIG. 3B, the FDB holds a correspondence relationship between the MAC address, the VLAN identifier VID, and the port. The relay processing unit 21 relays the encapsulated frame received at the port based on the FDB by performing learning and search of the FDB. In the example of FIG. 1 described above, the relay processing unit 21 of the core switch device SWC receives the encapsulated frame FR3 including the predetermined backbone VLAN identifier BVID (for example, “BV1”) from the edge switch device SWE1 at the port P1. Receiving.

  In response to this, as shown in FIG. 3B, the relay processing unit 21 uses the source encapsulation address BSA “BA1” and the backbone VLAN identifier BVID “BV1” of the encapsulated frame FR3 as the reception port identifier. The FDB learns in association with {P1}. In this specification, {P1} represents the identifier of the port P1, and hereinafter, similarly, {AA} represents the identifier of “AA”. Similarly, when receiving the encapsulated frame from the edge switch device SWE2, the relay processing unit 21 sets the encapsulation address BAMC “BA2” and the backbone VLAN identifier BVID “BV1” to the reception port identifier {P2}. The FDB learns in association.

  When the encapsulated frame is received, the relay processing unit 21 retrieves the FDB using the destination encapsulation address BDA and the backbone VLAN identifier BVID of the encapsulated frame as a retrieval key, and acquires the destination port identifier. Then, the relay processing unit 21 transmits the encapsulated frame with the destination port identifier added thereto to the interface unit 20. In the example of FIG. 1 described above, the relay processing unit 21 of the switch device SWC searches for the destination encapsulation address BDA “BA2” and the backbone VLAN identifier BVID “BV1” when the encapsulation frame FR3 is received at the port P1. The FDB is searched as a key, and the destination port identifier {P2} is acquired.

  The bandwidth monitoring unit 22 includes an entry-specific counter 23, a determination unit 24, and an entry management unit 25, and monitors the used bandwidth for each customer. Although details will be described later, for example, the bandwidth monitoring unit 22 sets a 24-bit service instance identifier (first identifier) ISID, an entry [1] (first bit area), and an entry [2] (second bit area). A plurality of bit areas are included, and the band of the frame (encapsulated frame) received by the port is monitored using the plurality of bit areas. The switch device SWC also has a function as a network monitoring device by including the bandwidth monitoring unit 22.

  4 (a) and 4 (b) are schematic diagrams showing an example of an implementation different from FIG. 3 (a) in the network monitoring apparatus according to the embodiment of the present invention. As shown in FIG. 3A, the network monitoring apparatus is not limited to the form coexisting with the switch apparatus, but may be a single form. For example, the network monitoring apparatus NM1 in FIG. 4A includes ports Pn1 and Pn2 and a bandwidth monitoring unit 22 similar to that in FIG. 3A, and is inserted into one of the communication lines 13 included in the PBB network 10. To be installed. That is, the network monitoring device NM1 relays the frame (encapsulated frame) received by one of the ports Pn1 and Pn2 to the other as it is, and monitors the bandwidth used for each customer based on the frame.

  On the other hand, the network monitoring device NM2 in FIG. 4B includes a port Pn1 and a bandwidth monitoring unit 22 similar to that in FIG. 3A, and is connected to a predetermined switch device SW in the PBB network 10. Installed. That is, the switch device SW copies a frame received at a predetermined port (here, a plurality of ports P1, P2,...), And transmits the copied frame to a predetermined port (here, port Pm). A mirroring unit 30 may be provided. The network monitoring device NM2 receives the frame transmitted from the port Pm of the switch device SW at the port Pn1, and monitors the bandwidth used for each customer based on the frame.

  The network monitoring device is not necessarily limited to the core switch device SWC, and may be installed at any location of the PBB network 10 including the edge switch device and the communication line 13. However, in particular, it is beneficial to install the core switch device SWC in which frames from each customer are aggregated. For example, for the configuration shown in FIG. It is beneficial to use the form as shown in FIG.

<Overall operation of the bandwidth monitoring unit>
FIG. 5 is an explanatory diagram showing a schematic operation example of the bandwidth monitoring unit in the switch device of FIG. The bandwidth monitoring unit 22 divides the 24-bit service instance identifier (first identifier) ISID included in the received frame (encapsulated frame) FR3 into a plurality of bit areas (entries), and uses the plurality of entries to Monitor bandwidth. In the example of FIG. 5, the plurality of entries are upper 12 bits of entry [1] (first bit area) 35a, followed by 6 bits of entry [2] (second bit area) 35b, and subsequent 3 bits. Entry [3] (third bit area) 35c and the remaining 3-bit entry [4] 35d.

  Then, in the first process, the bandwidth monitoring unit 22 uses the counter 23a by entry for the size of the received frame for each value of the entry [1] 35a for the frame FR3 received within a predetermined period. And count. 5, for example, the count value for the value “00... 00” of the entry [1] 35a is “1”, and for the value “00... 01” of the entry [1] 35a. The count value is “N1”. The size of the received frame is not particularly limited, but is the number of received frames or the frame length of the received frames.

  Here, when there is a count value that satisfies a predetermined condition in the entry-specific counter 23a, the bandwidth monitoring unit 22 is based on the first value of the entry [1] (first bit area) 35a corresponding to the count value. A second process is performed. In the second process, the bandwidth monitoring unit 22 receives the frame FR3 that is newly received within a predetermined period and the value of the entry [1] (first bit area) 35a is the first value. The frame size is counted for each value of entry [2] (second bit area) 35b.

  In the example of FIG. 5, the bandwidth monitoring unit 22 executes the second process when the count value in the first process exceeds a predetermined reference count value Nth1, and the value “00” of the entry [1] 35a Assume that the count value “N1” for “... 01” exceeds “Nth1”. In this case, the bandwidth monitoring unit 22 targets the frame FR3 newly received within a predetermined period for which the value of the entry [1] 35a is “00... 01” (first value). The size of the received frame is counted using the entry-specific counter 23b for each value of the entry [2] (second bit area) 35b. In the counter 23b by entry of FIG. 5, for example, the count value for the value “000000” of the entry [2] 35b is “1”, and the count value for the value “000001” of the entry [2] 35b is “N2”. .

  Here, similarly, when there is a count value that satisfies a predetermined condition in the entry-specific counter 23b, the bandwidth monitoring unit 22 similarly stores the second of the entry [2] (second bit area) 35b corresponding to the count value. A third process is performed based on the value. In the third process, the bandwidth monitoring unit 22 determines that the value of the entry [1] (first bit area) 35a and the value of the entry [2] (second bit area) 35b are the first value and the second value, respectively. In addition, for the frame FR3 newly received within a predetermined period, the size of the received frame is counted for each value of the entry [3] (third bit area) 35c.

  In the example of FIG. 5, the bandwidth monitoring unit 22 executes the third process when the count value in the second process exceeds a predetermined reference count value Nth2, and the value “000001” of the entry [2] 35b is assumed. The count value “N2” for “” exceeds the “Nth2”. In this case, the bandwidth monitoring unit 22 has values of the entry [1] 35a and the entry [2] 35b of “00... 01” (first value) and “000001” (second value), respectively, For the newly received frame FR3 within a predetermined period, the size of the received frame is counted using the entry-specific counter 23c for each value of entry [3] (third bit area) 35c.

  Similarly, the bandwidth monitoring unit 22 performs the fourth process when the count value in the third process exceeds a predetermined reference count value Nth3. In the example of FIG. 5, the count value “N3” for the value (third value) “001” of the entry [3] 35c exceeds the “Nth3”. In this case, the bandwidth monitoring unit 22 determines that the values of the entry [1] 35a, the entry [2] 35b, and the entry [3] 35c are the first value, the second value, and the third value, respectively, and within a predetermined period. For the newly received frame FR3, the size of the received frame is counted using the entry-specific counter 23d for each entry [4] 35d value.

  As a result, when the count value of the entry [4] 35d includes a count value that exceeds a reference count value (for example, Nth4), the bandwidth monitoring unit 22 determines the value of the entry [4] 35d corresponding to the count value. Then, the service instance identifier ISID is specified based on the first value to the third value of the entry [1] 35a to the entry [3] 35c that are the preconditions. Then, the bandwidth monitoring unit 22 determines that the specified service instance identifier ISID is an identifier that satisfies a predetermined condition.

  In the example of FIG. 5, the count value N4 for the value “001” of the entry [4] 35d exceeds the reference count value (Nth4). As a result, the bandwidth monitoring unit 22 determines that the service instance identifier ISID “00... 01000001001001” is an identifier that satisfies a predetermined condition. Specifically, for example, the bandwidth monitoring unit 22 determines a customer to which the service instance identifier ISID is assigned as a customer whose bandwidth is exceeded.

  As described above, by using the method as shown in FIG. 5, it is possible to typically perform bandwidth monitoring with small resources. That is, as a comparative example, when bandwidth monitoring is realized by a simple method, for example, it is necessary to provide 24 bits (about 16 million entries) in the entry-specific counter 23. On the other hand, in the method shown in FIG. 5, it is sufficient to provide a maximum of 12 bits (4096 entries) like the entry-specific counter 23a. Even when the entry-specific counters 23b to 23d are required, an additional 80 ( = 64 + 8 + 8) is only added. As a result, bandwidth monitoring can be realized with a small-capacity storage unit and a small processing load associated therewith, and hardware and / or software resources can be reduced.

  In this example, four entries [1] 35a to [4] 35d are used. However, the present invention is not particularly limited to this, and two or more entries may be used. In addition, here, the four entries are the upper 12 bits, the subsequent 6 bits, the subsequent 3 bits, and the remaining 3 bits. However, the present invention is not particularly limited to this, and each entry, the number of bits and the bit position, The correspondence relationship can be arbitrarily determined. In general, as the number of entries increases, the resource can be reduced. However, since the time required for specifying the service instance identifier ISID becomes longer, the method of dividing the entries may be appropriately determined in consideration of these balances.

  Here, for example, a bandwidth monitoring unit that does not support the PBB method or the like may include a storage unit for 12 bits based on the customer VLAN identifier CVID. Therefore, considering the applicability from the configuration, it is desirable that each entry is configured not to exceed 12 bits. In particular, entry [1] 35a is preferably 12 bits. Further, the reference count values Nth1 to Nth4 may all be the same value, or may be appropriately different depending on the case.

  Further, although the customer whose used bandwidth is exceeded is determined here, it is also possible to specify a customer whose used bandwidth is too low (that is, the count value is smaller than the predetermined count value) in the same manner. . Further, the first identifier to be monitored is not limited to the service instance identifier ISID, but may be, for example, an ES-VID used in the EoE method. Further, in some cases, it may be a 12-bit identifier such as a customer VLAN identifier CVID or a service VLAN identifier SVID included in the unencapsulated frame. In this case, for example, bandwidth monitoring can be realized using 2048 entries or the like.

<Detailed operation of bandwidth monitoring unit>
6 and 7 are flowcharts showing an example of detailed processing contents of the bandwidth monitoring unit in the switch device of FIG. In FIG. 6, the bandwidth monitoring unit 22 executes process [1] (first process). In the process [1], the bandwidth monitoring unit 22 (entry management unit 25) first sets the bit area of the service instance identifier ISID to N (N is an integer of 2 or more) bit areas as shown in FIG. The monitoring is divided into (entries [1] to [N]) (step S101).

  Next, the bandwidth monitoring unit 22 (entry management unit 25) starts timer [1] (step S102). Subsequently, the entry management unit 25 determines whether or not a frame from the interface unit 20 has been received (step S103). When the frame is received, as shown in FIG. 5, the entry management unit 25 updates the count value for each value of the entry [1] 35a in the entry-specific counter 23a (step S104).

  After step S104 or when no frame is received in step S103, the bandwidth monitoring unit 22 (entry management unit 25) determines whether or not the period of the timer [1] has expired (step S105). If the period of the timer [1] has not expired, the entry management unit 25 returns to step S103. On the other hand, when the period of the timer [1] ends, the bandwidth monitoring unit 22 (determination unit 24) determines whether or not there is a count value that satisfies a predetermined condition in the entry-specific counter 23a as shown in FIG. Is determined (step S106).

  When there is a count value that satisfies the predetermined condition, the bandwidth monitoring unit 22 (entry management unit 25) determines the value (first value) of the entry [1] 35a corresponding to the count value as the entry value to be monitored. (Step S107), the process [2] shown in FIG. 7 is started (Step S108). After step S108 or when there is no count value that satisfies the predetermined condition in step S106, the entry management unit 25 resets the count value of the entry-specific counter 23a (step S109), and ends the process [1].

  In FIG. 7, the bandwidth monitoring unit 22 executes process [2] (second process). In the process [2], the bandwidth monitoring unit 22 (entry management unit 25) determines whether or not the process [2] is activated in step S108 of FIG. 6 (step S201). If activated, the entry management unit 25 sets N = 2 (step S202) and activates the timer [2] (step S203). The period of the timer [2] is the same as the period of the timer [1] described above, for example.

  Next, the bandwidth monitoring unit 22 (entry management unit 25) determines whether or not a frame having a service instance identifier ISID value that matches the entry value to be monitored has been received (step S204). At this stage, the entry value to be monitored is set to the value (first value) of entry [1] 35a in accordance with step S107 in FIG. When the frame is received, the entry management unit 25 updates the count value for each value of the entry [N] (N = 2 here) 35b in the entry-specific counter 23b as shown in FIG. S205).

  After step S205 or when no frame is received in step S204, the bandwidth monitoring unit 22 (entry management unit 25) determines whether or not the period of the timer [2] has expired (step S206). If the timer [2] period has not expired, the entry management unit 25 returns to step S204. On the other hand, when the period of the timer [2] ends, the bandwidth monitoring unit 22 (determination unit 24) determines whether or not there is a count value that satisfies a predetermined condition in the entry-specific counter 23b as shown in FIG. Is determined (step S207).

  When there is a count value that satisfies the predetermined condition, the bandwidth monitoring unit 22 (entry management unit 25) determines the value (second value) of the entry [N] (N = 2 here) 35b corresponding to the count value, An additional entry value to be monitored is determined (step S208). Subsequently, the entry management unit 25 determines whether N = Nmax (step S209). If N = Nmax is not satisfied, the entry management unit 25 sets N = N + 1 (step S210) and returns to step S203.

  As a result, taking FIG. 5 as an example, the bandwidth monitoring unit 22 assumes that Nmax = 4, the process (third process) for entry [3] 35c (entry-specific counter 23c), and entry [4] 35d (entry The processing for the other counter 23d) is performed in order. If N = Nmax in step S209, the bandwidth monitoring unit 22 sets a service instance identifier ISID including each entry value determined in step S107 in FIG. 6 and sequentially added in step S208 in FIG. It is specified as an identifier that satisfies the condition (step S211). If the process [2] is not activated in step S201, or if there is no identifier that satisfies the predetermined condition in step S207, the bandwidth monitoring unit 22 ends the process without executing the process of step S211.

  Here, although not necessarily limited, the bandwidth monitoring unit 22 repeatedly executes the process [1] (first process) of FIG. 6 in parallel with the process [1] in order to prevent time-series monitoring omissions. Then, it is desirable to execute the process [2] (second process, third process,...) Of FIG. Specifically, the bandwidth monitoring unit 22 repeatedly executes the process [1] for each period of the timer [1]. For example, when a count value that satisfies a predetermined condition is generated in the period of a certain timer [1]. Performs processing [1] and processing [2] in parallel at the next timer [1] cycle (= timer [2] cycle).

  In this case, as the entry-specific counter 23 in FIG. 3A, at least the entry-specific counter 23a and the entry-specific counter 23b shown in FIG. 5 are provided. On the other hand, the entry-specific counters 23c and 23d do not compete with the resource for the entry-specific counter 23b, and may be configured to share the entry-specific counter 23b in some cases. In this case, resources can be reduced.

  On the other hand, when the entry-specific counters 23a to 23d are individually provided, for example, the processing shown in FIG. 8 is performed to efficiently use resources and reduce the time required to specify the service instance identifier ISID. Sometimes it can be shortened. FIG. 8 is a diagram illustrating an example of a specific sequence of the processes in FIGS. 6 and 7. In the example of FIG. 8, processing using the entry-specific counter 23a is performed in the timer period T1 of the timer [1] and the timer [2], and a count value that satisfies a predetermined condition is generated in the entry-specific counter 23a.

  Therefore, in the next timer period T2, processing using the entry-specific counter 23b is performed based on the value (first value) of the entry [1] 35a obtained in the timer period T1. In parallel with this, processing using the entry-specific counter 23a is also performed. As a result, a count value that satisfies a predetermined condition occurs in the entry-specific counter 23b, and a count value that satisfies a predetermined condition also occurs in the entry-specific counter 23a.

  Therefore, in the next timer period T3, processing using the entry-specific counter 23c is performed based on the value (second value) of the entry [2] 35b obtained in the timer period T2. Further, processing using the entry-specific counter 23b is performed based on the value (first value) of the entry [1] 35a obtained in the period T2. In parallel with this, processing using the entry-specific counter 23a is also performed. Thereafter, similarly, the bandwidth monitoring can be performed by efficiently using the entry-specific counters 23a to 23c (and 23d not shown).

  Here, an example in which one count value satisfying a predetermined condition is generated in each entry counter for each timer period. On the other hand, when a plurality of count values satisfying a predetermined condition are generated, for example, the values of a plurality of entries corresponding to the plurality of counter values are temporarily stored and extracted one by one for each timer period. The processing may be performed in order. Alternatively, in some cases, for example, a plurality of sets of entry-specific counters 23b and the like may be provided to perform processing in parallel.

  As described above, by using the network monitoring device and the relay system according to the present embodiment, it is possible to typically perform bandwidth monitoring with small resources.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiments. However, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the invention. For example, the above-described embodiment has been described in detail for easy understanding of the present invention, and is not necessarily limited to one having all the configurations described. Further, a part of the configuration of one embodiment can be replaced with the configuration of another embodiment, and the configuration of another embodiment can be added to the configuration of one embodiment. . Further, it is possible to add, delete, and replace other configurations for a part of the configuration of each embodiment.

10 PBB network 11a, 11b PB network 12a1 to 12a4, 12b1 to 12b4 Customer network 13 Communication line 15 Customer VLAN tag 16 Service VLAN tag 17 Service instance tag 18 Backbone VLAN tag 20 Interface unit 21 Relay processing unit 22 Bandwidth monitoring unit 23, 23a ˜23d Entry-specific counter 24 Judgment unit 25 Entry management unit 30 Port mirroring unit 35a-35d Entry BMAC encapsulation address BVID Backbone VLAN identifier CMAC customer address CVID Customer VLAN identifier FR1 to FR3 Frame ISID Service instance identifier NWc1, NWc2, NWc5 , NWc6, NWb1, NWb2, NWbb network P1-P4, Pn1, Pn2 , Pm port Pd [1] to Pd [n] Lower link port Pu Upper link port SVID Service VLAN identifier TM, TM1, TM2 Customer terminal SWE, SWC, SW switch device SWB1-SWB8 switch

Claims (12)

A port for receiving a frame including a first identifier of a plurality of bits;
The first identifier is divided into a plurality of bit areas including a first bit area and a second bit area excluding the first bit area, and the band of the frame received at the port is monitored using the plurality of bit areas. A bandwidth monitoring unit,
Have
The bandwidth monitoring unit
For a frame received within a predetermined period, a first process for counting the size of the received frame for each value of the first bit area;
In the first process, when there is a count value that satisfies a predetermined condition, the value of the first bit area of the first identifier is based on the first value of the first bit area corresponding to the count value. A second process that counts the size of the received frame for each value of the second bit area for a frame that is a first value and is newly received within a predetermined period;
Run the
Network monitoring device. The network monitoring device according to claim 1,
The bandwidth monitoring unit repeatedly executes the first process, and executes the second process in parallel with the first process.
Network monitoring device. The network monitoring device according to claim 1,
The second process is executed when the count value in the first process exceeds a predetermined reference count value.
Network monitoring device. The network monitoring device according to claim 1,
In the second process, when there is a count value that satisfies a predetermined condition in the second process, the bandwidth monitoring unit further determines the first identifier based on the second value of the second bit area corresponding to the count value. When the value of the first bit area and the value of the second bit area are the first value and the second value, respectively, and the frame is newly received within a predetermined period, the size of the received frame Performing a third process for counting the value for each value of the third bit area,
Network monitoring device. The network monitoring device according to claim 1,
The number of bits of the first identifier is greater than 12 bits;
The number of bits of the first bit area is 12 bits,
The number of bits in the second bit region is 12 bits or less.
Network monitoring device. In the network monitoring device according to any one of claims 1 to 5,
The first identifier is a service instance identifier based on the PBB standard.
Network monitoring device. A relay system including a switch device that relays an encapsulated frame including a first identifier based on a MAC-in-MAC scheme,
The switch device is
A port for receiving the encapsulated frame;
An FDB that holds the relationship between the MAC address and the port;
A relay processing unit that relays the encapsulated frame received at the port based on the FDB;
The first identifier is divided into a plurality of bit areas including a first bit area and a second bit area excluding the first bit area, and the bandwidth of the encapsulated frame received at the port using the plurality of bit areas A bandwidth monitoring unit for monitoring
Have
The bandwidth monitoring unit
A first process for counting the size of the received frame for each value of the first bit area for encapsulated frames received within a predetermined period;
In the first process, when there is a count value that satisfies a predetermined condition, the value of the first bit area of the first identifier is based on the first value of the first bit area corresponding to the count value. A second process that counts the size of the received frame for each value of the second bit area, with respect to an encapsulated frame that is a first value and is newly received within a predetermined period;
Run the
Relay system. The relay system according to claim 7, wherein
The bandwidth monitoring unit repeatedly executes the first process, and executes the second process in parallel with the first process.
Relay system. The relay system according to claim 7, wherein
The second process is executed when the count value in the first process exceeds a predetermined reference count value.
Relay system. The relay system according to claim 7, wherein
In the second process, when there is a count value that satisfies a predetermined condition in the second process, the bandwidth monitoring unit further determines the first identifier based on the second value of the second bit area corresponding to the count value. When the value of the first bit area and the value of the second bit area are the first value and the second value, respectively, and the frame is newly received within a predetermined period, the size of the received frame Performing a third process for counting the value for each value of the third bit area,
Relay system. The relay system according to claim 7, wherein
The number of bits of the first identifier is greater than 12 bits;
The number of bits of the first bit area is 12 bits,
The number of bits in the second bit region is 12 bits or less.
Relay system. In the relay system according to any one of claims 7 to 11,
The first identifier is a service instance identifier based on the PBB standard.
Relay system.

Images