Things change. Especially in the realm of infrastructure. We tend to continuously focus on optimizing and redesigning our networks to support the business goals. Or you might simple need to repurpose hardware. Whatever the reason might be we need to know the “how” and “what” of such changes. Take StackWise Virtual, for example. If we want to break up the StackWise Virtual switch pair, you can find this official documentation:

NIS 2 er et direktiv fra EU som har til formål at sikre et højt niveau af cybersikkerhed for alle medlemslandene. En disciplin, der sikrer, at samfundskritiske services som el, vand, varme, transport, medicin og fødevareproduktion (m.fl.) har styr på tingene, hvis uheldet er ude. Netop ordet “kritisk” er en betegnelse, der anvendes om de virksomheder (eller enheder, hvis man bruger NIS 2-sprog) som er væsentlige for vores samfund. Det er jo en rar ting, at man kan betale for sine madvarer, når man er ude at handle, så vi er fri for at plyndre bankerne som… nåh ja, alligevel ikke ligger inde med kontanter i dag.

Often times when I design secure infrastructure solutions, I find dependencies. Typically, we aim for independent solutions to ensure reliable and stable environments to keep our business running and customers happy. This is particularly important when working with critical infrastructure providers in the electricity, water, and heating sectors which we all rely on and depend upon ourselves. Island mode often refers to a state in which a system is disconnected from the Internet or the IT network, particularly from an OT perspective.

Fabric-based networks are no longer exclusive to the data center or service provider networks. Today we use fabric-based networks all over to provide the network services needed to support our business. I like to define a fabric-based network by two things: A network of devices (typically switches) that optimally inter-connect in a strict uniform way (think physical topology here) A robust network built to support L2 and L3 services on top of it using the concepts of underlay and overlays Roughly speaking the underlay is nothing but a L3 network responsible for providing reachability between the devices that hold our endpoints (be they users or servers).

It has become imperative to prioritize network design as part of a solid business strategy. This post zooms in on the workings of network design and what it’s all about. The goal is to broaden stakeholder’s perspective on the elements that are in play with network design. Network Design - Why Taking control of the network in a responsible way to keep things relevant and on track in accordance to the business requirements is key to being successful when it comes to network design.

This post delves into the pros and cons of another classical enterprise LAN design. Focus is on detailing why you might choose such a design and the workings of it. A few optimizations are shown, too. For Part I check out Classical Enterprise LAN Design - Part I Topology Below topology is the starting point. Some choices have been taken as described in the green boxes. SW1 and SW2 are distribution switches that mark the demarcation between L2/L3 from access to the rest of the network (core).

Many enterprises still have what is considered a classical network. This post deals with one such design. Focus is on highlighting the reasons why a network is built this way and reveal its shortcomings. Lastly some suggestions on how to optimize the logical design are shown. Topology Below topology is the starting point. Some choices have been taken as described in the green boxes. SW1 and SW2 function as the boundary between L2 and L3.

This post touches upon various approaches of designing an IP addressing plan for an enterprise network. It will also deal with segmentation in general, because IP addressing and segmentation are dependent on each other. IP Addressing A typical enterprise network consists of multiple sites of varying sizes that might span a wide geographical area - even international and/or inter-continental. A such we have different areas of network types that needs IP addresses.

Security is top of mind for most companies today. And for good reasons. Every day new major security incidents hit both the private and public sectors. We’re no longer dealing with curious geeks, script kiddies, and smaller groups of cyber criminals. Hacking used to be a niche thing. Today state-sponsored hackers are a reality. Although you cannot guarantee protection from these malicious events, you can try to limit the risk and possibility of their success.

DNAC is currently not designed to be VRF-aware with its Network Settings. The AAA server settings are configured with global context regardless of the device management IP being in a VRF. Here is what DNAC provisions for RADIUS: aaa new-model aaa authentication login default local aaa authentication login dnac-cts-list group dnac-client-radius-group local aaa authentication dot1x default group dnac-client-radius-group aaa authorization exec default local aaa authorization network default group dnac-client-radius-group aaa authorization network dnac-cts-list group dnac-client-radius-group aaa accounting Identity default start-stop group dnac-client-radius-group aaa accounting update newinfo periodic 2880 !