Hi guys ... just for the record.
I've fixed the issue simply moving the cable of the backup interface to
another switch as suggested by the network guys of the DC. Which is even
preferable under the network redundancy perspective.
Now works perfectly and the failover NIC0-NIC1 and (NIC1-NIC0) is
i
I actually don't know Damien. I'll have to have a chat with the network
guy in the DC as I'm not managing the switch neither I have access to
it, plus I'm not really a Cisco guy so I'll forward those questions to
him.
Moreover I'm getting a bit lost with this.
If the ports are in trunk mode would
I confirm you should see fast transition for your VLANs to forwarding state.
Are your ports in access or trunk mode ?
If they're trunked, portfast alone won't do it, you need "spanning-tree
portfast trunk".
Additionally, are you using link aggregation on the cisco swi ?
(channel-group)
On 3/1
That's the STP configuration on my two switch ports:
spanning-tree portfast
spanning-tree bpduguard enable
On Fri, 2012-03-16 at 12:10 +0100, Damien Fleuriot wrote:
> You're not looking for FEC or ethechannel or 802.3ad at all.
>
> What you're looking for, in the case of a *failover* configu
I've requested the configuration. I'll post that as soon as I have it.
Thank you very much for your time.
On Fri, 2012-03-16 at 12:10 +0100, Damien Fleuriot wrote:
> You're not looking for FEC or ethechannel or 802.3ad at all.
>
> What you're looking for, in the case of a *failover* configuration
You're not looking for FEC or ethechannel or 802.3ad at all.
What you're looking for, in the case of a *failover* configuration, is a
"spanning-tree portfast" feature so that your port doesn't transition
through the different spantree states before forwarding traffic.
Kindly obtain the configurat
Hi Dweimer and Damien,
thanks for replying.
The server is connected to a switch of the datacentre. The configuration
of this switch is unknown to me and I obviously have no access to it but
I truly believe that such an enterprise environment has management
capabilities.
Anyway, in which way the co
Sorry top posting from phone.
Show your switch's port configurations.
We're using VLAN tagging over lagg failover interfaces at work and I have
already tried the tests you described, to much better results.
We're also running 8.2 so the only thing that seems to differ between us is the
switch
On 15.03.2012 14:06, Snoop wrote:
Hi there,
a while after setting up my new server (with 8 jails in it) I've
decided
(after postponing several times) to properly check the functionality
of
the lagg and the result was very disappointing.
The test I've done is very simple.
I've started copying
