> > Mostly folks were using these for Route reflectors I think.
>
> That's what we do. Works like a charm, over 12x months now.
In this application how low bandwidth license can you get away with in
practice? Do the bandwidth license limits apply to both routed
traffic and control-plane traffic (
>
> I think the LAC will always send those two requests and will take what it
> likes better; in this case, a good old non-L2TP PPPoE.
>
> Don't use the same radius server for LAC and LNS, or at least, make sure
> testu...@example.net authenticates only when the NAS is the LNS, but not
> when the L
Now I appreciate that's a good incentive for
customers to migrate to IPv6 but I'd rather have the control :-)
--
Steve Glendinning
___
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/
>
> I have two 7204VXR with NPE-G2 running 15.2(4) S3 for some time. It's
> doing BGP, but no OSPF, but it's been very stable.
>
15.1(3)S3 is also very stable for us on both NPE-G1 and NPE-G2.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https:/
For a reference point, gigawords work well on 7200 15.1(3)S4.
Also this release is good for RFC4818 Delegated-IPv6-Prefix RADIUS
attribute. This tidied up our RADIUS database no end.
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.net
Hi all,
I've enabled 6PE on some of our rsp720-3cxl's (running SRE8) that carry
full global routes, and it appears to have allocated a separate MPLS label
for each IPv6 prefix in BGP (approx 16,000 of them). Consequently this is
chewing up significantly more FIB space, as each (global) IPv6 prefi
+= "lcp:interface-config=service-policy output
POLICE-10Mbit"
But alas, policing only applies to the ipv4 traffic. Ideally I'd like
the policer to apply to everything on the interface, such that both
IPv4 and IPv6 are policed. Any ideas if this is possible?
Thanks!
--
Steve Gl
7600 platform for IPv6
netflow?
Thanks in advance,
--
Steve Glendinning
Net That Works
___
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/
Hi all,
I'm resurrecting this old thread to record my progress for the archives.
Hopefully this will spare someone else a day of head scratching.
It turns out that the following RADIUS attribute prevents multilink from
establishing a bundle:
Cisco-AVPair += "ipv6:prefix#1=2A02::
configure 5
ppp max-bad-auth 3
ppp authentication chap pap callin
ppp multilink
ppp timeout retry 15
ppp timeout authentication 15
--
Steve Glendinning
___
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-n
LNS, and all the attributes are coming through as expected
so I don't think this is the problem.
--
Steve Glendinning
___
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/
no joy:
Cisco-Avpair = "multilink:max-links=2"
Cisco-Avpair = "multilink:min-links=1"
Cisco-Avpair = "multilink:load-threshold=10"
Cisco-Avpair = "preauth:ppp-multilink=1"
Thanks,
--
Steve Glendinning
___
cisco
12 matches
Mail list logo