[c-nsp] VPLS on 7600
Brad Hedlund
brhedlun at cisco.com
Wed Mar 4 00:26:24 EST 2009
Hi,
VPLS is not supported over GRE on 7600.
Brad Hedlund
bhedlund at cisco.com
http://www.internetworkexpert.org
On 3/3/09 10:28 PM, "Asheesh Jadav" <ajadav at gmail.com> wrote:
> Hi,
>
> I'm trying to get answers to a few questions regarding VPLS configuration
> on a 7600. Can someone please help me out here. Below is my running config.
>
> * I'm not seeing the traffic coming in on the VC get switched towards the
> attachment circuit. The traffic i'm using is Unicast, IP. Is there something
> i'm missing in my config?
> * The 'Output Interface' and 'Preferred path' parameters for the VC are
> default, why is it so? And how can I set a preferred path if I can?
>
> Thanks.
>
> Router#
> Router#show run
> Building configuration...
>
> Current configuration : 2641 bytes
> !
> upgrade fpd auto
> version 12.2
> service timestamps debug datetime msec
> service timestamps log datetime msec
> no service password-encryption
> service counters max age 10
> !
> hostname Router
> !
> boot-start-marker
> boot system flash
> sup-bootdisk:c7600s72033-advipservicesk9-mz.122-33.SRB5.bin
> boot-end-marker
> !
> !
> no aaa new-model
> ip subnet-zero
> !
> !
> !
> !
> ipv6 mfib hardware-switching replication-mode ingress
> mls ip slb purge global
> mls ip multicast flow-stat-timer 9
> mls flow ip interface-full
> no mls flow ipv6
> no mls acl tcam share-global
> mls cef error action reset
> mpls traffic-eng tunnels
> mpls ldp neighbor 7.7.7.7 targeted ldp
> mpls ldp discovery targeted-hello accept
> mpls label range 2048 524287
> mpls label protocol ldp
> !
> !
> spanning-tree mode pvst
> spanning-tree extend system-id
> diagnostic cns publish cisco.cns.device.diag_results
> diagnostic cns subscribe cisco.cns.device.diag_commands
> !
> !
> redundancy
> mode sso
> main-cpu
> auto-sync running-config
> !
> vlan internal allocation policy ascending
> vlan access-log ratelimit 2000
> l2 vfi vpls manual
> vpn id 100
> neighbor 7.7.7.7 encapsulation mpls
> !
> !
> !
> !
> !
> !
> !
> interface Tunnel1
> ip unnumbered Loopback0
> mpls traffic-eng tunnels
> mpls ip
> tunnel source GigabitEthernet4/1
> tunnel destination 7.7.7.7
> tunnel mode mpls traffic-eng
> tunnel mpls traffic-eng autoroute announce
> tunnel mpls traffic-eng path-option 1 dynamic
> !
> interface Loopback0
> ip address 9.9.9.9 255.255.255.255
> !
> interface GigabitEthernet4/1
> ip address 20.20.20.9 255.255.255.0
> ip ospf network broadcast
> ip ospf priority 2
> mpls traffic-eng tunnels
> mpls label protocol ldp
> ip rsvp bandwidth
> !
> interface GigabitEthernet4/2
> switchport
> switchport access vlan 100
> switchport mode access
> !
> interface GigabitEthernet4/3
> no ip address
> !
> interface GigabitEthernet4/4
> no ip address
> shutdown
> !
> interface GigabitEthernet4/5
> no ip address
> shutdown
> !
> interface GigabitEthernet4/6
> no ip address
> shutdown
> !
> interface GigabitEthernet4/7
> no ip address
> shutdown
> !
> interface GigabitEthernet4/8
> no ip address
> shutdown
> !
> interface GigabitEthernet5/1
> no ip address
> shutdown
> !
> interface GigabitEthernet5/2
> no ip address
> shutdown
> !
> interface Vlan1
> no ip address
> shutdown
> !
> interface Vlan100
> no ip address
> xconnect vfi vpls
> !
> router ospf 1
> router-id 9.9.9.9
> log-adjacency-changes
> network 9.9.9.9 0.0.0.0 area 0
> network 20.20.20.0 0.0.0.255 area 0
> mpls traffic-eng router-id Loopback0
> mpls traffic-eng area 0
> mpls traffic-eng interface GigabitEthernet4/1 area 0
> !
> ip classless
> !
> !
> no ip http server
> no ip http secure-server
> !
> !
> !
> mpls ldp router-id Loopback0 force
> !
> control-plane
> !
> !
> line con 0
> line vty 0 4
> login
> !
> !
> end
>
> Router#show ip cef
> Prefix Next Hop Interface
> 0.0.0.0/0 no route
> 0.0.0.0/32 receive
> 7.7.7.7/32 7.7.7.7 Tunnel1
> 9.9.9.9/32 receive Loopback0
> 20.20.20.0/24 attached GigabitEthernet4/1
> 20.20.20.0/32 receive GigabitEthernet4/1
> 20.20.20.7/32 attached GigabitEthernet4/1
> 20.20.20.9/32 receive GigabitEthernet4/1
> 20.20.20.255/32 receive GigabitEthernet4/1
> 127.0.0.0/8 attached EOBC0/0
> 127.0.0.0/32 receive EOBC0/0
> 127.0.0.51/32 receive EOBC0/0
> 127.255.255.255/32 receive EOBC0/0
> 224.0.0.0/4 drop
> 224.0.0.0/24 receive
> 240.0.0.0/4 drop
> 255.255.255.255/32 receive
> Router#
> Router#show mpls l2transport vc 100 detail
> Local interface: VFI vpls VFI up
> MPLS VC type is VFI, interworking type is Ethernet
> Destination address: 7.7.7.7, VC ID: 100, VC status: up
> Output interface: none, imposed label stack {2048}
> Preferred path: not configured
> Default path: active
> Next hop: Invalid ADDR
> Create time: 09:16:24, last status change time: 00:07:30
> Signaling protocol: LDP, peer 7.7.7.7:0 up
> Targeted Hello: 9.9.9.9(LDP Id) -> 7.7.7.7
> MPLS VC labels: local 2050, remote 2048
> Group ID: local 0, remote 100
> MTU: local 1500, remote 1500
> Remote interface description:
> Sequencing: receive disabled, send disabled
> VC statistics:
> packet totals: receive 111393, send 0
> byte totals: receive 6683580, send 0
> packet drops: receive 0, send 0
>
> Router#
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list