We are a long-time Enterasys shop migrating to Extreme/EXOS equipment. After a GREAT deal of effort I finally got Netsight Inventory Manager to do an acceptable automated backup of our new Summit EXOS switches, but I sincerely hope that there is an easier way than the one I used.
First, although a machine-readable binary config file is “nice” and the binary “CFG” file is necessary as the one that the switch will load from, the really critical component of any switch backup is an ASCII version that is human-readable in an editor. I figured out that in the EXOS environment this means a file-type of “.xsf”. In fact, Netsight seems to require that this ASCII version exist in the form of an “nms.xsf” file on the switch because my Netsight backup would simply not run until I had that exact file name there.
Unfortunately, it looks to me as though the only way to get this XSF file is by the “Save Config As-Script” command in the EXOS switch. What this seems to imply is that to do a valid “save” I must issue two separate commands each-and-every time; a “save config primary” and also a “save config as-script nms”. This is very awkward. Is there any way to generate both of these required files with a single command?
I suppose that an alternative that would make even more
sense would be if Netsight were smart enough to “translate” the binary “cfg”
file into an ASCII version automatically whenever it does a backup, since it
will always be necessary anyway. Is this planned?
How do other folks handle this? Do we really need to remember to issue 2 different Save commands all the time?