MPLS AND LDP

Latest reply: Nov 20, 2014 09:13:41 2637 7 0 1

Can any one explain the out put of the following command

<SPE1> display mpls lsp
----------------------------------------------------------------------
LSP Information: LDP LSP
----------------------------------------------------------------------
FEC In/Out Label In/Out IF      Vrf Name
2.2.2.9/32 NULL/3 -/Vlanif30
1.1.1.9/32 3/NULL -/-
3.3.3.9/32 NULL/1025 -/Vlanif30


[LSRA] display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------------------
DestAddress/Mask In/OutLabel UpstreamPeer Next-Hop Out-Interface
------------------------------------------------------------------------------
1.1.1.1/32 3/NULL 2.2.2.2 127.0.0.1 InLoop0
2.2.2.2/32 NULL/3 2.2.2.2 10.1.1.2 Vlanif10
3.3.3.3/32 NULL/1025 2.2.2.2 10.1.1.2 Vlanif10
------------------------------------------------------------------------------
TOTAL: 3 Normal LSP(s) Found.
TOTAL: 0 Liberal LSP(s) Found.
A '*' before a LSP means the LSP is not established
A '*' before a Label means the USCB or DSCB is stale



  • x
  • convention:

tanveer121
Created Nov 18, 2014 17:02:24 Helpful(0) Helpful(0)

i have the following problem while configuration this topology as you can see in the attachment.

before applying tunnel policy to vpn instance A and B i can ping each and every ip of the topology. 

2 all tunnels are up

3 after applying the tunnel policy to both instances A and B . i can not ping to the remote ip of instance A and B

4 all tunnel are up 

mpls te is the topology and  second is the configuration file please check...

This article contains more resources

You need to log in to download or view. No account?Register

x
  • x
  • convention:

StarOfWest
Created Nov 20, 2014 07:25:30 Helpful(0) Helpful(0)

I think you should add the loopback ip addresses into OSPF process.
  • x
  • convention:

tanveer121
Created Nov 20, 2014 09:13:41 Helpful(0) Helpful(0)

As you can see my configuration file and in this file configuration  of ospf 1

are as follow

ospf 1
opaque-capability enable
area 0.0.0.0
network 11.1.1.1 0.0.0.0
network 1.1.1.1 0.0.0.0
network 3.1.1.1 0.0.0.0
mpls-te enable

i add this loopback 0 with ip add 11.1.1.1  to ospf process... bgp session is established and LDP sessions are also in up state...... 

every thing working fine but with the apply of tunnel policy two vpn sites for customer A stop communication........

check the topology 


  • x
  • convention:

Sentinel
Created Nov 13, 2014 14:18:03 Helpful(0) Helpful(0)

OK let me try:

 

I assume the first column is fairly obviuos as it is the destination prefix the LSP refers to.

Column 2 shows the inbound and outbound labels. There will be variations depending on physical and logical network topologies but in general the inbound label will be the label this router expects to see on incoming frames for that destination. This will have been generated internally and advertised to the peer router(s) using LDP. The outbound label will be the label this router will use when sending the same frame out, this will generally have been learned from the peer router using LDP. In the event that either label shows as NULL, it either refers to a local link or frame from or to a peer which is not running LDP.

Column 3 shows the interfaces associated with the given labels for receiving and forwarding the frames, you clearly only have a couple of routers in your topology so it is a bit difficult to see anything particularly meainingful.

 

With a slightly larger network, say 4 or 5 routers you could actually get to see a proper LSP with labels being swapped, if you had multiple paths you could even see different labels for different paths - with just a couple of routers there is not much to see.

 

Take a look at the attached sequesnce and hopefully it should make a bit more sense.

 

Regards Nigel

 

This article contains more resources

You need to log in to download or view. No account?Register

x
  • x
  • convention:

tanveer121
Created Nov 15, 2014 05:00:04 Helpful(0) Helpful(0)

[LSRA] display mpls ldp session
LDP Session(s) in Public Network
Codes: LAM(Label Advertisement Mode), SsnAge Unit(DDDD:HH:MM)
A '*' before a session means the session is being deleted.
------------------------------------------------------------------------------
Peer-ID       Status           LAM      SsnRole    SsnAge   KA-Sent/Rcv
------------------------------------------------------------------------------
2.2.2.2:0   Operational      DU      Passive        000:00:22            91/91
------------------------------------------------------------------------------

TOTAL: 1 session(s) Found.

In fourth column SsRole is passive but some time this role is active...... what is passive and active indicates?

and with peer-id 2.2.2.2:0  what is :0 indicates?


  • x
  • convention:

tanveer121
Created Nov 15, 2014 15:56:30 Helpful(0) Helpful(0)

what are the possible reason  that the tunnel is down?

display int Tunnel 0/0/0
Tunnel0/0/0 current state : UP
Line protocol current state : DOWN
Description:this tunnel connected to 44.1.1.1
Route Port,The Maximum Transmit Unit is 1500
Internet Address is unnumbered, using address of LoopBack0(11.1.1.1/32)
Encapsulation is TUNNEL, loopback not set
Tunnel destination 44.1.1.1
Tunnel up/down statistics 0
Tunnel protocol/transport MPLS/MPLS, ILM disabled
Current system time: 2014-11-14 23:51-08:00
    300 seconds output rate 0 bits/sec, 0 packets/sec
    20 seconds output rate 0 bits/sec, 0 packets/sec
    0 packets output,  0 bytes
    0 output error
    0 output drop
    Input bandwidth utilization  : --
    Output bandwidth utilization : --


  • x
  • convention:

tanveer121
Created Nov 16, 2014 07:39:52 Helpful(0) Helpful(0)

HCIE-R&S Info Session (for WEU/Western Europe region)

http://support.huawei.com/learning/nodeQueryAction!loadTrainProjectInfo?lang=en&pbiPath=term1000025144&courseId=Node1000007801


  • x
  • convention:

Reply

Reply
You need to log in to reply to the post Login | Register

Notice Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!
Login and enjoy all the member benefits

Login and enjoy all the member benefits

Login