четверг, 2 апреля 2015 г.

Juniper Access port

1) Задаём 20-й влан

root@EX4200-1# set vlans v20 vlan-id 20

2)

root@EX4200-1#  set interfaces ge-0/0/18 unit 0 family ethernet-switching port-mode access vlan members v20


Juniper Trunk

1) Cоздаём native vlan

root@EX4200-1#  set vlans v1 vlan-id 1
 2) Переводим в  trunk

 root@EX4200-1# set interfaces ge0/0/14 unit 0 family ethernet-switching  port-mode trunk native-vlan-id 1 vlan members all
















среда, 1 апреля 2015 г.

Junipers L3-interface


1) Создаём VLAN:

root# set vlans <vlan-name> vlan-id <vlan-id> (1..4094)>
root@EX4200-1# set vlans v245 vlan-id 245

2) Создаём vlan.245:

root# set interfaces vlan unit <unit# (0..16385)> family inet address <ip address/mask>
root@EX4200-1# set interfaces vlan unit 245 family inet address 192.168.245.1/24


3) Ассоциируем vlan v245 с L3- интерфейсом vlan.245:

root# set vlans <vlan-name> l3-interface vlan.<unit# mentioned above>
root@EX4200-1# set vlans v245 vlan-id 245 l3-interface vlan.245


4) Ассоциируем vlan v245 с физ интерфейсом ge-0/0/14

root@EX4200-1# set vlans v245 vlan-id 245 interface ge-0/0/14

четверг, 13 ноября 2014 г.

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$;
                  }
            }
      }
}

вторник, 21 октября 2014 г.

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 … ];
     }
}