MSTP pending instance configuration

[Bruno Aguiar Pina]

Hi,

I have 2 procurves 2848 and i want to reconfigure the mstp. I created pending configuration with 5 instances. I odd vlans to each instance, but when use the command "show spanning-tree pending mst-config" i see the created instances but no vlans are showed in the "Mapped Vlans" column.

This is a bug or i'm doing something wrong?
The commands i used to create de pending spanning tree configuration was:

spanning-tree pending config-name XXX
spanning-tree pending config-revision 1
spanning-tree pending instance 1 vlan 1-4

Thks,

[Mohammed Faiz]

Hi,

I don't have a spare 2848 to test with but the MSTP pending commands work fine on my 2610 (running revision R.11.30).
What do you see if you run:

"show span pending inst ist"

[Bruno Aguiar Pina]

The command "sh spanning pending instance ist" return no additional information.

No vlan associated with the "Mapped Vlans" columns.

Thks

[Mohammed Faiz]

But are the VLANs you are looking for associcated with the IST?

[Mohammed Faiz]

Oh and what software revision are you running?

[Bruno Aguiar Pina]

The firmware revision is I.08.98 and the ROM version is I.08.07.

I Know, i know ... they need to be updated, but I take a look at the most recently software update release notes and didn't find any enhancements or fixes related to this issue.

[Mohammed Faiz]

Well you're not doing anything wrong so it does sound like a bug.
The question is whether the bug is just with the "show" command or whether the vlans aren't being assigned to the pending configuration at all.
The only other command you can try to test is : "show span pending inst 1" and see if they're listed there.

[Gerhard Roets]

Hi Bruno

I would suggest you go and look at the latest software from HP ProCurve.

In I.10.65 Enhancement (PR_0000001316) â The VLAN Assignment mapping to MSTP instances
is enhanced.

and

â   VLAN (PR_0000002103) â The alteration of the VLAN/MSTP instance mapping in the
pending configuration is not properly functioning. Any attempt to remove a single VLAN ID
(VID) from one MSTP instance and then assign it to another MSTP instance will fail, even
while specifying a VID range will succeed.