Unsolved

This post is more than 5 years old

3 Posts

19602

June 10th, 2014 14:00

7048 and vlan routing

Hello,

First off, I am new to this and secondly, I have searched high and low for a solution and I have found several in the forum and in the manual. None work - so I am missing something.

I have a 7048p switch with firmware 5.1.4.5

I am trying to set up several vlans - but I can't get even one to access the internet via the other. running config is :

console(config)#show running-config

!Current Configuration:
!System Description "PowerConnect 7048P, 5.1.4.5, VxWorks 6.6"
!System Software Version 5.1.4.5
!System Operational Mode "Normal"
!
configure
vlan 2,10
exit
vlan 2
name "EXIT_VLAN"
exit
vlan 10
name "DATA_VLAN"
exit
slot 1/0 6    ! PowerConnect 7048P
stack
member 1 6    ! PCT7048P
exit
ip routing
ip route 0.0.0.0 0.0.0.0 192.168.2.1
interface vlan 2
ip address 192.168.2.2 255.255.255.0
exit
interface vlan 10
ip address 192.168.10.1 255.255.255.0
exit
!
interface Gi1/0/3
switchport access vlan 10
exit
!
interface Gi1/0/48
switchport access vlan 2
exit
snmp-server engineid local 800002a2035c260acfbbb2
exit

console(config)#ex

console#ping 4.2.2.2
 Pinging 4.2.2.2 with 0 bytes of data:

Reply From 4.2.2.2: icmp_seq = 0. time= 40000 usec.
Reply From 4.2.2.2: icmp_seq = 1. time= 30000 usec.
Reply From 4.2.2.2: icmp_seq = 2. time= 30000 usec.
Reply From 4.2.2.2: icmp_seq = 3. time= 30000 usec.

----4.2.2.2 PING statistics----
4 packets transmitted, 4 packets received, 0% packet loss
round-trip (msec) min/avg/max = 30/32/40

console#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

Default Gateway is 192.168.2.1

S      0.0.0.0/0 [1/0] via 192.168.2.1,   Vl2
C      192.168.2.0/24 [0/1] directly connected,   Vl2
C      192.168.10.0/24 [0/1] directly connected,   Vl10

console#

From a host with ip 192.168.10.25 on gi1/0/3 (access vlan 10)  i can ping 192.168.10.1 (vlan 10 interface) and even 192.168.2.2 (vlan 2 interface) but I can't get to the router at 192.168.2.1 or 4.2.2.2.

I seem to be missing how to send trafic out gi1/0/48 (access vlan 2) from vlan 10.

Thanks in advance for help. I have banged my head on this for two days now!

Moderator

 • 

9.6K Posts

 • 

42.6K Points

June 10th, 2014 16:00

Hi cbmckay,

Gi 1/0/48 is what connects to the router correct? If you are able to ping vlan 2 from vlan 10 the routing should not be the issue. Typically routers are VLAN aware and can handle tagged packets and VLAN tags, so you would use a trunk port rather than an access port on that interface. If you put Gi1/0/3 on VLAN 10 can ping 4.2.2.2?

3 Posts

June 11th, 2014 08:00

Thanks for your help.

If I put Gi 1/0/3 on vlan 2 then yes I can ping out. And port 48 does connect to the router.

From the setups and diagrams I have seen, I don't need vlan 10 (or any others) on the router - do I? do I need to allow all the vlans over 48 to the router? Like: switchport trunk allow vlan add 10,20,30 tagged or some such?

Moderator

 • 

9.6K Posts

 • 

42.6K Points

June 11th, 2014 09:00

You are correct, you shouldn’t need to add VLAN 10 to the trunk port, but since both VLANs are untagged it may be the better solution.

Here is the path it sounds like the ping is taking

VLAN 10 PC->untagged ping(VLAN 10)->switch routes it to VLAN 2->ping travels to router on VLAN 2->router responds on VLAN 2->ping drops because it is untagged on VLAN 2.

Access ports are not VLAN aware, so incoming traffic is dumped into the VLAN that it is on, in this case VLAN 2.

Moderator

 • 

9.6K Posts

 • 

42.6K Points

June 12th, 2014 14:00

Probably something from Sonicwall, however you may want to contact tp-link and see if they have an answer to why it isn’t working, no reason to buy new hardware if you don’t have to.

3 Posts

June 12th, 2014 14:00

Well, I tried the setup with a second host on the vlan 2 port - instead of the router - and I was able to ping back and forth - no problem. Wow, a light at the end at last! However, the router is not accessible. I have a TP-link TL-er5120 router. Multi WAN ports was the idea. But, although it lists vlan support and QoS in the specs, it seems not to work very well. What router would you suggest to work with this switch? Wan access for voip is what we need.

No Events found!

Top