Please enable JavaScript.

Coggle requires JavaScript to display documents.

M1 hardware - Coggle Diagram

- - - - for APIC to switch remote access such as SSH
      - address pool for TEP
        
        belong to overlay-1
        
        this is infra VRF
        
        Should not overlap with other subnet
        
        Please change if overlap with other subnet
        
        The min subnet mask length supported subnet for a three-APIC is /23
  - - - show in lab 1
  - - - used to encapsulate fraffic in VLXAN to vswitch
      - Physical TEP
        
        As source IP before leaf switch send to others
    - - VLAN
        
        Infrastructure VLAN for the
        
        APIC to switch communication,
        
        including virtual switches.
    - - alid range: 225.0.0.0/15 to
        
        231.254.0.0/15 (prefix length must be /15
      - IP addresses used for fabric
        multicast.
    - - IP address that you use to
        
        access the APIC through the
        
        GUI, CLI, or API.
    - - After an ID is assigned, it cannot be updated. The switch name can be updated
      - It is recommended that leaf nodes and spine nodes be numbered differently. For
        
        example, you can number spines in the 200 range and number leaf switches in the 100
- - - - he Remote Leaf Multicast TEP Interface (rl-mcast-hrep)
  - - - requirement
        
        VMware vCenter running 6.0 or 6.5
        
        • Minimum 2 ESXI host for
        
        management cluster (vToR &
        
        vSpine)
  - - - ■ Multicast BiDir PIM (needed to handle Layer 2 broadcast, unknown unicast, and
        
        multicast traffic)
        
        ■ The OSPF protocol must be used to peer with the spine nodes and learn VTEP
        
        reachability
        
        ■ Jumbo MTU support (9150B) to handle VXLAN encapsulated traffic
        
        ■ DHCP-Relay
        
        ■ 50ms RTT
  - - - ACI Multi-Site Orchestrator pushes cross-fabric config to all clusters
      - No latency requirement
      - ACI Multi-Site introduced from release 3.0(1)
        
        • Support all ACI leaf switches (1st Generation, -EX and -FX)
        
        • Only –EX spine (or newer) to connect to the ISN
        
        • New 9364C/9332C non modular spine
        
        (64/32 40G/100G ports) also supported
        
        • 1st generation spines (including 9336PQ)
        
        not supported
        
        • Can still leverage those for intra-site leaf
        
        to leaf communication
    - - orchestrator cluster diagram
- - - - The system waits an interval of time before raising it.
    - - Fabric > Fabric Policies > Policies > Monitoring > Common Policy > Fault Lifecycle Policy.
- - - - 4 ports
        
        2 poert form bond 0 (ethe-1)
        
        1 active & 1 standby
        
        2 ports form bond 0 (eth2-2)
        
        1 active and 1 standy
        
        both bond 0form etherchannel
        
        10/25G
        
        bond means ether channel
        
        Only 1 connectins is allow for each pair
        
        Connect 1 cable either port 1 or port 2
        
        Another connection etiher port 3 or port 4
      - Bond 1
        
        1/10G port speed
        
        for out of band
    - - M3/L3
        
        L3 > than 1200 edge ports
        
        M3 up to 1200 edge ports
        
        cluster
        
        2 type
        
        M3 and L3
      - Standby Controller
        
        can manually switch to replace
        
        Optional; Means if active fail, the failed APIC can be replaced
        
        Recommended
      - can 't have even number of APIC
    - - spine switch
        
        port label green support wire-rate MACsec enry
      - fixed leaf
        
        93180
        
        port 25, 27, 29, 30, 31 can be configured as 40/100G
      - part number meaning
        
        https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/hw/n9k_taxonomy.html
    - - 1st geneartion
        
        Depending on where traffic needs to be mirrored, a
        different ASIC might do the traffic encapsulation; for example, Broadcom ASICs control the server-facing leaf ports, and Cisco ASICs control the network-facing leaf uplink ports
        as well as the spine ports.
    - - requirement is RTT is 50 ms; multi-site no latency requirement
    - - Both leaf and spine siupport 400G
    - - can support 40and 100G uplink
- - - - distinguish name
        
        ID of the object
    - - F0467 usually comes when pool - physical domain - AAEP mismatched.
      - https://quickview.cloudapps.cisco.com/quickview/bug/CSCvt02685
    - - https://your_apic_ip_address/
        visore.html (
      - youtube
        
        https://www.youtube.com/watch?v=zwkhD-CflF0
- - - - ■ 0% to 32%: red
      - ■ 33% to 65%: yellow
      - ■ 66% to 100%: green
    - - one EPG is configured on four different physical ports go down and it will change the H.S from 100% to 75%
      - It will affect the H.S of application profile and tenant