modem shows down in NMS when connecting Lan cable

(Read 5819 times)

Mar 22^nd, 2009 at 4:03pm

I have a strange issue in one site . cystomer informed that link is dwon . imonitor i found that link is down but as per site i came to know that all light are green (Idirect 3100) . later after many troubleshooting we found that whenever lan cable is removed from the vsat modem , link is up in NMS and when it is connected it suddenly shows down in NMS but status of3 the modem are ok . what could be the problem .

Mar 22^nd, 2009 at 9:30pm

Interesting. I have never seen this.

Is the modem able to pass traffic in its down status?

What is the latency tab telling you under the two circumstances? Request timed out? Or satellite round trip times?

Any chance of an IP conflict with Sat0 or the Lan interface (Eth0)?

When the remote is down, what is the events and conditions tab telling you? UCP or ACQ?

I would also ask what the SAROUTER IP tables look like when the remote is up, and when it is down? If you intend to telnet to that process, make sure you ID what blade the customer is on before you dig in.

Mar 24^th, 2009 at 7:46am

I would guess it s a routing or ip addressing problem.

Mar 24^th, 2009 at 11:23am

That is exactly why I asked about a possible IP conflict.

Mar 24^th, 2009 at 3:39pm

Its never an IP Conflict issue because sometimes i can see that sometimes Modem TX LEd go off while connecting to the switch . Finally after much troubleshooting we found that REDLINE wireless device is creating problem . But what we dont know . when the Wireless device is disconnected from the switch , the modem has no problem (i mean connected to switch) . The same setup was there since 2 years and nothing is changed and this is really wonder what is going with now.

Mar 24^th, 2009 at 3:48pm

The issue is now How another device can stop our modem transmission through Ethernet ?

Mar 24^th, 2009 at 11:44pm

It is difficult to troubleshoot your situation. There are many variables...

1. Is the interface (Eth0) on the remote reporting any errors?

2. Have the user telnet to falcon and turn on remote messages (xon). Look for errors and/or odd messages (such as tx queue saturated, etc). Check for ANY messages both with and without the ethernet (redline) connected. Often packets received by the remote via the local LAN are not able to be processed due to undefined routes for the packets. Could be anything from spam to possible routing loops....causing a packet flood. Also check for routing loops or possible duplicate IPs on the local LAN as well.

3. Check the CPU cycle on the remote....if it is low or within tolerance, then the above situation (packet flood) is not likely.

Mar 25^th, 2009 at 9:02pm

ok , if this some loop issue or conflict , how it can sop modem transmission ?

after investigation , we found again today that when modem ip address is changed than anything like 192.1.28.1 and 192.1.28.2 , it is workingwell

we had made sure one by one in the remote device that no device is usuing the same IP .

I dont understand anything

How i can check for TX queue in modem ?

Mar 27^th, 2009 at 1:14am

How? CPU cycle being overwhelmed.

Telnet to falcon and run the xon command. See if the modem is reporting anything out of the ordinairy....(this is a long shot, but frankly your issue is quite difficult for us to troubleshoot due to the amount of variables involved).

Apr 6^th, 2009 at 3:36pm

Hello

after all its an issue of virus flooding some continuous packets and made modem busy . device behind the modem establishing sessions and evem modem cannot acknwlodge trasmit updates to the PP , so loosing Even TX . we found some abnormal traffic on upstream and also enables ip accounting omn upstream router to get clear picture to know who is sending such traffic . we isolate those devices and fixed the problem and ok now

Thanks for the information and now everything going smoothly

Apr 8^th, 2009 at 11:53am

Glad to hear you isolated the problem. I figured it was some sort of flood that was keeping the box from its TDMA duties.

Email me:eric@satsig.net

Disclaimer, Terms of Use and Privacy

Old Forum rules

Cookie policy.