Pluggables in ASR-920 have incorrect product ID in the SNTC portal reports

[Benjamin Bartsch]

We have some SFP+ ZR optics in our ASR-920 routers.  All of them show up as Xenpaks in the SNTC portal inventory.

Anybody else having this issue?

Actual equipment - PID = SFP-10G-ZR-S

Reported equipment - PID = XENPAK-10GB-ZR

[Benjamin Bartsch]

Results from SNMP walk show correct PID for the 2 SFP+ ZR optics in this ASR-920:

c:\>snmpwalk.exe -r:[removed] -c:[removed] -os:.1.3.6.1.2.1.47.1.1.1.1.11.1 -op:.1.3.6.1.2.1.47.1.1.1.1.14.1

OID=.1.3.6.1.2.1.47.1.1.1.1.11.696, Type=OctetString, Value=FL[removed]25
OID=.1.3.6.1.2.1.47.1.1.1.1.12.696, Type=OctetString, Value=CISCO-FUJITSU
OID=.1.3.6.1.2.1.47.1.1.1.1.13.696, Type=OctetString, Value=SFP-10G-ZR-S

OID=.1.3.6.1.2.1.47.1.1.1.1.11.710, Type=OctetString, Value=FL[removed]35
OID=.1.3.6.1.2.1.47.1.1.1.1.12.710, Type=OctetString, Value=CISCO-FUJITSU
OID=.1.3.6.1.2.1.47.1.1.1.1.13.710, Type=OctetString, Value=SFP-10G-ZR-S

[Benjamin Bartsch]

Screenshot of SNTC portal attached showing incorrect PID listed as XENPAK-10GB-ZR

[Chris Camplejohn]

Can you private message me an example serial number so I can investigate?

[Benjamin Bartsch]

Chris - PM sent.  Thank you sir!

-ben

[Chris Camplejohn]

Thank you for the data and bringing this to our attention. This has been corrected and will be in production by tonight. If you send another upload from CSPC to SNTC tomorrow, then the data should be corrected once that upload is processed. Please let us know if that resolves the issue.

[Benjamin Bartsch]

Thanks, Chris.  Our uploads are scheduled for Monday mornings.  I'll check on it on 7/29.  I really appreciated the quick turnaround on this.  I'll be sure to update this thread with what we see.

Thanks again!

-ben

[Benjamin Bartsch]

Chris - the product ID is correct now, but we are still getting an alert for LDOS over 12 month and within 24 months.  The hyperlink provided via SNTC is still for the Xenpak.

[Chris Camplejohn]

Great to hear that the product ID is fixed. There is an open bug that the development team is working on for these types of “stale” EOL records left behind. I’ll see if they can run the clean-up script on your account in the meantime.

[Benjamin Bartsch]

Thanks for the update, Chris.  We'll continue to monitor and let you know when we see it resolved.

[Benjamin Bartsch]

Looks like it is all fixed now.  I hadn't checked on it in a while.  Thanks for the help!