Wan Optimization Support
Technical => Troubleshooting => : Anil Kumar H July 16, 2014, 03:09:03 PM
-
Hi,
is it necessary to have both Wan0 & LAN0 to be of same speed ?
-
It is not a requirement, e.g. it is possible to have 1 Gbps lan and 100 Mbps wan.
-
Today I connected A.Core-B.Core but after some download network failed at B end. I did port swap but still fails after sometime.. don't know what is wrong
PC---coreswitch---WanCore----100Mbps P2P link---WanCore---coreswitch---PC
Both ends with latest 1.2.2
-
...after some download network failed at B end
To help, some basic info is needed e.g:
What exactly happened here?
Did icmp pings drop completely?
Was the web interface up?
What did the logs say?
How did you fix it?
Is this running as a VM/ which hypervisor? (since you mentioned in another thread that you can't get the HDD image to work)
What are the hardware specs?
How much disk space is available?
Are any extra sites configured in MultiSite?
How are the tests done (tools/protocols/files)?
-
Hi anil
As admin said, you need to give more info to people to help
since we do not have your visibility of network.
can you produce more ping or port status from switch when you lost the connection.
Ram
-
What exactly happened here?
this was the setup, no routers at both end, isp was directly terminated on Wan0
PC---coreswitch---WanCore ( A )----100Mbps P2P link---WanCore ( B )---coreswitch---PC
Did icmp pings drop completely?
without data transfer yes network is up, when I started data transfer after some MB downloads, CPU utilzation went High on B End & network went down. in graph I see only 35% utilized, but when we saw physically on web interface during the issue it was to the peak.
Was the web interface up?
Machine was up, but not webinterface, nor no network. we had to hard reboot to make machine up.
What did the logs say?
A End:
hu Jul 10 16:34:15 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 10 16:34:15 UTC 2014 : Routine : Check Configs
Thu Jul 10 16:34:15 UTC 2014 : Routine : Updating Configuration
Thu Jul 10 16:34:15 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
DropBroadcasts: dropped a packet
Queue@58 :: Queue: overflow
Peer detected on lan0: 52
Peer detected on lan0: 56
Peer detected on lan0: 52
Peer detected on lan0: 56
Peer detected on lan0: 52
Peer detected on lan0: 56
B End:
Wed Jul 16 20:08:54 UTC 2014 : Routine : Initializing Startup Scripts
Wed Jul 16 20:08:54 UTC 2014 : Routine : Set Interface Roles
Wed Jul 16 20:08:54 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Wed Jul 16 20:08:55 UTC 2014 : Routine : Check Configs
Wed Jul 16 20:08:55 UTC 2014 : Routine : Updating Configuration
Wed Jul 16 20:08:55 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
Queue@57 :: Queue: overflow
Peer detected on lan0: 64
Peer detected on lan0: 64
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
How did you fix it?
We had to hard reboot B end machine.
Is this running as a VM/ which hypervisor? (since you mentioned in another thread that you can't get the HDD image to work)
Its Physical machine
What are the hardware specs?
A End:
Core i5
8GB RAM
500GB SATA HDD 7200RPM
B End:
Core i3
4GB RAM
320GB HDD 5400RPM
How much disk space is available?
100% free other than wanos folders, files & OS
Are any extra sites configured in MultiSite?
no
How are the tests done (tools/protocols/files)?
Started with FTP to test
Utilization during testing:
A End:
CPU:5%
Memory: 240MB
Disk I/O: 35%
Disk Usage: 35MB
B End:
CPU: 35%
Memory: 160MB
Disk I/O: 80%
Disk Usage:34MB
Later: at B End we configured similar conf machine which is of A end, but still it fails in Core--Core, Core--Edge, Edge--Edge.
-
For starters, lets fix the lan0 and wan0 cabling. The 'Peer detected on lan0' on both ends means both are reversed.
-
hi,
you mean to say, Change the Switch Interface Port Roles ? or physical cabling ?
-
Hi,
On A end, I did reverse cabling. B also did same
A End results
Thu Jul 17 14:57:27 UTC 2014 : Lan0-Wan0 Interface Port Roles Switched. Restarting Wanos Service
Thu Jul 17 14:57:28 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 17 14:57:28 UTC 2014 : Routine : Set Interface Roles
Thu Jul 17 14:57:28 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Thu Jul 17 14:57:28 UTC 2014 : Routine : Check Configs
Thu Jul 17 14:57:28 UTC 2014 : Routine : Updating Configuration
Thu Jul 17 14:57:28 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
B End,
Did cable interchange, port swap & still I see below error, network breaks.
Thu Jul 17 15:02:53 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 17 15:02:53 UTC 2014 : Routine : Set Interface Roles
Thu Jul 17 15:02:53 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Thu Jul 17 15:02:54 UTC 2014 : Routine : Check Configs
Thu Jul 17 15:02:54 UTC 2014 : Routine : Updating Configuration
Thu Jul 17 15:02:54 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
Queue@57 :: Queue: overflow
Peer detected on lan0: 56
Peer detected on lan0: 64
Peer detected on lan0: 52
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
Peer detected on lan0: 56
-
B is still detecting the peer on lan0, which it should not. There is some reason for this. Are lan0/wan0 perhaps connected to the same switch or vlan?
-
one more thing observed.
earlier I was downloading from B to A, this use to make B network go fail, im doing viceversa now, still B is up for time being. Need to figure out with your query on switch or vlan
vlan: 10.9.232.0/29
A--10.9.231.1 & 2 ( Vlan number 42 )
B--10.9.232.3 & 4 ( Vlan number 10 )
-
I suspect that it is possible that both lan0 and wan0 might be in the same vlan and hence the 'peer detected on lan0'. The wanos bridge needs to separate the wan side from the lan side, either physically between the router and lan switch or using two different vlans for the wan and lan network.
-
Hi,
In my case I don't have router here..even without wanos my P2P link setup is like this
A-Core---ISP--B-Core
at present I see this connection
A--Core ( 10.9.232.1 )--L2--WANOS ( 10.9.232.2 )---ISP---WANOS( 10.9.232.4 )--Core B( 10.9.232.3 ) ( B end L2 switch is missing, will connect to L2 & check, if this is not working, then will connect router )
Thanks for patience..
-
Ok, a layer-2 setup is fine, there is no need for a router, but the wanos bridge needs to separate the ISP side from the lan side, either physically with the cabling or with separate inside/outside vlans.
-
I did layer 2 setup, but speed decreased drastically from 10Mbps to 500kbps
A End:
Thu Jul 17 19:41:46 UTC 2014 : Info : Cleared Statistics and Logs
Thu Jul 17 19:41:54 UTC 2014 : Info : Clearing the datastore
Thu Jul 17 19:41:54 UTC 2014 : Info : Reboot Requested
Thu Jul 17 19:42:18 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 17 19:42:18 UTC 2014 : Routine : Set Interface Roles
Thu Jul 17 19:42:18 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Thu Jul 17 19:42:19 UTC 2014 : Routine : Check Configs
Thu Jul 17 19:42:19 UTC 2014 : Routine : Updating Configuration
Thu Jul 17 19:42:19 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
ToDevice(wan0): Message too long
ToDevice(wan0): Message too long
B End:
Thu Jul 17 19:42:28 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 17 19:42:28 UTC 2014 : Routine : Set Interface Roles
Thu Jul 17 19:42:28 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Thu Jul 17 19:42:29 UTC 2014 : Routine : Check Configs
Thu Jul 17 19:42:29 UTC 2014 : Routine : Updating Configuration
Thu Jul 17 19:42:29 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
any suggestions before I test with router, B End is not having stock of router, need to check how & what to do.
-
ToDevice(wan0): Message too long
Traffic is not flowing through B
-
Hi,
You mentioned 2separate vlan for LAN and wan...
On the wanos system can I configure different ip for each interface LAN0 and wan0
-
No, lan0 and wan0 are bridged in software and any ip addresses applied to them are not used.
-
Hi Admin,
I'm failing with my scenario where I don't have routers, could you help me with lan wan ip's for both ends pls..
this is the current ip conf
10.10.10.xxx--Lan--Core(Vlan Gw 10.9.232.1 )--Wanos ( 10.9.232.2 )--------ISP--------Wanos( 10.9.232.4)--Core(Vlan gw 10.9.232.3)--LAN ( 192.168.1.xxx )
-
Anil,
First get the network to work without installing Wanos. Then plot out the ip addresses as you have done here on the working topology.
Wanos is a bridge, like a switch, there is no need to make the addressing complicated. From one of the previous messages it sounded like the ISP link is a layer2 link? In this case I would expect the LAN on both ends to have the same addresses, so to see three different subnets without any layer3 devices is a bit confusing (or at a minimum not the complete picture).
-
Without Wanos, it works without issue. I have attached the diagram of setup with & without Wanos
ISP is Layer2
Please suggest further after checking the diagram.
-
1) Please provide the switch port config of the L2 P2P link without Wanos
2) How does the router decide which traffic to route over the L2 P2P: e.g. static routes or pbr. And is the routing asymmetrical?
-
A end switch port status:
GigabitEthernet0/1/45 is up, line protocol is up
Hardware is GigabitEthernet, address is 0024.38fa.eeec (bia 0024.38fa.eeec)
Configured speed auto, actual 1Gbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDIX
Member of L2 VLAN ID 42, port is untagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0, mac-learning is enabled
Flow Control is config enabled, oper enabled, negotiation disabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
Inter-Packet Gap (IPG) is 96 bit times
IP MTU 1500 bytes
300 second input rate: 896 bits/sec, 1 packets/sec, 0.00% utilization
300 second output rate: 1096 bits/sec, 1 packets/sec, 0.00% utilization
103532483 packets input, 58025915820 bytes, 0 no buffer
Received 302447 broadcasts, 7480046 multicasts, 95749990 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
190477506 packets output, 207835451080 bytes, 0 underruns
Transmitted 27738038 broadcasts, 5947649 multicasts, 156791819 unicasts
0 output errors, 0 collisions
Relay Agent Information option: Disabled
B end switch port status:
GigabitEthernet1/10 is up, line protocol is up
Hardware is GigabitEthernet, address is 0012.f220.8500 (bia 0012.f220.8509)
Configured speed 1Gbit, actual 1Gbit, configured duplex fdx, actual fdx
Configured mdi mode AUTO, actual MDIX
Member of L2 VLAN ID 4, port is untagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0
Flow Control is config enabled, oper enabled, negotiation disabled
Mirror disabled, Monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IPG MII 96 bits-time, IPG GMII 96 bits-time
IP MTU 1500 bytes, encapsulation ethernet
30 second input rate: 4904 bits/sec, 0 packets/sec, 0.00% utilization
30 second output rate: 1200 bits/sec, 2 packets/sec, 0.00% utilization
12374284644 packets input, 16913128663181 bytes, 0 no buffer
Received 5904322 broadcasts, 1146896 multicasts, 12367233426 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
9092507966 packets output, 3574619936350 bytes, 0 underruns
Transmitted 343055 broadcasts, 152496 multicasts, 9092012415 unicasts
0 output errors, 0 collisions
Relay Agent Information option: Disabled
2) we have static routes added for MPLS & P2P. Routing is not asymmetrical
for Ex:
If I want to divert some traffic to B End, then route on A end will be like this. 192.168.178.200 & 10.9.64.111 both paths on P2P link.
ip route 192.168.178.200 255.255.255.255 10.9.232.3
on B end it will be
ip route 10.9.64.111 255.255.255.255 10.9.232.1
-
I have added router on A-End.
Core--WanOS---Router---P2P ISp---WanOS--Core
Core--Core ( Network breaks & I have to reset B End Services or need to restart the machine )
Edge--Core( Network breaks & I have to reset B End Services or need to restart the machine )
Core--Edge( Network breaks & I have to reset B End Services or need to restart the machine )
Edge--Edge ( No issues observed, except router will not be reachable & I had to restart the A end services to make router reachable )
on A end I see
Mon Jul 21 16:40:44 UTC 2014 : Routine : Initializing Startup Scripts
Mon Jul 21 16:40:44 UTC 2014 : Routine : Check Configs
Mon Jul 21 16:40:44 UTC 2014 : Routine : Updating Configuration
Mon Jul 21 16:40:44 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
DropBroadcasts: dropped a packet
-
and B (where the issue is)?
-
Mon Jul 21 15:51:27 UTC 2014 : Routine : Initializing Startup Scripts
Mon Jul 21 15:51:27 UTC 2014 : Routine : Check Configs
Mon Jul 21 15:51:27 UTC 2014 : Routine : Updating Configuration
Mon Jul 21 15:51:27 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
-
Anil, provide the full log please. e.g. I need to see what happened at B end and if this is related to the required restart.
-
that was the recent log, do you need debug log ?
-
Then something is not setup right, because you are supposed to see the logs entries before the restart.
-
do you think should I load 1.2.1 & check ? currently im running with 1.2.2 on both sides.
before restart also I see prev Wanos service start logs, nothing much is captured, except prev logs like peer detected etc. which was shared earlier.
-
If you see the logs and after restarts they are gone and start from scratch again, then there is a disk related issue. This might also explain why you are having so much issues with the dd commands as well as explaining why no issues are seen in edge-edge mode. Perhaps start by replacing the B side, at least get the logs to persist during restarts. Check the overview page to see which drive the datastore is mounted on.
-
now again I connected without router.
Core--Core
I can download single Zip files of 300MB + ( earlier I have not tried single compressed files ), both ways multiple times. If same file is extracted & try to download then it stops after some time. Folder contains, exe, doc, etc.
Other B end don't respond, again we need to access via Ssh & reboot the machine
Core-Edge ( above issue )
Edge--Core ( above issue )
Edge--Edge
No issues oberved even for extracted files, I was able to download 600Mb extracted files muliple times both ways.
Do you think I should try with 1.2.1 version
-
Hi,
DD was for my other testing, so its not related to this testing.
-
Open remote access to the B end.
-
Open remote access to B end ? What I'm supposed to do ?
Sorry...this troubleshooting is going on for many days..thanks for your patience in trying to help me...
-
Yes Anil, I can't help without all the info as requested. Please provide login details so I can have a good look what is going on.
-
Is ssh access fine ?, if not I will share webex event id details for view.
Do you think should I check with 1.2.1 ?
-
Let me check the systems first. Yes, ssh is fine.
-
B end I see this
Mon Jul 21 19:30:01 UTC 2014 : Routine : Initializing Startup Scripts
Mon Jul 21 19:30:01 UTC 2014 : Routine : Set Interface Roles
Mon Jul 21 19:30:01 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Cannot set device rx csum settings: Operation not supported
Cannot set device tx csum settings: Operation not supported
Cannot set device scatter-gather settings: Operation not supported
Cannot set device tcp segmentation offload settings: Operation not supported
Mon Jul 21 19:30:01 UTC 2014 : Routine : Check Configs
Mon Jul 21 19:30:01 UTC 2014 : Routine : Updating Configuration
Mon Jul 21 19:30:02 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
-
hi,
Core--Core
Today we loaded 1Gig card on B end, now I see A end giving issue, if I try to upload the data to B...network stops & I have to restart A end services.
B to A download is not giving any issue at the moment
A end:
Wed Jul 23 17:00:02 UTC 2014 : Routine : Initializing Startup Scripts
Wed Jul 23 17:00:02 UTC 2014 : Routine : Check Configs
Wed Jul 23 17:00:02 UTC 2014 : Routine : Updating Configuration
Wed Jul 23 17:00:02 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
Wed Jul 23 17:11:40 UTC 2014 : Info : Reboot Requested
Wed Jul 23 17:12:05 UTC 2014 : Routine : Initializing Startup Scripts
Wed Jul 23 17:12:05 UTC 2014 : Routine : Set Interface Roles
Wed Jul 23 17:12:05 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Wed Jul 23 17:12:06 UTC 2014 : Routine : Check Configs
Wed Jul 23 17:12:06 UTC 2014 : Routine : Updating Configuration
Wed Jul 23 17:12:06 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
-
One more thing observed..if I try to copy multiple files at a time, then network stops. same compressed file of 2GB works fine without issue.
I'm not sure if wanos is able to handle multiple random files at same time.
on A end I see
ToDevice(wan0): Message too long
-
On B End I see, is this normal.
IPFragmenter(1500) DF
Thu Jul 24 11:22:28 UTC 2014 : Info : Reboot Requested
Thu Jul 24 11:22:49 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 24 11:22:49 UTC 2014 : Routine : Set Interface Roles
Thu Jul 24 11:22:50 UTC 2014 : Routine : Setting Optional Interface driver flags if supported
Thu Jul 24 11:22:50 UTC 2014 : Routine : Check Configs
Thu Jul 24 11:22:50 UTC 2014 : Routine : Updating Configuration
Thu Jul 24 11:22:50 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1512
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1513
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1513
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1513
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1513
IPFragmenter(1500) DF 192.168.39.152 10.9.64.111 len=1513
Thu Jul 24 15:42:05 UTC 2014 : Routine : Initializing Startup Scripts
Thu Jul 24 15:42:05 UTC 2014 : Routine : Check Configs
Thu Jul 24 15:42:05 UTC 2014 : Routine : Updating Configuration
Thu Jul 24 15:42:05 UTC 2014 : Routine : Initializing Wanos Click
wanos.click:9: While initializing 'lan0 :: FromDevice':
warning: lan0: no IPv4 address assigned
wanos.click:8: While initializing 'wan0 :: FromDevice':
warning: wan0: no IPv4 address assigned
-
Hi,
After updates, I don't see network hung...Transferred around 10GB of files of different size & format, everything going smooth.
Will mail you on the results & doubts which I have on report section.
-
Thanks Anil, great to hear that and appreciate the feedback.