|
|
|
Question : Problem: WTF's up with my iSCSI network config ???
|
|
Experts:
I just purchased an EMC AX4-5i dual-SP SAN appliance; two racks, one for SAS drives and the other with SATA drives. I'm just setting up the appliance and I'm stuck, hoping you all can help me figure something out.
If you look at the attached file you'll notice my vanilla setup: 1 server with 3 NICs connected to a pair of GigE switches configured in a meshed network connecting a pair of SP units, each with two iSCSI ports of their own.
The problem I'm having is that on the server i can only ping one of two switches and only two of four iSCSI ports
C:\Program Files\Support Tools>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : galapagos
Primary Dns Suffix . . . . . . . : xxx.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : xxx.local
Ethernet adapter 192.168.253.98:
Connection-specific DNS Suffix . : xxx.local
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter
Physical Address. . . . . . . . . : 00-04-23-AB-6A-0B
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.253.98
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter 192.168.253.99:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Server Adapter #2
Physical Address. . . . . . . . . : 00-04-23-AB-6A-0C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.253.99
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter 192.168.10.25:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC3163 Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-50-8B-EB-15-1C
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.25
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.13
192.168.10.25
Primary WINS Server . . . . . . . : 192.168.10.13
Secondary WINS Server . . . . . . : 192.168.10.25
C:\Program Files\Support Tools>ping 192.168.253.199
Pinging 192.168.253.199 with 32 bytes of data:
Reply from 192.168.253.199: bytes=32 time=3ms TTL=64
Reply from 192.168.253.199: bytes=32 time=2ms TTL=64
Reply from 192.168.253.199: bytes=32 time=1ms TTL=64
Reply from 192.168.253.199: bytes=32 time=2ms TTL=64
Ping statistics for 192.168.253.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms
C:\Program Files\Support Tools>ping 192.168.253.198
Pinging 192.168.253.198 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.253.198:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Program Files\Support Tools>ping 192.168.253.200
Pinging 192.168.253.200 with 32 bytes of data:
Reply from 192.168.253.200: bytes=32 time<1ms TTL=64
Reply from 192.168.253.200: bytes=32 time<1ms TTL=64
Reply from 192.168.253.200: bytes=32 time<1ms TTL=64
Reply from 192.168.253.200: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.253.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Program Files\Support Tools>ping 192.168.253.201
Pinging 192.168.253.201 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.253.201:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Program Files\Support Tools>ping 192.168.253.202
Pinging 192.168.253.202 with 32 bytes of data:
Reply from 192.168.253.202: bytes=32 time=1ms TTL=64
Reply from 192.168.253.202: bytes=32 time<1ms TTL=64
Reply from 192.168.253.202: bytes=32 time<1ms TTL=64
Reply from 192.168.253.202: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.253.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
C:\Program Files\Support Tools>ping 192.168.253.203
Pinging 192.168.253.203 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.253.203:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Program Files\Support Tools>
So before I go any further and start configuring iSCSI initiators or LUNs, etc...I wanted to clear up this networking mystery
Thanks,
juckyt
|
Answer : Problem: WTF's up with my iSCSI network config ???
|
|
Wow. I guess you do have money to pour down a rathole, especially if you're willing to shell out for a second M$ SBS license.
The current NetWare version is v6.5. To say "things have changed" from NetWare v3.12 is an understatement on the order of saying "Outlook is insecure and will open your organization to gobs of malware". Rather than just tossing aside the idea based on 15-year-old information, perhaps you might look at the *current* state of the technology.
You don't have to "teach your old dogs new tricks". From the client perspective, the NetWare environment is not all that different than the Windoze one, it just doesn't go down all the time. Remote directories are still accessed as drive letters, UNC notation works just fine, etc. etc. If you wanted, you could even have the NetWare server appear as a Windoze/CIFS server (just minus the BSODs) - the client machines will never know the difference (this is called Native File Access Protocols - think of it as SAMBA for NetWare; and its *included* with NetWare SBS v6.5).
You do NOT have to give up Outlook, as long as you don't mind being vulnerable to everything some pimple-faced script kiddie dreams up. GroupWise supports IMAP, POP, CAP (Calendar Access Protocol), and there is an GroupWise Plug-In for Outlook that lets Outlook directly access the GroupWise system. At least when a virus hits Outlook it won't compromise the server too. Or you could use Thunderbird...or any other IMAP client for that matter.
As for your backup software, if you have any one of a dozen or more backup systems, its just a matter of switching your licensed platform. You haven't bothered to state what your backup software is, but it probably has a NetWare-based version, and so there's no big deal to switch.
11) No, but I don't see much point in saving that kinda dough on the hardware just to waste it on software.
a) Nope.
b) Hmmmm....IBM is unlikely to be cheaper, altho they have good hardware.
Fine, you're not using DHCP or printing services. If you go to W2K3, you WILL be using DNS, because the laughable "Not really a Directory Service but we call it one" Active Directory is chained to DNS. Using elimination of DHCP and printing services from the list as a reason not to worry about running everything on one box is like saying you'll improve you car's gas mileage by throwing out the spare tire. A/V will drag the box, and Heaven knows, you desperately need A/V on a Windoze server. E-Mail and VPN will drag the box too.
12) Yes, in my opinion. There are very sound reasons you don't want to have all your eggs in one basket like this. Security 101 tells you that you don't want to put your core services on a machine that you must expose directly to the Internet. Business Continuity 101 tells you that you'll improve your reliability - remember the dead hard drive episode? - by running something like clustering - guess what? NetWare SBS v6.5 *includes* a two-node clustering license. You'll have to shell out more for clustering under M$ SBS 2K3. And no, NetWare clustering does NOT take identical hardware for each machine; again, this is NOT NetWare v3.12, the technology has CHANGED. Technology 101 tells you that Apache is both more widely-deployed and more stable/secure than IIS; NetWare ships with Apache, W2K3 ships with IIS.
Is this business important? Do you depend on its income? Then Security and Business Continuity should be serious concerns.
13) Yes, M$ SBS is limited to one box. You would have to go to the non-SBS versions, and then you pay a per-server license change. NetWare (either SBS or regular) does not have a per-server license charge - it is licensed per seat, regardless of how many servers you choose to use. Yes, you'd need to buy Exchange separately.
14) The issue with that idea, aside from the exorbitant cost, is that you will end up with two separate Domains/AD environments, each with deparate authentication. You'll double your account management burden. And since that old Dell is already struggling under NT4, what makes you think the even more bloated W2K3 SBS package is going to run with anything even approaching acceptable performance?
Does the M$ SBS package include VPN support? If not, you'll have to add it on, for more $$$. Its included in NetWare SBS v6.5.
NetWare SBS v6.5 also ships with Pervasive SQL 2000, MySQL, Tomcat, Perl, PHP and OpenSSH. How much would you have to shell out for M$ SQL on top of what you'd be paying for M$ SBS? Novell's offering you more useful tools for less money, and requiring less hardware and less administration headache, and you're still happy to throw your limited business funds at Redmond?
|
|
|
|
|
