Need help setting up Dell Powerconnect 7048p

I am very new to this switch. I need help setting up multiple vlans and the management vlan


I currently have many servers and many clients on the same subnet.  192.168.100.0

With the switch i want to make a vlan for
iSCSI traffic 192.168.110.0    12 ports
Servers  192.168.100.0  12 ports
Clients  192.168.120.0 12 ports

The seitch management traffic, how do i do this,really ont care what the ip is as this is the only swich on the network but im at a loss as to how to configure everything and still have the clietn traffic get to the servers and managment

I have more than 12 client computers but i also have several unmagaged switches that the clients connect in to.

how do i start, all my attempts have failed.  I was able to run the wizard to set the management ip to 192.168.100.99 and get the web interface but once i start to configure stuff i loose connection.


Help
LVL 1
mcrmanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

schapsCommented:
The step from a flat network to one of multiple VLANs with routing between is a huge step, so take it slowly. First, consider if you really need to do this. It sounds like you have well under 100 client/server devices. If the goal is to increase security, to segregate client devices from servers and control access, then this would be a good reason. If, however, your intent is to increase network speed and efficiency, with that few devices you are likely to see no noticeable improvement. If you wanted multiple client VLANs which could not communicate (for security reasons) with each other but still share resources, that's another reason to do this. But this huge step increases the complexity of your network, which increases the potential things which can go wrong and correspondingly makes troubleshooting more difficult.

OK, but if you want to go through with this, start small:
I assume the 192.168.100.0/24 network is VLAN 1 (Default VLAN). That is fine. Let's learn to crawl before we walk. For the time being, VLAN 1 should remain untagged on all ports except two that we'll practice VLANs with. Leave port 1 as the server VLAN (untagged VLAN 1), port 2 untagged for the client VLAN, and port 3 untagged the iSCSI VLAN. I assume you are intending to do the routing between VLANs with this switch, you do not have a router set for VLAN routing. You also need to have a DHCP server on each VLAN or configure the switch's "DHCP Relay," but you still need to set up DHCP scopes for each VLAN on whatever server or router you currently use to do DHCP.
The point here is that you only need to mess with the settings on these three ports and three computers plugged into them until you have everything working properly.
What do you think of this so far?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mcrmanAuthor Commented:
OK, lets Walk.  Lets also simplify this a little further.

2 VLans with no routing between them.

You assume right Vlan1 is for the 192.168.100.0 network, this is where all the servers and clients belong.  Ports 1-24

The ISCSI vlan2 will be used for ISCSI traffic only.   This is 192.160.110.0  Ports 25-48

I have binded the IP ranges to the vlans.

Is this all i need to do? it does seem to be working.
0
schapsCommented:
You mean everything is working accessing iSCSI from the client VLAN?
Do you need 24 ports for iSCSI nodes?
0
mcrmanAuthor Commented:
No the ISCSI traffic is segregated from client traffic.   Only my VMware environment will have access to the ISCSI targets,

I had to remove the Bind IP Subnets from the vlans.  


But its working.
0
mcrmanAuthor Commented:
Thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Hardware-Other

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.