Forum Discussion
aj1
Sep 14, 2015Nimbostratus
Hi Kevin. Apologies, should have tested this first time around, but it appears specifying the
ss-client-port+33761
option doesn't trim down the table any further, and instead gives all connection table entries based of ss-client-addr+192.168.6.100
. I can see only one entry on the BIG-IP (expected), but multiple when the same options are specified in GET.
show sys connection ss-client-addr 197.72.206.124 ss-client-port 1199
Sys::Connections
172.25.24.86%4:49327 68.67.176.52%4:443 197.72.206.124:1199 68.67.176.52:443 tcp 578 (slot/tmm: 1/1) none
Total records returned: 1
$ curl -sk -u 'admin:admin' -H "Content-Type: application/json" -X GET "https://x.x.x.x/mgmt/tm/sys/connection?options=ss-client-addr+197.72.206.124&ss-client-port+1199"
{
"kind": "tm:sys:connection:connectionstats",
"selfLink": "https://localhost/mgmt/tm/sys/connection?options=ss-client-addr+198.82.208.128&ver=11.6.0",
"apiRawValues": {
"apiAnonymous": "Sys::Connections\n172.25.24.86%4:49435 54.243.90.245%4:443 197.72.206.124:1051 54.243.90.245:443 tcp 35 (slot/tmm: 1/1) none\n172.25.24.86%4:49327 68.67.176.52%4:443 197.72.206.124:1199 68.67.176.52:443 tcp 582 (slot/tmm: 1/1) none\n172.25.24.86%4:49412 17.143.160.159%4:5223 197.72.206.124:1028 17.143.160.159:5223 tcp 402 (slot/tmm: 1/1) none\nTotal records returned: 3\n"
}
}