[rbak-nsp] Bridges and Cross-Connections

[Maciej Hiller]

Hi,

I tried, but the same result.

Maciej

W dniu 2014-08-23 18:10, Daniel Celiński napisał(a):
> Hello,
> 
> Try to modify the bridge profile:
> 
> bridge profile PROF-RTR-KAL-TO-RTR-KIJ
> 
>  trunk
> 
>  mac-limit 10
> 
> --
> 
> Daniel
> 
> 2014-08-23 14:30 GMT+02:00 Maciej Hiller <maciej.hiller at host24.pl>:
> 
>> Hi,
>> 
>> I tried to do bridge or cross-connect between two vlans, but no
>> success.
>> 
>> 1. CROSS-CONNECT
>> 
>> Current configuration:
>> !
>> port ethernet 2/1
>> encapsulation dot1q
>> dot1q pvc 11
>> bind bypass
>> !
>> port ethernet 2/3
>> encapsulation dot1q
>> dot1q pvc 11
>> bind bypass
>> !
>> xc-group RTR-KAL-RTR-KIJ
>> xc 2/1 vlan-id 11 to 2/3 vlan-id 11
>> !
>> end
>> 
>> #sh bypass summary
>> 
>> Endpoints total: 2, Up: 2, Down: 0
>> Crossconnects total: 1, Up: 1, Down: 0
>> 
>> #sh bypass
>> Circuit State XC Circuit State
>> 2/1 vlan-id 11 Up 2/3 vlan-id 11 Up
>> 
>> everything looks ok but ping doesn't go
>> 
>> 2. BRIDGE
>> 
>> Current configuration:
>> !
>> ! STP global configuration
>> spanning-tree profile BRIDGE-STP
>> !
>> !
>> ! Bridge global configuration
>> bridge profile PROF-RTR-KAL-TO-RTR-KIJ
>> mac-limit 10
>> !
>> context bridge
>> !
>> no ip domain-lookup
>> !
>> interface BRIDGE-KAL-KIJ bridge
>> bridge name RTR-KAL-TO-RTR-KIJ
>> no logging console
>> !
>> bridge RTR-KAL-TO-RTR-KIJ
>> !
>> spanning-tree
>> master
>> !
>> port ethernet 2/1
>> dot1q pvc 15
>> bind interface BRIDGE-KAL-KIJ bridge
>> bridge profile PROF-RTR-KAL-TO-RTR-KIJ
>> spanning-tree profile BRIDGE-STP
>> !
>> port ethernet 2/4
>> dot1q pvc 15
>> bind interface BRIDGE-KAL-KIJ bridge
>> bridge profile PROF-RTR-KAL-TO-RTR-KIJ
>> spanning-tree profile BRIDGE-STP
>> 
>> #sh bridge bindings all detail
>> Flags are,(L)earning,(D)ynamic,(t)ributary,(T)runk,
>> (R)estricted,(d)eleted,(S)tale,(l)og,(U)p, (Ld) Loop Detection
>> (D)eny bpdu,(O)nly bpdu,(A)llow bpdu (default)
>> (F)orwarding,(D)iscarding,(N)one,(M)aster,(C)lient
>> 
>> Headings : Ld Pri - Loop Detection Priority
>> (Bpdu Pri)- bridge protocol data unit Priority
>> Context Bridge Group Circuit MAC D-MAC
>> Limit Flag Ld Pri Bpdu Pri
>> bridge RTR-KAL-TO-R 2/1 vlan-id 15 0 0
>> 10 L--t----U--A 0 -
>> 
>> Source Filter Name : -
>> Source Filter Id : 0
>> 
>> bridge RTR-KAL-TO-R 2/4 vlan-id 15 0 0
>> 10 L--t----U--A 0 -
>> 
>> Source Filter Name : -
>> Source Filter Id : 0
>> 
>> #sh bridge bindings all tracking
>> Context Bridge Group Circuit Stp
>> State Role clients
>> bridge RTR-KAL-TO-RTR-KIJ 2/1 vlan-id 15
>> FORWARD MASTER 0
>> 
>> bridge RTR-KAL-TO-RTR-KIJ 2/4 vlan-id 15
>> FORWARD MASTER 0
>> 
>> #sh bridge associations all
>> Bridge Profile Circuit Port Number
>> PROF-RTR-KAL-TO-RTR-KIJ 2/1 vlan-id 15 2
>> 
>> PROF-RTR-KAL-TO-RTR-KIJ 2/4 vlan-id 15 3
>> 
>> #sh bridge info all
>> Type can be: (L)earning,(P)kt-order-vpls,(R)outing,(Md) MacMove Drop
>> Context Bridge Group Type Ccts Aging MAC D-MAC
>> PW-Ccts Description
>> 
>> bridge RTR-KAL-TO-RTR-KIJ L-Md 2 300 2 0 0
>> 
>> here looks ok too, but ping doesn't go
>> 
>> if anyone has done bridge or cross-conections?
>> 
>> Best regards,
>> Maciej.
>> 
>> _______________________________________________
>> redback-nsp mailing list
>> redback-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/redback-nsp [1]
> 
> 
> 
> Links:
> ------
> [1] https://puck.nether.net/mailman/listinfo/redback-nsp
> 
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp