Unsolved

This post is more than 5 years old

3 Posts

16654

March 14th, 2008 07:00

Problem with VLAN routing using PowerConnect 6224

Hi,

 

I have problem with VLAN routing using PowerConnect 6224. My network configuration is:

 

VLANs configuration

From the CLI environment:

 

1. I can ping all following ip addresses: 192.168.1.7, 192.168.1.10, 192.168.0.100 (DNS server on LAN), 212.20.96.20 (some computer on internet), 192.168.64.1, 192.168.64.2.

 

2. I can traceroute ip adresses: 192.168.1.7, 192.168.1.10, 192.168.64.1, 192.168.64.2.

 

3. But I cannot traceroute ip adresses: 192.168.0.100, 212.20.96.20. If I try, the router CLI environment hangs for about two minutes and even the web application Dell OpenManage Switch Administrator hangs as well. During this time, I can ping e.g. ip address 192.168.64.2 from 192.168.0.93 (workstation on LAN) without problems.

 

I cannot run any TCP/IP application through router, for instance I cannot conncet via SSH, FTP, VNC etc. from 192.168.0.93 to 192.168.64.2, the SSH application hangs withou any error message.

 

From 192.168.64.2 I can connect via SSH to any internet computer, but I cannot connect to any computer on LAN 192.168.0.0/22.

 

My configuration script is:

 

!Current Configuration:
!System Description "Dell PowerConnect"
!System Software Version 1.0.0.27
!
configure
vlan database
vlan 2-3
exit
hostname "router-aer.vzlu.local"
stack
member 1 1
exit
ip address 10.10.10.11 255.255.255.0
ip default-gateway 192.168.1.10
no ip domain-lookup
ip domain-name vzlu.local
ip name-server 192.168.0.100
ipv6 router ospf
no enable
exit
interface vlan 2
name "VZLU LAN"
routing
ip address 192.168.1.7 255.255.252.0
exit
interface vlan 3
name "Serverovna AER"
routing
ip address 192.168.64.1 255.255.252.0
exit
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.1.10
router rip
no enable
exit
username "root" password 6959eb3c5df3c9bd1e0164a602e2401f level 15 encrypted
no spanning-tree
router ospf
no enable
exit
!
interface ethernet 1/g1
spanning-tree disable
exit
!
interface ethernet 1/g2
spanning-tree disable
switchport access vlan 2
exit
!
interface ethernet 1/g3
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g4
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g5
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g6
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g7
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g8
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g9
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g10
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g11
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g12
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g13
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g14
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g15
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g16
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g17
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g18
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g19
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g20
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g21
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g22
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g23
spanning-tree disable
switchport access vlan 3
exit
!
interface ethernet 1/g24
spanning-tree disable
switchport access vlan 3
exit
exit

 

Why the routing does not work?

 

Thanks,

Dan

March 14th, 2008 22:00


Can you get the output of "show ip route" - so we can see the 6224 current routing topology - that

its believes it has ?

3 Posts

March 28th, 2008 10:00

show ip route

Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
       B - BGP Derived, IA - OSPF Inter Area
       E1 - OSPF External Type 1, E2 - OSPF External Type 2
       N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2

S      0.0.0.0/0 [1/0] via 192.168.1.10,   vlan 2
C      192.168.0.0/22 [0/0] directly connected,   vlan 2
C      192.168.64.0/22 [0/0] directly connected,   vlan 3

53 Posts

March 28th, 2008 16:00

Dan,

can you update your firmware to ver.2.0.0.12 first? 

3 Posts

March 31st, 2008 07:00

I just updated firmware to ver. 2.0.1.8 (the latest version available). It did not help, the behaviour is still the same :smileysad:

 

Dan 

March 31st, 2008 08:00

Okay so the basic routing table looks correct and your default route 0.0.0.0 is back towards your firewall 192.168.1.10 - so that looks good.

 

Can you check two things - as it seems devices in VLAN 2 ,192.168.0.0/22 are having the issue.

 

(1) The same subnet mask exists on your Firewall router (/22) for VLAN 2

 

(2) For end PC/host devices in VLAN 2 that you are using to test - i.e connected into a port in VLAN 2 - which default gateway are you pointing them at ?

It should be the L3 port of the switch (VLAN 2).....can you check that on your end Hosts/PC's

No Events found!

Top