11 Replies Latest reply: Feb 25, 2012 5:09 AM by Ian Levick RSS

Custom device template for Moxa EDS-P510 switch

prenticet
Currently Being Moderated

Good morning, I'm working on a custom template for these menu driven switches.  When you connect on telnet the first prompt is to set terminal type as vt100 or vt 52.  The default is vt100, so you can just press enter to continue.  The next prompt is username and password.  Admin is the default user, so you can just Downarrow to the password field.  So then you enter the password and press enter to enter the switch menu.   Here is what I have so far for the template

<Configuration-Management Device="Moxa" SystemOID=" 1.3.6.1.4.1.8691.7.19.1">
 <Commands>
  <Command Name="RESET" Value=""/>
  <Command Name="Reboot" Value=""/>
  <Command Name="RebootAt" Value=""/>
  <Command Name="EnterConfigMode" Value=""/>
  <Command Name="ExitConfigMode" Value="/>
  <Command Name="Startup" Value=""/>
  <Command Name="Running" Value=""/>
  <Command Name="DownloadConfig" Value=""/>
  <Command Name="UploadConfig" Value=""/>
  <Command Name="DownloadConfigIndirect" "/>
  <Command Name="UploadConfigIndirect" Value=""/>
  <Command Name="EraseConfig" Value=""/>
  <Command Name="SaveConfig" Value=""/>
  <Command Name="Version" Value=""/>
  <Command Name="PreCommand" Value="${CRLF}" Delay="3"/>
  <Command Name="PreCommand" Value"${Downarrow}"/>
  <Command Name="PreCommand" Value="(my password value here)${CRLF}"/>
  <Command Name="Menubased" Value="true"/>
 </Commands>

The file is named Moxa-1.3.6.1.4.1.8691.7.19.1.ConfigMgmt-Commands

After resetting server for everything to be clean, when I try to login to a device I get the "No device template for 1.3.6.1.4.1.8691.7.19.1 Device IP: x.x.x.x" 

If I then force it to use the moxa template rather than Auto, I get "unable to locate the device template Moxa"

Where am I going wrong?

Thank you.

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    I have just upgraded all our 408A/508A today with new firmware V3 which supports CLI, found a few issues with NCM, but can now download configs from the integrated web interface. Would upgrading to V3 be an option in your case as I see it is listed as available for your hardware on the Moxa site?

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    Yes we can download in NCM, but we did have a few issues!! When I try to download the configs manually via NCM, I get a message “cannot log into device bad password” however if you try executing the command “show running-config” it will display the config, also when hitting the download config from the web integration it will successfully download the config.


    Also, when I try to validate login credentials against the device, also get the bad password message.  


    Moxa tech support suspect the issue is with NCM(we are running 6.1), however he is yet to confirm.


    You may also need to reboot the device after the firmware upgrade as some of our Moxa’s would not allow an SNMP connection straight after firmware upgrade.

    • Re: Custom device template for Moxa EDS-P510 switch
      Ian Levick
      Currently Being Moderated

      Here is the template.

       

      <!--SolarWinds Network Management Tools-->
      <!--Copyright 2005 SolarWinds.Net All rights reserved-->
      <Configuration-Management Device="MOXA Switches" SystemOID="1.3.6.1.4.1.8691.7">
       <Commands>
        <Command Name="RESET" Value="terminal length 0"/>
        <Command Name="Reboot" Value="reload${CRLF}y${CRLF}"/>
        <Command Name="EnterConfigMode" Value="configure"/>
        <Command Name="ExitConfigMode" Value="exit"/>
        <Command Name="Startup" Value="startup-config"/>
        <Command Name="Running" Value="running-config"/>
        <Command Name="DownloadConfig" Value="copy running-config${CRLF}${StorageAddress}${CRLF}${StorageFilename}${CRLF}"/>
        <Command Name="UploadConfig" Value="copy tftp running-config${CRLF}${StorageAddress}${CRLF}${StorageFilename}${CRLF}Y${CRLF}${CRLF}"/>
        <Command Name="DownloadConfigIndirect" Value="copy ${ConfigType}${CRLF}${StorageAddress}${CRLF}${StorageFilename}${CRLF}"/>
        <Command Name="UploadConfigIndirect" Value="copy tftp running-config${CRLF}${StorageAddress}${CRLF}${StorageFilename}${CRLF}"/>
        <Command Name="SaveConfig" Value="save"/>
        <Command Name="Version" Value="show version"/>
        <Command Name="EnableCommand" Value="${CRLF}"/>
        <Command Name="MenuBased" Value="false"/>
       </Commands>
      </Configuration-Management>

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    In NCM device settings, we have the following so try setting the enable level to "enable 0", Execute scrips using "Telnet", request configs using "Telnet" and transfer configs using "TFTP"

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    I will try with SSH/SCP when Moxa can tell me where they have "hidden" this feature which they currently advertise on their web site, there is not a mention of these in their CLI manual from earlier this year.

    May have to wait until firmware 3.1????? 

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    Also add these custom macro's

    ${StorageAddress} [IP of your NCM server]

    ${StorageFileName} config.ini

  • Re: Custom device template for Moxa EDS-P510 switch
    Ian Levick
    Currently Being Moderated

    Ok, well if this works in NCM7, can anybody confirm if there are any known issues/bugs with 6.1 downloading device configs with the current device template?

More Like This

  • Retrieving data ...