Re: VSS and PFC3A

Thanks Martin,

That's very interesting, and something I will keep in mind for my
customers (they currently are not running modular code).
You are right about the savings, I normally don't use IP base (nor the
Cisco bundle) and go for Advanced IP Services to get the required
functionality.

regards Andy

Martin Kiefer wrote:
> BTW I noticed a stange thing last week, did a VSS configuration on a pair
> of 6504-E running SXI2 IP Base non modular software. The problem was that it
> did not have the OPSF, I got a "Protocol not in this image". I then changed
> the software to SXI2 modular instead. Now I can do both OSPF and BGP and
> still only in IP Base. I gues my customer just saved 2x 10.000 USD for the
> IP service software. Anyone who knows why OSPF and BGP is in the modular
> version and not in the non modular?
>
> /Martin
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Lucas, David
> Sent: 7. august 2009 01:06
> To: Sharifi, Reza; Martin Kiefer; GS CCIE-Lab
> Subject: RE: VSS and PFC3A
>
> I know exactly what you mean. In the VSS deployments I've done I've
> been lucky to have 4948s that I've used for dual active detection.
>
> As for the 3750 cross stack support, I haven't heard that this was going
> to be supported but you never know. You can always call TAC to confirm
> this if you find out anything let us know!!
>
> This is what they said in the same class at networkers about just this
> issue:
>
> "PAgP is supported in all platforms except 37xx stack configuration
> where cross-stack
> EtherChannel (LACP) is required to have MEC connectivity with VSS. Since
> cross-stack
> EtherChannel does not support PAgP, it cannot use enhanced PAgP for dual
> ACTIVE detection. Two solutions to the stack-only access-layer:
> Use Fast Hello or BFD as a dual ACTIVE detection method ePAgP can be
> enabled either on L2 or L3 PAgP MEC members. This means one can run
> ePAgP between VSS and core routers (though core routers require SXH1 or
> later)"
>
> Another thing to note, is the VSL under normal operation shouldn't carry
> data traffic over it. In MEC data traffic is forwarded to the local
> members of the EtherChannel bundle. If all local links fail in the
> EtherChannel bundle then data traffic will traverse the VSL. Think of
> normal operation as North to South, there is very little east to west
> that happens. This is partly why its suggested that everything
> connected to the VSS should use MEC.
>
> David Lucas
> CCIE No. 21272
>
> -----Original Message-----
> From: Sharifi, Reza [mailto:Reza.Sharifi_at_gdit.com]
> Sent: Thursday, August 06, 2009 5:46 PM
> To: Lucas, David; Martin Kiefer; GS CCIE-Lab
> Subject: RE: VSS and PFC3A
>
> David,
>
> Do you know when or in what version of the IOS for the 3750s the Multi
> chassis ePAGP will be implemented? Currently ePAGP is supported using a
> single 3750 not MCE. So, if you have 2 3750s stacked and each 3750 has a
> single 10 Gig uplink to a pair of VSS, you can not use ePAGP for dual
> active detection.
>
> Another word, if your uplinks are coming from one 3750, you are fine,
> but if coming from 2 different stacked 3750s, you can not create an
> EtherChannel.
> Thanks,
>
> Reza
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Lucas, David
> Sent: Wednesday, August 05, 2009 9:53 PM
> To: Martin Kiefer; GS CCIE-Lab
> Subject: RE: VSS and PFC3A
>
> Per the Breakout Session at Cisco Live (BRKRST-3035)
>
> "Diversify VSL bundle on separate line card and port, just like any
> resilient EtherChannel design. The VSL link port location also affect
> the QOS configuration on the other supervisors ports.
>
> Design 1 uses both 10G ports on supervisor which does not provide
> hardware diversity as both ports are connected to single internal fabric
> connection.
>
> Design 2 offers a practical solution where the cost is more influential
> then flexibility. Design 2 uses one port from Sup720-10G uplink and
> other from WS-X6708 line card. This design limits unused ports on
> Sup720-10G with default CoS based queuing. 12.2(33)SXI removes this
> restriction
>
> Design 3 is recommended if full flexibility of QOS configuration is
> required. This option avoids using Sup 720-10G uplink ports and uses two
> separate WS-X6708 line cards for VSL links but not as cost effective as
> option 2 or 1"
>
> David Lucas
> CCIE No. 21272
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE: The contents of this email, all related
> responses and any files and/or attachments transmitted with it are
> CONFIDENTIAL and are intended solely for the use of the individual or
> entity to whom they are addressed (or authorized to receive for the
> addressee). This email may contain legally privileged information and
> may not be disclosed or forwarded to anyone else without authorization
> from the originator of this email. If you have received this email in
> error, please notify the sender immediately and delete all copies from
> your system.
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Martin Kiefer
> Sent: Wednesday, August 05, 2009 11:18 AM
> To: 'GS CCIE-Lab'
> Subject: RE: VSS and PFC3A
>
> SXH does not support any service modules in a VSS setup, there you will
> need
> SXI and if you will be using the new 10G sfp modules you will need to
> run at
> least SXI2 software.
>
> Btw I have seen some using the 6708 and 6716 10G modules for the VSS
> link.
> Can anyone explain why you would do that?
>
> I always just use both of the 10G links in the supervisor, some would
> say
> that this is for redundancy, but where is the redundancy in this?
>
> Best regards
> Martin Kiefer
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> Reza
> Toghraee
> Sent: 4. august 2009 19:12
> To: 'KRATTIGER Lukas'; 'Andy Reid'; 'Ram Shummoogum'
> Cc: ccielab_at_groupstudy.com
> Subject: RE: VSS and PFC3A
>
> Correct,
>
> I have a VSS pair, with WS-X6748 with CFC.
> The only problem which I faced was the IOS, which must be SXI, not SXH.
> SXH
> does not support FWSM modules in VSS.
>
> Regards
> Reza
> CCIE R&S
>
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
> KRATTIGER Lukas
> Sent: Tuesday, August 04, 2009 7:56 PM
> To: Andy Reid; Ram Shummoogum
> Cc: ccielab_at_groupstudy.com
> Subject: AW: VSS and PFC3A
>
> Hi Andy
> This is not correct.
> Only the cards with VSL on it need to have DFC3C and the Sup has to be
> PFC3c.
> All the rest has to be a 67xx-Linecard but no matter if CFC or DFC3c.
> Important is, if DFC, it has to be 3c.
> Cheers
> -Lukas
>
> ________________________________
>
> Von: nobody_at_groupstudy.com im Auftrag von Andy Reid
> Gesendet: Di 04.08.2009 16:47
> An: Ram Shummoogum
> Cc: ccielab_at_groupstudy.com
> Betreff: Re: VSS and PFC3A
>
>
>
> Hi Ram,
>
> Yes, you have to have PFC3C to run in VSS mode. In addition, all modules
> equipped with DFC's must also be DFC3C.
>
> http://www.cisco.com/en/US/partner/prod/collateral/switches/ps5718/ps933
> 6/pr
> od_qas0900aecd806ed74b.html
>
> regards Andy
>
> Ram Shummoogum wrote:
>
>> Hi:
>>
>> Do you think I can convert my 6500 series to VSS with a PFC3A on my
>>
> sup.
>
>> Or do I absolutely need the PFC3C or PFC3CXL.
>>
>>
>> Thanks
>> Ram
>>
>>
>> Blogs and organic groups at http://www.ccie.net <http://www.ccie.net/>
>>
>
>
>>
> _______________________________________________________________________
>
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>
>
> Blogs and organic groups at http://www.ccie.net <http://www.ccie.net/>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 4305 (20090804) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature
> database 4305 (20090804) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sun Aug 09 2009 - 18:45:48 ART