Troubleshooting networks is challenging in the best of times, but trying to do so manually, one node at a time, and digging through a series of long and ugly logs make the job harder than it needs to be. NetQ provides rolled up and correlated network status on a regular basis, enabling you to get down to the root of the problem quickly, whether it occurred recently or over a week ago. The graphical user interface makes this possible visually to speed the analysis.
make the cut 4.1.0 210
In either in-band or out-of-band deployments, NetQ offers networkwide configuration and device management, proactive monitoring capabilities, and performance diagnostics for complete management of your network. Each component of the solution provides a critical element to make this possible.
The NetQ graphical user interface (UI) enables you to access NetQ capabilities through a web browser as opposed to through a terminal window using the Command Line Interface (CLI). Visual representations of the health of the network, inventory, and system events make it easy to both find faults and misconfigurations, and to fix them.
Cards present information about your network for monitoring and troubleshooting. This is where you can expect to spend most of your time. Each card describes a particular aspect of the network. Cards are available in multiple sizes, from small to full screen. The level of the content on a card varies in accordance with the size of the card, with the highest level of information on the smallest card to the most detailed information on the full-screen view. Cards are collected onto a workbench where you see all of the data relevant to a task or set of tasks. You can add and remove cards from a workbench, move between cards and card sizes, and make copies of cards to show different levels of data at the same time. For details about working with cards, refer to Access Data with Cards.
Cards present information about your network for monitoring and troubleshooting. This is where you can expect to spend most of your time. Each card describes a particular aspect of the network. Cards are available in multiple sizes, from small to full screen. The level of the content on a card varies with the size of the card, with the highest level of information on the smallest card to the most detailed information on the full-screen card. Cards are collected onto a workbench where you see all the data relevant to a task or set of tasks. You can add and remove cards from a workbench, move between cards and card sizes, change the time period of the data shown on a card, and make copies of cards to show different levels of data at the same time.
Medium cards are most effective at providing the key measurements for a given aspect of your network. They are commonly comprised of an icon to identify the aspect being monitored, one or more key measurements that make up the overall performance. Often additional information is also included, such as related events or components. Some examples include a Devices Inventory card, a Switch Inventory card, an Alarm Events card, an Info Events card, and a Network Health card, as shown here. Compare these with their related small- and large-sized cards.
If you are installing NetQ Platform software for a NetQ On-premises Appliance, select NetQ SW 4.1 Appliance to download the NetQ-4.1.0.tgz file. If you are upgrading NetQ software for a NetQ Cloud Appliance, select NetQ SW 4.1 Appliance Cloud to download the NetQ-4.1.0-opta.tgz file.
Verify that the needed files are present and of the correct release. This example shows on-premises files. The only difference for cloud files is that it should list NetQ-4.1.0-opta.tgz instead of NetQ-4.1.0.tgz.
For CentOS and Ubuntu, make sure you are running lldpd, not lldpad. CentOS and Ubuntu do not include lldpd by default, even though the installation requires it. In addition, CentOS does not include wget, even though the installation requires it.
You should see version 4.1.0 and update 36 in the results. For example:Cumulus Linux 3.3.2-3.7.x
netq-apps_4.1.0-cl3u361621595386.3030ea9_armel.deb
netq-apps_4.1.0-cl3u361621860085.c5a5d7e_amd64.deb
Cumulus Linux 4.0.0 and later
netq-apps_4.1.0-cl4u361621595395.3030ea91_armel.deb
netq-apps_4.1.0-cl4u361621860147.c5a5d7e2_amd64.deb
If you are upgrading NetQ Platform software for a NetQ On-premises Appliance or VM, select NetQ SW 4.1 Appliance to download the NetQ-4.1.0.tgz file. If you are upgrading NetQ software for a NetQ Cloud Appliance or VM, select NetQ SW 4.1 Appliance Cloud to download the NetQ-4.1.0-opta.tgz file.
You should see version 4.1.0 and update 36 in the results. For example:Cumulus Linux 3.3.2-3.7.x
netq-agent_4.1.0-cl3u361638992139.2c18daee_armel.deb
netq-agent_4.1.0-cl3u361638992139.2c18daee_amd64.deb
Cumulus Linux 4.0.0 and later
netq-agent_4.1.0-cl4u361638992139.2c18daee_armel.deb
netq-agent_4.1.0-cl4u361638992139.2c18daee_amd64.deb
The lifecycle management (LCM) feature enables you to upgrade to NetQ 4.1.0 on switches with an existing NetQ Agent 2.4.x-3.2.1 release using the NetQ UI. You can upgrade only the NetQ Agent or upgrade both the NetQ Agent and the NetQ CLI at the same time. You can run up to five jobs simultaneously; however, a given switch can only appear in one running job at a time.
While not typically an issue, you can restrict the NetQ Agent from using more than a configurable amount of the CPU resources. This setting requires Cumulus Linux versions 3.6.x, 3.7.x or 4.1.0 or later to be running on the switch.
4.1.0 Customers should contact Garmin or a Garmin and NMEA or ABYC certified entity within 30 days of a product failure for warranty service. All customers and/or Garmin and NMEA or ABYC certified entities are required to perform standard troubleshooting fault tests to determine whether onboard warranty service is appropriate. After standard troubleshooting fault tests have been performed, a RMA number will then be given. This RMA number is to be marked in plain view on the package being shipped to Garmin for the warranty service. This RMA number will act as a reference number for all parties involved. Technical assistance and request for an RMA can be made by contacting Garmin product support directly at:
When starting Cumulus Linux for the first time, the management port makes a DHCPv4 request. To determine the IP address of the switch, you can cross reference the MAC address of the switch with your DHCP server. The MAC address is typically located on the side of the switch or on the box in which the unit ships.
Installing a disk image is recommended if you are performing a rolling upgrade in a production environment and if are using up-to-date and comprehensive automation scripts. This upgrade method enables you to choose the exact release to which you want to upgrade and is the only method available to upgrade your switch to a new release train (for example, from 3.7.12 to 4.1.0).
The following script segment demonstrates how to check which Cumulus Linux release is running currently and upgrades the node if the release is not the target release. If the release is the target release, normal ZTP tasks execute. This script calls the ping_until_reachable script (described above) to make sure the server holding the image server and the ZTP script is reachable.
Errors in syslog for ZTP like those shown above often occur if the script is created (or edited as some point) on a Windows machine. Check to make sure that the \r\n characters are not present in the end-of-line encodings.
The tacplus-auth command handles the per-command authorization. To make this an enforced authorization, you must change the TACACS+ login to use a restricted shell, with a very limited executable search path. Otherwise, the user can bypass the authorization. The tacplus-restrict utility simplifies the setup of the restricted environment. The example below initializes the environment for the tacacs0 user account. This is the account used for TACACS+ users at privilege level 0.
The configuration file includes the mapped_priv_user field that sets the account used for privileged RADIUS users and the priv-lvl field that sets the minimum value for the privilege level to be considered a privileged login (the default value is 15). If you edit these fields, make sure the values match those set in the /etc/nss_mapuser.conf file.
ebtable rules are put into either the IPv4 or IPv6 memory space depending on whether the rule utilizes IPv4 or IPv6 to make a decision. Layer 2-only rules that match the MAC address are put into the IPv4 memory space.
You can add any valid command in the sequence to bring an interface upor down; however, limit the scope to network-related commands associatedwith the particular interface. For example, it does not make sense toinstall a Debian package on ifup of swp1, even though it istechnically possible. See man interfaces for more details.
Even though ifupdown2 supports the inclusion of multiple iface stanzas for the same interface, use a single iface stanza for each interface. If you must specify more than one iface stanza; for example, if the configuration for a single interface comes from many places, like a template or a sourced file, make sure the stanzas do not specify the same interface attributes. Otherwise, unexpected behavior can result.
The /usr/lib/python2.7/dist-packages/cumulus/__chip_config/[bcmmlx]/datapath.conf assigns buffer space and egress queues. The default thresholds defined in the datapath.conf file are intended for data center environments, but certain workloads may require additional tuning. It is best to make small, incremental changes to validate the changes with your application performance. Be sure to backup the original file before making changes. 2ff7e9595c
Comments