WAAS and PIX Firewalls
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
Similar Messages
-
WAAS / Active-Standby PIX Firewalls
Hi -
So we are exploring ways to implement WAAS in our network and our connection into our WAN contains two PIX firewalls in Active/Standby mode with a connection to a single 3560 switch.
I understand WAAS can do failover when connected in a daisychain fashion, but what is we put a WAAS device on each link to the 3560, that way if I PIX fails we can have failover. Would this be feasible? Anyone ever tested something like this?
Thanks!Hi. We have a similar diagram.
We have a stack of switches when connected the internal LAN and DMZ, two ASA5510 in Active/Standby mode and a 2811 router.
We want to put the WAE512 in the inside side of Firewalls managing the traffic of interlan LAN and DMZ, because as we finish the IPSec Tunnels on ASAs we think the WAE can't be located outside the firewalls.
How can we do this??
Our WAE has the Inline network adapter. -
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 -
Load balancing of PIX firewalls with multiple DMZs
I need a suggestion about how to balance the traffic through two PIX firewalls, with 4 interfaces (IN,OUT,DMZ1,DMZ2)
In all the documentation related to the subject, I see always the firewalls with only two interfaces:
http://www.cisco.com/warp/customer/117/fw_load_balancing.html
http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/advcfggd/firewall.htm
What if I need to balance on more than 2 interfaces?
Do I have to add more content switches, one for each interface ?
Or could I use VLANs inside the same content switches, and assign the ports to DMZs appropriately ?
Thank you in advance for any help.We just had some internal discussions about that at my work, and the suggestion from a local cisco specialist was, if you want to levarage load balacing over multiple DMZ's, then you get the CSS blades for the 65xx's. Right now we have mulriple CSS and LD failover pairs (One pair for each DMZ) and it is starting to become expensive, while we aren't really utilizing the full capacity of them. If you get the Blades, they have Gigabit traces to the backplane of the switch, and you can use them for as many poers as you have on the 6500.
Then again, it depends on if physical security is essential to you, and you are concerned with L2 attacks (VLAN Hopping, etc) There are tradeoffs and benefits when using a consildated infrastructure. -
Problem with VPN by ASA 5505 and PIX 501
Hi
I have this scenario: Firewall ASA 5505, Firewall Pix 501 (with CatOS 6.3(5) ).
I have configured this appliance for Easy VPN (server is ASA) and PIX, and remote Access with Cisco client vpn (for internal lan ASA).
When i configure the ASA i have this problem, when i configure nat for easy vpn.
This is my nat configuration:
nat (inside) 0 access-list 100
nat (inside) 1 192.168.1.0 255.255.255.0
nat (inside) 1 0.0.0.0 0.0.0.0
nat (inside) 0 0.0.0.0 0.0.0.0 outside
when i put this command:
nat (inside) 0 access-list no-nat
this command is necessary for configuration of easy vpn, but the previous nat:
nat (inside) 0 access-list 100
is replace with the latest command.To identify addresses on one interface that are translated to mapped addresses on another interface, use the nat command in global configuration mode. This command configures dynamic NAT or PAT, where an address is translated to one of a pool of mapped addresses. To remove the nat command, use the no form of this command.
For regular dynamic NAT:
nat (real_ifc) nat_id real_ip [mask [dns] [outside] [udp udp_max_conns] [norandomseq]]
no nat (real_ifc) nat_id real_ip [mask [dns] [outside] [udp udp_max_conns] [norandomseq]]
For policy dynamic NAT and NAT exemption:
nat (real_ifc) nat_id access-list access_list_name [dns] [outside] [udp udp_max_conns] [norandomseq]
no nat (real_ifc) nat_id access-list access_list_name [dns] [outside] [udp udp_max_conns] [norandomseq] -
Photoshop Elements 8 Mac - All fonts look jagged and pixely
HI,
I have the problem that all fonts look jagged and pixely when using Photoshop Elements 8 on Mac OS X 10.6.3. I am using the right image size 300dpi and so forth. Interestingly enough this only happens in Photoshop. If I repeat the procedure in Pixelmator everything is normal.
I would really appreciate any suggestions.Are you simplifying the font layer and then making it larger? Can you explain exactly, step by step, what you're doing?
-
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 -
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 -
Recommanded reboot of cisco routers and pix
is it recommanded to reboot all networking equipents which are on for 24 hours once in six month time ?
is there any documentation related to this please let us kow
regards
pushpakNope. You can have the devices on for years if you are not seeing any issues and have no need for an IOS upgrade. That being said you may not want to go for years without doing any sort of IOS upgrade. Keep a check on security advisories. I personally have seen 6500's and PIX's with over 1000 days of uptime. These are not your average MS Server.
-
I have a WAAS deployment where there is a reasonable amount of traffic that goes through a firewall. Logically speaking the traffic goes from client to waas to remote waas then through a firewall to the server. I believe that the WAAS devices use IP options to communicate between each other.
My question is if the firewall (a Cisco ASA) blocks IP options will this prevent WAAS from working in my topology? I know there is an inspect command to allow WAAS to work through a firewall, but there is a memory leak in that command under 7.2(3) so I would like to avoid using it if I can.Peter,
WAAS uses TCP option 33, not IP options. By default, ASA will remove unknown options from TCP packets. If the firewall is not sitting in between the WAEs (i.e. in the optimized path), then there shouldn't be any problem with the firewall scrubbing the options.
Regards,
Zach -
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
MoamenHey 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 -
Problem with VPN Client and PIX 7.0(5)
Hi, i have a problem configuring my pix 525 7.0(5) as a remote vpn server. I already configure the pix
sollowing this instructions (http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008060f25c.shtml)
and i can establish a vpn using CISCO VPN Client; but i can't reach any resource from my inside network or any network define in the PIX.
I think that could be a missing nat or an acl; but i have do a lot of research but i can figure out the solution.
This is the configuration i apply
access-list cryptomap-scada extended permit ip any 172.10.0.0 255.255.255.0
access-list acl-vpn-sap-remoto extended permit ip any 172.16.42.64 255.255.255.224
access-list acl-vpn-sap-remoto extended permit icmp any 172.16.42.64 255.255.255.224
access-list acl-vpn-sap-remoto extended permit ip any any
access-list acl-vpn-sap-remoto extended permit icmp any any
ip local pool pool_vpn_sap 172.*.*.1-172.10.0.254 mask 255.255.255.0
nat (inside) 0 access-list cryptomap-scada
group-policy VPN_SAP_PED internal
group-policy VPN_SAP_PED attributes
vpn-filter value acl-vpn-sap-remoto
vpn-tunnel-protocol IPSec
username vpnuser password **** encrypted
username vpnuser attributes
vpn-group-policy VPN_SAP_PED
crypto ipsec transform-set vpn-cliente-remoto esp-3des esp-md5-hmac
crypto dynamic-map vpn-remoto-dymap 7 set transform-set vpn-cliente-remoto
crypto dynamic-map vpn-remoto-dymap 7 set reverse-route
crypto map siemens-scada-map 7 ipsec-isakmp dynamic vpn-remoto-dymap
isakmp policy 7 authentication pre-share
isakmp policy 7 encryption 3des
isakmp policy 7 hash sha
isakmp policy 7 group 2
isakmp policy 7 lifetime 43200
tunnel-group VPN_SAP_PED type ipsec-ra
tunnel-group VPN_SAP_PED general-attributes
address-pool pool_vpn_sap
default-group-policy VPN_SAP_PED
tunnel-group VPN_SAP_PED ipsec-attributes
pre-shared-key clavevpnsap
Thanks in AdvancedHi, thanks for you response, if i remove the acl form de vpn filter, i get the same problem (i can't reach any host). This is the output from the command that you ask for.
PIX-Principal(config)# show running-config nat
nat (inside) 0 access-list cryptomap-scada
nat (inside) 9 JOsorioPC 255.255.255.255
nat (inside) 9 GColinaPC 255.255.255.255
nat (inside) 9 AlfonsoPC 255.255.255.255
nat (inside) 9 AngelPC 255.255.255.255
nat (inside) 9 JerryPC 255.255.255.255
nat (inside) 9 EstebanPC 255.255.255.255
nat (inside) 9 GiancarloPC 255.255.255.255
nat (inside) 9 WilliamsPC 255.255.255.255
nat (inside) 9 PerniaPC 255.255.255.255
nat (inside) 9 ElvisDomPC 255.255.255.255
nat (inside) 8 LBermudezPC 255.255.255.255
nat (inside) 9 HelpDeskPC 255.255.255.255
nat (inside) 9 OscarOPC 255.255.255.255
nat (inside) 9 AnaPC 255.255.255.255
nat (inside) 9 RobertoPC 255.255.255.255
nat (inside) 9 MarthaPC 255.255.255.255
nat (inside) 9 NOCPc5-I 255.255.255.255
nat (inside) 9 NOCPc6-I 255.255.255.255
nat (inside) 9 CiraPC 255.255.255.255
nat (inside) 9 JaimePC 255.255.255.255
nat (inside) 9 EugemarPC 255.255.255.255
nat (inside) 9 JosePC 255.255.255.255
nat (inside) 9 RixioPC 255.255.255.255
nat (inside) 9 DaniellePC 255.255.255.255
nat (inside) 9 NorimarPC 255.255.255.255
nat (inside) 9 NNavaPC 255.255.255.255
nat (inside) 8 ManriquePC 255.255.255.255
nat (inside) 8 MarcialPC 255.255.255.255
nat (inside) 8 JAlbornozPC 255.255.255.255
nat (inside) 9 GUrdanetaPC 255.255.255.255
nat (inside) 9 RVegaPC 255.255.255.255
nat (inside) 9 LLabarcaPC 255.255.255.255
nat (inside) 9 Torondoy-I 255.255.255.255
nat (inside) 9 Escuque-I 255.255.255.255
nat (inside) 9 Turbio-I 255.255.255.255
nat (inside) 9 JoseMora 255.255.255.255
nat (inside) 8 San-Juan-I 255.255.255.255
nat (inside) 8 Router7507 255.255.255.255
nat (inside) 8 NOCPc4-I 255.255.255.255
nat (InterfaceSAN) 8 MonitorHITACHI-I 255.255.255.255
Maybe you are looking for
-
I like to close open email messages by double clicking the small envelope in the upper left hand corner just above the "File" tab. A single click brings up options for restore, move, size, minimize, maximize, close. Close is the default option on a d
-
Album art, separate drive, can't update
I have searched the forums and have found many old posts concerning some of my issues. Nothing current, as far as I can tell I am running (connected, not wireless) Front Row from my iBook in my den to my amplifier. It is streaming music from my Mac P
-
Hi guru's, I am implementing SAP LSO recently. I want to use the Print Workbench(Collections) to create an email with a Attachment(NOT PDF Format). How can I do that? for example: When learner book a course, system will send a email(with attachment i
-
How To call a Tcode From a Program and returning back ?
Dear All, I have a requirement, i have to show all the open orders as in the the tcode va05 and return back to the my program. so how to display the tcode and getting back to my program. please help?
-
Buy Back Purchase from Sales order
Hi, I have this scenario and need advise how should I go ahead. end customer buys some material (Jewelry) from a particular sales unit. A standard sales order cycle is run for this. after sometime, the same customer comes and sells the same material