I haven't had any issues from 6.3 to 6.5... but 7.0 has me scared to update(since we don't have a lab unit to test on)
Is network connect replaced by pulse? is pulse optional?
After reading the release notes it seems like so much has changed that if I load it on my production box everything is going to be instantly broken. (hostchecker/network connect)
Anyone have any experience loading it on a production box? We really need some of the new features for exchange 2010 etc
Further to yesterdays post, my SA2500 is now running.. Seems after upgrade it restarted as expected, but in the log files, it says that it could not reach the gateway address.. ( i connected via the console serial port ) Very odd, its directly plugged in.. I rebooted it from teh console, and then everything popped into life..
So, it does upgrade, but my box seemed to have a hicup. Had i been on site i would have been able to get it going very quickly, but there you go..
Its the one box in the network that i don't have out of band network access to, so i was FORCED into taking a 'rookie-drive'.. ( rookie-drive, is what Junior engineers have to do, when they do jobs and have not quite thought through all the consquences..).. Sigh, just goes to prove that the humans are the weakest link
Pulse is optional; at it's simplest it is just another option for the L3 VPN connection.
Is there anything specific in the release notes/what's new that causes concern with the 7.0 release (other than Pulse)?
pulse will be listed under network connect, is optional and in my opinion blows NC out of the water since for laptops it will supress the wirless while its connected and DOES NOT break a connection as described below
Network ConnectÑWhen creating a tunnel with split tunneling disabled, Network
Connect removes existing default network, local subnet and host-to-host routes. (The
local routes are restored when the Network Connect session is terminated.) This change
forces all traffic through the tunnel. For example, if a user is connected to a home
network and, while sending an FTP stream, the user initiates a Network Connect VPN
connection, the FTP connection loses its connection to its destination host. The FTP
stream continues only after the interface updates its IP configuration, which must
come from the settings provided by the tunnel.
Junos PulseÑWhen creating a tunnel with split tunneling disabled, Junos Pulse
establishes the tunnel on a Junos Pulse virtual adapter and creates duplicate default
network, local subnet, and host-to-host routes with lower metric values than the
physical interfaces. Connections that exist prior to when Junos Pulse establishes a
tunnel continue to operate and pass traffic outside of the tunnel. For example, if a user
is connected to a home network and, while sending an FTP stream, the user initiates
a Junos Pulse VPN connection, the FTP stream continues uninterrupted along its original
interface according to that interfaceÕs IP configuration. If a packetÕs source IP is the
physical interface IP, then the packet is sent from that physical interface.
one more thing i have noticed with 7.0R1 is my CPU usage normally sat at 60% during peak hours, after upgrade CPU sits at barely 20% during peak hours and maybe 5% off peak, and by peak i mean 85+users connected and off peak anything below that, seems like right around 80-85 users is when cpu ramps up.
Which question were you concerned about? If it is Pulse as a replacement for Network Connect: No, it is not a replacement but an optional L3 connection that can be used as a replacement if you wish.
The upgrade from 6.3 to 7.0 is supported (this is in the 7.0R1 release notes).
Thanks for your response. I should have been more specific.
We are a large enterprise and getting ready to upgrade from 6.3. Since 7.0 is new, and 6.5 is a stable platform we were evaluating different needs.
Although iPhone is not a drop dead requirement , is it supported on 6.5
Is there a a large population that has deployed 7.0.
Appreciate your comments.