Migration from ACE to F5 - virtual contexts

1. Virtual Context = vcmp in F5 world. F5 vcmp, when compared to ACE virtual contexts or Netscreen virtualization, etc, isn't exactly apples-to-apples. Initially, you may be surprised that the F5 can do so few guest instances using vcmp but when you think about all the modules/functionality the F5 provide, it makes more sense.It's a multi-os/multi-app platform.

 

 

2.) Route domains can be applied. No need to redseign. On the 4200v, you will be limited to route domains (vrf equiv) and partitions(separate containers for objects) if you want/need to keep that separation. The few customers I have worked with on these migrations really loved the features/functionality once they got past the initial learning curve.

 

 

Keep in mind that you don't necessarily have to use route domains. If this is for internal use only (single tenant), you can securely keep traffic seprate via vlans/objects. The LTM is like a router but hardened in many ways. The VS can be configured to only speak on specific vlans. Of course, in your case, preconfiguring route domains would make it an easy "drop-in-place" solution.

 

 

By now, you have probably researched all this but I wanted to make sure you got a follow-up as well. Thanks,