Hi Saku, thanks for pointing me in the right direction. I was able to get it with: show xge-pic 0 link 0 sfp extensive
The show sfp and show xfp commands don’t find anything on the older FPCs. > On Mar 16, 2018, at 11:27 AM, Saku Ytti <s...@ytti.fi> wrote: > > T doesn't uniquely identify how to do this, this is how you can do it > on T4 Trio, I don't have access to older FPC: > > > HCFPC0(r21.labxtx01.us.bb vty)# show sfp list > Index Name Presence ID Eprom Reg ID I2C > Master I2C Group > ----- -------------- ---------- -------- -------- > ------------ ------- > 25 sfp-0/0/0(0) Present Complete 0x1 > 0x0 0x0 > > > HCFPC0(r21.labxtx01.us.bb vty)# show sfp 25 > > SFP driver state: > index: 25 > vector: 0x11d1d00c, pic context: 0x2370af28 sfp name: 'sfp-0/0/0' , pic arg: > 0 > type: 2, present: 1, id memory scanned: 1 delay count 0 > change: 0, failure count 0, diags enabled: 1, diags polling count = > 22448, no diags polling from RE = 0 > eeprom read time: 0 ms, diagnostics read time: 0 ms > SFP capability register values > diags implemented: 1, diag alarms implemented: 1 > addr change required: 0, int calibration: 1, ext calibration: 0 > Linkstate: DOWN > > I2C accel information: > is valid = TRUE > reg ID = 1 > Master index = 0 > Master index = 0 > Request flags = 0x1c > Status flags = 0x0 > Last request index = 7 > > SFP ID eeprom data: > Cable Type: 60 (SFP+-10G-LR) > SFP xcvr codes: > PNO: NON-JNPR > SNO: AM61GFS > REV: > Vendor name: CHAMPION ONE > Vendor PNO: 10GSFP+E-LR > Vendor REV: A > > ID: 0x03 > Extended ID: 0x04 > Connector type: 0x07 > Transceiver type: 0x00 > SFF-8472 compliance: v9.5 > NEBS compliance: No > Wavelength 1310 nm > Fiber mode SM > I2C write delay: 0 us > Tunable: False > > > 2-wire device address 0x50 > 0x00: 03 04 07 20 . 00 00 00 00 - 00 00 00 06 . 67 00 0a 64 > 0x10: 00 00 00 00 . 43 48 41 4d - 50 49 4f 4e . 20 4f 4e 45 > 0x20: 20 20 20 20 . 00 00 00 00 - 31 30 47 53 . 46 50 2b 45 > 0x30: 2d 4c 52 20 . 20 20 20 20 - 41 20 20 20 . 05 1e 00 0a > 0x40: 00 1a 00 00 . 41 4d 36 31 - 47 46 53 20 . 20 20 20 20 > 0x50: 20 20 20 20 . 31 32 30 32 - 31 33 20 20 . 68 f0 02 d2 > 0x60: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0x70: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0x80: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0x90: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xa0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xb0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xc0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xd0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xe0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xf0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > > 2-wire device address 0x51 > 0x00: 4e 00 f3 00 . 49 00 f8 00 - 90 88 71 48 . 8c a0 75 30 > 0x10: a6 04 1d 4c . 9c 40 27 10 - 3d e9 06 31 . 31 2d 07 cb > 0x20: 45 77 00 64 . 3d e9 00 9e - 00 00 00 00 . 00 00 00 00 > 0x30: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0x40: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 01 00 00 00 > 0x50: 01 00 00 00 . 01 00 00 00 - 01 00 00 00 . 00 00 00 7e > 0x60: 1d f3 81 42 . 48 a1 1b 7c - 00 02 00 00 . 00 00 32 00 > 0x70: 00 40 00 00 . 00 40 00 00 - ff ff ff ff . ff ff ff 01 > 0x80: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0x90: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xa0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xb0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xc0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xd0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xe0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > 0xf0: 00 00 00 00 . 00 00 00 00 - 00 00 00 00 . 00 00 00 00 > > HCFPC0(r21.labxtx01.us.bb vty)# > > On 16 March 2018 at 18:20, Kevin Wormington <kwor...@gmail.com> wrote: >> I’m trying to find an equivalent JunOS command (T Series) to dump the idprom >> info from a XENPAK adapter. I have found “show chassis hardware extensive” >> and from the PFE “show ideeprom scan verbose” but those don’t appear to grab >> the info from the XENPAK itself. If anyone has any suggestions please let >> me know. >> >> Thanks, >> >> Kevin >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > -- > ++ytti > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
