DNA Center - PnP Catalyst 9300

Поділитися
Вставка

КОМЕНТАРІ • 7

  • @fredharris1049
    @fredharris1049 Рік тому +1

    Thanks for posting this, it was very helpful. I was trying to figure out the best way to address how PnP automatically puts the trunk link in "allowed" mode with just the startup-vlan when I really want it to run LACP with multiple VLANs when it gets done onboarding. This video did the trick with the configuration you showed @5:51.

  • @BuzzNation69
    @BuzzNation69 2 роки тому +2

    What if we use layer 3 point to pint ISIS intermediate networks between a unlink switch and a edge switch?

  • @paulheavens1170
    @paulheavens1170 2 роки тому

    We need to use a specific interface, the mgmt0 interface for this?

  • @bbb229
    @bbb229 2 роки тому

    Trying this using the Mgt Gi0/0 and it is not working, New switch is not picking up on DHCP (which is active within the local VLAN). Do we need to connect the new switch using a Acces Port for this to work ?

  • @pwaghmare1258
    @pwaghmare1258 10 місяців тому

    what if the uplink device is a router and not a switch, how do we configure that.

  • @Justso65
    @Justso65 Рік тому

    Is the process different to bring an edge switch onboard to join an SDA fabric? How do I auto provision the L3 interface config, routing protocol settings and loopback address used by SDA for the VxLAN endpoint? If I recall we can auto configure all these parts and also deploy ISIS as the underlay protocol at PnP time.

    • @danielmaciejewski-gf3qr
      @danielmaciejewski-gf3qr Місяць тому

      all of those are performed if you are using SDA, LAN Automation will automatically provision those based on a few parameters you configured in DNA Center. However, if you have a fabric that was created and need to onboard a new switch - you will have to put all of those configs in either a day0 or Nday template and push it out to the device that way.