Fabric Attach: (VSP8600 -> x440G2 -> client vs VSP8600 -> x620 -> x440G2 -> client)

  • 11 September 2019
  • 0 replies

i have some issues using the fabric attach feature of the vsp and exos devices, if there are more then 2 switches involved in a connection to the core:

we are migrating our core-switches to vsp 8600 at the moment. therefore we created a spbm cluster with 4 vsp8600.

the edge switches consist of x440g2, which in most instances will be attached directly to the vsp and use the fabric attach feature.

via nac we want to assign vlans with nsi/isid to the client ports which should be propagated to the core.

if the x440G2 is connected directly to the vsp everything works as described.

the fa feature doesn't work if the x620 sits inbetween the edge and core switch:
client -> x440G2 -> x620 -> vsp8600

can you give me some hint if:
  • i'm doing it wrong?! I'm not sure if the standalone proxy mode could help accomplish the above
  • this should work but i have a configuration problem on one of the involved devices
  • the above configuration isn't supported at all?
For configuration: i enabled fa on the gigabitethernet interfaces of the VSPs connected to the x440g2 and x620 switches and defined an nsi/isid on the exos devices. if the x620 is involved the fa assignment on the x440g2 never gets active, it just stays in status pending.

0 replies

Be the first to reply!