Awesome work! Thanks a lot! I am running CML in a Bare Metal UCS Blade. And CML was going down after it trunking an external connector, I just had to wait to normalize...
Thank you, this helped me immensely! It is really difficult to find "how to" videos and documentation for CML administration and this video is great. Can you point me to any resources you use to learn about CML administration?
Just to clarify, you are setting up the Vlan sub interfaces so that the received packets (which are tagged by the physical switch) are processed. Does it untag the packet once it arrives into the topology?
Hello! I was watching this video and had a question. I am trying to run CML on a vswitch that does not have a physical interface mapped, and following the same concepts in this tutorial are not working (no ping.) Any reason why it has to be there? What else might I want to look at?
Not sure I fully understand. If you're saying you have a vSwitch in ESXi with not physical NIC mapped, what are you expecting to ping? While you could use such a thing to have multiple labs interconnected on the ESXi backplane, you would have to provide either an in-CML DHCP server or assign addresses statically. However, in those cases, you should be able to ping between lab nodes connected to the bridge-based external-connectivity nodes.
@@xorrkaz I am hoping to ping everything else on that vswitch. Forgive me, I didn't provide enough info. I am using this to (try to) connect a CML lab to multiple outside assets. I have VMs all on the same subnet and on the same vSwitch. They are able to ping each other, and able to ping the CML IP I gave to the VLAN adapter, but cannot ping the router on the inside of CML and that router cannot ping out (or, ping the CML IP I gave to the VLAN adapter.) No DHCP on this network, it's all statically assigned. I was wondering if my lack of a physical adapter would cause it, but as I see it this should be just like connecting a bunch of devices up to a simple switch, which as long as they all have an IP on the same subnet / mask should be able to reach each other. I have a topology diagram if you were interested, but can't share via TH-cam comments.
@@xorrkaz I have those set, but still with no connectivity. That's why I had to create the additional vSwitch, because I didn't want to enable those settings on vSwitches with other purposes and VMs on them.
Awesome work! Thanks a lot! I am running CML in a Bare Metal UCS Blade. And CML was going down after it trunking an external connector, I just had to wait to normalize...
Thank you, this helped me immensely! It is really difficult to find "how to" videos and documentation for CML administration and this video is great. Can you point me to any resources you use to learn about CML administration?
The admin guide is the currently the best resources: developer.cisco.com/docs/modeling-labs/#!cml-administrators-guide
Just to clarify, you are setting up the Vlan sub interfaces so that the received packets (which are tagged by the physical switch) are processed. Does it untag the packet once it arrives into the topology?
The frames are untagged when they arrive at the CML nodes. The CML VM (Linux) handles the tagging and untagging.
Hello! I was watching this video and had a question.
I am trying to run CML on a vswitch that does not have a physical interface mapped, and following the same concepts in this tutorial are not working (no ping.)
Any reason why it has to be there? What else might I want to look at?
Not sure I fully understand. If you're saying you have a vSwitch in ESXi with not physical NIC mapped, what are you expecting to ping? While you could use such a thing to have multiple labs interconnected on the ESXi backplane, you would have to provide either an in-CML DHCP server or assign addresses statically. However, in those cases, you should be able to ping between lab nodes connected to the bridge-based external-connectivity nodes.
@@xorrkaz I am hoping to ping everything else on that vswitch. Forgive me, I didn't provide enough info.
I am using this to (try to) connect a CML lab to multiple outside assets. I have VMs all on the same subnet and on the same vSwitch. They are able to ping each other, and able to ping the CML IP I gave to the VLAN adapter, but cannot ping the router on the inside of CML and that router cannot ping out (or, ping the CML IP I gave to the VLAN adapter.)
No DHCP on this network, it's all statically assigned.
I was wondering if my lack of a physical adapter would cause it, but as I see it this should be just like connecting a bunch of devices up to a simple switch, which as long as they all have an IP on the same subnet / mask should be able to reach each other.
I have a topology diagram if you were interested, but can't share via TH-cam comments.
@@Dartagn This is fine. Make sure your vSwitch allows promiscuous mode and forged transmits, and you should be set.
@@xorrkaz I have those set, but still with no connectivity. That's why I had to create the additional vSwitch, because I didn't want to enable those settings on vSwitches with other purposes and VMs on them.