JP2003318949A - Vpn system and router - Google Patents

Vpn system and router

Info

Publication number
JP2003318949A
JP2003318949A JP2002118109A JP2002118109A JP2003318949A JP 2003318949 A JP2003318949 A JP 2003318949A JP 2002118109 A JP2002118109 A JP 2002118109A JP 2002118109 A JP2002118109 A JP 2002118109A JP 2003318949 A JP2003318949 A JP 2003318949A
Authority
JP
Japan
Prior art keywords
vpn
router
function
request
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2002118109A
Other languages
Japanese (ja)
Other versions
JP3904968B2 (en
Inventor
Naoaki Yamanaka
直明 山中
Satoshi Okamoto
岡本　　聡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nippon Telegraph and Telephone Corp
Original Assignee
Nippon Telegraph and Telephone Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nippon Telegraph and Telephone Corp filed Critical Nippon Telegraph and Telephone Corp
Priority to JP2002118109A priority Critical patent/JP3904968B2/en
Publication of JP2003318949A publication Critical patent/JP2003318949A/en
Application granted granted Critical
Publication of JP3904968B2 publication Critical patent/JP3904968B2/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Abstract

<P>PROBLEM TO BE SOLVED: To provide a VPN (Virtual Private Network) system and a router wherein a VPN manager immediately revises a topology and a band of a VPN in a network of a network provider. <P>SOLUTION: A router is provided to a route in an IP network configuring the VPN, and a means for managing the IP network and a means for managing the VPN can make settings to the router on the basis of information including a network topology and a transmission band with respect to the VPN and collect management information including communication traffic information and fault information from the router. <P>COPYRIGHT: (C)2004,JPO

Description

【発明の詳細な説明】Detailed Description of the Invention

【０００１】[0001]

【発明の属する技術分野】本発明はＶＰＮ(Virtual Pri
vate Network)およびそれを構成するルータに関する。TECHNICAL FIELD The present invention relates to a VPN (Virtual Principle).
vate Network) and the routers that make it up.

【０００２】[0002]

【従来の技術】ＶＰＮは、公衆ネットワークを利用しな
がら、あたかもプライベートにネットワークを利用して
いるような環境をユーザに提供するサービスである。従
来の技術では、図５に示すように、ユーザが拠点２０と
拠点２３との間でＶＰＮを構成する場合に、拠点２０と
拠点２３との間に専用線２４をネットワークプロバイダ
から借りて接続しＶＰＮを構成するのが一般的である。
この場合に、専用線２４は、ＩＰネットワーク１に設置
されたルータ２１および２２によって設定される。ま
た、ルータ２１および２２は、ＩＰネットワーク１を管
理するネットワークプロバイダの管理システム２によっ
て設定が行われる。2. Description of the Related Art VPN is a service that provides users with an environment as if they were using the network privately while using the public network. In the conventional technology, as shown in FIG. 5, when a user configures a VPN between the bases 20 and 23, a dedicated line 24 is connected between the bases 20 and 23 by borrowing from a network provider. It is common to configure a VPN.
In this case, the private line 24 is set by the routers 21 and 22 installed in the IP network 1. The routers 21 and 22 are set by the management system 2 of the network provider that manages the IP network 1.

【０００３】[0003]

【発明が解決しようとする課題】しかし、このような従
来のＶＰＮでは、ＶＰＮのトポロジの変更や帯域の変更
を行う場合は、ＶＰＮ側からネットワークプロバイダの
ネットワークを制御できないため、ネットワークプロバ
イダに申し込み、このネットワークプロバイダの管理シ
ステムから変更を行う必要があり、即応性に欠けるとい
う問題がある。However, in such a conventional VPN, when changing the topology or bandwidth of the VPN, the VPN side cannot control the network of the network provider, so an application is made to the network provider. Since it is necessary to make changes from the management system of this network provider, there is a problem of lack of responsiveness.

【０００４】本発明は、このような背景に行われたもの
であって、ＶＰＮ管理者が、ネットワークプロバイダの
ネットワーク内でＶＰＮのトポロジの変更や帯域の変更
を即時に行うことができ、さらに、専用線の効率的な運
用により実質的に使用した分のみの専用線料金とするこ
とができ、ネットワークプロバイダは、ネットワーク全
体のリソースが有効に使用されるので、設備投資効果が
大きく、また、１つのルータをＶＰＮ毎の別ルータとし
て見せることによりルータを効率よく運用することがで
きるＶＰＮシステムおよびルータおよびプログラムおよ
び記録媒体を提供することを目的とする。The present invention has been made against such a background, and the VPN administrator can immediately change the topology or bandwidth of the VPN within the network of the network provider, and further, Due to the efficient operation of the leased line, the leased line fee can be used only for what is substantially used, and the network provider can effectively use the resources of the entire network. An object of the present invention is to provide a VPN system, a router, a program, and a recording medium capable of efficiently operating the router by making one router appear as a different router for each VPN.

【０００５】[0005]

【課題を解決するための手段】本発明は、１つまたは複
数のネットワークプロバイダのＩＰネットワークを用い
て構成する１つまたは複数のＶＰＮにおいて、このＶＰ
Ｎを構成する前記ＩＰネットワーク内のルートにルータ
を設け、このルータに対して前記ＩＰネットワークを管
理する手段とともに前記ＶＰＮを管理する手段からも前
記ＶＰＮに関するネットワークトポロジおよび伝送帯域
を含む情報に基づく設定および通信トラヒック情報およ
び障害情報を含む管理情報収集を可能とすることを特徴
とする。SUMMARY OF THE INVENTION The present invention resides in one or more VPNs configured with an IP network of one or more network providers.
A router is provided at a route in the IP network that constitutes N, and a setting based on information including a network topology and a transmission band related to the VPN is also provided from the means for managing the IP network to the router and the means for managing the VPN. It is also characterized by enabling management information collection including communication traffic information and failure information.

【０００６】このように、ＩＰネットワークを管理する
手段とともにＶＰＮを管理する手段からも前記管理情報
収集を行い、当該ＶＰＮを管理する手段において、前記
ＩＰネットワークを管理する手段とは関わり無く、ユー
ザからの設定変更リクエストに対して当該リクエストに
対応可能か否かを収集した前記管理情報から即座に判断
することができる。そして、この判断により、当該リク
エストに対応可能である場合には、ＶＰＮを管理する手
段は、即座に当該リクエストに対応してルータの設定を
変更することができる。As described above, the management information is collected not only from the means for managing the IP network but also the means for managing the VPN, and the means for managing the VPN does not depend on the means for managing the IP network, With respect to the setting change request, it is possible to immediately judge whether or not the request can be dealt with from the management information collected. Then, if it is possible to respond to the request by this determination, the means for managing the VPN can immediately change the setting of the router in response to the request.

【０００７】このように、ＶＰＮを管理する手段が独自
にリクエストに対応できることにより、ユーザからの設
定変更リクエストを即座に実現することができる。ＩＰ
ネットワークを管理する手段は、ＶＰＮを管理する手段
だけでは対応しきれないリクエストが発生した場合につ
いてだけサポートを行うようにＶＰＮシステムを構成す
ればよい。As described above, since the means for managing the VPN can independently handle the request, the setting change request from the user can be immediately realized. IP
As a means for managing the network, the VPN system may be configured so as to support only when a request that cannot be handled by the means for managing the VPN is generated.

【０００８】また、１つまたは複数のＶＰＮで使用する
ＩＰネットワークのＶＰＮを構成するルートに設けたル
ータにおいて、１つまたは複数のＩＰアドレスを持た
せ、この１つまたは複数のＩＰアドレスの個々を前記Ｖ
ＰＮの個々に対応させ、１つまたは複数の入出力ポート
を前記ＶＰＮの個々に対応させて割付け、前記ＶＰＮ個
々の管理システムから前記ＶＰＮ個々に対応した前記Ｉ
Ｐアドレスを用いて前記ＶＰＮ個々に関する設定および
管理情報収集を行うことを特徴とする。[0008] In addition, a router provided at a route which constitutes a VPN of an IP network used by one or more VPNs is provided with one or more IP addresses, and each of the one or more IP addresses is assigned. The V
Each I / O port is assigned to each VPN, and one or a plurality of input / output ports are assigned to each VPN.
It is characterized in that the P address is used to perform setting and management information collection for each VPN.

【０００９】これにより、１つの実際のルータを複数の
仮想的なルータとして機能させることができる。この仮
想的なルータは、実際のルータの能力を超えない範囲内
で、状況に応じて入出力ポート数を増減させたり、処理
能力を増減させることが可能であり、これによっても前
記リクエストに即座に対応することを容易にする。As a result, one actual router can function as a plurality of virtual routers. This virtual router can increase / decrease the number of input / output ports or increase / decrease the processing capacity according to the situation within the range that does not exceed the capacity of the actual router. Make it easy to meet.

【００１０】このようにして、ＶＰＮ管理者が、ネット
ワークプロバイダのネットワーク内でＶＰＮのトポロジ
の変更や帯域の変更を即時に行うことができ、さらに、
専用線の効率的な運用により実質的に使用した分のみの
専用線料金とすることができ、ネットワークプロバイダ
は、ネットワーク全体のリソースが有効に使用されるの
で、設備投資効果が大きく、また、１つのルータをＶＰ
Ｎ毎の別ルータとして見せることによりルータを効率よ
く運用することができる。In this way, the VPN administrator can immediately change the topology of the VPN or change the bandwidth within the network of the network provider.
Due to the efficient operation of the leased line, the leased line fee can be used only for what is substantially used, and the network provider can effectively use the resources of the entire network. One router to VP
The router can be operated efficiently by making it appear as a separate router for each N.

【００１１】すなわち、本発明の第一の観点は、複数の
拠点と、ルータとを備え、このルータは、前記複数の拠
点間にＶＰＮを構成するための専用線を設定する手段を
備えたＶＰＮシステムである。That is, a first aspect of the present invention comprises a plurality of bases and a router, and the router is provided with a means for setting a dedicated line for forming a VPN between the plurality of bases. System.

【００１２】ここで、本発明の特徴とするところは、前
記ＶＰＮを管理する手段が設けられ、この管理する手段
は、当該ＶＰＮに関する通信トラヒック情報および障害
情報を含む管理情報を前記ルータから収集する手段と、
前記拠点からの当該ＶＰＮのネットワークトポロジおよ
び伝送帯域の変更のリクエストを受け付ける手段と、こ
の受け付ける手段が受け付けたリクエストに対応可能か
否かを前記収集する手段により収集した前記管理情報に
基づき判断する手段と、この判断する手段により当該リ
クエストに対応可能と判断されたときには、当該リクエ
ストに基づく当該ＶＰＮのネットワークトポロジおよび
伝送帯域を前記ルータに対して設定する手段とを備えた
ところにある。Here, a feature of the present invention is that means for managing the VPN is provided, and this managing means collects management information including communication traffic information and failure information regarding the VPN from the router. Means and
Means for accepting a request for changing the network topology and transmission band of the VPN from the base, and means for judging whether or not the request accepted by the accepting means can be handled based on the management information collected by the collecting means And a means for setting the network topology and transmission band of the VPN based on the request to the router when the request is determined to be compatible with the request.

【００１３】前記ルータには、Ｎ（Ｎは自然数）個のＩ
Ｐアドレスが割当てられ、一つのＩＰアドレスに対して
一つまたは複数の入出力ポートを割付けることにより前
記ルータをＮ個の仮想的なルータとして機能分割し、当
該仮想的なルータを前記ＶＰＮを構成するために用いる
ルータとして割当てることが望ましい。In the router, N (N is a natural number) I
A P address is assigned, and by assigning one or more input / output ports to one IP address, the router is functionally divided into N virtual routers, and the virtual router is connected to the VPN. It is desirable to assign it as a router used for configuration.

【００１４】また、複数のＶＰＮに対してそれぞれ前記
ＶＰＮを管理する手段が設けられ、前記収集する手段
は、自ＶＰＮに関する前記管理情報を限定して収集し、
他ＶＰＮに関する前記管理情報の収集を禁止する手段を
備えることもできる。Further, means for managing the VPN is provided for each of the plurality of VPNs, and the means for collecting restrictively collects the management information on the own VPN,
It is also possible to provide a means for prohibiting the collection of the management information regarding the other VPN.

【００１５】これによれば、個々のプライベートネット
ワークにおける秘匿性を確保することができる。この場
合でもＩＰネットワークを管理する手段は、全てのＶＰ
Ｎに関する管理情報を収集しており、個々のＶＰＮを管
理する手段が自己が収集した自ＶＰＮ内に限定された管
理情報だけではリクエストの対応に苦慮したときには、
ＩＰネットワークを管理する手段が個々のＶＰＮを管理
する手段をサポートするようにＶＰＮシステムを構成す
ればよい。According to this, it is possible to secure confidentiality in each private network. Even in this case, the means for managing the IP network is all VPs.
When the management information about N is collected and the means for managing each VPN has a difficulty in responding to the request only with the management information limited to the own VPN collected by itself,
The VPN system may be configured so that the means for managing the IP network supports the means for managing the individual VPNs.

【００１６】本発明の第二の観点は、複数の拠点間にＶ
ＰＮを構成するための専用線を設定する手段を備えたル
ータであって、本発明の特徴とするところは、Ｎ個のＩ
Ｐアドレスが割当てられ、一つのＩＰアドレスに対して
一つまたは複数の入出力ポートを割当てることによりＮ
個の仮想的なルータとして機能分割され、当該仮想的な
ルータが前記ＶＰＮを構成するために用いるルータとし
て割当てられるところにある。[0016] A second aspect of the present invention is to connect V points between a plurality of bases.
A router having means for setting a dedicated line for configuring a PN, which is a feature of the present invention, is that N I
P address is assigned, and by assigning one or more input / output ports to one IP address, N
The functions are divided into individual virtual routers, and the virtual routers are assigned as the routers used to configure the VPN.

【００１７】本発明の第三の観点は、情報処理装置にイ
ンストールすることにより、その情報処理装置に、複数
の拠点と、ルータとを備え、このルータは、前記複数の
拠点間にＶＰＮを構成するための専用線を設定する手段
を備えたＶＰＮシステムに適用される装置に相応する機
能を実現させるプログラムである。According to a third aspect of the present invention, the information processing apparatus, when installed in the information processing apparatus, has a plurality of bases and a router, and the router forms a VPN between the plurality of bases. It is a program that realizes a function corresponding to the device applied to the VPN system, which is provided with a means for setting a dedicated line for doing so.

【００１８】ここで、本発明の特徴とするところは、前
記ＶＰＮを管理する機能を実現させ、この管理する機能
として、当該ＶＰＮに関する通信トラヒック情報および
障害情報を含む管理情報を前記ルータから収集する機能
と、前記拠点からの当該ＶＰＮのネットワークトポロジ
および伝送帯域の変更のリクエストを受け付ける機能
と、この受け付ける機能が受け付けたリクエストが実現
可能か否かを前記収集する機能により収集した前記管理
情報に基づき判断する機能と、この判断する機能により
当該リクエストが実現可能と判断されたときには、当該
リクエストに基づく当該ＶＰＮのネットワークトポロジ
および伝送帯域を前記ルータに対して設定する機能とを
実現させるところにある。Here, a feature of the present invention is to realize a function of managing the VPN, and as the function of managing the VPN, management information including communication traffic information and failure information regarding the VPN is collected from the router. Based on the management information collected by the function, the function of receiving a request for changing the network topology and the transmission band of the VPN from the base, and the function of collecting whether the request received by the receiving function is feasible The function of determining and the function of setting the network topology and transmission band of the VPN based on the request to the router when the request is determined to be feasible by the determining function are realized.

【００１９】複数のＶＰＮに対してそれぞれ前記ＶＰＮ
を管理する機能を実現させ、前記収集する機能として、
自ＶＰＮに関する前記管理情報を限定して収集し、他Ｖ
ＰＮに関する前記管理情報の収集を禁止する機能を実現
させることもできる。For each of a plurality of VPNs, the VPN
As a function to realize the function of managing
The management information on the own VPN is limited and collected, and the other V
It is also possible to realize the function of prohibiting the collection of the management information on the PN.

【００２０】本発明の第四の観点は、本発明のプログラ
ムが記録された前記情報処理装置読取可能な記録媒体で
ある。本発明のプログラムは本発明の記録媒体に記録さ
れることにより、前記情報処理装置は、この記録媒体を
用いて本発明のプログラムをインストールすることがで
きる。あるいは、本発明のプログラムを保持するサーバ
からネットワークを介して直接前記情報処理装置に本発
明のプログラムをインストールすることもできる。A fourth aspect of the present invention is a recording medium readable by the information processing device, in which the program of the present invention is recorded. By recording the program of the present invention on the recording medium of the present invention, the information processing apparatus can install the program of the present invention using this recording medium. Alternatively, the program of the present invention can be installed in the information processing apparatus directly from a server holding the program of the present invention via a network.

【００２１】これにより、コンピュータ装置等の情報処
理装置を用いて、ＶＰＮ管理者が、ネットワークプロバ
イダのネットワーク内でＶＰＮのトポロジの変更や帯域
の変更を即時に行うことができ、さらに、専用線の効率
的な運用により実質的に使用した分のみの専用線料金と
することができ、ネットワークプロバイダは、ネットワ
ーク全体のリソースが有効に使用されるので、設備投資
効果が大きく、また、１つのルータをＶＰＮ毎の別ルー
タとして見せることによりルータを効率よく運用するこ
とができるＶＰＮシステムおよびルータを実現すること
ができる。Thus, the VPN administrator can immediately change the VPN topology and the bandwidth within the network of the network provider by using the information processing device such as the computer device. Due to efficient operation, the leased line fee can be used only for what is substantially used, and the network provider can effectively use the resources of the entire network, resulting in a large capital investment effect and the use of one router. It is possible to realize a VPN system and a router that can operate the router efficiently by making them appear as separate routers for each VPN.

【００２２】[0022]

【発明の実施の形態】本発明実施例のＶＰＮシステムを
図１ないし図４を参照して説明する。図１は本実施例の
ＶＰＮシステムの全体構成図である。図２は第一実施例
のトポロジ変更を説明するための図である。図３は本実
施例のルータの構成図である。図４は第三実施例のＶＰ
Ｎの管理システムの動作を示すフローチャートである。DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A VPN system according to an embodiment of the present invention will be described with reference to FIGS. FIG. 1 is an overall configuration diagram of the VPN system of this embodiment. FIG. 2 is a diagram for explaining the topology change of the first embodiment. FIG. 3 is a block diagram of the router of this embodiment. FIG. 4 shows the VP of the third embodiment.
It is a flowchart which shows operation | movement of the management system of N.

【００２３】本実施例は、図１に示すように、複数の拠
点１０−１、１０−２、１１−１、１１−２、１２−
１、１２−２と、ルータ３〜７とを備え、このルータ３
〜７は、複数の拠点１０−１、１０−２、１１−１、１
１−２、１２−１、１２−２の間にＶＰＮを構成するた
めの専用線を設定するＶＰＮシステムである。In this embodiment, as shown in FIG. 1, a plurality of bases 10-1, 10-2, 11-1, 11-2, 12-.
1, 12-2 and routers 3 to 7 are provided.
To 7 are a plurality of bases 10-1, 10-2, 11-1, 1
This is a VPN system in which a dedicated line for configuring a VPN is set between 1-2, 12-1, and 12-2.

【００２４】ここで、本実施例の特徴とするところは、
ＶＰＮを管理する管理システム１０、１１、１２が設け
られ、この管理システム１０、１１、１２は、当該ＶＰ
Ｎに関する通信トラヒック情報および障害情報を含む管
理情報をルータ３〜７から収集し、拠点１０−１、１０
−２、１１−１、１１−２、１２−１、１２−２からの
当該ＶＰＮのネットワークトポロジおよび伝送帯域の変
更のリクエストを受け付け、この受け付けたリクエスト
に対応可能か否かを収集した前記管理情報に基づき判断
し、この判断により当該リクエストに対応可能と判断さ
れたときには、当該リクエストに基づく当該ＶＰＮのネ
ットワークトポロジおよび伝送帯域をルータ３〜７に対
して設定するところにある。Here, the feature of this embodiment is that
Management systems 10, 11 and 12 for managing the VPN are provided, and the management systems 10, 11 and 12 are related to the VP.
Management information including communication traffic information and failure information regarding N is collected from the routers 3 to 7, and the bases 10-1 and 10 are connected.
-2, 11-1, 11-2, 12-1, 12-2 accepts requests to change the network topology and transmission band of the VPN, and manages whether the accepted requests are collected or not. When it is determined based on the information and it is determined that the request can be handled by this determination, the network topology and the transmission band of the VPN based on the request are set in the routers 3 to 7.

【００２５】ルータ３〜７には、図３に示すように、Ｎ
個のＩＰアドレスが割当てられ、一つのＩＰアドレスに
対して一つまたは複数の入出力ポートを割付けることに
よりルータ３〜７をＮ個の仮想ルータ３−１〜３−３、
４−１、５−１、５−２、６−１、６−２、７−１とし
て機能分割し、当該仮想ルータ３−１〜３−３、４−
１、５−１、５−２、６−１、６−２、７−１を前記Ｖ
ＰＮを構成するために用いるルータとして割当てる。As shown in FIG. 3, each of the routers 3 to 7 has N
IP addresses are assigned, and one or a plurality of input / output ports are assigned to one IP address so that the routers 3 to 7 are assigned to N virtual routers 3-1 to 3-3,
Functions are divided as 4-1, 5-1, 5-2, 6-1, 6-2, 7-1, and the virtual routers 3-1 to 3-3, 4-
1, 5-1, 5-2, 6-1, 6-2, 7-1 is the V
It is assigned as the router used to configure the PN.

【００２６】また、図１に示すように、複数のＶＰＮに
対してそれぞれ前記ＶＰＮを管理する管理システム１
０、１１、１２が設けられ、当該管理システム１０、１
１、１２が前記管理情報を収集する際には、自ＶＰＮに
関する前記管理情報を限定して収集し、他ＶＰＮに関す
る前記管理情報の収集を禁止することもできる。このよ
うに、ＶＰＮが複数あるときは、あるＶＰＮの管理シス
テムは他のＶＰＮに関する管理情報を収集することがで
きないように制限を加えてもよい。Further, as shown in FIG. 1, a management system 1 for managing each of a plurality of VPNs.
0, 11, 12 are provided, and the management system 10, 1
When the management information 1 and 12 collect the management information, it is possible to limit the collection of the management information about the own VPN and prohibit the collection of the management information about other VPNs. As described above, when there are a plurality of VPNs, the management system of one VPN may be restricted so that it cannot collect management information about other VPNs.

【００２７】本実施例の管理システム２、１０、１１、
１２は、情報処理装置であるコンピュータ装置を用いて
実現することができる。すなわち、コンピュータ装置に
インストールすることにより、そのコンピュータ装置
に、複数の拠点１０−１、１０−２、１１−１、１１−
２、１２−１、１２−２と、ルータ３〜７とを備え、こ
のルータ３〜７は、複数の拠点１０−１、１０−２、１
１−１、１１−２、１２−１、１２−２の間にＶＰＮを
構成するための専用線を設定するＶＰＮシステムに適用
される装置に相応する機能を実現させるプログラムであ
って、前記ＶＰＮを管理する管理システム１０、１１、
１２に相応する機能を実現させ、この管理システム１
０、１１、１２に相応する機能として、当該ＶＰＮに関
する通信トラヒック情報および障害情報を含む管理情報
をルータ３〜７から収集する機能と、拠点１０−１、１
０−２、１１−１、１１−２、１２−１、１２−２から
の当該ＶＰＮのネットワークトポロジおよび伝送帯域の
変更のリクエストを受け付ける機能と、この受け付ける
機能が受け付けたリクエストに対応可能か否かを前記収
集する機能により収集した前記管理情報に基づき判断す
る機能と、この判断する機能により当該リクエストに対
応可能と判断されたときには、当該リクエストに基づく
当該ＶＰＮのネットワークトポロジおよび伝送帯域を前
記ルータに対して設定する機能とを実現させるプログラ
ムをコンピュータ装置にインストールすることにより、
そのコンピュータ装置を第一実施例の管理システム１
０、１１、１２に相応する装置とすることができる。The management systems 2, 10, 11 of this embodiment
12 can be realized using a computer device which is an information processing device. That is, by installing in a computer device, the computer device has a plurality of locations 10-1, 10-2, 11-1, 11-.
2, 12-1, 12-2 and routers 3-7 are provided, and the routers 3-7 have a plurality of bases 10-1, 10-2, 1
A program that realizes a function corresponding to a device applied to a VPN system that sets a dedicated line for configuring a VPN between 1-1, 11-2, 12-1, and 12-2. Management systems 10, 11 for managing
This management system 1 realizes the function corresponding to 12
As functions corresponding to 0, 11, and 12, a function of collecting management information including communication traffic information and failure information related to the VPN from the routers 3 to 7, and bases 10-1 and 10-1.
0-2, 11-1, 11-2, 12-1, 12-2, a function of accepting a request for changing the network topology and transmission band of the VPN, and whether or not the accepting function can respond to the request accepted The function of determining whether the request is based on the management information collected by the function of collecting, and when the function of judging determines that the request can be handled, the router determines the network topology and transmission band of the VPN based on the request. By installing a program that realizes the function to be set for
The computer device is the management system 1 of the first embodiment.
It can be a device corresponding to 0, 11, 12.

【００２８】あるいは、前記収集する機能として、自Ｖ
ＰＮに関する前記管理情報を限定して収集し、他ＶＰＮ
に関する前記管理情報の収集を禁止する機能を実現させ
るプログラムをコンピュータ装置にインストールするこ
とにより、そのコンピュータ装置を第三実施例の管理シ
ステム１０、１１、１２に相応する装置とすることがで
きる。Alternatively, the self-V
Limit the collection of the management information on the PN to other VPNs
By installing a program that realizes the function of prohibiting the collection of the management information on the computer device, the computer device can be a device corresponding to the management system 10, 11, 12 of the third embodiment.

【００２９】本実施例のプログラムは本実施例の記録媒
体に記録されることにより、コンピュータ装置は、この
記録媒体を用いて本実施例のプログラムをインストール
することができる。あるいは、本実施例のプログラムを
保持するサーバからネットワークを介して直接コンピュ
ータ装置に本実施例のプログラムをインストールするこ
ともできる。By recording the program of this embodiment on the recording medium of this embodiment, the computer device can install the program of this embodiment using this recording medium. Alternatively, the program of this embodiment can be directly installed in a computer device from a server holding the program of this embodiment via a network.

【００３０】これにより、コンピュータ装置を用いて、
ＶＰＮ管理者が、ネットワークプロバイダのネットワー
ク内でＶＰＮのトポロジの変更や帯域の変更を即時に行
うことができ、さらに、専用線の効率的な運用により実
質的に使用した分のみの専用線料金とすることができ、
ネットワークプロバイダは、ネットワーク全体のリソー
スが有効に使用されるので、設備投資効果が大きく、ま
た、１つのルータをＶＰＮ毎の別ルータとして見せるこ
とによりルータを効率よく運用することができるＶＰＮ
システムおよびルータを実現することができる。Thus, using the computer device,
The VPN administrator can immediately change the VPN topology or change the bandwidth within the network of the network provider, and the effective operation of the leased line allows the leased line charges to be substantially used. You can
Since the resources of the entire network are effectively used by the network provider, the capital investment effect is large, and the router can be operated efficiently by making one router appear as another router for each VPN.
A system and a router can be realized.

【００３１】以下では、本実施例をさらに詳細に説明す
る。The present embodiment will be described in more detail below.

【００３２】（第一実施例）第一実施例を図１および図
２を参照して説明する。第一実施例では、本実施例のＶ
ＰＮシステムの概要について説明する。図１の１はＩＰ
ネットワーク、２はＩＰネットワークを管理するネット
ワークプロバイダの管理システム、３、４、５、６、７
はネットワークプロバイダが管理する物理的なルータ、
３−１、３−２、３−３はルータ３を使用するＶＰＮ−
Ａ、ＶＰＮ−Ｂ、ＶＰＮ−Ｃの仮想ルータ、４−１はル
ータ４を使用するＶＰＮ−Ａの仮想ルータ、５−１、５
−２はルータ５を使用するＶＰＮ−Ｂ、ＶＰＮ−Ｃの仮
想ルータ、６−１、６−２はルータ６を使用するＶＰＮ
−ＡおよびＶＰＮ−Ｂの仮想ルータ、７−１はルータ７
を使用するＶＰＮ−Ｃの仮想ルータ、１０はＶＰＮ−Ａ
の管理システム、１０−１、１０−２はＶＰＮ−Ａの拠
点、１１はＶＰＮ−Ｂの管理システム、１１−１、１１
−２はＶＰＮ−Ｂの拠点、１２はＶＰＮ−Ｃの管理シス
テム、１２−１、１２−２はＶＰＮ−Ｃの拠点である。(First Embodiment) A first embodiment will be described with reference to FIGS. 1 and 2. In the first embodiment, V of this embodiment is used.
The outline of the PN system will be described. 1 in FIG. 1 is IP
Network, 2 is a management system of a network provider that manages an IP network, 3, 4, 5, 6, 7
Is a physical router managed by a network provider,
3-1, 3-2, and 3-3 are VPN-s using the router 3.
Virtual routers A, VPN-B, and VPN-C, 4-1 is a virtual router of VPN-A that uses the router 4, 5-1 and 5
-2 is a virtual router of VPN-B and VPN-C using the router 5, 6-1 and 6-2 are VPNs using the router 6.
-A and VPN-B virtual routers, 7-1 is router 7
Virtual router of VPN-C using 10 is VPN-A
Management system, 10-1 and 10-2 are VPN-A bases, 11 is a VPN-B management system, 11-1 and 11
Reference numeral -2 is a VPN-B base, 12 is a VPN-C management system, and 12-1 and 12-2 are VPN-C bases.

【００３３】一例として、ＶＰＮ−Ａが拠点１０−１と
拠点１０−２との間に３Ｍｂ／ｓの専用線をＩＰネット
ワーク１を管理するネットワークプロバイダへ申し込む
と、ネットワークプロバイダは管理システム２からルー
タ３、４、６に対して帯域３Ｍｂ／ｓ、使用ポート番
号、ＩＰアドレスを設定し、ルータ３、４、６の間の専
用線を形成してその結果をＶＰＮ−Ａに通知する。As an example, when the VPN-A applies a 3 Mb / s leased line between the base 10-1 and the base 10-2 to the network provider managing the IP network 1, the network provider causes the network provider to switch from the management system 2 to the router. A band 3 Mb / s, a port number used, and an IP address are set for 3, 4, and 6, a dedicated line is formed between the routers 3, 4, and 6 and the result is notified to the VPN-A.

【００３４】その後、ＶＰＮ−Ａが帯域を５Ｍｂ／ｓに
変更したい場合は、管理システム１０から仮想ルータ３
−１、４−１、６−１に対して帯域５Ｍｂ／ｓを設定す
ることができる。このように、ルータ３、４、６の間に
帯域の余裕があれば、ＶＰＮ−Ａの帯域を５Ｍｂ／ｓへ
拡大することがＶＰＮ−Ａ自身から簡単に設定できる。After that, when the VPN-A wants to change the bandwidth to 5 Mb / s, the management system 10 sends the virtual router 3
A band of 5 Mb / s can be set for -1, 4-1, and 6-1. In this way, if there is a margin of bandwidth between the routers 3, 4, and 6, the VPN-A itself can easily set the bandwidth of the VPN-A to 5 Mb / s.

【００３５】管理システム２では、各ルータから管理情
報を収集して使用状況を常に把握しており、ＶＰＮ−Ａ
が帯域を３Ｍｂ／ｓから５Ｍｂ／ｓへ変更したことを知
ることができる。さらにＶＰＮ−Ａで帯域の増加が必要
になった場合には、ルータ３と４との間の伝送路容量に
余裕がない場合は、図２の破線で示すように、トポロジ
を変更して専用線の一部をルータ３、５、６間で設定
し、要求する帯域を確保することができる。同様にＶＰ
Ｎ−Ｂ、ＶＰＮ−ＣもＩＰネットワーク１に専用線を形
成した後、帯域の変更やトポロジの変更を自身の管理シ
ステム１１、１２からそれぞれ行うことができる。The management system 2 collects management information from each router to constantly grasp the usage status, and the VPN-A
Can change the band from 3 Mb / s to 5 Mb / s. Further, if the bandwidth needs to be increased in VPN-A, and there is no margin in the transmission path capacity between the routers 3 and 4, the topology is changed and dedicated as shown by the broken line in FIG. A part of the line can be set between the routers 3, 5, and 6 to secure the required bandwidth. Similarly VP
N-B and VPN-C can also change the bandwidth and the topology from their own management systems 11 and 12, respectively, after forming a dedicated line in the IP network 1.

【００３６】第一実施例では、各管理システム１０、１
１、１２がそれぞれ全ＶＰＮの管理情報を把握してお
り、各管理システム１０、１１、１２が全仮想ルータ３
−１〜３−３、４−１、５−１、５−２、６−１、６−
２、７−１にわたって設定を行うことができる。In the first embodiment, each management system 10, 1
Each of the management systems 10, 11 and 12 knows the management information of all the VPNs.
-1 to 3-3, 4-1, 5-1, 5-2, 6-1, 6-
Settings can be made over 2, 7-1.

【００３７】したがって、第一実施例における管理シス
テム２は、ＩＰネットワーク全体を監視し、各管理シス
テム１０、１１、１２が対応困難な不測の事態が発生し
た場合にのみサポートを行うように構成される。これに
より、実質的なＶＰＮシステムの運用の殆どは各管理シ
ステム１０、１１、１２により行うことができる。Therefore, the management system 2 in the first embodiment is configured to monitor the entire IP network and provide support only when an unexpected situation in which each management system 10, 11, 12 is difficult to handle occurs. It As a result, most of the actual operation of the VPN system can be performed by the management systems 10, 11 and 12.

【００３８】（第二実施例）第二実施例を図３を参照し
て説明する。第二実施例では、本実施例のルータについ
て説明する。Ｐ１〜Ｐ８は入出力ポートである。本ルー
タには、ＶＰＮ−Ａ用のＩＰアドレスＩＰ−Ａ（例え
ば、１２８．１９．２５４．７）、ＶＰＮ−Ｂ用のＩＰ
アドレスＩＰ−Ｂ（例えば、１２８．１９．２５４．
９）、ＶＰＮ−Ｃ用のＩＰアドレスＩＰ−Ｃ（例えば、
１２８．１９．２５４．１６）が割当てられている。Ｖ
ＰＮ−Ａは入力ポートＰ１、出力ポートＰ５を用いて２
Ｇｂ／ｓ分を、ＶＰＮ−Ｂは入力ポートＰ２、Ｐ３、出
力ポートＰ６、Ｐ７を用いて６Ｇｂ／ｓ分を、ＶＰＮ−
Ｃは入力ポートＰ４、出力ポートＰ８を用いて１Ｇｂ／
ｓ分を使用している。次のノードとの伝送容量は１０Ｇ
ｂ／ｓ分が確保されている。(Second Embodiment) A second embodiment will be described with reference to FIG. In the second embodiment, the router of this embodiment will be described. P1 to P8 are input / output ports. This router has an IP address IP-A for VPN-A (for example, 128.19.254.7) and an IP for VPN-B.
Address IP-B (eg, 128.19.254.
9), IP address IP-C for VPN-C (for example,
128.19.254.16) is assigned. V
PN-A uses input port P1 and output port P5 for 2
Gb / s is used for VPN-B, and 6 Gb / s is used for VPN-B using input ports P2 and P3 and output ports P6 and P7.
C uses the input port P4 and the output port P8 to achieve 1 Gb /
s minutes are used. The transmission capacity with the next node is 10G
b / s is secured.

【００３９】いまＶＰＮ−Ｃが伝送帯域を１Ｇｂ／ｓか
ら２Ｇｂ／ｓに変更した場合には、ＶＰＮ−Ｃの管理シ
ステム１２はＩＰアドレスＩＰ−ＣのＯＳＰＦ(Open Sh
ortest Path First)パケットを送出して仮想ルータ３−
３、５−２、７−１に伝送帯域の拡大を指示する。When the VPN-C changes the transmission band from 1 Gb / s to 2 Gb / s, the management system 12 of the VPN-C uses the OSPF (Open Sh) of the IP address IP-C.
ortest Path First) packet is sent to the virtual router 3-
It instructs 3, 5-2 and 7-1 to expand the transmission band.

【００４０】仮想ルータ３−３、５−２、７−１ではＩ
ＰアドレスＩＰ−Ｃから自分へのパケットでかつＶＰＮ
−Ｃ用のものであることを判別し、パケットの内容を解
釈して、１Ｇｂ／ｓ分の帯域増加要求であることを知
る。要求の実行が可能かを判別して可能であれば、１Ｇ
ｂ／ｓ分の増加を行い、実施結果を送信元ＩＰアドレス
をＩＰ−ＣとしてＯＳＰＦパケットによりＶＰＮ−Ｃの
管理システム１２へ返す。同様にＶＰＮ−ＡおよびＢに
おいても仮想ルータへの指示はＩＰアドレスをＩＰ−Ａ
としたＯＳＰＦパケットにより行うことができる。In the virtual routers 3-3, 5-2, 7-1, I
Packet from P-address IP-C to itself and VPN
-C is determined, the contents of the packet are interpreted, and it is known that the bandwidth increase request is 1 Gb / s. Determine if the request can be executed and if possible, 1G
It is increased by b / s, and the execution result is returned to the management system 12 of the VPN-C by an OSPF packet with the source IP address as IP-C. Similarly, in VPN-A and B, the instruction to the virtual router is to change the IP address to IP-A.
Can be performed by the OSPF packet.

【００４１】このように、１つのルータにＶＰＮ対応に
ＩＰアドレスを持たせることにより、ＶＰＮ毎に制御す
ることができ、かつ他のＶＰＮからの制御を受けないた
め、１つのルータをＶＰＮ毎の仮想ルータとして見せる
ことができる利点がある。As described above, by giving one router an IP address corresponding to the VPN, it is possible to control each VPN and receive no control from other VPNs. It has the advantage that it can be viewed as a virtual router.

【００４２】（第三実施例）第三実施例を図４を参照し
て説明する。第三実施例では、ＶＰＮにおける管理情報
の収集を当該ＶＰＮの管理システムに限定し、他ＶＰＮ
の当該管理情報の収集を禁止することにより、各ＶＰＮ
間の秘匿性を向上させることができる。この場合でもＩ
Ｐネットワークの管理システム２では、全ＶＰＮの管理
情報を収集しており、個々のＶＰＮの管理システム１
０、１１、１２が自己が収集した自ＶＰＮ内に限定され
た管理情報だけではリクエストの対応に苦慮したときに
は、ＩＰネットワークの管理システム２が個々のＶＰＮ
の管理システム１０、１１、１２をサポートするように
ＶＰＮシステムを構成する。(Third Embodiment) A third embodiment will be described with reference to FIG. In the third embodiment, collection of management information in a VPN is limited to the management system of the VPN, and other VPNs
By prohibiting the collection of relevant management information of each VPN,
It is possible to improve the confidentiality of the space. Even in this case I
The management system 2 of the P network collects management information of all VPNs and manages the management system 1 of each VPN.
When the management information 0, 11, 12 has difficulty in responding to the request only with the management information limited to the own VPN collected by itself, the management system 2 of the IP network uses the individual VPNs.
The VPN system is configured to support the management systems 10, 11 and 12 of FIG.

【００４３】すなわち、第三実施例では、図４に示すよ
うに、リクエストを受け付け（ステップ１）、自ＶＰＮ
内で収集した管理情報に基づき、そのリクエストに自仮
想ルータのみで対応できるか否か判断し（ステップ
２）、対応できない場合には、ＩＰネットワークの管理
システム２に対して対応を依頼する（ステップ３）。ま
た、対応できる場合には、リクエスト対応処置を施す
（ステップ４）。That is, in the third embodiment, as shown in FIG. 4, the request is accepted (step 1) and the own VPN is used.
Based on the management information collected in the server, it is judged whether or not the request can be handled only by the own virtual router (step 2). 3). If the request can be dealt with, a request handling procedure is performed (step 4).

【００４４】図２の例では、ＶＰＮ−Ａで帯域の増加が
必要になった場合に、ルータ３と４との間の伝送路容量
に余裕がなく、トポロジを変更して専用線の一部をルー
タ３、５、６間で設定しているが、このような場合に
は、管理システム１０は、もはや自仮想ルータ３−１、
４−１、６−１のみではリクエストに対応できず、管理
システム２にリクエストへの対応を依頼する。In the example of FIG. 2, when the bandwidth needs to be increased in the VPN-A, there is no margin in the transmission path capacity between the routers 3 and 4, and the topology is changed to make a part of the leased line. Is set between the routers 3, 5, and 6, but in such a case, the management system 10 no longer has its own virtual router 3-1,
The request cannot be handled by only 4-1 and 6-1 and the management system 2 is requested to handle the request.

【００４５】したがって、第三実施例における管理シス
テム２は、ＩＰネットワーク全体を監視し、各管理シス
テム１０、１１、１２からの依頼に応じて各管理システ
ム１０、１１、１２と協調してリクエストに対応するよ
うに構成される。これにより、第一実施例と比較する
と、ＶＰＮシステムの運用の一部を管理システム２が担
う割合が大きくなるが、各ＶＰＮ間の秘匿性が向上する
とともに、管理システム１０、１１、１２間のネットワ
ークトポロジおよび伝送帯域の設定における競合が発生
した場合に、これを管理システム２により調停すること
ができる。Therefore, the management system 2 in the third embodiment monitors the entire IP network and responds to the requests from the management systems 10, 11, 12 in cooperation with the management systems 10, 11, 12 to make a request. Configured to correspond. As a result, as compared with the first embodiment, the management system 2 plays a larger proportion of a part of the operation of the VPN system, but the confidentiality between the VPNs is improved and the management systems 10, 11, 12 are connected. When a conflict occurs in the setting of the network topology and the transmission band, this can be arbitrated by the management system 2.

【００４６】（実施例まとめ）本実施例のＶＰＮシステ
ムでは、ＶＰＮ管理者は、ＶＰＮの管理システム１０、
１１、１２から容易に帯域の変更やトポロジの変更がで
きるため専用線の効率的な運用ができ、実質的に使用し
た分のみの専用線料金とすることができる利点がある。
また、ネットワークプロバイダは、専用線の運用を各Ｖ
ＰＮの管理システム１０、１１、１２に任せることがで
きるとともに、ネットワーク全体のリソースが有効に使
用されるので、設備投資効果が大きい利点がある。(Summary of Embodiments) In the VPN system of this embodiment, the VPN administrator is the VPN management system 10,
Since it is possible to easily change the band and the topology from 11 and 12, there is an advantage that the dedicated line can be efficiently operated and the leased line fee can be substantially used.
In addition, the network provider must operate the dedicated line for each V
Since the PN management systems 10, 11 and 12 can be entrusted to the resources, and the resources of the entire network are effectively used, there is an advantage that the capital investment effect is great.

【００４７】また、１つのルータにＶＰＮ対応にＩＰア
ドレスを持たせることにより、ＶＰＮ毎に制御すること
ができ、かつ他のＶＰＮからの制御を受けないため、１
つのルータをＶＰＮ毎の別ルータとして見せることがで
きる利点がある。Further, by giving one router an IP address corresponding to the VPN, it is possible to control for each VPN and not to be controlled by another VPN.
There is an advantage that one router can be made to appear as another router for each VPN.

【００４８】[0048]

【発明の効果】以上説明したように、本発明によれば、
ＶＰＮ管理者が、ネットワークプロバイダのネットワー
ク内でＶＰＮのトポロジの変更や帯域の変更を即時に行
うことができる。さらに、ＶＰＮ管理者は、専用線の効
率的な運用により実質的に使用した分のみの専用線料金
とすることができる。また、ネットワークプロバイダ
は、ネットワーク全体のリソースが有効に使用されるの
で設備投資効果が大きく、また、１つのルータをＶＰＮ
毎の別ルータとして見せることによりルータを効率よく
運用することができる。As described above, according to the present invention,
The VPN administrator can immediately change the VPN topology or the bandwidth within the network of the network provider. Further, the VPN administrator can set the leased line fee for only the amount used substantially by the efficient operation of the leased line. In addition, the network provider can use the resources of the entire network effectively, so that the capital investment effect is great, and one router can be used as a VPN.
By showing each router as a separate router, the router can be operated efficiently.

【図面の簡単な説明】[Brief description of drawings]

【図１】本実施例のＶＰＮシステムの全体構成図。FIG. 1 is an overall configuration diagram of a VPN system of this embodiment.

【図２】第一実施例のトポロジ変更を説明するための
図。FIG. 2 is a diagram for explaining a topology change of the first embodiment.

【図３】本実施例のルータの構成図。FIG. 3 is a configuration diagram of a router of this embodiment.

【図４】第三実施例のＶＰＮの管理システムの動作を示
すフローチャート。FIG. 4 is a flowchart showing the operation of the VPN management system of the third embodiment.

【図５】従来技術によるＶＰＮシステム構成例を示す
図。FIG. 5 is a diagram showing an example of a VPN system configuration according to a conventional technique.

【符号の説明】 １ ＩＰネットワーク ２、１０、１１、１２ 管理システム ３〜７、２１、２２ ルータ ３−１〜３−３、４−１、５−１、５−２、６−１、６
−２、７−１ 仮想ルータ １０−１、１０−２、１１−１、１１−２、１２−１、
１２−２、２０、２３拠点 ２４ 専用線[Description of Reference Signs] 1 IP network 2, 10, 11, 12 Management system 3 to 7, 21, 22 Router 3-1 to 3-3, 4-1, 5-1, 5-2, 6-1, 6
-2, 7-1 Virtual routers 10-1, 10-2, 11-1, 11-2, 12-1,
12-2, 20, 23 Location 24 Dedicated line

Claims (7)

【特許請求の範囲】[Claims] 【請求項１】 複数の拠点と、ルータとを備え、このル
ータは、前記複数の拠点間にＶＰＮ(Virtual Private N
etwork)を構成するための専用線を設定する手段を備え
たＶＰＮシステムにおいて、 前記ＶＰＮを管理する手段が設けられ、 この管理する手段は、 当該ＶＰＮに関する通信トラヒック情報および障害情報
を含む管理情報を前記ルータから収集する手段と、 前記拠点からの当該ＶＰＮのネットワークトポロジおよ
び伝送帯域の変更のリクエストを受け付ける手段と、 この受け付ける手段が受け付けたリクエストに対応可能
か否かを前記収集する手段により収集した前記管理情報
に基づき判断する手段と、 この判断する手段により当該リクエストに対応可能と判
断されたときには、当該リクエストに基づく当該ＶＰＮ
のネットワークトポロジおよび伝送帯域を前記ルータに
対して設定する手段とを備えたことを特徴とするＶＰＮ
システム。1. A plurality of bases and a router are provided, and the router has a VPN (Virtual Private N) between the plurality of bases.
In the VPN system provided with means for setting a dedicated line for configuring the network, there is provided means for managing the VPN, and this managing means provides management information including communication traffic information and failure information about the VPN. The means for collecting from the router, the means for accepting a request for changing the network topology and the transmission band of the VPN from the base, and the means for collecting whether or not the request accepted by the accepting means can be handled A means for judging based on the management information and a VPN based on the request when the judging means judges that the request can be handled.
And a means for setting the network topology and the transmission band of the router to the router.
system. 【請求項２】 前記ルータには、Ｎ（Ｎは自然数）個の
ＩＰアドレスが割当てられ、 一つのＩＰアドレスに対して一つまたは複数の入出力ポ
ートを割付けることにより前記ルータをＮ個の仮想的な
ルータとして機能分割し、 当該仮想的なルータを前記ＶＰＮを構成するために用い
るルータとして割当てる請求項１記載のＶＰＮシステ
ム。2. N (N is a natural number) IP addresses are assigned to the router, and one or a plurality of input / output ports are assigned to one IP address so that the router has N addresses. The VPN system according to claim 1, wherein the function is divided as a virtual router, and the virtual router is assigned as a router used to configure the VPN. 【請求項３】 複数のＶＰＮに対してそれぞれ前記ＶＰ
Ｎを管理する手段が設けられ、 前記収集する手段は、自ＶＰＮに関する前記管理情報を
限定して収集し、他ＶＰＮに関する前記管理情報の収集
を禁止する手段を備えた請求項１または２記載のＶＰＮ
システム。3. The VP for each of a plurality of VPNs
The means for managing N is provided, and the means for collecting comprises means for collecting the management information on the own VPN in a limited manner and for prohibiting the collection of the management information on other VPNs. VPN
system. 【請求項４】 複数の拠点間にＶＰＮを構成するための
専用線を設定する手段を備えたルータにおいて、 Ｎ個のＩＰアドレスが割当てられ、 一つのＩＰアドレスに対して一つまたは複数の入出力ポ
ートを割当てることによりＮ個の仮想的なルータとして
機能分割され、 当該仮想的なルータが前記ＶＰＮを構成するために用い
るルータとして割当てられることを特徴とするルータ。4. A router having means for setting a dedicated line for configuring a VPN between a plurality of bases, N IP addresses are allocated, and one or a plurality of input addresses are assigned to one IP address. A router characterized by being functionally divided into N virtual routers by allocating output ports, and the virtual routers are allocated as routers used to configure the VPN. 【請求項５】 情報処理装置にインストールすることに
より、その情報処理装置に、複数の拠点と、ルータとを
備え、このルータは、前記複数の拠点間にＶＰＮを構成
するための専用線を設定する手段を備えたＶＰＮシステ
ムに適用される装置に相応する機能を実現させるプログ
ラムにおいて、 前記ＶＰＮを管理する機能を実現させ、 この管理する機能として、 当該ＶＰＮに関する通信トラヒック情報および障害情報
を含む管理情報を前記ルータから収集する機能と、 前記拠点からの当該ＶＰＮのネットワークトポロジおよ
び伝送帯域の変更のリクエストを受け付ける機能と、 この受け付ける機能が受け付けたリクエストに対応可能
か否かを前記収集する機能により収集した前記管理情報
に基づき判断する機能と、 この判断する機能により当該リクエストに対応可能と判
断されたときには、当該リクエストに基づく当該ＶＰＮ
のネットワークトポロジおよび伝送帯域を前記ルータに
対して設定する機能とを実現させることを特徴とするプ
ログラム。5. The information processing device, when installed in the information processing device, includes a plurality of bases and a router, and the router sets a dedicated line for configuring a VPN between the plurality of bases. In a program that realizes a function corresponding to a device applied to a VPN system that includes a means for controlling the VPN, a function that manages the VPN is realized, and a management including communication traffic information and failure information regarding the VPN is performed as the managing function. With the function of collecting information from the router, the function of receiving a request for changing the network topology and transmission band of the VPN from the base, and the function of collecting whether or not the received function can handle the received request. By the function that makes a judgment based on the management information collected and the function that makes this judgment When it is determined that the request can be handled, the VPN based on the request
And a function for setting the network topology and the transmission band for the router. 【請求項６】 複数のＶＰＮに対してそれぞれ前記ＶＰ
Ｎを管理する機能を実現させ、 前記収集する機能として、自ＶＰＮに関する前記管理情
報を限定して収集し、他ＶＰＮに関する前記管理情報の
収集を禁止する機能を実現させる請求項５記載のプログ
ラム。6. The VP for each of a plurality of VPNs
The program according to claim 5, wherein a function of managing N is realized, and as the collecting function, a function of collecting the management information regarding the own VPN in a limited manner and prohibiting the collection of the management information regarding another VPN is realized. 【請求項７】 請求項５または６記載のプログラムが記
録された前記情報処理装置読み取り可能な記録媒体。7. A recording medium readable by the information processing device, in which the program according to claim 5 or 6 is recorded.
JP2002118109A 2002-04-19 2002-04-19 VPN system and router Expired - Fee Related JP3904968B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2002118109A JP3904968B2 (en) 2002-04-19 2002-04-19 VPN system and router

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2002118109A JP3904968B2 (en) 2002-04-19 2002-04-19 VPN system and router

Publications (2)

Publication Number Publication Date
JP2003318949A true JP2003318949A (en) 2003-11-07
JP3904968B2 JP3904968B2 (en) 2007-04-11

Family

ID=29535107

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2002118109A Expired - Fee Related JP3904968B2 (en) 2002-04-19 2002-04-19 VPN system and router

Country Status (1)

Country Link
JP (1) JP3904968B2 (en)

Cited By (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005203984A (en) * 2004-01-14 2005-07-28 Nec Corp System, method, and program for network management, and recording medium
GB2431816A (en) * 2005-10-31 2007-05-02 Agilent Technologies Inc Discovering and providing near real-time updates of virtual private networks (VPN) topologies
JP2008502190A (en) * 2004-06-04 2008-01-24 ノキア インコーポレイテッド A system for geographically distributed virtual routing
KR100861592B1 (en) 2006-12-01 2008-10-07 한국전자통신연구원 Method and apparatus for managing fault in customer network management system
WO2010093369A1 (en) * 2009-02-16 2010-08-19 Qualitest Technologies, Inc. Communications-network data processing methods, communications-network data processing systems, computer-readable storage media, communications-network data presentation methods, and communications-network data presentation systems
JP2011228864A (en) * 2010-04-16 2011-11-10 Nippon Telegr & Teleph Corp <Ntt> Traffic control instruction apparatus, traffic control instruction program, traffic control instruction system, and traffic control instruction method
JP2012525017A (en) * 2009-04-01 2012-10-18 ニシラ ネットワークス， インコーポレイテッド Method and apparatus for implementing and managing virtual switches
JP2014131347A (en) * 2009-10-07 2014-07-10 Nec Corp Information system, control server, virtual network management method and program
US8830835B2 (en) 2011-08-17 2014-09-09 Nicira, Inc. Generating flows for managed interconnection switches
US8880468B2 (en) 2010-07-06 2014-11-04 Nicira, Inc. Secondary storage architecture for a network control system that utilizes a primary network information base
US8913611B2 (en) 2011-11-15 2014-12-16 Nicira, Inc. Connection identifier assignment and source network address translation
US8958298B2 (en) 2011-08-17 2015-02-17 Nicira, Inc. Centralized logical L3 routing
US8964528B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Method and apparatus for robust packet distribution among hierarchical managed switching elements
US9043452B2 (en) 2011-05-04 2015-05-26 Nicira, Inc. Network control apparatus and method for port isolation
US9083609B2 (en) 2007-09-26 2015-07-14 Nicira, Inc. Network operating system for managing and securing networks
US9137107B2 (en) 2011-10-25 2015-09-15 Nicira, Inc. Physical controllers for converting universal flows
US9154433B2 (en) 2011-10-25 2015-10-06 Nicira, Inc. Physical controller
US9203701B2 (en) 2011-10-25 2015-12-01 Nicira, Inc. Network virtualization apparatus and method with scheduling capabilities
US9225597B2 (en) 2014-03-14 2015-12-29 Nicira, Inc. Managed gateways peering with external router to attract ingress packets
US9288104B2 (en) 2011-10-25 2016-03-15 Nicira, Inc. Chassis controllers for converting universal flows
US9313129B2 (en) 2014-03-14 2016-04-12 Nicira, Inc. Logical router processing by network controller
US9385954B2 (en) 2014-03-31 2016-07-05 Nicira, Inc. Hashing techniques for use in a network environment
US9407580B2 (en) 2013-07-12 2016-08-02 Nicira, Inc. Maintaining data stored with a packet
US9413644B2 (en) 2014-03-27 2016-08-09 Nicira, Inc. Ingress ECMP in virtual distributed routing environment
US9419855B2 (en) 2014-03-14 2016-08-16 Nicira, Inc. Static routes for logical routers
US9503371B2 (en) 2013-09-04 2016-11-22 Nicira, Inc. High availability L3 gateways for logical networks
US9503321B2 (en) 2014-03-21 2016-11-22 Nicira, Inc. Dynamic routing for logical routers
US9525647B2 (en) 2010-07-06 2016-12-20 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US9548924B2 (en) 2013-12-09 2017-01-17 Nicira, Inc. Detecting an elephant flow based on the size of a packet
US9569368B2 (en) 2013-12-13 2017-02-14 Nicira, Inc. Installing and managing flows in a flow table cache
US9571386B2 (en) 2013-07-08 2017-02-14 Nicira, Inc. Hybrid packet processing
US9575782B2 (en) 2013-10-13 2017-02-21 Nicira, Inc. ARP for logical router
US9577845B2 (en) 2013-09-04 2017-02-21 Nicira, Inc. Multiple active L3 gateways for logical networks
US9590901B2 (en) 2014-03-14 2017-03-07 Nicira, Inc. Route advertisement by managed gateways
US9602398B2 (en) 2013-09-15 2017-03-21 Nicira, Inc. Dynamically generating flows with wildcard fields
US9647883B2 (en) 2014-03-21 2017-05-09 Nicria, Inc. Multiple levels of logical routers
US9680750B2 (en) 2010-07-06 2017-06-13 Nicira, Inc. Use of tunnels to hide network addresses
US9768980B2 (en) 2014-09-30 2017-09-19 Nicira, Inc. Virtual distributed bridging
US9887960B2 (en) 2013-08-14 2018-02-06 Nicira, Inc. Providing services for logical networks
US9893988B2 (en) 2014-03-27 2018-02-13 Nicira, Inc. Address resolution using multiple designated instances of a logical router
US9952885B2 (en) 2013-08-14 2018-04-24 Nicira, Inc. Generation of configuration files for a DHCP module executing within a virtualized container
US9967199B2 (en) 2013-12-09 2018-05-08 Nicira, Inc. Inspecting operations of a machine to detect elephant flows
US9996467B2 (en) 2013-12-13 2018-06-12 Nicira, Inc. Dynamically adjusting the number of flows allowed in a flow table cache
US10020960B2 (en) 2014-09-30 2018-07-10 Nicira, Inc. Virtual distributed bridging
US10033579B2 (en) 2012-04-18 2018-07-24 Nicira, Inc. Using transactions to compute and propagate network forwarding state
US10038628B2 (en) 2015-04-04 2018-07-31 Nicira, Inc. Route server mode for dynamic routing between logical and physical networks
US10057157B2 (en) 2015-08-31 2018-08-21 Nicira, Inc. Automatically advertising NAT routes between logical routers
US10063458B2 (en) 2013-10-13 2018-08-28 Nicira, Inc. Asymmetric connection with external networks
US10079779B2 (en) 2015-01-30 2018-09-18 Nicira, Inc. Implementing logical router uplinks
US10091161B2 (en) 2016-04-30 2018-10-02 Nicira, Inc. Assignment of router ID for logical routers
US10095535B2 (en) 2015-10-31 2018-10-09 Nicira, Inc. Static route types for logical routers
US10103939B2 (en) 2010-07-06 2018-10-16 Nicira, Inc. Network control apparatus and method for populating logical datapath sets
US10129142B2 (en) 2015-08-11 2018-11-13 Nicira, Inc. Route configuration for logical router
US10153973B2 (en) 2016-06-29 2018-12-11 Nicira, Inc. Installation of routing tables for logical router in route server mode
US10181993B2 (en) 2013-07-12 2019-01-15 Nicira, Inc. Tracing network packets through logical and physical networks
US10193806B2 (en) 2014-03-31 2019-01-29 Nicira, Inc. Performing a finishing operation to improve the quality of a resulting hash
US10200306B2 (en) 2017-03-07 2019-02-05 Nicira, Inc. Visualization of packet tracing operation results
US10204122B2 (en) 2015-09-30 2019-02-12 Nicira, Inc. Implementing an interface between tuple and message-driven control entities
US10212071B2 (en) 2016-12-21 2019-02-19 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10225184B2 (en) 2015-06-30 2019-03-05 Nicira, Inc. Redirecting traffic in a virtual distributed router environment
US10237123B2 (en) 2016-12-21 2019-03-19 Nicira, Inc. Dynamic recovery from a split-brain failure in edge nodes
US10250443B2 (en) 2014-09-30 2019-04-02 Nicira, Inc. Using physical location to modify behavior of a distributed virtual network element
US10333849B2 (en) 2016-04-28 2019-06-25 Nicira, Inc. Automatic configuration of logical routers on edge nodes
US10341236B2 (en) 2016-09-30 2019-07-02 Nicira, Inc. Anycast edge service gateways
US10374827B2 (en) 2017-11-14 2019-08-06 Nicira, Inc. Identifier that maps to different networks at different datacenters
US10454758B2 (en) 2016-08-31 2019-10-22 Nicira, Inc. Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP
US10469342B2 (en) 2014-10-10 2019-11-05 Nicira, Inc. Logical network traffic analysis
US10484515B2 (en) 2016-04-29 2019-11-19 Nicira, Inc. Implementing logical metadata proxy servers in logical networks
US10498638B2 (en) 2013-09-15 2019-12-03 Nicira, Inc. Performing a multi-stage lookup to classify packets
US10511458B2 (en) 2014-09-30 2019-12-17 Nicira, Inc. Virtual distributed bridging
US10511459B2 (en) 2017-11-14 2019-12-17 Nicira, Inc. Selection of managed forwarding element for bridge spanning multiple datacenters
US10560320B2 (en) 2016-06-29 2020-02-11 Nicira, Inc. Ranking of gateways in cluster
US10608887B2 (en) 2017-10-06 2020-03-31 Nicira, Inc. Using packet tracing tool to automatically execute packet capture operations
US10616045B2 (en) 2016-12-22 2020-04-07 Nicira, Inc. Migration of centralized routing components of logical router
US10659373B2 (en) 2014-03-31 2020-05-19 Nicira, Inc Processing packets according to hierarchy of flow entry storages
US10742746B2 (en) 2016-12-21 2020-08-11 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10797998B2 (en) 2018-12-05 2020-10-06 Vmware, Inc. Route server for distributed routers using hierarchical routing protocol
US10841273B2 (en) 2016-04-29 2020-11-17 Nicira, Inc. Implementing logical DHCP servers in logical networks
US10931560B2 (en) 2018-11-23 2021-02-23 Vmware, Inc. Using route type to determine routing protocol behavior
US10938788B2 (en) 2018-12-12 2021-03-02 Vmware, Inc. Static routes for policy-based VPN
US11019167B2 (en) 2016-04-29 2021-05-25 Nicira, Inc. Management of update queues for network controller
US11095480B2 (en) 2019-08-30 2021-08-17 Vmware, Inc. Traffic optimization using distributed edge services
US11178051B2 (en) 2014-09-30 2021-11-16 Vmware, Inc. Packet key parser for flow-based forwarding elements
US11196628B1 (en) 2020-07-29 2021-12-07 Vmware, Inc. Monitoring container clusters
US11201808B2 (en) 2013-07-12 2021-12-14 Nicira, Inc. Tracing logical network packets through physical network
US11336533B1 (en) 2021-01-08 2022-05-17 Vmware, Inc. Network visualization of correlations between logical elements and associated physical elements
US11451413B2 (en) 2020-07-28 2022-09-20 Vmware, Inc. Method for advertising availability of distributed gateway service and machines at host computer
US11558426B2 (en) 2020-07-29 2023-01-17 Vmware, Inc. Connection tracking for container cluster
US11570090B2 (en) 2020-07-29 2023-01-31 Vmware, Inc. Flow tracing operation in container cluster
US11606294B2 (en) 2020-07-16 2023-03-14 Vmware, Inc. Host computer configured to facilitate distributed SNAT service
US11611613B2 (en) 2020-07-24 2023-03-21 Vmware, Inc. Policy-based forwarding to a load balancer of a load balancing cluster
US11616755B2 (en) 2020-07-16 2023-03-28 Vmware, Inc. Facilitating distributed SNAT service
US11677645B2 (en) 2021-09-17 2023-06-13 Vmware, Inc. Traffic monitoring
US11687210B2 (en) 2021-07-05 2023-06-27 Vmware, Inc. Criteria-based expansion of group nodes in a network topology visualization
US11711278B2 (en) 2021-07-24 2023-07-25 Vmware, Inc. Visualization of flow trace operation across multiple sites
US11736436B2 (en) 2020-12-31 2023-08-22 Vmware, Inc. Identifying routes with indirect addressing in a datacenter
US11902050B2 (en) 2020-07-28 2024-02-13 VMware LLC Method for providing distributed gateway service at host computer
US11924080B2 (en) 2020-01-17 2024-03-05 VMware LLC Practical overlay network latency measurement in datacenter

Cited By (272)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4650607B2 (en) * 2004-01-14 2011-03-16 日本電気株式会社 Network management system, network management method, and network management program
JP2005203984A (en) * 2004-01-14 2005-07-28 Nec Corp System, method, and program for network management, and recording medium
JP2008502190A (en) * 2004-06-04 2008-01-24 ノキア インコーポレイテッド A system for geographically distributed virtual routing
JP4657294B2 (en) * 2004-06-04 2011-03-23 ノキア インコーポレイテッド A system for geographically distributed virtual routing
GB2431816A (en) * 2005-10-31 2007-05-02 Agilent Technologies Inc Discovering and providing near real-time updates of virtual private networks (VPN) topologies
KR100861592B1 (en) 2006-12-01 2008-10-07 한국전자통신연구원 Method and apparatus for managing fault in customer network management system
US9876672B2 (en) 2007-09-26 2018-01-23 Nicira, Inc. Network operating system for managing and securing networks
US9083609B2 (en) 2007-09-26 2015-07-14 Nicira, Inc. Network operating system for managing and securing networks
US11683214B2 (en) 2007-09-26 2023-06-20 Nicira, Inc. Network operating system for managing and securing networks
US10749736B2 (en) 2007-09-26 2020-08-18 Nicira, Inc. Network operating system for managing and securing networks
WO2010093369A1 (en) * 2009-02-16 2010-08-19 Qualitest Technologies, Inc. Communications-network data processing methods, communications-network data processing systems, computer-readable storage media, communications-network data presentation methods, and communications-network data presentation systems
US8589542B2 (en) 2009-02-16 2013-11-19 Qualitest Technologies, Inc. First application receiving text script or application program interface (API) call from second application and executing applications in independent memory spaces
US10931600B2 (en) 2009-04-01 2021-02-23 Nicira, Inc. Method and apparatus for implementing and managing virtual switches
US11425055B2 (en) 2009-04-01 2022-08-23 Nicira, Inc. Method and apparatus for implementing and managing virtual switches
US8966035B2 (en) 2009-04-01 2015-02-24 Nicira, Inc. Method and apparatus for implementing and managing distributed virtual switches in several hosts and physical forwarding elements
JP2012525017A (en) * 2009-04-01 2012-10-18 ニシラ ネットワークス， インコーポレイテッド Method and apparatus for implementing and managing virtual switches
US9590919B2 (en) 2009-04-01 2017-03-07 Nicira, Inc. Method and apparatus for implementing and managing virtual switches
US11381455B2 (en) 2009-10-07 2022-07-05 Nec Corporation Information system, control server, virtual network management method, and program
US9794124B2 (en) 2009-10-07 2017-10-17 Nec Corporation Information system, control server, virtual network management method, and program
JP2014131347A (en) * 2009-10-07 2014-07-10 Nec Corp Information system, control server, virtual network management method and program
US9148342B2 (en) 2009-10-07 2015-09-29 Nec Corporation Information system, control server, virtual network management method, and program
JP2011228864A (en) * 2010-04-16 2011-11-10 Nippon Telegr & Teleph Corp <Ntt> Traffic control instruction apparatus, traffic control instruction program, traffic control instruction system, and traffic control instruction method
US9049153B2 (en) 2010-07-06 2015-06-02 Nicira, Inc. Logical packet processing pipeline that retains state information to effectuate efficient processing of packets
US10326660B2 (en) 2010-07-06 2019-06-18 Nicira, Inc. Network virtualization apparatus and method
US8964598B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Mesh architectures for managed switching elements
US9008087B2 (en) 2010-07-06 2015-04-14 Nicira, Inc. Processing requests in a network control system with multiple controller instances
US9007903B2 (en) 2010-07-06 2015-04-14 Nicira, Inc. Managing a network by controlling edge and non-edge switching elements
US11743123B2 (en) 2010-07-06 2023-08-29 Nicira, Inc. Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches
US9306875B2 (en) 2010-07-06 2016-04-05 Nicira, Inc. Managed switch architectures for implementing logical datapath sets
US11641321B2 (en) 2010-07-06 2023-05-02 Nicira, Inc. Packet processing for logical datapath sets
US9680750B2 (en) 2010-07-06 2017-06-13 Nicira, Inc. Use of tunnels to hide network addresses
US9077664B2 (en) 2010-07-06 2015-07-07 Nicira, Inc. One-hop packet processing in a network with managed switching elements
US10038597B2 (en) 2010-07-06 2018-07-31 Nicira, Inc. Mesh architectures for managed switching elements
US9106587B2 (en) 2010-07-06 2015-08-11 Nicira, Inc. Distributed network control system with one master controller per managed switching element
US9112811B2 (en) 2010-07-06 2015-08-18 Nicira, Inc. Managed switching elements used as extenders
US10103939B2 (en) 2010-07-06 2018-10-16 Nicira, Inc. Network control apparatus and method for populating logical datapath sets
US8966040B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Use of network information base structure to establish communication between applications
US8964528B2 (en) 2010-07-06 2015-02-24 Nicira, Inc. Method and apparatus for robust packet distribution among hierarchical managed switching elements
US11876679B2 (en) 2010-07-06 2024-01-16 Nicira, Inc. Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances
US9172663B2 (en) 2010-07-06 2015-10-27 Nicira, Inc. Method and apparatus for replicating network information base in a distributed network control system with multiple controller instances
US10320585B2 (en) 2010-07-06 2019-06-11 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US9692655B2 (en) 2010-07-06 2017-06-27 Nicira, Inc. Packet processing in a network with hierarchical managed switching elements
US10686663B2 (en) 2010-07-06 2020-06-16 Nicira, Inc. Managed switch architectures: software managed switches, hardware managed switches, and heterogeneous managed switches
US8958292B2 (en) 2010-07-06 2015-02-17 Nicira, Inc. Network control apparatus and method with port security controls
US10021019B2 (en) 2010-07-06 2018-07-10 Nicira, Inc. Packet processing for logical datapath sets
US8959215B2 (en) 2010-07-06 2015-02-17 Nicira, Inc. Network virtualization
US11677588B2 (en) 2010-07-06 2023-06-13 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US9231891B2 (en) 2010-07-06 2016-01-05 Nicira, Inc. Deployment of hierarchical managed switching elements
US9525647B2 (en) 2010-07-06 2016-12-20 Nicira, Inc. Network control apparatus and method for creating and modifying logical switching elements
US11223531B2 (en) 2010-07-06 2022-01-11 Nicira, Inc. Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances
US8913483B2 (en) 2010-07-06 2014-12-16 Nicira, Inc. Fault tolerant managed switching element architecture
US11979280B2 (en) 2010-07-06 2024-05-07 Nicira, Inc. Network control apparatus and method for populating logical datapath sets
US8880468B2 (en) 2010-07-06 2014-11-04 Nicira, Inc. Secondary storage architecture for a network control system that utilizes a primary network information base
US11509564B2 (en) 2010-07-06 2022-11-22 Nicira, Inc. Method and apparatus for replicating network information base in a distributed network control system with multiple controller instances
US9391928B2 (en) 2010-07-06 2016-07-12 Nicira, Inc. Method and apparatus for interacting with a network information base in a distributed network control system with multiple controller instances
US9300603B2 (en) 2010-07-06 2016-03-29 Nicira, Inc. Use of rich context tags in logical data processing
US11539591B2 (en) 2010-07-06 2022-12-27 Nicira, Inc. Distributed network control system with one master controller per logical datapath set
US9363210B2 (en) 2010-07-06 2016-06-07 Nicira, Inc. Distributed network control system with one master controller per logical datapath set
US9043452B2 (en) 2011-05-04 2015-05-26 Nicira, Inc. Network control apparatus and method for port isolation
US9444651B2 (en) 2011-08-17 2016-09-13 Nicira, Inc. Flow generation from second level controller to first level controller to managed switching element
US9209998B2 (en) 2011-08-17 2015-12-08 Nicira, Inc. Packet processing in managed interconnection switching elements
US8830835B2 (en) 2011-08-17 2014-09-09 Nicira, Inc. Generating flows for managed interconnection switches
US8958298B2 (en) 2011-08-17 2015-02-17 Nicira, Inc. Centralized logical L3 routing
US9319375B2 (en) 2011-08-17 2016-04-19 Nicira, Inc. Flow templating in logical L3 routing
US9350696B2 (en) 2011-08-17 2016-05-24 Nicira, Inc. Handling NAT in logical L3 routing
US9356906B2 (en) 2011-08-17 2016-05-31 Nicira, Inc. Logical L3 routing with DHCP
US10027584B2 (en) 2011-08-17 2018-07-17 Nicira, Inc. Distributed logical L3 routing
US9369426B2 (en) 2011-08-17 2016-06-14 Nicira, Inc. Distributed logical L3 routing
US8964767B2 (en) 2011-08-17 2015-02-24 Nicira, Inc. Packet processing in federated network
US10091028B2 (en) 2011-08-17 2018-10-02 Nicira, Inc. Hierarchical controller clusters for interconnecting two or more logical datapath sets
US9407599B2 (en) 2011-08-17 2016-08-02 Nicira, Inc. Handling NAT migration in logical L3 routing
US9288081B2 (en) 2011-08-17 2016-03-15 Nicira, Inc. Connecting unmanaged segmented networks by managing interconnection switching elements
US11804987B2 (en) 2011-08-17 2023-10-31 Nicira, Inc. Flow generation from second level controller to first level controller to managed switching element
US9059999B2 (en) 2011-08-17 2015-06-16 Nicira, Inc. Load balancing in a logical pipeline
US9276897B2 (en) 2011-08-17 2016-03-01 Nicira, Inc. Distributed logical L3 routing
US9137052B2 (en) 2011-08-17 2015-09-15 Nicira, Inc. Federating interconnection switching element network to two or more levels
US9461960B2 (en) 2011-08-17 2016-10-04 Nicira, Inc. Logical L3 daemon
US10193708B2 (en) 2011-08-17 2019-01-29 Nicira, Inc. Multi-domain interconnect
US10931481B2 (en) 2011-08-17 2021-02-23 Nicira, Inc. Multi-domain interconnect
US11695695B2 (en) 2011-08-17 2023-07-04 Nicira, Inc. Logical L3 daemon
US9185069B2 (en) 2011-08-17 2015-11-10 Nicira, Inc. Handling reverse NAT in logical L3 routing
US10868761B2 (en) 2011-08-17 2020-12-15 Nicira, Inc. Logical L3 daemon
US9203701B2 (en) 2011-10-25 2015-12-01 Nicira, Inc. Network virtualization apparatus and method with scheduling capabilities
US9319336B2 (en) 2011-10-25 2016-04-19 Nicira, Inc. Scheduling distribution of logical control plane data
US10505856B2 (en) 2011-10-25 2019-12-10 Nicira, Inc. Chassis controller
US9178833B2 (en) 2011-10-25 2015-11-03 Nicira, Inc. Chassis controller
US9231882B2 (en) 2011-10-25 2016-01-05 Nicira, Inc. Maintaining quality of service in shared forwarding elements managed by a network control system
US9154433B2 (en) 2011-10-25 2015-10-06 Nicira, Inc. Physical controller
US9137107B2 (en) 2011-10-25 2015-09-15 Nicira, Inc. Physical controllers for converting universal flows
US9246833B2 (en) 2011-10-25 2016-01-26 Nicira, Inc. Pull-based state dissemination between managed forwarding elements
US9602421B2 (en) 2011-10-25 2017-03-21 Nicira, Inc. Nesting transaction updates to minimize communication
US9253109B2 (en) 2011-10-25 2016-02-02 Nicira, Inc. Communication channel for distributed network control system
US9288104B2 (en) 2011-10-25 2016-03-15 Nicira, Inc. Chassis controllers for converting universal flows
US9407566B2 (en) 2011-10-25 2016-08-02 Nicira, Inc. Distributed network control system
US9300593B2 (en) 2011-10-25 2016-03-29 Nicira, Inc. Scheduling distribution of logical forwarding plane data
US9306864B2 (en) 2011-10-25 2016-04-05 Nicira, Inc. Scheduling distribution of physical control plane data
US11669488B2 (en) 2011-10-25 2023-06-06 Nicira, Inc. Chassis controller
US9319337B2 (en) 2011-10-25 2016-04-19 Nicira, Inc. Universal physical control plane
US9319338B2 (en) 2011-10-25 2016-04-19 Nicira, Inc. Tunnel creation
US9954793B2 (en) 2011-10-25 2018-04-24 Nicira, Inc. Chassis controller
US10191763B2 (en) 2011-11-15 2019-01-29 Nicira, Inc. Architecture of networks with middleboxes
US10884780B2 (en) 2011-11-15 2021-01-05 Nicira, Inc. Architecture of networks with middleboxes
US10949248B2 (en) 2011-11-15 2021-03-16 Nicira, Inc. Load balancing and destination network address translation middleboxes
US11372671B2 (en) 2011-11-15 2022-06-28 Nicira, Inc. Architecture of networks with middleboxes
US10310886B2 (en) 2011-11-15 2019-06-04 Nicira, Inc. Network control system for configuring middleboxes
US10514941B2 (en) 2011-11-15 2019-12-24 Nicira, Inc. Load balancing and destination network address translation middleboxes
US10235199B2 (en) 2011-11-15 2019-03-19 Nicira, Inc. Migrating middlebox state for distributed middleboxes
US9195491B2 (en) 2011-11-15 2015-11-24 Nicira, Inc. Migrating middlebox state for distributed middleboxes
US9172603B2 (en) 2011-11-15 2015-10-27 Nicira, Inc. WAN optimizer for logical networks
US9558027B2 (en) 2011-11-15 2017-01-31 Nicira, Inc. Network control system for configuring middleboxes
US11593148B2 (en) 2011-11-15 2023-02-28 Nicira, Inc. Network control system for configuring middleboxes
US8913611B2 (en) 2011-11-15 2014-12-16 Nicira, Inc. Connection identifier assignment and source network address translation
US8966024B2 (en) 2011-11-15 2015-02-24 Nicira, Inc. Architecture of networks with middleboxes
US10922124B2 (en) 2011-11-15 2021-02-16 Nicira, Inc. Network control system for configuring middleboxes
US9306909B2 (en) 2011-11-15 2016-04-05 Nicira, Inc. Connection identifier assignment and source network address translation
US9697030B2 (en) 2011-11-15 2017-07-04 Nicira, Inc. Connection identifier assignment and source network address translation
US9552219B2 (en) 2011-11-15 2017-01-24 Nicira, Inc. Migrating middlebox state for distributed middleboxes
US8966029B2 (en) 2011-11-15 2015-02-24 Nicira, Inc. Network control system for configuring middleboxes
US10089127B2 (en) 2011-11-15 2018-10-02 Nicira, Inc. Control plane interface for logical middlebox services
US11740923B2 (en) 2011-11-15 2023-08-29 Nicira, Inc. Architecture of networks with middleboxes
US9015823B2 (en) 2011-11-15 2015-04-21 Nicira, Inc. Firewalls in logical networks
US9697033B2 (en) 2011-11-15 2017-07-04 Nicira, Inc. Architecture of networks with middleboxes
US10977067B2 (en) 2011-11-15 2021-04-13 Nicira, Inc. Control plane interface for logical middlebox services
US10033579B2 (en) 2012-04-18 2018-07-24 Nicira, Inc. Using transactions to compute and propagate network forwarding state
US10135676B2 (en) 2012-04-18 2018-11-20 Nicira, Inc. Using transactions to minimize churn in a distributed network control system
US9571386B2 (en) 2013-07-08 2017-02-14 Nicira, Inc. Hybrid packet processing
US10033640B2 (en) 2013-07-08 2018-07-24 Nicira, Inc. Hybrid packet processing
US10680948B2 (en) 2013-07-08 2020-06-09 Nicira, Inc. Hybrid packet processing
US10181993B2 (en) 2013-07-12 2019-01-15 Nicira, Inc. Tracing network packets through logical and physical networks
US10778557B2 (en) 2013-07-12 2020-09-15 Nicira, Inc. Tracing network packets through logical and physical networks
US9407580B2 (en) 2013-07-12 2016-08-02 Nicira, Inc. Maintaining data stored with a packet
US11201808B2 (en) 2013-07-12 2021-12-14 Nicira, Inc. Tracing logical network packets through physical network
US11695730B2 (en) 2013-08-14 2023-07-04 Nicira, Inc. Providing services for logical networks
US9952885B2 (en) 2013-08-14 2018-04-24 Nicira, Inc. Generation of configuration files for a DHCP module executing within a virtualized container
US10764238B2 (en) 2013-08-14 2020-09-01 Nicira, Inc. Providing services for logical networks
US9887960B2 (en) 2013-08-14 2018-02-06 Nicira, Inc. Providing services for logical networks
US10003534B2 (en) 2013-09-04 2018-06-19 Nicira, Inc. Multiple active L3 gateways for logical networks
US9503371B2 (en) 2013-09-04 2016-11-22 Nicira, Inc. High availability L3 gateways for logical networks
US9577845B2 (en) 2013-09-04 2017-02-21 Nicira, Inc. Multiple active L3 gateways for logical networks
US10389634B2 (en) 2013-09-04 2019-08-20 Nicira, Inc. Multiple active L3 gateways for logical networks
US10382324B2 (en) 2013-09-15 2019-08-13 Nicira, Inc. Dynamically generating flows with wildcard fields
US10498638B2 (en) 2013-09-15 2019-12-03 Nicira, Inc. Performing a multi-stage lookup to classify packets
US9602398B2 (en) 2013-09-15 2017-03-21 Nicira, Inc. Dynamically generating flows with wildcard fields
US9977685B2 (en) 2013-10-13 2018-05-22 Nicira, Inc. Configuration of logical router
US9785455B2 (en) 2013-10-13 2017-10-10 Nicira, Inc. Logical router
US11029982B2 (en) 2013-10-13 2021-06-08 Nicira, Inc. Configuration of logical router
US10528373B2 (en) 2013-10-13 2020-01-07 Nicira, Inc. Configuration of logical router
US10063458B2 (en) 2013-10-13 2018-08-28 Nicira, Inc. Asymmetric connection with external networks
US9575782B2 (en) 2013-10-13 2017-02-21 Nicira, Inc. ARP for logical router
US9910686B2 (en) 2013-10-13 2018-03-06 Nicira, Inc. Bridging between network segments with a logical router
US10693763B2 (en) 2013-10-13 2020-06-23 Nicira, Inc. Asymmetric connection with external networks
US11539630B2 (en) 2013-12-09 2022-12-27 Nicira, Inc. Inspecting operations of a machine to detect elephant flows
US10158538B2 (en) 2013-12-09 2018-12-18 Nicira, Inc. Reporting elephant flows to a network controller
US9838276B2 (en) 2013-12-09 2017-12-05 Nicira, Inc. Detecting an elephant flow based on the size of a packet
US10666530B2 (en) 2013-12-09 2020-05-26 Nicira, Inc Detecting and handling large flows
US9967199B2 (en) 2013-12-09 2018-05-08 Nicira, Inc. Inspecting operations of a machine to detect elephant flows
US11811669B2 (en) 2013-12-09 2023-11-07 Nicira, Inc. Inspecting operations of a machine to detect elephant flows
US9548924B2 (en) 2013-12-09 2017-01-17 Nicira, Inc. Detecting an elephant flow based on the size of a packet
US11095536B2 (en) 2013-12-09 2021-08-17 Nicira, Inc. Detecting and handling large flows
US10193771B2 (en) 2013-12-09 2019-01-29 Nicira, Inc. Detecting and handling elephant flows
US9996467B2 (en) 2013-12-13 2018-06-12 Nicira, Inc. Dynamically adjusting the number of flows allowed in a flow table cache
US9569368B2 (en) 2013-12-13 2017-02-14 Nicira, Inc. Installing and managing flows in a flow table cache
US10380019B2 (en) 2013-12-13 2019-08-13 Nicira, Inc. Dynamically adjusting the number of flows allowed in a flow table cache
US9313129B2 (en) 2014-03-14 2016-04-12 Nicira, Inc. Logical router processing by network controller
US9590901B2 (en) 2014-03-14 2017-03-07 Nicira, Inc. Route advertisement by managed gateways
US10164881B2 (en) 2014-03-14 2018-12-25 Nicira, Inc. Route advertisement by managed gateways
US11025543B2 (en) 2014-03-14 2021-06-01 Nicira, Inc. Route advertisement by managed gateways
US9225597B2 (en) 2014-03-14 2015-12-29 Nicira, Inc. Managed gateways peering with external router to attract ingress packets
US10110431B2 (en) 2014-03-14 2018-10-23 Nicira, Inc. Logical router processing by network controller
US10567283B2 (en) 2014-03-14 2020-02-18 Nicira, Inc. Route advertisement by managed gateways
US9419855B2 (en) 2014-03-14 2016-08-16 Nicira, Inc. Static routes for logical routers
US11252024B2 (en) 2014-03-21 2022-02-15 Nicira, Inc. Multiple levels of logical routers
US9647883B2 (en) 2014-03-21 2017-05-09 Nicria, Inc. Multiple levels of logical routers
US10411955B2 (en) 2014-03-21 2019-09-10 Nicira, Inc. Multiple levels of logical routers
US9503321B2 (en) 2014-03-21 2016-11-22 Nicira, Inc. Dynamic routing for logical routers
US9413644B2 (en) 2014-03-27 2016-08-09 Nicira, Inc. Ingress ECMP in virtual distributed routing environment
US11736394B2 (en) 2014-03-27 2023-08-22 Nicira, Inc. Address resolution using multiple designated instances of a logical router
US11190443B2 (en) 2014-03-27 2021-11-30 Nicira, Inc. Address resolution using multiple designated instances of a logical router
US9893988B2 (en) 2014-03-27 2018-02-13 Nicira, Inc. Address resolution using multiple designated instances of a logical router
US11431639B2 (en) 2014-03-31 2022-08-30 Nicira, Inc. Caching of service decisions
US10659373B2 (en) 2014-03-31 2020-05-19 Nicira, Inc Processing packets according to hierarchy of flow entry storages
US9385954B2 (en) 2014-03-31 2016-07-05 Nicira, Inc. Hashing techniques for use in a network environment
US10193806B2 (en) 2014-03-31 2019-01-29 Nicira, Inc. Performing a finishing operation to improve the quality of a resulting hash
US10511458B2 (en) 2014-09-30 2019-12-17 Nicira, Inc. Virtual distributed bridging
US10020960B2 (en) 2014-09-30 2018-07-10 Nicira, Inc. Virtual distributed bridging
US11483175B2 (en) 2014-09-30 2022-10-25 Nicira, Inc. Virtual distributed bridging
US9768980B2 (en) 2014-09-30 2017-09-19 Nicira, Inc. Virtual distributed bridging
US10250443B2 (en) 2014-09-30 2019-04-02 Nicira, Inc. Using physical location to modify behavior of a distributed virtual network element
US11252037B2 (en) 2014-09-30 2022-02-15 Nicira, Inc. Using physical location to modify behavior of a distributed virtual network element
US11178051B2 (en) 2014-09-30 2021-11-16 Vmware, Inc. Packet key parser for flow-based forwarding elements
US10469342B2 (en) 2014-10-10 2019-11-05 Nicira, Inc. Logical network traffic analysis
US11128550B2 (en) 2014-10-10 2021-09-21 Nicira, Inc. Logical network traffic analysis
US11283731B2 (en) 2015-01-30 2022-03-22 Nicira, Inc. Logical router with multiple routing components
US11799800B2 (en) 2015-01-30 2023-10-24 Nicira, Inc. Logical router with multiple routing components
US10700996B2 (en) 2015-01-30 2020-06-30 Nicira, Inc Logical router with multiple routing components
US10079779B2 (en) 2015-01-30 2018-09-18 Nicira, Inc. Implementing logical router uplinks
US10129180B2 (en) 2015-01-30 2018-11-13 Nicira, Inc. Transit logical switch within logical router
US11601362B2 (en) 2015-04-04 2023-03-07 Nicira, Inc. Route server mode for dynamic routing between logical and physical networks
US10038628B2 (en) 2015-04-04 2018-07-31 Nicira, Inc. Route server mode for dynamic routing between logical and physical networks
US10652143B2 (en) 2015-04-04 2020-05-12 Nicira, Inc Route server mode for dynamic routing between logical and physical networks
US11050666B2 (en) 2015-06-30 2021-06-29 Nicira, Inc. Intermediate logical interfaces in a virtual distributed router environment
US10348625B2 (en) 2015-06-30 2019-07-09 Nicira, Inc. Sharing common L2 segment in a virtual distributed router environment
US10225184B2 (en) 2015-06-30 2019-03-05 Nicira, Inc. Redirecting traffic in a virtual distributed router environment
US10693783B2 (en) 2015-06-30 2020-06-23 Nicira, Inc. Intermediate logical interfaces in a virtual distributed router environment
US11799775B2 (en) 2015-06-30 2023-10-24 Nicira, Inc. Intermediate logical interfaces in a virtual distributed router environment
US10361952B2 (en) 2015-06-30 2019-07-23 Nicira, Inc. Intermediate logical interfaces in a virtual distributed router environment
US10805212B2 (en) 2015-08-11 2020-10-13 Nicira, Inc. Static route configuration for logical router
US11533256B2 (en) 2015-08-11 2022-12-20 Nicira, Inc. Static route configuration for logical router
US10230629B2 (en) 2015-08-11 2019-03-12 Nicira, Inc. Static route configuration for logical router
US10129142B2 (en) 2015-08-11 2018-11-13 Nicira, Inc. Route configuration for logical router
US10075363B2 (en) 2015-08-31 2018-09-11 Nicira, Inc. Authorization for advertised routes among logical routers
US11425021B2 (en) 2015-08-31 2022-08-23 Nicira, Inc. Authorization for advertised routes among logical routers
US10057157B2 (en) 2015-08-31 2018-08-21 Nicira, Inc. Automatically advertising NAT routes between logical routers
US10601700B2 (en) 2015-08-31 2020-03-24 Nicira, Inc. Authorization for advertised routes among logical routers
US11288249B2 (en) 2015-09-30 2022-03-29 Nicira, Inc. Implementing an interface between tuple and message-driven control entities
US10204122B2 (en) 2015-09-30 2019-02-12 Nicira, Inc. Implementing an interface between tuple and message-driven control entities
US11593145B2 (en) 2015-10-31 2023-02-28 Nicira, Inc. Static route types for logical routers
US10795716B2 (en) 2015-10-31 2020-10-06 Nicira, Inc. Static route types for logical routers
US10095535B2 (en) 2015-10-31 2018-10-09 Nicira, Inc. Static route types for logical routers
US10333849B2 (en) 2016-04-28 2019-06-25 Nicira, Inc. Automatic configuration of logical routers on edge nodes
US11502958B2 (en) 2016-04-28 2022-11-15 Nicira, Inc. Automatic configuration of logical routers on edge nodes
US10805220B2 (en) 2016-04-28 2020-10-13 Nicira, Inc. Automatic configuration of logical routers on edge nodes
US11019167B2 (en) 2016-04-29 2021-05-25 Nicira, Inc. Management of update queues for network controller
US10841273B2 (en) 2016-04-29 2020-11-17 Nicira, Inc. Implementing logical DHCP servers in logical networks
US11855959B2 (en) 2016-04-29 2023-12-26 Nicira, Inc. Implementing logical DHCP servers in logical networks
US10484515B2 (en) 2016-04-29 2019-11-19 Nicira, Inc. Implementing logical metadata proxy servers in logical networks
US11601521B2 (en) 2016-04-29 2023-03-07 Nicira, Inc. Management of update queues for network controller
US10091161B2 (en) 2016-04-30 2018-10-02 Nicira, Inc. Assignment of router ID for logical routers
US11418445B2 (en) 2016-06-29 2022-08-16 Nicira, Inc. Installation of routing tables for logical router in route server mode
US10560320B2 (en) 2016-06-29 2020-02-11 Nicira, Inc. Ranking of gateways in cluster
US10749801B2 (en) 2016-06-29 2020-08-18 Nicira, Inc. Installation of routing tables for logical router in route server mode
US10153973B2 (en) 2016-06-29 2018-12-11 Nicira, Inc. Installation of routing tables for logical router in route server mode
US11539574B2 (en) 2016-08-31 2022-12-27 Nicira, Inc. Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP
US10454758B2 (en) 2016-08-31 2019-10-22 Nicira, Inc. Edge node cluster network redundancy and fast convergence using an underlay anycast VTEP IP
US10341236B2 (en) 2016-09-30 2019-07-02 Nicira, Inc. Anycast edge service gateways
US10911360B2 (en) 2016-09-30 2021-02-02 Nicira, Inc. Anycast edge service gateways
US11665242B2 (en) 2016-12-21 2023-05-30 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10742746B2 (en) 2016-12-21 2020-08-11 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10212071B2 (en) 2016-12-21 2019-02-19 Nicira, Inc. Bypassing a load balancer in a return path of network traffic
US10237123B2 (en) 2016-12-21 2019-03-19 Nicira, Inc. Dynamic recovery from a split-brain failure in edge nodes
US10645204B2 (en) 2016-12-21 2020-05-05 Nicira, Inc Dynamic recovery from a split-brain failure in edge nodes
US10616045B2 (en) 2016-12-22 2020-04-07 Nicira, Inc. Migration of centralized routing components of logical router
US11115262B2 (en) 2016-12-22 2021-09-07 Nicira, Inc. Migration of centralized routing components of logical router
US11336590B2 (en) 2017-03-07 2022-05-17 Nicira, Inc. Visualization of path between logical network endpoints
US10200306B2 (en) 2017-03-07 2019-02-05 Nicira, Inc. Visualization of packet tracing operation results
US10805239B2 (en) 2017-03-07 2020-10-13 Nicira, Inc. Visualization of path between logical network endpoints
US10608887B2 (en) 2017-10-06 2020-03-31 Nicira, Inc. Using packet tracing tool to automatically execute packet capture operations
US10374827B2 (en) 2017-11-14 2019-08-06 Nicira, Inc. Identifier that maps to different networks at different datacenters
US10511459B2 (en) 2017-11-14 2019-12-17 Nicira, Inc. Selection of managed forwarding element for bridge spanning multiple datacenters
US11336486B2 (en) 2017-11-14 2022-05-17 Nicira, Inc. Selection of managed forwarding element for bridge spanning multiple datacenters
US10931560B2 (en) 2018-11-23 2021-02-23 Vmware, Inc. Using route type to determine routing protocol behavior
US10797998B2 (en) 2018-12-05 2020-10-06 Vmware, Inc. Route server for distributed routers using hierarchical routing protocol
US10938788B2 (en) 2018-12-12 2021-03-02 Vmware, Inc. Static routes for policy-based VPN
US11095480B2 (en) 2019-08-30 2021-08-17 Vmware, Inc. Traffic optimization using distributed edge services
US11159343B2 (en) 2019-08-30 2021-10-26 Vmware, Inc. Configuring traffic optimization using distributed edge services
US11924080B2 (en) 2020-01-17 2024-03-05 VMware LLC Practical overlay network latency measurement in datacenter
US11616755B2 (en) 2020-07-16 2023-03-28 Vmware, Inc. Facilitating distributed SNAT service
US11606294B2 (en) 2020-07-16 2023-03-14 Vmware, Inc. Host computer configured to facilitate distributed SNAT service
US11611613B2 (en) 2020-07-24 2023-03-21 Vmware, Inc. Policy-based forwarding to a load balancer of a load balancing cluster
US11902050B2 (en) 2020-07-28 2024-02-13 VMware LLC Method for providing distributed gateway service at host computer
US11451413B2 (en) 2020-07-28 2022-09-20 Vmware, Inc. Method for advertising availability of distributed gateway service and machines at host computer
US11570090B2 (en) 2020-07-29 2023-01-31 Vmware, Inc. Flow tracing operation in container cluster
US11196628B1 (en) 2020-07-29 2021-12-07 Vmware, Inc. Monitoring container clusters
US11558426B2 (en) 2020-07-29 2023-01-17 Vmware, Inc. Connection tracking for container cluster
US11736436B2 (en) 2020-12-31 2023-08-22 Vmware, Inc. Identifying routes with indirect addressing in a datacenter
US11336533B1 (en) 2021-01-08 2022-05-17 Vmware, Inc. Network visualization of correlations between logical elements and associated physical elements
US11848825B2 (en) 2021-01-08 2023-12-19 Vmware, Inc. Network visualization of correlations between logical elements and associated physical elements
US11687210B2 (en) 2021-07-05 2023-06-27 Vmware, Inc. Criteria-based expansion of group nodes in a network topology visualization
US11711278B2 (en) 2021-07-24 2023-07-25 Vmware, Inc. Visualization of flow trace operation across multiple sites
US11855862B2 (en) 2021-09-17 2023-12-26 Vmware, Inc. Tagging packets for monitoring and analysis
US11706109B2 (en) 2021-09-17 2023-07-18 Vmware, Inc. Performance of traffic monitoring actions
US11677645B2 (en) 2021-09-17 2023-06-13 Vmware, Inc. Traffic monitoring

Also Published As

Publication number Publication date
JP3904968B2 (en) 2007-04-11

Similar Documents

Publication Publication Date Title
JP3904968B2 (en) VPN system and router
US11689497B2 (en) Auto deploying network for virtual private cloud with heterogenous workloads
US7379987B2 (en) Integrated service management system
US7693980B2 (en) Integrated service management system
US7174390B2 (en) Address resolution protocol system and method in a virtual network
US9276827B2 (en) Allocating computing resources based upon geographic movement
CN111478852B (en) Route advertisement for managed gateways
US20030154236A1 (en) Database Switch enabling a database area network
US20070233825A1 (en) Reconfigurable, virtual processing system, cluster, network and method
US20060107108A1 (en) Service clusters and method in a processing system with failover capability
JP2005506726A (en) Virtual network system and method in processing system
JP2000312226A (en) Method for warranting communication quality
JP2004048125A (en) Connection control, device method therefor, and program thereof
JP3792707B2 (en) Data communication load distribution control program and data load distribution control method
JP3609948B2 (en) Multiprotocol network management method, multiprotocol network management proxy server system, multiprotocol address management server system, and multiprotocol network management system
JP6422345B2 (en) Management device, management system, management method, and program
JP3708444B2 (en) Multiprocessor information processing device
JP3857176B2 (en) Relay router and network and connection rearrangement method
JP5542098B2 (en) Route control apparatus, route control program, route control method, and route control system

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20040804

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20060120

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20060131

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20060328

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20060829

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20061012

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20070109

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20070110

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20110119

Year of fee payment: 4

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20110119

Year of fee payment: 4

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20120119

Year of fee payment: 5

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20130119

Year of fee payment: 6

S531 Written request for registration of change of domicile

Free format text: JAPANESE INTERMEDIATE CODE: R313531

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

LAPS Cancellation because of no payment of annual fees