SD-wan Version 5.2: (Obligatory) new GUI and some changed Features and Configuration Hierarchies

 Per default in version 5.2 the new Angular (html5) based GUI is now the only installed one.

So you should  get familiar with that new UI 

But if you search and search and do not find the necessary item in the new UI but need it urgently, what can you do ?

An operator can allow also the classical UI by changing a System Parameter to TRUE:


 and then the operator or MSP can enable the classical UI for the customer


as Operator/MSP/User then you see the "Open Classic Orchestrator" in the upper right area


NOTE: the classic UI is not maintained anymore, so there are already some items only vailable in the new UI and any new feature will only be visible by using the new UI

Working with the new UI in my environment there were 2 features which were not easy to find.

1. Assign new image to an Edge

In the old GUI you could go to the Configure/Edges and under Actions you could select "Assign new Image to Edge".

It seems that this feature has been removed (I double checked the old and new documentation to have a confirmation) 

BUT there is a workaround:

You need to clone (or let your MSP clone) the Operator Profile, select a different software version in that profile and afterwards attach that newly created operator profile to the customer and the customer can assign the profile to edge you want to be upgraded

Editing the operator profile now also has some new field regarding VCO address which must be filled out (pre 5.x versions used some VCO system parameter for that information) in order to save the changes


now the MSP need to assign the new Operator Profile to the customer

 


after that the Customer has the choice to select the different Operator Profile


In that way the Manged Service Provider and/or the Operator can decide or restrict which images that can be used by the Customer

2. Customer specific Gateway Handoff configuration 

This function has not changed but it has been moved to a different hierarchy, which is not that easy to find

 

Customer > Global Settings > Customer Configuration > Gateway Pools


In my next blog I will have a look into some newer monitoring and troubleshooting features of version 5.2


Comments

  1. StephanAugust 30, 2023 at 9:08 PM

    Schön dass du wieder zurück bist mit neuem Content. Ich dachte du würdest gar nichts mehr mit Velocloud machen. Mit welcher Subversion von 5.2 hast du denn getestet? Da tut sich nämlich gerade viel und gerade Softwareupdates gehen jetzt eigentlich.

    ReplyDelete
    Replies
    1. AlexanderAugust 31, 2023 at 7:37 AM

      I am using version 5.2.0.2 on edges and gateways and 5.2.0.3 on VCO. As there are some slight problems with the VCO regarding displaying Firewall Flow I will soon upgrade to 5.3.0.x (available only for the VCO)

      Delete

Post a Comment

Popular posts from this blog

Orchestrator Upgrade to Version 5.2

Image
 Recently I upgraded my VMware SD-WAN lab from version 5.0 to 5.2. Since some previous versions the official documentation  recommends to ask TAC for help in upgrading.   Docu 5.2: Orchestrator Upgrade  But if you have an unsupported implementation, like I do, you need to do it on your own: Trying to copy the new version to the VCO failed and I found out that I needed to increase a disk volume How to increase disk volume on VCO is described in this blog:   VCO Upgrade to 4.5.x After increasing the disk size my copy succeeded   NOTE: I did not copy direct to the installation directory including a renaming, as once an upgrade started that file gets deleted and if there are any problems to have to redo the copy from outside.  vcadmin@vco-lab-254:~$ ls -l total 2504488 drwxr-x--- 2 root    root          4096 Aug 31  2022 20220831130007 -rw-rw---- 1 vcadmin vcadmin 2564587520 Aug 10 07:57 vco-debs-signed-5.2.0.3-R5203-20230809-GA-ff5cd1917e.tar vcadmin@vco-lab-254:~$ sudo cp vco-debs-signed
Read more

Deep Dive on DMPO and its Performance Features (available and missing) Part 1

Image
 In the last year I got quite deep insight into ther vendors SD-WAN implementation and also have seen what various vendors are critizising about the VMware DMPO features. Also there are a lot of misconceptions on the market around some of these features. So let´s try and evaluate and look a little bit deeper into typical performance features and the VMware implementation of them Features discussed in this Blog (Part 1) Per Packet Load Balancing Forward Error Correction (FEC) Packet Replication Latency Remediation The following Features will be discussed in Part 2 of my blog TCP Optimization Techniques Dejitter Buffering SAAS Application Monitoring   Per Packet Load Balancing  Unfortunately this term can be quite easily misinterpreted, when you Google for the term and get the following result:  This behaviour (often criticized by other vendors about VMware) as described above would only work quite well when you have very similar or equal connections. If for example 2 links have  both 10
Read more

Deep Dive on DMPO and its Performance Features (available and missing) Part 2

Image
  The following Features will be discussed in this second part of my blog TCP Optimization Techniques Dejitter Buffering SAAS Application Monitoring   Before diving into the mechanism here an important basic fact:     Remediation is never done for applications classified as LOW priority     TCP optimization TCP has some embedded traffic management capabilities for reliable traffic delivery  (window.size, slow-start, RTT handling,...)  But there are a bunch of factors which can negatively influence the performance, like Latency TCP-slow-start Last Mile network problems Out of Sequence packets Busty losses end host TCP limitations (missing fatures like SACK, windows scaling or timestamp options)  Typically TCP optimization helps on the transmission side and improve the download time for large data transfers over latency-high and lossy WAN links. But it can also be used for improving perfomance when on the receiver side the amount of buffers is limited and/or when the client is n
Read more