HPE Storage Users Group

A Storage Administrator Community




Post new topic Reply to topic  [ 1 post ] 
Author Message
 Post subject: RCIP and jumbo frames question
PostPosted: Tue Oct 24, 2017 4:52 am 

Joined: Tue Mar 29, 2016 9:32 pm
Posts: 136
Hi all,

I've having a real struggle with HPE support to get an answer (having them understand the questions is a struggle, they keep saying "the manual says ....."), hoping I can bounce the idea of you guys and see what you think :-)

I have RCIP configured between an 8400 and an 8200, the network guys are certain that an MTU of 9000 will work the whole route (the company owns everything in between, fibre, switches, routers etc), they say their interfaces are configured for up to 9100 (something about catering for VPLS).
So I have configured the RCIP ports to an MTU of 9000.

However .. "checkrclink" complains and says the max MTU is only 1500.

Code:
------------------------------------------------------------
Starting max MTU test, from 0:3:1 -> 192.168.241.10
------------------------------------------------------------
ping: local error: Message too long, mtu=9000
ping: local error: Message too long, mtu=9000
ping: local error: Message too long, mtu=9000

MTU: 1500


Now if I run the "controlport rcip ping" tests and force a packet size greater than 1500, and set the do not fragment flag ... it works!

Code:
controlport rcip ping -c 5 -s 8972 -pf 192.168.241.31 1:3:1
PING 192.168.241.31 (192.168.241.31) from 192.168.241.11 : 8972(9000) bytes of data.
8980 bytes from 192.168.241.31: icmp_req=1 ttl=64 time=11.2 ms
8980 bytes from 192.168.241.31: icmp_req=2 ttl=64 time=11.2 ms
8980 bytes from 192.168.241.31: icmp_req=3 ttl=64 time=11.2 ms
8980 bytes from 192.168.241.31: icmp_req=4 ttl=64 time=11.2 ms
8980 bytes from 192.168.241.31: icmp_req=5 ttl=64 time=11.2 ms

--- 192.168.241.31 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 11.213/11.235/11.249/0.068 ms


(packet size of 8172, because ICMP or something adds the 28bytes making a total of 9000, running the same test and forcing it to be 9001 bytes fails as expected)

Any ideas what is going on ? Why would the ping test of big packets succeed, but checkrclink fail ?

Ideally I would love to find a command on the 3PAR that shows the network statistics and shows if packets are being received fragmented and re-assembled (like you get from "netstat -s" )

I can't do any tests by just running a cable between the 3PARs as they are about 800km apart.

Thanks!


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 


Who is online

Users browsing this forum: No registered users and 37 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group | DVGFX2 by: Matt