In the cisco web say that:
" Inside the base-level VM, you can run a number of different images. At this time, you can load IOS XR, IOS XE (via the CSR1000v), IOSv, as well as generic server images such as Ubuntu Linux. Some noticeable absences are the adaptive security appliance (ASA) and any kind of Layer 2 device."
"The base OS of the CML image is Ubuntu Linux, the hypervisor is kernel-based virtual machine s, and OpenStack Grizzly handles the VM orchestration. Cisco-proprietary pieces take over to handle the middleware layer (Service Topology Director) and user interface (Maestro is the working project name), with the configuration engine following on in the guise of AutoNetKit with several Cisco extensions added."
You can install and run different Virutal Machines inside CML.
... View more
There were some things I was not sure about so I have looked through several sets of documentation on multicast boundary. I have found several references that are specific in saying that multicast boundary uses standard (not extended) access list. These are probably reflecting earlier implementations or perhaps certain platforms. And clearly when using a standard access list the address and mask refer to the multicast addresses (so in a way you could consider these as destination addresses).
And I found some references that indicate that multicast boundary can use either standard or extended access list. These are probably reflecting more recent versions of code or perhaps different platforms. With the extended access list you can specify the source sending the packet as well as the multicast group to which it is sent. So the meaning of the fields in the extended access list are pretty much what we are used to in terms of source and destination addresses.
I have not found any reference that shows something like
80 permit ipv4 220.127.116.11 0.0.255.255 any 90 permit ipv4 18.104.22.168 0.0.255.255 any
as being valid and I must assume that they were created by someone who did not understand the config very well. And I assume that these access lists are probably not having the result that was intended for them.
... View more
Thanks, Ganesh, very good
explanation, that helps. I do see now that if in your example I used LB
by MAC, either source or destination, I would not have LB at all - the
traffic would go only through one port. Still not sure though about commands entered on both sides of the etherchannel for LB. Also,
still not clear how it would work for LB by both destination and source
- when packets are coming from some three IP to the Etherchannel
configured for both dest and src and they are destined to two servers
how are they going to be handled? If balanced properly then should not
we always configure LB for both src and dst? Why would it be a problem
(at least then no need to think what configure on both sides of the
Etherchannel - just do the same). In order to configure load balancing for ethere channel in switches just configure with the below mentioned steps:- Router# configure terminal Router(config)# port-channel load-balance src-dst-ip Check out the below link on etherchannel load balancing http://www.testequipmentconnection.com/specs/Cisco_WS-X6548V-GE-TX.PDF Hope to Help !! Ganesh.H Remember to rate the helpful post
... View more