cisco_for_dummies_cheat_sheet
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
cisco_for_dummies_cheat_sheet [2016/10/20 16:05] – walkeradmin | cisco_for_dummies_cheat_sheet [2016/10/20 16:33] – walkeradmin | ||
---|---|---|---|
Line 8: | Line 8: | ||
interface, configure a switch management interface, and configure an interface to use DHCP for your | interface, configure a switch management interface, and configure an interface to use DHCP for your | ||
Cisco network. | Cisco network. | ||
+ | \\ | ||
\\ | \\ | ||
===== Configuration modes for Cisco networking ===== | ===== Configuration modes for Cisco networking ===== | ||
Line 14: | Line 15: | ||
\\ | \\ | ||
\\ | \\ | ||
- | User EXEC mode: | + | **User EXEC mode:** |
\\ | \\ | ||
- | When you connect to a Cisco device the default configuration mode is user exec mode. With user exec | + | When you connect to a Cisco device the default configuration mode is |
- | | + | |
+ | | ||
mode because the IOS prompt displays a “>”. | mode because the IOS prompt displays a “>”. | ||
\\ | \\ | ||
- | Privileged EXEC mode: | + | **Privileged EXEC mode:** |
\\ | \\ | ||
- | In order to make changes to the device you must navigate to Privileged EXEC mode where you may be | + | In order to make changes to the device you must navigate to Privileged |
- | | + | |
+ | | ||
\\ | \\ | ||
- | Global Configuration mode: | + | **Global Configuration mode:** |
\\ | \\ | ||
Global Configuration mode is where you go to make global changes to the router such as the hostname. | Global Configuration mode is where you go to make global changes to the router such as the hostname. | ||
Line 31: | Line 34: | ||
“conf t” where you will be placed at the “(config)# | “conf t” where you will be placed at the “(config)# | ||
\\ | \\ | ||
- | Sub Prompts: | + | **Sub Prompts:** |
\\ | \\ | ||
There are a number of different sub prompts from Global Configuration mode you can navigate to such | There are a number of different sub prompts from Global Configuration mode you can navigate to such | ||
Line 85: | Line 88: | ||
</ | </ | ||
\\ | \\ | ||
+ | ===== Creating a VLAN for Cisco Networking ===== | ||
+ | \\ | ||
+ | When working with your Cisco network, you may want to separate users into different broadcast domains for | ||
+ | security or traffic reduction. You can do this by implementing VLANs. The following example will create VLAN (VLAN2) and place the ports on a switch (from 1-12) into VLAN2. | ||
+ | \\ | ||
+ | < | ||
+ | Switch1> | ||
+ | Switch1# | ||
+ | Switch1(config)# | ||
+ | Switch1(config-if)# | ||
+ | Switch1(config-if)# | ||
+ | Switch1(config)# | ||
+ | Switch1(config-if-range)# | ||
+ | Switch1(config-if-range)# | ||
+ | </ | ||
+ | \\ | ||
+ | If you are connecting two switches together, then you will want to allow all configured VLANs to pass | ||
+ | between the two switches. This is accomplished by implementing a trunk port. To configure port 24 on | ||
+ | your switch to be a trunk port, you will use the following code: | ||
+ | \\ | ||
+ | < | ||
+ | Switch1> | ||
+ | Switch1# | ||
+ | Switch1(config)# | ||
+ | Switch1(config-if-range)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Using EtherChannel for Cisco Networking ===== | ||
+ | \\ | ||
+ | Don’t be afraid to use EtherChannel on your Cisco network. EtherChannel allows you to take up to eight | ||
+ | network ports on your switch and treat them as a single larger link. This can be used to connect servers | ||
+ | with multiple network cards that are bonded (or teamed) to a switch, or to connect multiple switches | ||
+ | together. There are two main negotiation protocols, Port Aggregation Protocol (PAgP) which is a proprietary | ||
+ | Cisco protocol and Link Aggregation Control Protocol (LACP) which is an open standards protocol. | ||
+ | \\ | ||
+ | \\ | ||
+ | To set EtherChannel to use with of the protocols you will configure it to support one of the following modes. | ||
+ | \\ | ||
+ | \\ | ||
+ | * auto: Sets the interface to respond to PAgP negotiation packets, but the interface will start negotiations on its own. | ||
+ | * desireable: Sets the interface to actively attempt to negotiate a PAgP connection. | ||
+ | |||
+ | * on: Forces the connection to bring all links up without using a protocol to negotiate connections. This mode can only connect to another device that is also set to on. When using this mode, the switch does not negotiate the link using either PAgP or LACP. | ||
+ | |||
+ | * active: Sets the interface to actively attempt to negotiate connections with other LACP devices. | ||
+ | |||
+ | * passive: Sets the interface to respond to LACP data if it receives negotiation requests from other systems. | ||
+ | \\ | ||
+ | \\ | ||
+ | The following example will configure EtherChannel to use group ports 11 and 12 on the switch together using PAgP as the protocol. The same type of command would be used on the switch to which Switch1 is connected. | ||
+ | \\ | ||
+ | < | ||
+ | Switch1> enable | ||
+ | Switch1# configure terminal | ||
+ | Switch1(config)# | ||
+ | Switch1(config-if-range)# | ||
+ | Switch1(config-if-range)# | ||
+ | Switch1(config-if-range)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Working with Spanning Tree Protocol for Cisco Networking ====== | ||
+ | \\ | ||
+ | Spanning Tree Protocol (STP) enables you to create redundant loops on your Cisco network for fault | ||
+ | tolerance, and prevents inadvertent loops that may be created on your network from bringing the network to | ||
+ | its knees. | ||
+ | \\ | ||
+ | \\ | ||
+ | The following code will enable the Cisco proprietary Rapid Per VLAN Spanning Tree Protocol (PVST) over the | ||
+ | open standard of Multiple Spanning Tree Protocol (MSTP). In addition to configuring STP on the switch, you | ||
+ | will also configure port 2 on the switch for portfast, which allows the port to immediately transition to forwarding mode. | ||
+ | \\ | ||
+ | < | ||
+ | Switch1> enable | ||
+ | Switch1# configure terminal | ||
+ | Switch1(config)# | ||
+ | Switch1(config)# | ||
+ | Switch1(config-if)# | ||
+ | %Warning: portfast should only be enabled on ports connected to a single | ||
+ | host. Connecting hubs, concentrators, | ||
+ | | ||
+ | Use with CAUTION | ||
+ | %Portfast will be configured in 10 interfaces due to the range command | ||
+ | but will only have effect when the interfaces are in a non-trunking mode. | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Managing Static Routing for Cisco Networking ===== | ||
+ | \\ | ||
+ | When working with your routers on your Cisco network, it’s very likely that you’ll want to have your routers | ||
+ | route data. The first step in having your router pass data from one interface to another interface is to enable routing; just use these commands. | ||
+ | \\ | ||
+ | < | ||
+ | Router1> | ||
+ | Router1# | ||
+ | Router1(config)# | ||
+ | </ | ||
+ | \\ | ||
+ | Whether or not you choose to use a dynamic routing protocol, you may add static routes to your router. The following will add a static route to Router1 to send data to the 192.168.5.0/ | ||
+ | the IP address of 192.168.3.2. | ||
+ | \\ | ||
+ | < | ||
+ | Router1> | ||
+ | Router1# | ||
+ | Router1(config)# | ||
+ | Router1(config)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Managing routing information protocol for Cisco networking ===== | ||
+ | \\ | ||
+ | Routing Information Protocol (RIP) is widely used, with version 2 allowing you to use Variable Length Subnet | ||
+ | Masks (VLSM) across your network. The following code will enable routing, enable RIP, set RIP to version 2, | ||
+ | disable route summarization, | ||
+ | than broadcasting routes, it will send RIP data directly to 192.168.1.1. | ||
+ | \\ | ||
+ | < | ||
+ | Router2> | ||
+ | Router2# | ||
+ | Router2(config)# | ||
+ | Router2(config)# | ||
+ | Router2(config-router)# | ||
+ | Router2(config-router)# | ||
+ | Router1(config-router)# | ||
+ | Router2(config-router)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Managing enhanced interior gateway routing protocol for Cisco networking ===== | ||
+ | Enhanced Interior Gateway Routing Protocol (EIGRP) is the updated version of IGRP. The following code will | ||
+ | enable EIGRP using an autonomous-system (AS) number of 100, distribute two networks and disables auto summary. | ||
+ | \\ | ||
+ | < | ||
+ | Router2> | ||
+ | Router2# | ||
+ | Router2(config)# | ||
+ | Router2(config)# | ||
+ | Router2(config-router)# | ||
+ | Router2(config-router)# | ||
+ | Router2(config-router)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Managing open shortest path first for Cisco networking ===== | ||
+ | \\ | ||
+ | Open Shortest Path First (OSPF) is a link state protocol which is widely used. OSPF uses the address of the loopback interface as the OSPF identifier, so this example will set the address of the loopback interface, | ||
+ | then enable OSPF with a process ID of 100, and distributing a network of 192.168.255.254 and a network of | ||
+ | 192.168. 5.0/24 | ||
+ | \\ | ||
+ | < | ||
+ | Router2> | ||
+ | Router2# | ||
+ | Router2(config)# | ||
+ | Router2(config-if)# | ||
+ | Router2(config-if)# | ||
+ | Router2(config)# | ||
+ | Router2(config-router)# | ||
+ | Router2(config-router)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Viewing Routing Information for Cisco Networking ===== | ||
+ | \\ | ||
+ | After setting up any routing protocol that you want to implement – RIP, OSPF, or EIGRP – you can view all | ||
+ | of your routing information through the ip route command. The following is an example of the output of this command. The output includes a legend showing the codes for each routing protocol, and the specific routes | ||
+ | are identified by the source protocol. | ||
+ | \\ | ||
+ | < | ||
+ | Router2> | ||
+ | Password: | ||
+ | Router2# | ||
+ | Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP | ||
+ | D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area | ||
+ | N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 | ||
+ | E1 - OSPF external type 1, E2 - OSPF external type 2 | ||
+ | i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 | ||
+ | ia - IS-IS inter area, * - candidate default, U - per-user static route | ||
+ | o - ODR, P - periodic downloaded static route | ||
+ | Gateway of last resort is not set | ||
+ | D 192.168.10.0/ | ||
+ | O 192.168.10.0/ | ||
+ | R 192.168.10.0/ | ||
+ | C 192.168.5.0/ | ||
+ | C 192.168.1.0/ | ||
+ | S 192.168.3.0/ | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Securing a Cisco Network ===== | ||
+ | \\ | ||
+ | Security is always a concern, and your Cisco network needs to be properly secured. In the following sections, | ||
+ | you see how to secure your Cisco network by configuring NAT, by configuring an ACL, and by applying that ACL. | ||
+ | \\ | ||
+ | \\ | ||
+ | ===== Securing your Cisco network by configuring NAT ===== | ||
+ | \\ | ||
+ | The following commands are used to configure NAT overload services on a router called Router1. In this | ||
+ | example, a list of source address is created in access list #1, which is then used as the inside source | ||
+ | list. The FastEthernet 0/0 port is the overloaded public address port that all inside addresses get | ||
+ | translated to. | ||
+ | \\ | ||
+ | < | ||
+ | Router1> | ||
+ | Router1# | ||
+ | Router1(config)# | ||
+ | Router1(config)# | ||
+ | Router1(config)# | ||
+ | Router1(config-if)# | ||
+ | Router1(config-if)# | ||
+ | Router1(config-if)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Securing your Cisco network by configuring an access control list (ACL) ===== | ||
+ | \\ | ||
+ | ACLs are used to control traffic flow. They can be used allow or deny the flow of traffic. The two main | ||
+ | types of ACLs are: | ||
+ | \\ | ||
+ | * Standard ACLs, which have fewer options for classifying data and controlling traffic flow than Extended ACLs. They are only able to manage traffic based on the source IP address. These ACLs are numbered from 1–99 and from 1300–1999. | ||
+ | * Extended ACLs, which offer the ability to filter or control traffic based on a variety of criteria such as source or destination IP addresses, as well as protocol type such as, ICMP, TCP, UDP, or IP. These ACLs are numbered from 100–199 and from 2000–2699. | ||
+ | \\ | ||
+ | To create a standard ACL, you can use the following example which will create an ACL that allows traffic for the 192.168.8.0/ | ||
+ | \\ | ||
+ | < | ||
+ | Switch1> | ||
+ | Switch1# | ||
+ | Switch1(config)# | ||
+ | </ | ||
+ | \\ | ||
+ | To create an extended ACL you can use the following example which will create an ACL that allows traffic with addresses in the 192.168.8.0/ | ||
+ | \\ | ||
+ | < | ||
+ | Router1> | ||
+ | Router1# | ||
+ | Router1(config)# | ||
+ | Router1(config)# | ||
+ | Router1(config)# | ||
+ | </ | ||
+ | \\ | ||
+ | ===== Securing your Cisco network by applying an access control list ===== | ||
+ | \\ | ||
+ | After you have created an Access Control List (ACL), such as ACL 101 created above, you can apply that ACL | ||
+ | to an interface. In the following example, this ACL is placed to restrict outbound traffic on FastEthernet0/ | ||
+ | \\ | ||
+ | < | ||
+ | Router1> | ||
+ | Router1# | ||
+ | Router1(config)# | ||
+ | Router1(config-if)# | ||
+ | </ | ||
+ | \\ | ||
+ | \\ |
cisco_for_dummies_cheat_sheet.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1