Showing results for 
Search instead for 
Did you mean: 
Join Customer Connection to register!
N3t W0rK3r

Printer problems with Catalyst 3750 switch stack

Today we had 3 printers suddenly stop responding on the network at around the same time.  All printers are connected to the same switch stack, but to two different modules.  No other devices were affected by this.  Here is the switch stack information:

Switch Ports Model              SW Version            SW Image                

------ ----- -----              ----------            ----------              

*    1 52    WS-C3750-48P       12.2(55)SE5           C3750-IPBASEK9-M        

     2 52    WS-C3750-48TS      12.2(55)SE5           C3750-IPBASEK9-M        

     3 52    WS-C3750-48TS      12.2(55)SE5           C3750-IPBASEK9-M        

The printers all had static IPs and when we looked at their switchports, no MAC addresses were visible even though the ports were up/up and the printer was powered on as normal.

Power cycling the printers did nothing.  Shut/no shut on the ports did nothing.  Removing port-security and dhcp snooping commands on the switch and ports did nothing (these security features were recently added to our configurations enterpirse-wide).

We changed each printer's IP address to a different one (in the same subnet) and this seemed to work in all cases.  So after a few minutes we changed the IP addresses back to the original ones and the printers continued to work, for a while, but then they failed again.

Finally, we assigned new addresses to each printer, from a different subnet this time (and changed each port's vlan memebership accordingly) and the printers have now been working fine for a few hours.

Each port is configured similarly, as follows:

interface FastEthernet2/0/1

description S0065

switchport access vlan 353

switchport mode access

switchport port-security maximum 3

switchport port-security

switchport port-security aging time 1

switchport port-security aging type inactivity

spanning-tree portfast

ip dhcp snooping limit rate 100


BTW this is NOT the first time this has happened to us... this happened a few months ago and the solution was the same, but I can't remember if they were connected to the same switch stack or not.

Does anyone have any ideas about what may be happening here?  We'd really appreciate some help with this.