| Author |
Message |
Gary Brett
Guest
|
 Posted:
Mon Oct 11, 2004 6:37 pm Post subject:
VLAN 2 Baystack 470's over a private Circuit.... |
|
|
Hi,
Please can somebody assist with this problem I am facing? I have a
10MB Lan extension Circuit (private) which is basically a 10MB leased
Line (but not on the internet)connecting our 2 offices. At each end of
the circuit we have a Nortel Baystack 470-48 port switch and users at
both offices can browse the network as though in the same building. I
now have 2 servers at each office that need to talk to each other but
no-one else on the LAN so thought I could create a VLAN for this
purpose. Does anyone have any idea if Nortel have published any info
on this as I cannot find any. As a test I did the following:
The private circuit is patched into port 48 on both switches
1 - Switch A, Created a VLAN with ports 47 & 48 checked
2 - Switch B, Created a VLAN with ports 47 & 48 checked
3 - Switch A, Patched the server directly into port 47
4 - Switch B, Patched the server directly into port 47
The only thing that has occurred as far as I can see is that I have
now lost contact with the Switch A and cannot access through the
browser to check config. Have also tried pinging & telnet without
success. Is there another method to get into the Switch config & more
importantly is this actually acheivable what I am trying to do????
Many thanx
G |
|
| Back to top |
|
 |
Michael Roberts
Guest
|
| Posted:
Mon Oct 11, 2004 7:44 pm Post subject:
Re: VLAN 2 Baystack 470's over a private Circuit.... |
|
|
If you are running more than one VLAN across an interface, the interface
needs to have 802.1q VLAN tagging enabled. If port 48 is your uplink, then
that port needs to have tagging enabled.
As far as your management goes, the Baystacks have the ability to change the
management VLAN. Make sure that the management VLAN is set properly and you
should be able to ping/telnet/http the switch.
-mike
"Gary Brett" <globalg2001@yahoo.co.uk> wrote in message
news:5b221b4d.0410110637.15518281@posting.google.com...
| Quote: | Hi,
Please can somebody assist with this problem I am facing? I have a
10MB Lan extension Circuit (private) which is basically a 10MB leased
Line (but not on the internet)connecting our 2 offices. At each end of
the circuit we have a Nortel Baystack 470-48 port switch and users at
both offices can browse the network as though in the same building. I
now have 2 servers at each office that need to talk to each other but
no-one else on the LAN so thought I could create a VLAN for this
purpose. Does anyone have any idea if Nortel have published any info
on this as I cannot find any. As a test I did the following:
The private circuit is patched into port 48 on both switches
1 - Switch A, Created a VLAN with ports 47 & 48 checked
2 - Switch B, Created a VLAN with ports 47 & 48 checked
3 - Switch A, Patched the server directly into port 47
4 - Switch B, Patched the server directly into port 47
The only thing that has occurred as far as I can see is that I have
now lost contact with the Switch A and cannot access through the
browser to check config. Have also tried pinging & telnet without
success. Is there another method to get into the Switch config & more
importantly is this actually acheivable what I am trying to do????
Many thanx
G |
|
|
| Back to top |
|
|
Gary Brett
Guest
|
| Posted:
Tue Oct 12, 2004 12:14 pm Post subject:
Re: VLAN 2 Baystack 470's over a private Circuit.... |
|
|
Hi Mike & thanx for your time -
When the Baystacks arrived they were precongured with 1 VLAN on each
switch. By default that had all 48 ports ticked. I created a 2nd VLAN
and ticked port 48 (10MB Circuit link)& port 47 (Server Cable Patched)
on each switch before unchecking port 47 on the VLAN1(default). I can
now config the local swicth thru a broswer but for some reason I
cannot reach the remote Baystack, by any LAN method (Ping, http,
telnet)..Is there a console cable available so I can log in directlky
and check the config you kindly suggested??
Again thanx for your time
Gary
"Michael Roberts" <robertsmj@missouri.edu> wrote in message news:<8Txad.601$i_4.5136@news.more.net>...
| Quote: | If you are running more than one VLAN across an interface, the interface
needs to have 802.1q VLAN tagging enabled. If port 48 is your uplink, then
that port needs to have tagging enabled.
As far as your management goes, the Baystacks have the ability to change the
management VLAN. Make sure that the management VLAN is set properly and you
should be able to ping/telnet/http the switch.
-mike |
|
|
| Back to top |
|
|
Michael Roberts
Guest
|
| Posted:
Tue Oct 12, 2004 4:35 pm Post subject:
Re: VLAN 2 Baystack 470's over a private Circuit.... |
|
|
Try a straight-through serial cable. That is what we use. I do not think
any of the Baystacks ship with serial cables. It is a bummer.
-mike
"Gary Brett" <globalg2001@yahoo.co.uk> wrote in message
news:5b221b4d.0410120014.1cb4b4d1@posting.google.com...
| Quote: | Hi Mike & thanx for your time -
When the Baystacks arrived they were precongured with 1 VLAN on each
switch. By default that had all 48 ports ticked. I created a 2nd VLAN
and ticked port 48 (10MB Circuit link)& port 47 (Server Cable Patched)
on each switch before unchecking port 47 on the VLAN1(default). I can
now config the local swicth thru a broswer but for some reason I
cannot reach the remote Baystack, by any LAN method (Ping, http,
telnet)..Is there a console cable available so I can log in directlky
and check the config you kindly suggested??
Again thanx for your time
Gary
"Michael Roberts" <robertsmj@missouri.edu> wrote in message
news:<8Txad.601$i_4.5136@news.more.net>...
If you are running more than one VLAN across an interface, the interface
needs to have 802.1q VLAN tagging enabled. If port 48 is your uplink,
then
that port needs to have tagging enabled.
As far as your management goes, the Baystacks have the ability to change
the
management VLAN. Make sure that the management VLAN is set properly and
you
should be able to ping/telnet/http the switch.
-mike |
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in