SRX

Hello,

Is there any issues with running mixed SPC2 and SPC3 cards simultaneously on the SRX 5800 cluster? My customer

is currenlty running four SPC2 cards on each member of the HA and their plan is to add the new SPC3 card to the lowest numbered slot on the chassis, to ensure this card takes charge of the CP

functionality. 

They will also be running the EWF and SSL proxy feature once the new card is installed. Would there be any performance limitation, we should be concerned of with running SPC2/SPC3 cards

together? Would love to hear the feedback if you are running SPC2/SPC3 card together or if you have knowledge in this domain.

Thanks,

B

Hello Bjncp,

Greetings,

Please find below link which can help you understand which cards are supported on the SRX5800 Cluster.

Cards Supported on SRX5400, SRX5600, and SRX5800 Services Gateways:

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/topic-map/srx5800-line-card-modules.html#id-cards-supported-on-srx5400-srx5600-and-srx5800-services-gateways

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/topic-map/srx5800-line-card-modules.html#id-cards-supported-on-srx5400-srx5600-and-srx5800-services-gateways

There are certain conditions which you to note while running SPC 2 and SPC 3 simultaneously on the same same cluster.

The link gives which when to use both SPC's and what is the requirement for RE and CB while using both SPC's.

I hope this helps. Please mark this post "Accept as solution" if this answers your query.

Kudos are always appreciated! 

Best Regards,

Lingabasappa H

Hi B,

The SPC3 card enables performance and scale with backwards compatibility to the SPC2 service cards but you might want to consider RE/CB compatibility as well. These SPC3 cards support in-service software and in-service hardware upgrades.

Refer Figure1:  Interoperability Matrix for SRX5400, SRX5600, and SRX5800 Services Gateways

https://www.juniper.net/documentation/en_US/release-independent/junos/topics/topic-map/srx5800-line-card-modules.html#id-cards-supported-on-srx5400-srx5600-and-srx5800-services-gateways

If my understanding is right, SPC3 card requires Junos OS 18.2R1-S1 or greater. You should be considering that as well. 

Also, I believe running SSL/EWF should not be a problem unless the interoperability of hardware is maintained. 

Hope this helps 🙂

Please mark "Accept as Solution" if this answers all your queries.

Kudos are always appreciated 🙂

SPC3 and SPC2 interop in chassis cluster is supported starting 18.4R1. 

https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/18.4/jd0e15343.html#jd0e15506

SRX5K-SPC3 card with flow support in chassis cluster mode (SRX5400, SRX5600, and SRX5800)—Starting in Junos OS Release 18.4R1, the SRX5K-SPC3 and SRX5K-SPC-4-15-320 (SPC2) cards can operate together in a mixed-mode configuration on the SRX5000 line of devices using the same slot number in both nodes. If you are adding the SPC3 SPCs to the SRX5000 devices, you must install the new SPCs in the lowest-numbered slot of any SPC that provides central point functionality. SPC3 interoperates with the SRX5000 I/O cards (IOC2, IOC3), Switch Control Boards (SCB2, SCB3), Routing Engines, and SPC2 cards.

For an SPC3/SPC2 Mixed Mode, CP is always in SPC3. SPC3 needs to be installed in the lower number slots (starting the first slot) as you have mentioned.​
Also, system assigns cores to CP and SPU based on the number of SPC2/SPC3 ​in the chassis.
CP will work on combo mode if there are 1 or 2 SPC3 cards, and CP will work on full CP mode if there are 3+ SPC3 cards, it doesn’t count SPC2 cards number.​
In certain combinations sometimes, the total session capacity could be reduced, comparing to pure SPC2 mode.​
It is recommended to have at least 2 SPC3 cards when running with SPC3 + SPC2 mixed mode to maintain/increase session capacity.

My recommendation is to either fill-up all slots with SPC2 for better performance or replace the SPC2 cars, if possible.

Thank you all for your quick response.