09-30-2016 12:05 AM - edited 09-30-2016 12:10 AM
my task is to configure a VCS fabric with two VDX 6740 and four VDX 6746 ( Hitachi CB 500 DCB switch module ).
In order to form a logical chassis cluster, the same version of NOS must be installed: now, we can't get past version 4.1.3a in VDX 6746 because isn't supported by vendor.
Do you agree with the downgrade of the VDX 6740 firmware from v6.0.1a to 4.1.3a, in order to have the same version in all switches?
Are there better options?
Suggestions are welcome.
09-30-2016 12:36 AM
you can downgrade the 6740 to NOS 4.x, but as fair as I remember, you cannot form a VCS Fabric as logical chassis cluster between/with preview eAnvil ASIC.
If I'm wrong, then ignore please this post.
09-30-2016 01:05 AM
You can form a logical chassis between VDX6740 and VDX6746 (which uses the same ASIC as the VDX6720 - 1st generation boxes).
My initial instinct would say that this is probably not the best approach but it depends on what is important to you. If your priority is to create a single logical chassis with single management IP across the chassis then you can do it.
But you will be stuck then on the VDX6740s and limiting their functionality to whatever is available in 4.1.3.
A more flexible approach would be to form two node clusters of the VDX6746 switches within the CB500 chassis and then link them into the VDX6740s using vLAGs defined on the core fabric (VDX6740) and the edge fabrics (VDX6746)
This would result in you having to configure more fabrics but would provide a more future proofed solution.
09-30-2016 01:16 AM
-->>You can form a logical chassis between VDX6740 and VDX6746 (which uses the same ASIC as the VDX6720 - 1st generation boxes).
I'll not insist, but allow me please to ask, and sorry my stupid question: Are you sure 6740 and 6746 use the same ACIS as 6720 - 1st Ge ?
from NOS Brocade Release Notes 5.x and above
->...previous-gen ASIC (eAnvil) based platforms. These include VDX 6710, 6720, 6730 and 6746.
as per my understand 6710/20/30/46 are Based on preview-gen ASIC, where 6740 is not.
and in feew word this is not the same ASIC generation.
But as saied, is probable I'm a bit stupid.
09-30-2016 01:39 AM
Thank you Steve.
Your approach could be a good balance.
We aren't committed to set up a logical chassis for the sole purpose of having a single administration IP: it seemed to me a more appropriate configuration for AMPP feature with vCenter.
I mean that in fabric cluster layout, I have to put vCenter credentials in every switch, six times... and when we'll join to the other site with a DWDM, they will become twelve...
Following your reasoning we can decrease the administration points from six to two, retaining some fabric benefits by using vLAGs instead of ISL trunks between VDX 6740 and VDX 6746.
Well, it looks good.
09-30-2016 01:45 AM
Thank you Antonio.
Given my situation, what would you have done? Keep NOS 6.0.1a and setup multiple logical chassis as Steve suggested?
09-30-2016 01:58 AM
to be honest, I'm nut sure, for a simple reason as I written in my preview post, and from a point of view VCS config
( from you native post !! ) AFAIK such a config is not supported between different ASIC generation.
And both Platforms - concord Brocade DOC - have definitively different ASIC, and not the same.
09-30-2016 02:16 AM
To be clear - in your post you are suggesting that you cannot form a logical chassis between a VDX6746 and a VDX6740.
Regadless of this my suggestion is to not form a single logical chassis and instead use vLAG between the VDX6746 and the VDX6740s as this would leave Marco free to use the newer features in later NOS releases. I think it was this that Marco was asking about and whether you saw any issues with that.
As Marco says, if they are using vcenter discovery feature with AMPP then you would have to configure this feature on all of the fabrics.
09-30-2016 02:36 AM
->...your post you are suggesting that you cannot form a logical chassis between a VDX6746 and a VDX6740.
sure and you are probable absolutely correct.
however my main statement was related to different ASIC between the Platforms, that for first!
continue..... I wrote follow:
->...you cannot form a VCS Fabric as logical chassis cluster between/with preview eAnvil ASIC.
-> If I'm wrong, then ignore please this post.
AFAIK any VCS Fabric / logical chassis for some restrictions is not supported between different ASIC
and I don't want to insist or create any confusion if this is possible/supported or not.
but i insist that both generation of Platform use different ASIC