Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

ports (TechnicalUser) (OP)
21 Sep 03 0:22
Hi,
    We have a set of baystack 450's,460's in a stack, in which,Baystack 460 serves  as the base unit and 4x 450's for connecting to the user PC's.

I am not able to ping the stack IP but the stack is working fine as i am able to ping all PC's and servers connected to this stack.

I have configured this as a hybrid stack.

All, info on getting this working would be great.

Thanks,
FG.

 
leomavv (TechnicalUser)
21 Sep 03 2:29
Hi

Just to confirm that you have configured the right feilds

In-Band Stack IP Address:  [ x.x.x.x]       
In-Band Switch IP Address: [0.0.0.0]                   
In-Band Subnet Mask:       [ x.x.x.x]    

Default Gateway:           [ x.x.x.x]       

The x.x.x.x feilds are required to be configured.

Hope this help

Mavvy
ports (TechnicalUser) (OP)
21 Sep 03 5:11
Hi,
    I have put all the fields in the switch stack.
But still no luck.

Regards,
FG
jimbopalmer (Programmer)
21 Sep 03 7:30
One gotcha I do sometimes is to put the management IP in a VLAN with no ports.  If you are using VLANs be sure your management IP is in the VLAN you expect it to be.

I tried to remain child-like, all I acheived was childish.

ports (TechnicalUser) (OP)
21 Sep 03 23:30
Hi,
   Yes, I have the Management IP in the required VLAN.

Also the difference in this stack is that, I am Using both the 450's and 460's, this is a hybrid stack.

Well, i have tried all options, but still no Luck.


I apprecaite all the inputs, and waiting for more.

Thanks,
FG.
ZachBenj (TechnicalUser)
22 Sep 03 10:22
Check your PVID for the uplink port.  Make sure that is set correctly. If the uplink is set to access then you also need to make sure that the uplink port is not a member of any VLANS.  Biggest thing to keep in mind when using a 450 is that all changes have to be made manually.  Hope this helps!

My suggestions are what I would try myself. If incorrect, I welcome corrections to my knowledge.
Scott
stomlin@baptistfirst.org

Jynxx (IS/IT--Management)
22 Sep 03 11:50
The only switch that should have an IP address is the base 460.  All of the 450's should have 0.0.0.0 entered for everything.  Ensure that on the cascade modules, that the 460 is set as base but that's it...the rest should not be.  When you boot the stack...plug in the 460 JUST before the 450's.  It can be less than a second...just need the 460 to start first.

This should get you working if you have the correct IP info.

Another thing that I have ran in to, is that with older revs of code, I could not form a stack...I had to update all of the switches int he stack.
ports (TechnicalUser) (OP)
27 Sep 03 3:12
Hi,
   I have tried the option mentioned by Jynxx. But still i am not able to ping.

For information sake the following is the stack config,
Unit# Switch Model     MDA Model   GBIC Port   GBIC Port   Cascade SW Version
                                                           Module
----- ---------------- ----------- ----------- ----------- ------- ----------
  1   BayStack 460-24T None                               400-ST1 v3.0.0.54
  2   BayStack 450-24T 450-1SX                             400-ST1 v4.2.0.22
  3   BayStack 450-24T None                                400-ST1 v4.2.0.22
  4   BayStack 450-24T None                                400-ST1 v4.2.0.22
  5   BayStack 450-24T 450-1SX                             400-ST1 v4.2.0.22

I have checked from the Nortel site and the Stack sofware is compatible.

Now what do i do......Guys i would truly apprecaite if suggestions are made.

Thanks and Regards,
FG.
Jynxx (IS/IT--Management)
29 Sep 03 9:06
Dumb question, but are you sure that you have the cascade cables hooked up correctly?

Each module has 2 ports on it.  Port A on switch one should go to port B on the 2nd switch.  Port A on the second go to port B on the 3rd...on and on down the stack.

On the final switch, port A should loop back up and plug into port B on the top switch.
allyc75 (TechnicalUser)
29 Sep 03 9:38
A few further questions so i can understand your set-up better:-

Is the PC you are trying to ping the stack from connected directly to a port on the stack?

Is the PC in the management VLAN?

Are the 450-1SXs used as trunk ports back to a core router/switch?


ports (TechnicalUser) (OP)
29 Sep 03 9:41
Yup!!! Jynxx I have made the stack as u have mentioned.

As u can see from my previous post, the stack is working, as i can access all the 5 units from the Base Unit through console connection.

Has anyonefaced this problem before.

Thanks and Regards,
FG

ports (TechnicalUser) (OP)
29 Sep 03 9:41
Yup!!! Jynxx I have made the stack as u have mentioned.

As u can see from my previous post, the stack is working, as i can access all the 5 units from the Base Unit through console connection.

Has anyone faced this problem before?

Thanks and Regards,
FG

ports (TechnicalUser) (OP)
29 Sep 03 9:46
Hi Allyc75,
      Here are the answers to ur questionS,


Is the PC you are trying to ping the stack from connected directly to a port on the stack?---YES

Is the PC in the management VLAN?----IF I MAKE THE PC IN THE MANAGEMENT VLAN, IT CAN PING THE STACK IP, BUT IF I TRY TO PING FROM ANY OTHER VLAN DEFINED ON THE SWITCH ...IT DOES NOT PING

Are the 450-1SXs used as trunk ports back to a core router/switch?---YES AND THE INTERVLAN ROUTING WORKS PERFECTLY FINE. ALSO IN THE CORE SWITCH (PASSPORT 8600) I CAN SEE THE ARP RESOLUTION OF THE STACK IP.

Hope my answers are clear.

Thanks and Regards,
FG
allyc75 (TechnicalUser)
29 Sep 03 9:57
Can you ping both the stack and the PC from the passport?
ports (TechnicalUser) (OP)
29 Sep 03 12:30
Hi allyc75,
         I CANNOT ping the Stack from the Passport. But i can Ping the PC.
Also i would like to mention that i can ping all the PC's connected to this stack, from the passport and from any other PC's in the LAN.

Strange isn't it???

Regards,
FG

Jynxx (IS/IT--Management)
29 Sep 03 14:21
Another dumb question...but is the base light lit on the 460 and off on the 450's?  Just checkin'

I assume the asnwer is yes.  So at this point I would definately start looking at the VLAN/uplink configuration.

Are you tagging VLAN's to the siwtches, or are you using the 2 fiber cards as an SMLT for redundant stack uplinks?

Maybe try removing one of the uplinks and do a standard single uplink port tagging config?
ports (TechnicalUser) (OP)
30 Sep 03 0:54
Hi Jynxx,
    Answers to ur questions,

Are you tagging VLAN's to the siwtches, or are you using the 2 fiber cards as an SMLT for redundant stack uplinks?
NO, I AM NOT TAGGING VLANS TO THE SWICHES, I AM USING SMLT TO THE PASSPORT ON REDUNDANT STACK UPLINKS.


Maybe try removing one of the uplinks and do a standard single uplink port tagging config?
I DID TRY TO USE ONLY A SINGLE UPLINK TO THE CORE PASSPORT SWITCH AND IT DIDN'T HELP.

Anyways, i am glad that i am getting so many responses.
This is getting more challenging.

Thanks and Regards,
FG
 
allyc75 (TechnicalUser)
30 Sep 03 7:01
FG

Are the uplink ports in the management VLAN on the Stack? Also are the ports on the passport linking to the stack in the management VLAN?

AC
ports (TechnicalUser) (OP)
30 Sep 03 23:59
Hi AC,
      YES , the ports on either side are in the management VLAN.
Also i have checked the ARP on the Passport, and found the MAC of the switch stack and vice versa.

Regards,
FG
1911man (MIS)
3 Oct 03 11:05
sounds like you need to tag the port from your passport to stack and vice versa.  Make sure the passport and stack uplink port have the same PVID as the management VLAN.

If you are running multiple VLANs on your stack you must have tagging enabled for layer 3 functionality.
1911man (MIS)
3 Oct 03 11:17
another thought.
The IP of the stack is in the same subnet as the management VLAN on the switch, RIGHT?
ports (TechnicalUser) (OP)
3 Oct 03 11:55
Hi 1911man,
        What u suggest is already enabledn on the passport,
i.e the IP stackIPis on the management VLAN and in the same subnet , also Tagging is enabled on the truck ports of both the passport and the Switch stack.

Regards,
FG.
Jynxx (IS/IT--Management)
3 Oct 03 13:19
If you absolutely can not get to the management, default the switches, remove the SMLT and all VLANs, go back to a single uplink, and go from there.  

If, after going back to an a-typical switch stack, you can ping it, reapply your SMLT and VLAN's...if it breaks, then there is a problem with how you are configuring it.
ports (TechnicalUser) (OP)
4 Oct 03 3:55
Hi Jynxx,
   I guess ur right. I will the config from scratch and see if it works.
I will keep u guys posted if it works.

Also, i would like to metion that, i have 3 such hybrid stacks, with the combination of 450's and 460's and none seem to work.

Thanks for all the inputs.

Regards,
FG.
rjenk (IS/IT--Management)
30 Oct 03 16:21
Just my two pennies...

Check the code rev on the other stacks...I bet they are running an older version of code.  I vaguely recall reading something about not being able to remotely manage switches unless you were on the management VLAN (no routing to the management VLAN).  I'll try to find the release notes or manual reference.

One thing to try...can you ping the switch from other switches on the network that are on the management VLAN?  Use the built-in PING function to test.

Because you state that the MAC is in the ARP table of the 8600, you know that layer 2 is working...this leaves it to be the issue above, a tagging issue or a routing issue.

Ray
niklasw (TechnicalUser)
10 Nov 03 2:52
Hi

Umm, if the PC isn't on the management VLAN, you cant ping the stack. That's how it should be.

/Niklas

-Cheers, Niklas

pgerth (TechnicalUser)
25 Nov 03 2:27
Niklas is correct , if the PC isn't in the same VLAN as the stack management the only way to get them to talk is to route between
the VLANS , that's one of th reasons you use VLANS , to seperate
broadcast domains . Test connectivity by pinging from the stack to
the gateway IP on the management VLAN that youve configured
on the 8600, then ping a gateway on another VLAN . From a PC
on another VLAN, can you ping or tracert to the management VLAN
gateway or subnet ? Is the subnet in the 8600 routing table ?

---paulg
ports (TechnicalUser) (OP)
28 Nov 03 22:34
Hi,
  The stack has 3 VLAN's defined. This stack is uplinked to the Passport 8600( For Inter VLAN routing).
The PC's connected to this Switch Stack can Ping all other PC's and Servers in my Network, but cannot ping the management IP of the switch. Infact No PC's in my network can Ping this Switch Stack. Also management IP for this stack present in the Passport routing table.

Thanks and Regards,
FG
jimbopalmer (Programmer)
28 Nov 03 23:33
which of the 3 VLANs is the management VLAN?  What is the IP range of that VLAN? what is the IP of the stack?

I tried to remain child-like, all I acheived was childish.

ports (TechnicalUser) (OP)
29 Nov 03 1:47
The Switch Stack has the following VLAN's defined,
1. 1049
2. 1043
3. 1048
The PC's connected to this Switch stack, belong to either one of the above VLAN's.

The Management VLAN is 1. and No PC's belong to the management VLAN.

This switch stack is connected  by UPLINK ports to the Passport, which does the Inter Vlan routing. The Trunking is configured properly with tagging for all VLAN's i.e 1049,1048,1043 and 1.

Please note we can Ping all PC's connected to this switch stack from anywhere in the network.

The Problem is that we cannot ping the management IP of the switch stack.

Thanks and Regards,
FG


jimbopalmer (Programmer)
30 Nov 03 19:33
I am going to assume you configured these on the Accelar as I would, and explain the IP numbering I would have used, in a further effort to get you to discuss the issue.

On the Accelar (presumably Spanning Tree 1, or Accelar 1, although I found that with more than 4 accelars this numbering broke down) I would have called the 1049 subnet 192.168.49.x and made the VLAN IP 192.168.49.1, while in the 1043 VLAN was 192.168.43.x and the VLAN IP was 192.168.43.1 and so forth

The management VLAN would be 192.168.0.x and the accelars VLAN IP would be 192.168.0.1, the baystacks would then be 192.168.0.10 to 192.168.0.250  you would be having trouble pinging 192.168.0.37 say, although you could ping 192.168.0.1 (the accelar) and perhaps even other baystacks (192.168.0.25, say)

With the Accelar 1200's the router's IP cannot be pinged unless you have link to at least one other device in the subnet, if you cannot ping even the accelars Management VLAN IP, (192.168.0..1 in my example) you may need to put one end user device in that subnet hooked to the Accelar, to bootstrap this. it should not be needed once the baystacks work.

If the Management VLAN is VLAN 1 but the IP address of the stack is NOT in the same subnet as the accelar's Management IP then you need to give the Baystack a Management IP in the Management VLAN.

If you did not give the accelar a IP in the Management VLAN, then it cannot route from any other VLAN. (in this scenario you would be able to ping Baystacks from each other, but not from the PCs)

I tried to remain child-like, all I acheived was childish.

ports (TechnicalUser) (OP)
30 Nov 03 23:57
Hi Jim,
     Thanks for the inputs. To clarify further,

A) The baystack switches are a combination of 450's and 460. With the 460 as the base unit.
This switch stack is uplinked to a Passport 8610.

B) Now reagrding the Management IP's for,
1. Baystack switches- 192.168.10.40/24
2. For the Passport 192.168.10.1/24
Both these switches have VLAN 1 as the management VLAN.

C) The software on the Baystack
Unit# Switch Model     MDA Model   GBIC Port   GBIC Port   Cascade SW Version
                                                           Module
----- ---------------- ----------- ----------- ----------- ------- ----------
  1   BayStack 460-24T None                               400-ST1 v3.0.0.54
  2   BayStack 450-24T 450-1SX                             400-ST1 v4.2.0.22
  3   BayStack 450-24T None                                400-ST1 v4.2.0.22
  4   BayStack 450-24T None                                400-ST1 v4.2.0.22
  5   BayStack 450-24T 450-1SX                             400-ST1 v4.2.0.22

D) To conclude i guess this is a problem with the combination of 460 and 450's in the stack.

If you have further suggestion, please do post the same.

Thanks and Regards,
FG
jimbopalmer (Programmer)
1 Dec 03 0:40
Ok, lets try to prove to ourselves it is not just a routing issue.

Try to telnet to 192.168.10.1  this should be the management IP port of the accelar

from that telnet, ping the 192.168.10.40 address, from the 10.1 address that should not need a route, so if it works, we have a routing issue, if it does NOT ping we have a baystack issue.

in a similar fashion we could Hyperterminal to the Baystack and ping the 192.168.10.1 address, but it should be easier if the ping works from the accelar.

if these pings work we can telnet to the 192.168.10.40 address from the 192.168.10.1 accelar, if not, it sure looks like the 460 is more different from a 450 than I know  (all I have are 450s)


if you CAN ping from the accelar, we need to look more at routing

I tried to remain child-like, all I acheived was childish.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close