I never used the show running-config, so I did some quick tests:
[root@LABBIGIP1:Active:Changes Pending] config tmsh show running-config > show.txt
[root@LABBIGIP1:Active:Changes Pending] config tmsh list > list.txt
[root@LABBIGIP1:Active:Changes Pending] config ll
...
-rw-r--r--. 1 root root 132912 2017-03-14 13:22 list.txt
...
-rw-r--r--. 1 root root 132912 2017-03-14 13:21 show.txt
[root@LABBIGIP1:Active:Changes Pending] config diff list.txt show.txt
[root@LABBIGIP1:Active:Changes Pending] config
So, both commands are the same.
I guess because a lot of people are used to Cisco CLI, F5 just create show running-config as an alias for list command.
I am saying that because this command does not follow tmsh rules.
In tmsh commands, list is for listing the configuration, and show is for showing the object status.
The following 2 commands provide different things:
[root@LABBIGIP1:Active:Changes Pending] config tmsh list ltm pool pool_http
ltm pool pool_http {
members {
LABServer1:http {
address 172.16.0.11
session monitor-enabled
state up
}
LABServer2:http {
address 172.16.0.12
session monitor-enabled
state up
}
LABServer3:http {
address 172.16.0.13
session monitor-enabled
state up
}
}
monitor http
}
[root@LABBIGIP1:Active:Changes Pending] config tmsh show ltm pool pool_http
---------------------------------------------------------------------
Ltm::Pool: pool_http
---------------------------------------------------------------------
Status
Availability : available
State : enabled
Reason : The pool is available
Monitor : http
Minimum Active Members : 0
Current Active Members : 3
Available Members : 3
Total Members : 3
Total Requests : 16
Current Sessions : 0
Traffic ServerSide
Bits In 78.3K
Bits Out 109.5K
Packets In 60
Packets Out 45
Current Connections 0
Maximum Connections 7
Total Connections 7
Connection Queue Pool Pool and members
Number of connections queued now 0 0
Number of connections serviced 0 0
Queue head entry age (ms) 0 0
Maximum queue entry age ever (ms) 0 0
Maximum queue entry age recently (ms) 0 0
Average queue entry age (ms) 0 0
[root@LABBIGIP1:Active:Changes Pending] config