Mailing List Archive

Cisco equivalent of 'portfast' on FCX?
Nothing jumping out at me:

#spanning-tree ?
802-1w Disable or enable IEEE 802.1W parameters
designated-protect Declare the port to be on Designated guard for
all
spanning trees
root-protect Declare the port to be on Root guard for all
spanning
trees
<cr>

I'm guessing something like:

#no spanning-tree
#stp-bdpu-guard

Any clues?

--
Randy M.

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: Cisco equivalent of 'portfast' on FCX? [ In reply to ]
Hi Randy,
Under the port config you can set it to admin edge

port x/y
spanning-tree 802-1w admin-edge-port

BR
Salman


On Mon, Jun 16, 2014 at 6:22 AM, Randy McAnally <rsm@fast-serv.com> wrote:

> Nothing jumping out at me:
>
> #spanning-tree ?
> 802-1w Disable or enable IEEE 802.1W parameters
> designated-protect Declare the port to be on Designated guard for all
> spanning trees
> root-protect Declare the port to be on Root guard for all
> spanning
> trees
> <cr>
>
> I'm guessing something like:
>
> #no spanning-tree
> #stp-bdpu-guard
>
> Any clues?
>
> --
> Randy M.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
Re: Cisco equivalent of 'portfast' on FCX? [ In reply to ]
Hi,

btw, there is a "no spanning-tree", but you need to configure it per vlan.

SSH@xxx(config)# vlan 3000
SSH@xxx(config-vlan-3000)#no sp
spanning-tree Set spanning tree for this VLAN
SSH@xxx(config-vlan-3000)#no spanning-tree

kind regards
Rolf

> Nothing jumping out at me:
>
> #spanning-tree ?
> 802-1w Disable or enable IEEE 802.1W parameters
> designated-protect Declare the port to be on Designated guard for
> all
> spanning trees
> root-protect Declare the port to be on Root guard for all
> spanning
> trees
> <cr>
>
> I'm guessing something like:
>
> #no spanning-tree
> #stp-bdpu-guard
>
> Any clues?
>
> --
> Randy M.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>


_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: Cisco equivalent of 'portfast' on FCX? [ In reply to ]
Hello Folks,

You can do this with "Fast Span" or "Fast Uplink Span". Although it won't display in the running config, this is already enabled by default

Here's the details from our manual:
----------------------------------------------------------------------------------------------------------------------
Fast Port Span

When STP is running on a device, message forwarding is delayed during the spanning tree
recalculation period following a topology change. The STP forward delay parameter specifies the
period of time a bridge waits before forwarding data packets. The forward delay controls the
listening and learning periods of STP reconvergence. You can configure the forward delay to a
value from 4-30 seconds. The default is 15 seconds. Thus, using the standard forward delay,
convergence requires 30 seconds (15 seconds for listening and an additional 15 seconds for
learning) when the default value is used.

This slow convergence is undesirable and unnecessary in some circumstances. The Fast Port
Span feature allows certain ports to enter the forwarding state in four seconds. Specifically, Fast
Port Span allows faster convergence on ports that are attached to end stations and thus do not
present the potential to cause Layer 2 forwarding loops. Because the end stations cannot cause
forwarding loops, they can safely go through the STP state changes (blocking to listening to learning
to forwarding) more quickly than is allowed by the standard STP convergence time. Fast Port Span
performs the convergence on these ports in four seconds (two seconds for listening and two
seconds for learning).

In addition, Fast Port Span enhances overall network performance in the following ways:

. Fast Port Span reduces the number of STP topology change notifications on the network.

When an end station attached to a Fast Span port comes up or down, the Brocade device does
not generate a topology change notification for the port. In this situation, the notification is
unnecessary since a change in the state of the host does not affect the network topology.

. Fast Port Span eliminates unnecessary MAC cache aging that can be caused by topology
change notifications.

Bridging devices age out the learned MAC addresses in their MAC caches
if the addresses are unrefreshed for a given period of time, sometimes called the MAC aging
interval. When STP sends a topology change notification, devices that receive the notification
use the value of the STP forward delay to quickly age out their MAC caches. For example, if a
device normal MAC aging interval is 5 minutes, the aging interval changes temporarily to the
value of the forward delay (for example, 15 seconds) in response to an STP topology change.
In normal STP, the accelerated cache aging occurs even when a single host goes up or down.
Because Fast Port Span does not send a topology change notification when a host on a Fast
Port Span port goes up or down, the unnecessary cache aging that can occur in these
circumstances under normal STP is eliminated.

Fast Port Span is a system-wide parameter and is enabled by default. Thus, when you boot a
device, all the ports that are attached only to end stations run Fast Port Span. For ports that are not
eligible for Fast Port Span, such as ports connected to other networking devices, the device
automatically uses the normal STP settings. If a port matches any of the following criteria, the port
is ineligible for Fast Port Span and uses normal STP instead:

. The port is 802.1Q tagged
. The port is a member of a trunk group
. The port has learned more than one active MAC address
. An STP Configuration BPDU has been received on the port, thus indicating the presence of
another bridge on the port.

You also can explicitly exclude individual ports from Fast Port Span if needed. For example, if the
only uplink ports for a wiring closet switch are Gbps ports, you can exclude the ports from Fast Port
Span.

Disabling and re-enabling Fast Port Span

Fast Port Span is a system-wide parameter and is enabled by default. Therefore, all ports that are
eligible for Fast Port Span use it.
To disable or re-enable Fast Port Span, enter the following commands.
Brocade(config)# no fast port-span
Brocade(config)# write memory

To re-enable Fast Port Span, enter the following commands.

Brocade(config)# fast port-span
Brocade(config)# write memory

----------------------------------------------------------------------------------------------

Fast Uplink Span

The Fast Port Span feature described in the previous section enhances STP performance for end
stations. The Fast Uplink Span feature enhances STP performance for wiring closet switches with
redundant uplinks. Using the default value for the standard STP forward delay, convergence
following a transition from an active link to a redundant link can take 30 seconds (15 seconds for
listening and an additional 15 seconds for learning).

You can use the Fast Uplink Span feature on a Brocade device deployed as a wiring closet switch to
decrease the convergence time for the uplink ports to another device to just one second. The new
Uplink port directly goes to forward mode (bypassing listening and learning modes). The wiring
closet switch must be a Brocade device but the device at the other end of the link can be a Brocade
device or another vendor's switch.

Configuration of the Fast Uplink Span feature takes place entirely on the Brocade device. To
configure the Fast Uplink Span feature, specify a group of ports that have redundant uplinks on the
wiring closet switch (Brocade device). If the active link becomes unavailable, the Fast Uplink Span
feature transitions the forwarding to one of the other redundant uplink ports in just one second. All
Fast Uplink Span-enabled ports are members of a single Fast Uplink Span group.

NOTE
To avoid the potential for temporary bridging loops, Brocade recommends that you use the Fast
Uplink feature only for wiring closet switches (switches at the edge of the network cloud). In
addition, enable the feature only on a group of ports intended for redundancy, so that at any given
time only one of the ports is expected to be in the forwarding state.

NOTE
When the wiring closet switch (Brocade device) first comes up or when STP is first enabled, the
uplink ports still must go through the standard STP state transition without any acceleration. This
behavior guards against temporary routing loops as the switch tries to determine the states for all
the ports. Fast Uplink Span acceleration applies only when a working uplink becomes unavailable.

Active uplink port failure

The active uplink port is the port elected as the root port using the standard STP rules. All other
ports in the group are redundant uplink ports. If an active uplink port becomes unavailable, Fast
Uplink Span transitions the forwarding of traffic to one of the redundant ports in the Fast Uplink
Span group in one second bypassing listening and learning port states.
Switchover to the active uplink port

When a failed active uplink port becomes available again, switchover from the redundant port to
the active uplink port is delayed by 30 seconds. The delay allows the remote port to transition to
forwarding mode using the standard STP rules. After 30 seconds, the blocked active uplink port
begins forwarding in just one second and the redundant port is blocked.

NOTE
Use caution when changing the spanning tree priority. If the switch becomes the root bridge, Fast
Uplink Span will be disabled automatically.

Configuring a Fast Uplink port group

To configure a group of ports for Fast Uplink Span, enter the following commands:
Brocade(config)# fast uplink-span ethernet 1/2/1 to 1/2/4
Brocade(config)# write memory


----------------------------------------------------------------------------------------------------------------







-----Original Message-----
From: foundry-nsp [mailto:foundry-nsp-bounces@puck.nether.net] On Behalf Of "Rolf Hanßen"
Sent: Monday, June 16, 2014 12:20 AM
To: rsm@fast-serv.com
Cc: foundry-nsp@puck.nether.net
Subject: Re: [f-nsp] Cisco equivalent of 'portfast' on FCX?

Hi,

btw, there is a "no spanning-tree", but you need to configure it per vlan.

SSH@xxx(config)# vlan 3000
SSH@xxx(config-vlan-3000)#no sp
spanning-tree Set spanning tree for this VLAN
SSH@xxx(config-vlan-3000)#no spanning-tree

kind regards
Rolf

> Nothing jumping out at me:
>
> #spanning-tree ?
> 802-1w Disable or enable IEEE 802.1W parameters
> designated-protect Declare the port to be on Designated guard for
> all
> spanning trees
> root-protect Declare the port to be on Root guard for all
> spanning
> trees
> <cr>
>
> I'm guessing something like:
>
> #no spanning-tree
> #stp-bdpu-guard
>
> Any clues?
>
> --
> Randy M.
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>


_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: Cisco equivalent of 'portfast' on FCX? [ In reply to ]
Also, I think the default is not to use rstp/802.1w, so you will need to
configure that as well. I'm lazy, so I just run 'spanning-tree single
802-1w'. If you have a more complicated VLAN setup, you may need to do
something different. Keep in mind that normal spanning tree and 802-1w
use different show commands. 'show spanning-tree' will give you normal
stp, 'show 802-1w' will give your rstp/802.1w.

SSH@icx6450#show span

Spanning-tree is not configured on port-vlan 4094

L2 VLAN 1 22 to 23 140 999 1041 3000 4000 to 4001 are members of single spanning tree.

SSH@icx6450#show 802-1w

--- VLAN 4094 [ STP Instance owned by VLAN 4094 ] ---------------------------

Bridge IEEE 802.1W Parameters:

Bridge Bridge Bridge Bridge Force tx
Identifier MaxAge Hello FwdDly Version Hold
hex sec sec sec cnt
607c748ef8000000 20 2 15 Default 3

RootBridge RootPath DesignatedBri- Root Max Fwd Hel
Identifier Cost dge Identifier Port Age Dly lo
hex hex sec sec sec
607c748ef8000000 0 607c748ef8000000 Root 20 15 2

Port IEEE 802.1W Parameters:

<--- Config Params --><-------------- Current state ----------------->
Port Pri PortPath P2P Edge Role State Designa- Designated
Num Cost Mac Port ted cost bridge
1/1/1 128 20000 F F DESIGNATED FORWARDING 0 607c748ef8000000
1/1/2 128 20000 F F DESIGNATED FORWARDING 0 607c748ef8000000
1/1/3 128 20000 F F DESIGNATED FORWARDING 0 607c748ef8000000
1/1/4 128 20000 F F DESIGNATED FORWARDING 0 607c748ef8000000
<and so on>



--
Eldon Koyle
Information Technology
Utah State University
--
Mathematics is the only science where one never knows what
one is talking about nor whether what is said is true.
-- Russell

On Jun 16 7:53+0400, salman sadiq wrote:
> Hi Randy,
> Under the port config you can set it to admin edge
>
> port x/y
> spanning-tree 802-1w admin-edge-port
>
> BR
> Salman
>
>
> On Mon, Jun 16, 2014 at 6:22 AM, Randy McAnally <rsm@fast-serv.com> wrote:
>
> > Nothing jumping out at me:
> >
> > #spanning-tree ?
> > 802-1w Disable or enable IEEE 802.1W parameters
> > designated-protect Declare the port to be on Designated guard for all
> > spanning trees
> > root-protect Declare the port to be on Root guard for all
> > spanning
> > trees
> > <cr>
> >
> > I'm guessing something like:
> >
> > #no spanning-tree
> > #stp-bdpu-guard
> >
> > Any clues?
> >
> > --
> > Randy M.
> >
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >

> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
Re: Cisco equivalent of 'portfast' on FCX? [ In reply to ]
Yea, 'spanning-tree 802-1w admin-edge-port' was the answer, works great.
Already had 802.1w configured on each vlan so there was no funny
business.

Thanks for the clue everyone.

~Randy

On 06/16/2014 7:52 pm, Eldon Koyle wrote:
> Also, I think the default is not to use rstp/802.1w, so you will need
> to
> configure that as well. I'm lazy, so I just run 'spanning-tree single
> 802-1w'. If you have a more complicated VLAN setup, you may need to do
> something different. Keep in mind that normal spanning tree and 802-1w
> use different show commands. 'show spanning-tree' will give you normal
> stp, 'show 802-1w' will give your rstp/802.1w.
>
> SSH@icx6450#show span
>
> Spanning-tree is not configured on port-vlan 4094
>
> L2 VLAN 1 22 to 23 140 999 1041 3000 4000 to 4001 are members of
> single spanning tree.
>
> SSH@icx6450#show 802-1w
>
> --- VLAN 4094 [ STP Instance owned by VLAN 4094 ]
> ---------------------------
>
> Bridge IEEE 802.1W Parameters:
>
> Bridge Bridge Bridge Bridge Force tx
> Identifier MaxAge Hello FwdDly Version Hold
> hex sec sec sec cnt
> 607c748ef8000000 20 2 15 Default 3
>
> RootBridge RootPath DesignatedBri- Root Max Fwd Hel
> Identifier Cost dge Identifier Port Age Dly lo
> hex hex sec sec sec
> 607c748ef8000000 0 607c748ef8000000 Root 20 15 2
>
> Port IEEE 802.1W Parameters:
>
> <--- Config Params --><-------------- Current state
> ----------------->
> Port Pri PortPath P2P Edge Role State Designa-
> Designated
> Num Cost Mac Port ted cost bridge
> 1/1/1 128 20000 F F DESIGNATED FORWARDING 0
> 607c748ef8000000
> 1/1/2 128 20000 F F DESIGNATED FORWARDING 0
> 607c748ef8000000
> 1/1/3 128 20000 F F DESIGNATED FORWARDING 0
> 607c748ef8000000
> 1/1/4 128 20000 F F DESIGNATED FORWARDING 0
> 607c748ef8000000
> <and so on>
>
>
>
> --
> Eldon Koyle
> Information Technology
> Utah State University
> --
> Mathematics is the only science where one never knows what
> one is talking about nor whether what is said is true.
> -- Russell

_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp