Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

VMware Site Recovery Manager dr-ip-customizer.exe utility fails (1009856)

Last Updated: 4/1/2015Categories: TroubleshootingTotal Views: 9814Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

The VMware vCenter Site Recovery Manager (SRM) dr-ip-customizer.exe utility fails to run

When you run dr-ip-customizer.exe utility from the command line, you see entries similar to:

C:\Program Files\VMware\VMware Site Recovery Manager\bin>dr-ip-customizer.exe -cfg ..\config\vmware-dr.xml -csv c:\EG2.C SV -cmd recreate
Using config file: ..\config\vmware-dr.xml

['App' 2728 info] Current working directory: C:\Program Files\VMware\VMware Site Recovery Manage r\bin
['ThreadPool' 2728 verbose] TaskMax=10, IoMin=1, IoMax=21
['App' 2728 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
['CredentialsStore' 2728 trivia] Checking existence of stored credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Stored credentials for key='db:SRM' exist: True
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieving credentials, key='db:SRM'
['CredentialsStore' 2728 trivia] Retrieved credentials, key='db:SRM'
['Vdb' 2728 trivia] VdbStatement::Execute(): Executing statement 'select id from sequence_table where name = ?'
['Vdb' 2728 trivia] VdbStatement::Execute(): Executing statement 'select value from dr_product_i nfo where name = 'version''
Error on line number '2': The IP Address field is invalid. The Subnet Mask field is invalid. The Gateway field is invalid.

Solution

This issue is caused by incorrect formatting of the entries in the CSV file.

Customization specifications for each virtual machine have properties that may have multiple values. The scheme for representing multiple values for a single entity over many rows is done through the use of identifiers.

Each adapter that belongs to a virtual machine has its own identifier, in virtual PCI slot order. Information about each adapter can then be listed across multiple rows.

The adapter ID of 0 has special meaning in that it specifies the Global IP Settings. Global IP Settings constitute the IP settings not specific to a particular network adapter. Adapter ID = 0 should only populate Shadow VM ID, VM Name, Adapter ID, DNS Server(s), and DNS Suffix(es) if any are to be populated.

Common information should go into the adapter ID = 0. If there are no global IP settings specified in the DNS Server(s) or DNS Suffix(es) columns then none are applied.

You can populate the fields how you want, provided that you do not enter duplicate values for properties that can only hold one value. For example, do not have two rows for adapter ID = 1 that both define a DNS domain, or for adapter ID = 0 to define a MAC Address or IP Address.

You typically use a single row per adapter that defines as much as possible. When there are multiple values, add a new row. Each row is processed and appended to a single adapter definition.

There are two files attached to this article. 1009865_incorrect.zip highlights the incorrect format for the CSV file. 1009865_correct.zip highlights the correct format and demonstrates how to successfully construct a CSV file that can be parsed by the dr-ip-customizer.exe utility.

Additional Information

When you run dr-ip-customizer.exe command, you see the output:

Input argument error

Ensure that all long parameter names begin with two dashes.

For example:

dr-ip-customizer.exe -cfg ..\config\vmware-dr.xml --cmd generate --out c:\dr\newoutput.csv --vc co-atl-vcenter.domain.local

In the above example, the -cfg parameter is incorrect. The correct usage is:

dr-ip-customizer.exe --cfg ..\config\vmware-dr.xml --cmd generate --out c:\dr\newoutput.csv --vc co-atl-vcenter.domain.local

Note the two dashes before cfg.

For more information about the dr-ip-customizer.exe utility, see the VMware vCenter Site Recovery Manager Documentation.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

1009856_incorrect.zip

1009856_correct.zip

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

Related Versions:

VMware vCenter Site Recovery Manager 5.8.x

VMware vCenter Site Recovery Manager 5.5.x

VMware vCenter Site Recovery Manager 5.1.x

VMware vCenter Site Recovery Manager 5.0.x

VMware vCenter Site Recovery Manager 4.1.x

VMware vCenter Site Recovery Manager 4.0.x

VMware vCenter Site Recovery Manager 1.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant