Unsolved
4 Posts
0
1479
Dell M1000e Beginner
Hi Everyone,
I've inherited a Dell M1000e Blade Chassis with 4x M910 (Slots 1-4), 3x M710 (Slots 5-7), 2x M6348 (A1/A2) switches and 2x M5424 Brocades (C1/C2) installed.
I'm completely new to Blade Servers and I'm struggling to get started.
I've factory reset everything. I've got the CMC and iDrac web interfaces working. I've installed MS Hyper-V server on each of the blades, via console sessions. The M6348 in Slot A1 is connected to a BT Business Hub router via ethernet on port 33.
Now, I'm stuck.
I assumed the M6348 would start off working like a dumb-switch. I thought that with port 33 connected then I would be able to assign an IP address to the NICs on Blade 1 (Internal ports 1 & 9) and carry on as normal. Unfortunately, although I can start a console session, the blade is unable to access the network and vice-versa.
Right now I don't need to do anything fancy with the networking. I simply want to be able to have traffic move freely through the M6348 to the Blades so I can get the basics up and running.
If anyone can give me some tips or pointers I would be incredibly grateful.
If you're feeling generous and can give me a step-by-step guide I'd be over the moon.
Thanks!
Dell-DylanJ
4 Operator
4 Operator
•
2.9K Posts
0
December 17th, 2019 14:00
Since you can get into the switch console, you might look at the config to make sure the ports are coming up as expected, or more importantly, that there isn't anything unexpected showing up. Below is what you'd want to run in the shell.
The M6348 is an 1GbE switch, so you have them in the right spots in the chassis. Switch config is the next thing I'd be inclined to look at.
DELL-Rey G
3 Apprentice
3 Apprentice
•
944 Posts
0
December 18th, 2019 11:00
here is a link to a bunch of docs for the M6348, in case you havnt seen them:
https://www.dell.com/support/home/us/en/04/product-support/product/powerconnect-m6348/docs
I would highly suggest this doc, starting at page 123 thru 142.
https://downloads.dell.com/manuals/common/powerconnect-m6220_user%27s%20guide_en-us.pdf
I would think the blades would be configured correctly, but just to be sure, you have an integrated nic in the blades for communication with the A1/A2 IOMs? There could also be a mezzanine card in B and C sockets.
#Iwork4Dell
djb000m
4 Posts
0
December 30th, 2019 04:00
Hi Dylan,
Thanks for replying. I'm currently running the switch in Simple Mode, here's the output of show running-config:
Does anything look odd here? I haven't changed any settings other than network access, it's running the startup-config.
The status page shows ports 1, 9 & 33 connected on Slot A1. I would expect this as there are two physical NICs on each M910 blade and, I believe, the internal switch ports (1 & 9) are linked to the external port 33.
djb000m
4 Posts
0
December 30th, 2019 06:00
Hi Rey,
Thanks for the link. I have worked my way through those pages as suggested but I think I must still be doing something wrong.
Here's a summary of what I have configured:
I still get "destination host unreachable" when trying to ping into the Hyper-V Blade, or trying to ping out of it. All machines involved are configured with static IP addresses on the 192.168.1.0/24 subnet.
I believe there are two integrated NICs per blade configured to use the A1 IOM.
I also have two Brocade M5424s in C1/C2, if that makes a difference?
djb000m
4 Posts
0
January 6th, 2020 00:00
Thanks for your help guys but it turns out that my issue was hardware-related and nothing to do with my switch configuration. For those interested in the hardware issue, it was a faulty fibre optic cable.
I've returned to my previous configuration and everything is working great.