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
Original Message:
Sent: 09-01-2021 23:36
From: Unknown User
Subject: inet.3 table
I thought I configured the following, I should see inet.3 table. Right ?
root@vMX4# show protocols ospf | display setset protocols ospf area 0.0.0.0 interface ge-0/0/6.46 interface-type p2p[edit]root@vMX4# show | display set | match mplsset interfaces ge-0/0/6 unit 46 family mplsset protocols mpls interface ge-0/0/6.46[edit]root@vMX4# show | display set | match ldpset protocols ldp interface ge-0/0/6.46[edit]root@vMX4# run show mpls interfaceInterface State Administrative groups (x: extended)ge-0/0/6.46 Up <none>[edit]root@vMX4# run show ldp interfaceInterface Label space ID Nbr count Next helloge-0/0/6.46 10.0.0.4:0 1 1[edit]root@vMX4# run show ospf neighborAddress Interface State ID Pri Dead192.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 !!