Cisco Cisco ASR 5700 Fehlerbehebungsanleitung
In that state, for EGTPC there MAY be some peers for which the Restart counter is reported,
while most may be 0. This occurs for situations where the peer is actively sending echo
requests to which ASR5K should be responding. The restart counter can be determined by
running the EGTPC test command (discussed next), though in the inactive state, the counter
will not be updated in "show egtpc peers" even though it was received. Meanwhile for
GGSN, the restart counter is never forgotten.
while most may be 0. This occurs for situations where the peer is actively sending echo
requests to which ASR5K should be responding. The restart counter can be determined by
running the EGTPC test command (discussed next), though in the inactive state, the counter
will not be updated in "show egtpc peers" even though it was received. Meanwhile for
GGSN, the restart counter is never forgotten.
Note a couple peers below that have counts much higher than the other peers. These are for
SGWs that are physically located in the same site or the sister site of the PGW to which the MME
funnels most calls.
SGWs that are physically located in the same site or the sister site of the PGW to which the MME
funnels most calls.
Note that running this command on an Inter-Chassis Service Redundancy (ICSR) standby node is
only relevant for active peers, in which case the numbers should be close, for example in the
following pair:
only relevant for active peers, in which case the numbers should be close, for example in the
following pair:
PGW> show egtpc peers ... 20:51:52 (ACTIVE)
PGW-ICSR> show egtpc peers ... 20:51:51
(STANDBY)
(STANDBY)
Peer
RC
#
sessions
sessions
Max Sess Peer
RC
#
sessions
sessions
Max
Sess
Sess
AESKS
192.0.2.5
2
31
443 ADSKS 192.0.2.5
2
31
443
AESKS
192.0.2.2
4
4
3
117
123 ADNKS
192.0.2.2
4
4
3
117
123
AESKS
192.0.2.3
6
6
15
4223
6889 ADSKS
192.0.2.3
6
6
15
4223
6889
AESKS
192.0.2.4
4
4
7
119
331 ADSKS
192.0.2.4
4
4
7
119
331
AESKS
192.0.2.6
8
8
34
6174
9798 ADSKS
192.0.2.6
8
8
34
6171
9797
AESKS
192.0.2.6
9
9
7
2311
5027 ADSKS
192.0.2.6
9
9
7
2311
5027
AESKS
192.0.2.8
8
8
17
3914
8880 ADSKS
192.0.2.8
8
8
17
3913
8874
AESKS
192.0.2.1
64
64
16
833705 1298070 ADSKS
192.0.2.1
64
64
16
832037 1294412
AESKS
192.0.2.1
84
84
3 1438418 2153317 ADSKS
192.0.2.1
84
84
3 1435461 2147280
AESKS
192.0.2.1
93
93
21
11447
26577 ADSKS
192.0.2.1
93
93
21
11443
26568
AESKS
192.0.2.1
95
95
5
48
162 ADSKS
192.0.2.1
95
95
5
48
162
AESKS
192.0.2.2
26
26
21
1962
3931 ADSKS
192.0.2.2
26
26
21
1962
3931
AESKS
192.0.2.2
27
27
6
4465
9332 ADSKS
192.0.2.2
27
27
6
4466
9332
"egtpc test echo" is used to check a specific peer to see if it is reachable or not and must be run
in the context where the service is defined.
in the context where the service is defined.
Use gtp-version 1 for GGSN-SGSN connections
●
Using ping command is not a valid test, though if it is successful, it is known that there is some
level of reachability.
level of reachability.
●
The peer restart counter (Recovery) is displayed.
●
Running this command will increment the Tx echo request / Rx Echo response counters in
"show egtpc statistics"
"show egtpc statistics"
●
The restart counter of the peer is reported after Recovery keyword (11 in example below)
●
Warning: though this should not happen in normal circumstances, if a test echo is performed
●