Track Lead - F5, Infoblox IPAM

Others, Telangana

Job Summary

Job Responsibilities : Physical to Virtual (P2V) Migration • HCL will perform detailed discovery of the existing F5 physical environment using configurations and access provided by the Biogen. This includes analysis of virtual servers, pools, monitors, SSL certificates, profiles, and iRules. • Based on the Biogen provided design and target architecture, HCL will deploy the F5 Virtual Edition (VE) environment on the designated platform (on-prem). This includes system setup, licensing configuration, networking (VLANs, self IPs, routing), and high availability configuration. • HCL will execute configuration migration using UCS restoration or manual object-level recreation based on compatibility. Necessary adjustments will be made for virtual environment differences, including interface mappings and performance tuning. • HCL will conduct functional testing to validate configuration accuracy, including application reachability, load balancing behavior, SSL validation, and failover testing. Biogen will support application-level validation and provide approval for production readiness. • HCL will execute cutover activities, including traffic migration via DNS updates or routing changes, in coordination with Biogen ITSO approvals. Post-migration, HCL will provide HyperCare support, monitoring, issue resolution, and performance optimization before final handover. Physical to Physical (P2P) Migration • HCL will analyze the existing F5 physical workplace using access and configuration data provided by the Biogen. Based on the approved Biogen provided design, HCL will configure the new F5 hardware environment, including base system setup, licensing, and HA configuration. • Configuration migration will be performed using UCS restore or manual recreation depending on version compatibility. HCL will adapt configurations to align with new hardware interface mappings and capabilities. • HCL will execute comprehensive testing to validate application behavior, load balancing functionality, SSL operations, and failover readiness. Biogen will participate in validation and provide sign-off. • Cutover will be executed by the HCL through coordinated traffic switchover activities such as routing updates or VLAN transitions, with required approvals from the Biogen ITSO. Post-migration, HCL will provide HyperCare support and performance tuning. Virtual to Virtual (F5 VE to VE) Migration • HCL will assess the existing F5 Virtual Edition workplace based on access provided by the Biogen, including configuration extraction and compatibility validation. • Using the Biogen provided design, HCL will deploy the target VE environment, configure base system settings, and establish high availability. • Configuration migration will be executed using UCS restore or manual migration, ensuring accuracy of all LTM objects including virtual servers, pools, monitors, SSL configurations, and iRules. Adjustments will be made for platform-specific differences, especially in cross-hypervisor or cloud migrations. • HCL will perform testing to ensure application availability, persistence, SSL integrity, and failover capability. Biogen will validate application functionality and approve readiness. • HCL will execute the cutover by redirecting traffic to the current VE environment and will provide post-migration support, including monitoring, issue resolution, and optimization. Job Description : Physical to Virtual (P2V) Migration\\r\\n• HCL will perform detailed discovery of the existing F5 physical environment using configurations and access provided by the Biogen. This includes analysis of virtual servers, pools, monitors, SSL certificates, profiles,



and iRules.\\r\\n• Based on the Biogen provided design and target architecture, HCL will deploy the F5 Virtual Edition (VE) workplace on the designated platform (on-prem). This includes system setup, licensing configuration, networking (VLANs, self IPs, routing), and high availability configuration.\\r\\n• HCL will

Key Responsibilities

NA

Skill Requirements

Skill Requirement : Physical to Virtual (P2V) Migration • HCL will perform detailed discovery of the existing F5 physical environment using configurations and access provided by the Biogen. This includes analysis of virtual servers, pools, monitors, SSL certificates, profiles, and iRules. • Based on the Biogen provided design and target architecture, HCL will deploy the F5 Virtual Edition (VE) environment on the designated platform (on-prem). This includes system setup, licensing configuration, networking (VLANs, self IPs, routing), and high availability configuration. • HCL will execute configuration migration using UCS restoration or manual object-level recreation based on compatibility. Necessary adjustments will be made for virtual environment differences, including interface mappings and performance tuning. • HCL will conduct functional testing to validate configuration accuracy, including application reachability, load balancing behavior, SSL validation, and failover testing. Biogen will support application-level validation and provide approval for production readiness. • HCL will execute cutover activities, including traffic migration via DNS updates or routing changes, in coordination with Biogen ITSO approvals. Post-migration, HCL will provide HyperCare support, monitoring, issue resolution, and performance optimization before final handover. Physical to Physical (P2P) Migration • HCL will analyze the existing F5 physical environment using access and configuration data provided by the Biogen. Based on the approved Biogen provided design, HCL will configure the new F5 hardware environment, including base system setup, licensing, and HA configuration. • Configuration migration will be performed using UCS restore or manual recreation depending on version compatibility. HCL will adapt configurations to align with new hardware interface mappings and capabilities. • HCL will execute comprehensive testing to validate application behavior, load balancing functionality, SSL operations, and failover readiness. Biogen will participate in validation and provide sign-off. • Cutover will be executed by the HCL through coordinated traffic switchover activities such as routing updates or VLAN transitions, with required approvals from the Biogen ITSO. Post-migration, HCL will provide HyperCare support and performance tuning. Virtual to Virtual (F5 VE to VE) Migration • HCL will assess the existing F5 Virtual Edition environment based on access provided by the Biogen, including configuration extraction and compatibility validation. • Using the Biogen provided design, HCL will deploy the target VE environment, configure base system settings, and establish high availability. • Configuration migration will be executed using UCS restore or manual migration, ensuring accuracy of all LTM objects including virtual servers, pools, monitors, SSL configurations, and iRules. Adjustments will be made for platform-specific differences, especially in cross-hypervisor or cloud migrations.



• HCL will perform testing to ensure application availability, persistence, SSL integrity, and failover capability. Biogen will validate application functionality and approve readiness. • HCL will execute the cutover by redirecting traffic to the new VE environment and will provide post-migration support, including monitoring, issue resolution, and optimization.

Other Requirements

Other Requirement : Physical to Virtual (P2V) Migration • HCL will perform detailed discovery of the existing F5 physical workplace using configurations and access provided by the Biogen. This includes analysis of virtual servers, pools, monitors, SSL certificates, profiles, and iRules. • Based on the Biogen provided design and target architecture, HCL will deploy the F5 Virtual Edition (VE) environment on the designated platform (on-prem). This includes system setup, licensing configuration, networking (VLANs, self IPs, routing), and high availability configuration. • HCL will execute configuration migration using UCS restoration or manual object-level recreation based on compatibility. Necessary adjustments will be made for virtual environment differences, including interface mappings and performance tuning. • HCL will conduct functional testing to validate configuration accuracy, including application reachability, load balancing behavior, SSL validation, and failover testing. Biogen will support application-level validation and provide approval for production readiness. • HCL will execute cutover activities, including traffic migration via DNS updates or routing changes, in coordination with Biogen ITSO approvals. Post-migration, HCL will provide HyperCare support, monitoring, issue resolution, and performance optimization before final handover. Physical to Physical (P2P) Migration • HCL will analyze the existing F5 physical environment using access and configuration data provided by the Biogen. Based on the approved Biogen provided design, HCL will configure the new F5 hardware environment, including base system setup, licensing, and HA configuration. • Configuration migration will be performed using UCS restore or manual recreation depending on version compatibility. HCL will adapt configurations to align with new hardware interface mappings and capabilities. • HCL will execute comprehensive testing to validate application behavior, load balancing functionality, SSL operations, and failover readiness. Biogen will participate in validation and provide sign-off. • Cutover will be executed by the HCL through coordinated traffic switchover activities such as routing updates or VLAN transitions, with required approvals from the Biogen ITSO. Post-migration, HCL will provide HyperCare support and performance tuning. Virtual to Virtual (F5 VE to VE) Migration • HCL will assess the existing F5 Virtual Edition environment based on access provided by the Biogen, including configuration extraction and compatibility validation. • Using the Biogen provided design, HCL will deploy the target VE environment, configure base system settings, and establish high availability. • Configuration migration will be executed using UCS restore or manual migration, ensuring accuracy of all LTM objects including virtual servers, pools, monitors, SSL configurations, and iRules. Adjustments will be made for platform-specific differences, especially in cross-hypervisor or cloud migrations. • HCL will perform testing to ensure application availability, persistence, SSL integrity, and failover capability. Biogen will validate application functionality and approve readiness. • HCL will execute the cutover by redirecting traffic to the new VE setting and will provide post-migration support, including monitoring, issue resolution, and optimization.

📌 Track LeadInfoblox IPAM (India)
🏢 HCLTech
📍 India