SD-WAN

 View Only
last person joined: 14 days ago 

Ask questions and share experiences with SD-WAN and Session Smart Router (formerly 128T).
  • 1.  How do you recommend we name our device and network interfaces?

    Posted 10-17-2018 00:00


  • 2.  RE: How do you recommend we name our device and network interfaces?

    Posted 10-17-2018 00:00

    Hey @Justin - Can you provide a bit more context for this question? Are you looking for best practices or for naming conventions that have worked best for certain folks? If it's the latter, do you have a specific scenario you are trying to set up?



  • 3.  RE: How do you recommend we name our device and network interfaces?

    Posted 10-17-2018 00:00

    Certainly @Victoria Smiley !

     

    I'm looking for best practice, but what has worked for people is also very useful. I'm just rewriting the exercises in the training classes, so I want to make sure we follow the best practice.



  • 4.  RE: How do you recommend we name our device and network interfaces?

    Posted 10-17-2018 00:00

    I don't know of any best practices documents that we currently have, however, I'm tagging some folks I think would have some good examples of naming structures that have worked for them.

     

    @Gene @Stephen Voto @Brian K @Adam 

    ​​​​


  • 5.  RE: How do you recommend we name our device and network interfaces?

    Posted 10-17-2018 00:00

    Thank you @Jason and @Gene . That makes a lot of sense.

    ​​


  • 6.  RE: How do you recommend we name our device and network interfaces?

     
    Posted 10-17-2018 00:00

    For device interfaces you can go with numbered devices, like 5,11, 100, 200... Or you can go with alpha-numeric name, such as WANdevice1, LANdevice2. If you are using alpha-numeric characters make sure you don't go over the 12 char limit imposed or will get the following validation error:

     

    name; Must contain only alphanumeric characters or any of the following: _ - Length must be less than or equal to 12

     

    I also add the corresponding Linux device name in the description field for my own convenience purposes, such as eth0 or enp1s0 or eno2, etc.

     

    For network interfaces, name length is not limited to 12. So, I use names like WANinterface3, BackupLTEinterface-1, and so forth. The more descriptive the better in my view.

     

     



  • 7.  RE: How do you recommend we name our device and network interfaces?

     
    Posted 10-17-2018 00:00

    @Justin I would add to @Gene's comments and recommend using a naming convention that will be meaningful to the administrator down the road (while adhering to the 12 character limitation mentioned).

     

    For example, when troubleshooting issues I'll often want to see active sessions across the router(s). The 'Sessions' tab includes the device interface name in the output. Choosing names such as 'eno1' to match the Linux network-interface name or 'ISP1' to match the network the device interface is mapped to can be more meaningful than an integer value (see below).

     

    ​​