Come diavolo si rimuovere un master da uno stack?
Ho tolto tutti i cavi, lasciando solo quelli sul membro slave.
il master è completamente libero da tutto eccetto i cavi di stack.
Spengo il master...... si ferma tutto. Vedo che lo slave ricalcola probabilmente l'STP (le porte diventano arancioni per circa 30 secondi) ma poi la connettività è persa.
La configurazione delle porte è identica a quella del master, ho controllato con un "sh run" , le porte sono su, i portchannel anche (ed hanno le porte al loro interno in UP) ma lo switch non "switcha".
Se riattacco il master e rimetto i cavi al loro posto, tutto riparte.
Quello che mi fa strano è che i cavi che arrivano sul membro slave sono diversi da quelli del master, e fino allo spegnimento del master essi funzionavano.
Mi spiego: lo stack è un centrostella in cui ci sono gli arrivi di alcuni switch 2960 le cui porte gigabit formano un portchannel verso i 3750 in stack. (una porta su un membro, una porta sull'altro).
Staccando le porte che arrivano sul master, tendo quindi solo quelle dello slave, tutto continua a funzionare, indice che i portchannel son configurati correttamente.
Però, se spengo il master, si ferma tutto.
Rimuovere il master dello stack
Moderatore: Federico.Lagni
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
credo sia un problema di STP.
innanzi tutto verifica chi è il Root Bridge ed eventualmente setta la priorità affinchè il ruolo di root bridge sia sul centro stella.
Abilita Rapid-STP, avrai sicuramente tempi di convergenza minori
Sulle porte in access-mode imposta Spanning-PortFast, in questo modo non devi aver nessun tipo di disservizio.
controlla che effettivamente il portchannell stia funzionando correttamente sia lato centro stella, sia lato periferico
usa il comando : Show etherchannel summary, dovrebbe esserti d'aiuto
Se il problema persiste facci sapere,
Se riesci a mandare uno schemino della rete è meglio...
ciao S.
innanzi tutto verifica chi è il Root Bridge ed eventualmente setta la priorità affinchè il ruolo di root bridge sia sul centro stella.
Abilita Rapid-STP, avrai sicuramente tempi di convergenza minori
Sulle porte in access-mode imposta Spanning-PortFast, in questo modo non devi aver nessun tipo di disservizio.
controlla che effettivamente il portchannell stia funzionando correttamente sia lato centro stella, sia lato periferico
usa il comando : Show etherchannel summary, dovrebbe esserti d'aiuto
Se il problema persiste facci sapere,
Se riesci a mandare uno schemino della rete è meglio...
ciao S.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Lo schema della rete è banale e possiamo così semplificare:
2 3750G in stack come centro stella.
1 2960 con le due porte gigabit in LACP verso i 3750G (una porta per ciascun 3750)
Sul centrostella non mi pare di avere porte in access, ma solo trunk.
STP c'è, ma non ci sono loop nella rete, altrimenti sia con il master che senza il loop si presenterebbe.
Ecco cosa ho fatto: ho preso TUTTI i cavi del master e li ho staccati, uno ad uno, a distanza di 30-60 secondi, in modo da assicurarmi che tutto stesso funzionando a dovere.
Così facendo, giocoforza, ho anche testato gli etherchannel dei 2960 verso i 3750, dal momento che una delle porte è stata staccata.
Tutto ha funzionato a dovere, il traffico era gestito solo dal 3750 slave, il master era completamente svincolato.
Fiero di ciò, ho staccato il cavo della corrente (del master ovviamente) tanto non avevo più nulla attaccato.
Le luci delle porte con i cavi sullo slave son diventate arancioni per alcuni secondi (ecco perchè credo abbia ricalcolato l'albero STP) per poi tornare verdi e lampeggianti come di consueto, ma la rete è crollata.
Non può essere un problema di loop, perchè con master acceso e spento, come topologia di rete non cambia nulla, ripeto, il master non ha cavi attaccati e se non ci sono cavi non ci sono nemmeno loop.
E' come se lo slave avesse perso completamente la configurazione delle VLAN e delle porte in trunk, ma non è così perchè:
1) sh run mostra la configurazione corretta
2) le interfacce sono configurate a modo
3) gli apparati fuori vlan avrebbero dovuto continuare a funzionare anche se lo switch avesse perso la configurazione delle vlan stess, essendone fuori.
Ho risolto solo ricollegando il master e per non sapere ne leggere ne scrivere, riattaccando anche i cavi.
Quindi una domanda è d'obblgo: non basta staccare i cavi e spegnere lo switch? dopo tutto, se si dovesse rompere all'improvviso o dovesse saltare la luce, una persona non sarebbe in grado di fargli fare il takeover a mano e non avrebbe senso lo stack in se per se.
2 3750G in stack come centro stella.
1 2960 con le due porte gigabit in LACP verso i 3750G (una porta per ciascun 3750)
Sul centrostella non mi pare di avere porte in access, ma solo trunk.
STP c'è, ma non ci sono loop nella rete, altrimenti sia con il master che senza il loop si presenterebbe.
Ecco cosa ho fatto: ho preso TUTTI i cavi del master e li ho staccati, uno ad uno, a distanza di 30-60 secondi, in modo da assicurarmi che tutto stesso funzionando a dovere.
Così facendo, giocoforza, ho anche testato gli etherchannel dei 2960 verso i 3750, dal momento che una delle porte è stata staccata.
Tutto ha funzionato a dovere, il traffico era gestito solo dal 3750 slave, il master era completamente svincolato.
Fiero di ciò, ho staccato il cavo della corrente (del master ovviamente) tanto non avevo più nulla attaccato.
Le luci delle porte con i cavi sullo slave son diventate arancioni per alcuni secondi (ecco perchè credo abbia ricalcolato l'albero STP) per poi tornare verdi e lampeggianti come di consueto, ma la rete è crollata.
Non può essere un problema di loop, perchè con master acceso e spento, come topologia di rete non cambia nulla, ripeto, il master non ha cavi attaccati e se non ci sono cavi non ci sono nemmeno loop.
E' come se lo slave avesse perso completamente la configurazione delle VLAN e delle porte in trunk, ma non è così perchè:
1) sh run mostra la configurazione corretta
2) le interfacce sono configurate a modo
3) gli apparati fuori vlan avrebbero dovuto continuare a funzionare anche se lo switch avesse perso la configurazione delle vlan stess, essendone fuori.
Ho risolto solo ricollegando il master e per non sapere ne leggere ne scrivere, riattaccando anche i cavi.
Quindi una domanda è d'obblgo: non basta staccare i cavi e spegnere lo switch? dopo tutto, se si dovesse rompere all'improvviso o dovesse saltare la luce, una persona non sarebbe in grado di fargli fare il takeover a mano e non avrebbe senso lo stack in se per se.
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
ok ho chiaro la topologia della rete, ti confermo che il comportamento è anomalo.
Spegnendo il master non devi aver nessun tipo di disservizio.
Verifica chi è il root bridge e tutto quello che ti ho scritto prima.
Da qualche parte ci deve essere un inghippo.
ciao S.
Spegnendo il master non devi aver nessun tipo di disservizio.
Verifica chi è il root bridge e tutto quello che ti ho scritto prima.
Da qualche parte ci deve essere un inghippo.
ciao S.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Appena vado in ufficio verifico, ma toglimi una curiosità: se il master non ha cavi attaccati, e la rete con i cavi connessi allo slave è esente da loop, per quale motivo il rootbridge debba arrecare problemi spegnendo il master? Se non ci son loop con il master acceso, non ci saranno nemmeno anche a master spento e la topologia non vedo come possa cambiare.
L'elezione di un nuovo root bridge dovrebbe essere indolore e non generare alcun cambio di porte in blocking, visto che non ci sono loop.
L'elezione di un nuovo root bridge dovrebbe essere indolore e non generare alcun cambio di porte in blocking, visto che non ci sono loop.
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
confermo ma visto che si presenta una anomalia ci deve essere qualcosa di configurato non a dovere.
Lo switch slave potrebbe considerare lo spegnimento dello switch master come una topology change e non essendo il root bridge mettere le porte in listenin-learnin etc...
E' una supposizione... ma da qualche parte si deve pur cominciare...
verifica anche che su tutti gli switch della tua rete ci sia implementata la stessa versione di span-tree.
Le porte di Uplink fra i vari switch sono configurate in Trunk ? ci passano delle Vlan ?
Ti consiglio Rapid-PVST.
a disposizione ciao S.
Lo switch slave potrebbe considerare lo spegnimento dello switch master come una topology change e non essendo il root bridge mettere le porte in listenin-learnin etc...
E' una supposizione... ma da qualche parte si deve pur cominciare...
verifica anche che su tutti gli switch della tua rete ci sia implementata la stessa versione di span-tree.
Le porte di Uplink fra i vari switch sono configurate in Trunk ? ci passano delle Vlan ?
Ti consiglio Rapid-PVST.
a disposizione ciao S.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Posso fare tutte le prove che vuoi, ma NON posso spegnere di nuovo il master per vedere che succede se non quando ho una certezza quasi matematica che tutto funzionerà.
Oggi ho già passato dei bei 5 minuti.
La versione STP non so dirti se è uguale ovunque, visto che gli apparati non sono accessibili da remoto, come posso settare la stessa versione su tutti?
Preferirei una versione non proprietaria cisco, se possibile.
Si, le porte di uplink sono in trunk con alcune vlan.
Adesso ti mando l'output di show switch e show spanning-tree
Oggi ho già passato dei bei 5 minuti.
La versione STP non so dirti se è uguale ovunque, visto che gli apparati non sono accessibili da remoto, come posso settare la stessa versione su tutti?
Preferirei una versione non proprietaria cisco, se possibile.
Si, le porte di uplink sono in trunk con alcune vlan.
Adesso ti mando l'output di show switch e show spanning-tree
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
ok gira pure,
il fatto che gli switch non sono accessibili da remoto è un po una pecca.....
Rapid-STPV non mi risulta sia propietario Cisco, magari non è supportato da switch un po datati, ma nella rete sono presenti device non cisco ?
cmq per settare la versione, in global mode : spanning-tree mode rapid-pvst
ciao
il fatto che gli switch non sono accessibili da remoto è un po una pecca.....
Rapid-STPV non mi risulta sia propietario Cisco, magari non è supportato da switch un po datati, ma nella rete sono presenti device non cisco ?
cmq per settare la versione, in global mode : spanning-tree mode rapid-pvst
ciao
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Codice: Seleziona tutto
#show switch detail
Switch/Stack Mac Address : 108c.cfc7.4100
H/W Current
Switch# Role Mac Address Priority Version State
----------------------------------------------------------
1 Member 0014.69e6.6500 15 0 Ready
*2 Master 108c.cfc7.4100 1 0 Ready
Stack Port Status Neighbors
Switch# Port 1 Port 2 Port 1 Port 2
--------------------------------------------------------
1 Ok Ok 2 2
2 Ok Ok 1 1
Codice: Seleziona tutto
#show etherchannel summary
Flags: D - down P - bundled in port-channel
I - stand-alone s - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 7
Number of aggregators: 7
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
1 Po1(SU) LACP Gi1/0/1(P) Gi2/0/1(P)
2 Po2(SU) LACP Gi1/0/3(P) Gi2/0/3(P)
3 Po3(SU) LACP Gi1/0/21(D) Gi1/0/22(D) Gi2/0/21(P)
Gi2/0/22(P)
4 Po4(SU) LACP Gi1/0/5(P) Gi2/0/5(P)
5 Po5(SU) LACP Gi1/0/23(P) Gi2/0/23(P)
6 Po6(SD) LACP Gi1/0/24(D) Gi2/0/24(D)
7 Po7(SD) LACP Gi2/0/17(D)
Codice: Seleziona tutto
Switch#show spanning-tree summary
Switch is in pvst mode
Root bridge for: VLAN1001, VLAN1010, VLAN1105
Extended system ID is enabled
Portfast Default is disabled
PortFast BPDU Guard Default is disabled
Portfast BPDU Filter Default is disabled
Loopguard Default is disabled
EtherChannel misconfig guard is enabled
UplinkFast is disabled
BackboneFast is disabled
Configured Pathcost method used is short
Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN0001 0 0 0 6 6
VLAN0401 0 0 0 3 3
VLAN0501 0 0 0 3 3
VLAN0551 0 0 0 3 3
VLAN0552 0 0 0 3 3
VLAN0701 0 0 0 3 3
VLAN1001 0 0 0 2 2
VLAN1010 0 0 0 1 1
VLAN1050 0 0 0 3 3
Name Blocking Listening Learning Forwarding STP Active
---------------------- -------- --------- -------- ---------- ----------
VLAN1104 0 0 0 3 3
VLAN1105 0 0 0 1 1
VLAN1401 0 0 0 3 3
---------------------- -------- --------- -------- ---------- ----------
12 vlans 0 0 0 34 34
Switch#show spanning-tree
VLAN0001
Spanning tree enabled protocol ieee
Root ID Priority 32769
Address 001b.0dea.b900
Cost 3
Port 512 (Port-channel4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi2/0/19 Desg FWD 19 128.73 P2p
Po1 Desg FWD 3 128.488 P2p
Po2 Desg FWD 3 128.496 P2p
Po3 Desg FWD 3 128.504 P2p
Po4 Root FWD 3 128.512 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN0401
Spanning tree enabled protocol ieee
Root ID Priority 33169
Address 001b.0dea.b900
Cost 3
Port 512 (Port-channel4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33169 (priority 32768 sys-id-ext 401)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
Po4 Root FWD 3 128.512 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN0501
Spanning tree enabled protocol ieee
Root ID Priority 33269
Address 0023.5d10.5980
Cost 3
Port 496 (Port-channel2)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33269 (priority 32768 sys-id-ext 501)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po2 Root FWD 3 128.496 P2p
Po3 Desg FWD 3 128.504 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN0551
Spanning tree enabled protocol ieee
Root ID Priority 33319
Address 001b.0dea.b900
Cost 3
Port 512 (Port-channel4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33319 (priority 32768 sys-id-ext 551)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
Po4 Root FWD 3 128.512 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN0552
Spanning tree enabled protocol ieee
Root ID Priority 33320
Address 001b.0dea.b900
Cost 3
Port 512 (Port-channel4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33320 (priority 32768 sys-id-ext 552)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
Po4 Root FWD 3 128.512 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN0701
Spanning tree enabled protocol ieee
Root ID Priority 33469
Address 001b.0dea.b900
Cost 3
Port 512 (Port-channel4)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33469 (priority 32768 sys-id-ext 701)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
Po4 Root FWD 3 128.512 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN1001
Spanning tree enabled protocol ieee
Root ID Priority 33769
Address 108c.cfc7.4100
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33769 (priority 32768 sys-id-ext 1001)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN1010
Spanning tree enabled protocol ieee
Root ID Priority 33778
Address 108c.cfc7.4100
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33778 (priority 32768 sys-id-ext 1010)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
VLAN1050
Spanning tree enabled protocol ieee
Root ID Priority 33818
Address 001b.5361.4780
Cost 3
Port 488 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33818 (priority 32768 sys-id-ext 1050)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po1 Root FWD 3 128.488 P2p
Po3 Desg FWD 3 128.504 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN1104
Spanning tree enabled protocol ieee
Root ID Priority 33872
Address 001b.5361.4780
Cost 3
Port 488 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33872 (priority 32768 sys-id-ext 1104)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po1 Root FWD 3 128.488 P2p
Po3 Desg FWD 3 128.504 P2p
Po5 Desg FWD 3 128.520 P2p
VLAN1105
Spanning tree enabled protocol ieee
Root ID Priority 33873
Address 108c.cfc7.4100
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 33873 (priority 32768 sys-id-ext 1105)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po3 Desg FWD 3 128.504 P2p
VLAN1401
Spanning tree enabled protocol ieee
Root ID Priority 34169
Address 001b.5361.4780
Cost 3
Port 488 (Port-channel1)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 34169 (priority 32768 sys-id-ext 1401)
Address 108c.cfc7.4100
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300 sec
Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Po1 Root FWD 3 128.488 P2p
Po3 Desg FWD 3 128.504 P2p
Po5 Desg FWD 3 128.520 P2p
Switch#show spanning-tree detail
VLAN0001 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 32769, address 001b.0dea.b900
Root port is 512 (Port-channel4), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 27 last change occurred 04:41:20 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 73 (GigabitEthernet2/0/19) of VLAN0001 is designated forwarding
Port path cost 19, Port priority 128, Port Identifier 128.73.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 108c.cfc7.4100
Designated port id is 128.73, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9037, received 0
Port 488 (Port-channel1) of VLAN0001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.488.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 108c.cfc7.4100
Designated port id is 128.488, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8998, received 6
Port 496 (Port-channel2) of VLAN0001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.496.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 108c.cfc7.4100
Designated port id is 128.496, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8990, received 13
Port 504 (Port-channel3) of VLAN0001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8998, received 0
Port 512 (Port-channel4) of VLAN0001 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.512.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 001b.0dea.b900
Designated port id is 128.56, designated path cost 0
Timers: message age 2, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 534, received 8470
Port 520 (Port-channel5) of VLAN0001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 32769, address 001b.0dea.b900
Designated bridge has priority 32769, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8999, received 0
VLAN0401 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 401, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33169, address 001b.0dea.b900
Root port is 512 (Port-channel4), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 17 last change occurred 04:41:27 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN0401 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33169, address 001b.0dea.b900
Designated bridge has priority 33169, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8997, received 0
Port 512 (Port-channel4) of VLAN0401 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.512.
Designated root has priority 33169, address 001b.0dea.b900
Designated bridge has priority 33169, address 001b.0dea.b900
Designated port id is 128.56, designated path cost 0
Timers: message age 2, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 532, received 8472
Port 520 (Port-channel5) of VLAN0401 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33169, address 001b.0dea.b900
Designated bridge has priority 33169, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8998, received 0
VLAN0501 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 501, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33269, address 0023.5d10.5980
Root port is 496 (Port-channel2), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 12 last change occurred 04:41:30 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 496 (Port-channel2) of VLAN0501 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.496.
Designated root has priority 33269, address 0023.5d10.5980
Designated bridge has priority 33269, address 0023.5d10.5980
Designated port id is 128.56, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 17, received 8945
Port 504 (Port-channel3) of VLAN0501 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33269, address 0023.5d10.5980
Designated bridge has priority 33269, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8948, received 0
Port 520 (Port-channel5) of VLAN0501 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33269, address 0023.5d10.5980
Designated bridge has priority 33269, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8948, received 0
VLAN0551 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 551, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33319, address 001b.0dea.b900
Root port is 512 (Port-channel4), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 17 last change occurred 04:41:33 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN0551 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33319, address 001b.0dea.b900
Designated bridge has priority 33319, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9000, received 0
Port 512 (Port-channel4) of VLAN0551 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.512.
Designated root has priority 33319, address 001b.0dea.b900
Designated bridge has priority 33319, address 001b.0dea.b900
Designated port id is 128.56, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 532, received 8475
Port 520 (Port-channel5) of VLAN0551 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33319, address 001b.0dea.b900
Designated bridge has priority 33319, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9000, received 0
VLAN0552 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 552, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33320, address 001b.0dea.b900
Root port is 512 (Port-channel4), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 16 last change occurred 04:41:35 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN0552 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33320, address 001b.0dea.b900
Designated bridge has priority 33320, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9002, received 0
Port 512 (Port-channel4) of VLAN0552 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.512.
Designated root has priority 33320, address 001b.0dea.b900
Designated bridge has priority 33320, address 001b.0dea.b900
Designated port id is 128.56, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 532, received 8477
Port 520 (Port-channel5) of VLAN0552 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33320, address 001b.0dea.b900
Designated bridge has priority 33320, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9002, received 0
VLAN0701 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 701, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33469, address 001b.0dea.b900
Root port is 512 (Port-channel4), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 13 last change occurred 04:41:39 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN0701 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33469, address 001b.0dea.b900
Designated bridge has priority 33469, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9001, received 0
Port 512 (Port-channel4) of VLAN0701 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.512.
Designated root has priority 33469, address 001b.0dea.b900
Designated bridge has priority 33469, address 001b.0dea.b900
Designated port id is 128.56, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 14, received 9002
Port 520 (Port-channel5) of VLAN0701 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33469, address 001b.0dea.b900
Designated bridge has priority 33469, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9002, received 0
VLAN1001 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1001, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
We are the root of the spanning tree
Topology change flag not set, detected flag not set
Number of topology changes 8 last change occurred 04:41:42 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN1001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33769, address 108c.cfc7.4100
Designated bridge has priority 33769, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8988, received 0
Port 520 (Port-channel5) of VLAN1001 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33769, address 108c.cfc7.4100
Designated bridge has priority 33769, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8989, received 0
VLAN1010 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1010, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
We are the root of the spanning tree
Topology change flag not set, detected flag not set
Number of topology changes 5 last change occurred 04:41:43 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 1, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN1010 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33778, address 108c.cfc7.4100
Designated bridge has priority 33778, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8990, received 0
VLAN1050 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1050, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33818, address 001b.5361.4780
Root port is 488 (Port-channel1), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 13 last change occurred 04:41:45 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 488 (Port-channel1) of VLAN1050 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.488.
Designated root has priority 33818, address 001b.5361.4780
Designated bridge has priority 33818, address 001b.5361.4780
Designated port id is 128.56, designated path cost 0
Timers: message age 2, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 14, received 9003
Port 504 (Port-channel3) of VLAN1050 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33818, address 001b.5361.4780
Designated bridge has priority 33818, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9005, received 0
Port 520 (Port-channel5) of VLAN1050 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33818, address 001b.5361.4780
Designated bridge has priority 33818, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9005, received 0
VLAN1104 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1104, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 33872, address 001b.5361.4780
Root port is 488 (Port-channel1), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 13 last change occurred 04:41:47 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 488 (Port-channel1) of VLAN1104 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.488.
Designated root has priority 33872, address 001b.5361.4780
Designated bridge has priority 33872, address 001b.5361.4780
Designated port id is 128.56, designated path cost 0
Timers: message age 2, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 14, received 9004
Port 504 (Port-channel3) of VLAN1104 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33872, address 001b.5361.4780
Designated bridge has priority 33872, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9006, received 0
Port 520 (Port-channel5) of VLAN1104 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.520.
Designated root has priority 33872, address 001b.5361.4780
Designated bridge has priority 33872, address 108c.cfc7.4100
Designated port id is 128.520, designated path cost 3
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 9006, received 0
VLAN1105 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1105, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
We are the root of the spanning tree
Topology change flag not set, detected flag not set
Number of topology changes 5 last change occurred 04:41:51 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 1, topology change 0, notification 0, aging 300
Port 504 (Port-channel3) of VLAN1105 is designated forwarding
Port path cost 3, Port priority 128, Port Identifier 128.504.
Designated root has priority 33873, address 108c.cfc7.4100
Designated bridge has priority 33873, address 108c.cfc7.4100
Designated port id is 128.504, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 8993, received 0
VLAN1401 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, sysid 1401, address 108c.cfc7.4100
Configured hello time 2, max age 20, forward delay 15
Current root has priority 34169, address 001b.5361.4780
Root port is 488 (Port-channel1), cost of root path is 3
Topology change flag not set, detected flag not set
Number of topology changes 12 last change occurred 04:41:52 ago
from StackPort2
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 488 (Port-channel1) of VLAN1401 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.488.
Designated root has priority 34169, address 001b.5361.4780
Designated bridge has priority 34169, address 001b.5361.4780
Designated port id is 128.56, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 13, received 9007
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Non ho ancora avuto modo di terminare la configurazione della rete, per ora posso solo accedere da console.sanga ha scritto:il fatto che gli switch non sono accessibili da remoto è un po una pecca.....
Si, ci sono alcuni Procurve in giro, ma non sono direttamente connessi alla rete cisco (però, è anche in questi casi che STP fa comodo: se un pirlone dovesse incrociare le due reti....)Rapid-STPV non mi risulta sia propietario Cisco, magari non è supportato da switch un po datati, ma nella rete sono presenti device non cisco ?
R-STPV non è RSTP, vero ? Sui Procurve sono in RSTP.
Mi fa il ricalcolo di topologia con conseguente down delle porte?cmq per settare la versione, in global mode : spanning-tree mode rapid-pvst
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Uhm, quel Design FWD per una data vlan, sul portchannel sbagliato con mi convince.
Il root è giusto, gli altri due designated però non dovrebbero esserci credo. Non ci sono più path per raggiungere tale destinazione.
Che sia cambiato il root e di conseguenza il portchannel associato a tali VLAN ?
Il root è giusto, gli altri due designated però non dovrebbero esserci credo. Non ci sono più path per raggiungere tale destinazione.
Che sia cambiato il root e di conseguenza il portchannel associato a tali VLAN ?
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
cavolo hai in giro anche dei Procurve ???
non credo supportino lo spannig-tree per Vlan....
o metti tutto spantree oppure sui cisco configura MST e metti tutte le Vlan dentro la stessa istanza.
L'ho già fatto da un cliente e funzionava, cosi hai i tempi di convergenza del Rapid STP.
Cmq non mi sembra giusto il root bridge, almeno non per tutte le Vlan
non credo supportino lo spannig-tree per Vlan....
o metti tutto spantree oppure sui cisco configura MST e metti tutte le Vlan dentro la stessa istanza.
L'ho già fatto da un cliente e funzionava, cosi hai i tempi di convergenza del Rapid STP.
Cmq non mi sembra giusto il root bridge, almeno non per tutte le Vlan
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
sanga
- Cisco power user
- Messaggi: 75
- Iscritto il: ven 23 set , 2011 1:14 pm
scusa cosa intendi con :
Si, ci sono alcuni Procurve in giro, ma non sono direttamente connessi alla rete cisco
sono installati negli stessi armadi ma non sono connessi alla stessa rete o cosa ???
Si, ci sono alcuni Procurve in giro, ma non sono direttamente connessi alla rete cisco
sono installati negli stessi armadi ma non sono connessi alla stessa rete o cosa ???
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
Se vuoi una garanzia, compra un tostapane.
___________________________________
-
ale123
- Cisco enlightened user
- Messaggi: 162
- Iscritto il: ven 04 dic , 2009 9:43 am
Sono negli stessi armadi, ma formano una rete separata. Le due reti non sono interconnesse tra loro.sanga ha scritto:scusa cosa intendi con :
Si, ci sono alcuni Procurve in giro, ma non sono direttamente connessi alla rete cisco
sono installati negli stessi armadi ma non sono connessi alla stessa rete o cosa ???
Una è interamente cisco, l'altra è interamente procurve.
Ma l'RSTP "normale" su cisco come si attiva? Ho cercato nella documentazione tempo fa ma non trovai nulla in merito.
