The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
To clear the history of old tunnels from the Cisco Nexus 1000V InterCloud switch, use the clear intercloud tunnel history command.
clear intercloud tunnel history
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear intercloud tunnel history command on the InterCloud Switch and the InterCloud Extender.
|
|
---|---|
To clear the InterCloud tunnel statistics from the Cisco Nexus 1000V InterCloud switch, use the clear intercloud tunnel statistics command.
clear intercloud tunnel statistics [tunnel-id] [remote vm] [remote uuid]
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear intercloud tunnel statistics command on the InterCloud Switch.
|
|
---|---|
To clear InterCloud Agent logs for the VM, use the clear logging intercloud [vm name] command.
clear logging intercloud [vm name]
This command has the following arguments or keywords:
Name of the virtual machine you want to the clear the InterCloud logs for. |
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear logging intercloud [vm name] command on the InterCloud Switch.
To clear all the InterCloud modules, use the clear module service intercloud all command.
clear module service intercloud all
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear module service intercloud all command on the Cisco Nexus 1000V InterCloud VSM.
|
|
---|---|
Clears the InterCloud module statistics for a given module ID. |
|
Clears the InterCloud module for a given module ID for a VM. |
To clear the statistics of an InterCloud module, based on a module ID, use the clear module service intercloud module id statistics command.
clear module service intercloud module id statistics
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear module service intercloud module id statistics command on the InterCloud Switch.
|
|
---|---|
Clears the InterCloud module for a given module ID for a VM. |
|
To clear the InterCloud module for a given module ID and a VM, use the clear module service intercloud module-id vm command.
clear module service intercloud module-id[module-id] vm [vm-uuid]
This command has the following arguments or keywords.
ID of a configured module in the Cisco Nexus 1000V InterCloud. |
|
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the clear module service intercloud module-id vm command on the InterCloud Switch.
|
|
---|---|
Clears the InterCloud module statistics for a given module ID. |
To configure the redundancy manager event-logs, use the event-log redundancy manager command.
event-log redundancy-mgr {trace | info| error} [terminal]
This command has the following arguments or keywords.
(Optional) Displays event logs in real time on the terminal. |
Global configuration and EXEC modes
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the event-log redundancy-mgr command on the InterCloud Switch or the InterCloud Extender.
The following example shows the output to the event-log redundancy-mgr [terminal] command:
|
|
---|---|
Displays internal event log information for all modules on the Cisco Nexus 1000V InterCloud. |
To configure the tunnel manager event-logs, use the event-log tunnel-mgr command.
event-log tunnel-mgr {trace | info| error} [terminal]
This command has the following arguments or keywords.
(Optional) Displays event logs in real time on the terminal. |
Global configuration and EXEC modes
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the event-log tunnel-mgr command on the InterCloud Switch or the InterCloud Extender.
|
|
---|---|
To initiate a switchover in a high availability deployment, use the intercloud redundancy switchover command.
intercloud redundancy switchover
Global configuration and EXEC modes
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the intercloud redundancy switchover command on the InterCloud Extender.
To verify if the InterCloud Switch is reachable, use the intercloud test ics-reachability command.
intercloud test ics-reachability
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the intercloud test reachability command on the InterCloud Extender.
The following example shows the output to the intercloud test reachability command:
To set the logging level for all or a particular component of the InterCloud Agent on a VM, use the logging level intercloud command.
logging level intercloud [{all | clp | cncl | cncm | driver | hamgr | intfmgr | stm | subagent} ]
[{ emerg | alert | crit | err | warn | notice | inform | debug | disable}] [{all | vm name}]
This command has the following arguments or keywords.
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the logging level intercloud [component name] [level] [vm name] command on the InterCloud Switch.
Messages logged with an inferior level to the ones you set up for a component are ignored.
The following example shows the output to the logging level intercloud [component name] [level] [vm name] command:
To register a Cisco Nexus 1000V InterCloud VSM with the Cisco Prime Network Services Controller, use the nsc-policy-agent command.
|
|
---|---|
The source of the InterCloud CLI commands can vary depending on the devices you can execute the commands from. You can execute the nsc-policy agent command on the Cisco Nexus 1000V InterCloud VSM.
The following example shows how to register the Cisco Nexus 1000V InterCloud VSM with the Cisco Prime Network Services Controller:
|
|
---|---|
Verify the registration status of the Cisco Nexus 1000V InterCloud VSM. |