Strange behaviour of AS5350

Strange behaviour of AS5350

NewsGroups | Search | Tools
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Strange behaviour of AS5350 zoran brakus 08-22-2006
Posted by zoran brakus on August 22, 2006, 5:55 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Today, during routine testing through one of our 5350 GWs (that was
previously working fine) I realized my calls are failing, GW was not
reachable from the IP side (code 102). Configuration was not changed
for a longer time and there was no obvoius reason why it doesn't work
suddenly. I tried with reload, but the fun was just beggining. After
reboot I was not able to telnet anymore! Ping was also not possible,
box was unreachable. Console was the only way out, but then the real
surprise is coming. Connected through console port, I was not able to
ping the local fast-ethernet interface, the one connected to the LAN,
although the interface configuration was there and was correct (at
least "sh run" was showing that)! Disabling and enabling the interface
didn't help, but disable-reload-enable did. However, calls are still
failing (now with code 127), logs are giving me almost nothing. It
seems that some part of configuration is somehow "ignored", similar
like it was for the interface IP configuration (it was there but like
it wasn't). The problem is I cannot isolate which part of the config
is "missing". I've tried to re-configure dial-peers, translation
rules, but without success. Absolutely same configuration was working
just fine for months.

It's a very strange situation for me. Maybe someone had similar
experience? What could be wrong there? My only idea at the moment is
to erase nvram and import the complete config again, but I'm not sure
if this will really help. I would appreciate any hint.
Thanks!

--
"Usenet is not a democracy."
zobxATbluewinDOTch
ß&ß

Posted by john smith on August 22, 2006, 10:21 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Tue, 22 Aug 2006 23:55:40 +0200, wrote:

> Today, during routine testing through one of our 5350 GWs (that was
> previously working fine) I realized my calls are failing, GW was not
> reachable from the IP side (code 102). Configuration was not changed
> for a longer time and there was no obvoius reason why it doesn't work
> suddenly. I tried with reload, but the fun was just beggining. After
> reboot I was not able to telnet anymore! Ping was also not possible,
> box was unreachable. Console was the only way out, but then the real
> surprise is coming. Connected through console port, I was not able to
> ping the local fast-ethernet interface, the one connected to the LAN,
> although the interface configuration was there and was correct (at
> least "sh run" was showing that)! Disabling and enabling the interface
> didn't help, but disable-reload-enable did. However, calls are still
> failing (now with code 127), logs are giving me almost nothing. It
> seems that some part of configuration is somehow "ignored", similar
> like it was for the interface IP configuration (it was there but like
> it wasn't). The problem is I cannot isolate which part of the config
> is "missing". I've tried to re-configure dial-peers, translation
> rules, but without success. Absolutely same configuration was working
> just fine for months.
>
> It's a very strange situation for me. Maybe someone had similar
> experience? What could be wrong there? My only idea at the moment is
> to erase nvram and import the complete config again, but I'm not sure
> if this will really help. I would appreciate any hint.
> Thanks!


i would try two things:
1. surely you backed up your config right?
2. TAC

Similar ThreadsPosted
IP SoftPhone strange behaviour April 14, 2006, 10:55 am
Re: Strange Router behaviour June 14, 2008, 1:45 pm
Re: Strange Router behaviour June 14, 2008, 9:20 pm
strange SNMP behaviour on C3750 July 21, 2004, 9:44 am
strange crypto behaviour with FWSM March 2, 2006, 3:51 am
Re: strange STP behaviour : stack port in "sh spanning-tree" output February 5, 2008, 12:05 pm
as5350 and Cisco ACS v3.3 September 13, 2005, 2:01 am
as5350 question - Please help April 23, 2007, 7:52 pm
AS5350, TCL and DTMF Tone. April 15, 2005, 1:52 pm
WTS: AS5400/AS5350/AS5300 August 12, 2005, 4:51 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map