According to [1], reload reason was added in 15.0(1)M. [1] Cisco IOS Configuration Fundamentals Command Reference, R through setup: http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_r1.html#wp1078590
On 10/10/2013 04:04 AM, Luis Miguel Cruz Miranda wrote: > Which IOS are you using? > > El 08/10/13 09:53, Octavio Alvarez escribió: >> Wait a minute... My router supports "reload reason" already and rejects >> "reload int 10". >> >> Check later IOS versions. >> >> On 10/07/2013 12:05 PM, Pete Lumbis wrote: >>> The two outputs do have different warnings: >>> >>> reload reason: >>> =========================== >>> Router#reload >>> Proceed with reload? [confirm] >>> =========================== >>> >>> =========================== >>> Router#reload in 5 >>> Reload scheduled in 5 minutes by console >>> Reload reason: Reload Command >>> Proceed with reload? [confirm] >>> =========================== >>> >>> >>> >>> On Mon, Oct 7, 2013 at 11:46 AM, Octavio Alvarez >>> <alvar...@alvarezp.ods.org <mailto:alvar...@alvarezp.ods.org>> wrote: >>> >>> On 10/07/2013 05:30 AM, Pete Lumbis wrote: >>> > If we fix the behavior what does the fix look like? Do we not >>> allow any >>> > reason that starts with "i"(in) "c" (cancel) or "a"(at)? But then >>> what if >>> > you want a reload reason of "reload installing new software"? >>> Should this >>> > be blocked? >>> >>> Create "reload reason blahblah" and deprecate "reload blahblah". Issue a >>> warning each time "reload blahblah" happens. >>> >>> Also have different confirmation messages. "Reload in 10" could have >>> "Proceed with reload in 10?" while the other could be "Proceed with >>> immediate reload?" >>> >>> >> _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/