| That will be hard! I presume you mean using the MCC_CALL interface?
If you aren't limited to using the MCC_CALL interface I would recommend you
spawn NCL and parse the output (maybe even using something like awk to parse
the output)!
If you really want to use MCC_CALL, take a look at the example I posted in
the MCC_TOOLS conference of how to do the equivalent of SHOW NODE
dec:.reo.msrv26 CHANGES OF ADDRESS. The biggest problem you will face is in
constructing the entity name to represent that entity (and parsing the
entity names in the responses). At least it is easier than trying to look
at the IP Destination Node database where the identifier is a RECORD!
However, I still recommend parsing NCL output.
If you really don't want to do that then use SNMP. The ARP cache (which is
what that command displays) is part of MIB-II and DECNIS and all later
routers support MIB-II. If you are going to use SNMP you could use
something like the ISODE package instead of going to the complexity of
involving MCC.
Graham
|