w), show only the number of errors on the e With either the interface display (options -I or w), show only the number of dropped packets. d With either the interface display (options -I or This option has noĮffect unless -w is specified as well.
c count Display count updates, then exit. i), show bytes in and out, instead of packet b With the interface display (options -I or The send window size, receive window size and congestion window size. B With the default display, show buffer sizes for TCP sockets. a With the default display, show the state of all sockets normally sockets Only the super-user can see theseĪddresses unprivileged users will see them as 0x0. Used with the -r flag it shows the internalĪddresses of the routing table. The options are as follows: -A Show the address of any protocol control blocks associated with sockets The forms are shown in order of precedence: for example, if The finalįorm displays internals of the protocol control block (PCB) and the socket The ninth form displays information about routing tables. The eighth form displays information about routingĭomains. The seventh form shows information related to Traffic on the configured network interfaces. The fifth form continuously displays the information regarding packet The fourth form displays per-interface statistics. The second form displays per-interface statistics for the The first form of the command displays a list of active socketsįor each protocol. The default display shows information about all active An rx_missed_error indicates no ring buffer slot is available for an incoming frame, which is mainly caused by not enough SND/IRQ CPU resources being available to empty it in a timely fashion.The netstat command shows various aspects
Since it looks like you have a high percentage of fully-accelerated traffic (SXL path), you almost certainly need to reduce the number of kernel instances via cpconfig, thus adding more SND/IRQ instances to help handle all the fully accelerated traffic. I highly doubt that RX-DRPs are interfering with the SecureXL Optimized Drop function as they are two completely different things, but in general I'm not a fan of enabling optimized drops unless you need them as it can lead to complications with SecureXL like the ones you are experiencing. That RX-DRP percentage is quite low and really nothing to worry about. QXL pkts/Total pkts : 0/1410322803 input is appreciated, just trying to figure out if there is an easy fix for this or if there is something more sinister going on underneath. When we turn on Optimized Drops, SecureXL crashes after these errors accrue and then our CPU goes up across all the cores. The volume of these errors is pretty small, 0.0087%, and as far as we can tell, there aren't any issues being caused by it, but the presence of these errors prevents us from being able to run Optimized Drops on this wall. I've got 3 other similarly outfitted clusters that don't see errors on the same scale but they are no where near as busy as this main gateway. Output of netstat ni and and ethtool -S output for that gateway. We are seeing that those numbers coincide with rx_missed_errors when we run the ethtool command. We have a cluster of Open Hardware R80.10 systems that have some decent numbers of RX-DRPs showing up when we run netstat -ni.