WAE-512-1G Optimized TCP Connections

Hi all,
Regarding the Sizing Capabilities of a WAE-512-1G Appliance, what is the meaning of the "Optimized TCP Connections" ?
Is this parameter related only from the initiated point ? or from both directions?
I'm asking this because, after instaling in inline configuration, a point-to-point circuit only, (2 WAE's + 1 CM), in the Branch WAE we had a Minor Alarm saying that we have reached the TFO Limitation, and on the ohter end, we haven't that alarm.
Most of the traffic(connections), should be from the Branch to the Central Site.
So, the main question is, if this parameter is related to from where the connection is initiated.
Best Regards,
Bruno PetrÃ³nio

The branch Cisco WAE applies a new TCP option (0x21) to the packet if the application is identified for optimization by an application classifier. The branch Cisco WAE adds its device ID and application policy support to the new TCP option field. This option is examined and understood by other Cisco WAEs in the path as the ID and policy fields of the initial Cisco WAE device. The initial ID and policy fields are not altered by another Cisco WAE. The packet is forwarded to the branch router and then to the WAN.
http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/App_Networking/citrixdg_final.html

Similar Messages

WAAS Optimized TCP Connections

Hi all,
Is there any cli command that gives us an overview of the Total Optimized TCP Connections in the box for that moment ?
Best Regards,
Bruno PetrÃ³nio

Bruno,
Show stat tfo
Will give you the basics on the connections going through the box.
Show stat accelerator
Will give you details on connections going through the AOs.
There are sub commands for both of those CLIs.
Hope that helps,
Dan

WAE 674 Max TCP Connections

Does anyone know how many TCP connections the 674 will support with various memory options?
TIA
mike

Mike,
The WAE-674 will support the following memory/connection options:
4GB = 2,000 Connections
8GB = 6,000 Connections
Regards,
Zach

WAE-512 issue

Dear ,
I have site A and Site B.In site A I have AWe 512 is installed,at site B there is a WAE 512 and WAAS as a CM installed.
All the applications were working fine between site A and site B.All of a sudden applications are not working like RDP,Accessin file server and all not accessible at site A to site B.When I check the connectivity ,it is reachable from site A to site B.
Even telnet from site A to site B to all servers with the port 3389 is connecting.When I check through netstat -an it shows from site A source address to site B destination address to that port 3389 is established.
When mstc to that server is hanging,and \\x.x.x.x\ to remote is not able to open.
Please guide me to resolve.
Regards,

Hi Venkat,
Looking at your issue, are you sure this is WAAS issue? Can you please apply pass thru policy for this traffic and see if it works.
You can also use cli command: show stat conn | in to see if the connection is going thru WAAS and is being optimized. If it shows up as optimized, try putting a pass thru policy for this client and verify the functionality.
Further, is this issue limited to one client / one site / multiple sites? Depending on that you want to focus either on hub site or branch site or single client.
Please also provide us the software version and hardwares you are using at the affected sites.
Feel free to let us know if you think it is WAAS related.
Hope this helps,
Regards.
PS: if this resolves the problem, please mark this as Answered.

HTTP tunneling / number of TCP connections

Environment WLS 7.0 Sp2
We are experimenting with http tunneling and we noticed the following behavior,
when performing a lookup to get a handle to a few session beans that our UI is
using, Weblogic opens an additional TCP connection for every lookup however when
using t3 Weblogic opens a single connection for all of them. Our guess is that
Weblogic's T3 is optimized to pipeline and multiplex everything asynchronously
over one TCP connection.
Is there a way to configure Weblogic to use a single TCP connection when tunneling?

I believe it would just be an OS-level limit, on the number of socket handles that can be opened.

WAAS - TCP Connection High-Water Mark

Is there a way to tell the historical statistic for maximum number of TCP connections in a WAE? We are in the middle of a deployment and I am wondering how well we sized our HQ cluster.

Through CM dashboard -> manage devices and go to edge or core device, you will be able to see the connections for each device.
The other option, is to check and see if you are seeing a lot of bypass traffic.
Once WAAS reaches max, traffic will be bypassed until max sessions drops

Windows XP doesnt detect broken TCP connection

Hi Guys,
I have a client and a server. When they are both on a linux or both on a Windows machines there is no problem.
When the server is on linux and the client is on Windows XP, when the server goes down, the client does not recieve a SocketException.Connection Reset like it should.
It works fine otherwise, does anyone know why Windows cant see the TCP connection breaking if the server is on linux?

Java's platform independence cannot shield you from all variations in the implementation of the TCP/IP stack in the underlying operating system.
If you need to do special tricks for different operating systems chances are you are doing something in a non-optimal way. For the vast majority of programmers TCP/IP "Just Works". You open your sockets, do I/O on them, eventually close them.
If you write into a socket whose peer has done receive shutdown you eventually get an IOException (I'll guesstimate within one or three minutes absolute worst case). If you don't get the IOException then likely your program has a bug, such as ignoring exceptions. Far lesser likelihood is OS bug.
When you say "server goes down" do you mean the OS goes down (as in unplug the network connector), or the OS is shut down with a "shutdown" command, or the program is closed? TCP/IP will behave differently if the remote OS is forcefully brought down vs. the program exits and OS remains running. A "shutdown" command may exhibit either behaviour, depending on OS implementation and random timing effects.

Clearing TCP Connections

Hi,
Is there a WAAS command that will allow me to clear a TCP connection thats been hung for 500+ hours? The WAE is running 4.0.13.b23.
Thanks,
Mike

Thanks Zach,
The app (the only app I've had issue with) in question is a home grown product and I'm not quite sure whats causing the WAE to keep connections so long. I've check asymetric routing etc...but traffic is routing correclty. I think it's an app issue but the developers here don't like it when I say that:) My local SE and CCIE worked on this alittle last week in there lab but I had to finally remove the client and server from my WCCP ACL at the central location. Once I did that it removed the hung connections at the remote WAE (it's inline at the site) but when I logged into the 7300 at the central location I noticed they never cleared on that device. It's not building any new connections just hanging onto the old....for instance some have been open for 1000+ hours. I just don't want to force a reboot to get them cleared but it looks like my only option.
Mike

WAAS/WAVE snmp monitoring of TCP connection count

hi everyone,
i'm wondering if it's possible to query the amount of TCP connections via snmp, that are handled by a wae.
it's an important characteristic value to check if optimization is working properly.
looked over the several MIB documented in the latest config guide, but unfortunately got no clue...
can anyone help?
thanks in advance!

This statistics is currently not instrumented through SNMP. You can, however, access this statistics through the following methods:
CLI
XML API
Transaction Logs
Regards,
Zach

Current Active Optimized TCP Preposition Flows: 24 - Limit ?

Hi all
I have 2 x wae-7341 devices in a farm at our data centre. I have a preposition job running to serve some data to approx 100 edge SRE's.
This has been running for a few nights (due to schedule) and I have been checking b/w usage at our core WAN link.
This only ever reaches approx 1/3 of capacity and I started wondering why we were not driving more data.
Looking at the 2 x 7341's it appears that the TCP preposition flows never reach above 24 per 7341 at any one time.
Is 24 a maximum number of pp flows ? If not, any idea why this number may be so low as I have asked the PP job on the CM to PP to approx 100 sites concurrently ?
We are running 4.3.3 s/w.
7341 (a)
Current Active Optimized Flows:1097
   Current Active Optimized TCP Plus Flows:1060
   Current Active Optimized TCP Only Flows:13
   Current Active Optimized TCP Preposition Flows:24
7341 (b)
Current Active Optimized Flows:1012
   Current Active Optimized TCP Plus Flows:979
   Current Active Optimized TCP Only Flows:5
   Current Active Optimized TCP Preposition Flows:24
thanks
Anthony

Hi Anthony,
Only 24 downstream Cisco WAAS devices at a time can actively receive prepositioned files from a single core Cisco WAE. Additional Cisco WAAS devices assigned to a prepositioning job must wait for the completion of one of those processes. This delay must be taken into account when sizing a Cisco WAAS deployment for CIFS prepositioning.
Given a maximum of 24 prepositioning task processes per core Cisco WAAS device, specifying more than 24 destination sites can significantly extend the time required to complete a prepositioning job. Verify that all files in the prepositioned directory are actually needed at all sites. If they are not, construct multiple prepositioning jobs segregating the sites to receive only those files required. If all files are needed at more than 24 sites, divide the prepositioning job into multiple prepositioning tasks that start at different times
Regards
Kiran.

ASA 5505:Static Routing and Deny TCP connection because of bad flag

Hi Everybody,
I have a problem. I made a VPN site-2-site with 2 ASA 5505. The VPN works great. And I create a redondant link if the VPN failed.
In fact, I use Dual ISP with route tracking. If the VPN fails, the default route change to an ISDN router, situated on the inside interface.
When I simulated a VPN fail, the ASAs routes switch automatically on backup ISDN routers. If I ping elements, it works great. But when i try TCP connection like telnet, the ASAs deny connections:
%PIX|ASA-6-106015: Deny TCP (no connection) from 172.16.10.57/35066 to 172.16.18.1/23 flags tcp_flags on interface interface_name.
the security appliance discarded a TCP packet that has no associated connection in the security appliance connection table. The security appliance looks for a SYN flag in the packet, which indicates a request to establish a new connection. If the SYN flag is not set, and there is not an existing connection, the security appliance discards the packet.
thanks!
EDIT: On the schema, The interface of the main asa is 172.16.18.148...

Check if the xlate timer is set greater than or equal to what the conn timer, so as not to have connections waiting on xlates that no longer exist. To minimize the number of attempts, enable "service resetinbound" . The PIX will reset the connection and make it go away. Without service resetinbound, the PIX Firewall drops packets that are denied and generates a syslog message stating that the SYN was a denied connection.

Opening and closing Multiple TCP connections issues

Hi all I am having an issue with the TCP VI’s and wondering if anyone has experienced this issue.
My application is required to scan 50-100 IP addresses (statically assigned) and discover if an Ethernet device is connect at that IP address. Currently I am able to achieve this by opening a TCP connection and testing the error cluster to determine if a timeout has occurred (no timeout error means Ethernet device available at the IP address). I then ensure that the TCP connections are closed.
The issue I am have is that I require a 1 second delay between the TCP open and the TCP close which significantly slows down the process. Without the 1 second delay the vi successfully connects to the device once then fails to make any TCP connect regardless of the time delay until the PC is reset.
If anyone has any advice I would be very grateful
David Barr
P.S. I have attached a simplified section of code showing this issue
Attachments:
TCP Open close issue.vi ‏15 KB

smercurio_fc wrote:
If I understand you correctly you want the time delay to be 1 second if there's a successful connection....
While I don't have a specific answer for this problem. I want to clarify for him. I believe the issue is, what if all connections ARE there? That means you keep returning a wait of 1 second 50-100 times so It takes 50-100 seconds just to initialize. I think the user is looking for a way to check for valid connections, but do so in such a way that eliminates the need for a wait which is greatly slowing things down.
CLA, LabVIEW Versions 2010-2013

Anyone else having an issue with TCP connections using iCloud for Windows?

Hi,
Before I asked this question, I did wait to see if any related questions came up, but none did, so I submit it now.
On my admittedly older laptop running Windows 7 64b Home, I've run into difficulties with the iCloud for Windows app to the extent that I had to uninstall it.
It would that, as my laptop was running, in the background, iCloudServices.exe would endlessly iterate TCP connections, which, while not actively sending or receiving any data, after some hours would number over 100 instances, taking up resources, and grinding my laptop's WiFi connection to a grindingly slow pace. I ended up, within the app, turning off everything, iCloud Drive and Photos, (I never used bookmarks), but still this would continue to occur.
I contacted Apple Support, explaining what was going on, and they stated they only dealt with IOS and gave me a Microsoft Support number. When I called Microsoft support, I came more and more to the realization that the issue was specifically with the iCloud for Windows app, as that was the only software that was endlessly creating and not closing TCP connections as it was. How was Microsoft supposed to solve an issue with Apple code?
So I called Apple back, whereupon they insisted it was a Microsoft issue. I explained other cloud services installed on the same computer were not having the same issue, it was unique to ICloudServices.exe. They stated they only dealt with IOS. I stated I purchased an iPad Air less than 7 months ago, and was trying to run iCloud in support of that. They again stated they only dealt with IOS, and suggested I again try Microsoft. I asked them if it was reasonable to expect Microsoft to solve issues with Apple code? They said regardless, there was zero support offered for anything having to do with Windows, and all I could do was uninstall the app, which I did, though that did not feel very satisfactory to me. My thinking is, if Apple writes a Windows app in support of their hardware, they should offer support for it.
Anyway, I was just wondering, is this an issue unique to me? or have others experienced a similar issue? I found this issue by opening the Windows Resource Monitor, looking under the Networking tab, and scrolling through the TCP Connections section to find 100+ concurrent iCloudServices.exe instances listed, whereas even Chrome, with multiple tabs and extensions, topped out at around 20.
My one month old Desktop, DYI, sports a solid Asus 1150 MoBo, i7-4790k cpu, 16GB Ram, and an EVGA GTX 970 video card. I list some specs only to illustrate this computer has no hardware issues in comparison to my long in tooth laptop. On this desktop, running Win 8.1 Pro 64b, at least as many, identifiably Apple, background service TCP connections are created even compared to Chrome, regardless of many tabs being open, many extensions, and even some related apps. Adobe does not even come close, though I run the full CC subscription. On this new computer, running Windows 8.1 Pro 64b, there are currently over 50 TCP connections and loopbacks that do not identify themselves, with just a - for the Image, and PID. With the experience on my laptop, I wonder how many of these are generated by Apple software, if not specifically iCloud software?
The frustrating aspect of these connections is they seem in no way active, While the Chrome and Adobe connections can be seen to be transferring data, as long as I am not running iTunes, or so have my iPad actually plugged in, it seems 99% of the time these iCloudServices.exe connections are just taking up ports, neither sending nor receiving any data discernable to me under the Processes with Network Activity, or Network Activity lists, both displayed in the same window as the TCP Connections in the Windows Resource Monitor.
Though I am fairly ignorant as regards coding, it seems as if there is no call to close a connection, very specifically, iCloudServices.exe, when it is no longer needed, and the next time a connection is needed, a new one is opened, rather than accessing the one previously opened. The only other reason I could imagine this might be occurring is if my Norton Internet Security software might mask and/or block the port after a certain time of inactivity.
Anyone out there have any ideas or advice about this? Thanks in advance.

Thanks jared,
I'm still dealing with this issue through Apple. Some time after I posted this, I contacted Apple again. They did start a case up for me, as I was experiencing the same behavior on two different machines, with two different versions of Windows.
So far it remains unsolved. I've logged iClouds for Windows on my desktop, which is brand new, then logged for awhile after completely uninstalling Norton Security Suite, depending on the Microsoft security for some time, and finally logged after I uninstalled iCloud for Windows, restarted, installed a clean download, and connected using a completely different test account, which Apple set up for me. None of this made any difference. Looking at the logs, it seems every 10 minutes, iCloudServices.exe creates a new TCP connection to confirm I'm using less than 5GB on iCloud, (which I am by a good margin, using less than 2GB), it seems this connection is not closed, and when the next iteration rolls around 10 minutes later, a new TCP connection is created. I come very close to having 6 TCP connections created per hour, until I restart my computer. This works out to... 6 x 24 = 144/day.
Perhaps the article you posted will shed some further light on this. I'm thinking seeing the state of the connection through netstats, at the least, could help.
For the last week, I've been putting a hold on further logging, as Apple wants me to create a new user account on one of my computers, install iCloud for Windows there, and log it running in the other account. This however basically means I cannot use my computer for a fair number of hours, and I've been busy enough with work the past week that I haven't the time or energy to afford to set this up and run it. I've had need of my computers too much for the past week.

TCP connection error when sending MODBUS commands to WAGO 750-881 controller after 113655 bytes of data have been sent

Hi all,
I am new to the world of labview and am attempting to build a VI which sends commands to a 750-881 WAGO controller at periodic intervals of 10ms.
To set each of the DO's of the WAGO at once I therefore attempt to send the Modbus fc15 command every 10ms using the standard Labview TCP write module.
When I run the VI it works for about a minute before I recieve an Error 56 message telling me the TCP connection has timed out. Thinking this strange, I decided to record the number of bytes sent via the TCP connection whilst running the program. In doing so I noticed that the connection broke after exactly 113655 Bytes of data had been sent each time.
Thinking that I may have been sending too many messages I increased the While-loop delay from 10ms to 20, 100 and 200 ms but the error remained. I also tried playing with the TCP connection timeout and the TCP write timeout but neither of these had any effect on the problem.
I cannot see why this error is occuring, as the program works perfectly up untill the 113655 Bytes mark.
I have attached a screenshot of the basic VI (simply showing a MODBUS command being sent every second) and of a more advanced VI (where I am able to control each DO of the WAGO manually by setting a frequency at which the DO should switch between ON and OFF).
If anybody has any ideas on where the problems lie, or what I could do to further debug the program this would be greatly appreciated.
Solved!
Go to Solution.
Attachments:
Basic_VI.png ‏84 KB
Expanded_VI.png ‏89 KB

AvdLinden wrote:
Hi ThiCop,
Yes the error occurs after exactly 113655 bytes every time. The timeout control I would like to use is 10ms, however even increasing this to 1s or 10s does not remove the error, which leads me to believe that this is not the issue (furthermore, not adding any delay to the while loop, thus letting it run at maximum speed, has shown that the TCP connection is able to send all 113655 bytes in under 3 seconds again pointing towards the timeout control not being the issue here).
I attempted Marco's suggestion but an having difficulty translating the string returned into a readable string, (rightnow the response given is " -# + ").
As to your second suggestion, I implemented something similar where I created a sub VI to build a TCP connection, send a message and then close the connection. I now build each message and then send the string to this subVI which successfully sends the command to my application. Whilst not being the most elegant method of solving the issue, it has resolved the timeout problem meaning I am able to send as many commands as I want. So in that sense the problem has been solved.
If you still have tips on how to correctly read the TCP read output, I would however like to see if I could not get my first program to work as it is slightly more robust in terms of timing.
Modbus TCP RTU is a binary protocol, as you show in your Basic VI, where you format the data stream using byte values. So you have to interprete the returned answer accordingly with the Modbus RTU spec in hand. Now what is most likely happening is that the connection gets hung after a while since you do NOT read the data the device sends as response to your commands. The TCP/IP stack buffers those bytes and at some point the internal buffers overflow and the connection is blocked by the stack. So adding the TCP Read at strategic places (usually after each write) is the proper solution for this. Is there any reason that you didn't use the NI provided Modbus TCP library?
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to send joystick data over TCP connection

Hi all,
I am a long time Labview discussion forum user for learning, but this is my first time posting a question, I hope somebody can help me!
In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
Again, the actual TCP communication I get, and can operate fine, just formatting all the data into a string (or whatever is required) so that I can unpack on the other side is the issue here.
Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense...
One final question.....I already have a solution to this but using labview for the entirety of this project would be nice. I use skype to stream 1080p video from a webcam to my computer so I can view live feed. Can labview do this? This would be awesome if so, I am just not sure if the communication protocols in use could support real time (or as close as possible to streaming) for 1080p video.
Thanks all in advance for your help,
Physicsnole
Attachments:
cameraserver.vi ‏24 KB
cameraclient.vi ‏18 KB

Physicsnole wrote:
In the attached VI I am trying to send data from a joystick over a TCP connection. I can send data fine using the TCP examples (in fact the majority of my VI is just a copy of the example). However I am to the point where I do not know how to send all the data necessary (3 axis data, 12 buttons, and the POV data) over TCP. Strings, clusters, and arrays were never my strong suite and converting between them is a nightmare for me.
Well, you cast the axis info cluster to a string, but then you cast it back to an array of DBL. Thatr's not compatible. You should probably cast it back to an "axis info" cluster of exactly the same type. Go the the other VI and right-click the cluster wire to create a constant. Now move that diagram cluster constant to the other VI and use it as type.
Your default ports don't seem to match. You seem to have client and server roles confused. In the sever you create a listener, but then you start sending packets, even though no connection is established. The connection needs to be initiated by the client.
Your client stops the loop the first time a timeout is encountered. Shouldn't that be more permanent? Also, please retain code clarity and avoid unecessary complexities. For example, replace the "not or" with a plain "or" and change the loop to "stop if true"
Physicsnole wrote:
Basically I am trying to send each axis data (X,Y, and Z), button data (12 buttons), and POV data (the POV data will be calculated to adjust the position of a camera, so the immediate data is not important, I will add functions to add the change in the button movements to write a standing position for two servos [pan and tilt], for which that I will need to send over the TCP connection) over the TCP connection to control various cameras and motors. I don't know if it is posible to send that much data over a TCP connection in one write VI through a string, and also how to separate the string on the other side in order to control the client VI.
You can send as much as you want. The casting to/from string is the same as described above.
Physicsnole wrote:
Another question I have (not impotant to get the program running just might make it easier on me) is can a TCP server (which sends the data to the client) also recieve data back from the client on the same port ( for example sensor data and digital positions [on,off])? Or do I need to set up two TCP communication loops with the first client acting as the server on a different port than the first, which then sends the data to the original server, which also has a client TCP configuration in another loop? I hope this makes sense..
The primary function of a "server" is to wait for a connection and then communicate with the client once a conenction is established. An established TCP/IP connection is fully two-way and both sides can send and receive.
LabVIEW Champion . Do more with less code and in less time .

WAE-512-1G Optimized TCP Connections

Similar Messages

Maybe you are looking for