Nikolay Abromov blog

I got this strange behaviour where the IPv6 doesn't work correctly or not working at all on LT interfaces. http://www.juniper.net/techpubs/en_US/junos12.2/topics/concept/logical-systems-restrictions.html Logical systems have the following operations and restrictions: * You can configure only Frame Relay interface encapsulation on a logical tunnel interface ( lt- ) when it is configured with an IPv6 address. So if you are using Logical Systems on Juniper and you have to do IPv6 labs avoid encapsulation ethernet. Example root@jnlab# show interfaces {     lt-2/2/0 {         unit 46 {             encapsulation frame-relay;             dlci 100;             peer-unit 45;             family inet {                 address 172.27.0.58/30;             } ...

Configuring Node-Link Protection for OSPF You can configure node-link protection on any interface for which OSPF is enabled. Node-link protection establishes an alternate path through a different routing device altogether for all destination routes that traverse a protected interface. Node-link protection assumes that the entire routing device, or node, has failed. The Junos OS therefore calculates a backup path that avoids the primary next-hop routing device. Node-link protection is supported on: OSPFv2 and OSPFv3 interfaces OSPFv3 unicast realms OSPFv2 unicast topologies All routing instances supported by OSPFv2 and OSPFv3 Logical systems To configure node-link protection for an OSPF interface: Include the  node-link-protection  statement at the  [edit protocols (ospf | ospf3) area  area-id interface  interface-name ]  hierarchy level. Best Practice:  You must also configure a per-packet load-balancing routing policy to ensure t...

IRC Freenode is something really useful. It's amazing that people still prefer to use a real-time chat services rather than forums and mailing lists.

It's really lovely how straight-forward the JunOS conditional routing is. There is a quick example how to configure it. In the example we are monitoring the IS-IS route 172.27.255.2/32 and if it's in the routing table we will generate 172.27.0.0/16 route. The important bit here is the generate route and the policy which is in the end of the 'generate route' statement. [edit logical-systems r1 routing-options] root@m# show generate { route 172.27.0.0/16 policy isis-present; } policy-statement isis-present { term 1 { from { protocol isis; level 1; route-filter 172.27.255.2/32 exact; } then accept; } term 2 { then reject; } }

##################################################################################################### ## ISIS ##################################################################################################### # Be sure to set family iso on the interface to be placed into ISIS set interfaces <interface> family iso # By default Junos places interfaces as L1/L2 # Default route leaking:         L1 to L2 - all internal routes         L2 to L1 - 0/0 route # L1/L2 will send the attached-bit down to L1 and it will act as a NSSA-like area.  When the L1 interface # receives the attached-bit it will inject a 0/0 route into the RIB point to the L1/L2 interface. # To disable the attached bit use: set protocols isis ignore-attached-bit # Be careful with the "interface all" command, as it may have some unexpected consequences such as trying # to establish a neighbor on your fxp0 management...