Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
New VNXe3300 install network issues
Hello all, we got a new VNXe3300 Friday and got down to business to install the unit. Having an NS-120FC already, I did a similar setup.
The management interface and the two nics are connected on the main core swtich/lan with ip 192.168.0.219 so no issues there.
The 4 cards on SPA are connected to a separate physical switch isolated form the 192.168.0.0/24 network. The SP's are connected as follows:
| SP's | PORT | SWITCH |
|---|---|---|
| SPA eth2 | 13 | SW1 |
| SPA eth3 | 14 | SW1 |
| SPA eth4 | 15 | SW2 |
| SPA eth5 | 16 | SW2 |
| SPB eth2 | 13 | SW1 |
| SPB eth3 | 14 | SW1 |
| SPB eth4 | 15 | SW2 |
| SPB eth5 | 16 | SW2 |
Then I aggregated the links from all 4 nics into eth2 I guess and gave it the IP of 172.16.1.20.
Here is where the problem begins. It asks for a gateway IP and there is really none that exist as those are two separate physical LAN's. So I tried with both 192.168.0.254 or with 172.16.1.1 (which are the correct one's for each physical switch).
Now on the VMware site I already have a vmkernel working with 172.16.1.10 and the Celerra so I should be able to vmkping the 172.16.1.20 of the VNX, but no luck.
I opened a case with support and besides having to call myself to follow up after 5 hours a nice lady from overseas told me first this is not a supported config, then that I had DNS problem, then she was going to reseach until I finally gave up with her.
Is this supposed to work, I am already running the latest release from 7/18/11.
Regards,
Paul
I was jsut trying to find out if separating the management network and the storage nics was possible. To my surprise after opening a call with EMC I was not able to get this simple answer.
I have a stack brocade swiitch and it acts as one switch based on the doc information from above and it is working fine. As you pointed out all 4 nics on the e3300 are on one LACP group only, but it is spread across two switches acting as one.
Last Friday night I opened the call at 6:30 PM EST. By today Monday three days after I got such ridiculous answers as that I had DNS problems and even that I needed to integrate it with Active Directory.....
Really hope support for the VNX gets better...
Regards,
Paul
michael_khadra
17 Posts
517
0
Posted August 1st, 2011 00:00
So let me summarize the issue:
- You have connected the management port of the storage processors to the core switcha and gave the IP 192.168.0.219 for the VNXe to be used by Unisphere for management.
- You have aggregated the 4 ethernet ports on SP A and connected them to one switch (2 stackable switches acting as one), using an LACP etherchannel
- You have aggregated the 4 ethernet ports on SP B and connected them to that same switch, using an LACP etherchannel.
You created an iSCSI server and associated it with the SP A ethernet 2 interface, and gave it an IP of 172.16.1.20
When you say, it is asking for a gateway, could you specify on which screen is that? The only place where it asks for a gateway is in the initial setup when you configure the management IP which is in your case the 192.168.0.19, during the VNXe automatic discovery.
When creating the iSCSI server, it only asks for an IP address, a mask, storage processor to be used, and ethernet port to be used on that SP and optional VLAN ID.
jablonde
9 Posts
517
0
Posted July 25th, 2011 14:00
You can't use multiple LAG groups with the onboard NICs. You can only setup a single LAG group which means you are limited to using a single subnet for the NICs. Which, in turn, makes having a second switch pointless. I learned this only after purchasing the unit and spending much time with EMC support.
If you want to use a 2nd switch, then you need to purchase the additional IO Modules. Then you can create a LAG w/ the onboard NICs and then a 2nd LAG with the IO Module NICs. Each of those LAGs would be plugged into separate switches, then assign an IP address to each LAG, and finally assign them to your iSCSI Server.