The requirement was to have the Cisco 881 WAN port control the PPPOE connection, and have it's IP as the external IP of the connection. The Cisco 881 however does not have an analog telephone port so as to directly dial the connection. The CPE here that was provided was an Thomson Speedtouch ADSL router. The Cisco WAN port is connected to one of the Thomson ethernet ports.
If the PPPOE connection is configured on the Speedtouch as well as the Cisco 881, then there will be a fight between the two, to control the connection, the result being that the connection will keep dropping, expecting one of the two to dial.
What needs to be done is to setup the Thomson Speedtouch as a bridge, using the Easy Setup wizard on its web interface. This way, the only router that will dial the connection is the Cisco router and hence will receive the external IP of the ADSL connection on its WAN interface.
Thursday, August 18, 2011
Fujitsu-SAN!
I got an opportunity to setup a Fujitsu Eternux DX 80 Storage with a Fujitsu RX 200 server. Once the storage was out of the box, it was just a matter of putting up the railings and slowly placing the storage onto the grooves. Since the hard disks come pre-configured, there was no need to install them separately. I connected a laptop to the MNT port for configuration and setup an IP in the default IP range of the MNT port ( 192.168.1.1). Logged on to the web-interface using the default u/p combo (root/root). Setting up the RAID config and the volumes was quite easy, thanks to the detailed but well thought-of setup wizard.
Now the MNT port is used only for management through a direct connection to a device like server/desktop/laptop and cannot be connected to a switch. For that there is a RMT port which can be setup for remote configuration. Also , the MNT and RMT ports can't be on the same subnet.
trust me, I tried!
Now comes the part of setting up the volumes so that the server can see them. This setting is know as host affinity where we can set up the volumes in such a way that they can be 'reserved' for certain hosts. Very useful in the case of when the storage is connected to a fibre switch. This is done by using the feature of the fibre card known as WWN or World-Wide Name. This basically identifies the fibre card installed on the server to which the volume has to be associated to.
Once the volumes are setup , we needed to wait until the formatting is done.This took a while because one volume was 4TB and the other was 2TB. I tried setting up the server to recognize the volumes but it wouldn't show up. The formatting took a while to complete. Im not sure how long because I came back the next day to check, and it was done.
My first misconception was that the Storage volumes would show up during the HBA scan that usually happens when the server starts up. But after a little bit of reading, I found out that only certain fibre cards support this feature whereby you can actually boot from a SAN!
So in this case, the server OS had to load the drivers for the Fibre card , only after which the volumes could be detected. This server was running Ubuntu Server 11.04, so drivers wouldn't really be a problem.
Once the host affinity was configured and the volumes had completed formatting, the volumes showed up under devices folder on the server.
Now the MNT port is used only for management through a direct connection to a device like server/desktop/laptop and cannot be connected to a switch. For that there is a RMT port which can be setup for remote configuration. Also , the MNT and RMT ports can't be on the same subnet.
trust me, I tried!
Now comes the part of setting up the volumes so that the server can see them. This setting is know as host affinity where we can set up the volumes in such a way that they can be 'reserved' for certain hosts. Very useful in the case of when the storage is connected to a fibre switch. This is done by using the feature of the fibre card known as WWN or World-Wide Name. This basically identifies the fibre card installed on the server to which the volume has to be associated to.
Once the volumes are setup , we needed to wait until the formatting is done.This took a while because one volume was 4TB and the other was 2TB. I tried setting up the server to recognize the volumes but it wouldn't show up. The formatting took a while to complete. Im not sure how long because I came back the next day to check, and it was done.
My first misconception was that the Storage volumes would show up during the HBA scan that usually happens when the server starts up. But after a little bit of reading, I found out that only certain fibre cards support this feature whereby you can actually boot from a SAN!
So in this case, the server OS had to load the drivers for the Fibre card , only after which the volumes could be detected. This server was running Ubuntu Server 11.04, so drivers wouldn't really be a problem.
Once the host affinity was configured and the volumes had completed formatting, the volumes showed up under devices folder on the server.
Subscribe to:
Posts (Atom)