Differences

This shows you the differences between two versions of the page.

--- network_stuff:juniper:qfx [2021/03/19 11:32] – jotasandoku
+++ network_stuff:juniper:qfx [2024/09/25 14:18] (current) – jotasandoku
@@ Line 15: / Line 15: @@
 **MC-LAG**\\
-[[https://jira.oracledatacloud.com/browse/SYS-5112]]
+[[https://jira.mycompany2datacloud.com/browse/SYS-5112]]
   * Configuration with examples: [[https://www.juniper.net/documentation/en_US/release-independent/nce/information-products/pathway-pages/nce/nce-mc-lag-qfx-series.pdf|External Link]]
@@ Line 22: / Line 22: @@
       * Inter-chassis Control Protocol (ICCP): It uses TCP as a transport protocol and requires Bidirectional Forwarding Detection (BFD) for fast convergence
       * Interchassis link-protection link (ICL-PL) : Each ICL can learn up to 512K MAC addresses.
+    * *Consistency tools* (require 'set multi-chassis mc-lag consistency-check') [[https://www.juniper.net/documentation/us/en/software/junos/mc-lag/topics/topic-map/examples-mc-lag.html|LINK]]
@@ Line 73: / Line 74: @@
   show ospf database router lsa-id 148.64.56.250 detail
   show ospf database external lsa-id 0.0.0.0 detail
 ----
-**EVPN AND VXLAN**\\
-MAC addresses conveyed via bgp. Datacenter. At the end of the day these are knobs to avoid using L3!. Listen to this [[https://thenetworkcollective.com/2019/01/hon-evpn/|podcast]]
-  * ESI—An Ethernet segment must have a unique nonzero identifier, called the Ethernet segment identifier (ESI). The ESI is encoded as a 10-octet integer. When manually configuring an ESI value, the most significant octet, known as the type byte, must be 00. When a single-homed CE device is attached to an Ethernet segment, the entire ESI value is zero. The Ethernet segment of the multihomed Device CE1 has an ESI value of 00:11:22:33:44:55:66:77:88:99 assigned. The single-homed Device CE2 has an ESI value of 0.
-  * EVI—An EVPN instance (EVI) is an EVPN routing and forwarding instance spanning all the PE routers participating in that VPN. An EVI is configured on the PE routers on a per-customer basis. Each EVI has a unique route distinguisher and one or more route targets.An EVI is configured on Routers PE1, PE2, and PE3.
-  * Rest of the info in: [[https://www.juniper.net/documentation/en_US/junos/topics/concept/evpn-bgp-multihoming-overview.html]]
-----
 PORT MIRRORING:\\
@@ Line 130: / Line 122: @@
   set snmp location Coresite-LA1
-  set snmp contact "sysadmin@grapeshot.co.uk"
+  set snmp contact "sysadmin@mycompany1.co.uk"
   set snmp v3 usm local-engine user ODC authentication-sha authentication-password "XXXXXXXXX"
   set snmp v3 usm local-engine user ODC privacy-aes128 privacy-password "YYYYYYYYYYY"
@@ Line 155: / Line 147: @@
+This is to enable non standard ports for certain devices:
+  [rancid@nms]$ cat .cloginrc
+  add password fw0* {} {}
+  add user * rancid
+  add password * password
+  add identity * /var/rancid/.ssh/rancid_rsa
+  add method csw3.la1.mycompany1.co.uk {ssh:1023}
+  add method csw4.la1.mycompany1.co.uk {ssh:1024}
+  add method {ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no}
+  add method {ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no}
+  add method * ssh
+  add noenable fw0* {0}
+  add cyphertype fw0*.dc.mycompany1.co.uk aes256-cbc
+----
+__AIRFLOW / FANS__
+\\
+  * AFI (AIR FLOW IN)  - Port-side intake (PI)  -  refers to the airflow direction where the air is drawn from the **front** (fan side) and exhausted out the **back** (ports side).
+  * AFO (AIR FLOW OUT) - Port-side exhaust (PE) -  refers to the airflow direction where the air is drawn from the **back** of the device (ports side) and exhausted out the **front** (fan side).
+{{:network_stuff:juniper:airflow.png?400|}}

dokucama

User Tools

Site Tools

Differences

Page Tools