Thanks. I was looking for more granular error reporting
(i.e., iscsi session X failed at Y / iscsi session X had Y errors
between time A and time B)

On Sep 10, 11:24 pm, "Ulrich Windl" <ulrich.wi...@rz.uni-
regensburg.de> wrote:
> On 10 Sep 2009 at 10:53, solidguy wrote:
>
>
>
> > Is there a good way to monitor the iscsi sessions for errors? I need
> > to report it via SNMP (and perhaps kill the VM running over the
> > connection). Right now the only way I see is to monitor syslog -- but
> > the syslog doesn't always give me which session (or disk) is in
> > trouble.
>
> Maybe something like "netstat -s"? For those who don't know, here's an 
> example of
> "netstat -s" in HP-UX (partial output only):
>
> netstat -s
> tcp:
>         2230243561 packets sent
>                 2219104628 data packets (2507019105755 bytes)
>                 733 data packets (583009 bytes) retransmitted
>                 7150563 ack-only packets (3941611 delayed)
>                 3465 URG only packets
>                 271750 window probe packets
>                 52973 window update packets
>                 3992851 control packets
>         1443289314 packets received
>                 1362450977 acks (for 2507016701224 bytes)
>                 596 duplicate acks
>                 0 acks for unsent data
>                 646031312 packets (160540170224 bytes) received in-sequence
>                 0 completely duplicate packets (0 bytes)
>                 6499 packets with some dup data (1092308 bytes duped)
>                 6499 out of order packets (545964 bytes)
>                 0 packets (0 bytes) of data after window
>                 271750 window probes
>                 782772 window update packets
>                 18729 packets received after close
>                 0 segments discarded for bad checksum
>                 0 bad TCP segments dropped due to state change
>         1193488 connection requests
>         671426 connection accepts
>         1864914 connections established (including accepts)
>         2601445 connections closed (including 774164 drops)
>         717930 embryonic connections dropped
>         1361096509 segments updated rtt (of 1361096509 attempts)
>         322 retransmit timeouts
>                 3 connections dropped by rexmit timeout
>         271750 persist timeouts
>         308419 keepalive timeouts
>                 306875 keepalive probes sent
>                 0 connections dropped by keepalive
>         0 connect requests dropped due to full queue
>         718236 connect requests dropped due to no listener
>         0 suspect connect requests dropped due to aging
>         0 suspect connect requests dropped due to rate
> udp:
>         0 incomplete headers
>         0 bad checksums
>         0 socket overflows
> ip:
>         877280934 total packets received
>         0 bad IP headers
>         0 fragments received
>         0 fragments dropped (dup or out of space)
>         0 fragments dropped after timeout
>         0 packets forwarded
>         0 packets not forwardable
> icmp:
>         21109 calls to generate an ICMP error message
>         0 ICMP messages dropped
>         Output histogram:
>          echo reply: 6213
>          destination unreachable: 14896
>          source quench: 0
>          routing redirect: 0
>          echo: 0
>          time exceeded: 0
>          parameter problem: 0
>          time stamp: 0
>          time stamp reply: 0
>          address mask request: 0
>          address mask reply: 0
>         0 bad ICMP messages
>         Input histogram:
>          echo reply: 31569
>          destination unreachable: 14582
>          source quench: 0
>          routing redirect: 1
>          echo: 6213
>          time exceeded: 0
>          parameter problem: 0
>          time stamp request: 0
>          time stamp reply: 0
>          address mask request: 0
>          address mask reply: 0
>         6213 responses sent
> [...]
>
>
>
> > Thanks
> > --
> > solidguy
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to 
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to