Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

rbjohnson78

8 Posts

47140

February 6th, 2013 13:00

Powerconnect 6248 High Latency

I swapped out our core switch that was a 6024 for a 6248. Since then, we have had nothing but problems. Pinging from a switch that is connected to one of the fiber ports and I'm getting very high latency. Sometimes I don't even get reply's back. It is the oddest thing I have ever seen. 

I've messed with the arp and bridge times, flow control, and everything else and can't seem to fix it.

Any ideas? Below is the current running config

!Current Configuration:
!System Description "PowerConnect 6248, 3.3.1.10, VxWorks 6.5"
!System Software Version 3.3.1.10
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 100-103,105-107,110,200,1000
ip igmp snooping 100
ip igmp snooping 101
ip igmp snooping 102
ip igmp snooping 103
ip igmp snooping 105
ip igmp snooping 106
ip igmp snooping 107
ip igmp snooping 110
ip igmp snooping 200
ip igmp snooping 1000
vlan routing 100 1
vlan routing 101 2
vlan routing 102 3

--More-- or (q)uit
                     

vlan routing 103 4
vlan routing 105 5
vlan routing 106 6
vlan routing 107 7
vlan routing 110 8
vlan routing 200 9
exit
hostname "RENCORESW01"
sntp unicast client enable
sntp client poll timer 1024
sntp server us.pool.ntp.org
clock timezone -5 minutes 0
stack
member 1 2
exit
ip address 192.168.99.1 255.255.255.0
ip domain-name****.com
ip name-server 192.168.100.70
logging console debug
logging file debug
no diffserv

--More-- or (q)uit
                     

ip routing
ip route 0.0.0.0 0.0.0.0 192.168.100.2
ip route 172.16.24.0 255.255.255.0 192.168.100.2
ip route 10.0.0.0 255.255.255.0 192.168.100.2
bootpdhcprelay maxhopcount 8
interface vlan 100
routing
ip address 192.168.100.1 255.255.255.0
ip rip
ip dvmrp
ip igmp
exit
interface vlan 101
routing
ip address 192.168.101.1 255.255.255.0
ip helper-address 192.168.100.70
ip rip
ip dvmrp
ip igmp
exit
interface vlan 102

--More-- or (q)uit
                     

routing
ip address 192.168.102.1 255.255.255.0
ip rip
ip igmp
exit
interface vlan 103
routing
ip address 192.168.103.1 255.255.255.0
ip igmp
exit
interface vlan 105
routing
ip address 192.168.105.1 255.255.255.0
ip igmp
exit
interface vlan 106
routing
ip address 192.168.106.1 255.255.255.0
ip igmp
exit
interface vlan 107

--More-- or (q)uit
                     

routing
ip address 192.168.107.1 255.255.255.0
ip helper-address 192.168.100.70
ip igmp
exit
interface vlan 110
routing
ip address 192.168.110.1 255.255.255.0
ip helper-address 192.168.100.70 dhcp
ip igmp
exit
interface vlan 200
routing
ip address 192.168.200.1 255.255.255.0
ip igmp
exit
username "admin" password 7066e477d3a33162199fb9766ca8694b level 15 encrypted
no flowcontrol
spanning-tree priority 4096
bridge aging-time 1230
bridge multicast filtering

--More-- or (q)uit
                     

ip igmp snooping
router ospf
router-id 192.168.100.1
exit
ip multicast
ip igmp
sflow 1 destination owner renwmanage02 timeout 4284053848
sflow 1 destination 192.168.100.125 2055
dhcp l2relay
dhcp l2relay vlan 100-101,107,110
dhcp l2relay circuit-id vlan 107,110
!
interface ethernet 1/g1
no negotiation
storm-control broadcast
storm-control multicast
storm-control unicast
traffic-shape 50000 kbps
sflow 1 sampling 1500 50
sflow 1 polling 400
switchport access vlan 100

--More-- or (q)uit
                     

exit
!
interface ethernet 1/g2
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
description 'Patch-Port-29'
spanning-tree portfast
mtu 1528
switchport mode general
switchport general allowed vlan add 100-101,107,1000 tagged
exit
!
interface ethernet 1/g3
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400

--More-- or (q)uit
                     

switchport access vlan 100
exit
!
interface ethernet 1/g4
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
switchport mode general
switchport general allowed vlan add 100-101,107,1000 tagged
exit
!
interface ethernet 1/g5
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
description 'Cisco-R210'
spanning-tree cost 20000

--More-- or (q)uit
                     

spanning-tree portfast
spanning-tree mst 0 external-cost 20000
switchport access vlan 110
exit
!
interface ethernet 1/g6
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
description 'IP-Camera'
spanning-tree cost 20000
spanning-tree portfast
spanning-tree mst 0 external-cost 20000
switchport access vlan 100
exit
!
interface ethernet 1/g7
storm-control broadcast
storm-control multicast

--More-- or (q)uit
                     

storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
description 'Patch-Port-2'
switchport access vlan 101
exit
!
interface ethernet 1/g8
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Renovo-SAN-Switch'
spanning-tree cost 20000
spanning-tree portfast
spanning-tree mst 0 external-cost 20000
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 105-106
exit

--More-- or (q)uit
                     

!
interface ethernet 1/g9
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Patch-Port-49'
spanning-tree cost 200000
spanning-tree portfast
spanning-tree mst 0 external-cost 200000
switchport access vlan 101
exit
!
interface ethernet 1/g10
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Patch-Port-48'

--More-- or (q)uit
                     

spanning-tree portfast
switchport access vlan 101
exit
!
interface ethernet 1/g11
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Patch-Port-51'
spanning-tree portfast
switchport access vlan 101
exit
!
interface ethernet 1/g12
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400

--More-- or (q)uit
                     

description 'Firefly'
spanning-tree portfast
switchport access vlan 101
exit
!
interface ethernet 1/g13
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Developers-Environment'
switchport mode general
switchport general pvid 100
switchport general allowed vlan add 100
exit
!
interface ethernet 1/g14
storm-control broadcast
storm-control multicast
storm-control unicast

--More-- or (q)uit
                     

sflow 1 sampling 1500
sflow 1 polling 400
switchport access vlan 100
exit
!
interface ethernet 1/g15
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
switchport access vlan 100
exit
!
interface ethernet 1/g16
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Dell-Xen-Server'

--More-- or (q)uit
                     

spanning-tree cost 20000
spanning-tree portfast
spanning-tree mst 0 external-cost 20000
switchport access vlan 107
exit
!
interface ethernet 1/g17
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Patch-Port-15'
switchport access vlan 100
exit
!
interface ethernet 1/g18
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500

--More-- or (q)uit
                     

sflow 1 polling 400
mtu 9216
switchport mode trunk
switchport trunk allowed vlan add 105-106
exit
!
interface ethernet 1/g19
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500
sflow 1 polling 400
description 'Suite-215-Switch'
switchport mode trunk
switchport trunk allowed vlan add 100-101,107,200
exit
!
interface ethernet 1/g20
storm-control broadcast
storm-control multicast
storm-control unicast

--More-- or (q)uit
                     

description 'Cisco-R210-Redundancy'
spanning-tree cost 20000
spanning-tree portfast
spanning-tree mst 0 external-cost 20000
switchport mode general
switchport general pvid 101
switchport general allowed vlan add 101
exit
!
interface ethernet 1/g21
storm-control broadcast
storm-control multicast
storm-control unicast
description 'Equal-Logic-Management'
switchport access vlan 105
exit
!
interface ethernet 1/g22
storm-control broadcast
storm-control multicast
storm-control unicast

--More-- or (q)uit
                     

exit
!
interface ethernet 1/g23
storm-control broadcast
storm-control multicast
storm-control unicast
switchport access vlan 100
exit
!
interface ethernet 1/g24
no negotiation
storm-control broadcast
storm-control multicast
storm-control unicast
description 'to_anuj_switch'
switchport access vlan 101
exit
!
interface ethernet 1/g25
storm-control broadcast
storm-control multicast

--More-- or (q)uit
                     

storm-control unicast
exit
!
interface ethernet 1/g26
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g27
storm-control broadcast
storm-control multicast
storm-control unicast
switchport access vlan 100
exit
!
interface ethernet 1/g28
storm-control broadcast
storm-control multicast
storm-control unicast
exit

--More-- or (q)uit
                     

!
interface ethernet 1/g29
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g30
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g31
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g32
storm-control broadcast

--More-- or (q)uit
                     

storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g33
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g34
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g35
storm-control broadcast
storm-control multicast
storm-control unicast
exit

--More-- or (q)uit
                     

!
interface ethernet 1/g36
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g37
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g38
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g39
storm-control broadcast

--More-- or (q)uit
                     

storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g40
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g41
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g42
storm-control broadcast
storm-control multicast
storm-control unicast
exit

--More-- or (q)uit
                     

!
interface ethernet 1/g43
storm-control broadcast
storm-control multicast
storm-control unicast
exit
!
interface ethernet 1/g44
no negotiation
storm-control broadcast
storm-control multicast
storm-control unicast
description 'Port_To_Colo'
switchport access vlan 100
exit
!
interface ethernet 1/g45
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50

--More-- or (q)uit
                     

sflow 1 polling 400
switchport mode trunk
switchport trunk allowed vlan add 100-101,107,1000
exit
!
interface ethernet 1/g46
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
switchport mode trunk
switchport trunk allowed vlan add 100-101,107,110,1000
exit
!
interface ethernet 1/g47
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400

--More-- or (q)uit
                     

mtu 9000
switchport mode trunk
switchport trunk allowed vlan add 100-102,107,1000
exit
!
interface ethernet 1/g48
storm-control broadcast
storm-control multicast
storm-control unicast
sflow 1 sampling 1500 50
sflow 1 polling 400
mtu 9000
switchport mode trunk
switchport trunk allowed vlan add 100-102,107,1000
exit
!
interface ethernet 1/xg1
description '192.168.100.253'
exit
!
interface ethernet 1/xg2

--More-- or (q)uit
                     

description '192.168.100.251'
exit
!
interface ethernet 1/xg3
description '192.168.101.253'
exit
!
interface ethernet 1/xg4
description '192.168.101.252'
exit
!
interface port-channel 1
switchport mode trunk
switchport trunk allowed vlan add 100-101,107,200
exit
!
interface port-channel 2
switchport mode trunk
exit
snmp-server community  ro ipaddress 192.168.100.125
snmp-server host 192.168.100.125  traps v2

DELL-Willy M

802 Posts

February 6th, 2013 16:00

I see the firmware level you have on the switch is 3.3.1.10.  I would consider updating the firmware to the most recent update 3.3.5.5 released 11/20/2012.  Here is link for the download:

www.dell.com/.../powerconnect-6224

I’m not certain this is something affecting your set up.  When you mentioned upgrading from 6024 to a 6224 then this came to mind:

General links are mostly used today for legacy equipment.  However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID.  If you use Trunk mode, you will not have the default VLAN on those ports.  The ports will only allow tagged traffic.

General Links consist of a combination of VLAN Trunk and Access Links.

General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged.  All untagged  frames are sent to the native VLAN.

The native VLAN still applies to the General LINK.  While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID.  The PVID represents the native VLAN.  

While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN.

I will continue to look at the configurations that you have provided for any other possible suggestions for resolution.

rbjohnson78

8 Posts

February 7th, 2013 10:00

I will be performing the firmware upgrade tonight. I really hope that it helps our situation.  If you need more background on our network, please let me know.

Thank you for the help!

rbjohnson78

8 Posts

February 7th, 2013 11:00

Here is a question I should know but... If I have a switch that has jumbo frames configured. does the trunk port of that  switch that connects to the core need to have jumbo frames enabled too?

rbjohnson78

8 Posts

February 7th, 2013 11:00

Also, i ran the statistics counter and most see ok, except for the one that connects to our point to point. Here are the errors i'm getting on port 44

RENCORESW01#show statistics ethernet 1/g44

Total Packets Received (Octets)................ 326902333190

Packets Received 64 Octets..................... 44847080

Packets Received 65-127 Octets................. 219738547

Packets Received 128-255 Octets................ 22330660

Packets Received 256-511 Octets................ 14207893

Packets Received 512-1023 Octets............... 7569813

Packets Received 1024-1518 Octets.............. 202519007

Packets Received > 1518 Octets................. 3546

Packets RX and TX 64 Octets.................... 130667934

Packets RX and TX 65-127 Octets................ 308223478

Packets RX and TX 128-255 Octets............... 46510420

Packets RX and TX 256-511 Octets............... 36731989

Packets RX and TX 512-1023 Octets.............. 16133396

Packets RX and TX 1024-1518 Octets............. 589228509

Packets RX and TX 1519-2047 Octets............. 3546

Packets RX and TX 2048-4095 Octets............. 0

Packets RX and TX 4096-9216 Octets............. 0

Total Packets Received Without Errors.......... 511213000

Unicast Packets Received....................... 511176137

Multicast Packets Received..................... 0

Broadcast Packets Received..................... 36863

--More-- or (q)uit

Total Packets Received with MAC Errors......... 3546

Jabbers Received............................... 0

Fragments/Undersize Received................... 0

Alignment Errors............................... 3546

FCS Errors..................................... 0

Overruns....................................... 0

802.3x Pause Frames Received................... 0

Unacceptable Frame Type........................ 3

Total Packets Transmitted (Octets)............. 592782496551

Packets Transmitted 64 Octets.................. 85820854

Packets Transmitted 65-127 Octets.............. 88484931

Packets Transmitted 128-255 Octets............. 24179760

Packets Transmitted 256-511 Octets............. 22524096

Packets Transmitted 512-1023 Octets............ 8563583

Packets Transmitted 1024-1518 Octets........... 386709502

Packets Transmitted > 1518 Octets ............. 0

Max Frame Size................................. 1518

Total Packets Transmitted Successfully......... 616282726

Unicast Packets Transmitted.................... 603829515

Multicast Packets Transmitted.................. 3195425

--More-- or (q)uit

Broadcast Packets Transmitted.................. 9257786

Total Transmit Packets Discarded............... 0

Single Collision Frames........................ 0

Multiple Collision Frames...................... 0

Excessive Collision Frames..................... 0

802.3x Pause Frames Transmitted................ 0

GVRP PDUs received............................. 0

GVRP PDUs Transmitted.......................... 0

GVRP Failed Registrations...................... 0

BPDU: sent 569869, received 0

EAPOL Frames Transmitted....................... 0

EAPOL Start Frames Received.................... 0

Time Since Counters Last Cleared............... 13 day 4 hr 34 min 8 sec

DELL-Willy M

802 Posts

February 7th, 2013 11:00

I pulled all the trunk/general mode interfaces configured for multiple VLAN to pass traffic (listed below) to get a better picture of what is connecting on your set up.  

interface ethernet 1/g2

interface ethernet 1/g4

interface ethernet 1/g8

interface ethernet 1/g13

interface ethernet 1/g18

interface ethernet 1/g19

interface ethernet 1/g20

interface ethernet 1/g45

interface ethernet 1/g46

interface ethernet 1/g47

interface ethernet 1/g48

interface port-channel 1

interface port-channel 2

I’m not seeing any configurations that are associating a physical interface into either of the port-channel interfaces.

The following example shows how port g5 is configured to port-channel number 1 without LACP.

Console (config)# interface ethernet 1/g5

Console (config-if)# channel-group 1 mode on

When setting up a port-channel with the channel group command.  The only configuration on the physical interface that is set for the port-channel is the channel-group command.  Then once the port-channel is set the switchport commands are configured on the port-channel and not the individual interfaces associated with the port-channel.

It may be helpful to look at the show interfaces counters [ethernet interface | port-channel port-channelnumber] command for each of the above interfaces to see if any abnormal traffic is revealed.

Page 299-301 of the CLI Guide discusses the definitions of the output of the show interfaces counters command.

support.dell.com/.../cli_en.zip

rbjohnson78

8 Posts

February 7th, 2013 11:00

we were using port-channel for a little while and were having issues. so we removed the port from the port-channel. Will this cause issues the way it is?

DELL-Willy M

802 Posts

February 7th, 2013 11:00

I would suggest removing the configurations off the 2 port-channels if you are not using them.

Yes, if you have Jumbo Frames enabled at the access point you will need Jumbo Frames enabled on all the pass thru interfaces that the Jumbo Frames would need to pass.  If not you would be creating a bottle neck.  It's like when you are driving down a 4 lane highway and then you come up on some road construction and the 4 lanes go down to 1 lane.  You will inevitably have a traffic jam.

DELL-Willy M

802 Posts

February 7th, 2013 12:00

If there is a chance the Jumbo Frame traffic is going to traverse or is allowed to traverse over an interface then you will want Jumbo Frames enabled on that interface.  This will allow the larger packets to flow freely without any congestion on the network.

rbjohnson78

8 Posts

February 7th, 2013 12:00

Last question on the jumbo frames. If sw1 has jumbo frames enabled, and the core has it enabled. will sw2 that is connected to the core also need it enabled? On occasion sw2 talks to sw1, but not always.

Was this post helpful?

View All

No Events found!

Top