Skip to main content
Solved

Veeam CDP error


Forum|alt.badge.img+1
  • Comes here often
  • 77 comments

Hey guys,

I tried to install I/O filters on vCenter for CDP and it showing the error “ the operation is not allowed in current state” . Can anyone tell why it is showing like this and suggest what needs to be done. Please refer the screenshot for more details.

 

Best answer by MicoolPaul

Okay, the operation is not allowed in current state message will be being passed back from vSphere, so I suggest reading the full Veeam logs for any extra verbose information, and then checking in your vCenter logs as to any particular hosts it had an issue with etc.

View original
Did this topic help you find an answer to your question?

16 comments

MicoolPaul
Forum|alt.badge.img+23

Have you got any hosts offline or in maintenance mode? What version of ESXi are they running?


Forum|alt.badge.img+1
  • Author
  • Comes here often
  • 77 comments
  • June 1, 2022
MicoolPaul wrote:

Have you got any hosts offline or in maintenance mode? What version of ESXi are they running?

The ESXi version is 7.0.3 and the we got no hosts running offline or maintenance mode


MicoolPaul
Forum|alt.badge.img+23
  • 2358 comments
  • Answer
  • June 1, 2022

Okay, the operation is not allowed in current state message will be being passed back from vSphere, so I suggest reading the full Veeam logs for any extra verbose information, and then checking in your vCenter logs as to any particular hosts it had an issue with etc.


vNote42
Forum|alt.badge.img+13
  • On the path to Greatness
  • 1246 comments
  • June 1, 2022

vNote42
Forum|alt.badge.img+13
  • On the path to Greatness
  • 1246 comments
  • June 1, 2022

And when I remember correctly, DNS is mandatory for CDP filter driver installation:

https://forums.veeam.com/vmware-vsphere-f24/v11-install-cdp-t72139.html


Geoff Burke
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • 1313 comments
  • June 1, 2022

I had this on the weekend. DNS was the issue, I could not figure out when my problem was and ran out of time in the lab so in the end I just did host file entries to get it working. 


MicoolPaul
Forum|alt.badge.img+23

Considering that the screenshot shows an IP address, looks like @Geoff Burke & @vNote42 are into the right answer here talking DNS.


vNote42
Forum|alt.badge.img+13
  • On the path to Greatness
  • 1246 comments
  • June 1, 2022

Iams3le
Forum|alt.badge.img+11
  • Veeam Legend
  • 1374 comments
  • June 1, 2022
vNote42 wrote:

I agree with you and @Geoff Burke. All vital guides shared by you all point to DNS. I hope these tip(s) will be enough to help resolve his issue.


Chris.Childerhose
Forum|alt.badge.img+21
vNote42 wrote:

DNS is needed as noted with CDP. When I tested it in my lab for my book chapter I had the same issues until I addressed DNS then it worked no problem.


  • New Here
  • 1 comment
  • October 29, 2023

Hi team , i have a little question.

 

I try configure CDP in a veeam v12 (last patch), but my server is without domain ( i’m following de the “best practices”) so, i think that i need configure the “hosts” file to get the correct dns of my vcenter.

 

But i still with the failure, someone know if i can use the “hosts file” for correct the failure?

or

¿Someone knows wich is the correct configuration for this file?


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8402 comments
  • October 30, 2023
jmramirez wrote:

Hi team , i have a little question.

 

I try configure CDP in a veeam v12 (last patch), but my server is without domain ( i’m following de the “best practices”) so, i think that i need configure the “hosts” file to get the correct dns of my vcenter.

 

But i still with the failure, someone know if i can use the “hosts file” for correct the failure?

or

¿Someone knows wich is the correct configuration for this file?

If you need to do hostnames use the hosts file to do it. Easiest way around it without domain.


It was also DNS for me, but I will explain why and how I resolved it without editing hosts file.

First some background on my home lab setup:

vSphere 8u2 (evaluation)

VBR 12.1

2x Intel NUC 13th Gen w/ ESXi baremetal

VMware Workstation Pro 17.5 (Windows Desktop)

VCSA8 (VM inside Workstation)
1x Windows DNS server (VM in Workstation) with manual A and PTR records

Of course, I thought, no way it is DNS 😈, all of my backup and replication jobs are working fine! I had no issue adding all the components to my VBR server. I can see all the VMs and datastores in Inventory. I can ping and nslookup from VBR and DNS (Windows) to all the VMware infrastructure and back. All the IP/FQDNs are resolving fine!

EXCEPT, when I double-checked nslookup from the vCenter, (after enabling SSH and shell, with PuTTY and root credentials) vCenter was resolving IP/FQDN to the VBR fine but NOT resolving the VBR short name.

example:

nslookup vbr01.mydomain.local = returned the correct IP

nslookup IP_address_of_vbr01 = returned correct FQDN

nslookup vbr01 = failed to find server

I considered adding another DNS entry for short names or editing the hosts file on vCenter, but those seem messy and vi editor doesn’t like me 😀. That must be why I didn’t have any luck trying to edit ‘/etc/resolv.conf’. I decided to check my vCenter DNS settings again, since I am not using a domain controller.

My issue was mostly with the VCSA Direct Console UI (DCUI). I could not save a Custom DNS Suffix in the GUI, it would always fail. However, using the CLI utility, I was able to add a Custom DNS Suffix for my lab domain and then nslookup to the short names was working!

user swint commented:

SSH to the vCenter as root, type "shell" to get to the bash shell, then run the following cli tool.

/opt/vmware/share/vami/vami_config_net

Installing I/O filters failed again, BUT this time for a different error! Progress!

Veeam already had a KB for that issue with vSphere Lifecycle Manager
https://www.veeam.com/kb4096

After remediating all the hosts, I/O Filters were installed and I ran my first CDP Replication policy with SUCCESS!🤑


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8402 comments
  • January 15, 2024

Great to hear @DerekDavis that you fixed the issue and nice to see the steps for others to follow.  😎


  • New Here
  • 8 comments
  • October 17, 2024

@DerekDavis - thank you for the hint.

Exact Virtual Lab scenario. Resolving with FQDN worked on VCENTER, ESXI, VBR, so I also thought that it couldn’t be DNS. Then SSH to vcenter and pinging to short hostname, bang, exactly :) thanks again.

 


Forum|alt.badge.img
  • Experienced User
  • 44 comments
  • October 18, 2024

I’ve found that it’s almost always DNS :) If not, remediation of the hosts was missed in a few cases.  


Comment