problem with bvi interface on ASR 1004

[Muhammed AKYUZ]

Hi,

I tried to use bvi interface on ASR 1004 but it wasnot successfull..

What should be the problem:

ASR learns mac address. but it does not ping the devices. But if i assign the same ip to phisical port, it works (PINGS..)

asr 1000 e ait bridging config guide da bulamadim.

bridge irb
bridge 1 route ip
bridge 1 protocol ieee

interface GigabitEthernet0/0/1
  description 6500-BACKBONE-1
  no ip address
  negotiation auto
  bridge-group 1
!
interface GigabitEthernet0/0/2
  description 6500-BACKBONE-2
  no ip address
  shutdown
  negotiation auto
  bridge-group 1

interface BVI1
  ip address 10.72.33.250 255.255.255.0
!





ASR-1004-79#sh spanning-tree

Bridge group 1
   Spanning tree enabled protocol ieee
   Root ID    Priority    32768
              Address     c89c.1dc7.d901
              This bridge is the root
              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec

   Bridge ID  Priority    32768
              Address     c89c.1dc7.d901
              Hello Time   2 sec  Max Age 20 sec  Forward Delay 15 sec
              Aging Time 300

Interface           Role Sts Cost      Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi0/0/1             Desg FWD 4         128.9    P2p R-L2GP
Gi0/0/2             Desg DWN 4         128.10   P2p

[Reza Sharifi]

Hi

Take a look at below interface config.  It is shutdown.  do a "no sh" and try again

interface GigabitEthernet0/0/2
  description 6500-BACKBONE-2
  no ip address
  shutdown
  negotiation auto
  bridge-group 1

HTH

Reza

[Muhammed AKYUZ]

ı have tried with no sh state but it does not work..

[Muhammed AKYUZ]

asr 1000 series does not support bvi interfaces

tac responded to me like that

Sent from Cisco Technical Support iPhone App

[ayhancibm]

Late response I know but yesterday I was searching for the same problem... I could achieve this using BDI instead.

Spanning-Tree on Neighbour Switch(es) and default ARP timeout on ASR needs to be considered as a problem and sorted seperately.

|SW-1|    -----------  ____

       |                         |          |

       |                        | ASR |

|SW-2|    ------------|____|

!
interface BDI31
ip address 31.31.31.1 255.255.255.0
encapsulation dot1Q 31
!
interface BDI32
ip address 32.32.32.1 255.255.255.0
encapsulation dot1Q 32
!
interface BDI33
ip address 33.33.33.1 255.255.255.0
encapsulation dot1Q 33
!
interface BDI34
ip address 34.34.34.1 255.255.255.0
encapsulation dot1Q 34
!
interface BDI35
ip address 35.35.35.1 255.255.255.0
encapsulation dot1Q 35
!

!
interface GigabitEthernet0/2/3
no ip address
negotiation auto
service instance 1 ethernet
  encapsulation dot1q 31
  bridge-domain 31
!
service instance 2 ethernet
  encapsulation dot1q 32
  bridge-domain 32
!
service instance 3 ethernet
  encapsulation dot1q 33
  bridge-domain 33
!
service instance 4 ethernet
  encapsulation dot1q 34
  bridge-domain 34
!
service instance 5 ethernet
  encapsulation dot1q 35
  bridge-domain 35
!
!
interface GigabitEthernet0/2/4
no ip address
negotiation auto
service instance 1 ethernet
  encapsulation dot1q 31
  bridge-domain 31
!
service instance 2 ethernet
  encapsulation dot1q 32
  bridge-domain 32
!
service instance 3 ethernet
  encapsulation dot1q 33
  bridge-domain 33
!
service instance 4 ethernet
  encapsulation dot1q 34
  bridge-domain 34
!
service instance 5 ethernet
  encapsulation dot1q 35
  bridge-domain 35
!

---------------------------------------------------------------------------------------------------------------------------

Btw: "Backup interface" feature works much better for our case as we eleminate STP issues and enable "spanning-tree portfast trunk" on Switch Trunk Ports.