cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
247
Views
0
Helpful
6
Replies

How to detach offline devices from vManage

Kenneth Goh
Beginner
Beginner

Please advice what can be done to configure my cEdge. My cEdge router is currently unreachable and I am not able to detach it from device template nor can i make changes via CLI. Thanks in advanced.

KennethGoh_2-1685008395049.png

cEdge-30(config)# no ip route 0.0.0.0 0.0.0.0 10.1.15.13
cEdge-30(config)# commit
Aborted: 'system is-vmanaged': Commit from vManage is in progress. Configuration through the CLI is not allowed.

Device 'grey out', cannot be detach from device template

KennethGoh_1-1685008354239.png

 

2 Accepted Solutions

Accepted Solutions

iamdheerajdubey
Beginner
Beginner

Hi,

To switch to CLI mode from vManaged in Cisco vManage, you can follow these steps:

  1. Access the vManage dashboard.
  2. Navigate to Configuration >> Devices.
  3. Select the desired device from the list.
  4. At the top of the page, locate the "Change Mode" tab and click on it.
  5. Click on the CLI mode option.

If the above steps do not work, an alternative approach is to change the mode through the device's CLI with the assistance of Cisco TAC. Please note that this method requires TAC support. Follow these instructions:

  1. Access the device's CLI.
  2. Enter the command "unhide viptela_internal". This command will prompt you for a password.
  3. Contact Cisco TAC to obtain the required password.
  4. Enter the password provided by TAC.
  5. Switch to configuration mode by entering the command "config".
  6. Execute the command "no system is_vmanaged" to disable the vManaged mode.
  7. You are now in CLI mode.

It is important to reach out to Cisco TAC for assistance during the process to ensure a smooth transition. We hope this information is helpful.

Refer: Troubleshooting Commands for Cisco SD-WAN

View solution in original post

Check the alternate approach, till the device is completely de-attached from vManage you won't be able to make any changes. Raise a TAC case ask for "unhide viptela_internal" password set the "system is_vmanaged" flag to no and perform the required action.

View solution in original post

6 Replies 6

Kanan Huseynli
Rising star
Rising star

Hi,

normally, CLI is allowed if you lost connection to vManage, so if really there is no connection, you can do changes in (but will be overridden by vManage when connection is restored). Could you verify via clie with "show sdwan control connections" ?

Also, sometimes deployment/config push stucks, you can check with below API for active tasks of vManage:

https://[vmanage-ip]:8443/dataservice/device/action/status/tasks

See, how to clear stucked tasks:

https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/214660-vmanage-api-call-clearing-stuck-task.html

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

There is no task stuck

KennethGoh_1-1685067321263.png

 

 

Re-check control connection from router. If router really lost connection you can do change in CLI.

share from router:

show sdwan control connections

 

HTH,
Please rate and mark as an accepted solution if you have found any of the information provided useful.

iamdheerajdubey
Beginner
Beginner

Hi,

To switch to CLI mode from vManaged in Cisco vManage, you can follow these steps:

  1. Access the vManage dashboard.
  2. Navigate to Configuration >> Devices.
  3. Select the desired device from the list.
  4. At the top of the page, locate the "Change Mode" tab and click on it.
  5. Click on the CLI mode option.

If the above steps do not work, an alternative approach is to change the mode through the device's CLI with the assistance of Cisco TAC. Please note that this method requires TAC support. Follow these instructions:

  1. Access the device's CLI.
  2. Enter the command "unhide viptela_internal". This command will prompt you for a password.
  3. Contact Cisco TAC to obtain the required password.
  4. Enter the password provided by TAC.
  5. Switch to configuration mode by entering the command "config".
  6. Execute the command "no system is_vmanaged" to disable the vManaged mode.
  7. You are now in CLI mode.

It is important to reach out to Cisco TAC for assistance during the process to ensure a smooth transition. We hope this information is helpful.

Refer: Troubleshooting Commands for Cisco SD-WAN

switch to CLI mode from vManaged in Cisco vManage did not work

KennethGoh_2-1685067405240.png

 

Check the alternate approach, till the device is completely de-attached from vManage you won't be able to make any changes. Raise a TAC case ask for "unhide viptela_internal" password set the "system is_vmanaged" flag to no and perform the required action.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers