VIC2-2BRI NT/TE - link going down

Hi,
I have VIC2-2BRI NT/TE on router 2801.
If there are no calls for some time, the interfaces are going down, and none outbound call can't be placed.
Only when inbound call is placed, the link is going up, and everything is working 'till next time.
Does anybody know what could be the reason?
Thanks

I remember i've got a similar problem sometimes ago on the same router and on my 3825 router too.
But the difference is that the VIC2-2BRI NT/TE remains up until i place calls. The first call goes through one port of the interface, and after that, this port changes state to down. The second call uses the second port of the interface, and after goes down. then i can no more place calls. But i can receive calls from PSTN, and just before, the interfaces change state to UP. And i can place two other calls again and the same problem occur.
To issue this problem, i entered the command
" isdn transition-delay 1" at each BRI interface
And things now go well.
But i would like to get more information about this command, if you can help me

Similar Messages

Weird network problem: Ethernet link going down for few seconds, and up again

Hi,
this problem is driving me nuts for weeks now, and I've not had any success with solving it myself, so I hope someone might have a clue...
A few weeks ago, maybe 2 months, when downloading VOD content from iTunes, the download suddeny stopped after a while, saying that there is a problem with my network connection. I can then resume the download until the next connection drop occurs. iTunes was and still is the only app that makes the problem noticeable (FTP, browsing, Mac App Store etc. are working fine), however, as this also affects iDevice firmware downloads and basically everything I download via iTunes, the problem started to really annoy me. I'm not sure, but the problem might have been introduced after upgrading from Lion to Mountain Lion/10.8, which I needed for Logic X.
So here is what happens:
I have an iMac12,2, Mid 2011, 27inch, i5 2.7GHz, 16GB RAM, 256GB Apple SSD + 1TB HDD. When using ethernet, the iMac randomly loses its link to the network. My router is a FRITZ!Box 7390 (german make). There are no switches between my iMac and the router. When that happens while running ping, this is how it looks like:
64 bytes from 192.168.1.1: icmp_seq=3558 ttl=64 time=0.542 ms
64 bytes from 192.168.1.1: icmp_seq=3559 ttl=64 time=0.424 ms
ping: sendto: No route to host
Request timeout for icmp_seq 3560
ping: sendto: No route to host
Request timeout for icmp_seq 3561
ping: sendto: No route to host
Request timeout for icmp_seq 3562
ping: sendto: No route to host
Request timeout for icmp_seq 3563
ping: sendto: No route to host
Request timeout for icmp_seq 3564
Request timeout for icmp_seq 3565
64 bytes from 192.168.1.1: icmp_seq=3566 ttl=64 time=0.508 ms
64 bytes from 192.168.1.1: icmp_seq=3567 ttl=64 time=0.493 ms
And this is what the logfile contains at the same time:
28.10.13 21:36:35,000 kernel[0]: AppleBCM5701Ethernet [en4]: Link down (womp disabled, proxy idle)
28.10.13 21:36:37,099 configd[18]: network changed: v4(en4-:192.168.1.188) DNS- Proxy-
28.10.13 21:36:37,106 configd[18]: network changed: Proxy
28.10.13 21:36:37,112 netbiosd[12000]: network_reachability_changed : network is not reachable, netbiosd is shutting down
28.10.13 21:36:40,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en4, 1-Gigabit, Full-duplex, Symmetric flow-control, Debug [796d,0323,0de1,0300,cde1,3800]
28.10.13 21:36:40,237 configd[18]: network changed: Proxy
28.10.13 21:36:42,544 configd[18]: network changed: v4(en4+:192.168.1.188) DNS+ Proxy+ SMB
So the ethernet interface loses the link for a few seconds, and gets back up again. It's not long enough to affect average TCP connections, however it is long enough to completely screw iTunes.
What I've tried:
- changed all cables (save the one that's going from the ethernet outlet on my room's wall to the server/router room, as it's not replaceable (running within a wall) and I really don't know why it should become faulty offhandedly)
- cycled ethernet ports at the router to make sure they're not faulty
- ping'd the router from different computers on all its ethernet ports, all working fine
- connected my iMac to router via wifi, all working fine
- bought a Thunderbolt Ethernet adapter to make sure onboard ethernet card isn't faulty: problem still there
- installed 10.9 over 10.8.5, problem still there
What I didn't check is what happens when ping'ing the router via my cables, but from another computer, as I don't have one. I will try to borrow a MacBook and check that.
So I figured it must be a local problem, as the network infrastructure itself works nicely and all cables seem to be sound. It is also not a hardware issue, as the problem occurs both with the onboard NIC and the Thunderbolt NIC. What mystifies me is that it doesn't happen when using Wi-Fi (but switching to that is not an option - it's too slow).
I tried to use both DHCP and fixed IP addresses, different IP ranges, made sure that static IPs don't collide with the router's DHCP range, updated the router firmware, updated the firmware of all Airport Express and Time Capsules I've got in my network (just to be sure), switched all energy saving settings to "Never" (as it has been suggested here from time to time), but nothing helped ... and I don't know what else to check.
I hope that someone has an idea of what's happening here!
Thanks in advance!

It looks like hooking an ethernet switch between my iMac and the router did the trick. I didn't get any timeouts after I did that. It must have been a really weird incompatibility between my iMac and the router. Still have to see if iTunes gets through without losing the connection, I hope I'll be able to check that tomorrow night. I'll report back.
So maybe try just hooking another ethernet switch between your mac and the other side. It might actually help!

VIC2-2BRI problem

Hi,
I need help regarding problem i'm having with ISDN BRI cards.
The problem is from time to time L1 link goes down between PBX and Cisco 2801 with VIC2-2BRI cards. Problem is not related to a specific type of PBX or just one PBX, but this happens very frequently now, on multiple sites.
I've managed to find several workaround solutions, but they are far from final.
1. If i'm using new cards (BRI) and setting a new site, I can't get the cards to go up, that is OK light won't come up, unless I connect straight cable in BRI card, and on the other side connect (short circuit) pins 3,4 and 5,6, make a loop. And here is the "tricky" part, if I don't do shut, no shut cards won't come up, or reload the router and connect cable to card before interfaces come up.
2. On existing sites link just goes down, all by itself, in that case all that helps is to put the cards in another slot, and use the above method. Cables stay the same, cards and router also, IOS also.
I really don't see the problem here!
Has anyone had any similar experiences?
Thanks
Regards,
Damir

Hi,
Unfortunately, I don't see the actual transition, it would help me also.
This is only thing i've found in logs.
Nov 18 10:49:47: ISDN BR0/2/0 **ERROR**: handle_l2d_srq_mail: Layer 1 inactive
Nov 18 10:49:50: ISDN BR0/2/0 Q931: L3_ShutDown: Shutting down ISDN Layer 3
Nov 18 10:49:51.042 CET: %LINK-3-UPDOWN: Interface BRI0/2/0, changed state to down
But from this I can't see that much...
Thing is this happens more when you are using new cards, or existing somewhere else.
Normal cards light up OK when they are going through POST, it tells you that the card is recognized and working. B1 and B2 channels (lights) don't light of course.
More and more I think this a bug...
P.S. sorry I can't provide more errors, but this is only thing that happens, that's way it's strange!
Regards,
Damir

Radio going down on 1310AP

Hi there, I'm experiencing some issues with a 1310 LWAPP on a University, here is the scenario:
The AP is directed to some specific classrooms and at a certain point the radio goes down or at least there is no more communication between the clients and the AP, but the association in the computers remain the same for a couple of minutes, after that the link goes down, but the weird thing is that the communciation to the AP via Ethernet remains up. We tested this and the ping's all were responding while the radio was down.
Steps already done:
-A new 1310 has been tested, same results.
-A new power injector, same results.
-The UTP cabling between the power injector and the IDF has been changed, same results.
-The port to which the AP was connected at the IDF switch was changed, same results.
I'm thinking as a possible solution:
-Replacing the coax cabling between the power injector and the AP (not more than 15 ft).
-Ensure the AC voltage at the power outlet is delivered correctly (110v) not less, not more.
I'm wondering if this steps may be causing the device(s) to fail in such a way, because if it is not receiving the appropriate ammount of power the radio module simply goes down, but as the ethernet module requires less power it remains up.
What do you think?
Any recommendation is more than welcomed; too much time has been dedicated without success.
Thanks in advance!

For the troubleshooting chech the Red color indicates an overcurrent or overvoltage error condition disconnect input power from the power injector, check all coax cable connections for a possible short, wait approximately 1 minute, and reconnect input power to the power injector. If the LED turns red again, contact technical support for assistance.
The power injector requires approximately 50 seconds to recover from an overcurrent or overvoltage condition.
Off indicates input power is not available verify that the power module is connected to the power injector and that AC power is available or that 12- to 40-VDC input power is connected to the power injector.

After upgrading to Mavericks, the free space on my SSD keeps going down for no apparent reason

I downloaded Mavericks and installed it on my macbookpro ( with Crucial M4 SSD) and the free space on my ssd keeps going down for no reason. I reinstalled it from a bootable flashdrive, and the free space went from 20G to 60. Since then it keeps going down and I am now on 48G. I cannot find the source of the drain. Anyone else with the same problem?

http://reviews.cnet.com/8301-13727_7-20025542-263.html
I have not tested the solution suggested in the article linked above.
But hope it helps.

What happens to client session when host goes down?

I have a windows 2012 R2 RDP environment. 1 Broker and 3 Session Host Servers.
My question is as follows:
User connects via broker to one of the Host servers. Host server goes down, while user is still connected. Session is written in Broker database. User wants to connect again, but broker sends him on to the server which is down and so he cannot connect.
Other situation is similar, User connects to host, administrator drains host, stopping new connections. User disconnects session, session is still in Broker, when user tries to reconnect is sent to drained server but cannot login, as he is considered new
connection.
What am I missing?
Aaron

Hi Aaron,
Thank you for posting in Windows Server Forum.
We need to configure RDSH in a load balance farm where it can be managed by RD Connection Broker. For that we need to use DNS RR where need to make entry for all RDSH server which will be handled by RDCB Server or we can use any load balancing method to load
balance the different RDSH server and thus that connection will allow the disconnected session for reconnection and can identify the connection.
The RD Connection Broker for RDS serves the following main purposes:
• Determining the best RD Session Host server to connect to - this is based on the amount of current sessions per RD Session Host Server as a form of load balancing.
• Reconnecting a user to an existing session, in case there is one - this is called reconnecting to disconnected sessions.
• Being a resource for RD Web Access to deliver information about what Remote Apps are available on RD Session Host Servers that are a member of the broker.
More information.
Remote Desktop Server farms explained (Part 1
& Part 2) (Link is for Server 2008 R2 but it’s only for reference).
Step by Step Windows 2012 R2 Remote Desktop Services – Part 3 (For Server 2012 R2)
Hope it helps!
Thanks.
Dharmesh Solanki

SSRS Reporting manages goes down frequently. ERROR: The underlying connection was closed: An unexpected error occurred on a send.

We have been experiencing issues with SSRS over the past 5 weeks, the service goes down frequently. And it comes up only on reboot of the server.
We had also disabled the On Access scan in Mcafee.
The service is in use for about two years, and the below error started occuring over the last few days. Please advise on this.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: The underlying connection was closed: An unexpected error occurred on a send.
ui!ReportManager_0-2!24e8!08/14/2014-18:13:45:: e ERROR: HTTP status code --> 500
-------Details--------
System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException:
An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   --- End of inner exception stack trace ---
   at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
   at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetSecureMethods()
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
   at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
   at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
   at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel level)
   at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
   at System.EventHandler.Invoke(Object sender, EventArgs e)
   at System.Web.UI.Control.OnInit(EventArgs e)
   at System.Web.UI.Page.OnInit(EventArgs e)
   at System.Web.UI.Control.InitRecursive(Control namingContainer)
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
ui!ReportManager_0-2!24e8!08/14/2014-18:13:46:: e ERROR: Exception in ShowErrorPage: System.Threading.ThreadAbortException: Thread was being aborted.
   at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg) at    at System.Threading.Thread.AbortInternal()
   at System.Threading.Thread.Abort(Object stateInfo)
   at System.Web.HttpResponse.End()
   at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
   at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String errMsg)
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListParentsAction(/Data Sources).
library!ReportServer_0-1!1c90!08/14/2014-18:13:51:: Call to ListChildrenAction(/Data Sources, False).
webserver!ReportServer_0-1!1c90!08/14/2014-18:13:51:: i INFO: Processed folder '/Data Sources'
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to GetItemTypeAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListParentsAction(/).
library!ReportServer_0-1!68c!08/14/2014-18:13:56:: Call to ListChildrenAction(/, False).
webserver!ReportServer_0-1!68c!08/14/2014-18:13:56:: i INFO: Processed folder '/'

Hi SThiyag,
Based on your error message, it may be related to the “SecureConnectionLevel” in the RSReportServer.config file. Please go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer, use Notepad to open the RSReportServer.config,
modify <Add Key="SecureConnectionLevel" Value="0"/>, change the value into "1" or "2".
(Note: Please backup the file before modify it.)
Acceptable values are:
3 Most secure—Use SSL for absolutely everything.
2 Secure—Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 Basic Security—Accepts http but rejects any calls that might be involved in the passing of credentials.
0 Least Secure—Don't use SSL at all
Here is a blog for error message "The underlying connection was closed...", please refer to the link below:
http://blogs.msdn.com/b/engelsr/archive/2005/11/29/the-underlying-connection-was-closed.aspx
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Server Goes Down Alert

Hello,
I am running SCOM 2012 R2 and I am trying to setup an alert to let me know when a server goes down. I tried creating a rule that monitored the Management Server's "Operations Manager" Event Log for ID 20022. I also configured
the rule that parameter #2 must have my servers name. I also tried EventDescription conatains my servers name. None of them worked. But I looked in the Event Log of my Management Server and as I looked at all of the 20022 entries, I noticed
the computer I was on was listed as not heartbeating. Two of my other servers that are currently on were listed as not heartbeating. So obviously monitoring this 20022 entry is not reliable. I do not want to setup a monitor for something
like Ping Status. I want to try to avoid using monitors because they could be taxing on the servers, my management server, and my network.

Hi
yes event id 20022 is not reliable and never go for windows event id monitor for server shutdown or unavailability on agent , as scom health service will be stopped or connection closed with MS at the time of shutdown on agent.
you need to go for ICMP port monitoring for server availability, as port monitoring run from remote server(watcher node) and can capture server unavailability and ping test.
refer below link for port monitoring
http://technet.microsoft.com/en-us/library/hh457544.aspx
http://www.systemcentercentral.com/custom-tcp-port-monitoring-management-pack-for-scom-2012/
regards
sridhar v

HT4060 Bought a new ipad and now its down to 28% so I am trying to charge it by the plug in but instead of going up its going down in %

Trying to figure out how to charge my new ipad wi-fi cellar. I plugged it in but instead of going up in % is still going down and its now showing me that its charging like a cell phone does. When I started to charge it, it was 28% now its 27%. Its plugged into a wall.

The quickest way (and really the only way) to charge your iPad is with the included 10W or 12W USB Power Adapter. iPad will also charge, although more slowly, when attached to a computer with a high-power USB port (many recent Mac computers) or with an iPhone Power Adapter (5W). When attached to a computer via a standard USB port (most PCs or older Mac computers) iPad will charge very slowly (but iPad indicates not charging). Make sure your computer is on while charging iPad via USB. If iPad is connected to a computer that’s turned off or is in sleep or standby mode, the iPad battery will continue to drain.
Apple recommends that once a month you let the iPad fully discharge & then recharge to 100%.
How to Calibrate Your Mac, iPhone, or iPad Battery
http://www.macblend.com/how-to-calibrate-your-mac-iphone-or-ipad-battery/
At this link http://www.tomshardware.com/reviews/galaxy-tab-android-tablet,3014-11.html , tests show that the iPad 2 battery (25 watt-hours) will charge to 90% in 3 hours 1 minute. It will charge to 100% in 4 hours 2 minutes. The new iPad has a larger capacity battery (42 watt-hours), so using the 10W charger will obviously take longer. If you are using your iPad while charging, it will take even longer. It's best to turn your new iPad OFF and charge over night. Also look at The iPad's charging challenge explained http://www.macworld.com/article/1150356/ipadcharging.html
Also, if you have a 3rd generation iPad, look at
Apple: iPad Battery Nothing to Get Charged Up About
http://allthingsd.com/20120327/apple-ipad-battery-nothing-to-get-charged-up-abou t/
Apple Explains New iPad's Continued Charging Beyond 100% Battery Level
http://www.macrumors.com/2012/03/27/apple-explains-new-ipads-continued-charging- beyond-100-battery-level/
New iPad Takes Much Longer to Charge Than iPad 2
http://www.iphonehacks.com/2012/03/new-ipad-takes-much-longer-to-charge-than-ipa d-2.html
Apple Batteries - iPad http://www.apple.com/batteries/ipad.html
Extend iPad Battery Life (Look at pjl123 comment)
https://discussions.apple.com/thread/3921324?tstart=30
New iPad Slow to Recharge, Barely Charges During Use
http://www.pcworld.com/article/252326/new_ipad_slow_to_recharge_barely_charges_d uring_use.html
Tips About Charging for New iPad 3
http://goodscool-electronics.blogspot.com/2012/04/tips-about-charging-for-new-ip ad-3.html
How to Save and Prolong the battery life of your new ipad
https://discussions.apple.com/thread/4480944?tstart=0
Prolong battery lifespan for iPad / iPad 2 / iPad 3: charging tips
http://thehowto.wikidot.com/prolong-battery-lifespan-for-ipad
iPhone, iPod, Using the iPad Charger
http://support.apple.com/kb/HT4327
Install and use Battery Doctor HD
http://itunes.apple.com/tw/app/battery-doctor-hd/id459702901?mt=8
In rare instances when using the Camera Connection Kit, you may notice that iPad does not charge after using the Camera Connection Kit. Disconnecting and reconnecting the iPad from the charger will resolve this issue.
 Cheers, Tom

When remote database used in DB Link is down, JDBC hangs

Hello!
I have DB Link defined in my Oracle DB I work with from JSP application
which uses
Tomcat's connection pool. When remote DB is available, everything is
fine. But when
it goes down (I explicitly shut it down with "shutdown immediate"),
JDBC call hangs:
Statement Stmt1 = conn.createStatement();
rs = Stmt1.executeQuery("SELECT something FROM mytable@mylink");
Second line causes hang forever (or long enough for me to wait, more
that 30 minutes).
If I add this:
Stmt1.setQueryTimeout(5);
then it hangs for about 1min45sec, then throws exception "end of line
in communication
channel". Unfortunately, 1min45sec is too much to wait for the end
user. Also, it resets
my connection to my DB (not remote one), so it is no longer usable,
which costs me
something to recover.
It looks like the error occurs only when connection I use had
successful "history" of
being able to connect via DB Link. If I get connection not from
Tomcat's connection
pool, but force a new connection, everything works fine (something to
do with session
using DB Link).
Has anyone had similar problem? Is a workaround different from creating
a new
connection available?
Thanks!

Well, it appeared that this is nothing to do with Tomcat. The following sequence
of calls causes the same symptoms:
Statement stmt2 = cn.createStatement();
ResultSet rs2 = stmt2.executeQuery("select 'x' from dual@mylink");
rs2.next();
System.out.println(rs2.getString(1));
rs2.close();
stmt2.close();
// !!! do shutdown immediate to DB referenced by mylink, now
stmt2 = cn.createStatement();
rs2 = stmt2.executeQuery("select 'x' from dual@mylink"); // !!! hangs forever
rs2.next();
System.out.println(rs2.getString(1));
rs2.close();
stmt2.close();
If I would create a new connection for the second set of statements (before
second stmt2 = ...), it will not hang, and I will get correct error:
java.sql.SQLException: ORA-02068: following severe error from MYLINK
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Looks like something to do with Oracle JDBC driver?

Report sever is going down.

Hi experts,
APPS-11.5.10.2,
Db-10g
os- hp unix
My report server is going down.please below report server logs.
2013-03-02 15:30:24 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-02 17:02:45 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-02 17:42:57 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-03 04:41:41 -- Server is starting up.
*** 2013-03-03 18:23:14 -- Server is starting up.
*** 2013-03-04 01:43:44 -- Server is starting up.
*** 2013-03-04 11:28:48 -- Server is starting up.
*** 2013-03-04 11:57:22 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 12:42:10 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 12:46:50 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 13:16:58 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 13:34:50 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 15:30:14 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 15:35:30 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 16:29:10 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 16:49:31 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 17:44:41 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 18:15:39 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-04 18:48:58 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-04 20:26:29 -- Server is starting up.
*** 2013-03-05 03:50:03 -- Server is starting up.
*** 2013-03-05 04:01:42 -- Server is starting up.
*** 2013-03-05 09:31:04 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 10:01:15 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 10:09:40 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 12:11:33 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 12:14:21 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 13:15:41 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 14:15:23 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 15:03:10 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 15:10:45 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 15:40:53 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 15:49:24 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 16:59:43 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 17:30:03 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 18:21:53 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 18:55:00 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 19:25:11 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-05 20:00:22 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-05 20:30:30 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-06 10:47:28 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-06 11:17:38 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-06 12:03:22 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-06 12:33:30 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-06 12:46:23 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-06 13:16:34 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-06 16:00:34 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-06 16:30:40 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-06 16:45:26 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-06 17:18:18 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-08 09:15:34 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-08 09:45:43 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-08 11:44:54 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-08 12:29:14 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-08 15:54:36 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-08 16:24:44 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-08 16:46:39 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-08 17:16:43 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-08 17:39:13 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-08 18:19:10 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-09 10:53:30 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-09 11:32:42 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-09 12:34:18 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-09 13:22:56 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-09 13:44:55 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-09 14:15:03 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-09 14:42:18 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-09 15:12:21 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-09 15:31:51 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-09 16:01:59 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-10 03:58:01 -- Server is starting up.
*** 2013-03-10 04:23:40 -- Server is starting up.
*** 2013-03-10 07:19:23 -- Server is starting up.
*** 2013-03-10 08:45:44 -- Server is starting up.
*** 2013-03-10 09:21:13 -- Server is starting up.
*** 2013-03-10 14:11:24 -- Server is starting up.
*** 2013-03-17 03:43:31 -- Server is starting up.
*** 2013-03-18 10:19:52 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-18 10:50:03 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-18 10:57:55 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-18 11:28:07 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-18 12:58:29 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-18 13:28:36 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-18 16:26:54 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-18 16:59:26 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-03-24 04:02:59 -- Server is starting up.
*** 2013-03-24 15:57:01 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-03-26 22:24:49 -- Server is starting up.
*** 2013-03-31 04:01:43 -- Server is starting up.
*** 2013-04-03 11:46:09 -- Server is starting up.
*** 2013-04-03 11:49:51 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-04-03 12:39:07 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-04-03 12:53:32 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-04-03 14:25:51 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-04-03 14:41:13 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-04-03 15:26:58 -- Server shutting down an engine. (REP60_CRMPRD1)
*** 2013-04-03 15:39:32 -- Server started up an engine. (REP60_CRMPRD1)
*** 2013-04-05 07:33:57 -- Server is starting up.
*** 2013-04-06 07:45:01 -- Server is starting up.
*** 2013-04-06 10:35:41 -- Server started up an engine. (REP60_CRMPRD1)
Rgs,
Ram

891940 wrote:
hi hussien,
This is CRM.some time my report server is going down status.yes before it is working fine.we have changes as per below link.
conncurrent mager logfile errors
Rgs,
Ram.Please post the steps you followed to do the changes.
What are the issues you have with the reports server from the front-end?
Thanks,
Hussein

University Wi-Fi going down randomly

Hi,
when I connect my laptop to university's WiFi network the connection goes down randomly (I can stay connected for a few minutes).
I always thought that it was their fault (because they could not handle the high number of people connected), but on Windows it seems to stay connected. Also I don't remember having this problem on my netbook (Lubuntu).
I looked at the output of
sudo journalctl -xb
and I noticed a lot of output from wpa_supplicant saying something about the certificate. Could that be the problem? (I downloaded the certificate from my university's website, it's the link named "scaricarlo").
Here it is the output of
sudo journalctl -xb | grep "\(ntpd\|NetworkManager\|dhcpcd\|wpa_supplicant\)[\[0-9\]*]"
Any ideas?
Last edited by wil93 (2014-01-08 19:27:59)

You're saying you're having trouble on linux, but windows works fine on the same laptop? Sounds like a driver issue to me. Could you tell us which wifi card your laptop is using? Perhaps if you have a spare USB network card with a different chipset, could you try setting it up to test whether that card also performs badly? If it does then it's likely a software management problem. If not then I'd go for a driver problem.

There's a squiggly, grey line going down my screen

There's this grey line that going down on the entire side of the right of my screen. It only shows up when certain colors are on that side of the screen, so I haven't really been able to notice it and know how long it's been there until today. Anybody have any sort of solutions?

Howdy DeadlyFrog,
Welcome to Apple Support Communities.
The article linked below provides a lot of great information and troubleshooting suggestions that you can use to try and rule out a software issue before setting up service for the display issue with your iMac.
Apple computers: Troubleshooting issues with video on internal or external displays - Apple Support
Cheers,
-Jason

What if the CUA Central System goes down?

Hi,
a hypothetical questions: I have a CUA where I've configured that user info can only be changed in the central system. What happens if the central system goes down due to a crash or similar?
Can you still not change any user information in the child system?
If not, is there a work around for that so I can change user info in the child system?
If I can change user info in the child system, whats happens when the central system goes up again? Does it overwrite any changed info in the child system?
Thanks, Oscar

> a hypothetical questions: I have a CUA where I've configured that user info can only be changed in the central system. What happens if the central system goes down due to a crash or similar?
Then you un-link it from the child systems' side.
> Can you still not change any user information in the child system?
See above
> If not, is there a work around for that so I can change user info in the child system?
See above
> If I can change user info in the child system, whats happens when the central system goes up again? Does it overwrite any changed info in the child system?
That depends on your settings. I think the SAP help pages about CUA contain the answer to all your questions.
The risk of the CUA master going down should not withold you from implementing CUA

Wireless APs going down randomly

Hi All
We have a situation where wireless access points are just going down randomly on our network. The situation is as follows:
We have 2 Cisco 5508 WLCs (licensed for 250 APs each, with more licenses en-route), both running software version 7.2.103.0. Then we have a large-ish number (±300) of Cisco AIR-CAP3502I-E-K9 APs connecting to these two controllers. The APs are either connected to Cisco WS-C2960S switches, or in "older" areas of the network they are connected to WS-C2950 switches. We do not have PoE switches installed yet, so all APs are powered by power injectors (AIR-PWRINJ4=).
Anyhat, all the access points are in FlexConnect (previously HREAP) mode, and they all connect via trunk ports to the switches in order to get the VLAN per SSID working. Both controllers are in the same mobility group, and both are in the DNS as "cisco-capwap-controller" as they are load balancing. The APs are installed about 25m apart in most areas. There is one installation where two APs are about 10m apart, but this is due to the shape of the building in which they are installed. We have no autonomous APs deployed at all...
The problem is that some access points work for about a day, and then they just disassociate with whichever controller they were associated to, and then they just fall off the network completely. Both WLCs, the NCS, and the network monitoring system (WhatsUp Gold) show the affected APs as physically unreachable. Looking at the trunk port on the switch, it shows that the port is up and the line protocol is up, input rate is 0 bits/sec, and output rate is up to 70,000bits/sec. There are no input or output errors on the switch port. Here is the output from one such switch port:
FastEthernet0/19 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is dc7b.9439.da13 (bia dc7b.9439.da13)
Description: Link to NC_K22-AP1
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
     reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:50:20, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 71000 bits/sec, 91 packets/sec
     977358 packets input, 80661413 bytes, 0 no buffer
     Received 29925 broadcasts (16038 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 16038 multicast, 0 pause input
     0 input packets with dribble condition detected
     37567889 packets output, 3624164243 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out
Connecting a console cable to an affected AP is fruitless, as the AP appears to be unresponsive while it is "down". Rebooting the AP, then connecting a console cable works, but then you've lost your syslogs. Looking at the Ethernet interface on the AP, it appears as if the interface is picking up a lot of errors, especially CRC errors, which would indicate a physical cable problem.
I got our cabling contractor out to do a cable test again, and it passes every time. We have them test both the Systimax and the Molex cable installations of affected APs, and all is OK. They use a Fluke MicroScanner² cable tester which certifies the Cat 6 cable from patch lead to flylead. No problems there, and I trust that the cable is 100% as tested.
So I swap the power injector of an affected AP (let's call it AP A) with an AP that is not affected by this (let's call this one AP B), and AP A goes down again after a day, or sometimes only a couple of hours. AP B remains operational as usual. If I swap AP A out with a new AP (AP C), then AP C starts showing the same symptoms after about a day, and then it also just goes down. When "suspect" AP A is installed somewhere else, then it works and stays operational for, well, 58 days now. Changing the switch/switch port also makes no difference.
This happens to one of the APs that are part of the "10m apart deployment", but it also happens to another AP that is completely on its own in a building far away from any other wireless source, so I cannot think that this could be the problem. I happens to an AP that is less than 100m away from its closest WLC, and it happens to an AP that is more than 350km away from its closest controller. All the other APs deployed in our remote campus (350km fibre link) are 100% OK. It happens to APs connected to the older WS-C2950 switches as well as the brand new WS-C2960S switches.
I am at wits end with this one. Where could the problem be? I trust the "Big Green" company that does our cable installations, and I trust the equipment they use. I also trust both Systimax and Molex to be very good products. And I do trust Cisco, as this is the only network equipment we deploy.
Where to from here?
Regards
Connie

This issue has now been resolved. Details can be found here: http://www.cisco.com/en/US/partner/ts/fn/635/fn63537.html.
Here is the short version:
Problem Description:
Calibration between DRAM and processor on AIR-CAP350x and AIR-LAP126x results in Access Points (APs) failing to boot properly. One symptom includes a white LED and no console output.
Background:
The root cause is the DDR memory calibration process that was performed on the Access Points (APs) at the time of manufacture. The fix recalibrates the existing memory hardware, so it will operate more reliably.
Workaround/Solution:
The fix for this issue is now publicly available. Go to www.cisco.com to obtain Access Point (AP) IOS code version: 15.2(2)JA or later and/or WLC software version: 7.0.235.3 (or later 7.0 release), 7.2.111.3 (or later 7.2 release) or 7.3.101.0 (or later 7.3 release).
As of June 2012, new AP3500 and AP1260 products with version ID (VID) V02 are free of this issue.

VIC2-2BRI NT/TE - link going down

Similar Messages

Maybe you are looking for