Juniper firmware upgrade MX80/480 and 960 junos 11.4R7>>>13.3R9

juniperjuniper-junos

Ive been tasked with writing the SOp along with implementing the above task of upgrading our core/aggregation and ISP routers in my environment.

Were currently running 11.4R7 and after speaking with our Juniper rep he has advised 13.3R9 would be the best choice.

I have gathered the necessary firmware along with whitepapers and procedures. This will be my first go round with a Juniper upgrade so I am as expected slightly nervous. Im fairly new to Juniper but have years of experience in Cisco environments.

Those of you who have experience in this, what can I expect as far as turn over time per device? Any gotchas you have seen or experience that are worth sharing? Ive read the upgrade guide all 350 pages along with many other things.

Those of you who have done this before what was your methodology for proceeding through the process start to finish?

Thanks in advance,

Best Answer

I have been doing a lots of Junos Upgrade on MX960 and few even bigger stuff like PTX5k or T4k here is short instruction about MX960 http://ipexptobe.blogspot.com/2016/09/junos-upgrade.html

Maybe this will be usefull

Cheers, Patrick

Related Solutions

Juniper – Static Routes Between Virtual Routers on SRX100

In Junos you can add a route to point at your next routing table. EG If you wanted to route 0.0.0.0/0 to your routing instance called untrust you would use this syntax

set routing-options 0.0.0.0/0 next-table untrust.inet.0

The untrust routing instance is configured using

set routing-instances untrust instance-type virtual-router
set routing-instances untrust interface x.0
set routing-instances routing-options static route 0.0.0.0/0 next-hop x.x.x.x

Then if you did a show route 1.1.1.1 you should see something like this

>show route 1.1.1.1

inet.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0           *[Static/5] 1d 22:15:55
                      to table untrust.inet.0

untrust.inet.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

0.0.0.0/0           *[Static/5] 1d 22:14:42
                    > to x.x.x.x via ge-0/0/0.0

Juniper MX80 drops generated (TCP?) packets

Finally I found the issue, which was quite a stupid moment... The problem was the MTU of the link combined with many 1514byte packets in the PCAP with the DF bit set.

The PCAP file was recorded at a normal Ethernet connection. In this particular time frame, there were several large packets with 1514 bytes each and the Do Not Fragment (DF) bit set. During the troubleshooting process, I replaced the MX80 with a Cisco ASR10002-f router, and used show ip cef switching statistics which in turn shows a high counter for RP LES Fragmentation failed, DF.

After knowing this I modified the PCAP and truncated the packet in sizes below 1500, and the problem was gone.

Best Answer

Related Solutions

Juniper – Static Routes Between Virtual Routers on SRX100

Juniper MX80 drops generated (TCP?) packets

Related Topic