Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Switch 3750x-48PS

Hello guys,

'I new here in the Forum and would like to post my first question: Where I work, my client has 3 switches model 3750x-48PS connected via cable stack.

The problem is in the switch 3 of the stack the two doors giga3/0/21 and giga3/0/24, the phones don't register in the register, but when I ask for customer connect on another port or other switches in the stack, the phones register normally.

I did another procedure to give the command reload slot on the switch 3, the phones registered in ports that I mentioned above, but then lost the record. Has anyone got a similar problem? Know to report if there is a bug in these specific models?


Thank you in advance!
16 REPLIES
Super Bronze

Disclaimer

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.

Posting

A properly functioning 3750X stack, functional behavior shouldn't vary just depending on which stack member you connect to.

What IOS version is being used?

New Member

Hi Joseph,

Hi Joseph,

Thank you for the return! The IOS is version 15.0 (1) SE2 
But details are in the attached file.
 
Super Bronze

Do you have a maintenance

Do you have a maintenance contract and do you need 15x features?

New Member

I contacted Cisco and I was

I contacted Cisco and I was told that the agreement only covers replacement, as for example in the event of a failure. We have no right to the support engineer can do the troubleshooting.
Super Bronze

So your maintenance contract

So your maintenance contract doesn't support changing IOS versions?  (That's far different opening a TAC case.)

Bronze

Hello, Stefanio38.

Hello, .

Is there any difference at the configuration between this problem ports and ports that works well? Does another devices works well at this ports? Is there any errors at this ports?

Best Regards.

New Member

Hi, AllertGen

Hi, AllertGen

The settings are the same for all ports on the switch and logs p just nothing out of the ordinary of the door are ranging from UP and DOWN, because I was testing along with the client. The problem is that when it connects to the phone on the doors giga3/0/giga3/0/21 and 24 no phone registers on this port. If I test on another port on the same switch or another switch of the stack the phones register normally.

If case is useful phones of Cisco IP model 6945, with firmware version 6945.9-4-1 CCP-3.
I'm sending you attached the configuration file

Highlighted
Silver

Hi,

Hi,

Both your Gi3/0/21 and Gi3/0/24 ports have hardcoded speed and duplex. Can you please configure both to "auto" and see if there is any progress.

Best regards,

Antonin

New Member

Hi.

Hi.

I have done this test and had no effect no.
Bronze

Hi.

Hi.

Is there any errors by commands "show interface Gi3/0/21" and "show interface Gi3/0/24"?

Best Regards.

New Member

Hi, Allert,

Hi, Allert,

There is no errors in both doors. This problem is very bizarre!
WSPSW05#show interfaces gigabitEthernet 3/0/21
GigabitEthernet3/0/21 is down, line protocol is down (notconnect)
  Hardware is Gigabit Ethernet, address is 2894.0fc1.a815 (bia 2894.0fc1.a815)
  Description: --------------[CONEXAO COM USUARIO]
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 5d21h, output 2d21h, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     12119304 packets input, 3173328259 bytes, 0 no buffer
     Received 657602 broadcasts (259040 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 259040 multicast, 0 pause input
     0 input packets with dribble condition detected
     255026466 packets output, 63390961937 bytes, 0 underruns
     0 output errors, 0 collisions, 5 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
WSPSW05#
WSPSW05#
WSPSW05#
WSPSW05#show interfaces gigabitEthernet 3/0/24
GigabitEthernet3/0/24 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 2894.0fc1.a818 (bia 2894.0fc1.a818)
  Description: --------------[CONEXAO COM USUARIO]
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 1000Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 5d21h, output 00:00:28, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 98000 bits/sec, 60 packets/sec
     2896986 packets input, 418050619 bytes, 0 no buffer
     Received 169905 broadcasts (78415 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 78415 multicast, 0 pause input
     0 input packets with dribble condition detected
     152189136 packets output, 35524874407 bytes, 0 underruns
     0 output errors, 0 collisions, 4 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
WSPSW05#
The door 3/0/21 giga is down because I requested him to disconnect the ip phone. While the door giga3/0/24 I don't see coming CPD information in it. Possibly should be turned on any station, network printer or anything else that doesn't return CDP
Bronze

Well, the last test that I

Well, the last test that I can to offer is to put another device (not a phone) to this port and look how good it works. If there is problems as well than there could be damaged ports. If not than it's better to contact TAC if you (or your client) has a SmartNet contract.

Best Regards.

New Member

Thank you AllertGen.

Thank you AllertGen.

My client said had more 3 ip phone lost register. I'll open a TAC on Cisco.
Bronze

Could it be not a switch

Could it be not a switch problem? For example could it be out of license or extension numbers at the phone server side?

Best Regards.

New Member

Well... I don't think, Allert

Well... I don't think, Allert, because I before I had done test connecting the ip phone on the switch 1 of the stack they recorded normally. I'm arriving at the conclusion that switch problem ....

New Member

These are the logs that I

These are the logs that I took just now on the switch. Nothing out of the ordinary.
Feb  3 16:49:31.030: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:49:32.037: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:49:35.761: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:49:36.776: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:52:19.443: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:52:20.449: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:52:24.107: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:52:25.113: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:55:07.906: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:55:08.913: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:55:12.402: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:55:13.409: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:57:56.386: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:57:57.392: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 16:58:01.184: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 16:58:02.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:00:44.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:00:45.914: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:00:49.815: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:00:50.830: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:01:26.229: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/27, changed state to down
Feb  3 17:01:27.244: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/27, changed state to down
Feb  3 17:01:30.255: %LINK-3-UPDOWN: Interface GigabitEthernet3/0/27, changed state to up
Feb  3 17:01:31.262: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3/0/27, changed state to up
Feb  3 17:03:33.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:03:34.386: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:03:37.783: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:03:38.790: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:06:21.960: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:06:22.958: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:06:26.557: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:06:27.563: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:09:10.356: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:09:11.362: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:09:14.969: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:09:15.984: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:11:58.819: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:11:59.825: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to down
Feb  3 17:12:03.458: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/13, changed state to up
Feb  3 17:12:04.464: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/13, changed state to up
99
Views
0
Helpful
16
Replies
CreatePlease login to create content