Bundle-ether ASR9K to WS3750X

Hello!
I'm having trouble setting up port-channel between cisco ASR9K and stack of WS-C3750X-48T-S.
It seems to be configured correctly, but interfaces are down. Any ideas?
Here is my config:
ASR9K:
Cisco IOS XR Software, Version 4.2.1[Default]
interface Bundle-Ether4
description IN4 LAG
bundle minimum-active links 1
interface Bundle-Ether4.250
vrf AAAA
ipv4 address A.B.C.D 255.255.255.224
encapsulation dot1q 250
interface Bundle-Ether4.251
vrf AAAA
ipv4 address A.B.C.D 255.255.255.224
encapsulation dot1q 251
interface Bundle-Ether4.256
vrf BBBB
ipv4 address A.B.C.D 255.255.255.248
encapsulation dot1q 256
interface Bundle-Ether4.260
vrf AAAA
ipv4 address A.B.C.D 255.255.255.192
encapsulation dot1q 260
interface Bundle-Ether4.261
vrf AAAA
ipv4 address A.B.C.D 255.255.255.224
encapsulation dot1q 261
interface Bundle-Ether4.262
vrf AAAA
ipv4 address A.B.C.D 255.255.255.224
encapsulation dot1q 262
Physical interfaces:
interface GigabitEthernet0/2/0/12
bundle id 4 mode active
negotiation auto
interface GigabitEthernet0/4/0/12
bundle id 4 mode active
negotiation auto
======
Cisco WS-C3750X-48T-S stack:
IOS WS-C3750X-48 12.2(55)SE3 C3750E-UNIVERSALK9-M
interface GigabitEthernet1/1/4
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 250,251,256,260-262
switchport mode trunk
switchport nonegotiate
channel-group 6 mode on
interface GigabitEthernet2/1/4
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 250,251,256,260-262
switchport mode trunk
switchport nonegotiate
channel-group 6 mode on
interface Port-channel6
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 250,251,256,260-262
switchport mode trunk
switchport nonegotiate
Thanks in advance

Hello,
I got it working! Problem was faulty SFP on 3750 switches. Changed SFP's and config to:
ASR9K:
Gi0/2/0/12
bundle id 4 mode active
Gi0/4/0/12
bundle id 4 mode active
3750X
Gi1/1/4
channel-group 6 mode active
Gi2/1/4
channel-group 6 mode active
Thanks for your help,
Rudolfs

Similar Messages

Bundle-Ether between MSC card and FP140 card on CRS-3

Hi,
Currently we have implemented a Bundle-Ether between 3 interfaces in MSC Card (8x10GE) and now we are planning replace one MCS Card by one FP-140 Card (14x10GE), so I would like to know if there is any risk or any incompatibility to form Bundle-Ether with 2 interfaces of MSC card and one interface of FP-140 Card.
Regards,
Jaime Soto.

Hi Jaime,
as far as i know there is no issue with splitting the bundle between MCS and FP-140 cards.
wbr
/vadim

Traffic exceeding the policy limit on ASR9K Bundle-Ether

Hi,
I have a problem regarding an issue on ASR 9000 bundle interface.
I apply 20mbps input and output policy to the interface to limit our customers traffic but sometimes I see 40mbps of customer traffic. It doesn't happens always but it occurs on different customers on different bundle interface.
What would be the possible reason? Thanks in advance.
note: we have different burst values on other ASR9 devices such as:
police rate 20000000 bps burst 3750000 bytes
police rate 20000000 bps burst 3200000 bytes
police rate 20000000 bps burst 3000000 bytes
police rate 20000000 bps burst 2500000 bytes
but not sure if indeed this is the problem,
Configurations:
policy-map 20mbps
class class-default
police rate 20000000 bps burst 3200000 bytes
   conform-action transmit
   exceed-action drop
interface Bundle-Ether1
mtu 9216
load-interval 30
interface Bundle-Ether1.100
service-policy input 20mbps
service-policy output 20mbps
ipv4 address 10.10.10.1
encapsulation dot1q 100
interface GigabitEthernet0/0/0/1
bundle id 1 mode active
interface GigabitEthernet0/0/0/2
bundle id 1 mode active
when i send traffic of 40mb to the customer:
ASR9#sh int Bundle-Ether1.100
Bundle-Ether1.100 is up, line protocol is up
30 second input rate 11361000 bits/sec, 6642 packets/sec
30 second output rate 40558000 bits/sec, 6877 packets/sec

Hi Rivalino,
Here is the output, the thing is this time even if I've sent 40m, peak is 26m.
Bundle-Ether1.100
30 second input rate 4291000 bits/sec, 886 packets/sec
30 second output rate 24492000 bits/sec, 2574 packets/sec
     3763694312 packets input, 1626561697099 bytes, 108538 total input drops
     3365349 drops for unrecognized upper-level protocol
     Received 38 broadcast packets, 3365349 multicast packets
     4012226890 packets output, 3050913586640 bytes, 42481432 total output drops
     Output 123 broadcast packets, 0 multicast packets
ASR9#show policy-map interface Bundle-Ether1.100 output
Wed Jan 22 08:06:41.049 Turkiye
Bundle-Ether1.100 output: 20mb
Class class-default
Classification statistics          (packets/bytes)     (rate - kbps)
    Matched             :           413918382/342268391637         42461
    Transmitted         :           N/A
    Total Dropped       :             5387815/7327884962           17684
Policing statistics                (packets/bytes)     (rate - kbps)
    Policed(conform)    :           408530567/334940506675         24777
    Policed(exceed)     :             5387815/7327884962           17684
    Policed(violate)    :                   0/0                    0
    Policed and dropped :             5387815/7327884962

ASR9K bundle-ether question

hi guys,I have a question need confirm,could some friends help me.
the topology is like this
1 .does this portchannel support or not ,I mean ASR9001 side is router subinterface,C4500X side is SW trunk interface
2.if this portchannel is support,could i use lacp mode active ?(the old cisco router is not support lacp mode active like this case,only can use on mode)
Thank you very much.

Yup this is very much supported and I would recommend to use the option of running lacp for member management.
mode-on means that all members are hard inserted in the bundle with no state control. mode active means that you are running lacp and negotiate with the peer the member state and inclusion in the bundle.
on the a9k side you need to define EFP's or subinterfaces in order to peel out the different vlan's for either use as a routed interface or for insertion into a bridgedomain or xconnect.
regards
xander

Limit on ICL per NP per satellite when using bundled ICLs

Hi supportforum,
(IOS XR Configuration 4.2.3)
configuring an ICL with Bundle-Ether for nv satellite I received the following log message:
LC/0/0/CPU0:Feb 10 04:48:01.671 : ifo_ea[201]: %PLATFORM-PLAT_ICPE_EA-3-ICL_PROVISIONING_ERROR : Nv satellite interface provisioning on Interchassis Link(ifhandle 0x8002360) failed. Limit is 1 ICL per NP per satellite when using bundled ICLs for that satellite. A different satellite can still have a member link on the same NP
I can't find any documentation about restrictions or limits for NP configuring ICL bundle-eth.
Are there, in fact, any limitations about NP?
Tanks

This restriction was lifted in 4.3.1
Thanks,
Sam

%ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21

hi,
why this log message keep appearing??
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#RP/0/RSP0/CPU0:Oct 8 14:50:37.023 : isis[1001]: %ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21 will not be used
RP/0/RSP0/CPU0:9010-2#
On both side hello padding is disable for level 2.
interface Bundle-Ether22
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2
regards
tahir

Router 1 config outup:
RP/0/RSP0/CPU0:9010-1#sh run int bundle-ether 12
Tue Oct 9 14:26:10.591 KSA
interface Bundle-Ether12
description "EtherChannel to 9010-2"
mtu 9216
service-policy output EGRESS-NNI
ipv4 address 10.0.1.30 255.255.255.252
ipv4 unreachables disable
bundle minimum-active links 1
bundle minimum-active bandwidth 10000000
load-interval 30
dampening
RP/0/RSP0/CPU0:9010-1#show isis interface bundle-ether12
Tue Oct 9 14:25:56.600 KSA
Bundle-Ether12              Enabled
Adjacency Formation:      Enabled
Prefix Advertisement:     Enabled
BFD:                      Disabled
BFD Min Interval:         150
BFD Multiplier:           3
Circuit Type:             level-2-only
Media Type:               P2P
Circuit Number:           0
Extended Circuit Number: 134218016
Next P2P IIH in:          9 s
LSP Rexmit Queue Size:    0
Level-2
    Adjacency Count:        1
    LSP Pacing Interval:    33 ms
    PSNP Entry Queue Size: 0
CLNS I/O
    Protocol State:         Up
    MTU:                    9199
    SNPA:                   b414.89e0.9f99
    Layer-2 MCast Groups Membership:
      All ISs:              Yes
IPv4 Unicast Topology:    Enabled
    Adjacency Formation:    Running
    Prefix Advertisement:   Running
    Metric (L1/L2):         10/10
    MPLS LDP Sync (L1/L2): Disabled/Enabled
      Sync Status:          Achieved
IPv4 Address Family:      Enabled
    Protocol State:         Up
    Forwarding Address(es): 10.0.1.30
    Global Prefix(es):      10.0.1.28/30
LSP transmit timer expires in 0 ms
LSP transmission is idle
Can send up to 9 back-to-back LSPs in the next 0 ms
RP/0/RSP0/CPU0:9010-1#
RP/0/RSP0/CPU0:9010-1#
RP/0/RSP0/CPU0:9010-1#sh run router isis
Tue Oct 9 14:26:41.010 KSA
router isis core
net 49.0001.0100.0000.0003.00
nsf cisco
lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
lsp-refresh-interval 65000 level 2
max-lsp-lifetime 65535 level 2
address-family ipv4 unicast
metric-style wide
spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
redistribute static route-policy STATIC-TO-ISIS
redistribute ospf 100 route-policy RP-FROM-OSPF-TO-ISIS
interface Bundle-Ether12
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2
Router 2 output config:
RP/0/RSP0/CPU0:9010-2#sh run int bundle-ether 21
Tue Oct 9 14:24:11.346 KSA
interface Bundle-Ether21
description "EtherChannel to 9010-1
mtu 9216
service-policy output EGRESS-NNI
ipv4 address 10.0.1.29 255.255.255.252
bundle minimum-active links 1
bundle minimum-active bandwidth 10000000
dampening
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#show isis interface bundle-ether21
Tue Oct 9 14:23:48.457 KSA
Bundle-Ether21              Enabled
Adjacency Formation:      Enabled
Prefix Advertisement:     Enabled
BFD:                      Disabled
BFD Min Interval:         150
BFD Multiplier:           3
Circuit Type:             level-2-only
Media Type:               P2P
Circuit Number:           0
Extended Circuit Number: 134218208
Next P2P IIH in:          6 s
LSP Rexmit Queue Size:    0
Level-2
    Adjacency Count:        1
    LSP Pacing Interval:    33 ms
    PSNP Entry Queue Size: 0
CLNS I/O
    Protocol State:         Up
    MTU:                    9199
    SNPA:                   0026.980e.d3e2
    Layer-2 MCast Groups Membership:
      All ISs:              Yes
IPv4 Unicast Topology:    Enabled
    Adjacency Formation:    Running
    Prefix Advertisement:   Running
    Metric (L1/L2):         10/10
    MPLS LDP Sync (L1/L2): Disabled/Enabled
      Sync Status:          Achieved
IPv4 Address Family:      Enabled
    Protocol State:         Up
    Forwarding Address(es): 10.0.1.29
    Global Prefix(es):      10.0.1.28/30
LSP transmit timer expires in 0 ms
LSP transmission is idle
Can send up to 9 back-to-back LSPs in the next 0 ms
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#sh run router isis
Tue Oct 9 14:24:41.457 KSA
router isis core
net 49.0001.0100.0000.0002.00
nsf cisco
log adjacency changes
lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
lsp-refresh-interval 65000 level 2
max-lsp-lifetime 65535 level 2
address-family ipv4 unicast
metric-style wide
spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
interface Bundle-Ether21
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2

Native VLAN on ASR9K with XR 4.2.3

Is there a way to configure a native VLAN on an ASR with XR 4.2.3?
We found documentation indicating it can be accomplished but receive a commit failure. The console output is below.
RP/0/RSP0/CPU0:3901-ASR (config)# int Te0/0/0/10.144
RP/0/RSP0/CPU0:3901-ASR(config-subif)#encapsulation untagged
RP/0/RSP0/CPU0:3901-ASR(config-subif)#commit
Thu Jan 30 05:57:00.129 CST
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors
RP/0/RSP0/CPU0:3901-ASR(config-subif)#
RP/0/RSP0/CPU0:3901-ASR(config-subif)#show configuration failed
Thu Jan 30 05:58:02.583 CST
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface TenGigE0/0/0/11.144 l2transport
encapsulation untagged
!!% 'Ethernet Infra' detected the 'warning' condition 'Cannot pop more tags than are matched on ingress'
end
RP/0/RSP0/CPU0:3901-ASR (config)# int Te0/0/0/10.144
RP/0/RSP0/CPU0:3901-ASR(config-subif)#encapsulation dot1q 144 , untagged
RP/0/RSP0/CPU0:3901-ASR(config-subif)#commit
Thu Jan 30 06:02:17.728 CST
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors
RP/0/RSP0/CPU0:3901-ASR(config-subif)#show configuration failed
Thu Jan 30 06:02:22.489 CST
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface TenGigE0/0/0/11.144 l2transport
encapsulation dot1q 144 , untagged
!!% 'Ethernet Infra' detected the 'warning' condition 'Cannot pop more tags than are matched on ingress'
end
Please let me know if you need our full configuration or any other information.
Thanks!

Hello,
Looks like you still have 'rewrite ingress tag pop' configuration under that interface. Remove that config also in your changes.
Example of what i did in my lab:
RP/0/RSP0/CPU0:ASR9010-B(config)#interface Bundle-Ether11.285 l2transport
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#encapsulation untagged
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#commit
Thu Jan 30 16:33:22.544 EST
% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed' from this session to view the errors
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#show configuration failed
Thu Jan 30 16:33:26.533 EST
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.
interface Bundle-Ether11.285 l2transport
encapsulation untagged
!!% 'Ethernet Infra' detected the 'warning' condition 'Cannot pop more tags than are matched on ingress'
end
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:no
RP/0/RSP0/CPU0:ASR9010-B#show run int bundle-ether 11.285
Thu Jan 30 16:33:38.296 EST
interface Bundle-Ether11.285 l2transport
description TEST
encapsulation dot1q 285
rewrite ingress tag pop 1 symmetric
RP/0/RSP0/CPU0:ASR9010-B#conf
Thu Jan 30 16:33:47.077 EST
RP/0/RSP0/CPU0:ASR9010-B(config)#interface bundle-ether 11.285 l2transport
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#no rewrite ingress tag pop 1 symmetric
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#encapsulation untagged
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#commit
Thu Jan 30 16:34:23.228 EST
RP/0/RSP0/CPU0:ASR9010-B(config-subif)#
thanks,
rivalino

10G wan etherchannel bundling between 12410 routers or between CRS-1 router

How etherchannel/bundle ether will behave on the N*10G wan links between the 12410 routers and when running between the 12410 and CRS-1 routers and also when running between 2 CRS-1 routers ??
How it is advantageous compared to the normal CEF based load balancing on these above routers without etherchannel or bundle ether configured on them.
Any suggestions on this ??

Hello Rajesh,
we are speaking of high end routers that are expected to process tens of thousands of flows per second even just differentiating on source and destination ip addresses there should be enough variety in your traffic to use the parallel CEF links in a fair way.
CEF uses an EXOR of ip source and ip destination and an hash seed that changes only when the system is reloaded.
etherchannel can use EXOR of different fields:
MAC SA exor MAC DA
IP SA exor IP DA
L4 SA port exor L4 DA port
but only one of them applies to a type of traffic at a specific time.
Or you expect a few very high volume flows on the links (DR or DB synchronization just to say)
So to answer your question, unless used for connecting two data centers, I don't expect to gain in fairness by using a bundle.
Hope to help
Giuseppe

ISM with NAT44 - Need help with configuration

Hello everyone,
I'm trying to set up NAT44 in the following scenario below and I'm having a hard time figuring out how to redirect the traffic. As you can see the big problem is that I have one single interface that connects to the internal network (10.0.0.0/8) and also to the tunnel destinations all in the same VRF. Can you guys give me a hand? The trafiic comes from network network 10.0.0.0/8 enters interface bundle-ether 2 (Now it needs to be translated), once it is translated, now it needs to reach the destination known via GRE tunnel.
Configurations
vrf NAT_IN
address-family ipv4 unicast
vrf BLUE
address-family ipv4 unicast
hw-module service cgn location 0/3/CPU0
interface Bundle-Ether2
description UPLINK TO METRO ETHERNET
interface Bundle-Ether2.2 l2transport
encapsulation dot1q 2
rewrite ingress tag pop 1 symmetric
interface GigabitEthernet200/0/0/43
description LINK TO METRO ETHERNET
bundle id 2 mode active
interface GigabitEthernet300/0/0/43
description LINK TO METRO ETHERNET
bundle id 2 mode active
interface BVI2
description METRO
vrf BLUE
ipv4 address 100.0.0.10/24
interface tunnel-ip 101
description GRE_TUNNEL
vrf BLUE
ipv4 address 1.1.1.1/32
tunnel mode gre ipv4
tunnel source interface bvi 2
tunnel destination 200.0.0.1
interface BVI 100
vrf BLUE
ipv4 address [GATEWAY_100] [MASK_100]
interface BVI 200
vrf BLUE
ipv4 address [GATEWAY_200] [MASK_200]
interface BVI 300
vrf BLUE
ipv4 address [GATEWAY_300] [MASK_300]
interface ServiceApp1
vrf NAT_IN
ipv4 address 10.0.2.1 255.255.255.252
service cgn CGN service-type nat44
interface ServiceApp2
vrf BLUE
ipv4 address 10.0.2.2 255.255.255.252
service cgn CGN service-type nat44
interface ServiceInfra1
ipv4 address 10.0.3.1 255.255.255.0
service-location 0/3/CPU0
router static
address-family ipv4 unicast
vrf NAT_IN
address-family ipv4 unicast
0.0.0.0/0 ServiceApp1
10.0.0.0/8 vrf BLUE bvI 2 <NEXT HOP>
vrf BLUE
address-family ipv4 unicast
172.16.0.0/24 ServiceApp2
router ospf METRO
vrf BLUE
router-id [ROUTER_ID]
redistribute bgp 65500 metric 100
area 0
interface bvi 2
router ospf BLUE
vrf BLUE
router-id [ROUTER ID]
redistribute bgp 65500 metric 100
area 10
interface BVI100
interface BVI200
interface BVI200
router bgp 65500
address-family ipv4 unicast
address-family vpnv4 unicast
vrf BLUE
rd 65500:2
address-family ipv4 unicast
redistribute static
redistribute ospf BLUE
neighbor 1.1.1.2
remote-as 64512
ebgp-multihop 5
address-family ipv4 unicast
route-policy PASS in
route-policy PASS out
service cgn CGN
service-location preferred-active 0/3/CPU0
service-type nat44 nat44
portlimit 20000
inside-vrf NAT_IN
map outside-vrf BLUE address-pool 172.16.0.0/24
Thanks in advance,
Renato

Hi Somnath,
Let's see if you can help with this new scenario. I want to extend this NAT configuration to a new site (BO1), but instead of using this entire setup with ASR9K, etc, I just want to use ASR9000v module and have this AS9K + ISM as the host. The first problem I see in this scenario is that I have the same 10.0.0.0/8 network in both sites, network which will access the same resources as the devices in the 10.0.0.0/8 in the main site.
1) Do you think if I create a new inside VRF [NAT_IN1] would address this issue?
2) Can I use the same outside VRF?
Here is the configurations.
!! IOS XR Configuration 4.3.1
vrf NAT_IN
address-family ipv4 unicast
import route-target
   65500:2
   65500:3
export route-target
   65500:3
vrf RED
address-family ipv4 unicast
import route-target
   65500:1
export route-target
   65500:1
vrf NAT_OUT
address-family ipv4 unicast
import route-target
   65500:4
export route-target
   65500:4
vrf SATELLITE
vrf BLUE
address-family ipv4 unicast
import route-target
   65500:2
export route-target
   65500:2
hw-module service cgn location 0/3/CPU0
ipv4 access-list ABF
5 permit ospf any any
10 permit ipv4 any 10.200.0.0 0.0.255.255 nexthop1 vrf NAT_IN ipv4 10.0.2.2
20 permit icmp any any
interface Bundle-Ether3
description Uplink (BE3 - VRF NAT_IN) - VLAN 20
vrf NAT_IN
ipv4 address 1.1.1.1 255.255.255.0
ipv4 access-group ABF ingress
interface Bundle-Ether22
description LOOPBACK CABLE NAT_OUT
vrf NAT_OUT
ipv4 address 10.0.1.1 255.255.255.0
interface Bundle-Ether23
description LOOPBACK CABLE BLUE
vrf BLUE
ipv4 address 10.0.1.2 255.255.255.0
interface 6
description Uplink (BE6 - Global) - VLAN 20,51,80-82
interface 6.2
ipv4 address 1.1.1.2 255.255.255.0
encapsulation dot1q 2
interface 6.51 l2transport
description EFP - BE6 - VLAN 51
encapsulation dot1q 51
rewrite ingress tag pop 1 symmetric
interface 6.80 l2transport
description EFP - BE6 - VLAN 80
encapsulation dot1q 80
rewrite ingress tag pop 1 symmetric
interface 6.81 l2transport
description EFP - BE6 - VLAN 81
encapsulation dot1q 81
rewrite ingress tag pop 1 symmetric
interface 6.82 l2transport
description EFP - BE6 - VLAN 82
encapsulation dot1q 82
rewrite ingress tag pop 1 symmetric
interface Bundle-Ether100
description Bundle to Satellite 100
vrf SATELLITE
ipv4 point-to-point
ipv4 unnumbered Loopback0
nv
satellite-fabric-link satellite 100
   remote-ports GigabitEthernet 0/0/0-43
interface Bundle-Ether200
description Bundle to Satellite 200
vrf SATELLITE
ipv4 point-to-point
ipv4 unnumbered Loopback0
nv
satellite-fabric-link satellite 200
   remote-ports GigabitEthernet 0/0/0-43
interface Bundle-Ether300
description Bundle to Satellite 300
vrf SATELLITE
ipv4 point-to-point
ipv4 unnumbered Loopback0
nv
satellite-fabric-link satellite 300
   remote-ports GigabitEthernet 0/0/0-35
interface Loopback0
description MGMT SATELLITE
vrf SATELLITE
ipv4 address 10.0.0.254 255.255.255.0
interface tunnel-ip31101
description BLUE-TUNNEL01
vrf BLUE
ipv4 address 10.200.253.90 255.255.255.252
tunnel mode gre ipv4
tunnel source 6.2
tunnel destination 13.13.13.13
interface tunnel-ip31102
description BLUE-TUNNEL02
vrf BLUE
ipv4 address 10.200.253.94 255.255.255.252
tunnel mode gre ipv4
tunnel source 6.2
tunnel destination 14.14.14.14
interface tunnel-ip31103
description RED-TUNNEL03
vrf RED
ipv4 address 10.200.253.90 255.255.255.252
tunnel mode gre ipv4
tunnel source 6.2
tunnel destination 13.13.13.13
interface tunnel-ip31104
description RED-TUNNEL04
vrf RED
ipv4 address 10.200.253.94 255.255.255.252
tunnel mode gre ipv4
tunnel source 6.2
tunnel destination 14.14.14.14
interface TenGigE0/0/0/0
description LINK TO SATELLITE 100
bundle id 100 mode on
interface TenGigE0/0/0/1
description LINK TO SATELLITE 100
bundle id 100 mode on
interface TenGigE0/0/0/2
description LINK TO SATELLITE 200
bundle id 200 mode on
interface TenGigE0/0/0/3
description LINK TO SATELLITE 200
bundle id 200 mode on
interface TenGigE0/0/0/4
description LINK TO SATELLITE 300
vrf SATELLITE
ipv4 point-to-point
ipv4 unnumbered Loopback0
nv
satellite-fabric-link satellite 300
   remote-ports GigabitEthernet 0/0/36-43
interface TenGigE0/0/0/5
description LINK TO SATELLITE 300
bundle id 300 mode on
interface TenGigE0/0/0/16
description UPLINK (BE6 - GLOBAL) - VLAN 20,51,80-82
bundle id 6 mode active
interface TenGigE0/1/0/16
description UPLINK (BE6 - GLOBAL) - VLAN 20,51,80-82
bundle id 6 mode active
interface TenGigE0/0/0/17
description UPLINK (BE3 - VRF NAT_IN) - VLAN 20
bundle id 3 mode active
interface TenGigE0/1/0/17
description UPLINK (BE3 - VRF NAT_IN) - VLAN 20
bundle id 3 mode active
interface TenGigE0/0/0/22
description LOOPBACK CABLE TE0/1/0/22
bundle id 22 mode on
interface TenGigE0/0/0/23
description LOOPBACK CABLE TE0/1/0/23
bundle id 22 mode on
interface TenGigE0/1/0/0
description LINK TO SATELLITE 100
bundle id 100 mode on
interface TenGigE0/1/0/1
description LINK TO SATELLITE 100
bundle id 100 mode on
interface TenGigE0/1/0/2
description LINK TO SATELLITE 200
bundle id 200 mode on
interface TenGigE0/1/0/3
description LINK TO SATELLITE 200
bundle id 200 mode on
interface TenGigE0/1/0/4
description LINK TO SATELLITE 300
bundle id 300 mode on
interface TenGigE0/1/0/5
description LINK TO SATELLITE 300
bundle id 300 mode on
interface TenGigE0/1/0/22
description LOOPBACK CABLE TE0/0/0/22
bundle id 23 mode on
interface TenGigE0/1/0/23
description LOOPBACK CABLE TE0/0/0/23
bundle id 23 mode on
interface BVI30
vrf RED
ipv4 address 10.200.25.193 255.255.255.192
interface BVI31
vrf BLUE
ipv4 address 10.200.1.1 255.255.255.248
interface BVI32
vrf BLUE
ipv4 address 10.200.25.129 255.255.255.224
interface BVI33
vrf BLUE
ipv4 address 10.200.25.1 255.255.255.128
interface BVI36
vrf BLUE
ipv4 address 10.200.237.145 255.255.255.240
interface BVI51
vrf RED
ipv4 address 192.168.7.12 255.255.255.0
interface BVI80
vrf RED
ipv4 address 10.200.26.169 255.255.255.224
interface BVI81
vrf BLUE
ipv4 address 10.200.25.164 255.255.255.240
interface BVI82
vrf BLUE
ipv4 address 10.200.25.180 255.255.255.240
interface ServiceApp1
description NAT_IN
vrf NAT_IN
ipv4 address 10.0.2.1 255.255.255.252
service cgn CGN service-type nat44
interface ServiceApp2
description NAT_OUT
vrf NAT_OUT
ipv4 address 10.0.2.5 255.255.255.252
service cgn CGN service-type nat44
interface ServiceInfra1
description ISM
ipv4 address 10.0.3.1 255.255.255.0
service-location 0/3/CPU0
prefix-set PS_ROUTES
10.200.0.8,
10.200.5.40/29,
10.200.1.0/29,
10.200.5.32/29,
10.200.0.144/28,
10.200.106.0/28,
10.200.106.16/28
end-set
prefix-set PS_BGP_BLUE_OUT
10.200.24.192/26,
10.200.5.40/29,
10.200.240.0/25,
10.200.1.0/29,
10.200.25.128/27,
10.200.25.0/25,
10.200.5.32/29,
10.200.26.0/25,
10.200.0.144/28,
10.200.27.128/27,
10.200.27.0/25,
10.200.106.0/28,
10.200.106.128/25,
10.200.106.16/28,
10.200.107.128/25
end-set
route-policy RP_DENY_ALL
drop
end-policy
route-policy RP_PASS_ALL
pass
end-policy
route-policy RP_BGP_BLUE_OUT
if destination in PS_BGP_BLUE_OUT then
    pass
endif
end-policy
route-policy RP_PASS_ROUTES
if destination in PS_ROUTES then
    pass
endif
end-policy
router static
address-family ipv4 unicast
0.0.0.0/0 1.1.1.20
vrf NAT_IN
address-family ipv4 unicast
   0.0.0.0/0 ServiceApp1
vrf RED
vrf NAT_OUT
address-family ipv4 unicast
   0.0.0.0/0 10.0.1.2
   10.200.24.192/26 ServiceApp2
vrf BLUE
address-family ipv4 unicast
   10.200.24.192/26 10.0.1.1
router ospf
log adjacency changes
vrf NAT_IN
router-id 1.1.1.1
disable-dn-bit-check
redistribute bgp 65500 metric 5 metric-type 2 route-policy RP_PASS_ROUTES
area 7
   interface Bundle-Ether3
router ospf RED
log adjacency changes
vrf RED
router-id 10.200.26.169
disable-dn-bit-check
redistribute bgp 65500 metric 10 metric-type 2
area 11
   interface BVI30
   interface BVI80
router ospf BLUE
log adjacency changes
vrf BLUE
router-id 10.200.25.164
disable-dn-bit-check
redistribute static
redistribute bgp 65500 metric 10 metric-type 2
area 0
   interface BVI81
   interface BVI82
area 2
   interface BVI31
   interface BVI32
   interface BVI33
   interface BVI36
router bgp 65500
address-family ipv4 unicast
address-family vpnv4 unicast
vrf NAT_IN
rd 65500:3
bgp router-id 1.1.1.1
address-family ipv4 unicast
   route-target download
vrf RED
rd 65500:1
bgp router-id 10.200.253.90
address-family ipv4 unicast
   network 10.200.25.192/26
   network 10.200.26.128/27
   network 10.200.26.192/27
   network 10.200.27.192/26
   network 10.200.104.128/27
   network 10.200.104.160/27
neighbor 10.200.253.89
   remote-as 64512
   ebgp-multihop 5
   update-source tunnel-ip31103
   address-family ipv4 unicast
    route-policy RP_PASS_ALL in
    route-policy RP_PASS_ALL out
    soft-reconfiguration inbound
neighbor 10.200.253.93
   remote-as 64512
   ebgp-multihop 5
   update-source tunnel-ip31104
   address-family ipv4 unicast
    route-policy RP_PASS_ALL in
    route-policy RP_PASS_ALL out
    soft-reconfiguration inbound
vrf BLUE
rd 65500:2
bgp router-id 10.200.253.90
address-family ipv4 unicast
   network 10.200.0.144/28
   network 10.200.1.0/29
   network 10.200.5.32/29
   network 10.200.5.40/29
   network 10.200.24.192/26
   network 10.200.25.0/25
   network 10.200.25.128/27
   network 10.200.26.0/25
   network 10.200.27.0/25
   network 10.200.27.128/27
   network 10.200.106.0/28
   network 10.200.106.16/28
   network 10.200.106.128/25
   network 10.200.107.128/25
   network 10.200.240.0/25
neighbor 10.200.253.89
   remote-as 64512
   ebgp-multihop 5
   update-source tunnel-ip31101
   address-family ipv4 unicast
    route-policy RP_PASS_ALL in
    route-policy RP_BGP_BLUE_OUT out
    soft-reconfiguration inbound
neighbor 10.200.253.93
   remote-as 64512
   ebgp-multihop 5
   update-source tunnel-ip31102
   address-family ipv4 unicast
    route-policy RP_PASS_ALL in
    route-policy RP_BGP_BLUE_OUT out
    soft-reconfiguration inbound
l2vpn
load-balancing flow src-dst-ip
bridge group VLAN30
bridge-domain VLAN30
   routed interface BVI30
bridge group VLAN31
bridge-domain VLAN31
   routed interface BVI31
bridge group VLAN32
bridge-domain VLAN32
   routed interface BVI32
bridge group VLAN33
bridge-domain VLAN33
   routed interface BVI33
bridge group VLAN36
bridge-domain VLAN36
   routed interface BVI36
bridge group VLAN51
bridge-domain VLAN51
   routed interface BVI51
bridge group VLAN80
bridge-domain VLAN80
   interface 6.80
   routed interface BVI80
bridge group VLAN81
bridge-domain VLAN81
   interface 6.81
   routed interface BVI81
bridge group VLAN82
bridge-domain VLAN82
   interface 6.82
   routed interface BVI82
nv
satellite 100
type asr9000v
ipv4 address 10.0.0.1
satellite 200
type asr9000v
ipv4 address 10.0.0.2
satellite 300
type asr9000v
ipv4 address 10.0.0.3
service cgn CGN
service-location preferred-active 0/3/CPU0
service-type nat44 nat44
portlimit 20000
inside-vrf NAT_IN
   map outside-vrf NAT_OUT address-pool 10.200.24.192/26
Thanks in advance,
Renato

Ask the Expert: ASR9000 Hardware Architecture

With Satya Narra and Xander Thuijs
Welcome to the Cisco Support Community. This is an opportunity to learn and ask questions about software installation, SMU installation, ASR9000 architecture, installing satellite (ASR9000 nv), and troubleshooting of the Cisco ASR 9000 Series Aggregation Services Routers with experts Satya Narra and Xander Thuijs.
The Cisco ASR 9000 Series Aggregation Services Routers product family offers a significant added value compared to the prior generations of carrier Ethernet routing offerings. The Cisco ASR 9000 Series is an operationally simple, future-optimized platform using next-generation hardware and software.
Satya Narra is a network consulting engineer and specialist in ASR9000 deployments for service provider networks. He is an expert in many technology areas, including IP routing, MPLS, BGP, OSPF, multicast, system architecture, and network design. Satya has a master of science degree in electrical engineering from Wichita State University, Wichita, KS. He started his career as a customer support engineer in TAC/HTTS supporting some of the biggest networks, including Comcast, Citi, Amazon, JPMorgan, AT&T, Vodofone, and others.
Xander Thuijs is a principal engineer for the Cisco ASR 9000 Series and Cisco IOS-XR product family at Cisco. He is an expert and advisor in many technology areas, including IP routing, WAN, WAN switching, MPLS, multicast, BNG, ISDN, VoIP, Carrier Ethernet, System Architecture, network design and many others. He has more than 20 years of industry experience in carrier Ethernet, carrier routing, and network access technologies. Xander holds a dual CCIE certification (number 6775) in service provider and voice technologies. He has a master of science degree in electrical engineering from Hogeschool van University in Amsterdam.
Remember to use the rating system to let Satya and Xander know if you have received an adequate response.
Satya might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation in Service Providers community, sub-community, XR OS and Platforms discussion forum shortly after the event. This event lasts through February 14, 2014. Visit this forum often to view responses to your questions and the questions of other community members.

Hi Lisa,
The mLACP switchover method can be modified using the following CLI:
RP/0/0/CPU0:IOSXR(config)#interface bundle-ether 1 mlacp switchover type ?
brute-force    Force switchover by disabling all local member links
revertive      Revert based on configured priority values
RP/0/0/CPU0:ios(config)#interface bundle-ether 1 mlacp switchover type
These options(and the default, when this configuration is not present) are mutually exclusive, and the configuration must match on the bundle on both POA's. They determine the dynamic priority manamgement or brute force mechanism is used, and whether the behaviour is revertive or non-revertive.
Dynamic Priority Management
Switchover is acheved gracefully by modifying the LACP port priorites.
Brute force
This does not involve any priority changes. When using brute force, the operational priority always matches the configured priority. A Switchover is performed when the bundle goes down on the active POA. A switchover is also performed, If active-minimum-links is not satisfied, it brings down other active links on this bundle to force a switchover completely to other PoA.
Revertive
You can configure the MC-LAG in Revertive switchover mode. It means, whenever higher priority links are available, it forces an automatic switchover to that PoA.
Non-revertive
By default switchover is non-revertive. It means, bundle does not fail back to the original active PoA except when a subsequent failure is encountered. In this mode, POA's do not consider to be primary and secondary, only active or standby. The configured priorities are only used to determine which POA is initally active.
Regards,
--SN

Applying group on interface 5.1.3

Hi
Just wondering why it's not possible to configure an apply-group directly on an interface in one row.
RP/0/RSP0/CPU0:9K(config)#interface bundle-ether 2000.3628 a
aaa address-family arp auto-ip-ring
RP/0/RSP0/CPU0:9K(config)#interface bundle-ether 2000.3628 ?
aaa AAA configuration
address-family AFI/SAFI configuration
arp Configure Address Resolution Protocol
auto-ip-ring Auto-IP-Ring interface configuration commands
Apply-group is missing here.....
I need to go to the interface level to be able to run apply-group
RP/0/RSP0/CPU0:9K(config)#interface bundle-ether 2000.3628
RP/0/RSP0/CPU0:9K(config-subif)#a
aaa address-family apply-group apply-group-append
apply-group-remove arp auto-ip-ring
RP/0/RSP0/CPU0:9K(config-subif)#a
RP/0/RSP0/CPU0:9K(config-subif)#?
aaa AAA configuration
address-family AFI/SAFI configuration
apply-group Apply configuration from a group
apply-group-append Append apply-group configuration from a group
apply-group-remove Remove a group from apply-group configuration
arp Configure Address Resolution Protocol
When looking at config in formal mode its seem like you should be able to configuring it in one row.
Is there a technical reason for this behavior or just a miss when writing the code?
/Peter

Peter,
That looks like a miss in the parser code for both int and sub-int, I'll open up a bug with that team to get it fixed.
Thanks,
Sam

Cannot get ip

this circuit cannot get ip , what happened?
RP/0/RSP0/CPU0:TYCK-601#show subscriber session filter access-interface bundle-ether 10102.1146 detail
Mon Aug 25 18:22:30.192 Taipei
Interface: None
Circuit ID: TYCK-601 bundle-ether 10102 vlan-id 1146
Remote ID: Unknown
Type: IP: DHCP-trigger
IPv4 State: Up Pending, Mon Aug 25 18:22:01 2014
Mac Address: 000c.2a04.de70
Account-Session Id: 002afc8e
Nas-Port: Unknown
User name: ........SD000022324-ITA-00@CHT_ANY_ITA1
Outer VLAN ID: 1146
Subscriber Label: 0x00000c81
Created: Mon Aug 25 18:22:01 2014
State: Connected
Authentication: unauthenticated
Authorization: authorized
Access-interface: Bundle-Ether10102.1146
Policy Executed:
policy-map type control subscriber radius-aaa2
event Session-Start match-first [at Mon Aug 25 18:22:01 2014]
class type control subscriber dhcp-initial do-until-failure [Succeeded]
10 authorize aaa list for-local-dhcp [Succeeded]
20 activate dynamic-template urpf [Succeeded]
Session Accounting: disabled
Last COA request received: unavailable
Pending Callbacks:
Waiting for internal processing to complete
RP/0/RSP0/CPU0:TYCK-601#
RP/0/RSP0/CPU0:TYCK-601# show dhcp ipv4 server binding
Mon Aug 25 18:12:25.190 Taipei
Lease
MAC Address IP Address State Remaining Interface VRF Sublabel
000c.2a04.de70 0.0.0.0 UNKNOWN 24 BE10102.1146 default 0x99b
RP/0/RSP0/CPU0:TYCK-601# show dhcp ipv4 server binding
Mon Aug 25 18:12:28.166 Taipei

I think we need to see the configuration and the debug of the dhcp and the subscriber policy execution to give an idea as to why the address allocation didnt occur.
For this type of troubleshooting a tac case is probably best to continue the process.
regards
xander

Netflow on CRS (MPLS problem)

Hi all,
I have configured netflow on CRS platfom, but it seems it doesn't capture/export any mpls information(traffic) on mpls enabled interfaces. My configuration is:
flow monitor-map xxxxxxx
record mpls ipv4-fields
exporter xxxxxxx
cache entries 10000
cache timeout active 30
cache timeout inactive 15
sampler-map xxxxxxx
random 1 out-of 1500
flow exporter-map xxxxxxx
version v9
options interface-table timeout 60
options sampler-table timeout 60
template timeout 60
template data timeout 60
template options timeout 60
transport udp 9950
source Loopback0
destination xxxxxxx
interface Bundle-Etherx.xx
description test
mtu 9200
ipv4 mtu 9000
ipv4 address x.x.x.x
ipv6 mtu 9000
ipv6 address x6.x6.x6.x6
flow ipv6 monitor x6monitor sampler x ingress
flow mpls monitor MPLSmonitor sampler x ingress
dot1q vlan x
This is show command for that interface:
RP/0/RP0/CPU0:CN-Srce-00-RO#show flow monitor MPLSmonitor cache match interface ingress eq bundle-ether 1.155 location 0/7/CPU0
Fri Aug 29 13:09:57.352 MET
Cache summary for Flow Monitor CN-NetFlow-MPLSmonitor:
Cache size:                          10000
Current entries:                         0
High Watermark:                       9500
Flows added:                       3335609
Flows not added:                         0
Ager Polls:                       27241668
- Active timeout                   65946
- Inactive timeout               3244005
- TCP FIN flag                     25658
- Watermark aged                       0
- Emergency aged                       0
- Counter wrap aged                    0
- Total                          3335609
Periodic export:
- Counter wrap                         0
- TCP FIN flag                         0
Flows exported                     3335609
Matching entries:                        0
I have also configured ipv4 and ipv6 monitor maps on few other interfaces and I can see netflow info of that type of traffic.
Tnx for your help.
Best regards,
RJ.

Hi Marcin,
Unfortunately, if you try to sample an MPLS+IPv4 packet and only send the IPv4 part in the records, it's not possible with IOS-XR,
Best Regards,
N.

Help with VLANs on ASR9001

Hi All,
I have read the exapmles on this forum of setting up vlans but must have missed something.
Im trying to setup Bundle ether 1 to connect to a 3750x on vlan 220, bundle ether 2 will goto a customer (not active yet)
Both the asr and 3750 are reporting port chanel active but i cannot ping end to end
here is my ASR currect (non production) config
lacp system mac e4c7.2243.689c
rp mgmtethernet forwarding
interface Bundle-Ether1
description 2x10GbE Bundle to SecurITon Core
mac-address e4c7.2243.689c
interface Bundle-Ether1.220 l2transport
description -220-
encapsulation dot1q 220
rewrite ingress tag pop 1 symmetric
interface Bundle-Ether2
description 220
bundle minimum-active links 1
l2transport
interface TenGigE0/0/2/0
bundle id 1 mode active
interface TenGigE0/0/2/1
nv
edge
   interface
transceiver permit pid all
interface TenGigE0/0/2/2
bundle id 2 mode active
interface TenGigE0/0/2/3
nv
edge
   interface
interface TenGigE1/0/2/0
bundle id 1 mode active
interface TenGigE1/0/2/1
nv
edge
   interface
transceiver permit pid all
interface TenGigE1/0/2/2
bundle id 2 mode active
interface TenGigE1/0/2/3
nv
edge
   interface
interface BVI220
ipv4 address 172.17.220.2 255.255.255.0
l2vpn
bridge group VLANs
bridge-domain vlan220
   interface Bundle-Ether2
   interface Bundle-Ether1.220
   routed interface BVI220
here is sh int br
               Intf       Intf        LineP              Encap MTU        BW
               Name       State       State               Type (byte)    (Kbps)
              BV220          up          up               ARPA 1514   10000000
                BE1          up          up               ARPA 1514   20000000
            BE1.220          up          up             802.1Q 1518   20000000
                BE2        down        down               ARPA 1514          0
                Nu0          up          up               Null 1500          0
    Mg0/RSP0/CPU0/0          up          up               ARPA 1514    1000000
    Mg0/RSP0/CPU0/1          up          up               ARPA 1514    1000000
          Te0/0/2/0          up          up               ARPA 1514   10000000
          Te0/0/2/1          up          up               ARPA 1514   10000000
          Te0/0/2/2        down        down               ARPA 1514   10000000
          Te0/0/2/3          up          up               ARPA 1514   10000000
    Mg1/RSP0/CPU0/0          up          up               ARPA 1514    1000000
    Mg1/RSP0/CPU0/1          up          up               ARPA 1514    1000000
          Te1/0/2/0          up          up               ARPA 1514   10000000
          Te1/0/2/1          up          up               ARPA 1514   10000000
          Te1/0/2/2        down        down               ARPA 1514   10000000
          Te1/0/2/3          up          up               ARPA 1514   10000000
here is the 3750 x config
vlan 220
name220
Interface vlan 220
description 220
ip address 172.17.220.10 255.255.255.0
interface TenGigabitEthernet1/1/2
description —ASR9001
switchport access vlan 220
switchport mode access
no cdp enable
no cdp tlv server-location
no cdp tlv app
spanning-tree portfast trunk
spanning-tree bpdufilter enable
channel-protocol lacp
channel-group 12 mode active
interface TenGigabitEthernet2/1/2
description —ASR9001
switchport access vlan 220
switchport mode access
no cdp enable
no cdp tlv server-location
no cdp tlv app
spanning-tree portfast trunk
spanning-tree bpdufilter enable
channel-protocol lacp
channel-group 12 mode active
interface Port-channel12
description --ASR9001
switchport access vlan 220
switchport mode access
spanning-tree portfast trunk
spanning-tree bpdufilter enable

Thank you

MPLS TRUNK CONFIGURATION on TWO EDGE

Hi
Actually we have a network operate VRF on two EDGE (ASR9000) the diagram is this:
we try to configurate a MPLS conection between ASR (PE-1) and ASR (PE-2) try to use MPLS LDP and use a VRF OAM between this devices but the comunication is not possible
MPLS LDP is the option? or L2VPN or EoMPLS for this connection?
the actually configuration is:
ASR-2
mpls ldp
router-id 172.16.14.1
discovery hello holdtime 30
discovery hello interval 10
graceful-restart
explicit-null
interface Bundle-Ether100
ASR-1
mpls ldp
router-id 172.16.14.2
discovery hello holdtime 30
discovery hello interval 10
graceful-restart
explicit-null
interface Bundle-Ether100
but the VRF OAM only configurated between PE-1 and PE-2 is not neighbord
We don´t know if we are using the correct concept to connect the devices, can help us
thanks
Best Regards

Harold, thanks for your comments
we are making change for your comments and the final diagrame is:
on ASR9K - PE-1 we have configurated VRF, IGP and Conectivity for BUNDLE-Ethe 100 conectivity
ASR9K (PE-1):
vrf OAM
address-family ipv4 unicast
import route-policy pass-all
import route-target
   64518:64518
export route-policy pass-all
export route-target
   64518:64518
interface Bundle-Ether100
ipv4 address 172.16.14.1 255.255.255.252
interface Loopback10
vrf OAM
ipv4 address 172.16.162.1 255.255.255.255
router ospf 100
router-id 172.16.14.1
mpls ldp sync
mpls ldp auto-config
area 0
interface Bundle-Ether100
mpls ldp
router-id 172.16.14.1
interface Bundle-Ether100
ASR9K (PE-2):
vrf OAM
address-family ipv4 unicast
import route-policy pass-all
import route-target
   64518:64518
export route-policy pass-all
export route-target
   64518:64518
interface Bundle-Ether100
ipv4 address 172.16.14.2 255.255.255.252
interface Loopback10
vrf OAM
ipv4 address 172.16.162.2 255.255.255.255
router ospf 100
router-id 172.16.14.2
mpls ldp sync
mpls ldp auto-config
area 0
interface Bundle-Ether100
mpls ldp
router-id 172.16.14.2
interface Bundle-Ether100
when we verifying the MPLS neighbor is UP
RP/0/RSP0/CPU0:ED_MEX_1#sho mpls ldp neighbor
Wed May 22 18:29:03.496 UTC
Peer LDP Identifier: 172.16.14.2:0
TCP connection: 172.16.14.2:39527 - 172.16.14.1:646
Graceful Restart: No
Session Holdtime: 180 sec
State: Oper; Msgs sent/rcvd: 25/25; Downstream-Unsolicited
Up time: 00:18:46
LDP Discovery Sources:
    Bundle-Ether100
Addresses bound to this peer:
    172.16.14.2
RP/0/RSP0/CPU0:ED_MEX_2#sho mpls ldp neighbor
Wed May 22 16:24:53.223 UTC
Peer LDP Identifier: 172.16.14.1:0
TCP connection: 172.16.14.1:646 - 172.16.14.2:39527
Graceful Restart: No
Session Holdtime: 180 sec
State: Oper; Msgs sent/rcvd: 26/26; Downstream-Unsolicited
Up time: 00:19:19
LDP Discovery Sources:
    Bundle-Ether100
Addresses bound to this peer:
    172.16.14.1
on OSPF 100 the neighbor is UP
RP/0/RSP0/CPU0:ED_MEX_2#sho ospf neighbor
Wed May 22 16:26:15.169 UTC
* Indicates MADJ interface
Neighbors for OSPF 100
Neighbor ID     Pri   State           Dead Time   Address         Interface
172.16.14.1     1     FULL/BDR        00:00:31    172.16.14.1   Bundle-Ether100
    Neighbor is up for 00:54:34
Total neighbor count: 1
RP/0/RSP0/CPU0:ED_MEX_1#sho ospf neighbor
Wed May 22 18:31:18.614 UTC
* Indicates MADJ interface
Neighbors for OSPF 100
Neighbor ID     Pri   State           Dead Time   Address         Interface
172.16.14.2     1     FULL/DR         00:00:36    172.16.14.2     Bundle-Ether100
    Neighbor is up for 00:54:59
Total neighbor count: 1
but when try to send a PING from Loopback 10 from ASR 1 to ASR 2 ocurre this one and viceverse
RP/0/RSP0/CPU0:ED_MEX_1#ping vrf OAM 172.16.162.1
Wed May 22 18:32:54.046 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.162.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
RP/0/RSP0/CPU0:ED_MEX_1#ping vrf OAM 172.16.162.2
Wed May 22 18:32:57.794 UTC
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.162.2, timeout is 2 seconds:
UUUUU
Success rate is 0 percent (0/5)
the routing table for OAM on ASR-1 is:
RP/0/RSP0/CPU0:ED_MEX_1#sho route vrf OAM
Wed May 22 18:33:59.485 UTC
Codes: C - connected, S - static, R - RIP, 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, E - EGP
       i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
       U - per-user static route, o - ODR, L - local, G - DAGR
       A - access/subscriber, - FRR Backup path
Gateway of last resort is not set
L    172.16.162.1/32 is directly connected, 00:34:13, Loopback10
for ASR-2
RP/0/RSP0/CPU0:ED_MEX_2#sho route vrf OAM
Wed May 22 16:30:23.400 UTC
Codes: C - connected, S - static, R - RIP, 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, E - EGP
       i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, su - IS-IS summary null, * - candidate default
       U - per-user static route, o - ODR, L - local, G - DAGR
       A - access/subscriber, - FRR Backup path
Gateway of last resort is not set
L    172.16.162.2/32 is directly connected, 00:34:47, Loopback10
i don´t know if need something on OSPF
Best Regards

Bundle-ether ASR9K to WS3750X

Similar Messages

Maybe you are looking for