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.
How do I verify if my module is registered with the platform?
Recommended Solution
Enable com.cloupia.service.cIM.inframgr=DEBUG under the logging.properties file, in the /opt/infra/inframgr directory. After enabling the debug, you will see the following message:
jar to be loaded:jar: "Loading feature class " <moduleorFeatureName> " from feature definition file
If you do not find the "Error while loading feature classes for " error after a few lines, your module is added successfully.
After uploading zip file and restarting the Cisco UCS Director, check if the module features are uploaded successfully in Cisco UCS Director by verifying if the following three items are available in the /opt/infra/inframgr/features folder: <moduleId>.feature file, feature-<moduleId>.jar file, and <moduleId> folder.
How do I verify if my report is 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
For choosing the custom-defined pod, you must provide the <moduleId>.xml file in the poddefinition folder to define your own pod. Also, ensure that the correct pod type is defined in the xml file.
For choosing a pod defined in Cisco UCS Director, ensure that the account type is defined in the pod definition file (/opt/infra/inframgr/resources/LicenseBundle).
What do I do if the module is not loading?
Recommended Solution
If your module is not loading, check for the following message in the /opt/infra/inframgr/logfile.txt file:
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 the ClassNotFoundException error in the log file, check if the tempOA module name is declared in the .feature file.
If the path or the module file name is correctly defined in the .feature file, 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, you can see the report registered under the 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?
Recommended Solution
After restarting Cisco UCS Director, verify that the following files are in the /opt/infra/inframgr/features directory:
Cisco UCS Director does not restart successfully after uploading the module.zip file.
Recommended Solution
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:
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.
You can find the Infra Manager log file (logfile.txt) at the /opt/infra/inframgr path.
Developer can log error statements in the inframgr.out file at the /var/log/ucsd path, using the System.err.println statement or the printstacktrace statement. The logged error statements are used to identify the root cause for any exceptions or errors occurred.
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 the Deploying the Module on Cisco UCS Director section in the Cisco UCS Director Open Automation Getting Started Guide , for more details about access to and use of the Cisco UCS Director Shell menu.
Perform the following steps to setup the debug configuration for an Open Automation project and run the application on debug mode.