Hello,
I appear to have a strange issue, or a blunt misconfiguration somewhere.
We run a cluster of 2 * SRX240
Every connection to our switched platform is put in a separate redundancy-group, in order to cater for failover when a single switchport fails.
However, when I shut a switchport down on one of our ethernet-switches, the corresponding reth is showing down, allthough there are two member-interfaces configured to be in that reth and redundancy-group.
The redundancy-group will not failover, and the node where the interface is down, is still showing as primary.
When I do a manual failover to node1 (secondary in redundancy-group), all works wel, so there does not appear to be an issue on the switching platform behind it (mix of cisco 3750 and 4500)
Relevant configuration:
chassis {
cluster {
control-link-recovery;
reth-count 9;
<SNIP>
redundancy-group 7 {
node 0 priority 100;
node 1 priority 99;
}
}
}
ge-0/0/7 {
description "Trunk to DMZ's";
gigether-options {
redundant-parent reth7;
}
}
ge-5/0/7 {
description "Trunk to DMZ's";
gigether-options {
redundant-parent reth7;
}
}
reth7 {
vlan-tagging;
redundant-ether-options {
redundancy-group 7;
}
unit 200 {
description DMZ-WEB;
vlan-id 200;
family inet {
address 10.110.200.1/28;
}
}
}
}
reth7 is the only interface in redundancy-group 7 :
jbelles@blah-node0> show chassis cluster status
Cluster ID: 3
Node Priority Status Preempt Manual failover
Redundancy group: 0 , Failover count: 1
node0 100 primary no no
node1 99 secondary no no
<SNIP>
Redundancy group: 7 , Failover count: 5
node0 100 primary no no
node1 99 secondary no no
{primary:node0}
jbelles@blah-node0>
jbelles@blah-node0> show chassis cluster interfaces
Control link 0 name: fxp1
Control link status: Up
Fabric interfaces:
Name Child-interface Status
fab0 ge-0/0/2 up
fab0
fab1 ge-5/0/2 up
fab1
Fabric link status: Up
Redundant-ethernet Information:
Name Status Redundancy-group
reth0 Down Not configured
reth1 Down Not configured
reth2 Down Not configured
reth3 Up 3
reth4 Up 4
reth5 Up 5
reth6 Up 6
reth7 Down 7
reth8 Down Not configured
{primary:node0}
jbelles@blah-node0>
In the extensive interface output, you can see that obly one member is down:
jbelles@blah-node0> show interfaces reth7 extensive
Physical interface: reth7, Enabled, Physical link is Down
Interface index: 135, SNMP ifIndex: 513, Generation: 138
Link-level type: Ethernet, MTU: 1518, Speed: Unspecified, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Disabled, Minimum links needed: 1,
Minimum bandwidth needed: 0
Device flags : Present Running
Interface flags: Hardware-Down SNMP-Traps Internal: 0x0
Current address: 00:10:db:ff:30:07, Hardware address: 00:10:db:ff:30:07
Last flapped : 2012-01-27 02:13:05 HKT (00:40:22 ago)
Statistics last cleared: Never
Logical interface reth7.200 (Index 88) (SNMP ifIndex 569) (Generation 183)
Description: DMZ-WEB
Flags: Hardware-Down Device-Down SNMP-Traps 0x0 VLAN-Tag [ 0x8100.200 ] Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 146431 0 25580800 264
Output: 15740 0 2047979 0
Link:
ge-0/0/7.200 <-- down
Input : 303 0 27444 0
Output: 268 0 24828 0
ge-5/0/7.200
Input : 146128 0 25553356 264
Output: 15472 0 2023151 0
Logical interface reth7.32767 (Index 89) (SNMP ifIndex 570) (Generation 184)
Flags: Hardware-Down Device-Down SNMP-Traps 0x0 VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 0 0 0 0
Output: 0 0 0 0
Link:
ge-0/0/7.32767 <-- down
Input : 0 0 0 0
Output: 0 0 0 0
ge-5/0/7.32767
Input : 0 0 0 0
Output: 0 0 0 0
Any pointers?
regards,
Jeffrey