• November 20, 2017, 02:32:02 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Avaya 5520. Vlans cannot reach Internet.  (Read 333 times)

0 Members and 1 Guest are viewing this topic.

Offline hedin-eretic

  • Rookie
  • **
  • Posts: 3
Avaya 5520. Vlans cannot reach Internet.
« on: July 12, 2017, 09:31:08 PM »
Hello guys!

It would be much appreciated if somebody could help me configure Avaya 5520 correctly.

One of our client needs simple stuff but I could not set it up.

They have Netcomm NF4V router and Avaya 5520 switch, which connected to this router via Ethernet.

All PCs connected to the switch but they'd like to share their workspace with other people and requested to create 4 separated zone when everybody has the Internet access but could not reach sub-networks.

I've just done what Michael advised in his blog.
Created 4 different Vlans (192.168.20.0/24, 192.168.30.0/24, 192.168.40.0/24 and 192.168.50.0/24).
The router (192.168.20.1) connected to port 48. Port 48 is tagged all.
There is no DHCP other than the router, so I skipped part with DHCP-relay.

Enabled global routing but there is no Internet on Vlan 30, 40 and 50.

I've tried a few different things for example created a static route for 192.168.30.0 to 192.168.20.1 but it seems to me I have no idea what I am doing and added port 48 to all Vlans.

I am pretty sure it must be something simple but unfortunately I have no idea what. I am ready to provide any necessary information if it is needed.

Thanks in advance.



Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3818
    • michaelfmcnamara
    • Michael McNamara
Re: Avaya 5520. Vlans cannot reach Internet.
« Reply #1 on: July 13, 2017, 12:42:37 PM »
Welcome to the forums!

Assuming you assigned and IP interface to each VLAN?

Can you ping the .1 interface from your desktop/laptop in that VLAN?

I would suggest you review this blog post;
https://blog.michaelfmcnamara.com/2011/01/vlans-ip-routing-ethernet-routing-switch/

You'll also need static routes for each IP subnet you add added to your Netcomm NF4V router. You might also need to check your NAT rules to make sure that you are NATing the outbound traffic from these new IP subnets to the Internet.

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline hedin-eretic

  • Rookie
  • **
  • Posts: 3
Re: Avaya 5520. Vlans cannot reach Internet.
« Reply #2 on: July 14, 2017, 12:06:01 AM »
Thank you for your response, Michael. 

Yes, a connected device can ping Vlan interfaces (192.168.x.1).

Sorry, for the stupid question, this is not my field actually, but when you mentioned static routes on the router should it be like a Vlan interface IP (for example 192.168.30.1) to Avaya 5520 device IP  (192.168.20.233) or something else?

My apologies, I cannot get it, what traffic I am trying to route.

As far as I assumed, some device under a Vlan sends a request through Avaya 5520 and the router. The router does not know about the device, so could not send the packet back. Is something wrong with my logic?

I've tried to implement Multi-NAT OneToOne routes (that only thing I could find on Netcomm) but the router cannot ping Vlan interfaces, should it?


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3818
    • michaelfmcnamara
    • Michael McNamara
Re: Avaya 5520. Vlans cannot reach Internet.
« Reply #3 on: July 14, 2017, 12:23:48 PM »
The IP address of the Netcomm NF4V router is 192.168.20.1.

What is the IP address of the Avaya switch in that subnet? I'll guess that it's 192.168.20.2

You'll need routes on the Netcomm NF4V router for the additional IP subnets (VLANs) you deployed;

192.168.30.0/24 -> 192.168.20.2
192.168.40.0/24 -> 192.168.20.2
192.168.50.0/24 -> 192.168.20.2

This is so the Internet router knows where to send the reply traffic.

After you make this change the laptops/desktops in the individual IP subnets should be able to ping the Internet router at 192.168.20.1, as they likely can NOT ping it right now without the routes.

Cheers!


We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline hedin-eretic

  • Rookie
  • **
  • Posts: 3
Re: Avaya 5520. Vlans cannot reach Internet.
« Reply #4 on: July 18, 2017, 11:56:49 PM »
Hi Michael, thank you for your advice.

You did your magic and now the router is able to see Avaya 5520, to ping Vlans interfaces and all devices can ping the router. But there is still no internet on Vlans 30, 40 and 50 :(

As advised, I created static routes on the router like DestIP 192.168.x.0/24; Gateway 192.168.20.233 (Avaya), Interface br0

I've done tracert and a packet is going only to the router through Avaya 5520 but never comes back.

It looks like the router allows packets working only on local interface (Probably because of br0).

I would appreciate any bright thoughts.

Thank you again.

Cheers

« Last Edit: July 19, 2017, 12:29:16 AM by hedin-eretic »