Start a Conversation

Unsolved

This post is more than 5 years old

3620

March 20th, 2017 03:00

MXL-10/40GbE Management Interface

Dear,

I'm migrating all of my network to a new MNGT subnet.

I have 4 MXL-10/40GbE in a M1000e chassis.

The aim is to change the magenement interface ip address + GW management to the new network but when i do it i loss the connectivity.

This is normal because my new MNGT vlan have a TAG and so i would like to link the ethernet management 0/0 interface of each MXL to an access port in the new MNGT vlan.

The question is how to find the interface connected to it ?

And is it possible to change the VLAN 1 for mngt to another one ?


SAASRFW07#show interfaces switchport

Codes: U - Untagged, T - Tagged
x - Dot1x untagged, X - Dot1x tagged
G - GVRP tagged, M - Trunk, H - VSN tagged
i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT ta gged

Name: TenGigabitEthernet 0/1
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400,500

Native VlanId: 1.

Name: TenGigabitEthernet 0/2
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400,500

Native VlanId: 1.

Name: TenGigabitEthernet 0/3
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400,500

Native VlanId: 1.

Name: TenGigabitEthernet 0/4
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/5
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/6
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/7
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/8
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/9
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/10
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/11
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/12
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/13
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/14
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/15
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/16
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/17
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/18
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/19
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/20
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/21
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/22
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/23
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/24
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/25
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/26
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/27
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/28
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/29
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/30
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/31
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/32
802.1QTagged: Hybrid
Vlan membership:
Q Vlans
U 1
T 400

Native VlanId: 1.

Name: TenGigabitEthernet 0/49
Description: to Compellent 30386 S1P1
802.1QTagged: True
Vlan membership:
Q Vlans
T 400

Name: TenGigabitEthernet 0/50
Description: to Compellent 30386 S2P1
802.1QTagged: True
Vlan membership:
Q Vlans
T 400

Name: TenGigabitEthernet 0/51
Description: to Compellent 30387 S1P1
802.1QTagged: True
Vlan membership:
Q Vlans
T 400

Name: TenGigabitEthernet 0/52
Description: to Compellent 30387 S2P1
802.1QTagged: True
Vlan membership:
Q Vlans
T 400

SAASRFW07#show interfaces status
Port Description Status Speed Duplex Vlan
Te 0/1 Up 10000 Mbit Full 1,400,500
Te 0/2 Up 10000 Mbit Full 1,400,500
Te 0/3 Up 10000 Mbit Full 1,400,500
Te 0/4 Down Auto Auto 1,400
Te 0/5 Down Auto Auto 1,400
Te 0/6 Down Auto Auto 1,400
Te 0/7 Down Auto Auto 1,400
Te 0/8 Down Auto Auto 1,400
Te 0/9 Down Auto Auto 1,400
Te 0/10 Down Auto Auto 1,400
Te 0/11 Down Auto Auto 1,400
Te 0/12 Down Auto Auto 1,400
Te 0/13 Down Auto Auto 1,400
Te 0/14 Down Auto Auto 1,400
Te 0/15 Down Auto Auto 1,400
Te 0/16 Down Auto Auto 1,400
Te 0/17 Down Auto Auto 1,400
Te 0/18 Down Auto Auto 1,400
Te 0/19 Down Auto Auto 1,400
Te 0/20 Down Auto Auto 1,400
Te 0/21 Down Auto Auto 1,400
Te 0/22 Down Auto Auto 1,400
Te 0/23 Down Auto Auto 1,400
Te 0/24 Down Auto Auto 1,400
Te 0/25 Down Auto Auto 1,400
Te 0/26 Down Auto Auto 1,400
Te 0/27 Down Auto Auto 1,400
Te 0/28 Down Auto Auto 1,400
Te 0/29 Down Auto Auto 1,400
Te 0/30 Down Auto Auto 1,400
Te 0/31 Down Auto Auto 1,400
Te 0/32 Down Auto Auto 1,400
Fo 0/33 Down 40000 Mbit Auto --
Fo 0/37 Down 40000 Mbit Auto --
Te 0/41 Down Auto Auto --
Te 0/42 Down Auto Auto --
Te 0/43 Down Auto Auto --
Te 0/44 Down Auto Auto --
Te 0/45 Down Auto Auto --
Te 0/46 Down Auto Auto --
Te 0/47 Down Auto Auto --
Te 0/48 Down Auto Auto --
Te 0/49 to Compelle Up 10000 Mbit Full 400
Te 0/50 to Compelle Up 10000 Mbit Full 400
Te 0/51 to Compelle Up 10000 Mbit Full 400
Te 0/52 to Compelle Up 10000 Mbit Full 400
SAASRFW07#

Thanks for your help,

25 Posts

March 20th, 2017 08:00

Ok perfect, many thanks, i'll try it on tomorrow and keep you informed.

5 Practitioner

 • 

274.2K Posts

March 20th, 2017 08:00

 

The management interface is an OOB interface which connects through the chassis CMC. Traffic on this port is segregated from operational network traffic on the switch ports and cannot be switched or routed to the operational network.

 

The CMC has two Ethernet ports: Gb1 is used to connect to the external management network. Gb2 will allow CMCs in adjacent enclosures to be daisy-chained.

 

I believe you should be able to telnet/ssh to any VLAN with an IP Address assigned to it. If you wanted to create a new VLAN, assign it an IP Address, you should then be able to connect to that IP Address.

25 Posts

March 20th, 2017 08:00

Ok thanks for your reply.

So, if i understand, the management ethernet 0/0 of each MXL switch is using the CMC Gb1 / Gb2 of the chassis.

My topology is as below:

CMC M1000E IDRAC IP ADDRESS:10.150.0.10/24 (MNGT SUBNET)

CMC M1000E GB1 <--->MNGT Switch Gi1/0/3 (switchport access vlan MGNT_VLAN_ID)

CMC M1000E GB2<-->MNGT Switch Gi2/0/3 (switchport access vlan MGNT_VLAN_ID)

So, i should be able to change the management ethernet 0/0 interface of each MXL switch for a 10.150.0.x/24 ip address ?

25 Posts

March 20th, 2017 08:00

I forgot, one last question,...

I have 2 M820 blades in this chassis, i think, it's the same ? IDRAC of the blades M820 is going through GB1 ?

5 Practitioner

 • 

274.2K Posts

March 20th, 2017 08:00

Yes, you should be able to make that IP Address assignment. GB2 of the CMC is used only for daisy chaining Enclosures, not for connections to switches. GB1 of the CMC is what will carry to management traffic out to your management switch.

5 Practitioner

 • 

274.2K Posts

March 20th, 2017 08:00

That is correct, iDRAC traffic uses that interface as well.

25 Posts

March 20th, 2017 09:00

ok thanks and so... as i changed the IDRac IP Address of the GB1 M1000e... i lost the connectivity to my M820 blades ...

How is it possible to configure the M820 iDRAC ip address on M820 by using a console cable or other ?

25 Posts

March 20th, 2017 09:00

Yes, but i'm trying doing it for the MXL mngt by using SSH on idrac and setniccfg / getniccfg:

setniccfg -m switch-1 -s 10.150.0.25 255.255.255.0 10.150.0.254

setniccfg -m switch-2 -s 10.150.0.26 255.255.255.0 10.150.0.254

setniccfg -m switch-3 -s 10.150.0.27 255.255.255.0 10.150.0.254

setniccfg -m switch-4 -s 10.150.0.28 255.255.255.0 10.150.0.254

$ getniccfg -m switch-1
DHCP Enabled = 0
IP Address = 10.150.0.25
Subnet Mask = 255.255.255.0
Gateway = 10.150.0.254
$ getniccfg -m switch-2
DHCP Enabled = 0
IP Address = 10.59.200.6
Subnet Mask = 255.255.0.0
Gateway = 10.59.1.254
$ getniccfg -m switch-3
DHCP Enabled = 0
IP Address = 10.59.200.7
Subnet Mask = 255.255.0.0
Gateway = 10.59.1.254
$ getniccfg -m switch-4

DHCP Enabled = 0
IP Address = 10.59.200.8
Subnet Mask = 255.255.0.0
Gateway = 10.59.1.254

Do you know what it only works for the first MXL switch ?driving me crazy

5 Practitioner

 • 

274.2K Posts

March 20th, 2017 09:00

While making changes like these, a serial connection will probably be the best solution.

http://dell.to/2neBMVX

5 Practitioner

 • 

274.2K Posts

March 20th, 2017 09:00

I am not sure why it is only taking the first one. Are there any messages logged on the switches? Perhaps try making these changes why on the switch CLI?

http://dell.to/2nW7mEY

25 Posts

March 20th, 2017 10:00

nope, no error and as i managed to be able to reach the CMC1000e iDrac by web, i tried it by using the web interface and idrac told me that it'll take a moment.. don't know why,,, maybe a propagation time, i don't know..

And in the CMC Job queue interface, nothing present..

25 Posts

March 21st, 2017 02:00

hi,

I did it with the console cable and no issue, everything works fine !

Thanks at all,

5 Practitioner

 • 

274.2K Posts

March 21st, 2017 06:00

Excellent! glad to hear that worked.

Cheers

No Events found!

Top