Differences

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

--- network_stuff:cisco:nxos [2021/09/02 20:26] – jotasandoku
+++ network_stuff:cisco:nxos [2023/11/02 14:38] (current) – external edit 127.0.0.1
@@ Line 21: / Line 21: @@
   * 2K (aka FEX or Fabric Extensor)
   * 7K (Only >7k support MPLS)
-  * 9K this model was specifically designed for ACI.9500  platform modular, 9300 platform fixed-configuration.
+  * [[https://www.cisco.com/c/en/us/products/switches/nexus-9000-series-switches/datasheet-listing.html|9K]] : 9500  platform modular, 9300 platform fixed-configuration.
     * 9300 is EOLed
-      * 93108TC-EX
+    * N9K-C93180-EX/FX (25G generation): SoC switch (1U). Note 180 comes from 1.8Tbps line rate
+    * 9336C-FX2-E (100G generation) 7.2 Tbps
+    * N9K-C93240-FX2
     * 9504 : Now is not strictly needed for ACI, we can use for general purpose.
-      * 9516
+      * 9516 (x21 RUs )
   * UCS (rack of blades)
   * CSR 1000V
+Tables to check in the specs sheet:\\
+ **MAC (dynamic Mac learning) ; ARP-ND-ICMP ; Forwarding  ; RIB (unicast/multicast)**. Check these [[https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/92x/scalability/guide_923/b_Cisco_Nexus_9000_Series_NX-OS_Verified_Scalability_Guide_923.html|verified-limits]]\\
+**Layer-2** , Layer-3(host routes + mcast) , LPM(longest prefix match, for ipv4 and ipv6 Entries)
+\\
+\\
 More accessible: C200 (this is just a Cisco server)  and run Nexus 1000v, VSM
 \\
 **__ARCHITECTURE TERMS__**
-  * UPC: unified port controllers ("behind the ports"). Data plane. unified crossbar fabric (UCF) ross-connects the UPCs
+  * UPC: unified port controllers ("behind the ports"). Data plane. unified crossbar fabric (UCF) cross-connects the UPCs
   * SUP
   * SFM: Switch fabric mode determines the speed of a single fabric link between UPC and Fabric.
@@ Line 74: / Line 85: @@
 Cisco UFT (Unified Fabric Technologies):
+----
+MAINTENANCE:\\
+Eg: for a line card replacement.
+graceful insertion and removal (GIR) [[https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/7-x/system_management/configuration/guide/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x/b_Cisco_Nexus_9000_Series_NX-OS_System_Management_Configuration_Guide_7x_chapter_011101.html|External Link]]
+  NET-5587
+  snapshot create PRE-WORKS linecard-replacement
+  conf
+  system mode maintenance
+  ! works
+  conf
+  no system mode maintenance
+  snapshot create POST-WORKS linecard-replacement
@@ Line 199: / Line 226: @@
 **__Fabric Path:__**
-**ISIS** works behind the scenes in L2 FabP. It uses a control plane which is used in FabP unicast, mcast and anycast.
+**IS-IS** works behind the scenes in L2 FabP. It uses a control plane which is used in FabP unicast, mcast and anycast.
     TCN are used to pass the topology from the adjacent STP domains
 Classic VLANs vs FP VLANs
@@ Line 347: / Line 374: @@
   ! Double check line card support matrix
-----
-**FC - Fibre Channel**
-F ports, M ports
-MDS devices
-**VSAN**
-[[https://supportforums.cisco.com/document/130761/san-zoning-guidelines-nexus|Zoning]]\\
-Collection of ports that can communicate between them over the SAN. Recommended to define a zone per initiator and target, and deploy multiple small zones, rather than having larger zones defined as they consume more resources \\
-\\
-**Soft zoning:** (Software) Name server (FCNSto allow devices connect to FC) to reply with all devices registered to that zone.
-**Hard zoning:** (Hardware): Access through access list ACL
-\\
-**Zone membership**
-\\
-**Concept of VSAN**
-**How to setup**
-\\
-{{ :network_stuff:cisco:vsanvszone_table.png?550|}}
-  sh int brief  OR show interface fc1/5
-Besides the classical up, down we have:
-  *     init: initializing, the interface can be stuck in this state
-  *     inactive: vlan suspended/deleted
-  *     isolated: genrally due to a parameter mismatch
-  *     link failure: phy down
-  show flogi database vsan
-  show fcns database vsan {~dns but for the interface names. For a switch to join the fabric)
-  show fc-timer
-**NPiv** as a technology allows to assign several End point id / fc ids to a host port
-E-port troubleshooting \\
-MDS -FC->Cisco port analyzer (take FC traffic and encapsulates the traffic in ethernet to be sent to the wireshark machine)
-**FCoE:**
-    Jumbo frames
-    Map FC ids to MAC
-    Special (unique) vdc
-    FCForwarders: Encap and decap of FC traffic for FCoE
-    FCoE 0x8906
-    STP type: MSTP
-**CoS (Cisco Fabric Services)**
-Basically a way to propagates and synchronise the configurations
-show cfs application/peers/lock
 ----
 **See also:**:\\
@@ Line 465: / Line 440: @@
 pong : uses ptp to measure latency
+\\
+  show forwarding route 10.50.200.0  ! instead of 'show ip cef'
 ----
 **NAPALM (python)**\\
 [[https://github.com/jotasantos/ansible-eveng/tree/main/mgmt-dhcp]]
@@ Line 480: / Line 462: @@
   device_nxos
 ----
 **ANSIBLE**\\
 TODO
+----
+**FC - Fibre Channel**
+F ports, M ports
+MDS devices
+**VSAN**
+[[https://supportforums.cisco.com/document/130761/san-zoning-guidelines-nexus|Zoning]]\\
+Collection of ports that can communicate between them over the SAN. Recommended to define a zone per initiator and target, and deploy multiple small zones, rather than having larger zones defined as they consume more resources \\
+\\
+**Soft zoning:** (Software) Name server (FCNSto allow devices connect to FC) to reply with all devices registered to that zone.
+**Hard zoning:** (Hardware): Access through access list ACL
+\\
+**Zone membership**
+\\
+**Concept of VSAN**
+**How to setup**
+\\
+{{ :network_stuff:cisco:vsanvszone_table.png?550|}}
+  sh int brief  OR show interface fc1/5
+Besides the classical up, down we have:
+  *     init: initializing, the interface can be stuck in this state
+  *     inactive: vlan suspended/deleted
+  *     isolated: genrally due to a parameter mismatch
+  *     link failure: phy down
+  show flogi database vsan
+  show fcns database vsan {~dns but for the interface names. For a switch to join the fabric)
+  show fc-timer
+**NPiv** as a technology allows to assign several End point id / fc ids to a host port
+E-port troubleshooting \\
+MDS -FC->Cisco port analyzer (take FC traffic and encapsulates the traffic in ethernet to be sent to the wireshark machine)
+**FCoE:**
+    Jumbo frames
+    Map FC ids to MAC
+    Special (unique) vdc
+    FCForwarders: Encap and decap of FC traffic for FCoE
+    FCoE 0x8906
+    STP type: MSTP
+**CoS (Cisco Fabric Services)**
+Basically a way to propagates and synchronise the configurations
+show cfs application/peers/lock
+----
+__IS-IS PROTOCOL__
+\\
+Sample configuration:
+  interface loopback0
+    ip address 10.0.1.1 255.255.255.255
+    ip router isis
+    ipv6 address FEC0::CCCC:1/128
+    ipv6 router isis
+  !
+  interface et1/1
+    description Link to P router
+    ip address 10.0.7.9 255.255.255.252
+    ip router isis
+    ipv6 enable
+    ipv6 router isis
+  !
+  router isis
+    net 49.0000.0000.cccc.0001.00
+    metric-style wide [transition]
+    address-family ipv6
+      multi-topology [transition]

dokucama

User Tools

Site Tools

Differences

Page Tools