topic Manufacturing Number on a SPF LX module in General Topics

Manufacturing Number on a SPF LX module

XgateCorporationLimited — Mon, 13 Oct 2025 09:13:40 GMT

Hi All, sorry to ask a trivial question, a supplier has sold just sold me the following SPF LX module. I seen that it says "LN#56 5/2019" In my eyes it means production Lot Number 56, production date 5/2019. My supplier says "This represents the first release date of this item "PAN-SFP-LX." And the manufacturing date of the product can be found on the label of the packaging box." I am quite concerned about the authenticity of what I am getting. Can someone point me to a website or contact that I contract to confirm this product?

Many thanks.

Re: Manufacturing Number on a SPF LX module

JayGolf — Fri, 17 Oct 2025 03:42:14 GMT

Hi @XgateCorporationLimited ,

You can retrieve the SFP module details via the CLI. Enter the following command, replacing x with the slot number and y with the port number where your SFP is installed:

> show system state filter sys.sX.pY.phy

For example, interface 1/19 would be:

sys.s1.p19.phy

The output will display info such as vendor name and the vendor part number.

If you run this command, what info does it tell you?

Re: Manufacturing Number on a SPF LX module

XgateCorporationLimited — Fri, 17 Oct 2025 06:54:30 GMT

Hi Jay,

Thank you kindly for your help.
This is what I got; interesting data ... unfortunately date is not explicitly shown but wonder if we can get an implied date from the 'vendor-part-rev': 1.0 .

sys.s1.p13.phy: {

'duration': 3708,

'last-sample': 1969-12-31 16:00:00,

'link-partner': { },

'media': SFP-Plus-Fiber,

'sfp': {

'Raw-eeprom':

0 1 2 3 4 5 6 7 8 9 a b c d e f

0: 3 4 7 0 0 0 2 12 0 1 1 1 d 0 a 64

10:

20:

30:

50:

60:

70:

80: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

90: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

a0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

b0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

c0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

d0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

e0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

f0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

'ch1': {

'rx-power': 0.00 mW,

'tx-bias': 20.22 mA,

'tx-power': 0.22 mW, },

'connector': LC,

'diagnostic-monitor': Yes,

'encoding': 8B10B,

'identifier': SFP,

'link-len-km': 10 km,

'link-len-m': 10.0 km,

'link-len-om1': 0 m,

'link-len-om2': 0 m,

'link-len-om3': 0 m,

'link-len-om4': 0 m,

'pan-supported-optics': Yes,

'rx-power-alarm-hi': 0.63 mW,

'rx-power-alarm-lo': 0.01 mW,

'rx-power-warn-hi': 0.50 mW,

'rx-power-warn-lo': 0.01 mW,

'supplier-name': AMPHENOL ,

'supplier-part-number': SF1312-XXX-XXX ,

'supply-voltage': 3.29 V,

'temp-alarm-hi': 90.00 C,

'temp-alarm-lo': -5.00 C,

'temp-warn-hi': 85.00 C,

'temp-warn-lo': 0.00 C,

'temperature': 23.53 C,

'transceiver': 1000B-LX,SM,100 MBytes,

'tx-bias-alarm-hi': 90.00 mA,

'tx-bias-alarm-lo': 2.00 mA,

'tx-bias-warn-hi': 85.00 mA,

'tx-bias-warn-lo': 4.00 mA,

'tx-power-alarm-hi': 0.63 mW,

'tx-power-alarm-lo': 0.10 mW,

'tx-power-warn-hi': 0.50 mW,

'tx-power-warn-lo': 0.13 mW,

'vendor-name': PALO-ALTO-NTWKS ,

'vendor-part-number': PAN-SFP-LX,

'vendor-part-rev': 1.0 ,

'vendor-serial-number': XTW1244XXXXXXXX,

'voltage-alarm-hi': 3.57 V,

'voltage-alarm-lo': 3.03 V,

'voltage-warn-hi': 3.50 V,

'voltage-warn-lo': 3.07 V,

'type': Ethernet,

}

Re: Manufacturing Number on a SPF LX module

JayGolf — Fri, 17 Oct 2025 15:19:07 GMT

Hi @XgateCorporationLimited ,

That output tells us some good info here.

You won't be able to infer the actual manufacturer date, but based on the details you've shared the sfp appears to be authentic. Amphenol is a qualified OEM, the vendor-name is explicitly stated as PALO-ALTO-NTWKS, and the part-number is PAN-SFP-LX.

Also, the DOM monitoring values are successfully reporting diagnostic information. If an incompatible transceiver were in use, the CLI would typically return 'N/A' for diagnostic information it could not read.

Hope this helps! Feel free to reach out anytime.

Re: Manufacturing Number on a SPF LX module

XgateCorporationLimited — Mon, 20 Oct 2025 01:55:12 GMT

Thanks so much for your help Jay!