Hello Seth
Vlan 1 was tagged(i know i need to tagged even if its the native vlan)
Is not possible to have another port with just vlan 1, as this swithc is on the second floor, and there is just one cable that connect from the first floor to the second floor.
As a work around i did this
On alcatel switch
vlan 1 as native vlan
Vlan 220 and 219 tagged
On aruba switch
Created vlan 300(which doesnt exist on their network)
vlan 300 as native vlan
Vlan 300, 219 and 220 tagged
So im matching the vlan 300 which is untagged with vlan 1 of alcatel switch which is untagged as well...
I though that if the problem was that only the VLAND ID i though well lets just change the vlan id but still use the vlan 1 so the client doesnt need to change anything on their network, and it worked...
Why it doesnt liek vlan id 1 agains the alcatel switch? i dont know....
I would like to make the vlan 1 works without my work around as i mean their old switch which was a netgear worked just fine with it, how can i tell the client that this doesnt work ona switch that cost like 5 times more than their netgear???
I know vlan 1 is not recomended, and they should not use it, but i cannot tell the clietn all of the sundden, you need to change your network because this swithces which cost 5 times more does not support that...
Any ideas??
Cheers
Carlos