As mentioned in previous post, we choose 1 node setup with App OVA with 16vCPU and 64GB memory. It will be run in ESX cluster.
Pls review the link below
Deploying Nexus Dashboard Using VMware vCenter
Cisco Nexus Dashboard Fabric Controller 12
For SAN, you still need the following ready before deployment.
1) 2 NICs: one for management IP and one for data IP and both can be in the same subnet.
2) DNS and NTP are required
3) Cluster name and VM name should be different but it is a one node setup. So, it does not really matter.
4) Pool IP: 2 are required in our setup (2 IPs for data network) Ask for an additional IP if you plan to use SAN Insight). All pool IP should be whitelisted for SMTP traffic in additional to Management and Data IP.
5) Internal subnets settings (these subnets are used internally and will not leave cluster. Just in case, confirm the subnets are not in use and subnet mask has to be 255.255.0.0)
App subnet and Service subnet
6) May want extra space for HDD depends on the number of switches to manage.
The steps are very straight forward. However, depending on the environment, do not specify VLAN in step 18 for data network. Otherwise, the data network will not be able to communicate with the switches even they are in the same subnet. In our environment, VLAN info is already present at the switch and ESX level.
For initial setup, you can follow the document below
Feature Management will be set to SAN Controller with Performance Monitoring and SAN Web Device Manager for my environment.
Server settings are self explanatory. For SMTP, make sure all pool IPs are added to SMTP allowed list.
If you want to confirm SMTP alert, go to Event -> Event setup -> Forwarding -> Add Rule (same as DCNM). Multiple recipients allowed and event email will be sent thru pool IP.
Below link provided detail steps on how to add event email.
How
to Configure Event Forwarding using Cisco Nexus Dashboard Fabric Controller -
Cisco
I include a blog post below for bugs we faced for NDFC appliance. See
No comments:
Post a Comment