Background and result
In CML (Cisco Modeling Labs), when accessing each node in the lab from the outside via SSH, etc., a node called the External Connector is deployed and connected to the management interface of each node.
This procedure is shown in the user guide.
https://developer.cisco.com/docs/modeling-labs/#!bridge-mode
In my ESXi environment, the following work was required as a preliminary step.
- Accept promiscuous mode in ESXi https://developer.cisco.com/docs/modeling-labs/#deploying-the-ova-on-esxi-server
In addition, the following task was also required for CML 2.4.0.
- Edit the bridge interface in CML https://developer.cisco.com/docs/modeling-labs/#!configuring-the-management-ip-address
What I did
Accept promiscuous mode
- Check settings of port groups assigned to VMs in CML
- If it is inherited from a vSwitch, check the related vSwitch settings
- Change promiscuous mode to accept and save
Edit the bridge interface
-
Login to CML's Web console
- https://{CML's IP address}:9090/
- username : "sysadmin"
- password : string specified during installation
-
Press bridge0 after selecting Networking from the menu
- At this time, check the interface on which the management IP address is set
-
Press "+" on the port and select the interface you just checked
- in this case "ens160"
Confirm that bridge0 is assigned an IP address for management
The required step was the above.
Supplemental information and others
If the hypervisor is nested, then promiscuous mode must be accepted for all vNICs/vSwitches that the communication passes through.
Top comments (0)