Hi, Morten:
Specifically you can use
1. Utility as 'snoop' or 'wireshark' to capture the ethernet traffic
between your initiator and target, and then analysis the iscsi traffic
to see whether NOP is periodically exchanged between them.
For snoop, use command as "snoop -d e1000g0 -o abc.cap", while e1000g0
is used to specify your NIC that flow iscsi traffic, captured package is
stored in abc.cap file.
2. Write a dtrace file to trace the function of 'iscsi_nop_checks' and
'iscsi_handle_nop' to see whether initiator actively send NOP to target
when connection get idle.
A quite simple dtrace file like this:
#! /usr/sbin/dtrace -s
#pragma D option flowindent
fbt:iscsi:iscsi_nop_checks:
{}
fbt:iscsi:iscsi_handle_nop:
{}
3. Or simply check /var/adm/messages to track 'iscsi' driver log, to
have a check why iSCSI initiator get iSCSI LUN offline.
Regards,
ZhangYi
Andrey Kuzmin wrote:
Why not just post a tcpdump log of the session in question?
Regards,
Andrey
On Fri, Jan 15, 2010 at 10:54 AM, Morten Green Hermansen
<morte...@fanitas.com> wrote:
Hello!
Synology tells me that the problem is OpenSolaris. I have started a thread in
Synologys forums, see:
http://forum.synology.com/enu/viewtopic.php?f=147&t=19569
Best regards,
- Morten Green Hermansen, Fanitas
--
This message posted from opensolaris.org
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
