WAAS and WCCP
Hello ,
I have many Qs regarding the WAAS implemntation
1- which better , using inline card or wccp and why ( is there any problem with inline cards ?)
2- if we have ASA in the network , is there any os version required for the ASA to support tha WAAS, we have impelmnted the waas with wccp between 2 branches, all traffic optimized but there is 2 applications blocked ( not working at all ) , the 2 applications passing via Firewall is there any known reason for that ?
3- we have cat4500 and it should support wccp to redirect traffic for WAAS , but redirect list is not supported at all, do you know if that for all 4500 platform or for just specific OS or Sup as nothing clear on Cisco regarding this point ( wccp redirect list ).
Thanks
Moamen
Hey Moamen,
1. I would not say either is better, but there are different applications. Where you need more then a single WAE for scaling and redundancy, I would recommend WCCP. Where you have fairly simple topology, requirements for only one WAE, and/or non-Cisco gear, I would probably recommend In-line. I've done ton's of both and both work really well for interception.
2. ASA do have a minimum recommend code version. For interoperability with WAAS, you need Cisco ASA/PIX version 7.2.3 or later. In that version, there is the command "inspect waas" to allow for the sequence number jump in optimized traffic, which is why your ASA is blocking the traffic.
3. The CAT4500 can support WCCP in hardware. The platform hardware only supports ingress interception, L2-redirect, L2-return, mask-assign configs on the WAE and the minimum IOS version I would recommend running would be 12.2(40)SG or later. As you mentioned, there are limitations with the redirect lists, they are NOT supported in any version of IOS, it's a function of the hardware. If you need to exclude traffic, you might want to consider using application policies when using CAT-4500.
I hope that helps you out.
Dan
Similar Messages
-
WAAS and WCCP - looping packet detected
Hi,
Has anyone ran into this senario before. Before anyone answers with "move your WAE off the user subnet", it already has been.
I have wccp 61 redirect in on the user subnet (gig0/0.83 of a dot1q trunk). The WAE is on gig0/1. Before I apply wccp62 to the serial link, I attempt to telnet from a user pc to the router (same subnet, clients default gateway), and the telnet fails. I get a "looping packet detected" on the router console. It shows the source of the packet as the router (wccp router id actually), and the destination ip of the WAE, but the packet came in gig0/1 (interface connected to wae). Obviously the WAE returned the packet to the router (with the original GRE headers, (router as source)). I thought WCCP would understand this as "don't redirect this traffic to me anymore", but the router, actually tries to route it back down gig0/1 and then sees it as a looping packet. I believe the WAE is returning the encapsulated packet to the router to indicate it doesn't want the flow, and the router is attempting to route the GRE packet, instead of realizing it should remove the GRE header and route the internal packet. Router is IOS 12.4(12) as recommended by my Cisco engineer. 2821 router.
For kicks, I continue the WCCP setup on the datatcenter side. As expected, it doesn't work. When I apply the WCCP to the datacenter router (only redirecting lab subnet), the entire lab subnet is unreachable via TCP (but icmp still works as expected).
The WCCP configuration isn't very complex, I can't believe its something I'm doing. I think its a code issue.
Any advise?no "out" anywhere. The LAB router has a WAE list to only allow redirect to the lab WAE. I don't even need the 62 in on the WAN side, just applying 61 in on the LAN side breaks telnet to the router.
LOOPING PACKET DETECTION:
from router console
Feb 27 14:56:32.924: %IP-3-LOOPPAK: Looping packet detected and dropped -
src=132.242.11.18, dst=153.61.83.70, hl=20, tl=76, prot=47, sport=0, dport=0
in=GigabitEthernet0/1, nexthop=153.61.83.70, out=GigabitEthernet0/1
options=none -Process= "IP Input", ipl= 0, pid= 77 -Traceback= 0x410F6978 0x415CC960 0x415CDC60 0x415BBB38 0x415BCF18 0x415BD27C 0x415BD2FC 0x415BD4E8
Router configuration:
ip wccp 61 redirect-list REDIRECT-WAAS-SUBNETS-61 group-list remote-waas-box
interface Loopback0
ip address 132.242.11.18 255.255.255.255
h323-gateway voip bind srcaddr 132.242.11.18
interface GigabitEthernet0/0.83
description << data vlan 83 >>
encapsulation dot1Q 83
ip address 153.61.83.3 255.255.255.192
ip helper-address 192.127.250.22
ip helper-address 149.25.1.182
no ip proxy-arp
ip wccp 61 redirect in
standby 83 ip 153.61.83.1
standby 83 priority 200
standby 83 preempt
standby 83 track Serial0/1/0:0.99 100
interface GigabitEthernet0/1
description << WHQ LAB CE connection >>
ip address 153.61.83.65 255.255.255.192
load-interval 30
duplex full
speed 100
ip access-list standard remote-waas-box
permit 153.61.83.70
ip access-list extended REDIRECT-WAAS-SUBNETS-61
permit ip 153.61.83.0 0.0.0.63 any
WAE configuration:
device mode application-accelerator
primary-interface GigabitEthernet 1/0
interface GigabitEthernet 1/0
ip address 153.61.83.70 255.255.255.192
no autosense
bandwidth 100
full-duplex
exit
wccp router-list 1 153.61.83.65
wccp tcp-promiscuous router-list-num 1
wccp version 2
wccp slow-start enable -
Is it possible to transition between two different WAAS appliances if using WCCP redirection? Currently I'm using a WAVE 274 and want to migrate to a recently installed NM-WAE-522. WCCP is currently being used to redirect traffic to the WAVE. Can I simply add the WAE to the WCCP config and then remove the WAVE?
Does it matter that they are in the same subnet or not? The NM-WAE-522 is obviously on the same subnet as one of the router interfaces, but the WAVE-274 is actually on a different subnet off of our 6509. I thought I remembered reading that it was at least recommended that WCCP devices be on the same subnet for load balancing, but I'm guessing it doesn't matter as I'm using L3 GRE redirection.
-
WAAS and WCCP router selection
Hi
Is there some information about that how much of wccp traffic can be handled by different model of routers?
I'm not looking for throughput report like Process\CEF switching per routers but I would like to see some info about wccp treshold on each models, what's the maximum amount of redirected traffic what the router can handle?
thanksno "out" anywhere. The LAB router has a WAE list to only allow redirect to the lab WAE. I don't even need the 62 in on the WAN side, just applying 61 in on the LAN side breaks telnet to the router.
LOOPING PACKET DETECTION:
from router console
Feb 27 14:56:32.924: %IP-3-LOOPPAK: Looping packet detected and dropped -
src=132.242.11.18, dst=153.61.83.70, hl=20, tl=76, prot=47, sport=0, dport=0
in=GigabitEthernet0/1, nexthop=153.61.83.70, out=GigabitEthernet0/1
options=none -Process= "IP Input", ipl= 0, pid= 77 -Traceback= 0x410F6978 0x415CC960 0x415CDC60 0x415BBB38 0x415BCF18 0x415BD27C 0x415BD2FC 0x415BD4E8
Router configuration:
ip wccp 61 redirect-list REDIRECT-WAAS-SUBNETS-61 group-list remote-waas-box
interface Loopback0
ip address 132.242.11.18 255.255.255.255
h323-gateway voip bind srcaddr 132.242.11.18
interface GigabitEthernet0/0.83
description << data vlan 83 >>
encapsulation dot1Q 83
ip address 153.61.83.3 255.255.255.192
ip helper-address 192.127.250.22
ip helper-address 149.25.1.182
no ip proxy-arp
ip wccp 61 redirect in
standby 83 ip 153.61.83.1
standby 83 priority 200
standby 83 preempt
standby 83 track Serial0/1/0:0.99 100
interface GigabitEthernet0/1
description << WHQ LAB CE connection >>
ip address 153.61.83.65 255.255.255.192
load-interval 30
duplex full
speed 100
ip access-list standard remote-waas-box
permit 153.61.83.70
ip access-list extended REDIRECT-WAAS-SUBNETS-61
permit ip 153.61.83.0 0.0.0.63 any
WAE configuration:
device mode application-accelerator
primary-interface GigabitEthernet 1/0
interface GigabitEthernet 1/0
ip address 153.61.83.70 255.255.255.192
no autosense
bandwidth 100
full-duplex
exit
wccp router-list 1 153.61.83.65
wccp tcp-promiscuous router-list-num 1
wccp version 2
wccp slow-start enable -
we are currently using the IP SLA udp jitter measurement to monitor our voice paths accross the WAN. If we implement a partial WAAS across the same WAN the voice traffic will be acellerated but not the IP SLA jitter measurement. Does this mean that when WAAS is implemented IP SLA is limited in its use?
Hi Steve,
The answer to your question depends on 1) how you deploy WAAS and 2) how you use IP SLA. If you deploy WAAS using WCCP for interception, UDP traffic will never be intercepted. If the WAAS device is deployed inline, all traffic flows through the WAAS device, so an IP SLA probe using UDP will be subject to WAAS pass-through handling behavior.
What are you trying to measure with regards to WAAS?
Zach -
WAAS using WCCP with gre tunnel going via vpn
Hello All
I am trying to get WAAS using WCCP to work according to the attached diagram. I would like to know if there is a redirection config that I need to apply to the ASAs?
Many thanks
DonaghHello
Thanks for your reply.
I posted this twice in error.
Original is here
http://preview.tinyurl.com/ygpuehy
You might have a look and see if you agree. I have not deployed yet.
Thanks
Donagh -
Hello,
I seem to be having a lot of trouble with a very simple implementation. I have 2 routers and a data centre WAE via WCCP. These devices are on the same L2/L3 segment (x.x.x.0/24). The WAN interfaces on the routers are in different networks. The remote WAE is inline. I configured ip wccp 61 redirect in on the LAN interface of each router and ip wccp 62 redirect in on the WAN interface of each router. I get the alarm "WCCP router x.x.x.1(LAN) unusable for service id:61 reason redirection mismatch with router" and "WCCP router x.x.x.1(LAN) unusable for service id:62 reason redirection mismatch with router". For the WAN interfaces I get the alarm they are unreachable for the service ID.
Snadard router config
ip wccp version 2
ip wccp 61
ip wccp 62
int gi0/0
description LAN
ip address x.x.x.1
ip wccp 61 redirect in
int gi0/1
description WAN
ip address y.y.y.1
ip wccp 62 redirect in
Should I only be trapping inbound traffic on the LAN interface ?
The other thing I noticed was these messages from the PIX on the same L2/L3 segment
Dec 20 2011 05:49:52: %PIX-2-106006: Deny inbound UDP from WADMZJA02/2048 to IROUTER1/2048 on interface outside
Dec 20 2011 05:49:52: %PIX-2-106006: Deny inbound UDP from WADMZJA02/2048 to IROUTER2/2048 on interface outside
Dec 20 2011 05:49:52: %PIX-2-106006: Deny inbound UDP from WADMZJA02/2048 to IROUTER1/2048 on interface outside
Dec 20 2011 05:49:52: %PIX-2-106006: Deny inbound UDP from WADMZJA02/2048 to IROUTER2/2048 on interface outside
Access list
access-list outside_access_in extended permit udp host WADMZJA02 host IROUTER1 log notifications
access-list outside_access_in extended permit udp host WADMZJA02 host IROUTER2 log notifications
access-list outside_access_in extended permit udp host IROUTER1 host WADMZJA02 log notifications
access-list outside_access_in extended permit udp host IROUTER2 host WADMZJA02 log notifications
Best regards
Stephen
WAE config
sh run
2011 Dec 20 07:06:27 WADMZJA02 -admin-shell: %WAAS-PARSER-6-350232: CLI_LOG log_cli_command: sh run
! waas-universal-k9 version 4.3.1 (build b6 Nov 13 2010)
device mode application-accelerator
hostname WADMZJA02
clock timezone Europe/Brussels 1 0
ip domain-name fibe.fortis
primary-interface GigabitEthernet 1/0
interface GigabitEthernet 1/0
ip address x.x.x.248 255.255.255.0
exit
interface GigabitEthernet 2/0
shutdown
exit
ip default-gateway x.x.x.4 <== firewall
no auto-register enable
! ip path-mtu-discovery is disabled in WAAS by default
! <== traffic to be rerouted outbound ==>
ip route a.a.a.0 255.255.255.0 x.x.x.1 <== Outbound HSRP
ip access-list extended HK
permit ip any 0.0.0.0 255.255.255.0
exit
logging console enable
logging console priority debug
interception access-list HKWAAS
wccp router-list 1 z.z.z.202 y.y.y.122 x.x.x.1 x.x.x.2 x.x.x.3
wccp tcp-promiscuous router-list-num 1 hash-source-ip hash-destination-ip l2-redirect l2-return
wccp version 2
egress-method negotiated-return intercept-method wccp
ip icmp rate-limit unreachable df 0
directed-mode enable
transaction-logs flow enable
--More--
! [K
inetd enable rcp
sshd allow-non-admin-users
sshd enable
tfo tcp optimized-send-buffer 2048
tfo tcp optimized-receive-buffer 2048
accelerator http metadatacache enable
accelerator http metadatacache https enable
accelerator http dre-hints enable
central-manager address x.x.x.247
cms enable
! End of WAAS configurationHi Stephen,
The "Redirection mismatch" messages indicate that the redirection or return method configured on the WAE is not compatible with the router. Probably, the routers you are using don't support L2 redirection
Moving forward, I would recommend you to change the line "wccp tcp-promiscuous router-list-num 1 hash-source-ip hash-destination-ip l2-redirect l2-return" for "wccp tcp-promiscuous router-list-num 1". This will negotiate hash assignment, as well as GRE redirection and return, which are the parameters supported by most platforms.
As for the firewall messages, it seems that some WCCP negotiation packets (UDP port 2048) are being dropped. Unfortunately, my firewall knowledge is very limited, so I cannot really help you with that part.
Regards
Daniel -
WAAS and Juniper Netscreen Interoperability
I've been doing a dig on historical posts relating to WAAS deployed through firewalls.
I am working on a deployment with Juniper Netscreens & ASA5520 sitting between WAE's. IP connectivity is fine. I can ssh to remote device etc. but users cannot login (XP). The login scripts calls upon CIFS etc and I suspect this is being broken through the fw's.
When I disable WAAS for this flow - it all works fine i.e. users can login and access full set of corporate resources. I suspect the firewalls but would appreciate any leads..
thanks
AjazHi Ajaz,
WAAS adds TCP Option 0x21 and increments TCP packet sequence number during TCP handshake. FW needs to be configured to allow
these changes.
On the latest PIX/ASA a new command "ip inspect waas" has been added to allow above changes by wae. You might want to check
Netscreen config guide on command to disable TCP sequence number checking.
If SSH to Servers is working fine then it might not be FW dropping packets. However to confirm it might be best to use
tcpdump/tethereal on both WAEs and to sniff the traffic on whether its being dropped along the path by the FW.
Few questions:
- Whats the version running on WAEs?
- Is it only CIFS traffic which is affected? Try disabling CIFS AO if its enabled and then test.
Hope this helps,
Best Regards,
Rahul Vavale -
We are trying to get our WAAS environment to authenticate against TACACS and then fall over to local if TACACS is unavailable. For engineer logins everything is working as expected. However we are seeing several thousand failures against the TACACS server from a username of "CMS". This user is not configured in the CM or in TACACS. So we log the failed login and CMS logs into the WAE due to the failover to local mechanism. Looking at packet captures, and debugging aaa on the WAE's it is definitely a CMS user that logs in but shows 127.0.0.1 as its "from" host. I am fairly confident this is automation within the WAE syncing with the CM or vice versa. Does anyone know how to get WAAS and TACACS to work together without a mass amount of login failures? Is there a way this CMS user can be cloned/duplicated on the tacacs server? What is the password for this automation user?
Thanks in advance.Hi Stan,
WAE can authenticate against TACACS, RADIUS and Central Manager (Local) at any time depending on your configuration.
There are couple of things to keep in mind while configuring TACACS on WAE, on both sides - TACACS adn WAE CM.
On TACACS side:
1. Please make sure to create right username.
2. Please make sure to verify if you are using ASCII password authentication.
3. Try to use less than 15 letters - Alphanumeric TACACS password.
4. Please provide right user level / group level persmissions. This is somewhere under user account properties. Please also make sure to select right user password under user properties.
5. Verify if this user needs level 15 (admin equivalent account).
On WAE CM side:
1. Please make sure to select right authentication method as primary and secondary.
2. Please make sure to enable the check box for authentication methods.
You can verify the failure / successful log events on TACACS server in order to find out if the user is atleast trying to authenticate against TACACS.
I am sure you have looked at this link to find out all the required steps: Configuring TACACS+ Server Settings
Hope this helps.
Regards.
PS: Please mark this as Answered, if this resolves your issue. -
WAAS and Symantec Vertitas Volume Replicator
Hi,
We are forwarding Symantec replication traffic via our WAAS infrastructure over a 20Mb WAN link. The CM appears to register the traffic but does not optimize it at all. Has anyone had any experience with WAAS and Symantec Veritas Volume Replicator (VVR) 4.3?I tested with VVR in the lab. VVR default uses UDP and using the nerd knob in the GUI did not force VVR to start using TCP. To get VVR to use TCP, I had to input these commands:
vrport data 1999-1999
vrport heartbeat 2000-2000
or use what ever ports you want to use. The previous answer was asking if you were seeing TCP sessions in the WAE's. This can be seen by telneting to the WAE and issueing a "show tfo connection summary". Can you post the output of that command? -
Attach is the Visio as well as config for the India site. The Visio has 2 tabs (POC-WAAS and Proposed-WAAS). The POC (Proof of Concept) tab does not have the spare 3660 installed yet but I plan to do that soon. The "Proposed WAAS" is where we would want to be. However, my question will most likely address POC tab with the preparation to move to the Proposed tab.
Current assumptions:
Since we have a Manager in India, we will be getting another Manager in Calif, If so, I would like to setup a Primary/Standby deployment for redundancy.
Questions:
1. For Calif Primary WAE, the visio shows a Management interface but do I need a management interface or is it better to go with a standby interface instead as well as use MHSRP?
2. Since we have a high speed link (4 Mb Internet for VPN in POC but 10mb WAN for proposed), should we tune the buffers to the max? If so how?
3. Is this a recommend design for California? for India?
4. Is my configs a recommend configs for California 3660 in POC? If so, what do I need to change in 3825 in Proposed?Zach
After reading the SRND, I believe the best design is to move the 512 to the Cores. Please see the updated Visio and planned configs. Here's my updated requirements:
1. Calif is hub
2. All traffic to India (10.2/10.26) should go through the VPN tunnel through (ASA5520)
3. All traffic to 10.3 and 10.5 should go through WAN via (R-Voice2)
4. Latency to India is btwn 280 to 340msec and BW is 2mb. Do I also need to be concern with the BDP, L2 redirect(forwarding), and Mask assignments?
TIA -
Hi all,
Anybody how have setup Cisco WAAS and ERP application BAAN?
I am interesting to setup a full optimization for ERP Baan.
JanHi all,
We found the problem.
TCP/512 was in Classifier Unix-Remote-Execution and this Classifier was in pt.
Jan -
I have configured a pilot WAAS setup in the lab and currently testing for my client. Each time I initiate an FTP download, the download hangs up and fails. Each time I configure "wccp tcp-promiscuous router-list 1" on the core that connects to an MLS, the download works but I see nothing when I do "show tfo conn summary".
Whenever I replace this command "wccp tcp-promiscuous router-list 1" with "wccp tcp-promiscuous router-list 1 l2-redirect mask-assign", the download fails. Also connections using the CM GUI becomes extremely slow but "show tfo conn" command gives an output with FFFFF in it.
Am I missing anything here, please?Thanks for the response. I do have the Core WAE connected to the MLS on a separate interface and on a different Vlan. The only think that I can think of is that the 4506 device that is being used as the MLS does not support the " IP WCCP redirect exclude in" command.
Is there any workaround for this? -
Hi -
We are going into a WAAS deployment and have PIX firewalls running 6.3 code. We are looking to place the WAAS devices on the inside of our firewalls at each end. They will be deployed with WCCP, not inline mode.
I know the "inspect" commands are available in 7.x code, but it will be a big pain to upgrade these firewalls.
From what I read, the WAAS devices use IP or TCP options. Is this true? That's why you need the inspect on 7.x? Is there a way to preserve the options in 6.3 code?
Thanks in advance for a reply! : )Hi Zach;
I am doing one WAAS POC, and I have the problem of the no optmization connections. I reconfigured my appliances, but the prooblem happen, yet.
I would like if pix version ( 6.3.5 ) can to be the my problem?
The brief topology is in attach files.
Regards;
Fabio
Follow any outputs:
REMOTE SITE#SH STaTistics COnnection
Current Active Optimized Flows: 10
Current Active Optimized TCP Plus Flows: 9
Current Active Optimized TCP Only Flows: 0
Current Active Optimized TCP Preposition Flows: 0
Current Active Auto-Discovery Flows: 13
Current Reserved Flows: 10
Current Active Pass-Through Flows: 88
Historical Flows: 200
D:DRE,L:LZ,T:TCP Optimization RR:Total Reduction Ratio
A:AOIM,C:CIFS,E:EPM,G:GENERIC,H:HTTP,M:MAPI,N:NFS,S:SSL,V:VIDEO
ConnID Source IP:Port Dest IP:Port PeerID Accel RR
4061 172.25.101.46:1843 10.40.25.25:8014 00:1a:64:f2:23:81 TA 00.0%
4062 172.25.101.21:3053 10.40.10.102:139 00:1a:64:f2:23:81 TA 00.0%
4063 172.25.101.180:3919 10.40.10.197:8080 00:1a:64:f2:23:81 TA 00.0%
4064 172.25.101.68:4001 10.40.10.31:1417 00:1a:64:f2:23:81 TA 00.0%
4065 172.25.101.54:1703 10.40.10.197:8080 00:1a:64:f2:23:81 TA 00.0%
4066 172.25.101.21:3081 10.44.29.21:1026 00:1a:64:f2:23:81 TA 00.0%
4067 172.25.101.47:1567 10.42.25.25:8014 00:1a:64:f2:23:81 TA 00.0%
4068 172.25.200.250:29314 10.40.100.25:443 00:1a:64:f2:23:81 TA 00.0%
4069 172.25.101.180:3939 10.40.10.197:8080 00:1a:64:f2:23:81 TA 00.0%
4070 172.25.101.24:3123 10.40.15.87:10051 00:1a:64:f2:23:81 TA 00.0%
O-ST: Origin State, T-ST: Terminal State
E: Established, S: Syn, A: Ack, F: Fin, R: Reset
s: sent, r: received, O: Options, P: Passthrough
Local IP:Port Remote IP:Port Peer ID O-ST T-ST ConnType
10.42.25.25:8014 172.25.101.62:3083 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
10.42.25.25:8014 172.25.101.54:1723 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
172.25.101.24:10050 10.40.15.87:45117 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
172.25.101.22:10050 10.40.15.87:54799 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
172.25.101.22:10050 10.40.15.87:53856 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
172.25.101.22:10050 10.40.15.87:54342 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
172.25.101.24:10050 10.40.15.87:38569 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
172.25.101.24:10050 10.40.15.87:38611 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
10.40.10.102:389 172.25.101.22:1984 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
10.40.10.31:1417 172.25.101.68:4006 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
172.25.101.21:445 10.42.10.198:3639 00:1a:64:f2:23:81 SAsO SAr EXTERNAL SERVER
10.40.10.197:8080 172.25.101.54:1722 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
10.40.10.197:8080 172.25.101.54:1721 00:1a:64:f2:23:81 Sr Sso EXTERNAL CLIENT
Local IP:Port Remote IP:Port Peer ID ConnType
172.25.101.151:1062 10.40.15.139:5061 N/A PT In Progress
10.40.10.102:1026 172.25.101.167:4058 N/A PT In Progress
172.25.101.160:1663 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
199.105.179.227:8292 172.25.101.164:8278 N/A PT In Progress
10.40.10.31:1417 172.25.101.162:2598 N/A PT In Progress
10.40.17.107:1494 172.25.101.59:4325 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.102:389 172.25.101.21:3099 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.17.102:1494 172.25.101.69:2151 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.160:1086 10.40.15.139:5061 N/A PT In Progress
10.40.10.197:11801 172.25.101.68:3790 N/A PT App Cfg
10.40.10.197:8080 172.25.101.54:1720 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.21:3101 10.40.10.102:389 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.21:10050 10.40.15.87:58088 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.62:1602 10.40.17.107:1494 N/A PT In Progress
10.40.17.102:1494 172.25.101.42:1240 N/A PT In Progress
10.40.10.102:389 172.25.101.22:1980 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.164:2829 192.168.206.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.170:4868 10.40.15.156:80 N/A PT In Progress
172.25.101.164:1960 10.40.15.139:5061 N/A PT In Progress
172.25.101.21:3099 10.40.10.102:389 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.94:445 172.25.101.22:1976 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.22:1977 10.40.10.94:139 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.22:10050 10.40.15.87:51185 00:1a:64:f2:23:81 PT Asymmetric
192.168.207.15:44718 172.25.101.151:1215 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
192.168.207.15:44718 172.25.101.166:1531 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.22:1976 10.40.10.94:445 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.22:139 10.42.10.57:1513 00:1a:64:f2:23:81 PT Asymmetric
10.40.15.87:50394 172.25.101.22:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.10.197:8080 172.25.101.54:1719 N/A PT In Progress
10.40.15.156:80 172.25.101.170:4869 N/A PT In Progress
10.40.32.128:3630 172.25.101.21:445 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.64:2068 10.40.15.156:80 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.21:139 10.44.31.44:1623 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.151:1215 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.42:1240 10.40.17.102:1494 N/A PT In Progress
10.42.10.57:1513 172.25.101.22:139 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.163:1769 10.40.10.31:1417 N/A PT In Progress
192.168.207.15:44718 172.25.101.41:1213 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.69:1273 10.40.17.107:1494 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.24:10050 10.40.15.87:37482 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.167:3988 10.40.15.139:5061 N/A PT In Progress
10.40.10.197:43079 172.25.101.68:1284 N/A PT In Progress
172.25.101.62:3069 10.42.25.25:8014 N/A PT In Progress
172.25.101.59:4279 10.40.17.102:1494 N/A PT In Progress
172.25.101.47:4625 10.40.17.107:1494 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.166:2849 N/A PT In Progress
172.25.101.164:8278 199.105.179.227:8292 N/A PT In Progress
192.168.206.15:44718 172.25.101.151:1214 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.42:1165 N/A PT In Progress
172.25.101.72:1643 10.40.10.31:1417 N/A PT In Progress
172.25.101.54:1720 10.40.10.197:8080 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.166:1530 192.168.206.15:44718 N/A PT In Progress
172.25.101.164:8277 199.105.179.20:8292 N/A PT In Progress
10.40.15.87:59095 172.25.101.21:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.10.31:1417 172.25.101.42:1167 N/A PT In Progress
10.40.15.87:35209 172.25.101.24:10050 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.166:2849 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1417 172.25.101.61:1454 N/A PT In Progress
10.40.15.139:5061 172.25.101.166:4585 N/A PT In Progress
172.25.101.64:2066 10.40.15.156:80 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.42:1167 10.40.10.31:1417 N/A PT In Progress
172.25.101.42:2161 10.40.10.102:1026 N/A PT In Progress
10.40.10.102:1026 172.25.101.42:2408 N/A PT In Progress
10.42.25.25:8014 172.25.101.62:3069 N/A PT In Progress
172.25.101.62:3076 10.40.10.31:1417 N/A PT In Progress
172.25.101.151:1214 192.168.206.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.170:4869 10.40.15.156:80 N/A PT In Progress
192.168.206.15:44718 172.25.101.159:1187 N/A PT In Progress
172.25.101.152:2984 10.40.10.197:8080 N/A PT In Progress
172.25.101.24:10050 10.40.15.87:35209 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.22:1975 10.40.10.102:389 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.85:4681 172.25.101.21:139 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.164:2830 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.139:5061 172.25.101.158:1130 N/A PT In Progress
10.40.10.31:1417 172.25.101.46:1844 N/A PT In Progress
10.40.10.31:1417 172.25.101.162:2646 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.68:1272 10.40.10.197:42465 N/A PT In Progress
172.25.101.41:1213 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
192.168.207.16:44718 172.25.101.69:1413 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.62:3082 N/A PT In Progress
199.105.179.20:8292 172.25.101.164:8277 N/A PT In Progress
10.40.10.102:389 172.25.101.22:1982 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.44.31.44:1623 172.25.101.21:139 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.42:2408 10.40.10.102:1026 N/A PT In Progress
10.40.15.87:60046 172.25.101.21:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.10.102:1026 172.25.101.42:2161 N/A PT In Progress
172.25.101.68:3790 10.40.10.197:11801 N/A PT App Cfg
172.25.101.21:139 10.40.10.85:4681 00:1a:64:f2:23:81 PT Asymmetric
10.40.15.87:51254 172.25.101.22:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.17.107:1494 172.25.101.69:1273 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.69:2151 10.40.17.102:1494 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.197:8080 172.25.101.54:1717 N/A PT In Progress
172.25.101.160:1662 192.168.206.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.52:1181 N/A PT In Progress
172.25.101.159:1189 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.87:51185 172.25.101.22:10050 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.21:445 10.40.10.172:14095 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.21:445 10.40.32.128:3630 00:1a:64:f2:23:81 PT Asymmetric
10.40.15.156:80 172.25.101.64:2066 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
192.168.206.15:44718 172.25.101.166:1530 N/A PT In Progress
172.25.101.59:4325 10.40.17.107:1494 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.197:8080 172.25.101.152:2984 N/A PT In Progress
10.40.15.139:5061 172.25.101.154:3473 N/A PT In Progress
172.25.101.42:1165 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1417 172.25.101.61:1437 N/A PT In Progress
172.25.101.163:2626 10.41.22.31:139 N/A PT In Progress
172.25.101.22:1980 10.40.10.102:389 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.172:14095 172.25.101.21:445 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.22:10050 10.40.15.87:50394 00:1a:64:f2:23:81 PT Asymmetric
10.40.15.87:57663 172.25.101.21:10050 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.61:1437 10.40.10.31:1417 N/A PT In Progress
172.25.101.42:1242 10.40.17.102:1494 N/A PT In Progress
172.25.101.69:1412 192.168.206.16:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.102:389 172.25.101.22:1975 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.71:2538 10.40.10.31:1417 N/A PT In Progress
172.25.101.22:10050 10.40.15.87:51254 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.159:1187 192.168.206.15:44718 N/A PT In Progress
10.40.10.31:1417 172.25.101.72:1643 N/A PT In Progress
172.25.101.54:1717 10.40.10.197:8080 N/A PT In Progress
172.25.101.167:4056 10.40.10.102:1026 N/A PT In Progress
10.40.15.139:5061 172.25.101.51:3188 N/A PT In Progress
192.168.206.15:44718 172.25.101.160:1662 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.87:35513 172.25.101.24:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.10.31:1417 172.25.101.71:2538 N/A PT In Progress
172.25.101.166:4585 10.40.15.139:5061 N/A PT In Progress
172.25.101.154:3473 10.40.15.139:5061 N/A PT In Progress
172.25.101.158:1130 10.40.15.139:5061 N/A PT In Progress
10.40.17.102:1494 172.25.101.59:4279 N/A PT In Progress
172.25.101.62:3082 10.40.10.31:1417 N/A PT In Progress
10.42.25.25:8014 172.25.101.54:1696 N/A PT In Progress
10.40.10.102:1026 172.25.101.167:4056 N/A PT In Progress
10.40.15.87:58088 172.25.101.21:10050 00:1a:64:f2:23:81 PT Asymmetric
10.40.10.31:1417 172.25.101.166:2831 N/A PT In Progress
172.25.101.166:2831 10.40.10.31:1417 N/A PT In Progress
192.168.207.15:44718 172.25.101.160:1663 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.41:1212 192.168.206.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.163:1769 N/A PT In Progress
172.25.101.61:1454 10.40.10.31:1417 N/A PT In Progress
10.40.17.107:1494 172.25.101.62:1602 N/A PT In Progress
172.25.101.52:1181 10.40.10.31:1417 N/A PT In Progress
172.25.101.24:10050 10.40.15.87:35513 00:1a:64:f2:23:81 PT Asymmetric
10.40.15.139:5061 172.25.101.151:1062 N/A PT In Progress
172.25.101.51:3188 10.40.15.139:5061 N/A PT In Progress
10.40.15.156:80 172.25.101.170:4868 N/A PT In Progress
192.168.206.16:44718 172.25.101.69:1412 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.139:5061 172.25.101.164:1960 N/A PT In Progress
172.25.101.54:1719 10.40.10.197:8080 N/A PT In Progress
172.25.101.166:1531 192.168.207.15:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.54:1696 10.42.25.25:8014 N/A PT In Progress
10.40.17.102:1494 172.25.101.42:1242 N/A PT In Progress
10.40.15.87:59892 172.25.101.21:10050 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.21:10050 10.40.15.87:57663 00:1a:64:f2:23:81 PT Asymmetric
10.40.17.107:1494 172.25.101.47:4625 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.69:1413 192.168.207.16:44718 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.87:37482 172.25.101.24:10050 00:1a:64:f2:23:81 PT Asymmetric
192.168.206.15:44718 172.25.101.164:2829 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.139:5061 172.25.101.160:1086 N/A PT In Progress
172.25.101.22:1982 10.40.10.102:389 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.21:10050 10.40.15.87:59095 00:1a:64:f2:23:81 PT Asymmetric
10.41.22.31:139 172.25.101.163:2626 N/A PT In Progress
172.25.101.167:4058 10.40.10.102:1026 N/A PT In Progress
172.25.101.68:1284 10.40.10.197:43079 N/A PT In Progress
10.40.10.197:42465 172.25.101.68:1272 N/A PT In Progress
172.25.101.162:2598 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1417 172.25.101.62:3076 N/A PT In Progress
10.40.15.139:5061 172.25.101.167:3988 N/A PT In Progress
172.25.101.21:10050 10.40.15.87:60046 00:1a:64:f2:23:81 PT Asymmetric
192.168.206.15:44718 172.25.101.41:1212 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
192.168.207.15:44718 172.25.101.159:1189 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
192.168.207.15:44718 172.25.101.164:2830 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.94:139 172.25.101.22:1977 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.162:2646 10.40.10.31:1417 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.15.156:80 172.25.101.64:2068 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
10.40.10.102:389 172.25.101.21:3101 00:1a:64:f2:23:81 PT Peer AOIM Sync in Pr
172.25.101.21:10050 10.40.15.87:59892 00:1a:64:f2:23:81 PT Asymmetric
172.25.101.46:1844 10.40.10.31:1417 N/A PT In Progress
WAE-DC-CORE#SH STATistics COnnection
Current Active Optimized Flows: 7
Current Active Optimized TCP Plus Flows: 7
Current Active Optimized TCP Only Flows: 0
Current Active Optimized TCP Preposition Flows: 0
Current Active Auto-Discovery Flows: 19
Current Reserved Flows: 10
Current Active Pass-Through Flows: 289
Historical Flows: 200
D:DRE,L:LZ,T:TCP Optimization RR:Total Reduction Ratio
A:AOIM,C:CIFS,E:EPM,G:GENERIC,H:HTTP,M:MAPI,N:NFS,S:SSL,V:VIDEO
ConnID Source IP:Port Dest IP:Port PeerID Accel RR
8192 10.40.15.87:38710 172.25.101.22:10050 00:23:7d:06:4e:7c TA 00.0%
8193 10.40.15.87:45117 172.25.101.24:10050 00:23:7d:06:4e:7c TA 00.0%
8196 10.42.10.198:3639 172.25.101.21:445 00:23:7d:06:4e:7c TA 00.0%
8198 10.40.15.87:53856 172.25.101.22:10050 00:23:7d:06:4e:7c TA 00.0%
8200 10.40.15.87:42552 172.25.101.24:10050 00:23:7d:06:4e:7c TA 00.0%
8201 10.41.4.41:2001 10.40.10.31:135 N/A E 00.0%
8202 10.40.15.87:48193 172.25.101.21:10050 00:23:7d:06:4e:7c TA 00.0%
O-ST: Origin State, T-ST: Terminal State
E: Established, S: Syn, A: Ack, F: Fin, R: Reset
s: sent, r: received, O: Options, P: Passthrough
Local IP:Port Remote IP:Port Peer ID O-ST T-ST ConnType
10.40.10.197:8080 172.25.101.54:1743 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.10.197:8080 172.25.101.54:1742 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.41.1.151:445 10.42.10.27:65440 N/A Sr Ss EXTERNAL CLIENT
10.41.1.151:139 10.42.10.27:65441 N/A Sr Ss EXTERNAL CLIENT
10.41.1.151:139 10.42.10.27:65442 N/A Sr Ss EXTERNAL CLIENT
10.40.10.197:8080 172.25.101.180:3939 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
172.25.101.21:139 172.1.0.6:4200 00:23:7d:06:4e:7c Sr Sso EXTERNAL CLIENT
10.40.100.25:443 172.25.200.250:2931400:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.10.31:135 172.25.101.41:2426 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.10.102:389 172.25.101.22:1992 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.25.25:8014 172.25.101.46:1862 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.15.87:10051 172.25.101.24:3123 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
172.25.101.21:445 10.42.10.198:4186 00:23:7d:06:4e:7c Sr Sso EXTERNAL CLIENT
10.41.1.54:135 10.40.10.50:1409 N/A Sr Ss EXTERNAL CLIENT
10.40.10.197:8080 172.25.101.72:2350 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
172.25.101.21:139 10.42.10.198:4215 00:23:7d:06:4e:7c Sr Sso EXTERNAL CLIENT
10.44.29.21:1026 172.25.101.21:3081 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.42.25.25:8014 172.25.101.47:1567 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
10.40.10.197:8080 172.25.101.47:1573 00:23:7d:06:4e:7c SAsO SAr EXTERNAL SERVER
Local IP:Port Remote IP:Port Peer ID ConnType
10.42.10.182:26755 172.25.101.24:139 N/A PT In Progress
172.25.101.22:10050 10.40.15.87:41566 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.40.10.31:1417 10.41.1.150:4569 N/A PT In Progress
10.42.10.27:65451 10.41.6.22:445 N/A PT In Progress
10.41.1.21:139 10.40.10.85:1153 N/A PT No Peer
172.30.101.116:4852 10.42.17.101:1494 N/A PT In Progress
10.41.1.22:1870 10.40.10.94:1433 N/A PT No Peer
10.40.10.197:8080 10.41.4.41:2006 N/A PT No Peer
10.40.10.197:8080 10.41.80.143:1863 N/A PT No Peer
10.41.22.35:139 10.41.80.143:1867 N/A PT No Peer
10.40.15.222:80 10.41.4.42:2138 N/A PT No Peer
172.25.101.68:3790 10.40.10.197:11801 N/A PT App Cfg
10.41.4.41:1998 10.40.10.197:8080 N/A PT No Peer
10.40.15.87:47493 10.41.11.21:10050 N/A PT No Peer
10.40.10.197:8080 10.41.7.142:2987 N/A PT In Progress
172.25.101.166:1530 192.168.206.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.40.17.102:1494 172.25.101.175:3951 N/A PT In Progress
10.40.15.87:53532 10.41.80.21:10050 N/A PT No Peer
172.25.101.21:139 10.40.10.85:4681 N/A PT In Progress
172.25.101.52:1186 10.40.10.31:1417 N/A PT In Progress
10.42.17.101:1494 172.30.101.116:4852 N/A PT In Progress
172.25.101.160:1663 192.168.207.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.41.4.142:3102 192.168.207.15:44718 N/A PT No Peer
172.30.101.151:445 10.40.10.85:1050 N/A PT No Peer
10.40.15.87:44478 10.41.6.21:10050 N/A PT No Peer
10.41.4.22:10050 10.40.15.87:51065 N/A PT No Peer
172.30.101.151:10050 10.40.15.87:49696 N/A PT No Peer
172.30.101.56:3079 10.40.15.139:5061 N/A PT In Progress
10.41.1.150:1189 192.168.206.15:44718 N/A PT No Peer
10.40.15.87:51135 10.41.80.22:10050 N/A PT No Peer
199.105.179.227:8292 172.25.101.164:8278 N/A PT In Progress
10.40.17.107:1494 172.25.101.69:1273 00:23:7d:06:4e:7c PT Asymmetric
10.41.22.35:445 10.41.80.143:1866 N/A PT No Peer
172.25.101.54:1741 10.40.10.197:8080 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.56:3407 10.42.25.25:8014 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.21:10050 10.40.15.87:46744 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.41.6.22:10050 10.40.15.87:60136 N/A PT No Peer
10.40.15.87:52517 10.41.80.22:10050 N/A PT No Peer
172.25.101.164:8277 199.105.179.20:8292 N/A PT In Progress
172.30.101.72:2856 10.40.15.139:5061 N/A PT In Progress
172.30.101.101:3369 10.40.10.197:8080 N/A PT No Peer
10.40.17.107:1494 172.25.101.59:4325 00:23:7d:06:4e:7c PT Asymmetric
10.40.15.87:50525 10.41.1.22:10050 N/A PT No Peer
10.41.4.41:2005 10.40.10.197:8080 N/A PT No Peer
10.40.10.31:1417 172.25.101.166:2831 N/A PT In Progress
172.25.101.166:2831 10.40.10.31:1417 N/A PT In Progress
172.25.101.69:2151 10.40.17.102:1494 00:23:7d:06:4e:7c PT Asymmetric
172.30.101.110:2858 192.168.207.16:44718 N/A PT No Peer
10.41.7.21:10050 10.40.15.87:58747 N/A PT No Peer
10.40.10.31:1417 10.41.1.62:4122 N/A PT In Progress
172.25.101.160:1662 192.168.206.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.41.7.21:10050 10.40.15.87:57793 N/A PT No Peer
192.168.207.15:44718 172.25.101.160:1663 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.197:8080 172.30.101.114:2173 N/A PT In Progress
10.40.15.87:52823 10.41.80.22:10050 N/A PT No Peer
10.41.1.62:4122 10.40.10.31:1417 N/A PT In Progress
10.40.15.203:80 10.41.7.143:3701 N/A PT In Progress
10.40.17.102:1494 172.25.101.69:2151 00:23:7d:06:4e:7c PT Asymmetric
10.41.4.42:2139 10.40.15.222:80 N/A PT No Peer
172.25.101.41:1212 192.168.206.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.31:1417 10.41.1.150:1933 N/A PT In Progress
10.41.6.22:4544 10.40.25.25:8014 N/A PT In Progress
10.41.6.21:445 10.42.10.198:4086 N/A PT In Progress
10.40.10.197:8080 10.41.80.143:1852 N/A PT No Peer
10.40.10.31:1417 10.41.1.52:3675 N/A PT In Progress
10.41.4.21:445 10.42.10.198:3924 N/A PT In Progress
10.40.15.203:80 10.41.1.62:1921 N/A PT In Progress
10.40.15.87:38582 10.41.7.22:10050 N/A PT No Peer
10.40.15.87:44797 10.41.6.21:10050 N/A PT No Peer
10.41.80.143:1864 10.40.10.197:8080 N/A PT No Peer
10.41.80.22:10050 10.40.15.87:52777 N/A PT No Peer
10.41.4.142:3101 192.168.206.15:44718 N/A PT No Peer
10.42.10.198:4086 10.41.6.21:445 N/A PT In Progress
10.40.15.87:50685 10.41.80.22:10050 N/A PT No Peer
10.40.10.31:1417 172.25.101.163:1769 N/A PT In Progress
10.40.10.31:1417 172.25.101.41:2181 N/A PT In Progress
192.168.207.16:44718 10.41.4.44:2728 N/A PT No Peer
172.25.101.41:2429 10.42.25.25:8014 00:23:7d:06:4e:7c PT Asymmetric
10.41.22.32:139 10.41.80.45:2646 N/A PT In Progress
10.40.10.31:1417 172.30.101.51:2626 N/A PT In Progress
10.40.10.197:11801 172.25.101.68:3790 N/A PT App Cfg
10.40.10.31:1417 10.41.1.51:2973 N/A PT In Progress
10.40.15.87:38245 10.41.7.22:10050 N/A PT No Peer
10.41.4.49:1243 10.42.17.103:1494 N/A PT In Progress
10.40.15.87:52777 10.41.80.22:10050 N/A PT No Peer
10.40.15.87:57793 10.41.7.21:10050 N/A PT No Peer
10.40.10.31:1417 172.30.101.53:2960 N/A PT In Progress
10.40.34.74:445 172.25.101.166:4566 N/A PT In Progress
10.41.6.22:10050 10.40.15.87:32814 N/A PT No Peer
10.40.10.197:8080 172.25.101.54:1741 00:23:7d:06:4e:7c PT Asymmetric
10.40.15.87:57550 10.41.7.21:10050 N/A PT No Peer
10.40.10.31:1417 172.25.101.52:1181 N/A PT In Progress
172.30.101.51:2626 10.40.10.31:1417 N/A PT In Progress
10.41.1.150:1118 10.40.15.139:5061 N/A PT In Progress
10.42.25.25:8014 172.25.101.41:2429 00:23:7d:06:4e:7c PT Asymmetric
10.42.17.103:1494 10.41.4.49:1243 N/A PT In Progress
172.25.101.61:1210 10.42.25.25:8014 00:23:7d:06:4e:7c PT Asymmetric
10.41.7.142:2987 10.40.10.197:8080 N/A PT In Progress
10.40.10.85:1163 10.41.80.21:139 N/A PT No Peer
192.168.206.16:44718 172.30.101.110:2857 N/A PT No Peer
172.25.101.52:1181 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1417 10.41.6.141:2816 N/A PT In Progress
10.41.1.52:4807 10.42.10.102:445 N/A PT In Progress
10.41.4.21:445 10.40.10.85:4666 N/A PT In Progress
10.41.7.143:3701 10.40.15.203:80 N/A PT In Progress
10.41.1.50:4545 10.40.17.107:1494 N/A PT No Peer
10.40.10.85:1153 10.41.1.21:139 N/A PT No Peer
10.41.80.143:1865 10.40.10.197:8080 N/A PT No Peer
10.41.4.21:445 10.40.10.85:1235 N/A PT No Peer
10.41.6.22:10050 10.40.15.87:59337 N/A PT No Peer
172.25.101.159:1189 192.168.207.15:44718 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.170:4801 10.40.10.31:1417 N/A PT In Progress
172.25.101.21:10050 10.40.15.87:45074 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.41.80.142:1823 10.41.22.35:445 N/A PT No Peer
10.42.10.198:3882 10.41.11.21:445 N/A PT In Progress
10.41.80.21:445 10.42.10.27:65455 N/A PT In Progress
10.41.6.48:4629 10.40.10.102:1026 N/A PT In Progress
10.42.10.198:4049 10.41.83.21:445 N/A PT In Progress
10.41.1.50:3762 10.40.15.139:5061 N/A PT In Progress
10.40.25.25:8014 10.41.4.48:1436 N/A PT In Progress
10.40.17.107:1494 172.30.101.69:2720 N/A PT In Progress
10.40.10.31:1417 172.25.101.49:2416 N/A PT In Progress
172.25.101.62:2027 10.40.15.139:5061 N/A PT In Progress
10.41.1.21:445 10.42.10.198:4061 N/A PT In Progress
172.30.101.51:3091 10.40.10.31:1417 N/A PT No Peer
10.41.1.21:10050 10.40.15.87:53725 N/A PT No Peer
10.40.15.87:42827 10.41.6.21:10050 N/A PT No Peer
10.41.4.49:1242 10.40.17.102:1494 N/A PT In Progress
10.40.10.31:1417 10.41.1.150:4570 N/A PT No Peer
10.42.10.27:65455 10.41.80.21:445 N/A PT In Progress
10.41.1.62:1757 10.40.10.175:445 N/A PT No Peer
10.40.10.197:8080 10.41.7.142:2988 N/A PT No Peer
10.41.6.21:10050 10.40.15.87:44280 N/A PT No Peer
10.40.10.197:8080 10.41.1.55:3872 N/A PT No Peer
10.41.80.21:10050 10.40.15.87:53532 N/A PT No Peer
10.41.11.22:10050 10.40.15.87:50717 N/A PT No Peer
10.40.15.87:52520 10.41.1.21:10050 N/A PT No Peer
10.40.10.197:8080 10.41.1.55:3898 N/A PT No Peer
10.41.1.62:4085 192.168.201.153:443 N/A PT In Progress
10.40.15.87:51315 172.25.101.24:10050 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
172.25.101.167:4018 10.40.10.31:1417 N/A PT In Progress
10.40.15.87:59367 10.41.6.22:10050 N/A PT No Peer
192.168.206.15:44718 172.25.101.166:1530 00:23:7d:06:4e:7c PT Asymmetric
10.40.25.25:8014 172.25.101.180:3908 N/A PT In Progress
172.25.101.59:4325 10.40.17.107:1494 00:23:7d:06:4e:7c PT Asymmetric
10.41.80.21:445 10.40.10.85:1156 N/A PT No Peer
172.30.101.151:445 10.42.10.198:3217 N/A PT In Progress
10.41.1.52:3675 10.40.10.31:1417 N/A PT In Progress
10.42.10.27:65460 172.25.101.22:445 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.40.25.25:8014 10.41.6.22:4544 N/A PT In Progress
172.25.101.54:1739 10.40.10.197:8080 00:23:7d:06:4e:7c PT Asymmetric
10.41.6.22:10050 10.40.15.87:59367 N/A PT No Peer
172.30.101.151:10050 10.40.15.87:49145 N/A PT No Peer
10.40.15.139:5061 172.25.101.163:1056 N/A PT In Progress
172.30.101.53:3128 10.40.10.31:1417 N/A PT No Peer
10.41.80.22:10050 10.40.15.87:50660 N/A PT No Peer
10.41.4.49:2010 10.41.22.35:139 N/A PT In Progress
172.25.101.24:10050 10.40.15.87:51107 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
192.168.206.16:44718 172.25.101.69:1412 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.21:3118 10.44.9.21:1025 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.197:8080 10.41.80.143:1870 N/A PT No Peer
10.40.15.87:10051 10.41.6.21:3959 N/A PT No Peer
10.40.10.102:1026 172.25.101.21:3004 N/A PT In Progress
10.41.1.62:4084 192.168.201.153:443 N/A PT In Progress
10.40.10.197:8080 172.25.101.47:1570 00:23:7d:06:4e:7c PT Asymmetric
10.40.15.87:53725 10.41.1.21:10050 N/A PT No Peer
10.40.10.85:1236 10.41.4.21:139 N/A PT No Peer
10.40.15.87:37488 10.41.7.22:10050 N/A PT No Peer
10.40.10.31:1417 10.41.4.142:4230 N/A PT In Progress
10.40.15.139:5061 10.41.1.57:4427 N/A PT In Progress
10.41.11.22:10050 10.40.15.87:49203 N/A PT No Peer
10.40.15.87:46735 10.41.11.21:10050 N/A PT No Peer
10.41.80.143:1870 10.40.10.197:8080 N/A PT No Peer
10.40.10.197:8080 172.30.101.53:3127 N/A PT No Peer
172.30.101.69:4050 10.40.10.31:1417 N/A PT In Progress
10.41.1.42:3541 192.168.201.153:443 N/A PT In Progress
10.41.7.146:2596 10.40.10.31:1417 N/A PT In Progress
172.30.101.101:3368 10.40.10.197:8080 N/A PT No Peer
10.42.10.198:3217 172.30.101.151:445 N/A PT In Progress
10.40.10.85:1068 10.41.6.21:445 N/A PT In Progress
10.40.15.87:54352 172.30.101.152:10050 N/A PT No Peer
10.40.15.139:5061 10.41.4.41:3772 N/A PT In Progress
10.42.10.197:8080 172.30.101.69:4074 N/A PT No Peer
172.25.101.164:2829 192.168.206.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.41.1.22:10050 10.40.15.87:51195 N/A PT No Peer
10.42.10.102:445 10.41.1.52:4807 N/A PT In Progress
10.40.10.103:1026 10.41.1.42:3850 N/A PT In Progress
10.40.10.103:1026 10.41.1.62:4281 N/A PT In Progress
172.25.101.156:4804 10.40.15.139:5061 N/A PT In Progress
10.40.10.85:1156 10.41.80.21:445 N/A PT No Peer
172.25.101.166:1531 192.168.207.15:44718 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.31:1417 172.30.101.116:1322 N/A PT In Progress
192.168.201.153:443 10.41.1.62:4084 N/A PT In Progress
172.25.101.42:1104 10.40.10.102:1026 N/A PT In Progress
10.40.17.107:1494 10.41.1.50:4545 N/A PT No Peer
10.40.10.85:1050 172.30.101.151:445 N/A PT No Peer
10.40.15.87:50601 10.41.11.22:10050 N/A PT No Peer
10.41.1.60:4515 10.40.10.31:1382 N/A PT In Progress
10.40.15.87:50717 10.41.11.22:10050 N/A PT No Peer
172.30.101.71:1303 192.168.206.15:44718 N/A PT No Peer
10.41.80.43:4121 10.42.25.25:8014 N/A PT In Progress
10.40.10.31:1417 10.41.7.44:1512 N/A PT In Progress
172.30.101.116:1322 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1382 10.41.1.42:3554 N/A PT In Progress
10.40.15.87:45429 172.25.101.21:10050 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.40.10.85:4666 10.41.4.21:445 N/A PT In Progress
10.42.25.25:8014 172.25.101.56:3407 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.197:8080 10.41.80.143:1871 N/A PT No Peer
10.40.10.197:8080 10.41.4.41:1998 N/A PT No Peer
172.25.101.49:2416 10.40.10.31:1417 N/A PT In Progress
10.40.15.222:80 10.41.4.42:2139 N/A PT No Peer
10.41.7.44:1512 10.40.10.31:1417 N/A PT In Progress
10.40.15.87:49145 172.30.101.151:10050 N/A PT No Peer
172.25.101.156:3452 10.40.10.197:8080 N/A PT In Progress
10.41.1.51:2973 10.40.10.31:1417 N/A PT In Progress
10.40.15.87:50660 10.41.80.22:10050 N/A PT No Peer
172.25.101.52:1189 10.40.15.156:80 00:23:7d:06:4e:7c PT Asymmetric
172.30.101.53:3129 10.40.10.197:8080 N/A PT No Peer
172.25.101.62:3076 10.40.10.31:1417 N/A PT In Progress
10.40.25.25:8014 10.41.7.143:3655 N/A PT In Progress
10.41.83.21:139 10.40.10.85:1223 N/A PT No Peer
10.40.15.87:60387 10.41.6.22:10050 N/A PT No Peer
10.42.10.198:3954 10.41.7.21:445 N/A PT In Progress
172.25.101.41:2181 10.40.10.31:1417 N/A PT In Progress
10.41.1.142:2784 10.40.25.25:8014 N/A PT No Peer
10.44.62.21:2644 172.25.101.24:139 N/A PT In Progress
172.30.101.72:4720 10.40.25.25:8014 N/A PT In Progress
10.41.1.62:1921 10.40.15.203:80 N/A PT In Progress
172.25.101.168:1071 10.40.15.139:5061 N/A PT In Progress
10.41.80.143:1849 10.40.10.197:8080 N/A PT No Peer
172.30.101.151:10050 10.40.15.87:48082 N/A PT No Peer
10.40.10.31:1417 172.30.101.78:2812 N/A PT In Progress
10.40.10.31:1417 10.41.6.48:4329 N/A PT In Progress
172.25.101.151:1214 192.168.206.15:44718 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.47:1570 10.40.10.197:8080 00:23:7d:06:4e:7c PT Asymmetric
10.40.17.107:1494 172.25.101.47:4625 00:23:7d:06:4e:7c PT Asymmetric
10.41.80.21:10050 10.40.15.87:53558 N/A PT No Peer
10.40.15.87:51065 10.41.4.22:10050 N/A PT No Peer
10.40.25.25:8014 10.41.1.142:2784 N/A PT No Peer
10.41.7.142:2989 10.40.10.197:8080 N/A PT No Peer
10.40.10.197:8080 172.30.101.53:3129 N/A PT No Peer
10.40.15.87:41566 172.25.101.22:10050 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.41.80.22:10050 10.40.15.87:51135 N/A PT No Peer
10.41.1.22:10050 10.40.15.87:50525 N/A PT No Peer
10.40.15.87:60136 10.41.6.22:10050 N/A PT No Peer
10.41.7.142:2316 10.40.17.102:1494 N/A PT No Peer
10.40.10.31:1417 10.41.7.146:2596 N/A PT In Progress
10.40.10.197:8080 10.41.4.41:2005 N/A PT No Peer
172.30.101.53:2960 10.40.10.31:1417 N/A PT In Progress
10.40.10.31:1417 172.30.101.51:3091 N/A PT No Peer
10.42.17.101:1494 10.41.1.51:2132 N/A PT No Peer
10.40.10.197:8080 172.25.101.54:1739 00:23:7d:06:4e:7c PT Asymmetric
10.41.4.41:3772 10.40.15.139:5061 N/A PT In Progress
10.41.7.21:10050 10.40.15.87:57550 N/A PT No Peer
10.41.6.141:2816 10.40.10.31:1417 N/A PT In Progress
10.41.7.21:10050 10.40.15.87:57780 N/A PT No Peer
10.40.10.102:1026 172.25.101.42:1104 N/A PT In Progress
10.40.10.197:8080 172.30.101.101:3369 N/A PT No Peer
192.168.207.15:44718 172.25.101.151:1215 00:23:7d:06:4e:7c PT Asymmetric
10.41.80.21:10050 10.40.15.87:53311 N/A PT No Peer
10.42.10.198:3922 10.41.80.21:139 N/A PT In Progress
192.168.206.15:44718 172.25.101.159:1187 00:23:7d:06:4e:7c PT Asymmetric
10.40.10.31:1417 10.41.1.143:1276 N/A PT In Progress
10.41.1.55:3872 10.40.10.197:8080 N/A PT No Peer
192.168.201.153:443 10.41.1.62:4085 N/A PT In Progress
10.42.10.197:3926 172.30.101.152:2967 N/A PT No Peer
10.41.1.145:2676 10.40.17.107:1494 N/A PT In Progress
172.30.101.114:2173 10.40.10.197:8080 N/A PT In Progress
172.25.101.54:1738 10.40.10.197:8080 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.69:1413 192.168.207.16:44718 00:23:7d:06:4e:7c PT Asymmetric
172.25.101.21:10050 10.40.15.87:45429 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.41.1.142:2785 10.40.25.25:8014 N/A PT No Peer
10.40.15.139:5061 10.41.6.150:1581 N/A PT In Progress
172.25.101.21:445 10.40.32.128:3640 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.41.7.21:10050 10.40.15.87:60329 N/A PT No Peer
10.40.15.87:52288 172.30.101.152:10050 N/A PT No Peer
10.41.11.21:10050 10.40.15.87:47493 N/A PT No Peer
10.41.80.22:10050 10.40.15.87:50685 N/A PT No Peer
10.40.15.139:5061 172.25.101.168:1071 N/A PT In Progress
172.30.101.152:10050 10.40.15.87:52288 N/A PT No Peer
10.41.83.21:445 10.42.10.198:4049 N/A PT In Progress
10.41.80.143:1853 10.40.10.197:8080 N/A PT No Peer
10.40.15.87:51195 10.41.1.22:10050 N/A PT No Peer
10.41.6.21:10050 10.40.15.87:44478 N/A PT No Peer
10.41.6.21:10050 10.40.15.87:42675 N/A PT No Peer
192.168.207.15:44718 172.25.101.166:1531 00:23:7d:06:4e:7c PT Asymmetric
10.41.6.48:4330 10.40.10.31:1417 N/A PT In Progress
10.41.1.150:4569 10.40.10.31:1417 N/A PT In Progress
10.41.7.42:3974 10.40.15.139:5061 N/A PT In Progress
10.40.15.87:59337 10.41.6.22:10050 N/A PT No Peer
10.40.10.197:8080 10.41.80.143:1853 N/A PT No Peer
10.40.10.102:1026 10.41.6.48:4629 N/A PT In Progress
10.40.10.197:8080 172.25.101.46:1860 N/A PT In Progress
172.25.101.69:1412 192.168.206.16:44718 00:23:7d:06:4e:7c PT Asymmetric
10.41.6.22:10050 10.40.15.87:60815 N/A PT No Peer
10.41.4.44:2728 192.168.207.16:44718 N/A PT No Peer
10.40.10.197:8080 10.41.80.143:1862 N/A PT No Peer
192.168.206.15:44718 172.25.101.164:2829 00:23:7d:06:4e:7c PT Asymmetric
10.41.7.22:10050 10.40.15.87:38245 N/A PT No Peer
10.40.10.102:1026 172.25.101.21:3120 00:23:7d:06:4e:7c PT Asymmetric
10.42.10.198:4061 10.41.1.21:445 N/A PT In Progress
10.41.1.60:2750 10.40.10.31:1417 N/A PT In Progress
10.41.4.47:4733 10.40.17.107:1494 N/A PT No Peer
10.41.80.45:2646 10.41.22.32:139 N/A PT In Progress
192.168.201.153:443 10.41.1.42:3541 N/A PT In Progress
172.25.101.21:3004 10.40.10.102:1026 N/A PT In Progress
10.40.15.87:47815 172.30.101.151:10050 N/A PT No Peer
10.41.11.21:445 10.40.10.85:4913 N/A PT In Progress
172.30.101.101:3367 10.40.10.197:8080 N/A PT No Peer
10.40.15.87:47834 10.41.4.21:10050 N/A PT No Peer
10.40.10.85:1235 10.41.4.21:445 N/A PT No Peer
10.41.4.21:10050 10.40.15.87:49525 N/A PT No Peer
10.41.7.142:2988 10.40.10.197:8080 N/A PT No Peer
10.40.15.87:49725 10.41.11.22:10050 N/A PT No Peer
10.40.15.156:80 172.25.101.52:1188 00:23:7d:06:4e:7c PT Asymmetric
10.44.9.21:1025 172.25.101.21:2999 N/A PT In Progress
172.30.101.69:4074 10.42.10.197:8080 N/A PT No Peer
10.41.80.22:10050 10.40.15.87:52823 N/A PT No Peer
192.168.206.15:44718 10.41.4.142:3101 N/A PT No Peer
10.41.1.50:4540 10.42.17.101:1494 N/A PT No Peer
10.41.1.143:1276 10.40.10.31:1417 N/A PT In Progress
10.41.80.143:1867 10.41.22.35:139 N/A PT No Peer
10.40.15.87:48709 10.41.4.22:10050 N/A PT No Peer
10.40.15.87:52295 10.41.80.21:10050 N/A PT No Peer
10.41.80.22:10050 10.40.15.87:50424 N/A PT No Peer
10.40.10.31:1417 172.25.101.170:4801 N/A PT In Progress
10.40.10.31:1382 10.41.1.62:4072 N/A PT In Progress
172.25.101.42:2643 10.40.10.49:443 00:23:7d:06:4e:7c PT Asymmetric
10.41.6.21:10050 10.40.15.87:42827 N/A PT No Peer
10.41.1.42:3554 10.40.10.31:1382 N/A PT In Progress
10.41.1.42:3850 10.40.10.103:1026 N/A PT In Progress
10.40.32.128:3641 172.25.101.21:139 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.40.15.87:46474 10.41.11.21:10050 N/A PT No Peer
10.40.10.31:1417 10.41.1.60:2750 N/A PT In Progress
10.41.22.35:139 10.41.80.143:1839 N/A PT No Peer
10.40.15.139:5061 10.41.7.42:3974 N/A PT In Progress
172.25.101.47:1569 10.40.10.197:8080 00:23:7d:06:4e:7c PT Asymmetric
10.41.4.41:1999 10.40.10.197:8080 N/A PT No Peer
10.40.10.85:4681 172.25.101.21:139 N/A PT In Progress
10.41.80.143:1852 10.40.10.197:8080 N/A PT No Peer
172.30.101.101:1451 10.40.15.139:5061 N/A PT In Progress
10.40.25.25:8014 10.41.1.142:2761 N/A PT In Progress
10.41.1.62:4072 10.40.10.31:1382 N/A PT In Progress
10.40.17.102:1494 10.41.4.49:1242 N/A PT In Progress
10.41.11.22:10050 10.40.15.87:49725 N/A PT No Peer
10.40.10.175:445 10.41.1.62:1757 N/A PT No Peer
10.41.80.21:10050 10.40.15.87:52295 N/A PT No Peer
172.25.101.22:139 10.42.10.27:65461 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
10.40.10.31:1417 172.25.101.162:2647 00:23:7d:06:4e:7c PT Asymmetric
10.40.15.87:45074 172.25.101.21:10050 00:23:7d:06:4e:7c PT Peer AOIM Sync in Pr
172.25.101.163:1056 10.40.15.139:5061 N/A PT In Progress
10.41.1.21:445 10.40.10.85:1146 N/A PT No Peer
172.25.101.180:3908 10.40.25.25:8014 N/A PT In Progress
10.40.10.31:1417 172.30.101.116:1318 N/A PT In Progress
10.40.10.197:8080 172.25.101.156:3452 N/A PT In Progress
10.41.4.22:10050 10.40.15.87:48709 N/A PT No Peer
10.41.80.143:1861 10.40.10.197:8080 N/A PT No Peer
10.42.10.67:5242 10.41.1.52:4809 N/A PT In Progress
172.25.101.175:3951 10.40.17.102:1494 N/A PT In Progress
172.30.101.152:2967 10.42.10.197:3926 N/A PT No Peer
10.41.6.22:445 10.42.10.27:65451 N/A PT In Progress
172.30.101.116:1318 10.40.10.31:1417 N/A PT -
Hi team,
I am experiencing couple of issues with WAAS monitoring using NetQoS product. Here is what I have configured so far:
IP of the SuperAgent management console on the WAEs
enabled flow monitor on the WAEs
all WAEs appeared automatically under management console and connected to appropriate aggregator
opened icmp and 7878 port on the FW
The output of "show statistics flow monitor tcpstat-v1" command tells me:
for the Host connection (to management console)
connection state: Waiting to poll
connection failiures: never
for the Collector connection (to aggregator)
connection state: connected
connection failures: never
for the collection statisticsall zeros
I am interesting in unoptimized traffic stats on the superagent so I disabled all acceleration features (on the CM: Configure > Acceleration > Enabled Features > unchecked all).
So my questions are:
is "Waiting to poll" status for the Host connection OK ??
as I disabled all optimization features I see only passthrough traffic on the WAEs which is the way it should be. But will be this traffic sent to the aggregator (so far there are no collections from the aggregator)??
Many thanks!
Regards,
StanStan,
Unfortunately the Cisco WAE only exports optimized traffic through to the Aggregator. So you would need optimized data to get it to export. You would need a regular SuperAgent collector to see the unoptimized data through a SPAN/tap feed.
Other things to check on the WAE, once you optimize the traffic is to ensure that the host filters are the same as the WCCP redirect traffic that the WAE is seeing. You can see this data in a few places.
To address your first question, the "waiting to poll" is totally okay. The communication to the management console is asynchronous. So it's not continually updating.
If I can answer other questions let me know. I'm happy to help.
Maybe you are looking for
-
hy, is it possible to create a sound in a handy java game(J2ME) mfg pg
-
Unable to setup Yahoo account in Mail.app.
Everything worked ok till a couple of days ago and now keep getting error messages saying unable to connect to server. This is the latest message. There may be a problem with the mail server or network. Verify the settings for account "yahoo.com.au"
-
Hi, I have purchsed photoshop and currently have in design on trial. Our company has a 40 page brochure and we want to place this on our website. I have noticed several other websites that allow you to flip the page with the flip effect, just looking
-
Hey guys, I know some other people have been having this problem and wonder if anyone's found a solution. It seems the pen tool is trying to "intelligently" decide whether I'd like to start a new mask, or add a vertex, and I'd rather it didn't. Giv
-
Tried upgrading my iPod Touch 5G today to iOS 7.1.1 but didn't realize that I needed 2.1GB worth of needed internal memory for this update. I only had about 800MB of unused memory in my iPod 32GB Touch 5G before starting the iOS 7.1.1 download. So no