Oneview default scripts don't support A/B/C EOS devices?

[Rahman_Duran1]

Hi,

When I try to run default scripts like ModBPConfigBasic in OneView on A4H124-48, it fails. I looked to script's code and it seems it is not for EOS?

So all these predefined scripts are for XOS?

Thanks.

[Frank_Thomas]

Oneview scripting you can escape the TCL parsing by using CLI

An example of using a script against an K10 EOS switch

#@MetaDataStart#############################################################################################
# Define your user parameters in this section. For reference, see bundled scripts.
#############################################################################################
#@MetaDataEnd
# Enter all CLI commands from here
# EXOS CLI stype if statement (case sensitive : NO)
IF (!$match($isExos,true) ) THEN
Echo "$deviceIP is an EXOS switch."
enable ports $port
ELSE
Echo "$deviceIP is NOT and EXOS switch"
CLI set port enable $port
ENDIF

I believe most if not all the oneview scripts were ported for Ridgeline and are XOS based. There are a few example scripts to show how to do things for both.

[Rahman_Duran1]

Hello Mike,

Yes I see. But if I want to write scripts for EOS, I cant use "set" command as it is a TCL reserved keyword also. So "set vlan create 10" line fails.

I used inventory manager for scripting with success. But I don't want to use jlnp interfaces if I can use OneView (really when will we get rid of the jlnp interfaces for the sake of OneView?).

So is it possible to use TCL (because it's use of variables/form inputs are good) and EOS?

Thanks,

Rahman

[Mike_Thomas]

Hello Rahman,
The default scripts are for XOS devices. They are more script driven then EOS devices, which are more MIB-OID driven.
But custom scripts can be done in Oneview and console.
In Oneview they are in Administration->Scripting Tab.
An overview is in the help file. See partial screenshot below.