About Nik Noltenius

Nik Noltenius · 02-16-2024

Hello community,I apologize, it will be a rather long text, but I think I have to explain a lot and will still be missing half of the important information :SWe have a single-pod ACI fabric: The leaf switches on the lower end of the diagram connect ...

Nik Noltenius · 12-08-2020

Dear community, we have an ACI Multi-Pod environment with two Pods and one ESXi host connected to each of them. A static vPC is configured from the host to two leaf switches to provide failover redundancy: So far so good. If a leaf switch fails or a...

Nik Noltenius · 11-06-2020

Hi folks,I have a problem giving me sleepless nights.We have a Multi-Site environment with two fabrics. Both sites are connecting to perimeter firewalls via BGP, which are both active and provide the same prefixes. We deployed Intersite L3Out so that...

Nik Noltenius · 09-04-2020

Hello community, we have an ACI Multi-Pod fabric connected to a legacy environment:We have two L3Outs, all four leaf switches are configured in both of them.Each blue line is a physical connection transporting a green transfer VLAN for OSPF and a dif...

Nik Noltenius · 07-21-2020

Hello community, we have an NXOS device showing up in the discovery window of our ACI fabric (3.2(7f)).The device (n93180YC-EX) originally was running ACI code, however as it's used for IPN it was booted with an NXOS image. We even performed a SW-upg...

Nik Noltenius · 09-28-2022

Hello mgual, yes, after engaging TAC we found a solution. It turned out that using 0.0.0.0/0 with aggregate export subnet selected does not match any static routes. This seems to be a security mechanism to prevent BD routes (static pervasive routes) ...

Nik Noltenius · 12-09-2020

Hello Terry,thanks for your reply. While I agree that the IPN can be a tricky part I don't think it matters much in this case. Following the packets via ELAM we see that the ICMP request from VM_A to VM_B reaches it's destination and that the reply c...

Nik Noltenius · 11-10-2020

Hello Robert,thank you for your input.Regarding option C) you're correct. In this case I would have accepted, that all EPGs take their nearest exit and the HBRs would have been used to steer ingress traffic accordingly. Not achieving the original goa...

Nik Noltenius · 11-08-2020

Thank you Robert,I agree but I'm looking for alternatives still.There is one explanation and one real reason for the desired behavior. The explanation is that it has been done this way with the legacy network for years. In the legacy environment they...

Nik Noltenius · 11-08-2020

Thank you Chris,yes, Intersite is already configured. It was a prerequisite to be able to use the remote's L3Out to begin with. Unfortunately in this case it's rather part of the problem than of the solution. I read everything Multi-Site - and much m...

Member Since	‎05-07-2010 01:02 AM
Date Last Visited	‎10-08-2024 03:50 AM
Posts	129
Total Helpful Votes Received	90

User Statistics

User Activity

Floating L3Out - ECMP - eBGP to iBGP inside the fabric

ACI Multi-Pod - Traffic black-holing to leaf switch in maintenance mode (GIR)

ACI Intersite L3Out Egress Path Steering

ACI redistribution of static route into OSPF with two L3Outs on the same border leaf

NXOS switch showing up in ACI discovery

Re: ACI redistribution of static route into OSPF with two L3Outs on th

Re: ACI Multi-Pod - Traffic black-holing to leaf switch in maintenance mode (GIR)

Re: ACI Intersite L3Out Egress Path Steering

Re: ACI Intersite L3Out Egress Path Steering

Re: ACI Intersite L3Out Egress Path Steering