PB multi vlan between hp procurve 2650 and avaya p882

[garcon]

Hi

I used a default vlan 1 to connect the switch hp procurve 2650 to the switch p882 avaya via a trunk 802.1q.

I can access to the switch hp but I can't access to the computers on the vlan 2, 3 and 4.

The port are up, but the ping don't answer.

Configuration the switch p882 avaya :
Port Vlan : Default
Trunk mode : IEEE 802.1Q
Frame Tags : Use
Vlan Binding : Bind to all
Hunt group : swtest
all other fields : disable

Configurtion on the HP Procurve 2650

Startup configuration:
; J4899A Configuration Editor; Created on release #H.07.31
hostname "swtest"
time timezone 2
no cdp run
interface 1
speed-duplex 10-half
exit
interface 2
speed-duplex 10-half
exit
.......
interface 48
speed-duplex 10-half
exit
interface 49
speed-duplex 100-full
no lacp
exit
interface 50
speed-duplex 100-full
no lacp
exit
trunk 49-50 Trk1 LACP
ip default-gateway 123.123.1.99
sntp server 123.123.123.123
sntp server 123.123.123.124
no timesync
snmp-server community "public"
snmp-server community "private" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged Trk1
ip address 123.123.1.20 255.255.255.0
no untagged 1-48
exit
vlan 2
name "vlan2"
untagged 1-30
no ip address
tagged Trk1
exit
vlan 3
name "vlan3"
untagged 31-45
tagged Trk1
exit
vlan 4
name "vlan4"
untagged 46-48
no ip address
tagged Trk1
exit
no spanning-tree 1-48 edge-port
spanning-tree Trk1 priority 4
password manager
password operator

Could help me ?

Regards

Laurent

[Ron Kinner]

It's not clear how you expect this to work. Conections between VLANS are only possible by going to layer three which usually means IP routing. I know the Ayala can do IP routing with the right options but I don't see how it is supposed to know about the IP addresses of the hosts on the other VLANs.

I don't speak Ayala but you would need to tell it about VLANs 2-4 and also assign ip addresses and masks to each VLAN and then have VLAN 2-4 present and tagged on the port(s) going to the 2650. It appears to me that you have just told it about VLAN 1. Hosts in VLAN1 on the Ayala would need to know that they could get to the other subnets via the Ayala's IP address or the 2650's VLAN1 IP address. Hosts on other VLANS on the AYALA would have to use the IP address of the Ayala on their VLAN. Hosts on the 2650 VLANS would need to know about the IP address assigned on the Ayala to each of their VLANs and also that these addresses could be used to get to other subnets on the Ayala.

IF you want the 2650 to do the routing then you don't need VLAN2-4 on the trunk. Instead you need to assign IP addresses to each VLAN on the 2650 so it will know which VLAN has which subnet. You will also need to tell the hosts in each VLAN that they can get to the addresses on the Ayala by going to the IP address assigned to their VLAN. The host on the Ayala would need to know how to get back to the hosts on the 2650 - probably using the IP address assigned to their VLAN on the Ayala or via the IP address assigned to the VLAN1 on the 2650. You may also need to assign static routes on the 2650 to tell it how to get to any networks on the Ayala (other than the one used by VLAN1).

Ron

[garcon]

Hi

The problem resolved, it came from hardware problem.

This configuration is correct.

Thanks a lot.

Regards

Laurent