Duplicate load balancer records with different serial numbers

[midjoule]

Hello,

We are using discovery and service mapping in order to create maps of our services.

Maps are based on entry points that go through the load balancers.

Recently, the load balancers have been upgraded to a newer version. This has somehow changed their serial numbers. As a result, Discovey has created another record:

As a consequence, the maps that were using the previous version of the load balancer are not discovered any longer, because the error says that the load balancer is not active, hence the process stopped.

I think about two options to resolve the issue:

• Change the identification rule of the load balancer and remove the serial number (only keep the identification on the name of the load balancer)
• Copy the serial number of the new version of the load balancer into the old one, reactivate the old one and delete the new load balancer record. However, this solution will work temporary : if a new version of the load balancer creates a new serial number, then the same issue will come again.

What would you recommend to do ?

[Rahul Priyadars]

 the load balancers have been upgraded to a newer version. This has somehow changed their serial numbers. --> i will ask first the LB team is this an expected behavior as root cause is here not in service now.

Now coming to Service Now in my view i will go with long term solution plan as other components will be same in the tree only top entry point is making problem. 

Did u tried Maps with new entry?

Regards

RP

[midjoule]

Hi @Rahul Priyadars,

Thanks for taking care of my question.

I requested explanations from the F5 team and they told me that the serial number changed because the load balancer got migrated from physical server to logical server. This change of serial number should not occur next time we upgrade their version.

Now my challenge is to make all our previous maps use the new load balancer (our new maps use it).

I've done many changes in the cmdb_rel_ci in order to make the entry point of a service map use the new load balancer, by linking it to the same load balancer service record of the new load balancer, but it never provided the expected results. It's like if the entry point kept using the old path to the previous load balancer.

My last option was to remove the entry point from the old map and create a new map with that entry point, but here is the error message:

Would you know what's wrong ? I can't understand this is not working.

By the way, creating new maps to migrate them to the new load balancer would be the last option, because I've 100+ maps to migrate to the new load balancer. Would you have a recommendation for me on how to migrate them to the new load balancer ?

Best regards

Midjoule

[Jyothi Malkared]

@midjoule

Recently we face the same issue 

New Load  Balancers  were upgraded  ,it should have SSH credential 

srvmapping account (is a service account ) is available for New F5  and make sure password for the account is static