*****
loader> install --format tftp://192.168.6.53/junos-arm-32-15.1X53-D56.tgz
ETH LINK UP: 1000FD
cannot load kernel from package (error 2)
loader>
*****
using tftp. with u-boot prompt, i can get the EX to pull down the image but it doesn't do anything after the DL.
I recently had to try the following, and was able to get past.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB20643
https://kb.juniper.net/InfoCenter/index?page=content&id=KB29113
Can you send the output of your tftp upgrade attempt?
This is procedure:
https://kb.juniper.net/InfoCenter/index?page=content&id=KB20643
That is funny they have the word FAN in the report.
Still that is excessive heat .
loader> set ipaddr=192.168.6.150
loader> set netmask=255.255.255.0
loader> set serverip=192.168.6.53
loader> install --format tftp://192.168.6.53/junos-arm-32-15.1X53-D56.tgz
ETH LINK UP: 1000FD
cannot load kernel from package (error 2)
can't get to single user mode either =\
loader> boot -s
can't load 'kernel'
no bootable kernel
loader>
at the u-boot prompt, i can get the device to pull down an image from tftp server:
*****
=> tftpboot junos-arm-32-15.1X53-D56.tgz
ETH LINK UP: 1000FD
Using bcmiproc_eth-0 device
TFTP from server 192.168.6.53; our IP address is 192.168.6.150
Filename 'junos-arm-32-15.1X53-D56.tgz'.
Load address: 0x61000000
Loading: #################################################################
....
########################################################
603.5 KiB/s
done
Bytes transferred = 252393868 (f0b398c hex)
=>
*****
but it doesn't do anything with it. what am i missing here? 
can't get to single user mode either =\
This is known issue (I believe) with all newer ELS based EX switches outside of EX9200.
This is known issue (I believe) with all newer ELS based EX switches outside of EX9200.
So the only resolution is RMA?
single-user mode is different on EX3400 and EX2300; please see following KB: https://kb.juniper.net/InfoCenter/index?page=content&id=KB31403&actp=METADATA
aren't you able to boot from the OAM partition?
I don't know if the following page helps you: http://nextheader.net/2017/02/23/snapshots-on-ex2300ex3400/
The command show arp will also display the ip address. But the switch needs ot have a layer 3 interface in that vlan for those to be present. If the gateway is on an SRX then show arp there will display the mac along with the ip address.
Interesting, checking my switches I see is under unit instead of the physical interface.
I can only get to the UBoot and Loader prompts.
=(
spuluka wrote:Interesting, checking my switches I see is under unit instead of the physical interface.
Not sure I understand your comment. Can you show me what you are talking about..
Hi,
I think the answer is on this doc.
Services Feature Guide for EX4600 Switches
https://www.juniper.net/documentation/en_US/junos/topics/concept/dhcp-bootp-qfx-series.html
Regards,
TP
Sorry for the confustion. The kb article has this.
ae0 {
description "A LAG Uplink to EX3300 Virtual Chassis Switch";
native-vlan-id 1;
aggregated-ether-options {
minimum-links 1;
lacp {
active;
periodic fast;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members 30;
}
}
}
}
My switches have this
ae0 {
description "A LAG Uplink to EX3300 Virtual Chassis Switch";
aggregated-ether-options {
minimum-links 1;
lacp {
active;
periodic fast;
}
}
unit 0 {
family ethernet-switching {
interface-mode trunk;
native-vlan-id 1;
vlan {
members 30;
}
}
}
}
Unfortunately, I didn't find interface with index 28, and interface 28 itself (if this error maybe mean physical interface) has zero counters and I believe from moment of first start there was nothing connected to this port. So I'm kinda in dead end. For time this switch is in production I didn't notice any influences of this error messages on device performance, and maybe you are right, that this can be some kind of bug.
Any way, thank you for your help!
Hi Abdul,
Please find the sample config below. Find the Topology used in the attachment.
On CE devices:
root# show vlans >>>> Customer VLAN
CVLAN {
vlan-id 100;
}
root# show interfaces ge-0/0/7 >>>> Interface connected to PE
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members CVLAN;
}
}
}
On PE devices:
root# show interfaces ge-0/0/0 >>>> Interface connected to PE
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
ether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 10 {
vlan-id 100;
}
root# show interfaces ge-0/0/7 >>>> Interface connected to CE
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 10 {
vlan-id-list 100;
input-vlan-map push; /*Add a new VLAN tag to the top of the VLAN stack*/
output-vlan-map pop; /*Remove the VLAN tag from the top of the VLAN tag stack*/
}
root# show vlans >>>> SP VLAN
SVLAN {
interface ge-0/0/0.100;
interface ge-0/0/7.100;
}
root# run show vlans
Routing instance VLAN name Tag Interfaces
default-switch SVLAN NA ge-0/0/0.100
ge-0/0/7.100*
input-vlan-map: define the rewrite profile to be applied to incoming frames on this logical interface.
output-vlan-map: define the rewrite operation to be applied to outgoing frames on this logical interface.
Please let me know if you have any questions.
Regards,
David
Hi Abdul,
On CE devices:
root# show vlans >>>> Customer VLAN
CVLAN {
vlan-id 100;
}
root# show interfaces ge-0/0/7 >>>> Interface connected to PE
unit 0 {
family ethernet-switching {
interface-mode trunk;
vlan {
members CVLAN;
}
}
}
On PE devices:
root# show interfaces ge-0/0/0 >>>> Interface connected to PE
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
ether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 10 {
vlan-id 100;
}
root# show interfaces ge-0/0/7 >>>> Interface connected to CE
flexible-vlan-tagging;
encapsulation extended-vlan-bridge;
unit 10 {
vlan-id-list 100;
input-vlan-map push; /*Add a new VLAN tag to the top of the VLAN stack*/
output-vlan-map pop; /*Remove the VLAN tag from the top of the VLAN tag stack*/
}
root# show vlans >>>> SP VLAN
SVLAN {
interface ge-0/0/0.100;
interface ge-0/0/7.100;
}
root# run show vlans
Routing instance VLAN name Tag Interfaces
default-switch SVLAN NA ge-0/0/0.100
ge-0/0/7.100*
input-vlan-map: define the rewrite profile to be applied to incoming frames on this logical interface.
output-vlan-map: define the rewrite operation to be applied to outgoing frames on this logical interface.
Sorry for the delayed reply. I tried with multiple versions so versioning isn't an issue. It's the way the irb interface handles that connection when it is the gateway apparently. Ultimately I ended up setting up a switchport with an inet address and everything works as inteded. For whatever reason, what used to work with a vlan interface on non ELS switches doesn't work with an irb interface on ELS switches.