I am having an issue with utilizing a single port from the 2 Intel PRO/1000 MT
Dual port nics in a tpg of COMSTAR.
Here is the setup and I have been working on this issue starting with 2009.06,
yet the problem would also happen with CIFS shares as well.
MB Chipset: nVidia MCP55 Pro & NEC uPD720400
2 x Intel PRO/1000 MT Dual Port
snv-129
COMSTAR
NIC are configured like this
Onboard Port 0__
\
=== agg1 192.168.1.25
/
Intel 0 Port 0____
Onboard Port 1 = nge1 192.168.2.30
Intel 0 Port 1 = e1000g1 192.168.3.30
Intel 1 Port 0 = e1000g2 192.168.3.31
Intel 1 Port 1 = e1000g3 192.168.2.31
Each subnet has its own physical network.
Now after installing snv-129 I installed storage-server and enabled the COMSTAR
services. Then with the system being configured with nwam on nge0 (all other
nics are disabled at this point) I created my target and views with no tpg.
Success, no crashing, and excellent COMSTAR performance. (windows 7 iscsi
initiator)
Then I disabled nwam, created aggr1 with ngeo and e1000g0 and setup my static
ip (including my manual DNS and Gateway configurations). At this point I
enabled my other nics and statically addressed them. I then added aggr1 to a
tpg and added the tpg to my target.
Success again...
Now I add nge1 to the tpg so now I have aggr1 and nge1 in the tpg. I connect my
initiator and designate nge1 as the primary path.
Success yet again...
Here is the trick, if I add a single port, even in its own tpg, and that tpg
the only tpg assigned to the target, the system will reboot, no logs, no
savecore dumps (I have ensured that savecore dumps function), I believe I
rulled out a power supply issue as in the bios i set it to remain off if there
is a power failure.
There it is, I am thinking it is the intel nics, yet what is strange is that it
functions just fine in an aggrigated configuration.
Any thoughts?
Then I
--
This message posted from opensolaris.org
_______________________________________________
opensolaris-help mailing list
[email protected]
