ok, I am not a fw expert but this is what I found. we were actually getting
15:40:11 drop Custfw005 >eth-s2p2c0 proto tcp src 10.1.35.118 dst 10.28.78.204 service tcp-80-90 s_port 4959 rule 34 reason: port belong to service in TCP Fast Mode, port: tcp-80-90
So I looked at the services and...
Chris, Yes it is a site to site vpn. I think the encryptiondomains are correct. It drops on www traffic, but I see decrypts on other traffic types from the same source.
Hi all, I was just wondering how (where) I could find a readable version of the rulebase on the fw. I would like to see whats actually there versus whats on the gui. Also, is there a way (where would I find it) to view the same rulebase on the emc? Thanks.
Site Manager is available from Nortel, you can download it from their web site. If you are unable to do that the walusoft TFTP suite can be downloaded from any of the major utilities sites (tucows, cnet, zdnet...)
Try using a standard tftp client (walusoft? from zdnet or tucows?), and make sure to "enable tftp" on the router itself. The nortel website is a good source for documentation on all of the router commands. If you have nortel support they should be able to get you the bat files.
Is there a tool (Ciscoworks?) that you use to keep track of all the inventory (chassis, blades, spares and so on) for your networks? Is it a distributed datbase tool? Thanks.
Wondering if anyone has a prefered tool for tracking all of the components (ie: chassis, blades, fres, spares and so on) for BLN's and BCN's. Is there a distributed database tool?
not sure about access nodes, but on the Bays I've seen if you have a blade with a known password (say from a spare router) you can install the blade in the other router and use the known password for access, then reset the password on the entire router. ie: the password on a newly...
Have you tried the refresh method?, I think this is similar to an error I was recieving when I'd try to add a second record and would get a 3426 runtime error.
We configured mtu settings on the Cisco at 4470 on the Bay at 4495. the cisco sees some giant packets<br>
at 4182, but the link functions and is stable. When we dropped the mtu settings on the Bay the link <br>
became unstable. We were wondering what the giant packets were. BTW this atm...
We configured mtu settings on the Cisco at 4470 on the Bay at 4495. the cisco sees some giant packets<br>
at 4182, but the link functions and is stable. When we dropped the mtu settings on the Bay the link <br>
became unstable. We were wondering what the giant packets were. BTW this atm...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.