About tsm_

tsm_ · ‎10-23-2013

Hello VVJ, I have also trouble by SPE management cause there is no display in the header about the hostname and used ip addresses, so I agree with Ate. At the moment I created a jpg file for every SPE which includes the hostname, the internal, external and management ip address and a customer name and put it to the "Default UI" under Administrative Roles. It would be nice, if the SA could provide such a function out of the box. Features I am missing or can«t find until now in 7.4: - is it possible to configure the management interface as source Interface for all DNS queries ( including hostnames in roles )? For management traffic the definition of source interface is very easy and I would prefer that DNS queries take the same way to our LDAP/DNS servers. - how could I use native ethernet and VLAN«s on the internal interface of a SA SPE without Nexus 1000V as dvswitch? Vsphere doesn«t provide native ethernet on trunked interfaces and the SA SPE use native ethernet for DNS queries so I can«t use VLAN`s. Maybe you could give me some hints how I could fix it. Regards, Thilo

tsm_ · ‎11-06-2012

Does anybody knows if version 7.3 is supported on SA4000 hardware? There is no 7.3 software package available under SA4000 but other packages for SA4000/SA4500/SA6000 have all the same size. Maybe it is the same file for multiple hardware? In the document "Supported Platforms", chapter "SA Hardware Requirements" I could find the line "Junos Pulse Secure Access Service 4000/6000- FIPS". Does this mean SA 4000 and SA6000-FIPS or SA 4000-FIPS and SA6000-FIPS? Thanks & Regards, Thilo

tsm_ · ‎06-18-2012

I am running in the same problem. Cause I do not want to use "Pass Through Proxy or JSAM" I hope that Juniper could provide a solution based on the java rewriting mechanism. How does the current solution looks like? thanks and regards, Thilo

tsm_ · ‎10-24-2009

If you would provide WSAM and JSAM for the same resources in your network, you have to create, manage and troubleshoot WSAM and JSAM rules. It is a nice way to double your work. Be sure that you can handle this. An easy way to provide WSAM and JSAM at the same time is via different realms, one realm for WSAM and one realm for JSAM. regards tsm

tsm_ · ‎03-15-2008

Hi all, I had some problems configuring the VMware distributed switches v5.5 in conjunction with a SA SPE and VLANs on the internal interface. The Juniper document "AppNote-Virtual-SA-appliance-with-VLAN1.pdf" only provides information for older VMware versions and I can´t find a guide for VMware 5.5. So after some time, I found the following solution: - the VLAN configuration on the VMware distributed switch should look like VLAN Type = VLAN Trunking, VLAN trunk range = 0, 10,30, where 0 = the untagged internal interface of the SPE and 10,30 are two tagged VLANs - on the physical Cisco switch I configured the native vlan on each port connected to the vSphere Servers. ( switchport trunk native vlan xyz ) That´s all, without additional or dedicated ports for the SA SPE. Hope someone could use this information Regards, Thilo

Re: Pulse Secure Access Gateway 7.4 Features at a ...

Software Version 7.3 Support for SA4000?

Re: Splunk Web Pages and the SA box

Re: WSAM and JSAM

SA SPE meets VMware 5.5