Show chassic

root@EX2200# show chassis alarm
management-ethernet {
    link-down ignore;
}

root@EX2200# run show chassis ?
Possible completions:
  alarms               Show alarm status
  environment          Show component status and temperature, cooling system speeds
  firmware             Show firmware and operating system version for components
  fpc                  Show Flexible PIC Concentrator status
  hardware             Show installed hardware components
  led                  Show LED status
  location             Show physical location of chassis
  mac-addresses        Show media access control addresses
  nonstop-upgrade      Show nonstop upgrade status
  pic                  Show Physical Interface Card state, type, and uptime
  redundant-power-system  Show redundant power system chassis information
  routing-engine       Show Routing Engine status
  temperature-thresholds  Show chassis temperature threshold settings

 ------------------------------------------------------------------

root@EX2200# run show chassis alarms
No alarms currently active

 ------------------------------------------------------------------

CoS

Forwarding Class

A forwarding class is a label, used entirely within a network node, which is used to identify all traffic that requires a single behavior when leaving that node.
Forwarding classes do not explicitly appear outside a node, although if the QoS configuration of all nodes in a network is consistent, it can easily be derived from information in packet headers.

Classification

Classification is the act of identifying the class to which a packet belongs. It is usually initially performed on ingress to each node, although a packet may be reclassified at various points on its path through a network node.



          Interface Based Classification

If all traffic arriving on a single interface is known to be associated with a single class then the easiest mechanism to classify this traffic is simply to associate all traffic arriving on the interface with the relevant forwarding-class.

class-of-service {
      forwarding-classes {
            class $class_name$ queue $queue_number$;
      }
interfaces {
      $interface_name$ {
            unit $unit_id$ {
                  forwarding-class $class_name$;
                  }
            }
      }
}

Applying Routing Policies

protocols {
     rip {

          import [ policy1 policy2 …];

          group test {
               export [ policy1 policy2 …];

               neighbor fe-0/0/2.0 {
                    import [ policy1 policy2 …];
               }
          }
     }
}

protocols {
     isis {

          export [ policy1 policy2 … ];

     }

     ospf {

          export [ policy1 policy2 … ];

     }

}

OSPF configuration

 Example

[edit protocols ospf]
       user@Chablis# set area 0 interface all
       user@Chablis# set area 0 interface fxp0 disable

[edit protocols ospf]
user@Chablis# show
       area 0.0.0.0 {
              interface all;
              interface fxp0.0 {
                     disable;
       }
}

или на каждый интерфейс

protocols {
    ospf {
        area 0.0.0.0 {
            interface em0.0;
            interface em4.0;
        }
        area 0.0.0.1 {
            interface em1.0;
        }
    }
}

OSPF theory concept

Common Packet Header

RIP configuration

Таймеры протокола

• Update timer — частота отправки обновлений протокола, по истечению таймера отправляется обновление. По умолчанию равен 30 секундам.
• Invalid timer — Если обновление о маршруте не будет получено до истечения данного таймера, маршрут будет помечен как Invalid, то есть с метрикой 16. По умолчанию таймер равен 180 секундам.
• Flush timer (garbage collection timer) — По умолчанию таймер равен 240 секундам, на 60 больше чем invalid timer. Если данный таймер истечет до прихода обновлений о маршруте, маршрут будет исключен из таблицы маршрутизации. Если маршрут удален из таблицы маршрутизации то, соответственно, удаляются и остальные таймеры, которые ему соответствовали.
• Holddown timer — Запуск таймера произойдет после того, как маршрут был помечен как не достижимый. До истечения данного таймера маршрут будет находиться в памяти для предотвращения образования маршрутной петли и по этому маршруту передается трафик. По умолчанию равен 180 секундам. Таймер не является стандартным, добавлен в реализации Cisco.

Routing Policy basic concept

 Composing a Routing Policy

The application of a routing policy is always performed from the perspective of the routing table. Routes being placed into the routing table are said to be “inbound.” 

Routes being extracted from the routing table are said to be “outbound.”

Policy Processing

Each policy contains three possible results:

• accept
• reject
• next policy

Preference Values and Load Balancing

Load Balancing

Hierarchical concept

Routing tables

JUNOS software Routing Tables

The JUNOS software provides multiple routing tables that are used to store routes for your network. Each table is represented within the output of the show route command. The software provides default tables that the operating system builds on an as-needed basis. Each of the default tables contains separate route information.

inet.0
inet.1
inet.2
inet.3
inet.4
inet6.0
mpls.0
bgp.l3vpn.0
bgp.l2vpn.0

Configured Routes. Aggregated, Generated, Martians.

Static Routes

A static route within the JUNOS software is a route to a destination with an assigned next hop.
If we want to place the route into the routing table, the next hop must be valid. This means that the router is able to forward packets using the next hop.

Иерархический концепт

routing-options {
   static {
      defaults {
         static-options;
      }
      route destination-prefix {
         next-hop next-hop;
         qualified-next-hop address {
            metric metric;
            preference preference;
         }
         lsp-next-hop lsp-name {
            metric metric;
            preference preference;
         }
         static-options;
      }
   }
}

Standart Commands, debug, show and test

QSG for work with junipers at cli:

Приводим  cli в привычный рабочий формат

root> set cli terminal vt100

Переходим в конфигурационный режим

root> configure

Interfaces Overview

Types of Interfaces

            Permanent Interfaces

The permanent interfaces on a Juniper Networks platform perform two vital roles:

• Management -- interface fxp0, does not provide forwarding capabilities for transit data packets
• Operation -- interface fxp1 connects the Routing Engine to the Packet Forwarding Engine. This communications link is how routing protocol packets reach the Routing Engine to update the  routing table. The forwarding table updates reach the Packet Forwarding Engine across this interface as well

         

Packet Forwarding Engine Components

The components of the Packet Forwarding Engine fall into two main subsets:
1) Embedded OS software operating the circuit boards themselves
2) ASICs actually participating in packet forwarding.

Command-Line Interface. Modes. Configurations/Candidates. Redundancy.

Operational Mode

user@Merlot>

               Editing Command Lines

user@Merlot> set cli terminal vt100

приводит терминальный сеанс к удобоваримому стандарту для редактирования и работы.

Route Engine, Packet Forwarding Engine and other basic concepts

The central design principle of the Juniper Networks platform centers on a separation of the control and forwarding planes within the router.