Cisco UCS Director Open Automation Troubleshooting Guide, Release 5.4

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco UCS Director Open Automation Troubleshooting Guide, Release 5.4

Chapter Title

Open Automation Troubleshooting

Results

Chapter: Open Automation Troubleshooting

Open Automation Troubleshooting

Troubleshooting

How do I verify if my module was registered with the platform?

Recommended Solution

Enable com.cloupia.service.cIM.inframgr=DEBUG under the logging.properties file, in the /opt/infra/inframgr directory. If debug was enabled you will find: jar to be loaded:jar:, as well as "Loading feature class." If you do not find the following error "Error while loading feature classes for " after a few lines, then your module was added successfully.

They can check whether the module features are getting uploaded successfully in UCSD after uploading zip file and restarting the UCSD by verifying the following 3 items existence in /opt/infra/inframgr/features folder <moduleId>.feature file example ‹>dummy.feature Feature-<moduleId>.jar example ‹> feature-dummy.jar <moduleId> folder example ‹> dummy

How do I verify if my report was registered successfully?

Recommended Solution

Enable log4j.logger.com.cloupia.service.cIM.inframgr.reports.simplified=DEBUG to view the status of the report registration.

I'm not able to select a pod.

Recommended Solution

You must provide the Pod.xml file to define your own pod, and make sure it is the correct UCS Director POD type. If you provide your own Pod.xml, the account create must come under your custom pod.xml.

What do I do if the module is not loading?

Recommended Solution

If your module is not loading, check the following: 

initDynamicFeatures(FeatureContainer.java:295) - Loading feature class com.cisco.feature.tempOA.TempOAModule from feature definition file /opt/infra/inframgr/features/TempOA.feature
2015-08-17 20:58:57,258 [main] ERROR initDynamicFeatures(FeatureContainer.java:317) - Error while loading feature classes for /opt/infra/inframgr/features/TempOA.feature
java.lang.ClassNotFoundException: com.cisco.feature.tempOA.TempOAModule
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        at com.cloupia.service.cIM.inframgr.FeatureContainer.initDynamicFeatures(FeatureContainer.java:305)
        at com.cloupia.service.cIM.inframgr.FeatureContainer.loadFeatures(FeatureContainer.java:197)
        at com.cloupia.service.cIM.inframgr.FeatureContainer.<init>(FeatureContainer.java:52)
        at com.cloupia.service.cIM.inframgr.FeatureContainer.<clinit>(FeatureContainer.java:37)
        at com.cloupia.service.cIM.inframgr.InfraMgrImpl.initService(InfraMgrImpl.java:738)
        at com.cloupia.service.cIM.inframgr.APIProvider.initService(APIProvider.java:217)
        at com.cloupia.fw.services.provider.ServiceProvider.init(ServiceProvider.java:520)
        at com.cloupia.fw.services.provider.ServiceProvider.init(ServiceProvider.java:293)
        at com.cloupia.fw.services.provider.ServiceProvider.init(ServiceProvider.java:267)
        at com.cloupia.service.cIM.inframgr.InfraMgrMain.main(InfraMgrMain.java:176)

If you find this error in your log file, check the module name in the .feature file. Either the path or the module file name is wrong. Verify that the class does not end with .java.

The report displays incorrectly in the menu.—Identify the problem here.

Recommended Solution

Enable the log4j.logger.com.cloupia.service.cIM.inframgr.reports.simplified=DEBUG package to view the following logs: 

Creating Simple Tabular Report Entry for compute.ComputeTabReport
2015-08-13 16:48:38,956 [main] DEBUG createEntry(ReportRegistryProxy.java:370) - ***************Registering Report compute.ComputeTabReport******************************
2015-08-13 16:48:38,956 [main] DEBUG createEntry(ReportRegistryProxy.java:371) - Report name : compute.ComputeTabReport
2015-08-13 16:48:38,957 [main] DEBUG createEntry(ReportRegistryProxy.java:372) - Report Type : 2
2015-08-13 16:48:38,957 [main] DEBUG createEntry(ReportRegistryProxy.java:373) - Is config table false
2015-08-13 16:48:38,957 [main] DEBUG createEntry(ReportRegistryProxy.java:387) - Implementation class : class com.cloupia.feature.compute.reports.ComputeTabReportGenerator
2015-08-13 16:48:38,957 [main] DEBUG createEntry(ReportRegistryProxy.java:389) - Report label ComputeTabReport
2015-08-13 16:48:38,957 [main] DEBUG createEntry(ReportRegistryProxy.java:391) - Show in summary false
2015-08-13 16:48:38,958 [main] DEBUG createEntry(ReportRegistryProxy.java:393) - Map Rules UCSM_COMPUTE, 90305
2015-08-13 16:48:38,958 [main] DEBUG createEntry(ReportRegistryProxy.java:396) - Menu ID 50
2015-08-13 16:48:38,958 [main] DEBUG createEntry(ReportRegistryProxy.java:398) - Context level -1
2015-08-13 16:48:38,959 [main] DEBUG createEntry(ReportRegistryProxy.java:400) - Management report false
2015-08-13 16:48:38,959 [main] DEBUG createEntry(ReportRegistryProxy.java:402) - Embedded report true
2015-08-13 16:48:38,959 [main] DEBUG createEntry(ReportRegistryProxy.java:410) - Report priority : 5
2015-08-13 16:48:38,959 [main] DEBUG createEntry(ReportRegistryProxy.java:419) - Management column index -1
2015-08-13 16:48:38,960 [main] DEBUG createEntry(ReportRegistryProxy.java:425) - Operation level no_check

If you didn't override the getMapRules API for your report, then you will see the report registered under GlobalAdmin context. Your logs should be similar to the following logs: 

Processing hierarchy for report  compute.ComputeEasyReport @ Menu ID: 50
2015-08-13 16:48:38,960 [main] DEBUG preProcessReportHierarchy(ReportRegistryProxy.java:129) - Setting map rule global_admin,10
2015-08-13 16:48:38,978 [main] DEBUG preProcessReportHierarchy(ReportRegistryProxy.java:144) - The Dynamic context level to be used -1
2015-08-13 16:48:38,978 [main] DEBUG registerReportWithActions(ReportRegistryProxy.java:171) - Registering Report compute.ComputeEasyReport as a ConfigTable report
2015-08-13 16:48:38,978 [main] DEBUG registerReportWithActions(ReportRegistryProxy.java:175) - No Actions are defined for the report compute.ComputeEasyReport
2015-08-13 16:48:38,979 [main] DEBUG createConfigTable(ReportRegistryProxy.java:197) - Generating Config Table definition
2015-08-13 16:48:38,979 [main] DEBUG createConfigTable(ReportRegistryProxy.java:203) - The report context type -1
2015-08-13 16:48:38,979 [main] DEBUG createConfigTable(ReportRegistryProxy.java:207) - The Report entry context 10
2015-08-13 16:48:38,979 [main] DEBUG createConfigTable(ReportRegistryProxy.java:209) - The Management column 0
2015-08-13 16:48:38,980 [main] DEBUG createConfigTable(ReportRegistryProxy.java:211) - The Display column 1
2015-08-13 16:48:38,980 [main] DEBUG createEntry(ReportRegistryProxy.java:370) - ***************Registering Report compute.ComputeEasyReport.config******************************

How do I verify that my module features were uploaded successfully?

After restarting UCS Director, verify that the following files are in the /opt/infra/inframgr/features directory:

  • <moduleId>.feature

  • Feature-<moduleID>.jar

  • <moduleID>folder

UCS Director is does not restart successfully after uploading the module.zip file.

  • Delete the zip file from the/opt/infra/uploads folder directory.

  • Analyze the logs.

  • Update your module code.

  • Reload the zip file.

  • Restart UCS Director.

Debugging Open Automation

When you are debugging, you can trace problems through inframgr (Infra Manager) logs. You can get the inframgr logs through either the Cisco UCS Director Shell menu or the Cisco UCS Director GUI.

To use the shell admin approach:

  • Open the Cisco UCS Director Shell menu.

  • Choose 18, Tail Inframgr logs.

To use the Cisco UCS Director GUI:

  • Log in to the Cisco UCS Director GUI.

  • Navigate to Administration > Support Information.

  • Click System Information and Logs Link Page.

  • In the Cisco UCS Director Product System Information form, from the drop-down menu, choose Infra Manager and click Show Log.

Before You Begin

You will need shell admin access in order to use the debugging functions that are available in the Cisco UCS Director Shell menu (also known as shell admin). Refer to Deploying the Module on Cisco UCS Director, for more details about access to and use of the Cisco UCS Director Shell menu.

Setting Up the Open Automation Debug Configuration

Perform the following steps to setup the debug configuration for an Open Automation project and run the application on debug mode.

Procedure
    Step 1   Add the following line in bold next to java in the /opt/infra/inframgr/run.sh script. 
    java -Xdebug -agentlib:jdwp=transport=dt_socket,address=<port-number>,server=y,suspend=n -Xmx4096m -Xmx4096m -Djava.security.manager -Djava.security.policy=security.policy -verbose:gc
    Step 2   Replacing <port-number> with the port number you want to use, then save the file.
    Step 3   Create a debug configuration, by right clicking on your Open Automation project you Eclipse IDE and selecting Debug As >Debug Configurations.
    Figure 1. Debug Configuration



    Step 4   To create remote java application configuration, select Remote Java Application and click New.
    Step 5   Provide a name for the debug configuration.
    Step 6   Click browse at Project field and choose your Open Automation project.
    Step 7   In the Connection Type field, leave it as Standard (Socket Attach).
    Step 8   Provide your VM IP address and port number specified in the run.sh file.
    Step 9   Click Apply.
    Step 10   Add a breakpoint in your module.java class or any of your module code.
    Step 11   Start UCS Director, by running the shelladmin using option 4 – Start Services.
    Step 12   In your Eclipse IDE, right click on your Open Automation project and select Debug As > Remote Java Application Configuration Created.
    Step 13   Click Debug to start the debug session.

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco