Download Here
NetPerSec
NetPerSec measures the real-time speed of your internet connection. Different types of connections promise different connection speeds, but what are you actualy getting? Due to network traffic, actual speeds are often slower than what is promised. NetPerSec lets you check your connection speed in real time. It monitors all TCP/IP activity to and from the internet or other networks, and graphs the cummunication speed. Its dynamic tray icon shows send and recieve activity with a bar graph or a histogram.
Download Here
EIGRP Labs - CISCO Network Accademy
Best Labs ever designed to practise a roting protocol with all of its features and capabilities. Step by Step guide to learn and have complete hands on practise.
Download Here
Download Here
EIGRP CheatSheet
Handy Study referencing Cheat Sheet. Best for revising the main points in no time.
Password: ccnpbsci
Understanding EIGRP Null0 Interface
The Null interface is typically for preventing routing loops. EIGRP, for instance always creates a route to the Null0 interface when it summerizes a group of routes. ........
To Read More Download
To Read More Download
Reliable Open Port Check Tool
TO CHECK IF UR PORT IS OPEN
- Download PFPortCheck Program.
- Install PortCheck Program.
- Run PFPortCheck Program. Type in the port u want to check, choose TCP or UDP and click the Check Me button
GNS3 New Version - (All in one)
Best ever emulator for practicing labs on Cisco Routers. Latest and complete version for Windows.
Note: Best experienced on Win XP.
Download Here
Note: Best experienced on Win XP.
Download Here
Best IOS for 3640
Download the best IOS for practising on Cisco 3640. Pre-calculated Idle Pc value included. IOS for Dynapsis/GNS3.
Download here
Download here
How to configure a Frame-Relay Switch (Cisco 2520/2522)
This how-to guide will address all those questions and show you how to configure your Frame-Relay switch such as Cisco 2520 or the Cisco 2522 routers to route frame relay packets between your routers.
Any cisco router can serve as a frame-relay switch, but you may want to get one with 4 or more serial ports so you are able to connect many routers to it for a real-world simulation. I recommend that you buy a used cisco 2520 (for a small lab setup) or the cisco 2522 router (for large lab setup).
If you can afford it, you can buy a 2611XM router with 8-port asynchronous/synchronous serial network module (NM-8A/S) or the 16-port asynchronous/synchronous serial network module (NM-16A/S) and run latest IOS for greater scalability and expandability.
2520 and 2522 Comparison
Cisco 2520 has:
- 1 Ethernet port with a selectable attachment unit interface (AUI) connection or 1 Ethernet 10BaseT connection
- 1 Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) port (RJ-45)
- 2 high-speed synchronous serial ports
- 2 low-speed asynchronous/synchronous serial port
However, we will be using the cisco 2522 router for this how-to guide, which has:
- 1 Ethernet/IEEE 802.3 interface(s)
- 2 Serial network interface(s)
- 8 Low-speed serial(sync/async) network interface(s)
- 1 ISDN Basic Rate interface(s)
Other equipment being used which made this how-to possible:
- Cisco 2611XM (R1, R2, R3 and R4)
Dual Fast Ethernet Interfaces
2 WAN Interface Card (WIC) Slots with WIC-1T cards (installed)
1 NM Slot - Cisco 2511 Access Server
1 Ethernet
2 synchronous serial ports
16 asynchronous serial ports
The Network Topology in this scenario, a fully-meshed network:
The routers are connected with the frame-relay switch using DB-60 to DB-60 DTE/DCE cables, with DCE end of the cables attached to the frame-relay switch.
Let's log on to our frame relay switch and start configuring it
Before you can do any frame-relay switching on this router, you must enable it using this command:
FrameRelay-2522(config)# frame-relay switching
Enter the serial interface configuration mode:
FrameRelay-2522(config)# interface serial1
Add the description command so you know which interface is connected to which router:
FrameRelay-2522(config-if)#description Connected to Router1's Serial0 Interface
The interface should not have any IP address, so remove it with this command:
FrameRelay-2522(config-if)# no ip address
Encapsulation must be set to frame-relay, so use this command to set that:
FrameRelay-2522(config-if)# encapsulation frame-relay
FrameRelay-2522(config-if)# clock rate 64000
Set the Local Management Interface (LMI) type to ANSI:
FrameRelay-2522(config-if)# frame-relay lmi-type ansi
Set the frame-relay switch's interface type as DCE:
FrameRelay-2522(config-if)# frame-relay intf-type dce
Turn the interface on, enable it using:
FrameRelay-2522(config-if)# no shutdown
Let's configure the DLCI mapping:
FrameRelay-2522(config-if)# frame-relay route 102 interface Serial2 201
The above command will route packets with input DLCI of 102 to output interface of serial2 with output DLCI of 201. This will allow the frame relay switch to route packets between router1 (R1)'s serial0 to router2 (R2)'s serial0 interfaces.
Confused? Let's do another one on the same interface:
FrameRelay-2522(config-if)# frame-relay route 103 interface Serial2 301
That enables communication between Router1 (R1) and Router3 (R3) through the frame-relay switch.
Study the attached topology diagram to understand this better.
You will need to repeat these commands on each interface of the frame-relay switch along with correct DLCI mappings.
Let's verify the configuration on the frame-relay switch and circuit status. Since our routers were already configured with frame relay and DLCI mappings, they should be talking to each other. Let's take a look with following command:
Frame-Relay-2522# show frame-relay pvc
PVC Statistics for interface Serial1 (Frame Relay DCE)
<
DLCI = 102, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial1
input pkts 1581 output pkts 1560 in bytes 305706
out bytes 367148 dropped pkts 1 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 1581
pvc create time 13:23:39, last time pvc status changed 12:36:58
DLCI = 103, DLCI USAGE = SWITCHED, PVC STATUS = ACTIVE, INTERFACE = Serial3
input pkts 38 output pkts 66 in bytes 5082
out bytes 7734 dropped pkts 1 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0 Num Pkts Switched 37
pvc create time 13:23:49, last time pvc status changed 12:43:19
Notice the bold text, PVC status = ACTIVE means that the circuit is up and routers are communicating.
Let's run another command to verify our configuration:
Frame-Relay-2522# show frame-relay route
| Input Intf | Input Dlci | Output Intf | Output Dlci | Status |
| Serial1 | 102 | Serial1 | 201 | active |
| Serial2 | 103 | Serial1 | 301 | active |
| | | | | |
The above output shows you the mappings we performed earlier. If anything that says "inactive" in the status then there is a problem either on the corresponding routers or the frame relay configuration.
Finally, one more command to further check to make sure that everything is in working order:
Frame-Relay-2522# show frame-relay lmi
LMI Statistics for interface Serial1 (Frame Relay DCE) LMI TYPE = ANSI
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Rcvd 4625 Num Status msgs Sent 4625
Num Update Status Sent 0 Num St Enq. Timeouts 78
LMI Statistics for interface Serial2 (Frame Relay DCE) LMI TYPE = ANSI
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Rcvd 4624 Num Status msgs Sent 4624
Num Update Status Sent 0 Num St Enq. Timeouts 75
The number in the bold text should be increasing/changing every time you run the command.
Thats it, we are done with the basic configuration of the frame relay switch. If you have any questions or comments, feel free to post them here or use the contact us link to submit your feedback.
Good luck!
CCIE Routing and Switching Lab Exam Topics (Blueprint) v4.0
The following topics are general guidelines for the content likely to be included on the lab exam. However, other related topics may also appear on any specific delivery of the exam. In order to better reflect the contents of the exam and for clarity purposes, the guidelines below may change at any time without notice.
TO ACCESS THIS BLUE PRINT ON CISCO SITE YOU NEED TO LOGIN. I HAVE THE LOGIN ACCESS AND I HAVE COPIED THE SAME FROM THERE FOR YOUR ACCESS AND EASE.
Exam Sections and Sub-task Objectives
| 1.00 | Implement Layer 2 Technologies | √ |
| 1.10 | Implement Spanning Tree Protocol (STP) | |
| (a) 802.1d | ||
| (b) 802.1w | ||
| (c) 801.1s | ||
| (d) Loop guard | ||
| (e) Root guard | ||
| (f) Bridge protocol data unit (BPDU) guard | ||
| (g) Storm control | ||
| (h) Unicast flooding | ||
| (i) Port roles, failure propagation, and loop guard operation | ||
| 1.20 | Implement VLAN and VLAN Trunking Protocol (VTP) | |
| 1.30 | Implement trunk and trunk protocols, EtherChannel, and load-balance | |
| 1.40 | Implement Ethernet technologies | |
| (a) Speed and duplex | ||
| (b) Ethernet, Fast Ethernet, and Gigabit Ethernet | ||
| (c) PPP over Ethernet (PPPoE) | ||
| 1.50 | Implement Switched Port Analyzer (SPAN), Remote Switched Port Analyzer (RSPAN), and flow control | |
| 1.60 | Implement Frame Relay | |
| (a) Local Management Interface (LMI) | ||
| (b) Traffic shaping | ||
| (c) Full mesh | ||
| (d) Hub and spoke | ||
| (e) Discard eligible (DE) | ||
| 1.70 | Implement High-Level Data Link Control (HDLC) and PPP | |
| 2.00 | Implement IPv4 | |
| 2.10 | Implement IP version 4 (IPv4) addressing, subnetting, and variable-length subnet masking (VLSM) | |
| 2.20 | Implement IPv4 tunneling and Generic Routing Encapsulation (GRE) | |
| 2.30 | Implement IPv4 RIP version 2 (RIPv2) | |
| 2.40 | Implement IPv4 Open Shortest Path First (OSPF) | |
| (a) Standard OSPF areas | ||
| (b) Stub area | ||
| (c) Totally stubby area | ||
| (d) Not-so-stubby-area (NSSA) | ||
| (e) Totally NSSA | ||
| (f) Link-state advertisement (LSA) types | ||
| (g) Adjacency on a point-to-point and on a multi-access network | ||
| (h) OSPF graceful restart | ||
| 2.50 | Implement IPv4 Enhanced Interior Gateway Routing Protocol (EIGRP) | |
| (a) Best path | ||
| (b) Loop-free paths | ||
| (c) EIGRP operations when alternate loop-free paths are available, and when they are not available | ||
| (d) EIGRP queries | ||
| (e) Manual summarization and autosummarization | ||
| (f) EIGRP stubs | ||
| 2.60 | Implement IPv4 Border Gateway Protocol (BGP) | |
| (a) Next hop | ||
| (b) Peering | ||
| (c) Internal Border Gateway Protocol (IBGP) and External Border Gateway Protocol (EBGP) | ||
| 2.70 | Implement policy routing | |
| 2.80 | Implement Performance Routing (PfR) and Cisco Optimized Edge Routing (OER) | |
| 2.90 | Implement filtering, route redistribution, summarization, synchronization, attributes, and other advanced features | |
| 3.00 | Implement IPv6 | |
| 3.10 | Implement IP version 6 (IPv6) addressing and different addressing types | |
| 3.20 | Implement IPv6 neighbor discovery | |
| 3.30 | Implement basic IPv6 functionality protocols | |
| 3.40 | Implement tunneling techniques | |
| 3.50 | Implement OSPF version 3 (OSPFv3) | |
| 3.60 | Implement EIGRP version 6 (EIGRPv6) | |
| 3.70 | Implement filtering and route redistribution | |
| 4.00 | Implement MPLS Layer 3 VPNs | |
| 4.10 | Implement Multiprotocol Label Switching (MPLS) | |
| 4.20 | Implement Layer 3 virtual private networks (VPNs) on provider edge (PE), provider (P), and customer edge (CE) routers | |
| 4.30 | Implement virtual routing and forwarding (VRF) and Multi-VRF Customer Edge (VRF-Lite) | |
| 5.00 | Implement IP Multicast | |
| 5.10 | Implement Protocol Independent Multicast (PIM) sparse mode | |
| 5.20 | Implement Multicast Source Discovery Protocol (MSDP) | |
| 5.30 | Implement interdomain multicast routing | |
| 5.40 | Implement PIM Auto-Rendezvous Point (Auto-RP), unicast rendezvous point (RP), and bootstrap router (BSR) | |
| 5.50 | Implement multicast tools, features, and source-specific multicast | |
| 5.60 | Implement IPv6 multicast, PIM, and related multicast protocols, such as Multicast Listener Discovery (MLD) | |
| 6.00 | Implement Network Security | |
| 6.01 | Implement access lists | |
| 6.02 | Implement Zone Based Firewall | |
| 6.03 | Implement Unicast Reverse Path Forwarding (uRPF) | |
| 6.04 | Implement IP Source Guard | |
| 6.05 | Implement authentication, authorization, and accounting (AAA) (configuring the AAA server is not required, only the client-side (IOS) is configured) | |
| 6.06 | Implement Control Plane Policing (CoPP) | |
| 6.07 | Implement Cisco IOS Firewall | |
| 6.08 | Implement Cisco IOS Intrusion Prevention System (IPS) | |
| 6.09 | Implement Secure Shell (SSH) | |
| 6.10 | Implement 802.1x | |
| 6.11 | Implement NAT | |
| 6.12 | Implement routing protocol authentication | |
| 6.13 | Implement device access control | |
| 6.14 | Implement security features | |
| 7.00 | Implement Network Services | |
| 7.10 | Implement Hot Standby Router Protocol (HSRP) | |
| 7.20 | Implement Gateway Load Balancing Protocol (GLBP) | |
| 7.30 | Implement Virtual Router Redundancy Protocol (VRRP) | |
| 7.40 | Implement Network Time Protocol (NTP) | |
| 7.50 | Implement DHCP | |
| 7.60 | Implement Web Cache Communication Protocol (WCCP) | |
| 8.00 | Implement Quality of Service (QoS) | |
| 8.10 | Implement Modular QoS CLI (MQC) | |
| (a) Network-Based Application Recognition (NBAR) | ||
| (b) Class-based weighted fair queuing (CBWFQ), modified deficit round robin (MDRR), and low latency queuing (LLQ) | ||
| (c) Classification | ||
| (d) Policing | ||
| (e) Shaping | ||
| (f) Marking | ||
| (g) Weighted random early detection (WRED) and random early detection (RED) | ||
| (h) Compression | ||
| 8.20 | Implement Layer 2 QoS: weighted round robin (WRR), shaped round robin (SRR), and policies | |
| 8.30 | Implement link fragmentation and interleaving (LFI) for Frame Relay | |
| 8.40 | Implement generic traffic shaping | |
| 8.50 | Implement Resource Reservation Protocol (RSVP) | |
| 8.60 | Implement Cisco AutoQoS | |
| 9.00 | Troubleshoot a Network | |
| 9.10 | Troubleshoot complex Layer 2 network issues | |
| 9.20 | Troubleshoot complex Layer 3 network issues | |
| 9.30 | Troubleshoot a network in response to application problems | |
| 9.40 | Troubleshoot network services | |
| 9.50 | Troubleshoot network security | |
| 10.00 | Optimize the Network | |
| 10.01 | Implement syslog and local logging | |
| 10.02 | Implement IP Service Level Agreement SLA | |
| 10.03 | Implement NetFlow | |
| 10.04 | Implement SPAN, RSPAN, and router IP traffic export (RITE) | |
| 10.05 | Implement Simple Network Management Protocol (SNMP) | |
| 10.06 | Implement Cisco IOS Embedded Event Manager (EEM) | |
| 10.07 | Implement Remote Monitoring (RMON) | |
| 10.08 | Implement FTP | |
| 10.09 | Implement TFTP | |
| 10.10 | Implement TFTP server on router | |
| 10.11 | Implement Secure Copy Protocol (SCP) | |
| 10.12 | Implement HTTP and HTTPS | |
| 10.13 | Implement Telnet |
END
CCIE ® Routing and Switching Written Exam Topics (Blueprint) v4.0
The comprehensive CCIE R&S Written Exam (#350-001) has 100 multiple-choice questions and is two hours in duration. The topic areas listed are general guidelines for the type of content that is likely to appear on the exam. Please note, however, that other relevant or related topic areas may also appear.
Exam Sections and Sub-task Objectives
| 1.00 | Implement Layer 2 Technologies | √ |
| 1.10 | Implement Spanning Tree Protocol (STP) | |
| (a) 802.1d | ||
| (b) 802.1w | ||
| (c) 801.1s | ||
| (d) Loop guard | ||
| (e) Root guard | ||
| (f) Bridge protocol data unit (BPDU) guard | ||
| (g) Storm control | ||
| (h) Unicast flooding | ||
| (i) Port roles, failure propagation, and loop guard operation | ||
| 1.20 | Implement VLAN and VLAN Trunking Protocol (VTP) | |
| 1.30 | Implement trunk and trunk protocols, EtherChannel, and load-balance | |
| 1.40 | Implement Ethernet technologies | |
| (a) Speed and duplex | ||
| (b) Ethernet, Fast Ethernet, and Gigabit Ethernet | ||
| (c) PPP over Ethernet (PPPoE) | ||
| 1.50 | Implement Switched Port Analyzer (SPAN), Remote Switched Port Analyzer (RSPAN), and flow control | |
| 1.60 | Implement Frame Relay | |
| (a) Local Management Interface (LMI) | ||
| (b) Traffic shaping | ||
| (c) Full mesh | ||
| (d) Hub and spoke | ||
| (e) Discard eligible (DE) | ||
| 1.70 | Implement High-Level Data Link Control (HDLC) and PPP | |
| 2.00 | Implement IPv4 | |
| 2.10 | Implement IP version 4 (IPv4) addressing, subnetting, and variable-length subnet masking (VLSM) | |
| 2.20 | Implement IPv4 tunneling and Generic Routing Encapsulation (GRE) | |
| 2.30 | Implement IPv4 RIP version 2 (RIPv2) | |
| 2.40 | Implement IPv4 Open Shortest Path First (OSPF) | |
| (a) Standard OSPF areas | ||
| (b) Stub area | ||
| (c) Totally stubby area | ||
| (d) Not-so-stubby-area (NSSA) | ||
| (e) Totally NSSA | ||
| (f) Link-state advertisement (LSA) types | ||
| (g) Adjacency on a point-to-point and on a multi-access network | ||
| (h) OSPF graceful restart | ||
| 2.50 | Implement IPv4 Enhanced Interior Gateway Routing Protocol (EIGRP) | |
| (a) Best path | ||
| (b) Loop-free paths | ||
| (c) EIGRP operations when alternate loop-free paths are available, and when they are not available | ||
| (d) EIGRP queries | ||
| (e) Manual summarization and autosummarization | ||
| (f) EIGRP stubs | ||
| 2.60 | Implement IPv4 Border Gateway Protocol (BGP) | |
| (a) Next hop | ||
| (b) Peering | ||
| (c) Internal BorderGateway Protocol (IBGP) and External Border Gateway Protocol (EBGP) | ||
| 2.70 | Implement policy routing | |
| 2.80 | Implement Performance Routing (PfR) and Cisco Optimized Edge Routing (OER) | |
| 2.90 | Implement filtering, route redistribution, summarization, synchronization, attributes, and other advanced features | |
| 3.00 | Implement IPv6 | |
| 3.10 | Implement IP version 6 (IPv6) addressing and different addressing types | |
| 3.20 | Implement IPv6 neighbor discovery | |
| 3.30 | Implement basic IPv6 functionality protocols | |
| 3.40 | Implement tunneling techniques | |
| 3.50 | Implement OSPF version 3 (OSPFv3) | |
| 3.60 | Implement EIGRP version 6 (EIGRPv6) | |
| 3.70 | Implement filtering and route redistribution | |
| 4.00 | Implement MPLS Layer 3 VPNs | |
| 4.10 | Implement Multiprotocol Label Switching (MPLS) | |
| 4.20 | Implement Layer 3 virtual private networks (VPNs) on provider edge (PE), provider (P), and customer edge (CE) routers | |
| 4.30 | Implement virtual routing and forwarding (VRF) and Multi-VRF Customer Edge (VRF-Lite) | |
| 5.00 | Implement IP Multicast | |
| 5.10 | Implement Protocol Independent Multicast (PIM) sparse mode | |
| 5.20 | Implement Multicast Source Discovery Protocol (MSDP) | |
| 5.30 | Implement interdomain multicast routing | |
| 5.40 | Implement PIM Auto-Rendezvous Point (Auto-RP), unicast rendezvous point (RP), and bootstrap router (BSR) | |
| 5.50 | Implementmulticast tools, features, and source-specific multicast | |
| 5.60 | Implement IPv6 multicast, PIM, and related multicast protocols, such as Multicast Listener Discovery (MLD) | |
| 6.00 | Implement Network Security | |
| 6.01 | Implement access lists | |
| 6.02 | Implement Zone Based Firewall | |
| 6.03 | Implement Unicast Reverse Path Forwarding (uRPF) | |
| 6.04 | Implement IP Source Guard | |
| 6.05 | Implement authentication, authorization, and accounting (AAA) (configuring the AAA server is not required, only the client-side (IOS) is configured) | |
| 6.06 | Implement Control Plane Policing (CoPP) | |
| 6.07 | Implement Cisco IOS Firewall | |
| 6.08 | Implement Cisco IOS Intrusion Prevention System (IPS) | |
| 6.09 | Implement Secure Shell (SSH) | |
| 6.10 | Implement 802.1x | |
| 6.11 | Implement NAT | |
| 6.12 | Implement routing protocol authentication | |
| 6.13 | Implement device access control | |
| 6.14 | Implement security features | |
| 7.00 | Implement Network Services | |
| 7.10 | Implement Hot Standby Router Protocol (HSRP) | |
| 7.20 | Implement Gateway Load Balancing Protocol (GLBP) | |
| 7.30 | Implement Virtual Router Redundancy Protocol (VRRP) | |
| 7.40 | Implement Network Time Protocol (NTP) | |
| 7.50 | Implement DHCP | |
| 7.60 | Implement Web Cache Communication Protocol (WCCP) | |
| 8.00 | Implement Quality of Service (QoS) | |
| 8.10 | Implement Modular QoS CLI (MQC) | |
| (a) Network-Based Application Recognition (NBAR) | ||
| (b) Class-based weighted fair queuing (CBWFQ), modified deficit round robin (MDRR), and low latency queuing (LLQ) | ||
| (c) Classification | ||
| (d) Policing | ||
| (e) Shaping | ||
| (f) Marking | ||
| (g) Weighted random early detection (WRED) and random early detection (RED) | ||
| (h) Compression | ||
| 8.20 | Implement Layer 2 QoS: weighted round robin (WRR), shaped round robin (SRR), and policies | |
| 8.30 | Implement link fragmentation and interleaving (LFI) for Frame Relay | |
| 8.40 | Implement generic traffic shaping | |
| 8.50 | Implement Resource Reservation Protocol (RSVP) | |
| 8.60 | Implement Cisco AutoQoS | |
| 9.00 | Troubleshoot a Network | |
| 9.10 | Troubleshoot complex Layer 2 network issues | |
| 9.20 | Troubleshoot complex Layer 3 network issues | |
| 9.30 | Troubleshoot a network in response to application problems | |
| 9.40 | Troubleshoot network services | |
| 9.50 | Troubleshoot network security | |
| 10.00 | Optimize the Network | |
| 10.01 | Implement syslog and local logging | |
| 10.02 | Implement IP Service Level Agreement SLA | |
| 10.03 | Implement NetFlow | |
| 10.04 | Implement SPAN, RSPAN, and router IP traffic export (RITE) | |
| 10.05 | Implement Simple Network Management Protocol (SNMP) | |
| 10.06 | Implement Cisco IOS Embedded Event Manager (EEM) | |
| 10.07 | Implement Remote Monitoring (RMON) | |
| 10.08 | Implement FTP | |
| 10.09 | Implement TFTP | |
| 10.10 | Implement TFTP server on router | |
| 10.11 | Implement Secure Copy Protocol (SCP) | |
| 10.12 | Implement HTTP and HTTPS | |
| 10.13 | Implement Telnet | |
| 11.00 | Evaluate proposed changes to a Network | |
| 11.01 | Evaluate interoperability of proposed technologies against deployed technologies | |
| (a) Changes to routing protocol parameters | ||
| (b) Migrate parts of a network to IPv6 | ||
| (c) Routing Protocol migration | ||
| (d) Adding multicast support | ||
| (e) Migrate spanning tree protocol | ||
| (f) Evaluate impact of new traffic on existing QoS design | ||
| 11.02 | Determine operational impact of proposed changes to an existing network | |
| (a) Downtime of network or portions of network | ||
| (b) Performance degradation | ||
| (c) Introducing security breaches | ||
| 11.03 | Suggest Alternative solutions when incompatible changes are proposed to an existing network | |
| (a) Hardware/Software upgrades | ||
| (b) Topology shifts | ||
| (c) Reconfigurations |
Subscribe to:
Posts (Atom)