| Vadim Yanitskiy | 4d94434 | 2023-12-29 05:28:38 +0700 | [diff] [blame] | 1 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 2 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 3 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 4 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 5 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 6 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 7 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 8 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 9 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 10 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 11 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 12 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 13 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 14 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 15 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 16 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 17 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 18 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 19 | Ignoring NS STATUS from 1.2.3.4:1111 for non-existing NS-VC |
| 20 | Ignoring NS ALIVE ACK from 1.2.3.4:1111 for non-existing NS-VC |
| 21 | Ignoring NS RESET ACK from 1.2.3.4:1111 for non-existing NS-VC |
| 22 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 23 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 24 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 25 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4386, NSVCI=4386, cause=O&M intervention) |
| 26 | NSEI=4386 Tx NS RESET ACK (NSVCI=4386) |
| 27 | NSEI=4386 Rx NS UNBLOCK |
| 28 | NSVCI=4386 Rx NS RESET (NSEI=4386, NSVCI=4386, cause=O&M intervention) |
| 29 | NSEI=4386 Tx NS RESET ACK (NSVCI=4386) |
| 30 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 31 | Creating NS-VC for BSS at 1.2.3.4:3333 |
| 32 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4386, NSVCI=13124, cause=O&M intervention) |
| 33 | NSEI=4386 Tx NS RESET ACK (NSVCI=13124) |
| 34 | NS-VC changed NSEI (NSVCI=4386) from 4386 to 13124 |
| 35 | NSVCI=4386 Rx NS RESET (NSEI=13124, NSVCI=4386, cause=O&M intervention) |
| 36 | NSEI=13124 Tx NS RESET ACK (NSVCI=4386) |
| 37 | NSVCI=13124 Rx NS RESET (NSEI=4386, NSVCI=4386, cause=O&M intervention) |
| 38 | NS-VC changed link (NSVCI=4386) from 1.2.3.4:3333 to 1.2.3.4:4444 |
| 39 | NSEI=4386 Tx NS RESET ACK (NSVCI=4386) |
| 40 | NSVCI=4386 Rx NS RESET (NSEI=4386, NSVCI=4386, cause=O&M intervention) |
| 41 | NSEI=4386 Tx NS RESET ACK (NSVCI=4386) |
| 42 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 43 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 44 | Creating NS-VC for BSS at 1.2.3.4:1111 |
| 45 | NSVCI=65535(invalid) Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 46 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 47 | NSEI=4096 Rx NS UNBLOCK |
| 48 | NSVCI=65535 Creating NS-VC with Signal weight 1, Data weight 1 |
| 49 | Creating NS-VC for BSS at 1.2.3.4:2222 |
| 50 | NSVCI=65535(invalid) Rx NS RESET (NSEI=8192, NSVCI=8193, cause=O&M intervention) |
| 51 | NSEI=8192 Tx NS RESET ACK (NSVCI=8193) |
| 52 | NSEI=8192 Rx NS UNBLOCK |
| 53 | NSEI=4096 RESET procedure based on API request |
| 54 | NSEI=4096 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 55 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 56 | NSEI=8192 RESET procedure based on API request |
| 57 | NSEI=8192 Tx NS RESET (NSVCI=8193, cause=O&M intervention) |
| 58 | NSVCI=8193 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 59 | NS-VC changed link (NSVCI=4097) from 1.2.3.4:2222 to 1.2.3.4:1111 |
| 60 | NSEI=8192 RESET procedure based on API request |
| 61 | NSEI=8192 Tx NS RESET (NSVCI=8193, cause=O&M intervention) |
| 62 | failed to send NS message via UDP: Operation not permitted |
| 63 | NSEI=8192, error resetting NS-VC |
| 64 | NSEI=4096 RESET procedure based on API request |
| 65 | NSEI=4096 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 66 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 67 | NSVCI=8193 Rx NS RESET (NSEI=8192, NSVCI=8193, cause=O&M intervention) |
| 68 | NSEI=8192 Tx NS RESET ACK (NSVCI=8193) |
| 69 | NSEI=8192 Rx NS UNBLOCK |
| 70 | NSVCI=4097 Rx NS RESET (NSEI=61440, NSVCI=4097, cause=O&M intervention) |
| 71 | NSEI=61440 Tx NS RESET ACK (NSVCI=4097) |
| 72 | NSVCI=4097 Rx NS RESET (NSEI=4096, NSVCI=61441, cause=O&M intervention) |
| 73 | Creating NS-VC 61441 replacing 4097 at 1.2.3.4:2222 |
| 74 | NSVCI=61441 Creating NS-VC with Signal weight 1, Data weight 1 |
| 75 | NSEI=4096 Tx NS RESET ACK (NSVCI=61441) |
| 76 | NSVCI=61441 Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 77 | NS-VC changed link (NSVCI=4097) from 1.2.3.4:2222 to 0.0.0.0:0 |
| 78 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 79 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 80 | NS RESET ACK Discarding unexpected message for NS-VCI 4097 from SGSN NSEI=4096 |
| 81 | NSEI=4096 RESET procedure based on API request |
| 82 | NSEI=4096 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 83 | NSVCI=4097 Rx NS RESET ACK (NSEI=61440, NSVCI=4097) |
| 84 | NSEI=61440 RESET procedure based on API request |
| 85 | NSEI=61440 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 86 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=61441) |
| 87 | NS-VC changed link (NSVCI=61441) from 1.2.3.4:2222 to 0.0.0.0:0 |
| 88 | NSVCI=61441 Rx NS RESET (NSEI=4096, NSVCI=4097, cause=O&M intervention) |
| 89 | NS-VC changed link (NSVCI=4097) from 1.2.3.4:2222 to 0.0.0.0:0 |
| 90 | NSEI=4096 Tx NS RESET ACK (NSVCI=4097) |
| 91 | NSEI=4096 Rx NS UNBLOCK |
| 92 | NSEI=4096 RESET procedure based on API request |
| 93 | NSEI=4096 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 94 | NSEI=4096 Rx NS UNBLOCK ACK |
| 95 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 96 | NS RESET ACK Discarding unexpected message for NS-VCI 4097 from SGSN NSEI=4096 |
| 97 | NSEI=4096 Reset timed out but RESET flag is not set |
| 98 | NSEI=4096 Tx NS RESET (NSVCI=4097, cause=O&M intervention) |
| 99 | NSVCI=4097 Rx NS RESET ACK (NSEI=4096, NSVCI=4097) |
| 100 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 101 | NSVCI=257 Creating NS-VC with Signal weight 1, Data weight 1 |
| 102 | NSEI=256 RESET procedure based on API request |
| 103 | NSEI=256 Tx NS RESET (NSVCI=257, cause=O&M intervention) |
| 104 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=257) |
| 105 | NSEI=256 Tx NS UNBLOCK (NSVCI=257) |
| 106 | NSEI=256 Rx NS UNBLOCK ACK |
| 107 | NSVCI=257 Rx NS RESET (NSEI=256, NSVCI=257, cause=O&M intervention) |
| 108 | NSEI=256 Tx NS RESET ACK (NSVCI=257) |
| 109 | NSVCI=257 Rx NS RESET (NSEI=61440, NSVCI=257, cause=O&M intervention) |
| 110 | NSEI=256 Tx NS RESET ACK (NSVCI=257) |
| 111 | NSVCI=257 Rx NS RESET (NSEI=256, NSVCI=61441, cause=O&M intervention) |
| 112 | NSEI=256 Tx NS RESET ACK (NSVCI=257) |
| 113 | NSVCI=257 Rx NS RESET (NSEI=256, NSVCI=257, cause=O&M intervention) |
| 114 | NSEI=256 Tx NS RESET ACK (NSVCI=257) |
| 115 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=257) |
| 116 | NS RESET ACK Discarding unexpected message for NS-VCI 257 from SGSN NSEI=256 |
| 117 | NSEI=256 RESET procedure based on API request |
| 118 | NSEI=256 Tx NS RESET (NSVCI=257, cause=O&M intervention) |
| 119 | NSVCI=257 Rx NS RESET ACK (NSEI=57344, NSVCI=257) |
| 120 | NS RESET ACK Unknown NSEI 57344 (NS-VCI=257) from 5.6.7.8:32000 |
| 121 | NSEI=256 RESET procedure based on API request |
| 122 | NSEI=256 Tx NS RESET (NSVCI=257, cause=O&M intervention) |
| 123 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=57345) |
| 124 | NS RESET ACK Unknown NS-VCI 57345 (SGSN NSEI=256) from 5.6.7.8:32000 |
| 125 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 126 | NSVCI=257 Creating NS-VC with Signal weight 1, Data weight 1 |
| 127 | NSEI=256 RESET procedure based on API request |
| 128 | NSEI=256 Tx NS RESET (NSVCI=257, cause=O&M intervention) |
| 129 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=257) |
| 130 | NSEI=256 Tx NS UNBLOCK (NSVCI=257) |
| 131 | NSEI=256 Rx NS UNBLOCK ACK |
| 132 | NSEI=256 Tns-alive expired more then 10 times, blocking NS-VC |
| 133 | NSEI=256 RESET procedure based on API request |
| 134 | NSEI=256 Tx NS RESET (NSVCI=257, cause=PDU not compatible with protocol state) |
| 135 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=257) |
| 136 | NSEI=256 Tx NS UNBLOCK (NSVCI=257) |
| 137 | NSEI=256 Rx NS UNBLOCK ACK |
| 138 | NSVCI=65534 Creating NS-VC with Signal weight 1, Data weight 1 |
| 139 | Unable to resolve NSEI 256 to NS-VC! |
| 140 | NSVCI=257 Creating NS-VC with Signal weight 1, Data weight 1 |
| 141 | NSEI=256 RESET procedure based on API request |
| 142 | NSEI=256 Tx NS RESET (NSVCI=257, cause=O&M intervention) |
| 143 | All NS-VCs for NSEI 256 are either dead or blocked! |
| 144 | NSVCI=257 Rx NS RESET ACK (NSEI=256, NSVCI=257) |
| 145 | NSEI=256 Tx NS UNBLOCK (NSVCI=257) |
| 146 | All NS-VCs for NSEI 256 are either dead or blocked! |
| 147 | NSEI=256 Rx NS UNBLOCK ACK |