DE · EN
Call us
+41 44 508 80 00 Ueberlandstrasse 1, 8600 Dübendorf
build 7bbbddf7 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 267 | ● 0 skipped | | format
apiVersion: soultec.ch/v1kind: Servicemetadata: name: network locale: en labels: group: infrastructure capability/network: 2.16 capability/security: 2.16 vendor/vmware: 0.88 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 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. 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. - 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: 267 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.83} - {ref: solutions/vmware/vmware-cloud-foundation/addon/advanced-cyber-compliance, score: 0.57} alsoLike: - {ref: posts/distributed-network-security-services, score: 1.00} - {ref: posts/nsx-free-nsx-ebooks-to-download, score: 1.00} - {ref: solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing, score: 0.57} experts: - {ref: experts/marco-betschart, score: 0.49} - {ref: experts/matthias-frech, score: 0.49} - {ref: experts/rico-lenherr, score: 0.49}
{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "network", "locale": "en", "labels": { "group": "infrastructure", "capability/network": "2.16", "capability/security": "2.16", "vendor/vmware": "0.88" }, "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", "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.", "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." }, { "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": 267, "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.83" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/advanced-cyber-compliance", "score": "0.57" } ], "alsoLike": [ { "ref": "posts/distributed-network-security-services", "score": "1.00" }, { "ref": "posts/nsx-free-nsx-ebooks-to-download", "score": "1.00" }, { "ref": "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing", "score": "0.57" } ], "experts": [ { "ref": "experts/marco-betschart", "score": "0.49" }, { "ref": "experts/matthias-frech", "score": "0.49" }, { "ref": "experts/rico-lenherr", "score": "0.49" } ] }}
apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "network"locale = "en"[metadata.labels]group = "infrastructure""capability/network" = "2.16""capability/security" = "2.16""vendor/vmware" = "0.88"[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"order = 11tags = ["network", "security"]vendors = ["vmware"]summary = "From the classic campus network to network virtualization. We work with our partners' products and with yours."photoNeed = "Cabling being done properly: a patch panel mid-work, labelled, with the person doing it"stub = falsedraft = false[[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.'''[[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.'''[[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 = 267[[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.83"[[status.solutions]]ref = "solutions/vmware/vmware-cloud-foundation/addon/advanced-cyber-compliance"score = "0.57"[[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 = "solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing"score = "0.57"[[status.experts]]ref = "experts/marco-betschart"score = "0.49"[[status.experts]]ref = "experts/matthias-frech"score = "0.49"[[status.experts]]ref = "experts/rico-lenherr"score = "0.49"
<?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">2.16</entry> <entry key="vendor/vmware">0.88</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> <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> <photoNeed>Cabling being done properly: a patch panel mid-work, labelled, with the person doing it</photoNeed> <stub>false</stub> <draft>false</draft> </spec> <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. </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> <status> <corpus>267</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.83</score> </item> <item> <ref>solutions/vmware/vmware-cloud-foundation/addon/advanced-cyber-compliance</ref> <score>0.57</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>solutions/vmware/vmware-cloud-foundation/addon/avi-load-balancing</ref> <score>0.57</score> </item> </alsoLike> <experts> <item> <ref>experts/marco-betschart</ref> <score>0.49</score> </item> <item> <ref>experts/matthias-frech</ref> <score>0.49</score> </item> <item> <ref>experts/rico-lenherr</ref> <score>0.49</score> </item> </experts> </status></manifest>
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 2.16
Vendors VMware 0.88
04Solutions
02Capabilities
01Vendors
267Corpus

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.

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 Praktikant

Network
0.49

Matthias Frech

Senior System Engineer

NetworkSecurity
0.49

Rico Lenherr

Senior System Engineer

Network
0.49
Maybe you? Take a look at our open roles.

You might also like

post 1.00

Distributed Network & Security Services

post 1.00

9 Free NSX eBooks to download

solution 0.57

Load Balancing (Avi)