When you build a stack, you should always check to make sure the stack is communicating the way it should. Make sure the topology looks the way it should (which I edited out here), but also make sure the communication between CPU to CPU looks good. What that means is communication across the stacking cables from one CPU to another. What that boils down to is when a packet traverses from one switch in the stack to the other, switch one processes the packet, forwards across the stacking cable to switch two and on to its CPU for processing. You need to make sure communication is good, and the way to do that is highlighted below. Check it using the 'show stack connection' command, as show below:
CORE#show stack connection
edited...
trunk probe results: 4 links
Link 1: u4 -- u1, num=5
1: 1/2/1 (T0) <---> 4/2/6 (T1)
2: 1/2/2 (T0) <---> 4/2/7 (T1)
3: 1/2/3 (T0) <---> 4/2/8 (T1)
4: 1/2/4 (T0) <---> 4/2/9 (T1)
5: 1/2/5 (T0) <---> 4/2/10(T1)
Link 2: u2 -- u1, num=5
1: 1/2/6 (T1) <---> 2/2/1 (T0)
2: 1/2/7 (T1) <---> 2/2/2 (T0)
3: 1/2/8 (T1) <---> 2/2/3 (T0)
4: 1/2/9 (T1) <---> 2/2/4 (T0)
5: 1/2/10(T1) <---> 2/2/5 (T0)
Link 3: u3 -- u2, num=5
1: 2/2/6 (T1) <---> 3/2/1 (T0)
2: 2/2/7 (T1) <---> 3/2/2 (T0)
3: 2/2/8 (T1) <---> 3/2/3 (T0)
4: 2/2/9 (T1) <---> 3/2/4 (T0)
5: 2/2/10(T1) <---> 3/2/5 (T0)
Link 4: u4 -- u3, num=5
1: 3/2/6 (T1) <---> 4/2/1 (T0)
2: 3/2/7 (T1) <---> 4/2/2 (T0)
3: 3/2/8 (T1) <---> 4/2/3 (T0)
4: 3/2/9 (T1) <---> 4/2/4 (T0)
5: 3/2/10(T1) <---> 4/2/5 (T0)
CPU to CPU packets are fine between 4 units.
Here is what one looks like when CPU to CPU communication doesnt look good:
*** Error! should have 4 links, but 2: missing u1-u2, u2-u3, .
Link 1: u4 -- u1, num=1
1: 1/2/1 (T0) <---> 4/2/6 (T1)
Link 2: u4 -- u3, num=1
1: 3/2/6 (T1) <---> 4/2/1 (T0)
*** Error! no CPU to CPU: u1 -x- u2,
*** Error! only one directional CPU to CPU: u3 --> u1
*** Error! no CPU to CPU: u2 -x- u3,
*** Error! no CPU to CPU: u2 -x- u4,
*** Error! one directional CPU to CPU: u3 --> u4,
Make sure you check to verify what you think you have is correct.
Hi
ReplyDeleteWhat to do when you CPU to CPU communication doesn`t look good, like below:
*** Error! one directional CPU to CPU: u1 --> u6,
*** Error! one directional CPU to CPU: u1 --> u7,
*** Error! one directional CPU to CPU: u2 --> u7,
*** Error! only one directional CPU to CPU: u10 --> u5
*** Error! only one directional CPU to CPU: u9 --> u7
*** Error! one directional CPU to CPU: u7 --> u10,
*** Error! one directional CPU to CPU: u8 --> u10,
What model is this? A 6610?
Delete