LMS 3.1 and discovery issue

Unanswered Question
May 27th, 2009


I'm installing a LMS 3.1 Windows 2003 to replace a LMS 2.6.

I got some issues on discovery process:

- discovery sometimes does not finish

- MSFC2 card are not discovered by their loopback address but by another IP address

- when I started twice discovery process, results are differents (not the same devices are discovered).

I saw that many bugs exist on LMS 3.1

Do you know if there is an available patch for those issues ?

Thanks in advance



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (2 ratings)
Joe Clarke Wed, 05/27/2009 - 08:44

The two bugs responsible for Discovery not finishing will be fixed in LMS 3.2 due out early this summer. A patch for one of the bugs (CSCsv42110) is available from the TAC. The other bug can be easily worked around by making sure all Discovery debugging is disabled.

The discovery by loopback is user-configurable. You need to make sure that is how you chose to do the management address resolution in the Discovery settings. The algorithm will pick the loopback interface with the highest IP address. This is different than LMS 2.6 which chose the loopback with the lowest IP.

You may be seeing different sets of devices discovered due to network issues (e.g. latency, temporarily unreachable nodes, etc.).

ppoiron Thu, 05/28/2009 - 06:00

I tried many Discovery settings without success.

Sometimes, when I started a new discovery, it didn't find any devices (very strange).

So, I got some problems with this new discovery settings between use of modules or global discovery.

We decided to keep LMS 2.6 now until discovery issues will be fixed.

Do you know if upgrade 3.1 to 3.2 version is free and is possible via an upgrade patch ?


This Discussion