NetConfig extract “DEST” and “TRXID”

If you are on a later release of Cloverleaf, you can use the NCI (NetConfig Interface I think) to extract info from the NetConfig. It is documented fairly well in help but if you want an example I can provide one email me if you want that.

If on older Cloverleaf, there is an undocumented set of commands. Others on Clovertech do that and will have examples. I do not use those functions.

As Jim said you can use the NCI interface.  The commands are in the online docs.

If me I would do something like: (Assuming you want current site NetConfig)

netconfig load $::HciSiteDir/NetConfig

foreach conn [netconfig get connection list] {

set data [netconfig get connection data $conn]
set klst [keylget data DATAXLATE]

foreach {full part} [regexp -all -inline {DEST (.*?)\}} $klst] {
echo THREAD $conn –> $part
}
}

Note: Only threads with destinations will be listed as others will return empty from regexp command

Note the use of the regexp inline command.  To me, much easier than trying to drill down further as now you get into lists of keyed lists, etc.

I hope I did not misunderstand what you wanted.  If so this will still give you a kick start.

Hello Joe,

DATAXLATE is a single list with a list of 0-n routes and the routes contain lists of 0-n route details.

Get the list of routes:

set rteLst [lindex $dataxlate]

Then loop through the list looking for the fields you want:

foreach rte $rteLst {
  keylget rte TRXID trxid
  echo $trxid
}

Regards, Jim

We have some tools to read some NetConfig content – the stuff we’ve needed for our automation.

But this looked like fun so I played around with adding routing/xlate info as well.

Attached is a fairly complete example proc that will read NetConfig for a specified site.

usage: readNetConfigExt <site> <arrayName>

>>> something like: readNetConfigExt lab netConfigArray

There is also a proc to print what was read.

usage: printNetConfigExt <arrayName>

>>> something like: printNetConfigExt netConfigArray