EnterasysGeneralities: Difference between revisions

From LLL
Jump to navigationJump to search
No edit summary
m (Reverted edits by Yxawyjo (Talk) to last version by AlainKnaff)
 
Line 1: Line 1:
----
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
----
=[http://utugijynure.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]=
----
=[http://utugijynure.co.cc CLICK HERE]=
----
</div>
====Connecting for the first time.====
====Connecting for the first time.====


* Start Knoppix with option &lt;code&gt;failsafe&lt;/code&gt; at boot prompt to boot it on Portier's computer
* Start Knoppix with option <code>failsafe</code> at boot prompt to boot it on Portier's computer
* When booted, start &lt;code&gt;minicom -s&lt;/code&gt; in a terminal (konsole) or virtual console (Alt+F1)
* When booted, start <code>minicom -s</code> in a terminal (konsole) or virtual console (Alt+F1)
* In &lt;code&gt;minicom&lt;/code&gt; , &lt;code&gt;Serial port setup&lt;/code&gt;, configure the following items:
* In <code>minicom</code> , <code>Serial port setup</code>, configure the following items:
** A - &lt;code&gt;Serial Device&lt;/code&gt; &lt;code&gt; &lt;/code&gt;/dev/ttyS0=
** A - <code>Serial Device</code> <code> </code>/dev/ttyS0=
** E - &lt;code&gt;Bps/Par/Bits&lt;/code&gt; &lt;code&gt; &lt;/code&gt;9600 8N1=
** E - <code>Bps/Par/Bits</code> <code> </code>9600 8N1=
** F - &lt;code&gt;Hardware Flow Control&lt;/code&gt; &lt;code&gt; &lt;/code&gt;no=
** F - <code>Hardware Flow Control</code> <code> </code>no=
* &lt;code&gt;Exit&lt;/code&gt; from config, the switches login screen should appear
* <code>Exit</code> from config, the switches login screen should appear
* Log in with username &lt;code&gt;rw&lt;/code&gt; and password ''the same as on the server''
* Log in with username <code>rw</code> and password ''the same as on the server''
* Set IP address using the following command: &lt;code&gt;set ip address&lt;/code&gt; ''address'' &lt;code&gt;mask&lt;/code&gt; ''netmask''
* Set IP address using the following command: <code>set ip address</code> ''address'' <code>mask</code> ''netmask''
Example: &lt;code&gt;set ip address 10.0.90.2 mask 255.0.0.0&lt;/code&gt;
Example: <code>set ip address 10.0.90.2 mask 255.0.0.0</code>


====Connecting later on====
====Connecting later on====


* &lt;code&gt;telnet 10.0.90.2&lt;/code&gt;
* <code>telnet 10.0.90.2</code>


====Useful commands====
====Useful commands====


* Display mac address table (which address is behind which port?): &lt;code&gt;show mac&lt;/code&gt;
* Display mac address table (which address is behind which port?): <code>show mac</code>
* Display VLAN config: &lt;code&gt;show vlan&lt;/code&gt; ''n''
* Display VLAN config: <code>show vlan</code> ''n''


====VLAN philosophy====
====VLAN philosophy====
Line 34: Line 26:
VLANs are created using the following command:
VLANs are created using the following command:


&lt;code&gt;set vlan&lt;/code&gt; ''n'' &lt;code&gt;create&lt;/code&gt;
<code>set vlan</code> ''n'' <code>create</code>


VLANs are named using the following command (names are only for comment purpose):
VLANs are named using the following command (names are only for comment purpose):


&lt;code&gt;set vlan name&lt;/code&gt; ''n'' ''name''
<code>set vlan name</code> ''n'' ''name''




===Frames sent to a port===
===Frames sent to a port===


Each VLAN has two egress lists &lt;code&gt;tagged&lt;/code&gt; (default) and &lt;code&gt;untagged&lt;/code&gt;. Frames belonging to that VLAN are output to all ports in the VLAN. Packets sent to a &lt;code&gt;tagged&lt;/code&gt; port will receive a tag indicating to which VLAN the packet belongs (useful for the link connecting both switches between each other).
Each VLAN has two egress lists <code>tagged</code> (default) and <code>untagged</code>. Frames belonging to that VLAN are output to all ports in the VLAN. Packets sent to a <code>tagged</code> port will receive a tag indicating to which VLAN the packet belongs (useful for the link connecting both switches between each other).


There is also a &lt;code&gt;forbidden&lt;/code&gt; list; this however is only useful for automatic configuration (GVRP): a port in the forbidden list may not be registered to the VLAN by GVRP.
There is also a <code>forbidden</code> list; this however is only useful for automatic configuration (GVRP): a port in the forbidden list may not be registered to the VLAN by GVRP.


Add a port to VLAN egress list, and set it to be tagged:
Add a port to VLAN egress list, and set it to be tagged:


&lt;code&gt;set vlan egress 2 fe.1.47 tagged&lt;/code&gt;
<code>set vlan egress 2 fe.1.47 tagged</code>




Add a port to VLAN egress list, and set it to be untagged:
Add a port to VLAN egress list, and set it to be untagged:


&lt;code&gt;set vlan egress 2 ge.1.1 untagged&lt;/code&gt;
<code>set vlan egress 2 ge.1.1 untagged</code>




Remove a port from both &lt;code&gt;tagged&lt;/code&gt; and &lt;code&gt;untagged&lt;/code&gt; lists:
Remove a port from both <code>tagged</code> and <code>untagged</code> lists:


&lt;code&gt;clear vlan egress 2 fe.1.1&lt;/code&gt;
<code>clear vlan egress 2 fe.1.1</code>




Line 66: Line 58:
Frames bearing no tag (the normal case) received on a port will be put into that port's default VLAN (usually 1). Default VLAN can be chosen by the following command:
Frames bearing no tag (the normal case) received on a port will be put into that port's default VLAN (usually 1). Default VLAN can be chosen by the following command:


&lt;code&gt;set port vlan fe.1.47 2&lt;/code&gt;
<code>set port vlan fe.1.47 2</code>


Frames having a tag will be put into the VLAN corresponding to that tag. However, if &lt;code&gt;ingress-filtering&lt;/code&gt; is enabled on that port, packets are only accepted if the frame's VLAN corresponds to one of the VLAN's on whose egress list the port is (i.e. port accepts packet only for VLAN for which it would also send packets to this port)
Frames having a tag will be put into the VLAN corresponding to that tag. However, if <code>ingress-filtering</code> is enabled on that port, packets are only accepted if the frame's VLAN corresponds to one of the VLAN's on whose egress list the port is (i.e. port accepts packet only for VLAN for which it would also send packets to this port)


&lt;code&gt;set port ingress-filter fe.1.47 enable&lt;/code&gt;
<code>set port ingress-filter fe.1.47 enable</code>


CAUTION: ingress-filter also applies to default VLAN of port (i.e. if port is not in its default VLAN's egress list, it may not receive any untagged packets whatsoever from computer(s) connected to this port!)
CAUTION: ingress-filter also applies to default VLAN of port (i.e. if port is not in its default VLAN's egress list, it may not receive any untagged packets whatsoever from computer(s) connected to this port!)

Latest revision as of 19:48, 26 November 2010

Connecting for the first time.[edit]

  • Start Knoppix with option failsafe at boot prompt to boot it on Portier's computer
  • When booted, start minicom -s in a terminal (konsole) or virtual console (Alt+F1)
  • In minicom , Serial port setup, configure the following items:
    • A - Serial Device /dev/ttyS0=
    • E - Bps/Par/Bits 9600 8N1=
    • F - Hardware Flow Control no=
  • Exit from config, the switches login screen should appear
  • Log in with username rw and password the same as on the server
  • Set IP address using the following command: set ip address address mask netmask

Example: set ip address 10.0.90.2 mask 255.0.0.0

Connecting later on[edit]

  • telnet 10.0.90.2

Useful commands[edit]

  • Display mac address table (which address is behind which port?): show mac
  • Display VLAN config: show vlan n

VLAN philosophy[edit]

VLANs are relevant both for frames (packets) received from a port (sent by the computer(s) connected to that port), and for frames sent to that port (i.e. sent by computers connected to one of the other ports). VLANs are created using the following command:

set vlan n create

VLANs are named using the following command (names are only for comment purpose):

set vlan name n name


Frames sent to a port[edit]

Each VLAN has two egress lists tagged (default) and untagged. Frames belonging to that VLAN are output to all ports in the VLAN. Packets sent to a tagged port will receive a tag indicating to which VLAN the packet belongs (useful for the link connecting both switches between each other).

There is also a forbidden list; this however is only useful for automatic configuration (GVRP): a port in the forbidden list may not be registered to the VLAN by GVRP.

Add a port to VLAN egress list, and set it to be tagged:

set vlan egress 2 fe.1.47 tagged


Add a port to VLAN egress list, and set it to be untagged:

set vlan egress 2 ge.1.1 untagged


Remove a port from both tagged and untagged lists:

clear vlan egress 2 fe.1.1


Frames received by a port[edit]

Frames bearing no tag (the normal case) received on a port will be put into that port's default VLAN (usually 1). Default VLAN can be chosen by the following command:

set port vlan fe.1.47 2

Frames having a tag will be put into the VLAN corresponding to that tag. However, if ingress-filtering is enabled on that port, packets are only accepted if the frame's VLAN corresponds to one of the VLAN's on whose egress list the port is (i.e. port accepts packet only for VLAN for which it would also send packets to this port)

set port ingress-filter fe.1.47 enable

CAUTION: ingress-filter also applies to default VLAN of port (i.e. if port is not in its default VLAN's egress list, it may not receive any untagged packets whatsoever from computer(s) connected to this port!)