Avaya Switch to Cisco Switch Config

[absuizo14]

we are replacing old avaya switches with a Cisco switches and i could not understand the Avaya configuration on which are the etherchannels, access ports, trunk ports, what are the access vlans for the access ports and what is the native vlan? here is the part of the config im confused about.

!

! *** LACP (Phase 1) ***

!

!LACP mode is set to OFF on all interfaces to enable manipulation of

!ports with LACP enabled

interface Ethernet ALL

lacp mode port 1/ALL,2/ALL off

exit

!

! *** VLAN ***

!

vlan create 10 type port cist

vlan create 20 type port cist voice-vlan

vlan create 30,32,40,50,60,80,200 type port cist

vlan create 4051-4052 type spbm-bvlan

vlan name 10 "Management_Vlan"

vlan name 20 "Voice_Vlan"

vlan name 30 "Data_Vlan"

vlan name 32 "DATA_2"

vlan name 40 "CCTV_Vlan"

vlan name 50 "Guest-WVLAN"

vlan name 60 "Server_Vlan"

vlan name 80 "VLAN_L2"

vlan name 200 "Employee's-WVLAN"

vlan ports 1/1-3,1/10 tagging unTagPvidOnly filter-untagged-frame enable

vlan ports 1/13 tagging tagAll

vlan ports 1/21-24 tagging tagAll filter-untagged-frame enable

vlan ports 2/10-20 tagging unTagPvidOnly filter-untagged-frame enable

vlan ports 2/21-24 tagging tagAll filter-untagged-frame enable

vlan configcontrol flexible

vlan members 1 NONE

vlan members 10,50,200 1/1-3,1/10,1/13,1/21,2/10-21

vlan members 20,60 1/13,1/21,2/21

vlan members 30 1/1-6,1/8,1/10-15,1/21,2/10-21

vlan members 32 1/1-3,1/7,1/9-10,1/13,1/21,2/10-21

vlan members 40 1/1-3,1/10,1/13,1/16-21,2/1-8,2/10-21

vlan members 80 1/13,1/21,2/9,2/21

vlan ports 1/1-3 pvid 10

vlan ports 1/4-6 pvid 30

vlan ports 1/7 pvid 32

vlan ports 1/8 pvid 30

vlan ports 1/9 pvid 32

vlan ports 1/10 pvid 10

vlan ports 1/11-12,1/14-15 pvid 30

vlan ports 1/16-20,2/1-8 pvid 40

vlan ports 2/9 pvid 80

!vlan ports 1/22-24,2/22-24 pvid 0

vlan ports 2/10-20 pvid 10

no auto-pvid

!

what does these commands mean cist, tagging unTagPvidOnly filter-untagged-frame enable,  tagging tagAll filter-untagged-frame enable, tagging tagAll, no auto-pvid?

also client is saying that all the avaya switches are in "Fabric" what are the implications of that if we were to replace the switches in phases or batches which means there is a period where cisco switches are connected to avaya switches is there any config chages needed on the avaya side?

Avaya switch models and fw are as follows:

4826GTS-PWR+ HW:20 FW:5.8.0.3 SW:v5.11.0.011
4850GTS-PWR+ HW:20 FW:5.8.0.3 SW:v5.11.0 
VSP-4850GTS 6.1.0.0

[Flavio Miranda]

Hey @absuizo14 

 Unless you get luck to find some Avaya expert here, I would recommend you to put this question in some avaya forum. You´d probably have more change to get the information.

[absuizo14]

I actually posted this query(rephrased to not insult them) on the extreme forums since avaya switching was bought by them and what did i get? "that's yours and Cisco's problem". not really nice asking them how to replace their products. i guess we are just going to wing it. 

[MHM Cisco World · Accepted solution]

Other vendor always publishes pdf for interoperate 

https://blog.michaelfmcnamara.com/2010/06/avaya-and-cisco-interoperability-technical-configuration-guide/

MHM

[Flavio Miranda]

That´s why Cisco rule the world ofTelecom. Not because they have the better product, we all know that most vendor out there beat cisco in many ways. But, the knowledge base they built over the years make them king.

[Elliot Dierksen]

I have no actual knowledge of Avaya switches, so keep that in mind. The config reminds me of how older HP switches did things meaning the vlan assignments were done in the vlan config, not at the port level as Cisco does it. I would interpret the "pvid" command to indicate the native vlan assignment to those ports. It looks like you have to infer that a port is a trunk if it is a member of multiple vlan's. It looks like LACP isn't enabled anywhere.