25.12.2012 Views

TT CME Gateway System Administration Manual - Trading ...

TT CME Gateway System Administration Manual - Trading ...

TT CME Gateway System Administration Manual - Trading ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>TT</strong> Bandwidth Tester<br />

Results<br />

7 Troubleshooting<br />

2. The utility then prints the IP address of each test channel and returns a<br />

PASSED or FAILED message.<br />

Example:<br />

Run test for subject: <strong>CME</strong>_GLOBEX_MO_MESSAGES<br />

Run Test For 233.119.160.1:10001 on Interface 172.20.16.210<br />

Run Test For 233.119.160.65:100065 on Interface 172.20.28.138<br />

. PASSED<br />

Run test for subject: <strong>CME</strong>_ADMIN_CHANNEL<br />

Run Test For 233.119.160.2:10002 on Interface 172.20.16.210<br />

Run Test For 233.119.160.66:100066 on Interface 172.20.28.138<br />

……………………………………………………….PASSED<br />

3. The utility produces a FAILED test result when one of the following occurs:<br />

• A problem exists with the NetworkInterface parameter setting in the<br />

hostinfo.cfg file.<br />

• Inability to connect to the exchange.<br />

• No heartbeat received within 65 seconds.<br />

Note: If the test fails, <strong>TT</strong> suggests running the tool a second time with the<br />

-verbose option. This provides additional troubleshooting information.<br />

The following illustrates the results the <strong>TT</strong> Bandwidth Tester writes to the<br />

tt_fast_bandwidth.out logfile:<br />

To interpret the <strong>TT</strong> Bandwidth Tester results:<br />

1. The utility lists the MDP interfaces and IP addresses it listens to:<br />

Example:<br />

Create listener for 233.119.160.2.10002 on 172.20.16.210<br />

Create listener for 233.119.160.66.10066 on 172.20.28.138<br />

Create listener for 233.119.160.20.10020 on 172.20.16.210<br />

Create listener for 233.119.160.84.10084 on 172.20.28.138<br />

2. The utility calculates the normalized time difference between packets on the<br />

MDP feed and the machine itself. Ideally, these latencies should be close to<br />

zero.<br />

3. The utility prints out information on dropped and delayed packets. A delayed<br />

packet arrives 100 milliseconds later or more.<br />

Example:<br />

[2007-07-25 16:29:26.295]: <strong>CME</strong>_EQ_FUTURES: 233.119.160.142:10142:<br />

Sequence: 429651 Packet Latency: 100ms<br />

[2007-07-25 16:29:26.295]: <strong>CME</strong>_EQ_FUTURES: 233.119.160.142:10142:<br />

Sequence: 429652 Packet Latency: 102ms<br />

[2007-07-25 16:29:26.295]: <strong>CME</strong>_EQ_FUTURES: 233.119.160.142:10142:<br />

Sequence: 429661 Packet Latency: 102ms<br />

[2007-07-25 16:29:26.295]: <strong>CME</strong>_EQ_FUTURES: 233.119.160.206:10206:<br />

Sequence: 429651 Packet Latency: 102ms<br />

4. At the end of the test, the utility prints a test results summary that shows the<br />

number of dropped and lost packets.<br />

120 <strong>CME</strong> <strong>Gateway</strong> <strong>System</strong> <strong>Administration</strong> <strong>Manual</strong><br />

<strong>Trading</strong> Technologies International, Inc.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!