Jump to content

Search the Community

Showing results for tags 'mpls'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • ANNOUNCEMENTS
    • ANNOUNCEMENTS
  • CERTIFICATION - - - - - NO REQUESTS IN THESE FORUMS - - - - -
    • CISCO SYSTEMS
    • COMPTIA
    • LINUX
    • MICROSOFT
    • ORACLE
    • PROJECT MANAGEMENT
    • SECURITY CERTIFICATIONS
    • SUN MICROSYSTEMS
    • WIRELESS
    • OTHER CERTIFICATIONS
  • CISCO TECHNICAL SECTION
    • CISCO LABS
    • GNS3
    • NETWORK INFRASTRUCTURE
    • SECURITY
    • WIRELESS
    • SERVICE PROVIDERS
    • COLLABORATION, VOICE AND VIDEO
    • DATA CENTER
    • SMALL BUSINESS
  • MICROSOFT TECHNICAL SECTION
  • OTHER TECHNICAL SECTION
  • TRAINING OFFERS & REQUESTS
  • CERTCOLLECTION MALL
  • GENERAL FORUMS
  • COMMUNITY CENTER

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 73 results

  1. hello guys, The Network Engineer's Guide to MPLS is needed
  2. anyone please help download below [hide] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content] [Hidden Content]]
  3. Hi Guys, I managed to find a video related to Khawar Butt SD-WAN Topic Please don't forget to hit the Thanks button [hide][Hidden Content]]
  4. Hi Guys ,] need help i can ping internet but trace is going via R8. Can someone help how to make trace going via R7 iPC106#traceroute 8.8.8.8 numeric Type escape sequence to abort. Tracing the route to 8.8.8.8 VRF info: (vrf in name/id, vrf out name/id) 1 172.16.201.1 4 msec 1 msec 1 msec 2 172.16.2.2 0 msec 1 msec 0 msec 3 123.45.67.33 1 msec 1 msec 1 msec 4 123.45.67.13 [MPLS: Labels 22/58 Exp 0] 1 msec 0 msec 0 msec 5 123.45.67.25 [MPLS: Label 58 Exp 0] 1 msec 1 msec 2 msec 6 123.45.67.26 2 msec 1 msec 1 msec 7 172.16.0.5 2 msec 2 msec 1 msec 8 125.45.67.21 3 msec 6 msec 7 msec 9 134.56.78.38 3 msec 2 msec 2 msec 10 134.56.78.6 4 msec 7 msec 8 msec 11 8.8.8.8 9 msec * 3 msec PC106#
  5. Hi guys I recently stumbled into some very strange issue with L3VPN When PE router advertise any inet-vpn unicast route to RR - BGP session torn down with notification "Code 3 Subcode 10 - Incorrect NLRI - Update prefix length 0 too long" and didn't come up again When PE router doesn't advertise inet-vpn unicast route to RR (for example, when I delete interface from routing instance config) - BGP session comes up and everything works fine Config is quite simple - BGP with family inet, inet-vpn unicast, inet6 labeled-unicast, l2vpn signalling. No policies, except next-hop-self on PE. Routing instance type vrf with just RD, vrf-target and interface All devices - Juniper MX80 with Junos 12.3R4 Any suggestions? Did anybody saw issue like that before?
  6. Hi Team, please if anyone have this book name " MPLS: TECHNOLOGY AND APPLICATION" request you to share this wonderful book thanks in advance
  7. edgarl

    MPLS TE

    Hello , i am in the middle of learning MPLS TE , and there is one command that real troubles me , the command : conf t->if tunnel1->tunnel mpls traffic-eng autoroute announce many posts explain that the tunnel become part of IGP or routes that connected to the TAIL END will go over the tunnel etc ... so i read a lot about it , and i can not find the WHY traffic will go over the tunnel in case i issue it. Thanks ,
  8. Hello everyone, Uploading some of GNS3 Vault labs created for web iou. These include some labs on MPLS, BGP, OSPF, EIGRP and RIP. It contains all the topology diagrams, initial configs and the instructions required to complete the lab. Created these a while back for myself as GNS3 eats up a lot of CPU and RAM. I hope these are helpful. Just drop a comment for any suggestions. External download link -[hide] [Hidden Content]] iou-web-export-20131023172633 (GNS3 Vault Labs).gz
  9. Hi All, I am try to get the l2tpv3 up between 21 and 24 21---ppp---9---------5----fr---24 when I am bringing the ckt up, both end serial interfaces ( on 21 and 24 ) go down. and while testing i get the following outputs: R9#ping mpls ipv4 9.9.0.5 255.255.255.255 source 9.9.0.9 verbose Sending 5, 100-byte MPLS Echos to 9.9.0.5/32, timeout is 2 seconds, send interval is 0 msec: Codes: '!' - success, 'Q' - request not sent, '.' - timeout, 'L' - labeled output interface, 'B' - unlabeled output interface, 'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch, 'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry, 'P' - no rx intf label prot, 'p' - premature termination of LSP, 'R' - transit router, 'I' - unknown upstream index, 'l' - Label switched with FEC change, 'd' - see DDMAP for return code, 'X' - unknown return code, 'x' - return code 0 Type escape sequence to abort. F size 100, reply addr 9.9.18.8, return code 4 F size 100, reply addr 9.9.18.8, return code 4 F size 100, reply addr 9.9.18.8, return code 4 F size 100, reply addr 9.9.18.8, return code 4 F size 100, reply addr 9.9.18.8, return code 4 Success rate is 0 percent (0/5) Total Time Elapsed 10 ms any inputs as to what I am missing I have done testing by trying to bring send-label on two ASR's R7 and R8 but it did not succeeded.
  10. Good day, recently I passed MPLS (TS4) and K8. So thanks to all the forum members for sharing information and having such constructive discussions, escpecially: CJ, UldisD, RIKITEE, Xgeneo, WAYTOCCAR, magsoul, netizen, goosfraba, jimmyjiiimz, CCIEin2013. Extra special thanks to CJ for keeping the forum a "tidy" place! What I can remember, here to share: # MPLS / TS4 1 OSPF and RIP OSPF neighborship is init between R26/R24 - there was some filter/acl on R24 preventing neighborship R21 had an area range no-advertise for R26 Loopback 10.1.1.26 - removed it 2 EEM - the event manager was misconfigured, wrong order etc. 3 MPLS/BGP - Missing redistribution from BGP to OSPF on PE R4 - access-list 12 on P routers R1 & R2 was missing loopback0 10.1.1.4 for ldp 4 DHCP/EIGRP R19 had DHCP excluded whole /24 range - changed it to exclude only .20 - .23 R19 DHCP had wrong default router (not problem for the ping) - changed .1 to .19 5 QoS MQC R9 class SILVER was preconfigured with something like "conform-action set-prec-transmit 4 exceed-action set-prec-transmit 4" - changed from 4 to 5 (so i guess it was a policer...) 6 NAT most of the NAT was preconfigured, but both called NAT pools where missing - added both pools 7 Frame-Relay map-class frame-relay end-to-end was different on both routers, bidirectional & passive-reply - changed passive-reply to bidirectional - changed lmi-type to cisco on fr switch (not sure anymore) 8 MST switchport towards R10 was configured as dot1q trunk allowing VLAN 114 - deleted trunk config, changed port to access-port allowing VLAN 114 9 BGP on R1 or R2 there was a local policy calling an acl (permit tcp any any eq bgp, permit tcp any eq bgp any) setting next-hop interface null0 or some other interface, preventing bgp neighborship - changed both permits in acl to deny R3 had weight command >> removed weight command 10 IPv6 ospfv3 router-id mismatch R4 - changed router-id to 10.1.1.4 # K8 (was like discussed here except for some issues I was not aware of, but which maybe already discussed here as well). - Full reachability IPV4: I was not sure if the BB1 & BB2 networks have to be reachable. The question asks for full reachabillity of the IGP networks (don´t remember 100% wording). According to the proctor, internal/IGP prefixes have to be reachable. So conclusion was, the BB networks are not internal and therefore have not to be reachable. - Full reachability IPV6: IPV6 adresses were configured f.e. on the link R5-R3. The question asks for full reachabillity among all IPV6 speakers. The key word is speakers. Therefore I excluded them from reachabillity. - EIGRPv6: The question asks for applying the IPV4 Lo0 as Router-ID. I configured that, but it did not show up in the running config. - NTP task: ntp server command was only possible with VRF, not in global routing table. Besides ntp master 1/ntp source lo0/ntp update calendar I configured ntp broadcast on R1 serial link to R5 and R5 serial link to R3, as well as ntp broadcast client on R5 serial link to R1 and on R3 serial link to R5. Only worried about that the peers with this config do not really source ntp from loopback0 as requested right? So not sure if this is a solution. Now back to work, brain off, pasting templates.....
  11. I removed all MPLS QoS configs from R2/R3 , there is no service-policy on fa0/1 or serial. I did not expect to see a tos 160 counter increasing on the other site when doing a ping, but I could clearly see that it increased, TOS 160 was transmittedd successfully!! I am confused, questions is what is the MPLS QoS config good for if it works without? Rack19Sw2#sh access-l Extended IP access list 100 1 permit ip any any precedence routine 10 permit ip any any precedence priority 20 permit ip any any precedence immediate 30 permit ip any any precedence flash 40 permit ip any any precedence flash-override (126 matches) 50 permit ip any any precedence critical (111 matches) 60 permit ip any any precedence internet (124 matches) 70 permit ip any any precedence network
  12. Hi Guys, Am searching for TS study partner. I have already completed all those once. Now going through again. Let me know anybody is interested. Specially who is serious and planing for Feb or March. I will share the study plan via PM.
  13. EDIT: apparently I've missed ip cef on R6/R7 and this generated the issue. I don't have the problem anymore. I'm experiencing this issue on TSv5-301 MPLS ticket (ios 15.2.3) It looks a bug but please let me know If I've forgot something: I start with a blank configuration and I fix this: - on R8 md5 authentication to R6 - I enable mpls ip on all interfaces for R2 at this time from R8 I can ping R9 and R10 with source loo 0 and same the opposite Now I should fix the ldp neighborship with R8->R6/R7->R2 R6 and R7 use ldp autoconfig in OSPF but with wrong area. I change everything to area 0 (mpls ldp autoconfig area 0 (or 0.0.0.0)) and I got neighborship with R2, R8, R4, etc. At this time I lose ping form R8 to R9/R10 and vice versa. In routing table I see everything and path is fine, but I don't ping anymore. I've tried a reload of everything but problem is still there. Then I've removed mpls autoconfig from OSPF on R6/R7. Ping start to work again. then I enable mpls on each interface on R6/R7 (I got back ldp neighbours) and ping still work. Save+reload and I lose pings (100% lost). I disable the mpls again on R6/R7 and everything is back up (but ldp neighbours of course). I'm using latest UD iou (v 21 with ios 15.2.3). Someone else experienced this issue? Thanks
  14. Here again with always this nice topic. I've already discussed about this with other guys here but still cannot have a working solution with solutions provided. Last discussion I've was with sorri where he showed me up his K8 on real gear with provided solution and working (matching qos-group 467 and class CRITICAL). So I've seen it working.. no magic behind it. but he said same solution works 100% in his IOU, and it doesn't on mine GRRRR.. so I need help.. I've already just discussed this here: [Hidden Content] post #54 the only way I can make it work ping vrf SITE1 72.72.72.72 source l 71 and matching on the other side (R2) egress policy CRITICAL and CE-side QOSGROUP 467 is this: on both R2/R3: conf t class-map match-any QOSGROUP123 no match qos-group 123 match qos-group 1 match qos-group 2 match qos-group 3 class-map match-any QOSGROUP467 no match qos-group 467 match qos-group 4 match qos-group 6 match qos-group 7 end i this way I match what asked (CRITICAL on egress on the other side from ping) am I the only one that need this???? thanks for helping
  15. This is the Netbsd 5.1.2 for qemu sparc ready to run on just 127mb, one thing, they not have the iou unix images and scripts, you need to find it by your self, the runiou.sh (it makes no necesary the webiou at all) is on the image too and all dependency's are resolved including the key's just put the iou unix images and scripts and make it run, recommended qemu 0.14 that's what i use: [hide][Hidden Content]] if you guys have any issue with the image or needs something else for make it run just let me know but don't ask me about the iou's or any crack file User : root Pass : cisco Enjoy!
  16. hi MPLS Fundamentals [hide][Hidden Content]]
  17. Hi Guys, Please help me out , I have my lab in the next month ,please provide me the links for latest TS and K labs. As far as I know following are the TS and K labs currently active. TS: MPLS v1 MPLS v2 MPLS v3 MSDP v1 MSDP v2 TS5_v1 ( Renamed 503) TS5v2( Renamed 504) K Labs: K6 K6++ K7 K8
  18. Friends - I am struggling with MPLS and L3VPN in IOU and need some help on what to look at next. I check my configs and it matches with solution as far as I can see. Need help spotting any issue or troubleshooting. Pings from Site1 to Site2 and vice versa fail. Below is traceroute results and other findings: Traceroute from SITE1 TO SITE2 fails on the first hop (R3) Rack8SW2#traceroute vrf SITE1 Protocol [ip]: Target IP address: 72.72.72.72 Source address: 71.71.71.71 Numeric display [n]: Resolve AS number in (G)lobal table, (V)RF or(N)one [G]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to 72.72.72.72 VRF info: (vrf in name/id, vrf out name/id) 1 172.16.37.3 8 msec 4 msec 4 msec 2 * * * 3 * * * Traceroute from SITE2 TO SITE1 fails on the first hop (R2) Rack8SW2#traceroute vrf SITE2 Protocol [ip]: Target IP address: 71.71.71.71 Source address: 72.72.72.72 Numeric display [n]: Resolve AS number in (G)lobal table, (V)RF or(N)one [G]: Timeout in seconds [3]: Probe count [3]: Minimum Time to Live [1]: Maximum Time to Live [30]: Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to 71.71.71.71 VRF info: (vrf in name/id, vrf out name/id) 1 172.16.27.2 12 msec 4 msec 0 msec 2 * * * 3 * MPLS is established on R5 and it is receiving the routes via vpnv4 Rack8R5#sh tcp br TCB Local Address Foreign Address (state) B2F99620 18.5.5.5.31433 18.3.3.3.646 ESTAB B2FCF2B0 18.5.5.5.28098 18.4.4.4.646 ESTAB B2F96650 18.5.5.5.179 18.2.2.2.29778 ESTAB B2F97630 18.5.5.5.179 18.1.1.1.14071 ESTAB B2F98788 150.2.8.1.58775 150.2.8.254.179 ESTAB B2FC7218 18.5.5.5.179 18.3.3.3.54376 ESTAB B0D08020 18.5.5.5.23605 18.1.1.1.646 ESTAB Rack8R5#sh ip bgp vpnv4 all BGP table version is 3, local router ID is 18.5.5.5 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter, x best-external, a additional-path, c RIB-compressed, Origin codes: i - IGP, e - EGP, ? - incomplete RPKI validation codes: V valid, I invalid, N Not found Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 2:2 *>i 72.72.72.72/32 18.2.2.2 0 100 0 777 i Route Distinguisher: 3:3 *>i 71.71.71.71/32 18.3.3.3 0 100 0 777 i **R2 and R3 are configured as route reflector client and are both receiving the routes**: Rack8R2#sh ip route vrf SITE2 Routing Table: SITE2 Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP + - replicated route, % - next hop override Gateway of last resort is not set 71.0.0.0/32 is subnetted, 1 subnets B 71.71.71.71 [200/0] via 18.3.3.3, 00:13:56 72.0.0.0/32 is subnetted, 1 subnets B 72.72.72.72 [20/0] via 172.16.27.7, 00:14:08 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks C 172.16.27.0/24 is directly connected, Ethernet0/1 L 172.16.27.2/32 is directly connected, Ethernet0/1 R3 has the route to SITE2 (72.72.72.72) Rack8R3#sh ip route vrf SITE1 Routing Table: SITE1 Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP + - replicated route, % - next hop override Gateway of last resort is not set 71.0.0.0/32 is subnetted, 1 subnets B 71.71.71.71 [20/0] via 172.16.37.7, 00:14:59 72.0.0.0/32 is subnetted, 1 subnets B 72.72.72.72 [200/0] via 18.2.2.2, 00:14:53 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks C 172.16.37.0/24 is directly connected, Ethernet0/1 L 172.16.37.3/32 is directly connected, Ethernet0/1 Any help on this one would be greatly appreciated because i don't know where to go from here. Many thanks.
  19. Team, I have interface configured with MPLS IP and it has both IPV4 & V6 address. Running OSPF for both IPV4 and IPv6 and learning the routes via OSPF. However, under show mpls forwarding table, I see only label bindings for only for IPV4 routes. I dont see any labels for IPV6 routes. AM i missing something?
  20. Hi all, Great thanks to this forum and especially UldisD, CJ, RIKITEE, Paulno1, Netizen. Some feedback abt TS and Lab I got MPLS & K6. K6 was same as shared in this forum No new faults in MPLS. MPLS Tickets(All Tickets solved) 1. Frame-Relay : R22 Missing frame-relay class EEk under serial interface(facing R23). 2. NAT : Wrong NAT statement (outside, changed it to inside) 3. MST : SW1 vlan assignment to R10 is not there.(No restriction) 4. QOS : Wrong Class-map (Cannot modify Access-list on R7/8/9) 5. OSPF : R27 Loopback 0 advertised into area 0 R21 Area range for R26 Loopback not-advertise (remove it) 6. DHCP : UDP traffic is drop by control plane policy.(change conform-action to transmit) 7. EEM : Did not check for fault i just recreated it and worked perfectly 8. BGP : R2 has Control plane policy which is blocking every protocol, just changed it to transmit R3 weight 1 is configured for R1 (Removed It) 9. IPv6 : R5 didn`t have IPv6 Routing Process (Created and advertised interface in it.) 10. MPLS : R1/2 MPLS ldp neighborship to R4 was down cause of access-list, permit particular statement. R5 Wrong route-target configured (change it to same as R4) Regarding k6 nothing new, though some notes 1. All device has logging console informational/All line has password configured. 2. R4 f0/1 has IP but no vlan Assigned 3. you need to find out ip of Backbone for EBGP peering (in my case i got 51 and 46) 4. i used notepad for config throughout the lab 5. for IPv6 there is four five interface missing ipv6 address and on switch you need to configure sdm and reload 6. checked twice for verification and reachability checked by tcl script. Once again thank you guys for all your help and support !!!
  21. hello fellas, Can some one tell me more about this issue whats the probelem one side set to passive other bidir etc ? also is the link status down ? thanks Dave
×
×
  • Create New...