Start a Conversation

Solved!

Go to Solution

1 Rookie

 • 

9 Posts

23

April 18th, 2024 05:03

Issues Connecting Dell Powerconnect 8024 with PowerSwitch N2048

Hey,

I am currently working with two switches. The first is a Dell Powerconnect 8024, and the second is Dell PowerSwitch N2048. I am trying to get these switches to communicate ideally within the same subnet and vlan. I have tried the default vlan1 on both with access/trunk/general ports connecting the two and have not been able to get them to see each other. I've also tried moving both switches to vlan 10 again I cannot get them to see each other. Both switches are working with all the devices plugged into them I just cannot get the two switches to see each other when they are directly plugged into each other.

Current setup:

N2048: all ports on VLAN10 (192.168.2.3 /16), sfp+ 10GB port 2 is trunk mode tagged and uplink to 8024

8024:  all ports on VLAN10 (192.168.2.2 /16), sfp+ port 24 is trunk mode tagged and uplink to N2048

Switches are not sending traffic to each other.  Connecting via regular access ports also no traffic between them.

Add Bell GigaHub ONT, with 8024 and N2048 connected to it from a regular access port on each switch, and switches can send traffic to each other.  

*Note I've tried both tagged and untagged trunks, I have also tried tagged and untagged general ports none of these combinations will allow the two switches to send traffic to one another. The only way I've gotten them to see each other is through the Bell.*

Any help is really appreciated.

1 Rookie

 • 

9 Posts

April 26th, 2024 23:20

Thanks for all the help. Went through support and found the issue. There is some compatibility issue with my Bell Modem as it shows up as a STP loop and blocks the trunk. Once the modem is unplugged from the 8024 the two switches can communicate. 

Furthermore when the modem is plugged into the N2048 rather than the 8024 everything is working like I had hoped. Switches can communicate and see the internet through the trunk.

Thanks for the help

(edited)

Moderator

 • 

3.1K Posts

April 18th, 2024 08:40

Hi,

 

I'm that good with networking, so I talked to one of my networking support peeps, and he gave a simple configuration setup, hope this helps. He did mention also, get the switches firmware up to date. 

 

1 Rookie

 • 

9 Posts

April 19th, 2024 00:51

@DELL-Joey C​ Hi Joey,

Thanks for the quick response. I updated the firmware, boot code and CPLD on both switches. 

After that I tried what you stated with the ports in a LAG and without and neither configuration works. Ill attach my current configs on both switches and a diagram of what I want to achieve.

What I want to work but when I try this the switches cannot see each other:

The only way I can currently get it to work:

8024 Config: 

!Current Configuration:
!System Description "Powerconnect 8024, 5.1.18.1, VxWorks 6.6"
!System Software Version 5.1.18.1
!Cut-through mode is configured as disabled
!
configure
vlan 10
exit
vlan 10
name "VLAN10"
exit
stack
member 1 1    ! PC8024
exit
logging console emergencies
ip routing
interface vlan 1 1
exit
interface vlan 10 2
ip address 192.168.2.2 255.255.0.0
exit
username "root" password 5f4dcc3b5aa765d61d8327deb882cf99 privilege 15 encrypted
ip ssh server
!
interface Te1/0/1
switchport access vlan 10
exit
!
interface Te1/0/2
switchport access vlan 10
exit
!
interface Te1/0/3
switchport access vlan 10
exit
!
interface Te1/0/4
switchport access vlan 10
exit
!
interface Te1/0/5
switchport access vlan 10
exit
!
interface Te1/0/6
switchport access vlan 10
exit
!
interface Te1/0/7
switchport access vlan 10
exit
!
interface Te1/0/8
switchport access vlan 10
exit
!
interface Te1/0/9
switchport access vlan 10
exit
!
interface Te1/0/10
switchport access vlan 10
exit
!
interface Te1/0/11
switchport access vlan 10
exit
!
interface Te1/0/12
switchport access vlan 10
exit
!
interface Te1/0/13
switchport access vlan 10
exit
!
interface Te1/0/14
switchport access vlan 10
exit
!
interface Te1/0/15
switchport access vlan 10
exit
!
interface Te1/0/16
switchport access vlan 10
exit
!
interface Te1/0/17
switchport access vlan 10
exit
!
interface Te1/0/18
switchport access vlan 10
exit
!
interface Te1/0/19
switchport access vlan 10
exit
!
interface Te1/0/20
switchport access vlan 10
exit
!
interface Te1/0/21
switchport access vlan 10
exit
!
interface Te1/0/22
switchport access vlan 10
exit
!
interface Te1/0/23
duplex full
switchport access vlan 10
exit
!
interface Te1/0/24
duplex full
switchport mode trunk
switchport general pvid 10
switchport general ingress-filtering disable
switchport general allowed vlan add 10
switchport access vlan 10
exit
snmp-server engineid local 800002a203d067e576ae7d
enable password 5f4dcc3b5aa765d61d8327deb882cf99 encrypted
exit

N2048 Config:

!Current Configuration:
!System Description "Dell EMC Networking N2048, 6.7.1.22, Linux 4.14.174, Not Available"
!System Software Version 6.7.1.22
!
configure
vlan 10
exit
slot 1/0 2    ! Dell EMC Networking N2048
stack
member 1 3    ! N2048
exit
logging console emergencies
ip routing
interface vlan 1
exit
interface vlan 10
ip address 192.168.2.3 255.255.0.0
exit
username "root" password 5f4dcc3b5aa765d61d8327deb882cf99 privilege 15 encrypted
ip ssh server
application install SupportAssist auto-restart start-on-boot
!
interface Gi1/0/1
switchport access vlan 10
exit
!
interface Gi1/0/2
switchport access vlan 10
exit
!
interface Gi1/0/3
switchport access vlan 10
exit
!
interface Gi1/0/4
switchport access vlan 10
exit
!
interface Gi1/0/5
switchport access vlan 10
exit
!
interface Gi1/0/6
switchport access vlan 10
exit
!
interface Gi1/0/7
switchport access vlan 10
exit
!
interface Gi1/0/8
switchport access vlan 10
exit
!
interface Gi1/0/9
switchport access vlan 10
exit
!
interface Gi1/0/10
switchport access vlan 10
exit
!
interface Gi1/0/11
switchport access vlan 10
exit
!
interface Gi1/0/12
switchport access vlan 10
exit
!
interface Gi1/0/13
switchport access vlan 10
exit
!
interface Gi1/0/14
switchport access vlan 10
exit
!
interface Gi1/0/15
switchport access vlan 10
exit
!
interface Gi1/0/16
switchport access vlan 10
exit
!
interface Gi1/0/17
switchport access vlan 10
exit
!
interface Gi1/0/18
switchport access vlan 10
exit
!
interface Gi1/0/19
switchport access vlan 10
exit
!
interface Gi1/0/20
switchport access vlan 10
exit
!
interface Gi1/0/21
switchport access vlan 10
exit
!
interface Gi1/0/22
switchport access vlan 10
exit
!
interface Gi1/0/23
switchport access vlan 10
exit
!
interface Gi1/0/24
switchport access vlan 10
exit
!
interface Gi1/0/25
switchport access vlan 10
exit
!
interface Gi1/0/26
switchport access vlan 10
exit
!
interface Gi1/0/27
switchport access vlan 10
exit
!
interface Gi1/0/28
switchport access vlan 10
exit
!
interface Gi1/0/29
switchport access vlan 10
exit
!
interface Gi1/0/30
switchport access vlan 10
exit
!
interface Gi1/0/31
switchport access vlan 10
exit
!
interface Gi1/0/32
switchport access vlan 10
exit
!
interface Gi1/0/33
switchport access vlan 10
exit
!
interface Gi1/0/34
switchport access vlan 10
exit
!
interface Gi1/0/35
switchport access vlan 10
exit
!
interface Gi1/0/36
switchport access vlan 10
exit
!
interface Gi1/0/37
switchport access vlan 10
exit
!
interface Gi1/0/38
switchport access vlan 10
exit
!
interface Gi1/0/39
switchport access vlan 10
exit
!
interface Gi1/0/40
switchport access vlan 10
exit
!
interface Gi1/0/41
switchport access vlan 10
exit
!
interface Gi1/0/42
switchport access vlan 10
exit
!
interface Gi1/0/43
switchport access vlan 10
exit
!
interface Gi1/0/44
switchport access vlan 10
exit
!
interface Gi1/0/45
switchport access vlan 10
exit
!
interface Gi1/0/46
switchport access vlan 10
exit
!
interface Gi1/0/47
switchport access vlan 10
exit
!
interface Gi1/0/48
switchport access vlan 10
exit
!
interface Te1/0/1
switchport access vlan 10
exit
!
interface Te1/0/2
switchport mode trunk
switchport general pvid 10
switchport general ingress-filtering disable
switchport general allowed vlan add 10
switchport access vlan 10
exit
snmp-server engineid local 800002a203f48e384d6be0
enable password 5f4dcc3b5aa765d61d8327deb882cf99 encrypted
exit

Moderator

 • 

3.1K Posts

April 19th, 2024 07:22

Hi,

 

Based on your configuration, looks like the switchport mode is set to trunk and general. Can you try setting it to only trunk?

1 Rookie

 • 

9 Posts

April 19th, 2024 20:58

@DELL-Joey C​ 

Hey Joey thanks for the response; I think those were just residual changes I had made to the general setting on those ports. I reversed them, and the config for the two trunked switches now looks like this.

8024 

!
interface Te1/0/24
duplex full
switchport mode trunk
switchport access vlan 10
exit

N2048 

!
interface Te1/0/2
switchport mode trunk
switchport access vlan 10
exit

Again this is not working. I also tried just plugging the two switches together through separate RJ-45 ports set to access mode this also did not work.

On a side note, I've tested out both of the SFP+ ports I am trying to use they work and the DAC I am using for the Trunk also works.

I've even reset both switches to factory, and not configured them. This should allow me to connect any two ports and they see each other but this does not work.

I have no problem using vlan 1 if that makes things easier but I've tried it and it also does not work. My goal is to just get the two switches communicating with the same subnet.

(edited)

Moderator

 • 

3.1K Posts

April 22nd, 2024 01:44

Hi,

 

You might need to issue the command no shut to the interfaces. Also, you do not need to configure the switchport to access vLAN 10. 

 

8024 

!
interface Te1/0/24
duplex full
switchport mode trunk
no shutdown
exit

 

 

N2048 

!
interface Te1/0/2

duplex full
switchport mode trunk

no shutdown
exit

 

Let me know if this helped.

1 Rookie

 • 

9 Posts

April 22nd, 2024 02:29

@DELL-Joey C​ 

Hi,

Just tried that, Still nothing.

Moderator

 • 

3.1K Posts

April 22nd, 2024 07:29

Hi,

 

Weird. Ok, try using the front ports (1G), which you have tested before, but don't set it to access mode, but set it trunk mode. Once you have already done that and have same result with issue, do a show tech to let us check. 

1 Rookie

 • 

9 Posts

April 22nd, 2024 20:34

@DELL-Joey C​ ,

Hey Joey,

I did like you asked and trunked port 36 on the N2048, and port 16 on the 8024. It did not work so attached are the two 'show tech' files from each switch. I ran the show tech while the two new trunked ports were connected to each other. 

Thanks for the continued support.

<Private data removed from public view. DELL-Admin>

(edited)

Moderator

 • 

3.3K Posts

April 22nd, 2024 20:49

Hello,

 

We will get a look and follow up with you.

Moderator

 • 

3.1K Posts

April 23rd, 2024 03:06

Hi,

 

Checking on the logs, the 8024 looks like it's going to fail soon. Has fan and power censor issue. 

 

Since we're on port 16 8024 and port 36 N2048, both ports are unconfigured. Hence they would not be able to communicate. Please configure both ports as suggested in the first respond picture, and please do not add #switchport access vlan 10, it is not required. Eg:

 

interface Te1/0/36

duplex full
switchport mode trunk

switchport trunk native vlan 10

no shutdown
exit

 

1 Rookie

 • 

9 Posts

April 23rd, 2024 04:21

Hey,

Please ignore the warnings from the 8024, I had some fan failures and have temporarily swapped them with 'incompatible fans' I have ordered replacements to fix the warnings. The temps are not any higher than expected.

 On my previous post the N2048 has port Gi1/0/36 Configured as such:

interface Gi1/0/36

switchport mode trunk

switchport access vlan 10

exit

And the 8024 has port Te1/0/16 Configured as such:

interface Te1/0/16

switchport mode trunk

switchport access vlan 10

exit

I'm not sure how they are showing up as unconfigured as in the show tech files they both have these settings in the section titled 'Show Running Config'

I'd also note I found in the files some sort of communication as shown in sections below from the 8024 file it recognizes the N2048 by name and port:

 ***************** Show ISDP Neighbors *****************

 

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge,

                  S - Switch, H - Host, I - IGMP, r - Repeater

Device ID              Intf         Holdtime  Capability   Platform             Port ID

---------------------- ------------ --------- ------------ -------------------- ----------------------

CN0DMD5F282986950329A0 Te1/0/16     178       R            N2048                Gi1/0/36

 

 

 ***************** Show LLDP Remote-device All ***********

 

LLDP Remote Device Summary

 

Local

Interface RemID    Chassis ID            Port ID             System Name

-------  -------   --------------------  ------------------  ------------------

Te1/0/1    4       5C:E9:31:07:E8:AF     5C:E9:31:07:E8:AF

Te1/0/2

Te1/0/3

--More-- or (q)uit

Te1/0/4

Te1/0/5    2       WIN11X64-MA           5C:E9:31:3C:CE:CB

Te1/0/6    12      WIN11X64-MO           5C:E9:31:07:E8:65

Te1/0/7    3       5C:E9:31:07:E6:74     5C:E9:31:07:E6:74

Te1/0/8

Te1/0/9

Te1/0/10

Te1/0/11

Te1/0/12   14      DESKTOP-2CH45I4       E0:DB:55:E0:BF:49

Te1/0/13

Te1/0/14

Te1/0/15

Te1/0/16   13      F4:8E:38:4D:6B:E0     Gi1/0/36

Te1/0/17

Te1/0/18

Te1/0/19

Te1/0/20

Te1/0/21

Te1/0/22

Te1/0/23

Te1/0/24

Again this recognition by name and port can be seen in the N2048 file:

***************** Show Isdp Neighbors *****************

 

Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge,

                  S - Switch, H - Host, I - IGMP, r - Repeater

Device ID                Intf      Holdtime  Capability Platform         Port ID

------------------------ --------- --------- ---------- ---------------- ---------

CN0Y295K2829823N0001A05  Gi1/0/36  163       R S        PC8024           Te1/0/16

 

 

 ***************** Show Lldp Remote-device All ***********

 

LLDP Remote Device Summary

 

Local

Interface RemID   Chassis ID          Port ID           System Name

--------- ------- ------------------- ----------------- ------------------

Gi1/0/14  5       192.168.2.10        1C:1D:86:01:9B:F2 CISCO ATA SPA122

Gi1/0/33  15      DESKTOP-2CH45I4     E0:DB:55:E0:BF:49

Gi1/0/36  16      D0:67:E5:76:AE:7D   Te1/0/16

As requested I have removed the #switchport access vlan 10 from both of these ports and tried again to no avail. I will attach the two new tech files below. I will keep both sets up. The new ones have the suffix '2nd Tech'.

The only configuration change between the two files is the removal of access vlan 10; and running 'switchport trunk native vlan 10' . I ran through each of the commands again and checked each interface to ensure they stuck; and as can be seen in the configuration section of the tech files they are set to trunk for both runs. I issued the no shutdown command even though it seems to not show up in the config (I think because that is the default setting).

https://drive.google.com/drive/folders/14UjTFgmgklpqIHRf5k_ueqTEsCZDXlmV?usp=drive_link

Thank you

(edited)

Moderator

 • 

3.1K Posts

April 23rd, 2024 09:39

Hi,

 

Thanks for the logs. I may need some time to reply to you, my colleague is not available today, and I'm relying on him to try to help us on your issue. 

Moderator

 • 

3.1K Posts

April 24th, 2024 03:44

Hi,

 

My colleague manage to check the logs and seems that the configuration to be OK. Try this on switch 8024 only.

 

interface Te1/0/16
switchport mode trunk

switchport trunk native vlan 10
switchport trunk allowed vlan add 10

no shut

 

If this doesn't work, do you have other switch to test with? The 8024 has power issue, which might cause the networking not able to process between to switch trunks. 

 

1 Rookie

 • 

9 Posts

April 25th, 2024 02:59

@DELL-Joey C​ 

Hey,

Fixed the problem with the power supply's. 

Ran the commands you gave and still not able to ping across switches.

The Isdp neighbors does still show each switch though.

Thanks

No Events found!

Top