Show conn on ACE
I have some question related show conn on ace
the log like below:
ACEAD#1/130# show conn de | be 2633
2633 1 in TCP 330 100.254.130.13:39560 100.254.16.11:389 ESTAB
[ idle time : 00:33:21, byte count : 334 ]
[ elapsed time: 00:48:35, packet count: 5 ]
11239 1 out TCP 30 100.254.16.11:389 100.254.130.13:39560 CLOSED
[ conn in reuse pool : FALSE]
[ idle time : 00:33:21, byte count : 261 ]
[ elapsed time: 00:48:35, packet count: 3 ]
ACEAD#1/130# show conn de | be 2633
2633 1 in TCP 330 100.254.130.13:39560 100.254.16.11:389 ESTAB
[ idle time : 00:33:49, byte count : 334 ]
[ elapsed time: 00:49:03, packet count: 5 ]
11239 1 out TCP 30 100.254.16.11:389 100.254.130.13:39560 CLOSED
[ conn in reuse pool : FALSE]
[ idle time : 00:33:49, byte count : 261 ]
[ elapsed time: 00:49:03, packet count: 3 ]
100.254.130.13 is server side ip address.
100.254.16.11 is outside client's ip address
connection id 2633's connections status is ESTAB. but connection id 11239 is CLOSED
Is this a pair connection between 100.254.130.13 and 100.254.16.11?
In log, there are different connection id two flow each other.
If two connection is pair connection, why conn'id 2633 is ESTAB, and conn'id 11239 is CLOSED?
Or not, Is it a single flow , no related each other?
There are no explanation about this issue in document. I have no experience about this with Cisco ACE.
Anyone help me!.
The output you provided in the beginning of the is two flows that make up a single connection.
When a client initiates a connection to the ACE virtual address two flows are created on the ACE. flow-1 is client to ACE and flow-2 is ACE to server. But both of these flows are tied together and make up the connection.
My assumption on what is happening in your output:
1. This is the flow from the ACE to the server. The server has sent a FIN so this is why the ACE displays the connection as closed.
11239 1 out TCP 30 x.x.x.x:389 x.x.x.x:39560 CLOSED
2. This is the flow between the client and the ACE. The ACE has not seen a FIN ACK from the client so the connection remains open.
2633 1 in TCP 330 x.x.x.x:39560 x.x.x.x:389 ESTAB
3. These flows will remain in the connectino table until the idle timer expires (half-closed) or the ACE recieves a FIN ACK, RST, etc. from the client.
Here is documentation on setting the different idle timers on ACE.
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/v3.00_A1/configuration/security/guide/tcpipnrm.html#wp1072427
Similar Messages
-
Conn id in 'show conn' display - ACE
I would like to identify the latest connections in the 'show conn' table. Does the table build up in a linear fashion i.e. the latest con is the last row. Can timestamp be enabled on the 'show conn' display. Also, how is the conn id generated. I don't see it in sequence.
ACE is actually the combination of 3 CPU.
The Control Plane (CP) which is the management side - holds the configuration, answers snmp queries, sends probes,...
The IXP are the 2 CPU actually switching the traffic.
They are also called network processors or NP.
This is the 2nd column of the 'show conn'.
Gilles. -
ACE Sticky Connections, Show Conn Output and Show serverfarm
Hi Community,
I'm deploying a Cisco ACE module and I have some questions about sticky connections and about the output of the show conn command and show serverfarm command.
I have the follwoing configuration:
rserver host srv_1 ip address 10.4.11.14 inservicerserver host srv_2 ip address 10.4.11.18 inserviceserverfarm host farm_144 rserver srv_1 144 weight 1 inservice rserver srv_2 144 weight 3 inservice
sticky ip-netmask 255.255.255.255 address source st_host144
timeout 10080
serverfarm farm_144
class-map match-all vip_144
2 match virtual-address 10.4.11.208 tcp eq 143
policy-map type loadbalance first-match lb_144
class class-default
policy-map multi-match policy_vip_webcache
class vip_webcache_144
loadbalance vip inservice
loadbalance policy lb_144
loadbalance vip icmp-reply active
nat dynamic 411 vlan 411
We can assume that service policy was applied at the interface vlan. So, let's go to the questions:
1- If sticky is enabled the output command "show conn" should show just one entry by ip address?
The real output is:
DC01-ACE-01-PRIMARY-SW1/context_servidores# show conn | inc :143333046 1 in TCP 411 10.2.158.87:3616 10.4.11.208:143 ESTAB 286390 3 in TCP 411 10.2.158.87:3562 10.4.11.208:143 ESTAB310233 1 in TCP 411 10.1.5.87:3424 10.4.11.208:143 ESTAB
Look that the ip address 10.2.158.87 is shown 2 times. In same times, the same ip address is shown 4 times to the same VIP and the same port. Is it a normal behavior?
2- According to the configuration, the srv_2 has weight 3 and srv_1 has weigth 1, but the output of show serverfarm show somethin strange:
DC01-ACE-01-PRIMARY-SW1/context_servidores# show serverfarm farm_144 serverfarm : farm_144, type: HOST total rservers : 2 state : ACTIVE DWS state : DISABLED --------------------------------- ----------connections----------- real weight state current total failures ---+---------------------+------+------------+----------+----------+--------- rserver: srv_1 10.4.11.14:144 1 OPERATIONAL 11 386 0 rserver: srv_2 10.4.11.18:144 3 OPERATIONAL 35 66 0
We can see that the weight is working good, but the total of connections is higher at srv_1 than srv_2. Why?
Somebody can help me to understand better this problem of if its a normal behavior?
Thanks in advance!!Hi Gaurav,
About question 1, I got some informations too. It's perfectly normal the client open 2 or more connections at the same time. The client's application is the responsable. We removed the ACE and put the client directly to the server and the result of the total connections opened was the same.
About question 2, I made some "clears" on the serverfarm, the sticky database and after that, the numbers were more real.
DC01-ACE-02-SECONDARY-SW1/context_servidores# sh serverfarm farm_webcache_144
serverfarm : farm_webcache_144, type: HOST
total rservers : 2
state : ACTIVE
DWS state : DISABLED
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: srv_webcache_1
10.4.11.14:144 1 OPERATIONAL 1025 15499 4436
rserver: srv_webcache_2
10.4.11.18:144 2 OPERATIONAL 1794 33471 471
DC01-ACE-02-SECONDARY-SW1/context_servidores#
Anyway thank you very much for your feedback.
Plínio Monteiro -
Question about ACE show Conn command (tcp duration)
Hello,
I was checking connections and noticed that I would see the initial connection, but after a short time the connection quits showing up in the counters and the “show conn” command. However the user is still up and working.
This is the command I used:
sho conn serverfarm STAGING-HTTPS detail
The output shows all the connection info from source to destination, and in the ESTABLISHED state.
However, after maybe 2~3 minutes, when I up arrow I don't see any connection info. The web page is still up. If I refresh the web page, I do see the connections come in.
Can someone kindly point me to a document or provide an answer on how long should the connection be stored before they are flushed?
Config profile:
4 real servers
HTTPS protocol
Leastconn for predictor
sticky based on src/dst IP
Thanks,
RamanRaman,
If you would play with a sniffer capture, you could answer the question yourself.
If the browser loads a flash object or a java applet, once it is loaded, you can still work on the page but there is no data transfer.
with a sniffer tool you could see the browser closing the connections.
The default TCP idle timeout on ACE is 1 hour.
Gilles. -
Cisco ACE - "show conn" command queries
Hi all,
i have some queries regarding the "show conn" command in Cisco ACE.
Working Scenario:
VIP : 10.10.10.1
Server 1 : 10.10.20.1
Server 2 : 10.10.20.2
Client: 30.30.30.1
When a client 30.30.30.1 initiates a connection to the VIP on 10.10.10.1, the ACE load balances it to Server 1, 10.10.20.1. Looking at the "show conn" table, it shows that Server 1 is replying back to the Client 30.30.30.1 through the ACE.
Now, my question is when the ACE returns the traffic to the Client, should the Client be seeing the source IP coming from the VIP or Server 1? My understanding is that the Client should be seeing traffic returning from the VIP. But the show conn table does not seem to suggest so.
show conn table
conn-id np dir proto vlan source destination state
----------+--+---+-----+----+---------------------+---------------------+------+
1768 1 in TCP 10 30.30.30.1:9221 10.10.10.1:80 ESTAB
41 1 out TCP 52 10.10.20.1:80 30.30.30.1:9221 CLOSEDDaniel,
The client is expecting a response from the VIP otherwise there would be an asymmetrical routing problem and conns will never complete.
The fact that you're seeing 30.30.30.1 as the destination address is just that the server is able to see client's IP address on the request, when your backend servers sends the reply back to the client this response is forced to go through the ACE, when the ACE looks at the packet it matches with a previously conn created on the flow table so it "NATs" the reply so now the source of the packet is the VIP and destination is 30.30.30.1.
This is a expected behavior as you're not using S-NAT on your network.
HTH.
Pablo -
Hi Team,
Does the show conn count includes both tcp + udp + embryonic connections.
Because when i do a calculation in excel from the output of show conn, i got the below output.
It was extracted from the command "show local-host | include host|count/limit"
(A):
Total Sum of TCP embryonic count to host = 331
(B):
Total Sum of TCP flow count/limit = 102938
(C):
Total Sum of UDP flow count/limit = 3512505
firewall#show conn count
1912284 in use, 2000002 most used
Please let me know how this is caluclated. If show conn count = A+B+C, then i am suspecting that old connection entries are not getting flushed out from the connection table in cisco asa 5580 with version 8.3.2.
Really im in need of help...Hi Kimberly,
My question was, the count of show conn & show local-host does not match... More over, as the show conn was showing that the max limit of 2 million will be reaching very soon... So, i would like to troubleshoot the output of show local-host | include host|count/limit, where in i could see that one of the webserver has lots of tcp connection (lets say 35000, then the other two servers are consuming udp connections 7lacs,5lacs & 3 lacs, as given below...
local host: ,
TCP flow count/limit = 35857/unlimited
TCP embryonic count to host = 25
UDP flow count/limit = 0/unlimited
local host: ,
TCP flow count/limit = 306/unlimited
TCP embryonic count to host = 8
UDP flow count/limit = 736807/unlimited
local host: ,
TCP flow count/limit = 246/unlimited
TCP embryonic count to host = 2
UDP flow count/limit = 582010/unlimited
local host: ,
TCP flow count/limit = 1/unlimited
TCP embryonic count to host = 0
UDP flow count/limit = 308412/unlimited
can you pls let me know any other commands can be executed to know if any huge embryonic/virus attacks/too many broad casts...... Once i clear the local-host, the connections get reduced from a huge value to low value. i reallly do not know if these are geniue traffic or fake ? or do not know if the connection table is not flushing out old entries.. please help -
Can the show conn state command be used to monitor the connections for fix-up protocols?
Use the show port status command to display port status information.
show port status [mod_num[/port_num]]
Syntax Description
mod_num
(Optional) Number of the module.
/port_num
(Optional) Number of the port on the module.
This example shows how to display port status information for all ports:
Console> show port status
Port Name Status Vlan Level Duplex Speed Type
1/1 connected 523 normal half 100 100BaseTX
1/2 notconnect 1 normal half 100 100BaseTX
2/1 connected trunk normal half 400 Route Switch
3/1 notconnect trunk normal full 155 OC3 MMF ATM
5/1 notconnect 1 normal half 100 FDDI
5/2 notconnect 1 normal half 100 FDDI -
Cisco ASA get 'show conn all long' info through snmp
Hi,
I would need to gather the info about all established connections that I can see on the ASA terminal by using the command
show conn all long
for monitoring purposes through snmp. I am browsing several MIBs&OIDs but no one seems to contain this info.
Does anyone know if this is possible ?
Thanks.
Vladim looking for the solution ? did u ever find out if this was possible?
-
Hi,
Does the ASA have an SNMP OID which will provide information like the show conn command ?2 years later, how's LLDP support via SNMP?
If Cisco does not support LLDP via SNMP, please remove the wrong information from
http://tools.cisco.com/ITDIT/MIBS/MainServlet?ReleaseSel=2514&PlatformSel=231&fsSel=705
Stop lying! -
Right syntax of show conn command
Good day!
Please, help me with correct syntax of show conn command...
I need to show all active tcp connections from inside to outside on port 60565...
Thank you...!Hi,
Well there are a lot of options.
Below is the basic command
show conn
You can use the below commands to get more detailed information
show conn long
show conn detail
You can show certain port connections with the command (with some added parameters)
show conn detail port 60565
Some variation of the below command might also be helpfull
show local-host
Use the "?" (question mark) after the "show local-host" to see what options you have. Same option naturally applies to any other command on the ASA in general.
I would also suggest checking out the ASA Command Reference when you are unclear of the purpose of a certain command. They are listed in alphabetic order
http://www.cisco.com/en/US/docs/security/asa/command-reference/cmdref.html
- Jouni -
Show conn vs. show serverfarm
Hi all.
I have a ACE that shows different outputs in 'sh conn' and 'sh serverfarm':
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER# sho serverfarm STREAMSERVE
serverfarm : STREAMSERVE, type: HOST
total rservers : 2
----------connections-----------
real weight state current total failures
---+---------------------+------+------------+----------+----------+---------
rserver: SRVSTRMAPP01
10.200.12.5:0 8 OPERATIONAL 1 17603 61
rserver: SRVSTRMAPP02
10.200.12.6:0 8 OPERATIONAL 0 16617 86
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER# SH CONN | inclu 10.200.12.6
1135464 1 in TCP 143 10.200.12.6:1094 10.200.1.66:1433 ESTAB
3062787 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1094 ESTAB
2088671 1 in TCP 148 10.21.10.111:3117 10.200.12.6:3389 ESTAB
2106001 1 out TCP 143 10.200.12.6:3389 10.21.10.111:3117 ESTAB
2225411 1 in UDP 143 10.200.12.6:3354 10.8.34.70:88 --
2177453 1 out UDP 148 10.8.34.70:88 10.200.12.6:3354 --
2225669 1 in UDP 143 10.200.12.6:3356 10.8.34.70:88 --
2187600 1 out UDP 148 10.8.34.70:88 10.200.12.6:3356 --
2196103 1 in UDP 148 10.2.8.205:3224 10.200.12.6:161 --
2196243 1 out UDP 143 10.200.12.6:161 10.2.8.205:3224 --
2215001 1 in TCP 143 10.200.12.6:3350 10.200.3.196:445 ESTAB
2228901 1 out TCP 148 10.200.3.196:445 10.200.12.6:3350 ESTAB
2221732 1 in UDP 143 10.200.12.6:138 10.120.236.160:138 --
2218774 1 out UDP 148 10.120.236.160:138 10.200.12.6:138 --
2219128 1 in UDP 148 10.2.8.205:3228 10.200.12.6:161 --
2222138 1 out UDP 143 10.200.12.6:161 10.2.8.205:3228 --
2225008 1 in UDP 143 10.200.12.6:137 10.120.236.159:137 --
2220999 1 out UDP 148 10.120.236.159:137 10.200.12.6:137 --
2229004 1 in UDP 143 10.200.12.6:52684 10.200.0.161:53 --
2221019 1 out UDP 148 10.200.0.161:53 10.200.12.6:52684 --
2221119 1 in UDP 143 10.200.12.6:3363 10.120.236.160:389 --
2222377 1 out UDP 148 10.120.236.160:389 10.200.12.6:3363 --
2229015 1 in UDP 143 10.200.12.6:49834 10.200.0.161:53 --
2224776 1 out UDP 148 10.200.0.161:53 10.200.12.6:49834 --
2517090 1 in TCP 402 10.200.12.61:63072 10.120.239.228:5723 ESTAB
2516578 1 out TCP 148 10.120.239.228:5723 10.200.12.61:63072 ESTAB
2850581 1 in TCP 403 10.200.12.69:58338 10.120.239.228:5723 ESTAB
2853500 1 out TCP 148 10.120.239.228:5723 10.200.12.69:58338 ESTAB
2851806 1 in TCP 402 10.200.12.62:57716 10.120.239.228:5723 ESTAB
2852722 1 out TCP 148 10.120.239.228:5723 10.200.12.62:57716 ESTAB
2940106 1 in TCP 143 10.200.12.6:3151 10.200.1.66:1433 ESTAB
2939888 1 out TCP 148 10.200.1.66:1433 10.200.12.6:3151 ESTAB
2946426 1 in TCP 143 10.200.12.6:1389 10.200.1.66:1433 ESTAB
3063140 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1389 ESTAB
2960597 1 in TCP 143 10.200.12.6:1392 10.200.1.66:1433 ESTAB
2960621 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1392 ESTAB
3064078 1 in TCP 143 10.200.12.6:1408 10.200.1.66:1433 ESTAB
2983064 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1408 ESTAB
3003125 1 in TCP 143 10.200.12.6:1382 10.200.1.66:1433 ESTAB
3064163 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1382 ESTAB
3027036 1 in TCP 143 10.200.12.6:1360 10.200.1.66:1433 ESTAB
3042338 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1360 ESTAB
3027292 1 in TCP 143 10.200.12.6:1398 10.200.1.66:1433 ESTAB
3064186 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1398 ESTAB
3030678 1 in TCP 143 10.200.12.6:1097 10.200.1.66:1433 ESTAB
3063893 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1097 ESTAB
3063784 1 in TCP 143 10.200.12.6:1087 10.200.1.66:1433 ESTAB
3034024 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1087 ESTAB
3034146 1 in TCP 143 10.200.12.6:1088 10.200.1.66:1433 ESTAB
3062203 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1088 ESTAB
3042246 1 in TCP 143 10.200.12.6:1172 10.200.1.66:1433 ESTAB
3058035 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1172 ESTAB
3048113 1 in TCP 143 10.200.12.6:1391 10.200.1.66:1433 ESTAB
3048389 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1391 ESTAB
3058370 1 in TCP 143 10.200.12.6:1099 10.200.1.66:1433 ESTAB
3051850 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1099 ESTAB
3064287 1 in TCP 143 10.200.12.6:1174 10.200.1.66:1433 ESTAB
3056211 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1174 ESTAB
3061991 1 in TCP 143 10.200.12.6:1401 10.200.1.66:1433 ESTAB
3058206 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1401 ESTAB
3062666 1 in TCP 143 10.200.12.6:1108 10.200.1.66:1433 ESTAB
3058214 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1108 ESTAB
3058749 1 in TCP 143 10.200.12.6:1277 10.200.1.66:1433 ESTAB
3062067 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1277 ESTAB
3063953 1 in TCP 143 10.200.12.6:1106 10.200.1.66:1433 ESTAB
3058979 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1106 ESTAB
3059354 1 in TCP 143 10.200.12.6:1145 10.200.1.66:1433 ESTAB
3063650 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1145 ESTAB
3063126 1 in TCP 143 10.200.12.6:1403 10.200.1.66:1433 ESTAB
3059918 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1403 ESTAB
3061461 1 in TCP 143 10.200.12.6:1366 10.200.1.66:1433 ESTAB
3064241 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1366 ESTAB
3061581 1 in TCP 143 10.200.12.6:1362 10.200.1.66:1433 ESTAB
3068243 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1362 ESTAB
3061819 1 in TCP 143 10.200.12.6:1410 10.200.1.66:1433 ESTAB
3064986 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1410 ESTAB
3062574 1 in TCP 143 10.200.12.6:1279 10.200.1.66:1433 ESTAB
3062734 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1279 ESTAB
3063558 1 in TCP 143 10.200.12.6:1085 10.200.1.66:1433 ESTAB
3063621 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1085 ESTAB
3065061 1 in TCP 143 10.200.12.6:1359 10.200.1.66:1433 ESTAB
3064136 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1359 ESTAB
3064865 1 in TCP 143 10.200.12.6:1407 10.200.1.66:1433 ESTAB
3064795 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1407 ESTAB
3064819 1 in TCP 143 10.200.12.6:1412 10.200.1.66:1433 ESTAB
3067998 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1412 ESTAB
3069837 1 in TCP 143 10.200.12.6:1558 10.200.1.66:1433 ESTAB
3065138 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1558 ESTAB
3066038 1 in TCP 143 10.200.12.6:1657 10.200.1.66:1433 ESTAB
3073925 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1657 ESTAB
3072020 1 in TCP 143 10.200.12.6:1766 10.120.238.225:445 ESTAB
3066123 1 out TCP 148 10.120.238.225:445 10.200.12.6:1766 ESTAB
3069814 1 in TCP 143 10.200.12.6:1666 10.200.1.66:1433 ESTAB
3074035 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1666 ESTAB
3073244 1 in TCP 143 10.200.12.6:1664 10.200.1.66:1433 ESTAB
3074019 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1664 ESTAB
3084985 1 in TCP 143 10.200.12.6:1986 10.200.1.66:1433 ESTAB
3084992 1 out TCP 148 10.200.1.66:1433 10.200.12.6:1986 ESTAB
3671975 1 in TCP 143 10.200.12.6:3332 10.200.1.66:1433 ESTAB
3127024 1 out TCP 148 10.200.1.66:1433 10.200.12.6:3332 ESTAB
3307334 1 in TCP 143 10.200.12.6:3858 10.200.1.66:1433 ESTAB
3206408 1 out TCP 148 10.200.1.66:1433 10.200.12.6:3858 ESTAB
3337113 1 in TCP 143 10.200.12.6:3860 10.200.1.66:1433 ESTAB
3337010 1 out TCP 148 10.200.1.66:1433 10.200.12.6:3860 ESTAB
3348679 1 in TCP 148 10.120.236.139:59785 10.200.12.6:445 ESTAB
3469916 1 out TCP 143 10.200.12.6:445 10.120.236.139:59785 ESTAB
3418603 1 in TCP 143 10.200.12.6:4939 10.200.1.66:1433 ESTAB
3416546 1 out TCP 148 10.200.1.66:1433 10.200.12.6:4939 ESTAB
3797653 1 in TCP 143 10.200.12.6:3369 10.200.1.66:1433 ESTAB
3803076 1 out TCP 148 10.200.1.66:1433 10.200.12.6:3369 ESTAB
4041088 1 in TCP 143 10.200.12.6:3917 10.200.1.65:10016 ESTAB
4041386 1 out TCP 148 10.200.1.65:10016 10.200.12.6:3917 ESTAB
4049962 1 in TCP 143 10.200.12.6:4116 10.200.1.66:1433 ESTAB
4049968 1 out TCP 148 10.200.1.66:1433 10.200.12.6:4116 ESTAB
839009 2 in TCP 148 10.200.1.59:46446 10.200.12.6:139 ESTAB
593571 2 out TCP 143 10.200.12.6:139 10.200.1.59:46446 ESTAB
1600461 2 in TCP 143 10.200.12.6:3336 10.200.0.95:50000 ESTAB
1614811 2 out TCP 148 10.200.0.95:50000 10.200.12.6:3336 ESTAB
1735260 2 in TCP 143 10.200.12.6:3384 10.120.236.206:383 ESTAB
1721573 2 out TCP 148 10.120.236.206:383 10.200.12.6:3384 ESTAB
1838026 2 in TCP 148 10.200.1.63:4611 10.200.12.6:445 ESTAB
1836398 2 out TCP 143 10.200.12.6:445 10.200.1.63:4611 ESTAB
1916222 2 in TCP 143 10.200.12.6:3040 10.200.0.161:135 ESTAB
1913817 2 out TCP 148 10.200.0.161:135 10.200.12.6:3040 ESTAB
1915424 2 in TCP 143 10.200.12.6:3041 10.200.0.161:1026 ESTAB
1915542 2 out TCP 148 10.200.0.161:1026 10.200.12.6:3041 ESTAB
1924604 2 in UDP 148 10.2.8.205:3227 10.200.12.6:161 --
1920075 2 out UDP 143 10.200.12.6:161 10.2.8.205:3227 --
1921374 2 in UDP 143 10.200.12.6:3362 10.8.34.70:88 --
1927933 2 out UDP 148 10.8.34.70:88 10.200.12.6:3362 --
1928900 2 in UDP 143 10.200.12.6:137 10.200.0.161:137 --
1923915 2 out UDP 148 10.200.0.161:137 10.200.12.6:137 --
1928778 2 in TCP 148 10.21.15.0:2071 10.200.12.6:8080 ESTAB
1927395 2 out TCP 143 10.200.12.6:8080 10.21.15.0:2071 ESTAB
1933977 2 in UDP 143 10.200.12.6:3366 10.8.34.70:88 --
1934849 2 out UDP 148 10.8.34.70:88 10.200.12.6:3366 --
2803176 2 in TCP 143 10.200.12.6:1100 10.200.1.66:1433 ESTAB
2703524 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1100 ESTAB
2713308 2 in TCP 143 10.200.12.6:1411 10.200.1.66:1433 ESTAB
2800257 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1411 ESTAB
2766907 2 in TCP 143 10.200.12.6:1084 10.200.1.66:1433 ESTAB
2823713 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1084 ESTAB
2815194 2 in TCP 143 10.200.12.6:1095 10.200.1.66:1433 ESTAB
2785207 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1095 ESTAB
2803275 2 in TCP 143 10.200.12.6:1409 10.200.1.66:1433 ESTAB
2795328 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1409 ESTAB
2806481 2 in TCP 143 10.200.12.6:1665 10.200.1.66:1433 ESTAB
2803242 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1665 ESTAB
2822959 2 in TCP 143 10.200.12.6:1402 10.200.1.66:1433 ESTAB
2806282 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1402 ESTAB
2807545 2 in TCP 143 10.200.12.6:1361 10.200.1.66:1433 ESTAB
2828936 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1361 ESTAB
2817495 2 in TCP 143 10.200.12.6:1089 10.200.1.66:1433 ESTAB
2809525 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1089 ESTAB
2810758 2 in TCP 143 10.200.12.6:1144 10.200.1.66:1433 ESTAB
2826653 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1144 ESTAB
2812119 2 in TCP 143 10.200.12.6:1171 10.200.1.66:1433 ESTAB
2827160 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1171 ESTAB
2826264 2 in TCP 143 10.200.12.6:1098 10.200.1.66:1433 ESTAB
2817672 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1098 ESTAB
2820926 2 in TCP 143 10.200.12.6:1173 10.200.1.66:1433 ESTAB
2818309 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1173 ESTAB
2822420 2 in TCP 143 10.200.12.6:1397 10.200.1.66:1433 ESTAB
2824080 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1397 ESTAB
2822661 2 in TCP 143 10.200.12.6:1091 10.200.1.66:1433 ESTAB
2822577 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1091 ESTAB
2827822 2 in TCP 143 10.200.12.6:1272 10.200.1.66:1433 ESTAB
2823110 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1272 ESTAB
2830309 2 in TCP 143 10.200.12.6:1559 10.200.1.66:1433 ESTAB
2823353 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1559 ESTAB
2823359 2 in TCP 143 10.200.12.6:1365 10.200.1.66:1433 ESTAB
2828555 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1365 ESTAB
2823787 2 in TCP 143 10.200.12.6:1278 10.200.1.66:1433 ESTAB
2826005 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1278 ESTAB
2824445 2 in TCP 143 10.200.12.6:1390 10.200.1.66:1433 ESTAB
3067358 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1390 ESTAB
2827739 2 in TCP 143 10.200.12.6:1406 10.200.1.66:1433 ESTAB
2824710 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1406 ESTAB
2825151 2 in TCP 143 10.200.12.6:1276 10.200.1.66:1433 ESTAB
2825150 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1276 ESTAB
2825389 2 in TCP 143 10.200.12.6:1653 10.200.1.66:1433 ESTAB
2827466 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1653 ESTAB
2825960 2 in TCP 143 10.200.12.6:1400 10.200.1.66:1433 ESTAB
2829250 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1400 ESTAB
2826258 2 in TCP 143 10.200.12.6:1363 10.200.1.66:1433 ESTAB
2828366 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1363 ESTAB
2828459 2 in TCP 143 10.200.12.6:1399 10.200.1.66:1433 ESTAB
2826414 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1399 ESTAB
2826470 2 in TCP 143 10.200.12.6:1105 10.200.1.66:1433 ESTAB
2826511 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1105 ESTAB
2827960 2 in TCP 143 10.200.12.6:1271 10.200.1.66:1433 ESTAB
2826577 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1271 ESTAB
2826991 2 in TCP 143 10.200.12.6:1383 10.200.1.66:1433 ESTAB
2829344 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1383 ESTAB
2828175 2 in TCP 143 10.200.12.6:1662 10.200.1.66:1433 ESTAB
2828019 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1662 ESTAB
2829174 2 in TCP 143 10.200.12.6:1656 10.200.1.66:1433 ESTAB
2829382 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1656 ESTAB
3039878 2 in TCP 143 10.200.12.6:1393 10.200.1.66:1433 ESTAB
2829401 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1393 ESTAB
2832137 2 in TCP 143 10.200.12.6:1660 10.200.1.66:1433 ESTAB
2831829 2 out TCP 148 10.200.1.66:1433 10.200.12.6:1660 ESTAB
2833561 2 in TCP 143 10.200.12.6:1738 10.200.3.163:445 ESTAB
2834440 2 out TCP 148 10.200.3.163:445 10.200.12.6:1738 ESTAB
2835292 2 in TCP 143 10.200.12.6:1749 10.200.3.163:445 ESTAB
2835625 2 out TCP 148 10.200.3.163:445 10.200.12.6:1749 ESTAB
2869822 2 in TCP 143 10.200.12.6:2524 10.200.1.66:1433 ESTAB
2873103 2 out TCP 148 10.200.1.66:1433 10.200.12.6:2524 ESTAB
2966277 2 in TCP 143 10.200.12.6:3864 10.200.1.66:1433 ESTAB
2966255 2 out TCP 148 10.200.1.66:1433 10.200.12.6:3864 ESTAB
ACE-ASERCO/DATACENTER#
ACE-ASERCO/DATACENTER#
As yo can see, the 'current connections' of the 'show serverfarm' is different that the output of 'sh conn' in server 10.200.12.6
Exactly, waht is the difference between the both outputs?
Thanx in advance!Hello David,
- is the server with such ip used in other serverfarms?
- are there connections directly from clients to the server (without using a vip) that are being routed through the ACE?
- are there connections originating from the server that are traversing the ACE?
all the above conditions would results in entries in the connection table unrelated to that particular serverfarm and hence not counted as belonging to it.
Hope it helps,
Francesco -
Breakdown of 'show sticky database' - ACE
I need assistance to interpret the show sticky database response. What does the sticky entry value resolve to.
I have set the stickiness on source and destination addresses. Is it possible to identify from show sticky database that which is the source IP for the sticky entry in the display.No.
Client in this command is actual client.
for e.g following command shows that ACE has a sticky entry for client "x.x.x.x"
and this client is stuck to real server "Rserver2" due to sticky group "STICKY-GP1" and this sticky entry will remain in the sticky DB for 585 more seconds (if the connection remains idle).
switch/ACE# show sticky database client x.x.x.<
sticky group : STICKY-GP1
type : IP
timeout : 10
timeout-activeconns : FALSE
sticky-entry rserver-ints time-to-exp
---------------+--------------+------
2702367184 rserver2:8888 585
Syed -
CFMEDIAPLAYER Shows Conn Error When I Use It
I have ColdFusion 9 installed and have been trying out some of the new tags. In trying to use cfmediaplayer I am not able to play an FLV video located on the same site as the calling page. The tag is this:
<cfmediaplayer autoplay="false" name="GeorgeAndGracie" controlbar="true" fullscreencontrol="true" source="Videos/GeorgeGracie.flv">
There is another thread that discusses this and suggests adding the proper MIME type to our IIS server, but that has been done already. There are a couple other links in the other thread, but the links take me to an Adobe forum post that says I don't have permissions to view it:
http://forums.adobe.com/message/2107303#2107303
http://forums.adobe.com/message/2107540
So I am at a loss. I have tried the tag above using a root-relative address ("/Videos...") and a full URL starting with http, but nothing seems to help.
The paths to the various pieces inside the CFIDE folder should work, because I am seeing the correct-looking JS code in the browser source and I am getting the media player to show up. It is only when I click the Play button that I see "Conn Error".
Has anyone else had this trouble (and fixed it, I hope)? Thanks.The <%@ page import=" "%> tag is used to import other packages/ classes in other packages into your JSP/source file. You cannot import the classes of the same package, which you seem trying to do.
Hence the error!!!
fun_one -
How can I check the virtual-address up using show command in ACE?
I want to check the virtual-address using show command.
however, there are not in ACE. So I used the ping to check virtual-address status in ACE
I want to know the command what is verify virtual-address status , using show command
Thank :)Try -> show arp
There you have a Type column and a Status column.
Look for the entry "VSERVER" in the Type column
Roble -
[FL] slide show con cambio de tamaño de la pelicula
Hola,
ayer me mandaron desde este foro un ejemplo de lo que
intentaba explicar.
http://www.dynamicfactory.us/xmlswf/first/
Es exactamente lo que quiero hacer, un slide show de
imágenes y que el
tamaño de la película cambie según el
tamaño de la imagen.
¿Sábeis donde puedo encontrar un tutorial o algo
que me ayude? Tengo cositas
hechas, pero me están fallando...
Saludos,
RosaMuchas gracias Juan, me ha servido de mucho.
Saludos,
Rosa
"Juan Muro `8¬}" <[email protected]>
escribió en el mensaje
news:ehafdf$5qc$[email protected]..
> Hola Rosa, la verdad es que no es complicado lo que
pides, pero sí largo
> de explicar y laborioso de trabajar. Fíjate en que
no redimensiona la
> película swf incluida en el html, sino que
redimensiona el movieclip que
> contiene las imágenes y texto. Para que las
redimensiones den sensación de
> movimiento debes usar un evento sobre el movieclip,
basado en condiciones
> matemáticas que establezcan su tamaño en cada
momento que se reproduce la
> película.
> En www.ffflashhh.com existe una galería algo
parecida a lo que quieres,
> que reformaremos próximamente, quizá de
momento te sirva. Al menos el
> código está explicado.
> Salu2
> `8¬}
> Juan Mro
> "Rosa" <[email protected]> escribió en el
mensaje
> news:eha7dr$p0i$[email protected]..
>> Hola,
>>
>> ayer me mandaron desde este foro un ejemplo de lo
que intentaba explicar.
>>
http://www.dynamicfactory.us/xmlswf/first/
>>
>> Es exactamente lo que quiero hacer, un slide show de
imágenes y que el
>> tamaño de la película cambie según el
tamaño de la imagen.
>>
>> ¿Sábeis donde puedo encontrar un tutorial
o algo que me ayude? Tengo
>> cositas hechas, pero me están fallando...
>>
>> Saludos,
>> Rosa
>>
>
>
Maybe you are looking for
-
What happened to messages in archive folder that disappeared after 2 days
I archived messages and they showed in the 2014 archive folder and were visible for 2 days. 3 days later the folder is visible but no messages show. What happened? Are they lost forever?
-
This began when an auto update was downloaded to my pc late August. I do use thunderbird 6.02 and that is up to date. That I closed before Firefox update attempt. Task mnager in windows 7 says no programs are running. Current version in firefox is 6.
-
i have a scrollPane in a frame, and the scrollPane contains JPanels. The first JPanel appears and no scrollbar appears due to the JPanel fitting within the frame size..that's fine. Then upon a JButton click, a second JPanel appears in the first JPane
-
Enable, backup and restore FCSvr in command line
Hi All, Anyone know how to enable, backup and restore Final Cut Server in command line? Thanks, Spin
-
While trying to connect with RMAN getting the following error : Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 9.0.0 required My DataBase is: Oracle9i Enterprise Edition Release 9.0.1.0.0 - Production How to upgrade RMAN ? Thx