[
https://issues.apache.org/jira/browse/CLOUDSTACK-4569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radhika Nair resolved CLOUDSTACK-4569.
--------------------------------------
Resolution: Fixed
> [doc] Review comments on Egress Firewall
> ----------------------------------------
>
> Key: CLOUDSTACK-4569
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4569
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc
> Affects Versions: 4.2.0
> Reporter: Radhika Nair
> Assignee: Radhika Nair
> Fix For: 4.2.0
>
>
> 16.20.1.3. Changing the Default Egress Policy
> Change:
> Configuring Default Egress Policy
> 2.
> You can configure the default policy of egress firewall rules in Isolated
> Advanced networks.
> Change:
> The default egress policy for the isolated guest network is configured using
> the network offering. Create network offering with egress policy Allow/Deny.
> Now use this network offering to create network.
> 3.
> 16.15.3. Assigning Additional IPs to a VM
> 1. 1. You need to specify the secondary IP address on the guest VM.
> Change: You need to configure the IP on guest vm NIC manually.
> 2.
> In point# 6: ensure that you assign IPs to NIC each time the VM reboots.
> change:
> Ensure the ip address configuration persist on vm reboot.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
