No MSTP on SRX210H?

[keithr]

protocols {
    ##
    ## Warning: configuration block ignored: unsupported platform (srx210h)
    ##
    mstp {
        configuration-name mstp-test;
    }
}

*sigh*

This is a product that comes out the box configured to put its ports into switching mode.

As the Guinness commercials succinctly proclaim ---   BRILLIANT!!!!!

[dfex]

Yep, RSTP only on SRX. Should interoperate well though, as long as you didn't want the SRX as the root bridge of your MSTP domain ; )

[keithr]

These kind of things just blow my mind, though.

The SRX240 supports MSTP.  I don't know about the 220.

RSTP is fine from an operational standpoint, but when one is trying to keep a standardized configuration and basic protocol support isn't in the equipment, it just evokes facepalms and causes migraines.

[motd]

Maybe its version-specific? Even on my SRX100 I can configure MSTP in 10.4.  The 220 is pretty new and might need 10.4 for all versions to be supported as it usually takes a few releases before new hardware platforms support all features.

I've never seen it as an important limitation though. I try to avoid STP as much as possible. Especially MSTP is more trouble than its worth in my opinion.

[stevilone]

Just checked on my SRX220 Cluster in lab running 10.4R2.7

MSTP config appears to work (as posted above)

SRX220LAB-NODE0# run show version
node0:
--------------------------------------------------------------------------
Hostname: SRX220LAB-NODE0
Model: srx220h
JUNOS Software Release [10.4R2.7]

node1:
--------------------------------------------------------------------------
Hostname: SRX220LAB-NODE1
Model: srx220h
JUNOS Software Release [10.4R2.7]

{primary:node0}[edit]

SRX220LAB-NODE0# set protocols mstp configuration-name mstp-test    

{primary:node0}[edit]
SRX220LAB-NODE0# commit check
node0:
configuration check succeeds
node1:
configuration check succeeds

[keithr]

That SRX210 that I copied that config message from is running 10.4R2.7 (frightening, I know...)

I have a SRX240 running 10.2R3.10 that takes MSTP config just fine.  In fact I'm using it to do a multi-path failover between the SRX240 and a Brocade FESX.  One link has our NetEqualizer on it, the other link is a backup and doesn't.  If the NE fails, there's no downtime.

I'm not a huge fan of STP in general, either, but it has its uses.  I don't find MSTP all that much trouble, a few basic config steps and it usually works a charm.  In cases where devices are set to switching mode, I think it's a good idea to have STP around.

[keithr]

It commits fine on my SRX210.  Check your configuration, though, does your protocols -> mstp block contain the comment like the excerpt I posted saying it's being ignored?

If you do a "show spanning-tree interface" do you get results that show MSTP is running, or do you get "spanning-tree is not enabled at a global level" as I do?

[motd]

Its working on my srx100 but the detailed comments are interesting:

##
## protocols: Routing protocol configuration
## require: routing
## package: jkernel_usp
##
##
## mstp: Multiple Spanning Tree Protocol options
## products: m5, m10, m20, m40, m160, t640, t320, m40e, TX Matrix, ggsn-c, m320, m7i, m10i, j2300, j4300, j6300, m120, mx960, j4350, j6350, jsr2300, jsr4300, jsr6300, jsr4350, jsr6350, j2320, j2350, jsr2320, jsr2350, mx480, sumatra, ex3200-24t, ex3200-24p, ex3200-48t, ex3200-48p, ex4200-24f, ex4200-24t, ex4200-24p, ex4200-48t, ex4200-48p, ex8208, ex8216, mx240, txp, srx240b, srx240h, srx240h-poe, srx240h-p-m, srx630, srx650, srx680, srx100b, srx100h, srx100b-wl, srx100h-wl, srx100b-vdsl, srx100h-vdsl, srx100h-wl-vdsl, ex2200-24t-4g, ex2200-24p-4g, ex2200-48t-4g, ex2200-48p-4g, ln1000-v, fx1600_48, fx2160_48, sng-8s, ex4500-40f, mx80, mx80-48t, sng-16s, ex-xre, srx240h-dc

I might be getting blind, but I don't see the 210 in there. Thats crazy, its an old platform, I always assumed it to be identical to any other branch SRX. Some interesting new model numbers in there though

[stevilone]

Yes, you are correct, I did a dangerous thing by attempting to commit on the cluster (since switching is not support in cluster mode)  but it does produce the same message

protocols {
    ##
    ## Warning: configuration block ignored: unsupported platform (srx220h)
    ##
    mstp {
        configuration-name mstp-test;
    }
}

[mdheavy]

Confirmed on my SRX210H-POE, while it works fine on my SRX100B.  This is a good find...  I don't think this is a deal-breaker for any practical reasons, but I'm taking it into consideration for future lab purchases

http://www.juniper.net/us/en/local/pdf/app-notes/3500196-en.pdf
• On J Series platforms, Ethernet switching is supported on only one universal PIM (uPIM) per J Series chassis.
• MSTP is not supported on the SrX210.
• The IgMP snooping and Q-in-Q feature is not available for the SrX100.
• The J Series and SrX100 do not support advanced 802.1x features such as dynamic VLAN, guest VLAN, server-
• reject VLAN, server fail operations, and VoIP VLAN. But rAdIuS accounting and MAC authentication are available for
the SrX100.