ip+training+(dallas),+2+day

BSC3i Gb over IP presentationBSC IP Connectivity 2007 Dallas Use Slide show mode

Customer Confidential 1 Nokia Siemens Networks

IP Training/Timo Eloranta

ContentBSC IP introduction Redundancy models VLAN Spanning tree L2 and L3 technologies Gb over IP troubleshooting


IP training 2007/Timo Eloranta

IP connectivity in Mobile NetworksBSC Site Architecture conforms with Controller/Core Site Architecture in IP Connectivity in Mobile Networks solution description. BSC Site IP Connectivity Guidelines documentation presents BSC solution.NetAct BSC site= L2/L3 site switch

= IP/Ethernet = IP/SDH or PDH= site edge router

BSC IP BackboneGGSN

BSC

GGSN Other IP NE

BSC BSC MSC

SGSN

Core site

BSC siteCustomer Confidential 3 Nokia Siemens Networks IP training 2007/Timo Eloranta

BSC3i IP architecture Ethernet interfaces in BSC 3i O&M Lb/SMLC BBI/BSC-BSC A (signaling) Gb over IP LDI



BSC IP interfaces (related to Gb over IP)BSCOMU SWUsFTP TCP Telnet

O&MNetAct ClusterSNMP/TFTP/DHC P

IP ETHERNET

O&M

UDP

TELNE T TCP

Q3O&MBSSGP NS

MCMUs

IP ETHERNET

LDILAN Device Integration PCUs Gb Over IP

UDP IP ETHERNET

GbInternet Protocol (RFC 791) Internet Protocol, version 6 (RFC 2460)

SGSN

DNSDNS serverCustomer Confidential 5 Nokia Siemens Networks

Transmission Control Protocol (RFC 793) User Datagram Protocol (RFC 768) Stream Control Transmission Protocol (RFC 2960) Ethernet (IEEE 802.3)


Communication Network: CPULAN and PCULAN BSC3i 660BSC3i CPULANSWU-0 OMU OMU OMU MCMU MCMU MCMU BCSU BCSU BCSU

BSC IP Site

Backbone

SWU-1 Spanning Virtual gateway Routing protocol

IP backbone

PCULANPCU PCU PCU SWU-2

tree

Site Edge Routers/Switches e.g. Cisco 6500, 7200 or 7600 series L2/L3 Site Switches e.g. Cisco 3550/3750

SWU-3

L2 Switch ESB20-A / ESB26Customer Confidential 6 Nokia Siemens Networks IP training 2007/Timo Eloranta

BSC3i 1000, SWU0-5 BSC3i 1000, SWU0-5




Interface RedundancyUNIT-n (WOEX) Logical & carrier sense active 172.16.2.2

carrier sense backup (172.16.2.2)

0

1

Interface redundancy may be used to backup IP address assigned for Ethernet or VLAN interfaces inside the same computer unit. In a case physical link fails, a Carrier Sense IP address is quickly moved to the back-up interface and a gratuitous ARP is broadcasted to advertise the MAC address of the new active interface. Status changes at the physical link are detected by device interrupt and the redundant IP address switchover is therefore nearly transparent action for IP user applications; meaning redundant IP addressing switchover has no effect on established TCP/IP connections. The interface redundancy is used in OMU and PCU.



Logical IP addressingUNIT-1 (SP)-> (WO)

UNIT-0 (WO)-> (TE/SP) Logical & carrier sense active 172.16.2.2


Logical & carrier sense active 172.16.2.2


0

1

0

1

Logical IP addressing based redundancy model may be used to hide internal failover actions and remain serving IP address as the same for the remote peer-end application over the local unit switchover. Notice that only the IP address is able to remain over unit switchover and all existing IP connections are lost since the TCP/IP stack and local IP applications of DX200 are not warmed and not able to move established connections from the failing unit to the another working one. The logical IP addressing is used in PCU.



Spanning Tree ProtocolSpanning tree opens the shortest and the fastest path to backbone Port roles (root, designated, alternate, backup), Port states (Discarding, Learning, Forwarding) Prevention of network loopsIP backboneSite switch-1 Site

IP backbone

switch-2

MSTP

MSTP

SWU-2

SWU-3

SWU-2

SWU-3

PCUCustomer Confidential 10 Nokia Siemens Networks IP training 2007/Timo Eloranta

PCU

Multiple Spanning Tree (MSTP)SWU:! Protocol configuration: ! protocol ! ! MSTP configuration: ! mstp enable ! mstp name BSC_Plat instance 0 vlan 1-99,101-199,201-4094 instance 1 vlan 100 instance 2 vlan 200 interface 1/1/22 name gb mstp edge-port default vlan 800 ! interface 1/1/23 name cisco0 duplex-speed full-1000 mstp link-type point-to-point

Site Switch:spanning-tree mode mst spanning-tree extend system-id ! spanning-tree mst configuration name BSC_Plat revision 1 instance 1 vlan 100

instance 2 vlan 200spanning-tree mst 0-1 priority 24576 spanning-tree mst 2 priority 28672 interface GigabitEthernet1/0/3

description swu0_BSC1switchport trunk encapsulation dot1q switchport trunk allowed vlan 100 switchport mode trunk switchport nonegotiate duplex full

speed 100spanning-tree link-type point-to-point



Rapid Spanning Tree (RSTP)Site Switch:spanning-tree mode mst spanning-tree extend system-id ! spanning-tree mst configuration name BSCsite revision 1 ! spanning-tree mst 0 priority 24576 interface GigabitEthernet1/0/3 description swu0_BSC1 switchport trunk encapsulation dot1q switchport trunk allowed vlan 100

SWU:! Protocol configuration: ! protocol ! ! RSTP configuration: ! rapid-spanning-tree enable ! interface 1/1/22 name gb rapid-spanning-tree edge-port default vlan 800 ! interface 1/1/23 name cisco0 duplex-speed full-1000

switchport mode trunkswitchport nonegotiate duplex full speed 100 spanning-tree link-type point-to-point



Virtual GatewayVirtual Gateway works by the exchange of multicast messages that advertise priority among configured routers. When the active router fails to send a hello message within a configurable period of time, the standby router with the highest priority takes the virtual address and becomes the active router. Cisco has own Cisco Specific Hot Standby Routing Protocol (HSRP) for router redundancy.IP backbone IP backbone

Site switch-1

HSRP

Site switch-2

HSRP HSRP

Virtual Gateway

Virtual Gateway

SWU-2

SWU-3

SWU-2

SWU-3

PCUCustomer Confidential 13 Nokia Siemens Networks

Default gateway

Same IP address

Default gateway

PCU


Virtual gateway (HSRP)BSC:ZQKB; LOADING PROGRAM VERSION 4.18-0 BSC3i BSC1 2007-09-03 11:28:25

INTERROGATED STATIC ROUTES UNIT ------------------BCSU-0 -PCU2D-3 BCSU-0 -PCU2D-4 BCSU-0 -PCU2D-5 BCSU-0 -PCU2D-6 COMMAND EXECUTED DESTINATION -----------------DEFAULT ROUTE DEFAULT ROUTE DEFAULT ROUTE DEFAULT ROUTE GATEWAY ADDRESS -----------------10.16.137.129 10.16.137.129 10.16.137.129 10.16.137.129 ROUTE TYPE ----LOG LOG LOG LOG NBR ---------2 3 4 5

Site Switch:interface Vlan100 description gb

ip address 10.16.137.130 255.255.255.192no ip proxy-arp standby 2 ip 10.16.137.129 standby 2 timers msec 500 2 standby 2 preempt delay minimum 60 !Customer Confidential 14 Nokia Siemens Networks IP training 2007/Timo Eloranta

Site Switch IP, VLAN subnet virtual gateway address failure supervision returning from failure

EtherChannelCiscos EtherChannel allows to bundle identical physical ports together to form one logical port. IEEE 802.3ad uses term Link Aggregation Group for the same functionality, also called port or link trunking.

SWU GSREtherChannel Trunking Gigabit Ethernet x 2

SWU



Backbone routing protocolsWith routing protocols (e.g. Open Shortest Path First (OSPF)) the alternative routes to the service are advertised. Using the routing protocols neighbouring routers discover link failures and are able to route traffic to the surviving links .IP backbone

IP backboneSite switch-1 Site switch-2

OSPF

OSPF

SWU-2

SWU-3

SWU-2

SWU-3

PCU

PCU



Redundancies overallRedundant IP backbone may provide different IP path for sent and received IP packet. MSTP manages ports in the switches and opens the best path between assigned IFETH and L2/L3 switch. Switchover from root to alternate port takes 200 ms (even 100ms) Virtual Gateway address HSRP switchover takes 1-5 seconds by tuned timers (L2 recovery takes 100200ms)MSTP

SGSNIP backboneHSRP gateway MSTP instance Gb

Site Switch 2 MSTP ROOT 1 Interface change Site Switch Site Switch 2 failure failure

ROOT

SWU-2

SWU-3

Site Switch, ESB and Backbone redundancies (HW) Interface redundance andLogical interface PCUIP packet






BSC3i 660 CPULAN, ESB20-ASite

All VLANs tagged in TRUNKs1 or 2

Site switch-2

switch-1

10/100BASE-T/Tx Fast Ethernets 1 or 2 19 19 20 9 10 11 12

Exception:Lb-1 and -2 tagged9 10 11 12

SWU-0ESB20-A in MCMU-02013 14 15 16 17

SWU-113 14

ESB20-A in MCMU-1

18

15

16

17

18

Untagged0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

MCMU-0 MCMU-1Lb-1 VLAN Lb-2 VLAN Lb-1 VLAN Lb-2 VLAN

OMUO&M

BCSU-0 BCSU-1 BCSU-2 BCSU-3 BCSU-4 BCSU-5 BCSU-6A/BBI-1 VLAN A/BBI-2 VLAN A/BBI-1 VLAN A/BBI-2 VLAN A/BBI-1 VLAN A/BBI-2 VLAN A/BBI-1 VLAN A/BBI-2 A/BBI-1 VLAN A/BBI-2 VLAN A/BBI-1 VLAN A/BBI-2 A/BBI-1 VLAN A/BBI-2

VLAN

VLAN

VLAN

VLAN



BSC3i 660 PCULAN, ESB20-AGb VLAN tagged in TRUNKs10/100BASE-T/Tx Fast Ethernets 1 or 2 19 19 20 1 or 2

Site switch-1

Site switch-2

SWU-256 7 8 9

ESB20-A in MCMU-0 20

SWU-36 7 8 9

ESB20-A in MCMU-1

10 11 12 13 14 15 16 17 18

5

10 11 12 13 14 15 16 17 18

UntaggedPCU PCU 4/3 GbBCSU-0 VLAN

PCU 6/5

PCU 4/3

PCU 6/5 Gb

PCU 4/3

PCU 6/5 Gb

PCU 4/3

PCU 6/5

PCU 4/3 Gb

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

6/5

GbBCSU-1

GbBCSU-5

GbBCSU-6

VLAN

BCSU-2

VLAN

BCSU-3

VLAN

BCSU-4

VLAN

VLAN

VLAN



VLAN configuration SWUCreate vlan and add ports to the vlanvlan create gb config gb add ports add ports add ports 100 1/1/1,1/1/2,1/1/19,1/1/20 tagged trunk ports, egress rule 1/1/5-1/1/18 untagged host ports default 1/1/5-1/1/18 ingress rule

Default vlan for untagged Host portinterface 1/1/10 name gb mstp edge-port default vlan 100 ingress rule

Default vlan is not needed for tagged host port (Lb)interface 1/1/10 name lb-1 mstp edge-port



VLAN configuration Site SwitchVLAN introduction in Site Switchinterface Vlan100 description gb ip address 10.1.4.2 255.255.255.192 no ip proxy-arp standby 1 ip 10.1.4.1 standby 1 priority 100 standby 1 timers msec 500 2 standby 1 preempt delay minimum 60

Set the VLAN to be allowed in uplinkinterface GigabitEthernet1/0/2 description swu2 switchport trunk encapsulation dot1q switchport trunk allowed vlan 11,100 ingress and egress rules switchport mode trunk switchport nonegotiate duplex full speed 100 spanning-tree link-type point-to-point



Gb over IP (BSC site) / IP addresses1 subnet for each BSC, which includes following IP addresses: 1 address for each PCU (LOG) 1 address for PCU GW (HSRP for Gb VLAN) 1 address for Site Switch 1 (Gb VLAN) 1 address for Site Switch 2 (Gb VLAN)1 or 2 19 19 20 5 6 7 8 9

L2/L3 switch - 1GW-1 GW HSRP

L2/L3 switch - 2GW-2

1 or 2

SWU-25 6 7 8 9


SWU-3

ESB20-A in MCMU-1

10 11 12 13 14 15 16 17 18

10 11 12 13 14 15 16 17 18

IP PCU 6/5 GW

IP PCU GW 4/3

PCU IP 6/5 GW

PCU IP 4/3 GW

IP PCU 6/5 GW

IP PCU GW 4/3

PCU IP 6/5 GW

IP PCU 4/3 GW

PCU IP 6/5 GW

PCU IP 4/3 GW

IP PCU GW 6/5

IP PCU GW 4/3

IP PCU GW 6/5

IP PCU GW 4/3

BCSU-0

BCSU-1

BCSU-2

BCSU-3

BCSU-4

BCSU-5

BCSU-6



Gb subnet allocationBSC type PCU units 8 16 24 Site routers TOTAL Subnet mask examples and Virtual gateway 3 11 /28 == 14 addresses 3 3 3 3 19 27 53 103 /27 == 30 addresses /27 == 30 addresses /26 == 62 addresses /25 == 126 addresses Ending address 10.255.255.255 172.16.255.255 192.168.255.255

BSC BSC2i BSC3i 660

BSC3i 1000 50 BSC3i 2000 100 Private IP Address Block 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16Customer Confidential 24 Nokia Siemens Networks

Starting address 10.0.0.0 172.16.0.0 192.168.0.0IP training 2007/Timo Eloranta

Subnet allocation example for Gb VLAN Gb VLAN example in BSC3i 1000Gb VLAN SUBNET HSRP Site Switch-1 Site Switch-2 PCU-0 PCU-1 PCU-nn IP addresses 10.8.228.128-192/26 10.8.228.130 10.8.228.131 10.8.228.132 10.8.228.133 10.8.228.134 10.8.228.1xx






Rapid STP (RSTP) One spanning tree forswitches Fast re-calculation of loops Why RSTP concept?MSTPROOT

IP backbone

Easy to configureWhy not Site Switch redundance is not able touse efficientlySWU-0 SWU-1RSTP RSTP RSTP RSTP

SWU-2

SWU-3

MCMU LDI

PCU Gb



Multiple STP (MSTP) Enables VLANs to begrouped into a spanning-tree instance; supports multiple instances Why MSTP concept?MSTPROOT (instance 0)LDI

IP backbone

MSTPROOT (instance 1) O&M, Lb-1, A/BBI-1I

MSTPROOT (inctance 2) Gb, Lb-2, A/BBI-2

Multiple uplink paths. Site Switchredundance can be used.MSTP MSTP MSTP MSTP MSTP MSTP

Why not Sensitive configuration. Spanning treeconfiguration shall be identical in the switches.

SWU-0

SWU-1

SWU-2

SWU-3

LDI

CPUO&M Lb-1 A/BBI-1 Lb-2 A/BBI-2

PCU Gb



MSTP for Gb instance IP paths in Gb over IPVLANs Gb VLAN Site switch - 1MSTP instance Gb

MSTP port rolesPort open to root Port open

ROOT

forwarding IP backbone DESIGNATED

forwardingDESIGNATED forwarding

L2/L3

MSTP

switch - 1 ROOT

Port blocked

Gb in TRUNK

and ALTERNATE discarding

1 or 2 MSTP 19 19 20 5 6 7 8 9

1 or 2 MSTP

SWU-220

SWU-310 11 12 13 14 15 16 17 18

5

6

7

8

9

10 11 12 13 14 15 16 17 18

PCU 6/5

PCU 4/3

PCU6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

BCSU-0

BCSU-1

BCSU-2

BCSU-3

BCSU-4

BCSU-5

BCSU-6



MSTP for Gb instance (1/2) Site Switch-2 failureVLANs Gb VLANMSTP Site instance Gb ROOT

MSTP port rolesPort open to root Port

ROOT

forwarding

IP backbone DESIGNATEDforwarding DESIGNATED forwarding

open

switch - 1

instance Gb

L2/L3

MSTP

switch - 1 ROOT

Port blocked

Gb in TRUNK


1 or 2 MSTP 19 19 20 5 6 7 8 9

1 or 2 MSTP

SWU-220

SWU-310 11 12 13 14 15 16 17 18

5

6

7

8

9

10 11 12 13 14 15 16 17 18

PCU 6/5

PCU 4/3

PCU6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

BCSU-0

BCSU-1

BCSU-2

BCSU-3

BCSU-4

BCSU-5

BCSU-6



MSTP for Gb instance (2/2) Site Switch-1 failureVLANs Gb VLAN Site switch - 1MSTP instance Gb

MSTP port rolesPort open to root Port open

ROOT forwarding

IP backbone DESIGNATEDforwardingDESIGNATED forwarding

L2/L3

MSTP

switch - 1 ROOT

Port blocked

Gb in TRUNK


1 or 2 MSTP 19 19 20 5 6 7 8 9

1 or 2 MSTP

SWU-220

SWU-310 11 12 13 14 15 16 17 18

5

6

7

8

9

10 11 12 13 14 15 16 17 18

PCU 6/5

PCU 4/3

PCU6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

PCU 6/5

PCU 4/3

BCSU-0

BCSU-1

BCSU-2

BCSU-3

BCSU-4

BCSU-5

BCSU-6



ContentBSC IP introduction Redundancy models VLAN MSTP Site Solution L2 and L3 technologies Gb over IP troubleshooting



Multilayer SwitchingMultilayer switching is simply the combination of traditional Layer 2 switching with Layer 3 routing in a single product. Multilayer switch allows to isolate L2 issues (MSTP) from the rest of the network.L2 L3 SWU L2/L3 Router

MSTP

OSPF



IP Site Connectivity: L2 and L3CPU PCU ESB Multilayer Site SwitchL3 (routing) IP host L2 (switching) L2 (switching)IP backboneL3 (e.g. OSPF)

IP backbone L2 (VLAN + e.g. MSTP)

SWU-2#show mac-address-table ===============+======================+===============+===========+==========+ # | 9 | 10 | VID 0101 0101 | | | Mac 00:40:43:e3:d0:8e 00:40:43:e3:d0:90 | | | PORT 1/1/10 1/1/10 | | | STATUS dynamic dynamic | PRIORITY | | 0 | 0 | |

----+----------+----------------------+---------------+-----------+----------+

S6_app_plat_C0#SHow MAC-address-table Mac Address Table ------------------------------------------Vlan ---101 101 Mac Address ----------0040.43e3.d08e 0040.43e3.d090 Type -------DYNAMIC DYNAMIC Ports ----Gi1/0/4 Gi1/0/4

S6_app_plat_C0#SHow IP ROUte OSPF 10.0.0.0/8 is variably subnetted, 101 subnets, 6 masks O O 10.16.154.128/26 [110/3] via 10.16.176.250, 2w0d, GigabitEthernet1/0/52 10.16.155.128/26 [110/3] via 10.16.176.250, 2w0d, GigabitEthernet1/0/52



Switching principleIP Packet L2/L3 switch - 1 L2/L3 MAC TABLE (in Site-1) switch - 2Gb PORTGb PORT 1 5 MAC SITE-1 FF PCU 1 or 2 19 19 20 5 6 7 8 9 4

MAC TABLE (in SWU-2)

MAC-

41 or 2

PCU-

1819/20

PCUFF

SWU-27 8 9


SWU-3

ESB20-A in MCMU-1

5

6

10 11 12 13 14 15 16 17 18

10 11 12 13 14 15 16 17 18

IP PCU 6/5 GW

IP PCU GW 4/3

PCU IP 6/5 GW

PCU IP 4/3 GW

IP PCU 6/5 GW

IP PCU GW 4/3

PCU IP 6/5 GW

IP PCU 4/3 GW

PCU IP 6/5 GW

PCU IP 4/3 GW

IP PCU GW 6/5

IP PCU GW 4/3

IP PCU GW 6/5

IP PCU GW 4/3

BCSU-0

BCSU-1

BCSU-2

BCSU-3

BCSU-4

BCSU-5

BCSU-6



L2 IP BackboneNOT RECOMMENDED IP storms are known threat in switching backbones. NetAct2IP subnet for PCUs and HSRP Gb-3VLAN

BSC

MSTP

VLANUnique in MSTP region

IP subnetUnique in backbone

1

1 MSTP ROOT

1 region

10.16.130/26 10.16.131/26 10.16.132/26 10.20.100/26

3MSTP

4

BSC-1 IP (L2) BackboneGb-1VLAN

MSTP ROOT

GGSN

BSC-2Gb-2VLAN

MSTP Gb-4 IP subnetVLAN

GGSN Other IP NE

for PCUs and

BSC-4IP subnet for PCUs and HSRP

BSC-3

HSRP

MSC

SGSN



Routing principle IP address routing Each router knows neighboursubnets and accessing gatewayNetAct

IP ROUTING TABLE (BSC-1)IP ROUTE Core subnets via core gateway 1 IP ROUTE O&M subnet via O&M gatewayPort

IP ROUTING TABLE (CORE)IP ROUTE Core subnets via bsc-1 site gateway IP ROUTE O&M subnet via O&M gateway2Port

IPPacket BSC-1 IP (L3) BackboneGGSN

BSC-2

GGSN Other IP NE

BSC-4 BSC-3 MSC SGSN



L3 IP BackboneBSC RECOMMENDED BACKBONE NetAct2IP subnet for PCUs and HSRP GbVLAN

MSTP

VLANUnique in MSTP region

IP subnetUnique in backbone

1

1 2&3

1 region 2&3 region 2&3 region

10.16.130/26 10.16.131/26 10.16.132/26 10.20.100/26

3MSTP 1

4

Core

Core region

BSC-1 IP (L3) BackboneGb-1VLAN

MSTP Core

GGSN

MSTP

BSC-2Gb-2VLAN

2&3 Gb IP subnetVLAN

GGSN Other IP NE

for PCUs and

BSC-4IP subnet for PCUs and HSRP

BSC-3

HSRP

MSC

SGSN



ContentBSC IP introduction Redundancy models VLAN Spanning tree L2 and L3 technologies Gb over IP troubleshooting Example of customer problems Interface down Capacity throughput problem What next?



Customer case Communication network problemsOur testing has shown that pure Rapid Spanning Tree does not work or does have interoperability issues between Nokia ESB 20 A and CISCO 7609. Unfortunately there is no configurations guideline, where the dependencies have been described. Customer expect to get a clear interoperability Guideline regarding CISCO 7609 and Nokia Switches ESB 20 A. Furthermore Nokia has to show the convergence time for the Swap of the virtual connection from System testing Point of view! Problem categories: Gb over IP is not working Gb over IP is working, but recovery time is too long Gb over IP is working, but management access is missingCustomer Confidential 40 Nokia Siemens Networks IP training 2007/Timo Eloranta

Communication network ESB-3 management access is missingBSC3ino-STP

CPULANSWU-0

PVST ROOT

O&M OMU O&M backboneno-STP

LDI MCMU

SWU-1

RSTP ROOTPCU PCU PCU

PCULAN

LDI/SWU-3 problem PVST

RSTP SWU-2 LOOP

PVSTSWU-3

IP backbone

RSTPL2 Switch ESB20-A / ESB26Customer Confidential 41 Nokia Siemens Networks IP training 2007/Timo Eloranta

Communication Network Service breaks is Gb over IPBSC3ino-STP

CPULANSWU-0

PVST LOOP

PVST ROOT

O&M OMU O&M backboneno-STP

LDI MCMU

SWU-1


PCULANPVSTSWU-2

Gb problem PVSTSWU-3

IP backbone


Gb over IP Recovery time too longBSC3ino-STP

PVST ROOT

CPULANSWU-0

O&M OMUno-STP

O&M backbone

MSTP Cisco

LDI MCMU

SWU-1


PCULANSWU-2

MSTPCisco

IP backbone

SWU-3 Recovery time after interface shutdown is over 30 sec


Customer comment: It can be stated, that the Time converges to 33 sec which is not RSTP, where couple of 100 msec are expected!

Spanning tree problem Too long recoverySpanning tree settings in Site Switchspanning-tree mode mst spanning-tree portfast bpduguard default spanning-tree backbonefast spanning-tree vlan 1-900 priority 32728 ! spanning-tree mst configuration instance 1 vlan 89 ! spanning-tree mst 1 priority 24576! protocol rapid-spanning-tree enable rapid-spanning-tree priority 45056

Spanning tree settings in ESB! Protocol configuration:

!! VLAN configuration: ! vlan create userplane 89

RSTP

is compliant only with instance 0

config userplane

Recovery based on STP

add ports 1/1/1,1/1/19,1/1/20 taggedadd ports 1/1/7,1/1/9,1/1/11 untagged



NSN recommendation, how to proceedBSC3i CPULANMSTPSWU-0

PVST ROOT

O&M OMU O&M backbone MSTP LDI MCMUSWU-1

L3MSTP

PCULANMSTPPCU PCU PCU SWU-2

MSTPSWU-3

IP backbone

Gb root

MSTPL2 Switch ESB20-A / ESB26Customer Confidential 45 Nokia Siemens Networks IP training 2007/Timo Eloranta

ContentBSC IP introduction Redundancy models VLAN MSTP Site Solution L2 and L3 technologies Gb over IP troubleshooting Example of customer problems Interface down Capacity throughput problem What next?



Gb over IP troubleshooting Instruction steps for Interface down problemProblem description Step (1) Local host connectivity Step (2) Remote host and gateway connectivity Step (3) ESB port states

Step (4) MSTP port rolesStep (5) MSTP failure Step (6) VLAN Step (7) Testing



Gb over IP interface is down SymptomsA problem with IP transport may often manifest itself as an application level transmission failure. BSC application alarms may be raised. The supervision recognizes that there is problem in IP transport when the periodically requested remote host (IP address) becomes unreachable. When the response is missing, and the application fails because of a link failure, there is reason to suspect a problem in IP transport. BSC application alarm for Gb is the following: 3025 NETWORK SERVICE VIRTUAL CONNECTION TEST PROCEDURE FAILED in the Gb interface.



Gb over IP interface is down Active alarmsBSC9 BCSU-0 SWITCH 2007-09-04 ** ALARM BCSU-0 1A003-00 PCU2_D-7 (0399) 3019 NETWORK SERVICE ENTITY UNAVAILABLE 0E 0B8E FFNSEI 02958

13:10:57.89

BSC9 BCSU-0 SWITCH 2007-09-04 13:10:57.89 * ALARM BCSU-0 1A003-00 PCU2_D-7 (0398) 3020 NETWORK SERVICE VIRTUAL CONNECTION UNAVAILABLE 0E 0B8E FF 0B8E FFFF 04 0A 10 90 49 00 00 00 00 00 00 00 00 00 00 00 00 E875NSEI

BSC9 BCSU-0 SWITCH 2007-09-04 13:10:57.89 * ALARM BCSU-0 1A003-00 PCU2_D-7 (0397) 3025 NETWORK SERVICE VIRTUAL CONNECTION TEST PROCEDURE FAILED 0E 0B8E FF 0B8E FFFF 0A 10 90 49 00 00 00 00 00 00 00 00 00 00 00 00 E875NSEI 02958 IP address 10.16.144.73

02958

STATIC CONFIGURED NS-VL(S):OP ID NAME REMOTE REMOTE UDP PORT 59509 STATE RDW RSW IP ADDRESS BL-SY 200 200 10.16.144.73

----- ---------- ----- --- --- --------------- -------02958 PET5_NS24



Gb over IP interface is down Possible causesThere are several possible causes: The IP backbone router and/or the remote host cannot be reached. Multilayer site switches, switching unit(s), or the local host cannot be reached because of problems in the Spanning Tree Protocol (STP) or Virtual Local Area Network (VLAN) configurations.

?

PAPU

IP backbone

Site Switch-1

Site

?

??

Switch-2

? SWU-2

SWU-3

?PCUCustomer Confidential 50 Nokia Siemens Networks


Gb over IP troubleshooting Instruction steps for Interface down problemProblem description

Step (1) Local host connectivityStep (2) Remote host and gateway connectivity Step (3) ESB port states Step (4) MSTP port roles Step (5) MSTP failure

Step (6) VLANStep (7) Testing



Instructions, step 1-1 Local host connectivity Check the PCU host connectivity Problem may be in IP addressconfiguration and the address stateIP backbone PAPU

Site Switch-1

Site Switch-2

SWU-2

SWU-3

?PCUCustomer Confidential 52 Nokia Siemens Networks


Instructions, step 1-2 IP address stateCheck if the IP address of the host port is assigned (YES) and its administrative state UP.QRI:BCSU,0:; BSC3i BSC9 2007-09-02 16:18:55

INTERROGATING NETWORK INTERFACE DATA ADDR ADM UNIT NAME IP ADDRESS TYPE NML ASSIGNED STATE ------------------ -------- --------------- ---- --- -------- ----BCSU-0 EL0 10.16.140.84 L 28 YES UP EL1 10.16.140.100 L 28 YES UP -PCU2D- 3 IFETH0 10.16.140.132 L 25 YES UP -PCU2D- 3 IFETH1 10.16.140.132 L 25 NO UP -PCU2D- 4 IFETH0 10.16.140.133 L 25 YES UP -PCU2D- 4 IFETH1 10.16.140.133 L 25 NO UP -PCU2D- 5 IFETH0 10.16.140.134 L 25 YES UP -PCU2D- 5 IFETH1 10.16.140.134 L 25 Active NO UP -PCU2D- 6 IFETH0 10.16.140.135 L 25 interface YES UP PRIORISED ----- ----1500 NO 1500 NO 1500 NO 1500 NO 1500 NO 1500 NO 1500 NO 1500 NO 1500 NO MTU



Instructions, step 1-3 ResultsPAPU

Checked PCU configuration IP address == 10.16.140.132 address type == logical assigned port == IFETH0 admin status == YES Conclusion Checked and OK Checked and NOK If the administrative state is not UP,change the state of the network interface with the ZQRN-command

IP backbone

Site Switch-1

Site Switch-2

SWU-2

SWU-3

PCU








Instructions, step 2-1 Gateway and remote host connectivity Check gateway and remote host connectivity Problem may be in IP backbone and/or SGSN (PAPU) addition to BSC local IP problems Basic connection tests are between affected PCU and SGSN/Site Switch Advanced test can be done for rest of combinations within the connection path Site switch 1 to SGSN Site Switch 1 to next hop (next gateway) Site Switch 2 to SGSN Site Switch 2 to next hop (next gateway)

?

PAPU

IP backboneSite Switch-1

Site Switch-2

?

SWU-2

SWU-3

PCU



Instructions, step 2-2 Gateway address Check configuration of the gateway address (in affected PCU) E.g. PCU-4 in BCSU-0QKB:BCSU,0; LOADING PROGRAM VERSION 4.18-0 BSC3i BSC1 2007-09-03 11:28:25

INTERROGATED STATIC ROUTES ROUTE UNIT DESTINATION GATEWAY ADDRESS TYPE ------------------- ------------------ ------------------ ----BCSU-0 -PCU2D-3 DEFAULT ROUTE 10.16.137.129 LOG BCSU-0 -PCU2D-4 DEFAULT ROUTE 10.16.137.129 LOG BCSU-0 -PCU2D-5 DEFAULT ROUTE 10.16.137.129 LOG BCSU-0 -PCU2D-6 DEFAULT ROUTE 10.16.137.129 LOG COMMAND EXECUTED NBR ---------2 3 4 5



Instructions, step 2-3 Remote host connectivity Send a PING from active interface (PCU) to the alarmed IP address of theremote host.QRX:BCSU,0:PCU2D,4:IP=10.16.51.5:PING:; BSC3i BSC9 2007-09-02 16:39:38

PING, SENDING UNIT: BCSU-0 Pinging 10.16.51.5 (10.16.51.5) with 64 bytes of data: Request timed out: Resource temporarily unavailable (35). COMMAND EXECUTED

If you receive a positive response, it means that IP transport is working end-to-end and thus there is not IP transport problem. Otherwise continue with the instructions.Customer Confidential 58 Nokia Siemens Networks IP training 2007/Timo Eloranta

Instructions, step 2-4 Check the gateway connectivity Send a PING from affected PCU to the gateway address.QRX:BCSU,0:PCU2D,4:IP=10.16.137.129:PING:; BSC3i BSC9 2007-09-02 16:41:30

PING, SENDING UNIT: BCSU-0 Pinging 10.16.137.129 (10.16.137.129) with 64 bytes of data: Request timed out: Resource temporarily unavailable (35). COMMAND EXECUTED

If you receive a positive response, it means that IP transport is working between PCU and Site Switch and thus there is not problem in the BSC IP site. Otherwise continue with the instructions.Customer Confidential 59 Nokia Siemens Networks IP training 2007/Timo Eloranta

Instructions, step 2-5 Results Results of connectivity tests Gateway == timeout address== 10.16.137.129PAPU

SGSN address

== timeout== 10.16.51.5Site Switch-1

IP backbone

Conclusion Checked and only gateway is OK Check backbone routing configuration (tonext hop) and/or request backbone support

Site Switch-2

Checked and not OK IP transport is down in local siteSWU-2 SWU-3

PCU








Instructions, step 3-1 ESB port states Check port states in ESB-2 and ESB-3 Problem may be in ESB port admin stateand/or duplex settingIP backbone PAPU

Site Switch-1

Site Switch-2

SWU-2

?

SWU-3

PCU



Instructions, step 3-2 Port states in each ESB (PCULAN) Check the ESB port states and duplex mode settings.SWU-2#SH interface ============================================================================== |Port |Name |Type |State |Link|DuplSpeed|Flow |Backpres|Default Vlan +-----+--------+--------+-------+----+---------+-------+--------+------------1/1/1 100TX enable up full-100 disable disable 0001 1/1/2 100TX enable down unknown disable disable 0001 1/1/3 swu0-sw~ 100TX enable up full-100 disable disable 0111 1/1/4 100TX enable down unknown disable disable 0001 1/1/5 gb 100TX enable up half-100 disable disable 0101 1/1/6 gb 100TX enable up half-100 disable disable 0101 1/1/7 gb 100TX enable up half-100 disable disable 0101 1/1/8 gb 100TX enable up half-100 disable disable 0101 1/1/9 gb 100TX enable up half-100 disable disable 0101 1/1/10 gb 100TX enable up half-100 disable disable 0101 1/1/11 gb 100TX enable up half-100 disable disable 0101 1/1/12 gb 100TX enable up half-100 disable disable 0101 1/1/13 gb 100TX enable up half-100 disable disable 0101 1/1/14 gb 100TX enable up half-100 disable disable 0101 1/1/15 gb 100TX enable up half-100 disable disable 0101 1/1/16 gb 100TX enable up half-100 disable disable 0101 1/1/17 gb 100TX enable up half-100 disable disable 0101 1/1/18 gb 100TX enable up half-100 disable disable 0101 1/1/19 swu2-sw~ 100TX enable up full-100 disable disable 0001 1/1/20 swu2-sw~ 100TX enable up full-100 disable disable 0001Customer Confidential 63 Nokia Siemens Networks


Instructions, step 3-3 Results Port settings shall be following in ESB-2and ESB-3 Duplex mode and speed downlink == half (100) uplink == full (100 or 1000) redundance == full (100 or 1000)IP backboneSite Switch-1 uplink

PAPU

State Link

Site Switch-2

== enable == up

redundance

Conclusion Checked and OK Checked and not OK Reconfigure interface

link

SWU-2

SWU-3

downlink

PCU








Instructions, step 4-1 MSTP instance for Gb VLAN/port roles Check MSTP port roles in ESB-2 and ESB-3. Problem may be blocked portPAPU


Site Switch-2

?SWU-2

?

SWU-3

PCU



Instructions, step 4-2 ESB ports in Gb VLAN Check that the PCU host ports connected to the MSTP edge ports areadded to the Gb VLANs as untagged ports, and that the uplink and redundant ports are added to the correct VLANs as tagged ports.SWU-2#SHOW VLAN ==================================================================== Name |VTag| Tagged ports | Untagged ports --------------------+----+---------------------+-------------------default |1 | | gb |101 |1/1/1,1/1/2,1/1/19, |1/1/5-1/1/18 | |1/1/20 | SWU-3#SH VLAN ==================================================================== Name |VTag| Tagged ports | Untagged ports --------------------+----+---------------------+-------------------default |1 | | gb |101 |1/1/1,1/1/2,1/1/19, |1/1/5-1/1/18 |1/1/20

Port configuration shall be equal with cabling



Instructions, step 4-3 MSTP port roles in ESB-2 and ESB-3 Identify Gb VLAN instance and analyze the port roles. e.g. Gb VLAN 101.SWU-2#show MSTP MST02 VLAN mapped = 101,121,131,600,621,631,800,821,831,1200,1221,1231,1300,1321,1331 Priority = 32768 Regional Root = 24578.00:1A:2F:8C:95:80 RemainingHopCount = 3 TopChanges = 1 ============================================================================ Port |Pri|Port role |State|PCost |DCost |Designated bridge |DPrt --------+---+----------+-----+---------+---------+------------------+------01/01/01 128 Root frwrd 200000 210000 28672.001A2F701580 128.004 01/01/05 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.005 01/01/06 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.006 01/01/07 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.007 01/01/08 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.008 01/01/09 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.009 01/01/10 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.010 01/01/11 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.011 01/01/12 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.012 01/01/13 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.013 01/01/14 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.014 01/01/15 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.015 01/01/16 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.016 01/01/17 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.017 01/01/18 128 Designated frwrd 200000 210000 32768.00A0120B2A1A 128.018 AG03 128 Alternate block 100000 0 32768.00A0120B1818 128.023Customer Confidential 68 Nokia Siemens Networks

ROOT in Site Router

Edge ports to PCUs

Redundance LOOP blocked


Instructions, step 4-4 Results Port roles shall be following in ESB2 and ESB-3 downlink == designated forwarding uplink == root forwarding redundance == alternative blockedIP backboneSite Switch-1 uplinkMSTP instance Gb ROOT Primary

PAPU

Conclusion Checked and OK if the port roles are according above Checked and may be OK if redundance link is ROOT. The reasonshall be checked (is link open to Site Switch via other ESB or not?).

redundance link

Checked and NOT OK if ESB sees itself a ROOT if Site Switch is not the ROOTdownlink

SWU-2

SWU-3

PCUMSTP opens port for IP pathCustomer Confidential 69 Nokia Siemens Networks IP training 2007/Timo Eloranta






Instructions, step 5-1 MSTP instance for Gb fails If the port roles and states are not correct,it means that there is a problem with the spanning tree configuration (see step 4). Possible causes uncompliant spanning trees used in SiteSwitch(s) and ESB(s) e.g. PVST(+) MSTP configuration is not identical (name, revision, instance, vlan, mapping). Thus, ESB isolates itself and becomes a root.Site Switch-1

PAPU

IP backbone

Site Switch-2

Check that MSTP is used in Site SwitchesMSTP usage in Site Switches isessential for L2 interoperabilitySWU-2 SWU-3

PCU



Instructions, step 5-2 MSTP instances Give the show mstp configuration command.S6_app_plat_C0#SHow SPanning-tree MSt CONfiguration Name [BSC_Plat] Revision 1 Instances configured 3 Instance -------0 Vlans mapped --------------------------------------------------------------------Site 1-100,102-109,111-119,122-129,132-599,601-609,611-619,622-629 632-799,801-809,811-819,822-829,832-1199,1201-1209,1211-1219 Switch-1 1222-1229,1232-1299,1301-1309,1311-1319,1322-1329,1332-4094 1 110,120,130,610,620,630,810,820,830,1210,1220,1230,1310,1320 1330 2 101,121,131,600,621,631,800,821,831,1200,1221,1231,1300,1321 1331 ------------------------------------------------------------------------------SWU-2#show mstp configuration Name [BSC_Plat] Revision 1 Instance Vlans mapped --------- --------------------------------------------------------------------0 1-100,102-109,111-119,122-129,132-599,601-609,611-619,622-629,632-799, 801-809,811-819,822-829,832-1199,1201-1209,1211-1219,1222-1229,1232-1299, SWU-2 1301-1309,1311-1319,1322-1329,1332-4094 1 110,120,130,610,620,630,810,820,830,1210,1220,1230,1310,1320,1330 2 101,121,131,600,621,631,800,821,831,1200,1221,1231,1300,1321,1331 -------------------------------------------------------------------------------

Site Switch-2

SWU-3



Instructions, step 5-3 MSTP/Gb instance ROOT In the L2 site, MSTP instance ROOT is the Switchwhich priority is highest (== smallest value) Instance ROOT Site Switch 2 == ROOT primary (24576) Instance backup Site Switch 1 == ROOT secondary (28676) Instance never ROOT ESB(s) == esb default (32768)

MSTP instance Gb Secondary

MSTP instance Gb ROOT Primary

SWU-2MSTP instance Gb

SWU-3MSTP instance Gb ESB default

ESBdefault



Instructions, step 5-4 Results Conclusion Gb instance shall work when MSTP settings are equal in the eachregion Switch and Site swith-2 has the ROOT priority.








Instructions, step 6-1 VLAN configuration Check VLAN configuration in ESB-2 andESB-3, and Site Switches. Problem may be wrong VLAN id, unconfigured port or wrong tagging modeSite Switch-1

PAPU

IP backbone

Site Switch-2

??SWU-2

?? ?PCU SWU-3



Instructions, step 6-2 Tagged and untagged ports in Gb VLAN Check that the port you are investigating belongs to the Gb VLAN.SWU-2#SHOW VLAN ==================================================================== Name |VTag| Tagged ports | Untagged ports --------------------+----+---------------------+-------------------default |1 | | gb |101 |1/1/1,1/1/2,1/1/19, |1/1/5-1/1/18 | |1/1/20 | SWU-3#show VLAN ==================================================================== Name |VTag| Tagged ports | Untagged ports --------------------+----+---------------------+-------------------default |1 | | gb |101 |1/1/1,1/1/2,1/1/19, |1/1/5-1/1/18 |1/1/20

Downlink ports (mstp-edge)

Uplink and redundance portsCustomer Confidential 77 Nokia Siemens Networks


Instructions, step 6-3 Default VLAN Check default VLAN setting for PCU portsSWU-2#SHOW interface ============================================================================== |Port |Name |Type |State |Link|DuplSpeed|Flow |Backpres|Default Vlan +-----+--------+--------+-------+----+---------+-------+--------+------------1/1/1 100TX enable up full-100 disable disable 0001 1/1/2 100TX enable down unknown disable disable 0001 1/1/3 swu0-sw~ 100TX enable up full-100 disable disable 0111 1/1/4 100TX enable down unknown disable disable 0001 1/1/5 gb 100TX enable up half-100 disable disable 0101 1/1/6 gb 100TX enable up half-100 disable disable 0101 1/1/7 gb 100TX enable up half-100 disable disable 0101 1/1/8 gb 100TX enable up half-100 disable disable 0101 1/1/9 gb 100TX enable up half-100 disable disable 0101 1/1/10 gb 100TX enable up half-100 disable disable 0101 1/1/11 gb 100TX enable up half-100 disable disable 0101 1/1/12 gb 100TX enable up half-100 disable disable 0101 1/1/13 gb 100TX enable up half-100 disable disable 0101 1/1/14 gb 100TX enable up half-100 disable disable 0101 1/1/15 gb 100TX enable up half-100 disable disable 0101 1/1/16 gb 100TX enable up half-100 disable disable 0101 1/1/17 gb 100TX enable up half-100 disable disable 0101 1/1/18 gb 100TX enable up half-100 disable disable 0101 1/1/19 swu2-sw~ 100TX enable up full-100 disable disable 0001 1/1/20 swu2-sw~ 100TX enable up full-100 disable disable 0001



Instructions, step 6-4 Results Gb VLAN configuration shall be followingin ESB-2 and ESB-3. - DOWNLINK- default VLAN - tagged ports - untagged ports -UPLINK - default VLAN - tagged ports - untagged ports -REDUNDANCE LINK - default VLAN - tagged ports - untagged ports== Gb VLAN (e.g. 101) == not used == all PCU ports == not used == GB VLAN == not used == not used == GB VLAN == not usedIP backbone PAPU

Site Switch-1

Site Switch-2

GB VLAN Tagged

GB VLAN Tagged

SWU-2GB VLAN GB VLAN default Untagged

GB VLAN Tagged

SWU-3GB VLAN GB VLAN default

Untagged

PCU



Instructions, step 6-5 Gb VLAN in Site Switches Check VLAN configuration in the Site SwitchesCISCO#SHOW RUNNING-CONFIG interface GigabitEthernet1/0/4 description swu3_BSC1 switchport trunk encapsulation dot1q switchport trunk allowed vlan 101,111 switchport mode trunk switchport nonegotiate duplex full speed 100 spanning-tree link-type point-to-point interface Vlan101 description gb ip address 10.16.137.131 255.255.255.192 no ip proxy-arp standby 1 ip 10.16.137.129 standby 1 timers msec 500 2 standby 1 priority 200 standby 1 preempt delay minimum 60



Instructions, step 6-6 Results Gb VLAN configuration shall be followingin Site Switches. Interface port- allowed trunk== Gb VLAN == Gateway addressSite Switch-1

PAPU

IP backbone

Interface VLAN(Gb) standbySite Switch-2

GB VLAN Tagged

GB VLAN Tagged

SWU-2

SWU-3

PCU








Instructions, step 7-1 Gateway address is ready for testing Send ping to gateway IP address the address is active in the same siteswitch where is MSTP root.IP backboneS6_app_plat_C1#SHow STANdby VLAN 101 Vlan101 - Group 1 Site State is Active Switch-1 2 state changes, last state change 5w6d Virtual IP address is 10.16.137.129 Active virtual MAC address is 0000.0c07.ac01 Local virtual MAC address is 0000.0c07.ac01 (v1 default) Hello time 500 msec, hold time 2 sec Next hello sent in 0.374 secs Preemption enabled, delay min 60 secs SWU-2 Active router is local Standby router is 10.16.137.130, priority 100 (expires in 1.605 sec) Priority 200 (configured 200) IP redundancy name is "hsrp-Vl101-1" (default)IP packet

PAPU

MSTP instance Gb HSRP active ROOT

Primary

SWU-3

PCUPING



Instructions, step 7-2 Remote address is ready for testing Send ping to remote IP addressPAPU

Note: IP route configuration in site switch (static,ospf , rip etc) -> next hop ip address is neededIP backboneMSTP S6_app_plat_C1#SHOW IP ROute OSpf 10.0.0.0/8 is variably subnetted, 101 subnets, 6 masks O 10.16.154.128/26 [110/3] via 10.16.176.250, 2w4d, GigabitEthernet1/0/52

Site Switch-1

instance Gb

HSRPIP route

ROOT

Primary

OO O O O

10.16.155.128/26[110/3] via 10.16.176.250, 2w4d, GigabitEthernet1/0/52 10.16.152.128/26 [110/3] via 10.16.176.250, 2w4d, GigabitEthernet1/0/52 10.16.153.128/26 [110/3] via 10.16.176.250, 2w4d, GigabitEthernet1/0/52 10.16.148.128/28 [110/3] via 10.16.176.253, 2w4d, GigabitEthernet1/0/52 10.16.142.128/26 [110/3] via 10.16.176.244, 2w4d, GigabitEthernet1/0/52

SWU-2

SWU-3

PCUIP packet PINGCustomer Confidential 84 Nokia Siemens Networks IP training 2007/Timo Eloranta

ContentBSC IP introduction Redundancy models VLAN Spanning tree L2 and L3 technologies Gb over IP troubleshooting Interface down Capacity throughput problem What next?



Capacity throughput problem SymptomsA problem with IP transport may be seen as a bad throughput in the end user perspective or dropping of CS call. BSC application alarms may not be raised. Supervision may recognize temporarily problems in IP transport. Remote host (IP address) is reachable and NSEI is WO-EX.



Capacity throughput problem Possible causesPAPU

There are several possible causes: IP path configuration not symmetric in backbone Duplex mode configuration mismatch Spanning tree topology changes in BSC or SGSN site e.g. broken cable

IP backbone

Site Switch-1

Site Switch-2

SWU-2

SWU-3

PCU



Un-symmetric IP routing problem may cause CS call dropping Configuration mistakes may reveal in Site Switch switchover IP routing table (in backbone) includes only one path from backbone to BSC. All subnets (BSC) are available only via one Site Switch. Active HSRP and OSPF subnet may not locate in the same Site Switch Default timers and preempt values in HSRPSite Switch-1

IP packet

IFETH0Site Switch(s)

SGSN 0/1

BSCIP packet

IP backbone

IFETH1HSRP active

Site Switch-2Customer Confidential 88 Nokia Siemens Networks IP training 2007/Timo Eloranta

Some IP packets lost between PCU and ESB Duplex mode configuration mismatch Choros PCU half duplex ESB full-duplexSWU-2

SWU-3

NSEI in WO-EX and CS call is successful No alarms No logs Count of Total RX Errors & FCS error will raise The mismatch causes packet lost when inhigher capacity

PCU



Temporarily backbone access is missing

Spanning tree topology changes in BSCor SGSN site e.g. SW or HW failureSWU-2#SH MSTP Multiple spanning trees ProtocolSpecification Priority TimeSinceTopologyChange TopChanges CIST Root CIST Port CIST External Path Cost MaxAge HelloTime ForwardDelay BridgeMaxAge BridgeHelloTime BridgeForwardDelay ProtoMigratioDelay MaxHopCount TxHoldCount = = = = = = = = = = = = = = = = = enabled ieee8021s 32768 0 (Sec) 3 24576.00:1A:2F:70:15:80 01/01/01 0 20 (Sec) 2 (Sec) 15 (Sec) 8 (Sec) 2 (Sec) 15 (Sec) 3 (Sec) 5 3 Site Switch-1 Site Switch-2

ROOT? SWU-2 SWU-3

PCU



ContentBSC IP introduction Redundancy models VLAN Spanning tree L2 and L3 technologies Gb over IP troubleshooting Example of customer problems Interface down Capacity throughput problem What next?



BSC Problem ReportingWhen you suspect problem with IP transport, do as follows to collect all information required to solve problem.Printout of each site switch data. Open Telnet session or local CLI connection (serial cable) to the site router and give the following commands.

PAPU

show versionshow running-config show interfaces show vlan show spanning-tree mst (or other used spanning-tree) Printout of each SWU data. Open Telnet session (ZW6T:SWU,:) or local CLI connection (serial cable) to the SWU and give the following commands. show version show running-config show interface show vlan show mstp (or other used spanning-tree)

Site Switch-1


SWU-2

SWU-3

PCUPrintout of alarm history ZAHO; Printout of network interface data (IP address) ZQRI; Printout of active internet connections ZQRS:,:,; Printout of route data (gateway IP address) ZQKB; ZQKO;Customer Confidential 92 Nokia Siemens Networks IP training 2007/Timo Eloranta

Printout of host reachability testZQRX:,:,< index>:IP=:; ZQRX:,:,< index>:IP=:; Printout of LAN switch supervision ZYFF; Printout of LAN switch status ZUSI:SWU; ZUSI:CNW;

Ethereal / Port monitoring



References BSC/TCSM, Rel. S12, Product Documentation in NED library BSC Site IP Connectivity Guidelines (DN03502792) Integrated LAN Administration (DN0423824) NOLS ESB20-A 10/100 Mbit Ethernet Switch User Guide (DN03403532) ESB26 GigabitEthernet Switch User Guide (DN04130328) Intranet B12 training material on IP connectivityhttp://www6.connecting.nokia.com/net/dx200web.nsf/document/ES396CJCXL?OpenDocument

TCP/IP Platform Guidehttp://pi.nokia.com/urn.htm?id=09006c37809db34d&docb=espoo11&auth=T&version=current&document_id=13-399937

Internet RFC repository maintained by the IETF Secretariathttp://www.ietf.org/rfc

IEEE Standardshttp://www.ieee.org



Thank You.


IP Training/Timo Eloranta

ip+training+(dallas),+2+day

Documents

resource temporarily

111 100tx

sw 100tx

open telnet

l3 technologies

local cli

carrier sense

tree extend