Confusing VLAN/addressing scheme

[LORDxGOLD]

Hello all,
I am working on programming ~50 Avaya ERS 4800 switches. There's going to be quite a few stacks of about 7 switches each. I have been given a cut-sheet and other material to follow and according to it I am supposed to do this:

Stack IP address: 192.168.1.1
Management VLAN: 2
Switch IP address: 192.168.10.1
Default VLAN: 101

They want the switch IP address to be the address of the default VLAN (which I'm pretty sure just works by Avaya design) and the IP address of the stack to also be that of the management VLAN. Is that not impossible?

 

[amriddle01]

The Avaya IP Office forum is hardly the place for this question

 

[LORDxGOLD]

@amriddle01 - that was a typo on my end. Edited it to be appropriate

 

[intrigrant]

If you stack the Ciscos then all stacked switches is seen as one big switch.
So there will be only one VLAN ip address per VLAN for the complete stack.
The complete stack will also have only one MAC address, that of the stack master.

 

[LORDxGOLD]

@initgrant:
This is already understood. Whatever the default VLAN is is tied to the stack IP address. I could manipulate each switch to still have their own IP, but they would not be accessible through that address in the stack. My question is, could I have a vlan 101 on switch 1 that is tied to the Switch IP, and a vlan 2 (default vlan) tied to the stack IP?

 

[intrigrant]

No. As soon as you stack the switches it is considered by the IOS as one switch.
So any VLAN ip address belongs to all switches, the individual IP Adresses of the stacked switches are ignored/disabled.

 

[LORDxGOLD]

I figured out where my confusion lied:
Management VLAN is directly associated with stack IP
Default VLAN can be assigned it's own IP address
Stack IP address doesn't affect any VLANs

 

[derfloh]

AVAYA switches ignore the switch IP adresses if they work in a stack. They are only reachable through their common stack IP address. I usually delete the switch IP Adresses to avoid conflicts if the switch becomes a standalone switch again.

no ip address switch unit 1

will do it (replace the 1 for other units)

 

[LORDxGOLD]

@derfloh
The only reason I am configuring the switch IP addresses is that the "network engineers" for this client asked me to so that way if anything happened to the stack, they can access the switches individually (even though this would cause a slew of problems because the switch IPs are on a different subnet than the core switch IPs and much more).

 

[derfloh]

It makes no sense since the switch/stack will always be manageable throug it's configured management VLAN.

I think the easiest would be to let the IT walk to the switch with a laptop in case of trouble.

 

[LORDxGOLD]

@derfloh
Agreed and if I had the power that would be my job.

 

[mattKnight]

>I think the easiest would be to let the IT walk to the switch with a laptop in case of trouble

That solution really doesn't scale...

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.