cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1996
Views
10
Helpful
4
Replies

Unable to delete dvs under epgs on Cisco ACI APIC

b_o28
Level 1
Level 1

Hi!

we had one dvs which is associated epgs. We have deleted it then create a new one. But now we couldn't remove old dvs under epgs. When we try to remove this fault appears:

Failed to delete object.
Request in progress, please check state using URL: /api/checkRequestState.xml?id=9570328849809408

I need your suggestions to solve

 

Regards

1 Accepted Solution

Accepted Solutions

-Our server team deleted the vcenter and then configured new one. But our dvs couldn't get online so we tried to delete dvs.

-We created a new dvs with same vlan-pool,AEP but different datacenter name. It got online. We haven't associated this new dvs with epgs. First we want to delete the old one under epgs.

-The server team said that we don't see any vds or port groups after deleting vds. We didn't any configuration like disconnecting VMs, while server team deleting vcenter. 

-Only our new dvs appears on vCenter . By the way we applied enhanced lag policy may be it is releated this problem. May be we would had to delete lag policy before removing dvs.

-Version of APIC: 4.2(5l)

Firstly, never delete the vDS on vCenter.  If the vDS was created on APIC, remove it from the APIC.  There's no problem created the new VMM (vDS) on APIC, and associating it to your EPGS (even if the old one exists).  The server team can then re-bind their VMs to the correct vDS Port Groups.  The LAG Policy also needs to be created on APIC under the VMM domain.  Hopefully you did this, otherwise you'll see a fault on the VMM domain.   To fix/remove the original vDS, I would recreate it from the APIC with the EXACT same name as appears on VCSA.  Then gracefully remove it from the APIC.  This should clean things up.  If not, open a TAC case and they'll assist.

Robert

 

View solution in original post

4 Replies 4

Robert Burns
Cisco Employee
Cisco Employee

Going to need more info:

-How did you delete the original vDS?

-Did you create the new vDS with the exact same name or different?

-Did you disconnect all VMs from the Port Groups on vCenter before removing the original vDS?

-Are both vDS still showing on vCenter?

-Which version of APIC

Robert

-Our server team deleted the vcenter and then configured new one. But our dvs couldn't get online so we tried to delete dvs.

-We created a new dvs with same vlan-pool,AEP but different datacenter name. It got online. We haven't associated this new dvs with epgs. First we want to delete the old one under epgs.

-The server team said that we don't see any vds or port groups after deleting vds. We didn't any configuration like disconnecting VMs, while server team deleting vcenter. 

-Only our new dvs appears on vCenter . By the way we applied enhanced lag policy may be it is releated this problem. May be we would had to delete lag policy before removing dvs.

-Version of APIC: 4.2(5l)

 

Thank you

-Our server team deleted the vcenter and then configured new one. But our dvs couldn't get online so we tried to delete dvs.

-We created a new dvs with same vlan-pool,AEP but different datacenter name. It got online. We haven't associated this new dvs with epgs. First we want to delete the old one under epgs.

-The server team said that we don't see any vds or port groups after deleting vds. We didn't any configuration like disconnecting VMs, while server team deleting vcenter. 

-Only our new dvs appears on vCenter . By the way we applied enhanced lag policy may be it is releated this problem. May be we would had to delete lag policy before removing dvs.

-Version of APIC: 4.2(5l)

Firstly, never delete the vDS on vCenter.  If the vDS was created on APIC, remove it from the APIC.  There's no problem created the new VMM (vDS) on APIC, and associating it to your EPGS (even if the old one exists).  The server team can then re-bind their VMs to the correct vDS Port Groups.  The LAG Policy also needs to be created on APIC under the VMM domain.  Hopefully you did this, otherwise you'll see a fault on the VMM domain.   To fix/remove the original vDS, I would recreate it from the APIC with the EXACT same name as appears on VCSA.  Then gracefully remove it from the APIC.  This should clean things up.  If not, open a TAC case and they'll assist.

Robert

 

I configured a new vmm domain with exact same config that exist on old vmm domain. Then I applied LAG pollicy as the same old dvs.The problem was solved. All faults have  cleared on APIC. Thanks for your supports 

Save 25% on Day-2 Operations Add-On License