Customer Fixed Issues and Known Issues Tahoe SP4 HF10

 

On this page: Customer Fixed Issues | Known Issues 

Hotfix Merges

Following are the merged releases in Tahoe SP4 HF10:

Customer Fixed Issues 

This section provides details about the fixed customer issues in following modules.

Service Management

Issue ID

Issue Description

Scenario

Resolution

134955

Additional Configuration Item(CI) in Report RFC CI Info Report were getting populated despite the front end was only showing a few CIs.

Prerequisite:

Load denormalization Change Management tables job should be running.

Steps:

  1. Navigate to Change User New Change Record.

  2. Select the required tenant.

  3. Fill in all the mandatory details.

  4. Link the Configuration Items (CI).

  5. Click Submit to create a Change Record (CR).

  6. Navigate to recently created CR.

  7. Delink the linked CI.

  8. Click Submit.

The Report RFC CI Info Report is successfully populating the correct number of CIs.

138995

Users were experiencing issues while using EXPORT ALL on the right  panel of Service Request List Page.

Steps:

  1. Log in to the application.

  2. Navigate to Request > User > Manage Service Requests > Service Request List.

  3. In the right panel, click EXPORT ALL.

The data on the exported excel sheet is displaying as expected upon using EXPORT ALL.

Asset Management

Issue IDIssue DescriptionScenarioResolution
134053Users were experiencing performance issues as mapped profiles was not getting updated in the database.

Steps:

  1. Log in to the application.

  2. Navigate to Admin > Basic > Infrastructure > Custom Scheduler.

  3. Validate settings on App Control Map Profile.
There is no performance issues.

Agentless Discovery

Issue IDIssue DescriptionScenarioResolution

122857

Template Filter logic for with or without (DOT) for SNMP was not working appropriately.

For example, for devices discovered with 1.3.6.1.4.1.9.1.1208 and .1.3.6.1.4.1.9.1.1208(preceding with DOT), those discovered with preceding DOT were not retrieving the Serial No and Model information.

 

Steps:

  1. Log in to application.

  2. Navigate to Discovery & Monitoring > Discovery Templates.

  3. Select the Tenant and click the Template name from LIST page.

  4. Configure SNMP Template for Discovery job.

  5. Run the Discovery and verify the SysObjectID of the devices were getting discovered with preceding "." or without "."

Template Filter logic for Agentless Discovery job works appropriately after the resolution.

122857

While configuring the Discovery templates, the parsing condition was not able to fetch the value and trim it to have the required information retrieved.

Steps: 

  1.  Configure the template using SNMP.

  2. Create a user-defined parameter such as Manufacturer, IOS, etc. with proper parsing details.

  3. Navigate to Admin > Advanced > Discovery & Monitoring > Discovery Templates.
  4. Select the Tenant and Submit.
  5. Click Template Name. 
  6. Click on the Edit icon in the added parameter and the CONTENT PARSER window is displayed.
  7. Enter the desired preceding and succeeding text to get the relevant output.
  8. Click the Submit button.
  9. Configure the job and verify the parameter in the hardware details.

Note: Parser logic will not be applicable if two IDs are given for a field/parameter. Dash logic [-] is for stack switch and will not also allow parser logic to be applicable.

The parsing condition can fetch and trim the value to retrieve the required information after the resolution.

122857

In the Discovery Template, when a device was being mapped, the following issue occurred:

  1. Column Device Type of API Parameter was not populating appropriately.

  2. The system time was displaying properly.

  3. The Manufacture field was displayed blank.

Prerequisite:

Configure API configuration.

Steps:

  1. Login to the Summit application.

  2. Navigate to Admin > Advance > Discovery & Monitoring > Discovery Template.

  3. Click Add New, enter the required details and click Submit.

  4. Select the required Template Name and click Mapping tab.

The templates can be mapped without any issue.


Notes

  • Values are sourced from mapping in the template or, if not specified, retrieved from the API Configuration.

  • If it falls outside this mapping, the JSON attribute specified in the template will be taken into consideration.

  • If mapped based on the Model name if it starts with MR : Access point, MS : Switch, and MX :Firewall.


Known Issues 

This section describes the known issues detected by the Summit Dev and QA team in this release.

Issue IDIssue DescriptionScenario Workaround <if applicable>
127807

Using Report Builder only a few reports like Asset Management, CMDB, or Service Catalog reports can be generated.  

When a Tenant is mapped for example to Knowledge or Call management then the Report Type drop down is displayed as NO DATA. 

  1. Navigate to Admin> Infrastructure > Report Builder

  2. Click Filters.

  3. Select the Tenant having only Knowledge Management and Call Management module access. 

  4. Click dropdown Module Name, Report Type and verify if appropriate modules are displayed. 
NA