Cisco Catalyst SD-WAN Upgrade Guide

PDF

Cisco Catalyst SD-WAN Upgrade Guide

Upgrade memory and vCPU resources on a virtual machine hosting Cisco Catalyst SD-WAN Manager

Want to summarize with AI?

Log in

Learn how to upgrade memory and vCPU resources on a virtual machine hosting Cisco SD-WAN Manager . This procedure describes the steps to increase resources and verify the upgrade.


Only memory or vCPU increase is allowed. After the memory or vCPU is upgraded, you cannot downgrade.

Procedure

  1. Check the current configuration on Cisco SD-WAN Manager using the show system status command.

    vManage# show system status
    Viptela (tm) vmanage Operating System Software
    Copyright (c) 2013-2021 by Viptela, Inc.
    Controller Compatibility: 
    Version: 20.7.0-185
    Build: 185
    System logging to host  is disabled
    System logging to disk is enabled
    System state:            GREEN. All daemons up
    System FIPS state:       Enabled
    Testbed mode:            Enabled
    Engineering Signed:      True
    Last reboot:             Initiated by user. 
    CPU-reported reboot:     Not Applicable
    Boot loader version:     Not applicable
    System uptime:           1 days 02 hrs 44 min 52 sec
    Current time:            Sat Oct 23 22:12:10 UTC 2021
    Load average:            1 minute: 14.58, 5 minutes: 12.31, 15 minutes: 10.73
    Processes:               5775 total
    CPU allocation:          32 total
    CPU states:              31.58% user,   4.36% system,   64.06% idle
    Memory usage:            65741448K total,    38096172K used,   490324K free
                             4606444K buffers,  22548508K cache
    Disk usage:              Filesystem      Size   Used  Avail   Use %  Mounted on
                             /dev/root       15230M  3496M  10898M   24%   /
    vManage storage usage:   Filesystem      Size  Used  Avail  Use%  Mounted on
                             /dev/sdb        502942M  206906M  270435M   41%   /opt/data
    Personality:             vmanage
    Model name:              vmanage
    Services:                None
    vManaged:                false
    Commit pending:          false
    Configuration template:  None
    Chassis serial number:   None
                        
  2. Power the device down to upgrade the memory.

  3. Upgrade the CPU and memory for the VM using the guidelines of the hosting platform. You can make the following upgrades:

    Resources

    Current

    Upgrade

    vCPU

    16

    32

    Memory

    32 G

    64 G or 128 G

    Memory

    64 G

    128 G

  4. Power on the device and verify the memory and CPU.

    vManage1# show system status
    Viptela (tm) vmanage Operating System Software
    Copyright (c) 2013-2021 by Viptela, Inc.
    Controller Compatibility: 
    Version: 20.7.0-139
    Build: 139
    System logging to host  is disabled
    System logging to disk is enabled
    System state:            GREEN. All daemons up
    System FIPS state:       Enabled
    Testbed mode:            Enabled
    Engineering Signed:      True
    Last reboot:             Initiated by user - activate 20.7.0-139. 
    CPU-reported reboot:     Not Applicable
    Boot loader version:     Not applicable
    System uptime:           16 days 17 hrs 43 min 28 sec
    Current time:            Sat Oct 23 22:22:16 UTC 2021
    Load average:            1 minute: 15.86, 5 minutes: 13.02, 15 minutes: 11.45
    Processes:               6067 total
    CPU allocation:          32 total
    CPU states:              32.13% user,   4.34% system,   63.53% idle
    Memory usage:            131703148K total,    88221488K used,   19285636K free
                             7022488K buffers,  17173536K cache
    Disk usage:              Filesystem      Size   Used  Avail   Use %  Mounted on
                             /dev/root       15998M  10702M  4461M   71%   /
    vManage storage usage:   Filesystem      Size  Used  Avail  Use%  Mounted on
                             /dev/sdb        10402115M  702212M  9175615M   6%   /opt/data
    Personality:             vmanage
    Model name:              vmanage
    Services:                None
    vManaged:                false
    Commit pending:          false
    Configuration template:  None
    Chassis serial number:   None