Start a Conversation

Solved!

Go to Solution

788

July 12th, 2022 12:00

M1000e and Cisco B22 switch

Hi,

I got a used M1000e chassis. Everything works fine, except that the blades don't have network access.  The chassis has two Cisco Nexus B22 FEX switches, and I think I must configure the switch, but if I try to connect to it, it fails:

$ racadm connect -m switch-1
connect: switch-1 does not support console redirection

The switch itself does not have a physically accessible serial console.  

Can anyone tell me, how to access the switch?

Thanks,
Istvan

4 Operator

 • 

2.7K Posts

July 13th, 2022 06:00

Hello @bk7ycy


A Cisco Nexus B22 on a MD1000e does not support console redirection. The Cisco Nexus B22 Fabric Extender for Dell is managed by its parent Cisco Nexus switch over the fabric interfaces through a zero-touch configuration model. For example, you can upgrade the Fabric Extender by upgrading the software on the parent Cisco Nexus switch. A Fabric Extender is connected to the switch through physical Ethernet interfaces or an EtherChannel.


Check this guide, Cisco Nexus B22 Fabric Extender Getting Started Guide: 
https://dell.to/3AKCRum


Dell™ PowerEdge™ M1000e Systems Configuration Guide: https://dell.to/3uKDEYA

 

Regards.

Moderator

 • 

3.2K Posts

July 13th, 2022 00:00

Hi @bk7ycy,

 

Try connect switch-n instead. 

 

Reference: https://dell.to/3PpHcHu

 

Reference for B22: https://dell.to/3PmSxbw

3 Posts

July 13th, 2022 03:00

Thank you for your answer. If I understand correctly, the number of the appropriate device must be substituted for n in the "connect switch-n" command.  I tried issuing the commands below, but none of them helped:

$ connect switch-n
ERROR: The syntax of the command specified is not correct.
$ racadm connect switch-n
ERROR: The syntax of the command specified is not correct.
$ connect switch-1
connect: switch-1 does not support console redirection
$ radacm connect switch-1
Unsupported command
$ racadm connect -m switch-n
ERROR: The syntax of the command specified is not correct.
$ racadm connect -m switch-1
connect: switch-1 does not support console redirection

(switch-2 does the same)

I think "connect switch-1" or "racadm connect -m switch-1" would be the right command but it still doesn't work for some reason.  I don't know why the switch doesn't support console redirection, and how to get it to support it.

I can't find any settings for the switch either in the cms gui or the racadm commands. I can list the switches among the I/O modules, but I can't set anything.

$ getmodinfo -m switch-1

Switch-1 Present ON OK 
$ getmodinfo -m switch-2

Switch-2 Present ON OK 

Thank you,
Istvan

3 Posts

July 13th, 2022 16:00

Thank you @DiegoLopez!

Do I understand correctly, that the Cisco Nexus B22 switch is not viable by itself, because I have to put a Cisco Nexus 5500 switch in front of it? Instead of this, Can I replace the B22 with another switch module that works on its own without additional switches? For example, would a "Cisco Catalyst Blade Switch 3130 for Dell M1000E" switch be suitable instead of the B22? This would be a much more cost-effective solution.


Are the two identical switches only necessary for redundancy, and would it be functional with just one, or do I need to put two Cisco 3130 Catalyst switches in the chassis?

Thank you,
Istvan

Moderator

 • 

3.2K Posts

July 13th, 2022 21:00

Hi @bk7ycy,

 

Yes, the parent switch is Cisco Nexus 5500 series of switches. 

 

Well, it would be functional just as one switch. 2 switch configuration is best for redundancy, agreeable to your point. 

No Events found!

Top