09-24-2012 12:42 AM - edited 03-07-2019 09:03 AM
Hello,
We have an ASR and its the only one at DC3. The overlay state is up but nothing is being forwarded. All other adjacencies out side of this site can be seen. Any ideas what the problem might be?
ET-ASR1001-01#show otv site
Site Adjacency Information (Site Bridge-Domain: 8)
Overlay1 Site-Local Adjacencies (Count: 1)
Hostname System ID Last Change Ordinal AED Enabled Status
* ET-ASR1001-01 442B.03E7.ED00 - Not AED capable
Overlay Interface Overlay1
VPN name : None
VPN ID : 1
State : UP
AED Capable : No, overlay DIS not elected
IPv4 control group : 239.1.1.1
Mcast data group range(s): 232.1.1.0/28
Join interface(s) : Loopback10
Join IPv4 address : 192.168.230.248
Tunnel interface(s) : Tunnel1
Encapsulation format : GRE/IPv4
Site Bridge-Domain : 8
Capability : Multicast-reachable
Is Adjacency Server : No
Adj Server Configured : No
Prim/Sec Adj Svr(s) : None
ET-ASR1001-01#show otv
Overlay Interface Overlay1
VPN name : None
VPN ID : 1
State : UP
AED Capable : No, site interface not up
IPv4 control group : 239.1.1.1
Mcast data group range(s): 232.1.1.0/28
Join interface(s) : Loopback10
Join IPv4 address : 192.168.230.248
Tunnel interface(s) : Tunnel1
Encapsulation format : GRE/IPv4
Site Bridge-Domain : 8
Capability : Multicast-reachable
Is Adjacency Server : No
Adj Server Configured : No
Prim/Sec Adj Svr(s) : None
10-02-2012 01:12 AM
This was a configuration mistake - I didnt have the OTV Vlan (bridge domain 8) on the OTV inside so election was not possbile. This vlan should not be configured on the overlay.
hth others.
03-05-2013 10:11 AM
I am having the same issue, what do you mean when you say the vlan should not be configured on the overlay?
03-06-2013 04:33 AM
So the OTV vlan should not be configured on the Overlay interface.
That vlan should be configured on the INSIDE interface, towards your layer 2/3 switch internally. Then on that switch you need to create the same vlan id specified on the ASR, and then to allow that OTV vlan on the trunks so the election can take place.
I.e.
if your OTV vlan was say, vlan 8 and we want vlan 1 to be extended via OTV
Interface gi0/0/1
Description INSIDE TO SWITCH
service instance 8 Ethernet
Encapsulation dot1q 8
Bridge domain 8
!
Service instance 1 Ethernet
Encapsulation dot1q 1
Bridge domain 1
Interface Overlay 1
Service instance 1 Ethernet
Encapsulation dot1q 1
Bridge domain 1
End
Note that the OTV election vlan is not on the overlay interface. Should be on the inside so it can have an election with the other ASR on the same vlan. And if you didn't have another ASR and it was the only one then it will assume the active AED.
Let me know if this works for you.
Kind Regards
Sent from Cisco Technical Support iPhone App
03-06-2013 06:43 AM
I have it setup as you outlined, but I still cannot get an adjacency to form. This is the only ASR at this site and I am trying to get OTV running between a N7K and this ASR. There is a L3 MPLS network connecting both sites.
From the N7K I see the adjacency, but not from the ASR. I never get the AED to change. The ASR states it is not AED capable.
I have been through multiple docs and I do not know what else to change or look at to see how to get the adjacency to come up on the ASR.
03-06-2013 06:59 AM
Okay, so i assume there is normal ip connectivity between sites. Does the N7K have OTV working else where?
Please tell me which vlan you are using for your OTV Site (for the election to take place)
Have you got 'otv site bridge-domain #' configured? (the # should be the vlan-id that is going to be used for the site election)
On the ASR could you please output the following
show otv adjacency
show otv site
show otv detail
show run int overlay # (whichever overlay interface you are using)
show run int gi0/0/# (whichever interface is your INSIDE interface)
03-06-2013 07:33 AM
Yes there is connectivity between sites. This is the only OTV in the network, so there is not another OTV working.
The N7K is using vlan 910, it is a vlan only no interface vlan 910 is confiugred.
The ASR is using the same, and configured the same way.
show otv adjacency shows nothing.
show otv site -
Site Adjacency Information (Site Bridge-Domain: 910)
Overlay1 Site-Local Adjacencies (Count: 1)
Hostname System ID Last Change Ordinal AED Enabled Status
* DMD-DR-ASR1001 A493.4C30.3180 - Not AED capable
show otv detail -
Overlay Interface Overlay1
VPN name : Overlay1
VPN ID : 4
State : UP
AED Capable : No, overlay DIS not elected
IPv4 control group : 225.0.0.1
Mcast data group range(s): 232.10.10.0/24
Join interface(s) : GigabitEthernet0/0/0
Join IPv4 address : 172.16.100.7
Tunnel interface(s) : Tunnel0
Encapsulation format : GRE/IPv4
Site Bridge-Domain : 910
Capability : Multicast-reachable
Is Adjacency Server : No
Adj Server Configured : No
Prim/Sec Adj Svr(s) : None
OTV instance(s) : 0
FHRP Filtering Enabled : Yes
ARP Suppression Enabled : Yes
ARP Cache Timeout : 600 seconds
interface Overlay1
no ip address
otv control-group 225.0.0.1
otv data-group 232.10.10.0/24
otv join-interface GigabitEthernet0/0/0
otv vpn-name Overlay1
service instance 900 ethernet
encapsulation dot1q 900
bridge-domain 900
!
service instance 901 ethernet
encapsulation dot1q 901
bridge-domain 901
!
service instance 902 ethernet
encapsulation dot1q 902
bridge-domain 902
!
service instance 903 ethernet
encapsulation dot1q 903
bridge-domain 903
!
service instance 904 ethernet
encapsulation dot1q 904
bridge-domain 904
!
service instance 905 ethernet
encapsulation dot1q 905
bridge-domain 905
!
service instance 906 ethernet
encapsulation dot1q 906
bridge-domain 906
!
service instance 907 ethernet
encapsulation dot1q 907
bridge-domain 907
!
service instance 908 ethernet
encapsulation dot1q 908
bridge-domain 908
!
service instance 909 ethernet
encapsulation dot1q 909
bridge-domain 909
!
interface FastEthernet0/1/0
description UPLINK-2960G-0/6 Layer 2
no ip address
negotiation auto
service instance 102 ethernet
encapsulation dot1q 102
bridge-domain 102
!
service instance 172 ethernet
encapsulation dot1q 172
bridge-domain 172
!
service instance 900 ethernet
encapsulation dot1q 900
bridge-domain 900
!
service instance 901 ethernet
encapsulation dot1q 901
bridge-domain 901
!
service instance 902 ethernet
encapsulation dot1q 902
bridge-domain 902
!
service instance 903 ethernet
encapsulation dot1q 903
bridge-domain 903
!
service instance 904 ethernet
encapsulation dot1q 904
bridge-domain 904
!
service instance 905 ethernet
encapsulation dot1q 905
bridge-domain 905
!
service instance 906 ethernet
encapsulation dot1q 906
bridge-domain 906
!
service instance 907 ethernet
encapsulation dot1q 907
bridge-domain 907
!
service instance 908 ethernet
encapsulation dot1q 908
bridge-domain 908
!
service instance 909 ethernet
encapsulation dot1q 909
bridge-domain 909
!
service instance 910 ethernet
encapsulation dot1q 910
bridge-domain 910
!
end
Overlay Interface Overlay1
VPN name : Overlay1
VPN ID : 4
State : UP
AED Capable : No, overlay DIS not elected
IPv4 control group : 225.0.0.1
Mcast data group range(s): 232.10.10.0/24
Join interface(s) : GigabitEthernet0/0/0
Join IPv4 address : 172.16.100.7
Tunnel interface(s) : Tunnel0
Encapsulation format : GRE/IPv4
Site Bridge-Domain : 910
Capability : Multicast-reachable
Is Adjacency Server : No
Adj Server Configured : No
Prim/Sec Adj Svr(s) : None
OTV instance(s) : 0
FHRP Filtering Enabled : Yes
ARP Suppression Enabled : Yes
ARP Cache Timeout : 600 seconds
show run int overlay1 -
interface Overlay1
no ip address
otv control-group 225.0.0.1
otv data-group 232.10.10.0/24
otv join-interface GigabitEthernet0/0/0
otv vpn-name Overlay1
service instance 900 ethernet
encapsulation dot1q 900
bridge-domain 900
!
service instance 901 ethernet
encapsulation dot1q 901
bridge-domain 901
!
service instance 902 ethernet
encapsulation dot1q 902
bridge-domain 902
!
service instance 903 ethernet
encapsulation dot1q 903
bridge-domain 903
!
service instance 904 ethernet
encapsulation dot1q 904
bridge-domain 904
!
service instance 905 ethernet
encapsulation dot1q 905
bridge-domain 905
!
service instance 906 ethernet
encapsulation dot1q 906
bridge-domain 906
!
service instance 907 ethernet
encapsulation dot1q 907
bridge-domain 907
!
service instance 908 ethernet
encapsulation dot1q 908
bridge-domain 908
!
service instance 909 ethernet
encapsulation dot1q 909
bridge-domain 909
!
sho run int fa 0/1/0 -
interface FastEthernet0/1/0
description UPLINK-2960G-0/6 Layer 2
no ip address
negotiation auto
service instance 102 ethernet
encapsulation dot1q 102
bridge-domain 102
!
service instance 172 ethernet
encapsulation dot1q 172
bridge-domain 172
!
service instance 900 ethernet
encapsulation dot1q 900
bridge-domain 900
!
service instance 901 ethernet
encapsulation dot1q 901
bridge-domain 901
!
service instance 902 ethernet
encapsulation dot1q 902
bridge-domain 902
!
service instance 903 ethernet
encapsulation dot1q 903
bridge-domain 903
!
service instance 904 ethernet
encapsulation dot1q 904
bridge-domain 904
!
service instance 905 ethernet
encapsulation dot1q 905
bridge-domain 905
!
service instance 906 ethernet
encapsulation dot1q 906
bridge-domain 906
!
service instance 907 ethernet
encapsulation dot1q 907
bridge-domain 907
!
service instance 908 ethernet
encapsulation dot1q 908
bridge-domain 908
!
service instance 909 ethernet
encapsulation dot1q 909
bridge-domain 909
!
service instance 910 ethernet
encapsulation dot1q 910
bridge-domain 910
03-06-2013 07:44 AM
On your 2960G-0/6 - is it trunking vlan 910?
03-06-2013 07:54 AM
yes it is trunking all vlans, I did not specify specific vlans on the trunk.
03-06-2013 07:57 AM
What is the otv site-identifier for both N7K and the ASR?
03-06-2013 08:01 AM
910 on both.
N7K
otv site-vlan 910
ASR
otv site bridge-domain 910
03-06-2013 08:07 AM
I mean something like: otv site-identifier 0000.0000.0004
I have site A and site B...
Site A is configured with
otv site-identifier 0000.0000.0001
Site B is configured with
otv site-identifier 0000.0000.0002
03-06-2013 08:08 AM
So basically the ASR L3 interface is is connected to a 3560 switch which has a 7206 with the MPLS circuit,both the 7206 and the L3 on the ASR are on vlan1. The layer 2 internal interface of the ASR is connected to 2960G switch. The other location there is a 7206 with the MPLS circuit connected to the N7K.
03-06-2013 08:11 AM
I have them setup with different Identifiers, N7K is 0001, ASR is 0002
03-06-2013 08:15 AM
Umm, I haven't tried this set up before. What happens when you plug the ASR and the Nexus directly into the MPLS. So bypass the 7200's and the 3560. There should be IP connectivity between them.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide