JNCIP-M Lab preparation doubts - Telnet Logical router

william_yeowilliam_yeo Member Posts: 63 ■■□□□□□□□□
Hi Master,

I'm in the midst preparing for my JNCIP lab.

*By the way, i encounter a problem as i jz managed to setup my OLIVE lab and i'm wondering is ther anyway for me to Telnet to different Logical router ? All i can now is jz access to Main router only.


Any advice and comment are welcome :D

I using study material :
1. JNCIP-M Official Study Guide
2. AJNR_7.a
3. CJNR_7a

LAB :
1. FreeBSD + JUNOS 8.5 Olive

* Is my material sufficient ?



Thanks In advance

Comments

  • AldurAldur Juniper Moderator Member Posts: 1,460
    You really can't Telnet into a specific logical router. You have to telnet into the main routing instance and then configure any logical routers from there.

    When I've done this in the past I've Telnet'd into the main routing instance multiple times, how ever many logical routers I had configured. Then I would leave each open Telnet window at the desired logical router. This prevented the extra pain of jumping between logical routers.

    And yup, your study mats should be enough to get you through the exam.

    Good luck and let us know how your studying goes.
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • hoogen82hoogen82 Member Posts: 272
    How about something like this??

    Navigating the CLI is a bit unwieldy using Logical Routers if you're working from the root of the physical device, so its highly advisable to configure individual user accounts for each logical router. This will enable you to log in to each logical router and be positioned within the root of that logical router as if you were in the root of a real physical router. This can be accomplished with the following configuration:

    system {
    class dc {
    idle-timeout 0;
    logical-system dc;
    permissions all;
    class r7 {
    idle-timeout 0;
    logical-system r7;
    permissions all;
    }
    user dc {
    uid 2014;
    class dc;
    authentication {
    encrypted-password "xxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA
    }
    }
    user r7 {
    uid 2010;
    class r7;
    authentication {
    encrypted-password "xxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA
    }
    }
    }
    }
    IS-IS Sleeps.
    BGP peers are quiet.
    Something must be wrong.
  • william_yeowilliam_yeo Member Posts: 63 ■■□□□□□□□□
    hoogen82 wrote: »
    How about something like this??

    Navigating the CLI is a bit unwieldy using Logical Routers if you're working from the root of the physical device, so its highly advisable to configure individual user accounts for each logical router. This will enable you to log in to each logical router and be positioned within the root of that logical router as if you were in the root of a real physical router. This can be accomplished with the following configuration:

    system {
    class dc {
    idle-timeout 0;
    logical-system dc;
    permissions all;
    class r7 {
    idle-timeout 0;
    logical-system r7;
    permissions all;
    }
    user dc {
    uid 2014;
    class dc;
    authentication {
    encrypted-password "xxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA
    }
    }
    user r7 {
    uid 2010;
    class r7;
    authentication {
    encrypted-password "xxxxxxxxxxxxxxxxxxx"; ## SECRET-DATA
    }
    }
    }
    }






    thanks to hoogen82 & Aldur.... it works for me !!! going to start my JNCIP-M,,,,,,
Sign In or Register to comment.