Did you disable spanning tree or used portfast on the ports which are connected to clients. We have a customer that had the same issue and we changed the client ports on the 6500's to portfast. Here is the link.
http://www.cisco.com/warp/public/473/12.html Best regards, Cisco Breaker ""Michael Williams"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Okay.... we have two 6509s with Sup2/MSFC2 running Native IOS 12.1(8b)E7, > and a Cat5513 running CatOS 4.5(2) with RSM running IOS 11.3(3a)WA4(5). We > have 6509A connected via a Gig trunk (ISL) to 6509B and 6509B connects to > the 5513 via a 4-link FastEtherchannel trunk (ISL). Most of our Novell > servers are connected to the 5513 and ALL Novell servers reside in VLAN1. > All VLANs are trunked between all 3 switches. The RSM in the 5500 handles > all IPX routing for all VLANs and the two 6500s do no IPX routing. IP > Routing for the various VLANs are spread around the 6500s/5513 with HSRP. > Our standard PC image has Win95 with Netware Client 3.2 (I believe) > installed. IPX frame type under Windows is set to 802.3. Under normal > circumstances, the PC boots, and comes up to the Novell login. > > Issue: > > * If the PC is connected to 6509B in any other VLAN except 1, you get a > Novell login and IPX works fine. > > * If you connect a PC to 6509B in VLAN1, and boot, you get no Novell login. > You can, from the RSM in the 5513, so an IPX ping with standard Novell > Echos and it is successful. > But I also have a utility that runs in a DOS window under Windows called > SPXping. Using SPXping, I cannot ping to or from said PC. > > * If I move that PC to either 6509A or 5513, and reboot, it comes up fine > and SPXping works fine. (remember that 6509A has to go through 6509B to > reach the Novell servers on the 5513) > * If the PC is connected to either 6509A or 5513, boots up and you login to > Novell, you can then move the connection to 6509B and it works fine until > the PC is rebooted. > > * IP is not affected in any way no matter which switch the PC connects to > (which seems to imply a L3 IPX issue, but 6509B isn't running any L3 IPX and > should, from an IPX perspective, act as a L2 switch only for PCs connected > to it) > > Any input is appreciated!! I about to tear my hair out over this.... (and > so is the TAC engr).... > > Thanks! > Mike W. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=47952&t=47951 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
