Cisco 877 router config query

[Jeremy Begg]

Hi,

Yes it's not a Cisco mailing list but I know a few Cisco people read it, and
I'm sure there's a Multinet customer out there who knows the answer ...

I'm trying to diagnose a problem with a Cisco 877 router; the problem is
that we can talk to it from the ADSL side but not from the LAN side. I think
there's a problem with the configuration or state of the ethernet
interfaces. Here's the relevant part of the router config:

interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
description --- Ethernet LAN ---
ip address 192.168.3.254 255.255.255.0
ip nat inside
ip virtual-reassembly

And here's the interface state:

Vlan1 is up, line protocol is down
Hardware is EtherSVI, address is 001a.e218.69a3 (bia 001a.e218.69a3)
Description: --- Ethernet LAN ---
Internet address is 192.168.3.254/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
3 packets output, 180 bytes, 0 underruns
0 output errors, 2 interface resets
0 output buffer failures, 0 output buffers swapped out

Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up down
FastEthernet1 unassigned YES unset up down
FastEthernet2 unassigned YES unset up down
FastEthernet3 unassigned YES unset up down
ATM0 unassigned YES NVRAM up up
Vlan1 192.168.3.254 YES NVRAM up down
NVI0 unassigned YES unset up up
Dialer0 150.101.178.52 YES IPCP up up
Virtual-Access1 unassigned YES unset up up
Virtual-Access2 unassigned YES unset up up

I think my problem is that the "line protocol is down". What I want to know
is, what exactly does this mean and how do I make it "up"? And before
anyone asks, I am told that one of the FastEthernet ports *is* connected to
the local network switch. (I can't check it myself the site is on the other
side of the country.)

Any help would be much appreciated!

Thanks,

Jeremy Begg

[Christoph Gartmann]

Post by Jeremy Begg
I'm trying to diagnose a problem with a Cisco 877 router; the problem is
that we can talk to it from the ADSL side but not from the LAN side. I think
there's a problem with the configuration or state of the ethernet
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
description --- Ethernet LAN ---
ip address 192.168.3.254 255.255.255.0
ip nat inside
ip virtual-reassembly

The interface Vlan1 is a virtual interface. So I doubt that you can use it for
NAT.

Post by Jeremy Begg
Vlan1 is up, line protocol is down
Hardware is EtherSVI, address is 001a.e218.69a3 (bia 001a.e218.69a3)
Description: --- Ethernet LAN ---
Internet address is 192.168.3.254/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
3 packets output, 180 bytes, 0 underruns
0 output errors, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up down
FastEthernet1 unassigned YES unset up down
FastEthernet2 unassigned YES unset up down
FastEthernet3 unassigned YES unset up down
ATM0 unassigned YES NVRAM up up
Vlan1 192.168.3.254 YES NVRAM up down
NVI0 unassigned YES unset up up
Dialer0 150.101.178.52 YES IPCP up up
Virtual-Access1 unassigned YES unset up up
Virtual-Access2 unassigned YES unset up up
I think my problem is that the "line protocol is down".

Yes, indeed.

Post by Jeremy Begg
What I want to know is, what exactly does this mean

Usually, in case of a real hardware interface, it means that the interface is
configured (interface is up) but there is no cable connected or no electrical
activity.

Post by Jeremy Begg
and how do I make it "up"?

Plug a cable into it ;-) I think you need to make a connection between the
virtual interface and a real hardware interface.

Post by Jeremy Begg
And before anyone asks, I am told that one of the FastEthernet ports *is*
connected to the local network switch.

Ok, I am not familiar with this specific model but I assume that the four
FastEthernet interfaces are switchports and the Vlan1 aggregates them. None
of the FastEthernet interfaces is up, so I would look at these first.

Regards,
Christoph Gartmann

[Javier Henderson]

Post by Jeremy Begg
Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up down
FastEthernet1 unassigned YES unset up down
FastEthernet2 unassigned YES unset up down
FastEthernet3 unassigned YES unset up down
ATM0 unassigned YES NVRAM up up
Vlan1 192.168.3.254 YES NVRAM up down
NVI0 unassigned YES unset up up
Dialer0 150.101.178.52 YES IPCP up up
Virtual-Access1 unassigned YES unset up up
Virtual-Access2 unassigned YES unset up up
I think my problem is that the "line protocol is down". What I want to know
is, what exactly does this mean and how do I make it "up"? And before
anyone asks, I am told that one of the FastEthernet ports *is* connected to
the local network switch. (I can't check it myself the site is on the other
side of the country.)

From the Cisco IOS Command Reference guide:

The line protocol field status "indicates whether the software
processes that handle the line protocol consider the line usable (that
is, keepalives are successful) or whether it has been taken down by an
administrator."

So one of the FE interfaces may well be plugged into something, but who
knows what that something is, what it's doing, etc.

Can we get more details on what's on the other side of the link? Also,
log into the router, and do:

conf t
interface fastethernet0 (or whatever the number may be)
shutdown
no shutdown

And see what happens.

-jav
***@cisco.com

[Chu, Grant]

Which interface goes to the DEC box?
Gotta make sure that interface is in the right VLAN and that it's "no
shut".

-----Original Message-----
From: Jeremy Begg [mailto:***@vsm.com.au]
Sent: Thursday, April 12, 2007 11:39 PM
To: info-***@process.com
Subject: Cisco 877 router config query

Hi,

Yes it's not a Cisco mailing list but I know a few Cisco people read it,
and
I'm sure there's a Multinet customer out there who knows the answer ...

I'm trying to diagnose a problem with a Cisco 877 router; the problem is
that we can talk to it from the ADSL side but not from the LAN side. I
think
there's a problem with the configuration or state of the ethernet
interfaces. Here's the relevant part of the router config:

interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
description --- Ethernet LAN ---
ip address 192.168.3.254 255.255.255.0
ip nat inside
ip virtual-reassembly

And here's the interface state:

Vlan1 is up, line protocol is down
Hardware is EtherSVI, address is 001a.e218.69a3 (bia
001a.e218.69a3)
Description: --- Ethernet LAN ---
Internet address is 192.168.3.254/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
3 packets output, 180 bytes, 0 underruns
0 output errors, 2 interface resets
0 output buffer failures, 0 output buffers swapped out

Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up down
FastEthernet1 unassigned YES unset up down
FastEthernet2 unassigned YES unset up down
FastEthernet3 unassigned YES unset up down
ATM0 unassigned YES NVRAM up up
Vlan1 192.168.3.254 YES NVRAM up down
NVI0 unassigned YES unset up up
Dialer0 150.101.178.52 YES IPCP up up
Virtual-Access1 unassigned YES unset up up
Virtual-Access2 unassigned YES unset up up

I think my problem is that the "line protocol is down". What I want to
know
is, what exactly does this mean and how do I make it "up"? And before
anyone asks, I am told that one of the FastEthernet ports *is* connected
to
the local network switch. (I can't check it myself the site is on the
other
side of the country.)

Any help would be much appreciated!

Thanks,

Jeremy Begg

[Mark Berryman]

Post by Jeremy Begg
Hi,
Yes it's not a Cisco mailing list but I know a few Cisco people read it, and
I'm sure there's a Multinet customer out there who knows the answer ...
I'm trying to diagnose a problem with a Cisco 877 router; the problem is
that we can talk to it from the ADSL side but not from the LAN side. I think
there's a problem with the configuration or state of the ethernet
interface FastEthernet0
!
interface FastEthernet1
!
interface FastEthernet2
!
interface FastEthernet3
!
interface Vlan1
description --- Ethernet LAN ---
ip address 192.168.3.254 255.255.255.0
ip nat inside
ip virtual-reassembly
Vlan1 is up, line protocol is down
Hardware is EtherSVI, address is 001a.e218.69a3 (bia 001a.e218.69a3)
Description: --- Ethernet LAN ---
Internet address is 192.168.3.254/24
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
3 packets output, 180 bytes, 0 underruns
0 output errors, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
Interface IP-Address OK? Method Status Protocol
FastEthernet0 unassigned YES unset up down
FastEthernet1 unassigned YES unset up down
FastEthernet2 unassigned YES unset up down
FastEthernet3 unassigned YES unset up down
ATM0 unassigned YES NVRAM up up
Vlan1 192.168.3.254 YES NVRAM up down
NVI0 unassigned YES unset up up
Dialer0 150.101.178.52 YES IPCP up up
Virtual-Access1 unassigned YES unset up up
Virtual-Access2 unassigned YES unset up up
I think my problem is that the "line protocol is down". What I want to know
is, what exactly does this mean and how do I make it "up"? And before
anyone asks, I am told that one of the FastEthernet ports *is* connected to
the local network switch. (I can't check it myself the site is on the other
side of the country.)
Any help would be much appreciated!

You must specify which of the physical switch ports are part of the
VLAN. Until that is done, VLAN1 has no physical presence and will
remain in a "down" state. Add the command "switchport access vlan 1" to
whichever FastEthernet interface is connected to the downstream device
(which must either be a switch or you must be using a cross-over cable)
in order to add that port to the VLAN.

The fact that all of the FastEthernet devices also show a down state
indicates that none of them are plugged into anything (or, at least,
that they are not plugged in correctly or whatever they are plugged into
is not up and operational).

Mark Berryman