JP4047517B2 - Communication network system - Google Patents

Description

図６のネットワークサブマップ画面上では、東京都と付記されたドメインアイコンは、例えば、図１におけるＲ−ＮＭＳ２００ａ管理下のドメイン（ＲＮＷ１１，１２，１３，１４を含む）に相当する。同様に、神奈川県と付記されたドメインアイコンは、図１におけるＲ−ＮＭＳ２００ｂ管理下のドメイン（ＲＮＷ２１，２２，２３，２４を含む）に相当し、千葉県と付記されたドメインアイコンは、図１におけるＲ−ＮＭＳ２００ｃ管理下のドメイン（ＲＮＷ３１，３２，３３，３４を含む）に相当する。
【０１２２】
この例では、東京都と付記されたドメインアイコンが赤色で表示されており、該ドメインアイコンに対応する上記Ｒ−ＮＭＳ２００ａ管理下のドメインに障害が発生し、かつ危険域にあることが分かる。
【０１２３】
図６のネットワークサブマップ画面上で、任意のドメインアイコンを選択することにより、この選択されたドメインアイコンに対応するドメイン（Ｒ−ＮＭＳ２００）へログインし、図７に示す如くのドメインサブマップ画面を表示することができる。
【０１２４】
この場合の表示制御は以下のようにして実現できる。すなわち、ＮＭＳ３００において、表示部３０４に表示された上記ネットワークサブマップ画面（図６参照）上で、入力部３０３からマウス等を用いて同画面上の任意のドメインアイコンをダブルクリックする操作がなされると、ＳＮＭＰマネージャ３０２ａはその旨を画面接続アプリケーション３０５ｃに通知する。
【０１２５】
これにより、画面接続アプリケーション３０５ｃは、ＳＮＭＰマネージャ３０２ａと管理プロトコル３０５ｅを使用して、上記選択されたドメインアイコンに対応するＲ−ＮＭＳ２００のＳＮＭＰマネージャ２０２ａにドメイン管理結果の転送を要求する。
【０１２６】
要求先のＲ−ＮＭＳ２００では、管理プロトコル２０５ｇを使用して上記要求を受け、この要求をＳＮＭＰマネージャ２０２ａに渡す。ＳＮＭＰマネージャ２０２ａは、この要求を受けることにより、記憶部２０５から自装置で管理しているドメイン管理情報（被管理ノードから収集した障害管理情報１０６ａ，１５６ａ及び構成／状態管理情報１０６ｂ，１５６ｂ）を読み出し、管理プロトコル２０５ｇを使用して、指令ＮＭＳ３００に送出する応答処理を行う。
【０１２７】
これに対し、指令ＮＭＳ３００は、管理プロトコル３０５ｅを使用して、Ｒ−ＮＭＳ２００から応答送出された上記ドメイン管理情報を受信し、該情報をＳＮＭＰマネージャ３０２ａにより記憶部３０５に格納させる。
【０１２８】
次いで、ＳＮＭＰマネージャ３０２ａは、Ｒ−ＮＭＳ２００からドメイン管理情報を取り込んだ旨を画面接続アプリケーション３０５ｃに通知する。この通知により、画面接続アプリケーション３０５ｃは、記憶部３０５に格納された上記ドメイン管理情報に基づき表示部３０４に図７に示す如くのドメインサブマップ画面を表示する処理を行う。
【０１２９】
図７におけるドメインサブマップ画面は、例えば、図６のネットワークサブマップ画面上でシンボル色が赤色表示されているドメインアイコン（東京都と付記されたアイコン）をダブルクリックすることにより表示されたものである。
【０１３０】
この場合のドメインサブマップ画面（図７参照）上には、上記ダブルクリックされたドメインアイコンに対応するドメイン（図１のＲ−ＮＭＳ２００ｂ）を構成する各ＲＮＷ２１，２２，２３，２４を示すアイコン（以下、リングアイコンと称する）が、当該各ＲＮＷ２１，２２，２３，２４の各々の運用状態を反映させたシンボル色で表示される。この場合における運用状態とシンボル色との関係も上述したネットワークサブマップ画面と同じである。
【０１３１】
図７のドメインサブマップ画面において、ＡＴＭリング１と付記されたリングアイコンは、例えば、図１におけるＲ−ＮＭＳ２００ａ管理下のＲＮＷ１１に相当する。同様に、ＡＴＭリング２と付記されたリングアイコンは、ＲＮＷ１２に、ＡＴＭリング３と付記されたリングアイコンは、ＲＮＷ１３に、ＡＴＭリング４と付記されたリングアイコンは、ＲＮＷ１４にそれぞれ相当する。
【０１３２】
この例では、ＡＴＭリング１と記されたリングアイコンが赤色で表示されており、該リングアイコンに対応するＲＮＷ１１に障害が発生し、かつ危険域にあることが分かる。
【０１３３】
図７におけるドメインサブマップ画面上で、任意のリングアイコンを選択することにより、この選択されたリングアイコンに対応するＲＮＷのセグメント構成に対応した図８に示す如くのリングセグメントマップ画面を表示することができる。
【０１３４】
この場合の表示制御は以下のようにして実現できる。すなわち、ＮＭＳ３００において、表示部３０４に表示された上記ドメインサブマップ画面（図７参照）上で、入力部３０３からマウス等を用いて同画面上の任意のリングアイコンをダブルクリックする操作がなされると、ＳＮＭＰマネージャ３０２ａはその旨を画面表示アプリケーション３０５ａに通知する。
【０１３５】
画面表示アプリケーション３０５ａは、例えば、各Ｒ−ＮＭＳ２００ａ，２００ｂ，２００ｃ管理下のドメイン内の各リング毎のリングセグメントマップ画面、リング管理画面、各リング内の各ノード毎のノード管理画面、各ノード毎の接点警報管理画面等の順に下位の階層となるべく階層化された運用状態表示画面を管理している。
【０１３６】
そして、ＳＮＭＰマネージャ３０２ａより、上記ドメインサブマップ画面（図７参照）上の任意のリングアイコンがダブルクリックされたとの通知を受けると、まず、このドメインサブマップ画面の下位階層でかつ上記選択されたリングアイコンに対応するリングセグメントマップ画面（図８参照）を開き、かつ当該画面上におけるノードアイコン等の各アイコンに対して、上記画面接続アプリケーション３０５ｃを利用して接続先のＲ−ＮＭＳ２００から取得した記憶部３０５内のドメイン管理情報（障害管理情報１０６ａ，１５６ａ）中の障害発生または障害復旧内容をそれぞれに反映して表示する処理を行う。
【０１３７】
図８は、例えば、図７におけるドメインサブマップ画面上でＡＴＭリング１がダブルクリックされた場合のリングセグメントマップ画面の表示例を示すものである。この例では、「ＲＮ装置１０１」，「ＲＮ装置１０２」等のノードアイコンや、「リング１管理起動」等の動作状態アイコン等がその運用状態を反映した態様で表示される他、「ＲＮ装置１０１」と「ＲＮ装置１０２」間のループバック（図中、ＬＢと付記されている。）が実行されている様子等も表示される。
【０１３８】
図８におけるリングセグメントマップ画面上で、任意のノードアイコンを選択（ダブルクリック）することにより、この選択されたノードアイコンに対応するノードの運用状態を示す図９に示す如くのノード管理画面を表示することができる。
【０１３９】
この場合の表示制御は以下のようにして実現できる。すなわち、ＮＭＳ３００において、表示部３０４に表示された上記リングセグメントマップ画面（図８参照）上で、入力部３０３からマウス等を用いて同画面上の任意のノードアイコンをダブルクリックする操作がなされると、ＳＮＭＰマネージャ３０２ａはその旨を画面表示アプリケーション３０５ａに通知する。
【０１４０】
画面表示アプリケーション３０５ａは、上記通知を受けると、現在表示中のリングセグメントマップ画面の下位階層でかつ上記ダブルクリックされたノードアイコンに対応するノードのノード管理画面（図９参照）を開き、該ノードの構成要素を表示すると共に、これら各構成要素に対して、上記画面接続アプリケーション３０５ｃを利用して接続先のＲ−ＮＭＳ２００から取得した記憶部３０５内のドメイン管理情報（障害管理情報１０６ａ，１５６ａ）中の障害発生または障害復旧内容を反映して表示する処理を行う。
【０１４１】
なお、この場合のノード構成要素の表示処理において、画面表示アプリケーション３０５ａは、上記画面接続アプリケーション３０５ｃにより取得済みのドメイン管理情報のうちの構成／状態管理情報１０６ｂ，１５６ｂを基に、各項目に対応した構成及び状態を示す画像を、例えば、当該ノードの実機イメージそのままに表示部３０４上に描画するようにしている。
【０１４２】
一般に、被管理ノードの実機の構造に関しては、例えば筐体前面に、インタフェーススロット等が設けられる他、このインタフェーススロット等につながる内部基板の動作状態、電源の状態あるいはアラーム発生状況等を表示する表示素子等が設けられる。上記実機イメージとは、これら被管理ノードの実機構造を実際に筐体前面から見た場合と同じに認知し得る画像内容を意味する。
【０１４３】
従って、指令ＮＭＳ３００に居る管理者は、図９におけるノード管理画面を見ることにより、当該ノードを実際に見ているのと同じに、当該ノードの状態を詳細に把握することができる。
【０１４４】
更に、図９におけるノード管理画面上で、任意の構成要素表示領域をダブルクリックすると、該ダブルクリックされた表示領域が拡大表示される。この表示処理も、画面表示アプリケーションが３０５ａにより行われる。
【０１４５】
また、図９におけるノード管理画面上で、表示メニューの中から「障害」を選択し、これにより表示されるポップアップウィンドウの中の「接点警報」を選択することにより、図１０に示す如くの接点警報管理画面を表示することができる。
【０１４６】
この場合の表示制御は以下のようにして実現できる。すなわち、ＮＭＳ３００において、表示部３０４に表示された上記ノード管理画面（図９参照）の表示内容を基に、入力部３０３から上記「接点警報」の選択入力があると、ＳＮＭＰマネージャ３０２ａはその旨を画面表示アプリケーション３０５ａに通知する。
【０１４７】
画面表示アプリケーション３０５ａは、上記通知を受けると、現在表示中のノード管理画面の下位階層でかつ上記選択された「接点警報」に係わる接点警報管理画面（図１０参照）を開き、かつ当該画面上における各接点警報項目に対して、上記画面接続アプリケーション３０５ｃを利用して接続先のＲ−ＮＭＳ２００から取得した記憶部３０５内のドメイン管理情報（障害管理情報１０６ａ，１５６ａ）中の障害発生または障害復旧内容を各々反映して表示する処理を行う。
【０１４８】
図１０における接点警報管理画面は以下の構成要素を備える。
１）「タイトルバー」は、画面名称を表示する。
２）「接点番号」は、接点番号を表示する。
３）「接点警報状態」は、接点警報状態を色で表示する。接点警報状態と色の関係は、例えば、下記の表２に示されるような関係にある。
【表２】

４）「接点警報名称」は、接点名称を表示する。この欄には、コメントも入れることができる。
５）「接点警報名表示リストボックス（表示）」は、接点番号、接点警報名をリスト形式で表示する。「接点番号（表示）」は、接点番号を表示する。
６）「接点番号（表示）」は、接点番号を表示する。
７）「接点警報名（表示）」は、接点警報名称を表示する。
８）「縦スクロールバー（操作）」は、接点警報名表示リストボックスをスクロール巣するための操作ツールである。
９）「保存ボタン（操作）」は、表示画面の情報をファイルに保存するための操作ツールである。
１０）「変換ボタン（操作）」は、「保存ボタン」を用いて保存されたファイル（ＣＳＶ形式）を例えばEUCフォーマットからS-JISフォーマットに変換するための操作ツールである。
１１）「終了ボタン」は、本画面を終了するための操作ツールである。
１２）「ステータスバー」には、ＮＭＳアプリケーションのステータスを示すメッセージが表示される。メッセージの一覧を下記の表３に示す。
【表３】

更に、画面表示アプリケーション３０５ａは、以下の様な表示処理も行う。例えば、図１０に示す接点警報管理画面上で、「保存ボタン」が選択されると、図１１に示す接点警報保存画面を表示する。
【０１４９】
この接点警報保存画面において、「保存ファイル名」欄は、デフォルト名を表示及びファイル名変更のために用いられる。この場合の保存ファイル名は、（ファイル名）／ログインホームディレクトリ／POINT***.CVS（***は、ノードＩＰアドレス）という形式で構成される。
【０１５０】
また、同画面において、「ＯＫ」ボタンが選択されると、上述した保存ファイル名でファイルに保存される。この場合、ファイル形式は、CSV形式（カンマ（，）区切り）となる。また、１行で１回線の内容を書き込む。また、ファイルの内容は、装置名、接点番号、接点コメントとなる。
【０１５１】
また、同画面において、「キャンセルボタン」は、同接点警報保存画面を終了するための操作ツールである。この「キャンセルボタン」を操作することにより、図１０における接点警報管理画面に戻る。
【０１５２】
図１０における接点警報管理画面から、障害状態表示を終了する場合には、これまでに開いた画面を順に閉じて初期画面（図６におけるネットワークサブマップ画面）まで戻り、当該初期画面を閉じる操作を行う。
【０１５３】
なお、図６における初期画面を表示した状態で、任意のドメインの詳細な運用状態を確認するために、当該ドメインに対応するドメインアイコンをダブルクリックした後（つまり、上記画面接続アプリケーション３０５ｃを起動した後）、指令ＮＭＳ３００からＲ−ＮＭＳ２００への接続に失敗した場合は、図１２に示す如くのポップアップウィンドウ（接続エラー画面）が表示される。これ以後、続けて再接続する場合は、同ウィンドウ中の「再接続」ボタンをクリックし、中止する場合は、「中止」ボタンをクリックする。
【０１５４】
Ｒ−ＮＭＳ２００への接続失敗の要因としては、ネットワーク回線が混雑することに伴う通信タイムアウト発生、接続先Ｒ−ＮＭＳ２００の電源ＯＦＦ、指令ＮＭＳ３００で保持している指定したＲ−ＮＭＳ２００のＩＰアドレス誤り、指定したＲ−ＮＭＳ自体のＩＰアドレス設定誤り、ネットワーク機器（ハブ、ルータ等）の障害発生、通信ケーブルの障害発生（断線、コネクタ障害等）等が考えられる。従って、管理者は、図１２におけるウィンドウ上で再接続を行う前に、これらの要因を確認する必要がある。
【０１５５】
以上は、指令ＮＭＳ３００の画面表示アプリケーション３０５ａがサポートしている障害状態表示機能に基づく表示制御について述べたものであるが、次に、同アプリケーション３０５ａがサポートする障害情報表示機能に基づく表示制御について説明する。
【０１５６】
この障害情報表示機能は、管理下の各Ｒ−ＮＭＳ２００から送られてくる障害管理情報を収集し、これをキャラクタ情報として表示する機能である。この機能により表示された障害管理情報を解析することによっても、障害発生要因をつきとめることが可能である。また、本機能によれば、リアルタイム及び蓄積された障害管理情報をある条件を基に抽出して表示するといった処理にも対応できる。
【０１５７】
以下、指令ＮＭＳ３００に収集蓄積された障害管理情報を表示するための手順及び画面表示の各項目について説明する。
【０１５８】
この手順の初期段階としては、指令ＮＭＳ３００の表示部３０４上に図１３に示す如くの「イベント・カテゴリ」を表示する。この「イベント・カテゴリ」画面上で「全イベント」に対応する左側のボタンをクリックすると、図１４に示す如くの「全イベント・ブラウザ」画面が表示される。
【０１５９】
この「全イベント・ブラウザ」画面の表示は、例えば、以下の制御により実現できる。すなわち、ＮＭＳ３００において、入力部３０３から、「全イベント」に対応する左側のボタンをクリックする操作入力があると、ＳＮＭＰマネージャ３０２ａがその旨を画面表示アプリケーション３０５ａに通知する。
【０１６０】
画面表示アプリケーション３０５ａは、上記通知を受けると、既に画面接続アプリケーション３０５ｃを利用して接続先のＲ−ＮＭＳ２００から取得している記憶部３０５内の障害管理情報１０６ａ，１５６ａを読み出し、当該障害管理情報１０６ａ，１５６ａを表示部３０４に図１４に示す態様でキャラクタ情報のまま表示する。
【０１６１】
この「全イベント・ブラウザ」画面は以下の構成要素を備える。
１）「受託」は、イベントが受託されたかどうかを表示するチェックマークである。
２）「重要度」は、イベントの重要度を表示する。重要度は例えば５段階に区別されており、下位の表４に示す通り、色分けで実現される。
【表４】

３）「日時」は、イベントが発生した日時、曜日、時刻を表示する。
４）「ソース」は、イベントが発生したノードのＩＰアドレスを表示する。
５）「メッセージ」は、イベントの簡単な説明、ノード名称を表示する。
【０１６２】
ところで、本発明システムのＲ−ＮＭＳ２００（図３参照）では、管理下のドメイン内各ノード（ＲＮ１００，ＣＮ１５０）から収集された障害管理情報１０６ａ，１５６ａに基づき、ドメイン状態アプリケーション２０５ｃがドメイン状態情報を更新して指令ＮＭＳ３００に自律通知する際、接点アプリケーション２０５ｄが起動される。
【０１６３】
接点アプリケーション２０５ｄは、上記更新後のドメイン状態情報を基に、ドメイン全体としての警報状態を接点ＨＷ回路２０６に反映させる処理を行う。この時の接点ＨＷ回路２０６の接点情報は、接点転送装置２１０（２１０ａ，２１０ｂ，２１０ｃ）に読み取られ、接点転送路８０（８０ａ，８０ｂ，８０ｃ）を介して指令ＮＭＳ３００側に設置された接点状態表示装置３１０に転送される。
【０１６４】
一方、指令ＮＭＳ３００（図２参照）側では、Ｒ−ＮＭＳ２００側の接点転送装置２１０から転送されてくる接点情報を受信し、その接点情報の内容に応じて、例えば、ランプ表示やブザー音出力等の所定の方法によりドメイン状態の警報表示を行う。
【０１６５】
以上の如く、ネットワーク管理機能の階層化が図られた本発明システムにおけるＲ−ＮＭＳ２００及び指令ＮＭＳ３００の構成及び制御によれば、指令ＮＭＳ３００側に居る管理者は、特に必要がない限り、この指令ＮＭＳ３００に表示される上述したドメインアイコン表示画面を見ながらネットワーク管理が行える。
【０１６６】
この場合、ドメインアイコン表示画面上には、ドメインを構成する各ノードに対応するノードアイコンが存在しないため、ドメインあるいはドメイン内ノードが増加しても表示が煩雑になることはなく、障害監視が容易になる。
【０１６７】
しかも、ドメイン内での障害発生により対応するドメインアイコンの色が障害色に変化した場合等、必要に応じて、ドメインアイコン表示画面上で所望のドメインアイコンを選択すれば、この選択されたドメインアイコンに対応するＲ−ＮＭＳ２００が管理中のドメイン管理情報に基づくドメイン管理画面が表示されるため、この表示内容を基にドメイン内の各リングレベルでの運用監視が行える。
【０１６８】
更に、ドメイン管理画面上で、任意のドメイン構成要素が選択されると、まず、現在表示中の画面の下位階層でかつ上記選択された構成要素に対応する運用状態表示画面（リングセグメント構成画面）がその運用状態を反映した内容で表示され、以下同様にして下位階層の運用表示画面を例えば各リング構成画面→各ノード構成画面→各ノード毎の接点警報画面という階層順に開きかつその運用状態を反映した内容で表示できることから、簡単な選択操作で所望の階層レベルの詳細な運用監視が行え、障害発生個所を特定するまでの時間も短縮できる。
【０１６９】
また、本発明システムにおいて、指令ＮＭＳ３００は、自装置内のモニタ画面に対するドメインアイコン表示機能と併せて、別体の接点状態表示装置３００による接点状態表示機能も備えている。この構成によれば、ＮＭＳ３００側に居る管理者は、ＮＭＳ３００の管理画面を常に見ていなくても、接点状態表示装置３１０からの接点警報表示を基にある程度の運用状態変化を認識でき、これにより、指令ＮＭＳ３００自身が無くても最低限のネットワーク管理が行える。
【０１７０】
ところで、本発明システムのＲ−ＮＭＳ２００（図３参照）において、ＳＮＭＰマネージャ２０２ａは、被管理装置（ＲＮ１００、ＣＮ１５０、リング等）をこれら各装置を表す装置アイコンとして管理すると共に、自律通知表示アプリケーション２０５ａとの連携により、これら各被管理装置を装置アイコンとして表示部２０４上に表示する処理を行う。
【０１７１】
そして、自律通知表示アプリケーション２０５ａは、上記各被管理装置からの障害管理情報１０６ａ，１５６ａ〔以下、トラップ（Trap）と称する〕の自律通知発報の着信時、その発報元アドレスを参照して、ＳＮＭＰマネージャ２０２ａが管理している装置アイコンを検索する一方、この時の自律通知発報内のトラップの内容を参照し、その値によって、上記検索済みの装置アイコンのシンボル色を障害の発生を示す色または障害復旧を示す色に更新して表示部２０４上に表示する。
【０１７２】
一方、被管理装置（ＲＮ１００、ＣＮ１５０）では、トラップの自律通知発報はそれぞれ管理プロトコル１０６ｄ、１５６ｄにより実施されるが、この場合のプロトコルとしては上述した如くＳＮＭＰ／ＵＤＰ／ＩＰが用いられている。
【０１７３】
しかしながら、このプロトコルは再送手順を持たない。このため、Ｒ−ＮＭＳ２００と被管理装置との間の回線品質が悪化した場合等においては、被管理装置がトラップを送出したにもかかわらず、Ｒ−ＮＭＳ２００までトラップが到着しないという事態つまりトラップ受信落ちが発生し得る。
【０１７４】
トラップ受信落ちが発生すると、上述した装置アイコンに対するトラップ受信によるリアルタイムのシンボル色更新が停止し、Ｒ−ＮＭＳ２００での被管理装置の正確な運用管理が行えなくなる。
【０１７５】
このための対策として、本発明システムでは、Ｒ−ＮＭＳ２００から被管理装置に対し、一定周期で、被管理装置内のトラップのポーリングを行うことにより、それまでの間にトラップ受信落ちとなったトラップも確実にＲ−ＮＭＳ２００に取り込み、直ちにシンボル色更新処理に反映するようにしている。
【０１７６】
図３の構成において、Ｒ−ＮＭＳ２００の記憶部２０５内に設けられるトラップポーリングアプリケーション２０５ｅは、上述したトラップポーリングによりトラップ受信落ちを救済する処理を実施するアプリケーションである。
【０１７７】
図１５は、トラップポーリングアプリケーション２０５ｅによるトラップポーリング処理に係わる障害状態チェックプロセスの動作概念図である。
【０１７８】
図１５において、９１は管理ミドルウェア２０５ｆ（ＳＮＭＰマネージャ２０２ａ）が提供する被管理装置情報を格納するデータベースである。９２は管理ミドルウェア２０５ｆが管理する被管理装置シンボルであり、各被管理装置のアイコンのシンボル色を表す値（シンボルステータス）が記憶されている。９３は管理ミドルウェア２０５ｆが提供するイベント（トラップ）通知サービスを司るイベントプロセスである。９４，９５は、それぞれ、被管理装置としてのノードやリングである。
【０１７９】
以下、図１５における障害状態チェックプロセスの処理の流れについて、図１６を参照して説明する。図１６は、トラップポーリングアプリケーション２０５ｅによるトラップポーリング処理を示すフローチャートである。
【０１８０】
Ｒ−ＮＭＳ２００でのネットワーク管理実行中、トラップポーリングアプリケーション２０５ｅは、当該ポーリングの実施間隔として予め定められた一定周期をカウントし、該一定周期がタイムアウトする（ステップ１６０ＹＥＳ）毎に、管理ミドルウェア２０５ｆのデータベース９１から被管理装置（ノード９４、リング９５）情報を取得し（ステップ１６１）する。次いで、この取得した被管理装置情報を基に、管理ミドルウェア２０５ｆが管理する被管理装置シンボル９２からこれら各装置のアイコンのシンボル色を表すシンボルステータスを読み出す（ステップ１６２）。
【０１８１】
次に、トラップポーリングアプリケーション２０５ｅは、ステップ１６１で取得した被管理装置情報を基に、最初の被管理装置を選び、該被管理装置に対して障害状態取得要求を送出する（ステップ１６３）。
【０１８２】
この障害状態取得要求により、管理ミドルウェア２０５ｆが管理プロトコル２０５ｇを利用して、該当する被管理装置のＳＮＭＰエージェント１０５ｂ，１５５ｂにトラップの転送を要求する。
【０１８３】
一方、上記要求先の被管理装置（図４参照）では、管理プロトコル１０６ｄ，１５６ｄを使用して、上記転送要求をＳＮＭＰエージェント１０５ｂ，１５５ｂに渡す。
【０１８４】
ＳＮＭＰエージェント１０５ｂ，１５５ｂは、この転送要求を受けることにより、記憶部１０６，２０６から障害管理情報１０６ａ，１５６ａを読み出し、該情報１０６ａ，１５６ａを、管理プロトコル１０６ｄ，１５６ｄを使用して、Ｒ−ＮＭＳ２００に送出する応答処理を行う。
【０１８５】
これに対し、Ｒ−ＮＭＳ２００は、管理プロトコル２０５ｇを使用して、上記被管理装置から応答送出された障害管理情報１０６ａ，１５６ａを受信し、該情報１０６ａ，１５６ａを管理ミドルウェア２０５ｆに渡す。更に、管理ミドルウェア２０５ｆはこの障害管理情報１０６ａ，１５６ａをトラップポーリングアプリケーション２０５ｅに渡すことでトラップ（障害管理情報１０６ａ，１５６ａ）のポーリングが実現する。
【０１８６】
この間、トラップポーリングアプリケーション２０５ｅは、ポーリング先の被管理装置との接続が失敗したか否かを監視し（ステップ１６４）、当該接続が失敗した場合（ステップ１６４ＹＥＳ）、例えば、図１２に示す接続エラー画面を用いて再接続を試みる等の接続エラー処理（ステップ１７０）を行う。
【０１８７】
また、ポーリング先の被管理装置との接続が失敗でない場合（ステップ１６４ＮＯ）、次にトラップポーリングアプリケーション２０５ｅは、トラップを受信したかどうかをチェックする（ステップ１６５）。
【０１８８】
ここで、トラップが受信された場合（ステップ１６５ＹＥＳ）、トラップポーリングアプリケーション２０５ｅは、次のポーリング対象ノードがあるかどうかをチェックし（ステップ１６６）、次のノードがあれば（ステップ１６６ＹＥＳ）、ステップ１６３に戻り、上述と同様の処理を経てこのノードに対するトラップのポーリングを行う（ステップ１６３〜ステップ１６６）。このポーリングをステップ１６１で被管理装置情報を取得した全ての被管理装置に対して行う。
【０１８９】
この間、次のポーリング対象ノードが無いと判定された場合（ステップ１６６ＮＯ）、トラップポーリングアプリケーション２０５ｅは、これまでにポーリングした各ノードのトラップの値と、ステップ１６２で取得した各ノードのシンボルステータスとを各々対応するもの同士を比較し（ステップ１６７）、不一致となったものがあるかどうかをチェックする（ステップ１６８）。
【０１９０】
ここで、不一致となったものが存在すれば（ステップ１６８ＹＥＳ）、過去にトラップ受信落ちがあったものと判断し、管理ミドルウェア２０５ｆが提供するイベント通知サービスを司るイベントプロセス９３を経由して、当該シンボルステータス（シンボル色）を取得したトラップの障害状態を反映した色に更新するよう自律通知表示アプリケーション２０５ａに指示する（ステップ１６９）。
【０１９１】
自律通知表示アプリケーション２０５ａは、上記イベントプロセス９３からの指示に従って該当する被管理装置のシンボル色を更新する。つまり、当該被管理装置のシンボルステータスをポーリング取得した値に合致するように更新して被管理装置シンボル９２に記憶させる処理を行う。
【０１９２】
ポーリングした各ノードのトラップの値と、ステップ１６２で取得した各ノードのシンボルステータスとが各々一致している場合（ステップ１６８ＮＯ）、あるいは、自律通知表示アプリケーション２０５ａで、被管理装置のシンボルステータスをポーリング取得した値に合致するように更新して被管理装置シンボル９２に記憶させる処理を行った後は、トラップポーリング処理の初期ステップ（ステップ１６０）へと戻る。
【０１９３】
なお、上述したポーリング処理においては、トラップポーリング対象としてはノード９４に限らず、リング９５であっても良い（図１５参照）。
【０１９４】
このように、本発明システムのＲ−ＮＭＳ２００では、トラップポーリングアプリケーション２０５ｅが、被管理装置の障害管理機能に対して一定周期でトラップのポーリングを実施し、これにより得たトラップの障害情報と所定のトラップ受信タイミングでリアルタイム更新している被管理装置ステータスシンボルとを比較し、不一致であれば、過去にトラップ受信落ちが発生していたものと判断して、該シンボル色をポーリングにより取得した障害情報を表す色に更新するように自律通知表示アプリケーション２０５ａに指示し、該自律通知表示アプリケーション２０５ａがその指示に従って被管理装置のシンボル色を更新するように処理する。
【０１９５】
この処理機能によれば、上記所定のタイミングでのトラップ受信動作においてトラップ受信落ちが発生したとしても、それ以後、上記ポーリング周期のうちには当該トラップ受信落ちしたトラップを被管理装置から取得してその障害状態に応じたシンボル色更新を行うことでき、シンボル色に依存したネットワークの障害管理の信頼性を高めることができる。
【０１９６】
なお、本発明は、上記実施形態に限らず、その主旨を逸脱しない範囲で適宜変更若しくは応用が可能なものである。例えば、本発明に係わるドメインの構成は、図１に示すように被管理ノードをリング状に接続したＲＮＷに限るものではなく、被管理ノードを直線的に接続したりあるいはスター型に接続したり等、種々の接続形態も許容するものである。
【０１９７】
また、図１５及び図１６に示すポーリングによるトラップ受信落ち救済処理については、ノードまたはリングとＲ−ＮＭＳ２００との間のトラップの自律通知に限らず、Ｒ−ＮＭＳ２００とその上位の指令ＮＭＳ３００との間のトラップ自律通知にも適用できるものである。
【０１９８】
【発明の効果】
以上説明したように、本発明によれば、１または複数の通信装置を含むドメイン全体を管理する管理装置と、該管理装置を介してネットワーク全体を管理する上位管理装置を通信路により接続すると共に、管理装置に接点転送装置を近接設置し、かつ、上位管理装置に接点状態表示装置を近接設置して成り、管理装置は、管理下の通信装置から取得した障害管理情報を自装置管理下のドメイン全体としての運用状態に反映させたドメイン状態情報を生成して上位管理装置に自律通知し、上位管理装置は、管理装置から自律通知されるドメイン状態情報に基づき、該ドメイン状態情報の自律通知元の管理装置で管理されるドメインに対応する前記ドメインアイコンを該ドメインの障害発生または復旧を示すシンボル色で表示する一方、更に、管理装置は、上位管理装置にドメイン状態情報を自律通知する際、該ドメイン状態情報を基にドメイン状態を接点回路部に反映させ、該管理装置に近接設置される接点転送装置は上記接点回路部から読み取った接点情報を上位管理装置に近接設置される接点状態表示装置に転送し、該接点状態表示装置は、接点転送装置から転送される接点情報に基づき所定の接点警報表示を行うものである。
【０１９９】
かかる構成によれば、上位管理装置の監視画面には、ドメインの数分のアイコン（ドメインアイコン）が該当するドメインの障害発生または復旧を示すシンボル色で表示され、ドメインを構成する複数の通信装置に対応する装置アイコンが存在しないため、ドメインあるいはドメイン内通信装置が増加しても表示が煩雑になることはなく、障害監視が容易になる。
【０２００】
また、上記構成によれば、上位管理装置でのドメインアイコンの表示と並行して、該上位管理装置に近接設置される接点状態表示装置において、管理装置に近接される接点転送装置から転送される接点情報に基づき所定の接点警報表示（ランプ表示やブザー音鳴動等）を行うため、上位管理装置側に居る管理者は、例えば、接点警報がない正常運用時には接点状態のみを監視し（ドメインアイコン表示画面上での確認は行わない）、接点が警報を表示した場合に、ドメインアイコン表示画面上で該当するドメインアイコンを対象に詳細を確認する運用を通じて、上位管理装置の管理画面（ドメインアイコン表示画面）を常に見ていなくても、接点状態表示装置での接点警報表示を見ることである程度の運用状況変化を認識でき、多数の管理装置にわたるネットワーク全体の警報状態を容易に把握できる。
【０２０３】
更に、本発明において、通信装置は、管理下の通信装置に対して一定周期で障害管理情報のポーリングを行い、このポーリングにより取得した障害管理情報と、前記通信装置から自律通知された障害管理情報とを比較し、両者が不一致の場合に、障害管理情報の自律通知受信落ち有りと判定して、上記ポーリングにより取得した障害管理情報の内容に合わせて該ポーリング先の通信装置の装置アイコンのシンボル色を更新するようにしたため、自律通知受信タイミングで障害管理情報（トラップ）受信落ちが発生した場合にも、それ以降、上記一定周期のポーリング期間内には該トラップ受信落ちしたトラップの内容に応じたシンボル色更新処理を行うことができ、シンボル色をキーとしたネットワーク管理の信頼性を高めることができる。
【図面の簡単な説明】
【図１】本発明に係わる通信ネットワークシステムの全体構成を示す図。
【図２】本発明システムの指令ＮＭＳの構成を示すブロック図。
【図３】本発明システムのＲ−ＮＭＳの構成を示すブロック図。
【図４】本発明システムのＲＮ及びＣＮの構成を示すブロック図。
【図５】リング伝送路が無線回線で実現される場合のＲＮの構成例を示す図。
【図６】指令ＮＭＳでのドメインアイコン表示画面の表示例を示す図。
【図７】指令ＮＭＳでのドメインサブマップ画面の表示例を示す図。
【図８】指令ＮＭＳでのリングセグメントマップ画面の表示例を示す図。
【図９】指令ＮＭＳでのノード管理画面の表示例を示す図。
【図１０】指令ＮＭＳでの接点警報管理画面の表示例を示す図。
【図１１】指令ＮＭＳでの接点警報保存画面の表示例を示す図。
【図１２】指令ＮＭＳからＲ−ＮＭＳへの接続失敗時の接続エラー画面の表示例を示す図。
【図１３】指令ＮＭＳでの障害情報表示機能起動時の初期画面の表示例を示す図。
【図１４】指令ＮＭＳでの障害情報表示機能による障害情報表示例を示す図。
【図１５】Ｒ−ＮＭＳでのトラップポーリング処理に係わる障害状態チェックプロセスの動作概念図。
【図１６】Ｒ−ＮＭＳでのトラップポーリング処理を示すフローチャート。
【符号の説明】
１０ ノード本体部
２０ａ，２０ｂ 屋内装置（ＩＤＵ）
３０ａ，３０ｂ 屋外装置（ＯＤＵ）
３５ａ，３５ｂ アンテナ
４０ 接点監視装置
５０ リング伝送路
５５ａ，５５ｂ，５５ｃ，６０ａ，６０ｂ，６０ｃ，６５ａ，６５ｂ，６５ｃ，７５ 伝送路
５６，７１ 交換機
８０ａ，８０ｂ，８０ｃ 接点転送路
１００ リングノード装置（ＲＮ）
１０１、１０２，１０３ インタフェース（Ｉ／Ｆ）部
１０４ スイッチ部
１０５ 制御部
１０５ａ 状態監視部
１０５ｂ ＳＮＭＰエージェント
１０６ 記憶部
１０６ａ 障害管理情報
１０６ｂ 構成／状態管理情報
１０６ｃ 管理ミドルウェア
１０６ｄ 管理プロトコル
１１０ ローカル端末
１５０ａ，１５０ｂ，１５０ｃ センタノード装置（ＣＮ）
１５１、１５２，１５３ インタフェース（Ｉ／Ｆ）部
１５４ スイッチ部
１５５ 制御部
１５５ａ 状態監視部
１５５ｂ ＳＮＭＰエージェント
１５６ 記憶部
１５６ａ 障害管理情報
１５６ｂ 構成／状態管理情報
１５６ｃ 管理ミドルウェア
１５６ｄ 管理プロトコル
１５７ イーサネットインタフェース（Ｉ／Ｆ）部
２００ 中継ネットワーク管理装置（Ｒ−ＮＭＳ）
２０１ａ イーサネットインタフェース（Ｉ／Ｆ）部
２０１ｂ 伝送路インタフェース（Ｉ／Ｆ）部
２０２ 制御部
２０２ａ ＳＮＭＰマネージャ
２０３ 入力部
２０４ 表示部
２０５ 記憶部
２０５ａ 自律通知表示アプリケーション
２０５ｂ 画面表示アプリケーション
２０５ｃ ドメイン状態アプリケーション
２０５ｄ 接点アプリケーション
２０５ｅ トラップポーリングアプリケーション
２０５ｆ 管理ミドルウェア
２０５ｇ 管理プロトコル
２０６ 接点ハードウェア（ＨＷ）回路
２１０ａ，２１０ｂ，２１０ｃ 接点転送装置
３００ 指令ネットワーク管理装置（指令ＮＭＳ）
３０１ 伝送路インタフェース（Ｉ／Ｆ）部
３０２ 制御部
３０２ａ ＳＮＭＰ（Simple Network Management Protocol）マネージャ
３０３ 入力部
３０４ 表示部
３０５ 記憶部
３０５ａ 画面表示アプリケーション
３０５ｂ ドメインアイコン表示アプリケーション
３０５ｃ 画面接続アプリケーション
３０５ｄ 管理ミドルウェア
３０５ｅ 管理プロトコル
３１０ 接点状態表示装置[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a communication network system in which a higher-level management device is arranged above a management device that manages an entire domain including one or a plurality of communication devices, and the management function is hierarchized. The present invention relates to improvement of network operation state display control for facilitating network management in the network.
[0002]
[Prior art]
For example, in the fields of railway management systems, road management systems, and the like, network configurations are known in which a plurality of communication devices are distributed and information from each of these communication devices is collected and managed in a management center.
[0003]
In this type of system, for the purpose of network maintenance management, for example, a network management device is arranged in the network, and the network management device acquires various types of information from each managed communication device (managed device). In some cases, the management result is displayed on the management screen based on the acquired information.
[0004]
Here, as information acquired from the managed device by the network management device, for example, there is information related to the failure of the managed device. In this case, the network management device acquires information on the failure of the managed device by an autonomous notification from each managed device, and displays information on the failure of each managed device on the management screen based on the autonomous notification. It is common.
[0005]
Regarding the display of the autonomous notification information in the network management device, for example, a method for displaying character information relating to a failure autonomously notified from the managed device, or an icon (node icon) representing the managed device is prepared. There is a method of reflecting the symbol color indicating the failure occurrence on the node icon of the corresponding managed device based on the autonomous notification information from the managed device.
[0006]
By the way, with the progress of the large-scale network, a system has been proposed in which a higher-level management device is arranged above the above-described network management device and the network management device is hierarchized.
[0007]
In this type of conventional system, the upper management device manages node icons corresponding to one or more communication devices to be managed by the lower management device, and based on the fault management information autonomously notified from the lower management device, In general, a node icon corresponding to each communication device in the domain managed by the lower-level management device is displayed in a symbol color corresponding to the failure occurrence state of the communication device.
[0008]
According to the configuration of this conventional system, the display is complicated because there are always node icons corresponding to a plurality of communication devices constituting the domain under the management of the lower management apparatus on the management screen of the upper management apparatus. There was a trend. In particular, when the number of domains or intra-domain communication devices increases, this tendency becomes prominent, and it takes time to specify the location where a failure has occurred.
[0009]
Moreover, in the conventional system, the only way to know the failure of the managed device is the management screen, so if the administrator does not always look at the management screen of the higher-level management device, the failure occurrence cannot be monitored, inevitably, Each domain cannot be monitored without the host management device itself.
[0010]
In a system in which network management devices are hierarchized, the failure management result of the lower management device is reflected on the higher management device as it is, so it is very important to accurately manage the failure of the lower management device. .
[0011]
As one of the factors that impairs the accuracy of fault management in the lower management device, the occurrence of so-called trap reception failure that cannot receive fault management information (trap) that is autonomously notified from the managed communication device at the autonomous notification timing There is.
[0012]
This trap reception failure in the management apparatus occurs, for example, when the line quality with the managed apparatus deteriorates. In this type of conventional system, an autonomous notification is transmitted from the managed apparatus to the management apparatus. The protocol for this does not support the retransmission procedure, and once the trap reception is lost, the trap cannot be obtained even after the line quality is recovered.
[0013]
As described above, the management device performs processing for updating the symbol color of the node icon corresponding to the communication device under its management in real time based on the received trap. For this reason, when a trap drop occurs, real-time symbol color update processing triggered by trap reception stops, and accurate operation management cannot be performed, and this influence spreads to the upper management apparatus.
[0014]
[Problems to be solved by the invention]
As described above, in the conventional system of the network management device layering method, in the upper management device, the failure in which the node icon corresponding to the communication device constituting the domain under the management of the lower management device is acquired from the lower management device by autonomous notification. Since only the symbol color corresponding to the occurrence state is displayed, the display becomes complicated as the number of domains or intra-domain communication devices increases, and there is a problem that it takes time to specify the location where the failure occurs.
[0015]
Further, in the above conventional system, since the only means to know the failure is the management screen, if the administrator does not always look at the management screen of the higher-level management device, the occurrence of the failure cannot be monitored. There was a problem that each domain could not be monitored without it.
[0016]
Furthermore, in the above conventional system, since the protocol for transmitting the autonomous notification from the managed device to the management device does not have a retransmission procedure, the trap cannot be acquired again once the trap reception failure occurs. There was a problem that real-time symbol color update processing upon reception was stopped and accurate operation management could not be performed.
[0017]
The present invention eliminates the above-mentioned problems, and even when the number of domains or intra-domain communication devices increases, the management screen of the higher-level management device does not become complicated, network management is easy, and the time at which a failure occurs can be shortened. An object is to provide a network system.
[0018]
In addition, another object of the present invention is to add a facility other than the management screen as a means to know the failure, so that the occurrence of the failure can be monitored even if the administrator does not always look at the management screen of the upper management device. Accordingly, it is an object of the present invention to provide a communication network system capable of performing a certain level of network management without the host management device itself.
[0019]
Another object of the present invention is to provide a communication network in which even if a trap reception failure occurs in the management apparatus, the trap with the reception failure can be acquired and reflected in the symbol color update processing, and accurate operation management can be performed at all times. To provide a system.
[0020]
[Means for Solving the Problems]
  To achieve the above object, the invention described in claim 1 is directed to one or a plurality of communication devices, a management device that manages the entire domain including the communication devices, and a host that manages the entire network via the management device. Connect management devices via communication channelsAnd a contact transfer device arranged close to the management device and a contact state display device arranged close to the upper management device and connected to the contact transfer device by communication.Communication network systemBecauseThe management device generates domain state information in which failure management information related to failure occurrence or recovery autonomously notified from the communication device is reflected in an operation state of the entire domain under its own device management, and the domain state information is Domain state relay processing means for autonomous notification to the host management deviceA contact circuit unit that generates contact information; and a contact information processing unit that reflects the domain state to the contact circuit unit based on the domain state information when autonomously notifying the domain state information to the host management device;The upper management device acquires the domain status information autonomously notified from the management device, and associates the domain status information with a domain icon representing a domain under the management of the management device that is the autonomous notification source. Based on the acquired domain status information, a higher management processing means to manage, the domain icon corresponding to the domain under management of the management device that is the autonomous notification source of the domain status information is a symbol indicating the failure occurrence or recovery of the domain Domain icon display processing means for displaying in colorThe contact transfer device includes contact information transfer means for transferring contact information read from the contact circuit unit to the contact status display device, and the contact status display device is a contact transferred from the contact transfer device. Contact alarm display means for displaying a predetermined contact alarm based on informationIt is characterized by comprising.
[0021]
  The invention according to claim 2A communication network system in which one or a plurality of communication devices, a management device that manages an entire domain including the communication device, and a higher-level management device that manages the entire network via the management device are connected via a communication path. The management device generates domain state information in which failure management information relating to the occurrence or recovery of a failure autonomously notified from the communication device is reflected in the operation state of the entire domain under its management, and the domain state information is Based on the failure management information autonomously notified from the communication device, domain state relay processing means for autonomous notification to the higher-level management device, and a device icon corresponding to the communication device that is the autonomous notification source of the failure management information Device icon display processing means for displaying a symbol color indicating the occurrence or recovery of a fault and a communication device under management. The polling means for polling the fault management information periodically, the fault management information acquired by the polling by the polling means, and the fault management information autonomously notified from the communication device are compared, and whether or not they are inconsistent or coincident In response to this, the reception failure determining means for determining whether or not there is an autonomous notification reception failure of the failure management information, and when the reception failure determination means determines that there is an autonomous notification reception failure, according to the content of the failure management information acquired by the polling Updating means for updating the symbol color of the device icon of the polling destination communication device, the upper management device acquires the domain status information autonomously notified from the management device, and High-level management processor that manages in association with the domain icon representing the domain under the management of the autonomous notification source management device And the domain icon corresponding to the domain under the management of the management device that is the autonomous notification source of the domain status information based on the domain status information acquired by the higher-level management processing means is a symbol indicating the failure occurrence or recovery of the domain Domain icon display processing means to display in colorIt is characterized by comprising.
[0025]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.
[0026]
FIG. 1 is a diagram showing the overall configuration of a communication network system according to the present invention. In FIG. 1, each of the ring networks (RNW) 11, RNW 12, RNW 13, and RNW 14 is formed by connecting, for example, four ring node devices (RN) 100 in a ring shape by each ring transmission path 50.
[0027]
Each of these ring networks RNW11, RNW12, RNW13, and RNW14 is connected to one center node device (CN) 150a via each ring transmission path 50.
[0028]
The relationship between RNW21, RNW22, RNW23, RNW24 and CN 150b, and RNW31, RNW32, RNW33, and RNW34 and CN 150c are also realized by the same configuration and connection manner as the relationship between RNW11, RNW12, RNW13, RNW14, and CN 150a.
[0029]
One or a plurality of local terminals 110 are connected to each RN 100 in each RNW (11, 12, 13, 14, 21, 22, 23, 24, 31, 32, 33, 34). In FIG. 1, in particular, only one local terminal 110 connected to each of the two RNs 100 in the RNW 11 is illustrated.
[0030]
The CN 150a, CN 150b, and CN 150c are connected to the exchange 56 via transmission paths 55a, 55b, and 55c, respectively, and are connected to the relay network via transmission paths 60a, 60b, and 60c using, for example, Ethernet. It is connected to management devices (Relay-Network Node Manager: R-NMS) 200a, 200b, 200c.
[0031]
The R-NMSs 200a, 200b, and 200c are connected to the communication network 70 via transmission lines 65a, 65b, and 65c, respectively, and further, a command is sent via a transmission line 75 in which the exchange 71 is inserted at the end of the communication network 70. A network management device (command NMS) 300 is connected.
[0032]
Further, contact transfer devices 210a, 210b, and 210c are installed in the vicinity of the R-NMSs 200a, 200b, and 200c, respectively, and a contact state display device 310 is installed in the vicinity of the command NMS 300. The contact transfer devices 210a, 210b, 210c and the contact state display device 310 are connected by contact transfer paths 80a, 80b, 80c for transmitting contact information, which will be described later.
[0033]
In this system, each RN 100 and CN 150 (150a, 150b, 150c) in each RNW (11, 12, 13, 14, 21, 22, 23, 24, 31, 32, 33, 34) is, for example, ATM ( Asynchronous Transfer Mode (Asynchronous Transfer Mode)
[0034]
An ATM switch is connected to an ATM transmission path realized by a two-level network called a VP (Virtual Path) and a VC (Virtual Channel), and is a fixed-length cell (ATM cell) taken from an input port Is exchanged to an output port in accordance with VPI (Virtual Path Identifier) and VCI (Virtual Channel Identifier) included in the ATM cell.
[0035]
Accordingly, in FIG. 1, each ring transmission path 50 and transmission paths 55a, 55b, and 55c in each RNW are realized by ATM transmission paths.
[0036]
Each RN 100 performs data relay transmission with the adjacent RN 100 and with the local node accommodating local terminal 110 on the ring transmission path 50 in the RNW to which the local node belongs by the switching function.
[0037]
Also, the CNs 150a, 150b, and 150c use the exchange function to perform data relay transmission between the ring transmission lines 50 of each RNW under the management of its own node, and the ring transmission lines 50 and the transmission lines 55a and 55b. , 55c.
[0038]
Thereby, in each RNW, each RN 100 or each local terminal 110 can send and receive data to and from each other RN 100 or other local terminal 110 in the RNW via the ring transmission path 50. In addition, each RN 100 or each local terminal 110 in each RNW is connected to each RN 100 or local terminal in each other RNW under the jurisdiction of the CN 150 via a CN 150 (any one of CN 150a, 150b, and 150c) corresponding to the RNW. 110 can exchange data with each other, and can also exchange data with the RN 100 or the local terminal 110 in each RNW under the jurisdiction of the other CN 150 via the transmission paths 55a, 55b, and 55c.
[0039]
The CNs 150a, 150b, and 150c transmit data to and from the RN 100 or local terminal 110 in each RNW under the jurisdiction of the node, and data to and from the RN 100 or local terminal 110 in each RNW under the control of another CN 150. Not only the transmission but also the R-NMS 200a, 200b, 200c corresponding to the own node via the transmission paths 60a, 60b, 60c, respectively, the failure monitoring of the RN 100 in each RNW under the control of the own node and the own node Data for maintenance and maintenance management can also be transmitted and received.
[0040]
Further, the R-NMS 200a, 200b, 200c uses the data transmission / reception function with each of the above-described CNs 150a, 150b, 150c, and the operational status from each of the CNs 150a, 150b, 150c and the RN 100 in each RNW under its jurisdiction. Management information (failure management information, configuration / status management information, etc., which will be described later) is collected, and the operational status of each RNW (domain) under the jurisdiction is displayed based on this management information, or recognized from the displayed contents In addition to the domain management function that performs control to avoid failure by sending control data to the failed node in the corresponding domain based on the failure occurrence status etc. of each domain, each domain status information indicating this domain management result is transmitted A domain that autonomously notifies the command NMS 300 via the paths 65a, 65b, 65c, the communication network 70, and the transmission path 75. It has a management result relay function.
[0041]
On the other hand, the command NMS 300 receives domain state information notified autonomously from each R-NMS 200a, 200b, 200c, and based on the domain state information, the R-NMS 200a, 200b, 200c and each domain under its management. It has a control function such as displaying the operational status of the system on the screen.
[0042]
As described above, the system of the present invention (see FIG. 1) arranges the R-NMSs 200a, 200b, and 200c that manage domains including a plurality of managed devices (the entire RN 100, CN 150, and RNW) in a plurality of units. By placing an instruction NMS 300 that collects the operating status of the domain under the management of each R-NMS 200a, 200b, 200c and manages the entire network via the R-NMS 200a, 200b, 200c. The network management function is hierarchized.
[0043]
In this configuration, the R-NMSs 200a, 200b, and 200c in the lower layer as viewed from the command NMS 300 receive the failure management information that is autonomously notified from each node (RN 100 and CN 150) in each RNW that configures the managed domain. A domain management function for managing the operation state of the entire domain based on the failure management information, and a domain management result relay function for autonomously notifying the higher-order command NMS 300 of the management result.
[0044]
In order to realize the domain management function, the R-NMS 200a, 200b, 200c has an autonomous notification display application. For example, the autonomous notification display application displays a node icon corresponding to each node (RN100, CN150) in the managed domain on a screen (domain management screen) in a symbol color reflecting the failure state of each node. Process.
[0045]
Moreover, in order to implement | achieve the said domain management result relay function, R-NMS200a, 200b, 200c has a domain state application. When the failure of each node in the domain is detected based on the autonomous notification from the node in each domain, the domain state application reflects the content of the failure in the alarm information for the entire domain, and then the domain state obtained as a result. A process of autonomous notification of information to the command NMS 300 is performed.
[0046]
On the other hand, when viewed from the R-NMS 200a, 200b, and 200c, the higher-level command NMS 300 receives domain state information autonomously notified from each managed R-NMS 200a, 200b, and 200c, and the network is based on this information. Responsible for managing the overall operational status.
[0047]
As one means for realizing this management function, the command NMS 300 has a domain icon display application. This domain icon display application displays domain icons corresponding to the R-NMSs 200a, 200b, and 200c. Specifically, based on the domain state information notified autonomously from the R-NMSs 200a, 200b, and 200c in advance, A process of appropriately updating the color of the prepared domain icon according to the failure rank or the like is performed.
[0048]
As another means for realizing the management function, the command NMS 300 includes a screen connection application. When an arbitrary domain icon is selected on the domain icon display screen, the screen connection application connects to the R-NMS 200 corresponding to the selected domain icon, and the domain currently managed by the R-NMS 200 The management information is acquired, and the domain management screen is displayed based on the domain management information.
[0049]
As yet another means for realizing the management function, the command NMS 300 has a hierarchical screen display application (corresponding to a screen display application 305a described later).
[0050]
The hierarchical screen display application is, for example, in the order of the ring segment configuration screen for each domain managed by each R-NMS 200a, 200b, 200c, each ring configuration screen, each node configuration screen, contact alarm screen for each node, etc. On the domain management screen displayed based on the domain management information acquired from the R-NMS 200 of the connection destination by the above-mentioned screen connection application, and the function of managing the operation status display screen that is hierarchically layered as much as possible When a component is selected, first, an operation status display screen (ring segment configuration screen) corresponding to the selected component is opened at the lower hierarchy of the currently displayed screen, and the lower hierarchy is similarly used. Open operation display screens sequentially (each ring configuration screen → each node configuration screen → contact alarm screen for each node) While gradually, on a production status display screen of each layer is made of a function of displaying by reflecting each component corresponding fault occurrence or fault recovery contents in the acquired domain management information.
[0051]
Further, in the system of the present invention, the contact transfer devices 210a, 210b, and 210c are installed in the vicinity of the R-NMSs 200a, 200b, and 200c, and the contact transfer devices 210a, 210b, and 210c and the contact transfer paths 80a, A contact state display device 310 connected by 80b and 80c is arranged close to the command NMS300.
[0052]
Here, the contact transfer devices 210a, 210b, and 210c contact information read from a contact circuit unit (described later) provided in each corresponding R-NMS 200a, 200b, and 200c via the contact transfer paths 80a, 80b, and 80c. The information is transferred to the information display device 310.
[0053]
On the other hand, the contact state display device 310 is a predetermined contact such as a lamp display or a buzzer sound based on contact information sent from the contact transfer devices 210a, 210b, 210c via the contact transfer paths 80a, 80b, 80c. Alarm display.
[0054]
Next, configurations of the RN 100, the CN 150, the R-NMS 200, and the command NMS 300 in the present system will be described with reference to FIGS.
[0055]
Here, FIG. 2 is a block diagram showing the configuration of the command NMS 300 in this system. FIG. 3 is a block diagram showing the configuration of the R-NMS 200. FIG. 4 is a block diagram showing the configuration of the RN 100 and CN 150.
[0056]
In FIG. 2, a command NMS 300 includes a transmission path interface (I / F) section 301 that controls an interface with the transmission path 75, a control section 302 that controls the entire apparatus, a mouse, a keyboard, and the like. An input unit 303 for performing various instruction input operations, a display unit 304 for displaying various information related to network management, and a memory for storing various information necessary for network management in cooperation with the R-NMS 200 (200a, 200b, 200c) A unit 305 is provided.
[0057]
Further, a contact state display device 310 is installed near the command NMS 300. This contact state display device 310 is connected to contact transfer devices 210a, 210b, 210c installed on the R-NMS 200a, 200b, 200c side by contact transfer paths 80a, 80b, 80c.
[0058]
In the command NMS 300, the storage unit 305 stores a screen display application 305a, a domain icon display application 305b, a screen connection application 305c, management middleware 305d, and a management protocol 305e.
[0059]
The screen display application 305 a is an application that performs overall display processing for the display unit 304. In this display process, as will be described later, the operation status display screens (see FIGS. 8 to 10) of the respective layers are opened based on the domain management information acquired from the connection destination R-NMS 200 by the screen connection application 305c. The hierarchical screen display processing to be displayed is also included.
[0060]
The domain icon display application 305b is an application that performs processing for displaying the managed R-NMS 200 on the display unit 304 as a domain icon based on domain state information autonomously notified from the R-NMS 200.
[0061]
The screen connection application 305c connects to the R-NMS 200 corresponding to the selected domain icon based on the selection operation of an arbitrary domain icon on the domain icon display screen displayed by the domain icon display application 305b. -An application that acquires domain management information managed by the NMS 200 and displays a domain management screen on the display unit 304 based on this information.
[0062]
As the management middleware 305d, for example, an SNMP (Simple Network Management Protocol) manager can be used, and as the management protocol 305e, for example, SNMP / UDP / IP (Internet Protocol) can be used.
[0063]
Each of the applications 305 a, 305 b, 305 c, management middleware 305 d, and management protocol 305 e is read into the control unit 302 and executed under the control of the control unit 302. In FIG. 2, an SNMP manager 302a existing in the control unit 302 indicates management middleware 305d that is read from the storage unit 305 and is being executed.
[0064]
In FIG. 3, the R-NMS 200 communicates with an Ethernet interface (I / F) unit 201 a that manages an interface with the CN 150 with, for example, an Ethernet transmission line 60 (60 a, 60 b, 60 c), and a command NMS 300. A transmission path interface (I / F) unit 201b that controls an interface with a transmission path 65 (65a, 65b, 65c) for the control, a control unit 202 that controls the entire apparatus, a mouse, a keyboard, and the like. An input unit 203 for performing various instruction input operations, a display unit 204 for displaying various information related to network management, such as domain operation status, and various information necessary for network management in cooperation with each node (RN 100, CN 150) in the domain Storage unit 205 for storing the domain, operation of the entire domain under management Constructed comprises a contact hardware (HW) circuit 206 for generating the contact information reflecting state.
[0065]
Further, in the vicinity of the R-NMS 200, a contact transfer device that reads contact information from the contact HW circuit 206 and transfers it to the contact state display device 310 on the command NMS 300 side via the contact transfer path 80 (80a, 80b, 80c). 210 (210a, 210b, 210c) is installed.
[0066]
In the R-NMS 200, the storage unit 205 stores at least an autonomous notification display application 205a, a screen display application 205b, a domain state application 205c, a contact application 205d, a trap polling application 205e, a management middleware 205f, and a management protocol 205g.
[0067]
The autonomous notification display application 205a is an application that performs display processing on the display unit 204 based on information related to a failure autonomously notified from each node in the managed domain (failure management information 106a, 156a: see FIG. 4).
[0068]
The screen display application 205b includes information on the configuration of interface slots and the like of each node in each domain under management, and various states such as internal board operation status and alarm operation (configuration / status management information 106b and 156b) based on this configuration. ; See FIG. 4), an application that performs display processing on the display unit 204.
[0069]
When the failure of each node in the domain is detected based on the failure management information autonomously notified from each node in the managed domain, the domain state application 205c reflects this failure in the alarm state of the entire domain, This is an application that performs processing to autonomously notify the command NMS 300 of domain state information generated as a result.
[0070]
The contact application 205d is an application that performs a process of reflecting the domain state information on the contact HW circuit 206 and causing the contact transfer device 210 to read it when the domain N information is autonomously notified to the command NMS 300.
[0071]
The trap polling application 205e is configured so that each node in the managed domain can relieve a trap reception failure when failure management information (trap) autonomously notified from each node in the managed domain cannot be received at the notification timing. This is an application that performs trap polling at regular intervals.
[0072]
As the management middleware 205f, for example, an SNMP manager can be used, and as the management protocol 205g, for example, SNMP / UDP / IP or the like can be used.
[0073]
The applications 205a, 205b, 205c, 205d, and 205e, the management middleware 205f, and the management protocol 205g are read into the control unit 202 and executed under the control of the control unit 202. In FIG. 3, an SNMP manager 202a existing in the control unit 202 indicates the management middleware 205f read from the storage unit 205 and being executed.
[0074]
4A is a block diagram showing the configuration of the RN 100 among the nodes in each domain, and FIG. 4B is a block diagram showing the configuration of the CN 150.
[0075]
In FIG. 4A, the RN 100 includes interface (I / F) units 101 and 102 and a local terminal 110 that perform control related to transmission / reception of data (ATM cells) with each virtual path on the ring transmission path 50. An input cell from the interface (I / F) unit 103, I / F unit 101, I / F unit 102, or I / F unit 103 that controls the transmission / reception of data to / from the accommodated low-speed line is input to the cell. ATM switch unit 104 that performs cell switching operation to be sent to I / F unit 101 or I / F unit 102 or I / F unit 103 through an output port corresponding to the input port, switching table (cell input port and output port The control unit 105 that controls the cell switching operation in the ATM switch unit 104 in accordance with VPI and VCI). Constructed comprises a storage unit 106 for storing various information including the switching table.
[0076]
In the storage unit 106, in addition to the above switching table, as various information necessary for domain management in the R-NMS 200, fault management information 106a collecting information related to various faults of the own apparatus, the configuration of the interface slot of the own apparatus, The configuration / status management information 106b, the managed middleware 106c, and the management protocol 106d, which collect information related to various statuses such as the internal board operating status and alarm operation based on this configuration, are stored.
[0077]
As the managed middleware 106c, for example, an SNMP agent is used, and as the management protocol 106d, for example, SNMP / UDP / IP is used. The managed middleware 106 c and the management protocol 106 d are read into the control unit 105 and executed under the control of the control unit 105.
[0078]
Further, in addition to the control related to the cell exchange described above, the control unit 105 has a control function for monitoring a failure occurrence state and a change in an operation state in the own device and issuing an autonomous notification based on the monitoring result. . In order to realize this control function, a state monitoring unit 105a and an SNMP agent 105b are provided in the control unit 105.
[0079]
The state monitoring unit 105a monitors a failure occurrence state, a change in an operation state, and the like in the own device.
[0080]
The SNMP agent 105b is responsible for autonomously notifying the R-NMS 200 of information obtained from the above monitoring (failure management information 106a, configuration / state management information 106b held in the storage unit 106). . In FIG. 4A, the SNMP agent 105a existing in the control unit 105 indicates the managed middleware 106c read from the storage unit 106 and being executed.
[0081]
4B, in addition to the components of the RN 100 shown in FIG. 4A, the CN 150 is an Ethernet interface unit for connecting to an Ethernet (transmission path 60) extending between the CN 150 and the R-NMS 200. (I / F part) 157. For the other configurations, the parts having the same names as the parts in the RN 100 each perform the same function (however, the reference numerals of the parts are different from those of the RN 110).
[0082]
FIG. 5 is a diagram showing an example configuration of the RN 100 (the basic configuration is the same for the CN 150) when the ring transmission path 50 (see FIGS. 1 and 4) of the present system is realized by a wireless line. .
[0083]
In this example, an indoor unit (IDU) 20a, an outdoor unit (ODU) 30a, and an antenna 35a are provided on one side of the node main body [the entire RN 100 shown in FIG. 4A] 10, and a similar IDU 20b is provided on the opposite side. , An ODU 30b and an antenna 35b are provided. Further, contact monitoring devices 40a and 40b are connected between the IDU 20a and IDU 20b and the node body 10, respectively.
[0084]
In the configuration of FIG. 5, for example, a radio signal transmitted from the opposite RN 100 existing on the left side of the figure is received by the antenna 35a and input to the node body 10 through the ODU 30a and IDU 20a, and then the antenna is transmitted through the IDU 20b and ODU 30b. 35b and transmitted as a radio signal to another opposing RN 100 existing on the right side of the figure.
[0085]
At this time, the contact monitoring devices 40a and 40b monitor the operation states of the IDU 20a, ODU 30a, IDU 20b, and ODU 30b, respectively, and transfer the contact information corresponding to the operation states into the node main body unit 10.
[0086]
In the node main unit 10 (see FIG. 4A), the state monitoring unit 105a in the control unit 105 (in CN 150, the state monitoring unit 155a in the control unit 155) is transferred from the contact monitoring devices 40a and 40b. Based on the information, the failure occurrence state of the IDU 20a, ODU 30a, IDU 20b, and ODU 30b is recognized, and this state is reflected in the failure management information 106a in the storage unit 106 (same as the failure management information 156a in the storage unit 156).
[0087]
Next, the network management operation of the system of the present invention will be described in light of the configuration shown in FIGS.
[0088]
In the system of the present invention, the RN 100 [see FIG. 4A] detects and notifies the control unit 105 of the state monitoring unit 105a when a failure occurs or recovers in the own device. The control unit 105 collectively manages these detection results as failure management information 106a, determines whether a failure has occurred in the entire apparatus based on the detection result, or has recovered from the failure, and sends an SNMP agent 105b Requests an autonomous notification for failure occurrence or failure recovery according to the judgment result.
[0089]
Upon receiving this request, the SNMP agent 105b issues an autonomous notification including the failure management information 106a to the R-NMS 200 using the management protocol 106d.
[0090]
Similarly, in the CN 150 (see FIG. 4B), when a failure occurs or recovers in the own device, the state monitoring unit 155a detects this and transmits it to the control unit 155. The control unit 155 collectively manages these detection results as failure management information 156a, determines whether a failure has occurred as a whole device or a failure based on the detection results, and determines whether the SNMP agent 155b Requests an autonomous notification for failure occurrence or failure recovery according to the judgment result.
[0091]
Upon receiving this request, the SNMP agent 155b uses the management protocol 156d to issue an autonomous notification including the failure management information 156a to the R-NMS 200.
[0092]
On the other hand, the R-NMS 200 (see FIG. 3) receives an autonomous notification from the RN 100 or the CN 150 regarding the occurrence or failure recovery by the management protocol 205g, and includes autonomous notification information (failure management information 106a or 156a) included therein. To the SNMP manager 202a.
[0093]
The SNMP manager 202a stores the autonomous notification information in the storage unit 205 in association with the notification source address [the IP address of the managed node (RN 100, CN 150) that issued the autonomous notification).
[0094]
Here, the SNMP manager 202a also has a function of managing each managed node (RN100, CN150) as a node icon representing each managed node.
[0095]
In addition, in cooperation with this function and the autonomous notification display application 205a, each managed node is displayed as a node icon on the display unit 204, and the node icon is issued for the managed node of the issue source. Control is performed so that the symbol color is updated and displayed on the display unit 204 in accordance with the content of the autonomous notification information.
[0096]
Specifically, when the autonomous notification display application 205a receives the autonomous notification notification, the autonomous notification display application 205a refers to the notification source address and searches for a node icon managed by the SNMP manager 202a. The failure management information 106a and 156a in the report is referred to, and the color indicating the occurrence of failure or the color indicating failure recovery is reflected on the symbol 204 of the searched node icon on the display unit 204 according to the value. indicate.
[0097]
This autonomous notification display processing is performed every time an autonomous notification is issued from the managed node, and thereby the symbol color display of the node icon of the managed node of the notification source is updated each time.
[0098]
As described above, the R-NMS 200 of the system of the present invention supports a processing function for displaying on the screen using the node icons representing the managed nodes based on the autonomous notification information received from the managed nodes.
[0099]
In addition to the autonomous notification display function described above, the R-NMS 200 has a configuration / state display function for displaying information related to the configuration and state of the managed node. The configuration referred to here is, for example, the configuration of the interface slot on the front face of the managed node housing and each user port therein, and the state is, for example, the operating state of the internal board connected to the interface slot, the power supply state Or it indicates the alarm status.
[0100]
The screen display application 205b is responsible for processing related to this configuration / status display function. The configuration / status display process in the screen display application 205b can be activated in response to a predetermined configuration / status confirmation operation from the input unit 203, for example.
[0101]
As an example of this configuration / state confirmation operation, the administrator may specify an IP address of a managed node to be confirmed in the input unit 102 and then perform an operation to instruct display processing activation. In addition, on the above-described node icon display screen, an operation of clicking in the area of the node icon is performed in a state where a failure occurrence color is displayed with respect to the symbol color of an arbitrary node icon. The display function may be activated.
[0102]
After the startup operation described above, the screen display application 205b uses the management middleware 205f and the management protocol 205g to transmit information related to the configuration and state of the managed node connected by the transmission path 60 to the managed node. Request is made to the managed middleware 106c (managed middleware 156c) of the RN 100 (or CN 150).
[0103]
The request destination RN 100 (CN 150) accepts a request from the screen display application 205b using the management protocol 106d (same management protocol 156d), and receives the request as the managed middleware 106c (same, management protocol 156d). To the managed middleware 156c).
[0104]
Upon receiving the request, the managed middleware 106c (same as managed middleware 156c) receives the request, and the configuration / state management information 106b (same as configuration / state management information 156b) regarding its own device from the storage unit 106 (same as the storage unit 156). ), And a response process for sending the information 106b (same information 156b) to the R-NMS 200 using the management protocol 106d (same management protocol 156d).
[0105]
On the other hand, the R-NMS 200 receives the configuration / state management information 106b (or configuration / state management information 156b) sent out as a response from the managed node using the management protocol 205g, and receives the information 106b (same as the information 106b). , Information 156b) is stored in the management middleware 205f.
[0106]
Further, the screen display application 205b performs a drawing process on the display unit 204 based on the configuration / status management information 106b (same configuration / status management information 156b) stored in the management middleware 205f. In this drawing process, the screen display application 205b displays an image relating to the configuration and status corresponding to each item in the configuration / status management information 106b (same configuration / status management information 156b) acquired from the managed node. Draw the actual image of the node as it is.
[0107]
In general, in a managed node (actual device), for example, an interface slot is provided on the front surface of the casing, and a display element that displays an operation state of an internal board connected to the interface slot, a power supply state, an alarm occurrence state, and the like. Etc. are provided. The actual machine image means image contents that can be recognized in the same manner as when the front of the casing of the managed node (actual machine) is actually viewed.
[0108]
The R-NMS 200 draws the configuration and status of the managed node with the actual machine image as described above, and then periodically acquires the configuration / status management information 106b and 156b of the managed node by the same processing. To do.
[0109]
On the other hand, in the managed nodes (RN100, CN150), the configuration / state in which the latest contents are reflected based on the monitoring results of the state monitoring units (105a, 155a) in response to periodic information acquisition requests from the R-NMS 200 Management information (106b, 156b) is returned.
[0110]
The screen display application 205b uses the configuration / state management information information 106b and 156b acquired periodically, updates the past contents with the latest contents, and continues drawing with the actual machine image. As a result, even if the configuration or state of the managed node changes, the latest configuration and state regarding the managed node are always drawn as an actual machine image. As a result, the administrator in the R-NMS 200 can recognize the latest configuration and state of the managed node in the same way as when actually visiting the managed node and looking at the front of the case. The maintenance and management work can be carried out smoothly.
[0111]
Further, in the R-NMS 200, when the failure of the managed node in the domain is detected based on the autonomous notification information received from the managed node (RN100, CN150), the domain state application 205c displays the content of the failure. After reflecting the alarm state of the entire domain, it has a processing function of autonomously notifying the command NMS 300 of the domain state information generated as a result.
[0112]
In this process, the domain status application 205c reflects the content of the failure in the alarm status of the entire domain every time a failure of the managed node in the domain is detected based on the autonomous notification from the managed node in the domain. Then, after updating the domain state information, the SNMP manager 202a is requested to issue an autonomous notification to the command NMS300.
[0113]
Upon receiving this request, the SNMP manager 202a uses the management protocol 205g to issue an autonomous notification of domain state information to the command NMS 300 via the transmission path I / F unit 201b. The reported domain state information is transmitted to the command NMS 300 via the transmission path 65 (65a, 65b, 65c), the communication network 70, and the transmission path 75.
[0114]
On the other hand, the command NMS 300 (see FIG. 2) receives domain state information autonomously notified from the R-NMS 200 from the transmission path 75 via the transmission path I / F unit 301 by the management protocol 305e and passes it to the SNMP manager 302a.
[0115]
The SNMP manager 302a stores the domain state information notified autonomously in the storage unit 305 in association with the IP address of the R-NMS 200 that is the autonomous notification source.
[0116]
Here, the SNMP manager 302a manages all the managed R-NMSs 200 as domain icons and cooperates with the domain icon display application 305b to display each R-NMS 200 on the display unit 304 as a domain icon. have.
[0117]
Specifically, when receiving the autonomous notification notification from the R-NMS 200, the domain icon display application 305b searches for the domain icon managed by the SNMP manager 302a based on the notification source address, while the storage unit 305 The failure content of the domain state information stored in the search is retrieved, and on the display unit 304, the color indicating the occurrence of failure or the color indicating failure recovery is reflected on the searched domain icon according to the failure content. indicate.
[0118]
This domain icon display processing is performed each time an autonomous notification of domain state information is received from the R-NMS 200, and the color display of the domain icon corresponding to the R-NMS 200 of the reporting source is updated each time. .
[0119]
FIG. 6 is a diagram showing a display example of a domain icon display screen (network submap screen) based on the display processing of the domain icon display application 305b in the command NMS300.
[0120]
As can be seen from the figure, each managed domain (R-NMS) is represented by a domain icon on the network submap screen. Moreover, on this screen, the operational status of each domain is represented by the color of the icon. The relationship between the operation state of each domain and the display color of the icon is as shown in Table 1 below, for example.
[0121]
[Table 1]

On the network submap screen of FIG. 6, the domain icon appended with “Tokyo” corresponds to, for example, the domains (including RNWs 11, 12, 13, and 14) managed by the R-NMS 200a in FIG. Similarly, the domain icon attached with Kanagawa Prefecture corresponds to the domain (including RNW 21, 22, 23, 24) under the management of the R-NMS 200b in FIG. 1, and the domain icon attached with Chiba Prefecture is shown in FIG. Corresponds to a domain (including RNWs 31, 32, 33, and 34) under the management of the R-NMS 200c.
[0122]
In this example, the domain icon appended with “Tokyo” is displayed in red, and it can be seen that the domain under the management of the R-NMS 200a corresponding to the domain icon has failed and is in a danger zone.
[0123]
By selecting an arbitrary domain icon on the network submap screen of FIG. 6, the domain (R-NMS 200) corresponding to the selected domain icon is logged in, and a domain submap screen as shown in FIG. 7 is displayed. Can be displayed.
[0124]
The display control in this case can be realized as follows. That is, in the NMS 300, on the network submap screen (see FIG. 6) displayed on the display unit 304, an operation of double-clicking an arbitrary domain icon on the screen using the mouse from the input unit 303 is performed. Then, the SNMP manager 302a notifies the screen connection application 305c to that effect.
[0125]
As a result, the screen connection application 305c requests the SNMP manager 202a of the R-NMS 200 corresponding to the selected domain icon to transfer the domain management result using the SNMP manager 302a and the management protocol 305e.
[0126]
The requested R-NMS 200 receives the request using the management protocol 205g and passes this request to the SNMP manager 202a. Upon receiving this request, the SNMP manager 202a receives the domain management information (failure management information 106a, 156a and configuration / state management information 106b, 156b collected from the managed node) managed by the own device from the storage unit 205. Using the read and management protocol 205g, response processing sent to the command NMS 300 is performed.
[0127]
In response to this, the command NMS 300 uses the management protocol 305e to receive the domain management information transmitted as a response from the R-NMS 200, and causes the SNMP manager 302a to store the information in the storage unit 305.
[0128]
Next, the SNMP manager 302a notifies the screen connection application 305c that the domain management information has been fetched from the R-NMS 200. In response to this notification, the screen connection application 305 c performs a process of displaying a domain submap screen as shown in FIG. 7 on the display unit 304 based on the domain management information stored in the storage unit 305.
[0129]
The domain submap screen in FIG. 7 is displayed, for example, by double-clicking a domain icon (icon labeled as Tokyo) whose symbol color is displayed in red on the network submap screen in FIG. is there.
[0130]
On the domain submap screen (see FIG. 7) in this case, an icon (representing each RNW 21, 22, 23, 24 constituting the domain (R-NMS 200b in FIG. 1) corresponding to the double-clicked domain icon ( (Hereinafter referred to as a ring icon) is displayed in a symbol color reflecting the operational status of each of the RNWs 21, 22, 23, and 24. In this case, the relationship between the operation state and the symbol color is the same as that of the network submap screen described above.
[0131]
In the domain submap screen of FIG. 7, the ring icon appended with ATM ring 1 corresponds to, for example, the RNW 11 under the management of the R-NMS 200a in FIG. Similarly, the ring icon labeled ATM ring 2 corresponds to RNW 12, the ring icon labeled ATM ring 3 corresponds to RNW 13, and the ring icon labeled ATM ring 4 corresponds to RNW 14, respectively.
[0132]
In this example, the ring icon labeled ATM ring 1 is displayed in red, and it can be seen that a failure has occurred in the RNW 11 corresponding to the ring icon and is in a danger zone.
[0133]
By selecting an arbitrary ring icon on the domain submap screen in FIG. 7, the ring segment map screen as shown in FIG. 8 corresponding to the segment structure of the RNW corresponding to the selected ring icon is displayed. Can do.
[0134]
The display control in this case can be realized as follows. That is, in the NMS 300, on the domain submap screen (see FIG. 7) displayed on the display unit 304, an operation of double-clicking an arbitrary ring icon on the screen from the input unit 303 is performed. Then, the SNMP manager 302a notifies the screen display application 305a to that effect.
[0135]
The screen display application 305a includes, for example, a ring segment map screen for each ring in the domain under management of each R-NMS 200a, 200b, and 200c, a ring management screen, a node management screen for each node in each ring, and each node The operation status display screen is managed in a hierarchy as much as possible in the order of the contact alarm management screens.
[0136]
Upon receiving notification from the SNMP manager 302a that an arbitrary ring icon on the domain submap screen (see FIG. 7) has been double-clicked, first, a lower layer of the domain submap screen and the selected one are selected. The ring segment map screen (see FIG. 8) corresponding to the ring icon is opened, and each icon such as a node icon on the screen is acquired from the connection destination R-NMS 200 using the screen connection application 305c. Processing for reflecting and displaying the occurrence of failure or the contents of failure recovery in the domain management information (failure management information 106a, 156a) in the storage unit 305 is performed.
[0137]
FIG. 8 shows a display example of the ring segment map screen when, for example, the ATM ring 1 is double-clicked on the domain submap screen in FIG. In this example, node icons such as “RN device 101” and “RN device 102”, operation state icons such as “ring 1 management activation”, and the like are displayed in a manner reflecting the operation state, and “RN device” A state in which a loopback (labeled as LB in the figure) between “101” and “RN device 102” is being executed is also displayed.
[0138]
By selecting (double-clicking) an arbitrary node icon on the ring segment map screen in FIG. 8, a node management screen as shown in FIG. 9 showing the operation state of the node corresponding to the selected node icon is displayed. can do.
[0139]
The display control in this case can be realized as follows. That is, in the NMS 300, on the ring segment map screen (see FIG. 8) displayed on the display unit 304, an operation of double-clicking an arbitrary node icon on the screen from the input unit 303 is performed. Then, the SNMP manager 302a notifies the screen display application 305a to that effect.
[0140]
Upon receiving the notification, the screen display application 305a opens a node management screen (see FIG. 9) of the node corresponding to the node icon double-clicked on the lower layer of the currently displayed ring segment map screen. And the domain management information (failure management information 106a, 156a) in the storage unit 305 acquired from the R-NMS 200 of the connection destination using the screen connection application 305c for each of these components. Processing to reflect the contents of failure occurrence or failure recovery in the middle.
[0141]
In the node component display processing in this case, the screen display application 305a corresponds to each item based on the configuration / state management information 106b and 156b of the domain management information acquired by the screen connection application 305c. For example, an image showing the configuration and state is drawn on the display unit 304 as it is as the actual machine image of the node.
[0142]
In general, with regard to the structure of the actual device of the managed node, for example, an interface slot etc. is provided on the front of the casing, and the operation status of the internal board connected to this interface slot etc., the power supply status or the alarm occurrence status etc. are displayed Elements and the like are provided. The actual machine image means image contents that can be recognized in the same manner as when the actual machine structure of these managed nodes is viewed from the front of the chassis.
[0143]
Therefore, the administrator who is in the command NMS 300 can grasp the state of the node in detail in the same manner as the node is actually viewed by looking at the node management screen in FIG.
[0144]
Further, when an arbitrary component display area is double-clicked on the node management screen in FIG. 9, the double-clicked display area is enlarged and displayed. This display process is also performed by the screen display application 305a.
[0145]
Further, by selecting “Fault” from the display menu on the node management screen in FIG. 9 and selecting “Contact alarm” in the pop-up window displayed thereby, the contact as shown in FIG. An alarm management screen can be displayed.
[0146]
The display control in this case can be realized as follows. That is, in the NMS 300, if there is a selection input of the “contact alarm” from the input unit 303 based on the display content of the node management screen (see FIG. 9) displayed on the display unit 304, the SNMP manager 302a does so. Is notified to the screen display application 305a.
[0147]
Upon receiving the notification, the screen display application 305a opens a contact alarm management screen (see FIG. 10) related to the selected “contact alarm” at a lower hierarchy of the currently displayed node management screen, and on the screen. For each contact alarm item in FIG. 5, failure occurrence or failure recovery in the domain management information (failure management information 106a, 156a) in the storage unit 305 acquired from the R-NMS 200 of the connection destination using the screen connection application 305c A process of reflecting the contents and displaying them is performed.
[0148]
The contact alarm management screen in FIG. 10 includes the following components.
1) “Title bar” displays the screen name.
2) “Contact number” indicates the contact number.
3) “Contact alarm status” displays the contact alarm status in color. The relationship between the contact alarm state and the color is, for example, as shown in Table 2 below.
[Table 2]

4) “Contact alarm name” displays the contact name. You can also enter comments in this field.
5) “Contact alarm name display list box (display)” displays contact numbers and contact alarm names in a list format. “Contact number (display)” displays a contact number.
6) “Contact number (display)” displays the contact number.
7) “Contact alarm name (display)” displays the contact alarm name.
8) “Vertical scroll bar (operation)” is an operation tool for scrolling the contact alarm name display list box.
9) “Save button (operation)” is an operation tool for saving information on the display screen to a file.
10) “Conversion button (operation)” is an operation tool for converting a file (CSV format) saved using the “save button” from, for example, EUC format to S-JIS format.
11) The “end button” is an operation tool for ending this screen.
12) In the “status bar”, a message indicating the status of the NMS application is displayed. A list of messages is shown in Table 3 below.
[Table 3]

Furthermore, the screen display application 305a also performs the following display processing. For example, when the “save button” is selected on the contact alarm management screen shown in FIG. 10, the contact alarm storage screen shown in FIG. 11 is displayed.
[0149]
In this contact alarm storage screen, the “stored file name” field is used for displaying the default name and changing the file name. The saved file name in this case is configured in the format of (file name) / login home directory / POINT ***. CVS (*** is the node IP address).
[0150]
On the same screen, when the “OK” button is selected, the file is saved in the file with the above-described save file name. In this case, the file format is the CSV format (separated by commas (,)). Also, the contents of one line are written in one line. The contents of the file are the device name, contact number, and contact comment.
[0151]
In the same screen, the “cancel button” is an operation tool for ending the same contact alarm storage screen. By operating this “cancel button”, the display returns to the contact alarm management screen in FIG.
[0152]
When the fault status display is to be ended from the contact alarm management screen in FIG. 10, the screens that have been opened so far are closed in order and returned to the initial screen (network submap screen in FIG. 6), and the initial screen is closed. Do.
[0153]
In the state where the initial screen in FIG. 6 is displayed, after confirming the detailed operation state of an arbitrary domain, after double-clicking the domain icon corresponding to the domain (that is, the screen connection application 305c is started). After), when the connection from the command NMS 300 to the R-NMS 200 fails, a pop-up window (connection error screen) as shown in FIG. 12 is displayed. After that, click the “Reconnect” button in the window to reconnect, or click the “Cancel” button to cancel.
[0154]
Causes of connection failure to the R-NMS 200 include communication timeout due to congestion of the network line, power-off of the connection destination R-NMS 200, IP address error of the specified R-NMS 200 held by the command NMS 300, An IP address setting error of the specified R-NMS itself, a failure of a network device (hub, router, etc.), a failure of a communication cable (disconnection, connector failure, etc.) can be considered. Therefore, the administrator needs to confirm these factors before reconnecting on the window in FIG.
[0155]
The above is the description of the display control based on the failure state display function supported by the screen display application 305a of the command NMS 300. Next, the display control based on the failure information display function supported by the application 305a will be described. To do.
[0156]
This failure information display function is a function for collecting failure management information sent from each managed R-NMS 200 and displaying it as character information. By analyzing the failure management information displayed by this function, it is also possible to find out the cause of the failure. Further, according to this function, it is possible to cope with processing in which real-time and accumulated fault management information is extracted and displayed based on a certain condition.
[0157]
Hereinafter, a procedure for displaying the failure management information collected and accumulated in the command NMS 300 and each item of the screen display will be described.
[0158]
As an initial stage of this procedure, an “event category” as shown in FIG. 13 is displayed on the display unit 304 of the command NMS 300. When the left button corresponding to “all events” is clicked on this “event category” screen, an “all event browser” screen as shown in FIG. 14 is displayed.
[0159]
The display of the “all event browser” screen can be realized by the following control, for example. That is, in the NMS 300, when there is an operation input for clicking the left button corresponding to “all events” from the input unit 303, the SNMP manager 302a notifies the screen display application 305a to that effect.
[0160]
Upon receiving the notification, the screen display application 305a reads out the failure management information 106a, 156a in the storage unit 305 that has already been acquired from the connection destination R-NMS 200 using the screen connection application 305c, and the failure management information 106a and 156a are displayed as character information on the display unit 304 in the manner shown in FIG.
[0161]
This “all event browser” screen includes the following components.
1) “Consignment” is a check mark indicating whether or not the event has been accepted.
2) “Importance” displays the importance of the event. The importance is classified into, for example, five levels, and is realized by color coding as shown in Table 4 below.
[Table 4]

3) “Date and time” displays the date and time, day of the week, and time when the event occurred.
4) “Source” displays the IP address of the node where the event occurred.
5) “Message” displays a brief description of the event and the node name.
[0162]
By the way, in the R-NMS 200 (see FIG. 3) of the system of the present invention, the domain state application 205c obtains the domain state information based on the failure management information 106a, 156a collected from each node (RN100, CN150) in the managed domain. When updating and autonomous notification to the command NMS 300, the contact application 205d is activated.
[0163]
The contact application 205d performs processing for reflecting the alarm state of the entire domain on the contact HW circuit 206 based on the updated domain state information. The contact information of the contact HW circuit 206 at this time is read by the contact transfer device 210 (210a, 210b, 210c) and the contact state installed on the command NMS 300 side via the contact transfer path 80 (80a, 80b, 80c). It is transferred to the display device 310.
[0164]
On the other hand, on the command NMS 300 (see FIG. 2) side, contact information transferred from the contact transfer device 210 on the R-NMS 200 side is received, and, for example, lamp display or buzzer sound output is performed according to the content of the contact information. The domain status alarm is displayed by the predetermined method.
[0165]
As described above, according to the configuration and control of the R-NMS 200 and the command NMS 300 in the system according to the present invention in which the network management function is hierarchized, the manager on the command NMS 300 side, unless particularly required, uses the command NMS 300. Network management can be performed while viewing the above-described domain icon display screen displayed on the screen.
[0166]
In this case, since there is no node icon corresponding to each node constituting the domain on the domain icon display screen, the display does not become complicated even if the number of domains or nodes in the domain increases, and fault monitoring is easy. become.
[0167]
In addition, if a desired domain icon is selected on the domain icon display screen as necessary, such as when the color of the corresponding domain icon changes to a failure color due to a failure in the domain, the selected domain icon Since the domain management screen based on the domain management information managed by the R-NMS 200 corresponding to is displayed, operation monitoring at each ring level in the domain can be performed based on this display content.
[0168]
Further, when an arbitrary domain component is selected on the domain management screen, first, an operation status display screen (ring segment configuration screen) corresponding to the selected component at the lower hierarchy of the currently displayed screen. Is displayed with the contents reflecting the operation status, and the operation display screen of the lower hierarchy is opened in the order of the hierarchy, for example, each ring configuration screen → each node configuration screen → contact alarm screen for each node in the same manner, and the operation status is displayed. Since the reflected contents can be displayed, detailed operation monitoring at a desired hierarchical level can be performed with a simple selection operation, and the time until the location where a failure occurs can be shortened.
[0169]
In the system of the present invention, the command NMS 300 also has a contact state display function by a separate contact state display device 300 in addition to the domain icon display function for the monitor screen in the device itself. According to this configuration, the administrator on the NMS 300 side can recognize a certain operational state change based on the contact alarm display from the contact state display device 310, without always looking at the management screen of the NMS 300. The minimum network management can be performed without the command NMS 300 itself.
[0170]
Incidentally, in the R-NMS 200 (see FIG. 3) of the system of the present invention, the SNMP manager 202a manages the managed devices (RN100, CN150, ring, etc.) as device icons representing these devices, and also displays the autonomous notification display application 205a. In cooperation with, a process of displaying each of these managed devices on the display unit 204 as a device icon is performed.
[0171]
The autonomous notification display application 205a refers to the source address when the autonomous notification notification of the failure management information 106a, 156a (hereinafter referred to as a trap) is received from each managed device. While searching for the device icon managed by the SNMP manager 202a, the content of the trap in the autonomous notification issuance at this time is referred to, and the symbol color of the searched device icon is determined according to its value. The displayed color or the color indicating failure recovery is updated and displayed on the display unit 204.
[0172]
On the other hand, in the managed devices (RN100, CN150), the trap autonomous notification issuance is performed by the management protocols 106d and 156d, respectively, and SNMP / UDP / IP is used as the protocol in this case as described above. .
[0173]
However, this protocol has no retransmission procedure. For this reason, when the line quality between the R-NMS 200 and the managed device deteriorates, the trap does not arrive at the R-NMS 200 even though the managed device sends a trap, that is, trap reception. Drops can occur.
[0174]
When a trap reception drop occurs, real-time symbol color update by trap reception for the above-described device icon stops, and the R-NMS 200 cannot perform accurate operation management of the managed device.
[0175]
As a countermeasure for this, in the system according to the present invention, traps that have been missed by trapping until then are performed by polling traps in the managed device from the R-NMS 200 to the managed device at a fixed period. Also, it is surely taken into the R-NMS 200 and immediately reflected in the symbol color update process.
[0176]
In the configuration of FIG. 3, a trap polling application 205 e provided in the storage unit 205 of the R-NMS 200 is an application that performs a process of relieving trap reception failure by the trap polling described above.
[0177]
FIG. 15 is an operation conceptual diagram of a failure state check process related to trap polling processing by the trap polling application 205e.
[0178]
In FIG. 15, reference numeral 91 denotes a database for storing managed device information provided by the management middleware 205f (SNMP manager 202a). Reference numeral 92 denotes a managed device symbol managed by the management middleware 205f, and stores a value (symbol status) representing the symbol color of the icon of each managed device. Reference numeral 93 denotes an event process that manages an event (trap) notification service provided by the management middleware 205f. Reference numerals 94 and 95 denote nodes and rings as managed devices, respectively.
[0179]
Hereinafter, the processing flow of the failure state check process in FIG. 15 will be described with reference to FIG. FIG. 16 is a flowchart showing trap polling processing by the trap polling application 205e.
[0180]
During network management execution by the R-NMS 200, the trap polling application 205e counts a predetermined period that is predetermined as the polling execution interval, and every time the fixed period times out (step 160 YES), the database of the management middleware 205f The managed device (node 94, ring 95) information is acquired from 91 (step 161). Next, based on the acquired managed device information, a symbol status indicating the symbol color of the icon of each device is read from the managed device symbol 92 managed by the management middleware 205f (step 162).
[0181]
Next, the trap polling application 205e selects the first managed device based on the managed device information acquired in step 161, and sends a failure status acquisition request to the managed device (step 163).
[0182]
In response to this failure status acquisition request, the management middleware 205f uses the management protocol 205g to request the SNMP agents 105b and 155b of the corresponding managed device to transfer traps.
[0183]
On the other hand, the request destination managed device (see FIG. 4) passes the transfer request to the SNMP agents 105b and 155b using the management protocols 106d and 156d.
[0184]
Upon receiving this transfer request, the SNMP agents 105b and 155b read out the failure management information 106a and 156a from the storage units 106 and 206, and use the management protocols 106d and 156d for the information 106a and 156a. The response process sent to is performed.
[0185]
On the other hand, the R-NMS 200 receives the failure management information 106a and 156a sent out as a response from the managed device using the management protocol 205g, and passes the information 106a and 156a to the management middleware 205f. Furthermore, the management middleware 205f delivers the fault management information 106a and 156a to the trap polling application 205e, thereby realizing trap polling (fault management information 106a and 156a).
[0186]
During this time, the trap polling application 205e monitors whether or not the connection with the managed device of the polling destination has failed (step 164). If the connection fails (step 164 YES), for example, a connection error shown in FIG. Connection error processing (step 170) such as reconnection is attempted using the screen.
[0187]
If the connection with the managed device to be polled is not a failure (step 164 NO), the trap polling application 205e next checks whether a trap has been received (step 165).
[0188]
If a trap is received (YES in step 165), the trap polling application 205e checks whether there is a next polling target node (step 166). If there is a next node (YES in step 166), step 163 is performed. Returning to the above, trap polling for this node is performed through the same processing as described above (steps 163 to 166). This polling is performed for all managed devices that have acquired managed device information in step 161.
[0189]
During this time, if it is determined that there is no next polling target node (NO in step 166), the trap polling application 205e displays the trap value of each node polled so far and the symbol status of each node acquired in step 162. The corresponding ones are compared (step 167), and it is checked whether there is a mismatch (step 168).
[0190]
If there is a mismatch (YES in step 168), it is determined that there has been a trap reception failure in the past, and the event is transmitted via the event process 93 that manages the event notification service provided by the management middleware 205f. The autonomous notification display application 205a is instructed to update the symbol status (symbol color) to a color reflecting the failure state of the acquired trap (step 169).
[0191]
The autonomous notification display application 205a updates the symbol color of the corresponding managed device in accordance with the instruction from the event process 93. That is, a process is performed in which the symbol status of the managed device is updated to match the polled value and stored in the managed device symbol 92.
[0192]
When the polled value of each node's trap matches the symbol status of each node acquired in step 162 (NO in step 168), or the autonomous notification display application 205a polls the symbol status of the managed device. After performing the process of updating to match the acquired value and storing it in the managed apparatus symbol 92, the process returns to the initial step (step 160) of the trap polling process.
[0193]
In the above-described polling process, the trap polling target is not limited to the node 94 but may be the ring 95 (see FIG. 15).
[0194]
As described above, in the R-NMS 200 of the system of the present invention, the trap polling application 205e performs trap polling for the failure management function of the managed device at a constant period, and the trap failure information obtained thereby and the predetermined failure information Compared with the managed device status symbol that is updated in real time at the trap reception timing, and if it does not match, it is determined that trap reception failure has occurred in the past, and the failure information obtained by polling the symbol color The autonomous notification display application 205a is instructed to update to a color representing the information, and the autonomous notification display application 205a performs processing to update the symbol color of the managed device according to the instruction.
[0195]
According to this processing function, even if a trap reception failure occurs in the trap reception operation at the predetermined timing, the trap reception failure trap is acquired from the managed device during the polling period thereafter. The symbol color can be updated according to the failure state, and the reliability of network failure management depending on the symbol color can be improved.
[0196]
The present invention is not limited to the above-described embodiment, and can be appropriately changed or applied without departing from the spirit of the present invention. For example, the configuration of the domain according to the present invention is not limited to the RNW in which the managed nodes are connected in a ring shape as shown in FIG. 1, but the managed nodes are connected linearly or in a star shape. Various connection forms such as these are also allowed.
[0197]
15 and 16 is not limited to the trap autonomous notification of a trap between a node or ring and the R-NMS 200, but between the R-NMS 200 and a higher-level command NMS 300. It can also be applied to trap autonomous notifications.
[0198]
【The invention's effect】
  As described above, according to the present invention, the management device that manages the entire domain including one or more communication devices.And a high-order management device for managing the entire network via the management device, connected by a communication path, a contact transfer device is installed close to the management device, and a contact status display device is installed close to the high-order management device Consisting ofThe management device generates domain state information that reflects the failure management information acquired from the managed communication device in the operational status of the domain under its own device management, and autonomously notifies the higher-level management deviceAndBased on the domain status information autonomously notified from the management device, the upper management device indicates the occurrence or recovery of the domain icon corresponding to the domain managed by the management device that is the autonomous notification source of the domain status information Display in symbol colorOn the other hand, when the management device autonomously notifies the higher-level management device of the domain status information, the management device reflects the domain status on the contact circuit unit based on the domain status information, and the contact transfer device installed in the vicinity of the management device is The contact information read from the contact circuit unit is transferred to a contact state display device installed close to the upper management device, and the contact state display device displays a predetermined contact alarm display based on the contact information transferred from the contact transfer device. Is what you do.
[0199]
  According to such a configuration, on the monitoring screen of the host management device, icons for the number of domains (domain icons) are displayed in symbol colors indicating the occurrence or recovery of the corresponding domain,Since there are no device icons corresponding to a plurality of communication devices constituting the domain, even if the number of domain or intra-domain communication devices increases, the display does not become complicated, and fault monitoring becomes easy.
[0200]
  Further, according to the above configuration, in parallel with the display of the domain icon on the upper management device, the contact status display device installed close to the upper management device transfers the information from the contact transfer device adjacent to the management device. Since a predetermined contact alarm display (lamp display, buzzer sound, etc.) is performed based on the contact information, the administrator on the upper management device side monitors only the contact state during normal operation without a contact alarm (domain icon, for example). The management screen of the higher-level management device (domain icon display) through the operation of confirming the details for the corresponding domain icon on the domain icon display screen when the contact displays an alarm) Even if you do not always look at the screen), you can recognize a certain change in operating status by looking at the contact alarm display on the contact status display device, An alarm state of the entire network can be easily grasped over.
[0203]
Further, in the present invention, the communication device polls the managed communication device for failure management information at a constant cycle, and the failure management information acquired by this polling and the failure management information autonomously notified from the communication device. If the two do not match, it is determined that there has been a failure in receiving the autonomous notification of the failure management information, and the symbol of the device icon of the communication device that is the polling destination according to the content of the failure management information acquired by the polling Since the color has been updated, even if failure management information (trap) reception failure occurs at the autonomous notification reception timing, the trap reception failure will occur according to the trap reception failure within the fixed period thereafter. Symbol color update processing can be performed, and the reliability of network management using the symbol color as a key can be improved.
[Brief description of the drawings]
FIG. 1 is a diagram showing an overall configuration of a communication network system according to the present invention.
FIG. 2 is a block diagram showing the configuration of a command NMS in the system of the present invention.
FIG. 3 is a block diagram showing a configuration of an R-NMS of the system of the present invention.
FIG. 4 is a block diagram showing the configuration of RN and CN of the system of the present invention.
FIG. 5 is a diagram showing a configuration example of an RN when a ring transmission path is realized by a wireless line.
FIG. 6 is a view showing a display example of a domain icon display screen in a command NMS.
FIG. 7 is a diagram showing a display example of a domain submap screen in a command NMS.
FIG. 8 is a diagram showing a display example of a ring segment map screen with a command NMS.
FIG. 9 is a diagram showing a display example of a node management screen with a command NMS.
FIG. 10 is a diagram showing a display example of a contact alarm management screen with a command NMS.
FIG. 11 is a diagram showing a display example of a contact alarm storage screen with a command NMS.
FIG. 12 is a diagram showing a display example of a connection error screen when connection from the command NMS to the R-NMS fails.
FIG. 13 is a diagram showing a display example of an initial screen when a failure information display function is activated by a command NMS.
FIG. 14 is a diagram showing a failure information display example by a failure information display function in a command NMS.
FIG. 15 is an operation conceptual diagram of a failure state check process related to trap polling processing in an R-NMS.
FIG. 16 is a flowchart showing trap polling processing in the R-NMS.
[Explanation of symbols]
10 Node body
20a, 20b Indoor unit (IDU)
30a, 30b Outdoor unit (ODU)
35a, 35b antenna
40 Contact monitoring device
50 Ring transmission line
55a, 55b, 55c, 60a, 60b, 60c, 65a, 65b, 65c, 75 Transmission path
56,71 switch
80a, 80b, 80c Contact transfer path
100 Ring node equipment (RN)
101, 102, 103 interface (I / F) section
104 Switch part
105 Control unit
105a State monitoring unit
105b SNMP agent
106 Storage unit
106a Fault management information
106b Configuration / state management information
106c Management middleware
106d Management protocol
110 Local terminal
150a, 150b, 150c Center node device (CN)
151, 152, 153 Interface (I / F) section
154 Switch part
155 Control unit
155a State monitoring unit
155b SNMP agent
156 storage unit
156a Fault management information
156b Configuration / state management information
156c Management middleware
156d Management protocol
157 Ethernet interface (I / F) section
200 Relay network management device (R-NMS)
201a Ethernet interface (I / F) section
201b Transmission path interface (I / F) section
202 Control unit
202a SNMP manager
203 Input section
204 display
205 storage unit
205a Autonomous notification display application
205b Screen display application
205c Domain State Application
205d Contact application
205e Trap polling application
205f Management middleware
205g management protocol
206 Contact hardware (HW) circuit
210a, 210b, 210c Contact transfer device
300 Command network management device (command NMS)
301 Transmission path interface (I / F) section
302 control unit
302a SNMP (Simple Network Management Protocol) manager
303 Input section
304 display unit
305 storage unit
305a Screen display application
305b Domain icon display application
305c Screen connection application
305d Management middleware
305e Management protocol
310 Contact state display device

Claims (2)

One or a plurality of communication devices, a management device that manages the entire domain including the communication device, and a higher-level management device that manages the entire network via the management device are connected via a communication path , and close to the management device A communication network system including a contact transfer device arranged and a contact status display device arranged in proximity to the upper management device and connected to the contact transfer device by communication ,
The management device
Generates domain state information reflecting failure management information related to the occurrence or recovery of the failure autonomously notified from the communication device in the operation state of the domain under the management of the device itself, and makes the domain state information autonomous to the higher-level management device A domain state relay processing means to notify ;
A contact circuit unit for generating contact information;
Contact information processing means for reflecting the domain state to the contact circuit unit based on the domain state information when autonomously notifying the domain state information to the upper management apparatus ,
The upper management device is:
Upper management processing means for acquiring the domain status information notified autonomously from the management device and managing the domain status information in association with a domain icon representing a domain under management of the management device that is the autonomous notification source;
Based on the acquired domain state information, a domain icon display process for displaying the domain icon corresponding to the domain under the management of the management device that is the autonomous notification source of the domain state information in a symbol color indicating the failure or recovery of the domain and means,
The contact transfer device includes:
Contact information transfer means for transferring contact information read from the contact circuit section to the contact state display device
Comprising
The contact state display device
A communication network system comprising contact alarm display means for displaying a predetermined contact alarm based on contact information transferred from the contact transfer device . A communication network system in which one or a plurality of communication devices, a management device that manages an entire domain including the communication device, and a higher-level management device that manages the entire network via the management device are connected via a communication path. ,
The management device
Generates domain state information reflecting failure management information related to the occurrence or recovery of the failure autonomously notified from the communication device in the operating state of the domain under the management of the own device, and makes the domain state information autonomous to the higher-level management device A domain state relay processing means to notify;
A device icon display that displays a device icon corresponding to the communication device that is the autonomous notification source of the failure management information in a symbol color indicating the occurrence or recovery of the failure of the communication device based on the failure management information notified autonomously from the communication device Processing means;
Polling means for polling failure management information at a fixed period for a managed communication device;
The failure management information acquired by polling by the polling means is compared with the failure management information notified autonomously from the communication device, and whether or not there is a failure in receiving the autonomous notification of the failure management information depending on whether or not they match or does not match A reception failure judging means for judging;
An update unit that updates the symbol color of the device icon of the communication device at the polling destination according to the content of the failure management information acquired by the polling when the reception failure determination unit determines that there is an autonomous notification reception failure;
Comprising
The upper management device is:
Upper management processing means for acquiring the domain status information notified autonomously from the management device, and managing the domain status information in association with a domain icon representing a domain under management of the management device that is the autonomous notification source;
Based on the domain status information acquired by the higher-level management processing means, the domain icon corresponding to the domain under management of the management device that is the autonomous notification source of the domain status information is displayed in a symbol color indicating failure occurrence or recovery of the domain Domain icon display processing means to display and
A communication network system comprising:

Images