ExtremeSwitching (EOS)

  • 1.  Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 04:30
    In Cisco Nexus have a Virtual Device Context (VDC) for managing one physical switch to multiple logical switch.Could ExtremeNetworks do this function?

    Thank you


  • 2.  RE: Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 11:17
    Hi,

    A similar concept in EXOS would be the use of a user created Virtual-Router (VR).

    VR's have virtually separate routing and switching tables. Traffic by default is not routed or switched between VRs.

    For additional details see the below section of the EXOS User Guide:
    http://documentation.extremenetworks.com/exos/EXOS_21_1/Virtual_Routers/c_overview.shtml



  • 3.  RE: Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 11:36
    Hello,

    Currently, if you have separate HW devices (let's say 2 BDX8s switches) you have to manage them individually.

    There are some features that will help in some scenarios like MLAG, Virtual-Routers, etc. However you still need to configure each unit.


  • 4.  RE: Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 13:10
    Thank you for reply.

    I understand that's VR can use in different tag vlan but I cannot adding same tag vlan in different VR, right?

    From this concept, I have one physical chassis ethernet switch and I need to separate to multiple logical switch. for different kind of use.

    Thank you for sharing


  • 5.  RE: Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 13:22
    Hi,

    Vlan table is shared between VRs. However, each VR has its own L3 table and routing processes.

    You can separate the switch to multiple local switch by creating different VRs and different L3 tables. However, you cannot use the same vlan for different VRs.

    Each Vlan can belong to only one VR.


  • 6.  RE: Extreme Networks with Virtual Device Context (VDC) ?

    Posted 03-28-2016 13:25
    Thank you, Henrique.