• December 02, 2020, 04:17:07 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Inte rvlan and routing in Avaya switches over trunk links  (Read 1603 times)

0 Members and 1 Guest are viewing this topic.

Offline tham

  • Rookie
  • **
  • Posts: 1
Inte rvlan and routing in Avaya switches over trunk links
« on: April 15, 2017, 03:59:35 AM »
Hi all,

I am very new to this forum and also new to Avaya switches. I have been reading through the forum but was unable to find similar. Here is the case...

This is a new network and its going to connect to an existing HP network of 1910 and 1919 switches. The new environment has 1 core Avaya core switch (5530) and 11 spurred location with Avaya stacks. These suprred locations are connected to the core via fiber cables from ports 13-23. Port 24 is connected to HP 1910 port 50 (configured to trunk). A dhcp server (linux based) is sitting on Port 1 of the core switch. Each stack is servicing 2 vlans (XXX for users access and 300 for wifi access)

There are 2 VLAN in the HP network (Vlan 1 and Vlan2). Vlan 1 is where the current servers are located. After completion and stabilisation, the users will migrate over and servers will be relocated to the new rack on vlan 100. Server IP is 192.168.0.x

DHCP server:
Core switch:
Edge stack:

DHCP scope is set as: 192.168.x.x/24 gateway is 192.168.x.254
No DNS have been configured

1. Users in new building must be able to access vlan 100 in core switch (in the future)
2. Users in the new building should be able to receive IP from the DHCP server sitting in vlan 100
3. Users in new building must be able to access servers in vlan 1 in old HP switch
4. When new internet connectivity comes in, users in all vlan segment must be able to access internet through telco router.

What we have achieved:
We managed to achieve point 2.
We are able to access vlan 1 by tagging vlan 1 through the core switch, but not routing.

We are unable to ping dhcp server in vlan 100 ( or any vlan ip for that matter of fact.

Attached are config files and a simplified diagram.

Assistance would be most appreciated.