06-01-2006 05:34 AM - edited 03-03-2019 03:27 AM
I have been trying to get a Catalyst 2950 switch to work for over a week now. I received the switches with no box or packaging and I was told that there were no previous setup attempts on it. I tried performing the express setup but the lights on the server don't seem to behave the way the instructions explain. I also was never able to make a connection between the linux server I am trying to use to configure the switch and the switch. All i received was the switch and nothing else. I have an AC power cord and I also found an RJ45 - DB 9 adapter if needed. I have looked through alot of the manuals on the cisco main pages and nothing seems to be working or clicking. Please help!
06-02-2006 04:34 AM
No problem but please rate my posts if you are finding them useful. Also if it resolves problem please use the tick to indicate problem solved.
Ok your vlan1 interface is shutdown, you need to enable it if you want to telnet /ping it.
switch>enable
switch#config t
switch(config)#interface vlan 1
switch(config-int)# no shut
***exit back to switch# (ctrl-z)
switch#copy run start (this saves your change)
Ok now make sure you linux box has an ip address in the range 192.168.1.0 255.255.255.0 lets use .1 for now if not already used /setup. By default all the switchports are in VLAN1
You should now be able to ping your switch on 192.168.1.10, you should also be able to telnet into it on the same ip using the password macomvty. Let me know if this works now
There are more best practice things that should be done in this configuration in relation to security etc but outside scope of your question. Download yourself the Cisco configuration guide for the switch as it will be a good starting point for you. I urge you to use the command line over the http gui as you will learn more.I'm sure you've learnt a lot already!
HTH
--Phil
Please rate useful posts.
06-02-2006 04:59 AM
when i ping it sends packets but does not receive them...when i tried to telnet it said
telnet 192.168.1.10
Trying 192.168.1.10...
telnet: connect to address 192.168.1.10: No route to host
telnet: Unable to connect to remote host: No route to host
Also on this step
switch(config-int)# no shut
mine said
switch(config-if)# no shut
06-02-2006 05:31 AM
my typo, switch(config-if)#no shut is correct
From the switch try pinging your linux box. From the switch ping the switch ip
Then issue a 'show arp' paste the results here
From you linux box trying pinging the switch again
Then issue 'arp -a' paste results
Then issue 'route -n' paste results
Then issue 'ifconfig -a' paste results
Also do a 'switch2#show interface vlan 1' and 'switch2#sh ip int vlan 1 and paste both results.
--Phil
06-02-2006 05:57 AM
Results of pinging from switch to linux box and switch to switch were both 0%.
Switch2>show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 192.168.1.10 - 000a.8a7a.f280 ARPA Vlan1
No luck pinging switch from linux box again...
Arp -a Results
c358-hsrp102.xxxxx.com (xxx.xxx.102.1) at 00:00:0C:07:xx:xx [ether] on eth0
Route -n Results
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
xxx.xxx.102.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 148.174.102.1 0.0.0.0 UG 0 0 0 eth0
Ifconfig results
eth0 Link encap:Ethernet HWaddr 00:13:72:FD:xx:xx
inet addr:xxx.xxx.102.78 Bcast:148.174.103.255 Mask:255.255.254.0
inet6 addr: fe80::213:72ff:fefd:871d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38172 errors:0 dropped:0 overruns:0 frame:0
TX packets:16406 errors:0 dropped:0 overruns:0 carrier:0
collisions:224 txqueuelen:1000
RX bytes:8127476 (7.7 MiB) TX bytes:3941903 (3.7 MiB)
Interrupt:169
eth1 Link encap:Ethernet HWaddr 00:13:72:FD:87:1E
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::213:72ff:fefd:871e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:225
eth2 Link encap:Ethernet HWaddr 00:04:23:CD:B5:6A
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xecc0 Memory:fe9e0000-fea00000
eth3 Link encap:Ethernet HWaddr 00:04:23:CD:B5:6B
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xec80 Memory:fe9c0000-fe9e0000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6376 errors:0 dropped:0 overruns:0 frame:0
TX packets:6376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4647441 (4.4 MiB) TX bytes:4647441 (4.4 MiB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Lot of info there you are only allowed 3 attachments thats why i put it all in here and attached the last 2 hope you can find everything ok.
06-02-2006 06:22 AM
Switch2#sh ip int vlan 1
Vlan1 is up, line protocol is down
This looks like a problem. What port is your linux server connected to? Please can you do the following and paste results, you interface format will be 0/1 if you were connected to port 1.
switch2#show interface
Also do
switch#show mac-address-table and paste results.
Check your interface shows as connected and check duplex and speed on your linux box, either using mii-tool or ethtool. What type of cable are you connecting between the switch and linux box. It should be a straight through cat5 cable..
HTH
--Phil
06-02-2006 06:47 AM
ok i tried show interface 0/1 and it didn't work so then i just did show interface and received the following results
Vlan1 is up, line protocol is down
Hardware is CPU Interface, address is 000a.8a7a.f280 (bia 000a.8a7a.f280)
Internet address is 192.168.1.10/24
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 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
0 packets output, 0 bytes, 0 underruns
0 output errors, 6 interface resets
0 output buffer failures, 0 output buffers swapped out
FastEthernet0/1 is down, line protocol is down
It says FastEthernet0/1 is down??
When i did the show mac-address-table it was empty the following was there:
show mac-address-table
Mac Address Table
------------------------------------------
Vlan Mac Address Type Ports
---- ----------- ---- -----
which could be a problem?
Here are my speed and duplex settings along with the rest of the ethtool configuration settings:
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Half
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: d
Current message level: 0x000000ff (255)
Link detected: yes
And yes im using the blue cable that came with the switch so i am assuming it is a straight cat 5 cable and not a crossover cable.
06-02-2006 06:56 AM
Ok I made another typo i missed off the fa :o( ...its been a long week
Issue command and paste results.
switch2#show interface fa0/1
I'm thinking you don't have a connection to the switch which I think in turn is causing vlan1 interface not to come up, no port connected on that vlan so what point is there in the interface being up.
You you have any other cables there just in case its a cable fault. Also check your pinouts on the cable to make sure it isn't a crossover.
Also hard code your interface card on your linux box with following command
ethtool -s eth0 autoneg off duplex full speed 100
HTH
--Phil
06-02-2006 07:38 AM
Haha i can understand the long week are you at work as well? Do you work for Cisco? Anyways here are the results of the show interface fa0/1:
Switch2>show interface fa0/1
FastEthernet0/1 is down, line protocol is down
Hardware is Fast Ethernet, address is 000a.8a7a.f281 (bia 000a.8a7a.f281)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 03:45:15, 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
1 packets input, 64 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1 packets output, 64 bytes, 0 underruns
0 output errors, 0 collisions, 2 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
I checked the pinouts and it was a straight cat 5 but i did replace it with another ethernet cable for the time being. Are you sure we want a full duplex instead of half? Eitherway i hard coated the card
06-02-2006 05:48 AM
hi,
then it may be the issure regarding to the connectivity or speed or duplex missmatch. just check it out your arp table in linux box.
rate this post if it helps
regards
Devang
06-02-2006 05:56 AM
hi,
and also make sure you have configure the password and appropriate VTY line in order to get the access using the telnet. before that you need to correct the problem of the connectivity...so check it out port configuration for speed, duplex as well as cable configuration, and also study out your arp table...
still if you have problem let us know???
please rate the post if it helps
regards
Devang
06-02-2006 06:02 AM
I have no idea what or how to do the things you explained to tell you the truth. I am a new coop student at a company and they have been wanting to get this switch working for a while but never had anyone to do it, so me being new I got the job haha...i have had experience with routers, WANs and LANS but never anything to this scale...
There is connection on the server though obviously because I can browse the web...
06-02-2006 07:20 AM
Ok I made another typo i missed off the fa :o( ...its been a long week
Issue command and paste results.
switch2#show interface fa0/1
I'm thinking you don't have a connection to the switch which I think in turn is causing vlan1 interface not to come up, no port connected on that vlan so what point is there in the interface being up.
You you have any other cables there just in case its a cable fault. Also check your pinouts on the cable to make sure it isn't a crossover.
Also hard code your interface card on your linux box with following command
ethtool -s eth0 autoneg off duplex full speed 100
HTH
--Phil
06-02-2006 07:46 AM
Haha i can understand the long week are you at work as well? Do you work for Cisco? Anyways here are the results of the show interface fa0/1:
Switch2>show interface fa0/1
FastEthernet0/1 is down, line protocol is down
Hardware is Fast Ethernet, address is 000a.8a7a.f281 (bia 000a.8a7a.f281)
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed
input flow-control is off, output flow-control is off
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 03:45:15, 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
1 packets input, 64 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
1 packets output, 64 bytes, 0 underruns
0 output errors, 0 collisions, 2 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
I checked the pinouts and it was a straight cat 5 but i did replace it with another ethernet cable for the time being. Are you sure we want a full duplex instead of half? Eitherway i hard coated the card
06-02-2006 09:36 AM
Ok this output means it is not connected. You either have
a)A faulty NIC in your linux box, b) a faulty cable c) a faulty switchport
Have you got anything else you can plug in just to see if the interface comes up? If you have just issue the same command again (show int fa0/1)
100mbps and full duplex is the way to go. Lets hard wire the switchports so we know for sure what is going on and not leave it to auto negociate. Also set say port 24 to this as well and test connection in there
switch#conf t
switch(config)#int fa0/1
switch(config-if)#speed 100
switch(config-if)#duplex full
switch#copy run start
Also just do a switch2#show vlan and paste the output , all ports should be in vlan1 by default as the config is blank but lets check.
--Phil
06-05-2006 03:55 AM
Well my boss informed me today that he called the IT department to come give us a hand so I should be all set from here on out...thank your for your help and should i need anymore help i know where I can get it..thanks again
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide