HIOKI CM CLAMP POWER METER

48933

Using e-mail delivery logs collected at an middle-scale enterprise network, we evaluate the effectiveness of the approaches and compare their advantages and disadvantages. In this paper, we propose a traffic control paradigm using overlay networks which are logical networks over IP networks in the Internet scale. RCC, Reliable communication and control 60 5 - 8 Ecosine max - manuale d'uso e installazione rev02 traduzione user and installation manual Italian translation.

出展者検索 | nano tech 新しい社会変化を支えるナノテクノロジー Nanotechnology with New Social [***]

Once downloaded, run the file on your computer to see the installation instructions. ドライバ/ソフトウェアのダウンロード exe MB Version: /05/ Firmware release history for the Spectrum Master MSxC Handheld Spectrum Analyzers. ドライバ/ソフトウェアのダウンロード pdf KB Version: AHF Viewer ecosine active (FN /30) - V, ソフトウェア, ​, MB. AHF viewer ecosine active sync (FN 35xx) - V 私たちは、別の総合的なサードパーティ製のソフトウェアツールを使用して、​IMessageが履歴にアクセスします. We will use another comprehensive 3rd party​. 最近の比較評価レポートでは、BIおよびCPMソフトウェアベンダーの包括的なリスト内で、Boardは総合的な顧客満足度における最高製品として評価されてい.

Emi測定総合ソフトウェア ダウンロード. Instead of performing active measurements between a pair of particular end-hosts, we propose a method of estimating quality of service QoS such as latency between hosts through passive measurements, which enables us to grasp network-wide QoS states such as QoS matrix.

して記録できるよう、FactoryTalk® VantagePoint EMIソフトウェアが導入され [ ​] Magellan VantagePoint download- Information about the software Magellan. Faceabook ダウンロード 修羅 の 刻 ダウンロード. Emi測定総合ソフトウェア ダウンロード. 加賀 岬 ダウンロード 販売. 迷列車 bgm ダウンロード. SYSmark* や MobileMark* などの性能テストは、特定のコンピューター・​システム、コンポーネント、ソフトウェア、操作、機能を使用して測定したものです。. 駆動モデルも選択可; 完全密閉されたIP67構造 – IP69K等級の過酷な環境での使用に最適 (設置方法により異なる、仕様を参照); 周囲光、EMIおよびRFI​に対する. The REC3-SR/DR series is a low cost converter containing a built in linear regulator to give a regulated, load independent constant voltage output. The.

持続可能性:環境、社会、ガバナンス - リテルヒューズ

MSPWare™ ソフトウェアを含む無償のソフトウェアも提供しています の FRAM (強誘電体 RAM) と総合的な超低消費電力 MSP システム・ (1) To improve EMI on the HFXT oscillator the following guidelines Webページからデスクトップ・アプリケーションとしてダウンロードすることもできます. 新製品開発等に係る研究開発を支援するネクスト香川のEMC総合試験施設(電波暗室等) / 海老野//洋二郎/p13~19 ここまでできる Windows95/98対応--EP5​シリーズ/EMI自動測定ソフトウェア / 池永//裕司/p50~54 Download all images.Emi測定総合ソフトウェア ダウンロード 武田 志乃(量子科学技術研究開発機構放射線医学総合研究所). Shino Homma-​Takeda 動物体内での pH 測定を目指した近赤外レシオ型蛍光プローブの開発 Emi Hibino1,2, Masaki Nishimura2 (1Grad. 汎用 3 次元モデリングソフトウェア Blender を利用したタンパク質超分子構造の動的性質の理解. 出展者の資料ダウンロード、動画の公開は終了しております。 グラフェン導電性インク、導電性エポキシ、帯電防止コーティング、EMI(電磁妨害)シールド. ソフトウェア無線技術(周波数や通信方式等をソフトウェアによっ. て柔軟な 「Apr」を「Apl」に変更しないと、ダウンロードできない。 プロセスと品質のデータが測定され定量的管理がされている 総合的コンサルティングを実施した例. 8. l高速な伝送速度、低消費電力、低EMI、ノイズ耐性が高い. 1, SEMIスタンダード個別規格PDFダウンロード商品リスト(年04月21日版) 総合工場効率(OFE)および工場レベルにおけるその他の関連生産性測定​基準の Assess and Minimize Electromagnetic Interference (EMI) in a Semiconductor 27, 製造装置に関するもの, 製造装置ソフトウェア(Equipment Automation. Download the latest yamaha riod service manual. Check out and print yamaha riod service manual for free. I/O RACK. Page 1 of

Emi測定総合ソフトウェア ダウンロード.

Sustainability Program at Littelfuse Download the Michael Page AppApply to jobs easier than ever with the Michael Page AppMichael Page 電子系設計ソフトウエアの販売チームのシニアマネージャー 大手総合商社農業関連新規事業戦略の企画立案・実行・販路拡大営業 【測定器】 プリセールステクニカルマネージャー、東京勤務、年収万. ヒューズホルダー、ヒューズアクセサリの総合的なラインナップを提供しています。 ポンプ保護および液面レベル制御 · リレー用変流器 · リレーソフトウェア データシート & ダウンロード · 3D モデル · アプリケーションガイド · CAD の頻度を制限したり、広告キャンペーンの効果を測定する目的でも使われます。.

低電圧テスター · 磁場計 EMC/EMI · 拡声器、ヘッドホン、オーディオテスター Back; ソフトウェア · マイクロコントローラ/マイクロプロセッサ · FPGA/CPLD/​ASIC 光学顕微鏡 · 電子顕微鏡測定 · 投影機総合 · 顕微鏡カメラ · CNC測定​システム (CM only) Search for “HIOKI” and download the “GENNECT Cross”. "stretch" に含まれるソフトウェアパッケージ mips64el, mipsel, ppc64el, sx​]) [security]: https download transport for APT; apt-transport-s3 語辞書; aspell-​da (): 総合的なデンマーク語辞書 (DSDO) - aspell 用; aspell-de bridge frame table administration; ebumeter (): EBU-R に則ったラウドネス測定.   Emi測定総合ソフトウェア ダウンロード 注: YSISSホームページからダウンロードしてください。 ・DME32Diag. ・cont. るソフトウェアのバージョンです。 WORD CLOCK JITTER. ワードクロックのジッターを測定し、総合検査仕様書の規 LCフィルターEMI. L C フ. Download PDF Find Prior Art Similar. Other languages: Japanese; Inventor: アトゥル・ミシュラー: アラムギル・ファルーク: アロック・バトラ: サストリー・​. Ntt docomo technical journal vol 15 no.3 Traffic Localization by Incentive Content-Download Control in Peer-assisted インターネットではマルウェア(悪意のあるソフトウェア)の活動による被害が

Emi測定総合ソフトウェア ダウンロード

Xerox Phaser MFP ServiceManual - Free download as PDF File .pdf), Text File .txt) or read Software version of DSP / DSPのソフトウェアバージョン. modelling tools for download. One of the free 山西、江蘇、広東、山東の 4 省が国家標準化総合改革モデル実施. 計画を公表 【地方標準と 《残留応力超音波測定器較正規格》等、申請予定の業界計量技術. 規格 項目の 件》、《医療機器ソフトウェア_第 2 部:医療機器品質システムソ. フトウェアの.  Emi測定総合ソフトウェア ダウンロード RRIO、小型パッケージ、EMI フィルタ内蔵により、一般的な使用に. 適した特性を 初期精度、全温度範囲にわたる精度の両方で電流測定の総合. 精度を向上. which means that anyone can download the software and use it together with ETC料金所用リアルタイム電波伝搬測定装置の開発 電子情報通信学会総合​大会 ソフトウェア無線機を用いたGHz帯の電波伝搬路測定装置の開発.

Details of a Researcher - MORI, Tatsuya

  Emi測定総合ソフトウェア ダウンロード  

Emi測定総合ソフトウェア ダウンロード. JPA - Network element management system - Google Patents

  Emi測定総合ソフトウェア ダウンロード  Numbers 旧バージョン ダウンロード

Emi測定総合ソフトウェア ダウンロード

Checks gain settings. Checks 17 — 32 channels for loopback. Checks mute settings. Checks vari-pitch Riod 59 1. Riod 60 Riod 62 Riod 63 Riod 64 2. Riod 65 Riod 66 Riod 67 Riod 68 Riod 69 Riod 71 1. Preparations Refer to test program p. Measuring instruments use measuring instruments which can measure the check Riod 72 Vari pitch sound signal test input an analog signal from ch1 intput and measure the output signal from the ch1 output.

Gain word clock input frequency input level specifi ed output level permissible range 1 Riod 73 3. For the measurement procedure, refer to test program [2— Riod 74 1. Riod 75 Riod 76 3. Riod 77 1. Network setting use the same network setting as for test program. Application download riod test p Riod 78 If rio is connected through the network, the fi rmware state of the product is shown.

Riod 79 List of errors and warnings error no. Description [error] command transmission was failed. Riod 80 1. Riod 81 Riod 82 Internal backup memory initialize mode 1 set the dip switch to the internal backup memory initialize mode. All off 01 23 4 5 6 ab c d e f 2 turn on the power switch of riod. Riod 84 1. Application download riod test prog Riod 85 Selecting fi rmware select the fi rmware to be updated. As the fi le select message appears by pressing the [browse] button, select the fi rmware.

Dnt riod x-x-x-xx represents the version number. Selecting device when riod connected Riod 86 1. Riod 87 Riod 89 End of application press the [x] button at the upper right to end the application program. Turning off the power of riod 1 set the dip switch to the normal mode. All off 01 23 4 5 6 ab c d e f 2 turn off the power switch of riod.

In case of updating failed Riod 91 Power down key scan task activated. Checksum in parameter area calculated and stored in flash rom. Usually, the power is turned off completely here. Power turned on Warning components having special characteristics are marked and must be replaced with parts having specifi cation equal to those originally installed.

Riod 2 note : see parts list for details of circuit board conponent parts. Riod h g f e d c b a 1 2 3 4 5 6 3 jk, jk, cn 4p cn 4p cn 3p sw cn 3p 2 1 4 ic 5p cn 13p cn, 8p cn 16p cn 16p cn 16p cn 16p cn 14p cn 14p cn 11p cn 6p cn 23p cn 12p cn 14p cn 14p cn Riod 25 28cc transceiver led driver led driver to ledad1-cn page h-2 or to ledad3-cn page h-2 to ledad3-cn page h-2 or n.

Riod 26 28cc transceiver led driver to ledaeso-cn page h-4 or to ledda1-cn to ledda2-cn or n. Page of Go. Print this page. Page 2: Warning Riod 2 warning: chemical content notice! Page 9 9 riod! Page 13 13 riod 1. Page 15 15 riod 3. Page 16 16 riod 4. Page 17 17 riod 6. Page 18 18 riod 9.

Page 19 19 riod Page 20 20 riod Page 22 22 riod Page 23 23 riod It is important to improve the well-being of people and the environment by working in socially and environmentally sustainable and responsible ways. At Littelfuse, our sustainability program is designed to create a positive impact on society that will maximize value for our customers, suppliers, associates and shareholders.

Our innovative associates partner with our customers to design, manufacture and deliver high-quality solutions for a safer, greener and increasingly connected world.

As member of the global community, Littelfuse has always strived to understand the impact of what we do, and of what we create, on the world around us. Because of this, our concern for the environment is an integral and fundamental part of our business.

With more than 50 sales, manufacturing, and engineering facilities worldwide and a global network of distribution channels, Littelfuse is committed to conducting its manufacturing and distribution operations in a responsible manner that protects the environment and ensures the safety and welfare of our associates, customers and communities.

Littelfuse is committed to conducting its worldwide manufacturing and distribution operations in a responsible manner that protects the environment and ensures the safety and welfare of our associates, customers, and neighbors. Learn more about how we do this at Littelfuse by clicking on the below links. Note: If an interface group or port rectangle is yellow, it is already in use possibly at a different speed.

To complete the connection, click the update tool or select NE update from the action menu. The configuration dialog is displayed. The value is displayed for the next available virtual channel identifier VCI.

The user may override the channel selection. A ring VC creation dialog is displayed. Select or enter a value in the next field. Only 0 is valid. Congestion control—Choose whether congestion control should be enabled. Only AAL5 is valid. Click Cancel to cancel any changes and close the ring VC creation dialog. Click the appropriate port in the group configuration.

The dotted line s will indicate the connection. To complete the connection, click on the update tool or select NE update from the action menu. A cross-connect confirmation dialog is displayed. A SONET cross-connect connects a fast time slot to another fast time slot passthrough , a fast time slot to a slow time slot add and drop , and a slow time slot to another slow time slot hairpinning be able to.

Note: Not all types of cross-connects are always available depending on NE type and configuration. If the cross-connect needs to be a red line, either click on the red line tool or select a red line from the XC creation option in the action menu. The dotted line indicates the connection. If drop type connection is required, click on the first STS or VT1 group on the left or right side and then click on the drop port along the bottom of the window including the appropriate right group A dotted line will be created.

Note: The time slot speeds at both ends of this cross-connect must be equal. If the time slot rectangle is yellow, it is already in use possibly at a different speed. The cross-connect configuration dialog is displayed. Create, modify and delete one-way, two-way, bridge and roll cross-connects. Redline cross-connect leaning and deletion are supported. When the cross-connect is redlined, the redline must be removed before being deleted.

Select a hairpinning option from the Action menu. A hairpinning view FIG. Depending on the type of cross-connect, a one-way or two-way tool is selected or a corresponding menu option is selected from the action menu.

If the cross-connect needs to be a red line, click the red line tool or select the red line from the XC creation option in the action menu. Click the first group connected from the TP source line, then drag the mouse to the appropriate group of TP destination groups and click again. A dotted line will be displayed. When all cross-connects have been defined, click on the update tool or select NE update from the action menu.

Validate the connection. If the connection is correct, click Ok. If the cross-connect is successfully created on the NE, the line s will change from a dashed line to a solid line. If the NE cross-connect fails, the cross-connect line will remain dotted. If the connection is not correct, click Cancel and then change the connection. A connection confirmation dialog appears, indicating the success or failure of the cross-connect. Select the one-way service selector tool.

Click the slow port and then quick the destination fast port. Cross connect is displayed as a dotted line. Note: The default service selector and holdoff count can be changed at this point by right-clicking the cross-connect and selecting the appropriate menu item.

To complete the cross-connect, click on the update tool or select NE update from the action menu. By setting up a bridge, traffic from one termination point is sent to two other termination points. Bridge and roll operations are performed on the two NEs to complete the overall task. First, a bridge is executed at the cross-connect of one NE and then a roll is executed at the other NE.

Roll execution error, the bridge is cleared by the first NE. Log on to the NE whose path must be modified. A 1-way drop cross-connect to be bridged is selected. Click the bridge tool or select a bridge from the action menu. Select a destination time slot. The display will show the new bridge connection as a dotted line on the window when the operation is complete.

To complete the connection, click the NE update tool or select NE update from the action menu. The roll facilitates switching the source ADI from one time slot to another without loss of signal. Traffic is buffered by the NE during the roll operation. After the user selects a roll, the rubberband method begins and the user can select a new origin.

Pending roll cross connect is created. The user can then activate the roll cross-connect so that the original cross-connect is deleted and a new roll cross-connect is created. Bridge and roll operations are performed on the two NEs to complete the complete task. After the roll is executed, the first NE bridge is cleared. A 1-way drop cross-connect to be rolled is selected. Click the roll tool or select a role from the action menu. The display will show the new connection as a dotted line on the window when the operation is complete.

Old connections will appear as solid lines. To complete the cross-connection, click on the NE update tool or select NE update from the action menu. Click the Close button to close the cross connect report. The name can be structured to conform to the user's own network naming convention.

However, the cross-connect name must be alphanumeric and must not contain special characters. Multiple cross-connects can be updated simultaneously. Note: Cross-connect names must be alphanumeric and must not contain special characters. Log on to the NE with the cross-connect s.

Select a cross-connect that requires a new name. Select Name Setting from the Action menu, or right-click on the cross-connect and select Name Setting The cross-connect setting name dialog is displayed. Enter a new name. Select the Set All button and move the cross-connect name to the cross-connect name field in the cross-connect name setting dialog.

Click Ok to close the cross-connect name setting dialog. The cross connect is displayed as a dotted line. Click the update tool. A confirmation dialog is displayed. Verify that the information is correct and click Ok. A message dialog box appears with the new name shown in the table. Click Ok. Select the cross-connect that needs to be redlined.

A plurality of cross-connects can be selected by holding down the shift key and the CTRL key and then clicking the cross-connect line.

The cross-connect line will change to a red dotted line. To complete the redline designation, click on the update tool or select NE update from the action menu. If the cross-connect has been redlined, the redline must be removed as described in this procedure.

Log on to the NE where the cross-connect must be deleted. If the cross connect is redlined, the redline designation must first be deleted. Click on the NE update tool or select NE update from the action menu. Click Ok to delete the red line. Click the cross connect to be deleted. Multiple cross-connects can be selected by holding down the CTRL and shift keys and then clicking each cross-connect to be deleted. The cross-connect line changes from a solid line to a broken line, indicating an pending change in state.

After the cross-connect is marked for deletion in the GUI, change the NE by clicking on the update tool or select NE update from the action menu.

After verifying that the appropriate cross-connects are listed, click Ok to complete the deletion. If the cross-connect is not correct, click Cancel and reselect the connection. To cancel the deletion, click the Undo tool to restore the connection. Access the appropriate cross-connect window. Right-click on the cross-connect to display the menu. Select Set SS to Through. Setting menu selection SS to through changes to setting SS to insertion.

The user can toggle this selection between two items. Only inactive choices will appear in the menu. To change the Hall Off Off timer value, perform the following procedure. Log on to the NE where the holdoff timer must be set. Access the loss connect window without proper access.

Select the hold-off timer. Enter a value for the reset interval. Log on to NE. Right-click to select a cross-connect and display a menu for the user to select trace XC. The label will be displayed on the side of the cross-connect termination point that the user right-clicked.

This label identifies the other end of this cross-connect. Note: A facility cannot be created unless a supporting device has been created. The management-side facility dialog is displayed FIG. Click the speed and select a speed from the speed drop-down list. Select a shelf from the shelf drop-down list. Select a facility in the Facility field that does not exist.

Click the creation tool. Note: If there are no missing deleted facilities, there will be nothing in this list. If this facility has any attributes whose values must be specified at creation time, a dialog containing the key attributes will be displayed. Enter the values for these attributes and click Ok. Selected attributes of the selected facility will be displayed in the attribute table. A facility management message box appears. Facility creation. Since the facility does not exist, it will be moved to the existing column and activated.

Select a facility from the enlarged tree or from the graphics area. The attribute view is displayed. This display will vary slightly depending on the command origin issued from the tree or graphics area. Correct the required values displayed in blue or red and then click the correction tool or select the update option from the action menu. The same option can also be selected from the action menu. From any tab in the Configuration Manager, select the management facility option in the NE menu.

The management facility dialog is displayed. Select a facility in the Existing Facility column. Note: If there is no existing created facility, there will be nothing in this list. Click Ok to delete the facility. The facility will be moved from the existing facility to the non-existing facility and deactivated.

Devices and facilities to support FFP groups must already be created. Note: FFP group changes can change the system configuration and cause system configuration mismatch. The FFP management dialog is displayed. Note: The list will be empty if there are no non-existent deleted FPs. The group attributes tab appears. Modify the required value shown in blue and red by clicking on the value, then select a new option from the drop-down list. Click the fix tool to download the changes to the NE.

The changed value will be displayed in the value field. Select a speed from the Speed drop-down list. Select Delete from the Edit menu. The user must use the reload tool or the NE list reload command to redisplay the window and display the updated information. When opening this window from the topology window, the following choices are available: Select the number of NEs. Select the number of groups. Select the number of NEs and groups. Select a network group. To create a wavelength inventory report, perform the following tasks: 1.

The wavelength management window is displayed. Click NE to display the data. Select a filter tool from the toolbar to filter the columns in the data display. Click the first button below the field label. A list of values to use for filtering is displayed. Select one of these values. Once the filtering value is selected, the test button is activated. Click the test button to display a series of values to match and test for filtering. One of the following: containers lcontains starts with lstarts with ends with ends with 6.

Click to select one of the values listed above. Once the filtering value has been washed, click Ok to redisplay the wavelength management value with the filter s applied. NGDLC supports centralization of switched traffic and training of non-switched traffic.

Each of these groups is created by automatic discovery. TR defines an interface between a central office switch and a remote terminal to handle all call processing and usable functions of the DLC system. TR is a versatile interface that supports the majority of subscribers and transport bandwidth, giving operators the ability to choose the concentration ratio intended for traffic engineering guidelines.

It also activates the interface or pauses for maintenance purposes. Putting the NE into maintenance does not affect service. However, once a NE is in a maintenance state, operations performed on that NE can affect the service eg, loopback affects service. From the Configuration Manager, select the Interface Type tab. The Interface Type tab is displayed. A blue dot in the upper right corner indicates that the interface group has children. Double-click in the TR or TR box in the graphics area or in the enlarged tree and select the item corresponding to the interface to be modified.

The attribute dialog is displayed. Click on the interface option to be changed. Only interface options shown in blue can be changed. Select a new option from the drop-down list. Click the correction tool or select the update option from the action menu to make changes. However, once an NE is put into maintenance state, operations performed on that NE can affect the service eg, loopback affects service.

The plus sign on the left side of the interface group indicates that this interface group has multiple children. Expand the tree list and select T1 to be modified. An attribute dialog FIG. Only interface options that are displayed in red or blue can be changed. Select a new option from the drop-down list that appears when the value is clicked. Click the fix tool to complete the change.

The same option can be selected from the action menu. Operations that can only be applied to a single card or facility on a single NE are as follows. Element View: Accessing the Performance Manager from the topology window displays the element view. If no NE is selected, a list of available NEs is displayed in the performance manager window after it is launched.

The view is divided into two main parts. The selection area at the top of the view displays the selected element in the selected element list. The radio button to the right of the interval label is used to define the monitoring level. The bottom of the view displays monitoring data. The following information assumes that performance management has been selected from the action menu with no NE selected all NEs will be displayed in the list of available elements.

To start monitoring, select the Monitoring tab in the Performance Manager window. This is the default tab for element views. To select an NE for monitoring, select an item in the available element column and use the add button to add it to the selected element column. To delete an item from the selected element column, highlight the item in the selected element column and click the delete button.

After the ongoing message bar disappears, an entry is added to the monitoring data area. Verify the initialization status in the third column.

Click the Add All button to add all items to the selected elements column. Click the Delete All button to delete all items in the Selected Elements column. After the ongoing message bar disappears, the entry remains in the list, but the status is changed to disabled. Note: When it is impossible to use a selection, the selection is dimmed. For example, in the PM element view from NE : Monitor tab, the add button and the add all button cannot be used because there is nothing to add to the available element list.

The delete button is disabled until the selected element: element in the list is selected. Use the interval radio buttons to determine the interval for management. Options are 15 minutes 15 minute intervals or 1 day.

The default value is 15 minutes. If the user selects 15 minutes, the data is retrieved from the NE 15 minute register. When the user selects one day, the data is retrieved from the NE1 day register. To stop monitoring, select the monitoring tab and then click the Mon Off tool on the toolbar or select Turn off performance monitoring from the action menu. To initialize the register: 1. Select the Register tab in the Elements view Figure To select an NE for initialization, select an item in the available element column and use the add button to add it to the selected element column.

Click the Add All button to add all items to the Selected Elements column. Selecting this option will initialize all registers in the NE to zero. To retrieve performance data, perform the following tasks: 1. Select the database tab of the element view FIG. Select an element s from the list of available elements. Use the add button to add it to the selected element field. Click the Select All button to add all items to the Selected Elements column.

Interval-Displays the time period interval. Possible options are 15 minutes or 1 day. The default is 15 minutes.

If the user selects 15 minutes, the collected data will be divided into 15 minute periods. If the user selects one day, the collected data will be reported in a one day period.

A default format is provided. Select Reload from the action menu or click the Reload tool from the toolbar to start the data search. Otherwise, right-click to display the pop-up menu and then select PM display from the pop-up menu. If the card does not have a PM register, the PM tool is not displayed on the toolbar.

The device view displays only the register tab and prepares to set the register threshold and receive the current performance register.

AID type—The type of access identifier. AID—Access identifier name. Register—The register name. Value—The value of the retrieved register. Range—The allowable range of register values. Threshold-An indicator to the NE to re-create a threshold report if the threshold is exceeded. Default threshold—This is the default value set by the NE when it is first started. Under normal operating conditions, this value should be false. The PM register is accumulated at minute intervals.

If the value being reported is not for a full 15 minute interval, this value will be reported as true. Location-This value indicates where the data comes from near end or far end. The device register will always be the far end. Typically, the value reported for the facility will be Tx or Rx. For facilities, the time reporting interval will be displayed as either 15 minutes or 1 day. Index-This value will always be zero for the device. For the facility, the current register 0 plus past registers 1 through 32 will be displayed.

The monitor tab and the database tab cannot be selected because the device register is not a counter. They are the current operating level of items such as laser bias current normalized LBCN. For this reason, monitoring cannot be turned on or off, and the database will not contain historical data. To limit this data, a data collection threshold can be set. If these thresholds are not crossed, NE performance is assumed to be acceptable. A default threshold value exists for each register.

The threshold of any register can be set and changed. To set the threshold: 1. Select a device from the available device list and click the add button to add the device to the selected device list.

Select the numbered row in the report, then click the configuration tool on the toolbar. The threshold setting dialog is displayed.

Enter a new value for the threshold. The threshold range depends on NE and is displayed when the user selects a row for setting a register. The user can also refer to the system engineering section of the website of Fujitsu Network Communications regarding the TL1 threshold value specification for each NE. Click OK to select the threshold and close the dialog.

Select devices from the available device list and click the add button to add them to the selected device list. Select the reload tool from the toolbar. The reload tool updates a report regarding the devices included in the selected device list and the values specified in the location field, direction field, time interval field, and index field.

Otherwise, right-click to display the pop-up menu, then select Performance Display from the pop-up menu. The monitoring tab is the default initial display. By default, the facility selected in the Configuration Manager is the one displayed in the Performance Manager and the interval option is set to 15 minutes default.

Direction—Typically, the value reported for the facility will be Tx or Rx. Time interval-For facilities, the time reporting interval will be displayed as either 15 minutes or 1 day. For the index facility, the current register 0 plus the past registers 1 to 32 will be displayed.

The report status is automatically retrieved and displayed. When selecting an NE for monitoring, select an item in the available facility list and use the add button to add it to the selected facility list.

By default, the facility that is selected when the performance manager is started is already in the selected facility list. To delete an item from the selected facility column, highlight it in the selected facility column and click the delete button.

Click the Add All button to add all items to the selected facility column. Click the Delete All button to delete all items in the selected facility column. Select a location by selecting one of the location radio buttons. A direction is selected by selecting one of the direction radio buttons. Possible options are reception, transmission, or NA not applicable. This list is dynamically updated based on the facility selected. Interval: Select the interval for monitoring using the radio button.

Options are 15 minutes or 1 day. In the start index field and end index field, select a value between 0 and 32 in the register. The end index value must always be greater than the start index value.

Click the Mon On tool on the toolbar to start monitoring. To stop monitoring, select the Monitor tab, then click the Mon off tool on the toolbar. Select the Init tool on the toolbar. Selecting this option will initialize all selected NE facility registers to zero.

Once this tab is selected, a command is sent to the NE to retrieve register data for the selected facility. This data is displayed using default parameters for location index, direction index, interval and start index, and stop index. Select facilities from the available facility list and click the Add button to add them to the selected facility list. Select a direction by selecting one of the direction radio buttons. Use the Interval radio button to select the monitoring interval. When the user selects 1 day, the data is retrieved from the NE 1 day register.

In the start index field and end index field of the register tab, a value between 0 and 32 is selected for the register. The end index value must always be higher than the start index value.

These options may be updated dynamically depending on the selected type of facility. Select reload toolbar. When this tool is selected, the register data of the selected facility is reloaded to the index selected in Step 2, and the result is displayed in the window. To set the threshold from the Performance Manager: 1. Select facilities from the available facility list and add them to the selected facility list using the Add button.

Select the numbered row in the report, then click Settings on the toolbar. After the threshold setting dialog appears, enter a new value for the threshold. Click Ok to save your changes and close the dialog.

Select elements from the list of available elements and click the Add button to add them to the selected elements list. Select Add All to add all elements.

Click the reload tool from the toolbar and start receiving data. The batch TL1 command can be saved as a file and executed later.

This window has three main display areas. The top will contain any commands entered in the TL1 command text entry area. The lower part includes a TL1 command text input area, an active session list area, and a list of saved batch files. The lower part of the window is referred to as the batch listing area. The use of an individual Tl1 command is the simplest way to interact with a single NE and the command is appropriate before using it in a batch file especially a batch file that will be executed on multiple NEs Would be sure to run into.

When executing time-consuming TL1 commands, it is best to use a TL1 batch if an individual TL1 command is sent for execution, the Tl1 editor will remain busy waiting for command responses. The command is displayed in the history area of the TL1 window. There can be multiple sessions. In order to send a command, an active session must exist. At least one TID must be selected before the batch is executed.

In addition, before the batch can run, the batch must have a UID property set and a password property set.

Importing a TL1 file into a TL-1 batch editor will invalidate any existing commands in the editor. To edit an existing batch, double-click an existing batch in the batch listing at the bottom of the window, or click the batch name and select Edit from the Batch menu.

Select TID from the batch menu. A TID list dialog is displayed. Multiple TIDs can be selected. Click twice on the TID to deselect any unnecessary values. If there is no TID to add, this button is dimmed and cannot be used. Click Ok and select TID s.

  Environmental

The roll facilitates switching the source ADI from one time slot to another without loss of signal. Traffic is buffered by the NE during the roll operation. After the user selects a roll, the rubberband method begins and the user can select a new origin.

Pending roll cross connect is created. The user can then activate the roll cross-connect so that the original cross-connect is deleted and a new roll cross-connect is created. Bridge and roll operations are performed on the two NEs to complete the complete task.

After the roll is executed, the first NE bridge is cleared. A 1-way drop cross-connect to be rolled is selected. Click the roll tool or select a role from the action menu. The display will show the new connection as a dotted line on the window when the operation is complete. Old connections will appear as solid lines. To complete the cross-connection, click on the NE update tool or select NE update from the action menu. Click the Close button to close the cross connect report.

The name can be structured to conform to the user's own network naming convention. However, the cross-connect name must be alphanumeric and must not contain special characters. Multiple cross-connects can be updated simultaneously. Note: Cross-connect names must be alphanumeric and must not contain special characters. Log on to the NE with the cross-connect s. Select a cross-connect that requires a new name. Select Name Setting from the Action menu, or right-click on the cross-connect and select Name Setting The cross-connect setting name dialog is displayed.

Enter a new name. Select the Set All button and move the cross-connect name to the cross-connect name field in the cross-connect name setting dialog. Click Ok to close the cross-connect name setting dialog. The cross connect is displayed as a dotted line. Click the update tool. A confirmation dialog is displayed.

Verify that the information is correct and click Ok. A message dialog box appears with the new name shown in the table. Click Ok. Select the cross-connect that needs to be redlined. A plurality of cross-connects can be selected by holding down the shift key and the CTRL key and then clicking the cross-connect line.

The cross-connect line will change to a red dotted line. To complete the redline designation, click on the update tool or select NE update from the action menu. If the cross-connect has been redlined, the redline must be removed as described in this procedure.

Log on to the NE where the cross-connect must be deleted. If the cross connect is redlined, the redline designation must first be deleted. Click on the NE update tool or select NE update from the action menu. Click Ok to delete the red line. Click the cross connect to be deleted. Multiple cross-connects can be selected by holding down the CTRL and shift keys and then clicking each cross-connect to be deleted.

The cross-connect line changes from a solid line to a broken line, indicating an pending change in state. After the cross-connect is marked for deletion in the GUI, change the NE by clicking on the update tool or select NE update from the action menu. After verifying that the appropriate cross-connects are listed, click Ok to complete the deletion. If the cross-connect is not correct, click Cancel and reselect the connection. To cancel the deletion, click the Undo tool to restore the connection.

Access the appropriate cross-connect window. Right-click on the cross-connect to display the menu. Select Set SS to Through. Setting menu selection SS to through changes to setting SS to insertion. The user can toggle this selection between two items. Only inactive choices will appear in the menu. To change the Hall Off Off timer value, perform the following procedure.

Log on to the NE where the holdoff timer must be set. Access the loss connect window without proper access. Select the hold-off timer. Enter a value for the reset interval. Log on to NE. Right-click to select a cross-connect and display a menu for the user to select trace XC. The label will be displayed on the side of the cross-connect termination point that the user right-clicked. This label identifies the other end of this cross-connect. Note: A facility cannot be created unless a supporting device has been created.

The management-side facility dialog is displayed FIG. Click the speed and select a speed from the speed drop-down list. Select a shelf from the shelf drop-down list.

Select a facility in the Facility field that does not exist. Click the creation tool. Note: If there are no missing deleted facilities, there will be nothing in this list. If this facility has any attributes whose values must be specified at creation time, a dialog containing the key attributes will be displayed. Enter the values for these attributes and click Ok. Selected attributes of the selected facility will be displayed in the attribute table. A facility management message box appears.

Facility creation. Since the facility does not exist, it will be moved to the existing column and activated. Select a facility from the enlarged tree or from the graphics area. The attribute view is displayed.

This display will vary slightly depending on the command origin issued from the tree or graphics area. Correct the required values displayed in blue or red and then click the correction tool or select the update option from the action menu. The same option can also be selected from the action menu. From any tab in the Configuration Manager, select the management facility option in the NE menu. The management facility dialog is displayed. Select a facility in the Existing Facility column.

Note: If there is no existing created facility, there will be nothing in this list. Click Ok to delete the facility. The facility will be moved from the existing facility to the non-existing facility and deactivated. Devices and facilities to support FFP groups must already be created.

Note: FFP group changes can change the system configuration and cause system configuration mismatch. The FFP management dialog is displayed. Note: The list will be empty if there are no non-existent deleted FPs.

The group attributes tab appears. Modify the required value shown in blue and red by clicking on the value, then select a new option from the drop-down list. Click the fix tool to download the changes to the NE. The changed value will be displayed in the value field. Select a speed from the Speed drop-down list.

Select Delete from the Edit menu. The user must use the reload tool or the NE list reload command to redisplay the window and display the updated information. When opening this window from the topology window, the following choices are available: Select the number of NEs.

Select the number of groups. Select the number of NEs and groups. Select a network group. To create a wavelength inventory report, perform the following tasks: 1. The wavelength management window is displayed.

Click NE to display the data. Select a filter tool from the toolbar to filter the columns in the data display. Click the first button below the field label. A list of values to use for filtering is displayed. Select one of these values. Once the filtering value is selected, the test button is activated. Click the test button to display a series of values to match and test for filtering. One of the following: containers lcontains starts with lstarts with ends with ends with 6.

Click to select one of the values listed above. Once the filtering value has been washed, click Ok to redisplay the wavelength management value with the filter s applied. NGDLC supports centralization of switched traffic and training of non-switched traffic. Each of these groups is created by automatic discovery. TR defines an interface between a central office switch and a remote terminal to handle all call processing and usable functions of the DLC system.

TR is a versatile interface that supports the majority of subscribers and transport bandwidth, giving operators the ability to choose the concentration ratio intended for traffic engineering guidelines. It also activates the interface or pauses for maintenance purposes.

Putting the NE into maintenance does not affect service. However, once a NE is in a maintenance state, operations performed on that NE can affect the service eg, loopback affects service.

From the Configuration Manager, select the Interface Type tab. The Interface Type tab is displayed. A blue dot in the upper right corner indicates that the interface group has children. Double-click in the TR or TR box in the graphics area or in the enlarged tree and select the item corresponding to the interface to be modified. The attribute dialog is displayed. Click on the interface option to be changed. Only interface options shown in blue can be changed. Select a new option from the drop-down list.

Click the correction tool or select the update option from the action menu to make changes. However, once an NE is put into maintenance state, operations performed on that NE can affect the service eg, loopback affects service.

The plus sign on the left side of the interface group indicates that this interface group has multiple children. Expand the tree list and select T1 to be modified. An attribute dialog FIG. Only interface options that are displayed in red or blue can be changed. Select a new option from the drop-down list that appears when the value is clicked. Click the fix tool to complete the change. The same option can be selected from the action menu.

Operations that can only be applied to a single card or facility on a single NE are as follows. Element View: Accessing the Performance Manager from the topology window displays the element view.

If no NE is selected, a list of available NEs is displayed in the performance manager window after it is launched. The view is divided into two main parts. The selection area at the top of the view displays the selected element in the selected element list. The radio button to the right of the interval label is used to define the monitoring level.

The bottom of the view displays monitoring data. The following information assumes that performance management has been selected from the action menu with no NE selected all NEs will be displayed in the list of available elements.

To start monitoring, select the Monitoring tab in the Performance Manager window. This is the default tab for element views. To select an NE for monitoring, select an item in the available element column and use the add button to add it to the selected element column.

To delete an item from the selected element column, highlight the item in the selected element column and click the delete button. After the ongoing message bar disappears, an entry is added to the monitoring data area. Verify the initialization status in the third column. Click the Add All button to add all items to the selected elements column. Click the Delete All button to delete all items in the Selected Elements column. After the ongoing message bar disappears, the entry remains in the list, but the status is changed to disabled.

Note: When it is impossible to use a selection, the selection is dimmed. For example, in the PM element view from NE : Monitor tab, the add button and the add all button cannot be used because there is nothing to add to the available element list. The delete button is disabled until the selected element: element in the list is selected. Use the interval radio buttons to determine the interval for management. Options are 15 minutes 15 minute intervals or 1 day.

The default value is 15 minutes. If the user selects 15 minutes, the data is retrieved from the NE 15 minute register. When the user selects one day, the data is retrieved from the NE1 day register. To stop monitoring, select the monitoring tab and then click the Mon Off tool on the toolbar or select Turn off performance monitoring from the action menu.

To initialize the register: 1. Select the Register tab in the Elements view Figure To select an NE for initialization, select an item in the available element column and use the add button to add it to the selected element column. Click the Add All button to add all items to the Selected Elements column. Selecting this option will initialize all registers in the NE to zero. To retrieve performance data, perform the following tasks: 1.

Select the database tab of the element view FIG. Select an element s from the list of available elements. Use the add button to add it to the selected element field. Click the Select All button to add all items to the Selected Elements column.

Interval-Displays the time period interval. Possible options are 15 minutes or 1 day. The default is 15 minutes. If the user selects 15 minutes, the collected data will be divided into 15 minute periods. If the user selects one day, the collected data will be reported in a one day period. A default format is provided. Select Reload from the action menu or click the Reload tool from the toolbar to start the data search.

Otherwise, right-click to display the pop-up menu and then select PM display from the pop-up menu. If the card does not have a PM register, the PM tool is not displayed on the toolbar. The device view displays only the register tab and prepares to set the register threshold and receive the current performance register. AID type—The type of access identifier.

AID—Access identifier name. Register—The register name. Value—The value of the retrieved register. Range—The allowable range of register values. Threshold-An indicator to the NE to re-create a threshold report if the threshold is exceeded. Default threshold—This is the default value set by the NE when it is first started. Under normal operating conditions, this value should be false.

The PM register is accumulated at minute intervals. If the value being reported is not for a full 15 minute interval, this value will be reported as true. Location-This value indicates where the data comes from near end or far end. The device register will always be the far end. Typically, the value reported for the facility will be Tx or Rx. For facilities, the time reporting interval will be displayed as either 15 minutes or 1 day.

Index-This value will always be zero for the device. For the facility, the current register 0 plus past registers 1 through 32 will be displayed. The monitor tab and the database tab cannot be selected because the device register is not a counter. They are the current operating level of items such as laser bias current normalized LBCN. For this reason, monitoring cannot be turned on or off, and the database will not contain historical data. To limit this data, a data collection threshold can be set.

If these thresholds are not crossed, NE performance is assumed to be acceptable. A default threshold value exists for each register. The threshold of any register can be set and changed. To set the threshold: 1. Select a device from the available device list and click the add button to add the device to the selected device list.

Select the numbered row in the report, then click the configuration tool on the toolbar. The threshold setting dialog is displayed. Enter a new value for the threshold. The threshold range depends on NE and is displayed when the user selects a row for setting a register.

The user can also refer to the system engineering section of the website of Fujitsu Network Communications regarding the TL1 threshold value specification for each NE. Click OK to select the threshold and close the dialog. Select devices from the available device list and click the add button to add them to the selected device list. Select the reload tool from the toolbar.

The reload tool updates a report regarding the devices included in the selected device list and the values specified in the location field, direction field, time interval field, and index field.

Otherwise, right-click to display the pop-up menu, then select Performance Display from the pop-up menu. The monitoring tab is the default initial display. By default, the facility selected in the Configuration Manager is the one displayed in the Performance Manager and the interval option is set to 15 minutes default. Direction—Typically, the value reported for the facility will be Tx or Rx. Time interval-For facilities, the time reporting interval will be displayed as either 15 minutes or 1 day.

For the index facility, the current register 0 plus the past registers 1 to 32 will be displayed. The report status is automatically retrieved and displayed. When selecting an NE for monitoring, select an item in the available facility list and use the add button to add it to the selected facility list. By default, the facility that is selected when the performance manager is started is already in the selected facility list. To delete an item from the selected facility column, highlight it in the selected facility column and click the delete button.

Click the Add All button to add all items to the selected facility column. Click the Delete All button to delete all items in the selected facility column.

Select a location by selecting one of the location radio buttons. A direction is selected by selecting one of the direction radio buttons. Possible options are reception, transmission, or NA not applicable.

This list is dynamically updated based on the facility selected. Interval: Select the interval for monitoring using the radio button. Options are 15 minutes or 1 day. In the start index field and end index field, select a value between 0 and 32 in the register. The end index value must always be greater than the start index value. Click the Mon On tool on the toolbar to start monitoring.

To stop monitoring, select the Monitor tab, then click the Mon off tool on the toolbar. Select the Init tool on the toolbar. Selecting this option will initialize all selected NE facility registers to zero. Once this tab is selected, a command is sent to the NE to retrieve register data for the selected facility. This data is displayed using default parameters for location index, direction index, interval and start index, and stop index.

Select facilities from the available facility list and click the Add button to add them to the selected facility list. Select a direction by selecting one of the direction radio buttons.

Use the Interval radio button to select the monitoring interval. When the user selects 1 day, the data is retrieved from the NE 1 day register. In the start index field and end index field of the register tab, a value between 0 and 32 is selected for the register. The end index value must always be higher than the start index value. These options may be updated dynamically depending on the selected type of facility.

Select reload toolbar. When this tool is selected, the register data of the selected facility is reloaded to the index selected in Step 2, and the result is displayed in the window. To set the threshold from the Performance Manager: 1. Select facilities from the available facility list and add them to the selected facility list using the Add button. Select the numbered row in the report, then click Settings on the toolbar. After the threshold setting dialog appears, enter a new value for the threshold.

Click Ok to save your changes and close the dialog. Select elements from the list of available elements and click the Add button to add them to the selected elements list. Select Add All to add all elements. Click the reload tool from the toolbar and start receiving data. The batch TL1 command can be saved as a file and executed later. This window has three main display areas.

The top will contain any commands entered in the TL1 command text entry area. The lower part includes a TL1 command text input area, an active session list area, and a list of saved batch files. The lower part of the window is referred to as the batch listing area.

The use of an individual Tl1 command is the simplest way to interact with a single NE and the command is appropriate before using it in a batch file especially a batch file that will be executed on multiple NEs Would be sure to run into. When executing time-consuming TL1 commands, it is best to use a TL1 batch if an individual TL1 command is sent for execution, the Tl1 editor will remain busy waiting for command responses. The command is displayed in the history area of the TL1 window.

There can be multiple sessions. In order to send a command, an active session must exist. At least one TID must be selected before the batch is executed. In addition, before the batch can run, the batch must have a UID property set and a password property set. Importing a TL1 file into a TL-1 batch editor will invalidate any existing commands in the editor. To edit an existing batch, double-click an existing batch in the batch listing at the bottom of the window, or click the batch name and select Edit from the Batch menu.

Select TID from the batch menu. A TID list dialog is displayed. Multiple TIDs can be selected. Click twice on the TID to deselect any unnecessary values. If there is no TID to add, this button is dimmed and cannot be used. Click Ok and select TID s. Use the batch import tool to display the import batch dialog where you can specify the file to import, or use the batch export tool to specify the location and file name of the data to be exported indicate. Click to select the file to import or export.

Only one file can be selected at a time. Click OK, select the file, and close the dialog. To set batch properties, click the Props tool or select a property from the batch menu. The batch properties dialog is displayed. Values must be entered in the UID and password fields for the batch to execute.

Name-If this is a new batch, this field is blank. If this is an existing batch, this field displays the batch name. You cannot enter data in this field. Privilege—Select an individual if only the person who created the batch file can execute it, or publish if any user with TL1 privileges can execute the batch file. If a command in the batch file specifies a different user ID, the user ID in the batch file will invalidate this user ID.

Click Ok to save the property settings or close the dialog without making any changes. When the Save The file will be saved using this name. If multiple sessions are active, select an active session TID from the active session list.

Click on the send tool or select send from the batch menu to transmit the TL1 command. The new batch must have the UID property and password property set before the batch runs.

Batch commands can be exported as a single file, in which case the TID and property values will not be retained. Importing a TL1 file into the batch editor invalidates any existing commands in the editor. Use the batch import tool to display the batch import dialog where you can identify the file to be imported, or use the batch export tool to display the batch import dialog where you can identify the location and file name of the exported data.

Click OK to select the file and close the dialog. To modify batch properties, click the Props tool or select properties from the batch menu. The values in the UID field and password field must be changed so that the batch can be executed. To save the batch file, click the Save As tool or select Overwrite from the File menu.

The file is saved using this name. The TL1 console window allows the user to view TL1 activity that has occurred due to user actions.

For example, logging on to the NE, creating a cross-connect, etc. For information on viewing other TL1 record attributes or changing the order of displayed attributes, see Section A. See Section The TL1 console window is displayed.

As soon as the user opens the Tl1 console, the display of TL1 events begins and scrolls automatically to display additional events. The TL1 console window displays a maximum of records at a time. The TL1 console starts with default settings, which display TL1 messages.

The server starts sending messages to the console. Use the attribute sort dialog to add, delete, or reorder the displayed attributes. If the display is paused early by selecting the pause button, the console will display the message sent during the pause and then start displaying new messages.

If the display is stopped early by selecting the stop button, a new real-time message will begin to display. The activation button is active only when the display is paused or stopped. To pause the message display, select Pause from the Action menu or click the Pause tool. This option pauses the display of TL1 events on the console. Internally, messages are buffered up to records.

These records will be displayed when the user selects Start to resume display. To stop displaying any messages in the console, select Stop from the Action menu, or select the Stop tool on the toolbar. The server stops sending messages to the console. Click on the tool. The attribute sorting dialog is displayed. To add an attribute to the selected list, highlight the selected attribute below the attribute list and then click the Add button.

To remove an attribute from the selected list, highlight the attribute in the selected list and then click the delete button. Use the Add All or Delete All buttons to add or remove all attributes. TL1Msg is the default item in the selected list and cannot be deleted. To change the order of attributes in the list, select the attribute and then click the up button to move the attribute up in the list, or click the down button to move the attribute in the list.

Move down. Click OK to save the settings and close this dialog, or click Cancel to cancel all changes and close this dialog. Riod 47 1. Preparation Riod 48 Details of applications version information, etc. Are shown. The check result in detail is displayed. Test result is ok test items are displayed. S temscheckedinthecheckboxwillbetested s tispossibletoselectonebyonefor individual check. Riod 49 menu tool bar description view folder up moves to the folder just abo ve the current folder large icons displays items with large icons small icons displays items with small icons list displays items as a list details displays items as a detailed list options makes various option settin Riod 50 Riod 51 Test procedure test executing screen 3.

Use this to start testing. Put check marks in all checkboxes. Select [riod-service]. Put check marks for detailed test items as well. Check that [riod Riod 52 2. Test item Info test contents: checks the version of the boot. Checks the version of the program. Checks the mac address. Checks the serial no.

Checks the sheet id. Riod 53 Led test contents: checks if the power led lights up. Checks if the leds light up in order from left. Checks if all red leds light up. Checks if all green leds light up.

Checks if all orange leds light up. Checks if all leds light up. Precautions the test result should be judged by Riod 54 Sdram test contents: checks the address bus of sdram. Checks the data bus of sdram. Preparation back up head amp parameters in advance as necessary.

Item text indication ad Riod 55 Riod 56 Word clock test contents: checks word clock. The result is displayed in the output window as follows. Item t Riod 57 Checks gain settings. Checks 17 — 32 channels for loopback. Checks mute settings. Checks vari-pitch Riod 59 1. Riod 60 Riod 62 Riod 63 Riod 64 2. Riod 65 Riod 66 Riod 67 Riod 68 Riod 69 Riod 71 1.

Preparations Refer to test program p. Measuring instruments use measuring instruments which can measure the check Riod 72 Vari pitch sound signal test input an analog signal from ch1 intput and measure the output signal from the ch1 output. Gain word clock input frequency input level specifi ed output level permissible range 1 Riod 73 3. For the measurement procedure, refer to test program [2— Riod 74 1.

Riod 75 Riod 76 3. Riod 77 1. Network setting use the same network setting as for test program. Application download riod test p Riod 78 If rio is connected through the network, the fi rmware state of the product is shown.

Riod 79 List of errors and warnings error no. We reveal the intrinsic characteristics of the flow size distributions of video sharing services, which have not been known before. We show that the origin of the intrinsic characteristics is rooted on the differentiated service provided for free- and premium membership of the video-sharing services. We also discuss the implications of the intrinsic characteristics of video-sharing services. Toward scalable byte caching mechanism that operates on high-speed core routers, this paper proposes a selective packet filtration mechanism, using a probabilistic approach.

We develop a fast approximation algorithm for determining whether the router should cache bytes in a probabilistic way. Theoretical and experimental analysis demonstrates that our technique achieves good enough approximation for both small and large selection probabilities, which can be used to perform accurate filtration, i.

Understanding the large-scale spamming botnet. IEICE technical report 53 - 58 On November 11, , the primary web hosting company, McColo, for the command and control servers of Srizbi botnet was shutdown by its upstream ISPs. Subsequent reports claimed that the volume of spam dropped significantly everywhere on that very same day. In this work, we aim to understand the world's worst spamming botnet, Srizbi, and to study the effectiveness of targeting the botnet's command and control servers, i.

We conduct an extensive measurement study that consists of e-mail delivery logs and packet traces collected at three vantage points. The total measurement period spans from July to April , which includes the day of McColo shutdown. We employ passive TCP fingerprinting on the collected packet traces to identify Srizbi bots and spam messages sent from them. The main contributions of this work are summarized as follows. We first estimate the global scale of Srizbi botnet in a probabilistic way.

Next, we quantify the volume of spam sent from Srizbi and the effectiveness of the McColo shutdown from an edge site perspective. Finally, we reveal several findings that are useful in understanding the growth and evolution of spamming botnets. We detail the rise and steady growth of Srizbi botnet, as well as, the version transition of Srizbi after the McColo shutdown. IEICE technical report 79 - 84 The transmission bit-rate of video streaming with high quality is quite large, so generated traffic flows will cause link congestion.

Therefore, when providing streaming services of rich content, it is important to improve the maximum network throughput by flattening the link utilization, i. So, we have proposed that ISPs use parallel download to deliver rich content to balance the link utilization, and proposed optimum server allocation and server selection methods for parallel video streaming. In this paper, using 23 actual commercial ISP networks, we investigate the actual settings of link capacities and clarify the influence of link weight settings on the maximum network throughput.

We also analyze the impact of network topologies on the effect of parallel video streaming. Improving deployability of peer-assisted CDN platform with incentive.

IEICE technical report 7 - 12 As a promising solution to manage the huge workload of large-scale VoD services, managed peer-assisted CDN systems, such as P4P has attracted attention. Although the approach works well in theory or in a controlled network testbed, to our best knowledge, there have been no general studies that address how actual peers can be incentivized in the wild Internet; thus, deployablity of the system with respect to incentives to users has been an open issue.

With this background in mind, we propose a new business model that aims to make peer-assisted approaches more feasible. The key idea of the model is that users sell their idle resources back to ISPs. In other words, ISPs can leverage resources of cooperative users by giving them explicit incentives, e. We analyze how incentives and other external factors affect the efficiency of the system through simulation. Traffic caused by P2P services dominates a large part of traffic in the Internet, so reducing the P2P traffic within the networks is an important issue for ISPs.

To reduce the P2P traffic, it is effective for ISPs to implement cache devices at some ports of routers and reduce the hop length of P2P flows by delivering required contents from caches. Hence, we have proposed the optimum design method of caches for P2P traffic minimizing the total amount of P2P traffic based on the dynamic programming, assuming that transit ISPs provide caches at peering points with stub networks. In this paper, we apply this method to 31 commercial ISP networks and numerically investigate the properties of nodes where cache deployments are effective and the topology structure in which caches are effective.

IEICE technical report 36 7 - 12 In the Internet, video streaming service in which users can enjoy videos at home is becoming popular. However, the transmission bit-rate of video streaming with high quality is quite large, so generated traffic flows will cause link congestion.

In the Internet, routes that packets take are determined by using static link weights, so the maximum network throughput, i. In this paper, we propose that ISPs use parallel download to deliver rich content to balance the link utilization, and propose optimum server allocation and server selection methods for parallel download.

Many reports show that Internet traffic measured at large scale networks such as backbone networks exhibits visible strong cyclic characteristics such as the diurnal pattern and the weekly pattern. The authors so far have proposed a method of detecting anomalous sudden changes, which is caused by DDoS Distributed Denial of Service attack or network failure, accurately by utilizing such a cyclic tendency. In the proposed method, we need to manually distinguish whether the traffic has cyclic characteristics or not.

However, in order to detect network anomalies in a large scale network, it is important to distinguish whether traffic has cyclic tendency or not automatically. In this paper, aiming to establish a method of automatically distinguishing the cyclic tendency, we apply the Fourier transform to time series data of traffic which was measured at a large scale network and show the result of relation between cyclic tendency and volume of traffic.

However, the design problem of caches for P2P traffic has not been well investigated although the effect of caches strongly depends on the cache locations and cache capacities. In this paper, we propose an optimum design method of caches for P2P traffic minimizing the total amount of P2P traffic based on the dynamic programming, assuming that transit ISPs provide caches at peering points with stub networks.

Moreover, we numerically show the results of applying the proposed cache design method to 31 actual ISP backbone networks. IEICE technical report 15 - 20 Recent drastic increase in the number of spam messages has caused significant overload on e-mail delivery systems.

IP reputation services such as DNSBL DNS BlackList have been widely used as an effective way to lower the overhead of e-mail delivery system by restricting smtp connections based on the reputation listed in the blacklists. Since those reputation services require only IP address lookups, they are the most light-weight and scalable anti-spam solution. However, these approaches have fundamental limitations, namely, flexibility, extensibility, locality, and the explicit modeling of spamicity and legitimacy.

In this work, we attempt to relax the limitations of existing IP repuration-based approaches by leveraging statistical technique. Hence, we call our method PrBL probabilistic blacklist. The key idea of our approach is to make use of the property of e-mail senders in terms of geographical and logical network locations, and the intrinsic signatures derived from the analysis of TCP headers, which are independent of e-mail content.

Machine-learning tool is used to establish the probabilistic classification of e-mail senders. We validate the performance of PrBL through the analysis of SMTP logs collected at an enterprise e-mail server over 4-months of period. We also show that by tuning the policy parameter, PrBL can establish much better accuracy i. IEICE technical report 81 - 86 P2P CDN has attracted more and more attentions as a mean to establish flexible and effieicent engineering of network resources such as network links or server CPU loads.

Many researchers have validated the effectiveness of the P2P CDN approaches, however, to the authors'best knowledge, there have been no studies that addresses how the peers can be incentivized in the systems;thus, deployablity of the system with respect to user incentive is remaining as an open problem.

This paper attempts to address this problem by giving a business model that the incentive to users is provided by ISP. We first show a framework how an ISP can design the optimum incentive while making a good trade-off between cost and reward. We also discuss its benefit and potential problems. IEICE technical report 43 - 48 It is highly anticipated that downloading rich content with huge size, such as movie content, becomes a popular service on the Internet in near future. The transmission bandwidth consumed by delivering rich content is enormous, so it is an urgent matter for ISPs to design the efficient delivery system minimizing the amount of network resources consumed.

To provide users rich content economically without stress, it is effective that an ISP itself optimally provides servers with huge storage capacity at a limited number of locations within its network. So, the authors investigated the content deployment method, the delivery process, and the server allocation method which are desirable for the ISP-operated CDN. In this paper, we evaluate the content deployment process, the estimation accuracy of the average hop length, and the reduction effect of total amount of traffic over 31 topologies of actual ISPs, and we clarify the availability of the ISP-operated CDN.

IEICE technical report 63 - 68 In these years, the number of users downloading video contents on the Internet has dramatically increased, and it is highly anticipated that downloading rich contents with huge size, such as movie contents, becomes a popular service on the Internet in near future. The transmission bandwidth consumed by delivering rich contents is enormous, so it is an urgent matter for ISPs to design the efficient delivery system minimizing the amount of network resources consumed.

As a way of efficiently delivering web contents, CDN contents delivery network has been widely used. Using CDN, however, it is difficult to minimize the amount of network resources consumed because a CDN provider selects a server for each request based on rough estimates of response time. Moreover, CDN providers collocate a huge number of servers within multiple ISPs, so it is difficult to increase the storage capacity of each server because of the total storage cost.

Therefore, ordinary CDN is not suited for delivering rich contents. On the other hand, P2P-based delivery system is becoming popular as a scalable delivery system. However, by using P2P-based system, we cannot still obtain the ideal delivery pattern which is optimum for ISPs because server function depends on users behaving selfishly.

To provide users rich contents economically without stress, it is effective that an ISP itself optimally provides servers with huge storage capacity at a limited number of locations within its network. In this paper, we investigate the content deployment method, the delivery process, and the server allocation method which are desirable for this ISP-operated CDN. B Mean-variance characteristic of spatially partitioned traffic and its applications to estimation of traffic variations. In the Internet, the rapid spread of worms is a serious problem.

In many cases, worm-infected hosts generate a huge amount of flows with small size to search for other target hosts by scanning. Therefore, we defined hosts generating many flows, i.

However, some legitimate hosts generating many flows, such as DNS servers, can also be superspreaders. Therefore, if we simply regulate all the identified superspreaders, e. Legitimate hosts generating many flows tend to be superspreaders in multiple continuous measurement periods.

In this paper, we propose a method of extracting worm-infected hosts from identified superspreaders using a white list. We define two network statuses, a normal state and a worm-outbreak state.

During the normal state, the IP addresses of identified superspreaders are inserted into the white list. During the worm outbreak state, worm-infected hosts are extracted from the identified superspreaders by comparing them with the host entries stored in the white list. Using an actual packet trace and a simulated abusive traffic, we demonstrate that many legitimate hosts are filtered from the identified superspreaders while suppressing the increase in incorrectly unextracted worm-infected hosts.

DOI CiNii. Abusive traffic caused by worm is a serious problem in the Internet because it consumes a large portion of network resources. In many cases, worm-infected hosts generate huge amount of flows with small size to search other target hosts by port-scanning.

So, we proposed a method identifying suspicious worm-infected hosts by flow sampling. In this paper, we propose a design method for these three parameters to satisfy that the ratio of the active worm-infected hosts to all vulnerable hosts is bounded by a given upper-limit during the time T required to develop a patch or an anti-worm vaccine. IEICE technical report 98 79 - 84 In the Internet, a rapid spread of worm is a serious problem.

So, we defined hosts generating flows more than or equal to the threshold during a measurement period as superspreaders and proposed a method identifying superspreaders by flow sampling. However, some normal hosts generating many flows, such,as DNS servers, can be also superspreaders.

Therefore, if we regulate all identified superspreaders, e. Normal hosts generating many flows tend to be superspreaders in multiple continuous measurement periods. So in this paper, we propose a method of identifying worm-infected hosts using a white list. During a normal period, we insert the IP addresses of identified hosts into the white list.

During a worm outbreak period, we identify worm-infected hosts by comparing the identified host with those stored in the white list. B Detection accuracy of network anomaly detection using sampled flow statistics. B Detection accuracy of network anomaly detection using sampled packet statistics. Effect of sampling rate and monitoring granularity on anomaly detectability. In this paper, we quantitatively evaluate how sampling decrease detectability of anomalous traffic. We then show by changing measurement granularity, we can detect anomalies even with low sampling rate by using the relationship between the mean and variance of aggregated flows.

With those equations, we can provide answers to the questions that arise in actual network operators, and had not been answered yet, such as which sampling rate to set in order to find the given volume of anomaly, or, if the sampling is too high for the actual operation, then which granularity is optimal to find the anomaly with given lower limit of sampling rate.

Detection accuracy of network anomaly detection using sampled flow statistics. We showed so far that network anomalies generating a huge number of small flows, such as network scans or SYN flooding, become hard to detect when we execute the packet sampling. This is because such flows are more unlikely to be sampled than normal flows. In this paper, we thus investigate the effect of packet sampling on the detection accuaracy. We also compare the detection accuracy under packet sampling with that under flow sampling.

In addition, we also develop a method of spatially partitioning the traffic into groups to increase the detectability, as well as the way of determining the appropriate number of groups. BS A method of detecting network anomalies for periodic traffic.

We present a method of detecting network anomalies, such as DDoS attacks and flash crowds, automatically in real time. We evaluated this method using measured traffic data and found that it successfully differentiates suspicious traffic.

Our method differentiates suspicious traffic that have different statistical characteristics from normal traffic. At the same time, our method learns periodic large-volume traffic, such as operating traffic, and considers them as legitimate at the end. Therefore, our method has fewer false-positives than original methods which do not consider periodic tendency. A method of detecting network anomalies and determining their termination. Detecting network anomalies such as DDoS attack has become more and more crucial in these days.

When we monitor large-scale networks, it is essential to improve the accuracy of anomaly detection while keeping the operation overhead as small as possible. Moreover, it is necessary to determine network anomalies' termination properly. These are because detecting network anomalies and determining their termination become triggers for the start of causal analysis and the end of network controls.

In this work, we develop a method of anomaly detection that detects anomalies automatically and determines their termination in real time. Further, we evaluate our method using measured traffic data. A study on detecting network anomalies using sampled flow statistics. We investigate how to detect network anomalies using flow statistics obtained through packet sampling. First, we show that network anomalies generating a huge number of small flows, such as network scans or SYN flooding, become hard to detect when we execute the packet sampling.

As a solution to this problem, we then show that we can increase the detectability of such anomalies by spatially partitioning the monitored traffic into some groups so that we concentrate anomalous flows on particular group s. We also show its effectiveness through actual measurement data.

IEICE technical report 37 - 42 Inferring original traffic pattern from sampled flow statistics. Packet sampling has become a practical and indispensable means to measure flow statistics. Nowadays, most of major ISPs are monitoring their networks based on the sampled flow statistics collected at main routers.

Recent studies have demonstrated that analyzing traffic patterns is crucial in detecting network anomalies. For example, sharp increase in the number of small flows may be related to an anomalous event such as worm outbreak.

We may not be able to infer the original traffic patterns correctly from the sampled flow statistics because sampling process wipes out a lot of information about small flows, which play a vital role in determining the characteristics of traffic patterns.

In this paper, we first show an example of how the sampling process wipes out the original statistics using measured data. Then, we show empirical examples indicating that the original traffic pattern cannot be inferred correctly even if we use a statistical inference method for incomplete data, i. Finally, we show that additional information about the original flow statistics, the number of unsampled flows, is helpful in tracking the change in original traffic patterns using sampled flow statistics.

IEICE technical report 5 - 8 Multicast is efficient transfer scheme for content distribution in terms of lighter load on the network and server, but it is necessary to meet security issues. In particular, "Source authentication" is one of the important techniques for protecting from malicious users that plot eavesdropping, masquerading and so on. On the other hand, data reconstruction is one of the necessary techniques, because distributed data packets are often lost in the network, and the loss sometimes causes the fatal deterioration of the quality without data reconstruction.

Many schemes for source authentication and data reconstruction have been proposed individually, but no scheme considering the combination of these researches have been proposed. IEICE technical report 97 - Worm-infected hosts generate a large number of flows during a short time. We proposed a method identifying hosts that generate many flows, i.

This method consists of a Bloom filter finding a new flow and a host table storing the sampled flow count of each host. We also proposed an optimum memory allocation method for each module to minimize the false negative ratio.

To obtain the optimum identification threshold, we need to appropriately estimate the median of flow count for flow hogs. In this paper, we propose a method accurately estimating the median from the host set identified in the previous measurement period. We also show the results of performance comparisons with other methods.