Cloud Management and AIOps

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):

  • Cloud Pak for Multicloud Management

  • Cloud Pak for Network Automation - incl Orchestration and Performance Management

  • Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio

  • Control Desk

  • Edge Application Manager

  • IBM Observability with Instana

  • ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8

  • Workload Automation - incl Workload Scheduler

  • Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)

  • Tivoli Application Dependency Discovery Manager - TADDM

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Under review
Created by Guest
Created on Sep 7, 2021

HuaweiM2K Java Collector should discover all neTypes as in XML dumps

This case is a follow up from the previous TS005353782 case which was closed even before our last inquiry was answered.

For the NeType combination below which the previous PMR support described as “Not Supported”, we would like to know when it will be supported since this will be needed by Globe client.

===

Details from the previous case:

1) SRAN files with LTE ne-type are supported. For these files/ne-types to be processed, we need to configure two properties processor.enb.srannbi.netype and processor.enb.srannbi.neversion.

2) SRAN Files with "Co-MPT BTS" ne-type supported. If these files contain module that are not supported (like gNodeBFunctionModule), entire discovery fails and we see related message in log file. For these files/ne-types to be processed, we need to configure two properties processor.enb.srannbi.combinedsite.netype and processor.enb.srannbi.combinedsite.neversion

3) GNB* Files with ne-type as BSC6900GSMNE (GSM_BSC) are supported. No explicit configuration in properties files is required to specifically mention ne-types to process.

4) UNBI* files with ne-type as BSC6900UMTSNE (UMTS_RNC type) are supported. No explicit configuration in properties files is required to configure ne-type etc.

If adjacent NODEB devices data also supplied in CME* file format in same input data folder, those files/devices are also processed.

5) CME* files for ENODEB type (className is BTS3900NE and file contains BTS3900ENODEBFUNCTION MOs in file) are supported if we install draft instller for RFE144346. This functionality is not available in any released FP yet.

These files doesn't requires any explicit configuration to be processed. If they are part of input data folder, they are processed.

Example ENODEB Devices we identify in supplied input files are:

AMANSION1ACZ,100WESTMKTNCRIDF, 100KTOWERQCHL, 100KTOWERQCFW, 15THAVSOCOROQCNCREMFW,11AVEFHLKWR,

C5MARKETACZ, 8THNSIGNALTAGNCRFHLK, BCFILCYBERPSYIDFHKW, ABSAIESQCNCRPNPZ, 2102311HPF10K4000074.

6) CME* files for NODEB type (className is BTS3900NE and contains BTS3900NODEBFUNCTION MOs in file) are processed when supplied along with UNBI files and when the UNBI file has reference to NODEB mentioned in CME* file.

This way of getting them processed doesn't require any explicit configuration. They are processed when they are available in input data folder. When I run the discovery for data folder that contains UNBI* and CEM* of NODEB, I could see complete device structure.

CME* files for NODEB type (className is BTS3900NE and contains BTS3900NODEBFUNCTION MOs in file) are not supported if supplied alone(without corresponding UNBI* file). If we install draft installer for RFE144346, you would see mostly empty device structure for this data type. It is because they have same className as eNodeB/LTE devices.

We are planning to support processing of these CME* files for NODEB without any dependncy on UNBI files as part of 2nd phase of RFE144346.We need further analysis on it and yet to start on it.

Example NODEB Devices we identified in supplied input files are:

BDG911SAMARSTMLANCRZ, B3BONIHIGHACZ,B2BONIHIGHACZ, AYALACKTMALMKTNCRLSZ, AYALABAY1PQUENCRLSZ.

7) CME* files for GNODEB type (className is BTS3900NE and contains GNODEBFUNCTION MOs in file).

Examples of these devices in supplied files are ARENA3MOAM, ACACIAMN

8) CME* files with className value as ICSNE has no support. Example NE names in PMR supplied files are IPCLK SERVER AURORA-1, IPCLK SERVER VALERO-1

9) No support exists for CME* files with className as BSC6900GSMNE (and ne-type as BSC6900GSM).

Example NE names in PMR supplied files are NCRANTPLOBSC1, NCRAURORABSC1.

10) No support exists for CME* files with className as BSC6900UMTSNE (and ne-type as BSC6900UMTS).

Example NE names in PMR supplied files are NCRAURORARNC1, NCRAURORARNC2, NCRCANERORNC3, NCRCANERORNC4.

11) SRANFiles with NodeB ne-type are not supported. I remember adding its NE type value to processor.enb.srannbi.netype results in empty device structure.

12) SRANFiles with NR ne-type are not supported. I remember adding its NEtype value to processor.enb.srannbi.netype results in empty device structure.

Why is it useful?

Once the NEType combination supported by the new collector, ITNM will be able to discover the NEs with blank device structure.

Who would benefit from this IDEA? Globe Telecom
Idea Priority High