[c-nsp] IOS 12.4 and NAT

[Brian Vowell]

So it is safe to say that 12.3(14)T1 and 12.4(1) are twins?  I'm having 
the exact same problems with both releases, and the features available 
at the CLI appear to be the same. 

I've got 12.3(14)T1 loaded now, and it crashes about once per hour.  The 
info you request below (crashinfo file) is quite large.  I don't think 
posting that to the list would help, but I have been saving it.


--b

Rodney Dunn wrote:

>Instead of just saying "my box crashes blah blah blah" can
>you put some context around it?
>
>ie:
>sh ver
>sh stack
>crashinfo file
>configuration
>
>If there is a systemic problem with 12.4(1) I'll defer it and remove
>it from CCO if the problem is bad enough. 12.4(1) is no different
>than any of the T releases. After a mainline 1st release then it's
>bugfix only moving forward.
>
>So it goes:
>
>12.3(1st)T 12.3(2nd)T ..etc..  12.4(1)  ... 12.4(2)->bugfix only
>  |--------------newfeartures--------| |----------------->
>
>The first release of the mainline will have new features.
>
>But that doesn't justify bugs although it does increase the chances
>of them being there.
>
>Rodney
>
>On Wed, May 04, 2005 at 04:06:03AM -0700, Brian Vowell wrote:
>  
>
>>Well ours is a 1721, so I'm assuming the code is substantially 
>>different.  This same router with the smaller config is also crashing 
>>quite a bit under 12.3(14)T1.  It's crashing about once per hour, so I 
>>may have to drop it down to 12.3 mainline to get it to quit acting up.
>>
>>
>>--b
>>
>>Denny Reiter wrote:
>>
>>    
>>
>>>On Tue, May 03, 2005 at 04:34:30PM -0700, Brian Vowell wrote:
>>> 
>>>
>>>      
>>>
>>>>I could not get NAT to allow any translations without the enable 
>>>>command.  I've been having all sorts of problems with 12.4(1) all day, 
>>>>so I downgraded to 12.3(14)T1, and the command shows up there too.
>>>>
>>>>What hardware are you running 12.4(1.2) on?
>>>>   
>>>>
>>>>        
>>>>
>>>7206VXR with an NPE-G1
>>>
>>>We were running 12.3(14)T1 but couldn't keep it stable.  A crash
>>>was guaranteed within 3 days.  I was also running it on a new router
>>>yet to be put into service and it logged spurious memory access
>>>errors all over the place with absolutely no traffic running through
>>>it.
>>>
>>>
>>>Denny
>>> 
>>>
>>>      
>>>
>>_______________________________________________
>>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/
>>    
>>