linux and networking articles

Category: Juniper (page 1 of 2)

PPPoE termination on a Juniper MX

This post is about terminating PPPoE sessions dynamicly on a Juniper MX. Recently i’ve setup dynamic PPPoE termination succesfully on a MX series, the goal was to migrate PPPoE termination functionality from a Cisco 7206 VXR towards one of our Juniper MX’s.

There is documentation from juniper that describes how to set this up:

I stumbled upon several weird things while testing with PPPoE that i thought may be worth sharing.

There are several ways to setup PPPoE termination on a MX:

  • Static subscriber management
  • Dynamic subscriber management

When configuring static subscriber management you need to provision a logical interface for each subscriber, this will not scale when you hit more subscribers.

Dynamic subscriber management is the way i wanted to go, because of the amount of subscribers we have.

JunOS version 13.3R9 experiences

I started testing on JunOS 13.3R9, some things:

  • Documentation was not clear on whether you needed to set the access-profile at the vlan-profile or global.
  • Noticed that the command set available was not very useful for some serious troubleshooting
  • The dynamic ppp profile needs to end with -profile in the name, if you think of using a different name it will not work, it’s probably documented somewhere internally at Juniper.
  • IPCP DNS configuration for clients was not configurable and supported in this release.
  • test aaa commands cannot be used on a MX, you can give the command but it won’t do a thing. This command is apparently only valid on a Juniper EX?

After this experience a new recommended JTAC version was released so i continued with testing on JunOS 15.1R6.7.

JunOS version 15.1R6.7 experiences

Right after the upgrade from JunOS 13.3R9 towards 15.1R6.7, the PPPoE configuration that was previously working stopped completely.

After doing some packetcaptures i could see the PADI coming in from clients, but the MX was dead silent. “show pppoe statistics” were all at 0 confirming the MX was dead silent.

After some debugging i found the following message from auto-configuration:

The reason of this message is that dynamic subscriber management apparently only works on JunOS 15.x and onwards when you run the chassis in enhanced ip mode. I couldn’t find a reference of this in the release notes, but ok… :-)

After setting the configuration as described here PPPoE started working again! So what is this PPPoE configuration about?

The Cisco 7206VXR configuration for PPPoE that I was trying to convert was basicly the following config:

Configuration of dynamic subscriber management

Here is the configuration that i have used to setup dynamic subscriber management using dynamic vlans and dynamic PPP interfaces. The result of this configuration is that end-users can plug-and-play and the only thing you need to do is have a radius account for the happy enduser.

AAA configuration

System configuration

Before applying any dynamic-profile related stuff, I’ve enabled versioning on the MX, this allows a dynamic-profile to be adjusted while subscribers are online.

Dynamic vlan profile configuration

Dynamic ppp profile configuration

Interface configuration

Although it looks easy, it took a while before getting things working and to know how the demux interface works (or not ;-)).

I hope this helps other people setting up PPPoE termination on the MX platform, feel free to comment.

CLI commands to check optical attenuation

This post outlines CLI commands to check the optical attenuation on Cisco , Juniper , Huawei and Brocade platforms.

To check the attenuation, you need to have DOM (Digital Optical Monitoring) support in the optics.

Cisco Catalyst series:

Continue reading

Getting started with the JNCIP-SP

Designed for experienced networking professionals with advanced knowledge of the Juniper Networks Junos OS, this written exam verifies the candidate’s understanding of advanced routing technologies and related platform configuration and troubleshooting skills.

As it is the beginning of 2016, it is time to set new goals for this year. One goal is to achieve the Juniper JNCIP-SP exam. After the re-certification of JNCIS-SP and JNCIA in Oktober I thought it would be good to start studying on the JNCIP-SP exam as we are going to implement Juniper MX80 boxes this year. The JNCIP-SP exam objectives are listed here: http://www.juniper.net/us/en/training/certification/resources/jncip-sp/

I recommend creating an excel sheet for the topics that are listed on the exam so you can track your progress and see where you need to focus on. The one i created looks like this:

JNCIP-SP Excel sheet

JNCIP-SP Excel sheet

Before starting I have collected study materials for the Juniper JNCIP-SP exam on the Juniper website itself and ordered O’Reilly books from Amazon. Here is a list of the materials I am using right now.

Hardcover Books
  • Juniper MX Series (O’ Reilly)
  • Junos Cookbook (O’ Reilly)
  • MPLS enabled applications (by Ina Minei)

I have made some notes on the Juniper MX Series as I am reading the books chapter by chapter.

eBooks (PDF)
  • JNCIP_studyguide by Harry Reynolds (.pdf file from Juniper site)
  • Several Juniper Day One guides (from Juniper site)
    • mastering automation
    • deploying BGP multicast VPN’s
    • deploying MPLS
  • JNCIS-SP studyguides from the Juniper fasttrack
Alternative resources

Next to taking the official courses, you can order the official course material which is used in the classes. My personal preference is self-study and the official training books are a little bit too expensive to buy. So i decided to start studying without these materials.

VMware and olive lab setup

As this exam is CLI and syntax intensive I created the topology as listed in the JNCIP Studyguide in VMware ESXi with several Olives. The topology i created in VMware is the following:

JNCIP-SP topology

JNCIP-SP topology

This is the well-known fish topology and should be suitable for any kind of topic that is present in this exam as it contains a mix of CE, PE, and P routers.

Expect blog posts about the several topics in this exam, just as i did with the CCNP-SP blog posts and hopefully I will be ready within a certain a mount of time.

If you have other suggestions regarding the materials listed please let me know!


Juniper bridging, vlan mapping and irb

These are my notes for chapter two of the Juniper MX Series book.

There are two styles of configuration when it comes to bridging and VLAN mappings:

  • Enterprise style
  • Service Provider style

The enterprise style is easier to configure but less flexible, SP style requires more configuration and offers flexibility see here now.

  • IFD (Interface Device) = physical interface
  • IFL (Interface Logical) = sub-interface (unit config)
  • IFF (Interface Family) = protocol
  • IFA (Interface Address) = inet or inet6 address

Continue reading

Older posts

© 2017 ipnetworking.net

Theme by Anders NorenUp ↑