I am using two Windows 7 Pro laptops with Windows Firewall disabled and static IPs set on both to the same subnet. I added flow control and port security just to try to get it working (I have removed them now), as I wasn't sure what the defaults were. When I enable spanning tree, the output of the spanning tree command is:
console# show spanning-tree active
Spanning tree enabled mode RSTP
Default port cost method: long
Root ID Priority 32768
Address 00:15:c5:2a:f3:fd
This switch is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Number of topology changes 1 last change occurred 00:00:03 ago
Yes, if I direct connect the laptops together or through another switch, both of them can ping each other. No anti-virus besides Windows Firewall is running, and Windows Firewall is disabled.
I moved one laptop to port g24 and moved the second to g23, to my surprise, the pings worked! I then went and did a port-by-port test, and it appears only ports 15-24 work on my switch. All the other act like they are working (linkup, stp forwards etc.) but I cannot pass any traffic.
I'm not sure what else besides a hardware problem causes this with the default configuration.
instipod
5 Posts
0
October 14th, 2015 10:00
I am using two Windows 7 Pro laptops with Windows Firewall disabled and static IPs set on both to the same subnet. I added flow control and port security just to try to get it working (I have removed them now), as I wasn't sure what the defaults were. When I enable spanning tree, the output of the spanning tree command is:
console# show spanning-tree active
Spanning tree enabled mode RSTP
Default port cost method: long
Root ID Priority 32768
Address 00:15:c5:2a:f3:fd
This switch is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Number of topology changes 1 last change occurred 00:00:03 ago
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Interfaces
Name State Prio.Nbr Cost Sts Role PortFast Type
------ -------- -------- --------- ------ ---- -------- -----------------
g1 enabled 128.1 20000 FRW Desg No P2p (RSTP)
g2 enabled 128.2 20000 FRW Desg No P2p (RSTP)
The port counters command is:
console# show interfaces counters ethernet g2
Port InOctets InUcastPkts InMcastPkts InBcastPkts
---------------- ---------- ----------- ----------- -----------
g2 52118 0 248 245
Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts
---------------- ---------- ------------ ------------ ------------
g2 6888 1 92 12
FCS Errors: 0
Single Collision Frames: 0
Late Collisions: 0
Excessive Collisions: 0
Oversize Packets: 0
Internal MAC Rx Errors: 0
Received Pause Frames: 0
Transmitted Pause Frames: 0
console# show rmon statistics ethernet g2
Port g2
Dropped: 0
Octets: 53748 Packets: 509
Broadcast: 257 Multicast: 252
CRC Align Errors: 0 Collisions: 0
Undersize Pkts: 0 Oversize Pkts: 0
Fragments: 0 Jabbers: 0
64 Octets: 164 65 to 127 Octets: 386
128 to 255 Octets: 64 256 to 511 Octets: 9
512 to 1023 Octets: 0 1024 to 1518 Octets: 0
I have tried updating the firmware to 2.0.0.19, and that did not solve any problems. I am currently running 2.0.0.19, when I ran the above commands.
console# show version
SW version 2.0.0.19 ( date 05-May-2008 time 16:33:30 )
Boot version 1.0.0.13 ( date 13-Aug-2003 time 15:28:31 )
HW version 00.01.64
instipod
5 Posts
0
October 14th, 2015 11:00
I tried setting the ports to force 1000/full duplex with no change. I have swapped cables and these are known-good with another switch.
instipod
5 Posts
0
October 14th, 2015 13:00
Yes, if I direct connect the laptops together or through another switch, both of them can ping each other. No anti-virus besides Windows Firewall is running, and Windows Firewall is disabled.
instipod
5 Posts
0
October 14th, 2015 14:00
I moved one laptop to port g24 and moved the second to g23, to my surprise, the pings worked! I then went and did a port-by-port test, and it appears only ports 15-24 work on my switch. All the other act like they are working (linkup, stp forwards etc.) but I cannot pass any traffic.
I'm not sure what else besides a hardware problem causes this with the default configuration.