Let us discuss the port a group properties.
Here you can see that we have the properties security traffic shipping and the teaming and fail over
option when we are inside security.
We have promiscuous mode Mac I guess change and the phones transmit and the order that we can select
are the options that to select is accept or reject.
Correct.
So see one by one in case of promiscuous mode.
If it is chosen as a reject that means there is no effect but if we accept this mode that means you
are detecting the frames.
With respect to whatever policy you have configure for that particular port group or for that particular
adapter inside the port group correct.
So if it is except that means you are detecting all the frames passing through the V a sphere is kind
of a switch.
You can see the default setting here.
The default will be like this.
Promise cases reject Maca the change and the false transmit is except accept.
So let's see what is there in the MAC address.
Changes in macro does change one thing to note here that the V sphere the that is inside the V emacs
configuration file where there is during the MAC address.
So suppose if they see that any change inside the macro.
This means if you make this as a reject if any change in the macro just they will start dropping the
graphic rather if you make this as a except that means.
In that case they will allow those frames.
So what is happening here.
Changing the macro.
This from the guest always has the intended effect frames into the third Mac.
At this are received by the virtual machine.
So when the macro does changes there the frames will be passed false transmit reject means again false
means someone is using some sort of his spoofing.
In case of macro yes.
So here what will happen.
And this is again applied to the outbound frame.
So any outbound frame with a source macro does that is different from the one currently sitting in the
adapter is dropped.
So if a while doing the transmission of the frames it will see or the source macro is what is set in
the adapter and if it is rejected will you object.
If it is except it will allow that.
So it depends that what security policies we have according to that we can accept or reject.
I like travel clipping it's very much like Cisco configuration.
Cisco traffic shipping are the U.S. configurations what is happening here that you have say average
bandwidth then you may have a certain peak bandwidth so the peak and then if you're doing going out
for some slice of time if you're going a little bit up then you have both traffic OK.
So these are the normal actually optioning and this is Cookie was as well.
What is the Iskander what is the peak bandwidth and how much you want to buffer in case of a bust.
All right then we have the important thing that is the load balancing option and the failure in case
of Timmy.
So here we can see that we have multiple options.
I think we have six load balancing options here so legacy all the load balancing options.
One by one.
So first load balancing option here I can see that route based on the originating virtual port.
Now what will happen that the silicon uplink based on the virtual port I.D. on the switch.
So once they select the uplink then they will stick some sort of building type of option.
You have two or three uplink.
You select one of the uplink and you're sticking with that.
That's the default load balancing option we have.
Then we have the road based IP hash and the Mac based IP hash.
This is very much like if you are comparing this with the LSC people channel in switch when we are creating
the third channel.
So at that time they can do about.
They can do so so they can do IP Mac.
They can do IP Mac port added specimens.
There are also so many load balancing methods in case of a less VPN BGP.
I did the Cisco attach an item.
There are here also you can see that we have a cloud based IP hash means we are checking the hash value
of this source and the destination IP and then you set then you're sending the frames over the uplink
then.
Same thing with respect to Mac also.
We have then we have the load balancing option with respect to Nick Lord.
So suppose if we have to Nick one of the Nick having low 30 percent when have 10 percent automatically
Lord will save to the other Nick.
So this is also a nice feature then we have explicit failover order means according to the high interface
numbers but this is number two this is number one you're always been to number two.
So what is happening let me read from the list of active adapters.
Always use the highest order uplink that passes the failover detection criteria.
And this is no actual load balancing is performed in this option.
Obviously this is something like a user defined.
You can go and define the load balancing method.
So once we have the load balancing methods then what options we have the rest of the options we can
see we have the network failure detection Lincoln's status.
We only are beacon related.
Then you have notified switch and fallback legal status means it's very flagged If Lincoln's up and
down.
It will tell us all this particular link you are sending the traffic is down you the other link then
you have the beacon proving this is a smart intelligent way to detect the link as triggers.
So one two three what they will number of links we have we are sending the proofs after every one second
and we are checking that okay link is up or not.
And then if it is not up obviously the traffic will go to the some other direction very much like we
are doing in Cisco also but generally we try to check the ISP link.
So we have some sort of IP tracking SLA type of thing in Cisco.
So you are meant you are checking one link up to with respect to the link sending some sort of IP ICMP
unreachable type of beacon out probes and you are checking that link is up or not if it is not if it
is unreachable after every one second you are sending the probes with say for example hold on timer
of three second of a second if it is not responding you can go to the other direction notify message.
We have this option they specify where they were to switch notify the fiscal switch in case of failure.
So if any failure where it will notify the switch and then finally you have this fail over option.
This is also very logical filler filler option.
You have the fallback is said to yes if fallback is sick to No.
So suppose if you have to link and fallback is said to yes I put this link is down.
This will become active.
Suppose if this link will come back this will become active with standby in case of active standby.
So what they were originally State of the link was there.
Once it will get recovered it will start forwarding the graphic.
And that is not the case in the if the fallback is set to know.
So what will happen.
That two links are there active standby.
This is gone.
This stand may become active on maybe active active.
So now he is the primary who is ending the traffic.
Now suppose if this link will get reinstalled it still equals ending the traffic until unless something
will happen here and then it will become active and sending the traffic.
So these are the freeloader fallback options we have and these are the all the options we have inside
the base which you can see still we have multiple options related to security.
Catholic shipping teaming and Phil over.