Oncilla IP allocation

Support and Dispatch need to know that IP allocation is changing … one MNO at a time. It is moving from the old, slow tigrillo tools to a shiny new Oncilla one.
 
Traditionally we have used the IP allocation Web page to on the Tigrillo Helper pages, but as the MNOs are transferred from the old to the new, that page will progressively stop working.
 
So before allocating an IP use the following Query to tell you if the IP allocation is done by Oncilla. Look up your IMSI range  name in the results you get from it.
 
select b.name,'Oncilla'  from oncilla.ipPoolAttribute as a  left join oncilla.ipPool as b on a. ipPoolId = b.ipPoolId where a.attribute ='ipAllocationOncilla';
 
 
 
FIRST – The New System for the MNO range names  that the query above found as Oncilla allocations. You need to know :-
 
You /should/ never need to allocate an IP address for the ones done by Oncilla, because the system will always get there first. This is because there are a series of triggers that will cause the IP of a SIM to be assigned ( or reconciled to be correct to the package )
 
 

1. Package or Portfolio assignment in Infinity.  i.e. new SIMs when assigned to a package and a customer Portfolio will get IPs  allocated automatically )
2. Package Change in Infinity.   i.e. if Infinity is used to change Package, this will also update the IP addresses
3. Provisioning will change an IP address from Disabled to Enabled

 
Therefore, If you find an IP address ( New system) that is wrong it means that either
 

• it was allocated a long time ago, or
• someone has fiddled with it outside the tools. Or
• Most Likely , the IP is correctly allocated, but it is not what you were expecting. Check the Package is correct
  • In Particular, MTN Ghana Packages were migrated across, but the IP allocations didn’t match the packages, so it is highly probable you have a Package problem.

 
In the rare occasions that you do need to force a reconciliation; you can use one of these two stored procedures BUT after you have done this , you should Bounce the SIM ( in VP ) if it has updated  an MTN, Orange France or PWN IP address
 
Example call statement for input as iccId
use oncilla;
SET @errorMsg = 'override'; SET @myStatus = NULL; CALL _ipAllocation(NULL,'8912230102421160395',@errorMsg,@myStatus); SELECT @errorMsg, @myStatus;
 
Example call statement for input as imsiId
use oncilla;
SET @errorMsg = 'override'; SET @myStatus = NULL; CALL _ipAllocation('23010242116039',NULL,@errorMsg,@myStatus); SELECT @errorMsg, @myStatus;
 
 
 
SECOND  - anything on the OLD, Tigrillo Allocation.
 
Use Update IP by MSISDN only , using the tigrillo Helper Pages.

we can look into the log for what was done when running the SP for oncilla IP allocation
 
SELECT * FROM oncillaLogging.log where payload like '%8955170000203708319%' order by logId desc limit 5

 
from looking at this we could see there were a few issues with the subnet set up
 
select * from oncilla.subnet where name like '%Anova%';
 

 
The Ip allocation stratagy was Null -  this means that Oncilla saw no strategy meaning the SP was successful because it did nothing
The IpPoolID was null - this means that the subnet was not accociated to any pool such as NLT or Surf
 
the IP allocation stratagy is found in this table select * from oncilla.allocationStrategy;
 
The IPPoolID is found in this table Select * from  oncilla.ipPool ip