* To check the RBCP agent current status, use the '''/etc/init.d/cisco-rbcp status''' command.

* To check the RBCP agent current status, use the '''/etc/init.d/cisco-rbcp status''' command.

+

+

===Q. How do I enable or disable the debug level logging for the RBCP Agent?===

+

+

'''A.''' To enable or disable the debug level logging for the RBCP Agent, do the following:

+

+

'''1.''' Enable Remote Tech Support (SSH) from the DCUI or the vSphere Client, and then SSH to the VMware vSphere Hypervisor<sup>TM</sup> host.

+

+

'''2.''' Do one of the following as appropriate:

+

+

* To enable the debug level logging for the RBCP Agent, use the '''esxcfg-advcfg --user-var CiscoRBCPDebugLevel --set-user-var 1''' command.

+

+

* To disable the debug level logging for the RBCP Agent, use the '''esxcfg-advcfg --user-var CiscoRBCPDebugLevel --set-user-var 0''' command.

+

+

'''3.''' Reboot the VMware vSphere Hypervisor<sup>TM</sup> host for the setting to take effect.

===Q. How do I set the clock on the VMware vSphere Hypervisor?===

===Q. How do I set the clock on the VMware vSphere Hypervisor?===

Line 294:

Line 319:

* Make sure that the appropriate installation files are in the FTP server:

* Make sure that the appropriate installation files are in the FTP server:

-

- sre-v-k9-r.spa.smv.1.5.1.pkg—For Cisco SRE 900 Service Module

+

- sre-v-k9-r.spa.smv.1.5.1.pkg—For Cisco SRE 900 Service Module

-

- sre-v-k9.spa.smv.1.5.1.pkg—For Cisco SRE 700 Service Module

+

- sre-v-k9.spa.smv.1.5.1.pkg—For Cisco SRE 700 Service Module

* View the SRE installation log files to determine the cause of the installation failure. To view the SRE installation log files, enter the following command:

* View the SRE installation log files to determine the cause of the installation failure. To view the SRE installation log files, enter the following command:

Line 329:

Line 354:

'''Problem:''' After using the '''service-module sm slot/0 install url url argument keep-ds''' command to install Cisco SRE-V, the renamed virtual machines change back to their original names.

'''Problem:''' After using the '''service-module sm slot/0 install url url argument keep-ds''' command to install Cisco SRE-V, the renamed virtual machines change back to their original names.

-

'''Probable Cause:''' This is expected behavior. This problem occurs because when you use the '''keep-ds''' argument with the installation command, the disk data is retained, but vSphere Client is restored to its default settings. Therefore, the names of the virtual machines change back to their original names.

+

'''Probable Cause:''' This is expected behavior. This problem occurs because when you use the '''keep-ds''' argument with the installation command, disk data is retained but the vSphere Client is restored to its default settings. Therefore, the names of the virtual machines change back to their original names.

'''Solution:''' Rename the virtual machines.

'''Solution:''' Rename the virtual machines.

Line 399:

Line 424:

'''1.''' Make sure that you can ping the host IP address.

'''1.''' Make sure that you can ping the host IP address.

-

'''2.''' Right-click the hostname, and then choose '''connect'''.

+

'''2.''' Right-click the hostname, and then choose '''Connect'''.

===Orphaned Virtual Machine in the vCenter Server===

===Orphaned Virtual Machine in the vCenter Server===

Line 415:

Line 440:

'''4.''' Right-click the vmx file, which is located in the virtual machine folder, and then choose '''Add to Inventory'''. The virtual machine that was grayed out is now active.

'''4.''' Right-click the vmx file, which is located in the virtual machine folder, and then choose '''Add to Inventory'''. The virtual machine that was grayed out is now active.

-

===Cannot connect to the vCenter Server===

+

===Cannot Connect to the vCenter Server===

'''Problem:''' You cannot connect to the vCenter Server even though network connectivity is available.

'''Problem:''' You cannot connect to the vCenter Server even though network connectivity is available.

'''Problem:''' Helper install fails and you get the following error message:

'''Problem:''' Helper install fails and you get the following error message:

Line 569:

Line 594:

aesop application error.

aesop application error.

-

'''Probable Cause:''' If the SATA mode of the Cisco SRE Service Module was previously set to IDE mode, and then you try to install the Cisco SRE-V 1.1 software using the helper install, the installation fails. Cisco SRE-V 1.1 is only functional when the SATA mode on the Cisco SRE Service Module is set to AHCI.

+

'''Probable Cause:''' If the SATA mode of the Cisco SRE Service Module was previously set to IDE mode, and then you try to install the Cisco SRE-V 1.5 software using the helper install, the installation fails. Cisco SRE-V 1.5 is only functional when the SATA mode on the Cisco SRE Service Module is set to AHCI.

Q. Is the vSphere Client bundled with the Cisco SRE-V software package?

A. No, the vSphere Client is not bundled with the Cisco SRE-V software package. You must download it after you install Cisco SRE-V.

To download the vSphere Client, do the following:

1. Go to https://hypervisor-ip-address. You are directed to the VMware website, and the Welcome page opens.

2. Click Download vSphere Client, and then click Run to download the vSphere Client. The VMware vSphere Client is installed and a shortcut icon to the client appears on your desktop.

Note: To download the vSphere Client, connection to the Internet is required.

Q. How do I know which type of Cisco SRE Service Module is installed in the router from a Microsoft Windows virtual machine?

A. To determine which type of Cisco SRE Service Module is installed in your router, do the following:

From the Microsoft Windows virtual machine, choose System > Properties. From the CPU and processor information, you can determine the type of Cisco SRE Service Module, whether it is a Cisco SRE 700 Service Module or a Cisco SRE 900 Service Module:

Cisco SRE 700 Service Module—Solo CPU and Processor Type L3400

Cisco SRE 900 Service Module—Duo CPU and Processor Type L9400

Q. What is the correct syntax for using the FTP credentials in the installation and upgrade URL?

A. The correct syntax for using the FTP credentials in the installation URL is:

4. Follow the wizard steps to manually add the datastore to the inventory.

5. Click the Refresh and Rescan All... buttons. The datastore should now be visible from the Management virtual machine.

Module Does Not Respond After Using the Cisco SRE-V Install or Uninstall Commands

Problem: Occasionally, after using the Cisco SRE-V install or uninstall commands, the Cisco SRE Service Module does not respond.

Solution: To resolve this problem, verify that the router is using the supported Cisco IOS version, which is 15.1(4)M or later. Use the show version command to verify the Cisco IOS version.

If the Cisco IOS version that is installed on the router is not supported, install the appropriate Cisco IOS version.

If the Cisco IOS version that is installed on the router is supported, and the service module still does not respond, reset the service module and then install Cisco SRE-V again. Use the service-module sm slot/0 reset command to reset the service module:

Router# service-module sm 1/0 reset

Cisco SRE-V Installation Fails

Problem: Cisco SRE-V installation does not work.

Solution: To resolve this problem, do the following:

Make sure that you are able to ping the FTP server from the router.

Make sure that the FTP server is able to reach the service-module ip addresshypervisor-ip-address subnet-mask that was configured on the router.

Make sure that the appropriate installation files are in the FTP server:

- sre-v-k9-r.spa.smv.1.5.1.pkg—For Cisco SRE 900 Service Module

- sre-v-k9.spa.smv.1.5.1.pkg—For Cisco SRE 700 Service Module

View the SRE installation log files to determine the cause of the installation failure. To view the SRE installation log files, enter the following command:

Router# Debug sre-install all

View the service module console log files to determine the cause of the installation failure. To view the service module console log files, enter the following command after executing the installation command:

Probable Cause: This problem occurs because when you use the keep-ds argument with the installation command, the datastores and the virtual machines are retained, but you must manually add the virtual machines back into the inventory.

Solution: To manually add the virtual machines back into the inventory, do the following:

1. Choose Inventory > Configuration > Storage > Datastore.

2. Browse to the datastore for the appropriate virtual machine folder.

3. Right-click the vmx file, which is located in the virtual machine folder, and then choose Add to Inventory. The virtual machines appear in the vSphere Client.

New Virtual Machine Names Not Reflected After Cisco SRE-V Installation with keep-ds Argument

Problem: After using the service-module sm slot/0 install url url argument keep-ds command to install Cisco SRE-V, the renamed virtual machines change back to their original names.

Probable Cause: This is expected behavior. This problem occurs because when you use the keep-ds argument with the installation command, disk data is retained but the vSphere Client is restored to its default settings. Therefore, the names of the virtual machines change back to their original names.

Solution: Rename the virtual machines.

Virtual Machine Troubleshooting

Microsoft Windows License Activation Fails after Export and Import of the Virtual Machine

Problem: You exported a virtual machine and then imported it back, and you noticed that the Microsoft Windows software license activation failed.
Further Problem Description: You purchased the Cisco SRE-V Option 3 (Hardware, plus Virtualization software, plus Microsoft Windows software), and a virtual machine was provided to you by default. Both the Virtualization software license and the Microsoft Windows software license on this virtual machine were preactivated. You exported this virtual machine and then imported it back, and you noticed that the Microsoft Windows software license activation failed.

Probable Cause: This problem could occur for the following reasons:

Some of the configuration lines in the OVF file are missing.

Some of the VMX file parameters are missing.

Solution: To resolve this problem, do the following:

Manually add the following configuration lines to the OVF file in the Virtual Hardware section:

Verify that the VMX file contains the following parameters. If these parameters are missing, you must add them:

uuid.action = “create”
pcie.reportDataLink= “TRUE”

Cannot Modify the Advanced Settings Parameters in the vSphere Client

Problem: You cannot modify the Advanced Settings parameters.

Further Problem Description: From the vSphere client, go to Home > Inventory. From the left navigation tree, click the host name. Click the Configuration tab. From the left pane, under Software, choose Advanced Settings. The Advanced Settings page opens with several parameters. When you try to modify the Advanced Settings parameters, you notice that the OK button is disabled and you cannot modify the parameters.

Cause: The Advanced Settings parameters are intentionally blocked by Cisco Systems because they contain critical configuration, which you cannot modify.

Solution: There is no workaround.

Virtual Machine Cannot Mount the USB Thumb Drive

Problem: The virtual machine cannot mount the USB Thumb Drive.

Probable Cause: This problem occurs when the USB Thumb Drive that was used and formatted by a Microsoft Windows virtual machine was again used on a Linux-based virtual machine.

Solution: Use a new USB Thumb Drive.

Cannot Activate the Microsoft Windows License on a Virtual Machine

Problem: You cannot activate the Microsoft Windows license on a virtual machine.

Solution: To resolve this problem, do the following:

1. Use the show oem marker command to verify the OEM marker.

2. Make sure that the virtual machine is not a third-party virtual machine.

3. Make sure that the virtual machine is installed by Cisco manufacturing or is imported using the recovery DVD.

4. Make sure that the ACPIPassthrough setting is enabled in the virtual machine. To do so, check the Microsoft Windows hardware vendor information or the vmx file.

If the virtual machine is exported and then re-imported, see the appropriate user documentation for the procedure to enable the ACPI Passthrough setting.

vCenter Troubleshooting

Disconnected Host in vCenter Server

Problem: The host appears disconnected and is grayed out in the vCenter Server.

Solution: To resolve this problem, do the following:

1. Make sure that you can ping the host IP address.

2. Right-click the hostname, and then choose Connect.

Orphaned Virtual Machine in the vCenter Server

Problem: There is an orphaned and grayed out virtual machine in the vCenter Server.

Solution: To resolve this problem, do the following:

1. Remove the virtual machine from the inventory. Right-click the virtual machine and then choose Remove from Inventory.

2. Choose Inventory > Configuration > Storage > Datastore.

3. Browse to the datastore for the appropriate virtual machine folder.

4. Right-click the vmx file, which is located in the virtual machine folder, and then choose Add to Inventory. The virtual machine that was grayed out is now active.

Cannot Connect to the vCenter Server

Problem: You cannot connect to the vCenter Server even though network connectivity is available.

Solution: To resolve this problem, do the following:

1. Open services in the PC that has the vCenter Server.

2. Manually start the vCenter Server service and then try to connect again.

RAID Troubleshooting

Cannot View Datastores

Problem: After disk migration, reboot, or Cisco SRE-V software upgrade, you are unable to view the datastores in Inventory > Configuration > Storage.

Solution: To resolve this problem, do the following:

1. Rescan the system a couple of times. From the vSphere Client GUI Home page, do the following:

d. From the right pane, choose Disk/LUN, and then click Next. The Select Disk/LUN wizard page opens.

e. From the right pane, choose a disk, and then click Next. The Select VMFS Mount Options wizard page opens.

f. From the right pane, choose the Assign a New Signature radio button, and then click Next.

g. Choose Free Space, and then click Finish.

The missing datastores display with a modified name, which you can change. For example, Datastore_R0 displays as snap-XXXXX-datastore_R0; and datastore_R1 displays as snap-XXXXX-datastore_R1. To change the name of the datastore, right-click the appropriate datastore, and the choose Rename.

Datastore Name is Displayed as snap-XXXXX-datastore_datastore_name

Problem: After adding a new datastore in vSphere Client, the datastore displays with the name: snap-XXXXX-datastore_datastore_name.

Solution: This is a know problem. You can change the name of the datastore. To change the name, right-click the appropriate datastore, and then choose Rename.

Rebuild Process Does Not Start

Problem: After hot-swapping the faulty RAID 1 disk drive, the rebuild process does not start.

Probable Cause: RAID configuration shows a new JBOD logical volume, which you must delete.

Solution: To resolve this problem, do the following:

1. From the RAID management CLI, use the logdrv command to view RAID configuration.

When the valid partition table appears on the newly inserted drive, you might notice that the RAID configuration is unbalanced, as shown in the following example:

Cannot Create Datastores on a Single Disk RAID 0 Array

Solution: Use the init –a start –l 0 –i 0 -q command on the logical drive where you want to create the datastore.

RAID Troubleshooting Tips

Modifying RAID Configuration

If you are making any changes to the RAID configuration, make sure that you delete all datastores.

If you are using the RAID migration procedure to migrate between RAID levels, you do not need to delete datastores.

Orphan Configuration in VMware

Before using RAID management commands to change or delete a logical drive configuration, make sure that you delete the associated datastore. If you do not delete the associated datastores, an orphan configuration remains in the system.

Error Messages

Error Message: File or Directory on the Remote Server Cannot be Accessed

Problem: After entering the import command, you get the following error message:

File or directory on the remote server cannot be accessed.

Solution: To resolve this problem, do the following:

Verify that the ftp server directory has read/write permissions.

Verify that the username and password of the ftp server are correct.

Error Message: Aesop Application Error

Problem: Helper install fails and you get the following error message:

aesop application error.

Probable Cause: If the SATA mode of the Cisco SRE Service Module was previously set to IDE mode, and then you try to install the Cisco SRE-V 1.5 software using the helper install, the installation fails. Cisco SRE-V 1.5 is only functional when the SATA mode on the Cisco SRE Service Module is set to AHCI.