Resolved… with the following…
FPC showed a difference between what was running and what is available…
reminiscent of IOS-XR upgrades and subsequent fpd/fpga upgrades.
show system firmware
FPC 0ZL30634 DPLL 9 6022.0.0 7006.0.0
OK
request system
As I recall, proxy-arp behavior is proven by looking in the local host arp
cache and finding entries for foreign ip’s mapped to the default gateway’s mac
address. If that is still occurring, then it would seem that proxy arp
functionality is still working and you can move on to tshooting
…which is probably why you can configure it as “0” and Junos expands it to
“0.0.0.0”
Aaron
> On Nov 28, 2023, at 10:07 AM, Christian Scholz via juniper-nsp
> wrote:
>
> Also might be worth mentioning that the Router-ID - although it might look
> like one and you would usually use one you
I recall the MX204 being like that… an XE interface with a 1g speed command on
the interface
Aaron
> On Nov 3, 2023, at 11:00 AM, Olivier Benghozi via juniper-nsp
> wrote:
>
> Actually 1G ports are «10G ports operating at 1G speed».
> So, configured as 10G ports on chassis side, giga-ether
Years ago I had to get a license to make my 10g interfaces work on my MX104
Aaron
> On Oct 25, 2023, at 5:03 AM, Tobias Heister via juniper-nsp
> wrote:
>
> Am 25.10.2023 um 11:57 schrieb Xavier Beaudouin via juniper-nsp:
>>> So there are a couple of enforced licenses even on MX ... and they
To reiterate and add to my previous email…also, please realize I’m in my early
stages of learning about telemetry and Junos capabilities, so this is only what
little I’ve seen and understand about it thus far…
As a side note, the ACX7100-48L has been a challenge regarding telemetry as
well,
Also saw this message too…
Error related to jflow-specific reporting rate
[edit services analytics]
'sensor my-sensor-21'
reporting-rate can't be less than 30sec for Inline Jflow Sensor on mx304!
error: configuration check-out failed
Aaron
> On Oct 18, 2023, at 8:48 AM, Aaron1 wrote:
>
I have an MX304 in the lab, evaluating it at the moment. Junos: 22.2R3.15
Telemetry is running and a little different than what I have on my MX960’s
Also, I get a license warning when committing OSPF and LDP. We got a license
from our account team and now we don’t see that message anymore
Juniper is sending me a new one, thinking it’s a faulty unit.
Aaron
> On Jun 13, 2023, at 10:28 AM, Andrey Kostin wrote:
>
> Aaron Gould via juniper-nsp писал(а) 2023-06-12 11:22:
>
>> interestingly, the PR is said to be fixed in 22.2R2-EVO, wouldn't that
>> follow that it should be fixed in
9 matches
Mail list logo