SCVMM – Cannot Resolve with DNS

I observed this issue when creating a cluster in a remote site using Active Directory sites. DNS for this does take about 15 minutes based on the default replication value. Also this configuration had my Virtual Machine Manager in a remote site using site local library to deploy virtual machines. When trying to add another cluster to SCVMM shortly after I created it gave me the error message below.

SERVER cannot resolve with DNS

Ensure there is network communication with the DNS server. if the problem persists contact your network administrator

ID:404

Details: The request name is a valid but no data of the requested type was found

After logging in to the SCVMM server to test the DNS name of the cluster. The SCVMM server is the one making the DNS requests and must be able to resolve any cluster or server names which you wish to add. For this issue I had to flush out the previously cached values on the SCVMM server or wait for the cache to expire.

IPCONFIG /flushdns

If your experiencing issues I would start on your SCVMM server and check your DNS servers and if it can correctly retrieve the DNS records.

HP H3C – SNMP

Just a quick post to enable read snmp community. The commands will get you on your way.

snmp-agent
snmp-agent community read public
snmp-agent sys-info version all

You can change the read to write or all to filter which versions of SNMP you want to support. After running the snmp-agent command the device will generate a engineid which will show up in your configuration even if you don’t enable version 3.

snmp-agent local-engineid

Cisco ASA – TFTP Copy over a VPN connection

While looking into doing some automated backups of configuration files of Cisco ASA and other devices I found some routing issues while doing TFTP copies. Below is the syntax for TFTP copy command.

tftp://[user[:password]@]server[:port]/[path/]filename[;int=interface_name]

After using the int=INTERFACE allowed the TFTP copy to work over the tunnel.

copy /noconfirm running-config tftp://192.168.1.1/config/FW01.cfg;int=DMZ

Also good thing to know is you can set this same setting on the default TFTP client settings.

config t

tftp-server DMZ 192.168.1.1 config/FW01.cfg

After this set you can just do use some commands to take advantage of short hand.

write net

or

copy running tftp

Good References

http://www.cisco.com/en/US/docs/security/asa/asa84/command/reference/c4.html#wp2171368

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_tech_note09186a008072142a.shtml