Isolate iSCSI NIC to just iSCSI Traffic?

We just installed a iSCSI SAN and have put in dual NICs in many servers to
allow them to talk to the iSCSI SAN.

Though we are seeing a few issues.

The servers are registering the 2nd NIC in DNS and when some queries are
done, they are returning the iSCSI NIC IP, which is inaccessible to the rest
of the Clients.

Some of the Servers are using the iSCSI network to communicate with each
other vs using the 'intranet' NIC. Backup Exec seems to prefer using the
iSCSI NIC to get data from the servers.

How can I make it so the iSCSI NIC is only used to talk to the iSCSI SANs?

Thanks,
Scott<=-

First you have to set the Nic Properties in TCP IP to not register itself in
DNS

Then delete the bad DNS entries.

Then in DNS create manual A Records for each server and the SAN by using
"fake" names. Just make something up. Associate these "names" with the
correct IP#. These iSCSI nics in all the effected devices *must* be a
different subnet then the rest of the main LAN. Communication between the
Servers and the SAN will take place by using these "names".

The SAN will not be able to communicate with anything else on the rest of
the regular LAN.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

"Scott Townsend" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We just installed a iSCSI SAN and have put in dual NICs in many servers to
> allow them to talk to the iSCSI SAN.
>
> Though we are seeing a few issues.
>
> The servers are registering the 2nd NIC in DNS and when some queries are
> done, they are returning the iSCSI NIC IP, which is inaccessible to the
> rest of the Clients.
>
> Some of the Servers are using the iSCSI network to communicate with each
> other vs using the 'intranet' NIC. Backup Exec seems to prefer using the
> iSCSI NIC to get data from the servers.
>
> How can I make it so the iSCSI NIC is only used to talk to the iSCSI SANs?
>
> Thanks,
> Scott<=-

Hello Scott,

Thank you for using newsgroup!

From your post, I agree with Phillip Windell's opinion.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
================================================== ==
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ==
This posting is provided "AS IS" with no warranties, and confers no rights.





--------------------
| From: "Phillip Windell" <(E-Mail Removed)>
| References: <(E-Mail Removed)>
| Subject: Re: Isolate iSCSI NIC to just iSCSI Traffic?
| Date: Wed, 26 Sep 2007 09:33:51 -0500
| Lines: 43
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
| X-RFC2646: Format=Flowed; Response
| Message-ID: <#(E-Mail Removed)>
| Newsgroups: microsoft.public.windows.server.networking
| NNTP-Posting-Host: wandtv-host13.decatur.hansoninfosys.com 209.16.209.141
| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:7644
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| First you have to set the Nic Properties in TCP IP to not register itself
in
| DNS
|
| Then delete the bad DNS entries.
|
| Then in DNS create manual A Records for each server and the SAN by using
| "fake" names. Just make something up. Associate these "names" with the
| correct IP#. These iSCSI nics in all the effected devices *must* be a
| different subnet then the rest of the main LAN. Communication between
the
| Servers and the SAN will take place by using these "names".
|
| The SAN will not be able to communicate with anything else on the rest of
| the regular LAN.
|
| --
| Phillip Windell
| www.wandtv.com
|
| The views expressed, are my own and not those of my employer, or
Microsoft,
| or anyone else associated with me, including my cats.
| -----------------------------------------------------
|
| "Scott Townsend" <(E-Mail Removed)> wrote in message
| news:(E-Mail Removed)...
| > We just installed a iSCSI SAN and have put in dual NICs in many servers
to
| > allow them to talk to the iSCSI SAN.
| >
| > Though we are seeing a few issues.
| >
| > The servers are registering the 2nd NIC in DNS and when some queries
are
| > done, they are returning the iSCSI NIC IP, which is inaccessible to the
| > rest of the Clients.
| >
| > Some of the Servers are using the iSCSI network to communicate with
each
| > other vs using the 'intranet' NIC. Backup Exec seems to prefer using
the
| > iSCSI NIC to get data from the servers.
| >
| > How can I make it so the iSCSI NIC is only used to talk to the iSCSI
SANs?
| >
| > Thanks,
| > Scott<=-
|
|
|