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 Jul 13, 2021

New Collector for Discovering FiberHome MSAN devices

The customer has a set of MSAN’s that are from FiberHome OEM. The OEM supports TL1 as NBI for collecting inventory data.

Since ITNM doesn’t have a generic TL1 collector, we will need a new collector developed.

The following are the TL1 commands used:

LST-SHELF::OLTID=<MSANIPADDRESS>:CTAG::;

LST-BRDINFO::OLTID=<MSANIPADDRESS>,BOARDID=NA-NA-<SLOT#>:CTAG::;

LST-DEVICE::OLTID=<MSANIPADDRESS>:CTAG::;

LST-BOARD::ONUIP=<MSANIPADDRESS>:CTAG::;

Please note that, we already submitted the output of this command under the PMR "Case TS006116786: Need new collector for discovering FiberHome MSAN devices". Please see the response of PMR support below.

As per PMR support, here are the updates from the L3 team:

----------------------------------------------------------------------------------------------------

We have gone through the logs provided. As per our go through so far of provided logs and TL1 fiber home EMS collector, which is under development, we observed below differences in commands.

1. LST-BOARD - Current collector code handle only OLT parameter for this command. Now, as per new requirement, we shall need to handle ONU as there are changes in output when parameter is ONU. It might be needed be MSAN devices.

2. LST_SHELF - We did not have support for this command yet.

3. LST_BRDINFO - We did not have support for this command yet

4. LST-DEVICE - Already supporting. So can be reused.

Based on above data, we would like to indicate that there shall be a need for creation of RFE to enhance collector to support this new functionality of commands.

----------------------------------------------------------------------------------------------------

Idea priority High
Why is it useful?

It will be useful to Globe Telecom since they will use the FibeHome MSAN domain in their operations.

The generic TL1 collector is prerequisite to run the discovery of this domain.

Who would benefit from this idea? Globe Telecom