Header Only - DO NOT REMOVE - Extreme Networks

EMC 8.1 adding vlan to EAPS domain script fails on EXOS switch version 12.4


Our company has in production Netsight 7.1.3.25 we have over 70 EAPS scripts in use and working as designed. Currently, I have recently installed EMC 8.1.0.52 on new VM, I have started mirroring the scripts that I have in Netsight 7 to EMC 8.1 and noticed when I tested the script my vlan does not get configured on older exos switches (12.4.) My questions is, is this a known issue or is there a workaround? Below is an example of the error and the Script I used.

EMC User: tcoronado
EMC User Domain:
CLI Login: r00t
X480-24x_COH_HEC_W 192.168.2.2 2018-01-25 at 09:40:38 CST
create vman plw_vman_test_tibo_fannin_996
* X480-24x_COH_HEC_W.2 #
config vman plw_vman_test_tibo_fannin_996 tag 996
* X480-24x_COH_HEC_W.3 #
disable igmp snooping vlan plw_vman_test_tibo_fannin_996
* X480-24x_COH_HEC_W.4 #
config eaps ch46_coh_fan_hec_ring add protected plw_vman_test_tibo_fannin_996
WARNING: Primary port [25] is not added to vlan "plw_vman_test_tibo_fannin_996", EAPS="ch46_coh_fan_hec_ring"
WARNING: Secondary port [26] is not added to vlan "plw_vman_test_tibo_fannin_996", EAPS="ch46_coh_fan_hec_ring"

* X480-24x_COH_HEC_W.5 #
Error: timeout waiting for data

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

#@MetaDataStart
#@DetailDescriptionStart
##############################################################################
# Purpose : Example script to showcase how to declare a parameter and use it
##############################################################################
#@DetailDescriptionEnd
#@VariableFieldLabel (description = "circuit Name",
# type = String,
# scope = global,
# required = yes
# )
set var vlanname ""
#
#@VariableFieldLabel (description = "circuit Tag", type = String,
# scope = global,
# required = yes
# )
set var vlannametag ""
# Parameter that can take values only from the given list of valid values
#@VariableFieldLabel (description = "Please choose correct service:", validValues = [vman, vlan])
set var foo2 vman
#@MetaDataEnd
# Enter all CLI commands from here

if {[string equal $foo2 "vman"]} {

create vman $vlanname
config vman $vlanname tag $vlannametag
disable igmp snooping vlan $vlanname
config ch46_coh_fan_hec_ring add protected $vlanname
config $vlanname add port $port tagged
regexp {.*could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

else

create vlan $vlanname
config vlan $vlanname tag $vlannametag
disable igmp snooping vlan $vlanname
config ch46_coh_fan_hec_ring add protected $vlanname
config $vlanname add port $port tagged
regexp {.*Adding EAPS ring ports to a VLAN could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

}

5 replies

Userlevel 5
Hi Tiburcio,

Please keep in mind that EXOS 12.4 and XMC aren't compatible. The current recommended version for the X480 is 16.2.4.5. Upgrading may resolve your issue.

Thanks
Brad
Userlevel 6
Hi Tiburcio,
I guess the issue is that XOS is asking for some confirmation what the scripting engine is not aware of (as it is quite old firmware, the testing was not done), while the XMC is waiting for prompt.

Can you please check the CLI output from the switch?
the construct:

regexp {.*could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

does not work in version 8. You will need to tune CLIRules.xml or as you have XMC version 8.0.5+ you can use:

CLI -nowait config $vlanname add port $port tagged

Regards

Z.
Pala, Zdenek wrote:

Hi Tiburcio,
I guess the issue is that XOS is asking for some confirmation what the scripting engine is not aware of (as it is quite old firmware, the testing was not done), while the XMC is waiting for prompt.

Can you please check the CLI output from the switch?
the construct:

regexp {.*could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

does not work in version 8. You will need to tune CLIRules.xml or as you have XMC version 8.0.5+ you can use:

CLI -nowait config $vlanname add port $port tagged

Regards

Z.

Zdenek,

I will update the script and provide feed back if this fixes my issue, thanks.
Userlevel 3
Pala, Zdenek wrote:

Hi Tiburcio,
I guess the issue is that XOS is asking for some confirmation what the scripting engine is not aware of (as it is quite old firmware, the testing was not done), while the XMC is waiting for prompt.

Can you please check the CLI output from the switch?
the construct:

regexp {.*could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

does not work in version 8. You will need to tune CLIRules.xml or as you have XMC version 8.0.5+ you can use:

CLI -nowait config $vlanname add port $port tagged

Regards

Z.

Hi Tiburcio,
not sure if that helps but the following command should remove warning messages when configuring EAPS [and the need to answer y/n] - which may solve your script issue all together?

configure eaps config-warnings off

Thanks, JS
Pala, Zdenek wrote:

Hi Tiburcio,
I guess the issue is that XOS is asking for some confirmation what the scripting engine is not aware of (as it is quite old firmware, the testing was not done), while the XMC is waiting for prompt.

Can you please check the CLI output from the switch?
the construct:

regexp {.*could cause a loop.*} ${CLI.OUT} foundit
IF ([info exists foundit]) THEN
CLI y
ENDIF

does not work in version 8. You will need to tune CLIRules.xml or as you have XMC version 8.0.5+ you can use:

CLI -nowait config $vlanname add port $port tagged

Regards

Z.

Zdenek,

I tried your suggestion and my vlan was not added to the ports in the eaps domain and JS your method had the same results as before.

Reply