Yes, but IPv6 PBR is not, in that release. =(
Frank
From: Manu Chao [mailto:linux.ya...@gmail.com]
Sent: Tuesday, June 21, 2011 1:49 AM
To: frnk...@iname.com
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] Platform feature development for 7200
Right, but DHCPv6 Relay Agent notificat
LinkedIn
Fahad Ali Khan requested to add you as a connection on LinkedIn:
--
Vishal,
I'd like to add you to my professional network on LinkedIn.
- Fahad
Accept invitation from Fahad Ali Khan
http://www.linkedin.com/e/-bfctb5-gp7qs7
On Mon, Jun 20, 2011 at 11:31:31PM +0200, Gert Doering wrote:
> Standard Vendor answer #714: "what is this IPv6 thing?"
"no customer other than you is asking for that"
My all-time fav.
Best regards,
Daniel
--
CLUE-RIPE -- Jabber: d...@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
Hey Everyone:
Here is the configuration. It's in the 12.1 train IRC. This was from a
long-ago blog post, so there are some comments in at and the v6 ACL might
be out of date. All the IP's (v4 and v6) are RFC document ranges.
! BEGIN
!
!
dot11 ssid myssid
authentication open
authentication key-
Hi,
On Tue, Jun 21, 2011 at 04:47:17PM +, Michael K. Smith - Adhost wrote:
> You can do IPv6 on the 87x series, it's just kludgy. You have to use a
> separate /64 for the wireless and attach it to the VLAN interface, while
> leaving the IPv4 address on the dot11Radio interface.
>
> If anyone
On 6/21/2011 12:31 PM, ryanL wrote:
there is indeed ISSU for VSS, even with single supervisor models.
There is indeed no ISSU on 6500. What you are referencing is FSU or eFSU.
I would suggest you get a product brief from your Cisco team or your
preferred vendor/reseller.
i
recently upgraded
* Murphy, William [2011-06-21 12:43:24-0500]:
>
> We have been using L3 access for a couple of years and it does work quite
> well, but we are migrating away from it due to the fact that IPv6 forwarding
> in hardware is not doable on our access-layer switches, and it'd cost a
> bundle to upgrade e
We have been using L3 access for a couple of years and it does work quite
well, but we are migrating away from it due to the fact that IPv6 forwarding
in hardware is not doable on our access-layer switches, and it'd cost a
bundle to upgrade everything. For one of my larger buildings, upgrading to
there is indeed ISSU for VSS, even with single supervisor models. i
recently upgraded from sxi2a to sxi6 with no noticeable impact if you
do it right. that said, you do lose 50% of your cluster capacity. so i
guess it depends on your interpretation/requirement for ISSU ;-)
on the flip, i can attes
On 21.06.2011 20:12, Seth Mattinen wrote:
On 6/21/11 4:18 AM, Gert Doering wrote:
Hi,
On Tue, Jun 21, 2011 at 08:41:13PM +1000, Reuben Farrelly wrote:
It's a platform dependent "feature", primarily on the newer ISR G2s and
880s/890s. The original ISR's, 870s, 7200 etc have no such enforceme
You can do IPv6 on the 87x series, it's just kludgy. You have to use a
separate /64 for the wireless and attach it to the VLAN interface, while
leaving the IPv4 address on the dot11Radio interface.
If anyone would like to see a working configuration let me know and I'll
send it offlist.
Mike
On
On 6/21/11 4:18 AM, Gert Doering wrote:
> Hi,
>
> On Tue, Jun 21, 2011 at 08:41:13PM +1000, Reuben Farrelly wrote:
>> It's a platform dependent "feature", primarily on the newer ISR G2s and
>> 880s/890s. The original ISR's, 870s, 7200 etc have no such enforcement
>> under either 12.4 or 15.X.
>
If you see this happening a lot it could be a HW issue... I would
suggest working with TAC on this one.
Arie
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Righa Shake
Sent: Tuesday, June 21, 2011 13:56
To: cisco-nsp@puck.
Hi,
On Tue, Jun 21, 2011 at 08:41:13PM +1000, Reuben Farrelly wrote:
> It's a platform dependent "feature", primarily on the newer ISR G2s and
> 880s/890s. The original ISR's, 870s, 7200 etc have no such enforcement
> under either 12.4 or 15.X.
... yet.
gert
--
USENET is *not* the non-clicka
HI,
Am getting the following error on my logs from POS need assistance in making
heads of what it means.
%CMCC-3-PLIM_STATUS: SIP0: cmcc: A PLIM driver informational error SPA0 L2
protocol field offset past packet EOP, block 1b count 7
Thanks,
Righa Shake
_
Common misconception - IOS 15 didn't introduce enforced licensing, but a
number of new platforms which ship with 15.X *did*.
It's a platform dependent "feature", primarily on the newer ISR G2s and
880s/890s. The original ISR's, 870s, 7200 etc have no such enforcement
under either 12.4 or 15.X
hi
i have a device generating traffic connected to Cisco 7606-S via port channel
the device interfaces configured with MTU 1400 and tcp mss enabled on
the configuration from Cisco side is as below (i have port channel contains 5
physical G interfaces and assigned to SVI)
CR1.KJ-Building#sh ether
If you talking about new licensing scheme, then no 7206VXR use old
licensing scheme same as for 12.4
On 21/06/11 10:45, LM wrote:
Does the 15.x IOS needs the licenses to work under the 7206VXR?
I am a bit confused.
___
cisco-nsp mailing list cisco-n
18 matches
Mail list logo