Issue with a Dell N4032F switch

Have you tried in config mode:
interface po50
no shutdown

Or issue the above commands on the physical interfaces who are member of Po50?

Hi Daniel,

Thanks for your reply!  I've decided that the problem lies elsewhere!  This port channel was (I think) left over from when the equalogic was first replicated to the DR site.  At the moment I'm struggling to  understand why a simple trunk between a Cisco 3750 and a Dell N4032F is not working...... Its part of the same problem.

This is the config of the dell port:

interface Te1/0/21
switchport mode general
switchport general acceptable-frame-type tagged-only
switchport general allowed vlan add 5 tagged
switchport access vlan 5
switchport trunk allowed vlan 5
no lldp tlv-select dcbxp ets-config
no lldp tlv-select dcbxp ets-recommend
no lldp tlv-select dcbxp pfc
no lldp tlv-select dcbxp application-priority
exit

This is the cisco port:

GigabitEthernet4/0/11 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 1ce6.c7ee.670b (bia 1ce6.c7ee.670b)
  Description: *** TRUNK to Dell iSCSI 02 te1/0/21 ***
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:24, output 00:00:11, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1000 bits/sec, 1 packets/sec
  5 minute output rate 1000 bits/sec, 1 packets/sec
     534610 packets input, 35812772 bytes, 0 no buffer
     Received 534610 broadcasts (534577 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 534577 multicast, 0 pause input
     0 input packets with dribble condition detected
     1473264 packets output, 178337074 bytes, 0 underruns
     0 output errors, 0 collisions, 4 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

Im wondering if the problem is we don't have vlan association on the Dell.... I cant find a command that will display this info.

Thanks for your advice so far!

I will try that and post my result

Thanks!

Didn't make any difference but thanks for the suggestion!

There are lights on the port Daniel yes!  Is this the part number you are referring to?

SOC Hardware Info :............................ BCM56842_A1

Ah ok!  We seem to be using Startech spf's.  I have swapped it for another just to see and the switch rebooted .......Its back up but worried there is something deeper going on now.  I am heading hoem now but will update the thread with any progress.  Thank you for your help so far!

Cheers Daniel,

Not looking good....

<190> Jul  6 20:30:03 0.0.0.0-1 UNITMGR[Cnfgr_Thread ]: unitmgr_status.c(153) 13 %% StatusInit: init done
<185> Jul  6 20:30:02 0.0.0.0-1 SIM[Cnfgr_Thread ]: sim_util.c(3789) 12 %% Switch was reset due to software initiated exit.
<186> Jul  6 20:30:02 0.0.0.0-1 General[fp_main_task]: bootos.c(195) 11 %% Event(0xaaaaaaaa)
<189> Jul  6 20:30:02 0.0.0.0-1 BSP[fp_main_task]: bootos.c(179) 10 %% BSP initialization complete, starting switch firmware.
<190> Jul  6 20:30:02 0.0.0.0-1 OSAPI[fp_main_task]: osapi_crash.c(1236) 9 %% Oldest crashlog (5) will be deleted if another
crash happens.
<190> Jul  6 20:30:02 0.0.0.0-1 OSAPI[fp_main_task]: osapi_crash.c(1231) 8 %% 5 Crashlogs found.
<190> Jul  6 20:30:02 0.0.0.0-1 DRIVER[fp_main_task]: broad_hpc_stacking.c(2921) 7 %% FPS Stack unit/port 0/24 speed 10000 if
g 72 configured
<190> Jul  6 20:30:02 0.0.0.0-1 DRIVER[fp_main_task]: broad_hpc_stacking.c(2921) 6 %% FPS Stack unit/port 0/23 speed 10000 if
g 72 configured
<190> Jul  6 20:30:02 0.0.0.0-1 DRIVER[fp_main_task]: broad_hpc_stacking.c(1240) 5 %% Configuring CPUTRANS RX

Looks like it rebooted again overnight.  Bit worrying as this switch was apparently replaced a few months ago by Dell... Now I have more problems :) :(

Lost connectivity to the management interface and cannot telnet onto the switch either.........Can ping it but telnet and serial connections don't show any interface.  By that I mean I can connect but cannot see any text on the telnet session. :(

Hello,

what is the firmware version?

There were many new releases in last few months, fixing a lot of various issues, for example:

948938 N-Series-6.2.0.5-Member ports detach/attach from/to the port-channel interface.

(fixed in 6.3.0.6 http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=8V2TW&fileId=3549894568&osCode=NAA&productCode=networking-n4000-series&categoryId=NI )

1048238 6.3.0.6-N2000 Switch is non-responsive to management access (SSH/Console)

(fixed in 6.3.0.9 http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=YT1HD&fileId=3549894568&osCode=NAA&productCode=networking-n4000-series&categoryId=NI )

Few days ago I was unable to connect via SSH to the stack master on a stack of few N2000 - fortunately I was able to force failover via SNMP (snmpset with write community enabled on the switch),

which brought up a "fresh" management plane on a new master and I was able to login via SSH again.

If you create a support request probably the first thing they'll suggest would be a firmware upgrade.

Regards,

Jakub

Hi Daniel,

Thank you so much for your support!  My faith in the world has just been restored a bit :)  I have been off for a few days but back on the case now.  I will let you know where we are if that's ok.  I can get onto the management stack again after a reboot overnight.  Looks like over heating was causing them to fail!  We can now replicate with our DR site! Turns out it was a cabling issue........  Thanks again Daniel and stay well!

Thanks for your comment Jakub.  I have upgraded the firmware on the switch. to be fair, this is pretty much the first issue we have had with these devices.  Hopefully a one off :)

thanks for sharing