I recently ran into an issue with Class of Service on an SRX device where DSCP markings on traffic we not being seen on an upstream router when going through an SRX. After running packet captures showing the DSCP-marked traffic leaving the SRX the customer still wanted to proceed with troubleshooting the SRX as being at fault.
It’s been a while since I wrote up a new post, so I thought I would come back with a nice post about the changes in configuring DHCP Servers on the SRX’s. Since Junos 12.x a new DHCP process came out to help fix some long standing issues with the existing feature. In this post I will discuss the old configuration, some of the problems I would regularly encounter, and the configuration of the new DHCP process.
And now for something completely different… Many enterprises have multiple Secure Access (SA) or MAG appliances distributed globally to provide better remote access experiences to users all around the world. This post will discuss the need for a configuration push option, as well as describe how to perform said push.
Junos is a very powerful networking operating system, and by harnessing it we can perform more unusual tasks than we could with other alternatives. Today I will discuss a more unusual scenario to utilize conditional router advertisements and NAT to provide access to services. When the network is unavailable then the SRX will automatically disable its advertised routes.
In a recent post I described the cutover procedure used to move from a Virtual Chassis (VC) configuration to a Multi-Chassis Link Aggregation Group (MC-LAG) configuration. One of the other requirements on this cutover was to utilize DHCP Relay. However I ran into a problem getting the DHCP Relay to work.
The MX960 platform is known as one of Juniper’s flagship platforms in that it is flexible enough for deployments across services providers and enterprises alike. Recently I had the experience of converting an MX960 Virtual Chassis (VC) to an MX960 Multi-Chassis Link Aggregation Group (MC-LAG). This post discusses how the migration was performed.
So I have moved the blog from Tumblr over to WordPress, and the new DNS propagation should be completed by the end of the day.
On a sad note, I did not pass the JNCIE-ENT Beta exam. Back to the drawing board on that.
In a future post I will talk about migrating a MX Virtual Chassis to MX MC-LAG configuration. This should be exciting.