Edge port

[BobGreer65666]

Hi there,

Thanks for reading!  I have N3Ks connected to ESXI hosts.  Everything's working fine. 

I'm wondering how these two switchport commands configured on the port connected to the host actually work together.  Does the spanning-tree command supersede the access vlan command and render it meaningless? 

switchport access vlan 100
spanning-tree port type edge trunk

Here's the full switchport config:

interface Ethernet1/31
switchport access vlan 100
spanning-tree port type edge trunk
mtu 9216

Thanks!

[inderdeeps]

@BobGreer65666: Check this 

https://www.cisco.com/c/m/en_us/techdoc/dc/reference/cli/nxos/commands/l2/spanning-tree-port-type-edge.html 

[Peter Paluch · Accepted solution]

My friends,

Please allow me to join and add my two cents...

I'm wondering how these two switchport commands configured on the port connected to the host actually work together. Does the spanning-tree command supersede the access vlan command and render it meaningless?

No, certainly not - these commands combine nicely.

• switchport access vlan 100 says: "If the port is operating in access mode then the access VLAN is 100". This command would be ignored if the port was configured as a trunk - but since there is no switchport mode trunk command configured, the default port operating mode is indeed access.
• spanning-tree port type edge trunk says: "Regardless of whether the port is an access port or a trunk, treat it as an STP Edge port." Ordinarily, without the trunk keyword, the command would be effective only if the port was an access port (which is your case anyway) but not if the port was a trunk. Using the trunk keyword ensures that the port is treated as an edge port both in access and in trunk mode.

Best regards,
Peter

[BobGreer65666]

Thank you all for your insights!

[balaji.bandi]

nexus side if the port is access, then its edge is good. if the Trunk edge trunk will be an advantage here. (this is like you connecting any Servers Like Esxi)