%IPC-5-WATERMARK:

ciantwohig · ‎05-19-2015

Hi

We've a stack of 4 3850 switches trunked to catalyst 6500. The switches are connected to ESX servers. We are getting the following log messages


*May 19 12:21:14.300: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:21:48.301: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:22:23.898: %IPC-5-WATERMARK: 8308 messages pending in xmt for the port (11900900.4) from source seat 11100100,
       
*May 19 12:22:57.980: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:23:32.301: %IPC-5-WATERMARK: 8212 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:24:06.303: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:24:42.310: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:25:16.311: %IPC-5-WATERMARK: 8211 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:25:52.313: %IPC-5-WATERMARK: 8212 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:26:25.481: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:27:00.332: %IPC-5-WATERMARK: 8211 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:27:34.333: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:28:08.332: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:28:43.894: %IPC-5-WATERMARK: 8308 messages pending in xmt for the port (11900900.4) from source seat 11100100,
       
*May 19 12:29:18.331: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:29:53.891: %IPC-5-WATERMARK: 8307 messages pending in xmt for the port (11900900.4) from source seat 11100100,
       
*May 19 12:30:28.331: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
          
*May 19 12:31:03.892: %IPC-5-WATERMARK: 8307 messages pending in xmt for the port (11900900.4) from source seat 11100100,
       
*May 19 12:31:36.332: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:32:12.332: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:32:46.331: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:33:20.330: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:33:54.346: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:34:30.340: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:35:04.422: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:35:40.421: %IPC-5-WATERMARK: 8210 messages pending in xmt for the port (10900C00.4) from source seat 11100100,
       
*May 19 12:36:14.422: %IPC-5-WATERMARK: 8209 messages pending in xmt for the port (10900C00.4) from source seat 11100100,

Looking through posts online this appears to be a cosmetic bug, but it usually relates to 6500s and not 3850s

Any advise would be appreciated

thanks

Mark Malone · ‎05-19-2015

effects 3850s too

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/3se/release_notes/OL_28114.html

CSCuh20848

The console displays %IPC-5-WATERMARK log messages repeatedly.

There is no workaround. There is no functional impact.

ciantwohig · ‎05-19-2015

Thanks markmalone2008

chsarkar · ‎05-19-2015

Do you see these repeated messages in 3850 ? What code are you running ? Since when did you start to see these messages appearing ?

ciantwohig · ‎05-19-2015

Hi Chandan,

Yes, these messages are continuous, I do not know how long they have been appearing as these switches are not pointing at a syslog server at the moment.

I am running SW Version : 03.02.02.SE SW Image : cat3k_caa-universalk9

Thanks

Cian

chsarkar · ‎05-19-2015

You probably hitting below bug.

https://tools.cisco.com/bugsearch/bug/CSCuh20848/?reffering_site=dumpcr

Seen on 3850 switches running 03.02.01.SE or 3.2.2 or 3.2.3 that are stacked. No known trigger at this time.The messages have no operational impact. Due to a code change, this issue will not apply to 3.3.0(SE) and beyond. "logging discriminator" could be used to filter out the messages.

Hope it helps you !