<div>
You are looking at cisco specific documentation of extensions to STP for the Nexus line of switches. &nbsp;Specifically STP extensions for port type. &nbsp;These extensions allow a Nexus switch to self enable particular interface functionality and influence impact to STP and convergence. &nbsp;There are three types of ports; normal, network and edge.<br />
<br />
Normal ports are handled as normal network ports and can be connected to bridges, switches or end hosts.<br />
<br />
Network ports are assumed connected to other switches or bridges and will auto enable bridge assurance on the Nexus platform. &nbsp;The port will available to participate in STP.<br />
<br />
Edge ports are assumed connected to end hosts only (whether server, workstation, NAS, etc.) and will not participate in STP.<br />
<br />
Nexus STP Port Types do not have any affect on whether a port is a trunk or not.
</div>


<div>
Can you be more specific as to what you're looking for. <br />
<br />
With respect to &quot;normal&quot;, the document states there are Network, Edge and Normal ports. <br />
<br />
Edge ports should only be connected hosts or end stations. &nbsp;Network ports are only to be connected to switches or spanning-tree aware devices. Normal ports could be connected to either.
</div>


<div>
OK , what I understand:<br />
<br />
The Edge Port is similar to Access Port<br />
Network Port is similar to &nbsp;Trunk Port<br />
<br />
Normal Port , is not clear... does it detect the other side so as to form Trunk or Access ?
</div>


<div>
No. <br />
<br />
Trunk and access ports have nothing to do with spanning tree. <br />
<br />
For example, a trunk port can be an edge port or a network port. <br />
<br />
So forget trunk and access when discussing spanning tree port types. <br />
<br />
An edge port is connected to an end station. &nbsp;A device that would never forward traffic (a PC, server, printer). &nbsp; A network port is connected to a spanning tree aware device (bridge or switch). &nbsp;These port types are defined in the configuration. <br />
<br />
A normal port could be connected to either an end station or a switch.
</div>


<div>
jsk - <br />
<br />
As noted in my original message:<br />
<br />

<blockquote>
Nexus STP Port Types do not have any affect on whether a port is a trunk or not.
</blockquote>
</div>


<div>
so how do you make a port as Normal port ?
</div>


<div>
Do nothing. That's the default.
</div>


<div>
If no changes are made to the port or the global defaults then normal is the default port type in Nexus. &nbsp;Cisco best practice is to set the global default to edge though. &nbsp;Insures that if an STP capable device is connected to the switch without admin intervention, the port is disabled automatically.
</div>


<div>
So<br />
Normal port can be connected to &nbsp;Hosts or to Switches. &nbsp; so Normal port does not understand STP ?<br />
<br />
Network Port , understands STP. &nbsp; &nbsp;how do you make a port as &nbsp;Network port ?<br />
<br />
Edge port , I believe it does not understand STP &nbsp;, if you connect it to a Switch, what would happen ? <br />
<br />
Thanks
</div>


<div>
All the port types understand STP. &nbsp;What is at issue is how the ports handle STP, BPDU's, etc. &nbsp;Specific to this question:<br />
<br />
Normal - Handles BPDU's as normal STP.<br />
Edge - assumed non-spanning tree connection, any bpdu seen on the port leads to port err-disable<br />
Network - assumed to STP capable device, handles STP in fast bridging<br />
<br />
To configure<br />
by port<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42767734-1"><span>config t</span>
<span>interface ethernet x/n/x</span>
<span>spanning tree port type edge|normal|network</span>
</code></pre>
<br />
or globally<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-42767734-2"><span>config t</span>
<span>spanning tree port type edge|normal|network default</span>
</code></pre>
</div>


<div>
<blockquote>
Normal port can be connected to &nbsp;Hosts or to Switches. &nbsp; so Normal port does not understand STP ?
</blockquote>
No. &nbsp;Normal ports understand STP. &nbsp;Actually, all ports understand STP. <br />
<br />

<blockquote>
Network Port , understands STP. &nbsp; &nbsp;how do you make a port as &nbsp;Network port ?
</blockquote>
spanning-tree port type network<br />
<br />

<blockquote>
Edge port , I believe it does not understand STP &nbsp;, if you connect it to a Switch, what would happen ? 
</blockquote>
No. &nbsp;It depends on the configuration, but if an edge port is connected to a switch, the port go into error-disable mode.
</div>


jskfan

<div>
So. &nbsp; Ive got to ask. &nbsp;Would it be better if I just ceased answering or would that hinder the ability to repeat my answers?
</div>


<div>
Sorry for keeping asking. I need to be clear on the subject<br />
<br />
&lt;&lt;Edge - assumed non-spanning tree connection, any bpdu seen on the port leads to port err-disable&gt;&gt;<br />
<br />
This sounds like an access port with BPDU Guard enabled.<br />
<br />
<br />
Network Port:&lt;&lt;network port is connected to a spanning tree aware device (bridge or switch).&gt;&gt;<br />
<br />
This sounds like a trunk port<br />
<br />
<br />
Normal Port : If it understands STP then it can act as Network Port when connected to a Switch.<br />
it sounds like it should not be put for Client computers to connect to, otherwise if someone remove a PC and puts a switch it can create a TCN
</div>


<div>
<div class="content wysiwyg-content">
Spanning Tree Network Ports vs Normal Ports<br />
<br />
In Cisco link :<a href="https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/SpanningEnhanced.html" rel="ugc">https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/SpanningEnhanced.html</a><br />
it talks about Network Ports and Normal Ports.<br />
To me both sounds like Trunk Ports.<br />
<br />
Any clarifications on that ?<br />
<br />
Thank you
</div>
</div>


Spanning Tree Network Ports vs Normal Ports

In Cisco link :https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/SpanningEnhanced.html
it talks about Network Ports and Normal Ports.
To me both sounds like Trunk Ports.

Any clarifications on that ?

Thank you

Spanning Tree Network Ports vs Normal Ports

A router is a networking device that forwards data packets between computer networks. Routers perform the "traffic directing" functions on the Internet. The most familiar type of routers are home and small office cable or DSL routers that simply pass data, such as web pages, email, IM, and videos between computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks up to the powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone. Though routers are typically dedicated hardware devices, use of software-based routers has grown increasingly common.

Routers

A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

Switches / Hubs

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.