Unsolved

This post is more than 5 years old

6 Posts

3951

November 19th, 2016 05:00

X1018 - Can not ping or route with VLAN 2

Hi everyone,

i have some issues with the configuration of the X1018 for routing between two new VLAN's. 

So far i have set up 2 VLAN's in different subnets 172.x.x.x and 192.x.x.x. I activated the ip routing on the switch an it is partly working. 

When i set my client to the networt 192.x.x.x (VLAN 1) i can acces the switch and us it as a gateway to reach my VLAN2 (172.x.x.x) .

Now about my issue. When i set my client to VLAN2 (172.x.x.x) i can reach the other clients from that network but nothing else. I can't reach or ping the switch on the designated adress. I guess that is the reason why i cannot use it as a gateway to reach the other VLAN.

Any advise? Help would be greatly appreciated!

Thanks - Fabian

6 Posts

November 21st, 2016 23:00

I think my post was a little misleading. To make it clear here is a little Example:

Switch (as Router):

VLAN 1 192.168.15.254

VLAN 2 172.18.15.254

Test 1:

Client IP-Adress 192.168.15.100

Ping to every address on 192.168.15.xx possible

Ping on 172.18.15.254 possible, no ping on other adresses (but i guess that is because they cant find the way back)

Test 2:

Client IP-Adress 172.168.15.100

Ping on other clients of 172.168.15.xx possible. Router on 172.168.15.254 not reachable. Therefore network 192.168.15.xx not reachable because 254 is the standard gateway.

Port Settings on Switch:

After testing with Acess mode and restrictive vlans, i have set them now to "General" assigned both vlans as untagged and deactivated the ingress filter. But still, no effect.

Thanks for your help.

6 Posts

November 22nd, 2016 07:00

Hi Daniel,

L2+ mode is activated, otherwise i wouldn't have been able to activate "ip routing".

The ARP table lists some clients from both nets:

6 Posts

November 22nd, 2016 08:00

I just noticed that the subnet was to wide. So i switched it to 255.255.255.0 and there is now only one client of VLAN2 left. 

Special thing about that client is, that is the server which has one network adapter in VLAN1 and another one in VLAN2.

Interesting part is, my client which i am using personally, has a VLAN2 adress and is not mentioned in the ARP-table.

Routing between the VLAN's is still not possible. As well i still cant ping the router from VLAN 2 using its VLAN 2 adress.

P.s. i also just noticed that ipv6 ist still enabled on the server and might cause conflicts which i wasnt aware about. I will check this tomorrow and will come back to you.

Thanks in advance!

6 Posts

November 22nd, 2016 23:00

Good morning,

i switched off IP v6 and set the clients to the smaller subnet but still the same behavior.

VLAN2-clients can not ping or reach the Switch/Router over the VLAN2 adress, but VLAN1 clients can ping the router adress of VLAN2....

Strange thing...

April 3rd, 2017 07:00

Hi,

i have same problem.

i can not ping between Vlan's. Also i can not reach internet from client computers.

from switch i can ping 8.8.8.8.

here is my configuration file:

 

v3.0.0.90 / RASTUTE_800_026
CLI v1.0
set system mode L2+
policy-based-vlans inactive

@
vlan database
vlan 101-102,200
exit
voice vlan oui-table add 000181 Nortel__________________
voice vlan oui-table add 0001e3 Siemens_AG_phone________
voice vlan oui-table add 00036b Cisco_phone_____________
voice vlan oui-table add 00096e Avaya___________________
voice vlan oui-table add 000fe2 H3C_Aolynk______________
voice vlan oui-table add 001049 Shoretel________________
voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
voice vlan oui-table add 00907a Polycom/Veritel_phone___
voice vlan oui-table add 00e0bb 3Com_phone______________
!
interface vlan 1
ip address 192.168.2.1 255.255.255.0
no ip address dhcp
!
interface vlan 101
ip address 10.0.1.254 255.255.255.0
!
interface vlan 102
ip address 10.0.2.254 255.255.255.0
!
interface vlan 200
ip address 10.1.0.2 255.255.255.0
!
interface gigabitethernet1/0/4
switchport access vlan 102
!
interface gigabitethernet1/0/7
switchport access vlan 101
!
interface gigabitethernet1/0/22
switchport access vlan 200
!
exit
ip default-gateway 10.1.0.1

6 Posts

April 3rd, 2017 23:00

Hi,

first of all sorry for not continuing on that issue, but it was an on site installation and i did not have any more time. So i changed the whole configuration without using 2 vlans an was "good to go".

@Adam

Have you switched on the ip routing? It is not mentioned in the configuration file. You will have to do this via the console configuration. It did not solve it for me, but following the manual it is a minimum requirement, maybe you have more luck ;)

Regards,

Fabian

April 4th, 2017 05:00

i did ip routing, but still not working. also that command is no showing on running-configuration, even on startup-configuration :(

No Events found!

Top