Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,We have an IGX 8410. We continously recieve an error log as belows."Info Invalid Login Attempt via Control Port (Local)"Any help/comment would be much appreciated.Okan KANYILMAZAnkara / Turkey
hi,I am trying to connect a 2821 router with NM−4B−S/T to 2811 router with NM−4B−U.I installed the cards, made a crossover ISDN cable (3-6,4-5) and connected each other.but there is no light, nothing.Please help.
Can anyone tell me the maximum number of trunks to configure on a 8420 IGX.Because even though i have enough physical ports to connect E1, there is a warning that tells me that maximum number of trunks are reached.Sorry for the bad lang, i dont have ...
I have a terminal with BRI interface, and i want to communicate it with central switch. My connection to central office is E1. I have a 2811 with NM-8b-s/t for BRI interface and Vwic2-1mft-e1 for E1.I am trying to use the router as a bri-e1 convertor...
Hi,We have cisco 2821 routers connected to WAN with 2 ways. With e1 (say E1 0/0) and Frame-relay (serial 2/0). And also i have a main device connected through E1, say, Controller E1 0/1. I need such a routing configuration that would tell my main dev...
Hi,First of all, thank you for your response.The NPM is connected to the URM Console port via the console cable. This is an ordinary implementation for remote management of URM's.We connect to NPM and then to URM with "window" command. Then come back...
Hi,The problem is, there is no dialing. The terminal in the branch is a computer connected to the router through Diva BRI PCI interface. Ive found some configuration examples in the net but all of them were about dialing. The terminal is not using di...
I added static routes to both routers and also added "async mode dedicated" under interface async mode.It didnt make any sense to me but it worked perfectly.So after all, i realized the problem had no relation with OSPF. And also Cisco's document has...
