DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get service/network -o yaml$ soultec get service/network -o json$ soultec get service/network -o toml$ soultec get service/network -o xml$ python3 network.pyPS> ./network.ps1$ go run network.go$ node network.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: network locale: en labels: group: infrastructure capability/network: 2.16 capability/security: 1.91 vendor/vmware: 0.98 annotations: source: src/content/services/en/network.md route: /en/services/network/ schema: /nerd/schema/services.json markdown: /en/services/network.mdspec: title: Network group: infrastructure audience: [enterprise, provider] order: 11 tags: [network, security] vendors: [vmware] summary: >- From the classic campus network to network virtualization. We work with our partners' products and with yours. photo: rack-fibre-fanout photoNeed: >- Cabling being done properly: a patch panel mid-work, labelled, with the person doing it stub: false draft: false sections: - heading:

What we cover

body: | Network infrastructure in the datacentre and on campus, segmentation, and the move to network virtualization with NSX. Along with connecting branch sites and access from outside. Then there are the areas that tend to get lost in a data centre discussion: **edge networking** for branch sites, and **wireless**, where the constraints are rarely technical and almost always structural. For branch sites there is SD-WAN with WAN optimisation, and for access there is network access control: who connects with what is decided by role and location, not by the port. - heading:

What we work with

body: | Our partners' networking products, and equally with other vendors' kit on projects. A network is rarely built on a green field, and a partner who only touches their own products is not much use in an estate that grew. - heading:

Where the work actually is

body: | In segmentation, and there it is not technical. A distributed firewall is switched on in an afternoon. Writing a rule set someone can still justify in three years takes months, because first you have to answer which systems talk to each other today. That is why we start in monitor mode and only enforce once the flows are documented.status: corpus: 315 solutions: - {ref: solutions/vmware/vmware-cloud-foundation/addon/advanced-security, score: 1.00} - {ref: solutions/vmware/vmware-secure-access-service-edge, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/nsx, score: 0.82} - {ref: solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing, score: 0.58} alsoLike: - {ref: posts/distributed-network-security-services, score: 1.00} - {ref: posts/nsx-free-nsx-ebooks-to-download, score: 1.00} - {ref: services/managed-network, score: 0.57} experts: - {ref: experts/marco-betschart, score: 0.50} - {ref: experts/marco-mattei, score: 0.45} - {ref: experts/steven-rodenburg, score: 0.44} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "network", "locale": "en", "labels": { "group": "infrastructure", "capability/network": 2.16, "capability/security": 1.91, "vendor/vmware": 0.98 }, "annotations": { "source": "src/content/services/en/network.md", "route": "/en/services/network/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/network.md" } }, "spec": { "title": "Network", "group": "infrastructure", "audience": [ "enterprise", "provider" ], "order": 11, "tags": [ "network", "security" ], "vendors": [ "vmware" ], "summary": "From the classic campus network to network virtualization. We work with our partners' products and with yours.", "photo": "rack-fibre-fanout", "photoNeed": "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it", "stub": false, "draft": false, "sections": [ { "heading": "

What we cover

", "body": "Network infrastructure in the datacentre and on campus, segmentation, and the move to\nnetwork virtualization with NSX. Along with connecting branch sites and access from\noutside.\n\nThen there are the areas that tend to get lost in a data centre discussion: **edge\nnetworking** for branch sites, and **wireless**, where the constraints are rarely\ntechnical and almost always structural.\n\nFor branch sites there is SD-WAN with WAN optimisation, and for access there is network\naccess control: who connects with what is decided by role and location, not by the port." }, { "heading": "

What we work with

", "body": "Our partners' networking products, and equally with other vendors' kit on projects. A\nnetwork is rarely built on a green field, and a partner who only touches their own products\nis not much use in an estate that grew." }, { "heading": "

Where the work actually is

", "body": "In segmentation, and there it is not technical. A distributed firewall is switched on in an\nafternoon. Writing a rule set someone can still justify in three years takes months,\nbecause first you have to answer which systems talk to each other today.\n\nThat is why we start in monitor mode and only enforce once the flows are documented." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-foundation/addon/advanced-security", "score": "1.00" }, { "ref": "solutions/vmware/vmware-secure-access-service-edge", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/nsx", "score": "0.82" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", "score": "0.58" } ], "alsoLike": [ { "ref": "posts/distributed-network-security-services", "score": "1.00" }, { "ref": "posts/nsx-free-nsx-ebooks-to-download", "score": "1.00" }, { "ref": "services/managed-network", "score": "0.57" } ], "experts": [ { "ref": "experts/marco-betschart", "score": "0.50" }, { "ref": "experts/marco-mattei", "score": "0.45" }, { "ref": "experts/steven-rodenburg", "score": "0.44" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "network"locale = "en"[metadata.labels]group = "infrastructure""capability/network" = 2.16"capability/security" = 1.91"vendor/vmware" = 0.98[metadata.annotations]source = "src/content/services/en/network.md"route = "/en/services/network/"schema = "/nerd/schema/services.json"markdown = "/en/services/network.md"[spec]title = "Network"group = "infrastructure"audience = ["enterprise", "provider"]order = 11tags = ["network", "security"]vendors = ["vmware"]summary = "From the classic campus network to network virtualization. We work with our partners' products and with yours."photo = "rack-fibre-fanout"photoNeed = "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it"stub = falsedraft = false[[spec.sections]]heading = "

What we cover

"body = '''Network infrastructure in the datacentre and on campus, segmentation, and the move tonetwork virtualization with NSX. Along with connecting branch sites and access fromoutside.Then there are the areas that tend to get lost in a data centre discussion: **edgenetworking** for branch sites, and **wireless**, where the constraints are rarelytechnical and almost always structural.For branch sites there is SD-WAN with WAN optimisation, and for access there is networkaccess control: who connects with what is decided by role and location, not by the port.'''[[spec.sections]]heading = "

What we work with

"body = '''Our partners' networking products, and equally with other vendors' kit on projects. Anetwork is rarely built on a green field, and a partner who only touches their own productsis not much use in an estate that grew.'''[[spec.sections]]heading = "

Where the work actually is

"body = '''In segmentation, and there it is not technical. A distributed firewall is switched on in anafternoon. Writing a rule set someone can still justify in three years takes months,because first you have to answer which systems talk to each other today.That is why we start in monitor mode and only enforce once the flows are documented.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/advanced-security"score = "1.00"[[status.solutions]]ref = "solutions/vmware/vmware-secure-access-service-edge"score = "1.00"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/nsx"score = "0.82"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing"score = "0.58"[[status.alsoLike]]ref = "posts/distributed-network-security-services"score = "1.00"[[status.alsoLike]]ref = "posts/nsx-free-nsx-ebooks-to-download"score = "1.00"[[status.alsoLike]]ref = "services/managed-network"score = "0.57"[[status.experts]]ref = "experts/marco-betschart"score = "0.50"[[status.experts]]ref = "experts/marco-mattei"score = "0.45"[[status.experts]]ref = "experts/steven-rodenburg"score = "0.44"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>network</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/network">2.16</entry> <entry key="capability/security">1.91</entry> <entry key="vendor/vmware">0.98</entry> </labels> <annotations> <source>src/content/services/en/network.md</source> <route>/en/services/network/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/network.md</markdown> </annotations> </metadata> <spec> <title>Network</title> <group>infrastructure</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>11</order> <tags> <item>network</item> <item>security</item> </tags> <vendors> <item>vmware</item> </vendors> <summary>From the classic campus network to network virtualization. We work with our partners' products and with yours.</summary> <photo>rack-fibre-fanout</photo> <photoNeed>Cabling being done properly: a patch panel mid-work, labelled, with the person doing it</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

What we cover

</heading> <body>Network infrastructure in the datacentre and on campus, segmentation, and the move tonetwork virtualization with NSX. Along with connecting branch sites and access fromoutside.Then there are the areas that tend to get lost in a data centre discussion: **edgenetworking** for branch sites, and **wireless**, where the constraints are rarelytechnical and almost always structural.For branch sites there is SD-WAN with WAN optimisation, and for access there is networkaccess control: who connects with what is decided by role and location, not by the port. </body> </section> <section> <heading>

What we work with

</heading> <body>Our partners' networking products, and equally with other vendors' kit on projects. Anetwork is rarely built on a green field, and a partner who only touches their own productsis not much use in an estate that grew. </body> </section> <section> <heading>

Where the work actually is

</heading> <body>In segmentation, and there it is not technical. A distributed firewall is switched on in anafternoon. Writing a rule set someone can still justify in three years takes months,because first you have to answer which systems talk to each other today.That is why we start in monitor mode and only enforce once the flows are documented. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/advanced-security</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-secure-access-service-edge</ref> <score>1.00</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/nsx</ref> <score>0.82</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing</ref> <score>0.58</score> </item> </solutions> <alsoLike> <item> <ref>posts/distributed-network-security-services</ref> <score>1.00</score> </item> <item> <ref>posts/nsx-free-nsx-ebooks-to-download</ref> <score>1.00</score> </item> <item> <ref>services/managed-network</ref> <score>0.57</score> </item> </alsoLike> <experts> <item> <ref>experts/marco-betschart</ref> <score>0.50</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.45</score> </item> <item> <ref>experts/steven-rodenburg</ref> <score>0.44</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "network", "locale": "en", "labels": { "group": "infrastructure", "capability/network": 2.16, "capability/security": 1.91, "vendor/vmware": 0.98, }, "annotations": { "source": "src/content/services/en/network.md", "route": "/en/services/network/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/network.md", }, }, "spec": { "title": "Network", "group": "infrastructure", "audience": ["enterprise", "provider"], "order": 11, "tags": ["network", "security"], "vendors": ["vmware"], "summary": "From the classic campus network to network virtualization. We work with our partners' products and with yours.", "photo": "rack-fibre-fanout", "photoNeed": "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it", "stub": False, "draft": False, "sections": [ { "heading": "

What we cover

", "body": ( "Network infrastructure in the datacentre and on campus, segmentation, and the move to\n" "network virtualization with NSX. Along with connecting branch sites and access from\n" "outside.\n" "\n" "Then there are the areas that tend to get lost in a data centre discussion: **edge\n" "networking** for branch sites, and **wireless**, where the constraints are rarely\n" "technical and almost always structural.\n" "\n" "For branch sites there is SD-WAN with WAN optimisation, and for access there is network\n" "access control: who connects with what is decided by role and location, not by the port." ), }, { "heading": "

What we work with

", "body": ( "Our partners' networking products, and equally with other vendors' kit on projects. A\n" "network is rarely built on a green field, and a partner who only touches their own products\n" "is not much use in an estate that grew." ), }, { "heading": "

Where the work actually is

", "body": ( "In segmentation, and there it is not technical. A distributed firewall is switched on in an\n" "afternoon. Writing a rule set someone can still justify in three years takes months,\n" "because first you have to answer which systems talk to each other today.\n" "\n" "That is why we start in monitor mode and only enforce once the flows are documented." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/vmware/vmware-cloud-foundation/addon/advanced-security", "score": "1.00", }, { "ref": "solutions/vmware/vmware-secure-access-service-edge", "score": "1.00", }, { "ref": "solutions/vmware/vmware-cloud-foundation/nsx", "score": "0.82", }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", "score": "0.58", }, ], "alsoLike": [ { "ref": "posts/distributed-network-security-services", "score": "1.00", }, { "ref": "posts/nsx-free-nsx-ebooks-to-download", "score": "1.00", }, { "ref": "services/managed-network", "score": "0.57", }, ], "experts": [ { "ref": "experts/marco-betschart", "score": "0.50", }, { "ref": "experts/marco-mattei", "score": "0.45", }, { "ref": "experts/steven-rodenburg", "score": "0.44", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Service' metadata = [ordered]@{ name = 'network' locale = 'en' labels = [ordered]@{ group = 'infrastructure' 'capability/network' = 2.16 'capability/security' = 1.91 'vendor/vmware' = 0.98 } annotations = [ordered]@{ source = 'src/content/services/en/network.md' route = '/en/services/network/' schema = '/nerd/schema/services.json' markdown = '/en/services/network.md' } } spec = [ordered]@{ title = 'Network' group = 'infrastructure' audience = @('enterprise', 'provider') order = 11 tags = @('network', 'security') vendors = @('vmware') summary = 'From the classic campus network to network virtualization. We work with our partners'' products and with yours.' photo = 'rack-fibre-fanout' photoNeed = 'Cabling being done properly: a patch panel mid-work, labelled, with the person doing it' stub = $false draft = $false sections = @( [ordered]@{ heading = '

What we cover

' body = @'Network infrastructure in the datacentre and on campus, segmentation, and the move tonetwork virtualization with NSX. Along with connecting branch sites and access fromoutside.Then there are the areas that tend to get lost in a data centre discussion: **edgenetworking** for branch sites, and **wireless**, where the constraints are rarelytechnical and almost always structural.For branch sites there is SD-WAN with WAN optimisation, and for access there is networkaccess control: who connects with what is decided by role and location, not by the port.'@ } [ordered]@{ heading = '

What we work with

' body = @'Our partners' networking products, and equally with other vendors' kit on projects. Anetwork is rarely built on a green field, and a partner who only touches their own productsis not much use in an estate that grew.'@ } [ordered]@{ heading = '

Where the work actually is

' body = @'In segmentation, and there it is not technical. A distributed firewall is switched on in anafternoon. Writing a rule set someone can still justify in three years takes months,because first you have to answer which systems talk to each other today.That is why we start in monitor mode and only enforce once the flows are documented.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/advanced-security' score = '1.00' } [ordered]@{ ref = 'solutions/vmware/vmware-secure-access-service-edge' score = '1.00' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/nsx' score = '0.82' } [ordered]@{ ref = 'solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing' score = '0.58' } ) alsoLike = @( [ordered]@{ ref = 'posts/distributed-network-security-services' score = '1.00' } [ordered]@{ ref = 'posts/nsx-free-nsx-ebooks-to-download' score = '1.00' } [ordered]@{ ref = 'services/managed-network' score = '0.57' } ) experts = @( [ordered]@{ ref = 'experts/marco-betschart' score = '0.50' } [ordered]@{ ref = 'experts/marco-mattei' score = '0.45' } [ordered]@{ ref = 'experts/steven-rodenburg' score = '0.44' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": map[string]any{ "name": "network", "locale": "en", "labels": map[string]any{ "group": "infrastructure", "capability/network": 2.16, "capability/security": 1.91, "vendor/vmware": 0.98, }, "annotations": map[string]any{ "source": "src/content/services/en/network.md", "route": "/en/services/network/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/network.md", }, }, "spec": map[string]any{ "title": "Network", "group": "infrastructure", "audience": []any{"enterprise", "provider"}, "order": 11, "tags": []any{"network", "security"}, "vendors": []any{"vmware"}, "summary": "From the classic campus network to network virtualization. We work with our partners' products and with yours.", "photo": "rack-fibre-fanout", "photoNeed": "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

What we cover

", "body": "Network infrastructure in the datacentre and on campus, segmentation, and the move to\n" + "network virtualization with NSX. Along with connecting branch sites and access from\n" + "outside.\n" + "\n" + "Then there are the areas that tend to get lost in a data centre discussion: **edge\n" + "networking** for branch sites, and **wireless**, where the constraints are rarely\n" + "technical and almost always structural.\n" + "\n" + "For branch sites there is SD-WAN with WAN optimisation, and for access there is network\n" + "access control: who connects with what is decided by role and location, not by the port.", }, map[string]any{ "heading": "

What we work with

", "body": "Our partners' networking products, and equally with other vendors' kit on projects. A\n" + "network is rarely built on a green field, and a partner who only touches their own products\n" + "is not much use in an estate that grew.", }, map[string]any{ "heading": "

Where the work actually is

", "body": "In segmentation, and there it is not technical. A distributed firewall is switched on in an\n" + "afternoon. Writing a rule set someone can still justify in three years takes months,\n" + "because first you have to answer which systems talk to each other today.\n" + "\n" + "That is why we start in monitor mode and only enforce once the flows are documented.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/advanced-security", "score": "1.00", }, map[string]any{ "ref": "solutions/vmware/vmware-secure-access-service-edge", "score": "1.00", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/nsx", "score": "0.82", }, map[string]any{ "ref": "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", "score": "0.58", }, }, "alsoLike": []any{ map[string]any{ "ref": "posts/distributed-network-security-services", "score": "1.00", }, map[string]any{ "ref": "posts/nsx-free-nsx-ebooks-to-download", "score": "1.00", }, map[string]any{ "ref": "services/managed-network", "score": "0.57", }, }, "experts": []any{ map[string]any{ "ref": "experts/marco-betschart", "score": "0.50", }, map[string]any{ "ref": "experts/marco-mattei", "score": "0.45", }, map[string]any{ "ref": "experts/steven-rodenburg", "score": "0.44", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Service", metadata: { name: "network", locale: "en", labels: { group: "infrastructure", "capability/network": 2.16, "capability/security": 1.91, "vendor/vmware": 0.98, }, annotations: { source: "src/content/services/en/network.md", route: "/en/services/network/", schema: "/nerd/schema/services.json", markdown: "/en/services/network.md", }, }, spec: { title: "Network", group: "infrastructure", audience: ["enterprise", "provider"], order: 11, tags: ["network", "security"], vendors: ["vmware"], summary: "From the classic campus network to network virtualization. We work with our partners' products and with yours.", photo: "rack-fibre-fanout", photoNeed: "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it", stub: false, draft: false, sections: [ { heading: "

What we cover

", body: "Network infrastructure in the datacentre and on campus, segmentation, and the move to\n" + "network virtualization with NSX. Along with connecting branch sites and access from\n" + "outside.\n" + "\n" + "Then there are the areas that tend to get lost in a data centre discussion: **edge\n" + "networking** for branch sites, and **wireless**, where the constraints are rarely\n" + "technical and almost always structural.\n" + "\n" + "For branch sites there is SD-WAN with WAN optimisation, and for access there is network\n" + "access control: who connects with what is decided by role and location, not by the port.", }, { heading: "

What we work with

", body: "Our partners' networking products, and equally with other vendors' kit on projects. A\n" + "network is rarely built on a green field, and a partner who only touches their own products\n" + "is not much use in an estate that grew.", }, { heading: "

Where the work actually is

", body: "In segmentation, and there it is not technical. A distributed firewall is switched on in an\n" + "afternoon. Writing a rule set someone can still justify in three years takes months,\n" + "because first you have to answer which systems talk to each other today.\n" + "\n" + "That is why we start in monitor mode and only enforce once the flows are documented.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/vmware/vmware-cloud-foundation/addon/advanced-security", score: "1.00", }, { ref: "solutions/vmware/vmware-secure-access-service-edge", score: "1.00", }, { ref: "solutions/vmware/vmware-cloud-foundation/nsx", score: "0.82", }, { ref: "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", score: "0.58", }, ], alsoLike: [ { ref: "posts/distributed-network-security-services", score: "1.00", }, { ref: "posts/nsx-free-nsx-ebooks-to-download", score: "1.00", }, { ref: "services/managed-network", score: "0.57", }, ], experts: [ { ref: "experts/marco-betschart", score: "0.50", }, { ref: "experts/marco-mattei", score: "0.45", }, { ref: "experts/steven-rodenburg", score: "0.44", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 71 lines · YAML · validated at build# 105 lines · JSON · validated at build# 108 lines · TOML · validated at build# 126 lines · XML · validated at build# 124 lines · Python · read back at build, equals the JSON record# 121 lines · PowerShell · read back at build, equals the JSON record# 130 lines · Go · read back at build, equals the JSON record# 115 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/network.md

Service · infrastructure

Network

From the classic campus network to network virtualization. We work with our partners' products and with yours.

Topics Network 2.16 Security 1.91

Vendors VMware 0.98

04Solutions

02Capabilities

01Vendors

315Corpus

Rear of a rack at a customer site: aqua fibre patch cables fan out of the vertical cable tray to the servers, above a switch and the labelled patch panels for the multimode and singlemode feeds

What we cover

Network infrastructure in the datacentre and on campus, segmentation, and the move to network virtualization with NSX. Along with connecting branch sites and access from outside.

Then there are the areas that tend to get lost in a data centre discussion: edge networking for branch sites, and wireless, where the constraints are rarely technical and almost always structural.

For branch sites there is SD-WAN with WAN optimisation, and for access there is network access control: who connects with what is decided by role and location, not by the port.

What we work with

Our partners’ networking products, and equally with other vendors’ kit on projects. A network is rarely built on a green field, and a partner who only touches their own products is not much use in an estate that grew.

Where the work actually is

In segmentation, and there it is not technical. A distributed firewall is switched on in an afternoon. Writing a rule set someone can still justify in three years takes months, because first you have to answer which systems talk to each other today.

That is why we start in monitor mode and only enforce once the flows are documented.

Experts for this

Marco Betschart

System Engineer

Network

0.50

Marco Mattei

Senior System Engineer

NetworkSecurity

0.45

Steven Rodenburg

Senior Solution Architect

NetworkSecurity

0.44

Maybe you? Take a look at our open roles.

Post 1.00

Distributed Network & Security Services

7 May 2024

Post 1.00

9 Free NSX eBooks to download

6 Aug 2018

Support 0.57

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

What we cover

What we work with

Where the work actually is

Network

What we cover

What we work with

Where the work actually is

Experts for this

Marco Betschart

Marco Mattei

Steven Rodenburg

You might also like

Distributed Network & Security Services

9 Free NSX eBooks to download

Managed Network