Network

by

Mellanox Introduces Advanced Network Telemetry Technology

Mellanox today announced an advanced Network Telemetry technology that provides visibility into Data Plane Anomalies – for public cloud, private cloud and enterprise computing.

What Just Happened (WJH) is a new intelligent monitoring technology that goes well beyond conventional streaming telemetry and Inband Network Telemetry (INT) offerings. These conventional telemetry offerings generate enormous amounts of data that is mined from network port counters and statistical packet sampling and hop-by-hop INT data. This type of telemetry data lacks any context or actionable details on abnormal network behavior, forcing the network admin or monitoring tool to perform time consuming analysis to find the root cause of network issues. WJH event-based telemetry delivers direct and actionable information and thus eliminates the guesswork from network troubleshooting.

In Mellanox based switch systems, WJH inspects packets across all ports at line-rate, at speeds that would overwhelm traditional Deep Packet Inspection solutions. WJH then identifies anomalous behavior, consolidates this into concise, specific, and actionable data that enables rapid remediation and recovery of cloud applications and critical business operations.

http://www.mellanox.com/related-docs/solutions/SB_Mellanox_WJH.pdf?ls=pr&lsd=190513-WJH-1

by

How Mellanox ConnectX and BlueField Empower Cyber Security Solutions

News from Mellanox

  1. Mellanox Turns Zero-Trust to HERO-Trust
    A Mellanox blog discussing the zero-trust security model, and how Mellanox BlueField SmartNIC empowers zero-trust security solutions
  2. ConnectX & BlueField Empower Cloud Security SolutionsEye on Mellanox YouTube VideoA short video clip discussing how ConnectX & BlueField empower cloud security solutions
  3. Guardicore and Mellanox Deliver Agentless and High-Performance Micro-Segmentation in Hybrid Cloud
    Guardicore is a cyber security solution provider which offers a complete micro-segmentation solution for enforcing security policies in data-center networks. Micro-segmentation is considered a priority for CISO’s in 2019 and beyond. We have recently partnered with Guardicore to have their software run on top of BlueField, enabling agentless and high-performant micro-segmentation solution. The attached solution brief describes the key benefits of applying BlueField for micro-segmentation and key benefits of the joint solution. 
by

White Paper on Mellanox seamless integration with OpenStack

Mellanox’s Ethernet solutions enable cloud data centers to achieve the highest efficiency through a high-performance, low latency cloud network with rich network offload with acceleration and automation features.
Check out the attached Whitepaper from Mellanox and see how we can help you get it there!

See Mellanox Seamlessly Integrates with OpenStack, Increasing Efficiency and Reducing Operational Costs

 

by

Mellanox SN2100 Ethernet Bundle Configurator

Mellanox has a Ethernet Configurator which you can even use for other model.

Here’s how it works:
Choose the following:
1. Choose the setup

  • 1 switch
  • 2 switches connected with mLAG
  • 5 switches: testing both mLAG as well as leaf spine (BGP/ECMP) – simple L3/VTEP/VXLAN Routing (VXLAN on Cumulus only for now)

2. Choose the speed of the host/NIC

  • 10/25/100GbE

3. Choose the operating system

  • ONYX
  • Cumulus Linux

What you get is:
1. Topology: how to connect, which specific ports should be used

2. Solution brief for the selected scenario

3. One Click Configuration files:

  • For the CLI guys: running config
  • For the Ansible guys: Ansible playbooks (ONYX Ansible for mLAG and L3 will be added soon)
by

Configuring 2 Gateways on the Same Linux Box, one for All Traffic, the other for Specific Traffic

To configure two gateways on a Linux machine—one for all traffic (default gateway) and the other for a specific network, you have to consider static routes and multiple network interfaces

Suppose you have 2 networks on a PC:

  1. Default Gateway (GW1) – For General Internet Traffic, 192.168.90.0/24 (eth0).
    • eth0 (Connected to GW1: 192.168.90.1
  2. Specific Gateway (GE2) – For Specific Traffic for AD Authentication, 192.168.0.1/24 (eth1)
    • eth1 (Connected to GW2: 192.168.1.1)

Set the Default Gateway (GW1)

You can set the default gateway for all traffic using the following command:

ip route add default via 192.168.90.1 dev eth0

This sends all non-specific traffic through GW1.

Add Static Route for Specific Network Range via GW2

ip route add 172.21.0.0/16 via 192.168.1.1 dev eth1
ip route add 144.21.0.0/16 via 192.168.1.1 dev eth1

This ensures traffic for 172.21.0.0/16 and 144.21.0.0/16 is routed via GW2.

Verify the Route

ip route show
default via 192.168.90.1 dev eth0 proto static metric 102 
172.21.0.0/16 via 192.168.1.1 dev eth1 proto static metric 103 
144.21.0.0/16 via 192.168.1.1 dev eth1 proto static metric 103
by

How to find which switch the OpenSM is running on

1. On any clients do a ibstat

CA type: MT26428
        Number of ports: 2
        Firmware version: 2.9.1000
        Hardware version: b0
        Node GUID: 0x000xxxxxxxxxx
        System image GUID: 0xxxxxxxxxxxxxxxx
        Port 1:
                State: Active
                Physical state: LinkUp
                Rate: 40
                Base lid: 184
                LMC: 0
                SM lid: 1
                Capability mask: 0x02510868
                Port GUID: 0x0002c903005abfd7
                Link layer: InfiniBand

2. To check for the SM Manager

# smpquery ND -L 1
Node Description:.......Voltaire 4036 # 4036-0D9E

where 1 is the SM Lid:1

3. If you query InfiniBand SMInfo attribute

# sminfo
sminfo: sm lid 1 sm guid 0x8f10500200d9e, activity count 42554 priority 4 state 3 SMINFO_MASTER