Re: OTV and Multicast - Page 2

maverick-lamont · ‎02-25-2014

Hey Guys,

So I have setup the below lab and I am having trouble with the OTV adjacency finding the routers in the other site.

Lab Site 1:

1 ESX Host
1 WEB Server ( vlan 400)
2 x CSR 1000v
- Gi1 - WAN
- Gi2 - 300
- Gi3 - MGMT
- Gi4 - Trunk(vlan 400 and will trunk more when lab is working)
1 HP 1910 Switch
VLAN's trunked to ESX host
Access VLAN 300 patches to Switch in Site 2.

Lab Site 2:

1 ESX Host
1 WEB Server ( vlan 400)
2 x CSR 1000v
- Gi1 - WAN
- Gi2 - SITE LINK (VLAN 300)
- Gi3 - MGMT
- Gi4 - Trunk(vlan 400 and will trunk more when lab is working)
1 Cisco C3548XL switch.
VLAN's trunked to ESX host
Access VLAN 300 patches to Switch in Site 2

All routers have a port directly connect to VLAN 300 and configured with a 10.0.0.0/24 IP. All routers can ping each other and they have peered using iBGP. I have OSPF configured for internal VLAN's at each site that I dont want to extend with OTV and have BGP redistributing OSPF.

The OTV is peering with the other router in its site but not detecting the routers at the other site.

IP IGMP snooping is not running.

Config:

!

ip multicast-routing distributed

!

interface GigabitEthernet2

ip pim passive

ip igmp version 3

!
otv site-identifier 0001.0001.0001 #0002.0002.0002 for site 2.
!
interface Overlay1
otv control-group 239.37.37.37
otv data-group 232.37.37.0/24
otv join-interface GigabitEthernet2
no shutdown

If I change the OTV config to unicast it works fine but it is not recomended to do it this way and you can only specify 2 IP's when manually setting the adjacency.

Any ideas of where I should focus my efforts to troubleshoot would be much appreciated.

Regards

David

Bilal Nawaz · ‎02-27-2014

It doesn't seem to be AED capable anymore, anything else that you changed? Before it seemed fine from your screenshots, it just needed a WAN neighbor to operate fully.
The very fact the pim neighborship does not come up between both sites is a problem.

Sent from Cisco Technical Support iPhone App

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

maverick-lamont · ‎02-27-2014

It is because I turned off the second router that was in the same site. Because it had adjacency with that CSR it was AED capable. The problem is getting adjacency with the other site. If I move one of the CSR's so that they are both in the same site everything works fine, OTV works.

Bilal Nawaz · ‎02-27-2014

No, the router should be AED capable without the second router. It is not necessary that you have to have two routers for a router to become AED capable, thats just silly right? Unless this is some weird limitation which i very much doubt that Cisco would have introduced.

You need multicast to work across to the other site. I think, after the discussions we have had, the transport network between seems to be the cause.

I will try to get hold of CSR's VM'd up and see if I can replicate your situation. I'll post current configs with ASR1002's with point to point connections with OTV working.

Out of interest, this is the first time I have come across OTV with the virtual appliances hosted on ESX hosts, is this going in production?

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

maverick-lamont · ‎02-27-2014

This is the config guide I originally followed: http://www.layerzero.nl/blog/2013/05/otv-and-lisp-on-the-csr-1000v/

Worked first time but I was using a single ESX host.

We are planning to deploy OTV, so was just wanting to get familiar with it in a virtual lab.

I agree that it is probably the switch between the site, unfortunaly I am out of decent lab equipment.

I will try deploy them in our production ESX tomorrow and see if I can atleast bring the OTV with a decent switch in between.

Thanks

David

Bilal Nawaz · ‎02-27-2014

This router (ASR1002-x) has point to point links to DC and other sites with OTV functioning. Mainly going towards the DC - N7K which is interface Te0/3/0

ip multicast-routing distributed

!

otv site bridge-domain 8

!

otv site-identifier 0000.0000.0010

multilink bundle-name authenticated

!

track 1 interface TenGigabitEthernet0/3/0 line-protocol

!

interface Loopback0

description PIM-RP-ADDRESS

ip address 192.168.255.1 255.255.255.255

ip pim sparse-mode

ip ospf 1 area 0

!

interface Loopback1

description PIM-ANYCAST

ip address 192.168.255.11 255.255.255.255

ip pim sparse-mode

ip ospf 1 area 0

!

interface Overlay1

no ip address

otv control-group 239.1.1.1

otv data-group 238.1.1.0/28

otv join-interface TenGigabitEthernet0/3/0

!

interface GigabitEthernet0/0/0

description ## S-ASR-WAN01 ## REFXXXX ##

mtu 9216

ip address 192.168.143.1 255.255.255.252

ip pim sparse-mode

ip ospf network point-to-point

ip ospf bfd

ip ospf 1 area 0

ip ospf cost 1000

negotiation auto

bfd interval 50 min_rx 50 multiplier 5

cdp enable

!

interface GigabitEthernet0/0/1

description ## S-ASR1002-01 ## SHUK ##

mtu 1700

ip address 192.168.230.34 255.255.255.252

ip pim sparse-mode

ip ospf bfd

ip ospf 1 area 0

shutdown

negotiation auto

bfd interval 50 min_rx 50 multiplier 5

cdp enable

!

interface TenGigabitEthernet0/1/0

description ## ASR routing to ASR-WAN02 ##

mtu 9216

ip address 192.168.110.1 255.255.255.252

ip pim sparse-mode

ip ospf network point-to-point

ip ospf bfd

ip ospf 1 area 0

bfd interval 50 min_rx 50 multiplier 5

cdp enable

!

interface TenGigabitEthernet0/2/0

description ## Trunk to 6509E-VSS01 - OTV & ROUTE ## Te1/2/1 ##

no ip address

cdp enable

service instance 8 ethernet

encapsulation dot1q 8

bridge-domain 8

!

interface TenGigabitEthernet0/2/0.1111

description ## P2P to 6509E-VSS01 - ROUTE ## Te1/2/1 ##

encapsulation dot1Q 1111

ip address 192.168.111.1 255.255.255.252

ip pim sparse-mode

ip ospf network point-to-point

ip ospf bfd

ip ospf 1 area 1

bfd interval 50 min_rx 50 multiplier 5

!

interface TenGigabitEthernet0/3/0

description ## P2P to DC1-N7K-WAN01 - ROUTE ## Ex/x ##

mtu 9216

ip address 192.168.11.2 255.255.255.252

ip pim sparse-mode

ip igmp version 3

ip ospf network point-to-point

ip ospf bfd

ip ospf 1 area 0

bfd interval 50 min_rx 50 multiplier 5

cdp enable

!

router ospf 1

router-id 192.168.111.1

auto-cost reference-bandwidth 100000

passive-interface default

no passive-interface GigabitEthernet0/0/0

no passive-interface TenGigabitEthernet0/1/0

no passive-interface TenGigabitEthernet0/2/0.1111

no passive-interface TenGigabitEthernet0/3/0

!

ip pim rp-address 192.168.255.1

ip pim ssm default

ip msdp peer 192.168.255.12 connect-source Loopback1

ip msdp peer 192.168.101.3 connect-source Loopback1

ip msdp peer 192.168.201.3 connect-source Loopback1

ip msdp cache-sa-state

ip msdp originator-id Loopback1

ip msdp mesh-group MSDP-DC 192.168.101.3

ip msdp mesh-group MSDP-DC 192.168.201.3

!

event manager applet Int-Down

event track 1 state down

action 1.0 cli command "enable"

action 1.1 cli command "conf t"

action 1.2 cli command "interface overlay 1"

action 1.3 cli command "shutdown"

event manager applet Int-Up

event track 1 state up

action 1.0 cli command "enable"

action 1.1 cli command "conf t"

action 1.2 cli command "interface overlay 1"

action 1.3 cli command "no shutdown"

Please rate useful posts & remember to mark any solved questions as answered. Thank you.

maverick-lamont · ‎02-28-2014

Thanks, yeah I guess the point ot point is just part of their OSPF config.

Moved the CSR's to our production and ESX and it worked immediatly, it has to be that HP swithc in the middle.

Thanks

for the the help.