I recently started playing with the Extreme Fabric Connect (Old Avaya Fabric) and some Fabric Attached XOS switches and 39xx AP's.
I have two questions/comments that I thought would be good to share here and get some feedback.
1. When I connect a default XOS (X440-g2) switch to the Fabric (Via a FA port configured on the VSP fabric swithces) I expected the management vlan and all other fabric related info, to be pushed the the XOS switch from the fabric via LLDP. This would be a typical ZTP deployment scenario.
The problem I have is with the latest version of XOS (126.96.36.199) , LLDP is not enabled by default.
The FA management vlan and all other settings is only pushed to the XOS switch once I run the "Enble LLDP ports all" command.
Comment: LLDP should be enabled by default when you unpack a new switch.
2. On the Fabric Attached XOS switch I create a vlan and map an I-SID to the vlan. This mapping is then advertised via LLDP to the Fabric and learnt accordingly.
Why can I not map a i-sid to a VMAN? surely mapping a I-Sid to a vlan should be the same as mapping it to a VMAN. A typical scenario would be if I have various tenants on a network and each tenant was a Voice,Video and Data vlan. I would like to map the tenant a single port on a XOS switch, that is mapped to a VMAN, and what ever traffic is ingressing on this port should arrive on the remote side of the fabric and egressed. (Similar to how I would map a VMAN to a VPLS service across a MPLS network).
If this client connected directly to the Fabric connect switch I would be able to Map the interface to a I-Sid (isid 1234 elan-transparent port x/x) and that would work fine, but what if I had a XOS fabric attached switch between client and Fabric?
Looking forward to some comments on Fabric