Routing

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



Expand all | Collapse all

inet.3 table

  • 1.  inet.3 table

    Posted 09-02-2021 05:25
    I thought I configured the following, I should see inet.3 table. Right ?
    root@vMX4# show protocols ospf | display set
    set protocols ospf area 0.0.0.0 interface ge-0/0/6.46 interface-type p2p
    
    [edit]
    root@vMX4# show | display set | match mpls
    set interfaces ge-0/0/6 unit 46 family mpls
    set protocols mpls interface ge-0/0/6.46
    
    [edit]
    root@vMX4# show | display set | match ldp
    set protocols ldp interface ge-0/0/6.46
    
    [edit]
    root@vMX4# run show mpls interface
    Interface        State       Administrative groups (x: extended)
    ge-0/0/6.46      Up         <none>
    
    [edit]
    root@vMX4# run show ldp interface
    Interface            Label space ID        Nbr count   Next hello
    ge-0/0/6.46          10.0.0.4:0               1           1
    
    [edit]
    root@vMX4# run show ospf neighbor
    Address          Interface              State     ID               Pri  Dead
    192.168.46.13    ge-0/0/6.46            Full      10.0.0.5         128    33
    
    [edit]
    root@vMX4# run show route table ?
    Possible completions:
      <table>              Name of routing table
      inet.0
      inet6.0
      mpls.0
    [edit]
    ​

    But I did not.  What did I miss ?

    thanks !!



  • 2.  RE: inet.3 table

    Posted 09-02-2021 08:35
    The inet.3 table will only be created if there are label advertisements received from the peer device and it is in use by the router for label imposition. You are using LDP in this case as the label distribution mechanism, do a show ldp database session <PEER-IP> and you will observe that most likely no label assignment has been advertised from your peer device, this is the reason why inet.3 is not on your vMX4 device, since no instruction to do label imposition operation, there is no need to create inet.3 in this case.

    Elvin