I will list and explain the steps to configure SNMP on Cisco MDS 900 series Multilayer Fabric switch using the CLI.

Logon to the cisco swith CLI console. You use telnet over the network or via a serial cable connected to the console port.

Enter the configuration mode with the config t command.
cisco# config t
Enter configuration commands, one per line. End with CNTL/Z.

This step is not necessary to configure SNMP, but while you are in the configuration mode you might as well create an administrative username for youself.
cisco(config)# username myadminid password topsecret role network-admin

Configure the remote snmp server IP address, using SNMP version 2c, with a SNMP community name of monitor-me. You can get this information from the administrator who is responsible for the management server, if that is not you.
cisco(config)# snmp-server host 168.10.10.11 version 2c monitor-me

Define the SNMP community name.
cisco(config)# snmp community monitor-me

Exit the configuration mode.
cisco(config)# exit

Save the changes.
cisco# copy running-config startup-config

Now configure the Cisco MDS 9000 switch on the network monitoring server. This is the server that has the IP address of 168.10.10.11.

There are many ways to achieve this, NAT, VIP, MIP etc. In this article I will explain NAT (natting) on a Cisco PIX, ASA or router.

First you need to log onto the firewall or router. Enter en (enable) to get into the privilege mode, you will then be prompted for the password. Enter Config T to get into the configure terminal mode. You can now start confguring the network appliance.

Below is what your should see in the running config after you complete the configuration.

static (inside,outside) 172.210.10.10 11.12.13.10 netmask 255.255.255.255 0 0

The above line means that the IP address 172.210.10.10 (outside interface) is mapped to 11.12.13.10 (inside interface). Clients in the outside interface will connect to resources on 11.12.13.10 by referencing the natted (NAT) IP 172.210.10.10.

You also need to configure the access list or policy to allow traffic from the outside interface to flow into the inside interface. The access list then needs to be applied to the outside intefrace.

access-list Allowed_Traffic permit tcp host any host 172.210.10.10 eq www log

The above means that the name of the access list is Allowed_Traffic. Permit TCP traffic from any host to 172.210.10.10, only allow if service request is for www (TCP port 80), and log all traffic.

You then need to apply the access list to the outside interface.

access-group Allowed_Traffic in interface outside

At the scheduled 1 a.m. eatern time, I dialed into the conference bridge and connected with 3 other parties.  This was a new circuit we were trying to implement from Phoenix to New Jersey.  I am in Toronto, Ontario and the rest of the people were in the US.  The circuit was a frame-relay circuit, CIR of 64k and burstable to 128k, good old reliable frame-relay but pain in the behind to implement and configure.

Anyhow, what I really wanted to discuss here is NAT (network address translation).  NAT hides the real source of IP address and converts it to a different IP.  For excample if you have multiple computers that want to share one single internet connection, you can do this with NAT.  Your ISP assigns you one public IP, but you have more than one computer that accesses the internet.  You will need to purchase a router to share the internet connection, if you do not have a router there are other ways to do this as well. 

How does NAT work?  Well in the above example, say computer A is 10.0.0.2 and computer B is 10.0.0.3.  The router is connected to the internet and has a public ip of 70.64.238.1.  When computer A accessing www.cupidpost.com, via the router, the router will translate the ip address 10.0.0.2 to 70.64.238.1 and direct the connection to www.cupidpost.com.  If computer B accessing the internet at the same time a computer A, the router will translate the IP 10.0.0.3 to 70.64.238.1 as well.