PNNI 1.0 VP associated signalling

[Anonymous]

Please explain how SVC call established from end-user UNI device with Connection Identifier field set to explicit VPCI/VCI is propogated to PNNI interface that has 2 VPs.

VP0 has been configured with non-associated signalling

VP1 has it own signalling configured with VP associated parameters.

I'd love to know if that VPCI/VCI explicit message in that config must be attached to PNNI call setup message and which VP the original call must be placed to.

I have a problem with constant placement of SVC to VP1, sometimes it goes to VP 0. Does the VP associated signalling concept on PNNI mean the same as on UNI?

Thank you!

[donewald]

Attached is a link about PNNI explicit paths that might help you.

http://www.cisco.com/en/US/partner/products/hw/switches/ps1893/products_command_reference_chapter09186a0080091738.html#19593.

As for connections going over one of your VP's rather than the other, this could be a cost issue in your configuration or, which I have run into, an associated signaling imcompatability with certain IE (Informational Elements) that are passed along your VP in the call setup messages. Without some debugs or more information it's hard to say what the problem. Here's a link for IE information if you're interested.

http://www.cisco.com/en/US/partner/tech/tk39/tk49/technologies_tech_note09186a0080093d3d.shtml

I hope this helps you,

Don

[Anonymous]

Thanks Don,

I have some logs that shown weird behaviour on Setup Message coming out of PNNI interface that sometime contains Connection Identifier with VPCI explicit and sometimes doesnt. Please tell me one thing:

Does the setup message from UNI with IE VPCI exclusive propogates to setup message of NNI side and force Preceeding Switch (originator) to choose VPx other then VP0, VP1 in my case with VP associated? I dont have tunneling as such in my config. I have 2 equal logical paths with their own Signalling channel. But I wish to run all SVCs to VP1 only not 0. On UNI it is alwas VP1 as user device supports VP associated all the time.

My problem is that some techs say that Originating Switch doesnt care much about Connection Identifier field with VP associated request coming from UNI and decides the path based on its routing algorithm. Does the calling UNI party define the VP all the way through network to called party if VP1 path available in this network with VP associated?

I cant much theory on VP associated implementation anyware. It is optional in PNNI1.0 and not many people have practice with that. So if you have some more info for me that would be great!!

Tnanks a lot!

Vitaly

FRAME 9 UNI device demanded VC on on VP1 successfully(user side)

Call Reference Value: 0x000069

Message Type: Setup

Message Length: 126 bytes

Information Element Name: ATM Traffic Descriptor

Element Length: 16 bytes

Forward PCR (CLP=0): 181

Backward PCR (CLP=0): 181

Forward PCR (CLP=0+1): 181

Backward PCR (CLP=0+1): 181

Information Element Name: Broadband Bearer Capability

Element Length: 3 bytes

Bearer Class: BCOB-X

ATM Transfer Capability: Constant Bit Rate

Clipping: Susceptible to clipping

Configuration: Point-to-point

Information Element Name: Called Party Number

Element Length: 21 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Address: 0x39.036f.20004400000003000300.111111111111.11

Information Element Name: Connection Identifier “---this IE is missing in frame 10---”

Element Length: 5 bytes

VP Associated: ?? [---00---]

Preferred/Exclusive: Exclusive VPCI; Any VCI

VPCI: 1

VCI: 0

Information Element Name: ATM Adaptation Layer Parameters

Element Length: 3 bytes

AAL Type: AAL Type 5

SSCS Type: Null

Information Element Name: Broadband High Layer Information

Element Length: 9 bytes

Information Type: User Specific

High Layer Information: 8 bytes

Hex Display [0082]: 00 00 00 00 00 00 00 08

Information Element Name: Broadband Low Layer Information

Element Length: 4 bytes

Layer 2 Protocol: LAN Logical Link Control

Layer 3 Protocol: ISO/IEC TR 9577

Initial Protocol ID: 0xcc [11001100]

Information Element Name: Broadband Sending Complete

Element Length: 1 byte

Indication: Complete

Information Element Name: Calling Party Number

Element Length: 22 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Presentation Indicator: Presentation allowed

Screening Indicator: User-provided, not screened

Address: 0x39.036f.20004400000003000200.111111111111.11

Information Element Name: Quality of Service Parameter

Element Length: 2 bytes

QoS Class Forward: Class 0 - Unspecified

QoS Class Backward: Class 0 – Unspecified

FRAME 10 PNNI requested in Setup on VP1 unsuccessfully(VP0 has been chosen)

Call Reference Value: 0x000015

Message Type: Setup

Message Length: 215 bytes

Information Element Name: ATM Traffic Descriptor

Element Length: 16 bytes

Forward PCR (CLP=0+1): 181

Forward PCR (CLP=0): 181

Backward PCR (CLP=0): 181

Backward PCR (CLP=0+1): 181

Information Element Name: Broadband Bearer Capability

Element Length: 3 bytes

Bearer Class: BCOB-X

ATM Transfer Capability: Constant Bit Rate

Clipping: Susceptible to clipping

Configuration: Point-to-point

Information Element Name: Called Party Number

Element Length: 21 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Address: 0x39.036f.20004400000003000300.111111111111.11

Information Element Name: Quality of Service Parameter

Element Length: 2 bytes

QoS Class Forward: Class 0 - Unspecified

QoS Class Backward: Class 0 - Unspecified

Information Element Name: Broadband Repeat Indicator

Element Length: 1 byte

Repeat Indication: Last in, first out stack

Information Element Name: Designated Transition List

Element Length: 56 bytes

Transit Pointer: 2 (27 byte offset)

Node/Port Entry Number: 1

Indicator Type: Logical node/logical port

Node Identifier: 80:160:39.036f20004400000003000200.ff1a9b680001.00

Port Identifier: 0x10000000

Node/Port Entry Number: 2

Indicator Type: Logical node/logical port

Node Identifier: 80:160:39.036f20004400000003000300.ff1a99a30001.00

Port Identifier: 0xfffffffe

Information Element Name: ATM Adaptation Layer Parameters

Element Length: 3 bytes

AAL Type: AAL Type 5

SSCS Type: Null

Information Element Name: Broadband High Layer Information

Element Length: 9 bytes

Information Type: User Specific

High Layer Information: 8 bytes

Hex Display [0144]: 00 00 00 00 00 00 00 08

Information Element Name: Calling Party Number

Element Length: 22 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Presentation Indicator: Presentation allowed

Screening Indicator: User-provided, not screened

Address: 0x39.036f.20004400000003000200.111111111111.11

Information Element Name: Extended QoS Parameters

Element Length: 21 bytes

Origin: Intermediate network

Acceptable Forward CDV: Any cell delay variation acceptable

Acceptable Backward CDV: Any cell delay variation acceptable

Cumulative Forward CDV: 725 microseconds

Cumulative Backward CDV: 725 microseconds

Acceptable Forward CLR: Any cell loss ratio acceptable

Acceptable Backward CLR: Any cell loss ratio acceptable

Information Element Name: End-to-End Transit Delay

Element Length: 9 bytes

PNNI Accept Fwrd maxCTD: Any delay value acceptable

PNNI Cumltv Fwrd maxCTD: 0 microseconds

Origin Indicator: Network Generated

Information Element Name: Broadband Low Layer Information

Element Length: 4 bytes

Layer 2 Protocol: LAN Logical Link Control

Layer 3 Protocol: ISO/IEC TR 9577

Initial Protocol ID: 0xcc [11001100]

FRAME 53 UNI demanded VC on VP1 successfully

Call Reference Value: 0x00006d

Message Type: Setup

Message Length: 126 bytes

Information Element Name: ATM Traffic Descriptor

Element Length: 16 bytes

Forward PCR (CLP=0): 181

Backward PCR (CLP=0): 181

Forward PCR (CLP=0+1): 181

Backward PCR (CLP=0+1): 181

Information Element Name: Broadband Bearer Capability

Element Length: 3 bytes

Bearer Class: BCOB-X

ATM Transfer Capability: Constant Bit Rate

Clipping: Susceptible to clipping

Configuration: Point-to-point

Information Element Name: Called Party Number

Element Length: 21 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Address: 0x39.036f.20004400000003000300.111111111111.11

Information Element Name: Connection Identifier

Element Length: 5 bytes

VP Associated: ?? [---00---]

Preferred/Exclusive: Exclusive VPCI; Any VCI

VPCI: 1

VCI: 0

Information Element Name: ATM Adaptation Layer Parameters

Element Length: 3 bytes

AAL Type: AAL Type 5

SSCS Type: Null

Information Element Name: Broadband High Layer Information

Element Length: 9 bytes

Information Type: User Specific

High Layer Information: 8 bytes

Hex Display [0082]: 00 00 00 00 00 00 00 08

Information Element Name: Broadband Low Layer Information

Element Length: 4 bytes

Layer 2 Protocol: LAN Logical Link Control

Layer 3 Protocol: ISO/IEC TR 9577

Initial Protocol ID: 0xcc [11001100]

Information Element Name: Broadband Sending Complete

Element Length: 1 byte

Indication: Complete

Information Element Name: Calling Party Number

Element Length: 22 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Presentation Indicator: Presentation allowed

Screening Indicator: User-provided, not screened

Address: 0x39.036f.20004400000003000200.111111111111.11

Information Element Name: Quality of Service Parameter

Element Length: 2 bytes

QoS Class Forward: Class 0 - Unspecified

QoS Class Backward: Class 0 – Unspecified

FRAME 54 PNNI requested VC on VP1 successfully(VP1 has been chosen)

Call Reference Value: 0x00001a

Message Type: Setup

Message Length: 224 bytes

Information Element Name: ATM Traffic Descriptor

Element Length: 16 bytes

Forward PCR (CLP=0+1): 181

Forward PCR (CLP=0): 181

Backward PCR (CLP=0): 181

Backward PCR (CLP=0+1): 181

Information Element Name: Broadband Bearer Capability

Element Length: 3 bytes

Bearer Class: BCOB-X

ATM Transfer Capability: Constant Bit Rate

Clipping: Susceptible to clipping

Configuration: Point-to-point

Information Element Name: Called Party Number

Element Length: 21 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Address: 0x39.036f.20004400000003000300.111111111111.11

Information Element Name: Quality of Service Parameter

Element Length: 2 bytes

QoS Class Forward: Class 0 - Unspecified

QoS Class Backward: Class 0 - Unspecified

Information Element Name: Connection Identifier

Element Length: 5 bytes

VP Associated: VP Associated signalling

Preferred/Exclusive: Exclusive VPCI; Any VCI

VPCI: 1

VCI: 0

Information Element Name: Broadband Repeat Indicator

Element Length: 1 byte

Repeat Indication: Last in, first out stack

Information Element Name: Designated Transition List

Element Length: 56 bytes

Transit Pointer: 2 (27 byte offset)

Node/Port Entry Number: 1

Indicator Type: Logical node/logical port

Node Identifier: 80:160:39.036f20004400000003000200.ff1a9b680001.00

Port Identifier: 0x10010000

Node/Port Entry Number: 2

Indicator Type: Logical node/logical port

Node Identifier: 80:160:39.036f20004400000003000300.ff1a99a30001.00

Port Identifier: 0xfffffffe

Information Element Name: ATM Adaptation Layer Parameters

Element Length: 3 bytes

AAL Type: AAL Type 5

SSCS Type: Null

Information Element Name: Broadband High Layer Information

Element Length: 9 bytes

Information Type: User Specific

High Layer Information: 8 bytes

Hex Display [0153]: 00 00 00 00 00 00 00 08

Information Element Name: Calling Party Number

Element Length: 22 bytes

Type of Number: Unknown

Addressing Plan ID: ATM Endsystem Address

Presentation Indicator: Presentation allowed

Screening Indicator: User-provided, not screened

Address: 0x39.036f.20004400000003000200.111111111111.11

Information Element Name: Extended QoS Parameters

Element Length: 21 bytes

Origin: Intermediate network

Acceptable Forward CDV: Any cell delay variation acceptable

Acceptable Backward CDV: Any cell delay variation acceptable

Cumulative Forward CDV: 725 microseconds

Cumulative Backward CDV: 725 microseconds

Acceptable Forward CLR: Any cell loss ratio acceptable

Acceptable Backward CLR: Any cell loss ratio acceptable

Information Element Name: End-to-End Transit Delay

Element Length: 9 bytes

PNNI Accept Fwrd maxCTD: Any delay value acceptable

PNNI Cumltv Fwrd maxCTD: 0 microseconds

Origin Indicator: Network Generated

Information Element Name: Broadband Low Layer Information

Element Length: 4 bytes

Layer 2 Protocol: LAN Logical Link Control

Layer 3 Protocol: ISO/IEC TR 9577

Initial Protocol ID: 0xcc [11001100]

[donewald]

Vitaly,

I would think the following on your questions.

1. The originating UNI does not decide what VP to take. The NNI devices will, during call setup, chose e "best route" to the destination NSAP. A DTL will be constructed and a call (SVC), enventually setup.

2. The IE problems that I had run into were on the called , not the calling side. Basically the calling party would send and IE that was not supported on the terminating switch (Exiting VP) called side and the call setup would be terminated. There were some pretty drastic Associated signaling changes from 11.3 to 12.0 on the Atm switches in IOS.

Possibly your call setup issue is something to do with this Associated signaling I mention above...

FRAME 10 PNNI requested in Setup on VP1 unsuccessfully(VP0 has been chosen)

Says Unsuccessfully but I am curious as to what the failure cause is? Do you have any debugs of this issue?

Hope this helps,

Don

[Anonymous]

Hello Don,

Thanks for this.

"Unsuccesfully" - it is my meaning of that issue when SVC went to VP0 not to VP1.

Could you please explain finaly where and under what config we can use VP associated signalling. What is the practical use of it? You will probably mention the VP tunneling. Anything else?

Thank you one more time!

Cheers,

Vitaly

[donewald]

Vitaly,

VP tunneling is the only application of associated signaling that we are discussing that I am familiar with. There is CAS (Channel Associated Signaling) which is used mostly with CBR/Voice applications (Curcuit Emulation).

Normally an SVC failure has a failure code for the Call setup failing. This is what I was refering to, as it might be the Associated signaling IE incompatibilty issue I mentioned earlier.

Regards,

Don

[Anonymous]

Don,

I do Appreciate your assistance! Thanks. No, I do not have any incompatibility issues. All SVCs were connected, only routed to the Vp that they are not suppose to go.

Anyway I think have an answer for my further tests.

Have a nice day

Vitaly