[c-nsp] %ERROR: Standby doesn't support this command

[Church, Charles]

Arie,

	Thanks, I did confirm that we were seeing the tracebacks.  Since 12.2(54) adds VRF-aware TACACS, I think we need to go to that anyway.  Will give it a shot.

Chuck

-----Original Message-----
From: Arie Vayner (avayner) [mailto:avayner at cisco.com] 
Sent: Sunday, August 01, 2010 10:57 AM
To: Lee; Church, Charles
Cc: nsp-cisco
Subject: RE: [c-nsp] %ERROR: Standby doesn't support this command


This seems to be CSCsx87562.

Can you please see if you got some tracebacks in the log before this
happened?
Something like:
%SYS-3-TIMERNEG: Cannot start timer (0xXXXXXXXX) with negative offset (-
YYYYYYYYYY).

See release notes for more info...

Fix should be in 12.2(54)SG

Arie

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Lee
Sent: Friday, July 30, 2010 21:30
To: Church, Charles
Cc: nsp-cisco
Subject: Re: [c-nsp] %ERROR: Standby doesn't support this command

On 7/30/10, Church, Charles <Charles.Church at harris.com> wrote:
> Anyone,
>
> 	I'm having issues with some 4510s with dual Sup6-E running
> 12.2(53)SG2 doing this on interface range command.  Making our
deployment
> kind of tough:
>
> SCUAS01(config-if)#interface range GigabitEthernet1/1 - 48
> SCUAS01(config-if-range)# switchport mode access
> %ERROR: Standby doesn't support this command
> % Command failed on interface. Aborting
> SCUAS01(config)#

I don't remember the error message, but I've had that same type of
problem where a 'switchport mode access' fails when applied to a
range.  A
default int range g1/1 - 48
int range g1/1 - 48
 switchport mode access
gets around the problem.  But we have very few switches with dual
supervisors, so it might be a work-around for a different problem...

Regards,
Lee


>
> In the release notes it claims a similar issue was fixed:
>
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/O
L_51
> 84.html        CSCsa67042   But that's from a while ago.  I'm told by
our
> installer guy that occasionally it is accepted, seems to depend on if
the
> switch was recently rebooted, he claims.  The interface type is
correct.  I
> tried using bug navigator, but it's not giving me any results, not
sure if
> it's working right today, or if I've got a browser issue.  Any help
> appreciated.
>
> Thanks,
>
> Chuck
>
>
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/