[MUSIC] You will explore the Aruba switching portfolio models, specifications and use cases. You will be able to describe the AOS-CX operating system connectivity, port numbers and navigating the command line interface or CLI. You will expand on this knowledge by understanding how to use basic CLI commands to gather system health, status and connectivity information, perform basic configuration and discover enough information to make detailed network documentation. You begin this module by understanding 2 tier in 3 tier network design models. This will give you a good network design and troubleshooting foundation on which to build. You begin this module by understanding of rubles portfolio switches. This will help you to select the proper device for a given scenario. Then you will learn how to use Aruba switches how to connect to them and use the CLI to glean basic network health and status information, perform basic configuration and discover how an unknown network is connected. This ability to document a network will serve you well when you must diagnose network outages. [MUSIC] Traditionally, the network switch had one job. Provide wired access to computing devices. These legacy switches had low port bandwidth utilization and minimum power requirements, each wired user connected to a separate switch port. Each port handled traffic from a single user. Today, the role the switch has dramatically changed. Many users prefer a wireless connection. They connect to APs, which in turn connect to switches. Thus the switch has become an aggregation device. Each port handles traffic for multiple endpoints. For many organizations, good wireless communication is mission critical, resilient, reliable and high performance aggregation must ensure the best mobile user experience. Also, there is an increasing number of internet of things or devices often deployed throughout the organization. To support these devices, switches must offer security authentication and services such as power over Ethernet or PoE, to the devices that requested. The power over Ethernet feature enables a switch to provide device power in addition to data connectivity. This eliminates the need to run separate power cables to every device and drastically reduces cost. However, this means that the switch must have enough power supplies to not only power itself. Put all the connected PoE devices. Aruba Networks has created a switching portfolio that meets today's requirements in terms of performance, security, manageability, automation and wireless optimization. The portfolio accommodates any organization, regardless of their size or complexity. To meet the objectives of modern network deployments, Aruba Networks has developed two network operating systems or NOSs. The Aruba OS-S and the Aruba OS-CX, this family switches offer excellent performance in campus lands offering layer 2 and layer 3 features the Aruba 25 30 series switches. These are fixed switches available in 8, 24 and 48 port models suitable for the access wire. They have typical layer 2 features, along with simplified QS and security features. This series supports 10, 100 megabits per second only ports and gigabit Ethernet ports with up to 4 SFP uplinks. Full P we support provides up to 370 watts to power access points. IB cameras, IoT devices and more, multiple authentication methods are available in this series. This includes a very robust added to 1X authentication and a simpler but less secure Mac authentication. Web based authentication is available for clients that do not support A2 to 1X. This enhances security. By controlling access to the network, this series can be integrated into the Aruba central cloud based management platform. This provides a simple, secure and cost effective way. Demanded switches anywhere at any time. 0 touch provisioning simplifies installation of the switch infrastructure in remote locations. Note. That SFP is a compact hot plug cable network interface module. They gives to switch the interface port to be equipped with the suitable type of transceiver that is needed. For example, some SFP interfaces could support copper media, while others may support multi mode or single mode fiber optic connections. The 25, 40 switches series. These are fixed switches available in 24 and 48 port models suitable for the access layer. This series differ from the 25, 30 because supports do not support 10, 100 megabit Ethernet. The minimal port rate is gigabit Ethernet. The uplink ports that connect the aggregation switches support 1 or 10 gigabit Ethernet. Full PoE plus support is included. This series supports the typical layer 2 protocols, plus basic layer 3 features such as rip rotting ACL's and robust QOS. Security is enhanced by authentication methods in access controless or ACLs, source. Port filtering can limit certain ports to communicate only with each other. Simple deployment with 0 touch provisioning is available, as is the automation of network operations, monitoring and troubleshooting. This is enabled using rest APIs, the Aruba 2930F switch series. These are fixed switches, which are available in 8, 24 and 48 port models suitable to be deployed in the access layer. This series uses gigabit Ethernet ports with 1 and 10 gigabit per second uplinks. Full POS, PoE plus support provides up to 740 watts of power. The 2930F series offers layer 3 capabilities, including OSPF dynamic segmentation, ACL's, IPV6 and robust QS. All without requiring an additional software license. This series also supports virtualized switching or stacking. When switches are stacked, they appear as a single chassis. To simplify management, up to eight members can be stacked in a ring topology. Zero-touch provisioning simplifies installation of the switching infrastructure using Aruba Activate or a DHCP-based process. Aruba Central Management is also available. Security is enhanced by running user authentication methods, ACLs, STP protection, and private VLANs. The Aruba 2930M switch series. This series is available in 24 and 48-port models, and has similar software capabilities to the Aruba 2930F switch series. The key difference is modularity. A modular switch allows you to choose the right module for the uplink ports, add a secondary power supply, user modular 10 or 40-gigabit Ethernet uplinks, and select models with Smart Rate ports. HPE Smart Rate multi-gigabit Ethernet delivers faster connectivity that a regular gigabit Ethernet port, along with POE, using existing campus cabling. Full POE+ is supported with the newer 802.3bt Class 6 cabling standard. This means that you can power devices that require up to 60 watts. A redundant power supply is available to provide up to 1,440 total watts of power. The Aruba 3810M switch series. These fixed switches are available in 16, 24, and 48-port models, with or without full POE+ and Smart Rate 2 ports. These Smart Rate ports can delivery high-speed rates and power for 802.11ax and 802.11ac devices, using existing Cat 5E and Cat 6 twisted pair wiring. The 3810 series supports typical layer two features and layer three features such as OSPF and BGP. They also support VRRP, as well as QoS and security features. The switch series supports virtualized switching or stacking, and an available slot accepts both 10 and 40-gigabit Ethernet modules. Stacking has designed for high performance, and provides up to 336 gigabits per second of stacking throughput. Using a ring topology, you can stack up to ten switches. In a mesh topology, the maximum is five. The Aruba 5400R ZL2 switch series. These modular switches are available in 6-slot or 12-slot chassis, can be deployed at the axis or core of a campus network, depending on the size of the network. The 5400R ZL2 support the most demanding network features, including QoS and security. Redundant management modules and redundant power supplies provide high availability for environments that cannot tolerate downtime. The switch supports any combination of 10, 100 megabits Ethernet, and 1, 40, and 10-gigabit Ethernet, with full POE+ on all ports. Smart Rate 2 ports are also supported. The 5400 ZL2 switches can run layer three features such as OSPF, BGP, VRRP, and PIM. They also support the Virtual Switching Framework feature, which enables you to combine two switches into one virtual switch, called a fabric. AOS-CX is a modern software system for the enterprise core and aggregation that automates and simplifies many complex and critical network tasks. It delivers enhanced fault tolerance, and facilitates zero service disruption during planned or unplanned control plan events. The key innovations in AOS-CX are its microservices-style modular architecture, REST APIs, Python scripting capabilities, and the Aruba Network Analytics Engine, or NAE. CX is based on modern architecture that allows individual processes to restart and be upgraded. Its REST APIs and Python scripting enables fine-grained programmability of the switch functions. And its unique Aruba Network Analytics Engine, or NAE, provides for easy network monitoring and troubleshooting. A data center is a facility that centralizes an organization's IT operations and equipment, as well as where it stores, manages, and disseminates its data. Data centers house a network's most critical systems, and are vital to the continuity of daily operations. The security and reliability of data centers and their information is a top priority for organizations. A data center architecture could include a three-tier layer approach, access, aggregation, and core layers, which help to create a resilient network. CX switches were designed to work in the campus LAN network, as well as in the data center, offering a rich set of features and high performance. Aruba 8400 switch series, the Aruba 8400 switch is suitable for deployments as a campus core switch, or as a core aggregation switch in the data center. This series switch been designed to provide high availability and resiliency in every part of the hardware, supporting 99.999% availability. These modular switches are available in eight-slot chassis for interface modules or line cards. Options for line cards include 32-port 10-gigabit Ethernet modules, 8-port 40-gigabit Ethernet, and 6-port 100-gigabit Ethernet modules. Fabric modules provide the ability for traffic to flow between the line cards. The 8400 switch supports up to three fabric modules, which provide redundancy and keep the line rates in case of a failure. The switch offers up to 19.2 terabits per second switching capacity. The 8400 series switch supports redundant management modules, fan assemblies, and power supplies. All modules are hot-swappable, permitting upgrade or replacement without powering off the chassis. These switches also include the Aruba Network Analytics Engine, or NAE, a framework for monitoring, troubleshooting, and capacity planning. Advanced layer two and layer three features include BGP, OSPF, VRRF, multicasting, and IPv6. Also, this switch supports VSX and multi-chassis link aggregation. OVSX legs, which enables you to create one virtualized switch composed by two individual physical switches. The Aruba 6400 switch series as a modern, flexible and intelligent family of modular switches, ideal for access, aggregation and core in an enterprise, campus land and data center deployments. The switches provide the foundation for high performance networks supporting IoT Mobile and Cloud applications. This switch series comes with high quality next generation Aruba Gen7A6 to support multi gigabit requirements, automation, security, high availability and peewee. All running on a next generation modular C X operating system. This switch series introduces the models 6405 which is a five slot chassis for line cards and a 6410 switch a 10 slot chassis. Both chassis models support up to two management modules, four modular AC power supplies and two or four fan trees. Depending on the line card used the 6400 series supports a variety of interfaces 1 gigabit, 10 gigabit 25 gigabit 40 gigabit 50 gigabit and 100 gigabit. This switch offers 24 terabytes per second switching capacity. The switches support BGP, EVPN, VX lan, VRFs and OSPF with robust security and QOS, high availability is accomplished with the VSX redundancy and redundant power supplies and fans. The Aruba 8325 switch series offers a flexible and innovative approach to addressing the application, security and scalability demands of the mobile cloud and IoT error. These switches serve the needs of the core and aggregation layers, as well as top of rack and end of row data center requirements. This switch provides over 6.4 terabytes per second switching capacity with line rate gigabit Ethernet interfaces, including 1, 10, 25, 40 and 100 gigabits per second. This one rack unit switch supports advanced layer two and three features that include BGP, OSPF, VRFs and IPV6. Dynamic VX land with BGP, EVPN for deep segmentation and data center and campus networks. This switch series offers two models with the 48 32 ports. Both models include six fans and two power supplies. Also, each switch model offers a choice to select the airflow, either front to back or back to front. The Aruba 8320 switches are powerful one rack unit devices designed to provide core and aggregation services in mid sized campus networks. These switches offer three fixed port models with 10 and 40 gigabit interfaces, which offers up to 2.5 terabytes per second switching capacity. This model offers similar features as the 8325 Switches series, which include BGP SPF, VRF, IPV6, VSX and multi chassis link aggregation. The 8320 switches are also built for resiliency. They offer redundant power supplies and fans. The Aruba CX 6300 switch series is a modern, flexible and intelligent family of stackable switches, ideal for enterprise access and aggregation layers. This switch series is built around the new Aruba Gen7 asic, highly capable CPU and the next generation modular CX switch software platform. The Aruba Virtual Stacking Framework, or VSF, allows for stacking of up to 10 switches, providing scale and simplified management. This flexible series has a built in 1, 10, 25 and 50 gigabit ethernet uplinks and support high density, high power peewee interface is offering up to 880 gigabits per second system switching capacity. This series supports one touched of deployment with the Aruba CX mobile App. Aruba dynamic segmentation extends Aruba's foundational wireless role based policy capability to Aruba Wired switches. What this means is that the same security user experience and simplifying IT management can be enjoyed throughout the network, regardless of how users and IoT devices connect. Consistent policies are enforced across wired and wireless networks, keeping traffic secure and separate. The Aruba C X 6200 switch series is a modern, flexible and intelligent family of stackable switches ideal for enterprise access layer. This switch series is built around the new Aruba Gen 7A sic highly capable CPU in the next generation modular CX switch software platform. The Aruba Virtual switching or stacking framework BSF allows for stacking of up to eight member switches providing scale and simplified management. This flexibility series has built in one gigabit and 10 gigabit uplinks. And supports high density high power pewee interfaces offering up to 176 gigabits per second system switching capacity. This series supports one touch deployment with the Aruba CX mobile app. Aruba dynamic segmentation extends Aruba's foundational wireless role based policy capability to Aruba Wired switches. What this means is that the same security user experience and simplified IT management can be enjoyed throughout the network. Regardless of how users and IoT devices connect consistent policies are enforced across wired and wireless networks, keeping traffic secure and separate. The AO-SX software is a modern, database driven operating system that automates and simplifies many critical and complex network tasks. The built in time series database enables customers and developers to use software scripts for historical troubleshooting and analyze past trends. This helps to predict and avoid future problems due to scale, security and performance. This network operating system is built on a modular Lennox architecture with a state full database, which helps to offer the following unique capabilities. Easy access to all network state information, allowing unique visibility and analytics. Restful APIs and python scripting for fine grained program, ability of network tasks A microservices architecture that enables full integration with other ORC flow systems and services. Continual state synchronization that provides superior fault tolerance and IA availability. And last, security best practices were applied to completely create a trusted platform. The Aruba Network Analytics engine, or NAE, is a built in framework for network assurance and remediation, combining the full automation and deep visibility capabilities of the AOS-CX. This framework allows monitoring, troubleshooting, and easy network data collection using simple scripting agents. This framework analyzes a problem in real time, giving you the insight that you need to resolve the issue or take corrective action based on established policies. When an anomaly is detected, it can proactively collect additional statistics and data. AOS-CX has the following feature sets. For layer 2 switching VLAN support and tagging for 802.1Q, jumbo packet support, VX LAN Encapsulation Protocol, RSTP RPVST+, MSTP, IGMP and port mirroring. Layer 3 routing features include BFD, BGP, ECMP, multi-protocol VGP, OSPF, static routing, policy-based routing, IP performance optimization, IPv6 capabilities and PIM. Security features include ACLs for both IPv4 and IPv6 and Ethernet. RADIUS and TACACS+, control plane policing, authentication based on a 802.1X, MAC and web-based portal, DHCP protection, secure encryption for all access methods, including ssh, SSL and SNMP version 3. Switch CPU protection and identity driven ACLs. High availability and resiliency features include VRP, UDLD, LACP and VSX. Quality service features include strict priority queuing DWRR, traffic prioritization with 802.1p, layer 4 prioritization based on TCP and UDP port numbers, COS, rate limiting, unknown unicast rate limiting, large buffers for graceful congestion management. Note that the features listed do not apply to all switch models, necessarily. Please refer to the specific data sheet for each model to verify if the feature is supported. The CXF for fundamentals course covers the items listed in a bold font. Also, this text considers the feature set for CX 10.4 release. [MUSIC] What are some of the advantages of a modular chassis-based switch? They are more scalable, and they are more flexible. [MUSIC] When you initially configure a switch, you will typically use the out of band management on a console port. This special console port is integrated on all switch models and types to facilitate configuration, troubleshooting and management. Depending on the switch model, the console can be a USB-C port or an RJ-45 port. However, for both port types, you must establish a serial connection between the management station, perhaps your laptop, and the switch. To do this, you need the following items. If the switch has an RJ 45 port, then you'll use the serial cable, which is shipped with the switch. A USB to serial converter, which most modern laptops no longer include the serial port, so you must connect the console port, to a USB port on your laptop or desktop. Then you'll need software on your laptop or management station that emulates the serial session. Some common examples include Putty, Terraterm and secure CRT. If the switch has a USB-C port, then you'll need a USB-C cable. You also need the appropriate software on your management station. Also, the serial session must be configured with the following parameters. A baud rate of 115,200, data bits of eight, parity of none. Stop bits of 1 and no flow control. AOS-CX references interfaces using the member slot port notation. Remember, when Aruba Virtual Switching framework or VSF, or virtual switching extension VSX features are running multiple switches. This can be seen as one virtual switch, where this number indicates the member ID in the cluster. By default, an AOS-CX swhich will be member number one, indicating that these features are not running. The slot. In modular switches like the 8400 and 6400, this number represents the slot being used by a particular line card. For six fixed switches like the 8320 to 8325, 6300 and 6200, this number will always be 1. The port, this number references to the individual interface in the line card for modular switches or in the chassis fixed switches. The image shows an example with a fixed switch and a modular switch with VSX enabled. Note that VSF is available for the 6200 and 6300 series switches, while VSX is supported on the other platforms. You'll learn more about the VSF technology later in this course, AOS-CX is organized in a different configuration context or levels. Each context determines which parts of the switch can be managed, and which commands are available to users with the appropriate authority. The operating system defines the following contexts. The operator context enables you to execute commands to view but not change the configuration. This context requires the least user privilege to execute commands. when an operator context the CLI prompt is the switch name followed by a greater than sign the manager context. This is where you execute commands that do not require saving changes to the configuration in command descriptions. This context is listed as the name of the switch, followed by a hashtag to navigate to the manager context. Started the operator context, then enter the enable command as shown in the slide. You most likely have the administrative authority to enter the enable command the global configuration context. This is where you execute commands that changes switch configuration. To access this mode, start in manager mode, then enter the command configure terminal or shorten it to just the config command. To move back one level from this or any context, use the exit command. Other configuration commands context. Other configuration command context are descendants of the global configuration command context. From these command context, you can execute commands that apply to specific configuration or protocols, such as an interface or villain or routing protocol. Some examples include the interface, the routing into VLAN context to return back to manager context from any child or descendant context. Enter the in command the AOS-CX provides you with built in help features, for example, to show the available commands that you can execute in the current command context. Enter the question mark. This is shown in an example on the slide the question mark itself does not display on the screen when you enter it. To show the available parameters for command, enter the command followed by space, and then enter the question mark. This is shown on the bottom of the slide. Please notice that after the displays the information it automatically displays the text you entered before without including to help symbol itself. AOS CX supports both command abbreviation and command completion to save time by only typing an abbreviated version of the full syntax, enter enough letters to new uniquely specify a valid command and the only accepts the command. For example, you can enter con CON instead of configure to navigate from the manager context to the global configuration context. Command completion means that if you enter part of the command word and then press the tab key, one of the following will occur if you enter enough letters to match a valid command. The CLI displays the remainder of the word. If you have not entered enough letters to match a valid command, the CLI does not complete the command. For example, if you type an EMT, I n t then press the tab key. You see the word interface appear. If you press the tab key twice after a completed word, the CLI displays the command options. For example, if you type an interface and press the tab key twice, you'll see the words lag. Loopback management tunnel villain and V X lam as your options. [MUSIC] What kind of cables might you use to connect to an AOS CX switch console, port USB cable and serial cable. [MUSIC] In this section, you will learn about basic commands that will help you to verify your networking equipment along with his general capabilities. This is some of the most valuable information you can learn during entry level networking course. Good network engineers and administrators must be adept at discovering the actual connectivity of the network. This will help you to verify the accuracy of existing documentation or to create new network documentation from scratch. These show commands are valuable for baselining and troubleshooting. Using these commands, you can view many switch performance and health parameters, including CPU and memory utilization. Suppose that your network is healthy, everyone is happy, and all your switches are generally about 5% CPU utilization. You have been paying attention to this for months. Now you know your network. During an outage or slow down, you find a switch this running at 85% utilization. You might focus your diagnostic efforts on that switch, and it's directly attached devices because you paid attention. While the network is healthy, you are more efficient when a network is not healthy. If you had not paid attention, you would have no idea whether 85% utilization is normal or abnormal. Of course, Aruba has very effective management platforms that ease and automate these baseline processes, but it can still be valuable to use the CLI, the check network device, health and status. Mastering the commands that you're about to learn, creating good documentation and having good baseline information. It's kind of like getting the answers to a test before you take the actual test. Only this is a real world, and the test relates to how effective you are when the network is down. The show version command displays version information about the network operating system, software service, operating system software and a BIOS in a slide. You see that this system is running the AOS CX version. GL.10.4.0003 near the bottom. You see the service OS and BIOS versions. This is useful for your general knowledge and to help determine if upgrades are needed. The show system command displays a general status information about the system during road access, the device platform and version information may not be obvious. An example shown you're attached to a device name switch and Aruba model 83 25 48 YC. This is 48 25 gave it per second ports in 8 100 gigabit per second ports. You see the serial number, base Mac address and up time, as well as the CPU and memory utilization. This can give you some idea of the general health of system by baseline. In these parameters, you can begin to establish what normal is for your network. The show running config command displays the current non default configuration currently running on the switch. No user information is displayed The top CPU command shows detailed CPU utilization information. You learn how to see high level CPU utilization with the command show system, the top CPU command provides more detailed information. The show events command displays the event logs generated by the switch modules since the last reboot. Log analysis is a powerful tool to investigate and troubleshoot system and protocol related problems. Use the dash r parameter to list the most recent long events first, the show event command has other parameters that you can use. You can learn more about these parameters and the command line Interface guide for the AOS-CX documentation. The show interface brief command helps the administrator to see what the available interfaces and the current status is of them are. This command also briefly shows layer two and layer three configuration applied to the interface. This is a frequently used command for many network engineers. At a glance, you can tell the status of every interface on the entire device, with a specific focus on the enabled and status columns. Yes, under enabled means that the interface is not disabled into switch configuration. No administrator has disabled the interface, up in the status column means that something is attached to the interface. There's a at least a good layer, one layer, layer two connection between them. [MUSIC] Which command would use to validate network connectivity for an AOS-CX switch? Show interface brief. [MUSIC] You should name each network device, this ensures that you can easily identify them, especially in large networks. In real environment, this is one of the first configuration steps that you will do. Many corporations have documented standardized naming conventions. For example, one standard might be the building floor rack name. So the switches in rack two of the second floor of building nine might be named nine dash two dash two underscore SWA SWB SWC and so on. The slide shows how to name devices using the host name command. In AOS-CX all ports are disabled by default, however, you can modify the state using the no shutdown command as shown in this slot. To enable an interface, use the no shutdown command, to disable an interface, enter the interface context and use the shutdown command. A description can be configured for each interface, which facilitates management. The show interface command shows the status and configuration for all interfaces on the switch. And the figures top example administratively down means that a shutdown command was configured on that interface. You can also see that an interface description was configured on that interface with the description command. At the bottom of the example, notice that the interface is now up. Somebody has entered the no shutdown command, interface description remains unmodified. Power over Ethernet or POE, is a feature implemented on network devices such as layer two and multi layer switches. This provides power to endpoints using an Ethernet cable. This feature eliminates the need of external power sources, saving expenses of materials and installation time. POE uses twisted pairs of a UTP cable to send power to POE enabled devices. The first POE standard uses two twisted pairs to transmit data, while the other two were used for power transmission. With the new POE standards power and data are sent over the four twisted pairs. If you're thinking, how is that possible, the answer is that power and data use different frequencies. Electricity uses low frequency 60 hertz or less, and data uses a higher frequency or frequencies 10 to 100 megahertz. The Standard considers two types of devices, power devices or PDs, or devices that receive PoE power. While power sourcing equipment or PSE provides the power, typical PDs, or access points IP phones, cameras and some IoT devices. On the other hand, network switches are considered PSEs. The table displays of four different standards that are available in the industry. AOS-CX supports all the standards, the PSEs and PDs can negotiate the power. That PDS require more precisely using the LLDP protocol and the messages exchanged between the PD and PSE. [MUSIC] Which of the following options below accurately describes the network discovery commands or techniques. LLDP is a layer two discovery protocol, the ping command leverages ICMP echo requests and echo replies. [MUSIC] The AOS-CX modular switch series, which includes this 6400 and 8400. Their hardware architecture includes three major components management modules, fabric modules and line cards. The management modules has two main purposes, first, it runs the management plane for monitoring and configuration services. The management module also runs the control plane, which defines what to do with the incoming information by running protocols and algorithms. Fabric modules, this component helps to interconnect the multiple line cards that can be installed in the switch. A fabric card folds data between the ingress line cards and egress line cards. The device makes decisions based on information derived from data packets, and so is considered part of the data or forwarding plane. The line cards component works on the forwarding plane. It decides where traffic should be sent, data that must be forwarded to another port on the same line card uses an internal process within that line card. Traffic that must be sent to a different line card is sent via the fabric module. Which selects the appropriate or proper destination fabric card. The diagram simplifies the components in the communication paths between them. The AOS-CX software is a modern, database driven operating system, that automates and simplifies many critical and complex network tests. A built in time series database enables customers and developers to use software scripts for historical troubleshooting and analyze past trends. This helps to protect and avoid future problems to the scale, security, and performance. This network operating system is built on a modular Linux architecture with a staple database, which helps to offer the following unique capabilities. Easy access to all network state information, allowing unique visibility and analytics. RESTful APIs and python scripting for fine grained programmability of network tests. A micro-services architecture that enables full integration with other workflow systems and services. Continual state synchronization that provides superior fault tolerance and high availability. Security practices were applied to completely create a trusted platform. The current state database is the most important aspect of the AOS-CX software architecture. All software processes communicate with the database rather than with each other. This model ensures near real time state and resiliency. Using the current state database, you can upgrade software modules independently. The figure shows how processes like the history database or protocols interact directly with the database and not between each other. This streamlined approach allows all processes to use only one language to talk to the databases. Without this model, direct inter-process communication would be less efficient, wasting CPU resources. The database also maintains a current configuration, status of all the features, and statistics. The unified database ensures that all information is visible in a single place. Thus interaction is accomplished through a single open API. The diagram also shows how the active management module can synchronize information to the standby management module. This ensures a fault tolerant system that reduces downtime. Network protocols do not have to wait and re-converge. NAE is made up of agents, rules, databases, APIs, and a Web user interface, as shown in the figure. NAE agents, these are built into NAE and make use of agents to collect context information. Agents are scripts triggered in the device when a specific event occurs. Then it collects additional interesting and relevant network information. NAE rules, agents are triggered by user-defined rules. For example, you can create a rule to collect information when a CPU utilization exceeds a certain threshold for a specified period of time. The configuration of state databases. This database enables NAE's direct access to the current configuration and switch operational states. Data retreat from this database can be used to analyze trends and predict future capacity requirements. The time series database. This database gives users the ability to rewind and play back the network context surrounding a network event. Under normal use storage is estimated at 400 days. The RESTful APIs. This communication method enables integration with external systems such as SIEM tools in log analytic engines. Also, operators can use the APIs to request information from other devices in the network. This helps to create a complete picture of the network state when a specific event occurs. The Web user interface. This lets you access, view, and configure any scripts, agents, and alerts. Automatically generated grass provide additional context, which are useful for troubleshooting network issues. The top memory command shows memory utilization information. The show interfaces transceiver detail command, lists the transceivers installed in the switch. >> [APPLAUSE] >> You begin this module by exploring the networking devices used to build a typical network. This knowledge can help you to design, implement, and troubleshoot networks. You learned about important network services that are vital for proper network functions and end user interactions. Along with exploring two tier and three tier network design models, you reviewed Aruba's portfolio switches to help ensure that you can select the proper device for a given scenario. Then you learn how to use Aruba switches, how to connect to them and use the CLI to glean basic network health and status information, perform basic configurations, and discover how an unknown network is connected. This ability to document a network will serve you well when you must diagnose network outages.
