CCNA lab: Is this posible? I need your help.

notgoing2fail

thehourman wrote: »

No, it took the command, but the line protocol is still down.

Ok on the R4, I want you to issue the debug command, let's see what's happening...


debug ppp authentication


You have to issue this in regular priv. mode, not global config mode...

Then go into your serial interface issue shut(wait 10 seconds), then no shut(wait 10 seconds), and watch the messages...

notgoing2fail

Here's what you should see.....


Se0 PPP: Treating connection as a dedicated line
Se0 PPP: Phase is AUTHENTICATING, by the peer
Se0 CHAP: I CHALLENGE id 1 len 19 from "RouterLan2"
Se0 CHAP: O RESPONSE id 1 len 29 from "RTR-2507"
Se0 CHAP: I SUCCESS id 1 len 4

thehourman

Give me a few minutes because I just erased the nvram on R1.

thehourman

notgoing2fail wrote: »

Here's what you should see.....


Se0 PPP: Treating connection as a dedicated line
Se0 PPP: Phase is AUTHENTICATING, by the peer
Se0 CHAP: I CHALLENGE id 1 len 19 from "RouterLan2"
Se0 CHAP: O RESPONSE id 1 len 29 from "RTR-2507"
Se0 CHAP: I SUCCESS id 1 len 4

Here's the output after I issued the no shutdown command.
Se1/1 PPP: Using default call direction
Se1/1 PPP: Treating connection as a dedicated line
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required

notgoing2fail

thehourman wrote: »

Here's the output after I issued the no shutdown command.
Se1/1 PPP: Using default call direction
Se1/1 PPP: Treating connection as a dedicated line
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required
Se1/1 PPP: Authorization required

Ok did you set up each side properly with username accounts?

thehourman

Yes,
username R4 password cisco <-- R1
username R1 password cisco <-- R4

notgoing2fail

thehourman wrote: »

Yes,
username R4 password cisco <-- R1
username R1 password cisco <-- R4

NO!!! You're suppose to swap out the hostnames with your actual hostname.

So it should be:

username FRAMERELAY password cisco

username R1 password cisco


Double check but that should be right.

thehourman

I executed this command, username FRAMERELAY password cisco, on R1.
I executed this command, username R1 password cisco, on R4.
and vice versa
I still getting the authorization required. Maybe the damn NM-4A/S is really faulty

notgoing2fail

thehourman wrote: »

I executed this command, username FRAMERELAY password cisco, on R1.
I executed this command, username R1 password cisco, on R4.
and vice versa
I still getting the authorization required. Maybe the damn NM-4A/S is really faulty

Yeah that doesn't look good. I'm hoping someone else can chime in on this issue but sounds like we've tried everything possible.....

notgoing2fail

I'm gonna have to call it a night, sorry I couldn't help you out. I'll check this thread tomorrow and see if anyone has any thoughts.....

thehourman

Thanks man, I am tired too.

Sepiraph

Hey OP always take out the password info and any public ip addresses when you post your config.

Also you say you want to setup frame-relay (I assume using R4 as the FR switch), to do that you need the command 'frame-relay switching' enabled on the router but I don't see the command anywhere, also on the interface level you need "frame-relay encapsulation".

You definitely want to consult some documentation on how to setup a router to act as a FR switch.

Cisco Frame Relay Configurations > Configuring a Cisco Router as a Frame Relay Switch

mikej412

Did anyone ever do a show cdp neighbor. What's the output?

The NM-4A/S should be clearly marked as as Serial 0, Serial 1, Serial 2, and Serial 3 -- so I'd guess that end of the cable is attached to the correct port. What's the other router and interface card -- and are you sure you're configuring the correct serial port on that router?

Are these back-to-back cables with marked DCE/DTE ends?

There probably is some sort of LEDs for the ports -- what do they show?

This is real hardware -- right?

mikej412

thehourman wrote: »

R1#show controllers s0/1
Interface Serial0/1
Hardware is PowerQUICC MPC860
[B]DTE V.35 clocks stopped.[/B]

Sounds like a clocking issue, bad cable, cable not fully seated, bad port, or wrong port.

thehourman

mikej412 wrote: »

Sounds like a clocking issue, bad cable, cable not fully seated, bad port, or wrong port.

That is the WIC-1T on R1. It can't be a bad port because last night, I plugged that WIC-1T to R2's WIC-1T and they worked. Therefore, I am 100% sure it was not the R1's WIC.

I am going to reset everything and start from scratch again.

EDIT: How do I change the title of this thread? Or should I make a new thread about this problem?

mikej412

thehourman wrote: »

It can't be a bad port because last night, I plugged that WIC-1T to R2's WIC-1T and they worked.

Did you ever take R2's WIC-1T (and cable) and plug that into R4's WIC slot and see if that works -- to rule out an IOS bug or possible bad NM-4A/S or NM-4A/S port?

Did any of the other NM-4A/S connections work? If you have cables connected and no shut the ports on both ends, show CDP neighbor should show something.

thehourman wrote: »

EDIT: How do I change the title of this thread? Or should I make a new thread about this problem?

Try double-clicking next to the end of the subject in the Forum view.

thehourman

All my WIC-1Ts can talk to each other, but the NM-4A/S can't talk to WIC-1Ts.
Once I put the clock rate the status and protocol went up then after a few seconds the protocol went down. It is not just R1 who is having a problem with NM-4A/S. R2 and R3 can't talk to R4 with the same issue.

notgoing2fail

thehourman wrote: »

All my WIC-1Ts can talk to each other, but the NM-4A/S can't talk to WIC-1Ts.
Once I put the clock rate the status and protocol went up then after a few seconds the protocol went down. It is not just R1 who is having a problem with NM-4A/S. R2 and R3 can't talk to R4 with the same issue.

I have that same module. Later today if I have time, I'll try to lab up using that module and see if there's any noticeable difference.....

mikej412

thehourman wrote: »

All my WIC-1Ts can talk to each other, but the NM-4A/S can't talk to WIC-1Ts.

And for the 3rd time -- show cdp neighbor?

thehourman

mikej412 wrote: »

And for the 3rd time -- show cdp neighbor?

Nothing came up with show cdp neighbors.
I did the show cdp neighbors on both R4 and R1 they can't see each other.
Both the WIC-1T on R1 and NM-4A/S on R4 can detect the type of cable, but they can't see each other.
I just upgraded the IOS on R4, but it is still the same result.

mikej412

thehourman wrote: »

Nothing came up with show cdp neighbors.

But if R1 is connected to R2 and working -- why didn't that show up?

So you have 3 connections total on the NM-4A/S and none of them show up?

If you move that WIC from R2 to R4 -- it still doesn't show up?

thehourman

I turned it off, my room is like an oven.
So what I have on right now are R1 and R4.

I have not put a WIC-1T on R4, I'm gonna try that one.
What I am going to do, I am going to use the WIC-1T from R2 and put it on R4's WIC slot.

thehourman

Here's an update on my last post:

After I put the WIC-1T into R4's WIC slot and left the NM-4A/S on R4(R1 is still connected to NM-4A/S), and executed the command show cdp neighbors.

R4 can see R1's s0/0, but not the s0/1 which is connected to NM-4A/S.

mikej412

thehourman wrote: »

After I put the WIC-1T into R4's WIC slot and left the NM-4A/S on R4(R1 is still connected to NM-4A/S), and executed the command show cdp neighbors.

R4 can see R1's s0/0, but not the s0/1 which is connected to NM-4A/S.

If you then take that cable and attach it to Serial 0 on the NM-4A/S and no shut the port -- do you get anything than?

If you then put the cable from the NM-4A/S Serial 1 on the WIC that's working -- does that work?

And when the routers attached to the NM-4A/S Serial 2 and Serial 3 are powered on (and the ports no shut/configured) -- do they show anything with the show cdp neighbor command?

If you've tried all the ports on the NM-4A/S and none of them are working -- then you probably have a bad NM-4A/S (or bad NM Slot). Pull the NM-4A/S and try it in another router. Check the connector on the NM-4A/S and see if there is any damage -- and make sure you have it firmly seated (and screwed down) in the next router.

notgoing2fail

Is your cable cisco or chinese knock off? LOL...


Just had to ask...

thehourman

The cable works with no problem because I have been switching cables back and forth and got some pings. However, when i plugged the cable in NM-4A/S(any ports), the protocol is down. I also used no shutdown so many times.

None of any ports in NM-4A/S are showing in show cdp neighbors command
After the used the no shut on NM-4A/S it goes up up, but after like 15-25 secs it goes up down. So NM-4A/S can't maintain the up up state.

I'm going to try to pu the NM-4A/S to a different router.

@notgoing2fail, the cable is from monoprice.com ebay store.

notgoing2fail

thehourman wrote: »

I'm going to try to pu the NM-4A/S to a different router.

If you can do that, that would be great for troubleshooting purposes....

I had to turn the A/C on today so my lab time is limited unless I want to run up a huge electricity bill...

I'm pretty sure my module works though since I do see my V.35 cable connecting to one of the serial ports and to another router. Plus I'm also pretty sure I checked to make sure the module worked when I bought it off eBay.....

thehourman

I put the NM-4A/S into R2's slot, and unsuccessful.
Same output after no shutdown it goes up up then up down.

So the my NM-4A/S is bad?
But it can see the cable type with no problem.

blackninja

Try just using the wic cards.

Use clock rate 64000.

Make sure that you have the clock rate command on the DCE side of the cable.

Are the cables are seated correctly?

Make sure you get up/up before setting protocols to PPP - and don't use auth until you get up/up on PPP.

thehourman

blackninja wrote: »

Try just using the wic cards.

Use clock rate 64000.

Make sure that you have the clock rate command on the DCE side of the cable.

Are the cables are seated correctly?

Make sure you get up/up before setting protocols to PPP - and don't use auth until you get up/up on PPP.

The WIC-1T cards work without any problem.

notgoing2fail and I tried to do ppp last night, but did not work either. I have also tried to use all the clocks available on NM-4A/S and it is still nothing.
I tried to put the DCE to WIC-1T and DTE to NM-4A/S and tried all the clocks, still unsuccessful.

It only went up up when I entered no shutdown, but it went up down after 15-25secs.

Within 15-25secs time frame of up up, when I used the show ip int brief, it says up up as well. But once it goes down, it stays up down.