who to contact re: issue routing to local machines through bigip

Benjamin Anderson

Hi, Our team is just starting up with porting an existing product, TNP (Taxnet Pro), from web2 to cobalt. Part of this process is to be able to route to our local machines through bigip. However, this isn't working for us and we aren't sure who to contact to help us - have been trying for weeks to find the right team to fix it for us. Does anyone know? these all work fine: # straight to my ip works $ curl -s 'http://10.222.128.36:8888/sc/Platform/js/v1/Core/Cobalt.Hub.js' | tail -n 1 // Cobalt.Hub.CreateUUID is defined in Cobalt.js # through bigip using ssl works $ curl -s -k '
https://10.222.128.36-8888.ip.v3.ci.taxnetpro.com/sc/Platform/js/v1/Core/Cobalt.Hub.js' | tail -n 1 // Cobalt.Hub.CreateUUID is defined in Cobalt.js # http using the next.westlaw works $ curl -s '
http://10.222.128.36-8888.ip.next.ci.westlaw.com/sc/Platform/js/v1/Core/Cobalt.Hub.js' | tail -n 1 // Cobalt.Hub.CreateUUID is defined in Cobalt.js # http using the nextcanada.westlaw works $ curl -s '
http://10.222.128.36-8888.ip.nextcanada.ci.westlaw.com/sc/Platform/js/v1/Core/Cobalt.Hub.js' | tail -n 1 // Cobalt.Hub.CreateUUID is defined in Cobalt.js this doesn't work (and is the problem): # http using the v3.taxnetpro doesn't work $ curl -s '
http://10.222.128.36-8888.ip.v3.ci.taxnetpro.com/sc/Platform/js/v1/Core/Cobalt.Hub.js' | tail -n 1

mark.maruska

Routing through BIG-IP using the ip-style domain name is supported by the iRules team. However, some aspect of that is setup/configuration by the CM team to enable it for each project. So, you'll probably want to contact CM (Co_CM_TECH) for setup/configuration or iRules (Co-iRules-Tech) for routing.

Benjamin Anderson

Thanks, Mark. I sent an email to both of those lists at your suggestion. FWIW, our architect (Josh VanBuren) looked through the bigip configuration and thinks everything looks good there. We're thinking it might be a networking issue because it sometimes works for some people.