cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
441
Views
0
Helpful
2
Replies

WS-2960S-48FPS-L, 15.0(2)SE4 and 1040 Sensor

Christoph Faber
Level 1
Level 1

Just upgraded a switch WS-2960S-48FPS-L from 12.2(55)SE7 to 15.0(2)SE4. Connected to the swich is a 1040 sensor.

Using 12.2(55)SE7 it used to work fine, but since 15.0(2)SE4 it stopped working.

The Switch only recognizes it as IEEE PD, cdp neighbour is empty, the sensor is not reachable.

show power inline:

Gi1/0/11  auto   on         15.4    Ieee PD             0     30.0

switch log:

Jul 12 10:29:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 10:29:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Jul 12 10:30:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 10:30:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Jul 12 10:50:19: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 10:50:21: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Jul 12 10:50:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 10:50:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Jul 12 11:10:49: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 11:10:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Jul 12 11:11:08: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to down

Jul 12 11:11:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/11, changed state to up

Using another 1040 Sensor resulted in the same.

Any suggestions?

2 Replies 2

Leo Laohoo
Hall of Fame
Hall of Fame

Do the following:

1.  test cable tdr Interface GigabitEthernet1/0/11;

2.  Wait for approximately 5 to 7 seconds;

3.  sh cable tdr Interface GigabitEthernet1/0/11; and

4.  Post the output to #3.

Thanks for the reply. After some hours of testing I figured it out.

It was not an issue of the Sensor, but of the port-configuration.

If the same vlan for voice and access are configured on one interface with a SW-Version of 15.0(2) or higher, it is not possible to access the device via DATA.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco