Automate Gambitcomm MIMIC

What Gambitcomm MIMIC is

This is the API for MIMIC client to connect to MIMIC daemon.

API host: gambitcomm.local

What HumDay can do in Gambitcomm MIMIC

170 documented operations change something in Gambitcomm MIMIC. The 43 most useful are listed here.

• DELETEClears a users entry from access control database./mimic/access/del/{user}
• PUTThe current log file for the Simulator./mimic/set/log
• POSTAdds/Overwrites the user entry in the access control database./mimic/access/add/{user}/{agents}/{mask}
• PUTSave the lab configuration./mimic/save
• PUTStop MIMIC./mimic/stop
• PUTStart MIMIC./mimic/start
• PUTTerminate the MIMIC daemon./mimic/terminate
• PUTLoads the specified file for access control data./mimic/access/load/{filename}
• PUTSaves current access control data in specified file./mimic/access/save/{filename}
• PUTThe network address of the host where the MIMIC simulator is running./mimic/set/netdev
• PUTThis operation flushes all global objects which need to be made persistent to disk./mimic/set/persistent
• PUTprotocols supported by agent as a comma-separated list/mimic/agent/{agentNum}/set/protocol
• PUTAllows the user to enable/disable the access control check./mimic/access/set/enabled/{enabledOrNot}
• POSTAdd an agent./mimic/agent/{agentNum}/add/{IP}
• PUTThese commands treat the variable as a list, and allow to replace an entry in the list at the specified index with the specified value./mimic/store/lreplace/{var}/{index}
• PUTSaves current user settings in the currently loaded USM config file./mimic/agent/{agentNum}/protocol/msg/snmpv3/usm/save
• POSTAdd a source address that the agent will accept messages from./mimic/agent/{agentNum}/from/add/{IP}/{port}
• POSTAdd a new timer script to be executed at specified interval (in msec) with the specified argument./mimic/timer/script/add/{script}/{interval}/{arg}
• PUTDeletes a variable which is currently defined./mimic/store/unset/{var}
• PUTHalt the current agent./mimic/agent/{agentNum}/halt
• PUTSave agent MIB values./mimic/agent/{agentNum}/save
• PUTShow the agent's primary IP address/mimic/agent/{agentNum}/stop
• PUTPause the current agent./mimic/agent/{agentNum}/pause
• PUTStart the current agent./mimic/agent/{agentNum}/start
• PUTReload the current agent./mimic/agent/{agentNum}/reload
• DELETERemove the current agent./mimic/agent/{agentNum}/remove
• PUTResume the current agent./mimic/agent/{agentNum}/resume
• PUTSave the lab configuration in file./mimic/saveas/{cfgFile}/{firstAgentNum}/{lastAgentNum}
• POSTAdds a new ipalias for the agent./mimic/agent/{agentNum}/ipalias/add/{IP}/{port}/{mask}/{interface}
• PUTset of MIBs, simulations and scenarios/mimic/agent/{agentNum}/set/mibs
• PUTSet multiple variables in the Value Space./mimic/agent/{agentNum}/value/mset
• PUTUnset multiple variables in the Value Space/mimic/agent/{agentNum}/value/munset
• PUTAllows setting the name of the current access control database./mimic/access/set/acldb/{databaseName}
• PUTClear the lab configuration./mimic/clear/{firstAgentNum}/{lastAgentNum}
• PUTSaves current user settings in the specified USM config file./mimic/agent/{agentNum}/protocol/msg/snmpv3/usm/saveas/{filename}
• PUTSet the variable store for the global storage/mimic/store/set/{var}/{persist}
• PUTSaves current group, access, view settings in the currently loaded VACM config file./mimic/agent/{agentNum}/protocol/msg/snmpv3/vacm/save
• DELETEClears all user entries./mimic/agent/{agentNum}/protocol/msg/snmpv3/user/clear
• DELETEdelete a source address that the agent will accept messages from./mimic/agent/{agentNum}/from/delete/{IP}/{port}
• PUTThese commands allow the creation of a new variable, or changing an existing value./mimic/agent/{agentNum}/store/set/{var}/{persist}
• PUTThese commands treat the variable as a list, and allow to replace an entry in the list at the specified index with the specified value./mimic/agent/{agentNum}/store/lreplace/{var}/{index}
• DELETERemove a timer script from the execution list./mimic/timer/script/delete/{script}/{interval}/{arg}
• POSTAdd an entry to a table./mimic/agent/{agentNum}/value/add/{object}/{instance}

What HumDay can read from Gambitcomm MIMIC

These are the operations a schedule or a trigger can watch.

• GETThe currently loaded lab configuration file for the particular user./mimic/get/cfgfile
• GETThe current log file for the Simulator./mimic/get/log
• GETThis command will return the list of variables in the said scope./mimic/store/list
• GETReturns an array of entries./mimic/access/list
• GETThe list of {agentnum} that are currently active (running or paused)./mimic/get/active_list
• GETThis predicate indicates if the currently loaded agent configuration file has changed./mimic/get/cfgfile_changed
• GETThe list of {agentnum} that are currently configured./mimic/get/configured_list
• GETThe list of {agentnum {statistics}} for agents that are currently active and whose statistics have changed since the last invocation of this command./mimic/get/active_data_list
• GETList the source addresses that the agent will accept messages from./mimic/agent/{agentNum}/from/list
• GETThe list of {agentnum state} for which the state changed./mimic/get/changed_state_list
• GETThe list of {agentnum} for which a configurable parameter changed./mimic/get/changed_config_list
• GETList the timer scripts currently running along with the their intervals./mimic/timer/script/list
• GETThe maximum number of agent instances./mimic/get/max
• GETThe last configured agent instance./mimic/get/last
• GETThe default network device to be used for agent addresses./mimic/get/netdev
• GETThe return mode./mimic/get/return
• GETThe number of clients currently connected to the daemon./mimic/get/clients
• GETThe network address of the host where the MIMIC simulator is running./mimic/get/netaddr
• GETThe product number that is licensed./mimic/get/product
• GETThe version of the MIMIC command interface./mimic/get/version
• GETThe set of protocols supported by the Simulator./mimic/get/protocols
• GETThe set of network interfaces that can be used for simulations./mimic/get/interfaces
• GETList the outstanding asynchronous traps for this agent instance./mimic/agent/{agentNum}/trap/list
• GETThis command will return the list of variables in the said scope./mimic/agent/{agentNum}/store/list
• GETLists all the additional ipaliases configured for the agent./mimic/agent/{agentNum}/ipalias/list
• GETGet multiple sets of information about MIMIC, where infoArray is one of the parameters defined in the mimic get command./mimic/mget/{infoArray}
• GETReturns the current access control database in use./mimic/access/get/acldb
• GETReturns the state of access control checking./mimic/access/get/enabled
• GETReturns the current administrator./mimic/access/get/adminuser
• GETReturns the current user entries as a Tcl list./mimic/agent/{agentNum}/protocol/msg/snmpv3/user/list
• GETList the set of trap destinations for this agent instance./mimic/agent/{agentNum}/trap/config/list
• GETList the timer scripts currently running along with the their intervals./mimic/agent/{agentNum}/timer/script/list
• GETFetches the value associated with a variable./mimic/store/get/{var}
• GETThis command can be used as a predicate to ascertain the existence of a given variable./mimic/store/exists/{var}
• GETThis command can be used as a predicate to ascertain the persistence of a given variable./mimic/store/persists/{var}
• GETDisplay the MIB objects below the current position/mimic/agent/{agentNum}/value/list/{OID}
• GETShow the agent's current messages' cardinality/mimic/agent/{agentNum}/protocol/msg/mqtt/client/message/card
• GETShow the agent's TELNET user db file name/mimic/agent/{agentNum}/protocol/msg/telnet/server/get/userdb
• GETShow the parameters configured by the server in its DHCP-OFFER message/mimic/agent/{agentNum}/protocol/msg/dhcp/params
• GETfirst simulation name/mimic/agent/{agentNum}/get/sim
• GEThost address of the agent./mimic/agent/{agentNum}/get/host
• GETsubnet mask of the agent./mimic/agent/{agentNum}/get/mask
• GETset of MIBs, simulations and scenarios/mimic/agent/{agentNum}/get/mibs
• GETport number/mimic/agent/{agentNum}/get/port
• GETread community string/mimic/agent/{agentNum}/get/read
• GETfirst scenario name/mimic/agent/{agentNum}/get/scen
• GETone-way transit delay in msec./mimic/agent/{agentNum}/get/delay
• GETdrop rate (every N-th PDU)./mimic/agent/{agentNum}/get/drops
• GETowner of the agent./mimic/agent/{agentNum}/get/owner
• GETrelative start time/mimic/agent/{agentNum}/get/start
• GETcurrent running state of the agent/mimic/agent/{agentNum}/get/state
• GETSNMP PDU tracing/mimic/agent/{agentNum}/get/trace
• GETwrite community string/mimic/agent/{agentNum}/get/write
• GETMIB directory of the agent./mimic/agent/{agentNum}/get/oiddir
• GEThas the agent value space changed?/mimic/agent/{agentNum}/get/changed
• GETmaximum PDU size./mimic/agent/{agentNum}/get/pdusize
• GETprivate directory of the agent./mimic/agent/{agentNum}/get/privdir

How automating Gambitcomm MIMIC works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Gambitcomm MIMIC account.
4. Grant access, then go live. You approve the specific Gambitcomm MIMIC operations it may use — and only those.

Automate Gambitcomm MIMIC with these

• Meraki Dashboard263 operations
• ClearBlade220 operations
• Influxdata Influx OSS197 operations
• Intellifi Brain77 operations
• Adafruit IO71 operations
• Ijenko IoE² IoT to create end user applications67 operations
• smart me64 operations
• Opto22 PAC Control55 operations
• KeyServ24 operations
• Hardware Sentry TrueSight Presentation Server23 operations
• Netatmo19 operations
• dweet.io13 operations

Categories

• Iot

Questions about Gambitcomm MIMIC automation

Can HumDay connect to Gambitcomm MIMIC?

Yes. HumDay reads Gambitcomm MIMIC's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 356 operations are documented.

Do I need to write code to automate Gambitcomm MIMIC?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Gambitcomm MIMIC account.

What can HumDay do in Gambitcomm MIMIC?

170 of the 356 documented operations change something in Gambitcomm MIMIC, and 186 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Gambitcomm MIMIC account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Gambitcomm MIMIC is held behind that approval.

Where this came from

The operations above are read from a published API description for Gambitcomm MIMIC at www.gambitcomm.com/docs/mimic.yaml. Descriptions are the provider’s own words, not ours. Last published 2021-07-27.