+ Reply to Thread
Results 1 to 6 of 6
  1. Senior Member
    Join Date
    Dec 2014
    Posts
    261
    #1

    Default Core Routers Are Used For Transition Purpose

    I was watching a video that mentioned that core routers are used for transition purpose. In a service provider the purpose is to route traffic unlike an application provider in which it is a destination.

    In that case why can someone ping the core routers even though they only label switch packets?
    Reply With Quote Quote  

  2. SS -->
  3. Senior Member
    Join Date
    Dec 2014
    Posts
    261
    #2
    Maybe I should rephrase this question. What happens if the customer pings the core routers assuming that they know the ip.
    Reply With Quote Quote  

  4. Junior Member
    Join Date
    Mar 2011
    Location
    Ekaterinburg
    Posts
    7

    Certifications
    CCNA/CCNP/CCIP
    #3
    E.q for troubleshooting purpose.
    Reply With Quote Quote  

  5. Went to the dark side.... Moderator networker050184's Avatar
    Join Date
    Jul 2007
    Posts
    11,665

    Certifications
    CCNA, CCNP, CCIP, JNCIA-JUNOS, JNCIS-SP, JNCIP-SP, MCA200
    #4
    What happens? The same thing as any other router that is pinged. It responds unless it is configured not to.
    An expert is a man who has made all the mistakes which can be made.
    Reply With Quote Quote  

  6. Member
    Join Date
    Dec 2012
    Location
    Sydney, Australia
    Posts
    37
    #5
    It's not really clear to me here what you mean by transition purpose. I guess you mean that core routers act only as transit devices in the forwarding path. Generally core routers/switches are used for moving traffic from one part of the network to the other eg: high speed routing/switching with no ACLs, NAT or other functions that could slow them down.

    In regards to your comment about label switched packets, in an MPLS network usually the core routers would be P routers (thinking of service providers here). On a P router the only routes in the global routing table will usually be the loopback addresses of other P or PE routers. P routers only switch labelled packets so they only need to know about the LSP between the ingress and egress LSR and because of this there is no need for a P router to ever know a customer routes because they only need to know how to forward on the LSP between the PE routers that the customers are connected to.

    This is a bit of a simplified explanation, If you want a good understanding of MPLS and how it works I would recommend reading MPLS fundamentals. Im nearly finished reading through it (the first book I have read on MPLS) and it is VERY good at explaining the concepts and has a bucket load of config/scenarios that you can lab out.

    FYI: You of course will be able to ping the P routers IP from a PE edge router in the same network. Generally though the loopback addresses of P routers are not exported into the VRF on the CE device so these routes will generally not be seen from a customer point of view.
    Reply With Quote Quote  

  7. Senior Member pevangel's Avatar
    Join Date
    Feb 2014
    Location
    'Murica!
    Posts
    333

    Certifications
    CCNP, JNCIP-SEC, JNCSP-SEC, CCNA Security, JNCIS-SP/ENT, ITIL
    #6
    I'm going to assume you have some kind of L3VPN and you want to ping a P router. The answer is no you can't ping it because you won't have a route to it. You may have a default route but the PE won't have a route to the P router within your routing instance.
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks