Link to home
Start Free TrialLog in
Avatar of dingdong123
dingdong123

asked on

%IPC-SP-5-WATERMARK: xxx messages pending in rcv for the port Primary RFS Server Port(10000.D) seat 10000

Hi,

Can anybody please give me a hand with troubleshooting this error message we have on a Cisco 6509 switch. I am finding conflicting information when doing a goole search. We have recently upgraded to  12.2(33)SXI4 which is supposed to be Safe Harbour (and bug scraped by us with nothing of note picked up) and we now have people getting jumpy over whether this is a service impacting bug or not. Even displaying the show version output is hanging. Conversely this switches HSRP partner is not displaying this error (or an of the other 4 switches we have running this IOS). We have only been seeing this error for 2 days with the number of messages increasing. Memory and processor are not overloaded.

Thanks in advance!


%IPC-SP-5-WATERMARK: xxx messages pending in rcv for the port Primary RFS Server Port(10000.D) seat 10000


xxxxxxxxxxx#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI4, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Sat 29-May-10 17:55 by prod_rel_team

ROM: System Bootstrap, Version 12.2(17r)SX7, RELEASE SOFTWARE (fc1)

xxxxxxxxx uptime is 18 weeks, 4 days, 20 hours, 14 minutes
Uptime for this control processor is 18 weeks, 4 days, 20 hours, 19 minutes
Time since xxxxxxxxxxxx switched to active is 18 weeks, 4 days, 20 hours, 18 minutes
System returned to ROM by reload at 16:20:51 UTC Thu Dec 9 2010 (SP by reload)
System restarted at 16:24:16 UTC Thu Dec 9 2010
System image file is "sup-bootdisk:s72033-adventerprisek9_wan-mz.122-33.SXI4.bin"
Last reload reason: Unknown reason



.............



cisco WS-C6509-E (R7000) processor (revision 1.5) with 458720K/65536K bytes of memory.
Processor board ID xxxxxxxxxxxx
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
2 Virtual Ethernet interfaces
148 Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102


xxxxxxxxxx2#sh mod
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     xxxxxxxxxxxxx
  2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     xxxxxxxxxxxxx
  3   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX    xxxxxxxxxxxxxxxx
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-3B      xxxxxxxxxxxxxxx
  6    2  Supervisor Engine 720 (Hot)            WS-SUP720-3B       xxxxxxxxxxxxxxx

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  xxxxxxxxxxxxxxxxxxxx   3.4   12.2(18r)S1  12.2(33)SXI4 Ok
  2  xxxxxxxxxxxxxxxxxxxx   3.4   12.2(18r)S1  12.2(33)SXI4 Ok
  3  xxxxxxxxxxxxxxxxxxxx   3.4   12.2(18r)S1  12.2(33)SXI4 Ok
  5  xxxxxxxxxxxxxxxxxxxx   5.11  8.5(4)       12.2(33)SXI4 Ok
  6  xxxxxxxxxxxxxxxxxxxx   5.11  8.5(4)       12.2(33)SXI4 Ok

Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  1  Centralized Forwarding Card WS-F6700-CFC       xxxxxxxxxxxx  4.1    Ok
  2  Centralized Forwarding Card WS-F6700-CFC       xxxxxxxxxxxx  4.1    Ok
  3  Centralized Forwarding Card WS-F6700-CFC       xxxxxxxxxxxxx  4.1    Ok
  5  Policy Feature Card 3       WS-F6K-PFC3B       xxxxxxxxxxxxxxx  2.6    Ok
  5  MSFC3 Daughterboard         WS-SUP720         xxxxxxxxxxxxxxx  5.0    Ok
  6  Policy Feature Card 3       WS-F6K-PFC3B       xxxxxxxxxxxxxx  2.6    Ok
  6  MSFC3 Daughterboard         WS-SUP720          xxxxxxxxxxxxxx  5.0    Ok

Mod  Online Diag Status
---- -------------------
  1  Pass
  2  Pass
  3  Pass
  5  Pass
  6  Pass
xxxxxxxxxxxxxxxxxx#
Avatar of surbabu140977
surbabu140977
Flag of India image

You are hitting a IOS bug CSCsc80303.

Below is the copy paste from Cisco. You can typically do nothing about this. Please upgrade your IOS to any of the mentioned versions.
12.2(32.8.11)SX4
12.2(32.8.30)SRB
12.2(33)SXH
12.2(33)SB
12.2(32.8.99a)SR133
12.2(32.8.1)YCA172.24
12.2(32.8.1)YCA206.1

##############################
%IPC-SP-5-WATERMARK: 7167 messages pending in rcv for the port Card7/0:
Symptoms: IPC Watermark messages may be generated when a trunking interface
goes up or down, and a memory leak may occur.

Conditions: This symptom is observed on a Cisco Catalyst 6000 series switch
and Cisco 7600 series router that are configured with a dot1q trunking
interface that is bundled with more than 2000 VLAN interfaces.

Workaround: There is no workaround.
##############################

The last ios was a typo. It's 12.2(32.8.1)YCA206.18.

The category of this bug is noted as "severity 2". That means it might hamper your production environment and an upgrade of IOS is recommended, although the switch might continue to function.

Any IOS release, which is after the mentioned IOS releases above, will have this bug fixed. So it's not mandatory that you have to select *ONLY* those.

This is a cosmetic defect with the messages pending counter.

Best,

Avatar of dingdong123
dingdong123

ASKER

12.2(33)SXI4 is not listed in the know affected versions for this bug (I wonder if they are not publishing this IOS as they have declared it SafeHarbour!). We also do not have 2000 vlans.
Any IOS release, which is after the mentioned IOS releases above, will have this bug fixed

Surely we are running a newer IOS to those listed?
ASKER CERTIFIED SOLUTION
Avatar of surbabu140977
surbabu140977
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ok thanks - your help is much appreciated. Not going to trust SafeHarbour much in future!