This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

IpHost/IpHostGroup objects added via API never available to Firewall rules

Hi All,

I added the following IpHost/IpHostGroup objects via API -- which are accepted and created in the system -- with the following payload:

<?xml version="1.0" encoding="UTF-8"?>
<Configuration APIVersion="1700.1">
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>184.128.0.0</StartIPAddress>
<EndIPAddress>184.143.255.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC-155-165-0-0</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>155.165.0.0</StartIPAddress>
<EndIPAddress>155.165.255.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC-199-4-236-0</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>199.4.236.0</StartIPAddress>
<EndIPAddress>199.4.240.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_LVLT-ATTMO-3-4-38</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>4.38.0.0</StartIPAddress>
<EndIPAddress>4.38.15.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_LVLT-ATTMO-3-4-67-96</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>4.67.96.0</StartIPAddress>
<EndIPAddress>4.67.111.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC-209-183-32-0</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>209.183.32.0</StartIPAddress>
<EndIPAddress>209.183.63.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC-66-209-0-0</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>66.209.0.0</StartIPAddress>
<EndIPAddress>66.209.31.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC-66-102-160-0</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>66.102.160.0</StartIPAddress>
<EndIPAddress>66.102.191.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>107.224.0.0</StartIPAddress>
<EndIPAddress>107.255.255.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>107.64.0.0</StartIPAddress>
<EndIPAddress>107.127.255.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_ATT-MOBILITY-LLC</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>108.144.0.0</StartIPAddress>
<EndIPAddress>108.159.255.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_LVLT-ATTMO-3-4-23-88</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>4.23.88.0</StartIPAddress>
<EndIPAddress>4.23.89.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_LVLT-ATTMO-3-4-23-92</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>4.23.92.0</StartIPAddress>
<EndIPAddress>4.23.95.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_LVLT-ATTMO-3-4-43-50</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>4.43.50.0</StartIPAddress>
<EndIPAddress>4.43.51.255</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_Q0205-198-233-226-192</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>198.233.226.192</StartIPAddress>
<EndIPAddress>198.233.226.199</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_Q0223-63-144-237-8</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>63.144.237.8</StartIPAddress>
<EndIPAddress>63.144.237.15</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_Q0701-65-157-24-32</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>65.157.24.32</StartIPAddress>
<EndIPAddress>65.157.24.39</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_Q0727-65-132-22-160</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>65.132.22.160</StartIPAddress>
<EndIPAddress>65.132.22.167</EndIPAddress>
</IPHost>
<IPHost transactionid="">
<Name>ATTMO-3_Q0902-67-132-71-192</Name>
<IPFamily>IPv4</IPFamily>
<HostType>IPRange</HostType>
<StartIPAddress>67.132.71.192</StartIPAddress>
<EndIPAddress>67.132.71.223</EndIPAddress>
</IPHost>
<IPHostGroup transactionid="">
<Name>ATTMO-3</Name>
<Description/>
<HostList>
<Host>ATTMO-3_ATT-MOBILITY-LLC</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC-155-165-0-0</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC-199-4-236-0</Host>
<Host>ATTMO-3_LVLT-ATTMO-3-4-38</Host>
<Host>ATTMO-3_LVLT-ATTMO-3-4-67-96</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC-209-183-32-0</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC-66-209-0-0</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC-66-102-160-0</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC</Host>
<Host>ATTMO-3_ATT-MOBILITY-LLC</Host>
<Host>ATTMO-3_LVLT-ATTMO-3-4-23-88</Host>
<Host>ATTMO-3_LVLT-ATTMO-3-4-23-92</Host>
<Host>ATTMO-3_LVLT-ATTMO-3-4-43-50</Host>
<Host>ATTMO-3_Q0205-198-233-226-192</Host>
<Host>ATTMO-3_Q0223-63-144-237-8</Host>
<Host>ATTMO-3_Q0701-65-157-24-32</Host>
<Host>ATTMO-3_Q0727-65-132-22-160</Host>
<Host>ATTMO-3_Q0902-67-132-71-192</Host>
</HostList>
<IPFamily>IPv4</IPFamily>
</IPHostGroup>
</Configuration>

The API accepts this call and creates the IpHost/IpHostGroup objects, which are then visible in the admin interface:

However, none of the IpHost/IpHostGroup objects are available to firewall rules. For example, if you add a Business Application Rule, you cannot select any IpHost/IpHostGroup object added via the API. They are simply not in the list:

TLDR: Any IpHost/IpHostGroup object added via API isn't available via the web interface.

Any ideas?



This thread was automatically locked due to age.