Application-layer management protocol used for monitoring and administration. SNMP operates by sending information to Network Management Servers (NMS). The NMS learns about problems in the network by receiving traps or inform messages generated by the individual device running SNMP or what is more commonly called the managed device. SNMP Operations – Agents listen to UDP port 161 for messages sent by the NMS – Responses are sent back to the originating NMS port from a dynamic port. Many agents use port 161 also for this target – Traps are received on port 162 of a NMS The first two variants of SNMP have pretty much the same protocol structure. (V3 is shown below.) This means that each of them will encapsulate the same general message format into a UDP packet. This message will be similar to this: SNMP Message Sequence Diag SNMP Message Diagram Shark Capture showing Version, String and PDU SNMP Version field will be an integer value and it should be noted that both the NMS and the agent must agree on the version of SNMP being used to communicate. SNMP community string is best described as a string value used for the password check for the NMS before the managed device will allow it to access or manipulate the agent process. SNMP Protocol Data Unit (PDU). The actual communication of information in the SNMP Protocol is performed through the exchange of SNMP messages. These messages are sometimes called protocol data units or PDUs. The PDU is the higher-layer data that SNMP encapsulates; The values applied to this field represent various PDU types and formats. See SNMP Versions for SNMP PDUs […]
Filtering Routes on IOS
Route filtering with RIP & RIPNG– Passive interface (passive-interface)– Distribute-list (distribute-list 2 [in|out])– Offset list (offset-list)– Administrative distance (distance) Route filtering with EIGRP & EIGRP V6– Passive interface (passive-interface)– Distribute-list [in|out] – IPV4 ACLs only– Prefix-list (prefix prefix-list-name[in|out])– Route-map (route-map map-tag [permit|deny] [sequence-number])– Administrative distance (distance) Route filtering with OSPF– Stub area (area stub & area nssa)– LSA Type 3 filtering (area filter-list) – IPV4 only– Summarization (area range/summary address [not-advertise])– Redistribution (redistribute protocol route-map) Route filtering with BGP & BGP for IPV6– Prefix list (neighbor prefix list [in|out])– Distribute list (neighbor distribute list [in|out])– Filter list (neighbor filter list [in|out])– Route maps (neighbor route-map [in|out]) Regex characters on IOS“.” – match any character“|” – concatenates constructs. matches one of the characters or character patterns on either side of the vertical bar.“[]” – matches the character following the backslash“[0-9]” – match any single digit“[a-z]” – match any lower case“[A-Z] – match any upper case“_” – replaces a long regular expression list by matching a comma (,), left brace ({), right brace (}), the beginning of the input string, the end of the input string, a space or the end of an AS Path.“^” – match the beginning of a string.“$” – match the end of a string“\” – matches the character following the backslash and also escapes special characters. Regex Occurrence Modifiers on IOS“?” – means 0 or 1 times. matches zero or one occurrence of the pattern“*” – mean 0 or any times. matches zero or one occurrence of the pattern“+” – means 1 or any times. matches zero or one occurrence of the pattern Source:IP Expert VODCisco Doc: Additional and Legacy Protocols/Terminal Services Configuration Guide, Cisco IOS Release
Switching To Ubuntu
Table of Equivalent Commands Below is a table of equivalent commands for package management on both Ubuntu/Debian and Red Hat/Fedora systems. Task Red Hat/Fedora Ubuntu Adding, Removing and Upgrading Packages Refresh list of available packages Yum refreshes each time it’s used apt-get update Install a package from a repository yum install package_name apt-get install package_name Install a package file yum install package.rpm rpm -i package.rpm dpkg –install package.deb Remove a package rpm -e package_name apt-get remove package_name Check for package upgrades yum check-update apt-get -s upgrade apt-get -s dist-upgrade Upgrade packages yum update rpm -Uvh [args] apt-get upgrade Upgrade the entire system yum upgrade apt-get dist-upgrade Package Information Get information about an available package yum search package_name apt-cache search package_name Show available packages yum list available apt-cache dumpavail List all installed packages yum list installed rpm -qa dpkg –list Get information about a package yum info package_name apt-cache show package_name Get information about an installed package rpm -qi package_name dpkg –status package_name List files in an installed package rpm -ql package_name dpkg –listfiles package_name List documentation files in an installed package rpm -qd package_name – List configuration files in an installed package rpm -qc package_name dpkg-query –show -f ‘${Conffiles}\n’package_name Show the packages a given package depends on rpm -qR package_name apt-cache depends Show other packages that depend on a given package (reverse dependency) rpm -q -whatrequires [args] apt-cache rdepends Package File Information Get information about a package file rpm -qpi package.rpm dpkg –info package.deb List files in a package file rpm -qpl package.rpm dpkg –contents package.deb List documentation files in a package file rpm -qpd package.rpm – List configuration files in a package file rpm -qpc package.rpm – Extract files in a package rpm2cpio package.rpm | […]
RIP Authentication
RIPv1 does not support authentication. If you are sending and receiving RIP v2 packets, you can enable RIP authentication on an interface. The key chain determines the set of keys that can be used on the interface. Authentication, including default authentication, is performed on that interface only if a key chain is configured. Cisco supports two modes of authentication on an interface on which RIP is enabled: plain-text authentication and message digest algorithm 5 (MD5) authentication. Plain-text authentication is the default authentication in every RIPv2 packet. Do not use plain text authentication in RIP packets for security purposes, because the unencrypted authentication key is sent in every RIPv2 packet. Use plain-text authentication when security is not an issue; for example, you can use plain-text authentication to ensure that misconfigured hosts do not participate in routing. Specifying a RIP Version and Enabling Authentication Configuration example: ! router rip version {1 | 2} interface type number ip rip send version [1] [2] ip rip receive version [1] [2] ip rip authentication key-chain name-of-chain ip rip authentication mode {text | md5} ! Note: Key Chain needs to be configured for this to work. Troubleshoot: debug ip rip
Cisco Key Chains
To define an authentication, a key chain needed to enable authentication for routing protocols. To enter key-chain configuration mode, use the `key chain` command in global configuration mode. Only DRP Agent, Enhanced Interior Gateway Routing Protocol (EIGRP), and Routing Information Protocol (RIP) Version 2 use key chains. It is useful to have multiple keys on a key chain so that the software can sequence through the keys as they become invalid after time, based on the accept-lifetime and send-lifetime key chain key command settings. If the last key expires, authentication will continue and an error message will be generated. To disable authentication, you must manually delete the last valid key key chain commandkey chain name-of-chain no key chain name-of-chain Configuration example ! key chain MD5 key 1 key-string MD5HASH accept-lifetime 13:30:00 Jan 25 1996 duration 7200 send-lifetime 14:00:00 Jan 25 1996 duration 3600 exit ! key chain TEXT key 1 key-string CLEARTEXT key 2 key-string KEY2 !
Recent Comments