cabling all of them which to me contradicts what has been said on
this list.
Wikipedia articles:
http://en.wikipedia.org/wiki/Ds3
http://en.wikipedia.org/wiki/RG59
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco
, this was when SXE had just come out.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
is not something I would recommend. It's really
bad if you're running the older Engine 2 linecards, otherwise it's
managable. I still recommend ECMP over Etherchannel, though.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp
I don't really see why
you need it anyhow?
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
. Don't bother with DHCP protection and other
stuff in the fanout switches, they'll only break the other 23 participants
and it's fairly easy to faultfind.
So, in short, get cheap simple fan-out switch, do intelligence
centrally.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
issue.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
with it.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
actually tested it), ymmv.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
SXF.
It'll save you a lot of hassle in the long run.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail
bugfixed in 10 releases (basically) without adding
any features.
This is not bleeding edge, bleeding edge is when you install SXH (which is
the first revision of that feature release).
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp
On Thu, 25 Oct 2007, Aaron wrote:
They do have a DPT but you wont get OC12 on it. The 7200 just can't do that
much. The card will allow and OC12 through it.
In real life it flatlined at adding/removing approx 120 megabit/s to/from
the ring (empirical study).
--
Mikael Abrahamssonemail
On Tue, 30 Oct 2007, Pete Templin wrote:
Very helpful information...what commands should I be using to assess
where I'm at regarding Eng2 TCAM size?
show controllers psa mem on the LC in question is a good starting point.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
or
clock source internal in the CPE?
From your description it sounds like you should run clock source line in
the CPE.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman
On Sun, 2 Dec 2007, Jay Hennigan wrote:
Some non-Cisco gear relays CDP frames out all interfaces which results
I would say ALL non-cisco devices will relay CDP frames (and rightly so).
Only exception would be if someone else also implemented CDP.
--
Mikael Abrahamssonemail: [EMAIL
communication systems and
fiber-optic sensor applications.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco
the default ethernet
1500 mtu.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
On Sat, 12 Jan 2008, Peter Rathlev wrote:
But you still can't (shouldn't) use an interface MTU lower that the MPLS
MTU. Your interface MTU should be larger than the X MTU for any X.
Why?
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco
that is currently available.
The situation with devices on a subnet / L2 broadcast domain where some
speak mpls and some not, where some are older devices that do not support
mtu higher than 1500, needs this behaviour to avoid a network redesign.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
command such as show bgp ipv6 unicast summary.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
of the 6500.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
On Tue, 18 Mar 2008, Jon Lewis wrote:
On Mon, 17 Mar 2008, Mikael Abrahamsson wrote:
On Mon, 17 Mar 2008, Mark Tech wrote:
We currently run Cisco 7206VXR's using c7200-p-mz.122-25.S train in an
ISP environment. I am looking to get some 6500's but I'm a little
confused as to which IOS
initially?
I'd say it's worth it when you start to approach 5-10MPPS (due to CFC
worst case limit of ~15 MPPS) but not before.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net
have tried if you google a bit).
That is the only way I can think of.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
should be able to do somewhere around
150-200 meg of mixed traffic (bidirectionally), so if you're at 60% cpu
with 25 megs, that sounds like a lot of cpu for little traffic, even if
you would be running an NPE-150 or even slower.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
case, since it's out of support and
new software isn't compiled for it.
So telling someone don't use it for MPLS when there is a way to do it
that works, isn't really helpful.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing
or BU.
So don't expect this to get any better soon.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco
to) wirespeed
at all packet sized, but they have limited features.
I'd be more worried about the NPE-G2 performance if I were you.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net
here, we give 1000 users at least a gig, as they're going to use it
if they can.
So it's impossible to say how much is enough as it's very different
depending on audience and how much connectivity is available. There is no
such thing as too much.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
of the progress on this case, there must be very few
people doing etherchannel on these platforms.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive
of ZX. The -24dB receiver on the ZX can be sensitive enough to receive the
LX on the other end correctly.
Gigabit ethernet is mostly a play with attenuation and only attenuation,
whereas on 10G things like dispersion and other factors start to be
important as well.
--
Mikael Abrahamssonemail
accept it. PA-FDDI
won't work in VXR (which I guess is less of a problem).
I even need a VXR to run a NPE-300?
Yes.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net
is a great idea and I would really like to run it, but
it just didn't work with our mix of platforms and vendors.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo
over the link.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
and you can implement filtering etc?
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
for SUP720.
In my experience, not even Cisco will get it right all the time in what's
needed to get an old chassis to work with SUP720.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
30-40ms, then you might as well drop it (using WRED for
instance).
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
rebuild.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
On Mon, 18 Aug 2008, Sami Joseph wrote:
Is there a way to provide QoS for a specific VPN in an MPLS VPN Core?
Yes.
Depends on what you want, but you can for instance mark MPLS EXP for the
traffic in a certain VPN and treat those packets differently in your core.
--
Mikael Abrahamsson
data (interactive applications) and then
an best effort class. You might want to put all your VPN traffic into
priority data and let your Internet uses get a lower SLA if you mix
Internet and VPN traffic in your core.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED
to be unique per VPN,
how are you going to reach your CEs via SNMP etc?
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
, but rebooting would go into rommon).
To fix it, I would simply do a conf-reg 0x2102 and wr in regular config
mode, which seemed to set this conf-reg on all modules, making the problem
go away.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco
MPLS list
regarding the fact that I couldn't figure out where in the standard it was
said what address should be used where, but I received no reply so I am
still none the wiser how it should work so I know what vendor to tell to
go fix their stuff.
--
Mikael Abrahamssonemail: [EMAIL
, get a used Cisco 12000,
it'll take you into the gigabits/s realm quite cheaply, then when you're
past that, go for 7600.
7600 makes a lot of sense if you're ethernet only, the SONET/SDH
interfaces are quite pricey due to the need for SIP/SPAs.
--
Mikael Abrahamssonemail: [EMAIL
will be able to reach 0-2 second convergence
time...
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail
sources.
So make RD:s unique per PE, and of course make RTs identical within
the VPN.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive
RDs, there little downside apart from a
bit higher memory usage.
--
Mikael Abrahamsson email: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net
of headroom to do DS3.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
. Receivers are wideband and will take both 1310
and 1550nm light.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
unsupported in it.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
bugs where all jumbos are counted as
giants in interface counters, you might want to check the bug database.
--
Mikael Abrahamsson email: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco
run it over
a 1 meter cable. Also, I would be very surprised if cisco didn't support
SR in that module, where did you get that information?
whats everyone doing with 10G on the 12k out there ?
For 10GE on 12k, I'd say the SIP-601 + SPA1x10GE-L-V2 is the best way to
go.
--
Mikael
, but I guess that if you standardise on
MM within site (we use SM everywhere) I guess this might be a hassle.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo
. (The interfaces are configured with bfd interval 100 min_rx
100 multiplier 3.)
As far as I know, bfd timers so low aren't supported in SXF, you have to
go to SRB to get those.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list
etherchannel load sharing on 7200 and 7500. If it's of
interest, email me offline and I'll look into it tomorrow.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo
doesn't support nearly as agressive timers as SRB, from the top of my
head it was around second failure time (300x3), lower than that wasn't
supported.
Let's see if someone else here has more information, I don't have it in
writing easily accessable.
--
Mikael Abrahamssonemail: [EMAIL
a GEIP (with PA-GE) for $125? I'd say street value of that is
more like $500-$600. That's at least what the auctions went for a few
months back when I last checked.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp
packing
material. At least I've seen cisco ship 20+ of those oversize plastic
bags in a single box that wasn't big at all.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net
at CCO
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/12_4/ipv6_12_4_book.pdf
which has what you need and much more.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
of currently sold, is the two port
OC192 mentioned in another post.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
and iBGP, and to make sure
your IGP is preferred over BGP. I'd say this is highly recommended unless
you specifically need eBGP to be best.
--
Mikael Abrahamssonemail: [EMAIL PROTECTED]
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
media, doing ip tcp mss-adjust 1300 on the
interface where the traffic to encrypt/tunnel is passing
unencrypted/untunneled, might help you. Worth a try though, you don't want
multiple tunnel/encrypted packets per packet in the VPN.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
/received.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
about.
So I would be dismissing need because it's a LAN party without knowing
more about what scale we're talking.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman
/prod_white_paper0900aecd80673385.html
describes pretty well the different parts of the 6500/7600 platform when
it comes to what does what in it.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
from starvation of other classes I recommend putting a policer on the
priority class anyway.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive
thinking it is speaking to a hub that doesn't do autoneg, and
it'll detect the 100, but will go to 100/half.
There are recent hw from the past 1-2 years that can advertise
capabilities even when being fixed, but it has to be configured in another
way.
--
Mikael Abrahamssonemail: swm
-Optical conversion.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
and session teardown) but
S13 will have this behaviour changed if I understood correctly (and it's
already right in SY8).
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net
which
might get 32bit ASN (I don't have any concrete info though) would be
12.2SR-something or 12.4T.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
12.4 mainline should work well, I've used that in lab for IPv6
on 7500 RSP1 and VIP2-50:s. It has DHCPv6-PD etc...
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman
the process switching path.
If you just want to move packets, RSP720+67xx series line cards will do
just fine, plenty of grunt even without DFC.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
.
This works. Been there done, that plenty of times.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco
there will be no 12.0(33)S for GRP, just as you
stated.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
IPv4/IPv6
platform; if I run both protocols is the aggregate traffic limited by the
IPv6 specs?
No, you can change this, you have 1M total to play with, this is
partitioned between L2, L3 (IPv4/v6/MPLS etc).
--
Mikael Abrahamssonemail: swm...@swm.pp.se
nowadays.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
the previous version that's floating around as a PDF
(you have to do some googling).
It basically says the same thing, plus contains a lot of other excellent
suggestions.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco
free
at all times, it's sometimes needed during a re-route.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net
been that the routers are sending
packets with higher bitrate than the ATM network is policing cellrate to.
Make sure you have the correct UBR in your routers compared to what the
ATM network is policing the PVC to.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
On Wed, 10 Jun 2009, Paul Stewart wrote:
Which Cisco switches would be recommended to handoff approximately 20
Cat5 drops fed by fiber coming in?
3560/3750 seems to work well for this.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp
.
Which indicates a constant BER (bit error rate) which is consistant with
CD induced BER.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive
? I might be wrong
though, I can't get the whole article, google only displays from its
cache.
Is there a Cisco command to pull up the BER the optic is seeing?
No, on GE you can only see it by sending traffic and observing the error
counters.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
normally varies
by several milliseconds, and sometimes much more than that.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
accuracy, it just moves the decimal point.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
you get towards the customer?
Do you even get to the 7500?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net
the archives regarding full feed for Sup32. Basically it will
cpu-switch traffic to some prefixes.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
the smaller one, put in the equivalent other bigger one, check that
everything looks ok, then switch back to redundant mode.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman
to it at the
same time). Remember that 19200 serial only goes 10-20 meters in standard
form (very approximate, depends on serial hardware etc)
http://www.connectworld.net/interface-troubleshooting.html says even
less (20 feet).
screen -x is a wonderful collaboration tool.
--
Mikael
recommend:
mtu 1546 (or something else)
ip mtu 1500
clns mtu 1497 (if you run isis).
For a 7200 with FE ports this translates into:
mpls mtu 1546
Please see discussion regarding this from ~1 year back.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
On Wed, 29 Jul 2009, Robert Johnson wrote:
Suggestions?
Please provide output from show int switching (not tab-completable) to
verify that all traffic is cef switched.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list
of bug.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
be
good to verify that the one you're using doesn't have this problem.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http
load share on, but if you instead
have 10k flows and all of them are low-speed, then the odds of them being
equally load shared is much better?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
-
custport2 then I'd say you have control.
so do you typically use bpdufilter, only allow tagged vlans, not use vtp
- and this keeps things under control ?
Yes, I'd say so.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco
really like a release that supports mpls
tracroute.
Don't use mpls mtu, instead use mtu, ip mtu and clns mtu in
combination instead.
http://www.gossamer-threads.com/lists/cisco/nsp/97840
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp
.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
On Thu, 20 Aug 2009, Michael K. Smith - Adhost wrote:
Does anyone know what happened to the 12.0S GRP images? The software
navigator only shows PRP images.
GRP(-B) is end-of-life and considered obsolete.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
hardware such
as SPA-TENGE-V2 and it has a few more features such as mpls ldp igp sync
for ISIS.
Generally for the SY train has been early introduction of features,
historically MPLS was available there first for instance.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
/quickreference/routerperformance.pdf
You could probably look into the 1841 as well, it should be enough for
your 20 megabit/s need.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https
will
create performance problems in real life.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
multiple
vlans per IP subnet, so you get L2 isolation between customers but you do
not waste any IP addresses.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo
1 - 100 of 416 matches
Mail list logo