winfred.nl

A common rule of thumb for best effort (TCP) traffic is a burst size of 1.5
seconds. The math is left for your  exercise.

Interface: GigabitEthernet6/2 is up
TCAM screening for features: ACTIVE inbound
Interface: Vlan1600 is up
TCAM screening for features: ACTIVE inbound

Gi6/2 is mnagement port on RSP, Vlan1600 is active on Te4/1 in access mode.

!SVI of VLAN active on Te4/1
interface Vlan1600
ip address 192.168.100.1 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
load-interval 30
end

! null routing of destination IP of packets generated by downstream
device on te4/1
ip route 192.168.115.1 255.255.255.255 null0

7606s-test#show int vlan 1600
Vlan1600 is up, line protocol is up
30 second input rate 48325000 bits/sec, 100677 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec

7606s-test#top
CPU utilization for five seconds: 49%/48%; one minute: 48%; five
minutes: 34%

7606s-test#show ibc
Interface information:
Interface IBC0/0(idb 0x18D112A4)
5 minute rx rate 34956000 bits/sec, 72805 packets/sec
5 minute tx rate 0 bits/sec, 0 packets/sec

7606s-test#show netdr captured-packets
——- dump of incoming inband packet ——-
interface Vl1600, routine process_rx_packet_inline, timestamp 03:14:18.723
dbus info: src_vlan 0x640(1600), src_indx 0xC0(192), len 0x40(64)
bpdu 0, index_dir 0, flood 0, dont_lrn 0, dest_indx 0x380(896)
A8020400 06400000 00C00000 40000000 00110524 0E000040 00000000 03802000
destmac 00.21.D8.CB.4B.00, srcmac 00.1B.21.D7.36.74, protocol 0800
protocol ip: version 0x04, hlen 0x05, tos 0x00, totlen 28, identifier 6692
df 0, mf 0, fo 0, ttl 64, src 192.168.100.2, dst 192.168.115.1
udp src 3854, dst 10000 len 8 checksum 0x102A

>
> On 5 Nov 2014, at 18:32, Jiri Prochazka wrote:
>
>> We will try the same setup with another RSP720-3CXL. I am getting to
>> the point it may be faulty Sup, even it seems very odd for me.
>> Everything works, but uRPF on CFC equipped cards..
>
> What other features do you have turned on which use up TCAM space?
>
> It’s sure sounding like a bug, though.
>
> Also, the output from sh fm sum when the issue is occurring might be
> useful, as well.

 I’m trying to lab up a hub and spoke L2 VPN scenario using L2TPv3.

CPEs are ISR G2s such as 1941 and the PE/Hub is an ME3600. I’m not having much luck so I wondered if I’m chasing a ghost; Has anyone used
L2TPv3 xconnects (due to lack of MPLS) into a VFI on an ME3600 to get this scenario to work?

Perhaps you used something else that worked? Or do you think this simply can’t be done?

When mixing L2TPv3 with VFIs, is the logic present to do things like MAC learning, I’ve never tried this without MPLS and/or BGP.


Something like;


pseudowire-class l2tpv3-class
 encapsulation l2tpv3
 interworking ethernet
 ip local interface looopback 0

l2 vfi TEST manual
 vpn id 100
  bridge-domain 200
  neighbor 1.1.1.1 pw-class l2tpv3-class
  neighbor 2.2.2.2 pw-class l2tpv3-class

int gi0/2
 switchport mode trunk
 switchport trunk allow vlan none
  service instance 200 ethernet
  uncapsulation untagged
  bridge-domain 200

int vlan200
 no ip address