Open-source FlowViewer version 3.4 has been released.
FlowViewer is a web-based companion set of tools to Mark Fullmer's
flow-tools netflow capture and analysis tool suite (up to v7). FlowViewer
enables users to analyze and track traffic through their network. Users
can quickly and easily
On Tue, 2011-03-15 at 16:07 +0100, Peter Rathlev wrote:
We're thinking about introducing dedicated Route Reflectors in our
small-ish MPLS VPN network. We currently have ~35 PE devices, all
6500/Sup720. There are no dedicated P devices.
...
The ISR 2901 seems fit for the job. Any comments on
Is there any smart way configure an MPLS VPN network for a central
services VRF for all (or many) other VRFs?
I see three possible ways:
1) Use import export on the central services VRF, no configuration
on the other VRFs:
ip vrf A
rd 1:1
route-target both 1:1
!
I don't think any of them will work. The router import and export has
to be symmetric if you want bidirectional communication.
ip vrf A
rd 1:1
route-target both 1:1
route-target import 1:3
!
ip vrf B
rd 1:2
route-target both 1:2
route-target
On 3/18/2011 9:04 AM, Peter Rathlev wrote:
Is there any smart way configure an MPLS VPN network for a central
services VRF for all (or many) other VRFs?
I am doing this by (all VRFs import/export themselves) importing the customer
VRFs into
the services VRF, and each customer VRF imports the
On Fri, 2011-03-18 at 09:31 -0400, schilling wrote:
I don't think any of them will work. The router import and export has
to be symmetric if you want bidirectional communication.
[...]
But how was that not acheived in all the three scenarios I described?
Your suggestion:
ip vrf A
On Fri, 2011-03-18 at 09:59 -0400, Jeff Kell wrote:
I am doing this by (all VRFs import/export themselves) importing the
customer VRFs into the services VRF, and each customer VRF imports the
services VRF.
Yeah, that's a solution too (the same as schilling suggested AFAICT),
but of course
The 2901 can more than handle 35 connections, but how many routes are we
talking about, it's not just about the processing power, it's also about the
amount of mem, based on the amount of routes.
Jorge
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
On Fri, 2011-03-18 at 09:40 -0400, Jorge L. Rodriguez Aguila wrote:
The 2901 can more than handle 35 connections, but how many routes are
we talking about, it's not just about the processing power, it's also
about the amount of mem, based on the amount of routes.
As I snipped from my last mail
Have you looked at doing vrf-nat?
On 18 Mar 2011, at 13:04, Peter Rathlev wrote:
Is there any smart way configure an MPLS VPN network for a central
services VRF for all (or many) other VRFs?
I see three possible ways:
1) Use import export on the central services VRF, no configuration
Depending on platform and scalability requirements, EVN Route
Replication might provide some options
http://www.cisco.com/en/US/docs/ios/ios_xe/evn/configuration/guide/evn_shared_svcs_xe.html
Cheers,
Matt
Message: 9
Date: Fri, 18 Mar 2011 14:04:45 +0100
From: Peter Rathlev
Hello,
I'm searching for a way to exclude the netflow data of one interface
from the exported netflow-information. The underlying system is a
WS-C6509-E with a WS-SUP720-3B. The netflow / nde configuration part
is:
!
ip flow ingress layer2-switched vlan list-of-vlan-ids
mls flow ip full
mls nde
Hi,
On Fri, Mar 18, 2011 at 04:23:14PM +0100, md4799 wrote:
I'm searching for a way to exclude the netflow data of one interface
from the exported netflow-information. The underlying system is a
WS-C6509-E with a WS-SUP720-3B. The netflow / nde configuration part
is:
If you upgrade to SXH or
Hello,
WE are observing problem with snmp statistic which get from SRE2 IOS.
The Snmp values : ifHCInOctets / ifHCOutOctets.
We have physical interface and one logical subinterface on it.
The snmp statistic is different for the same interface.
If we watch snmp statistic on physical interface
Hi Peter.
Is there any smart way configure an MPLS VPN network for a central
services VRF for all (or many) other VRFs?
snip/
An SP from which we buy last-mile in a couple of VRFs have their
management prefixes leaked out into every VRF and we're looking for
something similar.
Does
Kind souls pointed me off-list to two quite relevant things:
a) I made a typo in the original example 2; VRF Central_Services in
scenario 2 would of course import/export RT 1:3, not 1:1 as I wrote.
b) Import/export to/from RT 1:3 from all VRFs would effectively join
all VRFs, which was
Broadcom themselves do some pretty fast and impressive switches.
http://www.broadcom.com/products/Switching
From: Chris Evans chrisccnpsp...@gmail.com
To: Asbjorn Hojmark - Lists li...@hojmark.org
Cc: Cisco NSP cisco-nsp@puck.nether.net
Sent: Wed, March 16,
Hi Gert,
hi Rayn,
thanks a lot for the quick answer and explanation!
Kind regards
Mark
On Fri, Mar 18, 2011 at 4:40 PM, Gert Doering g...@greenie.muc.de wrote:
Hi,
On Fri, Mar 18, 2011 at 04:23:14PM +0100, md4799 wrote:
I'm searching for a way to exclude the netflow data of one interface
On 3/14/2011 11:25 PM, Brad Hedlund (brhedlun) wrote:
Hi Chuck,
The switch not being upgraded will keep the vPC connections UP, just as you
witnessed when your switch rebooted due to fan issues. However...
Prior to the recent 5.0(2) release, IF your vPC connections were reset for some
other
19 matches
Mail list logo
