Scribd Logo
Upload

Welcome to Scribd!

  • 23 views

    Overview of The Cisco IOSv3

    Uploaded by

    lio messi
    This document provides an introduction to Cisco and Juniper device operating systems, highlighting some key differences. Both provide CLI access and configuration options like SNMP and web interfaces. Juniper configuration uses a more hierarchical structure with code segments while Cisco is flatter. Modes like user exec, privileged exec, and configuration are common to both, though Juniper has a monitor command mode instead of Cisco's debugging. Basic commands for configuring interfaces, routing protocols, and troubleshooting are also outlined.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Overview of The Cisco IOSv3

    Uploaded by

    lio messi
    23 views4 pages
    This document provides an introduction to Cisco and Juniper device operating systems, highlighting some key differences. Both provide CLI access and configuration options like SNMP and web interfaces. Juniper configuration uses a more hierarchical structure with code segments while Cisco is flatter. Modes like user exec, privileged exec, and configuration are common to both, though Juniper has a monitor command mode instead of Cisco's debugging. Basic commands for configuring interfaces, routing protocols, and troubleshooting are also outlined.

    Original Description:

    IOS CIsco

    Original Title

    Overview of the Cisco IOSv3

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides an introduction to Cisco and Juniper device operating systems, highlighting some key differences. Both provide CLI access and configuration options like SNMP and web interfaces. Juniper configuration uses a more hierarchical structure with code segments while Cisco is flatter. Modes like user exec, privileged exec, and configuration are common to both, though Juniper has a monitor command mode instead of Cisco's debugging. Basic commands for configuring interfaces, routing protocols, and troubleshooting are also outlined.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    23 views4 pages

    Overview of The Cisco IOSv3

    Uploaded by

    lio messi
    This document provides an introduction to Cisco and Juniper device operating systems, highlighting some key differences. Both provide CLI access and configuration options like SNMP and web interfaces. Juniper configuration uses a more hierarchical structure with code segments while Cisco is flatter. Modes like user exec, privileged exec, and configuration are common to both, though Juniper has a monitor command mode instead of Cisco's debugging. Basic commands for configuring interfaces, routing protocols, and troubleshooting are also outlined.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 4

    Junos, and Cisco Primer:

    This document provides a quick introduction to Cisco and Juniper devices and provides major points of
    differentiation amongst the software. It is designed for the entry level student but may also be used as
    an introduction to switching between OSes.

    Overview of the switch and router OSes:


    Both Cisco and Juniper provide multiple ways of configuring their devices. These include, command
    line driven OS, SNMP, Web interfaces, and proprietary configuration managers. Physically then these
    can be accessed by both serial port (console access), or network access (HTTP config manager page or
    SSH). It is important that you are familiar with the standard IOS (Cisco OS) which is what is
    conventionally used and will be provisioned for in your working environment. Switches and routers are
    ubiquitous in operation of protocols (hence compatible), and thankfully all* nomenclature and concepts
    are preserved between industry players. For example access lists, routing policy maps, routing
    protocols (bar proprietary protocols that may or may not be of interest) are the same and compatible.
    There are some subtle differences throughout which are generally quite superficial in that you will find
    optional configuration parameters in only one or the other device, and further default values and default
    enabled options will differ between vendors. There are some notable differences that are described in
    the next section.

    Juniper / Cisco general appearance.


    Both IOS and Juniper may be summarized by three modus operandi; configuration, fundamental
    operational based diagnostics, and debugging (a deeper diagnosis of internal device events). The IOS
    and Junos interfaces are both CLIs and similar in many respects, however the look and feel are a little
    different and worth noting. In Cisco the structure is rather flat. SNMP nor AAA configuration for
    example are grouped into logical subsections instead each instruction configurable in global config
    mode. Unlike Cisco, Juniper configuration is a lot more hierarchical. The configuration appears as Clike code segments or XML type structures encased in {}. The hierarchical basis makes the
    configuration a lot more readable than Cisco. All routing falls under the protocols branch all RIP
    configuration lies in the RIP branch in itself within the protocol branch etc.

    Modes and User Orientation


    In both Juniper and Cisco devices there are a set of different modes with which the administrator
    operates; User exec mode, Privilege exec mode, and Configuration mode. The difference between the
    first two are solely due to security. User exec mode enables the user to gather device statistics such as
    version number, and display the system configuration file, along with ping and traceroute tools.
    Privilege exec mode allows some basic control over the physical device, rebooting, resetting
    configuration file, as well as the aforementioned operational diagnostics (such as displaying routing
    tables), and enabling/disabling debugging messages. *All* configuration is performed in config mode
    (including various sub-modes). Instead of debugging (as in Cisco devices), Juniper has a monitor
    command mode in privilege exec.
    In IOS when logged in you begin directly in user exec mode (command prompt >). You can enter
    privileged exec mode with
    >en
    From where you may next access configuration mode with
    (#)config terminal

    To add command lines simply type these. To remove configuration lines prefix the configuration line
    with no.
    To view the running configuration use,
    (#)show running-config
    in priv exec mode. Show may be used to display many other operationally significant diagnostics
    which you will pick up with use.

    The Cisco hierarchy

    Figure 2 and table 1 below provides orientation around IOS and JUNOS summary.

    Configuration files
    In Cisco any configuration that is stated in the command line takes effect immediately (or immediately
    generates an error), however changes will revert to that previous upon a device reboot unless you
    perform write mem in privilege exec.

    Basic setup
    Basic configuration of the Cisco routers we have at the school can be found at,
    http://ecs.victoria.ac.nz/Courses/NWEN403_2011T1/StandardCiscoRouter

    a general summary of basic important commands can be found below


    In what follows is a summary of the most commonly used (IP and Ethernet based) commands available
    to routers. When reading the summary, note the mode details, some are located in the interface mode

    and others in configure (global configuration) mode. This is a reference summary for configuration
    and diagnostics only and does not describe the theory of operation of types.

    Node Admin:
    Reboot system.

    #reload

    Save running config


    to mem.
    Reload config from mem.

    #copy runnning startup

    Clear configuration.

    #clear config all

    #copy startup running

    Basic Router Config:


    Interface Specific:
    Set IP address and netmask

    Config-if# ip address [IP] [Netmask]

    Shutdown/Activate an Interface

    Config-if# shutdown

    Create or edit a VLAN (AKA sub-interface) Config# interface [int#].[sub int #]


    Line speed/duplex/mtu

    Config-if# speed [10|100] / duplex [full | half] / mtu [mtu]

    Static Routing:
    Add static route to route table

    Config# ip route [ip address] [subnet] [next hop address]

    Set default address


    (This is unidirectional!)

    Config# ip route 0.0.0.0 0.0.0.0 [default address]

    View routing table

    # show ip route

    RIP configuration:

    enable classeless routing

    config# ip classless /enable classless

    RIP

    config# router rip


    config# version 2
    config-router# network [network]

    Where the network command allows routing for that network. This should be repeated
    for each network you wish to route between (this may be in a summarised form).
    Clear the route table (restarting RIP):# clear ip route *
    debug:

    # (un)debug ip rip

    IP debugging:
    Illicit response from the stated
    node, to determine whether the
    node is up.

    (en>) ping [ip address]

    Illicit response from every node


    along the route path to the
    destination .

    (en>) traceroute [ip address]

    OSPF:
    Single area OSPF on Cisco/Soekris

    config# router ospf [#] //# can be anything!


    config-router# network [network] area[#]

    Set the outgoing cost of the link.

    config-router# cost #

    *The area should be used on all routers participating in the OSPF process.
    Show:

    # show ip ospf database

    You might also like