Support Board
Date/Time: Fri, 07 Feb 2025 12:49:39 +0000
Post From: Short Interruption with TT Routing 2020-05-27 / TT Account Balance/Credit Data
[2020-05-28 02:17:17] |
Sierra Chart Engineering - Posts: 104368 |
Around 11 AM US Eastern time today, 2020-05-27, we had a 2.5 minute interruption with the Sierra Chart/ TT order routing service due to an apparent issue on the TT server. 2 of 6 servers were affected. Details are below: Our tentative conclusion at this point, is that this was an issue with the TT FIX server. However, that still is yet to be determined. Most importantly, you always have the web-based trading panel available that you can use and can easily switch to any server: https://www.sierrachart.com/index.php?page=doc/SierraChartOrderRoutingServiceWithData.php#WebBasedTradingPanel There are several things we want to look into related to this and we have some logs from users. We want to make sure that Sierra Chart is automatically switching to the next server if it is unable to submit a new order, modify or cancel an order, due to the remote server not having a connection to the exchange. The order routing service does support this. And that there is no problem with passing through the server order ID immediately for a new order (Extremely unlikely there is a problem with this). So we are doing a thorough review of everything related to this incident. This is the log of the event from our Aurora order routing server: The data feed was lost. There was no activity for at least 2.0 minutes. | 2020-05-27 11:04:41.203
Connection to the external service has been lost. | 2020-05-27 11:04:41.203 TT FIX Trading: DisconnectFIX called. | 2020-05-27 11:04:41.219 TT FIX Trading: Sending a Logout message. | 2020-05-27 11:04:41.219 TT FIX Trading | Connecting to 192.81.51.68. Port 11702 | 2020-05-27 11:04:42.241 TT FIX Trading socket (81) | Creating socket. Using TLS 1.2. | 2020-05-27 11:04:42.241 TT FIX Trading socket (81) | Connecting to IP: 192.81.51.68. | 2020-05-27 11:04:42.241 TT FIX Trading: Connected to FIX server. | 2020-05-27 11:04:42.243 TT FIX Trading | Sending the Logon message. LocalCompID=LIVE_SIERRA_2 | 2020-05-27 11:04:42.444 TT FIX Trading: Connected. | 2020-05-27 11:04:43.864 This is the communication and information from our infrastructure provider regarding the crossconnect we have with TT: I just looked at the interfaces and both interfaces are clean with no drops. So this tells me that this was a software issue rather then a network/hardware issue. You should really just write directly to the CME and bypass TT for order entry! Here is the configuration of the ports: show configuration interfaces ge-2/1/4 description "XConnect to TT - Cable ID: 129113."; speed 1g; link-mode full-duplex; ether-options { no-loopback; auto-negotiation; no-flow-control; } unit 0 { family ethernet-switching { vlan { members service-121-tt-primary; show configuration interfaces ge-14/1/4 description "XConnect to TT - Cable ID: 129115."; speed 1g; link-mode full-duplex; ether-options { no-loopback; auto-negotiation; no-flow-control; } unit 0 { family ethernet-switching { vlan { members service-122-tt-backup; Here are the port stats: show interfaces ge-2/1/4 Physical interface: ge-2/1/4, Enabled, Physical link is Up Interface index: 944, SNMP ifIndex: 1541 Description: XConnect to TT - Cable ID: 129113. Link-level type: Ethernet, MTU: 1514, MRU: 0, LAN-PHY mode, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Online, Media type: Fiber Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Current address: 10:0e:7e:c5:f9:f3, Hardware address: 10:0e:7e:c5:f9:f3 Last flapped : 2020-04-16 16:45:37 CDT (5w6d 03:44 ago) Input rate : 656 bps (1 pps) Output rate : 696 bps (0 pps) Active alarms : None Active defects : None Interface transmit statistics: Disabled Logical interface ge-2/1/4.0 (Index 1861) (SNMP ifIndex 3370) Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge Input packets : 8375751 Output packets: 7203253 Protocol eth-switch, MTU: 1514 show interfaces ge-14/1/4 Physical interface: ge-14/1/4, Enabled, Physical link is Up Interface index: 934, SNMP ifIndex: 1666 Description: XConnect to TT - Cable ID: 129115. Link-level type: Ethernet, MTU: 1514, MRU: 0, LAN-PHY mode, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Auto-negotiation: Enabled, Remote fault: Online, Media type: Fiber Device flags : Present Running Interface flags: SNMP-Traps Internal: 0x4000 Link flags : None CoS queues : 8 supported, 8 maximum usable queues Current address: 28:8a:1c:62:b1:f3, Hardware address: 28:8a:1c:62:b1:f3 Last flapped : 2020-04-05 13:14:09 CDT (7w3d 07:16 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps) Active alarms : None Active defects : None Interface transmit statistics: Disabled Logical interface ge-14/1/4.0 (Index 1860) (SNMP ifIndex 3369) Flags: Up SNMP-Traps 0x24024000 Encapsulation: Ethernet-Bridge Input packets : 3252278 Output packets: 3428760 Protocol eth-switch, MTU: 1514 Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-05-28 02:19:54
|