From: Victor Cappuccio (victor@ccbootcamp.com)
Date: Mon Apr 23 2007 - 15:44:18 ART
Hi,
This is what I understand about those 2 actions in the LFIB
Untagged means the packet will be forwarded out the given interface as IP
packet (0x0800). The Pop tag mean that the penultimate router labels the
packet with the null label (label 3). Is an Egress LSR know now that it
should not process the packet as a labeled packet, the packet should be
treated as a ip packet.
thanks,
Victor Cappuccio.-
Network Learning Inc - A Cisco Sponsored Organization (SO) YES! We take
Cisco Learning credits!
victor@ccbootcamp.com
http://www.ccbootcamp.com (Cisco Training and Rental Racks)
http://www.ccbootcamp.com/groupstudy.html (groupstudy member discounts!)
Voice: 702-968-5100
FAX: 702-446-8012
-----Original Message-----
From: nobody@groupstudy.com on behalf of Iamgoingtobeaccie Iamgoingtobeaccie
Sent: Mon 4/23/2007 11:22
To: ccielab@groupstudy.com
Subject: MPLS
Group,
Do we have a separate list for CCIE-SP??I did subscribe to
CS,but there is no response to it.
I have a basic MPLS topology with OSPF as the IGP.If I
adverise the loopbacks with their default network type,their /32 network is
not being assigned labels.(Untagged) When I change the network type to
point-to-point,i see pop-tag is attached in the "show mpls forwarding" command
which is expected.
Is there a problem with Implicit null tag for /32 networks here.
R1#sh mpls for
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
43 Untagged 5.5.5.5/32 0 Et0/0 190.1.18.5
R1#sh mpls for
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
41 Pop tag 5.5.5.5//24 0 Et0/0 190.1.18.5
---------------------------------
Check out what you're missing if you're not on Yahoo! Messenger
This archive was generated by hypermail 2.1.4 : Tue May 01 2007 - 08:28:37 ART