From: Alexei Monastyrnyi (alexeim@orcsoftware.com)
Date: Wed May 09 2007 - 10:54:53 ART
Yep, would be nice to see 7.2.3 promoted to GD :-)
A quick update on my case, all works fine with smnp-server commands if
there is not too many of them :-)
In my case I have just removed one line
snmp-server host inside A.B.C.D community xxxx version 2c
leaving a great deal of snmp config in place.
funny :-)
A.
on 5/9/2007 3:14 PM Farrukh Haroon wrote:
> no problem :)
>
> ASA code has lots of bugs, and now we have 8.0 and the marketing buzz is
> "120+ new features for SSL etc.", so imagine how many more bugs those
> features will bring in :)
>
> and all this code is still marked ED by Cisco AFAIK, so I hope we see
> something like GD for ASA/PIX sometime soon.
>
> Regards
>
> Farrukh
>
> On 5/9/07, Alexei Monastyrnyi <alexeim@orcsoftware.com> wrote:
>> It helped indeed,
>> thanks, mate!
>>
>> Though I thought I had read carefully all bug-fixes for the latest
>> interim to 7.2.2.
>> Had to upgrade to 7.2.2 from 7.2.1 because of passive FTP stall issue
>> and now this one... :-)
>>
>> Any suggestion, BTW, why they keep 7.0, 7.1 and 7.2 at the same time?
>> Looks ill. :-)
>>
>> A.
>>
>> on 5/9/2007 1:46 PM Farrukh Haroon wrote:
>>> This is the CSCsg87808 Bug
>>> Use the 'Bug Toolkit' to search for it
>>>
>>> CCO:
>>>
>>> *Symptom:*
>>> If snmp-server commands are configured, in a rare corner case
>>> the configuration might fail to save to flash and give the error like
>>> below:
>>>
>>> pix# wr mem
>>> Cryptochecksum: ee8f5816 e1ce1ad7 83151424 f1a3b6fc %Error
>>> reading system:/running-config (Configuration line too long)
>>> Error executing command [FAILED]
>>>
>>> *Conditions:*
>>> The firewall must have snmp-server commands configured and running
>>> version 7.2(1)25 or greater (includes 7.2(2)).
>>>
>>> *Workaround:*
>>> Remove the snmp-server commands from the configuration
>>> -or-
>>> downgrade to a version of code previous to 7.2(1)25
>>>
>>> HTH
>>>
>>> Farrukh
>>>
>>>
>>> On 5/9/07, Alexei Monastyrnyi <alexeim@orcsoftware.com> wrote:
>>>> Hi List.
>>>>
>>>> Just wanted to ask if someone has ever come across such.
>>>>
>>>> pix(config)# wr me
>>>> Building configuration...
>>>> Cryptochecksum: 3f902968 e384da03 b938eff6 1bf4fb4f
>>>>
>>>> %Error reading system:/running-config (Configuration line too long)
>>>> Error executing command
>>>> [FAILED]
>>>> pix(config)# copy run start
>>>>
>>>> Source filename [running-config]?
>>>> Cryptochecksum: 3f902968 e384da03 b938eff6 1bf4fb4f
>>>>
>>>> %Error reading system:/running-config (Configuration line too long)
>>>>
>>>> Problem appeared after upgrading to 7.2.2 on my failover pair of PIXes.
>>>> System can read and save running config on stanalone PIX 515 with 7.2.2
>>>> in another location just fine.
>>>>
>>>> Workaround so far is to save running-config with help of terminal
>>>> logging and then pick it to startup-config via TFTP.
>>>>
>>>> Any hint would be highly appreciated.
>>>>
>>>> A.
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:20 ART