Community discussions

MikroTik App
 
andza
just joined
Topic Author
Posts: 14
Joined: Mon Feb 27, 2012 1:19 am
Location: Riga / Latvia

Routerboard 450 packet loss, when connected to HP-5308xl

Mon Feb 27, 2012 1:47 am

Hi,
I've been using Mikrotik products for many years. Now I connected with the problem.
Datacenter offered me switch port to HP-5308xl-switch, and I saw that ProCurve doesn't like Routerboard's ethernet link signals.
Firstly I connected Routerboard's first ethernet interface to switch via patch link. Set up host (IP/mask/gate) as host only router. The problem begins that I'couldn't connect to it from it's real IP address. With many tries I get connected. I mentioned also, that there's a big packet loss.
I asked to datacenter technical stuff to discover the problem, they said that "my device" has double and tripple MAC addresses seen on network.
Firstly they though that I am using a switch not router, with disabled STP protocol on bridge interface :)
I tried to change MAC adressess, switch ports to another - no results, then I changed Routerboards ethernet interface ports from ether1 to ether5, then performance was better (less packet loss), I also unchecked (disabled) auto-negotioation option under ethernet device.
I tried to ping real network address from mikrotik's console, then there haven't any packet loss.
But the problem connecting to router's real IP address from outside networks - still active.
I also tried to put my configuration on RB433 to ensure that there's no router problem, but also the same.
Both devices uses the same IC+ switch chip, and I think this IC+ conflicts with HP ProCurve switch. Tomorrow I'll ask to prepare me another port on Cisco switch, then I try again.
Has anybody connected with the same problem?

##############################################
Pings looks like:

Pinging xxx.yyy.zzz with 32 bytes of dat
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56

Ping statistics for xxx.yyy.zzz:
Packets: Sent = 80, Received = 62, Lost = 18 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms


##############################################

There's 30-50% packet loss, it's abnormal.

Routerboard 450
OS: latest - RouterOS 5.14.
firmware: latest - 2.39
 
andza
just joined
Topic Author
Posts: 14
Joined: Mon Feb 27, 2012 1:19 am
Location: Riga / Latvia

Re: Routerboard 450 packet loss, when connected to HP-5308xl

Mon Feb 27, 2012 11:09 pm

Hi,
I've been using Mikrotik products for many years. Now I connected with the problem.
Datacenter offered me switch port to HP-5308xl-switch, and I saw that ProCurve doesn't like Routerboard's ethernet link signals.
Firstly I connected Routerboard's first ethernet interface to switch via patch link. Set up host (IP/mask/gate) as host only router. The problem begins that I'couldn't connect to it from it's real IP address. With many tries I get connected. I mentioned also, that there's a big packet loss.
I asked to datacenter technical stuff to discover the problem, they said that "my device" has double and tripple MAC addresses seen on network.
Firstly they though that I am using a switch not router, with disabled STP protocol on bridge interface :)
I tried to change MAC adressess, switch ports to another - no results, then I changed Routerboards ethernet interface ports from ether1 to ether5, then performance was better (less packet loss), I also unchecked (disabled) auto-negotioation option under ethernet device.
I tried to ping real network address from mikrotik's console, then there haven't any packet loss.
But the problem connecting to router's real IP address from outside networks - still active.
I also tried to put my configuration on RB433 to ensure that there's no router problem, but also the same.
Both devices uses the same IC+ switch chip, and I think this IC+ conflicts with HP ProCurve switch. Tomorrow I'll ask to prepare me another port on Cisco switch, then I try again.
Has anybody connected with the same problem?

##############################################
Pings looks like:

Pinging xxx.yyy.zzz with 32 bytes of dat
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=1ms TTL=56
Reply from xxx.yyy.zzz: bytes=32 time=2ms TTL=56

Ping statistics for xxx.yyy.zzz:
Packets: Sent = 80, Received = 62, Lost = 18 (22% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms


##############################################

There's 30-50% packet loss, it's abnormal.

Routerboard 450
OS: latest - RouterOS 5.14.
firmware: latest - 2.39
Now switched to cisco, no change, still packet loss :(
 
andza
just joined
Topic Author
Posts: 14
Joined: Mon Feb 27, 2012 1:19 am
Location: Riga / Latvia

Re: Routerboard 450 packet loss, when connected to HP-5308xl

Tue Feb 28, 2012 9:45 pm

I send a problem description, to support@mikrotik.com, during 3 days no-one just auto-reply answered :)
I think because they haven't found any answers for this problem on mikrotik's forum :)
It seems that RB450 cannot be used on production environment (if you want quality of service), just only for home wired solutions and I think for modern home it is useless, because doesn't have wireless on it.

My message below (in Latvian):

Labdien,

Rakstu Jums saistībā ar Routerboard 450. Ir tehniskas problēmas, izveidojot linku ar HP-5308xl-sw komutatoru, liels packet loss, 30-50%. Izmēģināju visus Routerboard portus. Lielākais packet loss bija uz portu ether1, kur ir PoE - 50%. Pārslēdzu uz ether5 un interfeisam atslēdzu Auto-negotioation. Virzienā no rūtera uz kādu citu tīklu pings tagad ir normāls (0% packet loss) par to pārliecinājos veicot pingu no rūtera konsoles, bet savukārt slēdzoties no ārpuses - liels savienojuma aiztures laiks. Savienojas, tad dropojas nost.
Konfigurācija - standarta, links ar reālo IP, netmask un gateway, bridge interfeiss netiek izmantots. Kolēģis LatNet saka, ka viņš tīklā redzot dublējamies konkrētā pieslēgtā interfeisa MAC adreses un tas ir par iemeslu, kāpēc ir liels savienojuma aiztures laiks. Sākotnēji viņs bija domājis, ka es lietojot switch nevis router, kuram nav ieslēgts STP uz bridge interfeisa.
Eksperimentāli izmēģināju arī citu routerboard RB433AH - problēma tā pati. Plāni pārslēgt iekārtu no HP uz Cisco switch, tas tiks izdarīts rītdien. Vai ir novēroti Routerboard savienojumu darbības traucējumi, pieslēdzot pie kādiem specifiskiem switch? Par rūtera konfigurāciju esmu pārliecinājies un ar to nevajadzētu būt problēmām. Varbūt šī problēma jau ir zināma un tiek pie tās strādāts? Izskatās, ka gan RB450 gan RB433 lieto IC+ čipus, uz kuriem atrodas tīkla interfeisi, varbūt tieši pats čipset konfliktē ar HP iekārtu?
 
andza
just joined
Topic Author
Posts: 14
Joined: Mon Feb 27, 2012 1:19 am
Location: Riga / Latvia

Re: Routerboard 450 packet loss, when connected to HP-5308xl

Tue Feb 28, 2012 9:47 pm

Maybe they don't understand in Latvian, but then they can take google translate :)))
LOL
 
wpeople
Member
Member
Posts: 378
Joined: Sat May 26, 2007 6:36 pm

Re: Routerboard 450 packet loss, when connected to HP-5308xl

Wed Feb 29, 2012 9:06 pm

fix port speed to 100mbps FDX on both device. hopefully it will do the job.
 
andza
just joined
Topic Author
Posts: 14
Joined: Mon Feb 27, 2012 1:19 am
Location: Riga / Latvia

Re: Routerboard 450 packet loss, when connected to HP-5308xl

Wed Feb 29, 2012 9:23 pm

fix port speed to 100mbps FDX on both device. hopefully it will do the job.
As I previously wrote, I UNCHECKED AUTO NEGOTIOATION, it means that AUTO doesn't work but, manual Full-Dupplex is working.
Now I solved problem simply changing router with the same configuration on Routerboard 750 (cheaper than RB450)
Now all things goes smooth

Who is online

Users browsing this forum: elvo3d, glueck05, jebz and 21 guests