1401819 - bad port 2/0/33 or bad blade on moon4

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Description

[Van Le [:van]]

either bad port or bad blade. it wont detect a link.

configured as lag:
[moon4-access.rit47.inband.releng.mdc1.mozilla.net-Ten-GigabitEthernet2/0/33]dis
play interface ten 2/0/33
Ten-GigabitEthernet2/0/33
Current state: DOWN
Line protocol state: DOWN(LAGG)
IP packet frame type: Ethernet II, hardware address: 9cb6-54fe-854c
Description: Ten-GigabitEthernet2/0/33 Interface
Bandwidth: 10000000 kbps
Loopback is not set
Media type is not sure, port is connected to backplane

and no lag, still shows down

[moon4-access.rit47.inband.releng.mdc1.mozilla.net-Ten-GigabitEthernet2/0/33]dis
play interface Ten-GigabitEthernet 2/0/33
Ten-GigabitEthernet2/0/33
Current state: DOWN
Line protocol state: DOWN
IP packet frame type: Ethernet II, hardware address: 9cb6-54fe-854c
Description: Ten-GigabitEthernet2/0/33 Interface
Bandwidth: 10000000 kbps
Loopback is not set
Media type is not sure, port is connected to backplane
Unknown-speed mode, unknown-duplex mode
Link speed type is autonegotiation, link duplex type is autonegotiation
Flow-control is not enabled

Comment 1

[Van Le [:van]]

fwiw, port 1/0/33 is up so this probably points to a bad blade.

Comment 2

[Van Le [:van]]

reseated blade but didn't resolve the issue. opened an email case with HP.

Case ID: 5323186893

Comment 3

[Van Le [:van]]

looks like it'll take some time before they can send a replacement cartridge.

Hi Van Le,
 
This is regarding the Case Number: 5323186893
 
With great regret, I would like to inform you that the part ordered on this case is not available locally and we are trying to ship the part from a  close by ware house.
 
I have escalated the part and until then I will personally monitor this case and keep you updated regarding part delivery.
 
Please reply all to this mail if you have any concerns.
 
 
 
Regards,
 
Roshan R
 
AMS Delivery Control Tower
Enterprise Group
CSCB

Comment 4

[Van Le [:van]]

cartridge received, will swap out next trip.

Comment 5

[Corey Shields [:cshields]]

Is the cartridge already in Sacramento? This would be a good test of remote hands, especially while these are not yet in production.

Comment 6

[Van Le [:van]]

replaced the cartridge but it did not resolve the issue. sending back their RMA and will update their ticket.

Comment 7

[Van Le [:van]]

HPE is asking me to swap the cartridges around to see if we can rule out a backplane issue and grab logs. will need to sync with relops and handle this next trip.

Comment 8

[Van Le [:van]]

swapped cartridge 30 and 33's into one another's slots and still running into the same issue. sent logs to HPE but it looks like a possible motherboard issue with slot 33 which might turn out to be a big PITA if they need to swap everything out to get to the motherboard. 

BAGG30               UP   20G(a)  F(a)   T    208
BAGG33               UP   10G(a)  F(a)   T    208
XGE2/0/33            DOWN auto    A      T    208

everything appears normal other than slot 33 only getting 1 interface.

Comment 9

[Van Le [:van]]

Attachment: moonshot 4.rtf

show all/ show log iml all/ show log ilo all

Comment 10

[Van Le [:van]]

:q, HPE wants to swap out the motherboard on chassis 4 as the slot in cartridge 33 only gets one network port. i wont be available to go to MDC1 until after thanksgiving. do you see any issues with taking downtime to replace the motherboard?

Comment 11

[Q]

No go fir it

Comment 12

[Van Le [:van]]

tentatively scheduled for 1/9/2018 @ 10am.

Comment 13

[Van Le [:van]]

replacing motherboard/systemboard resolved issue.