Added Cisco Systems 2950 switch to home Network.

[leeishom]

(SOLVED)Added Cisco Systems 2950 switch to home Network.

Hi all, new here.

I just added a 2950 24 port switch to my network. It is hooked up to a RT56U - but all wired connections are not getting the connected to the net.
I have already configured the switch(being a CCNA), but it appears that the wired connections are not getting any feedback from the RT56U.

Is there a config I can add or change to the RT56U unit?


Thanks in advance.

 

[leeishom]

After further thinking about the issue, I have concluded that having the Switch act as DHCP server will in fact have all units have connectability. But I will lose Firewall and other consumer use functions.
Hmm.

 

[jdabbs]

DHCP has no impact on NAT/firewall functions. Router would be a better choice for DHCP as it can issue the current ISP-provided DNS server info to clients. I'd only rely on the switch for reserved leases (if your router lacks that feature).

The switch should work out of the box, so your config is suspect. If you copy/paste a sanitized version people can check it for mistakes.

 

[leeishom]

int f0/1
ip address 192.168.1.2 /24
switch access port vlan 1
default gateway 192.168.1.1 /24
DHCP server 192.168.1.1 /24
no shut

By default, all ports are vlan 1.

That's it.

Now, I configured the switch to be able to accept telnet sessions, that is why it as the .2 address.

 

[jdabbs]

The IP should be assigned to the VLAN, not the port. Nothing else stands out (other than DHCP, which I advised against earlier).

Here's what I would do:

1) Turn off DHCP on the switch. If you haven't verified basic connectivity, added complexity only makes it harder to troubleshoot.
2) Turn DHCP back on the router. Do an ipconfig /release and /renew on a PC cabled directly to the router to verify you can get an IP.
3) Take that PC and connect to one of the switch ports. Do an ipconfig /release and /renew to verify you can get an IP.
3a) (Assuming you are consoled in) If you can't, check the switch config to verify the ports are assigned to the same VLAN and not shut. Run a show ip int br to verify connectivity. If you still can't figure out what the problem is, reset the config and tweak until you're satisfied or you broke it again.
4) Bind an IP to the switch. Make sure it doesn't overlap with either your router or switch's DHCP scope. Ping that IP from the PC.
5) Once you've verified IP connectivity, then switch to telnet or muck around with DHCP.

 

[leeishom]

Hi, thanks for the reply - release and renew connected to the switch worked just for the laptop, but other devices, such as he PS3 are not able to connect, even after manual input.

I never did enable DHCP switch-side. One of the other problems was RT56U was connected to port 1 and this port was running errors. A simple shut, no shut did the trick.

Thanks.

 

[jdabbs]

I'd try the PS3 on a switch port that the laptop has confirmed working. Passing there would suggest a port-level problem.

Did you make the cable used when you were having problems with port 1? A bad crimp can cause errors.

 

[leeishom]

All cables are new Cat6, from an online vendor. As for the error, it was just on port 1, after a sh run, sh ip int br and other SHOW commands, all verified it was in Error, but after resetting it - it was fine. Just funny how, the PS3 cannot complete its DHCP request. But all others can. Even after manually inputting configs into it.

Below is the config for port 2, that is for the PS3.


EDIT: just cleared mac table. By issuing the -clear mac address dynamic- again, nothing.
Hmm..

 

[jdabbs]

When you run a sh ip int br when the PS3 is connected, are you seeing up/up on the corresponding port?

 

[leeishom]

Yup.
Status UP, Protocol UP.


EDIT: After googling up, surprised that others have connected their PS3 to a 2950!
Issuing the - spanning-tree portfast default - command did the trick!!! But, any hubs, bridges that are connected to the switch, with that command active - will create loops.

Thanks jdabbs for your attention and concern!

 

[jdabbs]

Link appears good--just no traffic. If you tested on Port 1 (or moved the PC to the PS3's port) you should be confident the config is not an issue. Could the PS3 be ignoring the Ethernet connection in favor of wireless?

 

[leeishom]

Link appears good--just no traffic. If you tested on Port 1 (or moved the PC to the PS3's port) you should be confident the config is not an issue. Could the PS3 be ignoring the Ethernet connection in favor of wireless?

Yup.
Status UP, Protocol UP.


EDIT: After googling up, surprised that others have connected their PS3 to a 2950!
Issuing the - spanning-tree portfast default - command did the trick!!! But, any hubs, bridges that are connected to the switch, with that command active - will create loops.

Thanks jdabbs for your attention and concern!

 

[jdabbs]

I can see DHCP not working in a scenario when the PS3 only sends out one request, whereas a PC would keep sending at regular intervals until the port goes live. That doesn't explain why a static IP wouldn't work after a minute or two, well within the amount of time necessary to manually input the IP configuration with a controller. Maybe the PS3 toggles the port on/off unnecessarily?

Still, good to hear that your issue was resolved after all.

 

[leeishom]

Yes, strange and unique - I would think something like a PS3 would connect, effortlessly, especially with manual input. Hmmm.

Remember Kids, issuing the - spanning tree portfast - command will work!