Solved

Error: SMLT VLAN must have i-sid association.


Userlevel 6
Badge

Hi,

Getting the error below but can’t understand what it is requiring me to do:

Error: SMLT VLAN must have i-sid association.

The VIST is up an running:


************************************************************************************
Command Execution Time: Wed Apr 07 07:43:06 2021 GMT
************************************************************************************
====================================================================================================
IST Info
====================================================================================================
PEER-IP VLAN ENABLE IST
ADDRESS ID IST STATUS
----------------------------------------------------------------------------------------------------
172.20.250.246 4053 true up


NEGOTIATED MASTER/
DIALECT IST STATE SLAVE
----------------------------------------------------------------------------------------------------
v6.0 Up Slave

Equally the VIST VLAN 4053 has a valid I-SID:

************************************************************************************
                Command Execution Time: Wed Apr 07 08:33:28 2021 GMT
************************************************************************************
====================================================================================================
                                   Vlan I-SID
====================================================================================================
VLAN_ID    I-SID                I-SID NAME

4053       10124053             ISID-10124053

This is the configuration I am adding, and where the error displays:

Core2:1(config)#% interface GigabitEthernet 3/1
Core2:1(config-if)#% encap dot1
Core2:1(config-if)#% name "BSD-SK1"
Core2:1(config-if)#% untagged-frames-discard
Core2:1(config-if)#% default-vlan-id 0
Core2:1(config-if)#% slpp packet-rx
Core2:1(config-if)#% slpp packet-rx-threshold 50
Core2:1(config-if)#% lacp key 301
Core2:1(config-if)#% lacp aggregation enable
Core2:1(config-if)#% lacp mode active
Core2:1(config-if)#% lacp enable
Core2:1(config-if)#% exit
Core2:1(config)#%
Core2:1(config)#% mlt 301
Core2:1(config)#% mlt 301 name "BSD-SK1"
Core2:1(config)#% mlt 301 encapsulation dot1q
Core2:1(config)#% interface mlt 301
Core2:1(config-mlt)#% lacp key 301
Core2:1(config-mlt)#% lacp enable
Core2:1(config-mlt)#% smlt

Error: SMLT VLAN must have i-sid association.

Many thanks in advance

icon

Best answer by Miguel-Angel RODRIGUEZ-GARCIA 7 April 2021, 12:59

Martin,

 

I see the VLAN 1 provisioned to the port 3/1.

 

Mig

View original

4 replies

Userlevel 6
Badge +1

Hi Martin,

 

It seems that some VLANs configured on the port 3/1 or MLT 301 has no i-sid.

check it with :

show vlan member

show vlan i-sid

Mig

Userlevel 6
Badge

Hi Mig,

Thanks for posting a reply.

Provided a small portion of the output below you requested, it covers interface 3/1 in the example above showing VLANs associated to the port and I-SID’s associated to the VLANs.

The MLT is using LACP, so no ports are directly associated to it yet (other then the LACP Key) being dynamic, hence no I-SID is currently directly tied to the MLT at this time - if I’ve understood that correctly.

When the interfaces come up and the MLT is dynamically formed then underlying port / VLAN assignment is then associated to the MLT I believe.

I’m obviously missing a step, but can’t put my finger on it as it all seems in place?

************************************************************************************
Command Execution Time: Wed Apr 07 09:29:02 2021 GMT
************************************************************************************
====================================================================================================
Vlan Port
====================================================================================================
VLAN PORT ACTIVE STATIC NOT_ALLOW
ID MEMBER MEMBER MEMBER MEMBER
----------------------------------------------------------------------------------------------------
1 1/1-1/16,3/1-3/22, 1/1-1/16,3/1-3/22,
4/1-4/22 4/1-4/22

100 3/1 3/1

102 4/2 4/2

104 3/3 3/3

106 4/4 4/4

108 3/5 3/5

110 4/6 4/6

112 3/7 3/7

114 4/8 4/8

116 3/9 3/9

118 4/10 4/10

120 3/11 3/11

122 4/12 4/12

124 3/13 3/13

126 4/14 4/14

128 3/15 3/15

130 4/16 4/16

132 3/17 3/17

134 4/18 4/18

136 3/19 3/19

138 4/20 4/20

200 3/1 3/1

 

************************************************************************************
Command Execution Time: Wed Apr 07 09:30:13 2021 GMT
************************************************************************************
====================================================================================================
Vlan I-SID
====================================================================================================
VLAN_ID I-SID I-SID NAME
----------------------------------------------------------------------------------------------------
1
100 12120100 ISID-12120100
102 12120102 ISID-12120102
104 12120104 ISID-12120104
106 12120106 ISID-12120106
108 12120108 ISID-12120108
110 12120110 ISID-12120110
112 12120112 ISID-12120112
114 12120114 ISID-12120114
116 12120116 ISID-12120116
118 12120118 ISID-12120118
120 12120120 ISID-12120120
122 12120122 ISID-12120122
124 12120124 ISID-12120124
126 12120126 ISID-12120126
128 12120128 ISID-12120128
130 12120130 ISID-12120130
132 12120132 ISID-12120132
134 12120134 ISID-12120134
136 12120136 ISID-12120136
138 12120138 ISID-12120138
200 12120200 ISID-12120200

Thanks.

Userlevel 6
Badge +1

Martin,

 

I see the VLAN 1 provisioned to the port 3/1.

 

Mig

Userlevel 6
Badge

Ah, well spotted!

That’s caught me out before, those ports should have already been removed from VLAN 1

Removed VLAN 1 from those ports and all now sorted.

Thanks for the insight.

Cheers,

Martin

Reply