1. System Configuration
2. Interfaces
3. IGPs
4. BGP
5. IPv4/IPv6 Routing
6. Network Security
7. Remote Connectivity
8. Class of Service
9. Multicast

System Configuration

• Remote access protocols and authentication mechanisms
• Local and remote user management
• Customized class templates with varying permissions and commands
• SNMP
• Syslog
• Configuration management
• Network Time Protocol (NTP)
• Dynamic Host Configuration Protocol (DHCP) server configuration
• Miscellaneous system management

Interfaces

• Frame Relay
• Virtual LAN (VLAN) tagged interfaces
• Redundancy and high availability with the Virtual Router Redundancy Protocol (VRRP)
• Helper functions such as DHCP
• Link bundling and aggregated interfaces
• Point-to-point or point-to-multipoint links with a variety of Layer 2 encapsulations

IGPs

• OSPFv2
• OSPF Multi-area, area types, virtual links
• RIPv1/RIPv2
• IGP tasks such as authentication and summarization
• IGP routing policies
• IGP redundancy design and implementation

BGP

• External BGP
• Internal BGP
• Policies to control route advertisement
• Miscellaneous BGP configuration options
• Load balancing BGP routes
• Internet service provider (ISP) Multi-homing scenarios

IPv4/IPv6 Routing

• Static, aggregate, and generated routes
• Filter-based forwarding and policy routing
• Bidirectional Forwarding Detection (BFD)

Network Security

• Securing a network with packet filters
• Network Address Translation (NAT)
• State-full firewall services
• Virtual routers to segment secure services
• Various types of service sets
• IP Security (IPSec) tunnels

Remote Connectivity

• IPSec tunnels as backup links
• Routing over an IPSec or generic routing encapsulation (GRE) tunnel
• GRE tunnel encryption
• GRE tunnels as backup links

Class of Service

• Behaviour aggregate (BA) and Multi-field classification
• Queue scheduling
• Congestion management and avoidance
• Code point rewriting
• Rate limiting with shaping, policing, or both
• Link efficiency mechanisms

Multicast

• Distance Vector Multicast Routing Protocol (DVMRP)
• Protocol Independent Multicast dense mode (PIM-DM)
• Protocol Independent Multicast sparse mode (PIM-SM)
• Bootstrap, Auto-RP, Anycast
• Multicast Source Discovery Protocol (MSDP)
• Source-specific multicast (SSM)

Anyone preparing for JNCIE-ER do contact.

Well story does not end here. Still there is a long way to go. I really want to thank all my family and friends who are always there praying for me.

For tips and tricks about JNCIE there are afew but many.

Most important is your dedication and timing. 2nd thing you can do is, practice as much as you can.

REQUEST: Please remember NDA before asking any question.

1. Network Discovery
2. MPLS  and Traffic Engineering
3. Firewall Filters and Traffic Sampling
4. Multicast
5. IPV6
6. Class of Servic
7. VPNS

I have gone through the book once. Trying it second time and doing the hands on practice also this time.

The recommended stuf to perpare for that is JNCIE Study Guide a great book and Advanced VPNs Training of Juniper.

Partially-Qualified Domain Names (PQDNs)

There are also some situations in which we may refer to a device using an incomplete name specification. This is called a partially-qualified domain name (PQDN), which means that the name only partially specifies the location of the device. By definition, a PQDN is ambiguous, because it doesn’t give the full path to the domain. Thus, one can only use a PQDN within the context of a particular parent domain, whose absolute domain name is known. We can then find the FQDN of a partially-specified domain name by appending the partial name to the absolute name of the parent domain. For example, if we have the PQDN “Z” within the context of the FQDN “Y.X.”, we know the FQDN for “Z” is “Z.Y.X.”

Why bother with this? The answer is convenience. An administrator for a domain can use relative names as a short-hand to refer to devices or sub-domains without having to repeat the entire full name. For example, suppose you are in charge of the computer science department at the University of Widgetopia. The domain name for the department as a whole is “cs.widgetopia.edu.” and the individual hosts you manage are named after fruit.

In the DNS files you maintain you could refer to each device by its FQDN every time; for example, “apple.cs.widgetopia.edu.”, “banana.cs.widgetopia.edu.” and so on. But it’s easier to tell the software “if you see a name that is not fully qualified, assume it is in the ‘cs.widgetopia.edu’ domain”. Then you can just call the machines “apple”, “banana”, etc. Whenever the DNS software sees a PQDN such as “kiwi” it will treat it as “kiwi.cs.widgetopia.edu”.

Differentiating FQDNs and PQDNs in DNS

As mentioned in the prior topic that the trailing dot for the null root domain is usually omitted. This is true in common parlance, and when users specify a domain name in an application; you don’t use the trailing dot in your Web browser for instance. However, within DNS itself, the dot is used to clearly distinguish a FQDN from a PQDN within DNS master files. This allows us to use both FQDNs and PQDNs together. In the example above, “apple” would refer to “apple.cs.widgetopia.edu.”, but “apple.com.” would refer to the fully-qualified domain name for Apple Computer, Inc. You have to be careful about watching the dots here, because “apple.com” (no trailing period) would be a PQDN, and would refer to “apple.com.cs.widgetopia.edu.”, and not the domain of Apple Computer.

Each port may enable loop detection. This optional feature detects that a port has been looped back to the local system. If a loopback is detected, the port is disabled. Note that loopbacks may exist between different ports. The feature will disable any port that both has the feature enabled, and receives an LACP message that was sent from the local system.

To enable or disable loopback detection, use the following commands:

enable lbdetect port <portlist> [retry-timeout<seconds>]

disable lbdetect port <portlist>

You can configure the local router so that it appears to be overloaded. You might do this when you want the router to participate in OSPF routing, but do not want it to be used for transit traffic. (Note that traffic to immediately attached interfaces continues to transit the router.)

You configure or disable overload mode in OSPF with or without a timeout. Without a timeout, overload mode is set until it is explicitly deleted from the configuration. With a timeout, overload mode is set if the time elapsed since the OSPF instance started is less than the specified timeout.

A timer is started for the difference between the timeout and the time elapsed since the instance started. When the timer expires, overload mode is cleared. In overload mode, the router LSA is originated with all the transit router links (except stub) set to a metric of 0xFFFF. The stub router links are advertised with the actual cost of the interfaces corresponding to the stub. This causes the transit traffic to avoid the overloaded router and take paths around the router. However, the overloaded router’s own links are still accessible.

To mark the router as overloaded, include the overload statement at the [edit protocols (ospf | ospf3)] hierarchy level (for routing instances, include the statement at the [edit routing-instances routing-instance-name protocols ospf] hierarchy level):

[edit protocols (ospf | ospf3)]

overload;

To specify the number of seconds at which overload is reset, include the timeout option when specifying the overload statement:

[edit protocols (ospf | ospf3)]

overload timeout <seconds>;

The time can be a value from 60 through 1800 seconds.

I will update Olive page  in a few days i am damn tired

I have been working for long time to get JNCIP done. Last year 2008 July I asked my company to get me boot-camp but they didn’t agree. So in November I wanted to appear as exam was going to held in Islamabad Pakistan. Again I was disappointed as Bomb blast postponed the exam.

At last for April they agreed to take exam in Pakistan for the first time Juniper Networks took lab exam in Pakistan. And I passed the exam.

Jason was the proctor he was very nice person, professionaly and socialy as well.

Now next mile-stone is JNCIE-M/T lets strat…