Tagged: Cisco

0

Cisco NS-OS: Virtual eXtensivle LAN (VXLAN) Overview

VXLAN is a tunneling protocol that encapsulates Layer 2 Ethernet frames in Layer 3 UDP packets. Why VXLAN: VLAN Scalability  – expands VLAN name space VLANs use 12 bit -4096 values VXLAN uses 24 bit – 16777216 values allows layer 2 multipathing no STP uses layer 3 ECMP over CLOS fabric (like FabricPath) allows for multi-tenancy separate of customer traffic over shared...

0

Cisco UC: ISR box-to-box REDundancy

The Interchassis High Availability feature (box-to-box redundancy) enables the configuration of pairs of routers to act as backup for each other. Failover: the standby router seamlessly takes over and starts processing call signaling and performing media forwarding tasks. Note: failover causes reboot by design. Configuration on ISR 4000 series Enable CUBE and redundancy on both routers: Configure an redundancy group with...

0

Cisco UC: PRTG and SIP calls

I found several ways monitoring SIP calls in PRTG using SNMP. Monitor active calls using SIP legs/2 Monitor each dial-peer separately and combine them in the Sensor Factory Just monitor multiple OIDs in one Sensor Enable SNMP on the CUBE: 1. Monitor active calls using SIP legs Idea: check how many SIP legs on the voice gateways (show call active voice...

0

Cisco NX-OS: FabricPath (FP)

FabricPath (FP) is a L2 Routing = “MAC-in-MAC” Routing. FabricPath is Cisco proprietary and works in the same way as TRILL (Transparent Interconnection of Lots of Links) that is an IETF standard. FP: to remove STP from the topology vPC: only 2 switches FP: full mesh, partial mesh, triangle, square etc Components: Classical Ethernet (CE) regular ethernet with regular flooding, regular...

4

Cisco NX-OS: vPC & Failures

vPC Orphan Ports – Traffic from remote Orphan is allowed over Peer Link and exit via local Member– Traffic from remote Member is allowed over Peer Link and exit via local Orphan-Orphans ports should be avoided at all costs because PL is a bottleneck of the system Ideal: vPC Peers only have vPC Member Ports and all downstream devices are dual...

0

Cisco NX-OS: vPC & FHRP

FHRP acts as active/active forwarding over vPC: traffic received in vPC Member Port of FHRP Standby to FHRP Virtual MAC is not forwarded over Peer Link to Active FHRP – essentially HSRP Standby acts as HSRP Active peer-gateway allows to proxy not only virtual active MAC address but also to proxy physical primary MAC address (in case destination MAC address is...

0

Cisco NX-OS: From vPC to Back-to-Back vPC

The vPC Peer Link should never be blocking because this link carries important traffic such as the Cisco Fabric Services over Ethernet (CFSoE) Protocol. The peer link is always forwarding. STP from SW8 and SW9: STP from NXOS1 and NXOS2: In the correct design, the vPC Peer Link should be used only in case of failure. All links are up and...

0

Cisco NX-OS: vPC Configuration

vPC Order of Operations IP connectivity for Peer Keepalive Enable vPC & LACP globally Create vPC domain define Peer Keepalive address configure vPC role priority (Optional) – lower priority => vPC primary switch. (default 32667) Establish Port Channel for vPC Peer link Verify vPC Consistency Parameters Disable vPC Member Port (optional but recommended) Configure vPC Member Ports Enable vPC Member Ports...

0

Cisco NX-OS: Virtual Port Channel (vPC)

Three Main Types of MCEC (Multi Chassis EtherChannel) C3750 Cross Stack Port Channels (StackWise) single control plane C6500 Virtual Switching System (VSS) single control plane via Virtual Switch Link (VSL) Nexus Virtaul Port Channel (vPC) separate control planes separate control plane protocol instances (STP/IGPs/BGP/FHRP) via a Peer Link (like VSS’s VSL) Each vPC peer has Peer Link to sync control plane...

0

Cisco NX-OS: FEX Designs

1. Basic topology: 2. Host Port-Channel: 3. vPC Implementation problem – configuration must be synced between different control planes: config sync command 4. Dual vPC or EvPC – Enhanced vPC – only N5K 5. N7K