Hi, This is simply because the LDP ID of the P router (192.168.1.2) is not reachable on PE2 (this is what is meant by the "no route" in "LDP Id: 192.168.1.2:0; no route" from your output), this should be simply resolved after you enable a routing protocol in your network. As a recommendation always set the LDP ID manually via the "mpls ldp router-id" command in order not to leave it to the coincidence. I hope that I've been informative. BR, Mohammed Mahmoud. ... View more

Hi Mohamed, Its all about the implementation, with AToM, VPLS, MPLS TE, MVPN and any relatively new technology that is still being developed and enhanced you must take care about the vendors' implementations and which standards and RFCs is it complying with and to what level. I've seen codes that do fragmentation for AToM and codes that don't, codes that support out of order recovery and codes that don't. But in the end the RFCs and standards are there, whether you are using a code that supports what you need or not is your call. Well, taking the AToM fragmentation and reassembly for example, I quote from "RFC 4623 Pseudowire Emulation Edge-to-Edge (PWE3) Fragmentation and Reassembly" : "Fragmentation takes place in the transmitting PE immediately prior to PW encapsulation, and reassembly takes place in the receiving PE immediately after PW decapsulation.", in brief it uses the B and E bits in the control word as well as the sequence number, and since the control word is imposed on the ingress PE and then processed on the egress PE, thus the ingress PE would be capable of fragmentation and the egress PE would be capable of reassembly, again its all about the code you are running. Now to the 1530 MTU point, again I'll take an AToM case (more specifically EoMPLS), the Core MTU must be equal or greater than the summation of: Edge MTU (1500:IP) + Transport Header (14:Ethr + 4:assuming dot1q) + Control Word (4) + MPLS Label Stack (4:LDP + 4:VC), which gives a total of 1530. I believe that the reason behind choosing the value of 1530 in the new codes lies in the fact that it is the most common highest MTU seen in practice, although a value of 1534 is required if EoMPLS VLAN + TE FRR is used, but anyway the MPLS MTU is user settable up to 1580. I hope that I've been informative. BR, Mohammed Mahmoud. ... View more

Hi, Please allow me to step in, I have a couple of comments; the PA-FE-TX and the MTU issue was solved with certain IOS codes (the mtu could be set up to 1530), however the mpls mtu command should do the trick for you if the interface mtu is not user settable, now all you need to do is to accommodate all the overheads allover your path. Regarding MPLS and fragmentation, MPLS with IP payload is fragmented (unless the DF bit is set), while AToM packets can only be fragmented on the ingress PE routers but not on the intermediate P routers. I hope that I've been informative. HTH, Mohammed Mahmoud. ... View more

Hi Shawn, Tried this before on a 7200VXR running 12.2SB code, but unfortunately PBR is not supported under VRF interfaces, you can only do marking. BR, Mohammed Mahmoud. ... View more

Hi, Kindly use Cisco Feature Navigator: http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp P.S I don't believe that you'll find a 12.4T that runs with 128MB DRAM on the 2801, but you'll find a 12.4 code. BR, Mohammed Mahmoud. ... View more

Hi, First of all i would never go from an S Train to a 12.3GD, plus i believe that SSO is only supported in S Train codes. As per IOS upgrade planner you can go to 12.2(25)S7. BR, Mohammed Mahmoud. ... View more

Jack, A wildcard of 0.0.0.0 = host, meaning that it must be an exact full 32 bit match (and it is the default in case you didn't state an explicit wildcard), and thus "access-list 1 permit host 0.0.0.0" = "access-list 1 permit 0.0.0.0 0.0.0.0" = "access-list 1 permit 0.0.0.0". I hope that i've been informative. BR, Mohammed Mahmoud. ... View more

Hi, Just use "access-list 1 permit host 0.0.0.0" and note that the IOS will store it as "access-list 1 permit 0.0.0.0" without the host keyword. BR, Mohammed Mahmoud. ... View more

Hi Nick, You are very welcomed :) GBICs are hot-swappable and thus you don't need to power down the switch to install them, and you won't need any extra special configuration for them to operate, please check the following link: http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/1000gbic/instnote.htm#xtocid16 http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/hardware/quick/guide/2950gsg2.html#wp50759 http://www.cisco.com/en/US/docs/switches/lan/catalyst2950/hardware/installation/guide/hgcable.html#wp1003758 [edit] Mark, sorry for the cross post. BR, Mohammed Mahmoud. ... View more

Hi Jack, Yes you can use " neighbor x.x.x.x distribute-list x in" plus an ACL, but i generally prefer using prefix-lists with route-filtering as they are more scalable, flexible and less CPU intensive than ACLs when we are talking about a large list. BR, Mohammed Mahmoud. ... View more

Hi All, First of all AFIAK we can't load share between iBGP and eBGP (eBGP is always preferred over iBGP) except with VPNv4 (using the "maximum-path eibgp x" command). As for the as-path ignore and as-path multipath-relax commands, they are mutually exclusive, which is very logically since the first instructs the router to ignore the as-path in the BGP best path selection algorithm (to comply with RFC 1771), and the second informs the router to load share across multiple BGP paths even if the as-path is different, if you tried to configure both you should get this error "% Cannot be used in conjunction with 'bgp bestpath as-path ignore'". Anyway, lets wait for Harold's wonderful comments. BR, Mohammed Mahmoud. ... View more

Hi Mohammed, Why don't you use the "debug ip cef packet" command: Router#debug ip cef packet all ? input Apply to ingress traffic output Apply to egress traffic Router#debug ip cef packet all in Router#debug ip cef packet all input ? <1-199> IP access list (standard or extended) <1300-2699> IP expanded access list (standard or extended) rate rate limit Router#debug ip cef packet all input r Router#debug ip cef packet all input rate ? <0-100> msg/s, 0 not rate limited You can replace the "all" with whichever interface you want, and please be as specific as you can using specific interface, ACL and rate if we are talking about an in production router. BR, Mohammed Mahmoud. ... View more