10-31-2002 06:23 AM - edited 03-02-2019 02:32 AM
I have a Cat2950 series switch we have configured only three ports to be up the others having all been shut down.
We are having problems with these three ports the devices cannot see each other.
Devices connecting to the switch are 2 routers and a firewall. The link lights are green and are blinking intermittently.
I have not configured and IP (shouldnt need to because this is a layer two device) but its bugging me that I have not done so and I some how think this is the problem. Is this the problem? Or is there something else that I am over looking?
10-31-2002 06:47 AM
Can you post the configuration of the three ports then we all can take a look at how its configured. You should not have to put an ip address on the ports of the switch but should have one to manage the switch from. Be sure all the ports are on the same VLAN. (i'll assume you've already done that)
10-31-2002 06:59 AM
I dont want to administer this switch via telnet so no ip is requred we have a console cable for that. all int are in the native vlan (vlan1) vlan 1 is up.
below is the run config:
Current configuration : 1936 bytes
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname IntecSwitch
!
enable secret 5
enable password 7
!
ip subnet-zero
vtp mode transparent
!
spanning-tree extend system-id
!
!
interface FastEthernet0/1
description Connection to Netscreen
no ip address
!
interface FastEthernet0/2
description Connection to UUNET
no ip address
!
interface FastEthernet0/3
description Connection to IS
no ip address
!
interface FastEthernet0/4
no ip address
shutdown
!
interface FastEthernet0/5
no ip address
shutdown
!
interface FastEthernet0/6
no ip address
shutdown
!
interface FastEthernet0/7
no ip address
shutdown
!
interface FastEthernet0/8
no ip address
shutdown
!
interface FastEthernet0/9
no ip address
shutdown
!
interface FastEthernet0/10
no ip address
shutdown
!
interface FastEthernet0/11
no ip address
shutdown
!
interface FastEthernet0/12
no ip address
shutdown
!
interface FastEthernet0/13
no ip address
shutdown
!
interface FastEthernet0/14
no ip address
shutdown
!
interface FastEthernet0/15
no ip address
shutdown
!
interface FastEthernet0/16
no ip address
shutdown
!
interface FastEthernet0/17
no ip address
shutdown
!
interface FastEthernet0/18
no ip address
shutdown
!
interface FastEthernet0/19
no ip address
shutdown
!
interface FastEthernet0/20
no ip address
shutdown
!
interface FastEthernet0/21
no ip address
shutdown
!
interface FastEthernet0/22
no ip address
shutdown
!
interface FastEthernet0/23
no ip address
shutdown
!
interface FastEthernet0/24
no ip address
shutdown
interface FastEthernet0/24
no ip address
shutdown
!
interface Vlan1
no ip address
no ip route-cache
!
ip http server
!
banner motd ^C
This is a secure Switch no Unautorised access is allowed! If you are unsure plea
se disconnect.^C
!
line con 0
password 7
line vty 0 4
login
line vty 5 15
login
!
end
10-31-2002 06:56 AM
Did you configure anything on the switch?
eg
Cat2950(config)#int range fa0/1 - 4
Cat2950(config-if-range)#switchport access vlan 10
I also assume the 3 devices are on the same subnet. Can you post the config? What does show int f0/1 show (ie up/up)? Are there errors on the interfaces (ie speed/duplex issue)? You would give the switch an IP if you want to be able to telnet to it (a good idea) for management, and a gateway if you want to be able to access the switch from other vlans.
Steve
10-31-2002 07:24 AM
have left them all in vlan 1, because I did know if it was the vlan causing the problem, the idea will be to move them into there own vlan but I have to get it working first. all interfaces show up up speed and duplex have not been configured until we have it running currently they are set to auto.
10-31-2002 07:30 AM
Under each of the 3 ports you need to place them in VLAN 1 by using the switchport access vlan 1 command, this should get you going.
-d
10-31-2002 07:36 AM
by default all ports are in this vlan, I can confirm this by doing a show vlan,
which gives me this:
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15, Fa0/16
Fa0/17, Fa0/18, Fa0/19, Fa0/20
Fa0/21, Fa0/22, Fa0/23, Fa0/24
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------
1 enet 100001 1500 - - - - - 0 0
1002 fddi 101002 1500 - - - - - 0 0
1003 tr 101003 1500 - - - - - 0 0
1004 fdnet 101004 1500 - - - ieee - 0 0
1005 trnet 101005 1500 - - - ibm - 0 0
as you can see the ports are in vlan 1 already
10-31-2002 07:53 AM
Ok.....so what are the IP addresses of the routers and the netscreen?
10-31-2002 10:30 PM
The IP addresses I cant really disclose but we have confirmed that they are in the same subnet /27 and are from in the same range.
I have removed the switch and added two clients with ip 10.2.5.7 and 10.2.5.8 on /24 network and connected themt o the switch and they cannot see each other either. its as if the switching method (cut trough or store and forward) is disabled. or not currently running.
is this possible and can I change that?
11-01-2002 12:24 AM
Help needed urgently
ok I have been playing around and I have noticed that loopback was not set on the vlan so tried it out and now I am getting traffic across the switch but very intermittenly and at about 1000 ms latency. which is strange if you have two clietns directly connected to the switch.
any other ideas
11-01-2002 06:18 AM
Um, my suggestion is to replace the switch with a hub as a test and make sure that everything is working fine like that... I am also assuming that you have rebooted the switch.... If not, try that...
Also, keep in mind that the netscreen can be configured to respond or not respond to pings. By default (at least in most SW revs!), the trust is pingable and the untrust is not.
11-01-2002 06:30 AM
currently I have had to put a hub there until I get the switch to work.
the hub works fine. I had enabled the untrust side to reply to icmp packets for the purpose of testing currently disabled because I have the hub there and it is working.
I have bounced the switch now just to double check and still no sweet success. I am throughing everything at this switch and getting no joy, my last resort is going to be to cisco to proove that their is no fault with the switch, I know POST should have picked up problems but somethign is definatly noot right with this switch.
11-01-2002 06:32 AM
thank you to all who tried to help me out, pitty I didnt solve it but I think I am going to have to get cisco in here to check this out because this is just to bazaar. murphies law the minute the engineer from cisco arrives it will work. if any body has any other ideas please send them in I will try anything.
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