Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Who maintains the KDLab?

The lab is maintained by Indeni IT.
Any modifications done in the KDLab need to be documented in the wiki as it occurs. This included IP addresses, netmap updates, un/pwds, etc. If there is a chance for downtime or disruption of commonly used resources, a heads up via email or Slack is well-received.

...

Vendor Specific

VLAN ID

Network

Default Gateway

Radware

189

192.168.189.0/24

192.168.189.1

F5 Networks - F5 Environment details

190

192.168.190.0/24

192.168.190.1

Cisco Systems

191

192.168.191.0/24

192.168.191.1

Symantec (Blue Coat

192

192.168.192.0/24

192.168.192.1

Fortinet

193

192.168.193.0/24

192.168.193.1

Check Point - Check Point Environment

194

192.168.194.0/24

192.168.194.1

Palo Alto Networks

195

192.168.195.0/24

192.168.195.1

Juniper Networks

196

192.168.196.0/24

192.168.196.1

...

  • vm name

  • cpu cores number

  • memory size

  • disk size

  • how many network interfaces

  • link to ova/iso file

  • any other relevant data for deployment

VMware infrastructure

Managing virtual devices is done via vCenter Server which is a virtual device hosted by the ESXi server.

As a backup solution should vCenter Server be unavailable, ESXi server https://172.16.20.3 can be reached directly

Currently there are no official backups, snapshots or redundancy for ANY device in the KDlab.
At the minimum, The HP Proliant DL360 G9 is using RAID5 in the event of a drive failure. 

FAQ

How do I log in? 

Credentials are issued on an individual basis.
Please refer to your manager in order to receive credentials.

What Datastore should I use if I need to create a virtual device? 

datastore0

What are the guidelines I should follow when working with devices in the KDLab?

  1. Document and update any existing wiki information

  2. Are you done with it? Remove it.

  3. Review and keep in-line with KDLab guidelines