Changes between Version 20 and Version 21 of ipv6v4config
- Timestamp:
- May 14, 2017, 2:53:25 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ipv6v4config
v20 v21 58 58 Router(config)# 59 59 }}} 60 '''note:''' If you get following error on !BorderRt, 61 {{{ 62 %Error opening tftp://255.255.255.255/AccessRt-confg (Timed out) 63 }}} 64 Give the following command in the config mode 65 {{{ 66 no service config 67 }}} 60 68 61 69 You can now start making configurations. 62 - First thing you have to add is the hostname of the device. Hostname is the device's identification. In this Lab device name is the same as host name. (Eg. CampusCore switch's hostname isCampusCore). Use the following command70 - First thing you have to add is the hostname of the device. Hostname is the device's identification. In this Lab device name is the same as host name. (Eg. !CampusCore switch's hostname is !CampusCore). Use the following command 63 71 {{{ 64 72 hostname <device name> … … 327 335 ==== Core Network Layer==== 328 336 329 Let's start Configuring the connectivity between core network (!CampusCore, FacACore and FacBCore). We will start from CampusCore.330 331 - Login to CampusCore device. Give your console port password (class password)337 Let's start Configuring the connectivity between core network (!CampusCore, FacACore and FacBCore). We will start from !CampusCore. 338 339 - Login to !CampusCore device. Give your console port password (class password) 332 340 - Go to config mode from user mode. Give your enable password (class password) 333 341 - Core network runs on VLAN 2. Create VLAN 2 and name it '''Core''' … … 367 375 }}} 368 376 369 - You have successfully configured the CampusCore device for you core networks connectivity. Let's move on to FacACore device.377 - You have successfully configured the !CampusCore device for you core networks connectivity. Let's move on to FacACore device. 370 378 {{{ 371 379 FacACore(config)# vlan 2 … … 399 407 - Finally Verify the connectivity 400 408 * Go to FacACore device 401 * Go to privileged mode and ping CampusCore and FacBCore409 * Go to privileged mode and ping !CampusCore and FacBCore 402 410 {{{ 403 411 ping 10.0.2.1 … … 501 509 ==== Connecting LAN to the Router ==== 502 510 503 Your Campus LAN is connecting to the outside through a border router. Your CampusCore switch connects to this border router. In this link router's fast ethernet interface IP connects with the Core switch's vlan interface IP. Let's start configuring this link starting from theCampusCore.504 505 - Login to CampusCore switch and switch to config mode511 Your Campus LAN is connecting to the outside through a border router. Your !CampusCore switch connects to this border router. In this link router's fast ethernet interface IP connects with the Core switch's vlan interface IP. Let's start configuring this link starting from the !CampusCore. 512 513 - Login to !CampusCore switch and switch to config mode 506 514 - Create VLAN 255 and name it Public 507 515 {{{ … … 524 532 CampusCore(config-if)#exit 525 533 }}} 526 - Now you have done CampusCore configuration. Let's start routers Configuration.527 - Login to BorderRt Router and switch to config mode534 - Now you have done !CampusCore configuration. Let's start routers Configuration. 535 - Login to !BorderRt Router and switch to config mode 528 536 - Router's IP allocation is as follows. You can get your Router's IP address from here 529 537 ||= Interface Name =||= IP Address =|| … … 546 554 BorderRt(config-if)#exit 547 555 }}} 548 - You have successfully finished connecting CampusCore to theBorderRt router. Let's verify the connectivity using the ping command.549 - Go to BorderRt and ping toCampusCore switch's VLAN 255 Interface IP556 - You have successfully finished connecting !CampusCore to the !BorderRt router. Let's verify the connectivity using the ping command. 557 - Go to !BorderRt and ping to !CampusCore switch's VLAN 255 Interface IP 550 558 {{{ 551 559 ping 10.0.255.253 … … 558 566 559 567 ==== Routing ==== 560 If You go to the Dept1PC and try a Ping to Dept2PC (10.0.20.1) and BorderRt router LAN port(10.0.255.254), you will not get a reply. That is because your LAN has no routing in it. In this Lab we will enable OSPF in all the core switches and we will add default routes in all core devices and the router.568 If You go to the Dept1PC and try a Ping to Dept2PC (10.0.20.1) and !BorderRt router LAN port(10.0.255.254), you will not get a reply. That is because your LAN has no routing in it. In this Lab we will enable OSPF in all the core switches and we will add default routes in all core devices and the router. 561 569 562 570 - Following are the default routes of the devices 563 571 ||= Device =||= Default Route IP =||= Description =|| 564 || BorderRt || 192.248.6.254 || This is Configured in the router in the Lab ||565 || CampusCore || 10.0.255.254 ||BorderRt routers LAN interface IP ||566 || FacACore || 10.0.2.1 || CampusCore Switches VLAN2 Interface IP ||567 || FacBCore || 10.0.2.1 || CampusCore Switches VLAN2 Interface IP ||572 || !BorderRt || 192.248.6.254 || This is Configured in the router in the Lab || 573 || !CampusCore || 10.0.255.254 || !BorderRt routers LAN interface IP || 574 || FacACore || 10.0.2.1 || !CampusCore Switches VLAN2 Interface IP || 575 || FacBCore || 10.0.2.1 || !CampusCore Switches VLAN2 Interface IP || 568 576 || Dept1PC || none || This is a L2 device || 569 577 || Dept2PC || none || This is a L2 device || 570 578 || Dept1PC || 10.0.10.254 || FacACore Switches VLAN10 Interface IP || 571 579 || Dept2PC || 10.0.20.254 || FacBCore Switches VLAN20 Interface IP || 572 - Now let's enable OSPF on Core devices. Starting from CampusCore573 * Login to CampusCore switch and switch to config mode580 - Now let's enable OSPF on Core devices. Starting from !CampusCore 581 * Login to !CampusCore switch and switch to config mode 574 582 * Define OSPF process and Process ID. In this lab use process ID as 1 575 583 {{{ … … 595 603 CampusCore(config-if)# exit 596 604 }}} 597 * Now you have enable OSPF on CampusCore Switch. Now lets add the default Route.605 * Now you have enable OSPF on !CampusCore Switch. Now lets add the default Route. 598 606 {{{ 599 607 CampusCore(config)# ip route 0.0.0.0 0.0.0.0 10.0.255.254 … … 634 642 }}} 635 643 * Both should give you a reply 636 - add the BorderRt Routers default gateway637 * Go to BorderRt and switch to config mode644 - add the !BorderRt Routers default gateway 645 * Go to !BorderRt and switch to config mode 638 646 * Add the default route 639 647 {{{ 640 648 CampusCore(config)# ip route 0.0.0.0 0.0.0.0 192.248.6.254 641 649 }}} 642 * Verify the route by ping a known host from the BorderRt router650 * Verify the route by ping a known host from the !BorderRt router 643 651 {{{ 644 652 ping 192.248.1.161 … … 648 656 649 657 ==== Router Configuration ==== 650 Now you have complete most of the IPv4 Configurations. Go to DeptPC1 and try a ping to the DNS server (192.248.1.161). You will not get a reply. That is because your PC have a private IP. There must be a method to connect to the outside using a private IP. What we use here is adding a NAT in BorderRt router. There are different NAT types what we use here is the method called NAT overload. In this method we can assign set of local(private) IP's and overload it to a interface with a global(public) IP. So the outside the network will see the traffic coming from local IP's as traffic coming from the global IP. Let's add this configuration to your router.651 - Login to BorderRt Router and switch to config mode658 Now you have complete most of the IPv4 Configurations. Go to DeptPC1 and try a ping to the DNS server (192.248.1.161). You will not get a reply. That is because your PC have a private IP. There must be a method to connect to the outside using a private IP. What we use here is adding a NAT in !BorderRt router. There are different NAT types what we use here is the method called NAT overload. In this method we can assign set of local(private) IP's and overload it to a interface with a global(public) IP. So the outside the network will see the traffic coming from local IP's as traffic coming from the global IP. Let's add this configuration to your router. 659 - Login to !BorderRt Router and switch to config mode 652 660 - Let's define the local IP set in a ACL. 653 661 {{{ 654 662 BorderRt(config)#access-list 1 permit 10.0.0.0 0.0.255.255 655 663 }}} 656 - Then dd the NAT entry. In your router public IP is assign to FastEthernet 0/1 interface664 - Then dd the NAT entry. In your router public IP is assign to !FastEthernet 0/1 interface 657 665 {{{ 658 666 BorderRt(config)#ip nat inside source list 1 interface FastEthernet0/1 overload … … 667 675 BorderRt(config-if)#exit 668 676 }}} 669 - Finally add a static route in the router so that the traffic coming to our defined network will redirect to CampusCore switch677 - Finally add a static route in the router so that the traffic coming to our defined network will redirect to !CampusCore switch 670 678 {{{ 671 679 BorderRt(config)#ip route 10.0.0.0 255.255.0.0 10.0.255.253
