Network interface naming convention
I know that the naming convention that applies to network interfaces is s.p where s is the slot and p is the port, as in 1.1. When I check my Viprion I see thinks like 1/1.1 and 2/1.1 so I'd say that the naming convention in this case would be b/s.p where b is blade and it seems that slot is always 1 for each blade. Knowing all this I check now the network interfaces in my vCMP guests and I see thinks like 1/0.3, 1/0.4, 1/0.5 and 1/0.6 in one of the guests and 1/0.7, 1/0.8, 1/0.9 and 1/0.10 And I wonder, which is the naming convention for a vCMP system? It seems that ports 3,4,5,6 are assigned to first guest and 7,8,9,10 to the second one. Are port numbers 1 and 2 then reserved ports in any way? Why there are 4 ports? (has it something to do with the number of cores assigned to the guest? I'm trying to understand all this, and I'm not finding documentation about this subjects :(
Is it possible to have a multi-chassis VIPRION cluster to further increase throughput?
Is it possible to have a multi-chassis VIPRION cluster to further increase throughput? Is it supported? I am trying to design a APM-based remote access TLS VPN solution supporting 200,000 concurrent users providing 100Mbps of bandwidth to each user. As a result, it will need to support 20Tbps of bulk crypto. Since each VIPRION 4450 Blade is limited to a maximum of 80 Gbps of bulk crypto, I calculate that this would require 250 VIPRION 4450 Blades in parallel. Since each VIPRION 4800 Chassis only supports a maximum of 8 VIPRION 4450 Blade, this will exceed the limitations of a single VIPRION 4800 Chassis cluster solution. Therefore, it is possible to have a multi-chassis VIPRION cluster?