Hi,
I am seeing the following errors in my environment, not sure why is it happening, any ideas? Thanks.
kernel: RPC: bad TCP reclen 0x73746174 (non-terminal ) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x63480000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x633f0000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x1201001a (non-terminal
What kernel version are you on? Also is the output of both these commands ran on each of the interfaces?
# ifconfig ethX | grep MTU
# ethtool -i ethX | grep driver
Basically there was a rpc regression a while back where if you were using jumbo frames then it would kick out the same error.
Sorry about the delay, No it dont display those info, and its a vmware environment. So as per vendor policy they wont disclose the NICs physical info. I am aware of the bug previously reported. But not sure if its a jumbo frame. Any other guesses? the output is below:
# uname -r
2.6.18-274.12.1.el5
# ifconfig ethX | grep MTU
ethX: error fetching interface information: Device not found
# ethtool -i ethX | grep driver
Cannot get driver information: No such device
You need to replace the X with the appropriate number for your device.
Sorry wasnt paying attention, but i did try those commands before. Below are out puts, but since its vmxnet3, how to know if its jumbo frames ?
# ifconfig eth0 | grep MTU
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
# ethtool -i eth0 | grep driver
driver: vmxnet3
the MTU would be 9000, so you are not using jumbo frames here, at least