N3048 Issue

Question

Hi Folks! We have Switches N3048 stacked we almost have 15 Stack each stack has 7 Switches. I am facing issue with the stacks. Sometimes the stack get stucked and lose the connectivity and lose the configuration. I have to copy the configuration again and reload the stack to work fine it happens often. The Switch Firmware is : 6.5.3.36 I copy the Error when i try to Access the Stack: User:disc ERR: Timeout occurred <187> Jan 13 07:51:22 N3048-1 DRIVER[bcmDISC]: disc.c(1311) 1852766 %% ER R disc ERR: Timeout occurred <187> Jan 13 07:51:22 N3048-2 DRIVER[unitMgrTask]: disc.c(1311) 1852768 % % ERR disc ERR: Timeout occurred <187> Jan 13 07:51:22 N3048-2 DRIVER[unitMgrTask]: broad_stack_mgr.c(2418 ) 1852769 %% ERR Stack Manager: Discovery failed due to timeout, restarting disc overy process <187> Jan 13 07:51:22 -N3048-1 DRIVER[bcmDISC]: broad_stack_mgr.c(2418) 18 52769 %% ERR Stack Manager: Discovery failed due to timeout, restarting discover y process User:RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80. <187> Jan 13 07:51:28 -N3048-2 DRIVER[unitMgrTask]: atp.c(3929) 1852770 %% ERR ATP: TX timeout, seq 41141. 11:80 cli 778. to 1 tx cnt 21.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.ATP: TX timeout, seq 16913. 10:80 cli 778. to 1 tx cnt 21. <187> Jan 13 07:51:29 -N3048-1 DRIVER[bcmATP-TX]: atp.c(3929) 1852771 %% E RR ATP: TX timeout, seq 16913. 10:80 cli 778. to 1 tx cnt 21.RPC - Timeout to CPU: 88:6f:d4:9c:10:80. User:User:User:User:RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.RPC - Timeout to CPU: 88:6f:d4:9c:10:80.

DELL-Tim G · Accepted Answer

In this case you can run the advanced feature set OS6 for N3000E:

https://www.dell.com/support/home/en-us/product-support/product/networking-n3000e-on/drivers

You may choose between 6.6.0.54 (stable N-1) or latest 6.6.3.36.

Cheers,

Tim

DELL-Tim G · Answer

Hello Mrfall,

I'm sorry but your stacks are hitting a software issue which was addressed since 6.5.4.10.

Please look for bug ID FIELD-3617 in the release notes and upgrade your stacks to latest version 6.5.4.15:

https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=m76mm

Regards,

Tim

DELL-Josh Cr · Answer

Hi Mrfall, It allows the switch to match the features of the N3121PX-ON so they can be stacked together.

Mrfall · Answer

Thanks For you Help. I have another Question

what is the Different between :N3000AdvLitev6 Firmware and N3000Advv6.

I sawy the ADVLiteV Support only : 8 Stack with 1024 Vlans

but N3000Advv6. Support 12 Stack with 4093

Mrfall · Answer

so what’s the firmware i have to download for N3000 to solve my issue please

DELL-Tim G · Answer

Hi Mrfall,

we have 3 versions of OS6 with different feature set to match each hardware platform:

Standard: N2000, N2100

AdvancedLite: N3000

Advanced: N3000E, N3100

If your N3048 switches are the "non-E" versions please use the image N3000AdvLitev6.5.4.15.stk I linked before.

Everything else is only needed if you mix different hardware version in a stack:

https://www.dell.com/support/kbdoc/en-us/000144404/n-series-6-5-mixed-stacking-technical-update

Regards,

Tim

Mrfall · Answer

I am really appreciate your help. My switches is N3048-E ON. We will not mix the stack. Can you please give me the firmware for Adv not lite. Thanks

DELL-Stefan R · Answer

Hi,

please use the one Tim provided (https://dell.to/3p2eLCY).

If you need instructions on how to upgrade to advanced follow the instructions in the "Upgrading Dell Networking N3000 Series Switches From Version 6.x.x.x to Version 6.5.4.15.pdf".

Note from the firmware page:

Administrators configuring mixed stack with N3000 Series switches and N3132PX-ON MUST follow the instructions documented in the "Upgrading Dell Networking N3000 Series Switches From Version 6.x.x.x to Version 6.5.4.15.pdf". It is strongly recommended to backup current switch configuration before forming mixed stacking.

As Tim mentioned: "Everything else is only needed if you mix different hardware version in a stack..."

BR
Stefan

Networking General

Was this post helpful?