unable to see SFP-GE-T in show version of ASR 9010

[Muhammad Thanveer]

Hi Folks,

I am unable to see SFP-GE-T as a PID in show version of ASR 9010. Is that any bug?

IOS version: asr9k-os-mbi-4.3.4/0x100305/mbiasr9k-rsp3.vm

Output of sh version

NAME: "module mau 0/2/0/16", DESCR: "SFP"
PID:    , VID: N/A, SN: MTC171807BM 

BR

Thanveer

[Rivalino Tamaela]

Get 'show controller gig0/2/0/16 internal'.

rivalino
 

[Muhammad Thanveer]

Hi Friend,

Please find the details:

show controller gig0/2/0/16 internal
Thu Apr 10 22:57:48.571 UTC

Port Number         : 16
Board Type          : 0x00000235
Port Type           : 1GE
Transport mode      : LAN
BIA MAC addr        : Removed
Oper. MAC addr      : Removed
Egress MAC addr     : Removed
Port Available      : true
Status polling is   : enabled
Status events are   : enabled
I/F Handle          : 0x040004c0
Cfg Link Enabled    : disabled
H/W Tx Enable       : no
MTU                 : 1526
H/W Speed           : 1 Gbps
H/W Duplex          : Full
H/W Loopback Type   : None
H/W FlowCtrl Type   : None
H/W AutoNeg Enable  : Off
H/W Link Defects    : (0x00000038)  HW_LINK SFP_PHY_LINK LASI
H/W Raw Link Defects : (0x01000038)  HW_LINK SFP_PHY_LINK LASI ADMIN_DOWN
Link Up             : no
Link Led Status     : Shutdown  -- Off
UDLF enabled        : no
UDLF force event    : no
UDLF uni_dir enabled: no
Pluggable Present   : yes
Pluggable Type      : 1000BASE-T
Pluggable PID       :
Pluggable Compl.    : Compliant
Pluggable Type Supp.: Supported
Pluggable PID Supp. : Supported

[Rivalino Tamaela]

Looks to me the router still recognize the PID but cannot show it, "Pluggable PID Supp. : Supported". You can try to unplug the SFP and plug to other router to see if the PID is shown on other router. Also, do you have other SFPs on this router and they are showing the missing PID under 'admin show inventory'?

thanks,

rivalino

[Muhammad Thanveer]

I have total of 4 sfp of this model and all of them dont show the PID, will try tomorrow under admin, thanks for your time dear friend.

[Muhammad Thanveer]

Dear Friend,

Please find the output of same under admin, I am still unable to see the PID, but where as I am able to see the PID for other type SFPs

NAME: "module mau 0/2/0/2", DESCR: "SFP"
PID:    , VID: N/A, SN: MTC17180GF4     

NAME: "module mau 0/2/0/15", DESCR: "SFP"
PID:    , VID: N/A, SN: MTC17180GC6     

NAME: "module mau 0/2/0/16", DESCR: "SFP"
PID:    , VID: N/A, SN: MTC171807BM     

NAME: "module mau 0/2/0/17", DESCR: "SFP"
PID:    , VID: N/A, SN: MTC17180DJ8  

NAME: "module mau 0/2/0/18", DESCR: "SFP"
PID: GLC-LH-SMD          , VID: V01 , SN: FNS17232B6A 

BR

Thanveer

[Muhammad Thanveer]

Any Help?

[Rivalino Tamaela]

Hey Thanveer,

If these 4 SFPs are still showing the same issue, i would like to try these 4 SFPs on other router and see if other router can sees the PIDs. If that router can show the PID, so we need to take a look on ASR9k traces.

rivalino

[Muhammad Thanveer]

Hello Rtamaela,

I cannot do that As I have only one Supporting LC in ASR 9k for this type of SFP.

I don't have same type of module in other ASR9ks. Is there any Other Idea.

BR

Thanveer

[Rivalino Tamaela]

Hi Thanveer,

Based on show controller output, i believe it should not have impact to the port itself. If you have other known good SFP, please try to plug it to the router. There are two possiibilities, the software cannot read PID of SFP, or the eeprom of SFP itself has gone bad. These two possibilities can be easily rule out if you have either known good SFP, or other router. WIth known good SFP, you can simply plug it to the router. With other router, you can simply plug these 'failed' SFP to other router.

If you don't have both, i suggest to open TAC case to investigate this.

rivalino

[Muhammad Thanveer]

Hey,

I found at one of the other sites we have, it is also not showing there, I am worried that what can be the issue.

Please suggest.

Regards

Thanveer

[Muhammad Thanveer]

Hey Buddy,

I got a response from my team, that this is an issue with ios release from 4.2.1(Could be earlier also). Since we are running 4.3.4 we still have this issue. Might get resolved in the higher versions. 

Regards

Thanveer