Network and Storage Protocols
Looking at nfsstat -s on a too-busy filer:
calls badcalls nullrecv badlen xdrcall
623374644 4294965579 0 0 4294965579
94335674 2 0 0 2
717710318 3 0 0 3
0 0 0 0 0
Why are IPV4 badcalls and IPV6 badcalls near zero? Shouldn't they be more or less the sum of TCP + UCP badcalls?
Even though badcalls=xdrcalls? (which is interesting by itself and might be the result of a bug in Objectivity and its proprietary brain-damaged NFS stack.)
I don't think this is a counter wrap issue (even though TCP calls seems to have wrapped.)
xdrcalls are calls that could not even be decoded by RPC layer. badcalls are calls that have been decoded but rejected.
NetApp Wins One Silver and One Bronze Stevie® Award in 2022 Stevie Awards for Sales and Customer Service
Live Chat, Watch Parties, and More!
Engage digitally throughout the sales process, from product discovery to conﬁguration, and handle all your post-purchase needs.