Category Archives: Routing

Dell Networking OS10 using GNS3

Dell EMC Networking OS10 combines the best of Linux, open computing, and networking to advance open networking disaggregation. OS10 is a transformational software platform which provides networking hardware abstraction through a common set of APIs.
You can enable consistency across compute and network resources for your system operator (sysops) groups that require server-like manageability, as well as leverage your existing network con€guration.
You can simulate OS10 devices using OS10 VM appliances. The OS10 VM appliances execute the same software deployed on OS10-enabled hardware devices, with the exception of the hardware abstraction layer. The OS10 VM hardware abstraction layer simulates hardware devices in a VM environment.

All CLI commands as well as RESTCONF and SNMP interfaces are available in the OS10 simulation environment. You can build sandbox environments to learn open networking concepts, and prototype network operations and scripts risk-free.

Dell OS10

OS10 simulation features

All OS10 CLI commands and north-bound interfaces (RESTCONF, SNMP) are available including:

  • System management (SSH, AAA, DHCP, and so on)
  • Management port

L3 data plane and control plane (using Linux functionality)

Partial support for L2 data plane and control plane (using Linux functionality):

  • LACP
  • VLAN
  • LLDP
  • VLT

OS10 feature limitations

  • No ACL or QoS support (NPU is not available) — ACL and QoS CLI commands are available (but have no effect on trafc)
  • Limited L2 functionality (NPU is not available on simulator) — no spanning-tree control plane functionality
  • No breakout mode for simulated ports
  • Defaults to S6000-ON hardware platform simulation

Requirements

  • Workstation or laptop with 16 GB RAM or larger recommended
  • 64-bit x86 CPU with 2 GHz or faster core speed (dual-core or larger recommended)
  • SDD with 64 GB available space
  • Virtualization environment — you can use either Windows, Linux, or VMware ESXi as a host system for the GNS3 Server VM environment
  • VMware ESXi server recommended for large network simulation

Download

https://cld.pt/dl/download/fff9c764-59cb-4521-8bd9-e9eeb38519c8/os10_virtualization_10.4.1.0v.zip

https://cld.pt/dl/download/2f61626b-f1fe-4415-8825-4357823e5ed8/os10_virtualization_guide.pdf

 

 

Cisco Live Barcelona 2018 here i GO!

This is going to be my 2nd Cisco Live, and i’m very excited because i’ve learned a lot over the past 8 years and i’m in a different professional stage at the moment that 8 years ago it was just a dream. I’m a strong believer that these events are important to grow your “networking” and keep you updated on new trends/technology.

So how my calendar looks like so far?

  • CCDE Techtorial and Exam
  • Firepower
  • ISE
  • Multi-Cloud
  • SD-X
  • DevOps

If you are are around, lets grab a beer and crack some of the topics above

Cisco Catalyst reborn

Cisco announced a new platform, Catalyst 9k (fixed and modular), a new hit for the Enterprise Architecture.

Some of the benefits i’ve captured:

  • Secure segmentation with SD-Access
  • Unmatched 60W POE on every access port
  • DNA Center
  • IoT readiness
  • Cloud readiness
  • IOS-XE
  • UADP 2.0
  • StackWise Virtual
  • IEEE1588
  • MACsec256
  • Encrypted Traffic Analysis (ETA)
  • Licensing mode changed (no info yet)

Catalyst 9300

Catalyst 9400

Catalyst 9500

 

My Recap from Cisco Vegas 2016

Let’s make it clear, i wish to be there! I read really some cool stuff this year in www.ciscolive.com, and i want to share with you my favourite topics:

  • Cisco HyperFlex Systems
  • Cisco Tetration Analytics
  • Cisco Spark
  • Cisco DNA
  • Security Related (Ransomware,etc)

References:

IO Visor Project

BRKCOM-1125 – Hyper-converged Computing

 PSODCN-2375 – Introduction to Cisco HyperFlex Systems )

Cisco Tetration Analytics Data Sheet – Cisco

PSOACI-2100 – Cisco Tetration Analytics: Real-time application visibility and policy management

BRKCOL-2235_Spark Call Extending Spark with Business-Class Communications

BRKSEC-2002 – It’s Cats vs Rats in the Attack Kill Chain!

BRKSEC-2010 – Emerging Threats – The State of Cyber Security

BRKDCT-3001 Leveraging Micro Segmentation to Build Comprehensive Data Center Security Architecture

BGP Free Core

“BGP Free Core” is a typical topology in MPLS Service Provider Networks where you run IGP+Label. This allows traffic to transit over devices which don’t know traffic final destination, instead they look only for labels, bring more performance at the end. MPLS allow applications such as L2VPN, L3VPN and much more.

bgp-free-core

Normal Forwarding

In normal forwarding traffic towards to destination will go hop-by-hop (lookup next-hop) until reach destination

R4#show ip route
Codes: L – local, C – connected, S – static, R – RIP, M – mobile, B – BGP
D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
E1 – OSPF external type 1, E2 – OSPF external type 2
i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
ia – IS-IS inter area, * – candidate default, U – per-user static route
o – ODR, P – periodic downloaded static route, H – NHRP, l – LISP
a – application route
+ – replicated route, % – next hop override

Gateway of last resort is not set

10.0.0.0/8 is variably subnetted, 20 subnets, 2 masks
i L2     10.1.1.1/32 [115/30] via 10.4.12.12, 00:13:18, GigabitEthernet1.412
[115/30] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.1.2.0/24 [115/20] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.1.11.0/24 [115/30] via 10.4.12.12, 00:13:18, GigabitEthernet1.412
[115/30] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.1.12.0/24 [115/20] via 10.4.12.12, 00:15:50, GigabitEthernet1.412
i L2     10.2.2.2/32 [115/20] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
C        10.2.4.0/24 is directly connected, GigabitEthernet1.24
L        10.2.4.4/32 is directly connected, GigabitEthernet1.24
i L2     10.2.11.0/24 [115/20] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.2.12.0/24 [115/20] via 10.4.12.12, 00:13:18, GigabitEthernet1.412
[115/20] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.2.13.0/24 [115/20] via 10.4.13.13, 00:13:18, GigabitEthernet1.413
[115/20] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
C        10.4.4.4/32 is directly connected, Loopback0
C        10.4.12.0/24 is directly connected, GigabitEthernet1.412
L        10.4.12.4/32 is directly connected, GigabitEthernet1.412
C        10.4.13.0/24 is directly connected, GigabitEthernet1.413
L        10.4.13.4/32 is directly connected, GigabitEthernet1.413
i L2     10.11.11.11/32
[115/30] via 10.4.12.12, 00:13:18, GigabitEthernet1.412
[115/30] via 10.2.4.2, 00:13:18, GigabitEthernet1.24
i L2     10.11.12.0/24 [115/20] via 10.4.12.12, 00:15:50, GigabitEthernet1.412
i L2     10.12.12.12/32
[115/20] via 10.4.12.12, 00:15:50, GigabitEthernet1.412
i L2     10.12.13.0/24 [115/20] via 10.4.13.13, 00:15:50, GigabitEthernet1.413
[115/20] via 10.4.12.12, 00:15:50, GigabitEthernet1.412
i L2     10.13.13.13/32
[115/20] via 10.4.13.13, 00:15:50, GigabitEthernet1.413

R4#show ip cef
Prefix               Next Hop             Interface
0.0.0.0/0            no route
0.0.0.0/8            drop
0.0.0.0/32           receive
10.1.1.1/32          10.2.4.2             GigabitEthernet1.24
10.4.12.12           GigabitEthernet1.412
10.1.2.0/24          10.2.4.2             GigabitEthernet1.24
10.1.11.0/24         10.2.4.2             GigabitEthernet1.24
10.4.12.12           GigabitEthernet1.412
10.1.12.0/24         10.4.12.12           GigabitEthernet1.412
10.2.2.2/32          10.2.4.2             GigabitEthernet1.24
10.2.4.0/24          attached             GigabitEthernet1.24
10.2.4.0/32          receive              GigabitEthernet1.24
10.2.4.2/32          attached             GigabitEthernet1.24
10.2.4.4/32          receive              GigabitEthernet1.24
10.2.4.255/32        receive              GigabitEthernet1.24
10.2.11.0/24         10.2.4.2             GigabitEthernet1.24

What is the exact path(or multiple)?

R4#trace 10.1.1.1
Type escape sequence to abort.
Tracing the route to 10.1.1.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.2.4.2 3 msec
10.4.12.12 4 msec
10.2.4.2 3 msec
2 10.1.12.1 3 msec
10.1.2.1 3 msec
10.1.12.1 2 msec

CSR-4#show mpls forwarding-table
no MPLS apps enabled or MPLS not enabled on any interfaces

MPLS Forwarding

On MPLS we have LIB and LFIB. LIB essentially holds all the labels and associated information, while LFIB do the forwarding based on incoming labeled packets. CEF is a pre-requirement to run MPLS.
For MPLS the routing table (RIB) still the same as we see on Normal Forwarding.

This is the LFIB table….

R4#show mpls forwarding-table
Local      Outgoing   Prefix           Bytes Label   Outgoing   Next Hop
Label      Label      or Tunnel Id     Switched      interface
16         Pop Label  10.12.12.12/32   0             Gi1.412    10.4.12.12
17         Pop Label  10.13.13.13/32   0             Gi1.413    10.4.13.13
18         Pop Label  10.1.12.0/24     0             Gi1.412    10.4.12.12
19         Pop Label  10.2.12.0/24     0             Gi1.24     10.2.4.2
Pop Label  10.2.12.0/24     0             Gi1.412    10.4.12.12
20         Pop Label  10.11.12.0/24    0             Gi1.412    10.4.12.12
21         Pop Label  10.12.13.0/24    0             Gi1.412    10.4.12.12
Pop Label  10.12.13.0/24    0             Gi1.413    10.4.13.13
22         Pop Label  10.2.13.0/24     0             Gi1.24     10.2.4.2
Pop Label  10.2.13.0/24     0             Gi1.413    10.4.13.13
23         22         10.11.11.11/32   0             Gi1.24     10.2.4.2
24001      10.11.11.11/32   0             Gi1.412    10.4.12.12
24         16         10.1.1.1/32      0             Gi1.24     10.2.4.2
24003      10.1.1.1/32      0             Gi1.412    10.4.12.12
25         17         10.1.11.0/24     0             Gi1.24     10.2.4.2
24004      10.1.11.0/24     0             Gi1.412    10.4.12.12
26         Pop Label  10.2.11.0/24     0             Gi1.24     10.2.4.2
27         Pop Label  10.1.2.0/24      0             Gi1.24     10.2.4.2
28         Pop Label  10.2.2.2/32      0             Gi1.24     10.2.4.2

Doing a trace to R1 we get a labeled path

R4#trace 10.1.1.1
Type escape sequence to abort.
Tracing the route to 10.1.1.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.2.4.2 [MPLS: Label 16 Exp 0] 3 msec
10.4.12.12 [MPLS: Label 24003 Exp 0] 10 msec
10.2.4.2 [MPLS: Label 16 Exp 0] 3 msec
2 10.1.12.1 3 msec
10.1.2.1 3 msec *