02-13-2015 01:30 AM - edited 03-07-2019 10:38 PM
Hi all,
We are experiencing an issue which seems to contradict itself on a stack of 3 switches. The issue we are seeing does not seem to be very well described in the Cisco documentation, if merely shows the status exists, but not if it's good or bad.
I'll note some output regarding the issue below.
Switch Ports Model SW Version SW Image
------ ----- ----- ---------- ----------
* 1 12 WS-C3750G-12S 12.2(55)SE5 C3750-IPBASEK9-M
2 12 WS-C3750G-12S 12.2(55)SE5 C3750-IPBASEK9-M
3 52 WS-C3750-48TS 12.2(55)SE5 C3750-IPBASEK9-M
Switch-1#sh sw stack-port summ
Switch#/ Stack Neighbor Cable Link Link Sync # In
Port# Port Length OK Active OK Changes Loopback
Status To LinkOK
-------- ------ -------- -------- ---- ------ ---- --------- --------
1/1 OK 3 50 cm Yes Yes Yes 2 No
1/2 OK 2 50 cm Yes Yes Yes 2 No
2/1 OK 1 50 cm Yes Yes Yes 2 No
2/2 OK 3 50 cm Yes Yes Yes 2 No
3/1 OK 2 50 cm Yes Yes Yes 2 No
3/2 OK 1 50 cm Yes Yes Yes 2 No
Switch-1#sh platform stack manager all
Switch/Stack Mac Address : xxxx.xxxx.xxxx.xxxx
H/W Current
Switch# Role Mac Address Priority Version State
----------------------------------------------------------
*1 Master xxxx.xxxx.xxxx.xxxx 15 0 Ready
2 Member xxxx.xxxx.xxxx.xxxx 14 0 Ready
3 Member xxxx.xxxx.xxxx.xxxx 13 0 Ready
Stack Port Status Neighbors
Switch# Port 1 Port 2 Port 1 Port 2
--------------------------------------------------------
1 Ok Ok 3 2
2 Ok Ok 1 3
3 Ok Ok 2 1
Switch-1# sh switch neighbors
Switch # Port 1 Port 2
-------- ------ ------
1 3 2
2 1 3
3 2 1
So far everything seems good, agreed?.. now the output that causes doubt.
SWMLSSGESR09-1#sh platform stack ports buffer
Stack Debug Event Data Trace
==============================================================
Event type LINK: Link status change
Event type RAC: RAC changes to Not OK
Event type SYNC: Sync changes to Not OK
==============================================================
Event Stack Stack PCS Info Ctrl-Status Loopback Cable
Count Port IOS / HW length
========= ===== =================================== =========== ======== ========
Event type: LINK OK Stack Port 2
0000000117 1 FF08FF00 84035BFD AAAAFFFF FFFFFFFF 0C340CE0 No /No 50 cm
0000000117 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 0C340CE0 No /No 50 cm
Event type: RAC
0000000118 1 FF08FF00 84035BFD AAAAFFFF FFFFFFFF 0C340CE0 No /No 50 cm
0000000118 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 0C340CE0 No /No 50 cm
Event type: LINK OK Stack Port 1
0000000655 1 FF08FF00 86032D8D 5555FFFF FFFFFFFF 1CE61CE0 No /No 50 cm
0000000655 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 1CE61CE0 No /No 50 cm
Event type: RAC
0000000656 1 FF08FF00 86032D8D 5555FFFF FFFFFFFF 1CE61CE0 No /No 50 cm
0000000656 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 1CE61CE0 No /No 50 cm
Event type: LINK NOT OK Stack Port 1
0000018717 1 FF08FF00 000128F6 00000002 FFFFFFFF 0E140CE0 No /No 50 cm
0000018717 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 0E140CE0 No /No 50 cm
Event type: RAC
0000018718 1 FF08FF00 00012940 16010703 FFFFFFFF 0E140CE0 No /No 50 cm
0000018718 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 0E140CE0 No /No 50 cm
Event type: LINK OK Stack Port 1
0000018913 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
0000018913 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 1EE61CE0 No /No 50 cm
Event type: RAC
0000018914 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
0000018914 2 FF08FF00 86038FE6 5595FFFF FFFFFFFF 1EE61CE0 No /No 50 cm
Event type: LINK NOT OK Stack Port 2
0000019999 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 0EE60CE0 No /No 50 cm
0000019999 2 FF08FF00 00018D79 00000000 FFFFFFFF 0EE60CE0 No /No 50 cm
Event type: RAC
0000020000 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 0EE60CE0 No /No 50 cm
0000020000 2 FF08FF00 00018DC2 09954FFF FFFFFFFF 0EE60CE0 No /No 50 cm
Event type: LINK OK Stack Port 2
0000020193 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
0000020193 2 FF08FF00 86036557 556AFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
Event type: RAC
0000020194 1 FF08FF00 8603CA6B AAAAFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
0000020194 2 FF08FF00 86036557 556AFFFF FFFFFFFF 1EE61CE0 No /No 50 cm
The 2 messages reading LINK NOT OK event types and Event type RAC and SYNC both seems to indicate an issue.
the stack cables have all been replaced already and this has not changed the status.
please let me know your thoughts, if possible an answer today would be perfect.
thank you,
Mike
Solved! Go to Solution.
03-30-2015 05:39 AM
Dude, you do not need to worry about anything.
Based on your post. you are concerned with the logs below:
There is nothing to worry about the logs above. that is just normal.
If you want proof check out this Cisco documentation, you can see that the "show platform stack ports buffer" shows it.
03-25-2015 07:37 AM
hi,
so after more than a month i haven't received any reply..
either the question is so advanced no one knows, or so stupid no one cares.
i'd still like to get an answer to this, i'm sure someone out there can shoot me a quick explanation at least? if any additional info is needed just let me know.
thank you,
03-25-2015 11:48 AM
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 whatsoever (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
More likely the former. Many of the posters to these forums are ordinary engineers, probably like yourself. Unless someone has been down the same path, most of us won't know.
This type of question is normally better done via Cisco's TAC, but perhaps someone will yet chime in.
03-26-2015 08:17 PM
I actually haven't seen this question posted on supportforums, well anyway.
Can you take a pic on how you connected the three switches? i.e., take a picture at the back of the switches?
Can you as well post (please put it in notepad) the following commands
03-27-2015 03:51 AM
Hi Isgabrillo,
thank you for your reply, at this point i'm unable to take a Picture due to the switches being on a remote location. though i suspect you would like to see the stack cabling?
if you looks at command: "sh platform stack manager all" above, you can see the connectivity order.
all cables are cisco original and have been swapped with spares.(and are securely fastened)
for the output i may need to send you output from a different 5 switch stack with this similar issue. i'm unable to access the 3 switch stack above at this time.
will attach requested output shortly.
thank you,
03-30-2015 02:23 AM
03-30-2015 05:39 AM
Dude, you do not need to worry about anything.
Based on your post. you are concerned with the logs below:
There is nothing to worry about the logs above. that is just normal.
If you want proof check out this Cisco documentation, you can see that the "show platform stack ports buffer" shows it.
03-31-2015 02:30 AM
hi,
thanks for your reply, indeed that output had me wondering if it was relating to the issue i'm having.
as far as proof goes, i've seen pretty much all Cisco documentation and indeed also noticed this status in the documentation, but it did not note/explain the status. it wouldn't be the first time Cisco documentation has undefined errors in output.
that being said, i do think you may be right and at this point 2 replies here indicate these are status messages generated during a certain process.
i will consider your answer correct, (untill proven otherwise?)
03-30-2015 07:00 AM
Sorry for the late reply, i have seen this a few times but it has never caused an issue with the stack. I actually think it is a historical event rather than a current issue.
I have a similar output on one of my stacks, however the stack works flawlessly and i simply swapped a stack cable out (It was longer than needed)
i hope this helps. I will keep looking.
03-31-2015 02:21 AM
thanks for your reply, i was thinking about that as well, so i'll probably need to be looking at the issue i'm having from another approach.
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: