Skip to main content

Cisco SDA - Components


Cisco Software Defined Access is a new paradigm towards building Enterprise Networks. Primarily built upon the Cisco's DNA Center software, it leverages several next-generation components to design, provision and apply policy to create an intelligent wired and wireless network infrastructure.


Cisco DNA Assurance which turns the network devices into sensors, giving visibility to everything on the network; guided remediation which automates resolution to keep the network at its optimal performance and thereby improve the end user experience, are some of Cisco's USPs.


Cisco SDA accomplishes this intent based networking via the following components:

  1. Fabric Control Plane nodes: Based on LISP map-server and map-resolver functionality combined together on the same node, control plane node (database) tracks the endpoints in the fabric site and associates the endpoints to fabric nodes. Border nodes and edge nodes register with the control plane nodes.
    Control Plane node can be dedicated or can be co-located with border node (explained later).
  2. Edge Node: Equivalent of the access switches in a traditional campus LAN design. The edge nodes however implement a Layer 3 access design.
  3. Intermediate Node: These nodes are a part of Layer 3 network used for interconnections between edge nodes and border nodes. Analogous to the distribution switches in the traditional campus network design. Intermediate nodes route and transport IP traffic inside fabric.
  4. Border Node: The fabric nodes serve as a gateway between the SDA fabric and the networks external to the fabric. It serves as a common exit point from the fabric for access to the rest of the network (outside the SDA fabric) and Internet.
  5. Fabric Wireless LAN controllers: Apart from the normal non-fabric WLC functions such as access point image and configuration management, mobility etc., fabric WLCs provide services such as fabric integration -- Register MAC addresses of wireless clients into the host tracking database of the fabric control plane during new wireless client joins and providing fabric edge RLOC location updates for roaming clients.
  6. Fabric Access Points: Fabric mode APs are associated with fabric WLC (above) and have one or more fabric-configured SSIDs. Fabric APs must be directly connected to the fabric edge node switch to enable fabric registration, RLOC assignment via WLC etc. CDP runs between fabric APs and fabric edge nodes to apply special port configurations.
  7. Identity Services Engine: Cisco's famous NAC solution which integrates with Cisco DNA Center using Cisco's Platform Exchange Grid (pxGrid), to provide visibility for the users and the groups in a simple interface while also facilitating end to end security policy management.
  8. Cisco DNA Center: The Godfather that pulls all the strings and holds all the components together. The Cisco DNA Center software, including the SD-Access application package, is designed to run on the Cisco DNA Center Appliance.

Labels:

Comments

Post a Comment

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o
Post a Comment
Read more

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s
5 comments
Read more

Tejas Jain - GCP Constraints & Random Facts

1.  Google Cloud Interconnect Security Cloud Interconnect does not encrypt the connection between your on-premises network and Google's network. Cloud VPN cannot be used with Dedicated Interconnect For additional security, use application-level encryption or your own VPN 2. While using Cloud CDN, the default time-to-live (TTL) for content caching is 3600 seconds = 60 mins 3. Cloud NAT sends only the translation logs and error logs to Cloud Logging service. 4. GCP Dedicated Interconnect - On Premises network device requirements:     10-Gbps circuits, single mode fiber or 100-Gbps circuits, single mode fiber     IPv4 link local addressing     LACP, even if you are using single circuit     EBGP-4 with multi-hop     802.1Q VLANs 5. While using Cloud VPN, the recommended MTU to be configured on the peer VPN  gateway = 1460 bytes 6. Each instance must have at least one network interface. The maximum number of network instances per instance is 8, depending on the instance's machine
1 comment
Read more