Source of ${Reset} command?

Question

Hey Everyone, I currently have a support case open with tech support (Case #19886) regarding the below issue. I thought I would also throw it out here to see if anyone has any ideas: We have a scheduled job that runs every morning that copies the startup configuration of 16 Enterasys XP2400 and 8600 routers. It apperas that Cirrus is somehow issuing a ${Reset} command during that scheduled job. Here is the command in question taken from the session trace logs: --> dc-ssr# Process Line = <> Process Line = <-- ${Reset} --> ${Reset} --> 2007-10-06 04:53:07 %CLI-E-FACUNKNWN, Telnet user (Unknown:10.4.1.66), unknown or ambiguous facility '${Reset}' --> dc-ssr# Process Line = <${Reset}> Process Line = <2007-10-06 04:53:07 %CLI-E-FACUNKNWN, Telnet user (Unknown:10.4.1.66), unknown or ambiguous facility '${Reset}'> I have removed the ${RESET} and the ${REBOOT} entry from the Enterasys/Cabletron Device Command Template that the devices are configured to use. I also removed the command from the generic template. There is no ${Reset} command in the script being used. I have sent the session trace logs and the device template directory to tech support and they have not found the source either. Am I missing something obvious?

Slider · Answer

After working off and on with Tech Support for a couple weeks this was their latest response:

"this looks to be something that Cirrus is going in the way the job runs. I don't know that there is a way to change or stop it."

willhepptemp · Answer

Not sure if you're missing something but I see the same behavior under Extreme XOS devices. The weird thing is that the config template for Extreme has the correct syntax ('disable clipaging') but whatever Cirrus is doing makes the command not function correctly. No idea why/how/where...

Will