Windows Server 2003
--
Questions
--
Followers
Top Experts
I've purchased a Dell PowerVault MD3000i, dual controllers, with the below hard disks installed:
10x 146GB
2x500GB
3x750GB
I need to build the following 'drives':
6 disk RAID 10
4 disk RAID 10
2 disk RAID 1 Â (using the 500GB disks)
3 disk RAID 5 Â (using the 750GB disks)
I've physically installed the SAN into my rack, but have no idea how to cable it up properly to utilise the redundancy and software install.
Is there a guide on the web? Where do I start?
Id much appreciate a good kick start!?!
Fals
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Here is the tech support number: (866)876-3355






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
in advance, will i need to modify my host NICs for jumbo frame size. Â i understand that the default NIC frame size is something 1500 and i'll need to modify the frames to 9000.
what's the deal with jumbo frames when it comes to this SAN?
do i need special network switches too?
any ideas about MD3000i cabling?

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
I've cabled the MD3000i up as follows:
1xMD3000i with two dual RAID controllers.
3x servers (2xDell PE2950 and 1xDell PE1950)
Two switches, one Powerconnect and and existing Netgear.
Each RAID controller plugs into the Dell PowerConnect and Netgear switch for redundancy.
I plug 1 management port per RAID controller into the Dell Powerconnect and 1 management port into the Netgear.
I have installed the MD management software onto the three servers, with only one active search (i forget what it called it, but it said upon install that only one instance of the software could search (?) ).
Each server can find the storage array via out-of-band configuration. Â when i first autodetected the array both management ports were detected and had an IP address.
Problems:
1. trying to give each management port a static IP address, I've 'accidentally' turned on remote login for one of the management ports, and now it won't get an IP address, on the summary page it only recognises 1 management port in out-of-band. Â I've tried to allow DHCP again to give the IP, but it gives a 192.168.120.101 IP, whereas my subnet is 192.2.12.x. Â Â Â i can't remove the 'remote login' as it says the port isn't configured as out-of-band, and i must do that first. Â Â I've countless times tried to search for the RAID controller, but nothing works. Â Â How do i get the management port/raid controller to be recognised again, so that i can remove the 'remote login' option?
2. I'm not able to add any hosts. Â do i need to do anything on each host? maybe with this initiator? that i've pre-req installed - any config needed for each server?
any ideas?
How can i reset the array back to factory settings???
Are your servers running windows? is this your first time using ISCSI?
If so install the windows iscsi initiator then open it and click on discovery click add and pop the ip address of the MD3000i in there. You should now see the disks in the targets tab click the disk you want and click logon






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
http://support.dell.com/support/edocs/systems/md3000i/

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Controller 0, Port 0: IP: 192.168.130.101
Controller 0, Port 1: IP: 192.168.131.101
Controller 1, Port 0: IP: 192.168.130.102
Controller 1, Port 1: IP: 192.168.131.102
This is the first time i've used iSCSI, so yes do need to configure each Initiator on each host, one of the hosts is server 2008, the other two are windows 2003.
I'm not able to do what you ask in the intiator discovery tab as i don't know what the management port IP addresses are, it's not accepting 192.168.128.101 or x.x.x.102 and the DNS/DHCP isn't showing the MD3000i SAN listed.
I'm not physcially present, so i must need to force a reset of the SAN hardware.
I would like to know how to start again from fresh with the knowledge i now have I'm confident i won't breka it again! Â How do i reset to factory default settings?
looks like it needs a hardware reset. Â :S






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
I'll find out if this is correct...
Two switches, both iSCSI ports being plugged in each switch.
The two management port,s 1 being plugged into each switch.
1 host, with two NIC, plugging into each switch.
Isolated away from rest of network, so no access to DHCP/DNS.
1 host NIC's IP configured as same subnet as the management ports:
192.168.128.10
subnet: 255.255.0.0
management ports are 192.168.128.101 and 192.168.128.102
I've set the subnet to 255.255.0.0, so as the iSCSI initiator can see the ports. Â
On the host, i've configured the iSCSI initiator, on Discovery new portals by adding each of the 4 RAID IPs:
RAID controller 0:
192.168.130.101
192.168.131.101
RAID controller 1
192.168.130.102
192.168.131.102
ok...the next problem i have is when i plug the SAN into my network, my network slows to a crawl and dies!. ouch!
I believe this is related to JUMBO mtu packet sizes of 1500 and i believe they should be at 9000. Â this being set on each hosts' NIC cards.
Can you confirm this, what's your expereince with JUMBO mtu packet sizes?

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Windows Server 2003
--
Questions
--
Followers
Top Experts
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).