Hi There,
I have seen this quite a few times so we have been working on a kb, try to follow it and let us know if this fixes the problem
Hope it helps! if it does dont forget to leave your feedback about the KB as well 
↧
Re: Virtual-Chassis QFX5100
↧
Re: EX4200, PoE not working on all ports
I upgraded this switch stack to Junos 12.3R12-S12 which is the JTac recommended version. It did not make any difference, I still have the same ports without PoE power. I have another edge closet with only one EX4200-PX switch. This switch has nearly all of its ports requiring PoE between phones, security cameras, and wireless access points. It had two ports where PoE was working and now is not working. I also installed the Junos 12.3 code on this switch and it made no difference.
Several months back we had an EX4200 with PoE problems. We would boot the switch, all ports went active with blinking lights everywhere. We would watch as ports would start failing one after the other with lights going out.
↧
↧
Re: EX4200, PoE not working on all ports
When I first started troubleshooting this problem, I went to the command line and issued a show poe controller command. This is the first time I had ever used this command since we have never had PoE problems before. The message I received was the PoE firmware needed upgrading. I was not even aware that upgrading PoE firmware was a separate process from upgrading Junos. We applied the upgrade to PoE to all of our switches. I do not know what PoE firmware version that was installed, but it is now version 4.1.6. Could the PoE firmware upgrade be the root cause of this issue?
↧
Re: EX4200, PoE not working on all ports
Hi HendersonD,
Absolutely, did you mean that message to upgrade the POE firmware was seen after the first reboot while on the Junos 15.1? That means the Junos version has a more latest POE firmware than what's installed on the switch at the time:
https://www.juniper.net/documentation/en_US/junos/topics/task/installation/poe-controller-software-upgrading.html
Assume the firmware upgrade has resolved it for you now? That's good news .
Hope this helps.
Regards,
-r.
--------------------------------------------------
If this solves your problem, please mark this post as "Accepted Solution."
Kudos are always appreciated .
↧
Re: Juniper EX4300MP activity LED's
UPDATE: After a couple of escalations of the ticket, I have received confirmation; This issue is a bug and they are working on the patch.
Regards,
T
↧
↧
Re: EX4200, PoE not working on all ports
We upgrade to 15.1 code a long time ago on these switches. At that time I had no idea there was also a PoE firmware upgrade that needed to be run. It was only last week when my switches rebooted due to a power outage and they had PoE problems did I realize there was firmware to upgrade. I upgraded the firmware at that time. The problem still persists, I still have PoE ports that should be active but are dead. The question becomes is the root cause of the problem the PoE firmware upgrade?
I do have this piece of code of every switch. We have had the lldp interface all for years. We added the lldp-med interface all when we added our IP phones
protocols {
igmp-snooping {
vlan all;
}
rstp;
lldp {
interface all;
}
lldp-med {
interface all;
}
}
↧
Not fully functional when booted from backup image
We have a a good number of EX2200 switches. We've observed issues when the switch boots from the backup partition (which, unfortunately, happens all too often when we restart our EX2200s).
Things like aggregated links may not function at all, or LLDP won't be started (despite the config clearly calling for AE interfaces and LLDP on all interfaces). This is even with a MATCHING version in both partitions. The switch boots from the backup partition just fine, and has a good config, but certain random services just don't start.
This occurs on both our EX2200 switches setup in VC, and standalone switches. This also occurs with versions 12 or 15 (yes, I know they pulled 15, and we are working on downgrading all of them to 12).
I've searched all over for information on this behavior, but haven't been able to find anything about missing functionality/services when booted from an equivelent backup version. I'm hoping someone can help point us in the right direction.
↧
Re: Not fully functional when booted from backup image
Hi,
Is there are a reason for keeping it booting from the backup partition?
https://kb.juniper.net/InfoCenter/index?page=content&id=KB23180
↧
Re: Juniper EX4300MP activity LED's
Thanks for the update. Glad to hear it is just a bug and the fix is in progress.
↧
↧
Re: Not fully functional when booted from backup image
The backup partition has both config and system so it is important to update the snapshot when config changes occur. Have definately seen issues which amount to a config rollback when the reboot goes to the backup partition.
But your issues seem that it might be different. If you have config that is in place and not working that is probably worth digging into the specifics. How do you end up fixing the issues? Config changes? reboots? other?
↧
Re: Not fully functional when booted from backup image
Config file versions 1-4 are stored in a different partition than backup or primary partitions. Versions >5 are stored in yet a different partition (/var)
https://kb.juniper.net/InfoCenter/index?page=content&id=KB21062&actp=LIST#Step1
Snapshotting after every config change is not needed.
% df -k|grep da0 /dev/da0s2a 331778 257992 47244 85% / <=current boot partition /dev/da0s3e 173752 16200 143652 10% /var /dev/da0s3d 908710 77368 758646 9% /var/tmp /dev/da0s4d 118292 284 108546 0% /config
% ls -la /config/*.conf* -rw-r----- 1 root wheel 2338 Mar 19 13:00 /config/juniper.conf.1.gz -rw-r----- 1 root wheel 2341 Mar 19 12:56 /config/juniper.conf.2.gz -rw-r----- 1 root wheel 2347 Feb 18 12:46 /config/juniper.conf.3.gz -rw-r----- 1 root wheel 2368 Mar 25 15:54 /config/juniper.conf.gz ---x--x--- 1 root wheel 32 Mar 25 15:54 /config/juniper.conf.md5 -rw-r----- 1 root wheel 2347 Feb 18 12:51 /config/rescue.conf.gz
test@test> show system commit 0 2019-03-25 15:54:30 PDT by xxx via netconf commit synchronize 1 2019-03-19 13:01:17 PDT by xxx via cli commit synchronize 2 2019-03-19 12:56:40 PDT by xxx via cli commit synchronize 3 2019-02-18 12:46:59 PST by xxx via other
↧
Re: Not fully functional when booted from backup image
Well, I know from lots of personal experience with Junos 12.3 at least on the ACX platform that booting to the alternate root reverts the active configuration to the one that was present at the time the snapshot was taken.
This happened multiple times over 3 years of experience where we have to managing the snapshoting of devices after every configuration change to avoid losing configuration changes when booting to the alternate partition.
Have not had the issue since upgrading to 15 but at the same time we have automated keeping the snapshots up to date so don't really know if it would still be occuring if we did not have that under control.
↧
LACP scenario
Hi everyone,
Please consider the following example:
SW1 gig1-----------gig1SW2
gig2------------gig2
Both switcehs have been configured with lacp.
LACP allows the switches to bundle the ports with same speed/duplex mode. This requires SW1 to know the current speed/duplex of gig1/gig2 on SW2 .
1) How does SW1 determine the speed/duplex of the gig1 /gig2 on SW 2 and vice versa? LACP ensures ports with same speed/duplex are bundled . When I look at the capture for LACP, I do not see any info about the speed/duplex being carried in LACP message so how does SW1 determine the speed /duplex of the gig1/gig2 on SW2?
Thanks and have a good weekend!!
↧
↧
Re: LACP scenario
Link speed and duplex negotiation is done seperately per interface outside the scope of LACP.
For GigE it will usually be done via autonegotiation where each links announces it's capabilities and agrees on the best match. Usually 1G/full-duplex today. You can force speed/duplex but it not recommended today.
There will be differences when looking at fiber transceivers where they will only run a specific speed and link will not come up if the other end doesn't match.
First when the interface is up with an agreed speed/duplex LACP PDUs will be sent out on the link in question.
↧
Re: LACP scenario
Sarahr,
Do share the config to check on this...
//Nex
↧
Re: more advanced using pipe for MORE specific output
Hi all
Thanks for ideas... All commands you showed are really nice particularly -show interfaces ge-0/0/5 extensive | match "^ +[0-7]|counters:"|except none$ . Thanks Nellikka...
I like to ask another qs to Nellikka. How can be troubleshoot when tail-dropped-packet occurs?
The following interface has dropped packets in the last a week after clearing the associated interface's statistics.
>show interfaces queue ge-0/0/5
Physical interface: ge-0/0/5, Enabled, Physical link is Up
Interface index: 134, SNMP ifIndex: 512
Description: ap_111
Forwarding classes: 16 supported, 6 in use
Egress queues: 8 supported, 6 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Transmitted:
Packets : 57831267
Bytes : 66421486085
Tail-dropped packets : 14
RL-dropped packets : 0
RL-dropped bytes : 0
Queue: 1, Forwarding classes: bs-app
Queued:
Transmitted:
Packets : 0
Bytes : 0
Tail-dropped packets : 0
RL-dropped packets : 0
RL-dropped bytes : 0
Queue: 2, Forwarding classes: bs-app-interact
Queued:
Transmitted:
Packets : 0
Bytes : 0
Tail-dropped packets : 0
RL-dropped packets : 0
RL-dropped bytes : 0
Queue: 3, Forwarding classes: high-priority
Queued:
Transmitted:
Packets : 0
Bytes : 0
Tail-dropped packets : 0
RL-dropped packets : 0
RL-dropped bytes : 0
Queue: 5, Forwarding classes: expedited-forwarding
Queued:
Transmitted:
Packets : 0
Bytes : 0
Tail-dropped packets : 0
RL-dropped packets : 0
RL-dropped bytes : 0
Queue: 7, Forwarding classes: network-control
Queued:
Transmitted:
Packets : 249381
Bytes : 23256570
Tail-dropped packets : 0
RL-dropped packets : 0
RL-dropped bytes : 0
↧
Re: more advanced using pipe for MORE specific output
Tail-dropped packets—Number of arriving packets dropped because output queue buffers were full.
If you are using any custom scheduler, please check allocated buffer size and the transmission rate configured.
Congestion can be managed by using drop profiles and packet loss priorities:
https://www.juniper.net/documentation/en_US/junos/topics/concept/cos-packet-loss-priority-understanding-security.html
https://www.juniper.net/documentation/en_US/junos/topics/concept/red-drop-profile-overview-cos-config-guide.html
https://forums.juniper.net/t5/Junos/Tail-dropped-packets/td-p/309331
↧
↧
Re: LACP scenario
LACP functions at the layer 2.
Speed and duplex are layer 1 properties. This is the reason we would not see lacp carrying those parameters.
L1 properties are negotiated before the lacp exchanges. If L1 properties like speed and duplex are not correct the interface itself will not be up.
As far as same speed and duplix requirement ij lacp it is for the local node and not the remote node.
↧
Re: LACP scenario
@sarahr202 - LACP active (802.3ad) standard does not allow for mix-match of different speed/duplex ports into a bundle. So if the interfaces for a LACP bundle have different mis-match, then LACP will not come up. This is sort of a pre-check before LACP negotiation even occurs. In a plain Juniper AE this mis-match should be allowed, but if also set with 802.3ad, then this is not allowed.
HTH
↧
EX2300 cannot change root password
I have super-user rights, and go thru the motion of changing the root password, but it never changes.
When I look at the config, the secret data for the password is the same as what is in all the other switches.
When I log into the switch, as root with the known password, this is what happens:
login as: root Keyboard-interactive authentication prompts from server: | Password: End of keyboard-interactive prompts from server Access denied Keyboard-interactive authentication prompts from server: | Password:
↧