[c-nsp] Cisco trunk port startup delay

[Tom Storey]

If they are connecting to servers, do you really need spanning tree?

I assume that spanning tree is blocking for x period of time, where x is
long or short depending on whether portfast is enabled.

If you remove spanning tree then there is no blocking, and it should come
up and be able to pass traffic as quickly as MAC tables can update?



On 11 July 2013 01:32, Shanawaz Batcha <ismath.shaan at gmail.com> wrote:

> Hi Guys,
>
> Question for you is how soon can we get a cisco trunk port (connecting to
> some enterprise servers) to initialize and pass traffic.
>
> From
>
> interface GigabitEthernet4/40
>
> switchport
>
> switchport trunk encapsulation dot1q
>
> switchport trunk native vlan 104
>
> switchport mode trunk
>
> spanning-tree bpduguard enable
>
> end
>
>
> With the above configuration, we were losing about 50 pings for an if-down
> event
>
> Enabling "portfast trunk" (no redundant connections), we lost somewhere
> between 10 and 15 pings. Which is way better.
>
> Running "switchport nonegotiate" to disable DTP gives me another ~2 seconds
>
> Disabling inline power and "disabling lldp" gives me another ~1 or 2
> seconds
>
> We are still losing about 6 pings. Anything else people do/tune to get
> quicker convergence if I may call it?
>
> Regards,
> Shan
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>