Rapid Spanning Tree Protocol

October 09, 2013
You may think why we may need RSTP. Go back my previous blog post where I wrote how STP work and its port state. Now we are going to talk about RSTP. Lets learn about it and you may know why we need it.

Recall my previous theory, as we already know STP is created very long time ago and STP have below problem to converge the link.

1. Listening : 15s of listening for BPDUs. Switch sends/receives BPDUs on this state
2. Learning : 15s of Learning MAC Address, populate switch CAM table
3. Forwarding : Port is Forwarding Traffic
4. Blocking : Switch will wait up to 20s before moving a block port into listening phase, because this the time where switch wait if the primary link may came live.

STP port state take minimum 30s to maximum 50s to link up. This is the port process which have to pass every switch when boots up or converge time.

STP downtime is the biggest problem for todays Network.

STP have problems but also we have solution !

Port Fast :

Port fast disable Spanning Tree. When you type this command on an interface it will display warning message. Like this



Because it won't really detect the node mention in Warning message. Just enable the command and unplug the cable then plug back in use show command it’s immediately transition into forwarding state because now we have the port fast enable.

You can enable port fast all end node connected ports, that allow immediate active.
Switch(config)#int range fa0/2-24
swirch(config)#spanning-tree portfast
****output omitted****
On the other hand we have problem with uplink link. We can't enable portfast on the uplink ports, as you can see in warning message. 50s downtime cause big problem to our network. So there has to be other solution for this problem. Yes you already heard about it, RSTP. Rapid Spanning tree is very fast and very good. RSTP give us faster convergence, yes what we need. Think about VoIP, dropping one packet isn't tolerance for it. Other transfer like file transfer can be retransmitted. But voice can't be retransmitted. Real time transmitting must need, we don't have loss in the link.

Some of you still using uplink fast or backbone fast, that wouldn't going to work if you have different switch other than cisco. Those are cisco proprietary. So RSTP standard have availability to participate all vender switches. Which speed things up. RSTP is very good, you can see in your network.

 RSTP with its port state 


Discarding : Its replacement of blocking state of STP, we study before. It’s mean, taking down layer 2 connectivity not sending out any traffic.
Learning: Its mean exactly STP's learning state, it is the process to learn MAC address is on that port, without it switch just act like hub, its forward every packet to every port.
Forwarding: It’s also like STP port state, forwarding means not blocking any traffic.

Port roles

Root port : The way reaching to root bridge.
Designated port : All root bridge port are designated port. Other switch have lower priority or lower mac address elected as designated port. Other switch should be block the traffic.
Alternate port : Instead blocking state in STP, where all port should be re-elected and take 50s to downtime of network. RSTP remember that port with alternate port to reach Root Bridge. If root port failure, its immediately turn it into forwarding state. So it’s doesn't have to wait 50s.
Edge port : Port fast is edge port. Where non switch are connected or host. We can use port past command to tell switch it is edge port.

Why   RSTP is better

a. RSTP doesnt forget its port unlike STP which re-elected when primery link is down.

b. Its dosn't use extra time of STP like listening BPDUs, bonus blockig penalty,

c. If change into trunk port, that will flood to each network with TC packets, where TC is topology changes. Those are part of the BPDU's.

Kali linux Device not manage

October 09, 2013
Recently I upgrade Kali linux 1.0.4 to 1.0.5, all goes well but when I try to up eth0 it didn't up and show message "Device Not Manage".

I did everything to get it up but no command avail to up it.
like:
root@kali:~#service networking restart
root@kali:~#service networking start
root@kali:~#ifconfig eth0 down
root@kali:~#ifconfig eth0 up

 Then after googling I found one solution

root@kali:~# vi /etc/NetworkManager/NetworkManager.conf

Network manager will opened and you can see following line on that file.
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false

Now edit and change  false to true
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=true

Now use this command to restart Network manager

root@kali:~# service network-manager restart

Then you can see your LAN is working. 

Send email using Telnet

August 25, 2013
How to send email through Telnet.

You can use it for troubleshoot purpose when sometime outgoing issue from the mail server.

1. First open the Command prompt. ctrl+r, now type "cmd".

before that you have to enable telnet service from control panel>program and feautre>Turn windows features on or off> now choose telnet client

2. Now, connect with telnet command just type

telnet mail.yourdomain.com 25



3. From the picture, you already enter into the server now use following command

helo mail.yourdomain.com




4. type mail from username, see on screenshots

mail from: username@yourdomain.com



5. Type receiver ID here, see screenshot.

rcpt to: yourfriend@hotmail.com, yourfriend@yahoo.com



6. To add message just use "data" command and type "subject" command. At the end don't forget to add "." to end the message and press enter.


data
subject: this is test email

hello,

This is jpudasaini.com.np, the portal where you can hangout for tutorial on the job training.

Regards
jpudasaini.com.np

.

7 Type quit to exit.

Identified SMTP mail server

July 22, 2013
This tutorial helps you to determine the mail server for any email address. This is helpful to identified SMTP mail sever to use or configure Outlook.

In day to day work I need to troubleshoot email ID with mail hosting server, so this syntax is very useful for me, if you don't kown the mail server just use following syntax to identify the mail server
mail.domainname.com or smtp.domainname.com, it those doesn't work then you need to follow below steps.

(change "domainname" with your desire domain.)

1. Open a DOS Command Prompt
2. Type "nslookup"
3. Your computer's DNS server name and IP address will be displayed.
4. Now just type "set type=mx" - this will force NSLOOKUP to shows Mail eXchange records from the DNS servers.
5. You can try using gmail.com or use your own domain name.
6. you can see below output.