About Nik Noltenius

Nik Noltenius · 11-11-2025

Hi folks,we've setup inband management on our ACI lab enironment. All switches and APIC can ping each other just fine. Then we have an L3Out in the management Tenant to allow external devices to reach the fabric nodes via their inband management addr...

Nik Noltenius · 10-14-2025

Hi folks, first of all: We have already opened a TAC case, but I thought it cannot hurt to have several irons in the fire This is our situation: We have a Multi-Pod environment with 100 Gbps links from the Spines to the IPN and a full mesh of 400 Gbp...

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 · 11-12-2025

Hi @RedNectar,thanks for your reply You're absolutely right, I failed to provide all context.So, everything is in VRF inb ans yes, there are other solutions than using a contract but all lead to the same result. Setting the VRF to unenforced is basi...

Nik Noltenius · 10-20-2025

I'm happy to announce that we successfully upgraded our Spine to IPN bandwidth.We followed Balaji's suggestion to modify the ospf link cost on all interfaces. To be more precise we set the exact same ospf cost value for all links no matter the bandwi...

Nik Noltenius · 10-14-2025

Thank you for your input Julian,this could indeed lead to the behavior that we have and it's a totally new angle to look at the issue. Highly appreciated!However, I doubt that we have a problem processing IGMP joins. After all you can see that the co...

Nik Noltenius · 10-14-2025

Thanks again,yes, it seems like we need to be in the problem situation to fully understand the issue. Right now we are checking if a design with mismatched speed on the Spine uplinks is even "officially supported". On the next maintenance window we'l...

Nik Noltenius · 10-14-2025

Thanks again This is the (remaining) ospf config on the IPN: router ospf IPN auto-cost reference-bandwidth 400 Gbps vrf IPN router-id 123.123.123.1 log-adjacency-changes On the Spine side these screenshots should cover the configuration.Gener...

Member Since	‎05-07-2010 01:02 AM
Date Last Visited	‎11-12-2025 12:37 AM
Posts	137
Total Helpful Votes Received	90

User Statistics

User Activity

ACL_DROP on inband management

Extending Spine to IPN connections breaks inter-pod communication

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

Re: ACL_DROP on inband management

Re: Extending Spine to IPN connections breaks inter-pod communication

Re: Extending Spine to IPN connections breaks inter-pod communication

Re: Extending Spine to IPN connections breaks inter-pod communication

Re: Extending Spine to IPN connections breaks inter-pod communication