Forum Discussion
VIPRION Network Failover
Currently, I have two chassis with one blade each. Network failover is made possible by a directly connecting 1/1.8 on each blade in each chassis to one another. I am currently using a unicast network failover address.
When adding additional blades, I am guessing that instead of cabling blades directly to each other, I should cable them all to a switch and place them on a common, isolated L2 VLAN; which would be used for network failover and configsync. Does this make sense?
Also, should I switch from a unicast network failover configuration to a multicast one? Support mentioned that I need to configure trunks per SOL13754, but I'm not sure if this means that I need to create one or two trunks (one per chassis)?
Any advice would be much appreciated.
Thanks.
- HamishCirrocumulusI always use a standalone switch (Or if possible a switch-stack) for the network failover (And heartbeats). I've never bothered with multicast for the HB's though... On a standalone switch with dedicated VLAN for that heartbeat traffic, I can't really see much advantage for the level of traffic I currently experience...
- Josh_41258NimbostratusThanks, this is exactly how I plan to proceed.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com