Unsolved

This post is more than 5 years old

8 Posts

18305

April 16th, 2007 05:00

Troubleshooting 6248

Hi all,

Replacing a HP L3 Switch with a Dell PC6248 and trying to get the configuration right. The HP switch had a lot less options since it was pretty darn cheap and sufficed for what we needed at that time.

My setup looks like this:

1/g1 - uplink xxx.xxx.1.160/24(vlan4) (xxx.xxx.1.164)
1/g2-21 - xxx.xxx.211.0/24 (vlan2) (xxx.xxx.211.1)
1/g22-47 - xxx.xxx.231.0/24 (xxx.xxx.231.1)
1/g48 - management vlan (vlan1)

The uplink is through a cisco switch managed by our ISP.

Testing routing between the VLANs works in testing - got a desktop set up with .231.100 and a laptop with .211.100 and they can run speed tests against eachother with max speed. The same goes for the .1.164 when i switch the laptop to it.

BUT when I set the laptop to .211.100 and then connect our uplink to 1/g1 I am no longer able to ping .211.1 or .1.164 or .231.1. But I am able to ping hosts on the internet and and our ISPs switch in the building .161.1.
As soon as I pull out the cable, Im then able to ping locally on the switch again.

Here is the running config:

!Current Configuration:
!System Description "Dell PowerConnect"
!System Software Version 1.0.0.27
!
configure
vlan database
vlan 2-4
exit
stack
member 1 2
exit
ip address 192.168.0.1 255.255.255.0
ip default-gateway 192.168.0.1
no ip domain-lookup
ipv6 router ospf
no enable
external-lsdb-limit 0
exit
no ipv6 forwarding
interface vlan 2
name "211"
routing
ip address xxx.xxx.211.1 255.255.255.0
ip local-proxy-arp
exit
interface vlan 3
name "231"
routing
ip address xxx.xxx.231.1 255.255.255.0
ip local-proxy-arp
exit
interface vlan 4
name "BBB"
routing
ip address xxx.xxx.1.164 255.255.255.248
ip netdirbcast
ip local-proxy-arp
exit
ip routing
ip route 0.0.0.0 0.0.0.0 xxx.xxx.1.161
router rip
no enable
split-horizon none
no hostroutesaccept
default-metric 1
exit
username "xxxxx" password xxxxx level 15 encrypted
aaa authentication login "defaultList" line
aaa authentication enable "enableList" line
line console
password xxxxx encrypted
exit
router ospf
no enable
exit
!
interface ethernet 1/g1
no negotiation
no mdix
ip igmp snooping
spanning-tree portfast
switchport access vlan 4
exit
!
interface ethernet 1/g2
switchport access vlan 2
exit
!
interface ethernet 1/g3
switchport access vlan 2
exit
!
interface ethernet 1/g4
switchport access vlan 2
exit
!
interface ethernet 1/g5
switchport access vlan 2
exit
!
interface ethernet 1/g6
switchport access vlan 2
exit
!
interface ethernet 1/g7
switchport access vlan 2
exit
!
interface ethernet 1/g8
switchport access vlan 2
exit
!
interface ethernet 1/g9
switchport access vlan 2
exit
!
interface ethernet 1/g10
switchport access vlan 2
exit
!
interface ethernet 1/g11
switchport access vlan 2
exit
!
interface ethernet 1/g12
switchport access vlan 2
exit
!
interface ethernet 1/g13
switchport access vlan 2
exit
!
interface ethernet 1/g14
switchport access vlan 2
exit
!
interface ethernet 1/g15
switchport access vlan 2
exit
!
interface ethernet 1/g16
switchport access vlan 2
exit
!
interface ethernet 1/g17
switchport access vlan 2
exit
!
interface ethernet 1/g18
switchport access vlan 2
exit
!
interface ethernet 1/g19
switchport access vlan 2
exit
!
interface ethernet 1/g20
switchport access vlan 2
exit
!
interface ethernet 1/g21
switchport access vlan 2
exit
!
interface ethernet 1/g22
switchport access vlan 3
exit
!
interface ethernet 1/g23
switchport access vlan 3
exit
!
interface ethernet 1/g24
switchport access vlan 3
exit
!
interface ethernet 1/g25
switchport access vlan 3
exit
!
interface ethernet 1/g26
switchport access vlan 3
exit
!
interface ethernet 1/g27
switchport access vlan 3
exit
!
interface ethernet 1/g28
switchport access vlan 3
exit
!
interface ethernet 1/g29
switchport access vlan 3
exit
!
interface ethernet 1/g30
switchport access vlan 3
exit
!
interface ethernet 1/g31
switchport access vlan 3
exit
!
interface ethernet 1/g32
switchport access vlan 3
exit
!
interface ethernet 1/g33
switchport access vlan 3
exit
!
interface ethernet 1/g34
switchport access vlan 3
exit
!
interface ethernet 1/g35
switchport access vlan 3
exit
!
interface ethernet 1/g36
switchport access vlan 3
exit
!
interface ethernet 1/g37
switchport access vlan 3
exit
!
interface ethernet 1/g38
switchport access vlan 3
exit
!
interface ethernet 1/g39
switchport access vlan 3
exit
!
interface ethernet 1/g40
switchport access vlan 3
exit
!
interface ethernet 1/g41
switchport access vlan 3
exit
!
interface ethernet 1/g42
switchport access vlan 3
exit
!
interface ethernet 1/g43
switchport access vlan 3
exit
!
interface ethernet 1/g44
switchport access vlan 3
exit
!
interface ethernet 1/g45
switchport access vlan 3
exit
!
interface ethernet 1/g46
switchport access vlan 3
exit
!
interface ethernet 1/g47
switchport access vlan 3
exit
!
interface port-channel 1
spanning-tree portfast
exit


Any advice would be awesome. Thanks!

909 Posts

April 18th, 2007 18:00

The switch CPU may be getting hit with traffic from the ISP.  This could prevent ping response.
 
Also, do you have any Cisco switches in your network connected directly or indirectly to this switch?  Having Cisco switches connected via a standards based switch can cause strange problems.
 
 

909 Posts

April 18th, 2007 19:00

I just tried your config and did not have any problem.
 
Instead of pinging the switch interface when you are seeing the problem, try pinging a PC plugged into the switch.  If this works, this tells us the switch CPU is being hit by something.

8 Posts

April 19th, 2007 08:00

Hi - thank you for your replies.

This switch connects to our ISPs Cisco switch in the basement of our building. Is there a standards issue between Dell and Cisco switches?

The problem ONLY surfaces when I connect our ISP to the switch. I have had 3 different PCs connected to the switch - one for each VLAN and have been able to ping and use max bandwidth between those 3 PCs.

When I remove one of the PCs and connect the ISP to the switch it starts to act weirdly. I have no problem connecting to the "outside" from my PC but when I try and ping my gateway it simply gives me about 80% packet loss or worse. A trace to an outside source shows that it fails getting the first node (gateway) but continues on without a problem.

When I disconnect the ISP I am able to ping the gateway again.

8 Posts

April 19th, 2007 08:00

I'll try connecting 2 PCs to it and then connect the ISP. If I'm able to ping the PCs then it shouldn't be a problem should there?

Is there anyway to force the switch to respond to ping even if it is hit by traffic?

8 Posts

June 12th, 2007 00:00

I realized I hadn't turned off OSPF and RIP which I did - all default traffic should go straight to our ISP unless it is connected through our switch. This helped with with the packet loss to the ISP - I was now able to ping the gateway at our ISP without any loss.
When I try connecting to the web UI for the powerconect with the uplink active im getting huge packet losses - up to 100%. So i try pinging a PC on the switch, same thing there and same goes for pinging the switch.
 
It feels like a routing issue but I just can't wrap my head around it.
Any help you guys could give me before we hire someone to look into it?
 
I've tried switching uplink ports just to make sure there wasnt any error with that specific port.
Tried with disabled SPT, forced 1000F negotiation (thats what our ISPs switch is set to).
I also set the forward net directed broadcasts to enabled on all VLANs just to see if it made any difference.
No Events found!

Top