Fabric SPB migration from Cisco core

  • 18 October 2020
  • 9 replies


I was wondering whether someone did migrate from a standard 802.1q tagged core like Cisco to a Fabric SPBM with VSP 7400 series and would like to share their lessons learned.



Cisco 4500x cores -- X460G2-10GE4 (distribution / edge)


VSP 7000 -- X460G2-10GE4 (fabric attach)

Options I can think of:


VSP 7400 --- Cisco 4500x

  • not sure how to have 802.1q tagging between VSP 7400 and Cisco 4500x and SPBM at the same time
  • Migrate all X460G2 from Cisco 4500x to VSP7400


VSP 7400 --- x460G2-10GE4 --- Cisco 4500x

  • the x460G2 would be a fabric attached client on the VSP7400 side and a standard 802.1q trunking client on the Cisco 4500x side.
  • migrate all remaining X460G2s to the VSP7400 as fabric attached units

Your thoughts?

Thank you,



9 replies

Userlevel 6
Badge +1


802.1q tagging is a standard and is working for all brands as far as I know and certainly between Cisco and VSP.

I would go for scenario 1.

The attention points for such migration are:

  • to be sure to control the spanning tree topology and be very careful if PVSTP is in use on the Cisco. The EXOS does support it but no the VSP.
  • check if you use SRP or VRRP for the IP redundancy
    • If you use VRRP, the VSP can join the VRRP instances and by changing the priority you have a smooth transition of the L3 functions

Traditional steps are:

  1. bridge VSP and Cisco core’s
  2. configure all VLANs tagged between them
  3. L2: migrate Edge switches from Cisco to VSP
    1. all the uplinks of switch one at the same time to avoid STP and/or loops issue
  4. Migrate the L3 functions

Steps 3 and 4 can easily be swapped




Userlevel 6

Hello Klaus,

your option one should work fine. You can have links with tagged vlans from the fabric to other (non fabric) switches. After you establised the connection between Fabric and Cisco, you can move your x460 switch by switch. 

In an third step you can move the routing interfaces from cisco to the fabric.


Best regards


Hi Mig, Stephan,


Thanking you both for your replies.

Cosmetical question:

  • Is there a way to have console messages synchronised and the prompt being shown after the message?

On a Cisco I would configure logging synchronous on line con 0 for instance.

Kind regards,


Userlevel 6
Badge +1



I’m not sure to fully understand your question but…

To have the on/off the console messages on console or SSH session on:

  • VSP: 
    • configure terminal
    • logging screen
    • no logging screen
  • EXOS
    • enable log display
    • disable log display


Hi Mig,


While I want logging on the console I also want the system to press the return key for me :grinning: like this:

Core-1-Hv:1(config)#1 2020-10-20T21:50:18.464Z Core-1-Hv CP1 - 0x00088524 - 00000000 GlobalRouter SW INFO Boot sequence successful



instead of this:frowning2:


Core-1-Hv:1(config)#1 2020-10-20T21:50:18.464Z Core-1-Hv CP1 - 0x00088524 - 00000000 GlobalRouter SW INFO Boot sequence successful.



Userlevel 6

Hello tfsnetman,


I think you will find the answere here (last message):


The command is  '”logging screen enable'”  hen you use telnet and ssh session.




Userlevel 6
Badge +1


We don’t have a solution for this cosmetic issue. A tuned console client can do the job but...

Personally I don’t like the automatic return key. It could happen in the middle of a command line.

I use RoyalTSX as console client and a plug-in based on iTerm can be configured for this.

Be careful anyway.



Hi Mig,

Totally agree with “automatic return” - poor choice of words.

I just meant the console or ssh session to come back to where I left it - so I can see where I was with my typing :grinning: .

I found SecureCRT to be very stable both OS X and Windows.


Cheers, Klaus

Userlevel 6
Badge +1


You could always use the TAB or “?” to clear the current line :wink: