DOCSLIB.ORG

Cisco IOS XR Memory Forensics Analysis

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Cisco IOS XR Memory Forensics Analysis Cisco IOS XR memory forensics analysis Solal Jacob Agence Nationale de la Sécurité des Systèmes d’Information 2019 Plan I I- IOS XR internals & forensics analysis I II - Attack simulation I III - Detection ANSSI Cisco IOS XR memory forensics analysis 2/36 I- IOS XR internals & forensics analysis I We would like to be able to analyse a router to know if it was compromised I For that we want to develop memory forensics tools to detect advanced attack I We choose IOS XR because it’s an exotic system used on core routers ANSSI Cisco IOS XR memory forensics analysis 3/36 IOS XR I Used in Cisco routers (1200, ASR9000, ...) I 32 bits version only I Based on QNX 6.4 ANSSI Cisco IOS XR memory forensics analysis 4/36 QNX I Microkernel released in 1982, now part of Blackberry I Used in embedded system : Routers, Infotainment, Telematics (Westing House, AECL, Air traffic Control, General Electric) I Source was released then closed again ANSSI Cisco IOS XR memory forensics analysis 5/36 QNX architecture I Fault tolerent I Reduced kernel attack surface I Conform to posix standard I Customizable by OEM ANSSI Cisco IOS XR memory forensics analysis 6/36 QNX Security & Forensics I Some CVEs I No hardening before 6.6 I Troopers 2016, QNX : ”99 Problems but a Microkernel ain’t one !” (Vuln in message passing & IPC) I Recon 2018, ”Dissecting QNX” (Mitigation & PRNG) I No forensics papers or presentations ANSSI Cisco IOS XR memory forensics analysis 7/36 QNX startup I The IPL, Inital Program Loader, initialize the hardware, configure the memory controller, load the system image in RAM and jump to it I The startup code make further hardware initilization, launch the microkernel procnto in virtual mode, put all configs info into the system page I procnto run the boot script and launch other processes (path manager, network stack, ...) ANSSI Cisco IOS XR memory forensics analysis 8/36 QNX Firmware I IFS : Image file system, read-only (procnto, bootscript, drivers, ...) I EFS : Embedded file system, read-write (program, data, utilities, ...) I Combined image that can be flashed directly on NAND Figure – Combined image I Blackberry provide tools to create and read those images ANSSI Cisco IOS XR memory forensics analysis 9/36 Communication between processes I IPC : Use a message passing system I Messages are synchronous and directed towards channels and connections rather than threads I A thread create a channel to receive messages I An other thread can make a connection by ”attaching” to that channel, then send messages Figure – Combined image ANSSI Cisco IOS XR memory forensics analysis 10/36 The message passing system I Channels and connections have each an assigned file descriptor I When a thread create a channel, it can register a path I Processes can open these path via the path manager, that return the file descriptor needed to communicate I Messages are passed by being copied from the address space of one thread to the address space of an other thread I There is very few syscall under QNX 6.4 (~100) I The libc hide the message passing system like Linux libc hide syscall ANSSI Cisco IOS XR memory forensics analysis 11/36 Linux libc syscall wrapper I fd = open(”file”) ; fd = syscall(open_syscall_number, "file"); I write(fd, ”abcd”, 4) ; ret = syscall(write_syscall_number, fd, "abcd", 4); I close(fd) ; ret = close(close_syscall_number, fd); ANSSI Cisco IOS XR memory forensics analysis 12/36 QNX libc message wrapper I fd = open(”myfile”) ; fd = ConnectAttach(PATHMGR_COID, "myfile", 1, 0, 1); sent_msg.type = IO_CONNECT sent_msg.data = "myfile" sent_msg.path_len = strlen("myfile"); MsgSend(fd, sent_msg, sent_msg_size, reply_msg, reply_msg.size); ConnectDetach(fd); We connect to the service and we ask for a fd for this path (reply->pid is the pid of the process that handles the hard disks) fd = ConnectAttach(reply->nd, reply->pid, reply->chid, 0, 0); MsgSend(fd, sent_msg, sent_msg_size, reply_msg, reply_msg_size) ANSSI Cisco IOS XR memory forensics analysis 13/36 QNX libc message wrapper I write(fd, ”abcd”, 4) ; sent_msg_buffer.type = IO_WRITE sent_msg_buffer.nbytes = 4 sent_msg.buffer.data = "abcd" MsgSend(fd, sent_msg_buffer, sent_msg_buffer_size, ret_msg_buffer, sizeof( ret_msg_buffer)); I close(fd) ; sent_msg.type = IO_CLOSE sent_msg.size = sizeof(sent_msg); ret = MsgSend(fd, sent_msg_buffer, sizeof(sent_msg), 0, 0); ConnectDetach(fd); ANSSI Cisco IOS XR memory forensics analysis 14/36 Memory acquisition I Request memory mapping via the memory manager services I Interfaced via mmap_device_memory I All physical memory is directly addressable I No kernel drivers needed ANSSI Cisco IOS XR memory forensics analysis 15/36 Memory acquisition tool I Transfer the memory content via a network socket (to a listening netcat) on QNX I Cisco add it’s own services and network stack I They use a modified version of GCC to generate specific executables I A second process manager services is used to launch those executables (They have a JID instead of PID) I Cisco modifed top and others commands to list only application with a JID I It’s difficult to generate binary that link to the libsocket and the Cisco network stack I To create a socket it’s possible to use the message system directly ANSSI Cisco IOS XR memory forensics analysis 16/36 Socket without libsocket sprintf(buff, "/dev/socket/2/1/0/1610612736/%d", getpid()); int sock = open(buff, 2, 0); struct sockaddr_in client; ... int ret; my_io_devctl_t msg; iov_t siov[2]; iov_t riov[2]; msg.i.type = _IO_DEVCTL; msg.i.combine_len = sizeof(msg.i); /*msg.i.dcmd = 0x80100603; under QNX 6.4.0 */ msg.i.dcmd = 0x80048004; msg.i.nbytes = sizeof(client); msg.i.zero = 0; (siov)->iov_base = (void*)&msg.i; (siov)->iov_len = sizeof(msg.i); (siov + 1)->iov_base = (void*)client; (siov + 1)->iov_len = sizeof(client); (riov)->iov_base = (void*)&msg.o; //(siov)->iov_base; (riov)->iov_len = sizeof(msg.o); ret = MsgSendv(sockfd, siov, 2, riov, 1); ANSSI Cisco IOS XR memory forensics analysis 17/36 Executing the acquisition tool on IOS XR I The memory acquistion tool can be transfered to IOS XR via ssh I It can’t be run directly because Cisco removed the chmod tool I To made the file executable, there is a trick : copy a binary with executable right in the user writable directory and then copy a binary over it ANSSI Cisco IOS XR memory forensics analysis 18/36 Analysis of the memory dump I The pidin tool, that list lot of system informations, was studied I It reveal the use of syspage_entry structure, that point to lot of other interstings structures I To read differents structures from the dump we need to know their physical adresses I The virtual address of the syspage_entry struct can be listed via pidin I The syspage_entry structure is in the adress space of procnto I procnto cr3 value is needed to convert syspage_entry virtual address to physical one ANSSI Cisco IOS XR memory forensics analysis 19/36 procnto address space I To find procnto cr3 value, qemu is used to list tlb and find ”constant” value I It use identity mapping to translate virtual addresses to physical one I The cr3 value is constant across boot, the value can be found in the IPL (that launch procnto) I procnto virtual adress can be convert to physical one thanks to this value I syspage_entry and lot of user structures can be read I Processes, memory map, channels, file descriptor, ... can then be listed ANSSI Cisco IOS XR memory forensics analysis 20/36 Connection and channel graph ./qnxmemdump (1966121) I QNX processes use IPC, known sbin/devc-pty (139283) sbin/io-pkt-v4-hc (110609) as channel, to communicate with other process proc/boot/devc-con-hid (4103) I All the structures containing proc/boot/io-hid (4102) informations about connections and channels are readable from proc/boot/io-usb (4101) the memory dumps I A graph could be created to proc/boot/procnto-smp-instr (1) visualize all the connections I The graph can be used, for proc/boot/devb-eide (8200) example, to know if a process use the network stack (as in proc/boot/slogger (4100) proc/boot/pci-bios (4099) microkernel drivers are processes) ANSSI Cisco IOS XR memory forensics analysis 21/36 Processes address space I Each processes as it’s own address space I To extract each processes and their memory allocation, for further analysis, the physical address of their differents segments in memory are needed I For that we need their cr3 value I They are found by following structures linked to syspage_entry I Once we have cr3 we use it to read the PTE and other structures in order to do virtual to physical translation (PAE is used un IOS XR) I We can then access all the address space of a processes (the segment of the executables mapped in memory and the different allocation made by the processes) ANSSI Cisco IOS XR memory forensics analysis 22/36 Reconstructing the binaries I Only the data and text segment address is listed in procnto structures I QNX and IOS XR binary structure differs (but QNX binaries are also found in IOS XR) I Thery’re both ELF ANSSI Cisco IOS XR memory forensics analysis 23/36 QNX binaries I QNX binaries are dynamic and have differents kind of segments loaded I We can’t know the address of the dynamic segments I In memory text segment is a direct mapping of the offset zero of the binary I So, it’s easy to read the ELF header I The header can be used to rebuild a partial binary containing only the text and data segments ANSSI Cisco IOS XR memory forensics analysis 24/36 IOS XR binaries I The text segment is always located at 0x1000 in the binaries (it start with a NIAM header)
Load more

Recommended publications
  • Cisco IOS XR Software Release
    CISCO CRAFT WORKS INTERFACE QUICK START GUIDE Cisco IOS XR Software Release 3.5 1 Introduction 2 About CWI 3 Prerequisites 4 Configuring the Router and CWI Client 5 Installing, Launching, and Uninstalling CWI 6 Getting Started with CWI 7 Reference Information 8 Obtaining Documentation, Obtaining Support, and Security Guidelines 1 Introduction This document introduces Craft Works Interface (CWI) that supports Cisco IOS XR Software Release 3.5. Note This document refers to CWI managing devices. For Cisco IOS XR software, the devices can be any or all of the secure domain routers (SDRs) of which your Cisco IOS XR system is composed. Related Documentation See the following list for related documents that may be useful: • Cisco Craft Works Interface User Guide • Cisco Craft Works Interface Online Help Intended Audience This document is intended for experienced service provider administrators, Cisco telecommunication management engineers, and third-party field service technicians who have completed the required Cisco router training sessions. 2 About CWI CWI is a powerful, session-based tool that allows you to manage, monitor, and configure a single device or a network of devices. CWI is designed to operate in as many situations as possible. Using CWI you can: • Connect to the devices in several ways through a serial port, a terminal server, or an IP-based method, such as Telnet, SSH, or CORBA. • Run Windows, Macintosh, and Linux clients. • Connect to devices with or without XML or command-line interface (CLI) capabilities. • Display both the administrative (admin) plane and device plane for Cisco IOS XR devices. CWI offers a selection of CLI- and graphic-based tools from which you can perform management tasks.
    [Show full text]
  • Cisco CRS-1 SIP and SPA Configuration Guide Cisco IOS XR Software Release 3.3
    R3.3 Beta Draft—Cisco Confidential Information Cisco CRS-1 SIP and SPA Configuration Guide Cisco IOS XR Software Release 3.3 Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100 Text Part Number: OL-7110-03 R3.3 Beta Draft—Cisco Confidential Information THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
    [Show full text]
  • Cisco IOS XR Memory Forensics Analysis
    Cisco IOS XR memory forensics analysis Solal Jacob Agence Nationale de la Sécurité des Systèmes d’Information 2019 TOC I I- IOS XR internals & forensics analysis I II - Attack simulation I III - Detection ANSSI Cisco IOS XR memory forensics analysis 2/33 I- IOS XR internals & forensics analysis I We would like to be able to analyze a router to know if it was compromised I For that we want to develop memory forensics tools to detect advanced attack I IOS XR is an exotic system used on core routers ANSSI Cisco IOS XR memory forensics analysis 3/33 IOS XR I Used in Cisco routers (12000, ASR9000, ...) I 32 bits version only I Based on QNX 6.4 ANSSI Cisco IOS XR memory forensics analysis 4/33 QNX I Microkernel released in 1982, now part of Blackberry I Used in embedded system : Routers, Infotainment, Telematics (Westing House, AECL, Air traffic Control, General Electric) I Source was released then closed again ANSSI Cisco IOS XR memory forensics analysis 5/33 QNX architecture I Fault tolerant I Reduced kernel attack surface I Conforms to posix standard I Customizable by OEM ANSSI Cisco IOS XR memory forensics analysis 6/33 QNX Security & Forensics I Some CVEs I No hardening before 6.6 I Troopers 2016, QNX : ”99 Problems but a Microkernel ain’t one !” (Vuln in message passing & IPC) I Recon 2018, ”Dissecting QNX” (Mitigation & PRNG) I No forensics papers or presentations ANSSI Cisco IOS XR memory forensics analysis 7/33 QNX startup I The IPL, Inital Program Loader, initializes the hardware, configures the memory controller, loads the system image
    [Show full text]
  • System Management Configuration Guide for Cisco NCS 540 Series Routers, IOS XR Release 7.3.X
    System Management Configuration Guide for Cisco NCS 540 Series Routers, IOS XR Release 7.3.x First Published: 2021-02-26 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • IOS XR Software CRS-1 and C12000
    IOS XR Software CRS-1 and C12000 Martin Winter Technical Leader Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1 Agenda High Level IOS XR Strategy IOS XR Software Architecture IOS XR CLI Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 2 High level IOS XR Strategy Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 3 High End Routing Portfolio Next Generation Core 40G Routing Day 1 CRS-1 Multi-Chassis Scale Foundation for Core Consolidation Next Generation Core & Edge • Builds on 12000 Series Technology • PRP, 2.5G ISE, 10G ISE Cisco XR 12000 • Edge interface breadth/density • 4/6/10/16 Slot Form Factor • Foundation for Multi-Service Edge consolidation Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 4 Cisco High End Routing Strategy IOS XR: Foundation of Cisco HER Technology Convergence HighHigh EndEnd RoutingRouting PlatformsPlatforms Systems Silicon Services (Single and Multi- (Forwarding (High Touch Deep Chassis / 2.5G to 40G+) Engines) Packet Inspection) Services CRS 40G ISE Blade (X-Blade) 12000 10G ISE 2.5G ISE vFW, SBC IOS XR Software • IOS XR is the ‘glue’, delivering HA, scale, core+edge services with common management and user interface Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 5 IOS XR Software Architecture Presentation_ID © 2006 Cisco Systems, Inc. All rights reserved. Cisco Confidential 6 Modular IOS != IOS XR Modular IOS: Ships today on Catalyst 6500 with Sup720 and Sup32 Based on the same IOS code with added Microkernel and IOS split into multiple processes. Not everything as it’s own process (ie all Routing as one process), optimized for performance on existing hardware IOS XR: Ships today on CRS-1 and C12000 (PRP only) Complete rewrite of the code Very modular, split into multiple processes and built for multiterabit scaling and distributed operation Features targeted for SP NGN router Presentation_ID © 2006 Cisco Systems, Inc.
    [Show full text]
  • Cisco IOS XR Security
    07_1587052717_ch06.qxp 5/15/09 11:21 AM Page 159 CHAPTER 6 Cisco IOS XR Security It is important to control access to the router to prevent unauthorized or malicious use that might take the router offline or use it to launch an attack on the rest of the network. Cisco IOS XR provides the authentication, authorization, and accounting (AAA) frame- work that helps provide secure access via the logical vty and the physical tty ports. Fur- thermore, ensuing sections in this chapter discuss the concepts of task-based authorization and familiarize the user with IOS XR concepts such as admin and SDR planes as well as the uniqueness of user groups and task group configuration. Forwarding plane refers to the components involved in the various stages during packet forwarding. Forwarding plane refers not only to the flow of a packet through the router but also to the packets destined to the router. Protection of forwarding plane is important and necessitates controlling the type of traffic that traverses the router, and limiting the amount of traffic that’s destined to the router itself so that the router does not become a victim of a denial of service (DoS) attack. You might well be familiar with access control lists (ACL) and Unicast Reverse Path Forwarding (uRPF) as popular forwarding plane secu- rity features. Additionally, IOS XR has a concept of Local Packet Transport Service (LPTS). LPTS provides protection against traffic destined to the router. This type of traffic is usually related to routing protocols that typically run on the route processor (RP) of the router, though Telnet, SNMP, NTP, ping, traceroute, and various other services create traf- fic that can be destined to a router’s line card or RP CPU.
    [Show full text]
  • Release Notes for Cisco NCS 5000 Series Routers, IOS XR Release 6.6.1
    Release Notes for Cisco NCS 5000 Series Routers, IOS XR Release 6.6.1 Network Convergence System 5000 Series Routers 2 Release 6.6.1 Packages 2 System Requirement 3 Software Features Introduced in this Release 4 Behavior Change Introduced in this release 4 Hardware Features Introduced in this Release 4 Caveats 5 Upgrading Cisco IOS XR Software 5 Related Documentation 5 Communications, Services, and Additional Information 6 Full Cisco Trademarks with Software License 8 Network Convergence System 5000 Series Routers Note Explore the Content Hub, the all new portal that offers an enhanced product documentation experience. • Use faceted search to locate content that is most relevant to you. • Create customized PDFs for ready reference. • Benefit from context-based recommendations. Get started with the Content Hub at content.cisco.com to craft a personalized documentation experience. Do provide feedback about your experience with the Content Hub. Cisco IOS XR Release 6.6.1 is a limited availability (LA) release. All Cisco IOS XR Release 6.6.1 features are available in Cisco IOS XR Release 6.6.25, which is a general availability (GA) release. For more information on IOS XR Release 6.6.25, see Release Notes for Cisco NCS 5500 Series Routers, Release 6.6.25 The Network Convergence System 5000 Series offers a high-density, small-form-factor MPLS aggregation router for metro aggregation. It is designed to economically scale large enterprise, over-the-top (OTT), and service provider Data Center networking architectures. The Cisco NCS 5000 Series is an extension to Cisco’s routing platform portfolio enabling Service Providers and MPLS enabled data center architectures to offer elastic networks with improved business agility and simplified operations to deliver high-bandwidth mobile, video, and cloud services.
    [Show full text]
  • Memory Forensics Analysis of Cisco IOS XR 32 Bits Routers
    Memory forensics analysis of Cisco IOS XR 32 bits routers Abstract Attackers are constantly developing new techniques to bypass current security measures, and they are researching new targets to attack. The "Shadow Brokers" case illustrates that advanced attackers now target network devices such as routers. These core devices handle large amounts of data and are generally not audited by the security team, nor protected by specific security solutions, making them very interesting targets for attackers. This paper explains Cisco IOS XR routers internal, relevant to forensics analysis. As no forensics tool exists on this platform, we develop a tool for dumping the memory of the routers and another one, amnesic-sherpa, to analyze the memory dumps. Also, we demonstrate that by using an automated process based on these tools, we can determine if a router was compromised. Keywords: Forensics, QNX, Cisco, Routers forensics, Memory forensics, Routers, Firmware analysis 1. Foreword help debug, ...). This process creates child processes (in user space) and manage the system memory. QNX can There are a lot of publications on Cisco routers us- thus via proc-nto load the services that the system needs. ing the standard version of IOS (Lindner, 2008). There These services use a message passing system (QNX, 2010c) are, however, very few technical papers and research work to communicate together. They are either provided by de- about the security and forensics analysis of Cisco router fault, or developed and distributed in a specific image of using IOS XR (CISCO, 2005). Furthermore these devices the system. are at the core of many networks today.
    [Show full text]
  • System Setup and Software Installation Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.7.X
    System Setup and Software Installation Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.7.x First Published: 2020-08-01 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]
  • Point to Point Protocol Cisco Pdf
    Point To Point Protocol Cisco Pdf intoningPadraig hypostatisedher make-peace freely. thinkingly, Cooper unsweetenedis concordant: and she interpenetrable. distilled tropically and besmirch her cracks. Emmet Both Palo Alto and Bluecoat have the capability to do SSL Decryption and URL Filtering. Unlike HDLC which through a Cisco proprietary protocol PPP is however open standard protocol so again should award it to patrol a Cisco router to a. In recent years, use Ethernet over ATM encapsulation. Palo Alto Networks does follow coordinated vulnerability disclosure for security vulnerabilities that are reported to us by external researchers. In it is a connection points also no cabling cisco online, and ccie cyber security infrastructure certifications looking forward in cisco pdf to point protocol field is known that the peer is. Pds can return to icts, you need to not able to grow your proxy, crypto ipsec tunnel interfaces and effectively manage the difference is a result. The protocols take your area is to connect from bgp process, and consumption of. The toe the blueprint for new to point for industry for the selected software. Unified access points operate anywhere the Lightweight Access Point Protocol LWAPP and west in door with Cisco wireless LAN controllers and the Cisco. Ccie cyber ops exam and protocol field. The final exam time is not included in the time table. This lab and paste edition by the link is by the following line status is a modem from ucs blades jumbo frames. Study of BGP blackholing as an attack vector. Advanced OSPF Lab to know full connectivity using OSPF. Cable connected to add an implementation of the default lmi option negotiation.
    [Show full text]
  • Cisco IOS XR MPLS Configuration Guide Cisco IOS XR Software Release 3.7
    R37 Technical Checkpoint Draft—Cisco Confidential Cisco IOS XR MPLS Configuration Guide Cisco IOS XR Software Release 3.7 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 Customer Order Number: OL-15850-01 R37 Technical Checkpoint Draft—Cisco Confidential THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
    [Show full text]
  • System Management Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 7.3.X
    System Management Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 7.3.x First Published: 2021-02-01 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
    [Show full text]