You said you reused the ip address:
> .2 and .3 with .1 as an hsrp ip
> The new nexus equipment is configured as .5 and .6 with .2 as an hsrp ip
It happens sometimes that the old MACs get stuck on the end-hosts.
Coupled with the F5 using SVI mac instead of the virtual IP MAC this can cause
so
Hi Waris et al.
Are there any plans to move service-policy configuration from channel-group
member ports to port-channel interface please?
On a physical port you can configure service-policy under the service instance
Ethernet.
However on a port-channel interface you can't configure service-p
On Monday, March 03, 2014 02:02:34 PM Vitkovský Adam wrote:
> Hi Waris et al.
> Are there any plans to move service-policy configuration
> from channel-group member ports to port-channel
> interface please?
>
> On a physical port you can configure service-policy under
> the service instance Ether
Tarko,
thank you very much for all the information!
regards,
Martin
On Sun, Mar 2, 2014 at 8:43 PM, Tarko Tikan wrote:
> hey,
>
>
> so even once Huawei releases its GPON ONT in SFP form-factor which is
>> compatible with their GPON OLT in OMCI protocol wise, it wont help as
>> long as serv
Hi,
> Hi,
>
> I have ip dhcp snooping and ip arp inspection enabled:
>
>
> ip arp inspection vlan 311-314
> ip arp inspection validate src-mac dst-mac ip
> ip dhcp snooping vlan 311-314
> ip dhcp snooping
>
> This appears to enforce that, if you are on one of those vlans and
> you don't have a dh
Dimitris,
thank you for confirming this. I managed to find two Cisco routers
supporting BFD in "echo mode" and connected those two directly with each
other:
R1#sh bfd neighbors details
OurAddr NeighAddr LD/RD RH/RS Holddown(mult) State Int
10.10.10.110.10.10.2 1/12Up
Just an update. Working with Cisco, we confirmed that the F5 was directing
traffic for the HSRP VIP to the MAC address of the SVI. We implemented
peer-gateway and this resolved the issue.
Thanks to all for their suggestion, on and off list,
Blake
-Original Message-
From: Vitkovský Ada
We have some 3560G switches whose control-plane is useless because the
switch punts ~2200 pps via the "sw forwarding" CPU queue. Investigating
shows that it's caused to IPv6 traffic. The switch itself is stricly
layer-2, is using the "desktop default" SDM template and has no IPv6
features (like MLD
On 03/03/2014 19:38, Peter Rathlev wrote:
layer-2, is using the "desktop default" SDM template and has no IPv6
features (like MLD snooping) configured.
Are you absolutely sure about this? Isn't MLD snooping on by default?
They are multicast listener reports, and there are far far too many of
On 03/03/2014 19:50, Phil Mayers wrote:
On 03/03/2014 19:38, Peter Rathlev wrote:
layer-2, is using the "desktop default" SDM template and has no IPv6
features (like MLD snooping) configured.
Are you absolutely sure about this? Isn't MLD snooping on by default?
No wait I'm talking rubbish.
On Mon, 2014-03-03 at 19:50 +, Phil Mayers wrote:
> I wonder if it's the same thing we (and others) saw:
>
> http://lists.cluenet.de/pipermail/ipv6-ops/2014-February/009835.html
It sounds very much like it, now that you say it. The part about two of
these goading each other turned out true; I
11 matches
Mail list logo
