Руководство По Обслуживанию для Cisco Cisco Packet Data Gateway (PDG)
Generally Available 06-30-2010
Modified Configuration Commands
3-91
CLI (Context Configuration Mode)
ip pool name { ip_address subnet_mask | ip_addr_mask_combo | range
start_ip_address end_ip_address } [ private [ priority ] | public [
priority ] | static ] [ tag { none | pdif-setup-addr } ] [
address-hold-timer seconds | alert-threshold [ group-available | pool-free
| pool-hold | pool-release | pool-used ] low_thresh [ clear high_thresh ] ]
[ group-name group_name ] [ include-nw-bcast ] [ nat priority ] [
nexthop-forwarding-address ip_address [ overlap vlanid vlan_id ] [
nw-reachability server server_name ] [ respond-icmp-echo ip_address ] [
resource ] [ send-icmp-dest-unreachable ] [ explicit-route-advertise ] [
srp-activate ] [ suppress-switchover-arp ] [ unicast-gratuitous-arp-address
ip_address ] [ policy allow-static-allocation ] [ nat-one-to-one [ [
alert-threshold [ { pool-free | pool-hold | pool-release | pool-used }
low_thresh [ clear high_thresh ] + ] [ nat-binding-timer binding_timer ] [
on-demand ] [ send-nat-binding-update ] + ] | napt-users-per-ip-address
users [ [ alert-threshold [ { pool-free | pool-hold | pool-release |
pool-used } low_thresh [ clear high_thresh ] + ] [ max-chunks-per-user
chunks ] [ nat-binding-timer timer ] [ on-demand ] [ port-chunk-size size ]
[ port-chunk-threshold chunk_threshold ] [ send-nat-binding-update ] + ]
no ip pool name [ tag { none | pdif-setup-addr } ] [ address-hold-timer |
alert-threshold [ group-available | pool-free | pool-hold | pool-release |
pool-used ] ] [ group-name ] [ include-nw-bcast ] [
nexthop-forwarding-address ] [ nw-reachability server ] [ respond-icmp-echo
ip_address ] [ send-icmp-dest-unreachable ] [ explicit-route-advertise ] [
send-nat-binding-update ] [ srp-activate ] [ suppress-switchover-arps ] [
unicast-gratuitous-arp-address ] [ policy allow-static-allocation ]
Web Element Manager Path
This functionality is not supported at this time on the Web Element Manager.
readdress server commands in inbound IPv4 ACLs
Prior to Release 8.3, for packets received from the packet data network destined for a
subscriber's UE, the system applied logic to reset the source address of a packet to the
original destination address of the input packet before applying the outbound ACL (access
control list). In Release 8.3 and higher, the system reverses the order and applies the
outbound ACL before resetting the source address. This change impacts all current
readdress server rules in inbound IPv4 ACLs.
subscriber's UE, the system applied logic to reset the source address of a packet to the
original destination address of the input packet before applying the outbound ACL (access
control list). In Release 8.3 and higher, the system reverses the order and applies the
outbound ACL before resetting the source address. This change impacts all current
readdress server rules in inbound IPv4 ACLs.
After upgrading to Release 8.3, for every readdress server rule in an inbound IPv4 ACL,
customers must now add a permit rule to an outbound ACL that explicitly permits packets
from the readdress rule's redirect address and port number. If customers omit this permit
rule, the system will reject all packets destined for the subscriber's UE from the readdress
rule's redirect address and port number.
customers must now add a permit rule to an outbound ACL that explicitly permits packets
from the readdress rule's redirect address and port number. If customers omit this permit
rule, the system will reject all packets destined for the subscriber's UE from the readdress
rule's redirect address and port number.