{"id":711,"date":"2024-09-04T10:21:35","date_gmt":"2024-09-04T14:21:35","guid":{"rendered":"https:\/\/bryanward.net\/wp\/?p=711"},"modified":"2025-07-22T14:37:35","modified_gmt":"2025-07-22T18:37:35","slug":"more-juniper-poe-controller-repair","status":"publish","type":"post","link":"https:\/\/bryanward.net\/wp\/2024\/09\/04\/more-juniper-poe-controller-repair\/","title":{"rendered":"More Juniper PoE Controller Repair"},"content":{"rendered":"\n

This is a continuance of my earlier article “Recovering from Juniper PoE Controller DEVICE_FAIL<\/a>“.<\/p>\n\n\n\n

Due to chip supply constraints, Juniper has had to swap the PoE controller chip in some of their switches.
The different chip requires different firmware, and so the file \/usr\/lib\/poe_latest.s19<\/code> may no longer exist.
Newer versions of Junos are required to use this different model PoE chip as well.<\/p>\n\n\n\n

bward@4300mp> request system firmware upgrade poe fpc-slot 1 file \/usr\/libdata\/poe_latest.s19
PoE: cannot open file<\/code><\/pre>\n\n\n\n
See related TSB71559<\/a>, and PRs PR1744343<\/a>, PR1741298<\/a>, PR1745088<\/a>, and PR1743547<\/a><\/p>\n\n\n\n
If you need to manually apply firmware to the PoE controller on a switch (such as when the output of show poe controller reports DEVICE_FAIL, or if the PoE Controller simply isn’t listed), you’ll now need to load the model-specific firmware file:<\/p>\n\n\n\n
root@4300mp:RE:0% cd \/usr\/libdata
root@4300mp:RE:0% ls -la
\u2026
lrwxr-xr-x 1 root wheel 32 Sep 4 03:26 poe_at_type1.s19 -> \/var\/host\/poe_msemi_69200_at.s19
lrwxr-xr-x 1 root wheel 32 Sep 4 03:26 poe_at_type2.s19 -> \/var\/host\/poe_msemi_69220_at.s19
lrwxr-xr-x 1 root wheel 32 Sep 4 03:26 poe_bt_type1.s19 -> \/var\/host\/poe_msemi_69200_bt.s19
lrwxr-xr-x 1 root wheel 32 Sep 4 03:26 poe_bt_type2.s19 -> \/var\/host\/poe_msemi_69220_bt.s19
\u2026<\/code><\/pre>\n\n\n\n
The Type1 files are for the older model PoE controller chip, whereas the Type2 files are for the newer model.
You’ll also need to choose between AT and BT mode, as appropriate.<\/p>\n\n\n\n
The command you’ll need to use looks something like:
request system firmware upgrade poe fpc-slot 1 file \/usr\/libdata\/poe_bt_type1.s19<\/code><\/p>\n\n\n\n
Don’t forget to reboot after doing this!<\/strong><\/p>\n\n\n\n
But, how do you know if your switch has a Type1 or Type2 PoE controller?
Well, if the PoE controller is working\u2026 you can see this in the output of show chassis firmware detail<\/code><\/p>\n\n\n\n
bward@4300mp> show chassis firmware detail\nFPC 0\nPoE firmware 3.5.2.0.30 (type1)<\/strong>\nPHY version 5d47.37a.47.305\nBoot Firmware\nU-Boot ***\nBoot Firmware\nloader FreeBSD\/i386 bootstrap loader 1.2<\/code><\/pre>\n\n\n\n
But if it’s not working, then the PoE firmware line won’t be present \ud83d\ude41<\/p>\n\n\n\n
I cannot confirm the below, as I no longer have a failed device, but it looks like you can determine the type of PoE controller by using the following:<\/p>\n\n\n\n
bward@4300mp> start shell user root<\/strong>\n\nroot@4300mp:RE:0% vty fpc1<\/strong>\n\nFPC1(4300mp vty)# sh poe bt version<\/strong>\nREQUEST : 0x02 0x17 0x07 0x1E 0x21 0x4E 0x4E 0x4E 0x4E 0x4E 0x4E 0x4E 0x4E\nRESPONSE: 0X03 0X17 0X00 0X4E 0X18 0X01 0X60 0X00 0X1E 0X03 0XE8 0X4E 0X4E\nHW version = 0x00\nProduct Number = 0x18\nController Type = Type1(PD69200)-BT<\/strong>\nFull SW version = 24.0352.30.00\nInternal SW = 0x03e8\n\n\nFPC1(4300mp vty)# exit\n\nroot@4300mp:RE:0% exit<\/code><\/pre>\n\n\n\n
If you don’t have an 802.3bt capable device, then remove the bt<\/code> keyword from the above command.<\/p>\n\n\n\n
<\/p>\n\n\n\n
UPDATE<\/p>\n\n\n\n
It appears that a switch will produce an error if you try to load the wrong firmware:<\/p>\n\n\n\n
bward@4300mp> request system firmware upgrade poe fpc-slot 1 file \/usr\/libdata\/poe_bt_type1.s19\nPoE: file format\/size\/content corrupted\n\n{master:0}\nbward@4300mp> request system firmware upgrade poe fpc-slot 1 file \/usr\/libdata\/poe_bt_type2.s19   \nFirmware upgrade initiated. Poe Upgrade takes about 10 minutes\nUse 'show poe controller' to get the download status,\nPlease Reboot the system after Upgrade is complete.<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
Due to chip supply constraints, Juniper has had to swap the PoE controller chip in some of their switches.
\nThe different chip requires different firmware.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[9,10,44],"class_list":["post-711","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-juniper","tag-junos","tag-poe"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/posts\/711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/comments?post=711"}],"version-history":[{"count":2,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/posts\/711\/revisions"}],"predecessor-version":[{"id":775,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/posts\/711\/revisions\/775"}],"wp:attachment":[{"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/media?parent=711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/categories?post=711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bryanward.net\/wp\/wp-json\/wp\/v2\/tags?post=711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}