Version 3.110 is now available

Yes, a new version number

About Every 10 years I switch to a new version control system. I'm now using SVN instead of CVS. I don't care what you think about this, It's working for me.

ibcli has been surprisingly stable in the last 6-9 months and there have been very few changes, but this week I found an ugly bug with deleting fixed addresses so I thought I should release a new rev.

Get the Code
Get the Release Notes
Get the User Guide

What's New in Version 3.110

    Auto Generate hosts

    You can post process a zone and create host records

       conf zone mod foo.com generate_hosts

  Copy a zone to another view

    you need the source and destination zone and views

        conf zone copy  view  to  dest_view  
        conf zone copy zone.com view int to newzone.com dest_view external

  Show information about an IP address

      show ipam address 1.2.3.4

  Add a network to a discovery job

    Each network gets added to the current discovery job

      configure ipam discovery add network 1.2.3.0/24

  Show a discovery job

      show ipam discovery


Other cosmetic cleanups :

    Fixed the syntax for adding 'forward_to' zones

       conf zone add fwd.foo.com forward_to ns1.x.com,2.2.2.2 member 10.0.0.20

    Configuring a host for no dns (disable for dns)

       conf zone info.com add host pc2 2.3.3.3 ... nodns

    You no longer need the network when working with ranges or fixed
    addresses

       conf network add fixed ... option = [opt =value>]
       conf network add fixed 10.0.1.4 .. option 82="some data"

       conf network add range 10.1.1.20 10.1.1.40
       conf network add range 10.1.1.20 10.1.1.40 view default


    Show Member DNS settings

       show member  dns 

       show member ns1.lab.com dns

        ( You can also get there from the zone command )

       show zone member ns1.lab.com

Version 3.48 is now available

New in version 3.48

Fixes for Network Views
Network Discovery
Network Containers
Member status and licenses

Get the Code
Get the Release Notes
Get the User Guide

Version 3.46 is now available

New in version 3.46

Scheduled updates
Network Views for ranges and fixed addrs
Template fixes
Next_available IP
and other stuff

Get the Code
Get the Release Notes
Get the User Guide

What versions of NIOS does ibcli work with ?

I was just asked the question :

Given the various versions of ibcli.pl listed,
what is the recommended way to validate which
version of ibcli.pl should be used - based on
the version of NIOS that's on the GM that ibcli
will be interacting with ?

The answer is : "Use the latest version of ibcli, always".

Wherever possible I've tried to make ibcli backwards compatible, including working around known bugs, and inserting multiple versions of code (such as support for extensible attributes or IPAM fields).

If you use an old version of ibcli you won't have access to some of the commands. If you use a new version of ibcli against an old version of NIOS, some commands just won't do anything ( type 'set debug 1' to see the failures )

And, as usual, if you find a bug, let me know.

Version 3.44 is now available

New in version 3.44

Get the Code
Get the Release Notes
Get the User Guide

More support for permissions
Network Views
and other stuff

Version 3.43 is now available

New in version 3.43

Get the Code
Get the Release Notes
Get the User Guide

You can modify views and fixed addreses
Provisional support for roaming hosts
Showing and adding extensible attributes
Showing and adding permissions to objects

I still haven't coded the 'update' feature yet, but no-one has been screaming for it.

For the next releae

For the next release I'm working on 2 new features. One is adding Extensible attributes to networks and other 'non-host' objects. The second one is more tricky, it has to do with modifying hosts. The command(s) I'm proposing are something like :

 conf zone insert host ...
 conf zone update host ...

If you go to modify a host and it isn't already there, you will get an 'object not found' error. This happens a lot if you are going back later and trying to import a pile of IPAM data on top of a pile of DNS data (it is never a 1-1 match).

So you have to do 2 passes :

• Modify the existing hosts
• Walk the error log and add hosts that didn't exist.
  

So I'm proposing a comand that will first try to MODIFY the host, and if there is an error, then try to ADD the host.

But, and here is the problem. Which is more efficient ? MODIFY then ADD, or ADD then MODIFY (or do we need both)

What are your thoughts ?