Hello, We are in the plans to add a 525 to a customers network which is currently utilizing a 6509 with ACL's for all intra-campus routing and interfacing to the internet. The internet is provided by a special ISP of sorts as it serves connectivity to various school districts in the county. The 6509 is currently utilizing secondary addresses on the internet vlan for TCP/IP based printing through nat. (hard to explain)
ie. Interface vlan100 ip address 63.x.x.x 255.255.255.x ip address 192.168.10.x 255.255.255.0 secondary ip nat outside ip nat inside source static 10.10.10.10 192.168.10.5 (NAT'd TCP/IP Printer) Basically the ISD (ISP for school districts) has their routers configured to forward traffic destine for 192.168.10.x to the 63.x.x.x address on VLAN100 which in turn has a secondary on the 192.168.10.x subnet. From there the NAT takes place to the 10.10.10.10 internal printer. With the plans to add a pix to the network, my plans are to move the 63.x.x.x network to the outside interface and the inside will reside on a 10.x.x.x network consistent with the campus IP schema. My question is can similar functionality be taken over for the 'secondary' addressing NATs? I read a similar post that stated that as long as the upstream router from the ISD is configured to route properly for the NAT'd 192.168.10.x subnet to the outside of the PIX interface, I can from there have static NATs in the form of: static (inside,outside) 192.168.10.5 10.10.10.10 (or similar) Otherwise is there another way to accomplish this functionality similar to secondary address functionality of the IOS based platforms? Possibly trunking with logical interfaces using the 6.3 code? Thanks! Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=70635&t=70635 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
