Description

This article explains the limitation of Service Now with respect to showing multiple platforms which might not be present in a user's environment but appears in EOL reports.

Symptoms

Why does the Service Now EOL report is show Junos platforms which is not present in the environment? For example, if an environment has only SRX100H, another platform SRX100B is also reported as the EOL model. 

Solution

Currently, HW file contains only the <part-number> , which is sent to the EOL tool and not the <model-number> . The EOL tool cannot find the <model-number> to match, so it uses the <part-number> instead.

This is a limitation since the EOL tool cannot determine the model-number and currently only the part-number is provided. One part-number might map to several model-numbers. This is the safe way to provide all the mapping model-numbers. Otherwise, if we only provide the first or last mapping model-number, there is the possibility of getting the incorrect model-number.

Example

Snippet of HW file
……
<chassis>
<name> Chassis
<serial-number> AU3912AF0701
<description> SRX100H
<chassis-module>
<name> Routing Engine
<version> REV 19
<part-number> 750-021773
<serial-number> AT3912AF0701
<description> RE-SRX100H
……

There is no model-number tag like this:

<model-number> SRX100H

Since the part-number 750-021773 is used by SRX100B, SRX100H, SRX100H-TAA,  the three models appear in the EOL report since the EOL tool cannot determine the exact model-number by the part-number.