- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- Filtering interfaces from VM ( VMware vcenter Inte...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Filtering interfaces from VM ( VMware vcenter Integration)
Hello CheckMates,
I had a question regarding the integration with VMware vcenter.
If an imported virtual machine has more then one interface, all of the IP addresses of this VM are learned and traffic regarding these IPs is allowed or blocked.
Is it possible to use this imported object and allow only one of the interfaces? If I add a datacenter object I had no chance to filter something like this. The whole object is imported and used with all existing IPs.
Thanks
Wolfgang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did not experience this scenario myself, but it sounds like you may have to create a dummy object with single IP if you want to use it in the policy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Vladimir,
that's what I don't want todo, creating an extra object is more work todo. It simplifies the configuration using the original datacenter object.
Wolfgang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Understandable, but I think this is one of those situations that automatically created objects would not work.
Consider: vCenter provides the data about the object, but it is unaware about its routing properties.
If you are to edit the object's properties in CP, the data between CP and vCenter gets out of sync.