ter incoming routes. That way your session is still up.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
--- End Message ---
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.n
semi-unstable state where some traffic is dropped/unusable, and can
only be fully recovered by reboot.
My advice is "don't let that happen".
--
Mikael Abrahamssonemail: swm...@swm.pp.se
--- End Message ---
___
cisco-nsp mai
On Sun, 12 Aug 2018, ring...@mail.com wrote:
It also selects a public server which is outside of your AS thus taking
into consideration the busy international links which are outside of
your administration andas a result for a 30Mbps package the measure
shows 15 for example.
My experience is
was important to use features that were CEF enabled,
otherwise performance would go down a lot.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco
On Thu, 14 Sep 2017, Harry Hambi - Atos wrote:
HI All,
Logged onto a ASR9k and trying to find commands to show me the following :
BSR router
"show pim bsr", there are multiple commands under that.
Where pim is enabled.
"show pim interface"
--
Mikael Abrahamssonema
, I just want to roll back to it
Any help?
You need to re-install IOS XR. The re-install procedure is called "turbo
boot".
https://supportforums.cisco.com/document/123576/asr9000xr-understanding-turboboot-and-initial-system-bring
--
Mikael Abrahamssonemail: swm...
ature-rich edge/core features mean you
need platform that supports this. If you keep down the features required,
you typically have more platforms to choose from.
But yes, I agree, the type of traffic you're expecting worst-case dictates
what platforms you can choose and how to use the
e is less and less focus on them, probably meaning
significantly higher cost compared to the gear coming out that caters to
the "less-complicated" networks.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.n
regarding BFD is not acceptable.
--
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/
r for the
problem description?
--
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/
If I remember correctly, this works in accelerated mode as long you have a
unique IPv4 address per tunnel endpoint.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/lis
On Fri, 12 Aug 2016, Nick Hilliard wrote:
you're very brave with your iphones. Shining a laser on a CMOS sensor
doesn't seem like a smart thing to do.
Smarter than looking into laser with remaining good eye.
--
Mikael Abrahamssonemail: swm...
usage dropped to (let's say) 95% again. The
problem would only be solved by reboot. Is this still the case?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/list
What version of XR are you trying to do this with?
--
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/
ped.
If there were some L2 switches in between the PE and CE, then it/they
might have dropped it.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
that does optical within a
chassi.
It seems there were copper advancements in the meantime that made copper
still scale well for backplane connectivity, and that's why existing
vendors have kept using copper traces switch fabric connectivity instead
of going optical.
--
Mikael Abrahamsso
configuration handling.
I prefer that the vendor does a proper job. We'll see if XR 6.x actually
is properly done, or if it's just failed promises again.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list
x27;ve been told XR 6.x will have a new package handler, I am curious to see
if that actually fixes a lot of the problems. I kept stating to people
involved with XR that the Debian apt tool was better in 2000 than the
package handling in XR in 2014.
--
Mikael Abr
erly tested SRs instead of SMU-hell.
--
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/
as due to level of testing and that they were in different BUs back
then.
--
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://
f you want something that works,
wait 1-2 years after first customer shipment and try it, then it usually
works. Now, at that time it's not fast and cheap anymore...
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list
s
most of the complexity and dynamic inspection stuff, you could even have
static ACLs on each subinterface/port if you want to.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.n
and IPv6) connectivity. Limit
your broadcast domains (I'd say 20-50 users per broadcast domain), and
make sure you do antispoofing (BCP38) for everybody.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.ne
e/software that is going to be supported for a lot longer time.
--
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
boot with old IOS.
A newer bootloader can always load an old IOS, so keep your existing boot
loader, especially with the above versions which are both fairly recent
(and not 15 years old).
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco
per-packet
loadbalancing on?
--
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/
With the kind of router that ASR9k is, you most likely find it under
support if it works ok, otherwise it's not mentioned at all.
Re-assembly of fragmented packets is typically something that routers do
not do. As soon as you need to keep state across packets you need a fairly
differe
. Reverse on the other side and it "should" just work.
I doubt it. That device seems to do 3R which means it does not look past
individual bits, and it can't do speed conversion (because that would
require media insight).
So it means it can do MM to SM for 8G but it won't do 8G
seen as "input drop".
Also, I am curious behind your reasoning for the carrier delay settings
(I'd say they are backwards to what I would configure), and why are you
using flow control?.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
__
memory and different platforms work differently.
--
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/
cost of a router that can do full DFZ
routing table.
--
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
B
•256 MB
--
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/
.
So my question now is, is there a boot variable I can set to make XR
either format or completely "clean" disk0: on secondary RP after initial
boot? I know this can be done with turbo-boot, but I haven't been able to
find anything on how to do this if I don't want to turbo-
er interfaces to form PIM neighborship, plus
configuring "version" directly under "router mld".
This way it seems I get away from having interface-unique entries under
router pim and router mld.
I still don't understand why the design choice to require PIM to be
running o
plane stops
the forwarding of this multicast group without PIM enabled on the
interface. I just don't understand why.
Could someone please enlighten me?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@p
ot; on your code base. You can't use both it seems.
--
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/
different origin ASs for a
short time ?
What are your suggestions ?
I would contact my upstream just like you say, and also add their new AS
to the route-object so the route-object has two ASes mentioned in it.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
). Traffic now flows according to BGP routing.
Change route object.
In case someone has a problem with the route object, your encompassing
larger prefix is going to make sure you get the traffic anyway.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
channel and the interface retained the
information that was applied by being a member of the port channel this
caused a loop. Don't want to repeat this.
Are you running LACP or not?
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing
igure "mpls ip" on.
--
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/
our terminology. "cloud interface"? "VLANs interface"?
Please post config.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive
particulars details to consider when
implementing MPLS with ME-3750-24TE-M. How am i supposed to do.
Apart from that they have very little RAM and forwarding table, everything
is fine :P They're very restricted, make sure you test them properly for
your scaling needs.
--
Mikael Abrahamsson
nters at each
end, make sure there is no policing of traffic anywhere, etc.
There is no obvious culprit from what you have described so far, the
solution you described should have worked, at least up to 70-90 megabit/s
of actual TCP througput.
--
Mikael Abrahamssonemail: swm...@swm.
esults are contradicting.
--
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/
ying isn't
supported.
--
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 asdot notation?
--
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-VRF-Lite.html
--
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/
s the IOS linked to the serial of the router itself ?
There is no binding of software version to serial number of chassi, so
just take the software you already have and apply to them.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cis
l RPs, then it'll do both at the same
time.
--
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/
rule the world, you want
compromise between the camps, that's when good balance usually happens.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cis
rs the vendor didn't think about,
but it also helps to know what application the vendor thought the
equipment would be used in, in order to understand why things are the way
they are.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-ns
he 10km.
When 40GE and 100GE was standardized it was taken for granted that 40GE
would be used to connect servers and perhaps a little inter-building
backhaul, because of that only up to 10km was standardized.
If you want longer reaches, you have to do 100GE.
--
Mikael Abrahamssonemail: s
olutely nothing in common with the ASR9k, ASR5k or ASR90x
platforms (which each of them have nothing in common with each other, ASR
is just a marketing name).
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.n
o use ECMP instead (have two links with separate
IPs on them) and see if that works better.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archi
15.2M (latest) will boot on NPE-300 with 256M of ram (with warning saying
it's not supported), but there isn't much memory to spare for routes.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.n
s end-of-software
development in sep 2011. However, hardware support is available until Sep
2015.
Also, they are still releasing images (probably because NPE-G1 runs same
code). 15.2M and 15.2S seems to be the last images made for it. Last image
available is from september 2013 anyway.
--
M
.
c7200-advipservicesk9-mz.152-4.M4.bin for instance work just fine on
NPE-400 and is supported.
To original poster, you probably want 512M of ram on it. It'll use approx
130-150W of power.
If you need full tables, get NPE-G1 with 1G of RAM.
So +1 on the 7200 recommendation for
.com/en/US/partner/docs/routers/asr9000/software/asr9k_r4.3/addr_serv/command/reference/b_ipaddr_cr42asr9k_chapter_010.html>.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.ne
On Thu, 28 Nov 2013, Bill Blackford wrote:
My experience with Cisco IPv6 is limited but I believe you can't even
configure a v6 address until you have the IPv6 SDM template loaded.
You don't need to have an IPv6 address on an L2 switch, to L2 switch
0x86dd ethertype frames.
but it's doable.
5-10 years ago it was possible to do bug scrubs based on information on
CCO. This is no longer possible, now one needs to pay advanced services
for their NOS service to be able to do it, just because the customer
accessable information just isn't complete enough.
. Only
by customers complaining will we see improvement.
--
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
omers who are no
longer customers can end up being transited to your network because you
now receive the prefix via a peer, but still announce it to your transits.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisc
On Thu, 24 Oct 2013, naresh reddy wrote:
will they charge us for the traffic that we pump and pull to internet on per MB
basis ??
if so what would be the cost
No, they will not charge you for traffic.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
On Wed, 28 Aug 2013, Jeff Kell wrote:
On 8/28/2013 10:46 PM, Mikael Abrahamsson wrote:
Think of 15.x as 12.(5+x). There isn't that mcuh different when it
comes to commands, it's mostly under the hood and of course new
functionality.
Is that true on the 6500?
Yes.
--
Mikael A
every service in IOS15. I
am particularly interested in the differences in IOS 15 command line.
Think of 15.x as 12.(5+x). There isn't that mcuh different when it comes
to commands, it's mostly under the hood and of course new functionality.
--
Mikael Abrahamssonemail: s
" if you really need to force duplex.
--
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/
rt is no longer wire speed and the loss you're seeing would be
understandable.
Any ideas? And would QOS tuning be likely to help?
QOS is a way of selecting what packets to drop. I don't see how it would
help here.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
yes, hw failure.
--
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/
der-advanced-technology-class/ipv6-over-mpls-with-102.html>
I managed to watch one of them, then it requires registration (so I can't
watch this one). If it's as good as the one I watched, it should be
worthwile for the topics in this thread.
--
Mikael Abrahamssonemail:
On Sat, 22 Jun 2013, Ahmed Hilmy wrote:
But i dont have MP-BGP between IGW & RR, I have pure BGP IPv4.
So ?
You said it was a PE so I presumed it was an MPLS speaker.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing
On Sat, 22 Jun 2013, Ahmed Hilmy wrote:
Can i add address family IPv6 at IGW to advertise IPv6 routes to RR,
since it is directly connected ?
Sure. I would configure send-label there as well so that you do thing in a
consistent manner, but that's a matter of opinion.
--
Mikael Abraha
On Fri, 21 Jun 2013, Ahmed Hilmy wrote:
What do u think ?
I don't have experience with mixing 6PE and native so I can't offer much
advice in this case. I also do not know what IGW is.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
6
unicast but you add "send-label".
--
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/
"send-label".
--
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/
ceiver%20Challenges-ECOC2012-ChrisCole.pdf>
might be interesting to read if you want to see where things are and where
they're headed for the future.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puc
rovide more headroom in the event of one of the modules
failing. Apparently V1 can just about do a fully loaded chassis with 2
modules.
My bad. Yes, I knew about the power shelves/supplies, just didn't know
that they were reflected in the chassis ID as well.
--
Mikael Abrahamsson
On Thu, 20 Jun 2013, Mattias Gyllenvarg wrote:
Dear List
What is the difference between the chassie versions?
Is the V2 just a hardware revision?
V2 is probably the uprated FAN array, which means you can have DWDM optics
in all slots in a 24x10GE card.
--
Mikael Abrahamssonemail: swm
eue shape 100 150 200
--
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/
t sure where the initial 9097 comes from though.
If you configure main interface mtu 9114 on ASR9k and 9100 on IOS,
it should just work out of the box, no need to adjust clns mtu or any
other protocol MTU.
Both Juniper and IOSXR includes the 14 byte ethernet header in the MTU
calculation. IOS do
isco is that this is appreciated. Basically release all fixes
in a rollup SMU pack every 3 months, mimicking the way IOS used to work,
releasing a new fix release every 3-4 months.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mai
to Intels tick/tock approach, they develop new
architecture one step and new manufacturing technique the next step, then
new arch again. Not both at the same time.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@pu
there is hope that things are improving with 4.3 and later
releases.
--
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/
rying to say here.
Anyhow, I apply the same logic here as I do in IOS-land. You start to get
on 12.0(32)SYx when X is above 3 or 4. Same with SRE for 7600, SRE4-5 or
so started to be ok.
Cisco is not alone in this, I'd say most vendors have similar problems.
--
Mikae
ou wait at least 6 month after major release if you
want stable software.
--
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.
have no graceful restart configured. Please talk
to your account team and ask them to talk to the BU and get them to fix
this.
Desired behaviour:
On a dual RP system, advertise yourself as GR capable.
On a single RP system, only do GR "helper".
Either auto detect this or make it configurab
t 30, 2013
---
This is the date they should be looking at.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archi
On Wed, 24 Apr 2013, Lee Starnes wrote:
would have any issues with this or if it's only difference is the
ability to do POS.
I was under the impression that the WL did 10GE WANPHY (and LANPHY), not
POS.
POS is not Ethernet.
--
Mikael Abrahamssonemail: swm...@swm.
On Thu, 18 Apr 2013, gu...@golas.ru wrote:
Try to use another version 4.2.3 with SMUs.
4.2.3 with SMUs seems stable. There are still some bugs, but nothing
causing catastrophic failures (with smupack 2 released end of January).
--
Mikael Abrahamssonemail: swm...@swm.pp.se
omising as well.
--
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/
bidirectionally.
--
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/
SIP will carry only 10 GE ( IN + OUT ) ... ?
Would you please share your experience about this isue.
A SIP-601 will do ~11-12 gigabit/s of througput, full duplex. By inserting
two 10G SPAs you've overbooked the SIP by almost a factor of 2. There is
no local switching I'm aware of.
to a pcap file and
open this is wireshark and to a TCP stream analysis so you can actually
*see* what is going on.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman
On Tue, 2 Apr 2013, Aaron wrote:
Any assistance is appreciated
"show controller dwdm 0/0/0/0" both ends.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailma
on the servers and look
for packet loss. Wireshark has excellent TCP analysis tools that can show
you exactly what's going on, if the problem is maxed out TCP windows or if
it's caused by TCP saw-toothing due to packet loss.
--
Mikael Abrahamssonemail: swm...
omes to netflow. For "Internet peering router at 10GE with typical
eyeball traffic" my opinion is that 6500/7600 doesn't have working
netflow.
I'm sure there are use cases where 6500/7600 netflow works just fine, but
not in the scenario a lot of poeple seem to want to use i
was released in january with the bug still in
"review" yesterday.
--
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 really need, and probably skip some
nice-to-have ones.
--
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 Sun, 10 Mar 2013, Gordon Bryan wrote:
Also, even in a completely private core, a PE still becomes exposed to
the outside world on its PE-to-CE interface when delivering Internet
services. Has anyone developed any proficient methods for locking down
these interfaces and making them unrespons
ethods are there for controlling routed multicast?
--
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/
lking about was "Internet" multicast, ie multicast between
ISPs. Watching NASA multicast streams for instance (I did this at my
university in ~1995). Very few commercial ISPs support this.
--
Mikael Abrahamssonemail: swm...@swm.pp.se
__
1 - 100 of 446 matches
Mail list logo